F5F Stay Refreshed Hardware Desktop The Asus Rog Strix X670E-E BIOS remains stuck and won't progress to the update stage.

The Asus Rog Strix X670E-E BIOS remains stuck and won't progress to the update stage.

The Asus Rog Strix X670E-E BIOS remains stuck and won't progress to the update stage.

Z
zhobs
Junior Member
4
10-29-2023, 05:49 AM
#1
Just after some shiz and giggles, I checked my BIOS version since it hasn’t been updated in a while. I tried following instructions multiple times, but nothing worked. I moved everything onto an 8 gig flash drive, including the renamed version at the root of the flash. Turned off the system, inserted the drive into the rear USB port, and pressed the small button until it counted to three. The flashlight blinked briefly before stopping. That’s all. Someone should know what happened. Mobo: Asus Rog Strix X670E-E Gaming CPU: AMD Ryzen 7 7800X3D RAM: Corsair Dominator 6000 64Gigs (2x32). Slots A2 and B2. Current BIOS: 1416. Date: 05/16/2023. New BIOS: 2124. Date: 07/19/2024. Thanks a lot for the help—it really means a lot. Take care and good luck.
Z
zhobs
10-29-2023, 05:49 AM #1

Just after some shiz and giggles, I checked my BIOS version since it hasn’t been updated in a while. I tried following instructions multiple times, but nothing worked. I moved everything onto an 8 gig flash drive, including the renamed version at the root of the flash. Turned off the system, inserted the drive into the rear USB port, and pressed the small button until it counted to three. The flashlight blinked briefly before stopping. That’s all. Someone should know what happened. Mobo: Asus Rog Strix X670E-E Gaming CPU: AMD Ryzen 7 7800X3D RAM: Corsair Dominator 6000 64Gigs (2x32). Slots A2 and B2. Current BIOS: 1416. Date: 05/16/2023. New BIOS: 2124. Date: 07/19/2024. Thanks a lot for the help—it really means a lot. Take care and good luck.

A
Adoptions
Junior Member
24
10-29-2023, 07:30 AM
#2
I only use flashback in this way, so here are some notes on differences or things to watch out for. For Asus boards, just use the renamed BIOS file from the root of the flash drive—no other files or folders needed. This applies to all brands. Make sure you enabled the correct file extensions during renaming; otherwise you might get a file like "SX670EE.CAP.CAP". The included renamer should help prevent this issue. Your flash drive must be freshly formatted with FAT32 and have an MBR partition table. GPT drives often don’t work with flashback. If your board has variations, double-check you have the correct one, as incorrect files can cause flashing failures. If problems persist, try another flash drive. The older the drive, the better—USB2 is preferable for compatibility.
A
Adoptions
10-29-2023, 07:30 AM #2

I only use flashback in this way, so here are some notes on differences or things to watch out for. For Asus boards, just use the renamed BIOS file from the root of the flash drive—no other files or folders needed. This applies to all brands. Make sure you enabled the correct file extensions during renaming; otherwise you might get a file like "SX670EE.CAP.CAP". The included renamer should help prevent this issue. Your flash drive must be freshly formatted with FAT32 and have an MBR partition table. GPT drives often don’t work with flashback. If your board has variations, double-check you have the correct one, as incorrect files can cause flashing failures. If problems persist, try another flash drive. The older the drive, the better—USB2 is preferable for compatibility.

C
Chassabelle
Junior Member
19
10-30-2023, 04:59 PM
#3
Thank you for your assistance. It seems the Renamer issue was causing the *.cap.cap files to appear. After identifying this, I managed to resolve everything properly. There were likely over 10 BIOS updates from the initial 1416 file up to the final 2124 file. Fortunate I didn’t have to apply all those updates first before working with the 2124 version. That would have been a real hassle. Again, many thanks for your support.
C
Chassabelle
10-30-2023, 04:59 PM #3

Thank you for your assistance. It seems the Renamer issue was causing the *.cap.cap files to appear. After identifying this, I managed to resolve everything properly. There were likely over 10 BIOS updates from the initial 1416 file up to the final 2124 file. Fortunate I didn’t have to apply all those updates first before working with the 2124 version. That would have been a real hassle. Again, many thanks for your support.