Overclock.net - An Overclocking Community - Reply to Topic

Thread: Ryzen BIOS mods + how to update BIOS correctly Reply to Thread
Title:
Message:

Register Now

In order to be able to post messages on the Overclock.net - An Overclocking Community forums, you must first register.
Please enter your desired user name, your email address and other required details in the form below.
User Name:
If you do not want to register, fill this field only and the name will be used as user name for your post.
Password
Please enter a password for your user account. Note that passwords are case-sensitive.
Password:
Confirm Password:
Email Address
Please enter a valid email address for yourself.
Email Address:

Log-in


  Additional Options
Miscellaneous Options

  Topic Review (Newest First)
07-22-2019 10:14 PM
numlock66 @Erick Aguero , I realy think Asrock put protections like digital signature to his BIOS so the only way to flash modded BIOS is throughout an external programmer like ch341a.
07-22-2019 07:02 PM
Erick Aguero I found the fTPM option, it was under Advanced\CPU Configuration\AMD fTPM switch
But it was already disabled.

No luck.
I tried the "EFI Shell from device filesystem" in the EXIT menu in UEFI BIOS, but it print an error saying "Warning. Not Found".
So, I can only boot the EFI Shell from the USB.
Really weird.



Quote: Originally Posted by Veii View Post
Hmm i see

