I fixed it by changing the path to my python in the .bat file. I have python 3.7 installed in "D:\Users\FPSUs\AppData\Local\Programs\Python\Python37\Python3.exe"

@FPSUsername

No issues at all updating to 0x20011

The problem isn't updating the gop, it's flashing the bios with the updated gop. Nvflash64 is giving me the error

Let me try with my VGA card. Stay tuned.

I've used NVflash 5.236 modified version and no issues at all in flashing the generated updated gop firmware.

I'll try once I have access to my pc

@plutomaniac
That is an elegant solution and I will have to test it against my entire database. I really wish I could use it, but my main concern is that the version can have anywhere between 8 and 12 chars, followed by date, thus the length of the string is critical. My feeling is that I will end up with some bits of the date in some of the versions. Still, without testing this is just chattering, so I will get back to you after I have fully compared it against my entire repo of AMD GOPs. Also, using "#!/usr/bin/env python3" only works on Linux. On Windows, if you have Py2 and Py3 side by side, and if you updated Py2 at some point and forgot to unselect the py launcher association, it will mix them up. Bottom line, on Windows it is the last installed Python launcher that will determine which Python to call. At least this is what happened to me.

@FPSUsername
I think you missed the first two posts. It says to drop the file on GOPupd.bat, not on GOPupd.py. There are some steps under the hood, like extracting the EFI ROM, decompress it with UEFIRomExtract.exe, check the decompressed EFI driver. Maybe I can glue them together inside the python script, but since UEFIRomExtract.exe is needed, I decided to release this tool as Windows centric and make the GOPupd.bat as master of ceremony. The only error I can see from my part is locating the Python path, which is not that easy, given the multiple versions and multiple paths. Can you check with the attached file, by replacing the one from 1.9.6 package?

@lordkag you can also call it with:
python3 gopupd.py bios.bin gop_upd

That's how I uptaded from 0x2000B to 0x2000E

That batch file from #593 gives the same python not found issue, but I managed to flash it with the certificate bypass nvflash. This is the output:

@plutomaniac
I checked your solution on all my repo and it works! You seem to have reached the AMD enlightenment. Or, in a Bond-Connery voice, "You've been spending too much time with the enemy, mister Pluto. You've been corrupted!". I had to slightly adjust on the date extraction, as there are some cases you weren't aware of, but it is way easier now. Just not too easy, we don't want to upset the AMD gods.



You are also right about the python shebang. I just remember having a meltdown after a Python 2.x update were nothing worked. And if I'm reading > this < right, it is still the Python launcher that has the last word.

Released a minor update, version 1.9.6.1 changelog:
- Updated AMD version extraction, thanks to Plutomaniac.
- Fixed Nvidia checksum correction. Hopefully for good.

Zitat von lordkag im Beitrag #598

---

Released a minor update, version 1.9.6.1 changelog:
- Updated AMD version extraction, thanks to Plutomaniac.
- Fixed Nvidia checksum correction. Hopefully for good.

---

@gpvecchi 2nd post always. Only like "beta" releases are posted in between the pages I'd say.