Forum - RE: HP Pavilion All-in-One - 24-b105nx (ME Firmware Update failed/Error sending end of post message to ME: HECI disabled, proceeding w boot)

#16 | RE: HP Pavilion All-in-One - 24-b105nx (ME Firmware Update failed/Error sending end of post message to ME: HECI disabled, proceeding w boot) datum

Sun Jun 16, 2019 8:38 pm (Last edited: Sun Jun 16, 2019 8:49 pm)

Hi, I was successful after shorting the FDO jumper, please find attached the output. Now at every boot I see a message appearing in blue color that the Manufacturing programming mode is in Unlock Mode, i have returned the jumper back though, computer is performing fine now.

Bundle of thanks for your continuous support.

AdnanMumtaz has attached files to this post

Flashed.txt

reply

#17 | RE: HP Pavilion All-in-One - 24-b105nx (ME Firmware Update failed/Error sending end of post message to ME: HECI disabled, proceeding w boot) datum

Sun Jun 16, 2019 8:56 pm

C:\FW\Intel CSME System Tools v11 r25\MEInfo\WIN64>MEInfoWin64.exe -verbose

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

Windows OS Version : 10.0

FW Status Register1: 0x90000245
FW Status Register2: 0x060B0506
FW Status Register3: 0x00000020
FW Status Register4: 0x00084000
FW Status Register5: 0x00000000
FW Status Register6: 0x40000000

CurrentState: Normal
ManufacturingMode: Disabled
FlashPartition: Valid
OperationalState: CM0 with UMA
InitComplete: Complete
BUPLoadState: Success
ErrorCode: No Error
ModeOfOperation: Normal
SPI Flash Log: Not Present
FPF HW Source value: Not Applicable
ME FPF Fusing Patch Status: ME FPF Fusing patch NOT applicable
Phase: ROM/Preboot
ICC: Valid OEM data, ICC programmed
ME File System Corrupted: No
PhaseStatus: CALL_NEXT_MODULE
FPF and ME Config Status: Match
FW Capabilities value is 0x31111140
Feature enablement is 0x31111140
Platform type is 0x12220322
No Intel Wireless device was found
Intel(R) ME code versions:

