Hello everyone,

I wanted to report that the BIOS generated by UBU v1.43 gives me a "Selected file is not a proper BIOS!" when trying to update (I cannot force update via flashback either). The motherboard in question is a R5E and I update UEFI IRST / LAN via UBU and the ROM IRST manually. Previous versions work fine.

EDIT: The BIOS worked via flashback after I completely disabled power, entered BIOS and rebooted. I believe it was a problem with CMOS, maybe I accidentally hit the clear button - doing so will result in flashback not working until the user enters the BIOS at least once.

Hi,

Wondering does UBU add the ffs files neccessary for NVME drive support into bios? Is this a feature to look forward to?

Thank you

Why cpu microcode update, sata orom and efi update create in my x99 champion problem?
Today i had to reset bios and update with normal bios without rom update

Zitat von Fernando im Beitrag #2159

---

Zitat von pipes80 im Beitrag #2158

---

Why cpu microcode update, sata orom and efi update create in my x99 champion problem?

---

The problems are not UBU related. They are caused by the Company American Megatrends (AMI), whose Aptio V MMTool doesn't work properly, and by the mainboard manufacturers, who are trying to prevent, that the BIOSes for their newest mainboards will be modified by the users.

---

Hi guys,
This is my report:
UBU: 1.43
MB: MSI H81M-E33
CPU: Pentium G3258
Bios: 6.7
RST Driver: 14.8.0.1042
Win 10: 1511 Build 10586.17 x64

----UBU INFO----
1 Intel RST(e) OROM and EFI SataDriver
OROM IRST RAID for SATA - 14.8.0.2377
EFI IRST RAID for SATA - 14.8.0.2377
2 Intel OROM VBIOS and EFI GOP Driver
OROM VBIOS Haswell - 1038
EFI GOP Driver Broadwell - 5.5.1033
3 LAN OROM PXE and EFI UNDI - Intel, Realtek, BCM, QCA
OROM Intel Boot Agent CL - 0.1.06
OROM Realtek Boot Agent - 2.63
EFI Realtek UNDI - 2.035
7 Update Intel CPU MicroCode Haswell/Broadwell
CPU Microcode 0306C3 HSW - 19

Flashed using Afuwin64 - Programming All Blocks checked

Status: OK, no problems.

Thanks.

Reporting UBU v1.43 Updt 1 using Asus USB Flashback on my (legacy mode) machine:

Success:
-8086-0102 Intel Sandy-Ivy VBIOS 2171
-EFI GOP Driver IvyBridge v3.0.1030
-EFI SATA Marvell AHCI v1.1.0.1020
-OROM LAN Intel Agent Boot CL v0.1.06 (82579/i217/218/219)
-OROM LAN Realtek PXE v2.64
-CPU Microcode ver 1C for CPU IvyBridge (LGA1155)...



Thanks!

PS: seems no probs with VBIOS 2171, no black screen, as i also using GPU Virtualization (iGpu & dGpu).

Hi guys,
New Report:
UBU: 1.43 U1
MB: Asus P8H77-V-LE
CPU: Core i3-3240
Bios: 1307
CentOS Linux release 7.1.1503
ME: 8.1.65.1586

Success:
1 Intel RST(e) OROM and EFI SataDriver
OROM IRST RAID for SATA - 14.8.0.2377
EFI IRST RAID for SATA - 14.8.0.2377
2 Intel OROM VBIOS and EFI GOP Driver
OROM VBIOS Sandy/IvyBridge - 2143
EFI GOP Driver IvyBridge - 3.0.1030
EFI GOP Driver SandyBridge - 2.0.1024
3 LAN OROM PXE and EFI UNDI - Intel, Realtek, BCM, QCA
OROM Intel Boot Agent CL - 0.1.06
OROM Realtek Boot Agent - 2.64
EFI Realtek UNDI - 2.035
7 Update Intel CPU MicroCode SandyBridge/IvyBridge
CPU Microcode 0306A9 IVB - 1C
CPU Microcode 0206A7 SNB - 29

Had to downgrade to the 608 bios (1307 -> 608) using the EzFlash feature to unlock de SPI, then booted DOS and flashed the modded bios with FTK.
Status: OK, no problems.

UEFIFind 0.10.4.1:
- solved a problem with error codes interpreted as chars
- updated to the new engine
UPD: uploaded fixed version, please redownload and reintegrate.

@SoniX What is the correct GUID so I can update Realtek OROM using UEFITool on a Gigabyte Z170 Aptio V BIOS?

Zitat von rootuser123 im Beitrag #2165

---

@SoniX What is the correct GUID so I can update Realtek OROM using UEFITool on a Gigabyte Z170 Aptio V BIOS?

---

Is the new UEFITool 0.30.0 alpha16 safe to use for modding or is it better to use the original UEFITool 0.21.x for now?

@sinders, you can't mod anything with 0.30 alphas, because the only operations supported are "Extract as is" and "Extract body" (image rebuild code is just not ready yet).
The goal is to test the new parser and to see the new functions like physical address calculation, more information about items and so on.
Because UEFIExtract and UEFIFind are both only parsers, they are already using the new engine (that is why their version numbers are 0.10.x now), but UEFITool and UEFIPatch will use the old one until I get enough time to finish my work on ffsbuilder.