Zitat von plutomaniac im Beitrag #1707

---

@ Pacman:

As expected. Have you tried the UPD image with FWUpdLcl 1173 just in case we see a new "Unknown" error?

---

@ Pacman:

Check the attached UPD image if you want. Maybe 1173 FWUpdate helps.

Zitat von ifix im Beitrag #1718

---

here
http://station-drivers.com/index.php?opt...&id=105&lang=en

---

Zitat von plutomaniac im Beitrag #1720

---

@ Pacman:

Check the attached UPD image if you want. Maybe 1173 FWUpdate helps.

---

Intel ME 11.0 Corporate PCH-LP Firmware v11.0.0.1173
Intel ME 11.0 Consumer PCH-LP Firmware v11.0.0.1171 (EXTR --> RGN)



Intel ME System Tools v11.0 r7:

Flash Image Tool: 11.0.0.1173
FWUpdate(DOS): 11.0.0.1173
FWUpdate(EFI64): 11.0.0.1173
FWUpdate(Win): 11.0.0.1173
MEInfo(DOS): 11.0.0.1173
MEInfo(EFI64): 11.0.0.1173
MEInfo(Windows): 11.0.0.1173
MEManuf(DOS): 11.0.0.1173
MEManuf(EFI64): 11.0.0.1173
MEManuf(Windows): 11.0.0.1173
MEManuf(Windows64): 11.0.0.1173
CCT(DOS): 11.0.0.1173
CCT(EFI): 11.0.0.1173
CCT(Windows): 11.0.0.1173
Manifest Extension Utility: 11.0.0.1173

SPT Corporate FW Bring Up Guide v1.0 (07/2015)

@ Pacman:

Yes certainly, take your time. No rush. We'll see the error again probably but it never hurts to test. You can also check the rest of the 1173 tools.

@ ifix:

Thank you for doing the right thing. For the record, it's not about "ego" but rather respecting someone else's collective work. A "mirror" of the stuff we share here does not do that. A reference link to this forum for people that need to look for something more does.

@ plutomaniac

Well i tried the 11.0.0.1180 UPD image with fwupdate 11.0.0.1173, but sadly got the same Invalid restore Point error as Before :(

But, after a little bit of work with FIT, and flashed with FPT, it is working well :)

Yes, use UBU Tool to update the UNDI module.

Hello :)

Here is ME FW 11.0.0.1180_COR_X_PRD_EXTR.

Intel ME 11.0 Corporate PCH-H Firmware v11.0.0.1180



@ Pacman:

Thank you for the firmware. Some notes:

1. There is no X SKU, only H and LP. When MEA does not know if the firmware is H or LP, it sets a placeholder SKU of X instead.
2. The 20-bytes (160-bits or 40 characters) at the end of the name are important for MEA as that's the way I differentiate between H and LP at the moment. It's actually the SHA-1 of a part of the firmware which is unique no matter CON/COR,H,LP,Stepping etc. I have a pre-defined table of SHA-1 hashes and that's how new Skylake firmware become "known" with new MEA releases. Until an actual detection is implemented (not up to me, UnHuffMe needs to be updated with ME11 support first as the SKU is found at the compressed Kernel subsection of FTPR region), you could leave that hash at the end of the file name when uploaded here. Not that I can't re-calculate it, but why not? For the ME Thread or SD, the X needs to be replaced with either H or LP and the SHA-1 at the end is not needed.

Zitat von gpvecchi im Beitrag #1730

---

Nope, error 1 with 1180 on my Z170...

---