[Discussion] UBU Tool related Questions/Reports/Suggestions

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

2 Likes

Thank you very much for informing me this Github respositories. :smiling_face_with_three_hearts:

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

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)

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

1 Like

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.

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

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

1 Like

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

1 Like

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.

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”

@ChrisM

Send this BIOS file.

1 Like

To all UBU users.
Please just describe the problem and attach the BIOS file or link.

Example:

-The GOP Driver file is not being replaced
The version is not defined.
-<“BIOS file”>

Thank you all very much,

2 Likes

This is the FPT dumped full bios.

Dell Vostro 3670 2.33.zip (7.8 MB)

As a side note, when I downloaded your entire (a15) Modding.rar, the UBU_v1_80_a15.rar wouldn’t open, so I downloaded the UBU_v1_80_a15.rar individually, and it did open/extract.

-The intel EFI GOP Driver Xe file is not being replaced
I found the BIOS of both Z590 mobos share the same issue.

Sorry the BIOS file size is too big for the forum limitation. I linked it to MEGA cloud.
ASUS ROG Maximus XIII BIOS file link

Gigabye Z590 Aorus Elite

@ThomasRhin

I am aware of this problem of two different versions of the GOP,

Try the following:

  1. Open UBU.cmd
  2. Find string 31003700
  3. Change the entire line
set str_patt=310037000000000000000000

This should help you

2 Likes

@SoniX

Unfortunately, the microcode update hasn’t been working since version 1.80a14. ASRock Z790 Pro RS…
The MMTool variant doesn’t seem to be in order.

Z790ProRS14.01

@RoadrunnerDB

Works with mmtool_a5.exe (v5.2.0.25).

1 Like

I placed both MMT 5.2.0.24 and 5.2.0.25 directly into the UBU folder. This time, the script indicated it was using MMT 5.2.0.24 (which makes sense given my carryover thread post), and the microcodes were replaced.

I’m still having the removed Padding file issue, but MC replacement did process in the UBU a15 folder with the inclusion of MMTool 5.2.0.24.

Still getting the EFI Realtek UNDI Driver - Unknown issue.

I completely forgot that AMI doesn’t want it to be distributed.

But there’s a new problem.

@SoniX

Network Realtek modules are not being swapped. The CMD stops, see the image!