(A7) Me FW Downgrade - Request MeSpiLock Failed - HP EliteDesk 800 65W G2 Desktop Mini PC

PS C:\swsetup\SP89025\FW64> dir


Directory: C:\swsetup\SP89025\FW64


Mode LastWriteTime Length Name
---- ------------- ------ ----
-a---- 9/25/2018 5:25 PM 506 error.log
-a---- 6/21/2018 2:29 PM 8666 FWUpdateLib.h
-a---- 6/21/2018 2:29 PM 566216 FwUpdateLib.lib
-a---- 6/21/2018 2:29 PM 2958912 FWUpdLcl64.exe
-a---- 6/21/2018 2:26 PM 72848 Idrvdll32e.dll
-a---- 6/21/2018 2:26 PM 121960 ISHLib64.dll
-a---- 7/18/2018 3:25 PM 12632 MEFWDetailFile.exe
-a---- 6/21/2018 2:26 PM 3097152 MEInfoWin64.exe
-a---- 6/24/2018 3:48 PM 7348224 ME_11.8_Corporate_C0_LP_Production.bin
-a---- 6/21/2018 2:26 PM 125072 Pmxdll32e.dll
-a---- 7/18/2018 4:37 PM 934 update64.bat


PS C:\swsetup\SP89025\FW64> .\MEInfoWin64.exe

Intel(R) MEInfo Version: 11.8.55.3510
Copyright(C) 2005 - 2017, Intel Corporation. All rights reserved.




Error 76: Communication error between application and Intel(R) ME module (AMT client)

Error 76: Communication error between application and Intel(R) ME module (AMT client)

Error 76: Communication error between application and Intel(R) ME module (AMT client)

Error 76: Communication error between application and Intel(R) ME module (AMT client)

Error 76: Communication error between application and Intel(R) ME module (AMT client)

Error 107: Failed to create dependency list for features



- upgrading the BIOS to the latest version - HP EliteDesk 800 G2 DM System BIOS (N21) 02.35 Rev.A Jun 12, 2018 "Done"

- Install Drivers Intel Management Engine Driver 11.6.0.1045 Rev.A Mar 20, 2017 "Done"

- Resetting the BIOS settings to Factory Default "Done"

- Disabling Safe Boot and Enabling Legacy Boot "Done"

- Intel Management Engine (ME) Firmware 11.8.55.3510 Rev.A Aug 17, 2018 "Not upgrade"



PS C:\swsetup\SP89025\FW64> .\FWUpdLcl64.exe -f ME_11.8_Corporate_C0_LP_Production.bin -allowsv -y

Intel (R) Firmware Update Utility Version: 11.8.55.3510
Copyright (C) 2007 - 2018, Intel Corporation. All rights reserved.

Communication Mode: MEI
Checking firmware parameters…

Error 8704: Firmware update operation not initiated due to a SKU mismatch


ME Information
Version: 11.8.50.3425
SKU: Unknown
Provisioning Mode: Not Provisioned
Control Mode: None
Is CCM Disabled: True
Driver installation found: True
EHBC Enabled: False
LMS service state: NotPresent
microLMS service state: NotPresent
Is SPS: False

Why are you trying to flash CSME PCH-LP firmware on a PCH-H platform? If that was successful, the system would be bricked now so it’s good that FWUpdate tool stopped you. First, before using FWUpdate tool, make sure that the current CSME firmware is healthy by running MEInfo and MEManuf tools. If you see errors, it might not be. In such case, post the output of “MEInfo -fwsts”.

PS C:\swsetup\SP89025\FW64> .\MEInfoWin64.exe -fwsts

Intel(R) MEInfo Version: 11.8.55.3510
Copyright(C) 2005 - 2017, Intel Corporation. All rights reserved.



FW Status Register1: 0x90002242
FW Status Register2: 0x06F60506
FW Status Register3: 0x00000430
FW Status Register4: 0x00084004
FW Status Register5: 0x00000000
FW Status Register6: 0x40000000

