NVidia Flashen unmöglich?! Die 2-Klassen-Gesellschaft bei den Turing Chips der GeForce RTX 2070

[Tow]

did you tested it in admin mode?

 

[Vipeax]

@Igor Wallossek
I'll see what I can find. Is there perhaps anything like Discord (text/chat, not voice) that you use? That might make it easier to work on this together.

Someone on Tweakers.net mentined a few weeks ago that MSI messed with the RTX 2080 Ventus, making it impossible to use NVFlash with it.

 

[Vipeax]

https://drive.google.com/open?id=13Cft-k7nn1_t8ufdRibSqgeJvqzwccYz

Try this one.

 

[Igor Wallossek]

did you tested it in admin mode?

Try DOS with Admin mode

Sure, and I'm in my own W10 system more than admin, I'm the trusted installer

 

[BigReval]

Soll ich volltanken und mit dem Progger in die Hauptstadt fahren?

 

[Igor Wallossek]

@Vipeax
Tried the new one, but sorry, I get the same error code

It's possible that MSI is using a protected EEPROM?

 

[Vipeax]

Is the output the exact same as before as well?

 

[Igor Wallossek]

Totally the same

--protecton and --protectoff were succesful and caused no errors

Just trying a Palit Dual

Same problem

If I try to flash an Armor BIOS to the Palit, it works. Both are Non-A chips

With the patched NVFlash64 I can now sopy BIOSEs from different vendors without issues, but not an A-chip BIOS to an Non-A-chip BIOS.

 

[DedSec]

@Vipeax
It's possible that MSI is using a protected EEPROM?

I think so. Take the EEPROM-chip off and solder a new one on the PCB- if it is worth it

 

[Vipeax]

That's truly unfortunate. Sadly I don't have time to dive into this tonight, but it sounds like the error is coming back from the chip.

https://envytools.readthedocs.io/en/latest/nvrm/pmu/ucode-cmds.html

0x5a = NV_UCODE_ERR_CODE_DEVID_MATCH_LIST_DEVID_MATCH_FAILED

 

[Igor Wallossek]

Take your time. no worries. But (for the 2070) it works, as I wrote it in my artcle, only within the same chip classes.
The 2080 Ti FE and the Galax with the 380 watts BIOS are both A-chips

 

[Vipeax]

The 2080 Ti FE and the Galax with the 380 watts BIOS are both A-chips

That one should work with my version yes.

 

[Igor Wallossek]

But I wrote about the cross-flashing with different hardware IDs

 

[Vipeax]

But I wrote about the cross-flashing with different hardware IDs

Yes, I hope this image explains the issue better:

So while Founder Edition cards only have a different Board ID (when compared to AIB models), it seems the A chips also have a different Device ID. :-(

 

[Igor Wallossek]

And that's the reason why I wrote my review
They splitted the owners into 2 classes

 

[hellm]

Erstmal vielen Dank an Igor und alle beteiligten. Ich liebe Community.

Naja, wäre auch zu "einfach" gewesen. Ich wäre für Crowdfunding wegen der Tankladung für BigReval.

 

[Biedermeyer]

ein wenig OT,
sehe erst jetzt die Igor-Sig...

*ggg, desshalb liebe ich Dummchen

 

[Vipeax]

And that's the reason why I wrote my review
They splitted the owners into 2 classes

Yes, sorry I never disagreed with your statement. In fact, this popped up because of the comment by DedSec regarding Founders Edition flashing. I wonder if NVIDIA is doing this out of "greed" or perhaps the whole fake-card issue on Ebay, Amazon etc could be related as well. If people can't cross-flash across different boards combined with the certificate check people can't push out fake cards anymore on the second hand market. An issue that has been going on for a few years now.

 

[Igor Wallossek]

You're right mate

 

[hellm]

You think Nvidia did this "for us".. hmm that would be a nice thing to believe in.. but weren't those fake cards only about the last editable Fermi Chips? 1060 bought, and then you get a old Fermi chip.. on newer cards even kepler or something you can't write 1060 over it, i guess. And i don't think anyone could make a fortune by flashing a non-oc to a oc modell..

But yeah, here we are.