@ 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.

1. SoniX, who is doing the main UBU work (he had the idea, writes the script named UBU.bat and bundles the various included tools and modules to an up-to-date BIOS modding toolkit),
2. CodeRush, the developer of several BIOS tools (UEFITool, UEFIFind, UEFIExtract etc.), which are components of the UBU toolkit and used by SoniX's script and
3. plutomaniac, the developer of the Intel ME Analyzer tool, which is an additional component of the UBU toolkit package.

• 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.
• Problem with AMI Aptio V BIOSes:
  The UBU tool uses the AMI Aptio MMTool v5.0.0.7 (for the newest Aptio V BIOSes) and supports all Intel and AMD platform BIOSes. Unfortunately the currently available AMI Aptio V MMTool v5.0.0.7 has problems with the update of certain BIOS modules of the latest Intel chipset mainboards (X99 and newer). That is why the UBU tool may not be able to update all BIOS modules of AMI Aptio V BIOSes (the tool will only show the version of the currently inserted BIOS modules).
  Solution: It is possible to modify an AMI Aptio type V BIOS manually by using CodeRush's UEFITool, which is part of the UBU tool package. You can find a short guide within the start post of >this< thread (Chapter B).
• Special problem with Intel's iGPU VGA ROM modules (=VBIOS):
  Contrary to the other Option ROM modules there is no "universally" usable Intel VGA ROM module available for systems with an Intel CPU from Sandy/Ivy Bridge up. That is why the mainboard specific VBIOS settings have to be transfered by using a special tool named BMP to the desired Intel VGA ROM module version, before the UBU tool is able to update the VBIOS version (for details see below).

1. Preparations:

   • Download the latest version of the "UBU" tool from >here< (developer's link) or >here< (MEGA link, not always up-to-date).
     Note: For users with an Intel 6-Series chipset RAID0 system there is no need to download any "especially modded" Intel RAID ROM module. The UBU tool contains various Intel RAID ROM module versions, which have been "universally TRIM modified" by me according to CPL0's latest method.
   • Optional:
     If you want to get the Intel iGPU VGA ROM (VBIOS) updated by the UBU tool, you should additionally download and install Intel's utility named "Binary Modification Program" (BMP). You can get the latest version of this tool >here<.
   • 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.)
   
   Note: If you want to replace any of the OROM/EFI modules by a modded one (except the "TRIM in RAID0 modded" Intel RAID ROM modules the UBU tool is offering), please look into >this< post regarding the preparation.
