@Fernando
OK, I understand. Maybe it’s better this way - the packed archive is only 173MB so you can download it quickly. 6GB would be a long download.
I swapped my beloved GA-Z97X SLI rev 1.2 for a crappy ROG motherboard, simply because the GA couldn’t boot even a live usb of Arch linux. People at RMA got it to work, so eventually I sold it, no need to invest time fixing things.
The latest bios (2018 release) is even more outdated than the Gigabyte bios (2016) in terms of intel vbios, RST and ethernet firmware. I proceded to update everything like usual and flashed it using the usb backup flash method.
All is fine except that overclocking is quite broken. Overclock doesn’t apply inside the bios (everything is reported at stock speeds), but CPU overclock does work. Ram overclock on the other hand doesn’t. Ram timing is set to 9-9-9-24, speed at 1333MHz and voltage to 1.35v (since I have two low voltage sticks and two 1.5v sticks). Ram oc settings are totally ignored.
I reverted to the original bios and I can only think that a microcode update patched some potential expoloits which break functionality of the bios.
If anyone could take a look at it, would be appereciated.
I might try and update everything except microcode and try again.
DrvVer v0.29.0 out/ Changes for Intel RST. Now displayed as:
EFI Intel RST RAID Driver - x.x.x.x
or
EFI Intel RST VMD Driver - x.x.x.x
@westlake
As a temp solution:
Replacing UEFIFind.exe & UEFIExtract.exe by A51 (last "non-shrinked") version solves the "hang" issue with that BIOS image.
Hi, when trying to updated the Raid Orom and the EFI drivers for the Huananzhi T8 Bios I get the following result:
See the images (Before the update and after)
Practically I get 2 entries for the “EFI sSata Drivers” (one with the old version and one with the new).
Instead only one entry should have been there for “EFI sSata Drivers” the other one should have been for "EFI Sata Drivers"
For making the update I’ve used the “RAID ROM module v5.5.5.1005” and the “EFI RaidDriver_v5.5.5.1005” from this forum (as the motherboards has a C612 chipset)
Can somebody please help me figure it out what went wrong here?
Not sure if there is a problem with the UBU or if I did something wrong.
I would be grateful if anybody can proper update this Bios file for me. Here is the original Bios file used.
bios.rar (3.61 MB)
@codehunter , maybe naming problem? I don’t know. Here is the updated BIOS file. But the microcode update is tricky.
@SoniX , any idea? I tried "all" the MMTool versions, but nothing. 
BIOS.rar (3.87 MB)
@westlake , thank you so much for taking the time and effort!
Log-term, it would be nice if the UBU tool will be able to recognize and update properly the microcode (the same happens when v.6 of the OROM/EFI drivers are being used).
Perhaps yeah, there is something that need to be adjusted in respect to the naming…
EFI AMD GOP Driver - 2.18.0.17.10 (>2.17.1.17.10)
OROM VBIOS Barcelo - 017.010.000.029.000000 (new item)
OROM VBIOS Lucienne - 017.010.000.029.000000 (new item)
So many new stuff, we need updated UBU. 
(But wait for the new microcode database. 30+ new item.)
amd.rar (76.3 KB)
Hi,
i have mid update UBU with the DB r205 which offers a new code for my cpuid 906E9, but i have this error message?
"mCode FFS: parseFile: non-empty pad-file contents will be destroyed after volume modifications
No replacements can be applied to input file "
or can I find the .bin file for the 906E9 cpuid?
Thank you
@Div You can find the latest Microcode here https://github.com/platomav/CPUMicrocodes and here Intel, AMD, VIA & Freescale CPU Microcode Repositories Discussion
If you want old Microcode, you can find it [OFFER] Intel CPU Microcode Archives
This links if I’m not mistaken updates "OROM Intel RST for SATA" goes to Files\intel\RST, what about "EFI Intel RST for SATA"?
Both files in same folder, EFI driver and OROM.
README.TXT
# Only IRST files should be located in this folder.
# RaidOrom.bin DevID 2822/282a
# RaidDriver.efi
RaidDriver.efi
RaidOrom.bin
@westlake Do you happen to have an efirom version of this GOP driver, so it can be used with GOPupd?
I noticed that bringing in any change on the ROG Maximus VII Ranger bios breaks RAM overclocking.
I first tried to update everything (that moment when a 2018 bios from Asus on a top end motherboard has older firmwares than a 2016 bios from Gigabyte), then tried everything without the CPU microcode and last I tried to update only the RST.
The RAM speed is then stuck at 1333MHz, even though 2133MHz is selected. The rest seems to be working fine.
I hope someone has a workaround for this issue.
Preferrably I would like to know if it’s possible to get 1080p output support over a GPU attached to the PCIe port. Iirc, it currently only has 1280x960 stretched and it looks blurry and ugly. I heard that 1080p output should work over the iGPU, but I haven’t tried it (nor is the iGPU of any use to me).
To me it’s quite unacceptable for a motherboard that costed nearly 100 euro (at the time) more than Gigabyte’s entry level Z97X-SLI which does have 1080p support.
hi
it makes sense to update intel GOP "EFI rom / VBT"
when using only D-gpu mode
benefits come only for igpu mode ??
,.,.it’s just weird that so many users are trying to update this 
@SoniX
The UBU tool is amazing and I cant wait for the next release! Is there any chance of adding support for other platforms of bios? Insyde or Phoenix/Award for example? Possibly a separate tool for each platform?