I’m trying to put together all updates available (microcode, NVME module, Intel ME, SATA module, ReBAR, etc.) into a BIOS created from the latest available one on the ASUS website (v4801). As a beginning I’ve used the already modded one posted here that already has the updated Intel ME (8.1.70.1590).
I’ve flashed the BIOS and it works almost fine after I’ve replaced the NvmExpressDxe_4 module with NvmExpressDxe_5. I’ve also ReBAR working without issues (and Above 4G patched to be enabled when the optimal settings are being loaded from the BIOS screen). But the last step I need is to have Intel ME working, because right now it’s displayed as N/A into the BIOS info screen. With ME Analyzer I’ve noticed that my BIOS have this info:
So the BIOS region has the 8.1.70.1590 version but it’s of type Region, Extracted. But in Flash Image Tool is reported the original and old 8.1.51.1471 version. So I believe (please, correct me if I’m wrong) that the final step that I need is to flash the 8.1.70.1590 into the Intel ME chip. And this is the point were I’m lost because it’s a total mess.
Using the tool MEinfo from Windows I get this result:
Intel(R) MEInfo Version: 8.1.56.1541
Copyright(C) 2005 - 2014, Intel Corporation. All rights reserved.
PMXUtil: Error during PMX Call: idrvdll.dll!IDRVInstallDriver(): Failed to start loaded service err: -2146762484
Error 9470: Fail to load driver (PCI access for Windows)
Tool needs to run with an administrator privilege account.
But the CMD window I’m using is already as admin.
And also I’ve the file 8.1.70.1590_1.5MB_PRD_RGN.bin (downloaded here) that I believe that it’s the right one that I need to put into the Intel ME chip. Am I wrong? Is this right? What do I do next?
It’s very very hard for me to follow the guides because they uses a lot of acronyms. From this guide Intel (Conv.Sec.) Management Engine: Drivers, Firmware and Tools (2-15) I’ve understood that there is a difference between the extracted state and the original OEM. But it’s a bit unclear about what happens when I’m already using a BIOS that has a extracted Intel ME as in my case (see the image in my post). I don’t know if I need to replace something into my currently working BIOS or not (as I’ve said all is working, including the overclock, and also ReBAR and NVME). Also it’s not very clear to my understanding if I only need to flash the Intel ME chip with this file: 8.1.70.1590_1.5MB_PRD_RGN.bin (this is the one wich match exactly with my current BIOS but there is not any other with _EXTR into the name).
So, AFAIK, very basic, there are two chips: one is the BIOS and the other is the Intel ME. Do I need to flash only the second one, the Intel ME? If not, what else do I need to do with my BIOS?
So I need help for dumbs. I don’t need to upgrade the Intel ME because the BIOS I have already has it updated. So, What else do I need to do?
I suppose that there are two different things: one is the module or the region into the BIOS to talk with the Intel ME and the other one is the contents of the Intel ME chip itself. I believe that this file → 8.1.70.1590_1.5MB_PRD_RGN.bin is the raw binary content needed to be burned into the Intel ME. Isn’t it? If so, Why it is not as simple as using a tool like the one used for the BIOS? There is no way to just burn the file and forget it?
I understand that those guides are for general purpose, as there is information for many versions, motherboards and different chipsets. But all of this make them even more obscure. If you can just download a BIOS and flash it to the comp, why there is no the same or similar procedure for Intel ME. There is tools for other motherboards where you can only download the files from the manufacturer and run. But unfortunately there is not for my motherboard.
For the record, if you are talking about the pad-raw-pad-raw structure in UEFITool (I’m not sure if this is that you want to mean with “misteps in bios”) I’ve verified it and it seems to be right. It was very hard to get it working with the needed patches for the ReBarDxe module, but I have finally working (don’t ask how, because now I don’t remember it, so If I need to do it again it could be impossible ). But if there is anyone who need it I can share mine here.
Wrong…theres only one IC SPI bios, the ME FW is a partition/region on the bios, in these mb generations. No research done from the user side… lead to act as “dumb”.
The guide on 2nd link was shared, due to… “because right now it’s displayed as N/A into the BIOS info screen”
ME FW NA in bios, still is correclty identified in MEA or UEFI tool viewing dumps/bios regions…but still is corrupted, besides using latest version avaiable …1590.
Final note… the guides served thousands of users with sucess, some of the guides require a certain degree of user knowlodge, it only needs reading and learning. Users who dont have capabilities or time for it, should consult an IT Tech/Service.
Thanks MeatWar. I was wrong then. So it’s a great advance now to know were was my mistake. I believed that there was two independent chips.
So my issue is only that the BIOS I have was created with a wrong method because the ME Region is already extracted. If I’m not wrong now I must put a non extracted region inside and wait for it to work. The problem in my case is that MEinject (also called ME Cleaner in some versions or guides) doesn’t find any suitable replacement into the repository. May be it’s due to the old 8.1 version? It happens even with the original BIOS downloaded from the ASUS website. The ME Inject sees the info inside but then there is no any data into the dropdown list to select. There is another different tool to replace the ME Region? I’ve tried with UEFITool with no success (after the replacement with the original region from the untouched original ASUS BIOS it stills displays N/A into the BIOS). I’m also trying with Flash Image Tool (inside the “Intel ME System Tools v8 r3” package) but the problem is that I don’t know how to come back to the CAP format after extracting the BIN from the capsule. How can I put the BIN into CAP again?
I have time for it, that’s why I’m trying to learn. I’m not specialist in BIOS structure matters. That’s why I’m asking here, in this forum.
The guide exists because there’s no other way to fix it, unless a full SPI programming with a fully functional image, with a programmer, so mods aside, your primary goal is to fix the ME FW NA.
After fixed it can be upgraded to latest, in this case none cause updates have stoped in 1590.
We dont support any hack tools like ME Cleaner or similar, every guide and files here on the forum are intended for original work and operations by Intel methods/tools or shared internal developed tools from users.
Initialized/configured ME FW images shouldnt be swaped in regions, only re-initialized/own system images.
CAP files have an 0x800/0x1000 db header, removing this header or extracting the Intel_inage from an Asus CAP file, with UEFI tool NE “extract as”, save as bin/rom.
HEX editor can merge back the content to an origianl CAP file making it again valid security.
CAP files cannot be used in programmers
End of lesson and consider yourself a lucky user, i hate lazzy people than cant search and read/learn, being all this in the forum.
SO NOW its really OVER_N_OUT…of here.
That’s great because I also hate that kind of persons. I’m trying to solve my issue more than a month, watching videos and also reading threads here, but unfortunately without any luck.
Any case, If you don’t like to participate into the forum threads to exchange experiences with other people, may be you could be more comfortable writing guides or in other kind of activity. I can understand you with no issues because I was systems engineer and software architect for many years.
So, you do know how hard is to pass a professional experience to a common user or to someone “out of his league” and for sure you can imagine how repeating this can be…in a forum and as free info, not counting with the time lost to other activities/family etc…im glad you understand and no ranks to pull here sir.
PS: In a near future i do pretend to engage ant farming/grasshopper and maybe a bit of manure export…ww of course, stay tunned, cheers.
Of course I can understand it, without any hassle. That’s why I suggested what I said before.
In my case I’m doing my research more by pure curiosity and as a matter of study, to learn something that was in some manner outside of my traditional area of speciality. I like to learn how are functioning the low level systems of the computers, in this case, the BIOS.
I know perfectly the great complexity and the difficulties for non specialists, mainly due to what I said before, the large number of standards, acronyms, specs, etc.
But also I thought that the same that I’m doing this in my spare time it could be helpful for other users of the same mainboard than mine, to have something like a new-modded-unnoficial release of the BIOS to give to their setups a second chance, a new life. That’s why I started the task of joining all the new features available that it’s possible to add the the latest released BIOS by ASUS. This was a really good mainboard and it works really well after the years.
). But if there is anyone who need it I can share mine here.