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

ROM not erased. Error 0FL01

Xaviguinho

New Member
Joined
Nov 16, 2024
Messages
27 (0.14/day)
Hello, good morning, Bia, afternoon, good evening. I have a problem with my video card (Amd RX580 2048SP 8GB FROM JIESHUO), in my attempt to change to "BIOS", I ended up bricking the card; I did the procedure using a YouTube tutorial lol anyway, I used the files that I will attach here later.

amdvbflash -i

amdvbflash -unlockrom 0

amdvbflash -f -p 0 NOMEDABIOS.rom


In my failure, I tried to use the commands above to "Flash" the (ROM); the first attempt failed because I think I must have typed a command wrong. But the second time, I did it again and it seemed like it was going well, but the screen froze; I waited at least 5 minutes, until I forced the reboot at the time, no video. Well, I tried to go back to the "ORIGINAL BIOS", I used a post from this forum in an attempt to reverse the situation (which I caused myself lol); the way is to start windows in safe mode so that this error: error rom not erased would not happen again (THE FACT THAT I COULD STILL VIEW THE WINDOWS SCREEN WAS BECAUSE I DOWNLOADED AN APPLICATION/PROGRAM FROM SPACEDESK THAT ALLOWED ME TO "STREAM" THE SCREEN); but I did not count on the fact that when starting windows in safe mode/with networking, (innocently thinking that the program would also start), I lost the view of the screen. Since I do not have a second machine or a processor with integrated video, I believe that I have lost hope of recovering this error. That is why I posted here in this forum in the hope of finding someone who can perform miracles for me HELP!!! PLEASE!!!! And excuse my English.
 

Attachments

  • Screenshot_20241117_121533_Chrome.jpg
    Screenshot_20241117_121533_Chrome.jpg
    326 KB · Views: 65
  • Screenshot_20241117_121906_Chrome.jpg
    Screenshot_20241117_121906_Chrome.jpg
    647 KB · Views: 63
  • 251962.rom
    251962.rom
    256 KB · Views: 44
  • Screenshot_20241117_121719_Chrome.jpg
    Screenshot_20241117_121719_Chrome.jpg
    814.3 KB · Views: 94
  • 20241117_115708.jpg
    20241117_115708.jpg
    2.8 MB · Views: 87
  • 20241117_115610.jpg
    20241117_115610.jpg
    2 MB · Views: 89
  • 20241117_115526.jpg
    20241117_115526.jpg
    2.9 MB · Views: 85
  • 20241117_115459.jpg
    20241117_115459.jpg
    2.5 MB · Views: 80
  • BIOS.rar
    BIOS.rar
    406.4 KB · Views: 50
Last edited:
JIESHUO is not a real brand. Its a brand which relabels other brands cards and then sell them as their own.
Just for confirmation, did you use amdvbflash v2.93?

You need to make a picture of your card with the cooler removed.
We need clear pictures of the whole PCB and memory before we can locate the correct bios for your card.

Can you also remove the thermal pads on the memory? Otherwise you dont know which brand memory and part number is on the card.
 
JIESHUO is not a real brand. Its a brand which relabels other brands cards and then sell them as their own.
Just for confirmation, did you use amdvbflash v2.93?

You need to make a picture of your card with the cooler removed.
We need clear pictures of the whole PCB and memory before we can locate the correct bios for your card.

Can you also remove the thermal pads on the memory? Otherwise you dont know which brand memory and part number is on the card.
It looks like some pcie pins might be damaged
 
JIESHUO is not a real brand. Its a brand which relabels other brands cards and then sell them as their own.
Just for confirmation, did you use amdvbflash v2.93?

You need to make a picture of your card with the cooler removed.
We need clear pictures of the whole PCB and memory before we can locate the correct bios for your card.

Can you also remove the thermal pads on the memory? Otherwise you dont know which brand memory and part number is on the card.
Good evening, I forgot to mention the memories in the Post. But they are from (Samsung).

It looks like some pcie pins might be damaged
I don't think so, as I only opened the dish to take photos.
 
Good evening, I forgot to mention the memories in the Post. But they are from (Samsung).


I don't think so, as I only opened the dish to take photos.
Image 5 which shows the back side of the card, look at the pcie pins moving towards the vid outputs on the pcie 8/16 blade, it looks like damage is there
 
Get a picture of 1 ram chip without the thermalpad please

From the picture it looks like it, but I looked again and it was nothing more than a tiny bit of dirt.

The screwy thing is the chip pn.

It can be a Rx 470 or 2048 580
 
Por favor, tire uma foto de 1 chip de RAM sem o thermalpad
The Vram is from Samsung, Gpu-Z confirmed this. But unfortunately I couldn't take a screenshot

Get a picture of 1 ram chip without the thermalpad please



The screwy thing is the chip pn.

It can be a Rx 470 or 2048 580
SO, when choosing in GPU-Z, it was showing an rx470 after the failed procedure.

SO, when choosing in GPU-Z, it was showing an rx470 after the failed procedure.
Before that, that is, before the big shit, GPU-Z had an RX580 2048SP
 
The Vram is from Samsung, Gpu-Z confirmed this. But unfortunately I couldn't take a screenshot


