Look like a corrupt ME, indeed. MeatWar gave you the link for the cleaning procedure already. This procedure is described for ME up to version 15, but 16.x will work accordingly.
For the Intel tools search for 16.1r0 in the forum. Try to make a dump with fptw64 -d SPI.bin
Unfortunately anti tampering / recovery features have been introduces widely in these generations notebooks. You should check for redundant information / other large SPI chips when dumping your firmware!
Thank you for the response. I am going to attempt to do all in the guide during the weekend. Hopefully all goes well.
The HP firmware update contains a complete Intel firmware image, so you could simply use the ME region extracted from this update and replace the ME region in your dump.
Your system might have a firmware TPM, so be sure to have secured the recovery information for every encrypted drive!
And again, make sure to check for recovery SPIs which may have duplicate information and to (cautiously) dump it, too.
So I have attempted all that said. I might be doing something wrong since I am always unable to go past all software related to fw update. The issue is that is just cannot detect the ME hardware and it cannot proceed. Is there something I am skipping or just ain’t doing right? Is there isn’t anything does that actually mean I will end up using the Programmer tool I mentioned in the beginning?
That’s very unspecific- “attempted all that said” isn’t very precise - conclusion is as you said “you’re might be doing something wrong”.
Attach the files you created / the dump you made or the commands used and their results- then we might be able to advise.
Sorry for making myself unclear, I was rushing and did not really check out what I was going to send.
I am going to redo all steps and document each step of doing the guides.
So Currently I dumped my SPI, got the file, analyzed that it’s 16.1.32.2418
and then got CSE ME 16.1.32.2418 Prod ConsH Unkn ADP_RPP.bin from this forum.
Now I will attempt to do the rest of the stuff and I will periodically update this forum.
Okay so now I might be dumbfounded somewhere around the part where the File System State is suppose to be Initialized rather than Configured, is there a way to make Initialized?
ME changes its state from configured to initialized when booting. So if this is a dump from a machine this ME never was booted.
So it never booted, then that makes sense why attempt to update with FW Tool ends up with error 20.
At this point I am really thinking of doing it the hardware way. But I will post here my files in case I missed something.
I am gonna keep on going to see what I can do.
Not following you here.
Onedrive has login?
That’s weird, it shouldn’t have one. I am going to try to upload here again.
Firmware Used.zip (2.2 MB)
FIT Generated.zip (7.5 MB)
HP Downloaded BIOS.zip (8.6 MB)
SPI2.zip (8.7 MB)
I don’t understand what you tried to generate with FIT.
But since HP does provide a complete firmware image you can simply use it. Transfer the first and second padding in bios region from your own dump to HPs firmware image.
Be aware that there’s the second NVRAM volume missing, the system will generate it automatically later. But that means that second padding not just begins after the NVRAM, but 0x40000 ‘later’, at 0x683000
The only change between a stock ME and the one in your dump is some bytes in FLOG partition.
Very unuasual, some sources refer to FLOG as crash log. Question is why ME never got initialized.
Again: Check the board for other SPIs with 16 MB or a little smaller to be sure it doesn’t have recovery information somewhere.
Do you mind telling me about the SPIs with 16 MB or a little smaller? What other software will allow me to extract more SPIs from the board? Sorry if it sounds somewhat stupid but I am lost abit.
You need to provide motherboard information, detailed hres photos, hp product number etc…
ex: SPS N35247-601… many modern systmes have multiple NOR flash ICs and we are not HP employes to have access to all relevant repair information/schematics of all system ww
In short:
I have to get every single information of my motherboard, including the actual text on the Mobo itself? like Disassemble the mobo and take pictures of the chip and the codes it has on it .
You do as you please sir…its your task only and the system is in your possession…not ours…
Didnt you mentioned the possibility of using a CH341 programmer in 1st post? Well… this is relevant for operation…like this example:
What did you expected… easy, magic work???
I am sorry, that sounded somewhat rude. I did not expect this to be an easy work. I played around bioses multiple times, sometimes success sometimes fail. I never did anything around HP bioses. I do know that I can flash the BIOS chip the hardware way. i will post the specs later on.
Does that mean im not expected anymore at “The Excelsior” for dinner and after-hours party with a bunch of twenties girls…all pay by you…damm sir, ill try to be more gently at you and more rude to my woman…some nervs!!!
Get on your “horse” do your job done and feal lucky if succeded…OVER_N_OUT…of here.
Nice.
Just posting my specs, I have decided to use the CH341 Programmer:
System Model: OMEN by HP Laptop 17t-cm200
(HP official website does not see 17T-CM200 as an actual model prob because it got discontinued, it is recognized as 17T-CK2000)
System SKU: 70W93AV
Bios: F.12
Motherboard: 8BAD
I am gonna post photos of the MicroChips I believe are bios chips soon.
I have managed to get the CH341A Programmer, I also found out that I have 2 winbond IC chips which i assume to be BIOS chips. One is near the CPU which as I have read from many threads (IC Bios chips are usually closest to the CPU) and one is the image that MeatWar showed. I think I will read both of the chips and compare which one’s data has something similar to that of Bios to determine which one is correct.