Table Type 5 ( 0x 05 ) found, size of 0 (0x 00 ) bytes
BIOS Version F.47
Table Type 5 ( 0x 05 ) found, size of 0 (0x 00 ) bytes
Table Type 0 ( 0x 00 ) found, size of 45 (0x 2D ) bytes
Table Type 1 ( 0x 01 ) found, size of 51 (0x 33 ) bytes
Table Type 2 ( 0x 02 ) found, size of 35 (0x 23 ) bytes
Table Type 3 ( 0x 03 ) found, size of 34 (0x 22 ) bytes
Table Type 8 ( 0x 08 ) found, size of 21 (0x 15 ) bytes
Table Type 9 ( 0x 09 ) found, size of 23 (0x 17 ) bytes
Table Type 11 ( 0x 0B ) found, size of 85 (0x 55 ) bytes
Table Type 12 ( 0x 0C ) found, size of 8 (0x 08 ) bytes
Table Type 32 ( 0x 20 ) found, size of 22 (0x 16 ) bytes
Table Type 34 ( 0x 22 ) found, size of 19 (0x 13 ) bytes
Table Type 26 ( 0x 1A ) found, size of 29 (0x 1D ) bytes
Table Type 36 ( 0x 24 ) found, size of 18 (0x 12 ) bytes
Table Type 35 ( 0x 23 ) found, size of 14 (0x 0E ) bytes
Table Type 28 ( 0x 1C ) found, size of 29 (0x 1D ) bytes
Table Type 36 ( 0x 24 ) found, size of 18 (0x 12 ) bytes
Table Type 35 ( 0x 23 ) found, size of 14 (0x 0E ) bytes
Table Type 27 ( 0x 1B ) found, size of 30 (0x 1E ) bytes
Table Type 36 ( 0x 24 ) found, size of 18 (0x 12 ) bytes
Table Type 35 ( 0x 23 ) found, size of 14 (0x 0E ) bytes
Table Type 27 ( 0x 1B ) found, size of 17 (0x 11 ) bytes
Table Type 36 ( 0x 24 ) found, size of 18 (0x 12 ) bytes
Table Type 35 ( 0x 23 ) found, size of 14 (0x 0E ) bytes
Table Type 29 ( 0x 1D ) found, size of 27 (0x 1B ) bytes
Table Type 36 ( 0x 24 ) found, size of 18 (0x 12 ) bytes
Table Type 35 ( 0x 23 ) found, size of 14 (0x 0E ) bytes
Table Type 26 ( 0x 1A ) found, size of 29 (0x 1D ) bytes
Table Type 28 ( 0x 1C ) found, size of 29 (0x 1D ) bytes
Table Type 27 ( 0x 1B ) found, size of 30 (0x 1E ) bytes
Table Type 29 ( 0x 1D ) found, size of 27 (0x 1B ) bytes
Table Type 39 ( 0x 27 ) found, size of 55 (0x 37 ) bytes
Table Type 41 ( 0x 29 ) found, size of 26 (0x 1A ) bytes
Table Type 7 ( 0x 07 ) found, size of 29 (0x 1D ) bytes
Table Type 4 ( 0x 04 ) found, size of 122 (0x 7A ) bytes
Table Type 16 ( 0x 10 ) found, size of 25 (0x 19 ) bytes
Table Type 17 ( 0x 11 ) found, size of 104 (0x 68 ) bytes
Table Type 19 ( 0x 13 ) found, size of 33 (0x 21 ) bytes
Table Type 20 ( 0x 14 ) found, size of 37 (0x 25 ) bytes
Table Type 130 ( 0x 82 ) found, size of 22 (0x 16 ) bytes
MEBx Version 10.0.0.0001
GbE Version Unknown
Vendor ID 8086
PCH Version 31
FW Version 11.8.50.3470 H
Security Version (SVN) 3
LMS Version Not Available
MEI Driver Version 11.7.0.1057
Wireless Hardware Version 2.1.77
Wireless Driver Version 19.51.21.1

FW Capabilities 0x31111140

Intel(R) Capability Licensing Service - PRESENT/ENABLED
Protect Audio Video Path - PRESENT/ENABLED
Intel(R) Dynamic Application Loader - PRESENT/ENABLED
Service Advertisement & Discovery - NOT PRESENT
Intel(R) NFC Capabilities - NOT PRESENT
Intel(R) Platform Trust Technology - PRESENT/ENABLED

Re-key needed False
Platform is re-key capable True
TLS Disabled
Last ME reset reason Firmware reset
Local FWUpdate Enabled
BIOS Config Lock Enabled
GbE Config Lock Enabled
Get flash master region access status...done
Host Read Access to ME Disabled
Host Write Access to ME Disabled
Get EC region access status...done
Host Read Access to EC Disabled
Host Write Access to EC Disabled
Protected Range Register Base #0 0x0
Protected Range Register Limit #0 0x0
Protected Range Register Base #1 0x0
Protected Range Register Limit #1 0x0
Protected Range Register Base #2 0x0
Protected Range Register Limit #2 0x0
Protected Range Register Base #3 0x0
Protected Range Register Limit #3 0x0
Protected Range Register Base #4 0x0
Protected Range Register Limit #4 0x0
SPI Flash ID 1 EF4017
SPI Flash ID 2 Unknown
BIOS boot State Post Boot
OEM ID 00000000-0000-0000-0000-000000000000
Capability Licensing Service Enabled
OEM Tag 0x00000000
Slot 1 Board Manufacturer 0x0000203A
Slot 2 System Assembler 0x00000000
Slot 3 Reserved 0x00000000
M3 Autotest Disabled
C-link Status Disabled
Independent Firmware Recovery Disabled
EPID Group ID 0xFBE

Retrieving Variable "LSPCON Port Configuration"
LSPCON Ports None

