I have flashed the bios dump but the laptop turns on with a black screen. The bios chip of this laptop has already been flashed by someone else. The laptop works randomly, so I am assuming that it is a problem with the bios. But, I noticed that MEA shows an error message:
Error: Firmware is incomplete/corrupted, expected 0x600000 not 0x400000!
Warning: Firmware size exceeds Engine/Graphics region, possible data loss!
Note: Adjusted buffer to Flash Descriptor 0x0 - 0x600000!
I downloaded several bios dumps from the internet, exactly 5 bios dumps, but MEA displays the same error message in all of them. Are all the bios dumps I downloaded corrupted? I donāt quite understand what this MEA error message means. So, I donāt know exactly what to doā¦
The one 4 MB chip isnāt a working bios, MEA expects the sum og buth chips!! And you may flash the 4 MB chip as often as you want- if the 2 MB chip isnāt flashed with the proper image- part the machine will not boot!
FIT expects a full firmware image to work (or in older versions the ME region alone can be used).
MEA compares firmware size given in FD with real firmware size and complains, but it works fine.
Both donāt care what it is in the bios region- you could givr the an image with a bios region filled with just FFs and they wouldnāt complain - but your machine wouldnāt boot, of course.
EDIT
REgarding the 2 MB chip: FIT works with what you give to it, bios region (which the 2 MB most probably contains part of) is copied unchanged when FIT builds an outimage- thereās no check if this is a valid regionā¦
So it might simply be a misplaced soic clip that gave you just FFs for the second chip.
What machine are we talking about and please post the dump of the first 4 MB chip
I have tried to clean a (CS) ME Region of a dumped file, however during the process of building image the following error was showed up in FIT environment:
Error 197: [Fit Actions] Invalid settings combination. If āEOM on First Boot Enabledā is set to: āYesā, Then "Boot Guard Profile Configuration " cannot be set to: āBoot Guard Profile 3 - VMā
What is the best way to solve this error: Change the EOM parameter to NO or change Boot Guard Profile to another value, for instance: 4-FVE?
Why was it possible for LBE to clean (CS)ME Region of same file keeping EOM as YES and Boot Guard Profile as 3-VM, considering that they are invalid settings combinations?
See link below for Dumped and LBE Files: Microsoft OneDrive
Hello.
Iām wondering if you guys could help me (and many others, each one with itās own) with my old laptop Dell, model Inspiron 5557.
Since itās BIOS was updated via Windows Update (from 1.6 to 1.9) after a replace SSD and OS reinstall, an annoying screen with āā¦invalid configuration blablablaā¦ā appears everytime that we turn it on! Trying to downgrade to 1.6 again was successful, but Intel ME with final error 2236. Installed Intel MEI version still same as 1.9 BIOS: 11.8.77.3664, when 1.6 is 11.8.60.3561. I believe thatās related to dirty MEI Region. If I was correct, can you help us? Sorry for my bad english, and thank you for nowā¦
It would be nice to get a ārealā translation, preferable a human reading of that āBLABLAā of yoursā¦ and maybe we get a āpictureā of what is the SSD related to the Intel ME FW of a system.
Bios updates only upgrade the Intel ME FW when theyāre required to (system has lower/old version) than the payload package and ME FW is never downgraded by normal flash methods.
To the best of my knowledge, this is the latest version (9.1.45.3000). What is the problem with the current file format? I have updated them without any problems with FWUpdLcl64.exe. You donāt need to modify the files under v12. You can use !save.bat to save the existing version and write.bat to update it (9.1.45.3000_5MB_PRD_RGN_D8D49751).
The earlier versions of the HP ME update had a clean ME region that was byte copied to the ME area of the flash 1-to-1, and one byte was set to ā01ā to enable it to initialize upon boot.
So I wanted to extract the clean ME thatās 1-to-1 match to the flash region out of the ME update file, but it looks like itās sort of challenging with the bin files that are supposed to be used by FWUpdLcl64.exe
Before ME12 one could use a configured ME region for an update. But you canāt be sure that an update is configured properly for this machine since the update process doesnāt worry anout any configuration data but updates just the code partitions of an ME region. So the udate file might ot might not be configured correctly for your machine.
So you have to check the update file in FIT if it has the correct configuration, if so you might use it as a region. But whatās all this about?
The link you gave is a procedure to update older workstations from ME7 to ME8 and the MEBLAST folder contains a complete firmware image, not just the ME. So thereās no āearlierā, this is a single special case for the upgrade from ME 7 to ME 8.
Thatās different models, the one you asked for first is Z1 G2, Z228, Z230, Z440, Z640 and Z840 Workstations, the ones you mentioned later are for Z420, Z620, Z820, Z1 G1, Z210 CMT, and Z210.
What kinda machine do you want to update from which version to which version?
Of course, you are correct, these are 2 different workstation series!
I want a clean ME image for Z440 (exactly sized to the flash chip ME region), but using that early meblast-like procedure from Z420. So would be doing this on Z440 with clean ME 9.1:
fpt.exe -ME -f me91_clean_image.bin
Probably all data regions in the clean image will be filled with FF, except for byte 0x400 which would be ā01ā to initialize the ME.