SO, when choosing in GPU-Z, it was showing an rx470 after the failed procedure.


Before that, that is, before the big shit, GPU-Z had an RX580 2048SP
We are asking for a reason and a third time now! Knowing it is Samsung is not enough.

Is it Samsung K4G80325FB, K4G80325FC or K4G41325FE
 
Estamos perguntando por um motivo e pela terceira vez agora! Saber que Samsung não é suficiente.

É Samsung K4G80325 FB , K4G80325 FC ou K4G41325 FE
I have an RX580 2048SP with a TDP of 125W, 1286MHz and 1750MHz. The problem is that I have the original BIOS, because I did the Beckup, but I can't flash it because of this error: "

ROM not erased. Error 0FL01
 

Attachments

  • 20241118_213323.jpg
    20241118_213323.jpg
    392.6 KB · Views: 59
Last edited by a moderator:
Olá, boa noite, que tipo de lembrança está aqui?

1002 6FDF 1002 0B31


I have a RX580 2048SP with TDP of 125W, 1286MHz and 1750MHz. The problem is that I have the original BIOS, because I did the Beckup, but I can't flash it because of this error: "

ROM not erased. Error 0FL01
 
You aren't doing it right is why, follow my guide
 
Olá, bom dia, Bia, tarde, boa noite. Estou com um problema na minha placa de vídeo ( Amd RX580 2048SP 8GB DA JIESHUO ), na minha tentativa de mudar para " BIOS ", apenas brickando a placa; fiz o procedimento usando um tutorial do YouTube rs enfim, usei os arquivos que anexarei aqui depois.

amdvbflash -i

amdvbflash -unlockrom 0

amdvbflash -f -p 0 NOMEDABIOS.rom


Na minha falha, tentei usar os comandos acima para "Flash" a ( ROM ); a primeira tentativa falhou porque acho que devo ter digitado algum comando errado. Mas na segunda vez, fiz de novo e parecia que estava indo bem, mas a tela travou; esperei pelo menos 5 minutos, até forçar o reboot na hora, sem vídeo. Bem, tentei voltar para a " BIOS ORIGINAL ", usei um post deste fórum na tentativa de reverter a situação (que eu mesmo causei rs); o jeito é iniciar o windows em modo de segurança para que esse erro: error rom not erased não acontecesse de novo ( O FATO DE EU AINDA CONSEGUIR VISUALIZAR A TELA DO WINDOWS FOI PORQUE BAIXEI UM APLICATIVO/PROGRAMA DO SPACEDESK QUE ME PERMITIU FAZER "STREAM " DA TELA ); mas eu não contava com o fato de que ao iniciar o windows em modo de segurança/com rede, (pensando inocentemente que o programa também iniciaria), eu perdia a visão da tela. Como não tenho uma segunda máquina nem um processador com vídeo integrado, acredito que perdi a esperança de recuperar esse erro. É por isso que postei aqui neste fórum na esperança de encontrar alguém que possa fazer milagres para mim AJUDA!!! POR FAVOR!!!! E desculpe meu inglês.
Still having the same problem guys but it's giving the error: FAILED TO READ ROM ERROR: 0FL01
 
Last edited:
Still having the same problem guys but it's giving the error: FAILED TO READ ROM ERROR: 0FL01
0FL01 is a generic error code. Sometimes need to try a couple of times. It can even be that a pin of the bios chip isn't properly soldered on the pcb.
Did you try a sligtly newer version of amdvbflash? Can you make a print screen of the command prompt?
 
0FL01 is a generic error code. Sometimes need to try a couple of times. It can even be that a pin of the bios chip isn't properly soldered on the pcb.
Did you try a sligtly newer version of amdvbflash? Can you make a print screen of the command prompt?
Improper cmd prompt syntax will trip it too, in 2.93 the bios must be unlocked first, in like 3.15 or higher the flash driver must the installed. Certain cmd switches are different between 2.93 and 3.15 and higher
 
0FL01 é um código de erro genérico. Às vezes, é preciso tentar algumas vezes. Pode até ser que um pino do chip do bios não esteja soldado corretamente no pcb.
Você tentou uma versão um pouco mais nova do amdvbflash? Você pode fazer um print screen do prompt de comando?
Hello, yes, of course I can.
 
Last edited:
0FL01 é um código de erro genérico. Às vezes, é preciso tentar algumas vezes. Pode até ser que um pino do chip do bios não esteja soldado corretamente no pcb.
Você tentou uma versão um pouco mais nova do amdvbflash? Você pode fazer um print screen do prompt de comando?
In fact, I tested, I think a lot of it
useiba version of amdvbflash 3.20 and 2.92
 

Attachments

  • IMG-20241119-WA0014.jpg
    IMG-20241119-WA0014.jpg
    162.5 KB · Views: 51
Last edited:
In fact, I tested, I think a lot of it
useiba version of amdvbflash 3.20 and 2.92
3.20, you need to enter amdvbflash -?

Or use 2.93
 
Really!??? in 3.20 enter amdvbflash -? And post a screenshot of the window please

Also in the amd vbflash folder, there is a driver that must be installed, if it is not installed, you cant flash
 
Back
Top