PDA

View Full Version : Intel MEI & ME Version 8.1.10.1300 & 8.1.10.1286 (driver and FW)



nikolator
10-18-2012, 08:49 AM
Just found http://www.station-drivers.com/forum/viewtopic.php?f=32&t=4116
Made easy installation of driver ver 8.1.10.1275 and soft and no sucsess of FW...
Any ideas how to jump from version 7... of FW?

nikolator
10-18-2012, 10:34 AM
another link with instructions for x79
ftp://europe.asrock.com/drivers/Intel/Others/ME_Win8-64_Win8_Win7-64_Win7_Vista64_Vista_XP64_XP(v8.1.10.1286_5M).zip

but for me it's too complicated...
this link is dead now, the difference between the previous one was just manual

jezjohnson
10-18-2012, 11:14 AM
Looks fairly complicated, hopefully someone has a bit of time on their hands to work this one out! :)

tistou77
10-18-2012, 01:18 PM
For MEI Driver it's OK, but I have not tested for the firmware, it's complicated?

And I tried to install (.exe), and I got it 3 update, what they correspond?
If I want to manually install

12671

Thanks

Necrosan
10-18-2012, 02:06 PM
I was able to successfully update to ME version 8.1.10.1286 by using FITC to save the image for Patsburg X79 (Change number of flash components to 0 for ME only, as Intel instructs) then flash it using "fptw64 -ME -F ME8_X79_HED.bin"

(If you'd like you can make backup of ME region with fptw64 -ME -D backup.bin)

Worked 100% perfect. Make sure you shutdown after you flash (reboot is not enough)

Also, if it wasn't clear by the utility this flash was done inside of Windows, although I'm sure it would work the same if performed from a DOS boot.

12672



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

Intel(R) ME code versions:

BIOS Version: 3010
MEBx Version: Not available
Gbe Version: 1.3
VendorID: 8086
PCH Version: 5
FW Version: 8.1.10.1286
UNS Version: Not Available
LMS Version: Not Available
MEI Driver Version: 8.1.10.1275
Wireless Hardware Version: Not Available
Wireless Driver Version: Not Available

FW Capabilities: 0x00101460

Intel(R) Anti-Theft Technology - PRESENT/ENABLED
Intel(R) Capability Licensing Service - PRESENT/ENABLED
Protect Audio Video Path - PRESENT/ENABLED
Intel(R) Dynamic Application Loader - PRESENT/ENABLED

Cryptography Support: Disabled
Last ME reset reason: Power up
Local FWUpdate: Enabled
BIOS Config Lock: Disabled
GbE Config Lock: Disabled
Host Read Access to ME: Enabled
Host Write Access to ME: Enabled
SPI Flash ID #1: EF4017
SPI Flash ID VSCC #1: 20052005
SPI Flash BIOS VSCC: 20052005
BIOS boot State: Post Boot
OEM Id: 00000000-0000-0000-0000-000000000000
Capability Licensing Service: Enabled
OEM Tag: 0x00000000
Localized Language: Unknown
Independent Firmware Recovery: Disabled


Simple flash instructions (Inside Windows x64 using Intel Flash Programming Tool (NOT FWUPDATE!)):
fptw64 -ME -F ME8_X79_HED.bin

Here are links to the two different versions:

Download High-End Desktop Build (Mimics ME settings from stock RIVE ME) (http://dl.dropbox.com/u/6400726/ME8_X79_HED.bin)

Download Workstation Build (Includes the FW capabilities listed above, not sure if they work on our platform) (http://dl.dropbox.com/u/6400726/ME8_X79_WS.bin)

tistou77
10-18-2012, 02:29 PM
Can you explain in detail for FITC, I do not understand how to update, please

In DOS mode, it does not work :(

Thanks

Necrosan
10-18-2012, 02:31 PM
Can you explain in detail, I do not understand how to update, please

In DOS mode, it does not work :(

Thanks

You are likely trying to use the wrong tool.
Re-read my post and do exactly as I instructed. If you do this incorrectly you run the risk of ruining your board.

tistou77
10-18-2012, 02:34 PM
That's what I do not understand (which is what is in FITC)


by using FITC to save the image for Patsburg x79 (Change flash region to 0 for ME only, as Intel instructs) then flash it using "fptw64 -ME -F ME_81101286_X79.bin" (outimage being the output file from FITC)

Thanks

Necrosan
10-18-2012, 02:37 PM
That's what I do not understand (which is what is in FITC)



Thanks

Just follow "Simple Instructions" - the info you quoted is how I generated the valid image for our board and not applicable to those just wanting to update.

tistou77
10-18-2012, 02:56 PM
Ok I just use fptw64 and your file .bin?

Alex1990
10-18-2012, 04:07 PM
Ok I just use fptw64 and your file .bin?
Yes! but i copy all file from folder "Flash Programming Tool\Windows64" to local disk D:/ and run "fptw64 -ME -F ME_81101286_X79.bin"/ update succesful! thanks Necrosan

tistou77
10-18-2012, 04:18 PM
Yes that's what I did (if it is missing. Dll) and it's OK
I have not tested the DOS mode (USB key), but it should work as I think

Thanks necrosan ;)

Otherwise, it's weird, I can not take screenshot of the bios (USB key), I got a message that the USB does not have enough free space, but it is empty

Techotic
10-18-2012, 04:46 PM
I got a "PDR Region does not exist" message when updating firmware (see attached). Hopefully that's nothing to be concerned about.

tistou77
10-18-2012, 04:56 PM
Another method

Fwupdate: DOS or Windows (use the corresponding files)
MEInfo: To know the version

https://rapidshare.com/files/281832325/System_Tools.7z

EDIT: it's same for me, Techotic ;)

Necrosan
10-18-2012, 05:12 PM
I got a "PDR Region does not exist" message when updating firmware (see attached). Hopefully that's nothing to be concerned about.

That region doesn't exist in the .BIN I provided - perfectly normal message. Just means the PDR region remains untouched.

Necrosan
10-18-2012, 05:34 PM
FOR TINKERERS ONLY - Don't bother with this information unless you are testing things out. And _ALWAYS_ remember to make backups.


Just tested and you can also update to the latest GBE firmware included in that ME update and it works perfectly fine. (Made for our controller, 82579V)
I compared the original & the new version to make sure they weren't the same, also. (No sense updating if the same)

Not sure how to determine the differences as they both just list as version 1.3 in MEInfo application.

Backup old version first with: fptw64 -GBE -D backupgbe.bin

To update, move 82579_C0_CPT_B2_VER0PTD4.bin (8kb) to same folder as fptw64 and flash like this:
fptw64 -GBE -SAVEMAC -F 82579_C0_CPT_B2_VER0PTD4.bin


Make sure you shutdown after flash as GBE controller won't work until you do

Necrosan
10-18-2012, 05:40 PM
Also not sure if these are new features to ME 8 firmware, but they sound interesting regardless and are noted in the update PDF:

• Platform Clocks – Tune Intel® C600 Series Express Chipsets clock silicon to the parameters of a specific board, configure clocks at run time, and power management clocks. Benefit: Allows extensive customizability and soft control of “Third generation” clock solution and makes clocks available before CPU powers up.

• Silicon Workaround Capability – Intel® ME FW will have limited capabilities to perform targeted workarounds for silicon issues. Benefit: Allows Intel® ME FW to address some issues that otherwise would require a new silicon stepping.

• Thermal Reporting – Intel® ME FW has the ability to collect platform thermal data and provide that data to embedded controllers and super I/O devices over SMLINK1 as well as in memory map I/O space.

jezjohnson
10-18-2012, 05:46 PM
All working great here, thanks Necrosan

tistou77
10-18-2012, 05:50 PM
Firmware 8.0 is better for X79?
if I understood correctly

It is better to upgrade the GBe too?

Thanks

PS: Besides, what's the GBe?

Necrosan
10-18-2012, 05:51 PM
Totally up to you. Not sure what the differences are so the call is yours. I am certain however that this is the most recent GBE bin available for our chipset.

Nodens
10-18-2012, 05:59 PM
Necrosan regarding the GBE, the firmware could be tied to the OpROM in the UEFI. I don't suggest flashing it until I check the OpROM versions.

tistou77
10-18-2012, 06:08 PM
Ok thanks Necrosan, I will update to GBe, also ;)

Necrosan
10-18-2012, 06:12 PM
Necrosan regarding the GBE, the firmware could be tied to the OpROM in the UEFI. I don't suggest flashing it until I check the OpROM versions.

You can always revert it to the original version if that does turn out to be an issue. Let us know what you find out, can't wait to hear.
I've had none yet, and have uploaded the original version here for anyone that encounters any issues: oldgbe.bin (http://dl.dropbox.com/u/6400726/oldgbe.bin)

Nodens
10-18-2012, 06:58 PM
They're probably unrelated but I gave a warning just in case anyone is seeing any trouble. The ME Interface is probably tied to the GBE firmware for the remote control aspects of ME and GBE firmware could be tied to the GBE OpROM due to Booting from LAN and possible integration with the ME (even so it could pose no issue at all if the GBE OpROM is not loaded). I'll probably have time to do a bit of digging tomorrow and I'll tell you if I find anything.

tistou77
10-18-2012, 07:05 PM
Thanks Nodens for your feedback ;)

nikolator
10-18-2012, 10:22 PM
Just tested and you can also update to the latest GBE firmware included in that ME update and it works perfectly fine. (Made for our controller, 82579)
I compared the original & the new version to make sure they weren't the same, also. (No sense updating if the same)

Not sure how to determine the differences as they both just list as version 1.3 in MEInfo application.

To update, move 82579_C0_CPT_B2_VER0PTD4.bin (8kb) to same folder as fptw64 and flash like this:
fptw64 -GBE -F 82579_C0_CPT_B2_VER0PTD4.bin
(Optionally backup old version first with: fptw64 -GBE -D backupgbe.bin)

Make sure you shutdown after flash as GBE controller won't work until you do

Hi,

WB HEDT 1.5MB FW Bring Up Guide 8.1.10.1286_.pdf (page 13 of 91) says
"82579_B0_CPT_B1_VER0PTD4.bin Intel® LAN PHY firmware image. This image is for Romley Workstation platforms only."

Thanks a lot for you work!

tistou77
10-18-2012, 10:41 PM
not useful for us :D

nikolator
10-18-2012, 11:34 PM
The prosedure upgrating FW is working for p9x79PRO also

If someone installed driver before FW upgrade (as me) I recomend reinstall the soft, couple new services will appear (btw not nessary ones..)

Premudriy
10-19-2012, 12:06 AM
Ok, guys, as soon as I flashed the GBE (GigaBit Ethernet) the LAN adapter was not working. I tried removing the driver for it, resetting settings, but nothing would help.

I saw that adapter was sending out packets, but no packets were received (shown 0 packets in adapter properties/status). Looks like it lost ability to receive packets all of a sudden.

To resolve this I had to flash my previous firmware backup for it.

So note to everyone: BACKUP YOUR GBE FW before flashing!


The ME firmware flash, however, was very smooth. Thank you Necroson!

Necrosan
10-19-2012, 12:13 AM
Been using it for a few hours now, interesting find about Romley platform note.

Premudriy - You need to shutdown fully after flashing it, as I explained in the post. You clearly did not do that.

tistou77
10-19-2012, 12:20 AM
It is better to update the Gbe or not?
Knowing that it is for Worstation?

Thanks

Nodens
10-19-2012, 12:44 AM
Romley Workstation Platform means Xeon Multi-CPU..

Premudriy
10-19-2012, 01:07 AM
Necrosan, I did shut it down. I followed all instructions word by word. I did:
1) Rebooted computer, turned all antivirus/firewall, just in case.
2) Flashed ME firmware.
3) Shutdown computer
4) Started it again and went to BIOS to verify that ME version got updated (It did, wohoo!)
5) Booted to windows, flashed GBE
6) Shutdown the machine
7) Booted and noticed that network is gone.
8) Uninstalled LAN driver, fully shut down the machine, even removed the power cord and waited a minute
9) Booted windows in Safe Mode and looked/removed all possible hidden versions of GBE adapter in device manager.
10) Rebooted, installed the driver again, no connection. Noticed that packets are sending, but not receiving.
11) Went to properties of lan adapter and clicked "Defaults" on all tabs that had it, even changed the connection to 10MB/s
12) Shut down the machine again, removed power cord
13) Booted up, still same, no connections, packets received, but not sent.
14) Flashed the old backup of the firmware, then went to here to post about this.

