@ all users, who are searching for an easy way to get any OROM or EFI module of their AMI UEFI BIOS updated:
It was our member eierfrucht, who gave me the links to >this< very interesting thread at forum.overclockers.ru and to a BIOS modding toolkit named "OROM_Replace", which has been developed by the Russian BIOS modding expert named LS_29. Meanwhile I found out, that LS_29 is just another nick name for our Forum member SoniX. This is very good news for all visitors of this Forum, because they may get answers to their questions by the developer himself.
Since this toolkit is very simple to use and seems to be able to update all interesting LEGACY and UEFI modules of an AMI UEFI BIOS without the need of an advanced BIOS modding knowledge, I decided to present it within my Forum.
It was our member eierfrucht, who gave me the links to >this< very interesting thread at forum.overclockers.ru and to a BIOS modding toolkit named "OROM_Replace", which has been developed by the Russian BIOS modding expert named LS_29. Meanwhile I found out, that LS_29 is just another nick name for our Forum member SoniX. This is very good news for all visitors of this Forum, because they may get answers to their questions by the developer himself.
Since this toolkit is very simple to use and seems to be able to update all interesting LEGACY and UEFI modules of an AMI UEFI BIOS without the need of an advanced BIOS modding knowledge, I decided to present it within my Forum.
Use of the "UEFI BIOS Updater" (UBU)
(last updated: 06/04/2014)
new: UBU v1.5.0
- Changelog:
- updated: Intel RST OROM and EFI (now v13.1.0.2126)
- replaced: OROMVer.exe on FindVer.exe (You can now customize search and display versions OROM)
Important:
The UBU tool has been designed for the modification of Desktop mainboard BIOSes and not for BIOSes of Mobile systems (laptops, tablets etc.).
Short description of the tool:
This tool is very easy to use and able
- to detect the versions of the OROM/EFI modules, which are inside an AMI UEFI BIOS file and
- to update
a) the most important OROM/EFI modules (incl. various "Universal TRIM in RAID0 modified" ones) and
b) the CPU MicroCode
of any AMI UEFI BIOS.
This tool cannot be used, if you want to
- modify any other BIOS type (Award/Phoenix, non-UEFI AMI or Intel mainboard BIOSes) or
- insert a BIOS module, which is not present within the original BIOS or
- remove a BIOS module.
- Preparations:
- Download the latest version of the "UBU" tool from >here< (developer's link) or >here< (Forum link).
New:
Intel 6-Series Chipset users, who want to get "TRIM in RAID0" support, don't need to download the separate "UBU_TRIM6" addon anymore, because everything is fully integrated into the UBU tool since v1.4. There are various Intel RAID ROM/SataDriver modules available, which have been "universally TRIM modified" by me according to CPL0's latest method. - Create any folder within the root of your system partition (drive C:) and name it anyhow (e.g. C:\UBU).
- Unzip the downloaded UBU tool archive completely into the just created folder. Now you should have some subfolders and a lot of files within the UBU processing folder.
- Additionally I recommend to copy the BIOS file (the pure file, not an EXE archive), which you want to get modified, into the just created UBU processing folder.
(Note: If the UBU tool shouldn't find a BIOS file within the UBU processing folder, it will give you the opportunity to navigate to it.) - Start UBU by running the command "UBU.bat"
Open the UBU processing folder, right click onto the file named UBU.bat and choose the "Run as Administator" option.
Alternatively you can run the DOS box (CMD) as Admin, navigate to the UBU folder and execute the command "UBU.bat".
As first step the execution of this command will rename the BIOS file, which is within the created UBU processing folder, to "bios.bin" and analyze the actual module content.
After having completed this action, the tool will show you, which OROM/EFI modules are within the BIOS and which version they have.
In my example (ASUS P8Z77-V BIOS v2104) the DOS box looked like this:
UBU Pic1.png - Bild entfernt (keine Rechte)
According to this screenshot the UBU Tool gave me the informations, that the original BIOS contained- an Intel RAID ROM v11.0.0.1339 and an Intel EFI SataDriver v11.5.0.1582,
- an Intel Sandy/Ivy Bridge VGA ROM v2132 and the related Intel Sandy/Ivy Bridge EFI GopDrivers v2.0.1016 and v3.0.1012 and
- an Intel LAN PXE ROM v1.3.81 and the related Intel EFI UNDI module v5.0.12.
As next step you will get the option to update different OROM, EFI and CPU Microcode modules and to replace them by different versions.
Here are some examples: - a) Update of the Intel RAID ROM/EFI SataDriver modules:
- b) Update of the Intel VGA ROM/EFI GopDriver modules:
- c) Update of the Intel LAN PXE ROM/EFI modules:
- d) Update of the Intel CPU MicroCode:
- Finishing UBU
If you want to finish UBU's work, you have to enter the number "0".
After having done that, the tool may offer the option to rename the BIOS file. This additional feature is very useful especially for capsuled ASUS BIOSes with the extension ".CAP". Modified .CAP BIOSes can only be flashed into the mainboard BIOS chip by using the "USB Flashback" feature.
The next picture shows how the UBU Tool renamed my ASUS P8Z77-V BIOS with the original name "P8Z77-V-ASUS-2104.CAP" to "Z77VB.CAP" according to ASUS "USB Flashback" rules:
UBU Pic9.png - Bild entfernt (keine Rechte)
The last UBU screen shows the credits to people, who helped SoniX to develop his tool. It will disappear after having hit the "Enter" key.
That's all you have to do! The BIOS file named bios.bin, which is still within the processing folder, has been updated by the UBU Tool according to your demands.
Notes:- The BIOS file may have to be renamed before you are going to flash it into the mainboard BIOS chip.
- You should remove the bios.bin file from the UBU processing folder, before you start a new BIOS module update procedure.
Note: If you want to replace any of the OROM/EFI modules by a modded one, please look into >this< post regarding the preparation.
General remarks regarding the usage of the UBU toolkit
- It is not a good idea to use this tool without any knowledge about what your are doing.
That is why I recommend to get some informations, before you are going to modify any BIOS and to flash it into the BIOS chip of any mainboard.
You can get them here:- a) >BIOS Modding: Introduction and Preparations< (the start post should be read completely),
- b) >Guide: AMI UEFI BIOS Modding< (the start post contains a lot of informations) and
- c) >Section "BIOS Modules" of this Forum< (here you can find detailed informations about the modules you want to get updated).
- If you are using this toolkit the first time, you should only update 1 single module (that one, which is the most important for you). This way you can minimize the risk of a BIOS update failure.
- The most critical toolkit option is the "Update of the Intel CPU Microcode". According to the developer LS_29 resp. SoniX the special procedure to update the Intel CPU microcode depends on the manufacturer of the mainboard and may be quite different from the procedure, which will be used by the toolkit. Here is the comment done by SoniX:
Zitat von SoniX
Unfortunately for MSI, Asus and others with similar BIOS-structure there are some problems in updating microcode processor module with this tool. This is not a problem with ASRock, Gigabyte, Biostar, ECS.
Consequence: This toolkit option should only be used by persons, who know, that it will work for their special mainboard. - Usually the toolkit renames the BIOS file to bios.bin. This way the BIOS shall be prepared for being flashed with the "Flash Toolkit" (=FTK, look>here< and >here<). If the user wants or have to to use another BIOS flash method, it is no problem to rename the BIOS file.
- It is possible to use this toolkit even for the replacement of an original by a modded module (example: "Universally TRIM modified" Intel RAID ROMs).
The modded module should be replaced within the related OROM subfolder of the toolkit before running the UBU.bat. If you want to know the exact procedure, please look into >this< post.
Note: The modded OROM should have the same version as the one, which is within the UBU tool OROM subfolder, and has to be renamed according to the UBU rules (should have exactly the same name as the replaced original OROM module).
Attention:
- After having finished the previous work, but before you are going to flash the BIOS, you should verify the BIOS modding success (by opening the updated BIOS file with the Aptio MMTool, extracting the related modules and checking the version with a Hex Editor) and the usability of the updated modules (by checking the DeviceID).
- Before you are going to flash the BIOS you should carefully read the chapter "Flashing the modded BIOS into the mainboard BIOS chip", which you can find within the start post of >this< thread.
- No warranty
Although I have tested the tool successfully with the actual BIOS 2003 of my ASUS Z77-V, I cannot give you any guarantee, that it will work with other AMI UEFI BIOSes as well. If you should run into problems, I recommend to post them into this thread.
Good luck with this interesting BIOS modding toolkit!
Fernando
My current System:
Mainboard: ASUS Z77-V, Disks: 2x256 GB Samsung 840 Pro as RAID0, Graphics: Intel HD4000, OS: Windows 8.1 Pro x64
Mainboard: ASUS Z77-V, Disks: 2x256 GB Samsung 840 Pro as RAID0, Graphics: Intel HD4000, OS: Windows 8.1 Pro x64
\
