Updating me

Since you are able to dump your whole SPI image, the problem can be fixed. I updated because amt stopped working after update.I used the you asked me for in the ME Analyzer thread, the one i extracted with FWUpd Lcl64 -save After that, i reflash bios with latest bios from gigabyte (f2) from dos, couldn't do from windows.Does it complete successfully or do you see Error 26?If it completes without error 26, attach the file to check the ME region. Even if you tried the latest BIOS from Gigabyte, it has ME 8.1.2.1318 inside.It is under PCH-FW Configuration, Firmware update configuration, ME FW Image reflash (enabled/disabled).I put it on enabled just in case it prevented from bios flashig on windows (not now, I did it before open thread). Just in case, here is the actual output od fptw64 -d

It didn' work so i tried to flash f2 but could't do it from windows. I was getting mad with amt not working, just to realize mac address had changed.

I believe that you updated to 8.1.65 and then encountered this beeping. Download the attached file and use Flash Programming Tool with the command fptw64 -rewrite -me -f ME_F2

At this point a fptw -greset was needed but you ended up flashing something else which caused the other errors you are seeing. When it's completed successfully, use Flash Programming Tool again with the command fptw64 -greset and the system should reset. You can then proceed to update to 8.1.65 firmware via FWUpdate with the command fwupdlcl64 -f ME8_5M_-forcereset. Later f1 and then f2 so I suppose 8.0.1 comes from there. Well, I did it.fptw64 -rewrite and fptw64 -greset went well.

Try to flash that via FWUpd Lcl64 -f ME8_5M_command and reboot.

If it works just fine (no errors at MEInfo, MEManuf), then we know the problem is the older MEBx version. Note: I'd like to point out that your motherboard does not seem to have a way to recover from bricks (dual bios or similar) so keep that in mind. If it goes ok, I think i'm not going to flash it again, fear of a brick.

The "ME FW Image reflash" option enables/disables either the flash descriptor or the ME itself which indeed is what allows you to reflash it easily. Can you try to set this option to Disabled and try again?

[[

It didn' work so i tried to flash f2 but could't do it from windows. I was getting mad with amt not working, just to realize mac address had changed.

I believe that you updated to 8.1.65 and then encountered this beeping. Download the attached file and use Flash Programming Tool with the command fptw64 -rewrite -me -f ME_F2

At this point a fptw -greset was needed but you ended up flashing something else which caused the other errors you are seeing. When it's completed successfully, use Flash Programming Tool again with the command fptw64 -greset and the system should reset. You can then proceed to update to 8.1.65 firmware via FWUpdate with the command fwupdlcl64 -f ME8_5M_-forcereset. Later f1 and then f2 so I suppose 8.0.1 comes from there. Well, I did it.fptw64 -rewrite and fptw64 -greset went well.

Try to flash that via FWUpd Lcl64 -f ME8_5M_command and reboot.

If it works just fine (no errors at MEInfo, MEManuf), then we know the problem is the older MEBx version. Note: I'd like to point out that your motherboard does not seem to have a way to recover from bricks (dual bios or similar) so keep that in mind. If it goes ok, I think i'm not going to flash it again, fear of a brick.

The "ME FW Image reflash" option enables/disables either the flash descriptor or the ME itself which indeed is what allows you to reflash it easily. Can you try to set this option to Disabled and try again?

||

It didn' work so i tried to flash f2 but could't do it from windows. I was getting mad with amt not working, just to realize mac address had changed.I believe that you updated to 8.1.65 and then encountered this beeping. Download the attached file and use Flash Programming Tool with the command fptw64 -rewrite -me -f ME_F2At this point a fptw -greset was needed but you ended up flashing something else which caused the other errors you are seeing. When it's completed successfully, use Flash Programming Tool again with the command fptw64 -greset and the system should reset. You can then proceed to update to 8.1.65 firmware via FWUpdate with the command fwupdlcl64 -f ME8_5M_-forcereset. Later f1 and then f2 so I suppose 8.0.1 comes from there. Well, I did it.fptw64 -rewrite and fptw64 -greset went well.Try to flash that via FWUpd Lcl64 -f ME8_5M_command and reboot.If it works just fine (no errors at MEInfo, MEManuf), then we know the problem is the older MEBx version. Note: I'd like to point out that your motherboard does not seem to have a way to recover from bricks (dual bios or similar) so keep that in mind. If it goes ok, I think i'm not going to flash it again, fear of a brick.The "ME FW Image reflash" option enables/disables either the flash descriptor or the ME itself which indeed is what allows you to reflash it easily. Can you try to set this option to Disabled and try again?

]]

You must have an account to comment. Please register or login here!