I usually try to read the entire thread when I attempt to do something that can potentially brick my hardware, so I always make sure that I follow the safest procedure described and complete all the steps.

It just somehow did not work on my system. I'd be thankful if more people tried to flash the GBE firmware and report their success/failure. If everyone will have success, I'll try flashing again.


Another note, when I flashed the new GBE firmware, my adapter was detected as a new hardware (Intel(R) 82579V Gigabit Network Connection #2) and even after removing all dead/hidden network adapters in device manager in safe mode, it was still detected as such. Not sure why.


EDIT: it was always "packets sent, but not received"

Necrosan
10-19-2012, 01:28 AM
Very strange as I have been using it for a while now with no issues.
Knowing this is for Romley platform means I will likely switch back to the original version.
It does however work perfectly fine for me.
I suggest unless you're a big tinkerer to leave the GBE portion of the ROM alone, and will edit my earlier post to reflect this.

tistou77
10-19-2012, 01:43 AM
Romley Workstation Platform means Xeon Multi-CPU..

useless then, thank you ;)

nikolator
10-19-2012, 02:41 AM
Hi Necrosan,
I got a problem with p9x79 WS (I edited my previous post about updating x79PRO and x79WS).
Maybe because it has 2 LAN chips?
So x79WS with 3101 bios (9/03/12), loaded defaults, just added one change ahci to raid
and what I got from error.log:
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.
and "cmd" screen
12701
Any help?
Thank you in advance and always!

Necrosan
10-19-2012, 04:57 AM
Hi Necrosan,
I got a problem with p9x79 WS (I edited my previous post about updating x79PRO and x79WS).
Maybe because it has 2 LAN chips?
So x79WS with 3101 bios (9/03/12), loaded defaults, just added one change ahci to raid
and what I got from error.log:
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.
and "cmd" screen
12701
Any help?
Thank you in advance and always!

That means that your boards ME is read only it seems.
You could try running it in DOS mode, but I don't think it will help much if it is 'artificially' disabled.

blackwolf
10-19-2012, 05:02 AM
Thank you for your contribution, Necrosan.

nikolator
10-19-2012, 05:55 AM
That means that your boards ME is read only it seems.
You could try running it in DOS mode, but I don't think it will help much if it is 'artificially' disabled.
No, I'm able to upgrade visa versa from original ME 7.1.21.1134 to ME 7.1.52.1176...
the same error with DOS mode...
It's sad...
Is it connected anyhow with "old" September 3101 bios?
Thank you!

Necrosan
10-19-2012, 06:25 AM
No, I'm able to upgrade visa versa from original ME 7.1.21.1134 to ME 7.1.52.1176...
the same error with DOS mode...
It's sad...
Is it connected anyhow with "old" September 3101 bios?
Thank you!

Try this, I made a backup of the 'premodified' ME but with FWUpdLcl64.exe

