AFUWINx64.exe looks like it works but it does nothing. Secure flash error
I attempted the commands:
Afuwinx64.exe P9X79.rom /GAN
AFUWINx64.exe P9X79.rom /P /B /GAN
AFUWINx64.exe P9X79.rom /P /B /GAN /R
AFU /GAN doesnât work wit CAP files renamed to ROMâŚ
I followed the step: Open the *.CAP file, do a right-click onto the listed âAMI Aptio capsuleâ, choose the option âExtract bodyâŚâ and save it as *.ROM file. With the UEFITool .
Anyone that has modded their AM4 B450 MOBO/modified NvStarpsReBar.ffs
feel free to DM me to assist me if you are able to, thanks in advance!!
TL;DR - Is there anything different I should be using regarding Flash Programming Tool (v1.3) & any up-to-date steps/processes pertaining to this in 2025.
Again, Iâm not entirely certain exactly the path to taken with my specific configuration due to the cluster of comments, updates, problems, and specific cases for specific components everyone has.
Just being ultra cautious here as a means of strictly doing what I need to do for myself so no unnecessary steps are applied to my situation.
Blockquote
-
Copy the Flashrom files named flashrom.exe and CWSDPMI.EXE into the root of the just created bootable USB Flash Drive.
-
Boot off the USB Flash Drive in LEGACY mode (CSM should be set within the mainboard BIOS to âENABLEDâ).
-
Once you have access to the DOS image, type
flashrom -p internal -r BACKUP.ROM
and hit the âEnterâ key. Wait until the process has been finished.
You hopefully will see something like this on your desktop screen:
-
Now you can shut down your PC and remove the USB Flash Drive. Donât forget to enter the BIOS during the next start of the PC and to restore your desired BOOT order and options.
-
The just created file named BACKUP.ROM is a clean complete BIOS Region dump of your mainboard and should be stored outside of your PC to be able to recover the original BIOS Region later on, if something should go wrong at any time.
Now you should use a copy of the backup.rom file as source for the UBU work updating the desired BIOS modules.
-
Once you have finished the desired UBU processing and saved the product as âBACKUP.ROMâ, rename it to âMOD.ROMâ and copy it onto the already previously used USB Flash Drive.
-
Boot off the USB Flash Drive in LEGACY mode again, type
flashrom -p internal -w MOD.ROM
and hit the âEnterâ key.
Now wait until the erasing, flashing and verification process has been finished.
Users, who want to get a logfile about what exactly has been checked, detected and done by the tool, should execute the command with the suffix â -o writelog.txtâ (thanks to hancor for the info).
When mentioned to use FlashPrgTool v1.3, does the commands differ to FlashRomTool here?
as for the copying the program files:
- Copy the Flashrom files named flashrom.exe and CWSDPMI.EXE into the root of the just created bootable USB Flash Drive.
is this the same process with FlashPrgTool?
I cannot find any .exe nor CWSDPMI.EXE files.
They are all H, C, SH, TMPL, RULES [file types]
@Nameless
Donât expect any support from my side regarding your problem. Since I donât have any own experience with the usage of the new âflashprog toolâ, you should better ask the tool developer for help.
After having flashed the latest original BIOS into the chip of my ASRock X570 Pro4 I am not even able to create a proper BACKUP.ROM by using the Flashrom v1.2 Utilities, which worked fine with the same system before.
Meanwhile I have given up any intention to flash a modded BIOS into this rather modern ASRock X570 chipset mainboard. I donât want to risk a bricked system.
1 Like
So, essentially itâs probable none work on modern boards.
Yeah, I just wasnât sure exactly if Flashrom tool was dated now to Flashprogramming tool.
Itâs frustrating as heck as this is solely for my GPU⌠The MOBO has 4G Decoding + Re-BAR support. Yet, I need to get past this secure check on ASRocks BIOS.
I donât know if the manual removal of specific modules on the BIOS image files are necessary or not.
Currently on P3.60 [SMBIOS 3.2] as I rolled back in the hopes it would flash as standard initially.
When I first used UBU 1.79 I think, The file size never changed as per the security check function.
Now I tried to start fresh with another BIOS file drag the file over and drop it on to UBU.bat. However, time and time again it just seems to keep refering to the last file it scannedâŚ
And when using UEFITool I have a message in the base text box stating:
{ FfsParser::performSecondPass: the last VTF appears inside compressed item, the image may be damaged }
Relative to Preformatted textsecCore_VolumeTopFile`
On bios downloads from ASRocks site, simply extracted from the zip to use the file in UEFITool and UBU respectfully.
No idea if I do anything with this either.
I read various discussionâs with @sonix @ket @Koekieezz If anyone can help at all, feel free to dm m, or [If you guys could direct me to someone else that may be better suited for this then please do] as it would be some super help, everything is appreciated!!
Thanks again @Fernando for some information about the X570 issues you had.