@plutomaniac and @all

I've uploaded a folder on my google drive, including .py source as well as a preliminary support for VEGA cards !!!!

Please someone test both versions please.

@plutomaniac

VEGA Uefi table, at offset showing the DRV Version is shorter (4 bytes) than previous ati gop tables. Editing the .py source makes vega gop properly displayed but has the collateral effect
of making normal amd cards not properly detected. The relative string is "t_version...." and I don't know how write a string that can consider both lenghts (short and long). If you wish and
have time it would be nice to take a look at it. Thanks !!!

Zitat von plutomaniac im Beitrag #572

---

Please provide with two samples which differ.

---

Sorry for the absence and the possible ranting in this comeback post. I took some time off for some personal issues, ended up enjoying too much the available time and the procrastination that accompanies it, wanted to return with more palpable results and thus postponed the moment with days and weeks... and months flew by without doing any real progress - or any work for that matter. Rather than expecting the greatness/impossible to show up, I should have let the small things fill in the cracks. Which is why I will quickly post some updates and answer any questions or PMs in the following weeks.

I would like to thank those that helped, expressed concerns regarding the future of the app, or simply mentioned my name. It is what makes any return not only easier, but rather necessary. It is sad that not everyone finds the same culture of sharing. I see people like Fernando, Plutomaniac, Pacman and Gupsterg (to name a few) that spend so much time in helping and providing drivers/firmwares/info/etc. for everyone and anyone, which makes me feel so humble in my limited interaction. And then I see the case of the Polaris Bios Editing thread on OCN, where the single phrase "added the BIOS signature check to the pixel clock patcher" is used to wash away any effort I made. It's not that I need my name to shine over others, I can very well let my work speak for myself, be it modest or better. I know it is only a few bytes of change (most patches or moddings are), but those bytes are the pinnacle of a few hours/days of research, a few brilliant ideas and a few brave souls to test the patch. I'm all in favor of using an automated solution and don't want it to be in any way altered or removed, nor do I need a royal seat at the table, nor do I desire a war between sites or a clash between members. But come on, was it that hard to add in small letters, anywhere, "thanks to xxx for finding a patch and to yyy and zzz for testing"? It is moments like these that make me leave the scene forever and enjoy my free time as I should be. Imagine the lockdown Nvidia has imposed on its latest cards, being forced on AMD users - and with Vega it might be so. If some of you had the pleasure of using a modded VBIOS on patched Windows drivers AND patched GOP/EFI drivers, it is because someone took the time to solve a problem that wasn't even his to begin with. Imagine that beginners (in reversing) like me and JoeDirt brought the joy of using your hard payed hardware to its fully potential, WITHOUT asking or expecting anything in return. And to see this work simply copy-pasted without a hint towards the original provider, it is simply heart-breaking coming from someone who should know better the value of this work. Anyway, this is not as important as it would seem from the amount of words I have dedicated to it (I actually feel ashamed for having to even mention this), but rather a thorn that I wanted to remove for some time.

I don't know if I ever thanked/credited enough to Sonix, CodeRush, Plutomaniac, Pacman, Donovan6000 and all others who helped build bridges of knowledge, so here is to you, you wonderful bastards human beings! And robots!

Back to fun stuff. I will edit this post in the future to give all the necessary credits and add any fix/feature I might have forgotten. Here is version 1.9.6 changelog:

