Read the previous link i posted
1 Like
Hi,
I found the problem why the UBU tool doesn’t update the RAW GOP VBT in my case. The problem lies in the UBU.bat. First of all, in my bios there are 2 raw sections with the same RAW GOB VBT and that leads to the problem at the same time.
The UBU.bat counts how many GUIDs from GOP VBT there are, since in my case there are 2, the script is aborted. Here is the code from UBU.bat
If %vbt_count% is 2 in my case, the update is aborted with && goto end_video
If i remove && goto end_video one GUID of the both is updated.
Who can help my with this to Update the UBU.bat to get both GUID from Bios Updated ?
Look into the script parts for NIC firmware, maybe possible to ‘steal’ something there: Later versions of UBU were able to update two OROMS. But those were two identical OROMS in one guid.
UBU output
Main Menu
[Current version in BIOS file]
1 - Disk Controller
EFI Intel VROC for SATA - 6.3.0.1005
OROM Intel VROC for SATA - 6.3.0.1005
EFI NVMe Driver present
2 - Video OnBoard
EFI GOP ASPEED - 0.08.8c
OROM VBIOS ASPEED - 1.10.01
3 - Network
EFI Intel PRO1000 UNDI - 9.3.10
OROM Intel Boot Agent GE - 1.5.88
OROM Intel Boot Agent GE - 1.5.88
4 - Other SATA Controller
5 - CPU MicroCode
View/Extract/Search/Replace
S - AMI Setup IFR Extractor
0 - Exit
RS - Re-Scanning
A - About
Choice: 3
Network
[Current version]
EFI Intel PRO1000 UNDI - 9.3.10
OROM Intel Boot Agent GE - 1.5.88
OROM Intel Boot Agent GE - 1.5.88
[Available version]
-\ for i82579/i217/i218/i219 chips
EFI Intel Gigabit UNDI - 0.1.00
OROM Intel Boot Agent CL - 0.1.16
-\ for i210/i211/i350 chips
EFI Intel PRO1000 UNDI - 9.8.15
OROM Intel Boot Agent GE - 1.5.89
1 - Replace Intel
S - Share files
0 - Exit to Main Menu
Choice:
Choice:1
For compatibility of the DevID,
it is possible to install up to versions 6.6.04 and/or 1.5.62
EFI Intel PRO/1000 GUID 1B22B3F2-3151-4468-8AF3-590650EEAD22
File replaced
Set Device ID 0x1533
OROM in GUID A062CF1F-8473-4AA3-8793-600BC4FFE9A8
OROM VenID 0x8086 DevIO 0x1533 - Container: OROM found
OROM replaced
OROM VenID 0x8086 DevIO 0x1533 - Container: OROM found
OROM replaced
File replaced
EFI Intel PRO1000 UNDI - 9.8.15
OROM Intel Boot Agent GE - 1.5.89
OROM Intel Boot Agent GE - 1.5.89
Press any key to continue . . .
~~
Main Menu
[Current version in BIOS file]
1 - Disk Controller
EFI Intel VROC for SATA - 6.3.0.1005
OROM Intel VROC for SATA - 6.3.0.1005
EFI NVMe Driver present
2 - Video OnBoard
EFI GOP ASPEED - 0.08.8c
OROM VBIOS ASPEED - 1.10.01
3 - Network
EFI Intel PRO1000 UNDI - 9.8.15
OROM Intel Boot Agent GE - 1.5.89
OROM Intel Boot Agent GE - 1.5.89
4 - Other SATA Controller
5 - CPU MicroCode
View/Extract/Search/Replace
S - AMI Setup IFR Extractor
0 - Exit
RS - Re-Scanning
A - About
Choice:
Or use MMTool or UEFITool 0.25/0.28 or do it manually (HxD)?
I have found a better easyer Way.
I Updated it with UEFITool manually
Extracted the single Body of each to a .bin File, used BMP with BSF File from this Version to save all Settings in a transfer.ssf
Applied the transfer.ssf to the SKL 221 vbt.bin
And then you can Replace this Body with Uefitool
Same step 2 times for both bodies and perfect results
Can anyone confirm this tool works with asus x299 bios?
If not could some point me in the right direction to update modules and roms etc?
Since the Intel X299 chipset has been released already in 2017, the UBU tool will work with the related mainboard BIOS. Nevertheless I recommend to replace within the root of the UBU package the files named drvver.exe, MCE.py and MCE.db by newer versions. You will find them by doing a “Google Search”.
Depending on your specific hardware configuration it may be useful as well to update some BIOS modules, which are located within the UBU\Files folder.
1 Like
@Fernando, YESS, my dear friend Dieter! I’ll post the link in a couple of hours. Indicate in what topic. SoniX doesn’t mind. I should note that MCExtractor remains the old version for compatibility. I am updating MCE.DB.
Ok thanks.
@Fernando
YESS, my dear friend Dieter! SoniX doesn’t mind. I should note that MCExtractor remains the old version for compatibility. I am updating MCE.DB.
Yesterday I just turned 60 years old. What a puppy I am in front of you 
14 Likes
Sorry where do I find updated modules and stuff, sorry I’am new to this?
If there are any lol?
@Michael_Code
Dear Michael, thank you very much for your efforts to keep this beautiful tool available and up-to-date for the next years with the current and the upcoming chipset generations.
As soon as I have the required time, I will test your linked updated UBU package.
Happy birthday 
- the next 20 years will pass much quicker than the past ones (according to my own experience). Enjoy them nonetheless!
@Dudette
You have to search for the needed and matching BIOS modules yourself - the latest are not automaticly the best, especially not for old mainboards! You can find many new BIOS modules within >this< Forum Category.
Good luck!
1 Like
@Fernando I`m plannig 100 yers old,
Thankk You, my animals Docter!!!
I have add, my friend Dieter. You best Administratr And Pluto. And otther our friends. GitHub now rest.
Happy Birthday, you old chap… keep your spirit “young” cause time will pass anyway 
1 Like
@Michael_Code
Thank you for the updated UBU tool. Interested users, who are not satisfied with the BIOS updates delivered by the mainboard manufacturers, will be very grateful.
Since I was very curious about how it will work, I just have tested your updated toolkit with the latest Beta BIOS v5.61 for my ASRock X570 Pro4 and according to the results I got you have done a very good job - congratulations! 
My advice: Start a new UBU thread and give it a short, but meaningful title.
@plutomaniac
What is your opinion?
3 Likes
Sure 
2 Likes
Tried to use this thingy on an Aptio 5 (AM5 B650-E Gigabyte Aorus Master f22b bios).
mcodes seem all to up to date with f22b.
i225 (3) does not seem to get recognized correctly.
so far, so well
Poor respect for such a useful tool… 
i225 must be updated/replaced in UEFItool
I’m sorry. I didn’t want to be disrespectful. Happy about it
@/Maghook sorry my be my mistake?