AFAIK there is neither a Firmware v1.3 nor a Firmware v1.5. So you cannot update the Firmware v1.3 to v1.5
Flashed the new firmware: v9.1.1.1000
Is not good for z87 (Maximus VI Extreme) , BCLK Bug
Thanks for your report.
So which Intel ME9 1.5MB Firmware version do you recommend to use?
For time being, I would recommend "ME9 1.5MB FWUpdate v9.0.31.1487"
On the other hand, Iām having trouble downgrading? :
Anyone knowing whatās going on?
/Cheers
Hello! I have tried on my Q87 MEI 5MB - all 9.0.* versions, and successfully downgraded to stock, but after I have flashed 9.1.0.1120 and tryed to downgrade to 9.0.* - I got same message as in previos reply: "Error 8704: Firmware update operation not initiated due to a SKU mismatch". As I understood - 9.1.* fw is for 9x chipsets, or it is officially suitable for Q87 too? Is there any possibility to revert my mobo to 9.0.*?
@ KuDeSnik33ra:
Welcome at Win-RAID Forum and thanks for your report!
These questions should be answered by our ME9 Firmware experts.
Since I donāt have an Intel 8- or 9-Series chipset system, I am not sure regarding this special topic.
Regards
Fernando
I have one off-topic question. Is it recommended to apply the latest INF chipset package 10.x.xxxx from station-drivers even for old chipsets like PM45?
@gpvecchi
Have you tried the latest method I posted to remove MEI drivers or have you reinstalled the OS?
I know that GbE can be updated by hex, Intel FITC or Intel FPT. If you have any other method, please share, even though this only concerns users with an (older) Intel Lan card. There is some differences between 1.3 and 1.5, which could be anything from bugfix, feature enable/disable or ID check. The first red byte is the version.
[[File:Intel GbE 1.3 vs 1.5.png|none|auto]]
@PROMAN28
I already answered your question.
@tObber166
The new 9.1.x ME firmware has a new chipset / SKU version. The updater detects this new version and prevents any downgrade. Why it worked in the first place, it is a different question. Try to flash an original BIOS or use FPT.
@kevindd992002
I have tried the new 10.x package on my PM45 and the SMBus driver is not working, preventing sensors to read the temperature on my RAMs. Luckily I have the Synaptics touchpad drivers, which installs its own real driver. So it is best to stay with 9.x on older hardware.
Hallo! Sorry, I havenāt tried because of lack of timeā¦ Iām going to try todayā¦
This is what I used to update GBe on my Z77, I used old version, I actually found a newer one;
https://drive.google.com/file/d/0B3HG-j1ā¦dit?usp=sharing
This is the howto (taken from another forum, all credits go to author)
Flashing GbE region only. Command: gberefl. The BIOS file to flash must be named "bios.bin" and must be in the same directory with FTK. You can use a file from another board as GbE source.
Use it to reflash/update/downgrade your GbE region.
The command works as follows: Intel FPT makes BIOS backup copy named backup.bin. Then FD44Copier copies MAC to bios.bin file. Then it removes CAP-file header (if present) from bios.bin file. Then FPT erases GbE region and flashes GbE region from bios.bin file to BIOS chip. If something goes wrong, the error message will be shown. If so, you can use restore command to restore your BIOS to previous state.
Again, no need to use anything special, normal reset is enough.
@Fernando I now understand; region=part of bios including GBe, I thought you were talking of a world region, like DVDsā¦ 
@ gpvecchi:
Thanks for details about how to "update" the GbE region.
Much more interesting for me is the question: Which are the benefits for the user?
@gpvecchi
Let me add a few things. The author of FTK is CodeRush and the site is this. It was mostly designed for ASUS boards, which use the module FD44820B- to store these informations. Any .bat that uses FD44Cpr.exe on other boards will probably fail, because of not finding ASUS signature and storage.
Edited: only biosrefl.bat and reflash.bat should fail on non-ASUS boards, because they rely on FD44820B- providing some data. GbErefl.bat will work because it reads the MAC from the backup it takes. But this requires that all regions are unlocked. So I still say that the next command should be tested first.
This is my question: why not use āfpt -rewrite -savemac -savesxid -gbe -f gbe.binā instead, which should work on all boards?
And for Fernandoās question: the GbE region seems to store info like MAC address, ID, name/presentation of Lan controller. So it is best to have the latest/cleanest version corresponding to your board.
So will installing the latest 9.x package with the -overall switch fix the issue if you already went ahead and tried installing v10.x?
And any computer using 2nd gen Intel core is considered a newer platform that v10.x supports, correct?
Are you speaking about the Intel Managment Engine Drivers & Software Sets or the Intel Chipset Device Software Sets ("INF Update Utilities") v9 and v10?
Both contain completely different things. The topic of this thread is the Intel Management Engine Interface.
Are you speaking about the Intel Managment Engine Drivers & Software Sets or the Intel Chipset Device Software Sets ("INF Update Utilities") v9 and v10?
Both contain completely different things. The topic of this thread is the Intel Management Engine Interface.
Sorry, I was talking about the Intel Chipset Device software that I ask as an off-topic question yesterday. Can you answer it via PM though?
Flashing original BIOS donāt help. Can you please add some info about FPT?
Ok, I will give you an answer here, but please donāt continue the off-topic discussion within this "Intel Management Engine" Sub-Forum.
If you had installed the v10 Intel Chipset Device INF files this way, you can try that.
Since I donāt like the " -overall" command suffix at all, I would "downgrade" the related INF files manually from within the "System Devices" section of the Device Manager (look for the "Driver" version of all listed Intel devices) by using the "Have Disk" button.
@lordkag Thanks for updated infos!
I tried your updated manual remove of Intel driversā¦ No successā¦ In particular I noticed that I have a very few of that entries, just some reg value.
@tObber166
@KuDeSnik33ra
Try the package corresponding to your board, at your own risk. I assume you know how to flash them, so please avoid āhow toā¦ā questions. They are compiled to that specific SKU, rather than an empty one.
tObber166 might also be in luck with other methods, since he has provided details about his board. First try flashing a BIOS file with UBF. It will most likely be pointless, because I donāt think it will touch the ME region. Then try with āfpt -rewrite -me -f me.binā. Your board seems to have all regions unlocked, but I could be wrong and the BIOSLock is set. You can also try flashing a BIOS file using afuwin/afudos with the /ME command, which will flash the ME region - one warning though, better remove the capsule header. The last attempt would be to erase the ME region and then flash a new one, but this is dangerous without a programmer to recover (and pointless when you have a programmer to flash the full chip).
Please download the packages as soon as possible, because I plan to remove them to avoid cluttering the forum.
Edited: as promised, packages removed. The Q87 package was wrong from the start, since I had forgotten that it needs a 5MB firmware and not a 1.5MB one. It is also better to use FTK from here, since it packs some nice .bat files to avoid typing all commands. Some warnings: when flashing the ME using fpt, provide either a bios file or a full 1.5/5M ME file, not the small saved old.bin. Also, some ASUS users might watch for a new BIOS region protection.
@gpvecchi
At least we tried. Did you also cleaned the reg hives with CCleaner, to remove all remaining related keys? I even managed to remove a broken Office using the manual way, repairing .NET framework installation, correct some nasty bugs related to slui.exe, remove RST and MEI drivers, re-register broken dll etcā¦
I did also used procmon (Process Monitor) sometimes, but the important thing is to have a strong will and follow all connections. At this point, I think you are only left with a clean install.
Thanks for the files! I have successfully reverted to 9.0.* versions using FTK. Unpack archive to DOS bootable flash, place stock bios file as bios.bin - boot to this DOS - exec merefl.bat for ASUS, merefl_ga.bat for Gigabyte. For me everything works ok, BUT there can be problem with ASUS - write protection in BIOS, there is info in the internet how to remove protection with FTK. On my GA-Q87N there is no protection.