CurrentState: Recovery
ManufacturingMode: Disabled
FlashPartition: Valid
OperationalState: CM0 with UMA
InitComplete: Complete
BUPLoadState: Success
ErrorCode: Disabled
ModeOfOperation: Normal
SPI Flash Log: Present
FPF HW Source value: FPF HW Not Set
ME FPF Fusing Patch Status: ME FPF Fusing patch NOT supported in this FW Version
Phase: ROM/Preboot
ICC: Valid OEM data, ICC programmed
ME File System Corrupted: No
PhaseStatus: AFTER_SRAM_INIT
FPF and ME Config Status: Match

I trying to flash firmware from official site

https://support.hp.com/us-en/drivers/sel…mini-pc/8741496

Intel Management Engine (ME) Firmware Component 11.8.55.3510

sp89025.exe

Download CSME System Tools v11 from Intel Management Engine: Drivers, Firmware & System Tools and run Flash Programming Tool with command “fptw -greset” and check if MEInfo shows a proper output after the restart. If not, run “fptw -me -d me.bin” and check if any error is shown.

PS C:\Intel CSME System Tools v11 r14\Flash Programming Tool\WIN64> .\FPTW64.exe -greset

Intel (R) Flash Programming Tool. Version: 11.8.55.3510
Copyright (c) 2007 - 2017, Intel Corporation. All rights reserved.

Could not set the GlobalReset bit

FPT Operation Successful.

PS C:\Intel CSME System Tools v11 r14\MEInfo\WIN64> .\MEInfoWin64.exe

Intel(R) MEInfo Version: 11.8.55.3510
Copyright(C) 2005 - 2017, Intel Corporation. All rights reserved.

Error 76: Communication error between application and Intel(R) ME module (AMT client)

Error 76: Communication error between application and Intel(R) ME module (AMT client)

Error 76: Communication error between application and Intel(R) ME module (AMT client)

Error 76: Communication error between application and Intel(R) ME module (AMT client)

Error 76: Communication error between application and Intel(R) ME module (AMT client)

Error 107: Failed to create dependency list for features

PS C:\Intel CSME System Tools v11 r14\Flash Programming Tool\WIN64> .\FPTW64.exe -me -d me.bin

Intel (R) Flash Programming Tool. Version: 11.8.55.3510
Copyright (c) 2007 - 2017, Intel Corporation. All rights reserved.

Reading HSFSTS register… Flash Descriptor: Valid

— Flash Devices Found —
W25Q128FV ID:0xEF4018 Size: 16384KB (131072Kb)



Error 318: The host CPU does not have read access to the target flash area. To enable read access for this operation you must modify the descriptor settings to give host access to this region.
FPT Operation Failed.

I have to do Dump SPI with Flash Programming Tool, follow the cleanup guide and flash back followed by fptw -greset command. - right?

No, and you can’t dump ME region due to error shown in #8, ME region is locked. Do you have backup of BIOS before this happened? Please wait for plutomaniac to reply again, so it does not get worse situation.
Your ME is corrupted right now, I think the only way to fix is by using FPT and a correct type BIOS that contains working ME after doing shorting method (Pinmod) to enable FD/ME access, or with flash programmer.

Check your motherboard while you wait, and see if you have any two-pin jumpers labeled ME, FD, or Service - or any unlabeled two-pin jumpers (Add image to show us if no label)
I will check stock BIOS for you now and see if it’s an option or not. Do you use N21 or N11 type BIOS, if you are not certain, please check and see if CPU-z motherboard tab shows either of those, or link your BIOS download page
Is this your exact system? https://support.hp.com/us-en/drivers/sel…mini-pc/8741496

This system might have HP’s “Surestart” recovery features, we ran into that with the tower version - RE:HP EliteOne 800 G2 CPU Gen6 to Gen7
Maybe you can enable this and specifically ME setting for it in the BIOS, I am not sure of all the options for this, or if your smaller version has it? But when we changed his ME it auto recovered, so maybe you can mess with that if it’s in your BIOS and get it to fix itself.

