Good morning, Mister
I want to tell you what happened with me yesterday
I took off the chip the BIOS and promised to ship it
There was a big error and a unique identifier changed uuid
Two letters FFFFFFFFFFFFFFFFFFFFFFFFFFFF In this way
With this error, the Internet did not work in any way
I returned the old BIOS that was on the machine
The letters returned again
Please help me what to do
What are you doing??? BIOS Chip was fine, did not need removed, or re-programmed etc. we can do all that with software. Maybe only thing you should have done with programmer is unlock the FD
Of course, if you put BIOS without your board specific details in there it’s not going to have you UUID or LAN MAC ID etc (Serial number gone too)
Did you backup your BIOS before you wrote new BIOS? If yes, put that backup BIOS back onto the chip.
I have no clue where you are now, what BIOS is on there etc.
From your MEInfo - verbose, it looks like you either do not have AMT enabled in BIOS, or do not have drivers installed in windows, or both.
I checked the 7G7_0114.bin BIOS/ME and it has AMT enabled in the ME, so you need to enable in BIOS and then install drivers
Yes I took a backup Yes, this backup is on the slide.
I am from Egypt
I’ve already backed up the backup
Thus, the letters of error were returned as shown in the attached pictures
Please stand by me until the mistakes are finished
If you put back on backup of where we were, you would not see HECI error again 
Please take images of your BIOS, all pages and all settings within each section and put in a zip file, so I can see about AMT options in your BIOS.
Also, please show me an image of any stickers showing model numbers on your system. Do you know if it’s DV8000, ZD8000, NC8000
No backups of where we were
I will re-create the image file you requested
And come back again
Ohh, back to square one? Run all three of the below in order
FPTw.exe -f 7G7_0114.bin << After this, shut down and put on FDO Jumper, then boot to windows and run next two commands.
FPTw.exe -me -f 7G7_0114.bin
FPTw.exe -greset
Once done, on reboot enter BIOS and load optimal settings and save/exit and boot to windows. Once in windows, shut down, remove the FDO jumper again, then boot back to windows.
I found this for you, looks like you have to enter MEBx first (Control + P at post screens, during startup), to enable AMT
http://h10032.www1.hp.com/ctg/Manual/c01954655
And this, which shows some of the BIOS settings info (Look at Management section)
https://support.hp.com/us-en/document/c01941927 Ads!
https://support.hp.com/si-en/document/c01941927
Photos you requested
You edit the photos and arrange them so that they are clear with you
I am sure you will solve all the problems
And thank you from the depths of my heart
Desktop 1.rar (5.55 MB)
Desktop 2.rar (5 MB)
Desktop 3.rar (5.3 MB)
Desktop 4.rar (2.03 MB)
Thank you for the images, I will check Did you do as mentioned above in post #86, and read those links?
This is after running only the first command
Now turn off and put on the FDO Jumper
And running the following two commands.
FPTw.exe -me -f 7G7_0114.bin
FPTw.exe -greset
BIOS is OK anyway I think, so not important we reflash that
How does next two commands go, as shown?
After you run the following two commands.
FPTw.exe -me -f 7G7_0114.bin
FPTw.exe -greset
Nothing happened to you for illustration
Two small things:
1. Never ever use FPT regional arguments (-desc/-me/-bios/-pdr etc) with a full SPI image, give it exact regions only as input.
2. Don’t use the Windows versions of very old tools, read the Notice at Section C of Intel Management Engine: Drivers, Firmware & System Tools
I am very sorry I do not understand this talk
Sorry this is not my problem it’s a personal problem
Please help with the simplest way
I am really sorry
The commands do not work
Please help
I changed the version of Windows from 32 bit to 64 bit
Yesterday it is possible to affect the operation of orders
After installing the definitions by the manufacturer of the device get errors in the device manager
This triangle is yellow
I hope the pictures help to clarify and solve the problem
Greetings to you
Plutomaniac thanks for your advice, I was not aware of #2 issues. And I have never seen anyone mention what you say at #1, I see FPT used with regions and full image all the time, even by you I thought, must be wrong 
You should have warn me on this sooner 
, I’ve been having people fix things that way for long time and no one mentioned this before. However, thank you for the warning, I will have to retrain my brand and keep this in mind!
Also of note here, all this was fixed (except he needed to enable AMT via MEBx) until he removed the chip and put back on old BIOS without backing up the fixed BIOS!
Can you please tell me how to check if the ME below has programmed OEM data, so if he cannot boot DOS I can maybe have him flash this ME via FPT instead, if it’s ready ME (It’s not from SPI image, it’s from MW FW Download on HP site)
@efraym - ME drivers need installed, and you need to follow the guides I linked you to in post #86 order to enable AMT at the BIOS level, it can only be done on your end via MEBx interface
Right now, I think BIOS and ME is fine, unless you are still, again, getting the 2233-HECI error at bootup?
If still 2233-HECI Error, please download the following ME and FW Update tool from the “DOS” Folder, then run this command from DOS Bootable USB or CD and then reboot
FWUpdLcl.exe 52501039.BIN
http://s000.tinyupload.com/index.php?fil…852817260455915
If you end up having to try from windows, use the following command instead
FWUpdLcl.exe 52501039.BIN -generic
The ability for FPT to read the FD of the image-to-be-flashed was added later, check the warning in the picture at post #73 and you’ll see how that could have gone terribly wrong if the FD jumper was set. No matter what, it is best to not trust that FPT will read the target image FD properly and tell it exactly what to do instead. As for the other stuff, ME 5 does not interest me to be honest due to age and obscurity. As you’ve seen, any configuration of a healthy firmware is done by MEBx (CTRL + P) and any info about its state is gathered by MEInfo.
I did see that, and wondered why! I didn’t know FPT had/has issues like this with older versions, I’ve never seen such on newer FPT except by user error (ie trying to use .cap BIOS, but at least then you get yellow size warning)
Thanks for the heads up about this, I will now try to always send region files when having someone issue region based procedures! Bummer you are not thrilled by this, me either, and I hoped you’d jump in and solve this already
I thought I did have it all sorted, and then he erased our progress, but that was before I knew he had to enable stuff from the MEBx so we still wasn’t sure at that time why things were not all working properly.
I suspect all will be fine again as it was, once he redoes the ME and gets rid of the HECI error. I’ll have to get him into the MEBx quick once that happens, so he doesn’t pull off the chip again yes, I know you are reading this @efraym - kidding around to give you a little laugh at our pain 
Thank you for cooperating with
1. Error messages appear now
2233-HECI Error
2-I could not update ME drivers
Because of the error in the picture below
Sorry, I forgot FW Update tool will not work while ME is messed up.
Please flash this extracted ME using FPT from DOS, put FDO jumper in place first, then remove once done flashing
FPTw.exe -me -f Extracted_ME.bin
http://s000.tinyupload.com/index.php?fil…598223764608278