[Discussion] UBU Tool related Questions/Reports/Suggestions

Radu91 · August 14, 2024, 5:56pm

@SoniX can UBU be made to insert NEW option rom, or maybe can you do a guide how to do it manually? I want to add VIA VT6421A option rom into the bios. The PCI Card is connected with a PCIE to 2XPCI to z690 UD DDR4. The “option rom” tab in MMTOOL I think is for EFI rom not legacy, and it makes the new saved bios invalid for BIOS UPDATE.

I simply added V041312.rom data to the end of my OROM body, forced bios flash(using recovery mode) and it did not work, the sata drive is not in the Bios boot menu,

You talked about “Size OROM”, do I need now to find hex value representing this in my OROM and increase it by the amount of V041312.rom size?, this is what I don’t understand, size as ‘bytes’, how is the hex representing this, example number 85 in hex normally as 38 35, or switched 35 38?

(it is the same GUID for me 365C62BA-05EF-4B2E-A7F7-92C1781AF4F9, in my OROM I see text ‘RAID’, ‘USB’, NVME, SATA, PCI, CD-ROM, FLOPPY, this:
.AMIBIOS(C)2010 American Megatrends, Inc. …BIOS Date: 12/24/18 09:42:34 Ver: 08.00.10 )

I tried with rambios(to load the rom and init it) I can access the ROM menu and see the sata drive connected, but FDISK or XFDISK hangs when attempting to access the new visible drive, and grub4dos does not see it(for it to then to boot from it)

SoniX · August 15, 2024, 12:10am

@Radu91
Can you provide this OROM?

Radu91 · August 15, 2024, 5:52am

@SoniX

z690_UD_DDR4_F25_OROM_BODY.zip (46.9 KB)
VIA VT6421 Option ROM V041312.zip (38.8 KB)

Another way I tried, I replaced lan pxe(from MMTOOL “Option ROM” tab) with the via option rom, the lan pxe boot(non uefi) option disappeared from boot menu but the disk connected to the via pci card did not appear.
(replaced the lan pxe with MMTOOL and UEFITOOL, same result)

ThomasRhin · August 16, 2024, 6:45pm

Just got a new Intel LGA 1200 11th gen CPU microcode from extracting ASUS BIOS that UBU shows the message the mCode does not exist in the database and suggests me to share it. May I attach the microcode here ?

cpuA0671_plat02_ver0000005E_2023-09-14_PRD_45D810F0.bin

as shown by the file name : patch version 5E, dated as 2023-09-14

I have successfully transferred the new mCode to another Gigabyte Z590 mobo BIOS.

lfb6 · August 16, 2024, 7:01pm

Possibly old MCE database in UBU since it’s known since DB281

Otherwise this thread would be the perfect place:

Latest is Intel cpuA0671_plat02_ver00000062_2024-03-07_PRD_2B7D62D5

But thanks a lot for sharing the µcode anyway!

westlake · August 16, 2024, 7:01pm

@ThomasRhin

Use this updated database (r276).
Only some AMD microcode is not included, which requires a newer version of MCE (1.94.2+).

MCE.rar (80.9 KB)

Ludolf · August 18, 2024, 9:08pm

Got this error today:
no-python

OS: Windows 7 Professional x64
installed python-3.8.8rc1, also x64 (latest for Windows 7)
updated pip and installed “colorama” and “pltable”

Does anyone have idea how to fix it?

westlake · August 18, 2024, 9:32pm

@Ludolf

If it worked before, something must have changed, right? Anyway, I think 3.8.19 is the latest version that still works with Windows 7. I’ve done the BIOS, if you’re interested.

Medion.rar (2.4 MB)

Ludolf · August 18, 2024, 9:47pm

No, this was on a fresh install.

But fixed it.

I uninstalled python and this time i used v3.8.9 (i have no idea how to update it without a compiled installer, sorry) and checked the box for “PATH” while beginning of installation. Maybe this was the solution.

SoniX · August 19, 2024, 5:27pm

