So there really is no way to brick the video card because nvflash can always re-write the entire VBIOS? If that's the case, why can't I edit the Device ID, Vendor ID, Subsystem ID, or even the VBIOS version? Those have to be in the VBIOS unless there is other non-volatile storage on the cards (which seems unlikely simply due to cost and complexity). There would be no need for a hardware programmer unless some portion of the VBIOS is used for this information and accessible to nvflash. I don't get it. Are there secret commands for nvflash not listed in the built-in help? What commands did you use to "get things back in working order"?
I'm doing this on an old HP EliteDesk 800 G1 USDT running Windows with integrated graphics (Intel i7-4790S) and an MXM slot for the DELL-branded Quadro M2200. I'm trying to figure out the difference, if any, between the DELL-branded Quadro M2200 and HP-branded before possibly purchasing a new card (DELL are much less expensive and more readily available). My card is likely suffering a hardware failure that won't be worth repairing.
I've really had no trouble with nvflash so far and have managed to make the card useless a few times along the way. Why Linux?