Retrieving Variable "eDP Port Configuration"
5K Ports None
OEM Public Key Hash FPF 0000000000000000000000000000000000000000000000000000000000000000

Retrieving Variable "OEM Public Key Hash"
OEM Public Key Hash ME 0000000000000000000000000000000000000000000000000000000000000000
ACM SVN FPF 0x0
KM SVN FPF 0x0
BSMM SVN FPF 0x0
GuC Encryption Key FPF 0000000000000000000000000000000000000000000000000000000000000000

Retrieving Variable "GuC Encryption Key"
GuC Encryption Key ME 0000000000000000000000000000000000000000000000000000000000000000

FPF ME
--- --
Force Boot Guard ACM Disabled
Retrieving Variable "Force Boot Guard ACM Enabled"
Disabled
Protect BIOS Environment Disabled
Retrieving Variable "Protect BIOS Environment Enabled"
Disabled
CPU Debugging Enabled
Retrieving Variable "CPU Debugging"
Enabled
BSP Initialization Enabled
Retrieving Variable "BSP Initialization"
Enabled
Measured Boot Disabled
Retrieving Variable "Measured Boot Enabled"
Disabled
Verified Boot Disabled
Retrieving Variable "Verified Boot Enabled"
Disabled
Key Manifest ID 0x0
Retrieving Variable "Key Manifest ID"
0x0
Enforcement Policy 0x0
Retrieving Variable "Error Enforcement Policy"
0x0
PTT Enabled
Retrieving Variable "Intel(R) PTT Supported"
Enabled
PTT Lockout Override Counter 0x0
EK Revoke State Revoked
PTT RTC Clear Detection FPF 0x0

C:\FW\Intel CSME System Tools v11 r25\MEInfo\WIN64>

reply

#18 | RE: HP Pavilion All-in-One - 24-b105nx (ME Firmware Update failed/Error sending end of post message to ME: HECI disabled, proceeding w boot) datum

Sun Jun 16, 2019 9:14 pm

Now that you have reset the jumper, the output looks perfect. The system should work just fine. You have probably lost some BIOS info like Serial Number etc, if that is of interest to you. But you have kept a backup of the SPI image before the re-flash so they could be transferred by someone who knows these things such as LOST_N_BIOS. Do you still get the new message upon each boot? If yes, it must be because the system is not provisioned with SN etc info.

reply

#19 | RE: HP Pavilion All-in-One - 24-b105nx (ME Firmware Update failed/Error sending end of post message to ME: HECI disabled, proceeding w boot) datum

Sun Jun 16, 2019 9:17 pm

Hi yes on every boot I see the message Manufacturing programming mode is in unlock mode, yes I noticed i didn't see the serial number and other info. once again thanks a lot, I will try to connect with LOST_N_BIOS to seek his help

reply

#20 | RE: HP Pavilion All-in-One - 24-b105nx (ME Firmware Update failed/Error sending end of post message to ME: HECI disabled, proceeding w boot) datum

Thu Jun 20, 2019 6:01 am

@AdnanMumtaz - Send me the SPI image you flashed in, along with a copy of your original backup. You'll have to reflash it same way again after I edit

As for manufacturing mode, if this is a BIOS or HP thing, not ME FW thing, then you should be able to see a message to end this mode either at the same screen where you are seeing that, or in the BIOS itself somewhere

