Forum - RE: Intel Management Engine: Drivers, Firmware & System Tools

Win-Raid Forum (Drivers - Firmware - Modding) � Special Topics � Intel Management Engine � Intel (Converged Security) Management Engine: Drivers, Firmware and Tools

Page 133 of 380 � Page 1 ... 128 129 130 131 132 133 134 135 136 137 ... 380 Page �

Topic settings

Print view

Jump to forum

General & Forum related Topics News / Announcements Forum-related Questions & Suggestions Off Topic Important Drivers (AHCI/RAID, NVMe, USB etc.) General: Storage Drivers (AHCI/RAID, NVMe and USB) Specific: Intel AHCI/RAID Drivers Specific: NVIDIA nForce Chipset Drivers (incl. AHCI/RAID) Specific: NVMe Drivers Other Drivers System Performance RAID Performance AHCI/NVMe Performance Solid State Drives BIOS Modding BIOS Modding Guides and Problems BIOS modules (PCI ROM, EFI and others) BIOS Modding Requests Reports: BIOS Modding Results Offers: Already modded special BIOSes Special Topics Intel Management Engine CPU Microcodes NVMe Support for old Systems Other Tools (not BIOS modding related) Interesting PC Hardware & Software OS related Topics Windows 11 Windows 8-10/Server 2012-2019 Windows 7/Vista/Server 2008 Windows XP/2000/Server 2003 DOS/Windows 3.X/9X/ME - Retro Gaming Other Operating Systems

#1981 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Thu Feb 25, 2016 3:46 pm

Intel ME System Tools v11.0 r16

Flash Programming Tool(DOS, EFI64, Windows, Windows64): 11.0.0.1205

reply

#1982 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Fri Feb 26, 2016 12:14 pm

FormatC

Show info

Posts:	3
Registered since:	02.26.2016

Hello,

I found this forum by searching for an error I've got after updating my BIOS.
The error is:

1
2
 
Me FW Downgrade - Request Me Spilock Failed Error
Error sending End Of Post message to ME
 

This error comes on every boot when I completly switch off the PC (no power).
The Intel MEBX-Features are activated.

The PC is a DELL Precision 3620.
The BIOS-Version is 1.32
The Intel ME-Version is 11.00.194
Skylake-H-CPU

Upon searching for a solution I found this forum and updated the Intel ME to the latest version from here (11.0.0.1205), but unfortunately the error doesnt disappear.

Can anyone suggest a solution?

Thanks

reply

#1983 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Fri Feb 26, 2016 4:26 pm

@ FormatC:

Can you boot into Windows? Run MEInfo -verbose and MEManuf tools and show me pictures. Before updating the BIOS, had you already updated the ME firmware manually by any chance?

reply

#1984 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Sat Feb 27, 2016 5:18 pm

Hi, I got eglobal i3-5005U mini pc (Broadwell WildcatPoint-LP motherboard) with fully unlocked BIOS.
BIOS shows that ME FW info is missing, and MeInfo gives me the following errors

Windows64>MEInfoWin64.exe -verbose

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

FW Status Register1: 0x1E040195
FW Status Register2: 0x16522116
FW Status Register3: 0x00000200
FW Status Register4: 0x00004000
FW Status Register5: 0x00000000
FW Status Register6: 0x00000000

CurrentState: Normal
ManufacturingMode: Enabled
FlashPartition: Valid
OperationalState: Bring Up
InitComplete: Initializing
BUPLoadState: Success
ErrorCode: No Error
ModeOfOperation: Unsecured mode by H/W jumper
Phase: BringUp
ICC: Valid OEM data, ICC programmed
SPI Flash Log: Not Present
ME File System Corrupted: No
PhaseStatus: UNKNOWN

FPF and ME Config Status: Not committed

HECI device is found to be disabled.

Error 9256: Communication error between application and Intel(R) ME module (FW Update client)

Error 9256: Communication error between application and Intel(R) ME module (FW Update client)

Error 9256: Communication error between application and Intel(R) ME module (FW Update client)

Windows OS Version : 6.2.9200 ""
OS BIOS Support : UEFI

