A post was split to a new topic: Using the UEFITool_NE_A68
Thank you very much for replying . I have tried both UBU a14 and a15, and , yes , UBU could replace Intel EFI GOT Xe driver after modifying the strip. However, both Gigabyte Z590 Aorus Elite and Asus Maximus XIII will experience boot failure after flashing the modified BIOS with EFI GOP Xe driver replaced. If the GOP Xe driver remains untouched, everything will be fine. I can confirm it because I have experimented it on both motherboards for almost 10 times. Besides, the UBU always generates 3 GOP Xe drivers as shown in the attachment of screenshot. I don’t know if repeated Xe drivers count for boot failure because the debug code of ASUS mobo indicates it is I/O related. Again , the link of the BIOS.
3 GOP is bad. I’ll think about it,
SoniX, thanks for looking at that Dell Vostro 3670 bios. The first mis-flash was a head-scratcher. I’ll have to play with a hex editor - was trying to avoid that, and it still may be a bridge too far.
This will be an issue for the Dell Inspiron 3670 also, and probably all Dell computers that have the Winbond W25Q256JV 32MB bios chip.
Users recently reporting several issues with UBU and other tools pointed on the forum, need to understand the “main” issue here…specially regarding the biggest percentage of bios AMI Core based…
There is NO RECENT “leaks” to the web of these tools, since the past Aptio IV based bios, to deal with recent Aptio V bios structures/advances, this was 10yrs ago and that’s a “Century” in this area of innovation.
Resulting this in several modifications to the users files getting bad bios mods, by using these tools…the only versions available but not suitable for modern bioses.
Many volumes/modules can be touched and the user don’t have the clue on what was moved/deleted/modified…
These shared user developed tools are always tied to the manipulation of the bios vendor main code and the task becomes much harder…(don’t want to say impossible) when such tools are part of the project and there’s no technical information “outside” for guidance and building.
With this i just want to pass the message, be patient and don’t expect “fix” for all issues, at least in a shorth time period and think on the developer user passion… on the other side, that may not have the time, the health and the age/spirit from other times…
RTK UNDI 2.039
Alius optio:
set str_patt=00000000000000000000000000000000409A499A599A609AIf it finds more GOP, then add 00 to the beginning of the line.
1 Like
My CPU is i9-11900K and i5-11600K ,both come with built-in UHD750 iGPU. I have tried with or without adding 00 to the beginning of the strip line. This time,UBU does replace the GOP Xe driver correctly. There is no repeated or redundant replacement. My Z590 mobos did successful boot with a “beep” sound. Unfortunately, I got a blank screen after the “beep” sound and then boot procedure stopped. It seems the modified BIOS is accepted by the mobo and passes the self tests in the BIOS initialization. However, something wrong occurred to load the GOP Xe driver , which results in blank screen. I tested the GOP Xe 17.0.1085 driver in another LGA 1700 Z790 platform(i9-14900KS, UHD770 iGPU) without any modification in the UBU.cmd strip line and it works just fine. I assume the GOP Xe 17.0.1085 driver is universal to UHD750 and UHD770, but i don’t know why it works in Z790 platform but not in Z590 platform.
What are the VBT versions of each board?
1 Like
There is no point in offering a replace here, as you have nothing to replace. Lenovo BIOS + EFI file. Is the i219 EFI some new file? I can’t find an older version in my own collection. Of course, it could also be that I haven’t looked enough at Lenovo BIOSes.
a15_DVfix
I have corrected the DrvVer for old Realtek LAN, but it is possible that versions 050-056 will not be detected.
Edit:/Add
a15_DVfix2
1 Like
It recognizes it, but it does not display the real version number. v2.050 to v2.057 (not up to 56) will display the same non-real version (8.04F BD). However, the current state is better than the previous one, since the UBU can now replace the file. It replaces the “good” with the “bad” and vice versa.
Tested:
2.010, 2.013, 2.015, 2.021, 2.022, 2.023, 2.026, 2.027, 2.028, 2.030, 2.034, 2.035, 2.036, 2.037, 2.039, 2.040, 2.041, 2.042, 2.043, 2.044, 2.045, 2.046, 2.048, 2.049, 2.050, 2.052, 2.053, 2.054, 2.055, 2.056, 2.057, 2.058, 2.059, 2.060, 2.061, 2.063, 2.064, 2.065, 2.066, 2.067
mod: with fix2 almost everything works. There are two “different” files that you probably haven’t come across (53, 54). They still show up incorrectly. I also have two types of files from 56, but both are well displayed.
realtek_efi.rar (70.5 KB)
SoniX, I have attached infos of both BIOS as following.
ASUS Maximus XIII(Z590)
Gigabyte Z590 Aorus Elite.
UEFI BIOS Updater v1.80.a16
Changelog:
Added the option to use MMTool for files.Updated:
DrvVer 0.31.1.4 mCodes LGA 1151v2
Using mmtool_a5 and bypassing microcodes, no issues/problems.
a16 run:
Summary
Scanning BIOS file backupa.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-F820FBBA180EUEFIReplace v0.25.0 will be used.
MMTool Aptio v5.02.0024You will use MMTool?0 - Do not use MMTool. (As in UBU v1.7x).
1 - Use MMTool. (If, after replacement without MMTool, XMP, OC, etc. do not work,)
Choice:1
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 - 2.041
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:1
Disk Controller
[Current version]
EFI Intel RST RAID Driver - 17.8.1.4572[Available version] EFI Intel RST RAID Driver - 17.8.4.46711 - Replace
X - Extracted
0 - Exit to Main Menu
Choice:1Intel RST GUID 8C2E10DB-280F-4D4C-9B6E-C4C2A8A4C629
parseIntelImage: unknown flash descriptor version 0.0
parseVolume: non-UEFI data found in volume’s free space
parseSection: section with unknown type 00h
parseSection: section with unknown type 00h
parseSection: section with unknown type 1Ah
parseFile: non-empty pad-file contents will be destroyed after volume modifications
reconstructIntelImage: discovered unexpected 0.0 descriptor version, trying to continue…
File replaced
Rebuilding GUID 8C2E10DB-280F-4D4C-9B6E-C4C2A8A4C629. Wait…
Done.EFI Intel RST RAID Driver - 17.8.4.4671Press any key to continue . . .
Video OnBoard [Current version] EFI GOP Driver SKL-AML - 9.0.1085 RAW GOP VBT SKYLAKE - 221 [Available version] EFI GOP Driver SKL-CML - 9.0.11131 - Replace GOP Driver
X - Extracted
0 - Exit to Main Menu
Choice:1
Intel GOP Driver SubGUID D8248140-88B5-4C14-9E9F-FD1CFA9D071E
parseIntelImage: unknown flash descriptor version 0.0
parseVolume: non-UEFI data found in volume’s free space
parseSection: section with unknown type 00h
parseSection: section with unknown type 00h
parseSection: section with unknown type 1Ah
parseFile: non-empty pad-file contents will be destroyed after volume modifications
reconstructIntelImage: discovered unexpected 0.0 descriptor version, trying to continue…
File replaced
Rebuilding GUID 26061B47-0B90-4FB4-A0D7-DA89B4AED49B. Wait…
Done.EFI GOP Driver SKL-CML - 9.0.1113 RAW GOP VBT SKYLAKE - 221Press any key to continue . . .
Network [Current version] EFI Realtek UNDI Driver - 2.041 [Available version] EFI Realtek UNDI Driver - 2.0672 - Replace Realtek
X - Extracted
0 - Exit to Main Menu
Choice:2
Realtek GUID 4953F720-006D-41F5-990D-0AC7742ABB60
parseIntelImage: unknown flash descriptor version 0.0
parseVolume: non-UEFI data found in volume’s free space
parseSection: section with unknown type 00h
parseSection: section with unknown type 00h
parseSection: section with unknown type 1Ah
parseFile: non-empty pad-file contents will be destroyed after volume modifications
reconstructIntelImage: discovered unexpected 0.0 descriptor version, trying to continue…
File replaced
Rebuilding GUID 4953F720-006D-41F5-990D-0AC7742ABB60. Wait…
Done.EFI Realtek UNDI Driver - 2.067Press any key to continue . . .
Main Menu [Current version in BIOS file]1 - Disk Controller
EFI Intel RST RAID Driver - 17.8.4.4671
EFI NVMe Driver present
2 - Video OnBoard
EFI GOP Driver SKL-CML - 9.0.1113
RAW GOP VBT SKYLAKE - 221
3 - Network
EFI Realtek UNDI Driver - 2.067
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:0
Yes, I did mention that another Z790 mobo(ASUS Z790 Dark hero) works just fine with the GOP Xe driver replaced. The GOP/VBT info is as following. Thank you for further investgation.
I think this is a similar situation with GOP 9.0.1082. Necesitaba una versión VBT 221 o superior…
In your case, VBT 237 and 240 are installed on the Z590, and 250 on the Z790.
In order for GOP 17 to work correctly on different chipsets, you need to search and check all versions from 1060 to 1084.
1 Like