• 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.

Help, error flashing gpu "0FL01"

rwee

New Member
Joined
Dec 16, 2022
Messages
5 (0.01/day)
I've flashed plenty gpus, mostly Nvidia without trouble, Amd has always been more troublesome

I have a MSI 6700xt Mech 2x which stupidly has been flashed to a Gigabyte 6700xt Gaming OC by a miner, meaning the display outputs don't work properly. I can't for the sake of it force a bios flash back to MSI. For example I had another 6700xt where I could change the vbios to "wrong" version and with ssid mismatch, as well as a 5700 to 5700xt.

This one however, I can't even get back to it's original. Says SSID mismatched, and ERROR: 0FL01, no matter how I try to flash it with Amdvbflash, even with unlocked rom and forcing the flash.

When I try to flash it's already installed (gigabyte) bios, it says flash already programmed as normal, but if I try to force it, nothing happens which is also weird.

edit: no dual bios, and ofc tried opening with admin rights.

edit2: If I use "-p -fa -fp" instead I get "Adapter not found" and then the same error
 

Attachments

  • ssidmismatch.JPG
    ssidmismatch.JPG
    13.7 KB · Views: 216
  • mismatch2.JPG
    mismatch2.JPG
    11.9 KB · Views: 199
Last edited:
Did you run it with gui or in cmd. If you used latter one add -f parameter for force flash if you are sure that bios is correct.
 
both. as i originally said i used force command, didn't help.

-t 0 = pass
-v (correct bios) = 0x4/0x100000 bytes verified
ERROR: 0FL04

-mb 0 (correct bios) = Invalid entry provided, Line 1. - Line 2272

Bios Checksum does not match

GOP Driver does not carry tables (actually says GOP Driver does not carr(random symbols))

Found "sneaky" command "-fs", supposed to "Force flashing bypassing BIOS SSID check." which in theory is what I need. Sadly doesn't work/help
 
Last edited:
I would try on a different computer and/or Windows install- it looks like software issues from the GPU-Z screenshot.

Otherwise, a hardware programmer is your best bet.
 
I would try on a different computer and/or Windows install- it looks like software issues from the GPU-Z screenshot.

Otherwise, a hardware programmer is your best bet.
yeah that was just windows messing up after some back and forth with drivers, a restart fixed that.

However now, somehow, I managed to flash after trying 20 ways, but it wasn't fully successful and said it had written over the bios but couldn't verify any of the. Seems I bricked the bios entirely. Code 43 and Amdvbflash cannot read Rom anymore; now it tries to patch and remove old bios/rom, however results in "Fail" or other times "Failed to read ROM Error: 0FL01"

Some further trying and now I guess I turned a 90% working gpu to a paperweight. AmdvbflashWin (gui) totally refuses to open saying it cannot read rom and no wonder why, in cmd it says the card lacks a VBIOS completely. As well as no P/N or anything really.
 

Attachments

  • f.JPG
    f.JPG
    68.3 KB · Views: 254
Which bios did you try to flash and did you check which memory is on the PCB?

It should be still be possible to recover the graphics card with a CH314A programmer:
 
Hello.
In your case you must use only the CMD command line.
In the command syntax you must use -f to force flash it.
And...this one is from my personal experience: in the CMD window after you receive the error that can't read ROM, run again the command line.
In some cases it managed to write it after 5 more tries but in worst cases it took me more then 20 .
just be patient.
 
This needs some clarification, I think.

Actually it currently seems impossible to cross flash NAVI GPUs with ambvbflash from within the host os. I tried it with different versions of amdvbflash from within Windows and Linux. The conclusion is that as far as I could find out newer versions than 2.93 do not have the -f option anymore, which is needed for skipping subsystem mismatch error, but you need a newer version for working with navi gpus.

Actually what @VuurVOS said is correct- flashing can easily be done with and external spi programmer. You will have to take the card apart (at least I had to take the cooler off but your milage may vary).

I managed to program the flash with a CH341A using flashrom easily. I recommend getting information about the spi in the first place, cards may have different spi chips and not all chips can be programmed with every flasher. You can the get rom type information from ambvbflash -i X. Just google the spec sheet of the rom chip and make sure it is running at the correct voltage and you have a matching clip and you software does support the chip - while not all chips may be listed- if you are feeling lucky- have a try.

Make sure you save a backup of your old rom. If you dump it with the programmer make sure you read it at least twice and compare the files, spi programmer may in some ocasions read wrong data as there is no integrity check of the transferred data- or get the dump with amdvbflash- dumped roms should match bytewise exactly.

I flashed an rx6500xt successfully with the rom of a different vendor and so changed subsystem id- card runs fine- but you won't be able to go back to original without external programmer.

now it looks as follows: you can see id 0 is a different card as it has a different spi chip- but it is running the same bios as the second gpu.

adapter seg bn dn dID asic flash romsize test bios p/n
======= ==== == == ==== =============== ============== ======= ==== ================
0 0000 05 00 743F Navi24 MX25V8035F 100000 pass 113-D6320100-S06
1 0000 08 00 743F Navi24 P25Q80H 100000 pass 113-D6320100-S06
 
Last edited:
Back
Top