i ran the GOPupd.bat and it said i should post my find here. I already hacked this version successfully by copy-pasting lordkag’s work on 1.60. But still, here is the newest pre-Vega
update: apparently i am to lazy to read… sry for double posting…
added the hacked version; working now, fixed the header.
device id at offset 22-23 is 67DF (470/480/570/580); has to be changed for use with other cards.
Hi, there is a Gigabyte AMD HD 7970 which works fine with a full HD monitor but with a 21:9 screen (2560x1080) it is not possible to access the PC BIOS as there is no valid signal until it enters windows. will a more recent GOP file solve the issue? thanks Edit: will there be any real advantage to use the latest 1.63.xx GOP provided by @Sylar76 , considered it’s such an old card?|addpics|bpu-5-c558.jpg-invaddpicsinvv|/addpics|
First…thank you sir! I can verify that it works. Even better than expected. I thought you had to use the patched atikmdag.sys and turn Secure Boot OFF to get it to work. But apparently you don’t. Since all I did was manually install your hacked .EFIROM File(after fixing the Device ID), and I can now boot in "pure UEFI mode"(CSM=OFF, SB=ON, FB=ON) without issues. Why is that? I’m running a HEAVILY modified BIOS, the latest drivers with an untouched atikmdag.sys, and Secure Boot is ON. How is it working? I don’t get it. All I do know is without a hacked .EFIROM File installed it doesn’t. I get the black screen during boot.
Second…what all gets modified when you do that? By that I mean is it still essentially the newer GOP version 1.63? It’s not version 1.60 dressed up like version 1.63 right? Are whatever improvements over version 1.60 still in place? I realize these are stupid questions. Obviously you wouldn’t bother doing it otherwise. I’m just trying to understand it better.
On another note…as speculated, version 2.0 doesn’t work on older cards. At least not on my older card(R9 280X). And I would presume any older card that originally came with GOP version 1.63 or earlier. What’s totally weird though is I found a BIOS in the TPU database for an XFX RX 560 4GB that has GOP version 2.0. What’s up with that? Can it(version 2.0), and/or can an older BIOS, be modified to work on older cards? Most(all that I’m aware of) other RX 560s came with GOP version 1.62 or 1.63. How did they make it work on an RX 560? I can’t see any obvious differences in the BIOS. It looks to me like all they did was plug version 2.0 in and somehow it works. I mean I assume it works. I don’t have that card with that BIOS to verify. And I guess someone could have put it together themselves and uploaded it to TPU broken. Seems unlikely anyone would though.
One more question…for anyone reading…how do you post on this site without replying to someone else’s post? I looked around for quite a while and never figured it out. I’m a member on MANY forums and I’ve never seen one like this without an obvious place to start typing up a post.
EDIT: I forgot to mention that updating my GOP from version 1.53(stock BIOS) to version 1.63 cut my UEFI GOP boot times roughly in half. So basically my PC boots twice as fast now when using UEFI GOP boot. If your asking yourself if it’s worth updating your GOP to a newer version…there’s your answer.
Hi,i recently upgraded to a Pascal GPU and from what i’ve read their vbioses are locked and now i’m worry that if i try to update the uefi/gop it might brick the card.My question is did anyone here had a success flashing it if yes if it’s not too much trouble can you post short tutorial on how to(just need the flashing part,i know how to do the rest).Thank you.
Since I’ve done that in my GTX1080, updating the GOP from 30004 to 30008 without any problem and it boots purely fine in uefi mode with csm=off and sb=on, It shouldn’t be of any problem. No specific procedure need to be performed, just drop the original bios on the bat, get the modded bios, find a nvflash and flash it in. But of course I can’t guarantee that it will work 100%
I have a problem with my card gtx970 pny. If i use display port in uefi mode (disabled cms) the monitor dont show bios(black screen), If u use hdmi it works ok. In legacy mode display port shows bios screen. It is possible an update to vbios gop to fix this? My motherboard btw is an asrock z97 anniversary.
Sorry but i dont know how to see crc but i upload both files. Can i flash it? I will use the same version of nvflash which i use to modify my vbios.
-Edit: Basically later i found the newer nvidia gop updater packer from Sylar76. I updated my vbios gop to the latest. And then i use the modded nvflash from joe dirt to flash my card. My problem is not solved but anyway the flash work as intended.
EDIT by Fernando: Inserted screenshot from an insecure source replaced by a resized one, which has been directly attached by using the Forum software (can be enlarged by clicking onto it)
well, i don’t know why on your system secure boot can be activated. I really just copypasted lordkags work. And that would be some bytes that affect all this checksum-whatsoever thing, nothing more, so it is a real 1.63.
I also did this for version 2.0, but since Vega is unmoddable i thought there would be no use for it. if you want to give it a try…
I just noticed that in the first 2 lines of log, there is the message that there is no EFI Rom present. So that means that i cannot use it for pure UEFI boot, correct ?
I first need an UEFI enabled rom for my card and then mod with the GOP updater ?
The file named Tahiti_updGOP.rom has already been updated with GOP version 1.63.0.15.50. You can check it by dropping that file on the #AMD_ROM_Info batch file. It will verify that the update was successful. So all you need to do now is flash Tahiti_updGOP.rom on your card and pure UEFI boot should work. Unless the legacy part of the BIOS was modified. If you want to use a modified BIOS you need to use a modified GOP version for pure UEFI to work with it. Such as the "hacked" version 1.63.0.15.50 provided by hellm in post #361.
The legacy part was not modified from me, if that is what you mean. I just grabbed it from my stock card. My only concern is that the Tahiti_updGOP.rom is 122KB when the original file from my card was 128KB.
I mentioned the part about a modified BIOS for anyone reading this thread(not just you). Which will hopefully save someone the time of having to read through this entire thread to figure it out(like I had to).
Anyway, the updated BIOS file being a little smaller in size isn’t any cause for concern. There’s "padding"(unused bits) in the BIOS file that get deleted by the updater. The padding isn’t necessary and is usually added by whichever program is used to dump the BIOS. Meaning the original file probably wasn’t 128KB until you dumped it. I don’t know the exact reasoning behind why the padding is added. Other than it makes the file large enough to completely fill the EEPROM chip that the BIOS is stored on. Which, as stated, isn’t required. And I don’t know why somebody thinks it’s a good idea to do so. But somebody obviously does…so that’s why you get that size when you dump the BIOS. If you wanted to you could add the padding manually to make it 128KB. Or flash it and then dump it(with GPU-Z or atiflash). I can’t provide you with a good reason why you should though. It won’t fix anything or make anything work better.
I can verify that it works. Even better than expected. I thought you had to use the patched atikmdag.sys and turn Secure Boot OFF to get it to work. But apparently you don’t. Since all I did was manually install your hacked .EFIROM File(after fixing the Device ID), and I can now boot in "pure UEFI mode"(CSM=OFF, SB=ON, FB=ON) without issues. Why is that? I’m running a HEAVILY modified BIOS, the latest drivers with an untouched atikmdag.sys, and Secure Boot is ON. How is it working? I don’t get it. All I do know is without a hacked .EFIROM File installed it doesn’t. I get the black screen during boot.