2. 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 and which CPU Microcodes are within the BIOS and which version they have.
   In my example (ASUS P8Z77-V BIOS v2104) the DOS box looked like this:
   
   According to this screenshot the UBU Tool gave me the informations, that the original BIOS contained
   • the Intel RAID ROM v11.0.0.1339 and the Intel EFI SataDriver v11.5.0.1582,
   • the Intel Sandy/Ivy Bridge VGA ROM v2132 and the related Intel Sandy/Ivy Bridge EFI GopDriver modules v2.0.1016 and v3.0.1012,
   • the Intel LAN PXE ROM v1.3.81 and the related Intel EFI UNDI module v5.0.12 and
   • the CPU Microcodes 17 (for IvyBridge) and 28 (for SandyBridge)
   
   Additionally the UBU tool offers the option to detect the Intel Management Engine Firmware version of the related BIOS by running the tool named ME Analyzer (developed by our Forum member plutomaniac).
   
   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 RaidDriver (former name: SataDriver) modules:
     
     If you want to do that, you should type "1" and then hit the "Enter" key.
     Now you will see a picture like this (example here: ASUS P8Z68-V BIOS):
     
     
     On top the tool shows the Intel RAID ROM and SataDriver module versions, which are currently within the BIOS.
     Below you can see the Intel RAID ROM and SataDriver versions, which you can get, if you want.
     Note: If you should not find the desired Intel RAID ROM/EFI RaidDriver version listed, you can insert the related modules as SataOrom.bin or/and RaidDriver.efi files into the UBU\Modules\IRST\User subfolder and re-run the UBU tool after having done that. This is a new UBU feature since v1.47.
     
     Now you can choose the Intel RAID module version you want to get inserted (unless you want a TRIM modded one).
     
     Special TRIM-mod option for Intel 6-Series RAID0 systems:
     As you can see, the UBU tool offers an additional option "T", which is for 6-Series chipset users, who want to get an "Universal TRIM modded" Intel RAID module version.
     If you hit "T" or "t" instead of any number, you will get a picture like this:
     
     
     Then you can choose the TRIM modded Intel RAID ROM/EFI SataDriver version you want to get inserted.
     In my example I have entered "4" and got this picture, which shows, that the insertion of both modules (RAID ROM and SataDriver) as desired TRIM modded version was successful:
     
     
     After having hit any key, you will get the first picture again and have the option to update another OROM or EFI module (inclusive the CPU Microcode).
   • b) Update of the Intel VGA ROM/EFI GopDriver modules:
     
     This is the picture I got after having updated the Intel EFI GopDriver modules for Sandy/Ivy Bridge CPU's:
     
     In my example the Intel Sandy/Ivy Bridge GopDriver modules have been successfully updated to the latest versions.
     Remarks regarding the update of the Intel VGA ROM (VBIOS) modules:
     Unfortunately there are no Intel VGA ROM (VBIOS) modules available, which are compatible with all existing DeviceID specific iGPU Graphics Controllers. For unknown reasons the mainboard manufacturers insert slightly different VGA ROM modules into their BIOSes with an Intel Chipset from 6-Series up. That is why the UBU tool is not able to update the Intel VGA ROM module the easy way as with other Option ROMs.
     Nevertheless the UBU tool can help you to get your Intel VGA ROM updated, but you will additionally need
     1.) the newest Intel VGA ROM module for your special Intel CPU architecture (as *.dat files) with associated binary script files (as *.bsf files). You can download this VBIOS package from >here< and
     2.) the tool named "Intel(R) Binary Modification Program" (BMP), which you can get >here<.
     SoniX has written a detailed guide about how to get the Intel VGA ROM (VBIOS) module safely updated. You can find his instructions >here<.
   • c) Update of the LAN ROM/EFI UNDI modules:
     
     This is the picture I got after having chosen this option with my ASUS P8Z77-V BIOS:
     
     In my case the Intel LAN ROM (=Boot Agent CL) of the BIOS had been updated to v0.1.06 and the Intel EFI Gigabit UNDI module to v0.0.09.
   • d) Update of the Intel CPU MicroCode:
     
     After having entered the number 7, you will get a popup window showing the actual CPU Microcode details of the BIOS:
     
     After having hit the "Esc" key and entered the desired option number, you will get a new popup window showing the updated CPU MicroCode details.
     In my case it looked like this:
     
     In the background you can see the UBU processing window (hopefully) showing the successful update of the CPU Microcode.
     This is the picture I got:
     
     After having hit the "Esc" key, the popup window disappears and the UBU returns to the main menu showing the options and the OROM and EFI module versions, which are currently present within the BIOS (after the update).
   • e) Optional: Usage of the Intel ME Analyzer:
     
     Besides the classical "BIOS Region", where all the above mentioned BIOS modules are located, Intel Chipset mainboard BIOSes contain a special "Intel ME Region", where the Firmware of the Intel Management Engine is situated.
     The UBU tool package contains a special tool named "ME Analyzer", which has een developed by plutomaniac and is able to show the most important Intel ME Region details of the opened BIOS.
     This is the picture I got after having hit the number 9 from the UBU Main Menu:
     
     Important notes:

     1. The ME Analyzer detects the Intel ME Firmware version, which is within the presented BIOS file and has nothing to do with the Intel ME Firmware version, which is within the BIOS chip of the target mainboard. So don't worry, if the Intel ME Firmware of your BIOS Chip is newer than the Intel ME Firmware, which is within the BIOS you are going to flash. The Intel ME Firmware of your system will not be "downgraded".
     2. It is impossible to update the Intel ME Firmware by using the UBU tool package. The only possibility to get an up-to-date Intel ME Firmware is to flash the ME platform related latest Firmware into the BIOS chip of the mainboard by using the appropriate Intel ME Firmware Update Tool (look >here<).
3. 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:
   
   
   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 (usual name given by UBU: bios.bin), which is still within the UBU processing folder, has been updated and finally renamed 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 recently processed BIOS file from the UBU processing folder, before you start a new BIOS module update procedure.

• 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.
• A 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.
  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).

• After having finished the previous work, but before you are going to flash the BIOS, you should verify the BIOS modding success. You can do it either by re-running the UBU tool or by opening the modded BIOS file with the Aptio MMTool, extracting the related modules, checking the version with a Hex Editor and the usability of the updated modules (by checking the DeviceID).
• Users of an ASUS or ASRock mainboard may get an "Integrity Error" message, when they try to flash any modded BIOS. >Here< is a guide about how to circumvent the built-in integrity check.
• 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.

Since the AMI UEFI BIOS Module "Replacer" has just been updated to v0.995, I have customized and complemented the start post of this thread.

Enjoy it!
Fernando