We also had to use flash programmer on his, so I assume you will end up needing for your system as well. Go ahead and order now, CH341A and SOIC8 test clip w/ cable.
But you can see if FPT will give you full dump using this command, 16MB dump is what you need to see otherwise it’s not complete.
FPTw.exe -d biosbackup.bin

PS C:\Intel CSME System Tools v11 r14\Flash Programming Tool\WIN64> .\FPTW64.exe -d biosbackup.bin

Intel (R) Flash Programming Tool. Version: 11.8.55.3510
Copyright (c) 2007 - 2017, Intel Corporation. All rights reserved.

Reading HSFSTS register… Flash Descriptor: Valid

— Flash Devices Found —
W25Q128FV ID:0xEF4018 Size: 16384KB (131072Kb)



Error 318: The host CPU does not have read access to the target flash area. To enable read access for this operation you must modify the descriptor settings to give host access to this region.
FPT Operation Failed.

IMG_20180926_111229.jpg

IMG_20180926_111924.jpg


Correct. Your CSME firmware is corrupted. But you cannot use FPT if you don’t have Flash Descriptor read/write access to the Engine region of the SPI/BIOS chip. At the picture I see a “FDO” mark which should mean “Flash Descriptor Override” and in that case, this is what we are looking for. Move the blue jumper to the FDO position, boot/reboot and try “fptw -d spi.bin” again. If it completes successfully, follow [Guide] Clean Dumped Intel Engine (CS)ME/(CS)TXE Regions with Data Initialization with “spi.bin” as input and flash “outimage.bin” back via “fptw -f outimage.bin”, set the jumper back to its original position and run “fptw -greset” to restart the system.

I assumed it would fail, that FPT dump. You’re going to either have to short the board (Pinmod) per the guide
Or get a flash programmer, unless Plutomaniac has a method

Wait, I see FDO jumper (Furthest left two pins in your image) - you’re in luck, see here for how that’s used
[Guide] Unlock Intel Flash Descriptor Read/Write Access Permissions for SPI Servicing

Put that jumper on, and then run the dump with FPT again I gave you, then we can fix that file for you (Or you can) then reflash it via FPTw -f fixedbios.bin, then shut down, remove jumper and get into windows and run FPTw -greset
Keep a spare copy of the backup dump safe, not edited somewhere, that way if you can’t get it fixed and we have to fix then it will be a clean unedited file.

*Edit, plutomaniac ninja’d me hey man, sorry to jump in on this, but was reading so thought I’d help!


No problem whatsoever, I appreciate the fact that the Engine support section is not a one man show anymore.

in the leftmost position FDO - PC not start "screen 1"
in the middle position BB - PC start in vga mode "screen 2"
in the rightmost position swd - PC normal start

1.jpg

2.jpg

plutomaniac - Thanks, happy to help when I can. I do not see “Sections” I only use view latest post link at top, always then help when possible. I do try to sit back on threads when I know you are helping or better one to help, because you are much better at this than I, and usually solve in a much quicker way than I do too

@pg1 - what is “Screen 1” - never mind, you meant image one, sorry! That is not good, should be OK to start, hopefully plutomaniac will know what to do! You may need PSWD one there always, and another on FDO too.
Find another jumper, or short FDO pins with something metal like a tiny clip. Probably grab a jumper off another board laying around if you have any, especially older ones.

https://www.itouchbiometrics.com/Manuals…%20600%20G2.pdf

ok one moment please

not start ((((

IMG_20180926_141723.jpg

Please edit your posts while you wait for someone to reply, don’t post consecutively. Now, FDO is definitely what you want and it should work by itself. Some random google searching for similar models proves as such:

Capture0.PNG



Capture.PNG



If for whatever reason you cannot get the FDO jumper to work, you can do it manually, meaning E1 at [Guide] Unlock Intel Flash Descriptor Read/Write Access Permissions for SPI Servicing.