OS Windows 7 x64 Python 3.8.10 x64
Install to “C:\Python”
Install Launcer
Add to Enviroment “Path=…”
Assiciated Python Files
Wirks good!

ThomasRhin · August 20, 2024, 7:34pm

Thank you very much for informing me this Github respositories.

ThomasRhin · August 20, 2024, 7:37pm

Thank you too for sharing me with the updated mCode and DB from Github reponsitories.

ThomasRhin · August 20, 2024, 7:41pm

i stucked at the Python stuff for a long time too. Sorry i am not good at the Environment path thing. Shoud i point the path to the Python installing directory by editing(adding) the environment system variable ?

By the way, adding the internal testing VMD-RST EFI driver from ASUS BIOS.
Intel-VMD-RST_EFI-RaidDrive v20.1.0.5817.rar (142.6 KB)

westlake · August 22, 2024, 12:50am

@SoniX

wrong_data

The BIOS version is 3.08 and the date is 22 July 2024(?). True, it is a Strix Point BIOS, but it works fine with another one.

ChrisM · August 22, 2024, 7:01pm

Hi all. This a carryover from this thread post.

UBU (UEFIReplace, I’m guessing) is slightly modifying the bios structure due to the size of 2 of 4 replaced/upgraded microcodes. To “buy some space”/minimize the issue, I’ve re-run UBU to maintain 1 of the MC’s so that I’m only dealing with 1 needed MC that is oversized.

UBU is getting rid of a non-empty Padding file under File GUID: B52282EE-9B66-44B9-B1CF-7E5040F787C1. The thinking is to add it back in, and then reduce the size of the Padding file under Microcode and/or reduce the size of the Volume free space.

I can hex editor add a Padding file under File GUID: B52282EE-9B66-44B9-B1CF-7E5040F787C1. But the original Padding file is not data free. I could also remove FF’s in the other 2 places. Looking for a little help to finish this off.

I ran fptw64 -a 0x1D50000 -l 0xF0000 -d ucode.bin, so I could flash the corrected ucode.bin, or just FPT the new full bios.

ucodebins.zip (974.1 KB)

The attached are the original/unmodified and UBU modified ucode bins + the UBU run result.

westlake · August 22, 2024, 7:45pm

@SoniX

The wrong date (12/12/2012) will be a general error. It is also present in this BIOS.

I don’t fully understand the “BIOS release” and “BIOS version” parts either. I have looked at some BIOSes, but the BIOS version part is only visible for Strix Point. On older BIOSes, the version is listed before the date. Wouldn’t it be logical to have the date at “BIOS release” and the version at “BIOS version”? In fact, perhaps “date” instead of “release” would be a better choice.

Also, I deliberately use the latest version of MCE, and if I select option 5 in UBU, the microcode is automatically saved to that directory, as if the X command had been used. How intentional is this? I find it quite confusing.

SoniX · August 22, 2024, 10:20pm

@ChrisM

I posted f15. MMTool is now used instead of UEFIReplace.
I do not give any guarantee that this solution will work as it should. Unfortunately, the tools are old, but there are no new ones.

SoniX · August 22, 2024, 10:37pm

@westlake

The version and model data are taken from two files. But it seems that the ACS decided to put their own rules in order.

ChrisM · August 23, 2024, 5:18am

Thanks @SoniX. I’m seeing that now. I’ll make a run at it. I’ve been at this for a few months, now. I’ve learned patience, finally. Ok. I’ll follow up.

ChrisM · August 23, 2024, 9:32pm

Hi there. I’m assuming you meant a15.

You probably already know this, but if you’re looking for feedback, this is my a15 UBU run result:

Details: (open/hide by a click)

^{Scanning BIOS file backup.bin.}
^{Please wait…}
^{Manufacturer - Default string}
^{Model - Default string}
^{BIOS release - 5.13 08/31/2023}
^{BIOS version - 00.30}
^{BIOS platform - AMI Aptio 5}

