Is it possible to unbrick my Vega 56?

[BlueFlame]

Hello guys,

I have a PowerColor Red Dragon Vega 56 with Samsung memory and I tried flashing it to a Red Devil Vega 64 but it didn't work. I flashed it via Windows CMD and it said it was a success but after restarting the card wouldn't even load the bios let alone boot into windows.
So I flipped the bios switched and was able to get into Windows with the second bios. I then tried reflashing the original back after flipping the switch again and I kept getting the locked ROM error. I tried using the unlock ROM command but it didn't work.
Since the second bios is a power saver bios it's very weak for performance so I decided to flash it with the card's original full power bios and it again said it was successful but after restarting the PC it won't boot into Windows (at least this time I can get into the mobo bios).
I put back my older RX580 just to get back into Windows. Then I put the Vega card in the second pcie slot but when I boot into Windows it imminently freezes.

Any help would be appreciated, thanks.

 

[Vayra86]

@eidairaman1

 

[eidairaman1]

SPI flasher is your only hope on this card since you flashed both bios files.

 

[Sasqui]

Since the second bios is a power saver bios it's very weak for performance so I decided to flash it

At a loss for words

 

[MrGenius]

Boot with the RX 580. Then use DDU to uninstall the drivers and shutdown the PC.

Then install JUST the Vega 56 and try booting into Windows again.

 

[kastriot]

So you destroyed up both bioses, i think gpu makers should start making triple bioses but i guess it wouldn't help in your case

 

[BlueFlame]

Boot with the RX 580. Then use DDU to uninstall the drivers and shutdown the PC.
View attachment 111768

Then install JUST the Vega 56 and try booting into Windows again.

I forgot to mention that I did do that once but after like 3 minutes in Windows the PC froze again. Should I try it again but after getting into Windows immediately try installing the Vega drivers from AMD?

 

[eidairaman1]

No

Boot with the RX 580. Then use DDU to uninstall the drivers and shutdown the PC.
View attachment 111768

Then install JUST the Vega 56 and try booting into Windows again.

Run ddu in safe mode then twice in protected mode

I forgot to mention that I did do that once but after like 3 minutes in Windows the PC froze again. Should I try it again but after getting into Windows immediately try installing the Vega drivers from AMD?

Since you flashed both bios files on the card you will need to take pictures of all of the white stickers on the back of the card, make sure that all text on the white stickers is clear so that it can be read.
You will need to take the heatsink off of the graphics card and get a picture of one of the memory chips information, make sure that text is clear, upload all of those pictures here, I will try to locate proper bios once that info is submitted here.

Once in a while, if you email power color they sometimes give you the bios files with the proper flash tools as long as you give them all the information and being honest with them, so try them too.

We will try to do a flash using the AMD flash tool however there is a 50% chance it will work and a 50% chance it will not work, if it does not work you will need to get a SPI flasher.

 

[MrGenius]

...i think gpu makers should start making triple bioses...

Or just do what AMD does on their reference cards and write protect the secondary BIOS. There's no way to flash the secondary BIOS on my reference Vega 64 with ATIFlash.

EDIT: BTW there have been GPUs with triple BIOSes. Such as the GTX 980 Ti K|NGP|N.

 

[eidairaman1]

Or just do what AMD does on their reference cards and write protect the secondary BIOS. There's no way to flash the secondary BIOS on my reference Vega 64 with ATIFlash.
View attachment 111787

Lets see if @BlueFlame BlueFresponds

 

[BlueFlame]

Lets see if @BlueFlame BlueFresponds

I'll try removing the drivers and booting with the bricked card again but this time I'll immediately start installing the amd vega drivers.

 

[eidairaman1]

I'll try removing the drivers and booting with the bricked card again but this time I'll immediately start installing the amd vega drivers.

Try without drivers...

 

[BlueFlame]

Boot with the RX 580. Then use DDU to uninstall the drivers and shutdown the PC.
View attachment 111768

Then install JUST the Vega 56 and try booting into Windows again.

Ok so I'm in Windows which is an improvement but flashing doesn't work. I've attached a text file with data for both of my bios gathered by using the AtiFlash -ai command. I've tried using "unlockrom" but it doesn't work.

Try without drivers...