Table Type 0 ( 0x 00 ) found, size of 24 (0x 18 ) bytes

Windows OS Version : 6.2.9200 ""
OS BIOS Support : UEFI

Table Type 0 ( 0x 00 ) found, size of 24 (0x 18 ) bytes
Table Type 1 ( 0x 01 ) found, size of 27 (0x 1B ) bytes
Table Type 2 ( 0x 02 ) found, size of 15 (0x 0F ) bytes
Table Type 3 ( 0x 03 ) found, size of 25 (0x 19 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 10 ( 0x 0A ) found, size of 6 (0x 06 ) bytes
Table Type 11 ( 0x 0B ) found, size of 5 (0x 05 ) bytes
Table Type 12 ( 0x 0C ) found, size of 5 (0x 05 ) bytes
Table Type 32 ( 0x 20 ) found, size of 20 (0x 14 ) bytes
Table Type 34 ( 0x 22 ) found, size of 11 (0x 0B ) bytes
Table Type 26 ( 0x 1A ) found, size of 22 (0x 16 ) bytes
Table Type 36 ( 0x 24 ) found, size of 16 (0x 10 ) bytes
Table Type 35 ( 0x 23 ) found, size of 11 (0x 0B ) bytes
Table Type 28 ( 0x 1C ) found, size of 22 (0x 16 ) bytes
Table Type 36 ( 0x 24 ) found, size of 16 (0x 10 ) bytes
Table Type 35 ( 0x 23 ) found, size of 11 (0x 0B ) bytes
Table Type 27 ( 0x 1B ) found, size of 15 (0x 0F ) bytes
Table Type 36 ( 0x 24 ) found, size of 16 (0x 10 ) bytes
Table Type 35 ( 0x 23 ) found, size of 11 (0x 0B ) bytes
Table Type 27 ( 0x 1B ) found, size of 15 (0x 0F ) bytes
Table Type 36 ( 0x 24 ) found, size of 16 (0x 10 ) bytes
Table Type 35 ( 0x 23 ) found, size of 11 (0x 0B ) bytes
Table Type 29 ( 0x 1D ) found, size of 22 (0x 16 ) bytes
Table Type 36 ( 0x 24 ) found, size of 16 (0x 10 ) bytes
Table Type 35 ( 0x 23 ) found, size of 11 (0x 0B ) bytes
Table Type 26 ( 0x 1A ) found, size of 22 (0x 16 ) bytes
Table Type 28 ( 0x 1C ) found, size of 22 (0x 16 ) bytes
Table Type 27 ( 0x 1B ) found, size of 15 (0x 0F ) bytes
Table Type 29 ( 0x 1D ) found, size of 22 (0x 16 ) bytes
Table Type 39 ( 0x 27 ) found, size of 22 (0x 16 ) bytes
Table Type 41 ( 0x 29 ) found, size of 11 (0x 0B ) bytes
Table Type 41 ( 0x 29 ) found, size of 11 (0x 0B ) bytes
Table Type 41 ( 0x 29 ) found, size of 11 (0x 0B ) bytes
Table Type 7 ( 0x 07 ) found, size of 19 (0x 13 ) bytes
Table Type 7 ( 0x 07 ) found, size of 19 (0x 13 ) bytes
Table Type 7 ( 0x 07 ) found, size of 19 (0x 13 ) bytes
Table Type 7 ( 0x 07 ) found, size of 19 (0x 13 ) bytes
Table Type 4 ( 0x 04 ) found, size of 42 (0x 2A ) bytes
Table Type 221 ( 0x DD ) found, size of 12 (0x 0C ) bytes
Table Type 16 ( 0x 10 ) found, size of 23 (0x 17 ) bytes
Table Type 17 ( 0x 11 ) found, size of 34 (0x 22 ) bytes
Table Type 17 ( 0x 11 ) found, size of 34 (0x 22 ) bytes
Table Type 19 ( 0x 13 ) found, size of 31 (0x 1F ) bytes
Table Type 20 ( 0x 14 ) found, size of 35 (0x 23 ) bytes
Table Type 221 ( 0x DD ) found, size of 54 (0x 36 ) bytes
Table Type 221 ( 0x DD ) found, size of 68 (0x 44 ) bytes
Table Type 221 ( 0x DD ) found, size of 26 (0x 1A ) bytes
Table Type 136 ( 0x 88 ) found, size of 6 (0x 06 ) bytes
Table Type 13 ( 0x 0D ) found, size of 22 (0x 16 ) bytes
Table Type 14 ( 0x 0E ) found, size of 17 (0x 11 ) bytes
Table Type 127 ( 0x 7F ) found, size of 4 (0x 04 ) bytes

Error 9256: Communication error between application and Intel(R) ME module (FW Update client)

Error 9459: Internal error (Could not determine FW features information)

MeAnalyzer confirms there is no Intel Engine installed

MEA.exe -info

--------- ME Analyzer v1.4.10 ---------

Error, could not access the Intel Engine driver!

--> Make sure you are running ME Analyzer as Administrator!

--> Make sure you are using an Intel Engine compatible system!

--> Make sure you have an Intel Engine driver installed first!

MeAnalyzer says I got ME region in BIOS update file

--------- ME Analyzer v1.4.10 ---------

File: GBDW1108.bin

Firmware: Intel ME
Version: 10.0.36.1030
Release: Production
Type: Region, Extracted
FD: Unlocked
SKU: 1.5MB
VCN: 2
PV: Yes
Date: 04/02/2015
FITC Ver: 10.0.30.1054
Platform: Mobile
Latest: No

Is it possible to extract and reflash only ME region from the BIOS file?

BIOS file - GBDW1108.bin

reply

#1985 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Sat Feb 27, 2016 5:27 pm

@ miasma:

Either at the BIOS or via a hardware jumper, you have disabled ME. If the motherboard has such a jumper, make sure it's at the default state of ME Enabled. Otherwise, there should be a BIOS option (could be called HMRFPO, ME Disable, Protection Disable or similar) which needs to be set to Enabled again. When the ME is disabled the driver interface (MEI/HECI) doesn't work. MEInfo reports that as well of you check (ModeOfOperation: Unsecured mode by H/W jumper & Phase: BringUp).

reply

#1986 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Sat Feb 27, 2016 6:42 pm

There are no hardware jumpers on this board as I can see.

This is the relevant BIOS section - can you help me to identify the option?

I already tried to enable/disable "Me FW Image Re-Flash" from Firmware Update Configuration option without success.

Thanks.

reply

#1987 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Sat Feb 27, 2016 7:22 pm (Last edited: Sat Feb 27, 2016 7:22 pm)

Yes, the BIOS option is indeed the "Me FW Image Re-Flash" one. That should be Disabled by default so that the ME is enabled without the ability to reflash. The fact that the BIOS does not show the version may actually indicate something being wrong with the firmware. Since you have the "Me FW Image Re-Flash" option you should Enable it in order to reflash the ME firmware. I have attached the extracted ME Region from the SPI image you linked above. Extract the file ME.bin and use Flash Programming Tool with the command fptw -rewrite -me -f ME.bin. After it's done (successfully), use Flash Programming Tool again with the command fptw -greset which will reset the platform and ME. Once the system boots up, go to BIOS and disable the "Me FW Image Re-Flash" option. Hopefully you will also be able to see the Version from there as well. If yes, when booted into Windows, run MEInfo and MEManuf tools to check that everything is ok as instructed at the first post.

plutomaniac has attached files to this post

ME_GBDW1108.rar

reply

#1988 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Mon Feb 29, 2016 6:27 pm

It didn't work, I still can't see ME enabled when running MEInfo and it shows as N/A in BIOS.
Also tried to flash ME regions from different BIOS versions for this board without success. It

Is it possible to flash Intel Firmware from the B1 section of the first post?

reply

#1989 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Mon Feb 29, 2016 6:54 pm (Last edited: Mon Feb 29, 2016 6:56 pm)

Zitat von plutomaniac im Beitrag #1984
@ FM:

What system do you have?.......

Hello plutomaniac,

thank you for your answer.
Little bit complicated since the tools do not run in 64bit environment so i had to set up a 32bit...
This is a Fujitsu C5731, SKU shows 18492 if TPM is enabled DIP, 18460 without DIP set.

Verbose of original installed ME with TPM DIP activated:

Copyright(C) 2005-08 Intel(R) Corporation. All Rights Reserved.
Intel(R) MEInfo Version: 5.0.0.1167

Trying to initialize heci...
Reading Fw Status Register....
FW Status Register: 0X3004066A

Manageability Mode is 1SKU is 2110Intel(R) Remote PC Assist Technology is disabled
GET Code versions
BIOS Version: 6.00 R1.06.3004.A1
Intel(R) Standard Manageability code versions:
Flash: 5.2.10 Netstack: 5.2.10
Apps: 5.2.10 Intel(R) Standard Manageability: 5.2.10
FW Capabilities: 62
ASF2
Intel(R) AMT
Intel(R) Standard Manageability
Intel(R) QST
Intel(R) TPM

VendorID: 8086
Build Number: 1023

Manageability Mode: Intel(R) Standard Manageability
UNS Version: Not Available
LMS Version: Not Available
MEI Driver version: 5.2.0.1008
GET Intel(R) AMT STATE
Link status: Link down
Cryptography fuse: Enabled
Flash protection: Enabled
Last ME reset reason: Global system reset
GET PROVISIONING STATE COMMAND FOR THE PARAMETER CONFIGURATION STATE
Configuration state: In process
GET END OF POST STATE
BIOS boot State: Post Boot

GET MAC ADDRESS
MAC Address: 00-19-99-xx-xx-xx

GET FW UPDATE COUNTERS COMMAND FOR THE PARAMETER FWUPDATE COUNTER AND QUALIFIER PARMETERS
FWU Override Counter: Always
FWU Override Qualifier: Always

GET FLASH DESC OVERRIDE COMMAND

GetLanInterfaceSettings COMMAND FOR THE PARAMETER IP ADDRESS
IP Address: 0.0.0.0
MEBx Version: 5.1.0.19
FT Version: 5.2
FT Build Number: 1023
Local FWUpdate: Enabled
Secure FWUpdate: Disabled

GET RCS CAPABILITY
Remote Connectivity Service Capability: False
GET PROVISIONING MODE
Configuration Mode: Enterprise

TPM Vendor ID: INTC
TPM SPEC Version: 1.2.5.2
TPM FW Version: 5.2
TPM Firmware Build Number: 1023
TPM State: Operational
TPM Operational Mode: Enabled Unowned Inactive
iTPM - FIPS 140-2: False
iTPM - Failed Attempts Threshold:61440
iTPM - Initial lockout period: 526
iTPM - Lockout multiplier: 4096
iTPM - Fade-out period: 0
iTPM - Physical presence life time lock flag: False
iTPM - Physical presence command enabled flag: True
iTPM - Physical presence HW enabled flag: True
TPM fuses (MCH/ICH/soft strap MCH/ soft strap ICH): Enabled
FW behavior on Flash Descriptor Override Pin-Strap: Halt

I cannot run fptw because of error 405: There are no supported SPI flash devices installed or ....
Even if I disable TPM...

I recognised the problem with the updated ME on the board: first time the system gets the powercord attached the activity LEDs on the LAN stay ON. Shutting down the system per Windows shutdown with the original ME Firmware, they stay on - so I can use WOL. With the 5.2.71 version they go OFF after first shutdown no matter what combination I tried....

reply

#1990 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Tue Mar 01, 2016 7:07 pm

Hello, I have problem with my Yoga 3 Pro 1370 after ME upgrade. Could someone help me extract ME region from original bios file ?

reply

#1991 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Tue Mar 01, 2016 7:24 pm (Last edited: Tue Mar 01, 2016 7:25 pm)

Just wanted to warn before upgrading ME 5 to 5.2.71 - I just tested it again, upgrading from 5.2.10 (original) to 5.2.50 was perfect, no WOL affected. Upgrading from 5.2.50 to 5.2.71 kills the WOL on the onboard Intel LAN. I resolved it now by installing a separated PCI LAN Intel card, where WOL works again. Seems like no downgrade of the firmware is possible. Can you confirm that plutomaniac? Thank you

reply

#1992 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Tue Mar 01, 2016 8:54 pm (Last edited: Tue Mar 01, 2016 8:59 pm)

I tried to downgrade to 10.0.45.1024 ( version in bios ) but without success so I can only upload the same with -allowsv. I think I have a problem

Error 8741: FW Update Failed.

Error 8758: The image provided is not supported by the platform.

Can you help me, please ?

reply

#1993 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Tue Mar 01, 2016 10:32 pm (Last edited: Tue Mar 01, 2016 10:46 pm)

@ miasma:

If reflashing the ME region did not solve the issue, it's simply not there. Maybe the BIOS has been tampered with or needs a clear cmos or similar? Have you tried reflashing the entire 8MB SPI image to the chip for testing purposes? Obviously keep a backup (dump) first. I am not mentioning anything about the Flash Descriptor because if I remember properly that SPI image from the OEM has it unlocked. That can be checked with MEA by dropping the full 8MB SPI image you linked me before.

@ FM:

Unfortunately I cannot confirm anything as this is an old platform which I have no experience with. I never had an AMT compatible system so I guess it's a general statement. However, it's the first time someone has reported such an issue. My initial thinking was that some MEBx setting was reset or similar. Have you checked MEBx by any chance to see if something is not right? I don't think the firmware is "incompatible", maybe something else is causing this. You said you upgraded as a test from one version to another. Did you do that with older Fujitsu BIOS releases or similar? If yes, can you provide the actual BIOS/SPI image used because the files provided by Fujitsu are compressed in a proprietary way and the one tool from 2006 that extracts these doesn't work properly from what I can see. Apart from MEBx settings, I am also thinking that maybe you need a newer MEBx. The 5.2.71 firmware was found at a Dell system which mentioned at the changelog that the MEBx was also updated to the latest of 5.1.0.0020. You currently have 5.1.0.0019, maybe it's not compatible with the latest 5.2.71 firmware? I wouldn't know as I need the documentation from Intel to determine that for sure. Maybe a GbE firmware update as well is needed. If you can provide a proper SPI image from Fujitsu or at least your system's dumped SPI image, I can look into the MEBx and GbE newer versions that I have and try to update them. Obviously, this is now becoming more invasive and I cannot guarantee that it will work out. If you are an advanced user then I'll gladly see what I can do but if this system is critical for work or something and don't have the tools to recover it in case of a BIOS/ME issue (programmer would be nice to 100% safe) then you shouldn't proceed.

@ blogger:

My guess is that you are trying to flash the wrong SKU or something. Also, "have a problem" does not really help anyone understand if it's even remotely related to ME. And there is no reason to send pms for help, I don't reply to these. Last but not least, I cannot check the ME of your system's BIOS/SPI image because that Lenovo executable refuses to extract on anything but that system and my other quick manual attempts failed. So you need to extract it manually and attach the BIOS/SPI image here or maybe a dump.

reply

#1994 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Tue Mar 01, 2016 11:01 pm (Last edited: Thu Mar 03, 2016 7:12 am)

Zitat
Zitat

I can't make a backup

C:\Intel\Flash Programming Tool\WINDOWS64>fptw64 -d bckup.bin

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

Platform: Intel(R) Premium Express Chipset
Reading HSFSTS register... Flash Descriptor: Valid

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

Error 26: 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.

reply

#1995 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Tue Mar 01, 2016 11:56 pm

If you updated to 10.0.47.1006, that has a VCN of 4 so you cannot downgrade to anything lower with FWUpdate, thus the error. Also the locked flash descriptor (error 26) means that you cannot reflash the entire ME Region as extracted from the Lenovo SPI image. You still haven't mention what the problem is. It's probably not ME related, especially if MEInfo and MEManuf do not report any issues. Check the first post on how to run them and verify that.

reply

Repair MEI on Samsung NP550P7C-S04PL � � Strange ME Region size mismatch after reconfiguring and rebuilding

Page 133 of 380 � Page 1 ... 128 129 130 131 132 133 134 135 136 137 ... 380 Page �

Please enter a reason for warning.