I did, in order:
- fwupdlcl to latest 7 (no greset)
- fpt to HP FW 8 (no greset) (this is the one you sent me too)
- fwupdlcl to latest 8 (no greset)
- fpt back to HP FW 8 (no greset)
- fpt to FIT extracted HP FW ( WITH greset)

So, yes practically there was "fptw -me -f sp100751_J63_0396_ME.bin" twice, but without greset.

I did Reset to Defaults in bios after the flashes.
Maybe I should have used greset more often :D

Thank you, I will further investigate and try to reflash bios, maybe clear cmos via jumper,..
(I wanted to avoid the full flash because of the need of transferring MAC etc.)

I wonder what MEManuf* -verbose would tell you?

Otherwise the ME 8 package contains a Clock Commander Tool- all 'get' commands seem to be safe. I can't explain the output, but maybe there's an error message?

I understand that the 'No valid OEM data, ICC not programmed' is worrying you, but manufacturing mode shouldn't. My System is running in this mode all the time and that leaves me the possibility to flash ME since closing manufacturing mode would mean changes in flash region access. Probably not your problem since you have a jumper, but as far as I know also the only thing ending manufacturing mode does: Settting access rules to the ME-region...

By the way: Did you try meinfo with jumper on or off?

@lfb6 I wouldn't mind manufacturing mode or disabled ME.
At least in freedos everything seems fine, I don't know yet if something is wrong in some real OS.
All the ME-tools are working only without ME override.
I will try cct asap, thx! (When I have reassembled the PC)

I was going to try pinmod in the meanwhile. It didn't work yet and it seems easier to flash the chip via SPI.
After trying the pinmod on this tiny realtek the 16-SOP package of the flash appears really huge to me

For anyone interested and for the search engines, here some pictures of the HP Z820 rev 1.00 mainboard:

@lfb6
memanuf says "MEManuf Test Passed"
cct returns "ConnectClient() failed with status: 8205" with all read commands.
Doesn't seem to be a common error, I didn't find anything in internet

Zitat von maaax im Beitrag #20

---

.... memanuf says "MEManuf Test Passed"....

---

Zitat von maaax im Beitrag #19

---

.... All the ME-tools are working only without ME override......

---

@lfb6
It was already late yesterday after the boot block update.. Here some update!

Zitat

---

ME override?

---

The ME/FD-override jumper enables write to ME/FD but also disables ME.

@plutomaniac @Lost_N_BIOS @lfb6
Thanks for your help so far!
I was able to update boot block via SPI and the v2 cpu works great.

Regarding to "no valid OEM data" I tried reflashing BIOS, resetting CMOS, greset, fpt.. no success.
After reading this thread:

Zitat von plutomaniac im Beitrag ME gone after bios update - ME FW version 0.0.0.0 - could not fix it by sw so I decided to do some soldering

---

.. 8.1.60.1561 which makes no sense as it doesn't exist..

---

Zitat von plutomaniac im Beitrag [Guide] Clean Dumped Intel Engine (CS)ME/(CS)TXE Regions with Data Initialization

---

....
[li]If you are working on FITC v8.1.40.1456 with ME 8 firmware which is configured as any "Intel (R) C600 Series Chipset" (Patsburg SKU), then you must use a ME region only for the cleanup process and not a SPI/BIOS image. So if you have a SPI/BIOS image, first extract the ME region and then load it to FITC. That is due to a FITC bug in which Patsburg settings are not properly shown/transferred when using anything but a bare Engine region image. More info can be found here. When you load the bare ME region at FITC, if the SKU at the top bars does not match what you see when loading the full SPI/BIOS image, make sure to first adjust that accordingly and don't leave it empty or different.
.....

---

I'm sorry, "self-cleaned" was meant like 'using the tools available for creating and testing, which were supposed to work together' and check if it'd be possible to get a ME region which passed all checks.

But I totally agree, there's no meaning in this. HP should've had the latest tools (if there might be a newer version) and they'd know best how to create a working bios for this PC... And with a buggy toolset there's possibly no way to get 'correct' settings since one doesn't know which values were the right ones...