@Fernando
This procedure is only for OROM VBIOS Haswell/Broadwell. As you already know, you can not take any OROM VBIOS for Hasvell/Broadwell and insert into the BIOS. So settings are specific to each motherboard. But as has been available BMP, reference VBIOS files and scripts BSF to them, then became possible to transfer the settings from the old version to the new version of the VBIOS. I often had to do OROM VBIOS update, so this has been added to the upgrade procedure. Unfortunately, to fully automate the process will fail, hence this option is designed for advanced users.

The process itself is simple.
With the help of UBU look what version OROM VBIOS. For example in 2170.
1. With the help of MMTool extract OROM VBIOS from BIOS file. Usually this VID-DID 8086-402/c02/412/c12.
For example we want to upgrade from 2170 to 2180.
2. In a separate folder, copy the files:
- OROM VBIOS extracted from the BIOS
- script BSF for 2170
- reference DAT and script BSF 2180.
3. Run BMP.
4. Loading OROM VBIOS 2170, and his script BSF, also in 2170.
5. Choose from the menu "BIOS Setting" - "Save All..." and save the settings in SSF-file.
6. In the saved file SSF find and delete one string "STRING $Signon......."
7. Load reference and script files version 2180.
8. Choose from the menu "BIOS Setting" - "Apply All..." and select the previously saved file SSF.
9. After filling in all settings save the file as VBIOS.DAT and copy this file to folder \Modules tool UBU.
Everything is now possible to update the correct BIOS.
This is a simple procedure and works correctly in most cases.

Collection OROM VBIOS and BMP modification program, the links in >this< post.

Zitat von Fernando im Beitrag #910

---

@ SoniX:

Thanks for your reply and for the detailed explanation of the Intel Haswell/Broadwell VBIOS update.
There is only 1 question left for me (or am I blind?):

Zitat von SoniX im Beitrag #909

---

Run BMP.

---

Where is the link to that tool?

---

Zitat von Fernando im Beitrag #913

---

@SoniX:
Meanwhile I have tried to update the DEV_0412 Intel VBIOS version of my ASRock Z97 Extreme6

---

Zitat

---

BIOS from v1022 to v1028 according your guide.
At least I succeeded.
Look here:


So thank you very much for having published the new UBU version 1.8.5, which now makes it possibe to update the Intel Haswell/Broadwell VBIOS version.

Note:
I compared the hex code of the original file named hsw_1022.dat with my modded VBIOS.DAT file and got the result, that they were identical. Is this ok or should the hex code be different?

---

In my differences should be.
So I did the transfer settings from 1022 to 1028 from the motherboard ASRock Z97 Extreme6, BIOS ver 1.30, VBIOS DEV_402.
Compare, if match, then you've done everything correctly.

Zitat von Fernando im Beitrag #915

---

Your attached VBIOS.DAT is different from mine. That means, that I have done something wrong.

---

Zitat von SoniX im Beitrag #909

---

The process itself is simple.
With the help of UBU look what version OROM VBIOS. For example in 2170.
1. With the help of MMTool extract OROM VBIOS from BIOS file. Usually this VID-DID 8086-402/c02/412/c12.
For example we want to upgrade from 2170 to 2180.

---

ok thx so much! works prefect!

ASRock Z97X Killer Fully updated!

Intel RST(e) OROM and EFI SataDriver
OROM IRST SATA - 13.2.0.2134
EFI IRST SATA - 13.2.0.2134
Intel OROM VBIOS and EFI GOP Driver
OROM VBIOS Haswell - 1215
EFI GOP Driver Broadwell - 5.5.1023
LAN OROM PXE and EFI UNDI - Intel
OROM Intel PXE - 1.5.53
OROM QCM-Atheros PXE - 2.1.1.5
Intel CPU MicroCode Haswell/Broadwell
CPU Microcode 0306C3 - 1C

@ Fernando
This is good. :)

@SoniX

I have found Marvell 91xx-92xx AHCI 1.1.0.1015, Haswell-Broadwell VBIOS 5.5.1030 and some strange 8086-2827 sSATA RSTe RAID 4.1.0.1026. The sources are from this post and this one. No direct link because that guy seems to be a ninja as well, just like Pacman, so it deserves some credit.

The Marvell and sSATA are from a server BIOS, so it would explain that sSATA. The Marvell controller is 9230, so some testing is needed before release. I have attached other stuff (forgot the source), maybe you will find a use for them. The only one worth mentioning is a new AMD GOP 1.54.0.0.0 from Asrock VisionX Series, which appears to be signed. No need to replace the current one in UBU, just something to be aware.

More to come...

@SoniX

Why is there a 111.bin in Modules\lan\FFS folder?

I think it should be possible to use modded 3.2.1.0 for 1022-7801. Here is an example in hex -



Here is the same disassembled -



It might be a wild guess, but to me it looks like it should support 4391, 7801, 7804. Not sure if other patch is needed. Also, a list of AMD AHCI/RAID IDs is to be found here -



- In UBU.bat lines 28-31 it should be 6.1.3-00035, not 6.1.3.00035. Not important, but consistency is needed, otherwise new users might wonder why is there a difference.
- line 128 should be "set m8=8" or "set m8=0" ?
- lines 177, 179 should be changed to something like "... hexfind 5472696E69747947656E6572 ..." and "... hexfind 4B6162696E6947656E6572 ... " or you will get a double extraction every time when VBIOS is found.

Other minor stuff in attached file. Please note that some of the changes are for my own personal taste, you don't need to view all of them as complaints.