To make it easier for me to transfer over Serial, UUID, LAN MAC ID etc, I need images of all stickers on the back of your casing, and on the inside of the back casing too (and any on that backside of the motherboard as well.
Be sure to include any stickers on/near the memory slots, and remove memory too in case there is any underneath. And if you can, in case it's not on a sticker, check your router logs and see if you can find your LAN MAC ID
With the above two BIOS files, and all those images I requested, also include an image of this Manufacturing Mode message so I can see it's exact wording and all things on screen etc.

Did you now disable ME FW Re-Flash in BIOS? If not, you need to disable that again (back to default) Otherwise ME FW is disabled until you do (Reading from page one, didn't look at above info as I'm not good at ME stuff so I can never tell what's going on )

Please don't send PM's for help on BIOS edits, I can't help with BIOS in PM's. Please make a thread and I will try to help as soon as I can - thanks!
If you appreciate my efforts and are willing to donate to help improve my hardware, gift cards work for me (Amazn, NuEgg, eBa) - send me a PM
I view the forum like this, please bump your thread 1x every 24-48 hours if no reply

reply

#21 | RE: HP Pavilion All-in-One - 24-b105nx (ME Firmware Update failed/Error sending end of post message to ME: HECI disabled, proceeding w boot) datum

Thu Jun 20, 2019 8:04 pm

An FDO jumper was used so the entire SPI was re-flashed with HP's stock SPI image. The CSME is healthy, only DMI info from BIOS is missing which caused this new message to appear. For HP, I'm fairly certain you need to use their technician-only NbDmiFit tool to get the job done properly. I think the last version we've found will work on your system as it's not that new. You'll need to read the provided documentation yourself though but it shouldn't be that difficult.

reply

#22 | RE: HP Pavilion All-in-One - 24-b105nx (ME Firmware Update failed/Error sending end of post message to ME: HECI disabled, proceeding w boot) datum

Thu Jun 20, 2019 8:48 pm

I thought so after reading back. Don't you usually need a personalized SMC.bin from HP to use NbDmiFit? They send them out, if you provide proof of purchase and give them your serial, UUID etc.
It can be done without that I think, at least all the DMI info. Closing out the manufacturing though I am not sure about, that may need to be done with NbDmiFit he'll have to see what options he has without a SMC.BIN
I have 2.05 version, if 2.13 proves to be too new or something.

Please don't send PM's for help on BIOS edits, I can't help with BIOS in PM's. Please make a thread and I will try to help as soon as I can - thanks!
If you appreciate my efforts and are willing to donate to help improve my hardware, gift cards work for me (Amazn, NuEgg, eBa) - send me a PM
I view the forum like this, please bump your thread 1x every 24-48 hours if no reply

reply

#23 | RE: HP Pavilion All-in-One - 24-b105nx (ME Firmware Update failed/Error sending end of post message to ME: HECI disabled, proceeding w boot) datum

Thu Jun 20, 2019 9:39 pm

Maybe you're right about SMC but I've never used NbDmiFit so I don't know. Something else you can try to avoid all is to re-flash the old BIOS region only but the problem may come back if it wasn't just a corrupted CSME firmware. Maybe you can transfer the NVRAM only or something. You know these things best. ;)

reply

#24 | RE: HP Pavilion All-in-One - 24-b105nx (ME Firmware Update failed/Error sending end of post message to ME: HECI disabled, proceeding w boot) datum

Thu Jun 20, 2019 9:43 pm (Last edited: Thu Jun 20, 2019 9:45 pm)

Thanks for your reply, please download the info you asked from the link below, i wasnt able to upload it here because of file size , backup.bin is the image before flashing and the other bin file is the one which plutomaniac sent me

http://www.skidmail.com/intel/adnan.rar

reply

#25 | RE: HP Pavilion All-in-One - 24-b105nx (ME Firmware Update failed/Error sending end of post message to ME: HECI disabled, proceeding w boot) datum

Thu Jun 20, 2019 9:46 pm (Last edited: Thu Jun 20, 2019 9:52 pm)

I've never used NbDmiFit myself either, but here on forums when I've helped people try to use it or fix their BIOS etc, every time the user had to contact HP to get that SMC file.
It does sound like a ME Only issue, so you're right, it may be best to first try direct swap back of his old BIOS region. If that fails and brings back error, then yes I can transfer out details to stock image, usually these are in padding files, sometimes NVRAM as you mentioned, or certain modules like SMBIOSStaticData

* Edit - here @AdnanMumtaz - first test this, write back with FD jumper on. This is your original BIOS region swapped back into stock image. If this fails, or brings back error, then I will pull the details out directly and swap them in.
http://s000.tinyupload.com/index.php?fil...139891800826420

Please don't send PM's for help on BIOS edits, I can't help with BIOS in PM's. Please make a thread and I will try to help as soon as I can - thanks!
If you appreciate my efforts and are willing to donate to help improve my hardware, gift cards work for me (Amazn, NuEgg, eBa) - send me a PM
I view the forum like this, please bump your thread 1x every 24-48 hours if no reply

reply

#26 | RE: HP Pavilion All-in-One - 24-b105nx (ME Firmware Update failed/Error sending end of post message to ME: HECI disabled, proceeding w boot) datum

Thu Jun 20, 2019 10:39 pm

Thanks a lot, Shall I use the same command FPTW64.exe -f filename.bin with this file ?

reply

#27 | RE: HP Pavilion All-in-One - 24-b105nx (ME Firmware Update failed/Error sending end of post message to ME: HECI disabled, proceeding w boot) datum

Fri Jun 21, 2019 12:31 am

Yes, it's a full SPI image so you need "fpt -f" as you said, like before.

reply

#28 | RE: HP Pavilion All-in-One - 24-b105nx (ME Firmware Update failed/Error sending end of post message to ME: HECI disabled, proceeding w boot) datum

Fri Jun 21, 2019 6:47 am (Last edited: Fri Jun 21, 2019 6:47 am)

plutomaniac - I was looking into the NdDMIFit package, and he may be able to use wndmifit only, which may not require a valid/proper SMC.BIN for all functions, I'm not sure... There is a FSMC.bin in there already, so maybe not a good sign.
But, if ME FW was the only issue, then the above file should sort it out for him anyway. This is RSA Signed BIOS too, so we may run into some issues editing, signature is just above Last VTF

Please don't send PM's for help on BIOS edits, I can't help with BIOS in PM's. Please make a thread and I will try to help as soon as I can - thanks!
If you appreciate my efforts and are willing to donate to help improve my hardware, gift cards work for me (Amazn, NuEgg, eBa) - send me a PM
I view the forum like this, please bump your thread 1x every 24-48 hours if no reply

reply

#29 | RE: HP Pavilion All-in-One - 24-b105nx (ME Firmware Update failed/Error sending end of post message to ME: HECI disabled, proceeding w boot) datum

Sun Jun 23, 2019 2:35 am

Thanks guys a billion! its done, no more errors and everything is working fine now. see the output below

Microsoft Windows [Version 10.0.18362.175]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>cd "\fw\Intel CSME System Tools v11 r25"

C:\FW\Intel CSME System Tools v11 r25>dir
Volume in drive C is Windows
Volume Serial Number is E24E-3F70

Directory of C:\FW\Intel CSME System Tools v11 r25

14-Jun-19 04:15 PM <DIR> .
14-Jun-19 04:15 PM <DIR> ..
14-Jun-19 04:15 PM <DIR> Clock Commander Tool
14-Jun-19 04:15 PM <DIR> Flash Image Tool
14-Jun-19 04:15 PM <DIR> Flash Programming Tool
14-Jun-19 04:15 PM <DIR> FWUpdate
14-Jun-19 04:15 PM <DIR> Manifest Extension Utility
14-Jun-19 04:15 PM <DIR> MEInfo
14-Jun-19 04:15 PM <DIR> MEManuf
14-Jun-19 05:18 AM 898 Tools Version Info.txt
1 File(s) 898 bytes
9 Dir(s) 240,414,494,720 bytes free

C:\FW\Intel CSME System Tools v11 r25>cd "Flash Programming Tool"

C:\FW\Intel CSME System Tools v11 r25\Flash Programming Tool>dir
Volume in drive C is Windows
Volume Serial Number is E24E-3F70

Directory of C:\FW\Intel CSME System Tools v11 r25\Flash Programming Tool

14-Jun-19 04:15 PM <DIR> .
14-Jun-19 04:15 PM <DIR> ..
14-Jun-19 04:15 PM <DIR> DOS
14-Jun-19 04:15 PM <DIR> EFI64
14-Jun-19 04:15 PM <DIR> WIN32
23-Jun-19 02:22 AM <DIR> WIN64
0 File(s) 0 bytes
6 Dir(s) 240,414,298,112 bytes free

C:\FW\Intel CSME System Tools v11 r25\Flash Programming Tool>cd WIN64

C:\FW\Intel CSME System Tools v11 r25\Flash Programming Tool\WIN64>dir
Volume in drive C is Windows
Volume Serial Number is E24E-3F70

Directory of C:\FW\Intel CSME System Tools v11 r25\Flash Programming Tool\WIN64

23-Jun-19 02:22 AM <DIR> .
23-Jun-19 02:22 AM <DIR> ..
16-Jun-19 02:32 AM 6,291,456 bios.bin
16-Jun-19 08:50 PM 221 error.log
14-Jun-19 05:18 AM 15,153 fparts.txt
14-Jun-19 05:18 AM 3,261,416 FPTW64.exe
14-Jun-19 05:18 AM 72,848 Idrvdll32e.dll
14-Jun-19 05:18 AM 125,072 Pmxdll32e.dll
20-Jun-19 09:46 PM 8,388,608 RGNSwap.bin
15-Jun-19 05:51 AM 8,388,608 sp93316_081B7F47.bin
16-Jun-19 08:08 PM 8,388,608 sppi.bin
9 File(s) 34,931,990 bytes
2 Dir(s) 240,414,298,112 bytes free

C:\FW\Intel CSME System Tools v11 r25\Flash Programming Tool\WIN64>FPTW64.exe -f RGNSwap.bin

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

Reading HSFSTS register... Flash Descriptor: Valid

--- Flash Devices Found ---
W25Q64FV ID:0xEF4017 Size: 8192KB (65536Kb)

GbE Region does not exist.

- Reading Flash [0x0800000] 8192KB of 8192KB - 100 percent complete.
- Erasing Flash Block [0x002000] - 100 percent complete.
- Programming Flash [0x0002000] 4KB of 4KB - 100 percent complete.
- Erasing Flash Block [0x0B1000] - 100 percent complete.
- Programming Flash [0x00B1000] 32KB of 32KB - 100 percent complete.
- Erasing Flash Block [0x0D4000] - 100 percent complete.
- Programming Flash [0x00D4000] 108KB of 108KB - 100 percent complete.
- Erasing Flash Block [0x0F0000] - 100 percent complete.
- Programming Flash [0x00F0000] 36KB of 36KB - 100 percent complete.
- Erasing Flash Block [0x10F000] - 100 percent complete.
- Programming Flash [0x010F000] 120KB of 120KB - 100 percent complete.
- Erasing Flash Block [0x1BE000] - 100 percent complete.
- Programming Flash [0x01BE000] 4KB of 4KB - 100 percent complete.
- Erasing Flash Block [0x241000] - 100 percent complete.
- Programming Flash [0x0241000] 4KB of 4KB - 100 percent complete.
- Erasing Flash Block [0x261000] - 100 percent complete.
- Programming Flash [0x0261000] 124KB of 124KB - 100 percent complete.
- Erasing Flash Block [0x283000] - 100 percent complete.
- Programming Flash [0x0283000] 132KB of 132KB - 100 percent complete.
- Erasing Flash Block [0x7FF000] - 100 percent complete.
- Programming Flash [0x07FF000] 4KB of 4KB - 100 percent complete.
- Verifying Flash [0x0800000] 8192KB of 8192KB - 100 percent complete.
RESULT: The data is identical.

FPT Operation Successful.

C:\FW\Intel CSME System Tools v11 r25\Flash Programming Tool\WIN64>

reply

#30 | RE: HP Pavilion All-in-One - 24-b105nx (ME Firmware Update failed/Error sending end of post message to ME: HECI disabled, proceeding w boot) datum

Sun Jun 23, 2019 2:38 am

What could be the reason of this issue, i would like to know so i can prevent it happening in the future

reply

Please enter a reason for warning.