vega 56 sapphire pulse bios 1 write fail

[corint1]

I have a vega 56 from sapphire (pulse) but i have a big problem ... i managed to rewrite the first bios (with the button in the initial position-1) but after 3-4 rewriting successfully, can not rewrite ... it gives me the known error "atiflash error 0fl01" ... I tried everything I found on Google, but for vega there is nothing ... what can I do in this situation? ... everything I try to rewrite in bios I give this error ... I tried in the prom but without result ... thanks in advance

 

[kastriot]

And why you flashed bios in 1st place?

 

[corint1]

And why you flashed bios in 1st place?

First of all I have rewritten the second bios ... it worked smoothly and it works now ... then I read somewhere that the first bios must be more recent ... rewritten the first ... function, 3-4 times, then he did not want it and kept it like that error

my question was not why, but how can I restore the first bios ... I did not expect anyone to quarrel ... or understand that nothing could be done?

 

[Caring1]

….my question was not why, but how can I restore the first bios ... I did not expect anyone to quarrel ... or understand that nothing could be done?

Of course people will question why you flashed in the first instance, unless there was a problem and the manufacturer instructed you to flash, it is unnecessary.

 

[corint1]

Of course people will question why you flashed in the first instance, unless there was a problem and the manufacturer instructed you to flash, it is unnecessary.

ok ... maybe stupidity or curiosity or ignorance ... blame I assume it ... important is now if I can recover something or not ...

 

[Candor]

This may or may not help you.

See last five or so posts on this page:

https://www.reddit.com/r/EtherMining/comments/7qifnc

 

[corint1]

This may or may not help you.

See last five or so posts on this page:

https://www.reddit.com/r/EtherMining/comments/7qifnc

thank you but I found this thread... I try what is in this post ... no work ...
strange is that the video card works with the bios written now ... it's not the one in the factory, it's a newer version ... but everything from sapphire pulse ...

my problem is that I want to rewrite another bios and that does not work ... I tried with all the possible arguments ... it does not want peace ...

 

[Candor]

When you say you want to write another bios, what is the bios you are trying to write?

An older version? A newer version? A version from the same card but from another vendor? Please clarify.

 

[corint1]

When you say you want to write another bios, what is the bios you are trying to write?

An older version? A newer version? A version from the same card but from another vendor? Please clarify.

is original bios , saved before ... or with a bios from sapphire vega 64 ...
that size is the same: 256 kb ... as an additional error message "write fail" ... does not pass on the side where it checks the one that wrote ...

 

[H3llSp4wN]

Hello Guys, my first time here, i hope you can help me with this one

last friday i bought a Sapphire Pulse Vega 56, this one has 3 display ports and 1 HDMI.

In order to obtain vega64 performance and unlock higher voltages in samsung HBM, i flashed the Sapphire Nitro+ Vega64 bios.

Everything ok, the card bootup nice and smooth.

The problem is, the Sapphire Nitro+ card has 2 display ports and 2 HDMI, so i noticed that my 3rd Display port is dead with this bios ( it makes sense ).