metest.bin (http://dl.dropbox.com/u/6400726/metest.bin)

Make a backup of your original ME fw just in case with:

FWUpdLcl64 -save oldme.bin

Then flash metest.bin with:

FWUpdLcl64 -F metest.bin

Nodens
10-19-2012, 06:39 AM
nikolator, Necrosan's initital assumption was right. You don't have write access to flash the entire thing. You can flash the update because it does not write to that area.

nikolator
10-19-2012, 01:01 PM
...
Make a backup of your original ME fw just in case with:

FWUpdLcl64 -save oldme.bin

...

Thank you for your time!
But I could not make a backup, the same error. So I decided to give up...

Necrosan
10-19-2012, 01:05 PM
Thank yuo for your time!
But I could not make a backup, the same error. So I decided to give up...

Which tool did you use to update to the latest 7.x ME version? I can try making a backup with that as a last ditch effort for you.

nikolator
10-19-2012, 01:13 PM
nikolator, Necrosan's initital assumption was right. You don't have write access to flash the entire thing. You can flash the update because it does not write to that area.
Thank you!
Is it a special feature of p9x79WS? Asus always makes BIOS changes for it one month later others p9's…
So should I just wait for an official upgrade tool? Or is something wrong with this particular mobo?

nikolator
10-19-2012, 01:32 PM
Which tool did you use to update to the latest 7.x ME version? I can try making a backup with that as a last ditch effort for you.
I used fwudpclc ver 7.1.20.1119 (?, no signature, from station-drivers.com). But it stopped to work after upgrade to 8...
I mean, I upgraded RIVE and p9x79PRO and after that I tried to downgrade back (just for fun) with this tool, but it stopped to work.

Necrosan
10-19-2012, 02:01 PM
To me it sounds like the update you did before locked you out somehow.
The only other possibility is ASUS noticed it was unlocked & locked it in a BIOS update.

Nodens
10-19-2012, 10:28 PM
Necrosan, I was just reading the pdfs in the kit. Did you actualy configure it or was the ME Region option the only thing you changed? I'm asking because many of the default options in the tool don't match the Intel reference design options.

EDIT: Actualy nevermind. I just finished reading the entire thing. And the ME Region options are fine as they are. It's the Flash Descriptor options that need tweaking but we're not flashig the decriptor (which is probably locked anyhow). The image you posted should be great!

By the way the Intel white papers included are an excellent read. And there's a few stuff you can hack with this information.:)

Rassal
10-20-2012, 05:18 AM
Hi,

I read this thread, and i am wondering... what's the utility to flash this MEI? Anyone can tell me really what it will give us more by flashing from V7 to V8?

hsm06
10-20-2012, 09:57 AM
i try it
Necrosan Provided
fptw64 -ME -F ME_81101286_X79.bin
update is completed.
thx Necrosan~

C0sm0s
10-22-2012, 04:50 PM
Flashed the ME and GBe and all went fine.

Now only one problem..

Adapter is now named: Intel(R) 82579V Gigabit Network Connection #2
Just get connection and everything.. only sometimes in windows its displaying their is no internet connection..
But the connection works fine even when it's saying their is no connecion.. can browse/download/etc.

So i wanted to flash the GBe back to the backup i made.
Only now i get an error message..

PMXUtil: Error during PMX Call: idrvdll.dll!DRVInit<>: Failed VerAddVersion<> call
Error 284: Fail to load driver (PCI access for Windows).
Tool needs to run with an adminitrator priviledge account.


Maybe someone knows how 2 fix this problem?
Just doing it exactly when i was flashing to the new version.. that worked without a problem.

Unixsystem
10-22-2012, 05:42 PM
Tool needs to run with an adminitrator priviledge account.


Looks like your answer is right there.

C0sm0s
10-22-2012, 05:58 PM
Looks like your answer is right there.

If you read the story you know i flashed to the new ME and GBe first..
So I know how the tools work..:p
Redownloaded the tools again.. still same problem.

Nodens
10-22-2012, 07:23 PM
One fast way to solve any problem is copy your second UEFI chip to the first(it will fix both ME and GBE to default), then flash only the ME.

C0sm0s
10-22-2012, 08:24 PM
One fast way to solve any problem is copy your second UEFI chip to the first(it will fix both ME and GBE to default), then flash only the ME.

Can't find any info on how about to do that..

Nodens
10-23-2012, 01:16 AM
Not sure if I got you right..you mean you don't know how to copy the second chip to the first?
Switch to your second chip either via the button on the motherboard or the option in the UEFI (check the manual) and then go to the UEFI, at BIOS Flashback menu, select Copy 2 to 1. Switch to 1 again and flash only the ME this time.

R4E3960X
10-23-2012, 08:42 AM
Thank you all buddy here, I've successful update both ME firmware, Gigabit LAN firmware and ME driver already. Special Thank to Necrosan.

Here is my review from Windows 8 Pro sale release.

Intel Management Engine Interface method has change!

http://image.ohozaa.com/i/g20/6YDjXK.jpg (http://image.ohozaa.com/view2/wpu8GPfnG1earL3X)
Long time ago, people don't care about Intel Management Engine Interface because it was the part of Intel AMT and Intel vPro. Many think that useless and not important in term of performance gain by itself. Due Intel always said its only part of security and remote desktop for consult only. But now Intel Management Engine Interface on X79 platform are more than normal utility that they think in the past. It's important tool to working completely with your CPU, PCH and also Gigabit LAN chipset.

http://image.ohozaa.com/i/7b4/noQbPb.jpg (http://image.ohozaa.com/view2/wpubPNytDGXGlq7D)
:o Update Intel ME Firmware to 8.1.0.1286 working extremely well on ASUS RAMPAGE IV EXTREME BIOS 3010 :o

For Windows 8 user here is the solution step by step

1. Download Intel Flash Programming tool for Windows x64 and
1.1 Necrosan file or Station driver file name
: ME_81101286_X79.bin <-- Intel Management Engine firmware 8.1.10.1256 lastest by Intel.
1.2 82579_C0_CPT_B2_VER0OPTD4.BIN <-- Intel 82579V lastest firmware.

2. Creat Directory on your HDD name "MEFLASH" and moving all above file in same location and then.
http://image.ohozaa.com/i/c85/fl8Tbb.JPG (http://image.ohozaa.com/view2/wpuesvNvNd9YWEDk)
Step 1 : Backup your both Intel ME Firmware 7.1.52.1176 and Intel 82579V firmware as picture above.
http://image.ohozaa.com/i/c61/PIEQ4I.JPG (http://image.ohozaa.com/view2/wpuf1BH1RKlU0l23)
Step 2 : Flashing your Intel ME Firmware 8.1.10.1286 as picture above.
http://image.ohozaa.com/i/9df/76Vitt.JPG (http://image.ohozaa.com/view2/wpufmasAjuphUxyi)
Step 3 : Flashing your Intel 82579V Firmware as picture above.

After that use "Shut Down" from Windows 8 setting menu to finish all firmware update process. :o

3. When you've power on your system enter UEFI BIOS in this page you'll get it done!
http://image.ohozaa.com/i/7b4/noQbPb.jpg (http://image.ohozaa.com/view2/wpubPNytDGXGlq7D)
To be ensure that those process above done already check it here!

4. To complete Intel ME 8.1.1.1286 suite installation go to Windows 8 and install this
http://image.ohozaa.com/i/9ed/ca7ZQ6.JPG (http://image.ohozaa.com/view2/wpuh8LPmMAyTuv8P)
More than security and performance gain with completely software and firmware updated

5. Check the version after installed.
http://image.ohozaa.com/i/298/Z7uv6Y.JPG (http://image.ohozaa.com/view2/wpuhDBYHsll2SBqc)
For Intel Management Engine Interface Driver on Windows 8
http://image.ohozaa.com/i/97e/a8otRP.JPG (http://image.ohozaa.com/view2/wpuhRN7YNls8A2Oi)
For Intel 82579V Driver on Windows 8

After I'd complete update all. System working very well no issue found. My system just like flying even not overclock :o

http://www.youtube.com/watch?v=pwe7iImy2mY
Unleash your CPU, PCH and Gb LAN Controller for RIVE with GOD CLOTH Intel ME 8.1.10.1286 today!!!

Rassal
10-23-2012, 12:52 PM
Thanks R4E3960X, i managed to update everything. Nice detailed information.

Nodens
10-23-2012, 02:15 PM
The GBE image is for the Xeon Platform. Flash at your own risk.

Unixsystem
10-23-2012, 03:01 PM
Guys! One important thing about flashing your network card! Add the switch -SAVEMAC, if you don't you will get a new mac address that is not correct.

The only way I found to get it back, is to flash with your backup image, then reflash again with that switch.

Necrosan
10-23-2012, 03:17 PM
Guys! One important thing about flashing your network card! Add the switch -SAVEMAC, if you don't you will get a new mac address that is not correct.

The only way I found to get it back, is to flash with your backup image, then reflash again with that switch.

Very good info!

tistou77
10-24-2012, 08:31 AM
On new RIVE, Asus has already put this firmware ME (8.1.10.1286) :D

aniv
10-24-2012, 08:56 AM
how can we get the new firmware from ASUS for existing RIVE users? Will it be made available as an update later?

I am aware of the unofficial process mentioned in this thread but might as well wait for something through the official channel.

tistou77
10-24-2012, 09:01 AM
I don't know, sorry

aniv
10-24-2012, 09:28 AM
Thank you Neroscan for the ME firmware file :)

Thanks R4E3960X for the detailed instructions. Update ME firmware and installed ME driver as per your instructions. Will wait until I hear from the moderators about the GBe firmware update.

Working great.

Necrosan
10-24-2012, 01:08 PM
Just updated my first post in this thread to include two separate versions for those who want to a version of ME built without the additional Workstation profile features (High-End Desktop version has these features disabled). Flash same as before, both links in the post.

Thanks Nodens for pointing that out!

aniv
10-24-2012, 03:13 PM
I am confused now :\ The firmware image you had posted before : ME_81101286_X79.bin, is it the HE Desktop Version or the WS version?

