Zitat von dygkset im Beitrag #890

---

asrock x79 bios locked..
so user can not update intel management firmware.

and lordkag post how to do unlock it..

is i read that post and i upload my patched bios file..
for someone use same model...

---

Zitat von dygkset im Beitrag #893

---

in stock asrock bios check me version every boot. compare 'ME region' whit 'back up of ME firmware' in bios region
if there is diffence of version exist. then bios rewrite ME region...

so update me firmware using FWUpdate, after reboot bios automatically rollback the ME firmware.

---

Update:

Yes, I was right guys. For Intel 5-series 5MB ME images (8MB SPI size) there are two SKUs: Desktop (DT) and Mobile (MB). Previously I thought MB meant MegaBytes but that's a wrong assumption.

Up until now I was giving only the mobile SKU for 5MB ME6 named: PCH_8M_MB_UPD_Production
From now on I will add the desktop SKU for 5MB ME6 named: PCH_8M_DT_UPD_Production



Now, since OEMs used (& use) to rename the binaries I need to check the $SKU to identify them. It seems to slightly change from binary to binary but I figured it out (maybe @lordkag disagrees? - LINK):

03 00 00 00 77 FC 6E 00 --> Desktop
03 00 00 00 77 FC EE 00 --> Mobile

03 00 00 00 77 DC 6E 00 --> v6.x
03 00 00 00 77 FC 6E 00 --> v6.0

Now, based on the binaries I have found and if I am correct, the latest Desktop (DT) ME6 5MB firmware is v6.2.50.1062 from an HP package. The "latest" definitely Desktop firmware (based on the file's name) is v6.0.40.1215 and it's the file I have given to grml4d HERE.

So, @grml4d (once your internet is stable, no worries in the meantime) let me know if the one I gave you works. If it does, I'll give you the (almost latest) v6.2.50.1062 firmware to try which I suspect is for Desktop (DT) models as well.

I updated my previous findings and I am now certain of what ME6 5MB SKU is for Desktop and for Mobile. Once it's verified, I will add it to the main post.

@ grml4d:

Since you unfortunately (I've been there) have slow internet and probably limited data, I have attached for you another file. Please test this one, not the previous one. If everything goes properly, this should update your HM57 machine from ME v6.0.31.1208 to v6.2.50.1062.

@ grml4d:

Well yes, normally you need the MB firmware as it's a mobile platform. I don't know why the latest MB v6.2.60.1066 firmware we have here (from Lenovo) is not working for your mobile system. It should. The finding that there is also a desktop firmware was coincidental but I asked you to try it just in case.

Without a look at your current firmware I cannot make any more progress really. Go to Flash Programming Tool and run fptw -d ME.bin -ME. Does it say Error 26? If yes, we cannot take a peak at your ME region unfortunately.

@ lordkag:

Thanks for looking into it. What do you mean by "third byte of the SKU"? FC or DC? This definitely has to do with whether it's v6.0 or v6.1/v6.2. I don't see how that could determine a firmware as coming from a wrong SKU.

Either way, the last MB v6.0 is v6.0.41.1216. I don't think it will make any difference for grml4d but he can try it. I have attached it below.

As I said earlier 5-series was a total mess, everything became a lot simple after 6-series. HM57 could probably accommodate either a 1.5MB ME (4MB SPI flash) or a 5MB ME (8MB SPI flash).



But we still don't know whether you have a 1.5MB or 5MB ME firmware image. We can find that by checking your motherboard's SPI flash size. If it's 4MB -> 1.5MB SKU otherwise if it's 8MB -> 5MB SKU. An easy way to determine that is by running FPTw -d x.bin. For example on my 6-series system I can see that:



To continue and not go blind it's important to know whether you have an 1.5MB or 5MB ME image first. If fpt shows these weird errors (other than error 26), can you run MEManuf to check if everything is ok with the ME?

So if I understand what you are saying properly, your opinion is that 6.1 is for different SKUs than 6.0? Meaning that for example an FC 6E machine can only update to a latter FC 6E firmware? This has never happened at all the previous or following ME firmware versions (4,5,7,8 etc).

Other than that, indeed it doesn't make sense to have the ME major version version at the $SKU for me as well. For good measure, before posting those results for the different 5MB SKUs, I downloaded all the firmware from Lenovo (6.0.31 up to 6.2.60) and checked the $SKU. All of them were EE (makes sense, mobile) and 11/13 were DC (v6.x) with only the remaining two being FC (v6.0.31 & 6.0.41). So my theory makes perfect sense fact-wise.

What Lenovo means by "added support for xxx model" I do not know exactly. It's not like you can set something "laptop-specific" via FITC (only platform specific) so my guess so far has been that this means "users of this xxx model will from now on be able to download the ME firmware from it's support page".