I already shared this in different thread, but I decided to make own thread for it 
Note: If you want to increase power limits of your card, check also this guide: www.overclock.net/posts/29481571/
Note2: @ApolloX30 has in his thread (3rd and 4th spoiler) list of tested cards vs vbioses. When you flash some bios (no matter is successfully or not) and it's not listed in the table, please tag him here and write your experience. Thanks!
Here is also google sheet
This is a modded tool for flashing AMD cards (including RDNA4 with version 879) even when SSID mismatch.
Here is screenshot by @RedF on RDNA4:
The 616 version includes also modifications, so it's possible to flash also over corrupted bios in RDNA3 cards. More info in the original post: https://www.overclock.net/posts/29431108/
I will also add some general information about vbios, which I collected meanwhile:
Step-by-step:
Note: for simplicity I wrote in the steps amdvbflash. Of course if it's command in cmd, replace it with correct name of the .exe utility (e.g. amdvbflash_879_Moded_v1).
Summary:
amdvbflash 5.0.616.0 v2 - up to RDNA3 cross flash and ability to flash over corrupted vbios
amdvbflash 5.0.879.0 v1 - up to RDNA4 cross flash
Warning: Use this tool at your own risk! I bypassed some exceptions in the SW, so in worse case it can lead to even more corrupted vbios! Be sure that you have some backup solution in hand (CH341, second bios switch)! For sure reflash the vbios again using non modified amdvbflash, with PartNumber forcing switch only (amdvbflash -p 0 romfile.rom -fp) until it says that the bioses are the same!
Note: If you want to increase power limits of your card, check also this guide: www.overclock.net/posts/29481571/
Note2: @ApolloX30 has in his thread (3rd and 4th spoiler) list of tested cards vs vbioses. When you flash some bios (no matter is successfully or not) and it's not listed in the table, please tag him here and write your experience. Thanks!
Here is also google sheet
This is a modded tool for flashing AMD cards (including RDNA4 with version 879) even when SSID mismatch.
Here is screenshot by @RedF on RDNA4:
The 616 version includes also modifications, so it's possible to flash also over corrupted bios in RDNA3 cards. More info in the original post: https://www.overclock.net/posts/29431108/
I will also add some general information about vbios, which I collected meanwhile:
- Turn OFF the PC - After bios flash, turn off the PC completely, not just reboot.
- Dual partition vbios - from RDNA3 the bios in the card is dual. And I don't mean HW switch for changing OC/Silent bioses. The bios is dual in one ROM chip. One partition is always active and second inactive. The flash tool always flash the inactive partition and this flashed partition became active after successful boot. This luckily can save your card from bricking, when bios flash fails.
In amdvbflash you can check both partitions using command
-ai --active
-ai --inactive
Here is nice drawing by @RedF
- Flash multiple times - After successful flash, I recommend to flash the card only with PartNumber force switch (so only amdvbflash -p 0 romfile.rom -fp), until the tool says that the bios file is the same as in the card (power cycle between each flash of course). For some reason it can take up to 3 flashes. Don't post bios backups without this, as it can lead to flash fail on other cards!
The reason is, that some people reported weird issues when cross-flashing RX7000 series.
E.g. power not increased, in worse case black screen after reboot. - Bios changes when flashing - When you flash bios and read it back, it will not be 1:1. It's normal behavior noticed on RDNA3 (and maybe other too). The bios ROM contains some partitions, which are changed with each flash. Some bytes even looks like simple counter. That's also reason why in TPU vbios database you can find so many bioses for RDNA3 which should be identical. Slightly more info here: https://www.overclock.net/posts/29458202/
- GPU-Z bios info - GPU-Z is reading only the first partition of the vbios and doesn't care about active/inactive state. That's why you can still see the old bios version after a first flash.
Step-by-step:
Note: for simplicity I wrote in the steps amdvbflash. Of course if it's command in cmd, replace it with correct name of the .exe utility (e.g. amdvbflash_879_Moded_v1).
- Download amdvbflash, flashing drivers and DDU.
- Extract amdvbflash to some folder and put vbios in the same folder.
- Restart to safe mode
- DDU old drivers (without reboot)
- Install special drivers for flashing (thanks TechPowerUp for them)
- open CMD as Admin and cd into folder with amdvbflash
- check GPU first with
amdvbflash -i
and get correct number of your card (important if you have multiple GPU, e.g. integrated).
This number is referenced in following commands by # - Always do backup of original vbios! Use command
amdvbflash -s # backup_name.rom
- Flash vbios using command
amdvbflash -p # vbios_name.rom -fp -fv -fa
- After flashing power down the PC (don't just reboot).
- After you are done with flashing, it's recommended to remove the flashing drivers (because of potential security risk)
Summary:
amdvbflash 5.0.616.0 v2 - up to RDNA3 cross flash and ability to flash over corrupted vbios
amdvbflash 5.0.879.0 v1 - up to RDNA4 cross flash
Warning: Use this tool at your own risk! I bypassed some exceptions in the SW, so in worse case it can lead to even more corrupted vbios! Be sure that you have some backup solution in hand (CH341, second bios switch)! For sure reflash the vbios again using non modified amdvbflash, with PartNumber forcing switch only (amdvbflash -p 0 romfile.rom -fp) until it says that the bioses are the same!