i think we talk at cross purposes here…
so u really know that the firmware tool is nothing more than nvflash with gui and all it does is updating the gop? That is what i wanted to be sure on, not just suspect it…
ok i compared vbios before and after update by dp firmware update tool.
the only difference is the gop.
and i use nvflash to update gop manually , then backup it to get a new vbios file , which is identical to the vbios file that update by dp firmware update tool.
and if you check the string of dp firmware update tool , you will find words including nvflash.
thx, that is what i wanted to know. 
so, completely unnecessary tool for us…
Thanks, any guide on how to manually flash till a new GOP Updater version is out? (I think this should be in the OP)
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
You mean the signature hack for the Radeons? Pascal BIOS is protected, no mods possible.
Thanks, nvflash -u file.efirom doesn’t work, it look that -u is an invalid parameter…
Nope, it is a valid command. You can find it under "Commands and Options" in the nvflash readme file. Also, dsanke mentioned this on the previous page.
“Don’t quote people, it’s slowing down the site, and making it unreadable”. Seriously?!
1. Buy better servers.
2. That’s a load of crap. Please don’t insult my intelligence. What you actually mean is…you want to make it unreadable(because you’d rather not upgrade your servers). Great idea!!! 
@Shonk , in reply to your post , VBE7 disables/deactivates UEFI GOP. You need to manually re-enable/activate it with a hex editor(info found here), or with a tool(such as the HD 7XXX Series GOP UEFI Bios Patcher Beta). You will also need to use a patched UEFI GOP module with the edited legacy BIOS for an R9 280X. I would suggest using the patched version of AMD GOP 1.65.0.15.50 posted by hellm here. Which is the latest pre-Vega compatible UEFI GOP module. You might also need to disable secure boot.
@wyhtc , I found a VBIOS in the TPU database with AMD GOP 2.2.0.0.0
https://www.techpowerup.com/vgabios/200963/200963
AMD GOP 2.2.0.0.0_newGOP.zip (84.8 KB)
@rootuser123
1. Open the patched EFIROM(found here labeled AMD GOP 1.65.0.15.50_signed_68337C30_compr.efirom.zip).
2. From the beginning of the hex select a block with length E434 and copy(ie. everything before the end padding).
3. Open the BIOS that needs patched and find the beginning of the EFI ROM image hex(hex “55 AA” just before the second instance of text-string “PCIR”).
4. From the beginning of the EFI ROM image hex select a block with length E434.
5. Paste write to that block.
6. Replace any extra bits after the block(between the end of the EFI ROM image and padding) with padding(FF) if required.
7. Save the file.
Simple enough?
@MrGenius I want to actually patch the GOP myself using lordkag’s method, not replace the GOP manually in the vBIOS using hex editor.
It is not a method, it is a hack. We can apply it to other versions, like i did, but it will always be the same file afterwards. So, “patching” the GOP with a method isn’t the case here, this only has to be done once.
If you have a vanilla BIOS, you only need the right dev id. If you want to mod your BIOS, copy over the lordkag version.
If you want to know how the hack works, unpack the modded version and compare it with the original GOP. Then you need some info to know what these bytes actually mean. I don’t really know how to get this information…
OK, I solved using nvflash u gop.efirom, without the "-": but I get the invalid extension. Obviously, filename is correct… Any hint?
i have made the same mistake, forgot the “-” before the u. Then you get this weird error message.
There has to be some other problem. Maybe wrong nvflash … but then you wouldn’t get the error? Maybe you should just tell us step by step exactly what you are doing? Would max the chance that someone can help you.
I edited the 2 bytes with HXD to 06 1B (1080 Ti), then renamed the efirom to confortable name.efirom, then from admin CMD I executed the nvflash64 u name.efirom. I tried different nvflash versions, 32 and 64 bits, always getting the "Firmware image filename must have a valid extension. ( .rom .nvr .efr .efirom )"… It looks strange.
Hmm. I just figured out there is a newer version of nvflash available. I used 5.427, changed the id as well, named it 3000B.efirom. Then (after i forgot the - and got the same error message…) i typed "nvflash -u 3000B.efirom" and after pressing y the flash happened. nvflash also corrected file length and what not.
@hellm
Where did you get version 5.427 of nvflash? Also my 1080’s have an unmodified firmware as I compared against Techpowerup database. The GOP version is 30007. So I can just update to 3000B by typing ‘nvflash -u 3000B.efirom’ ? I have two in SLI though.
Thanks.
Also at offset x26 + x28 in the illustration you posted I see 1C and 03 appear again. You mentioned to change offset x22-23 only. Should the other offset be altered? Thanks.
Edit: Looking into my original rom file where me device id was 80 1B I see 1C 03 at offset x26+x28 so I would say no you don’t have to alter those bytes (to answer my own question).