[ISSUE]: Model Number Unknown DTL-H70011S

[Guest117]

Checks

• I provided nvram backup file
• I provided sticker photo

Console model

DTL-70011S

Describe the issue

NVM Backup with latest release and dev build don't match, included both.
NVM.zip

[AKuHAK]

@Guest117 please provide dump from https://github.com/AKuHAK/PS2Ident/releases/tag/latest

[Guest117]

DTL-H70011_1500530.zip

[AKuHAK]

Thank you. Do you agree to include your dump into ps2 bios set ?

[AKuHAK]

Also about mechapwn. I kindly advice you to restore original nvram backup and do not ever try to install mechapwn again. The whole idea of mechapwn is to mimic DTL-H console behaviour on the retail consoles. But your console is already DTL-H so it is mechapwned by Sony. Cant imagine how much you spent for that console, last time I saw that model it was about 300 USD, but nowadays probably it price is doubled.

[Guest117]

I do consent to my BIOS being included in the PS2 BIOS dump.

And that makes sense, in my excitement I forgot to check if there are any other tools like PS2ident to check if my PS2 was in the database.
I never actually intended to install MechaPwn on this console, the disc drive seems to be busted anyways, only reads PS1 games and Audio CDs.

Which NVRAM backup should I restore? I took the one from the 2.00 release first, and that one differs from the Dev build and ps2ident dumps.

[AKuHAK]

Restore that one from 2.0, seems this is vanilla nvram. Hmm, but the nvram backup from later revision clearly shows that mechapwn is installed.
Actually the only thing you can get from mechapwn is changing osd language set, not worth it.
It may not read discs exactly because nbvram is corrupted.
Anyway, you can try to do PMAP if you have knowledge.

[ab310714gz4700]

• Dragon TEST support is blocked!
• Real DEX (non-QA) flags have not been added to the public version of MechaPwn for your safety.

[AKuHAK]

Dragon TEST support is blocked!
Real DEX (non-QA) flags have not been added to the public version of MechaPwn for your safety.

actually this was wrong, balika forgot to block it when released 2.0 version. As evidence - this issue where can be clearly seen that mechapwn altered nvram