Hi mates, I need your help because I want to update the CPU microcode for the ASUS M5A88-V EVO, it´s BIOS is an AMI BIOS (non-UEFI BIOS) and its lastest version is 1801 from 2013, I've updated the LAN, AHCI and RAID ROMs without problems, but I don't kmow how to update the CPU microcode.

I know which are the microcodes that I've to update (mc extractor tool used) but I don't know how to do it, because there isn't a tutorial for AMD AMI non-UEFI bios, can you help me people???

Thank you so much, kind regards.

@RaskaipikaFWR -
Here's an excellent tutorial on CPU microcode updating/modding using the non-UEFI AMI BIOS MMtool ... http://wp.xin.at/archives/tag/microdecode

I agree, we need a guide for AMD microcode updating UEFI and Non-UEFI Same! Even a short guide on how AMD microcodes are named vs what's detected in a BIOS by MC Extrator vs available microcodes on the github repository would be helpful too!

I can edit manually by hex, or MMTool hex combo but I guide on the actual codes would be great to find.

Sometimes I compare CPUID of known compatible CPU per motherboard QVL List vs BIOS and what's shown as included microcodes by MC Extractor and the names look nothing alike, and nothing like what is shown at repository.
Sometimes I even see all names look similar, but for example (made up) CPUID is 000F25. I know this CPU is compatible, QVL says so, check BIOS many similar microcodes shown in recognizable name style but only 000F24 and 000F26 along with many others is listed by MC Extractor but 000F25 missing.
When that happens, how is CPUID 000F25 compatible? AMD microcode is very confusing due to this, I can edit and update, but a guide on all that would be a great!

@RaskaipikaFWR - attached is modified 1801 BIOS - Microcodes update only (All done via hex insertion manually)

@Lot Lost_N_BIOS, how did you do it???, because yesterday, I tried to make the same (Hex insertion) and NO SUCCESS, I like do the things by myself, to learn mainly, and of course, thanks, I will try it in few time and I will comment about the result.

@Lost_N_BIOS I've tested your BIOS and the result is the same, EZ 2 Flash says: "The BIOS is corrupted or damaged", at this point, I don't know what I can do to make the update, umm.

I just saw your comment about integrity check, you may get that when trying to flash this too, not sure?
I used HxD too, copy all on each old code, then search via hex byte on BIOS using "Find All" so it highlights the entire old code, then open new code copy all and back to BIOS right click on highlighted old code and hit paste.

You may need to use one of the methods outlined in these threads to flash modified BIOS
[Guide] How to flash a modded AMI UEFI BIOS
[Guide] Flashing modified AMI Aptio UEFI using AFU

Zitat von Lost_N_BIOS im Beitrag #6

---

I just saw your comment about integrity check, you may get that when trying to flash this too, not sure?
I used HxD too, copy all on each old code, then search via hex byte on BIOS using "Find All" so it highlights the entire old code, then open new code copy all and back to BIOS right click on highlighted old code and hit paste.

You may need to use one of the methods outlined in these threads to flash modified BIOS
[Guide] How to flash a modded AMI UEFI BIOS
[Guide] Flashing modified AMI Aptio UEFI using AFU

---

Edited out old post, I thought you said BIOS was not AMI

So what, AFU does not work for this BIOS, probably only due to those are new versions? Here, attached is 3x AFU ES versions and 1x older AFU for your specific AMI BIOS type (BIOS8).
With the ES versions, use /GAN as last switch, but try the BIOS8 version first (/GAN may or may not work on the BIOS8 version, but you can try)

AFUDOS BIOSFilename.bin /P /B /K /GAN

No matter what you do, make a backup first before flashing, so later you can modify back in your board's serial number, UUID and DTS key, along with LAN MAC address too.
AFUDOS biosbackup.bin /O

@Lost_N_BIOS, I've made a little progress, I've found that in the E2 Dynamic Module, there are the Microcodes Updates, I'm using MMTool v3.26, I've extracted that module (E2) and I've made a hex edit, then, I've replaced the module in MMTool and then save ROM BIOS.

I've been able to flash the BIOS, but when the process finish, the ASUS Crashfree BIOS 3 program popups in the screen, the BIOS isn't good but I think that I'm in the right way, maybe, I've to edit other thing or reference for the new microcode too, I don't know.

Good find, and thanks for posting info, I will look at that way next too for you.
I also came back here to say I think I found issue with hex method way we did originally, I'm checking something now and changing, will post back with info and new BIOS to try in a few

I've made another discover, maybe and only maybe, the problem is the way that the program replace the module, because, I've extracted again the E2 module and without edit it, I've replace the module in the BIOS and the result is the same, the CrashFree BIOS 3 program popups in the screen when the update finish.

I've made a screenshot to see the changes made by the program, and the results are here:



The program changes the "RomLoc" field, at this moment, the E2 module isn't the second in the list, is the fifth or sixth in the list, the size of the module and its size in the ROM are the same, but like I said above, its "Romloc" is different.

Other test that I've made, is replace the AHCI option ROM, and here the situation changes, the RomLoc is the same but the sizes (rom's size itself and its size in the BIOS) are different, it's logical because I'm replacing the original version with and updated version.

Good catch, your eyes are open! I thought I had my eye on something in hex, but no luck. I'm now looking at this method you are using too, and comparing before/after insertions.
I think finding the right MMTool is key, I have many version so plan to send you several files to try once I check a few versions out to see which differ and how compared to the original BOS.

Keep in mind, when thinking of size changes, all the microcode updates are same size as the old ones, so I don't think anything should change in size.

3.12 same change, E2 is moved to location 5
3.19 "" ""
3.22 "" ""

All same! I tried adding location in the offset and segment, both then give vendor ID error or something like that.

I think I got it! Try attached file now @RaskaipikaFWR

I found AMITool always gave error when that E2 module moved, error was unable to extract 1B module (which is single link arch BIOS). So I did mod via hex, hex editing in the modified E2 file, then extracted 1B Single Link Arch BIOS from original and replaced in modified BIOS with MMTool.
I was using MMTool 3.22 then, but I don't think it matters. Key here was replacing ED module via hex overwrite, then copy in 1B via MMTool from original BIOS into edited BIOS. At least I think that may be the key, if it only flashes properly, no errors and no E2 move though when doing this!

Unfortunately, this doesn't work too, again CFB3 popups, but ey, I will find the method to update the microcodes, I hope.

Damn! I will keep on this with you, hopefully we can eventually solve this! There is a way, we just have to find it

How about this one, corrected a single bit checksum (if works will give tool) Too bad AMITool does not work like PhoenixTool, and allow you to edit modules before/during it's work, then we could use it in that manner but ignore or uncheck all SLIC settings.
I found this in AMITool PDF, probably some of the source of our issues

Zitat

---

Repair AMIMMWIN damage - AMIMMWIN can damage the resulting image in a number of ways (overwrite initial bytes (ie. ASUSTEK string), damage module 80h, invalidate main BIOS checksum, damage Extended Bootblock).
Preserve boot block - Both AMIMMWIN and MMTool alter the bootblock. This option copies the bootblock and extended bootblock (if present) in entirety from the original image.

---

Looking into using these options without that tool, so we aren't messing with SLIC and can still do the microcode updates.

@Lost_N_BIOS:

No luck mate, corrupted or damaged file, , but you're the man mate, thanks for your help.