^{[EFI Drivers - Find and Extract]}
^{Intel RST GUID 8C2E10DB-280F-4D4C-9B6E-C4C2A8A4C629}
^{Intel GOP SubGUID D8248140-88B5-4C14-9E9F-FD1CFA9D071E}
^{AMI NVMe GUID 634E8DB5-C432-43BE-A653-9CA2922CC458}
^{Realtek Undi GUID 4953F720-006D-41F5-990D-0AC7742ABB60}
^{Intel GOP VBT GUID 56752DA9-DE6B-4895-8819-1945B6B76C22}

^{[OROM - Find and Extract]}
^{VBIOS in GUID FD41D244-F0FB-4FD0-8FD6-4276BD4323D0}
^{OROM in GUID 7C3B8701-2C3B-49FA-A529-F31D441265B1}
^{OROM in GUID 6357578A-52D1-4517-BE96-10391404754C}
^{OROM in GUID 914AB3BE-A2C2-463A-B77D-F820FBBA180E}

^{UEFIReplace v0.25.0 will be used.}

^{Waiting for 8}

^{Main Menu}
^{[Current version in BIOS file]}
^{1 - Disk Controller}
^{EFI Intel RST RAID Driver - 17.8.1.4572}
^{EFI NVMe Driver present}
^{2 - Video OnBoard}
^{EFI GOP Driver SKL-AML - 9.0.1085}
^{RAW GOP VBT SKYLAKE - 221}
^{3 - Network}
^{EFI Realtek UNDI Driver - Unknown}
^{4 - Other SATA Controller}
^{5 - CPU MicroCode}
^{View/Extract/Search/Replace}
^{S - AMI Setup IFR Extractor}
^{O - Option ROM in other GUIDs}
^{0 - Exit}
^{RS - Re-Scanning}
^{A - About}
^Choice:5