I got into Windows but AtiFlash isn't working. It keeps saying Rom not erased. I've tried using unlockrom command but it doesn't work. I've attached a text file with my bios information gathered from -ai command.

Try without drivers...

UPDATE: I flashed the original "full performance" bios over the reserve slow bios but when I tried to install the amd vega drivers my PC restarted. At least it still let's me boot into Windows. The weird thing is that I keep getting a blank space under bios p/n so I guess that's why the drivers don't want to install?

I don't know what more to do. Like since the flash is technically working what next?

Now I can open GPUZ without the PC crashing but I'm getting a lot of "unknowns" in some of the sections.

 

[eidairaman1]

Ok so I'm in Windows which is an improvement but flashing doesn't work. I've attached a text file with data for both of my bios gathered by using the AtiFlash -ai command. I've tried using "unlockrom" but it doesn't work.



I got into Windows but AtiFlash isn't working. It keeps saying Rom not erased. I've tried using unlockrom command but it doesn't work. I've attached a text file with my bios information gathered from -ai command.



UPDATE: I flashed the original "full performance" bios over the reserve slow bios but when I tried to install the amd vega drivers my PC restarted. At least it still let's me boot into Windows. The weird thing is that I keep getting a blank space under bios p/n so I guess that's why the drivers don't want to install?

I don't know what more to do. Like since the flash is technically working what next?

Since the gpu is in hard lock, you will need to see this link.

https://www.techpowerup.com/forums/threads/bios-980-gtx-ti-flash.249644/page-2#post-3952037

There are links in my signature too.

Also another note here are 2 videos

 

[BlueFlame]

Since the gpu is in hard lock, you will need to see this link.

https://www.techpowerup.com/forums/threads/bios-980-gtx-ti-flash.249644/page-2#post-3952037

There are links in my signature too.

Also another note here are 2 videos

Holly shit. I decided to try updating the driver via Device Manager and it worked???!!! Now I just need to figure out how to get the actual AMD driver installed so I can have access to all of the features.

 

[MrGenius]

Nice! You should be able to install everything else by using the installers in the AMD folder(C:\AMD). That works for me most of the time. It can be a little tricky though...sometimes. But if you keep messing with it you'll probably figure it out. I usually do anyway...

BTW...are you on Windows 7 or 10? Or...God forbid...8?

Also...nothing wrong with the Flashcat. But there are MUCH cheaper, and equally effective, tools.
https://www.overclock.net/forum/74-...unbrick-flash-almost-any-card-amd-nvidia.html

