• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

5600XT with wrong BIOS, "failed to read rom" in v2.93 (win or UEFI), unable to force past SSID mismatch in v3+ (win, no uefi exists).

darius510

New Member
Joined
Feb 14, 2022
Messages
4 (0.00/day)
I'm at a loss at how to restore the stock BIOS on a bunch of cards I purchased. It's a sapphire 5600 XT pulse that has a mining tuned BIOS on it, that reads as a powercolor red dragon. So whoever flashed it must have overwritten the SSID.

Tried flashing it back to the stock bios (from the library) using the latest version of AMDVBFLASH, but as far as I can tell, the option to force flash an SSID mismatch is no longer possible in windows, getting the message "-f option not supported in external version of tool." It does successfully read the ROM though - it still does leave a message about the SSID mismatch.

Tried v2.93, both in windows and the UEFI version, and both return the message "failed to read ROM."

Since the newer version can read the ROM, my best guess at this point is it was flashed in such a way that only the new version can read the ROM, but there appears to be no way (as far as I can tell) to force past an SSID mismatch with v3+, since there is no UEFI version available (again, as far as I can tell.)

How to move forward here?
 
Did you see this thread? it is possible the card came with a bad BIOS chip, or one that was flashed wrongly with a SPI flash programmer.
 
Did you see this thread? it is possible the card came with a bad BIOS chip, or one that was flashed wrongly with a SPI flash programmer.
The card isn't actually bricked - it works as you'd expect from a bios modded mining card. I can run furmark on it in windows no problem. There's just a very obvious hard temp limit at 75C, and I havent dug into the clock speeds or timings but I suspect they're all janked up as well. We also bought some red dragon cards from the same seller, as I suspect he flashed the exact same bios to ALL of them, even the sapphires. I would like to restore the cards to stock bios for resale to gamers.
 
If you can't flash it back by ordinary tools, you'll have to use non-ordinary tools such as SPI programmer.
 
If you can't flash it back by ordinary tools, you'll have to use non-ordinary tools such as SPI programmer.
I guess I don't understand why they removed the option to force past the SSID mismatch in the newer versions? I have no reason to believe that I would not be able to flash it if that option still existed.
 
Did you use:

amdvbflash -unlockrom 0
amdvbflash -f -p 0 filename.rom

with cmd.exe with administrator privileges? and version 2.93?

If so, its a device ID mismatch and you need SPI programmer to restore.
 
Did you use:

amdvbflash -unlockrom 0
amdvbflash -f -p 0 filename.rom

with cmd.exe with administrator privileges? and version 2.93?

If so, its a device ID mismatch and you need SPI programmer to restore.

Yes - using 2.93 I get the "failed to read ROM" message. I've had plenty of experience flashing polaris cards for years but the navi cards are still new to me. Is there some technical reason why you can't force the flash past those mismatches on navi but you can on polaris?
 
Yes - using 2.93 I get the "failed to read ROM" message. I've had plenty of experience flashing polaris cards for years but the navi cards are still new to me. Is there some technical reason why you can't force the flash past those mismatches on navi but you can on polaris?
Have 1 card installed at a time in the system plugged directly into a pcie 16x slot, not on a extension cable.

I have a mini guide.

Follow it, also some miners use a bios that will report incorrect ram on the card so i suggest getting pics of the ram.

 
Back
Top