[ARCHIVE] Outdated UBU Tool related Questions, Reports and Suggestions

[SoniX]

@Fernando

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

Probably DEV_402?

BIOS from v1022 to v1028 according your guide.
At least I succeeded.
Look here:
<img src=‘http://files.homepagemodules.de/b602300/f16t154p8403n2_coBXHPYd.png’alt=’’ style='border:none; ’ />

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.

VBIOS_1028_Z97_Extreme6.rar (39.1 KB)

[Fernando]

@SoniX

Zitat von Fernando im Beitrag #913

---

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

Probably DEV_402?

---

Yes, according to the Aptio MMTool it’s DEV_0402, but according to my Win8.1 Device Manager the correct DeviceID is DEV_0412.
Look here:

Zitat von SoniX

---

@Fernando

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.

---

So I suspect, that I have done a mistake while trying to transfer the specifications from the extracted VGA ROM v1022 to the latest v1028 ROM module.
I will repeat the test tomorrow.
EDIT:

@SoniX

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

[SoniX]

@Fernando

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

Experience comes with time. I also had a lot of errors. I’ll try to make the screenshots, I think it will help in the future.

[f3bandit]

@SoniX

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.

Having a hard time with step one? how exactly are you locating the orom in the bios with MMTool??

EDIT by Fernando: Unneeded quoted text removed (to save space within this voluminous thread)

Z97XKil_SLIC2.1_1.55.rar (5.48 MB)

[Fernando]

@f3bandit

Having a hard time with step one? how exactly are you locating the orom in the bios with MMTool??

All Option RIM modules are usually within the CSMCORE file of the AMI UEFI BIOS.
Regarding the OROM extraction procedure please look into the chapter 2 of >this< guide. The only difference between the extraction of an Intel VGA ROM (VBIOS) and an Intel RAID ROM is, that the Intel Graphics Controller has another DeviceID. So you have to choose another "Link ID" combination (for example "8086,402") within the "For Option ROM only" section, before you hit the "Extract" button.

[f3bandit]

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

z97xkil_slic2.1_1.55b.rar (5.45 MB)

[Fernando]

@ SoniX:

Today I have repeated the update of the Intel Haswell/Broadwell VBIOS from v1022 to v1028 according the actual guide and succeeded without any problems.
So I have obviously done a mistake yesterday.

[SoniX]

@ Fernando
This is good.

[lordkag]

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

stuff.rar (977 KB)

[lordkag]

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

compare.rar (11.6 KB)

[SoniX]

@lordkag

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

This file can be deleted. I forgot about it after the next test.
For information saterial and thank you so much. I’ll see next weekend, now just a lot of other things.
Regards.

[f3bandit]

Zitat von lordkag im Beitrag #922
"Haswell-Broadwell VBIOS 5.5.1030"

this vbios is old, The most up to date so far is 5.5.1215 as mentioned earlier in this thread.

[SoniX]

@f3bandit

Zitat von lordkag im Beitrag #922
"Haswell-Broadwell VBIOS 5.5.1030"

this vbios is old, The most up to date so far is 5.5.1215 as mentioned earlier in this thread.

Do not confuse version OROM VBIOS and a version VBT for EFI GOP Driver.
You can put here OROM VBIOS version 5.5.1215?
Very interesting to see…

[f3bandit]

@SoniX

Zitat von f3bandit im Beitrag #925

---

Zitat von lordkag im Beitrag #922
"Haswell-Broadwell VBIOS 5.5.1030"

this vbios is old, The most up to date so far is 5.5.1215 as mentioned earlier in this thread.

You can put here OROM VBIOS version 5.5.1215?
Very interesting to see…

---

It’s from the package you uploaded i was surprised as well after I did you’re mod and re-ran UBU to check everything it detected it as 1215.
And I checked the file he uploaded against other files. I am pretty sure it’s a vbios as it said bios in hex editor. and nothing about gop driver.
altho I did second guess my self and if you’re looking at it as driver version 5.5.1030. it would appear to be a newer driver version. but when I
checked it in hex it appeared to be a vbios. well I can try the same mod with the file he uploaded and see what it shows up as after?
as the vbios you uploaded was v1028. but after the mod shows up as 1218. so we will see.

asrock_vbios.rar (1.53 KB)

[f3bandit]

I have verified the one you uploaded is newer! "5.5.1215" is the one you uploaded! if you hex edit the vbt files under folder 1028 the bios signon header reads 1215

[f3bandit]

[quote=SoniX|p8377] New OROM VBIOS here

What bios did you pull the GOP vbios from? I would reason to guess the gop driver is newer as well!?! Can you upload or attach the bios you scavaged the vbios from please?

[lordkag]

@f3bandit

Sonix was right. What you think is a VBIOS is actually a VBT = Video BIOS table. The legacy VBIOS is easily modified using the appropriate tools, so it doesn’t need an extra file, OEMs just replace the original Intel VBIOS with a patched one. The VBIOS follower in UEFI system is named GOP = Graphics Output Protocol and has many new good things, one of them being the ability to sign the UEFI drivers, which is why the GOP needs an extra file to accommodate the needed OEM settings, because the GOP cannot be modified.

You are lucky that your system still works after your “update”, you probably boot in pure UEFI or use a separate GPU. Something to remember:

- The VBT is small - 5-6 KB, the VBIOS is larger - 64 KB.
- The VBT starts with $VBT and is located in GUID 878AC2CC-5343-46F2-B563-51F89DAF56BA, the VBIOS starts with hex 55AA and is usually located in CSMCORE.
- The VBT has no PCI ID, the VBIOS has one and it is found after string PCIR, stored in hex little indian.

[f3bandit]

okay I see what I did wrong and thx. surprisingly the adapter works fine actually! lol

But I did update the bios the proper way! thx guys!


Select option for update

1 Intel RST(e) OROM and EFI SataDriver
OROM IRST SATA - 13.2.0.2134
EFI IRST SATA - 13.2.0.2134
2 Intel OROM VBIOS and EFI GOP Driver
OROM VBIOS Haswell - 1030
EFI GOP Driver Haswell - 5.0.1037
3 LAN OROM PXE and EFI UNDI - Intel, Realtek, BCM, QCA
OROM Intel PXE - 1.5.56
OROM QCM-Atheros PXE - 2.1.1.5
7 Update Intel CPU MicroCode Haswell/Broadwell
CPU Microcode 0306C3 - 1C
9 Look the Version of all UBU modules in VerDID.txt
0 Exit
Press ENTER - Re-Scanning ALL EFI modules.

Enter number:

[quetzalin]

Can someone explain better how to use Intel® Binary Modification in order to be able to flash the last OROM?.

I managed to extract the VBIOS OROM from my BIOS using MMTool Aptio but i have no clue what to do on Intel BMP.

When i go to File - Open… i’m being asked for two files, one is a Binary data file, i guess i have to select my extracted VBIOS OROM here but i don’t know what i have to select on BMP Script File?, is it the .bsf of the VBIOS version i want to flash?, already tried to do so but then i dont know how to proceed.

Edit: Never mind, i’m blind and didn’t read all the thread, here is the answer

@SoniX

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.

[MacG32]

@SoniX Is there a X99 compatible version of this slated for the near future? I’ve seen that X99 motherboard makers can’t seem to update their newly released BIOSs either. Thank you.