@gQx@Vernnon password for v2 is 634987dvfk. No need to keep the password behind closed doors anymore all the testing that we could do is done.
@belikeimpasta sorry I have no experience with a 3060ti or any nvidia GPU since the GTX980 as that was the last era of nvidia GPUs worth tinkering with anything since then is paper not physical experience.
@Vernnon that password is for v2, not third version. I’ll have to dig around some more to find the password for v3, it might have been lost when one of my pen drives got corrupt. Patched third version doesn’t need a password, first versions password is; erm_pui,.6y8
Laptop has no uefi and any gpu with uefi gop in vBIOS causes no boot. Not sure if removing uefi gop using that method and flashing with my ch341a programmer will brick card. MXM Quadro have signature requirement in vBIOS. Idk if that mod alone will break any signature.
AFAIK no modern GPU has a “legacy only” vBIOS, they are all hybrid/UEFI now and have been for some years. The last GPU you could really dive in and mess with was the Polaris cards for AMD or the Maxwell II cards for nvidia. GPUs are boring as shit now.
Alienware M17xR3 ? - best try pascal gpu + TDP 150W is ok from MXM “lot users using more - 200W” and still works good
also this gpu is in best range for yours others HW ,.,benefits from RTX is minimal here
easy app for TDP mod - TDP tweaker “but need HWflasher + 1.8V adapter” and configure custom TDP in AFTERBURNER .,.and all works nice
if you no need QUATRO ,.,i recommend normal gtx1070 - best for you “gtx1080 need power cable”
Hybrid vBIOSes exist to support older systems that don’t support UEFI, I forget the specifics but essentially the only way to use a vBIOS in legacy mode on a UEFI system is to completely rip out the GOP, which in turn breaks the vBIOS encryption in place to prevent tampering to an extent this was true even for Polaris cards vBIOS mods broke the UEFI support and you had to do a specific fix for that if you didn’t want to run in legacy mode only. Then there’s other stuff with modern GPUs such as the checksum and the possibility of modern Windows systems possibly not even loading the display driver with such vBIOS changes so… good luck breaking the encryption. Theres a reason things like more power tool exist and its not because people lack the knowledge to modify vBIOS and tailor them precisely to their needs among several reasons it is because manufacturers got tired of RMAing cards users “broke” and didn’t know how to unbrick them or lacked the ability to do so.
Just for the record, my favourite GPUs of all time because of how much you can customise them and the performance you can get out of them when properly optimised are the Polaris cards, those things are still potent 1080p cards and aren’t too bad at 1440p in a lot of titles still.
For the needs of the graphics card firmware research, I modified the last two versions of nvflash, mainly modified 7 jumps so that the program will not go to “Invalid firmware image detected”, because it is an experimental project, it may destroy the function or An unknown situation occurred. Please feedback if there is any situation.
Are you writing to a different model of vbios?
For 30-series, I don’t know what verification has been added at this time, so any modifications to vbios may not pass verification, perhaps using programmer to write to the chip will work.
I can’t offer any more help at the moment.