Asrock Fatal1ty Z370 Gaming K6. When I try to flash the modified by UBU_v1_70_rc14_2 UEFI, it says "Secure Check Failed". I am trying the newest UEFI, which is version 3.20.

@Ruin

Hello.
If possible, please check languages with EFI LAN PRO/1000 v8.4.09.

Edit:
Attach deleted.

The option rom downloaded from this forum says for device 2822. However, my AHCI device ID is 1C02.

The older Ubutool version correctly shows both an OROM and an EFI module.

The new one only shows an UEFI module.

I used the old ubutool and updated both to 12.x

When updating the non-URFI module it said something about a DevID 282a. Will this work?

@bobypf - [Discussion] UBU Tool related Questions, Reports and Suggestions (297) (One page back)

Thank you! Yes, I read it, but it sounds a bit too complicated and I am not sure it's worth the effort. Hopefully Sonix will find a way to circumvent the protection in his UBU Tool.

Zitat von SoniX im Beitrag #4458

---

@Ruin
If possible, please check languages with EFI LAN PRO/1000 v8.4.09.

---

@SoniX
When I use UBU to update the following;

EFI IRST
EFI GOP Driver HSW-BDW
EFI Lx Killer

I get these messages:
parseSection: PE32 image with invalid DOS signature
parseSection: PE32 image with invalid DOS signature
parseSection: PE32 image with invalid DOS signature
parseSection: PE32 image with invalid DOS signature
parseSection: PE32 image with invalid DOS signature
parseSection: PE32 image with invalid DOS signature
parseSection: PE32 image with invalid DOS signature
parseSection: PE32 image with invalid DOS signature
File replaced

Is this normal?

@Spindle [Discussion] UBU Tool related Questions, Reports and Suggestions (297)

Zitat von mockingbird im Beitrag #4459

---

The option rom downloaded from this forum says for device 2822. However, my AHCI device ID is 1C02.

The older Ubutool version correctly shows both an OROM and an EFI module.

The new one only shows an UEFI module.

I used the old ubutool and updated both to 12.x

When updating the non-URFI module it said something about a DevID 282a. Will this work?

---

@SoniX

I have downloaded mainly and tested latest AMD 990FX chipset based various mainboard bioses from MSI 3, Asus 7, Gigabyte 7+, (I will give full detail at the bottom, there might be more.)

Sadly, none of those mainboard's CPU microcode updates are upgradeable by UBU! They all can support AMD FX-8xxx and some of them FX-9xxx serie. Those mainboards have Spectre patches, but none of their microcodes are upgradeable by UBU.

Their CPU microcodes are present inside CSMCORE and there is no utility to modify this file for CPU upgrade. UBU can only extract microcodes by pressing X.

There are many other lower chipsets other than 990FX like 990X, 970, 8xx etc. seemingly they all are at the same situation.

Can you please work for CPU microcode modification(s) for this CSMCORE file? (Actually there are many more things in it for upgrading, as you know.)
There is an urgent need for CSMCORE modifying tool!

Thanks in advance....

My tested ones:
MSI 990FX chipset: 990FXA-GD90, 990FXA-GD65, 990FXA Gaming....
Asus 990FX chipset: Sabertooth, Sabertooth R2, Sabertooth Gen 3 R2, Sabertooth R3, M5A99FX PRO R2.0, Formula V, Formula V Z....
Gigabyte 990FX chipset: GA-990FXA-UD7, GA-990FXA-UD5, GA-990FXA-UD5 R5, GA-990FXA-UD3, GA-990FXA-UD3 R5, GA-990FXA-UD3 Ultra, GA-990FX Gaming.... (+ = I have also tested various pcb bios revisions 1.x, 2.x, 3.x etc.)

Note: I have found a manual way, explaining how to do it! --> Need help to update Microcode for FX-8350 on AMD 990FX-Board

Did the above job manually with HxD Hex editor.

Erased: cpu00600F20_ver06000822_2013-01-03_8690F440.bin
İnserted: cpu00600F20_ver06000852_2018-02-06_893C1544.bin

saved, tried to check it with the latest UBU version UBU_v1.70.rc14.2_without-MMTool, used patched version of MMTool_v5.02.0024 but when reading, it said:

The input image is not Aptio V. --> Closed the window,
At Ubu window appeared --> ^CTerminate batch job (Y/N)? --> Pressed N, checked the result, well my insertion was successful.

I have tried to saved the modified cap file as bios.bin but after running UBU again, same error repeated!

I have replaced the .bin file correctly, checked the size, Length(h): 800800 unchanged, repeated "paste insert" 3 times, by freshly starting every time on Hex editor to be sure, on my SABERTOOTH-990FX-GEN3-R20-ASUS-2501.CAP bios file.

What to think about for this error?

Lately, I have tried the same job with using unpatched MMTool_v5.02.0024, no error messages displayed this time!



@Lost_N_BIOS those are not off topic. Probably you did not read it well....

@karakarga

OROM VBIOS Carrizo @ 015.048.000.071
(old @ 015.048.000.070.007160)

Does it make sense to update a bios every time a new version of UBU is released and includes updated CPU Microcodes? In other words should a bios contain the latest CPU Microcodes?

@kyriacos
If you are satisfied with the microcode version in the new BIOS file, it is not boring to update.