It should erase a tiny capsule there, ubu does it properly
Just i wonder why doesn't the board let you flash it
Can you check, in your bios you have an "anti bios flash" feature something similar like tTPM (idk how much i messed up it's name)
Disable that one and use the first colum of usb ports , either the first top or bottom
If it still doesn't let you reflash the official "edited" bios - try to use the EFI Shell started directly from the bios (without exiting the bios - next to the save & exit button)
Maybe it will give you then permissions to flash

i feel you, have the same issue with my Toma - but that's a controller flaw, it's compensatable with some LLC
On my toma it let's me adjust it in 0.1v steps, on the taichi it accepted 0.05v steps
I don't know if we can do anything about this at all - 1usmus should know better
I think so far it's a pure controller limitation

Overall keep us up to date - maybe you need to downgrade first one step
Then flash the "new" official one without their verification check injected - and afterwards only theh mod
Tho /X should fully clean it - i think tTPM or similar , is just enabled on your side / asrock bioses do have that switch
Just wait so far with EFI & GOP / only microcodes and PMU
07-22-2019 01:07 PM
Veii
Quote: Originally Posted by Erick Aguero View Post
Hi, I'm still having problems, this is what I did

I put the original BIOS (downloaded from the ASRock site) through UBU, the tool made its thing, I made no modifications and just exited the tool and asked for to rename the BIOS file to BIOS.BIN

With this file I tried the command
Afuefix64.efi BIOS.BIN /P /B /N /K /X /CLRCFG
And the output was:
Code:
1e - Error: Secure Flash function is not supported on this file.
I noticed that something gets changed in UBU process because the CRC32 of the original file and the BIOS.BIN file are different. If I compare both files, the BIOS.BIN has 4096 bytes changed to 0xF.
The exact DATA correspond to a section in the BIOS with the following GUID
5A88641B-BBB9-4AA6-80F7-498AE407C31F
This is the info in UEFITool for that section
Code:
Type: 18h
Full size: 1014h (4116)
Header size: 14h (20)
Body size: 1000h (4096)
Subtype GUID: 5A88641B-BBB9-4AA6-80F7-498AE407C31F
In the BIOS.BIN file, this whole section is just filled with 0xF.
Hmm i see
It should erase a tiny capsule there, ubu does it properly
Just i wonder why doesn't the board let you flash it
Can you check, in your bios you have an "anti bios flash" feature something similar like tTPM (idk how much i messed up it's name)
Disable that one and use the first colum of usb ports , either the first top or bottom
If it still doesn't let you reflash the official "edited" bios - try to use the EFI Shell started directly from the bios (without exiting the bios - next to the save & exit button)
Maybe it will give you then permissions to flash
Quote: Originally Posted by Erick Aguero View Post
Actually it was my own "custom" BIOS, but it didn't have any active modification, I just wanted to update the microcode, EFI drives & GOP modules.
I just wanna to start with that, later I was thinking if it would be possible to change the behavior of the official BIOS in respect to the DRAM voltage settings. In my board, the user cannot input a fine grained value for the DRAM voltage, you just select from pre-selected values in a combo list from values that change in 0.05 increments, let's say 1.20, 1.25, 1.30, 1.35, 1.40 and so on. So, it's not possible to enter, let's say 1.36V.
But all this was for a later round, I cannot even flash a simple microcode update.
i feel you, have the same issue with my Toma - but that's a controller flaw, it's compensatable with some LLC
On my toma it let's me adjust it in 0.1v steps, on the taichi it accepted 0.05v steps
I don't know if we can do anything about this at all - 1usmus should know better
I think so far it's a pure controller limitation

Overall keep us up to date - maybe you need to downgrade first one step
Then flash the "new" official one without their verification check injected - and afterwards only theh mod
Tho /X should fully clean it - i think tTPM or similar , is just enabled on your side / asrock bioses do have that switch
Just wait so far with EFI & GOP / only microcodes and PMU
07-21-2019 10:24 PM
Erick Aguero Hi, I'm still having problems, this is what I did

I put the original BIOS (downloaded from the ASRock site) through UBU, the tool made its thing, I made no modifications and just exited the tool and asked for to rename the BIOS file to BIOS.BIN

With this file I tried the command
Afuefix64.efi BIOS.BIN /P /B /N /K /X /CLRCFG
And the output was:
Code:
1e - Error: Secure Flash function is not supported on this file.
I noticed that something gets changed in UBU process because the CRC32 of the original file and the BIOS.BIN file are different. If I compare both files, the BIOS.BIN has 4096 bytes changed to 0xF.
The exact DATA correspond to a section in the BIOS with the following GUID
5A88641B-BBB9-4AA6-80F7-498AE407C31F
This is the info in UEFITool for that section
Code:
Type: 18h
Full size: 1014h (4116)
Header size: 14h (20)
Body size: 1000h (4096)
Subtype GUID: 5A88641B-BBB9-4AA6-80F7-498AE407C31F
In the BIOS.BIN file, this whole section is just filled with 0xF.
This is the output of the UBU while it unpack the original BIOS file
Code:
Scanning BIOS file X47GIA_3.30.
Please wait...
BIOS platform - AMI Aptio V
Manufacturer  - ASRock
Model         - X470 Gaming-ITX/ac

        [EFI  Drivers - Find and Extract]
AMD GOP SubGUID 12FA6BCD-E5C0-4E61-8BC6-3876EC6C2083
AMD RAIDXpert2 GUID C74F06D2-ED92-489B-879C-C0E428A22167
AMI NVMe GUID 634E8DB5-C432-43BE-A653-9CA2922CC458
Intel 1Gb GUID 48392194-D155-4567-9AAF-FA805BAEEC6C
Intel 1Gb GUID 9006872D-3A86-4BAE-A2F0-E527B9D7119E
Broadcom Undi GUID 4DD4DF07-3278-406F-B5DE-EC7EECC650E1

        [OROM  - Find and Extract]
VBIOS in SubGUID 12BF5331-4DF7-4CA8-9C7F-155EF4A67A3A
VBIOS in SubGUID 2EEB6B7E-F112-4350-AB72-ADEC3840255C
VBIOS in SubGUID 430A34B2-65F8-4C0A-B765-E02ADEC8DD63
OROM in GUID A0327FE0-1FDA-4E5B-905D-B510C45A61D0
OROM in GUID A0327FE0-1FDA-4E5B-905D-B510C45A61D0
OROM in GUID A0327FE0-1FDA-4E5B-905D-B510C45A61D0
Press any key to continue . . .
And about where I get it, I think it's my mistake I didn't explain myself properly.

Actually it was my own "custom" BIOS, but it didn't have any active modification, I just wanted to update the microcode, EFI drives & GOP modules.
I just wanna to start with that, later I was thinking if it would be possible to change the behavior of the official BIOS in respect to the DRAM voltage settings. In my board, the user cannot input a fine grained value for the DRAM voltage, you just select from pre-selected values in a combo list from values that change in 0.05 increments, let's say 1.20, 1.25, 1.30, 1.35, 1.40 and so on. So, it's not possible to enter, let's say 1.36V.
But all this was for a later round, I cannot even flash a simple microcode update.



Any suggestions?


Quote: Originally Posted by Veii View Post
Hey, somewhere glad it didn't pass trough
/X does erase every capsule and fully replaces it with the current flashed bios
AFUGAN is there to bypass ASUS's verification check (quote me on that with the exact location of it)
ASRock has also a capsuled bios like Asus (I think current MSI ones are capsuled too)

The reason you use AFUGAN after flashing the official bios, is to keep the integrity in tact on ASUS Boards
(also quote me on that with the exact description)
ASRock has a verification capsule in all of their official BIOSes - which the user needs to remove and "decapsule" the bios
To do that normally you have to UUID edit as mentioned in post #1367 or put the bios file once through UBU.bat - to remove that integrity check
Afterwards you just flash it via Afuefix64 over the normal bios without /X and without /CLRCFG

If issues still remain and you continue to get integrity check issues
- push first the official bios trough UBU (just load it and export as .bin) & flash it clean with /X
- then later push your mod through the same procedure just to be sure & flash it without /X - imo you can check microcode updates too
* just don't update any EFI "packages" & GOP so far, as it can mess stuff up ^^#

Oh may I ask you where you got ASRock bios mods ?
Did some active modder appear ?
07-21-2019 04:52 PM
Axilya I would like to modify "Max CPU Boost Clock Override" value for Precision Boost Overdrive on ASUS X370 Crosshair VI, BIOS: 7201. I attempted to look for that exact string with AMIBCP with no success. I am absolutely new to this.

How can I do that?
07-21-2019 02:25 PM
BUFUMAN Yeah we need some mods crosshair VI without hpet please.

Or a easy manual how to mod this rom.

Gesendet von meinem LYA-L29 mit Tapatalk
07-21-2019 12:26 PM
Veii
Quote: Originally Posted by Erick Aguero View Post
Hi, I'm having problem flashing modded BIOS for an ASRock Fatal1ty X470 Gaming-ITX/ac
If I use

Afugan.efi MODDED.ROM /GAN

I end up with this error:
Code:
46 - Error: Problem getting flash information.
I tried the suggestion on this thread to use the 1st command with the modded BIOS file

Afuefix64.efi MODDED.ROM /P /B /N /K /X /CLRCFG

But I end with the following error:
Code:
1e - Error: Secure Flash function is not supported on this file.
Any suggestion?
Hey, somewhere glad it didn't pass trough
/X does erase every capsule and fully replaces it with the current flashed bios
AFUGAN is there to bypass ASUS's verification check (quote me on that with the exact location of it)
ASRock has also a capsuled bios like Asus (I think current MSI ones are capsuled too)

The reason you use AFUGAN after flashing the official bios, is to keep the integrity in tact on ASUS Boards
(also quote me on that with the exact description)
ASRock has a verification capsule in all of their official BIOSes - which the user needs to remove and "decapsule" the bios
To do that normally you have to UUID edit as mentioned in post #1367 or put the bios file once through UBU.bat - to remove that integrity check
Afterwards you just flash it via Afuefix64 over the normal bios without /X and without /CLRCFG

If issues still remain and you continue to get integrity check issues
- push first the official bios trough UBU (just load it and export as .bin) & flash it clean with /X
- then later push your mod through the same procedure just to be sure & flash it without /X - imo you can check microcode updates too
* just don't update any EFI "packages" & GOP so far, as it can mess stuff up ^^#

Oh may I ask you where you got ASRock bios mods ?
Did some active modder appear ?
07-21-2019 10:09 AM
Erick Aguero Hi, I'm having problem flashing modded BIOS for an ASRock Fatal1ty X470 Gaming-ITX/ac
If I use

Afugan.efi MODDED.ROM /GAN


I end up with this error:
Code:
46 - Error: Problem getting flash information.
I tried the suggestion on this thread to use the 1st command with the modded BIOS file


Afuefix64.efi MODDED.ROM /P /B /N /K /X /CLRCFG


But I end with the following error:
Code:
1e - Error: Secure Flash function is not supported on this file.
Any suggestion?
07-21-2019 10:00 AM
helder19 biostar x370gt7 has many problems, cad bus blocked, any bios mod available?
07-20-2019 01:03 PM
dobermann24
Quote: Originally Posted by qpens8 View Post
I have ROG Strix x470-f gaming, and I'm on 5007 bios. I there any mod for that board/bios?
The old mod bios, but not the new one. Or anyone make this.
This thread has more than 10 replies. Click here to review the whole thread.

Posting Rules  
You may post new threads
You may post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off