Overclock.net - An Overclocking Community - Reply to Topic

Thread: AGESA FW stack patched bioses for 3rd gen 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)
06-01-2020 03:55 PM
Veii
Quote: Originally Posted by dobermann24 View Post
Is it possible to flash the original bios from the asus rog strix x470-f gaming whit this method? I had the newest bios version, but I had installed the mod bios for my board. Than I went back to the backup bios. All fine, but when I start the pc only when the pc is complete off, than the windows shutter and the sound ist crazy. I can only shut it off whit the power button. After this the pc runs normal.
Just to clarify,
You where on bios A, used afuefi to flash bios B and then with afugan flashed mod_B ?
Or did you directly only use afugan to flash from old bios A to mod_B ?
Did you only use flashrom to wipe and flash the mod_B ?

You went down a bios version, how did you do that exactly
If I understand that correctly you did follow the 1usmus bios mod thread, meaning you used afuefi first ?
Or was all done purely with flashrom

Did you CMOS reset directly after the flash ?
Did you have boot up issues the first time you flashed mod_B ?

It doesn't sound like, the biosmod was the main issue, but its known that Asus boards do have their own ext controller with external firmware
Taking for example the cross hair lineup, or any Asus board with USB flashback support
Something you can not flash with flashrom and also not with afuefi or afugan

Edit:
The answer is yes, but if your board has USB flashback support
Use that, as it will update the ext controller firmware too
Only using flashrom on that specific usecase, can lead to strange bugs
Although flashrom does wipe the whole romchip
The issue would be then more on asus's side (:
06-01-2020 08:47 AM
dobermann24
Quote: Originally Posted by Veii View Post
Demonstration Tutorial
The tool supports several programmers, as well as flashing GPU ROMs

Typically you do
dir
first, before you even try any command
- to know what you have to type, as there is no TAB Autocomplete sadly

Code:
flashrom -p internal -r BACKUP.BIN
Should be used in the first place
Not only do you backup NVRAM, GUID, Board Serial & current Presets
But you also Test if your Flashchip can be read,
before going the vague way of erasing and trying to write to it
Overall always do it the first time when you try it on a new board

Keep your filenames at 8 digits max
We don't have TAB Support and you don't want guessing your filename
MS-DOS does support random USB removable, if you ever worry about your stick dying midflash / or you messed up your names and want to correct
But dont't count on it to reinitialise, as the files are preloaded into RAM

Code:
flashrom -p internal -w filename.bin
This command Erases & Writes your bios (be it whatever extension) to your board

The flashing process all-together takes about 5-15min
The erasing progress for 16mb chips about 90sec

IF something Fails, let's say the stick dies mid flash and it errors out
- DO NOT cut power to the system
Be sure to keep it running as long as you can, because it is able to support hotplug and the community can help you re-flash it from a 2nd USB
(in case your bios file was messed up and you need to correct something or it exceeds flash size)
Overall, keep it running and seek for help
The Flashrom Page has an IIRC chat, OCN is here
- just never turn off a system after erased but failed flash

Flashing Manual <- because -h page in ms-dos is not scroll-able
At the end, cold boot your system (PSU off)
often it can happen that even after SPI flash, the bios was preloaded
- soo cutting power is recommended


+rep @The Stilt
~ it does work flawlessly, lazy me doens't have to use the EVC2 on another notebook and crawl under the desk to attach
Is it possible to flash the original bios from the asus rog strix x470-f gaming whit this method? I had the newest bios version, but I had installed the mod bios for my board. Than I went back to the backup bios. All fine, but when I start the pc only when the pc is complete off, than the windows shutter and the sound ist crazy. I can only shut it off whit the power button. After this the pc runs normal.
05-25-2020 12:40 PM
Sushank21x
Quote: Originally Posted by The Stilt View Post
It is available at MSI site: https://download.msi.com/bos_exe/mb/7A38vAJQ.zip

E7A38AMS.AJQ file inside the archive, is the ready to be used binary.
Thank you soo much for the reply i would try it.
05-25-2020 07:14 AM
The Stilt
Quote: Originally Posted by Sushank21x View Post
i was updating my bios and my pc turned off during the update my pc is not turning on.
I have a msi b350m pro vdh motherboard
It does not have a bios button i went to a local repair shop and he said that the bios can be flashed back to some "motherboard chip" but he doesn't have a bin file of the bios he said that he needed that file for the usb programmer. It would be greatly appreciated if someone can provide me with this bios bin file for the msi b350m pro vdh motherboard.
It is available at MSI site: https://download.msi.com/bos_exe/mb/7A38vAJQ.zip

E7A38AMS.AJQ file inside the archive, is the ready to be used binary.
05-25-2020 05:44 AM
Sushank21x i was updating my bios and my pc turned off during the update my pc is not turning on.
I have a msi b350m pro vdh motherboard
It does not have a bios button i went to a local repair shop and he said that the bios can be flashed back to some "motherboard chip" but he doesn't have a bin file of the bios he said that he needed that file for the usb programmer. It would be greatly appreciated if someone can provide me with this bios bin file for the msi b350m pro vdh motherboard.
05-24-2020 06:06 AM
Veii
Quote: Originally Posted by The Stilt View Post
I've never seen one without it, not even a PR (similar to QS) CPU.

