Successfully updated the BIOS for my Maximus Hero X (not the first time), however, I've run into an issue with the beta BIOS update (2.00) released by ASRock for my old Z77 (Extreme9) board.

The scanning starts and stops at this point:

[OROM - Find and Extract]
VBIOS in GUID A062CF1F-8473-4AA3-8793-600BC4FFE9A8
OROM in GUID A062CF1F-8473-4AA3-8793-600BC4FFE9A8

Now, it's been some time since I've used UBU to update the BIOS on my Z77 but I'm sure it worked in the past.

What am I missing?

[Edit] I'm using UBU v1.70.rc18.5

[Update] Nevermind. I worked it out. Had to roll back to MMTool 5.0.0.7

[Update] No. Spoke too soon. That didn't work either: parseFile: invalid data checksum 5Ah, should be AAh when updating

@devoidx360 - try with 4.50.0.23, this is Aptio 4 BIOS - never mind, I checked BIOS with UEFITool and that error is in stock BIOS too, so you can ignore

Still no luck with the update. I tried rolling back to an earlier version of MMTool and receive the same checksum errors. :-(

Any thoughts folks?

@devoidx360 - sorry, I must not have explained very well, using 4.50 or 5.0.0.7 you mentioned you can go ahead with your mods, that checksum error is present in the stock BIOS from Asus, so you can ignore that warning and proceed with the mod

Awesome! Thanks. :-D

Zitat von westlake im Beitrag #4662

---

Things...

---

Already try but failed...
Can anybody help for the Rampage IV Extreme X79 latest version BIOS (Driver & NVME)
Thanks a lot!!

@TBone
This part is not for questions but until it erases by Fernando, I can help you.

I have that motherboard at our summer house at Manavgat/Antalya/Turkey. This summer I have updated it to latest microcode of 42D by using UBU. But, with the updated bios it crashed. Somehow the insertion with USU doesn't work for it. (I have removed the bios chip, programmed with UBU by using CH341A external USB programmer.)

Then I see that, manual insertion with MMTool successfully replaced old bios files with new ones.

First extract your current microcodes. Find the old and new ones. How? Use the UBU program but note, which are old and which are not. For new ones, goto https://github.com/platomav/CPUMicrocodes download the package. Look in it, and prepare new ones for replacement.

Obtain MMTool MMTool_v5.0.0.7 search internet how to do that replacement with it. (You may already know that, I don't want to write in detail.) You should not have to copy the first two 5 times, you can copy two times for the first two microcodes, but then use 5 copies after the first two.

I also realized that, there are 2 updates for Asmedia Raid controller update. Here choose not the newest one. Because the newest file includes initialization screen, delays booting time a lot, but if you wish you can use it as well. (Personally I programmed 2 bios chips with both versions, but using the older one at normal boot.)

Another addition is for NVMe insertion. You can use NvmExpressDxe_4.ffs it works for identifying NVMe based M.2 cards by using an adapter. I have tested with Asus x4 Mini adapter, works fine. (At boot "PATA SS" it says, identified my Samsung 970 Pro 512GB, there is nothing needs else for booting Windows 7 and Windows 10.)

If those explanations look too hard for your knowledge, ask me via personal mail. I can post you my bios image if you wish. But, as I said, I have used an external programmer. I did not do it from Asus bios flashing screen at bios.

@SoniX

Display bios version possible in scanning screen with other MB info ?
to confirm/verify what version you are modding

Thanks

@biozzz

Give an example.

@SoniX

Display bios version possible in scanning screen with other MB info
to confirm/verify what version you are modding.

Would also be usefull when a bios file name is incorrectly versioned
or does not indicate version no.


Scanning BIOS. Please wait...
Define BIOS platform - AMI Aptio V
Manufacturer - ASUSTek COMPUTER INC.
Model - ROG-RAMPAGE-VI-EXTREME
Bios Version - 1503


Thanks

@biozzz

Perhaps, but not for all BIOS. Also, there will not always be a correct display of the BIOS version.