@ 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 very interesting thread at forum.overclockers.ru and to a BIOS modding toolkit named 'OROMReplace', which has been developed by the Russian BIOS modding expert named LS29. Meanwhile I found out, that LS29 is just another nick name for our Forum member SoniX.
[email protected], Skype: Vinafix. Dismiss Notice Download 422.3 KB.zip. AMI Aptio UEFI MMTool ThienBui. AMI Aptio UEFI MMTool v5.0.0.7. ThienBui, Jul.
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. Preliminary Notes: 1. The RAID BIOS modules are only used, when the on-board SATA Controller is running in 'RAID' mode.
The update will only work, if there are matching RAID modules within the UBU subfolder Files Intel RST resp. Files Intel RSTe (see Chapter A).
Procedure: If you want to update the Intel RAID ROM or EFI RaidDriver module, you should type '1' from within the Main Menu and then hit the 'Enter' key. Now you will see a picture like this (example here: ASRock Z97 Extreme6 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 EFI RaidDriver versions, which are offered by the UBU tool for a replacement (they were previously put by me into the UBU subfolder Files Intel RST). After having entered '1' (= Update), I got this picture, which shows, that the replacement of the originally present Intel RAID BIOS modules (OROM and EFI 'RaidDriver') by the desired ones has been successfully completed: After having pressed any key, you will get the Main Menu picture again, but now showing other Intel RAID module versions. This is what I got: Now you have the option to update another sort of BIOS modules (inclusive the CPU Microcodes).
b) Update of the 'Video on-board' BIOS modules (here: Intel Haswell/Broadwell EFI GopDriver). If you want to do that, you should type '2' from within the Main Menu and then hit the 'Enter' key. These are the pictures I got before and after having updated the Intel EFI GopDriver module: In my example the Intel Haswell/Broadwell CPU GopDriver module has 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 and 2.) the tool named 'Intel(R) Binary Modification Program' (BMP), which you can get. SoniX has written a detailed guide about how to get the Intel VGA ROM (VBIOS) module safely updated. You can find his instructions. c) Update of the 'Network Adapter' BIOS modules (here: Intel and Realtek LAN ROM/EFI UNDI).
Preliminary Note: The LAN Option ROM resp. EFI UNDI BIOS modules are only used by the PC/Mobile system, if the 'Wake-on-LAN' option has been ENABLED within the BIOS. That means, that an update of these BIOS modules has no effect for users, who don't use the Wake-on-LAN option. Procedure: If you want to update the LAN modules of any AMI UEFI BIOS, you should type '3' from within UBU's Main Menu and then hit the 'Enter' key. This is the picture I got after having chosen this option with my ASRock Z97 Extreme6 BIOS: Here are the pictures about how I updated the Intel LAN Option ROM and EFI UNDI modules (left Pic: Update procedue, right Pic: Result): And here you can see how to update the Realtek LAN modules (left Pic: Update procedure, right Pic: Result): As you can see within the right Pic, all Intel and Realtek LAN modules have been successfully updated by the UBU tool. d) Update of 'Other SATA Controller' BIOS modules (here: ASMedia 106x Option ROM).
After having entered the number '5' (CPU MicroCode), you will get a popup window showing the actual CPU Microcode details of the BIOS: After having entered 'C' (creating FFS file with Microcodes), you will get a new window showing a preview of the new CPU MicroCode details (not yet updated). In my case it looked like this: After having chosen the option 'M' (for using the MMTool) the CPU Microcode update will be done by the UBU tool.
These are the pictures I got (left Pic: Update procedure, right pic: Result): By entering '0', you can finally return to the UBU Main Menu. f) Only for experts: Running the 'AMI Setup IFR Extractor' tool. This is what I got after choosing the option 'S' from the UBU main menu: If you want to know more about the IFR Ectractor tool, you may look. Finishing UBU:. After having completed all desired (resp. Currently available) UBU tasks, you will get the final results of the UBU work.
In my example I got this picture: If you want to finish UBU's work, you should 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 the renaming options I got for my modded ASRock Z97 Extreme6 BIOS: 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.
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) (the start post should be read completely),. b) (the start post contains a lot of informations) and. c) (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 LS29 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 and ).
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 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. 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. 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 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! New UEFI BIOS Updater Pre-Release 9 test Change: - Reworked the script and menu design - Added Preview versions of OROM - oromver v0.1 (test) - Added displaying EFI LAN Intel - Added new GUID LAN Realtek, QCM-Atheros and Broadcom - Added OROM VBIOS 2178 Haswell - Updated EFI LAN Broadcom UNDI 15.4.6 - Updated OROM's Marvell SATA 1.0.0.1038/1.0.0.0032 and LAN Realtek PXE 2.58 Edit: New UEFI BIOS Updater Pre-Release 10 test Change: - Updated EFI LAN Realtek UNDI 2.024!!!
This is a test version. Therefore, displaying versions OROM is not configured.
@ all experienced and courageous users, who want to update a PCI ROM module of their mainboard BIOS: Preliminary notes: Since I have some experience regarding the extraction and replacement of PCI ROM modules, which are part of the mainboard BIOS, I decided to create and to publish step-by-step guides for the different AMI/Award/Phoenix BIOS structures. Although these detailed instructions are mainly written for users, who want to update the Intel RAID ROM module of their mainboard BIOS, they basically can be used for the extraction and replacement of any other PCI ROM module too. BIOS Modding: Introduction and Preparations Introduction Warning: Modding a BIOS file by updating the inserted PCI ROM module is neither very difficult nor risky, but it is dangerous, if you are going to flash a modded BIOS into the BIOS chip of a mainboard. In the worst case you may not be able to use the computer anymore until you will get a new and working BIOS chip from the manufacturer of your mainboard. This is why I recommend to flash a modded BIOS only for experienced users, who know about the risks and do all necessary preparations for a possible failure of the BIOS update process (inclusive a complete backup of their data).
There is no warranty regarding the safety of my BIOS modding guides and the linked BIOS and PCI ROM files. Everything you are doing will be at your own risk. Actual BIOS files do not contain any separate AHCI ROM module, because such BIOS module resp. Firmware is not required anymore. The Intel SATA AHCI Controller of the mainboard is not supported at all by the RAID ROM module. That is the reason why users with an AHCI (non-RAID) system will not benefit from an update of the RAID ROM version. The PCI ROM modules are within the mainboard BIOS file and only visible by opening the BIOS file with a special tool like MMTool or CBROM.
Nevertheless it is possible to extract any PCI ROM module and to replaced it by another version, because the entire mainboard BIOS file has a modular structure. Although the BIOS files are developed and published by the mainboard manufacturer, the inserted PCI ROM modules were made by the vendor of the related on-board Controller chips.
Each PCI ROM module version, which has been delivered from the Controller chip vendor to the mainboard manufacturers, is identical and not dependent on the BIOS structure (AMI/Phoenix/Award) the mainboard manufacturer is using. As a consequence an extracted PCI ROM file usually can be inserted into each mainboard BIOS, which already contains the same sort of PCI ROM module. Basically the extraction and the replacement procedure of all PCI ROM modules is quite similar. That is why this guide is usable for the modification of any PCI ROM module from any vendor. Important note: Not all mainboard BIOSes can be easily modified by the user.
Examples:. Intel mainboards are equipped with an especially modified BIOS. These Intel BIOSes with the suffix.BIO cannot be opened and modified by any standard BIOS tool. Some old Phoenix BIOSes cannot be opened and modified by any common version of the tool CBROM. Some Gigabyte and ASUS mainboard BIOSes can be modified, but the flash procedure is checksum sensitive. Within my BIOS modding guides you may find some tips how to pass this restriction. Preparations (valid for nearly all AMI/Award/Phoenix BIOSes) This is what you should prepare, if you want to extract, to add or to replace any PCI ROM module from any mainboard BIOS:.
A. Download the following files and tools: ( Note: The offered files have to be unzipped by using WinRAR v5.xx!). the actual mainboard BIOS for your system (get it from the manufacturer). the appropriate BIOS processing tool The choice of the suitable BIOS modding tool depends on the BIOS platform of your special mainboard/system.
The most popular BIOS platforms are made by AMI (American Megatrends Inc.) and by Phoenix resp. Award ( Note: Intel and Dell mainboard BIOSes use another platform and connot be opened and modified by the tools, which are listed here.). Tip: If you don't know the architecture of your mainboard BIOS, you can find it out by starting your computer and entering the BIOS. Then you should see the name of the BIOS platform. AMI platform BIOS modding tools: Here are the download links to the available tools, which are able to open and modify BIOSes with an AMI platform:.
a) Non-UEFI AMI BIOS tool MMTool v3.26 (for older AMI BIOSes without UEFI structure): The link to the 'AMI MMTool v3.26' has been removed upon demand of American Megatrends Inc. (AMI), but you will find it, if you do a Google search for 'MMTool 3.26'. b) AMI Aptio IV UEFI MMTool v4.5 (for all Intel 6-/7-/8-/9-Series chipset systems and for AMD systems with an UEFI BIOS): The link to the 'AMI Aptio UEFI MMTool v4.50.0.23' has been removed upon demand of American Megatrends Inc.
(AMI), but you may find it, if you do a Google search for 'MMTool Aptio 4.50.0023'. c) AMI Aptio V UEFI MMTool v5 (for the latest Intel chipsets from X99 and 100-Series up): The links to the 'AMI Aptio UEFI MMTool v5.0.0.7' and to the 'AMI Aptio V UEFI MMTool v5.2.0.24' have been removed upon demand of American Megatrends Inc. (AMI), but you may find it, if you do a Google search for 'MMTool Aptio 5.00.0007 resp.
'MMTool Aptio 5.02.0024'. d) CodeRush's UEFITool (currently latest: v0.26.0) (for advanced BIOS modding users, usable with all Intel and AMD chipset mainboards with an UEFI BIOS): ( Phoenix/Award platform BIOS modding tools:. This is the tool I recommand to download and to use for the old Award or Phoenix BIOSes: Note: The CBROM32198.EXE has been renamed by me to 'CBROM.EXE' to make it easier for you. It works in the DOS box (has to be run as Admin) of all actual Windows Operating Systems, even within a 64bit environment. If this CBROM version should not handle your special Phoenix/Award BIOS file correctly, you should download and try another CBROM version you get. Attention: Only very few CBROM versions will work in a 64bit environment, some of them need to be run in real DOS mode. Only for users with a Gigabyte Award BIOS: Due to the specific characteristics of Gigabyte Award BIOSes (look ) you may additionally need the older version 155 of CBROM.
You can get it here:. Tip: If you are not sure, which tool you will need, you should download them all. the PCI ROM module file you want to insert into your BIOS. either as already extracted uncompressed PCI ROM file or.
as complete BIOS file, where you want to get the desired PCI ROM module extracted from. Note: You can find download links to a lot of actual and already extracted AHCI/RAID ROM modules from different chipset manufacturers within the start post of thread.
optional: any Hex Editor like HxD (just to verify the PCI ROM version). is the link to the HxD homepage. Alternatively you can download the latest multi-language version of HxD directly from or from (MIRROR).
Create a special folder within any partition of your hdd/SSD (example: C: test) and copy all previously downloaded and unzipped files into it. Just for the emergency case you should leave a copy of your original mainboard BIOS file somewhere else outside the system (example: USB stick). D. Only for AMI (non-UEFI) BIOSes: If the mainboard BIOS file does not have the suffix '.ROM' rename the suffix to '.ROM'. This is necessary, because the MMTool prefers to open '.ROM' files. Additional remarks:. AHCI and RAID systems generally will work at its best, when the in-use RAID ROM module (='firmware' of the AHCI/RAID Controller) and the in-use AHCI/RAID drivers belong to the same generation (for Intel: MSM/RST/RSTe) and - if possible - to the same version series (e.g.
Intel MSM v8.9 or Intel RST v10.1). Unfortunately there are some technical limitations, because the actual PCI ROM modules are not fully backwards compatible. Only the owners of a brandnew mainboard or pc can be sure, that the newest PCI ROM version definitively will work. As a consequence users with an older hardware configuration have to find out themselves (or by a Google search) the last PCI ROM version, which is suitable for their mainboard/system. Users, who have flashed a BIOS with an uncompatible Intel RAID ROM version, probably will not be able to run and/or to use the Intel RAID ROM Utility (by hitting CTRL+I), but usually this problem can be solved by reflashing the original BIOS.
Good luck with the later BIOS modding and flashing procedure! @ dlguevara: Welcome at Win-RAID Forum! Zitat von im Beitrag Hi, I'm having the issue with a 3tb hdd being detected as a 746 GB HDD, in addition to my idea to use RAID. Asi I understood for what it's written here 'Intel mainboards are equipped with an especially modified BIOS. These Intel BIOSes with the suffix.BIO cannot be opened and modified by any standard BIOS tool.' , game is over for me.
The only way to solve this is to change my mother? I'm using an intel DQ35MP.
As you have already realized, your Intel mainboard BIOS file cannot be opened and modified by using any of the standard BIOS tools. I just have downloaded the latest BIOS for the Intel board DQ35MP and was able to look into it by using Andi's Phoenixtool v2.1.9. The BIOS contains the Intel MSM RAID ROM v8.9.0.1023. For the detection of 2 TB sized RAID volumes an Intel RST RAID ROM v10.5 or higher is required. Since I don't have any experience with the modification of Intel BIOS files, I am not able to help you. Maybe someone else can do it.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |