Sorry to double post but I discovered something very interesting I wanted to share. For starters I was able to update my GOP to 3000B by changing the device id and flashing with the latest nvflash64 Version 5.469.0. That was a success!
Heres the interesting part. For a while I could only post video onto my second installed GPU. That was since Asus upgraded the bios past 3000 rom version for my Z170 WS board. If the displayport cable was installed to the first card, even if I set the default gpu manually in bios settings, I would not get a picture on the screen. So I dumped my vbios on the first card which had GOP version 30007 and assumed the second card had the same GOP…
Not so!!!
After 'nvflash64 --index=[gpu number 0 or 1] -u 3000B.efirom - NvFlash was kind enough to mention that it had successfully updated 3000A to 3000B! So I must have had two different GOP’s with the same firmware version and this board preferentially would only post to the GPU with the latest GOP!!!
Unbelievable!!!
Thanks everyone who posted earlier detailing how you were able to update the GOP manually. Thank you all.
Latest nvflash is 5.469.0…
EDIT: with this version, I succeded, using the -u command.
About that version 5.469.0 . . It resizes the command window. Scared me to death! Normal behavior I guess.
Yup, LOL! But don’t worry you can usually blind flash a graphic card, or boot with integrated GPU and flash again…
Hi, I am trying to use this program to add the necessary for UEFI to a rom dump I made with GPU-z and then dragged it on top of GOPupd.bat as per the instructions. I received the following 2 lines:
Data after ROM and not part of EFI! Please report it!
Unable to recover extra data at the same offset 0xFF80! Please report it!
which it said to report (and so I am) and I think as the resulting rom file is way over size at 186kB that it is no good to flash (it should be 128kB I believe but the starting rom was already 128kB which I guess was full of padding).
So am I doing something wrong or does it not work with my romdump ? (its from an ATI 5450 Silent 1 Gb GDDR3 model). I am using GOPUpd_v1.9.5 as per the OP.
Thanks in advance.
I have used Hex editor before for CPU microcodes and stuff. But with your quide I got a message from MB in boot:
and then forcing CSM - mode.
### EDIT ###
You have to change the device id, so it matches your card. At least i think this has to be done manually. Works for sure. I recommend HxD.
you find the device id at offset 0x22-0x23:
03 1C -> 0x1C03 -> GTX 1060 6GB
find your device id:
http://envytools.readthedocs.io/en/lates…ciid.html#gp104
for the 1070Ti:
0x1B82 -> 82 1B
then u can simply update the UEFI/GOP with nvflash using this command:
nvflash -u file.efirom
This fix it. Thanks for you guys!
BUT! I cannot get into the bios any more.
I think it issue with showing up graphics of the bios? Platform Asus X99.
No… you should be able to access your mainboard UEFI as usual, afaik.
What graphics card do you have, Geforce or Radeon?
Asus X99-A/USB 3.1, R9 Nano.
I think the problem is some where else, because I not able to get into the bios with orginal amd gop update firmware either (https://community.amd.com/community/gaming/blog/2016/04/05/radeon-r9-fury-nano-uefi-firmware).
But I don’t have any glue what could be a problem.
To update the UEFI on a Radeon, you have to edit the sub id, and then copy&paste. If you get something wrong with file length or didn’t erase all of the old GOP, you might get problems. Other than that, no idea…
A very good thread about Fiji BIOS modding is found here:
Fiji Bios Editing ( Fury / Fury X / Nano / Radeon Pro Duo )
And here is more knowledge:
[Official] AMD R9 Radeon FURY / NANO / X / Pro DUO FIJI Owners Club
Thanks for you help. I figured out that bios is showed up with hdmi! Displayport have some issues, but working under CSM. Maybe it could be also the monitor that can’t handle the signal? I have Asus MG279Q / AMD Radeon R9 Nano.
AMD GOP 2.4.0.0.0.MA_signed_D7DC9A98，from Powercolor, Nano, Radeon RX Vega, (1590 / 800).
VGA Bios Collection: Powercolor Vega 56 8192 MB | TechPowerUp https://www.techpowerup.com/vgabios/202224/202224
[[File:QQ??20180716161356.png|none|auto]]
AMD GOP 2.4.0.0.0.MA_signed_D7DC9A98.zip (83.8 KB)
Sorry but AMD HD 6800 can be upgraded with AMD GOP 2.X? Or stay on 1.65?
1.xx previous Radeons including Polaris
2.xx Vega (and future releases?)
New RX 580 released (MSI RX 580 Mech 2). Bios: https://www.techpowerup.com/vgabios/2030…580-8192-180503
2
3
4
AtiFlash.exe -biosfileinfo MSI.RX580.8192.180503.rom
...
GOP Driver Name: AMD GOP X64 Release Driver Rev.1.66.0.15.50.Apr 23 2018.17:50:07
...
Thank you, successfully updated to v1.66.0.15.50 my Asus Dual-RX480-O4G (ID = 1002-67DF) vBios with "GOP_Updater_1.9.8".
I had to edit the #GOP_Database.txt after extracting from the MSI efi.rom and also edit the AMD_GOP_IDs.txt in order to update, thus it was still showing the lower version 1.65.0.15.50 in the Gop Database.
Flashed with the "atiflash_277" tool.
Here is the magic version with lordkag’s hack.
Device id at offset 0x22-0x23 is 0x67DF (470/480/570/580); has to be changed for use with other cards.
AMD GOP 1.66.0.15.50_signed_EEB7AA71_compr.efirom.zip (57.4 KB)
Well, I love magic, but what’s inside the hack?
It doesn’t have the same checksum crc32: “AMD GOP 1.66.0.15.50_signed_7426BBE8_compr.efirom” inside the .zip attached file (AMD GOP 1.66.0.15.50_signed_EEB7AA71_compr.efirom.zip).
You still have to edit the AMD_GOP_IDs.txt to enter 1002_67DF… Seems to be ok anyway!
Well I’m back to AMD Gop version 1.65.0.15.50…with latest Gop I lost the “0dB fan” function on my Asus RX 480 graphic…with both MSI and Lordkag’s hack
Yes, i didn’t change the filename. Wasn’t noticed with 1.63/65, and it is just the filename. sorry about that, but i don’t think it will be a problem.
With the zero fan function, how does your fan behave now? Is there a minimum where the fan rpm remains, or is the fan spinning up at a certain temp? This is a Asus tool that is telling zero fan is off?
@hellm
It wasn’t a problem with the filename, I could update in anyways…
About the 0dB fan function, when updating to latest include Lordkag’s one, the function disappear of the UI (those two little check boxes off & on) and in advanced mode it showed fans at -35%…soon as I went back to previous, check boxes on top right of the UI reappeared and showed right value for fans + 0% (auto) or +35% (depends on my settings) in advanced mode. Yes this is Asus telling by erasing the 0dB function off the UI, so I have no control on those check boxes
Could be the latest vBios not supporting some Asus functions also…