- special thanks to Sylar76 for maintaining this tool and this thread alive.
- updated a few GOPs, with the help of Sylar76, TPU, [...]
- updated AMD to 1.66.0.15.50, GF10x to 0x1002B, GK1xx to 0x10038, GM1xx to 0x10036, GM2xx to 0x20011, GP1xx to 0x3000C, GV1xx to 0x40006, GM1xx_MXM to 0x10035.
- added Volta support
- patched the latest AMD GOP. Used a more generic patch, like the one I used for the drivers.
- use "yp" or "ypat" without the quotes to use the modded GOP instead of the original one. Use them when asked "Do you want to update GOP to ..."
- patched AtiFlash (using it instead of GopInfoX) to avoid loading and hooking the drivers at Windows startup. For the love of all things, AMD, why would I need these drivers to be loaded *always* at logon for what may be just one time flashing or even checking the VBIOS? This is the gazillion time I find such a sloppy design on your firmware/software - and I'm not even the average researcher.
- must do something similar for Nvidia. Noticed that on recent versions of NVFlash they are hiding the extra juicy details on their signature blocks. And they also relaxed the checks on image integrity, thus the older NVFlash version.
- added an automated solution for the microcode case. But can't remember if it is for all cases or even finished. Yes, that's the state of my work!
- fixed some Nvidia bugs. This was mostly on my part, but Nvidia isn't making things easier. More details in the next days.
- added a more robust parser of ROM and EFI, work in progress. Should have started from the beginning of GopUpd, but I honestly thought it will be just "flip a byte, fix the checksum" thing. Had I known what it will come to, I probably would have given up.
- -ISBN, -DEBUG, -ROMSCAN and -PATCHED are configs that can be set from GopUpd.bat, more on them latter.
- added a validation of GOP, using the PE checksum. Don't know if it is the flasher, the backup software (GPU-Z?) or simply AMD, but check the amount of badly formatted images from AMD side. It is simply ridiculous to have so many and makes me question the integrity of the main VBIOS as well.
- modified the version extraction code for AMD GOP. God forbid for AMD to use a clear structure! On anything!
- modified the ID extraction code. This one is on me, don't know how I missed the masked IDs or the range of IDs, as it was there all along, next to the others. Talk about ... vision. Or should I say "AMD robustness"?
- added version report for .efi and .ffs files.
- added VEGA support, but it is useless without a proper signature. I suspect there could be a way to bypass the protection, knowing this is AMD, but it requires a lot of time and work from my part; and frankly, seeing how my last attempt was treated, I'm not remotely inclined in investing any slice of time.
- can't use 2.x.x.x.x on all cards, as it is not designed for cards older than Vega. Firstly, it checks for the ID to be in range 6860-687F, 69A0-69BF, 66A0-66BF, 15D0-15EF, 7310-732F. Secondly, it seems to have removed the signature check (oh joy!), probably as it is done in hardware, but the ID check makes it still the need for a patch (oh noes!) and Secure Boot off. Thirdly, having so much code removed and being Vega only, it makes no sense in offering a patched 2.x.x.x.x GOP.
- probably introduced some bugs.

@lordkag

Hi mate,

I'm very happy to hear your voice (text) again. I'd like to thank you for the great effort you have given to us with your amazing tool and I apologize for not having thanked you enough in the past.

I'm getting ERROR: Invalid firmware image detected. when trying to flash the updated GM2xx - 0x20011 - Jan 16 2017 - 21577143 - 80A19AD5 on my GTX 960 card.

Didn't try these, but 0x2000E works.
GM2xx - 0x2000F - Jan 19 2016 - 20357017 - ACDBE171
GM2xx - 0x20010 - Feb 26 2016 - 20482337 - 3230CD4E

Edit:
Full error

BCRT Error: Certificate 2.0 verification failed
BIOS Cert 2.0 Verification Error, Update aborted.
Nothing changed!
ERROR: Invalid firmware image detected.

Oh and this:
Update Aborted - Invalid firmware image detected. Provide an Enthusiast Key to flash this firmware image.

Hi, I want to update the GOP driver of a Nvidia GT 720 (ASUS GT720-2GD3-V2/DP), I want to know which version of the program I've to use and if there is something that I've to know at the moment to modify and flash the BIOS, thank you so much for your help and excuse me for answer like a noob, but I can't read 39 pages thread, kind regards.

I have an issue using the .bat to update GOP and the python script always tells me that GOP isn't present (while it has a GOP installed)

To call python 3, I use `python3 ......` and colorama is installed

How can you select older GOP versions?

GM2xx - 0x20011 - Jan 16 2017 - 21577143 - 80A19AD5 seems to be invalid (post 578), I'm on 0x2000E but would like to test 0x2000F and 0x20010

When the script asks me if I want to install the latest version, I select no and then it quits instead of letting me select all others.

Because it allows only that. It's not been written to select which GOP table user can select.

Anyway, I'll take a look at that table as I've a GTX Titan X Maxwell with same 0x20011 and it works like a charm.

@FPSUsername

Could you link your bios please ?

Okay, thank you. Please also check at post 852, could be because you call python3 as python, I have python 2 and python 3 installed and need to have python 3 being called as python3 so it won't conflict with python 2

Here is my bios.

I also uploaded the "clean" version which was shipped by EVGA OEM (version 0x2000B I think)