So i tried to flash the stock bios ( i've made a backup with gpu-z ) and problems starts here.

i repeat the same procedure, CMD in admin mode // atiflash.exe -unlockrom 0 // atiflash.exe -p 0 -f bios.rom, atiflash gives me following error: ( write passed 80000/8000, write verified 2/80000 fail, error 01FL1 )

no mather wich bios i tried to flash i allways get this error!

do i need the 1+8 pin method ?

sorry for my english

thanks in advanced

 

[eidairaman1]

First thing, lets get a GPU-Z Screenshot, post it here

Second please take pictures of the White Stickers on the back of the card- Make sure the Text is clear and post them Here.

 

[fullinfusion]

@eidairaman1 you need to inform these people with aftermarket vega cards not even bother messing with the BIOS.. only if you have a reference card then by all means flash whatever other reference bios you want to it. When you buy an aftermarket Vega you're going to have these issues guaranteed every single time! If you want, send the vendor an email and ask them for a compatible bios to change your 56 into a 64, sometimes they will and other times they won't.

If the user plays around with the Vega settings they will find out that there is basically no difference flashing a 56 to a 64. These aftermarket cards have really good cooling solutions so take advantage of raising the voltage on the core and that will also increase the voltage to the hbm..

 

[therealmeep]

Hello Guys, my first time here, i hope you can help me with this one

last friday i bought a Sapphire Pulse Vega 56, this one has 3 display ports and 1 HDMI.

In order to obtain vega64 performance and unlock higher voltages in samsung HBM, i flashed the Sapphire Nitro+ Vega64 bios.

Everything ok, the card bootup nice and smooth.

The problem is, the Sapphire Nitro+ card has 2 display ports and 2 HDMI, so i noticed that my 3rd Display port is dead with this bios ( it makes sense ).

So i tried to flash the stock bios ( i've made a backup with gpu-z ) and problems starts here.

i repeat the same procedure, CMD in admin mode // atiflash.exe -unlockrom 0 // atiflash.exe -p 0 -f bios.rom, atiflash gives me following error: ( write passed 80000/8000, write verified 2/80000 fail, error 01FL1 )

no mather wich bios i tried to flash i allways get this error!

do i need the 1+8 pin method ?

sorry for my english

thanks in advanced

This is an issue with flashing bioses onto aib cards where that last video out may be different on different vendor cards. My 1080ti does the same thing with a strix XOC bios on it and I have my original bios on my second slot. Best advice is if you want the full function keep the stock one, otherwise if you want the performance, you're probably going to have to sacrifice that displayport.

 

[MrGenius]

The only exception to that rule is the MSI Air Boost Vega cards. Which have the same PCB as reference Vegas. But with slightly higher State 7 core clock speeds. I've been running the MSI Air Boost BIOS on my reference PowerColor 64 for a while now without issues.

The 01FL1 error can be a real PITA sometimes. I wasn't able to flash one of the BIOSs on my 280X for like a year or so because of it. Then one day, out of the blue, I tried flashing it and it suddenly worked again. And I never got that error again afterwards. Why? I haven't a clue.

Other than get used to it, the only other thing I might recommend is to replace the chip. Not too expensive and fairly easy to do. Just need a new EEPROM chip, a cheap programmer, and a soldering iron. Basically.

BTW, AFAIK the 1 + 8 pin trick doesn't work on dual BIOS chips.

EDIT: Now that I think of it, you might just need a SPI programmer. Since there's probably nothing wrong with the EEPROM chip.
https://www.overclock.net/forum/74-...most-any-card-amd-nvidia.html#/topics/1612108

 

[fullinfusion]

The only exception to that rule is the MSI Air Boost Vega cards. Which have the same PCB as reference Vegas. But with slightly higher State 7 core clock speeds. I've been running the MSI Air Boost BIOS on my reference PowerColor 64 for a while now without issues.

The 01FL1 error can be a real PITA sometimes. I wasn't able to flash one of the BIOSs on my 280X for like a year or so because of it. Then one day, out of the blue, I tried flashing it and it suddenly worked again. And I never got that error again afterwards. Why? I haven't a clue.

Other than get used to it, the only other thing I might recommend is to replace the chip. Not too expensive and fairly easy to do. Just need a new EEPROM chip, a cheap programmer, and a soldering iron. Basically.

BTW, AFAIK the 1 + 8 pin trick doesn't work on dual BIOS chips.

Like I mentioned to @eidairaman1 off the record it could be something as simple at some M$ update that why suddenly a flash that wouldn't work now does..


One of our vanguard testers uses the red devil V64 and was successful flashing a reference water bios to the card but he also lost one HDMI DP in the process and also wasn't able to flash back. He's been using the card for.months with no issues.

 

[H3llSp4wN]

First thing, lets get a GPU-Z Screenshot, post it here

Second please take pictures of the White Stickers on the back of the card- Make sure the Text is clear and post them Here.

i'm working right now but tonight i'm gonna post some images and videos for more detailed information!

very grateful for your attention!

The only exception to that rule is the MSI Air Boost Vega cards. Which have the same PCB as reference Vegas. But with slightly higher State 7 core clock speeds. I've been running the MSI Air Boost BIOS on my reference PowerColor 64 for a while now without issues.

The 01FL1 error can be a real PITA sometimes. I wasn't able to flash one of the BIOSs on my 280X for like a year or so because of it. Then one day, out of the blue, I tried flashing it and it suddenly worked again. And I never got that error again afterwards. Why? I haven't a clue.

Other than get used to it, the only other thing I might recommend is to replace the chip. Not too expensive and fairly easy to do. Just need a new EEPROM chip, a cheap programmer, and a soldering iron. Basically.

BTW, AFAIK the 1 + 8 pin trick doesn't work on dual BIOS chips.

EDIT: Now that I think of it, you might just need a SPI programmer. Since there's probably nothing wrong with the EEPROM chip.
https://www.overclock.net/forum/74-...most-any-card-amd-nvidia.html#/topics/1612108

btw do you reinstalled windows ?

i'm only asking because some users said that windows reinstall sometimes can solve this situation!

thanks for your attention!

 

[ArbitraryAffection]

I've flashed my 56 Pulse back and forth between NITRO+ 64 and its stock bios so many times without issue now. One thing I did notice is that sometimes when flashing the stock bios back, it gets stuck on the power saver mode (165W) on both switches. And it actually needs unplugging from the PC for like 10 minutes to change bioses.

@eidairaman1 you need to inform these people with aftermarket vega cards not even bother messing with the BIOS.. only if you have a reference card then by all means flash whatever other reference bios you want to it. When you buy an aftermarket Vega you're going to have these issues guaranteed every single time! If you want, send the vendor an email and ask them for a compatible bios to change your 56 into a 64, sometimes they will and other times they won't.

If the user plays around with the Vega settings they will find out that there is basically no difference flashing a 56 to a 64. These aftermarket cards have really good cooling solutions so take advantage of raising the voltage on the core and that will also increase the voltage to the hbm..

Flashing 56 to 64 increases the HBM2 voltage from 1.25V to 1.35V this is essential for most 56's to reach over 1 GHz HBM2. I am almost 100% sure increasing core voltage does not increase HBM voltage. The HBM voltage option in Wattman is related to the core, interestingly, and not the HBM2. That is the main reason for my flashing my 56 to 64. Everything else can be done with a powerplay mod.

 

[H3llSp4wN]

I've flashed my 56 Pulse back and forth between NITRO+ 64 and its stock bios so many times without issue now. One thing I did notice is that sometimes when flashing the stock bios back, it gets stuck on the power saver mode (165W) on both switches. And it actually needs unplugging from the PC for like 10 minutes to change bioses.


Flashing 56 to 64 increases the HBM2 voltage from 1.25V to 1.35V this is essential for most 56's to reach over 1 GHz HBM2. I am almost 100% sure increasing core voltage does not increase HBM voltage. The HBM voltage option in Wattman is related to the core, interestingly, and not the HBM2. That is the main reason for my flashing my 56 to 64. Everything else can be done with a powerplay mod.

Cool tip!

i'm gonna try it asap and give feedback here!

tks

okay so i have developments,

if i try to reflash the same vega 64 bios it let me to.

the vega 64 bios that i flashed is this one

i noticed that its the only bios compiled in 2018, all the otheres were compiled in 2017!

can be some kind of downgrade protection ?

i will attach some printscreens here.

 

[fullinfusion]

I've flashed my 56 Pulse back and forth between NITRO+ 64 and its stock bios so many times without issue now. One thing I did notice is that sometimes when flashing the stock bios back, it gets stuck on the power saver mode (165W) on both switches. And it actually needs unplugging from the PC for like 10 minutes to change bioses.


Flashing 56 to 64 increases the HBM2 voltage from 1.25V to 1.35V this is essential for most 56's to reach over 1 GHz HBM2. I am almost 100% sure increasing core voltage does not increase HBM voltage. The HBM voltage option in Wattman is related to the core, interestingly, and not the HBM2. That is the main reason for my flashing my 56 to 64. Everything else can be done with a powerplay mod.

sorry was umm busy, pre-occupied.

Anyways you are correct. on the increasing core voltage doesn't affect the HBM.

All I can say is if you really were able to flash many times and now you cant. I would probably try another system and flash it on there or just do a clean OS install. Trust me M$ is one of the biggest issues with your sort of problem.

Did you install an older driver and it worked? If so use that driver, Do your flash in WINDOWS! yes Windows. Try that and im sure something should work.

PS I tweak my 56 to the point it runs sometimes faster then the 64 and when not it nipps its heels to the tripping point

 

[Wachsmann]

I had the exact same thing happen. Flashed the nitro 64 bios ok, card works fine (minus the third DP port).
But if I want to restore the stock bios, it errors out exactly the same. Weird.

Atiflash gives the same info:
Write fail
80000/80000h bytes programmed
2/80000h bytes verified

ERROR: 0FL01

 

[H3llSp4wN]

I had the exact same thing happen. Flashed the nitro 64 bios ok, card works fine (minus the third DP port).
But if I want to restore the stock bios, it errors out exactly the same. Weird.

Atiflash gives the same info:
Write fail
80000/80000h bytes programmed
2/80000h bytes verified

ERROR: 0FL01

In that case i think its somekind of protection.

The bios file that i used its the only one compiled in 2018, and if you try to reflash it again eveverything its fine without errors.

 

[MrGenius]

btw do you reinstalled windows ?

No. But it was Windows 10. So it got upgraded to the latest version at least a couple times I'm sure. Which is pretty close to a reinstall every time you do that.

In that case i think its somekind of protection.

I don't think so. I'm not even sure if that's possible. But, even if it is, I've never heard of it happening.

 

[Wachsmann]

So, did a little more tinkering. After flashing that 64 bios, everything else is a no go. The other bios (left switch), is fine, I can flash the stock and low power version without problem. The right side (switch), where I flashed the 64 bios, seems to be somehow ignoring all new writes/flashes.

Atiflash states that 80000/80000h bytes were programmed, but fails the verification every time. Only bios that it doesn't, is the one that was already there (since the verification just compares the same existing bios, it doesn't fail). So it's not really changing anything.

Any other bios (even vega 64) fails. Sometimes at 2/80000h bytes verified, others at 4/80000h bytes verified.
Either that side of the bios chip only had one write left (is that even a thing?), or that version somehow write protected itself and atiflash can't literally write over it. At this point, I can't even corrupt or flash anything there. It's essentially perma stuck there.

I tried atiflash 2.77 on win8.1, same thing, so it's not the windows version, or the atiflash version. Tried other pci-e slots, same thing.
The card is still functional (since the left switch if perfectly fine), but the other one seems toast. The 64 bios isn't stable enough for me, even lowering clocks.

I'm stumped.

 

[H3llSp4wN]

my situation is exactly the same!

i think we should contact the sapphire support!

its a risk but we can try!

EDIT

did you try to flash via MSDOS?

 

[MrGenius]

Either that side of the bios chip only had one write left (is that even a thing?)...

It's not a thing in any practical sense. These chips are rated for >100,000 erase/program cycles per sector(industry standard spec). So they should pretty much last forever(as in survive more erase/program cycles than you'll ever manage to throw at them).

...or that version somehow write protected itself and atiflash can't literally write over it.

I don't know exactly what the deal is with it. First, I don't understand how a failure during the verification process somehow causes the bytes it says it already programmed to not be programmed. Verification is supposed to be a byte to byte comparison of what's been programmed on the chip and the file you just programmed it with. IOW verification shouldn't even matter as far as programming the chip. It's good to know if everything was programmed correctly. But what if it wasn't? Does it reprogram a copy of the BIOS it just erased? I really don't get what's going on here.

Anyway...this is what it looks like when you try to flash a write protected BIOS.

That's the secondary BIOS on my reference Vega 64. Trying to flash it with any BIOS(same or not) is impossible(with ATIFlash). It won't erase or program(or, needless to say, verify).

did you try to flash via MSDOS?

There's no version of ATIFlash that's supports Vega and can be run in DOS. Flashing from DOS is a thing of the past.