Sorry, I did a mistake installing it at the same folder as previous version and I didn't notice, the install package wasn't the same as previous 9.1.20.1035 from Lenovo. My bad.

Is there a point in updating the MEBx firmware after having updated the regular ME firmware? If so, how?

Can I make a small suggestion? When a System Tools package gets updated, maybe the first post should also reflect that, like "Intel ME System Tools vx.x (updated on xx.xx.xxxx) " next to the link. The rest of the links have the version in name, so it easy to know what you have, but the tools are not that easy to inspect.

I say this because some of us may want to have a copy of the tools, so it would be rather easy to check the date and know that you have the last version of the package.

Hi plutomaniac.

I've tried to update my ME FW 7.1.10.1065 to posted 7.1.60.1193 without success. I've used FWUpdLcl 7.1 for DOS. The new image is sent to FW, FW verifies it and FWUpdLcl ends with a bright green "FW update complete, reboot to run the new FW version". Then I've tried by rebooting (as explicitly indicated) as well as by powering off the computer after "success" message from FWUpdLcl.

In both cases (reboot/power off) the PC powers off after a couple of seconds, then powers on and show some Writting/Erasing messages at the top left corner of screen. Then powers off, powers on again and PC booting proceeds normally, except it still displays the same POST message (same for almost 2 years): Running ME FW 7.1.10.1065, backup is 7.1.10.1065.

So its like old ME is rejecting the "received new FW" (according to FWUpdLcl completion message) and restoring old 7.1.10.1065. I've even tried to restore my MoBo BIOS defaults, should my overclock was interfering the ME update process. Didn't make any difference.

After each try I've checked ME with the DOS tools (MEInfo, MEManuf, redumped FW with FWUpdLcl). All dumps are SHA1 matches of my original 7.1.10.1065 (posted a few days ago). Same MEManuf error (SMBus test) always, except after the first update try. MEManuf ended *without* errors (SMBus read ok!). But after subsequent ME FW update attempts, MEManuf reported SMBus test error again (like before trying to update ME FW).

I've not tried to update ME FW from Windows. Will requiere a reboot/power off as well, so I don't see why the result could be different.

@plutomaniac

I've been reading the hanson, CPL0 and lordkag posts. So Asrock harcoded ME FW version 7.1.10.1065 in AMITSE module of my current BIOS (1.10). This module checks for that precise ME version to be the running one. Any other version is not accepted and replaced with the backup, which is 7.1.10.1065.

Two approaches to this limitation:

a) Include the new ME FW (customized to system according to old ME FW in BIOS) in the BIOS FW *and* patch AMITSE module so it is harcoded to the ME FW version -> Approach tested working by Hanson
b) (I like this more) Patch AMITSE module in BIOS to bypass/ignore the ME FW version check code that causes the backup reflash. This approach does not require the new (and customized) ME FW in the BIOS and allows for FWUpdLcl usage -> lorkag provided the patched AMITSE module to hanson for him to replace in the original BIOS, but hanson didn't report back (or I cannot find the post).

I will not worry about current ME 7.1 issues then, now that I know the reasons (except this SMBus test fail, that I've passed at least 1 time). However it would be interesting to check if AMITSE module in 2.30/2.31a BIOS (I've yet to decide if going to use the beta) is harcoded to 8.0.2.1410/8.1.0.1248 ME version resp. in advance.

EDIT: My ME FW 7.1.10.1065 dump from FWUpdLcl matches the image contained in the package linked in this post by iceman. Thanks for your wise guidelines so far plutomaniac. I'm still wrapping up, because I will update my BIOS and reinstall my OS and stuff into new HDDs.

Hi plutomaniac,
I try to update the firmware ME v.7.1.60.1193 on a laptop Sony VPCEJ2L1E , but "FWUpdLcl" command is not recognized? I use a 64bit system.
I think that's why it does not work. Is is possible to do this update?

Regards,
Div.

But the tool FWUpdLcl64 is not present in the v.7.1.60.1193 pack?

Ok. Well apparently I try with FWUpdLcl or 64 of the tool ME8, it does not work. This Sony is reluctant to this update, Lol.

I use well these tools.

I get the following error: Error 8716: Invalid usage

edit: If I add the command extensions .exe and .bin, I error : 8714

current system "Win. 7 64"