I don’t know if you can help with this but since it involves very old firmware I thought I would give it a try. Regarding ME5, up until now I knew about these:
AMT Professional : EL_ICH10_SKU1_ME_Production.bin AMT Basic: EL_ICH10_SKU4_ME_Production.bin
It makes sense for there to be SKU2 & SKU3 images as well but I hadn’t found anything like that so far. Today, I extracted from a Sony SPI image this region:
It’s smaller than AMT Basic or AMT Professional and has less sections. The $SKU is also different so I’m thinking it’s either SKU2 or SKU3. I have searched the ICH10 datasheets but there is no clear answer. That Sony desktop had a P43 Express chipset so according to Intel that means ICH10 (not D or DO so AMT is out of the table).
Do you happen to know (or be able to tell) what’s the name of that ME5 SKU? My guess is it’s either RWT, ASF or QST. Probably the latter.
As far as I know, there were 3 ME5 versions: 4MB corporate, 4MB consumer and 8MB consumer, but some big companies like Sony or Apple could use a stripped-down ME version with non-zero OEM ID and get another ME version from Intel just for themselves.
I discovered that SVN number is not the one I thought (4-bytes before VCN) but rather exactly after build (2 bytes) number. This will be fixed at next release 1.0.3. There is also another bit that signifies whether the image is PV or not. Once I find it, I’ll add this as well.
I am almost certain this applies for the first PCH so that’s ME6 and not ME5. Also, ICH ME never had OEM-IDs as far as I can see from FITC settings. This ME5 SKU is either ASF or QST (both such firmware existed at ME2 and ME3). ME4 was mobile only and mostly TPM-based so it’s different.
Well I used ASUS 5th gen cpu IMEI updater and it updated my ASUS Z87 Deluxe to 9.1.25.1005 from 9.0.30.1482… All went smooth until I checked bclk
In my case its at 100.94mhz (cpuz or Aida cpuid detects as 101mhz), which also makes 50mhz higher OC 4.70ghz is now 4.75ghz or stock 3550mhz… It activates as soon as I enable XMP… If I load optimized defaults it detects at fixed 100mhz again, but if I change anything it detects as 100.94mhz… 125mhz strap doesn’t work either…
EDIT: OK nvm guess I got really lucky phew, I tried Asus flashback2 with latest 2103 as last chance and it reverted back to old firmware! YES!
Hopefully all is ok now…
EDIT2: after I made this 2nd screen RealTempTI showed 99.94mhz, but then I flashed again in windows using 4th gen IMEI and 2103 bios and now its finally fixed, even when I OC’ed back to 4.7 and re-enabled XMP!! lol Now I really won’t change that ever again, lesson learned for good!
Normally BIOS Flashback does not solve this problem because it only restores unlocked SPI regions (usually BIOS only and not the locked ME). Your motherboard has an unlocked Flash Descriptor so ME was unlocked for write access. Yes, you were lucky to have an unlocked descriptor. Now, you can update to the latest 1.5MB v9.0 firmware which is 9.0.31.1487 and can be found at the first port of mine.
Updates (02-03/05/2015):
Added at ME System Tools v10.0 r1: 1.5MB FW Release Notes v10.0.26.1000 (HF , 07/2014) Added at ME System Tools v9.5 r1: 1.5MB FW Release Notes v9.5.13.1706 (MR1 , 08/2013) Updated at ME System Tools v9.5 r1: 1.5MB and 5MB Intel(R) ME SW Only Release Notes from v9.5.21.1754 → v9.5.24.1790 Updated at ME System Tools v9.0 r1: 1.5MB FW Release Notes from v9.0.3.1347 (04/2013) → v9.0.21.1462 (09/2013) Updated at ME System Tools v9.0 r1: 5MB FW Release Notes from v9.0.14.1402 (07/2013) → v9.0.21.1462 (09/2013) Updated at ME System Tools v9.0 r1: MEBx Release Notes from v9.0.0.0024 (03/2013) → v9.0.0.0025 (05/2013) Updated at ME System Tools v6.0 IGN r2: System Tools User Guide from v1.05 (11/2009) → v1.07 (03/2010) * Added at ME System Tools v6.x r2: Ibex Peak 4MB Firmware Release Notes v6.1.20.1059 , v6.0.40.1215 & v6.0.0.1184 Updated at ME System Tools v6.x r2: IBX QST Tool User Guide from v0.75 (07/2009) → v1.0 (02/2010) Updated at ME System Tools v6.x r2: QST Tools from v6.0.3.1195 package → v6.0.40.1215 package Updated at ME System Tools v6.x r2: ME 4MB FW Bring Up Guide from v6.0.3.1195 (11/2009) → v6.0.40.1215 (03/2010) Updated at ME System Tools v6.x r2: System Tools User Guide from v1.05 (11/2009) → v1.07 (03/2010) Updated at ME System Tools v6.x r2: Flash Image Tool from v6.0.30.1202 → v6.0.40.1212 Added at ME System Tools v6.x r2: ConfigWizard v6.0.40.1212 Removed from ME System Tools v6.x r2: ConfigWizard v6.0.2.1189 extra package Updated at ME System Tools v6.x r2: Flash Programming Tool(Windows) from v6.0.30.1202 → v6.0.40.1214 Updated at ME System Tools v6.x r2: MEManuf(DOS) from v6.0.30.1202 → v6.0.40.1214 Updated at ME System Tools v6.x r2: MEManuf(Windows) from v6.0.30.1202 → v6.0.40.1214 Updated at ME System Tools v6.x r2: UpdParam(DOS) from v6.0.30.1202 → v6.0.40.1212 Updated at ME System Tools v2.x r1: FWUpdate(Local-Win) from v2.5.1.1025 (29/08/2007) → v2.5.1.1034 (30/06/2009)
Updated at ME Thread: Intel ME 6 Firmware 1.5MB from v6.0.3.1195 → v6.0.40.1215 Updated at ME Thread: Intel ME 6 MEManuf (DOS/Windows) from v6.0.30.1202 → v6.0.40.1214 Updated at ME Thread: Intel ME 2 FWUpdate(Local-Win) from v2.5.1.1025 → v2.5.1.1034
Note: From now on, ME & TXE System Tools will follow the same revision (rX) scheme as the Firmware Repository. As of yesterday, all System Tools start from r1. Today’s updates at 6.0 IGN and 6.x 1.5MB/5MB are followed by r2.
Thank you for the report of new 9.1 firmware guys. The one you posted is dirty/EXTR though. You can find the clean/RGN version from Lenovo.
Updates:
NEW!Intel ME 9.1 1.5MB Firmware from v9.1.25.1005 –> v9.1.26.1006 (Clean/RGN)
Updated at ME System Tools v8.1 r2: 5MB FW Release Notes from v8.1.20.1336 (11/2012) –> v8.1.30.1350 (01/2013) Updated at ME System Tools v8.1 r2: 5MB FW Bring Up Guide from v8.1.20.1336 (11/2012) –> v8.1.30.1350 (01/2013) * Updated at ME System Tools v8.1 r2: MEBx Release Notes from v8.0.0.0066 (05/2012) –> v8.0.0.0069 (11/2012)
MEBx stands for Management Engine BIOS Extension. It’s only for AMT/5MB systems and it provides a boot menu where you can adjust ME settings & available features. It’s basically like the RST option-rom menu. For legacy systems you access MEBx via Ctrl+P during system bootup.
Note: ME/AMT 1.0 is the firmware of the Intel 82573E Gigabit Ethernet Controller (codename Tekoa). Unlike ME2 and up it’s not found inside the SPI image but on the controller itself. The images I’ve found were included with SPI BIOS updates in order for the controller to be updated while a system BIOS update is performed.
Also, UnHuffMe v2.4 was released with fixed SPS 3 support. ME11 is not supported yet.
I have been trying to flash my msi Z97 MpowerMax Ac board with the New Version ME Firmware 9.1.26.1006 and this is what I get.Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\NICK>CD C:<br /> C:>CD C:\Local-Win64
C:\LOCAL-Win64>FWUpdLcl64 -f ME.BIN
Intel (R) Firmware Update Utility Version: 9.1.2.1000 Copyright (C) 2007 - 2014, Intel Corporation. All rights reserved.
Communication Mode: MEI Checking firmware parameters…
Error 8714: Firmware update not initiated due to file open or read failure
I do not have the file open in a hex editor,what else would cause the firmware to not run due to file open or read failure.The command prompt is run as administrator also,and my anti virus is disabled with the firewall too.Anyone have any ideas on what else I could try.
Is the file called ME.bin or did you forget to change it’s name? This might be something Windows-specific. Try updating via DOS.
@All:
Generally, I suggest to all of you to use FWUpdate via DOS/EFI to limit all chances of a Windows program/service interfering with the flashing process.
Back in February I ended up bricking my laptop because for some weird reason FWUpdate decided to freeze at 50%. It must have been some Windows process that caused it to freeze and so I’m advising everyone to do the same if possible.
In case something does go wrong while flashing with FWUpdate inside Windows and if you have an unlocked flash descriptor, remember that you can recover via FPTw by reflashing the entire ME region before rebooting of course!
If I’m not mistaken you have a ME9.1 and ME10.0 system. Can you provide me with two UPD images from those systems? You need FWUpdLcl -save command for this. There’s no rush of course.
Yep, I renamed Intel ME 9.1 Consumer 1.5MB Firmware v9.1.26.1006 to ME.BIN.I ran the command FWUpdLcl -fwver it ran ok,also ran FWUpdLcl -save OLD.BIN and it did that ok.It just will not do FWUpdLcl64 -f ME.BIN .
As I said, try the DOS version. Probably something Windows-specific.
Also, can you attach your old.bin firmware? It’s not relevant to the issue that you are having, it’s just that I’m looking for update images of ME9.1 and ME10.0 firmware. Your’s is ME9.1.
, I tried Asus flashback2 with latest 2103 as last chance and it reverted back to old firmware! YES! 