I assume the stamping has no other significance besides being either the logo of the company who either assembles the CPUs or provides the blank heatspreaders to AMD.
Hmm, i wish i could share some better data except just words
But i've seen non stamped batches
Always was curious about UF and UG meaning (:
05-24-2020 06:02 AM
The Stilt
Quote: Originally Posted by Veii View Post
There where 3rd gen ryzens without the bottom UG & UF stamp
and new batches which all where stamped at the bottom left corner
I've never seen one without it, not even a PR (similar to QS) CPU.

I assume the stamping has no other significance besides being either the logo of the company who either assembles the CPUs or provides the blank heatspreaders to AMD.
05-24-2020 05:49 AM
Veii
Quote: Originally Posted by The Stilt View Post
Huh?
"New stamped", what is that supposed to mean?
There where 3rd gen ryzens without the bottom UG & UF stamp
and new batches which all where stamped at the bottom left corner
05-24-2020 05:48 AM
Veii
Quote: Originally Posted by Fernando 1 View Post
@Veii :
Thank you very much for your very interesting and helpful information.After having read your post, I followed your advice and searched for the code "8B A6 3C 4A 23 77 FB 48 80 3D 57 8C C1 FE C4 4D" within the latest original BIOSes (untouched by UBU) for the following ASRock mainboards by using HxD:
a) X570 Pro4 (my new main PC mainboard) and
b) Fatal1ty Z170 (my formerly used mainboard).
Result: The exactly same code was present 2x within the Intel Z170 MB BIOS, but 4x within the AMD X570 one.
After having removed the ASRock Instant Flash protection by the UBU tool I found the code only 1x within the Intel Z170 BIOS, but 3x within the X570 one.

This indicates for me, that it may be possible to flash a modded 32MB sized ASRock BIOS by using the Instant Flash tool, if both relevant codes (the upper one of each BIOS half) have been removed by an upcoming UBU version.
As soon as possible I will let the UBU maker SoniX know about your tip and the result of my hex code search.

Thanks again!
Dieter
The problem is, the 3 pictures show the locations of it, while it is present on 4 locations
It's a lookup and connection header and has to stay intact & existing
It should be 4 while the UBU patch does just wipe the main capsule - to skip the "unverified bios" on bootup message
It's a resolve for even being able to flash unverified bioses, but it's only a bypass to what i want to call it
The UBU patch was done some time ago - but if you look at the first picture, the signing code remains to be unique between bioses, and only little parts of it change

The key from my research was it to generate an always accepting whitelist or always accepting verification header by tricking the check feature always "accepting" the result and flashing on non modded boards
UBU does patch it out and clear it, but the indication headers remain active and are checked on the listed partitions = still won't allow a flash

There looks to be more to this code, the yellow and green'ish marked fields
But i couldn't find direct relation to them back then
Soo this whole thing is in an experimental state, although i think it should work by now
It would just need some testing to figure out if their verification code needs to be a specific length, or just the parts locations of the code have to have some kind of data = can be empty too & just need the spacing hex afterwards (first picture)
UBU again does wipe the connection and i can see how the old way of bypassing - can cause big issues once it doesn't accept "empty data" anymore
Although UBU patch does only clean one sector, but doesn't resolve the issue at all

At best we do want a whitelist method, soo every bios that is pushed through UBU is signed with an "always accepted" signing
It would already be helpful if once flashed, it does allow every asrock bios to be flashed normally with the same signing header
compared to the old method, which does boot up but then again triggers verification error on for example afuefi flashing

Yes, the only thing that needs to be figured out, is how long the signing field has to be in length
And if my method works
The signing capsule seems to be at the same place, and the modules seem to be one only (they are 3+1 capsule)
The lookup header has to stay intact tho, else people can brick flash their boards without any check (UBU does wipe it)
Just removing the main capsule GUID from the 4 locations that are responsible for signing check
or making an always accepted signed capsule (master-key) - should resolve any flashing issues we had with asrock boards

EDIT:
Quote:
Result: The exactly same code was present 2x within the Intel Z170 MB BIOS, but 4x within the AMD X570 one.
After having removed the ASRock Instant Flash protection by the UBU tool I found the code only 1x within the Intel Z170 BIOS, but 3x within the X570 one.
Soo on intels side it should be easy to resolve it
First one is always the main capsule header, 2nd one is just needs removale of the pointing to the capsule in order to bypass verification check
OR - we'll get the master-key method to work
But technically removing any link to the capsule should already be a fix
The question remains only - what we need to do, for ASRocks EZ Flash to accept new bioses
What's the capsules "always accepted" signature
05-24-2020 05:34 AM
The Stilt
Quote: Originally Posted by Veii View Post
Like it was done after AGESA 1003AB(B), and the new stamped 3rd gen batches
Huh?
"New stamped", what is that supposed to mean?
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