Is there a Flash Image Tool- version or ME System Tools- package that supports Bios with Intel SPS 3 ME firmware? (Asus P9D-I, C222 chipset, bios 1801). Tried versions for normal ME or TXE- versions, they do (of course?) not work.

Thanks in advance!

Hey im new to this forum, please help me out, i have a alienware 15 r2 skylake 6700HQ, i think HM170 chipset.. it came with 11.0 firmware i believe.. and BIOS is updated to latest one, 1.3.12... could you tell me which version of ME firmware is proper one for my motherbaord.. i updated to 11.7.4.3314 version, with latest ME Consumer driver 11.7.0.1035.. im not able to revert back to 11.0 firmware.. downgrade gets failed.. just curios to know whether im using the right firmware.. thank you.

Hi, I'm new to the forum. Not sure if this is the right place to ask such question.

Earlier this year, my Asus Z170 Hero Alpha mobo had a RMA due to the ME Version shows 0.0.0.0 in BIOS, after I try to update BIOS from v2202 to v3201.
When I got my replacement mobo, I succesfully updated BIOS from v2202 to v3401. Unfortunately, the "ME Version shows 0.0.0.0" came back when I update the BIOS from v3401 to the latest v3504.

Symptoms:
PC is still bootable, but the post code in MB shows "01" around 15 seconds before the ROG logo shows up/monitor light up, cause slow boot.
ME Version shows 0.0.0.0 in BIOS.
Intel Management Engine Interface despaired from Device Manager.
Not able to run Meinfo, it closes immediately. error.log: Internal error (Could not determine FW features information)
Not able to run FPTW64, it closes immediately when I press ANY key on the keyboard. error.log: Invalid parameter value specified by user. Use -? option to see help.

I have tried:
Clear CMOS; reflash BIOS; downgrade by using USB FLASHBACK BIOS; unplug power cable and battery; reinstall Windows ME driver but got error message "This platform is not supported."

Any suggestion and advice will be appreciated.
ps. Will purchase a USB Programmer CH341A fix this issue?

fptw -greset, unplug power for 2 minutes, should fix itself.

PS. LOL, they all close immediately, fptw64 and meinfo and pretty much all those DOS mode tools, doooh, unless you run them in Command Prompt with admin mode.

Zitat von Ataemonus im Beitrag #3220

---

fptw -greset, unplug power for 2 minutes, should fix itself.

PS. LOL, they all close immediately, fptw64 and meinfo and pretty much all those DOS mode tools, doooh, unless you run them in Command Prompt with admin mode.

---

No shit ?
Of course you get the errors, because the ME Firmware is not there.
But you continue to avoid the proposed solution. Worked for me in the very same situation, just a different motherboard.

Zitat von Ataemonus im Beitrag #3222

---

No shit ?
Of course you get the errors, because the ME Firmware is not there.
But you continue to avoid the proposed solution. Worked for me in the very same situation, just a different motherboard.

---

Nevermind, if a simple unplug is too complicated and you expect the computer to do it by itself, clearly the problem is far too great for you to solve.

Zitat von vstar im Beitrag #3223

---

Zitat von Ataemonus im Beitrag #3222

---

No shit ?
Of course you get the errors, because the ME Firmware is not there.
But you continue to avoid the proposed solution. Worked for me in the very same situation, just a different motherboard.

---

I just tried fptw64 -greset, pc reboots itself instead shutdown to let me unplug power.
Should I shutdown it normally, then unplug power and battery?

---

Zitat von Ataemonus im Beitrag #3224

---

Nevermind, if a simple unplug is too complicated and you expect the computer to do it by itself, clearly the problem is far too great for you to solve.

---

Zitat von plutomaniac im Beitrag #1

---

Never flash RGN firmware to the Engine region without first configuring them for your specific system (EXTR) via Intel's Flash Image Tool. The use of any software (Intel's Flash Programming Tool, AMI's AFU, Flashrom etc) or hardware (programmer) firmware flasher, which directly deals with the Engine region of the SPI/BIOS chip, requires prior configuration of ME RGN to EXTR firmware.

---

@plutomaniac:

The meupd.bat contains the following code

@echo off
if exist me.bin goto UPD
echo File me.bin not found.
goto EXIT
:UPD
echo Updating ME firmware from me.bin
fwupdlcl -f me.bin
:EXIT
echo Thank you for using FTK. Have a nice day.
 

so yes, it uses FWUpdate.
If i get it right, and update the ME firmware my way, i do not need to worry whether its RGN or EXTR?
I previously flashed 11.6.25.1229 (which exact name is 11.6.25.1229_CON_H_D0_PRD_EXTR.bin), and now i have got 11.7.0.3290 (11.7.0.3290_CON_H_D0_PRD_RGN.bin), and i could not notice any difference/problems.

Zitat von plutomaniac im Beitrag #3227

---

@ vstar:

MEInfo, MEManuf and FPT are command line tools so you need to open a command prompt first to use them. That aside, have you tried to test if running Flash Programming Tool with command "fptw -greset" fixes the problem? Does "fptw -d spi.bin" command complete successfully or do you see an error? If you have a hardware programmer such as CH341A, that would definitely solve the problem.

---

Zitat von plutomaniac im Beitrag #3230

---

@ vstar:

You can do it at the same pc if you like (let it boot, remove chip and place back before next reboot) but it's preferable to use another one if you have. You need to remove the SPI chip and program it with the programmer by using the latest ASUS BIOS from their website after removing the AMI Capsule. Use UEFITool to easily remove the latter, just save the "Intel Image" as a new file.

---