^{╔═════════════════════════════════════════╗}
^{║ MC Extractor v1.94.2 r276 ║}
^{╚═════════════════════════════════════════╝}
^{╔════════════════════════════════════════════════════════════════════════════╗}
^{║ Intel ║}
^{╟─┬─────────┬─────┬─────────┬────────┬──────────┬─────┬───────┬─────────┬────╢}
^{║#│ Type │CPUID│Platforms│Revision│ Date │State│ Size │ Offset │Last║}
^{╟─┼─────────┼─────┼─────────┼────────┼──────────┼─────┼───────┼─────────┼────╢}
^{║1│Microcode│906EA│ 22 (1,5)│ F4 │2023-02-23│ PRD │0x19800│0x1D50400│Yes ║}
^{╟─┼─────────┼─────┼─────────┼────────┼──────────┼─────┼───────┼─────────┼────╢}
^{║2│Microcode│906EB│ 02 (1) │ F4 │2023-02-23│ PRD │0x1A000│0x1D69C00│Yes ║}
^{╟─┼─────────┼─────┼─────────┼────────┼──────────┼─────┼───────┼─────────┼────╢}
^{║3│Microcode│906EC│ 22 (1,5)│ F4 │2023-02-23│ PRD │0x19C00│0x1D83C00│Yes ║}
^{╟─┼─────────┼─────┼─────────┼────────┼──────────┼─────┼───────┼─────────┼────╢}
^{║4│Microcode│906ED│ 22 (1,5)│ FA │2023-02-27│ PRD │0x1A000│0x1D9D800│Yes ║}
^{╚═╧═════════╧═════╧═════════╧════════╧══════════╧═════╧═══════╧═════════╧════╝}
^{These microcodes are in your BIOS file}
^{GUID 17088572-377F-44EF-8F4E-B09FFF46A070}

^{[Intel CPU MicroCode]}
^{F - Find and Replace from MCUpdate.txt}
^{V - View/Edit MCUpdate.txt}
^{U - Find and Replace from USR_mCode.txt}
^{E - View/Edit USR_mCode.txt}

^{[MC Extractor]}
^{X - Extract all CPU microcodes}
^{S - Search for available microcode in DB.}
^{0 - Exit to Main Menu}
^Choice:F
^{CPUID 906EA found.}
^{Files\Intel\mcode\1151v2\cpu906EA_plat22_ver000000F8_2024-02-01_PRD_47291E44.bin}
^{Checksum correct.}
^{CPUID 906EB found.}
^{Files\Intel\mcode\1151v2\cpu906EB_plat02_ver000000F6_2024-02-01_PRD_9F8FF344.bin}
^{Checksum correct.}
^{CPUID 906EC found.}
^{Files\Intel\mcode\1151v2\cpu906EC_plat22_ver000000F4_2023-02-23_PRD_2EDF8103.bin}
^{Checksum correct.}
^{CPUID 906ED found.}
^{Files\Intel\mcode\1151v2\cpu906ED_plat22_ver00000100_2024-02-05_PRD_78F54C97.bin}
^{Checksum correct.}
^{Generate FFS with Microcode}

^{╔═══════════════════════════════════════════╗}
^{║ MC Extractor v1.94.2 r276 ║}
^{╚═══════════════════════════════════════════╝}

^{bios.bin (1/2)}

^{╔════════════════════════════════════════════════════════════════════════════════════════════════╗}
^{║ Intel ║}
^{╟───┬───────────┬───────┬───────────┬──────────┬────────────┬───────┬─────────┬───────────┬──────╢}
^{║ # │ Type │ CPUID │ Platforms │ Revision │ Date │ State │ Size │ Offset │ Last ║}
^{╟───┼───────────┼───────┼───────────┼──────────┼────────────┼───────┼─────────┼───────────┼──────╢}
^{║ 1 │ Microcode │ 906EA │ 22 (1,5) │ F4 │ 2023-02-23 │ PRD │ 0x19800 │ 0x1D50400 │ Yes ║}
^{╟───┼───────────┼───────┼───────────┼──────────┼────────────┼───────┼─────────┼───────────┼──────╢}
^{║ 2 │ Microcode │ 906EB │ 02 (1) │ F4 │ 2023-02-23 │ PRD │ 0x1A000 │ 0x1D69C00 │ Yes ║}
^{╟───┼───────────┼───────┼───────────┼──────────┼────────────┼───────┼─────────┼───────────┼──────╢}
^{║ 3 │ Microcode │ 906EC │ 22 (1,5) │ F4 │ 2023-02-23 │ PRD │ 0x19C00 │ 0x1D83C00 │ Yes ║}
^{╟───┼───────────┼───────┼───────────┼──────────┼────────────┼───────┼─────────┼───────────┼──────╢}
^{║ 4 │ Microcode │ 906ED │ 22 (1,5) │ FA │ 2023-02-27 │ PRD │ 0x1A000 │ 0x1D9D800 │ Yes ║}
^{╚═══╧═══════════╧═══════╧═══════════╧══════════╧════════════╧═══════╧═════════╧═══════════╧══════╝}

^{mCode.ffs (2/2)}

^{╔══════════════════════════════════════════════════════════════════════════════════════════════╗}
^{║ Intel ║}
^{╟───┬───────────┬───────┬───────────┬──────────┬────────────┬───────┬─────────┬─────────┬──────╢}
^{║ # │ Type │ CPUID │ Platforms │ Revision │ Date │ State │ Size │ Offset │ Last ║}
^{╟───┼───────────┼───────┼───────────┼──────────┼────────────┼───────┼─────────┼─────────┼──────╢}
^{║ 1 │ Microcode │ 906EA │ 22 (1,5) │ F8 │ 2024-02-01 │ PRD │ 0x19C00 │ 0x18 │ Yes ║}
^{╟───┼───────────┼───────┼───────────┼──────────┼────────────┼───────┼─────────┼─────────┼──────╢}
^{║ 2 │ Microcode │ 906EB │ 02 (1) │ F6 │ 2024-02-01 │ PRD │ 0x1A000 │ 0x19C18 │ Yes ║}
^{╟───┼───────────┼───────┼───────────┼──────────┼────────────┼───────┼─────────┼─────────┼──────╢}
^{║ 3 │ Microcode │ 906EC │ 22 (1,5) │ F4 │ 2023-02-23 │ PRD │ 0x19C00 │ 0x33C18 │ Yes ║}
^{╟───┼───────────┼───────┼───────────┼──────────┼────────────┼───────┼─────────┼─────────┼──────╢}
^{║ 4 │ Microcode │ 906ED │ 22 (1,5) │ 100 │ 2024-02-05 │ PRD │ 0x1A000 │ 0x4D818 │ Yes ║}
^{╚═══╧═══════════╧═══════╧═══════════╧══════════╧════════════╧═══════╧═════════╧═════════╧══════╝}

^{Note: Microcode #1 is not in the database! You can help this project}
^{by sharing it at https://win-raid.com forum. Thank you!}

^{Note: Microcode #2 is not in the database! You can help this project}
^{by sharing it at https://win-raid.com forum. Thank you!}

^{Note: Microcode #4 is not in the database! You can help this project}
^{by sharing it at https://win-raid.com forum. Thank you!}
^{These microcodes will be entered into your BIOS file}

^{R - Start replacement}
^{0 - Cancel}
^Choice:R
^{[Preparing for replacement]}
^{BIOS file backup}
^{mCode GUID: GUID replaced}
^{[Replacement]}
^{mCode FFS: File replaced}
^{Real Pointer}
^{FIT Offset - FFD50100 == FFD50100}

^{Real FIT}
^{Press any key to continue . . .}

^{╔═════════════════════════════════════════╗}
^{║ MC Extractor v1.94.2 r276 ║}
^{╚═════════════════════════════════════════╝}
^{╔════════════════════════════════════════════════════════════════════════════╗}
^{║ Intel ║}
^{╟─┬─────────┬─────┬─────────┬────────┬──────────┬─────┬───────┬─────────┬────╢}
^{║#│ Type │CPUID│Platforms│Revision│ Date │State│ Size │ Offset │Last║}
^{╟─┼─────────┼─────┼─────────┼────────┼──────────┼─────┼───────┼─────────┼────╢}
^{║1│Microcode│906EA│ 22 (1,5)│ F4 │2023-02-23│ PRD │0x19800│0x1D50400│Yes ║}
^{╟─┼─────────┼─────┼─────────┼────────┼──────────┼─────┼───────┼─────────┼────╢}
^{║2│Microcode│906EB│ 02 (1) │ F4 │2023-02-23│ PRD │0x1A000│0x1D69C00│Yes ║}
^{╟─┼─────────┼─────┼─────────┼────────┼──────────┼─────┼───────┼─────────┼────╢}
^{║3│Microcode│906EC│ 22 (1,5)│ F4 │2023-02-23│ PRD │0x19C00│0x1D83C00│Yes ║}
^{╟─┼─────────┼─────┼─────────┼────────┼──────────┼─────┼───────┼─────────┼────╢}
^{║4│Microcode│906ED│ 22 (1,5)│ FA │2023-02-27│ PRD │0x1A000│0x1D9D800│Yes ║}
^{╚═╧═════════╧═════╧═════════╧════════╧══════════╧═════╧═══════╧═════════╧════╝}
^{These microcodes are in your BIOS file}
^{GUID 17088572-377F-44EF-8F4E-B09FFF46A070}

^{[Intel CPU MicroCode]}
^{F - Find and Replace from MCUpdate.txt}
^{V - View/Edit MCUpdate.txt}
^{U - Find and Replace from USR_mCode.txt}
^{E - View/Edit USR_mCode.txt}

^{[MC Extractor]}
^{X - Extract all CPU microcodes}
^{S - Search for available microcode in DB.}
^{0 - Exit to Main Menu}
^Choice:

EFI Realtek UNDI Driver - Unknown and MC replacement is off in a15.

Edit by Fernando: Post’s length shrinked by putting the details into a “spoiler”