• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

5600XT flashing problem

cadjer

New Member
Joined
Jun 13, 2021
Messages
6 (0.00/day)
Hello!
Like many people here I have a problem with my 5600 xt (Sapphire Pulse rx5600xt BE. PN S88-4E416-002SA).
I think I broke it with a bad bios.
From the first boot up, I got:
- impossible to start my rodi which gave me a black screen (I couldn't even see the bios of my computer..)
-> I managed to get past this stage with the paper clip trick (connecting two legs of the microprocessor together).
- I'm not sure if I'm going to be able to get my computer to boot up, but I'm sure I'll be able to see my 5600 card in amdvbflash_win.
The problem I have is that I can't get a new stable BIOS to work with it.
The problems I'm having:
-- "error in Vbios image": yet I tried several BIOS or error 0FL01.
I've tried several BIOSes, but even when I try to apply the one I've saved, it doesn't work (it's the one attached to this email)
- I have tried all amdvbflash: 3.04, 3.04+, UEIF, windows.

- The back commands I use are:
CMD in admin
amdvbflash -i (sometimes I can't even see my card so I have to reboot);
amdvbflash -unlockrom 0 (0 is the location of my card)
amdvbflash -f -p 0 biosname.rom

- under windows:
amdvbflash
I'm trying to select a bios but every time I get: "error in Vbios image".

Under IUEF:
I have "unable to read ROM".

Is "Insttool64.exe" mandatory with the windows version and the DOS version?
Is the bios I have to inject 512 or 1 MB?
I've tried all the amdvbflash: 3.04, 3.04+, UEIF, windows... Can anyone tell me what I should do as I'm afraid I broke my card...

Thank you very much to all of you!
 

Attachments

Hello
For sure you bricked your card.
Well, you know something but you did not went all the way.
What i mean is : you must use a paper clip to shortcut those 2 pins, but you must keep it until you finish the flash procedure.
Only AFTER you finished the flash procedure you can take off the paper clip.
Do it again and keep us informed
 
ok thanks!
I thought the paper clip was just for switching to windows.
So I do the whole procedure under my back but with the paper clip and I only remove it afterwards?
 
1. Unplug all your dead cards, plug in the working card (I used USB riser, seating it could work but with the paperclip it's going to be hard).
2. Boot your PC, press F11 to access BIOS settings (for me). You need enable that you primarily boot from your IGPU (or videocard). It should be somewhere under Advanced Settings > GPU cards or similar.
3. Turn off your PC. I now connected my monitor cable into the VGA input on my motherboard (so it was not directly plugged into the GPU card)
4. Turn your PC on to ensure that you can boot. If OK, turn off.
5. Unplug your working card, and connect one of your dead cards (Power+riser). Keep the monitor cable connected to the motherboard.
6. Use the 1+8 method. This means you connect pins 1 and 8 on your dead GPU using a paperclip, you bridge the pins so that they touch.
zto6zhi4n4yg.jpg

7. Turn on your PC. Post screen should appear. If not, check that paperclip is touching pins 1 and 8 (I gave it a nudge).
8. Once in Windows, open the cmd admin prompt for atiflash. Run atiflash -i and your dead card should appear, but state "fail".
9. Remove the paperclip, re-run atiflash -i, now you should see BIOS version (I liked to take this extra step).
10. Now reflash as you want using atiflash -f -p 0 xxx.rom.
11. Once finished, turn off your PC and repeat from step 5 for each card.
12. Do not forget to enter BIOS one last time to switch back the primary boot to your PCI Express card before you boot up using your resurrected cards.


This post i used as a guide to unbrick my card.
So i put it here in order to have it.

Good luck!
 
Last edited:
no dual bios switch to use as a work around?
why the update? is your card a 12 or 14 gbs memory model?
 
cadjer...some news ?
 
Hello!
I just tried the above method.
It is the one I had already tried.
I have several situations:
- sometimes the card is detected but as a basic microsoft card;
- sometimes it is not detected at all...
I'm not sure if it's a good one or not...

Thanks a lot for your help :)
 
Hello
If your card appear in device manager as basic microsoft... then it was correctly discovered under windows but you need to install the drivers for it.
On the other hand when you do not see it under device manager then this could be a bad BIOS flashed into.
Let's refresh a bit the post:
- tell us how in the 1st place you got into this situation?
- i mean the video card that you own now - was new, you buy it from store ?
- if yes - how it end in this situation when you have a wrong BIOS in it ?
 
so yes, it is a bios problem.
I bought this card second hand and it worked fine.
I wanted to increase its performance so I decided to flash its bios.
I made a backup of its original bios.
Then I modified it.
However, when injecting this modified bios, I got an error message.
I checked it was still working.
But when I rebooted my pc, it had a bug.
I restarted my pc and I got my card which prevented me from even seeing my bios....
I did the paper clip technique and tried to reflash it with the bios I had saved. But impossible...
Very often I had the message "error VBIOS image";
sometimes my card is recognized sometimes not. Sometimes amdvbflash sees an AMD card sometimes not...

Now I'm really stuck.
 
so yes, it is a bios problem.
I bought this card second hand and it worked fine.
I wanted to increase its performance so I decided to flash its bios.
I made a backup of its original bios.
Then I modified it.
However, when injecting this modified bios, I got an error message.
I checked it was still working.
But when I rebooted my pc, it had a bug.
I restarted my pc and I got my card which prevented me from even seeing my bios....
I did the paper clip technique and tried to reflash it with the bios I had saved. But impossible...
Very often I had the message "error VBIOS image";
sometimes my card is recognized sometimes not. Sometimes amdvbflash sees an AMD card sometimes not...

Now I'm really stuck.
Stop using paperclips/wires and follow my directions.

Uninstall the GPU drivers before flashing using Display Driver Uninstaller found online.

You cannot modify GTX1000 or RX Vega Bios and newer. We will need to try and restore the card.


This is most likely the SKU on your card.
11296-05-20G

The Device and Subsystem ID is this
1002-731F-1DA2-E416

Subsystem ID E416 along with the SKU number is on the card, either on the back or by the pcie blade contactor.

I found 1 BE bios. Download it

From this list

You are not using correct command line syntax. So for now stop using DOS/CMD.

Get this tool.




www.techpowerup.com



AMD VBFlash / ATI ATIFlash (3.20) Download

Unzip the tool, open the Winflash.exe version by right clicking and opening with administrator rights.

Find the bios file and flash. (You may need to unzip the bios file first)

Warning use these methods below if 1 above fails

2nd method use only if 1st method doesn't work.

Since the Subsystem ID will be changing slightly you will need to do a force flash in an administrator privileged command prompt. (Find cmd in start menu right click and open as administrator)

If that is not performed you may receive the stupid 0FL error.

Then follow this command

Enter this command first

Amdvbflash.exe -unlockrom 0

(0 is the very first card in the top pcie slot, 1 is the secondary card)


Then enter this command

amdvbflash -f -p 0 XXXX .rom

Note: XXXX is the name of the VBIOS file you downloaded. You can also change the downloaded file name to a simple name.


Last method if 1&2 dont work due to syntax being wrong.


Create a new text file in your ATIFlash directory, name it FLASH.bat, and place this code into it:

@Echo off
cls

echo Flashing card 0 with BIOS.rom...
echo.
amdvbflash -p 0 -f BIOS.rom
echo.

pause
Assuming the new BIOS you want to flash onto your card is named BIOS.rom, this is the BIOS it will use for flashing.

Save your changes, then run the batch file by double-clicking on it.

Once you've received a success message, reboot your computer for the new BIOS to come into effect. If you can boot into Windows successfully, then that's good! (Note: your screen may flicker for a bit, because you basically have a new card, and Windows is trying to recognize it. If you want to be thorough, go ahead and do a clean re-install of your graphics drivers.)
 
Last edited:
Hello, before I take apart card and try the paperclip trick, just wanted to post for some response on my issue with the ASROCK RX5600XT CLD 6GO I bricked. I inadvertently flashed wrong vbios through Hive to a perfectly good working GPU. I can get it to boot to DOS only and amdflash totally recognizes it, can unlock it and get all info, but fails using the different flash commands. Unfortunately I don't have the original BIOS so have been using BIOS off ASROCK site and techpowerup. Thanks in advance!

eg. Bn dn. Did. asic Flash. ROMSIZE test. Bios p/n
0000. 04 00. 731F Navi10 GD25Q80C. 1000. PASS. -


seg=000. pciid=731f1002. Ssid c8131462

Asic family - navi10
Flash type. GD25Q80C. (1024)
PRODUCT NAME. 113-MSITV381MH.3A0
BIOS ONFIG FILE 303PP.SB
BIOS PN - PN NOT AVAILABLE
BIOS VERSION 017.001.000.068.000000
BIOS DATE: 03/09/20. 23:07
ROM IMAGE TYPE: HYBRID IMAGES
ROM IMAGE DETAILS
IMAGE0 - SIZE(57856 BYTES), TYPE (LEGACY IMAGE)
IMAGE1. - SIZE(44544 BYTES), TYPE(EFI IMAGE)


OLD SSID: C813
NEW SSID: 5122
SSID MISMATCHED
ERROR 0FL01 - PRESS 1 TO CONTINUE

BIOS/PN IN FILE mynew.rom is. : 113-ext800124-l12
Bios p/n on rom is :
Rom p/n and file p/n comparison failed
 
Stop using hive to flash

Get white sticker pics and a pic of a ram chip from the card
 
Stop using hive to flash

Get white sticker pics and a pic of a ram chip from the card
Absolutely! Lesson learned. :-( Here are the pictures.
 

Attachments

  • IMG_1454.jpg
    IMG_1454.jpg
    6.4 MB · Views: 223
  • IMG_1455.jpg
    IMG_1455.jpg
    4.3 MB · Views: 202
  • IMG_1456.jpg
    IMG_1456.jpg
    2.7 MB · Views: 177
  • IMG_1457.jpg
    IMG_1457.jpg
    3.6 MB · Views: 183
Absolutely! Lesson learned. :-( Here are the pictures.
Give me time

Hello!
Like many people here I have a problem with my 5600 xt (Sapphire Pulse rx5600xt BE. PN S88-4E416-002SA).
I think I broke it with a bad bios.
From the first boot up, I got:
- impossible to start my rodi which gave me a black screen (I couldn't even see the bios of my computer..)
-> I managed to get past this stage with the paper clip trick (connecting two legs of the microprocessor together).
- I'm not sure if I'm going to be able to get my computer to boot up, but I'm sure I'll be able to see my 5600 card in amdvbflash_win.
The problem I have is that I can't get a new stable BIOS to work with it.
The problems I'm having:
-- "error in Vbios image": yet I tried several BIOS or error 0FL01.
I've tried several BIOSes, but even when I try to apply the one I've saved, it doesn't work (it's the one attached to this email)
- I have tried all amdvbflash: 3.04, 3.04+, UEIF, windows.

- The back commands I use are:
CMD in admin
amdvbflash -i (sometimes I can't even see my card so I have to reboot);
amdvbflash -unlockrom 0 (0 is the location of my card)
amdvbflash -f -p 0 biosname.rom

- under windows:
amdvbflash
I'm trying to select a bios but every time I get: "error in Vbios image".

Under IUEF:
I have "unable to read ROM".

Is "Insttool64.exe" mandatory with the windows version and the DOS version?
Is the bios I have to inject 512 or 1 MB?
I've tried all the amdvbflash: 3.04, 3.04+, UEIF, windows... Can anyone tell me what I should do as I'm afraid I broke my card...

Thank you very much to all of you!
Absolutely! Lesson learned. :-( Here are the pictures.


That major wet spot on the back of thr card has me concerned

Hello!
Like many people here I have a problem with my 5600 xt (Sapphire Pulse rx5600xt BE. PN S88-4E416-002SA).
I think I broke it with a bad bios.
From the first boot up, I got:
- impossible to start my rodi which gave me a black screen (I couldn't even see the bios of my computer..)
-> I managed to get past this stage with the paper clip trick (connecting two legs of the microprocessor together).
- I'm not sure if I'm going to be able to get my computer to boot up, but I'm sure I'll be able to see my 5600 card in amdvbflash_win.
The problem I have is that I can't get a new stable BIOS to work with it.
The problems I'm having:
-- "error in Vbios image": yet I tried several BIOS or error 0FL01.
I've tried several BIOSes, but even when I try to apply the one I've saved, it doesn't work (it's the one attached to this email)
- I have tried all amdvbflash: 3.04, 3.04+, UEIF, windows.

- The back commands I use are:
CMD in admin
amdvbflash -i (sometimes I can't even see my card so I have to reboot);
amdvbflash -unlockrom 0 (0 is the location of my card)
amdvbflash -f -p 0 biosname.rom

- under windows:
amdvbflash
I'm trying to select a bios but every time I get: "error in Vbios image".

Under IUEF:
I have "unable to read ROM".

Is "Insttool64.exe" mandatory with the windows version and the DOS version?
Is the bios I have to inject 512 or 1 MB?
I've tried all the amdvbflash: 3.04, 3.04+, UEIF, windows... Can anyone tell me what I should do as I'm afraid I broke my card...

Thank you very much to all of you!
By the way that does not look like a pulse in any way, looks like an asrock or asus card

It doesnt even have a sku & pn sticker (E366, 353, 387) that all sapphire gpus have
 
Give me time





That major wet spot on the back of thr card has me concerned


By the way that does not look like a pulse in any way, looks like an asrock or asus card
HA! I definitely does look like that in the photo. I can assure you, it's the thermal gunk only and not wet or has ever been exposed to any elements other than the GPU box in a static bag or my PC. :)
 
HA! I definitely does look like that in the photo. I can assure you, it's the thermal gunk only and not wet or has ever been exposed to any elements other than the GPU box in a static bag or my PC. :)
Go get some isopropyl alcohol and remove it, if it were me id replace that thermalpad as well.

So it has samsung ram for sure, let me look in database
 
HA! I definitely does look like that in the photo. I can assure you, it's the thermal gunk only and not wet or has ever been exposed to any elements other than the GPU box in a static bag or my PC. :)
Oh yes, i'm sorry if i didn't mention that. It's ASROCK RX5600 CLD 6G0

Oh yes, i'm sorry if i didn't mention that. It's ASROCK RX5600 CLD 6G0
SSID mismatch is the error i receive when trying to flash ASROCK vbios back on it and get rid of the incorrectly flash MSI vbios. I have it limping along in Windows now and GPUZ recognizes it fine.. but with MSI attributes, vbios. If there was a way to force the SSID to take the asrockvbios.rom SSID, i would think it would be solved. Thanks again for the input here!
 
Last edited:
Just tried the new bios you recommended. Pesky SSID error whether I use command line or UI ..
Be patient, i gave another bios,can you use windows?

What version of vbflash you are using?
 
Be patient, i gave another bios,can you use windows?

What version of vbflash you are using?
Yep, I can use Windows now. vbflash 3.20 but have also tried the older versions. They all report SSID mismatch like I typically see with both of your recommended bios. All utilities are talking to the GPU just fine and I can unlock rom successfully. It just won't let me bypass to flashing due to the SSID mismatch

Yep, I can use Windows now. vbflash 3.20 but have also tried the older versions. They all report SSID mismatch like I typically see with both of your recommended bios. All utilities are talking to the GPU just fine and I can unlock rom successfully. It just won't let me bypass to flashing due to the SSID mismatch
Got it working!! Little different process then what I have been trying and a very old vbflash version was the only way. See attached files showing the fix. Thank you everyone! It's a good day :)
 

Attachments

  • successful flashing commands.JPG
    successful flashing commands.JPG
    147.5 KB · Views: 328
  • successful flashing.JPG
    successful flashing.JPG
    126.6 KB · Views: 258
Last edited:
Yep, I can use Windows now. vbflash 3.20 but have also tried the older versions. They all report SSID mismatch like I typically see with both of your recommended bios. All utilities are talking to the GPU just fine and I can unlock rom successfully. It just won't let me bypass to flashing due to the SSID mismatch


Got it working!! Little different process then what I have been trying and a very old vbflash version was the only way. See attached files showing the fix. Thank you everyone! It's a good day :)
Yup either a win cmd prompt or a script

Now use windows, dos, uefi to flash only
 
Back
Top