Oh...and I almost forgot. That p/n is just the BIOS part number. It doesn't mean anything. It can be whatever, doesn't matter. I opened the file with a hex editor and found it to be "111". Not sure why that doesn't show up in ATIFlash. Maybe it's too short or something(it's usually a lot longer, like 12 or more characters). Try checking with GPU-Z under the Advanced tab > AMD BIOS.

EDIT: Somehow I glazed over the "111" here.

 

[BlueFlame]

Ok so it let me update the drivers via AMD's installation software but I get an error when I try to access Radeon Settings. I also noticed that when I got to device manager and click driver details on Vega, a lot of the the files have "Unknown" listed under Provider etc. I've attached a picture. I still don't have a bios p/n thing listed in atiflash, but GPUZ is reporting everything correctly.

At this point my theory is that the bios flash was technically sucessful but for whatever reason the bios doesn't have a number and that somehow is messing with the AMD drivers?

Another thing I just noticed is that in GPUZ under Driver Signature it says Unknown. I'm going to sleep so tomorrow I guess I'll try to use DDU and then re-install the drivers.

 

[MrGenius]

At this point my theory is that the bios flash was technically sucessful but for whatever reason the bios doesn't have a number and that somehow is messing with the AMD drivers?

Well...when you get back to us...make a copy of the BIOS with GPU-Z and attach it to a post here(put it in a zipped folder first). And I'll check it against the known good file in the database. I doubt it will be any different. But it'll be good to know if it is or isn't. I'm betting the problem is not the BIOS however. I'm onto something suspicious going on with ATIFlash that might be causing these problems(not just you). Something just doesn't add up with the size of the file and the size it's trying to program. Not sure what to make of it. Don't seem right to me though. Nope. Barking up the wrong tree...

 

[BlueFlame]

Well...when you get back to us...make a copy of the BIOS with GPU-Z and attach it to a post here(put it in a zipped folder first). And I'll check it against the known good file in the database. I doubt it will be any different. But it'll be good to know if it is or isn't. I'm betting the problem is not the BIOS however. I'm onto something suspicious going on with ATIFlash that might be causing these problems(not just you). Something just doesn't add up with the size of the file and the size it's trying to program. Not sure what to make of it. Don't seem right to me though. Nope. Barking up the wrong tree...

Here is the stuff from GPUZ: http://gpuz.techpowerup.com/18/12/04/8eu.png
http://gpuz.techpowerup.com/18/12/04/7m9.png

I guess I'll just keep trying to use DDU for the drivers then. I'm on Windows 10 1709. Do you have any idea why it won't let me flash the other bios and unlockrom doesn't work?

UPDATE: After using DDU again and this time installing AMD's drivers directly from the extracted folder in C, everything went smoothly! I'm able to OC the card and it's been stable in a short FireStrike Extreme run. GPUZ now shows Beta under Digital Signature. In device manager it still says Unknown in the driver details of the gpu so I'm kind of worried that'll come back to bite me later if I don't sort it out?

 

[Splinterdog]

Hello guys,

I have a PowerColor Red Dragon Vega 56 with Samsung memory and I tried flashing it to a Red Devil Vega 64 but it didn't work.

I'm sorry for butting in here and please excuse my ignorance.
Why would you want to flash a Vega 56 GPU to a Vega 64, in the first place?

 

[BlueFlame]

I'm sorry for butting in here and please excuse my ignorance.
Why would you want to flash a Vega 56 GPU to a Vega 64, in the first place?

Well the HBM voltage goes from 1.25 to 1.35 which will let you reach around 1050 MHz and above speed, which is important for this architecture. Currently I'm locked to 1.25 and the most I can do is 950 MHz. You also get a higher power limit which let's you push the clocks more.
From what I was reading online, if you're on a reference card flashing is almost 100% guarenteed to suceed and the second bios is write protected so you can't really make anything worse. The problem is that at the time I didn't realize this only applies to reference models and flashing AIB ones is close to impossible.

 

[eidairaman1]

Well the HBM voltage goes from 1.25 to 1.35 which will let you reach around 1050 MHz and above speed, which is important for this architecture. Currently I'm locked to 1.25 and the most I can do is 950 MHz. You also get a higher power limit which let's you push the clocks more.
From what I was reading online, if you're on a reference card flashing is almost 100% guarenteed to suceed and the second bios is write protected so you can't really make anything worse. The problem is that at the time I didn't realize this only applies to reference models and flashing AIB ones is close to impossible.

I asked you for a few things to locate the correct bios of the card, do you want the card fixed?

Also if force flash does not work with the correct bios of the card then you need to see a Link I posted earlier.

 

[Hellfire]

I asked you for a few things to locate the correct bios of the card, do you want the card fixed?

Also if force flash does not work with the correct bios of the card then you need to see a Link I posted earlier.

But that's too difficult to do...... Short cuts and bricking cards ftw... [/Sarcasm]

 

[BlueFlame]

I asked you for a few things to locate the correct bios of the card, do you want the card fixed?

Also if force flash does not work with the correct bios of the card then you need to see a Link I posted earlier.

Wait what do you mean? I've uploaded screenshots of GPUZ as well as a text file with the information form atiflash. I'll attach the actual bios here but I think the bios problem is fixed. I just need to get Windows/AMD give me an actual driver signature. Both of these are the same bios.

 

[MrGenius]

http://gpuz.techpowerup.com/18/12/04/8eu.png

Cool. The BIOS part # is 111. Thought so.

In device manager it still says Unknown in the driver details of the gpu so I'm kind of worried that'll come back to bite me later if I don't sort it out?

It won't. That's normal. Mine says the same thing. Sorry I never bothered to check until now.

...I think the bios problem is fixed. I just need to get Windows/AMD give me an actual driver signature. Both of these are the same bios.

The BIOS problem IS fixed. Both of those BIOS files are identical to this verified one in the database.

Way to go man! You fixed your card!