Nodens
10-24-2012, 04:02 PM
The first image is the Workstation one. RIVE should normaly use the "High End Desktop" one which is the new image Necrosan posted. The difference is that that the Workstation image (which is normaly for Patsburg D version of the PCH) enables some additional features (eg Intel Anti-Theft technology and PAVP). We are unsure if those features work properly if they're just unlocked via the ME firmware, there's a very high chance that they don't--we can't say without further information which is unfortunately not available. So there's the second option of the firmware built that is similar to the RIVE stock one. You can choose what you want to use or have the "stock" one as a fallback if things don't work as expected:)

Juanlo
10-24-2012, 04:39 PM
Guys, you are talking all the time about the RIVE, but I guess it should work the same way on the RIVF, am I right?

Nodens
10-24-2012, 04:53 PM
Yes they're both X79. ME FW is flashable on the Formula as it is.

Juanlo
10-24-2012, 09:16 PM
Any idea why I'm getting this error message? I've opened that DOS prompt with Administrator privileges

12922

Nodens
10-24-2012, 09:46 PM
You are doing several things wrong :p

1) You're trying to use the FWUpd tool which doesn't work in this case.
2) You're trying to flash the 1.5M Production binary image which is not directly flashable but it's used to create a flashable image.
3) Not sure if you even checked Necrosan's post but if you flash with the proper tool and only the -f parameter, you're gonna brick the board:p (you can still recover from secondary UEFI chip though.

Read Necrosan's post carefuly (it's in the first page) and download one of the two images he posted there. Then use the proper tool and parameters as described in his post.

aniv
10-24-2012, 09:51 PM
Nodens thanks for the update regarding difference between the HED and WS version :)

Flashed the HED version posted by Necrosan :cool:

Juanlo
10-24-2012, 09:59 PM
You are doing several things wrong :p

1) You're trying to use the FWUpd tool which doesn't work in this case.
2) You're trying to flash the 1.5M Production binary image which is not directly flashable but it's used to create a flashable image.
3) Not sure if you even checked Necrosan's post but if you flash with the proper tool and only the -f parameter, you're gonna brick the board:p (you can still recover from secondary UEFI chip though.

Read Necrosan's post carefuly (it's in the first page) and download one of the two images he posted there. Then use the proper tool and parameters as described in his post.

