Thank you.My old me version is 9.5.3.1520，my latest ME is Intel ME Firmware v9.5.60.1952 (1.5MB).Is it right?The pictures are my old and latest me version.
@MeatWar Could you send ME System Tools v9.5 r6 to my [email protected],I can’t download it through the disk.Thank you.
Yes its correct, latest ME is Intel ME Firmware v9.5.60.1952 (1.5MB)
No i will not send anything, figure out yourself why you cant download.
OK,my network is wrong.
Zitat von plutomaniac im Beitrag #634
It’s from Toshiba bios, that’s how they usually pack ME firmware.
Since we are talking about weird/rare ME versions, here are the <redacted for forum rule>Intel Server Platform Services Tools for Firmware 3.0 E5 (February 2014) which includes ME firmware v3.0.5.402 from April 2014[/URL]. These are special server tools named spsFITC, spsFPT, spsInfo, spsManuf etc at version 1.1.32.34. Included are some scripts, source code, documentation, firmware, tools and more which are for servers and thus advanced users. If I’m not mistaken they are for Wellsburg PCH (X99 & C612).
Hi there, I’m working on some C612 retired server board BIOS modding and found then link you posted for "Server_ME_v3.0.5.402_Tools_v1.1.32.34.rar". However the mediafire download link was not working. Some old C612 motherboard was only compatible with E5 2600 V3 CPUs, but with E5 v4 cpu installed, it just stucked at POST code 53(Not memory error, I tested the CPU, memory, motherboard separately, they all works well). I’m trying to adjust the newer ME firmware for the BIOS and found that file, can you re-post the file "Server_ME_v3.0.5.402_Tools_v1.1.32.34.rar"? Thanks.
@naivekun
Which motherboards exactly? The Intel ME (Management Engine) has nothing to do with processor support. The microcode is responsible for that.
In general you are wrong. The motherboard can’t boot with incompatible version of ME, but can boot without microcode in BIOS.
I killed the ME in my X299 motherboard, but it still works. How? 
In some cases active ME isn’t required.
Yes, that makes perfect sense. How convenient answer. 
Those are too old, had them once, didn’t work with later versions of SPS 3 Grantley. I suppose you’ll need SPS 3.1…
Transplant/copy a ME from a related stock bios?
(There are motherboards that don’t boot without µcode.)
It’s an OEM motherboard from Inventec, the FRU info shows that the model is "Inventec B600G3", a sticker on the BIOS flash shows "BIOS v1.02 2014/08", It’s too old for e5 v4 famliy. The microcode inside is 306F0, 306F1, 306F2.
I have another C612 motherboard from Quanta, which has a newer ME version and compatible with all of the e5 v3 and v4 cpu. The microcode inside is 306F2, 406F1, 406F2.
I tried to extract the 406F? microcode from Quanta motherboard and Insert/Replace into the inventec one, still stuck at POST code 53. So the next step, I’ll try to move the ME from the Quanta one to the Inventec
However, with my modding experience, simply move ME from one board to another always leads to BMC malfunction. e.g a lot of sensor errors, full speed of the fan, power button not responding, PCIe from PCH malfuntion. That’s why I’m looking for the C612 spsFIT tool and ask @plutomaniac for the C612 ME Tools.
"inventec_b600g3_bios.zip" bios backup from Afu, only 8MB, does not contain ME. I mod the microcode of this file and use Afu to flash it back.
"inventec_b600g3_bios_with_me.zip" bios backup from CH341A programmer, contains ME. (already modded microcode, only modded microcode)
"quanta_s2v_ddr4_bios_with_me.zip" bios backup from CH341A programmer, contains ME.
the inventec board was not compatible with e5 v4, but the quanta board works well with both v3 and v4.
It seems the ME of the inventec board was too old(3.0.7.145). The quanta board was relatively new(3.1.3.23).
[update]
moving ME region from Quanta board to Inventec does not work, still stuck at POST code 53
inventec_b600g3_bios_with_me.zip (3.94 MB)
quanta_s2v_ddr4_bios_with_me.zip (4.58 MB)
inventec_b600g3_bios.zip (3.02 MB)
MEI Driver v2145.1.42.0 (Win10)
CSME 16.0 CON H A v16.0.15.1620
CSME 16.0 COR H A v16.0.15.1605
CSME 15.0 CON H B v15.0.35.2028
CSME 15.0 CON LP B v15.0.35.2039
CSME 15.0 COR H B v15.0.35.2028
CSME 15.0 COR LP B v15.0.35.2039
CSME 14.1 COR H A v14.1.60.1892
CSME 14.1 COR LP BA v14.1.60.1892
CSME 11.8 CON H DA v11.8.90.3987
PMC ADP H A v160.2.00.1036
PMC ADP LP A v160.1.00.1016
PMC ADP SoC A v160.0.00.1036
PMC LKF SoC B v133.0.10.1049
PHY N ADP v14.525.501.8203
Note 1: ME Analyzer v1.260.0 or newer is required for improved CSME 12+ detection. Especially important for CSME 16 and 15 LP.
Note 2: For CSME 16 LP (CON, COR) firmware, a newer Modular Flash Image Tool (MFIT) is required first. Current one is buggy at non-H firmware.
Hi,
have problem wih z690-a strix D4
Can’t boot any UEFI OS, only W7 and XP. This is MEI problem. Tryed to flash bios many times to triger update MEI but without any luck. All day trying to start tools in W7 but no go got 0xc00007b eror
@d0minat0r
Damm sir… a brand new board/chipset and you’re telling us that you cant boot UEFI OS… this is serious, have you report this issue to Asus, they may not know this, this is really a serious case, you should report it.
Can you tell us how did you found the MEI issue and its cause? We would appreciate that…
Latest bios version 0901 comes with Intel ME FW image 16.0.15.1545.
Asus released an ME FW update to version 16.0.15.1620: https://dlcdnets.asus.com/pub/ASUS/mb/03…0.15.1620_T.zip
This ME update should be done after a successful update of the 0901 bios.
This is ME16 Firmware update, not Intel MEI OS driver update.
yes but for asus tool for firmware update need mei driver. second problem is I bought mb in other country and it little complicated to send to rma. maybe try update firmware with programator