I don't normally end up in a situation where I appear to have exhausted all options, but here I am.
I've got a GTX Titan Z that's running some pre-production firmware and won't cooperate with any drivers, modified or not. I would like to get the card running with production firmware via flashing both ASICs vBIOS with the retail versions. This is where I hit a snag, board ID Mismatch. nvflash does not appear to allow force flashing like ATIWinFlash does, so this simple error stops the whole process in its tracks.
Quick breakdown of different commands tried just from google searching previous threads:
nvflash -i# -4 -5 -6 romname.rom (replace pound with number of device to be flashed)
nvflash -i# -f -6 romname.rom
nvflash -index=# -f -6 romname.rom
nvflash -index=# -4 -5 -6 romname.rom
I understand that those are basically the same commands spelled differently, but I was just covering all bases. I did disable write protect on all available devices as well to clear that up.
My question really is, can I get around this roadblock and force the firmware in any way? While the board ID is a mismatch the device ID is the same and should work perfectly fine in the event that the retail firmware is applied.
Any help is appreciated, and I'm hoping it's a simple issue I've overlooked.
I've got a GTX Titan Z that's running some pre-production firmware and won't cooperate with any drivers, modified or not. I would like to get the card running with production firmware via flashing both ASICs vBIOS with the retail versions. This is where I hit a snag, board ID Mismatch. nvflash does not appear to allow force flashing like ATIWinFlash does, so this simple error stops the whole process in its tracks.
Quick breakdown of different commands tried just from google searching previous threads:
nvflash -i# -4 -5 -6 romname.rom (replace pound with number of device to be flashed)
nvflash -i# -f -6 romname.rom
nvflash -index=# -f -6 romname.rom
nvflash -index=# -4 -5 -6 romname.rom
I understand that those are basically the same commands spelled differently, but I was just covering all bases. I did disable write protect on all available devices as well to clear that up.
My question really is, can I get around this roadblock and force the firmware in any way? While the board ID is a mismatch the device ID is the same and should work perfectly fine in the event that the retail firmware is applied.
Any help is appreciated, and I'm hoping it's a simple issue I've overlooked.