Yeah, I read that post, but the Tistou77 method (http://rog.asus.com/forum/showthread.php?24150-Intel-MEI-amp-ME-Version-8.1.10.1300-amp-8.1.10.1286-(driver-and-FW)&p=171387&viewfull=1#post171387) seemed faster and easier, you know, I'm getting older, and lazier :p

I just followed Necrosan's instructions and it worked perfectly, thanks!

Nodens
10-25-2012, 02:59 AM
Heh, always use the option that is most thoroughly documented when it is so intrusive that things can go very wrong :p

nikolator
10-27-2012, 10:34 AM
available official download of new BIOS with this ME upgrade for p9x79WS.

tistou77
10-27-2012, 12:21 PM
I do not know if this is related to the bios, as well as the R4E currently sold (bios 1305) the ME firmware is updated (8.1.10)

nikolator
10-27-2012, 07:36 PM
P9X79 WS Formal BIOS 3209 release
1. Update ME F/W to 8.1.10.1286.
2. Revise the auto rule that system would support secure boot and CSM at the same time.

PS Looks like HED version (w/out 2 services)

Nodens
10-27-2012, 11:55 PM
If I'm not mistaken, there is no Patsburg-D board in existence right now so there's no board built with the "Workstation" station as default. Patsburg-D is what the X79 was supposed to be but it got released as X79 with reduced features from what was announced. This is why PCH features don't work peroperly most likely...there's also a chance that they just left some stuff disabled on purpose for the chipset coming with IB-E...

izajasz
10-30-2012, 02:48 AM
Well , its a bit unfair that p9x79 ws gets newest MEI firmware and 3101 bios for RIVE doesnt contain MEI update ....

EDIT: They changed the LOG at asus.com download site for p9x79 WS . Now the 3209 has only :
"2. Revise the auto rule that system would support secure boot and CSM at the same time."
but nothing about updated firmware for MEI. Did they remove FW update ? Or did they just remove this point from changelog so others wont complain that they didnt got the update ?

nikolator
10-31-2012, 01:16 AM
Well , its a bit unfair that p9x79 ws gets newest MEI firmware and 3101 bios for RIVE doesnt contain MEI update ....

EDIT: They changed the LOG at asus.com download site for p9x79 WS . Now the 3209 has only :
"2. Revise the auto rule that system would support secure boot and CSM at the same time."
but nothing about updated firmware for MEI. Did they remove FW update ? Or did they just remove this point from changelog so others wont complain that they didnt got the update ?
No, they did not remove ME FW for p9x79 WS. And I just tried 3101 on a fresh RIVE with vol. 7 MEI, no upgrade...

Nodens
11-01-2012, 01:06 AM
Yes there is no upgrade on 3101. It was the first thing I checked.

Cyrex
11-11-2012, 10:57 PM
When i try to update my Intel ME Firmware from 7.1.21.1134 to 8.1.10.1286.. i get a
error message.. like this http://www.abload.de/img/fwupdatef0uyx.jpg
Any idear?

R4E3960X
11-12-2012, 11:16 AM
When i try to update my Intel ME Firmware from 7.1.21.1134 to 8.1.10.1286.. i get a
error message.. like this http://www.abload.de/img/fwupdatef0uyx.jpg
Any idear?

Please read this threaded page 6 you'll find the solution. :p

Nodens
11-12-2012, 11:18 AM
Which board are you trying to flash with this? With an educated guess I'd say you're trying to flash a 5M board with the 1.5M image..

Hopper64
11-13-2012, 08:55 PM
Will this FW be automatically updated in a future bios release? Thanks.

GRIP77
11-15-2012, 10:41 AM
Is there any proven benefit in updating these firmwares? (OROM for SATA, FW for NIC's etc)

I'm just like the next guy wanting the latest and greatest versions on all and everything but has anyone actually noticed any improvment at all ? :)

Nodens
11-15-2012, 12:02 PM
Will this FW be automatically updated in a future bios release? Thanks.

Yes at some point. ASUS needs to qualify it for the board first I guess. It will certainly get incorporated prior to IB-E coming out. Some users
have reported though that current boards being sold have it updated which I find strange heh.


Is there any proven benefit in updating these firmwares? (OROM for SATA, FW for NIC's etc)

I'm just like the next guy wanting the latest and greatest versions on all and everything but has anyone actually noticed any improvment at all ? :)

What you are asking is a very generic question. There have been noted performance gains on SATA OROM upgrades. The effects of the ME firmware are subtle and vast so you can't possibly know. NIC FWs etc probably have bug fixes implemented but the one with this version of ME is for the Xeon platform according to the PDF which means there's some kind of fix included for that platform only.

Hopper64
11-15-2012, 12:52 PM
Thanks. I will probably just wait for a new bios.

Cyrex
11-15-2012, 11:20 PM
Which board are you trying to flash with this? With an educated guess I'd say you're trying to flash a 5M board with the 1.5M image..

I just flashed my Rampage without any issues with the tut. on page 6. Now I'm trying to flash my ASRock E9 X79 to a higher ME Version. But without any success :/

1,5M Image and 5M Image failed..

Necrosan
11-15-2012, 11:36 PM
I sent you a message with some instructions on something you can try Cyrex.

Cyrex
11-16-2012, 12:30 AM
With your fw image.

13857

Necrosan
11-16-2012, 04:17 AM
Sounds like that board is locked.
Sorry man.

Nodens
11-16-2012, 11:59 AM
What Necrosan said. You won't update that board until Asrock comes up with an update or you mod a UEFI image yourself (which can be dangerous if the board uses a ME FW that deviates from reference).

tistou77
12-09-2012, 07:05 PM
Hello

Is this someone will fptw64.exe file?
The link from Asrock does not work

I get the file ME8_X79_HED.bin (first page) of Necrosan,
But I miss it .exe to flash the RIVE with firmware 8.1.10.1286 (7.1.52.1176 is now)

Thanks

Necrosan
12-09-2012, 07:55 PM
Hello

Is this someone will fptw64.exe file?
The link from Asrock does not work

I get the file ME8_X79_HED.bin (first page) of Necrosan,
But I miss it .exe to flash the RIVE with firmware 8.1.10.1286 (7.1.52.1176 is now)

Thanks

Here ya go bud: http://dl.dropbox.com/u/6400726/FPT_Windows64.zip
Copy is for Windows64.

tistou77
12-09-2012, 08:05 PM
Thanks so much, I'll try it for my friend ;)

tistou77
12-09-2012, 08:14 PM
It does not work, this message

14776

I put your file ME8_X79_HED.bin (available on the first page and renamed in 1286.bin) in the directory that you set.
An idea?

Thanks

Necrosan
12-09-2012, 08:21 PM
What version of Windows is this?
32 or 64 bit?

If it's a 32 bit copy that last upload won't work for you. (64 bit only)

Try this if it's 32 bit install of Windows: http://dl.dropbox.com/u/6400726/FPT_Windows32.zip

tistou77
12-09-2012, 08:22 PM
it's WIndows 7 64 bit ;)

Necrosan
12-09-2012, 08:31 PM
Something seems wrong with the install of Windows in that case. (The tool cannot detect administrator privileges for whatever reason)
You can try DOS copy of the tool and make DOS boot disk - that is my only suggestion.

DOS Copy of FPT - http://dl.dropbox.com/u/6400726/FPT_DOS.zip

tistou77
12-09-2012, 08:35 PM
Ok thank so much, he tries with DOS ;)

tistou77
12-09-2012, 09:39 PM
Thankso much, it works very well ;)

nikecmh
12-10-2012, 05:47 PM
Where does 82579_C0_CPT_B2_VER0OPTD4.BIN come from?

I can't find it anywhere unless some links are dead.

Necrosan
12-10-2012, 05:57 PM
Where does 82579_C0_CPT_B2_VER0OPTD4.BIN come from?

I can't find it anywhere unless some links are dead.

It is old & outdated (and not technically for this platform) - 1.5 is the most recent and can be updated to by downloading the zip linked at the end of this message and running "gberfl.bat" (Obviously choose the correct version based on whether you're running 32/64 bit, and run as Administrator)

http://dl.dropbox.com/u/6400726/FTK_0.9.1_Windows.zip

nikecmh
12-10-2012, 07:00 PM
It is old & outdated (and not technically for this platform) - 1.5 is the most recent and can be updated to by downloading the zip linked at the end of this message and running "gberfl.bat" (Obviously choose the correct version based on whether you're running 32/64 bit, and run as Administrator)

http://dl.dropbox.com/u/6400726/FTK_0.9.1_Windows.zip

The original ME8_X79_HED.bin is still needed though right?

Necrosan
12-10-2012, 11:12 PM
The original ME8_X79_HED.bin is still needed though right?

I'm not 100% sure on whether the GBE firmware is dependent on MEI firmware. (Although I don't think it is.)
To be on the safe side you may want to update to 8.x before running the GBE update.

I don't know if anyone has tried it on 7.x.

Seth-01
12-11-2012, 10:00 AM
14815

Hi !! i tried to flash MEI firmware with the last 8 version. I thinked all was good but MEInfo give me errors and i can't install the MEI driver because the device is still gone from device manager (look picture attached)

what can i do ??? Thx and sorry for poor english :p

edit : under BIOS in the main tab i can see "ME Version : N/D"

R4E3960X
12-11-2012, 10:17 AM
You must flash ME firmware first. Then install 8.1.20.1336 PV driver from Intel. :p

Seth-01
12-11-2012, 11:16 AM
OK problem solved !! I flashed again my Rampage IV Formula with the same last bios 3204 and the BIOS showed me ME Version 1286 instead of "ME Version : N/D". Then i can flash with the last update 1386 and install driver. All is OK now !

Thanks ! ;)

Rassal
12-11-2012, 04:50 PM
Ok... i managed to get the MEI 1286 installed, but i cannot get 1386 installed, all i get is the ME Version: N/D" in bios... and yellow ! in device manager...

I used my 2nd bios to get back of there... can anyone tell me the procedure exactly (as i am probably a noob) on how to succesfully get 1386 installed using FTK_0.9.1_Windows (i am on windows 8 pro x64)

Here's what i have so far:

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

Intel(R) ME code versions:

BIOS Version: 3301
MEBx Version: Not available
Gbe Version: 1.3 <--- This is what i would like to get to 1.5, as it's latest version
VendorID: 8086
PCH Version: 5
FW Version: 8.1.10.1286 <--- This is also what i would like to upgrade to 8.1.10.1386
UNS Version: 8.1.10.1300
LMS Version: 8.1.10.1300
MEI Driver Version: 8.1.10.1275 <--- I guess i can install the latest driver version once i get FW updated.
Wireless Hardware Version: Not Available
Wireless Driver Version: Not Available

FW Capabilities: 0x00110440

Intel(R) Capability Licensing Service - PRESENT/ENABLED
Intel(R) Dynamic Application Loader - PRESENT/ENABLED

Cryptography Support: Disabled
Last ME reset reason: Power up
Local FWUpdate: Enabled
BIOS Config Lock: Disabled
GbE Config Lock: Disabled
Host Read Access to ME: Enabled
Host Write Access to ME: Enabled
SPI Flash ID #1: EF4017
SPI Flash ID VSCC #1: 20052005
SPI Flash BIOS VSCC: 20052005
BIOS boot State: Post Boot
OEM Id: 00000000-0000-0000-0000-000000000000
Capability Licensing Service: Enabled
OEM Tag: 0x00000000
Localized Language: Unknown
Independent Firmware Recovery: Disabled

Anyone can help me out here?

tistou77
12-11-2012, 06:17 PM
Hello Rassal

How did you manage to get the versions

UNS Version: 8.1.10.1300
LMS Version: 8.1.10.1300

With my RIVE, I did not :confused:

Rassal
12-11-2012, 08:36 PM
Hello Rassal

How did you manage to get the versions

UNS Version: 8.1.10.1300
LMS Version: 8.1.10.1300

With my RIVE, I did not :confused:

Wish i could tell you my friend, i tried so many things to get the latest version of MEI, that i lost track of what i did...

CodeRush
12-11-2012, 09:27 PM
@Rassal, it depends on what you have.
If you have a BIN-file with latest ME update named ME_1.5M_Production.bin or similar, that rename it to me.bin, place in FTK/WinXX folder and run meupdate.bat as Administrator.
If you have BIOS dump or ME dump from another board with update ME, then rename the dump to bios.bin, place in FTK/WinXX folder and run merefl.bat as Administrator. I must warn that there is no checking performed by merefl.bat, so if you have bad ME dump, ME will be lost.
Please read my guide to know more about FTK and use of it. (http://hardforum.com/showthread.php?t=1726429)

Nodens
12-11-2012, 10:55 PM
UNS Version: 8.1.10.1300
LMS Version: 8.1.10.1300

Those are related to AMT, which means you have flashed a ME version that is not for the RIVE. As the RIVE doesn't support AMT and the ME images for it do not carry those.

CodeRush, I didn't know you had an account here:)

nikolator
12-12-2012, 03:17 AM
I just made flashback bios upgrade 3301 (we are so lazy sometimes!)
http://event.asus.com/2012/mb/USB_BIOS_Flashback_GUIDE/
and results:
1. FW MEI 8.1.10.1286 is included
2. it does not matter which FW you had before 7... or 8.1.20.1336, the result FW will be 8.1.10.1286
I think that asus should underline flashback method upgrade in case of new FW MEI...
PS 3203 for p9x79PRO and 3209 p9x79WS - the same results

Nodens
12-12-2012, 03:54 AM
Perhaps that is why these versions have the "renamer" utility packed inside. Unfortunately they lack any documentation. A simple README.TXT inside would work :p Anyhow I'd like someone to try EZ-Flash with 3301 and see if it updates the ME region.

DooRules
12-12-2012, 08:53 AM
It did not update my MEI with EZ=Flash. Still on MEI 7.???

Just tried the FB method, still did not update my MEI FW.

R4E3960X
12-12-2012, 11:53 AM
http://image.ohozaa.com/i/630/B8O0SW.JPG (http://image.ohozaa.com/view2/wvVJZVfcPdx8FKqs)

Lastest ME firmware for X79 was version 8.1.20.1336 and Gbe Firmware version was 1.5. :o

nikolator
12-12-2012, 12:32 PM
Perhaps that is why these versions have the "renamer" utility packed inside. Unfortunately they lack any documentation. A simple README.TXT inside would work :p Anyhow I'd like someone to try EZ-Flash with 3301 and see if it updates the ME region.
It does not work

Nodens
12-12-2012, 03:10 PM
This is rather weird. nikolator reports that flashing through Flashback updated the ME Region but DooRules reports that it did not for his board...VERY strange.

DooRules
12-12-2012, 03:16 PM
I shut down and flashed second bios with EZ to the new bios, no MEI update. Went back to bios 1 as I was before.

This morning I shutdown and went to bios 2, which already had the new bios on it and reflashed with FB method, still no MEI update. I am thinking it should not have mattered that the second bios was already on 3301.

My current MEI FW is 7.1.20.1119

Rassal
12-12-2012, 10:59 PM
Ok Thanks everyone... i managed to get 8.1.20.1336 installed along with GBE 1.5.

Nodens
12-13-2012, 12:36 AM
I shut down and flashed second bios with EZ to the new bios, no MEI update. Went back to bios 1 as I was before.

This morning I shutdown and went to bios 2, which already had the new bios on it and reflashed with FB method, still no MEI update. I am thinking it should not have mattered that the second bios was already on 3301.

My current MEI FW is 7.1.20.1119

How long does the LED flash when you flash it via Flashback? If it flashes fast for a few seconds then it is not flashing at all. If that's not it I'm willing to bet some part of your SPI flash is corrupted..

DooRules
12-13-2012, 12:42 AM
No, it flash's for what seems like 2-3 mins at least, much longer than EZ flash it seems.

Nodens
12-13-2012, 12:52 AM
Then it works like it's supposed to..It won't flash you ME though which means something is wrong with your SPI flash..

Red Jhon
12-13-2012, 10:11 PM
If I use the tool "fptw64.exe" under dos I should be able to update, right? Unfortunately, the 3301 does not update the bios MEI, in my case.

Red Jhon
12-13-2012, 10:15 PM
I can try, under dos:

fpt.exe -ME -F ME8_X79_HED.bin

after the backup, clearly:

fpt.exe -ME -D backup.bin

What do you think Nodens?

If I succeed to update to versione MEI 8.1, with this tool, in case of problem, I can come back to MEI 7.x?

Nodens
12-13-2012, 10:40 PM
Yes that should flash it properly.

Red Jhon
12-13-2012, 10:50 PM
I can downgrade in case of problem to MEI 7.x with this tool?

-------------

MEI 7.x firmware has 1.304Kb dimension, while the firmware 8.1 has dimension 1.524Kb ...
Is this normal?

Necrosan
12-13-2012, 11:19 PM
It should only flash what's necessary - that file is correct.

Red Jhon
12-13-2012, 11:27 PM
The strange thing is that the backup of firmware MEI 7.x with the tool FWUpdLcl.exe, gave as 1.304Kb size, backup of firmware 7.x with fpt.exe gave size 1.524Kb...

Why is that? This is a curious thing.

Red Jhon
12-14-2012, 12:01 AM
is absurd, I tried to flash and it says that the file is identical to what was there.

http://img132.imageshack.us/img132/2329/20121214004955.jpg (http://imageshack.us/photo/my-images/132/20121214004955.jpg/)

Uploaded with ImageShack.us (http://imageshack.us)

After the flash, here's the surprise in the bios .. MEI: N/A

http://img19.imageshack.us/img19/9153/20121214005106.jpg (http://imageshack.us/photo/my-images/19/20121214005106.jpg/)

Uploaded with ImageShack.us (http://imageshack.us)

If I try again, it gives me this screen ...

http://img688.imageshack.us/img688/6421/20121214010500.jpg (http://imageshack.us/photo/my-images/688/20121214010500.jpg/)

Uploaded with ImageShack.us (http://imageshack.us)

possible?

Red Jhon
12-14-2012, 12:42 AM
I state that the flash was done with the system configured and Overclock. I put it back in the bios default settings, and gave me MEI Firmware 8.1 correctly.

Out of curiosity I wanted to re-try the flash, and instead give me all indentical and verified, I checked the file and installed it. However, the first time I've done the flash gave me a very long string of updates and this time made ​​minimal. (A few lines, and then I said it was the same) When you restart gave me back N / A. I made a clear and gave me new MEI 8.01

http://img338.imageshack.us/img338/4404/20121214012741.jpg (http://imageshack.us/photo/my-images/338/20121214012741.jpg/)

Uploaded with ImageShack.us (http://imageshack.us)

What do you say .. everything is ok now? I reconfigured everything and put in OC ..

Necrosan
12-14-2012, 12:57 AM
8.1.20.1336 is the most recent version is linked in the other thread.
You do need to be on the version you're on now to update to it, though.
All looks fine to me. :)


Also - the reason for the size differences is this:

The 1.5MB image is made for FPT

The 1.3MB image is for FWUpd

Please don't use incorrect tool to flash. Follow instructions exactly.

Red Jhon
12-14-2012, 12:59 AM
First problem ... just to stay on topic! After two restarts, after system boot gave me that the network card was not initialized (In Device Manager) and does not work. If i reboot again back to work!

Obviously before I not had this problem ..

Necrosan
12-14-2012, 01:00 AM
First problem ... just to stay on topic! After two restarts, after system boot gave me that the network card was not initialized (In Device Manager) and does not work. If i reboot again back to work!

Obviously before I not had this problem ..

GO in Device Manager and show hidden devices - Uninstall all Intel Gigabit Ethernet 82579 device - reboot.

Red Jhon
12-14-2012, 01:01 AM
I use the MEI driver 8.1.xx1275, if I change the firmware by putting the 1336, I also change the driver?

The firmware is installed always with fpt.exe?

Can you link me the thread?

Red Jhon
12-14-2012, 01:03 AM
GO in Device Manager and show hidden devices - Uninstall all Intel Gigabit Ethernet 82579 device - reboot.

Uninstall and reinstall the drivers?

Necrosan
12-14-2012, 01:03 AM
I use the MEI driver 8.1.xx1275, if I change the firmware by putting the 1336, I also change the driver?

The firmware is installed always with fpt.exe?

Can you link me the thread?

Firmware is independent of drivers almost always. So no, you don't need to change the driver.

Firmware is installed differently depending on the instructions - don't attempt to do this if you aren't 100% sure of what you're doing as you risk potentially ruining your board.

I'll try and dig up the post for you with the other update now.

Necrosan
12-14-2012, 01:04 AM
Uninstall and reinstall the drivers?

Windows is smart enough to reinstall them - you do not need to.

Necrosan
12-14-2012, 01:06 AM
Here is link for the most recent update (8.1.20.1336):

http://rog.asus.com/forum/showthread.php?25842-New-ME-Firmware-8.1.20.1336

Red Jhon
12-14-2012, 01:08 AM
Thanks Necrosan.. but I can flash Firmware using fpt.exe (DOS)? ;)

Necrosan
12-14-2012, 01:12 AM
No.
You will need to use the DOS version of FWUpd.
I told you in previous post what each size image represents.

Red Jhon
12-14-2012, 01:15 AM
Practically sti flash alternate between the tool FWUpd and tool fpt .. You could not use a tool unique to each flash? To put the 1286, I used fpt.

However, I will follow the thread and I will look to do. Thanks a lot

Red Jhon
12-14-2012, 01:39 AM
I uninstall lan driver and reboot my sistem.. after restart I see lan V 82579 # 2 -- Why 2? It's possible reset 2? I want see connection without 2

Necrosan
12-14-2012, 02:00 AM
You clearly are not following my directions.
Re-read my post or google how to show hidden devices in device manager.
Remove the one that is hidden, reboot - move on with life.

Spartanj
12-14-2012, 03:08 AM
Stupid question, I've looked everywhere for fptw64 (Intel Flash Programming Tool) but I can't find it anywhere in any of the files or when I search for it im not finding a place to download it. The link to it on page 2 is dead. Am I missing something simple or perhaps someone has link to it they would share. Thank you.

nikolator
12-14-2012, 09:54 AM
The whole story of my upgrades
RIVE
1. EZ Flash 3010, by FWUpdLcl upgraded FW up to 7.1.52.1176
2. EZ Flash 3101, by fptw64 upgraded FW up to 8.1.10.1286
3. EZ Flash 3204, by FWUpdLcl64 upgraded FW up to 8.1.20.1336
4. Flashback 3301 and FW WAS DOWNGRADED TO 8.1.10.1286
P9x79PRO
1. Ez Flash 3009, by FWUpdLcl upgraded FW up to 7.1.52.1176
2. Ez Flash 3102, by fptw64 upgraded FW up to 8.1.10.1286
3. using FWUpdLcl64 upgraded FW up to 8.1.20.1336
After I saw what happened with RIVE #4 step, I did downgrade FW using backups back to 7.1.52.1176
4. Flashback 3203 and FW UPGRATED TO 8.1.10.1286
P9x79WS
1. Ez Flash 3101 , by FWUpdLcl upgraded FW up to 7.1.52.1176
2. fptw64 does not work (I mentioned that before)
3. EZ Flash 3209 and FW WAS UPGRATED UP TO 8.1.10.1286
4. using FWUpdLcl64 upgraded FW up to 8.1.20.1336
5. Flashback 3209 one more time, AND FW WAS NOT DOWNGRATED, IT’S 8.1.20.1336

Nodens
12-14-2012, 11:04 AM
Necrosan explained it very well. There are 2 formats of ME updates.
One is the format that is pushed as an update. That one is flashed by FWUpdLcl/64. (1.3MB in size for these boards)
The other is the format of region binary image. That one is flashed by fpt/w/64 with -ME -F (1.5MB in size for these boards)

Only use the proper tools. If you can't understand how these things work then you need to follow the directions TO THE LETTER.
Otherwise you risk bricking the board.

Data identical is a verification message. The flashing tool does a verification operation at the end.
PDR Region does not exist message is normal. These boards do not have a PDR region.

DooRules
12-14-2012, 12:18 PM
I have yet to see a step by step procedure for how to do this.

Nodens
12-14-2012, 02:41 PM
I have yet to see a step by step procedure for how to do this.

Weird..cause it's at the first page of this very thread:
http://rog.asus.com/forum/showthread.php?24150-Intel-MEI-amp-ME-Version-8.1.10.1300-amp-8.1.10.1286-(driver-and-FW)&p=171302&viewfull=1#post171302

And the tools for it are included in the package linked in the First post...

Red Jhon
12-14-2012, 08:01 PM
You clearly are not following my directions.
Re-read my post or google how to show hidden devices in device manager.
Remove the one that is hidden, reboot - move on with life.

You have written only to eliminate the driver in Device Manager, which any fool could do it. Also enabling hidden files and deleting them does not solve anything. The letter continues to remain the same. I'm afraid it is you who should read your comment.

nikolator
12-15-2012, 01:48 AM
I uninstall lan driver and reboot my sistem.. after restart I see lan V 82579 # 2 -- Why 2? It's possible reset 2? I want see connection without 2
Hi,
check this, sounds the same problem
http://www.station-drivers.com/forum/viewtopic.php?f=32&t=4150
http://www.station-drivers.com/forum/viewtopic.php?f=32&t=3532&p=13724&hilit=intel+network#p13724
All the best

Necrosan
12-15-2012, 01:55 AM
You have written only to eliminate the driver in Device Manager, which any fool could do it. Also enabling hidden files and deleting them does not solve anything. The letter continues to remain the same. I'm afraid it is you who should read your comment.

First result on Google pertaining to removing hidden duplicate devices in Windows 7 links me to this:

http://social.technet.microsoft.com/Forums/en/w7itprogeneral/thread/6c4a6394-0b01-4ccb-af9b-da172f554796

The provided solution is exactly how to do it. What is hard to understand? I had the EXACT same problem and this fixed it, so you must be doing something incorrectly.

BurrWalnut's solution is the correct one.

(TIp: On WIndows 8 this is unnecessary, as it shows disconnected devices by default.)

Nodens
12-15-2012, 03:58 PM
To further elaborate this happens because the device is enumerated in a different way so windows who "knew" about a lan nic can't see it anymore and instead it sees a new one that doesn't match what it knew so since it has the same exported name, Windows names it #2. It doesn't matter that it happens but if you want to get rid of it, you do what Necrosan posted..

Red Jhon
12-15-2012, 08:02 PM
Hi,
check this, sounds the same problem
http://www.station-drivers.com/forum/viewtopic.php?f=32&t=4150
http://www.station-drivers.com/forum/viewtopic.php?f=32&t=3532&p=13724&hilit=intel+network#p13724
All the best

Thank you so much for these links .. but before updating the firmware I want to be sure it's necessary. I have found a problem with the network card ...

With the generic Windows driver, the card when windows starts, it initializes always, if I install the driver 17.2/17.3/17.4 every now and then to restart the card gives me error. Sometimes in device manager tells me that it works correctly, but still can not negotiate the carrier, sometimes gives me error like malfunzionate. If I use drivers of windows 8 I have no problem.

Under Windows 7, with this driver (17.x) i've not problem.

You recommended to update the firmware to use the latest drivers?


First result on Google pertaining to removing hidden duplicate devices in Windows 7 links me to this:

http://social.technet.microsoft.com/Forums/en/w7itprogeneral/thread/6c4a6394-0b01-4ccb-af9b-da172f554796

The provided solution is exactly how to do it. What is hard to understand? I had the EXACT same problem and this fixed it, so you must be doing something incorrectly.

BurrWalnut's solution is the correct one.

(TIp: On WIndows 8 this is unnecessary, as it shows disconnected devices by default.)

I thank you for your help, but should you be more specific, what are the hidden files to uninstall to fix it? I do not want to see the letter of 2 for my network card.

Can you tell me the specific keys to be deleted? Thanks

phoenix20
08-06-2013, 05:38 PM
Hi all iam new to the rog forum and would like to know how to get passed error 200 i start up fptw get the
press any key 1st.
then again and fptw shuts down with error if any of you could help me get from Intel me 7 to 8 it would be a great help

Pandemie
09-06-2013, 06:42 AM
Hello
Please tell me how to update the "Intel MEI" from the first version to the latest version. When you update the BIOS, "Intel MEI" has not been updated. I've updated all 2 BIOS, but version "Intel MEI" has not changed.
Photo BIOS: http://s1.ipicture.ru/uploads/20130904/ZtTr15n5.jpg
If no trouble, write where and what to download, and in what order to do things.
Thank you.

Delitus
09-07-2013, 12:50 PM
Hello
Please tell me how to update the "Intel MEI" from the first version to the latest version. When you update the BIOS, "Intel MEI" has not been updated. I've updated all 2 BIOS, but version "Intel MEI" has not changed.
Photo BIOS: http://s1.ipicture.ru/uploads/20130904/ZtTr15n5.jpg
If no trouble, write where and what to download, and in what order to do things.
Thank you.

You need to use the USB BIOS Flashback (http://event.asus.com/2012/mb/USB_BIOS_Flashback_GUIDE/) method:

1. Format a USB flash drive as FAT32

2. Download the BIOS you want to flash to. (BIOS 4206 recommended for 3930k)

3. Rename the BIOS file correctly, depending on your motherboard:
- for RIVE motherboard, filename: R4E.CAP
- for RIVE motherboard, filename: R4F.CAP
- for RIVG motherboard, filename: R4G.CAP

4. Copy this file onto the USB flash drive

5. Plug in flash drive into white USB slot at the back of the motherboard

6. Turn off computer, then press-and-hold the ROG Connect button (looks like a chain link) for ~5 seconds

7. Release the button. You should see the button blinking, meaning the firmware is being updated. WAIT until it stops blinking! It should take maybe 5 minutes or less.

8. Turn on your computer. You should see the splash screen appear and a progress indicator showing the flashing process being finalised. The computer may reboot a few times - just be patient. :)

9. When everything is finished, you should be able to access the UEFI menu, and the MEI will be updated to the correct version.

Spach
09-08-2013, 04:21 PM
Nouveau firmware Intel ME (Management Engine) Version 8.1.50.1456 (1.5Mo) pour Z68, Z77, X79....

http://station-drivers.com/index.php/tops-news/122-intel-management-engine-version-8-1-50-1456

Necrosan
09-08-2013, 10:57 PM
Nouveau firmware Intel ME (Management Engine) Version 8.1.50.1456 (1.5Mo) pour Z68, Z77, X79....

http://station-drivers.com/index.php/tops-news/122-intel-management-engine-version-8-1-50-1456

Thanks for updating the thread.
I have installed this version a few days ago to test & all is well for RIVE users.

Zoldjah
04-13-2014, 06:06 PM
FOR TINKERERS ONLY - Don't bother with this information unless you are testing things out. And _ALWAYS_ remember to make backups.


Just tested and you can also update to the latest GBE firmware included in that ME update and it works perfectly fine. (Made for our controller, 82579V)
I compared the original & the new version to make sure they weren't the same, also. (No sense updating if the same)

Not sure how to determine the differences as they both just list as version 1.3 in MEInfo application.

Backup old version first with: fptw64 -GBE -D backupgbe.bin

To update, move 82579_C0_CPT_B2_VER0PTD4.bin (8kb) to same folder as fptw64 and flash like this:
fptw64 -GBE -SAVEMAC -F 82579_C0_CPT_B2_VER0PTD4.bin


Make sure you shutdown after flash as GBE controller won't work until you do

Hello,

has somebody saved this .bin file an is able to upload it.

I have the Code 10 problem and its my last hope.

thanks and sorry for diggin out threads that already rested in peace :)

BOLTS4BREKFAST
04-13-2014, 10:47 PM
Hello,

has somebody saved this .bin file an is able to upload it.

I have the Code 10 problem and its my last hope.

thanks and sorry for diggin out threads that already rested in peace :)

Here is my GBe backup file.. I just made it. I have a RIVE.. 1.3GBe firmware. Hope this helps!
https://drive.google.com/file/d/0B5ALl8wHmmIQS3RkeWJSNFRRV0U/edit?usp=sharing

DualEdge
04-14-2014, 12:15 AM
Okay, I've been looking at this thread for hours now and I think I just need to ask for some help. My OS is Windows 8.1 and I'm trying to update MEI as instructed by Necrosan on the first page using his HED .bin file. Problem is, when I into CMD (Admin) and try to run the .bin file, I get an "Error 201 [fptw64] cannot be run on the current platform. Please contact the vendor" message. I've currently tried to run this in Windows and in DOS (USB bootable) and I get the same message in both locations. My MEI version is currently 7.x (can report this later). ANY help would be greatly appreciated!

Edit: MEI version is currently 7.1.21.1134 if that matters.

BOLTS4BREKFAST
04-14-2014, 01:45 AM
Okay, I've been looking at this thread for hours now and I think I just need to ask for some help. My OS is Windows 8.1 and I'm trying to update MEI as instructed by Necrosan on the first page using his HED .bin file. Problem is, when I into CMD (Admin) and try to run the .bin file, I get an "Error 201 [fptw64] cannot be run on the current platform. Please contact the vendor" message. I've currently tried to run this in Windows and in DOS (USB bootable) and I get the same message in both locations. My MEI version is currently 7.x (can report this later). ANY help would be greatly appreciated!

Edit: MEI version is currently 7.1.21.1134 if that matters.

There are 32-bit and 64-bit versions of fpt... be sure that you're running the one that matches your OS... and also be sure that you're running Command Promt as Administrator.

Gottex
04-14-2014, 06:16 AM
Okay, I've been looking at this thread for hours now and I think I just need to ask for some help. My OS is Windows 8.1 and I'm trying to update MEI as instructed by Necrosan on the first page using his HED .bin file. Problem is, when I into CMD (Admin) and try to run the .bin file, I get an "Error 201 [fptw64] cannot be run on the current platform. Please contact the vendor" message. I've currently tried to run this in Windows and in DOS (USB bootable) and I get the same message in both locations. My MEI version is currently 7.x (can report this later). ANY help would be greatly appreciated!

Edit: MEI version is currently 7.1.21.1134 if that matters.

DualEdge, you have to do the following:

- flash your bios with 4206 or with the latest available using flashback method, do you know how ? here (http://event.asus.com/2012/mb/usb_bios_flashback_guide/)
- after that you'll have FW ver. 8.1.10.1286
- download MEI v8.1.52.1496 (https://www.dropbox.com/s/9gy02xsqlxohjfu/Win64.rar)
- open Command prompt (Admin) and type (file path may differ) cd С:\Win64\FWUpdLcl64.exe -f ME8_1.5M_Production.BIN
- after successful flashing turn off your PC for 5 sec, then turn on and you're good to go

DualEdge
04-14-2014, 09:51 PM
DualEdge, you have to do the following:

- flash your bios with 4206 or with the latest available using flashback method, do you know how ? here (http://event.asus.com/2012/mb/usb_bios_flashback_guide/)
- after that you'll have FW ver. 8.1.10.1286
- download MEI v8.1.52.1496 (https://www.dropbox.com/s/9gy02xsqlxohjfu/Win64.rar)
- open Command prompt (Admin) and type (file path may differ) cd С:\Win64\FWUpdLcl64.exe -f ME8_1.5M_Production.BIN
- after successful flashing turn off your PC for 5 sec, then turn on and you're good to go

Hey, thanks for the info. Just a question before I get started here, is the USB flashback method the same as otherwise just downloading the BIOS from the ASUS website and flashing it? If so, I'm on BIOS 4804 already and I'm still reporting that older MEI version. Again, just trying to make sure I know what to expect here. Thanks!

BOLTS4BREKFAST
04-15-2014, 12:37 AM
Hey, thanks for the info. Just a question before I get started here, is the USB flashback method the same as otherwise just downloading the BIOS from the ASUS website and flashing it? If so, I'm on BIOS 4804 already and I'm still reporting that older MEI version. Again, just trying to make sure I know what to expect here. Thanks!

Flashback method is not the same... Here is the flashback method:
http://event.asus.com/2012/mb/USB_BIOS_Flashback_GUIDE/

DualEdge
04-15-2014, 02:18 AM
Thanks for the help Bolts & Gottex! I was able to successfully upgrade with your assistance and I verified the new version in my BIOS. I never knew the USB Flashback method was any different than a standard motherboard BIOS upgrade, so there's my lesson for the day. Thanks again! :)

zoomee
05-03-2014, 05:34 PM
prob a silly question but here goes lol

Is this still required with the latest BIOS revisions? i.e. 4804

If yes - just out of curiousity why havn't Asus added this to the latest BIOS revision as standard?

Zoldjah
05-04-2014, 01:31 PM
Here is my GBe backup file.. I just made it. I have a RIVE.. 1.3GBe firmware. Hope this helps!
https://drive.google.com/file/d/0B5ALl8wHmmIQS3RkeWJSNFRRV0U/edit?usp=sharing


Thanks for the useful reply, but days before i bricked my board and got a new one (same again)
as replacement.

This was a later launched Version an had already actuall ME and a working GBE Adapter.

Problem solved by money -.-° (and learning what i shoudnt do ^^)

Sergio987
09-25-2018, 01:16 PM
Hello,

has somebody saved this .bin file an is able to upload it.

I have the Code 10 problem and its my last hope.

thanks and sorry for diggin out threads that already rested in peace :)

Sorry to dig up this topic. Yesterday I tried to do the MEI firmware update which in my sabertooth x79 was in version 7.1 and I tried in every way update to 8.1 the problem is that I did not understand and looking in google I found a program called fptw64 I did the nonsense to use without read nothing on. Resolved after using this software with the 8.1 firmware I restarted my computer and the same did not call anymore it was turned on and off without letting me do anything. So I did the flshback to the original 4701 BIOS and the computer was reconnected and to my surprise I had upgraded the MEI to 8.1 in the BIOS. But entering Windows my network card lost its name is no longer recognized as intel. I tried reinstalling the driver and until the drive says it can not find intel network card. And now what can I do to recover my network card?

chevell65
09-25-2018, 03:31 PM
Sorry to dig up this topic. Yesterday I tried to do the MEI firmware update which in my sabertooth x79 was in version 7.1 and I tried in every way update to 8.1 the problem is that I did not understand and looking in google I found a program called fptw64 I did the nonsense to use without read nothing on. Resolved after using this software with the 8.1 firmware I restarted my computer and the same did not call anymore it was turned on and off without letting me do anything. So I did the flshback to the original 4701 BIOS and the computer was reconnected and to my surprise I had upgraded the MEI to 8.1 in the BIOS. But entering Windows my network card lost its name is no longer recognized as intel. I tried reinstalling the driver and until the drive says it can not find intel network card. And now what can I do to recover my network card?

For Windows to see the network card again. Uninstall network driver and shut down system, remove power cord and bleed off power with start button.
Remove network card from PCI slot. Reinstall network card and power system back on, Windows should see network card on reboot, reinstall driver for network card.

Sergio987
09-25-2018, 03:44 PM
For Windows to see the network card again. Uninstall network driver and shut down system, remove power cord and bleed off power with start button.
Remove network card from PCI slot. Reinstall network card and power system back on, Windows should see network card on reboot, reinstall driver for network card.

So I've already removed the driver and left the computer turned off for a long time without power and when trying to reinstall the driver the driver itself says it does not have an intel network card. The network card seems to have lost its identity. My board is onboard the own sabertooth x79 Intel 82579v.