Because ME_16.0_Cons.bin is not ME Sub Partition itself, it’s a prestitched FWUpdate for some Lenovo platform. You have to decompose it first using MFIT, to get unconfigured ME Sub Partition.bin, as you can see on screenshot.
Then you can try to use it for cleaning your initialized bios dump, although it is not recommended to use Extracted type.
1 Like
@Anton35 Sir you are well deserving my thanks! Spot on with your description. I had no idea that I would need to further decompose the station-drivers provided ME. Thank you very much for your help, i can now see with ME Analyser that “File System State │ Configured” which i assume the correct one.
CSE ME 16.50.0.1232 Production Atom LP Unknown A
PMC 160.50.00.1008 Production Independent Unknown ADP
PCHC 16.50.0.1013 Production Independent ADP
PHY 14.14.508.4007 Production Independent N ADP
v16.50.0.1232.bin.zip (2.1 MB)
1 Like
hello everyone; i tried to clear a BIOS 64MB of DELL XPS 15 9520 La-l402p, but i got some errors! i don’t know what have to do…
‘’‘ERROR : Decompose ‘C:/Users/Line_teck/Desktop/XPS 15 9520 La-l402p r1.0 Gagarin .BIN’ image failed.
Details: Intel(R) AlderLake P Chipset - Corporate - SPI not found in the available layouts’’
A post was merged into an existing topic: Intel (Converged Security) Management Engine: Drivers, Firmware and Tools (2-15)
How to correct this error? Layout dictionary generated successfully
“ERROR : Failed to initialize MFS.
ERROR : Failed to instantiate container CseRegion:0.1”
when trying to decompress 16.1 image
Heya,
I have came across the following error while I tried to clean the ME:
I receoved a FW image for my laptop for which the bios chip was blown up. I attempted to clean the ME region using MFIT Intel tool of the right version because MEA tool was showing “Initialized” instead of “Configured”. I can decompose the image but unfortunately I am getting the following errors when I try to assemble the image.bin even when I am not touching the ME part (simple decompose and then immediately build):
Start decompose ‘D:/bios/latest badcap/FX517ZM.bin’ image.
MFIT version used to build the image: 16.0.15.1662
WARNING : Skipping ROMB. Missing…
WARNING : Skipping FDCR. Missing…
Decompose ‘D:/bios/latest/FX517ZM.bin’ image completed successfully
Build ‘p:\Gen\HW\BIOS MOD\CSTXE System Tools v16\Modular Flash Image Tool\WIN32\image.bin’ start…
ERROR : Failed to build container: CsePlugin:AutoNvars
ERROR : NVAR ProcEmulation file at path policy/cfgmgr/cfg_rules is readonly…
Source: ‘CsePlugin:AutoNvars’
Would anybody happen to know how to deal with this? Can I try to flash the image even though the bios is “Initialized”?
Many thanks!
CSE ME 16.1.30.2307 Prod ConH ‘Unknown’
PMC 160.2.00.1043 Prod H A ADP
16.302307_1602001043.zip (1.8 MB)
EDIT:
I think this one might be new, too?
Can be found here:
https://fwupd.org/lvfs/devices/com.dell.uefie428af72.firmware
3 Likes
From the PRIME-Z790-A-WIFI-ASUS-1601
MFIT Version 16.1.30.2319
MFIT Core Version 1.1.0
Image Layout Intel(R) RaptorLake S Chipset - Consumer - SPI - A0
Versions:
Important! Versions shown below are applicable to image build time.
In case of FW update for IUP, its version may not be reliable.
ME 16.1.30.2307
PMCP 160.2.0.1043
NPHY 13.62.211.7255
PCHC 16.1.0.1014
SPHY 13.0.1.7085
Available package also @ST
I am after a tool that would allow me to flash 16.1.30 ME firmware. I already have the bin so don’t need to build it or anything like that but need either the Linux or EFI version of FWUpdLcl.
I’ve been through this entire thread carefully (I think?) and there is a Linux version that works with the previous gen (16.0.something) and MFIT for 16.5 (MFIT can’t flash though it seems only modify).
Does anyone have the above or at least know a good way to go about finding it? The original vendor is MSI who afaik are very “we dont support Linux go away”.
Also I know I could use Windows PE but last time I tried to boot up Windows PE it just froze and screwed up some EFI vars. I’d also like to keep the tool handy for future updates.
Thank you, unfortunately unless im missing something (which I probably am!) that only has Windows versions of FWUpdate. It does have “fpt.efi” but that appears to be more for system BIOS
Modular Flash Image Tool (WIN32): 16.1.25.2091
Modular Flash Image Tool (LINUX64): 16.1.25.2053
Flash Programming Tool (EFI64): 16.1.25.2049
Flash Programming Tool (WIN64): 16.1.25.2049
What seems to be the trouble here… bad English or blurry display…
And where did you got the ideia of and EFI driver being a system bios file???
By the content of your words… you have no knowledge of this tools and so on… we do not encourage inexperienced users to mess with this and get a bricked system.
Anyway, its a user choice, thats it, good luck.
EDIT: Oh…no offense taken at all… welcome to my fan list of “Straight words hatters”, cheers!
1 Like
yes mate my screens broken and I can’t speak English (or any language for that matter). Clearly asked for LINUX or EFI versions of FWUpdLcl (FWUpdate) or advice on how to seek.
I am so sorry that I offended you so deeply by not instantly knowing what FPT.EFI does (which I now do and will try as a last resort).
Thanks for your “help”, thanks even more for your crappy attitude
edit: looked more into fpt.efi, says that region (ME) is locked and the guides for unlocking it feel a bit heavier than what I want to get into at the moment - I don’t want to brick this system. Thanks again for the link though!
Since you didn’t specified motherboard/model… look for any ME_jumper on the board, usually found on “branded” systems, not on laptops or retail motherboards.
Just to mention: The images used by FWUpdLcl and FPT are different!
FWUpdLcl uses an update image (configuration irrelevant since just the code gets updated, FPT would flash either a complete firmware image (which should contain your specific ME configuration and the board specific data in bios region) or just an ME region (which should have correct and specific configuration and size!
1 Like
Just to mention: The images used by FWUpdLcl and FPT are different!
Thank you for pointing this out. Fortunately, I was trying to just flash what I had just dumped out of the current firmware to check the method.
FWUpdate_16.1_Linux64.zip (144.1 KB)
Thank you so much!!! Works perfectly!