Help please X1 carbon 9 gen Me region sku mismatch

[Filebin | vcx0xitevpjk9qts]

Attached is my bios dump.

What has happened is somehow the me sku has become mismatched.
its originally a corp sku
but somehow the updates had managed to install the consumer image on it and It wont update now with the updater due to the mismatch.

Thanks In advance

Sorry its
an x1 carbon 9th gen

drivers page is here
https://shorturl.at/b03u0

You’d have to re-initialize / clean the configuration of your ME according to this guide:

Unfortunately your ME configuration can’t be read any longer. You can take the already cleaned ME region of the file “X1 Carbon 9th Gen Laptop (ThinkPad) - Type 20XX.rar” in this thread (post #6 from hoaca388) and transfer this me region into your dump:

In addition part of your NVRAM does look a little suspicious to me- in my understanding there shouldn’t be a non-empty padding with NVRAM entries in it :

Easiest way would be to try the mentioned complete file from post#6 at the badcaps thread. This file did work at least there.
(You’re sure there’s no second bios chip- most probably half or same size- on the board? And be aware that you might easily brick your board)

I have played with it fair bit…
the following entry is causing my problem

C:\DRIVERS\WIN\ME\20240909.13141235>MEInfoWin64.exe -verbose
Intel (R) ME Info Version: 15.0.47.2521
Copyright (C) 2005 - 2023, Intel Corporation. All rights reserved.

Transactional FW Information
** Original image type Corporate**
** Current sku type Consumer**

I have got the machine working… but the only way to update me on it is to physically flash it … as it has the mismatch… entry…

it has a secondary chip too,

Filebin | nclv4chsim1fcvwl

that is that file.

I tried that file,
but the mismatch remained.

From my limited knowledge on this so far is there is a missmatch entry in the esrt table ? causing the issue… ?

Here is the current working one I have compiled…
emphasized text

You openend a thread at badcaps some days ago with the same question?

If you have a working one what’s this about then?

I still have the mismatch i cannot get it to update the me firmware

only way to update the me firmware is to manually flash it via a programmer
I am trying to fix the mis match

1 Like

The corrupt and the working image both have a Corporate LP firmware:

The dump of the second chip- did you change it or is it in its original unchanged state?

the second chip is in its original form

Yes they have the corp firmware
but there is a mistmatch in one of the tables causing the issue that cause s a mismatch error when you try to reflash the firmware…

I don’t think this is located inside the ME region itself.

How do you update? Capsule / non- capsule? Simply running the Lenovo file? Manuallt?

Please make a screenshot of the error message you get when trying to update.

If you’re working in Windows: Please make a screenshot of the content of the WIndows\firmware folder, should look like this:

Originally it was using lenovo vantage update
Machine would keep rebooting and trying to update and fail.

now i am using the downloaded firmware and non capsule.
As it allows you to flash the fimware

the folder

using the firmware check tool in the package

Now trying to flash the corp.bin

Screenshot of “c:\windows\firmware

c:\windows\firmware

this is on a clean install

Thank you!

Please delete the TglME_15_0-47-2521_Lp_Cons cap- file in C:\Windows\Firmware

The folder rely to firmware updates installed via MS update (see MS update catalog)
14F3350E-CF63-4E68-A0D9-0AF1D5389A17 is Bios
61B65CCC-0116-4B62-80ED-EC5F089AE523 is EC
486E285B-5A0E-4BA7-AC67-CDC1DB5861D5 is Battery Fw

I din’t find 0D803EE9-F231-4AD7-9CBB-563BCBE75C13
Could you open that folder and the Quectel folder and make a screenshot?

Regarding manual update- you need to give the Lenovo OEMID for all Lenovos I know about, it’s always the same: (So that error wasn’t related, but there might a new error when using the command with correct syntax)

FwUpdLcl -f ME_15.0_corp.bin -allowsv -OEMID 4C656E6F-766F-0000-0000-000000000000

Please send a screenshot with the result of the command.

0D803EE9-F231-4AD7-9CBB-563BCBE75C13

and quectel

flashing is successful.

device is still