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

GIGABYTE EAGLE 6700xt cannot be used normally after upgrading with the official BIOS

gaoang520

New Member
Joined
Oct 1, 2021
Messages
7 (0.01/day)
GIGABYTE Falcon 6700xt cannot be used normally after upgrading with the official BIOS upgrade tool of the corresponding model of GIGABYTE, and the backup BIOS cannot be flashed back with AMDvbflash. The error message is Failed to read ROM ERROR: 0FL01 Please help me. Thank you very much.
微信图片_20210929123506.png
微信图片_20211001184215.png
微信图片_20211001184313.png
微信图片_20211001184642.jpg
 
You put the incorrect bios on the card is why.

Open the folder where you extracted the tools to and open the readme.txt file and the guide.pdf file- read them both and understand them.

You are using the wrong syntax for the version of amd flash.

Open the command prompt with administrator privileges.

amdvbflash -i to see if the card is even detected.
GIGABYTE Falcon 6700xt cannot be used normally after upgrading with the official BIOS upgrade tool of the corresponding model of GIGABYTE, and the backup BIOS cannot be flashed back with AMDvbflash. The error message is Failed to read ROM ERROR: 0FL01 Please help me. Thank you very much.
View attachment 219009View attachment 219010View attachment 219011View attachment 219012
 
Last edited:
You put the incorrect bios on the card is why.
The correct BIOS, I just upgraded the BIOS version from F1 to F2, which is the same brand and the same model of BIOS, and did not flash other versions of the BIOS. But the graphics card was broken after the upgrade. I had two identical graphics cards, and the other one was in normal use without any problems after the upgrade, but this one was broken.
 
Why do people feel the need to flash them if they work fine. There should be a noob lock on GPU's
Ha ha , agree.
Usually when a thing is working fine, why someone should alter it ?
 
You put the incorrect bios on the card is why.

Open the folder where you extracted the tools to and open the readme.txt file and the guide.pdf file- read them both and understand them.

You are using the wrong syntax for the version of amd flash.

Open the command prompt with administrator privileges.

amdvbflash -i to see if the card is even detected.
 

Attachments

  • 微信图片_20211001201704.png
    微信图片_20211001201704.png
    77.9 KB · Views: 117
Last edited by a moderator:
Ha ha , agree.
Usually when a thing is working fine, why someone should alter it ?
They never learn, it's a XT card, nothing to gain.

The only time a gpu should be flashed is to fix bugs or a mining card.
 
Last edited:
They never learn, its a XT card, nothing to gain
I'm very sorry to trouble you, I hope my graphics card can get better, and I don't want to toss it again in the future.

You put the incorrect bios on the card is why.

Open the folder where you extracted the tools to and open the readme.txt file and the guide.pdf file- read them both and understand them.

You are using the wrong syntax for the version of amd flash.

Open the command prompt with administrator privileges.

amdvbflash -i to see if the card is even detected.
微信图片_20211001211016.png

Graphics card can be detected
 
I entered CMD with administrator authority and still can’t flash

View attachment 219022

I'm very sorry to trouble you, I hope my graphics card can get better, and I don't want to toss it again in the future.


View attachment 219025
Graphics card can be detected

Im glad it's detected. Now use this syntax instead, thanks @impero

amdvbflash.exe -fa -fp -p BIOS.rom

(Replace bios.rom with name of file you are trying to flash.)
 
I am glad i can help.
I tested a lot of versions and i use help command at each one of them to know how to use them.
This is how i learned the syntax.
:)

Im glad it's detected. Now use this syntax instead, thanks @impero

amdvbflash.exe -fa -fp -p BIOS.rom

(Replace bios.rom with name of file you are trying to flash.)
:)
 
I am glad i can help.
I tested a lot of versions and i use help command at each one of them to know how to use them.
This is how i learned the syntax.
:)


:)
Whoever wrote The Flash programs had recently changed the syntax

Which makes me think that they force flash now automatically
 
Forced flashing still does not work for it.View attachment 219257
Hello.

I would like to ask you something regarding the syntax you used for flashing the BIOS.
I noticed you used the name "bios.rom" as we told you in our example.
But in reality did you changed the name of your file you want to write in to "bios" ?
Else you have to use the exact name of the file you want to write ....like XT5700.rom (this is an example)
 
Hello.

I would like to ask you something regarding the syntax you used for flashing the BIOS.
I noticed you used the name "bios.rom" as we told you in our example.
But in reality did you changed the name of your file you want to write in to "bios" ?
Else you have to use the exact name of the file you want to write ....like XT5700.rom (this is an example)
The bios chip is locked out from the tom foolery
 
Hello.

I would like to ask you something regarding the syntax you used for flashing the BIOS.
I noticed you used the name "bios.rom" as we told you in our example.
But in reality did you changed the name of your file you want to write in to "bios" ?
Else you have to use the exact name of the file you want to write ....like XT5700.rom (this is an example)
The name of my bios file is bios.rom. There is nothing wrong with it. It should be that the bios chip is broken.
 
IF you renamed previously the BIOS file to "bios.rom" then you used the right syntax.
Then yes , i suspect a hardware level failure.
 
Time to get a SPI flasher

The name of my bios file is bios.rom. There is nothing wrong with it. It should be that the bios chip is broken.

IF you renamed previously the BIOS file to "bios.rom" then you used the right syntax.
Then yes , i suspect a hardware level failure.
 
Back
Top