@pipes80 :
Thanks for your reply.
You are right - my guide was absolutely misleading. As I just have realized, there was a typo within the command text. The second command, which is valid for the flashing procedure, has to contain a "w" (for WRITE) and not an "r" (for READ).
Meanwhile I have corrected my mistake.
I am sorry for having confused you.
Feedback with great success and big thanks !
Did a successful flash on Asus Pro WS X570-ACE , used latest 1302 base bios , updated microcode also for my ryzen 3600.
Had to clear CMOS so i can boot the system after the flash.
@d3vnul :
Welcome to the Win-RAID Forum and thanks for your feedback!
It makes me happy as well, that you got the modded ASUS X570 BIOS properly flashed by following my new Flashrom guide.
Enjoy it!
Dieter (alias Fernando)
It was an easy 5 minutes read , which made me confident to attempt the operation 
Really impressive work all together to all involved, I really am amazed on what a community can do.
Had to at least make an account and Thank You Dieter !
there can be an oversight with all the immense work you do in this forum
what does it mean? does the command create a copy of bios on the stick?
@Rabanik - Thanks, sounds like FD was not written back then. Please put on jumper again, dump new fdnew.bin and send to me so we can confirm.
I do indeed need your dumped BIOS region, not stock, this is what we edit and flash with FPT (ONLY THIS). I only wanted stock BIOS so I could look at that, compared to your dumped BIOS region to check some things.
What I mentioned still applies, what you show in images or what you mentioned, does not apply to your dumped BIOS region. I know the mod was not applied, I’m not talking about the mod, I’m talking about the padding files you showed in image and the other BIOS modules above and around that.
None of what you show in that image is in your BIOS at the location shown. Maybe you were modifying some other BIOS, and comparing some other BIOS, both of those BIOS in the image looked similar, but neither match your actual BIOSreg dump you sent me
See the image below, this is your stock BIOS and your dumped BIOS region side by side, notice there is no padding AND there is no modules x2 starting with GUID 05CA01F (and the rest of this area does not match your image either) << This is what I was talking about, nothing to do with the actual mod or not.
Yes, the file named BACKUP.ROM is a copy of the complete BIOS Region, which is within the SPI chip of the mainboard.
Hi. The dumped FDnew.bin is the same like your FDunlocked.bin
The BIOSREGION was succesfully written back. The problem was that I tried to flash back the origin biosreg.bin made before writting of your FDunlocked.bin I did not know it.
It works now I am attaching a new BIOSREG.bin file for NVME mod.
thank you a lot.
BIOS.zip (3.67 MB)
i have used a file backup.rom and when I had read with the know command the program create a file named mod_backup.rom then mod with ubu
@pipes80 :
This is the usual order:
1. The file named BACKUP.ROM will be created by the Flashrom tool after having executed the first (READ) command.
2. Then you can modify this file by using the UBU tool. After having finished the UBU tasks the modded BIOS will be named "mod_BACKUP.ROM" (if chosen option 1).
3. Before you run the second (WRITE) command, it is a good idea to rename the file to MOD.ROM (DOS cannot handle long file names).
@Fernando
I looked through the backup from my Asrock x570m Rro4 and did not find unique information (MAC, SN, UUID, etc).
It turns out that you can flash the stock BIOS, and not backup. Of course, all settings will be set by default.
@Rabanik - Sorry, I forgot I sent you unlocked FD before 
So, write in either of those with jumper on, then remove it, and you should then be able to write BIOS region back. Looks like you can now!
Here is NVME mod BIOS, write back >> FPTw.exe -bios -f biosregNVMEMM.bin
http://s000.tinyupload.com/index.php?fil…491902269955638
@SoniX :
Which tool did you use, when you stored a backup of your ASRock mainboard’s BIOS?
By the way - meanwhile I have flashed several times an UBU updated BIOS into the chip of my ASRock X570 mainboard by using Flashrom and all my personal BIOS settings were still active.
Supermicro uses usual afuefix64.efi to flash 32MB SPI ROM:
afuefix64.efi %1 /K /RLC:F
afuefix64.efi %1 /P /B /N /R /RLC:F
afuefix64.efi %1 /x /atr /SSB:{NONBOOT16M} /RLC:e
@Fernando @Sonix @Lost_N_BIOS
Okay I finally figured out how to use the flashrom procedure correctly.
The proper nomenclature to achieve is to enter the following at the C:\ prompt of the bootable DOS USB drive:
C:\flashrom -p internal -w MOD.ROM -o writelog.txt
Below is my renamed writelog.txt with the successful results.
EFI_ROM mods:
Microcode mods:
I had a few scares for a moment when I did the full update with UBU_1_78_0 as the EFI ROM Onboard Video driver killed my backward compatibility to my old ASUS VG278H monitor from 2012 which still has a dual-DVI connector. Of course I had only had a goofy patch cord to go from DisplayPort on the EVGA 2080Ti to the dual-DVI on the monitor. I kept the monitor around as it would still run at 120Hz refresh rate. After trying to boot up I got the proverbial BLANK SCREEN which caused some irritation and concern, as I couldn’t reenter the BIOS/UEFI without visuals as I’m not clairvoyant yet…! Then I started to think about my setup. I checked up the the connections specs and realized I had an HDMI port on the Asus VG278H monitor, and one HDMI port on the EVGA 2080Ti. I scrambled around on and found my neglected HDMI cable flying around behind the back of the desk collecting no small amount of dust. I shut down computer and monitor, hooked up the HDMI cable and suddenly had visuals on boot up. This allowed me to flash the BACKUP.ROM to its previous state. Further I noticed, that the RAIDExpert2 EFI on the 9.3.0.xxxx is a nonstarter on the Asus Zenith Extreme so I wound up looking through my UBU folders for an older version of RAIDExpert2 EFI and found the version 9.2.0-00127. I reflashed and with the older RAIDExpert2 module and VOILA my NVMe RAID0 boot array was recognized.
EDIT by Fernando: Unneeded blank lines removed (to save space)
Asus Zenith Extreme v2001 BIOS_UEFI flashrom update log 25 05 2020.pdf (143 KB)
@hancor :
Thanks for posting the complete flashrom flash command (incl. suffix) for users, who want to get a log file about what the tool has checked and done.
Does this mean, that the command "flashrom -p internal -w MOD.ROM" is not correct?
@aGeoM @Fernando @Lost_N_BIOS @SoniX
Originally: your script on page one was denoted to read as C:\flashrom -p internal -r BACKUP.ROM
Which was correct.
Then the second command was to WRITE the new modded bios
Originally this was set out as: C:\flashrom -p internal r MOD.ROM a couple of days back…
Of course this was a typo as this only reads the contents of the BIOS over one’s modded bios !
I see you’ve since corrected this as follows: C:\flashrom -p internal w MOD.ROM
I looked up the documentation from the original source and near the end of the doc found the BIOS write command as:
C:\flashrom -p internal -w MOD.ROM -o writelog.txt
In any case, it is sorted out now!
Also I had a query as I am running the RAIDExpert2 module with an NVME RAID0 array using two Samsung 970 PRO 1TB drives. At one point @aGeoM suggested there was a RAIDExpert module denoted 9.2.0.138 somewhere. I combed through my File folders of my collection of older AMD RAID modules but haven’t found it.
Anybody have an idea where I can find this module?
Cheers!
and to create a backup bios you have to make it read an original bios downloaded from the manufacturer site, right?