Would’ve been interesting to read the complete output.
ME override? Again, complete command and output would’ve been nice. And it would be helpful if you could post a complete dump/ backup of this bios.
@lfb6
It was already late yesterday after the boot block update… Here some update!
The ME/FD-override jumper enables write to ME/FD but also disables ME.
Intel(R) MEInfo Version: 8.1.56.1541
Copyright(C) 2005 - 2014, Intel Corporation. All rights reserved.
Intel(R) Manageability and Security Application code versions:
BIOS Version: J63 v03.96
MEBx Version: 8.0.0.0072
Gbe Version: 1.3
VendorID: 8086
PCH Version: 5
FW Version: 8.1.60.1561
FW Capabilities: 0x0C7A5445
Intel(R) Active Management Technology - PRESENT/ENABLED
Intel(R) Capability Licensing Service - PRESENT/ENABLED
Protect Audio Video Path - PRESENT/ENABLED
Intel(R) Dynamic Application Loader - PRESENT/ENABLED
Intel(R) AMT State: Enabled
Cryptography Support: Enabled
Last ME reset reason: Global system reset
Local FWUpdate: Enabled
BIOS Config Lock: Enabled
GbE Config Lock: Enabled
Host Read Access to ME: Disabled
Host Write Access to ME: Disabled
SPI Flash ID #1: C22018
SPI Flash ID VSCC #1: 20052005
SPI Flash BIOS VSCC: 20052005
BIOS boot State: Post Boot
OEM Id: 00000000-0000-0000-0000-000000000000
Link Status: Link up
System UUID: …
MAC Address: …
IPv4 Address: 0.0.0.0
IPv6 Enablement: Disabled
Privacy/Security Level: Default
Configuration state: Not started
Provisioning Mode: PKI
Capability Licensing Service: Enabled
OEM Tag: 0x00000000
Slot 1 Board Manufacturer: Unused
Slot 2 System Assembler: Unused
Slot 3 Reserved: Unused
M3 Autotest: Disabled
Wireless Micro-code Mismatch: No
Wireless Micro-code ID in Firmware: 0x0082
Wireless LAN in Firmware: Intel(R) Centrino(R) Ultimate-N 6205
Wireless Hardware ID: No Intel WLAN card installed
Wireless LAN Hardware: No Intel WLAN card installed
Localized Language: English
Independent Firmware Recovery: Disabled
Intel(R) MEInfo Version: 8.1.56.1541
Copyright(C) 2005 - 2014, Intel Corporation. All rights reserved.
FW Status Register1: 0x1E000255
FW Status Register2: 0x61000100
CurrentState: Normal
ManufacturingMode: Enabled
FlashPartition: Valid
OperationalState: M0 with UMA
InitComplete: Complete
BUPLoadState: Success
ErrorCode: No Error
ModeOfOperation: Normal
ICC: No valid OEM data, ICC not programmed
Intel (R) Clock Commander Tool Version: 8.1.40.1456
Copyright (C) 2011 Intel Corporation. All rights reserved.
ConnectClient() failed with status: 8205
HECI INITIALIZATION FAILED
Intel(R) MEManuf Version: 8.1.56.1541
Copyright(C) 2005 - 2014, Intel Corporation. All rights reserved.
FW Status Register1: 0x1E000255
FW Status Register2: 0x61000100
CurrentState: Normal
ManufacturingMode: Enabled
FlashPartition: Valid
OperationalState: M0 with UMA
InitComplete: Complete
BUPLoadState: Success
ErrorCode: No Error
ModeOfOperation: Normal
ICC: No valid OEM data, ICC not programmed
Get FWU info command…done
Get FWU version command…done
Get FWU feature state command…done
Get ME FWU platform type command…done
Get ME FWU feature capability command…done
Feature enablement is 0xC7A5445
gFeatureAvailability value is 0x1
Request Intel(R) ME test result command…done
ME initialization state valid
ME operation mode valid
Current operation state valid
ME error state valid
Verifying FW Status Register1…done
Request Intel(R) ME test result command…done
vsccommn.bin was created on 04:35:50 08/08/2012 GMT
SPI Flash ID #1 ME VSCC value is 0x2005
SPI Flash ID #1 (ID: 0xC22018) ME VSCC value checked
SPI Flash ID #1 BIOS VSCC value is 0x2005
SPI Flash ID #1 (ID: 0xC22018) BIOS VSCC value checked
FPBA value is 0x0
No Intel vPro Wireless device was found
Request Intel(R) ME Full BIST test command…done
Get Intel(R) ME test data command…done
Total of 26 Intel(R) ME test result retrieved
Policy Kernel - Power Package: Live Heap Test - Passed
Common Services - LAN: Connectivity to NIC in M3 - Passed
MicroKernel - Internal Hardware Tests: Internal Hardware Tests - Passed
Policy Kernel - ME Password: Validate MEBx password - Passed
Policy Kernel - Power Package: Package 1 supported - Passed
Policy Kernel - Power Package: Default package supported - Passed
MicroKernel - Blob Manager: Set - Passed
MicroKernel - Blob Manager: Get - Passed
MicroKernel - Blob Manager: Remove - Passed
Policy Kernel - ME Configuration: Wlan Power Well - Passed
Policy Kernel - ME Configuration: PROC_MISSING - Passed
Policy Kernel - ME Configuration: M3 Power Rails Available - Passed
Policy Kernel - ME Recovery: ME Recovery mode check - Passed
Policy Kernel - Embedded Controller: Power source type - Passed
Policy Kernel - SMBus: Read byte - Passed
Common Services - General: Low power idle timeout - Passed
Common Services - Privacy Level: Valid Privacy Level settings - Passed
Common Services - EHBC State: Valid Embedded Host Based Configuration (EHBC) state - Passed
Common Services - General: WLAN enabled only on mobile or desktop - Passed
Common Services - General: Vlan not enabled on mobile - Passed
Common Services - Provisioning: Both PID and PPS are set - Passed
Common Services - Provisioning: MEBX password set when PID and PPS set - Passed
Common Services - EHBC State: EHBC and Privacy Level states compatibility - Passed
Common Services - LAN: Connectivity to NIC in M0 - Passed
AMT - Power: Valid LAN power well - Passed
AMT - Power: Power-package 2 supported - Passed
Clear Intel(R) ME test data command…done
Get EPID Group ID command…done
EPID Group ID: 802
EPID GID Check passed
MEManuf Test Passed
I can pm you the dump if you like!
@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:
the last thing I tried was a downgrade to a version where FIT and ME versions match (BIOS 2.55)
For safety, first with fwupdlcl and then with fpt again, followed by greset.
As it was still manufacturing mode, I closed it with closemnf.
This time closemnf said "Setting the ME Manufacturing Mode Done bit was successful" and I think this was only possible because I set all regions to read/write in the descriptor region before closemnf (…they were already in intel recommended mode or similar…)
The machine is running fine now with ME enabled, no manufacturing mode, v2 cpu
but still "No valid OEM data, ICC not programmed" 
I don’t care 
Many thanks again and please tell me if there is anything I could try out or if this message maybe is a bug or something.
Yes, ignore that if you know the BIOS and Engine firmware are ok. This is probably due to bad BIOS design from OEM, not reporting something finished initializing to the Engine co-processor or similar. I remember another motherboard a few years ago (Z170 ?, user jjxaker ?) which had the same issue even though the SPI image was stock/healthy. It’s rare to see that but you can ignore it in your case.
It might have to do with the buggy tools for C60x/Patsburg chipset. FITc shows different values for ME settings for this bios, too, when either using ME region or complete image. Maybe MEInfo gets wrong values, too, when ckecking?
Would be ‘interesting’ to check if a self- cleaned ME would solve the problem/ give different results, but I wouldn’t bother if everything seems to work fine 
Congratulations for getting it to work!
What do you mean by "self-cleaned"? Manually transferring settings from two FITC windows? Things is, with how broken FITC v8 was at PBG images, we can’t trust that the info it displays is proper so transferring them ourselves does not change anything really. From my limited testing at the time, I had "concluded" that the settings we see when loading a bare ME region are (more ?) proper compared to the ones from the full SPI image. You might be right though, this error could be because of FITC v8 + PBG but I think I’ve seen that message being displayed constantly at a SKL platform so maybe not? Ahhh, who knows… 
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…
Hello,
I have got myself a Z820 too.
The serial number is
SP P/N 619562-001
CT PBLP0CM42L3K9
AS P/N 618266-001 2012
PCB Rev: 1.00 Bios is latest version J63 V03.96 12/28/2011
I have a EZP2019 High Speed USB SPI Programmer and have done few laptop bios upgrades / recoveries. Any help in upgrading the BIOS?
-
So far it’s unclear how to connect sop16 clip to the EZP2019. Is there adapter available with the clip? I don’t have 16pin clip just 8pin that came with the programmer.
-
The guide is unfinished a bout the Upgrading ME firmware v7 → v8 in OS Seems like this part of the guide is for Z620?
This thread contains questions but no answers:
# ME V7 → V8 upgrade. Final recommended path?
BillDH2k commented [on May 16]
edited
Follow up -
I did the following: starting from a dump v3.96 bios from my board, then replaced the ME and Boot Block with codes from the official v.3.96 BIOS (“J61_0396.BIN”). Flashed the modified BIOS into the board (using PI 3+B). Now I have 2013 boot block and 8.1.x ME. Everything is working. The only issue is that “ME is in manufacturing mode” msg during booting.
How did you replace the data? HxD ?
ME: 0x005000 to 0x50FFFF
Boot block region: 0xFF0000 to 0xFFFFFF
Did you solve the “ME is in manufacturing mode” msg during booting. ???
Hey sorry for waking up an old thread. I have modded a Z420. In case you still haven’t figured out, and for future readers’ reference:
Check out the datasheet of the flash chip. You don’t have to buy an adapter if you have some TTL wire around.
The difference between sop8 and sop 16 variants is just the middle 4 pins in the middle.
Say sop8 it’s like
1 2 3 4
8 7 6 5
On sop16 side it should wire as
1 2 x x x x 3 4
8 7 x x x x 6 5
Where all x are unconnected.
There are two ways to go, one is follow the guide , use HxD. Get the latest BIOS from HP, copy the data from ME region to your BIOS.
I used UefiTool. First use the release build to open official image, right click on the ME region, extract and save as file. Then use the alpha build to open your image, right click on the ME region and replace with the extracted data.
This method works for the boot region too. The boot region is located deeper in the structure. Using the offset value on the right panel as reference, until you find a block matching the address in that guide. Then same steps to transplant the boot region.
I don’t have ME enabled because I have no need to use it. But as far as I remember, I have that message and ME/AMT still works. It’s just cosmetic annoyance, so ignore it or use the jumper to disable ME.
(AMT only has serial console, no GUI because Xeon has no iGPU. )