[ISSUE]: SCPH-77004 not reading NTSC-J PS2-only games

[Bassa-Bassa]

Checks

• I provided nvram backup file
• I provided sticker photo

Console model

SCPH-77004

Describe the issue

nvm_6.10_2619675.zip

Mechpwn version used: MechaPwn 3.0 RC4 (408eab8)

FMCB used: FMCB installer v0987 (FMCB v1966) with Cross-region

Issue: After Mechapwn installation, I can't get other regions (NTSC-J) PS2 original games to boot, whereas original NTSC-J PS1 and PAL PS1 do (the latter, with PAL-to-NTSC video issues, apparently expected), and NTSC-J PS1 burns do as well, both from OSD. Tried it with and without a memory card with FMCB. I don't have PAL PS2 discs so I can't test them.

Moreover, my Mechapwn installation process was apparently different from what you usually find described or tubed out there - after the NVM dump and rebooting the console, I get the information screen and then I'm asked if I want to Change region or Restore NVRAM backup. Right after choosing Change region: Select console type (Retail-DEX / CEX (retail) in this order). Right after choosing Reatil-DEX: Select region (OSD/DVD). Here I've tried with both, Europe (Multi-7) first, and later in a second install, Japan. Right after that, Patch menu, from which I picked Keep current patch in both instances.

As I've never been asked to pick a console model or current region in the process as every other tutorial explains, and never was asked which DEX region did I want either, I'm wondering if the process like described is correct and if I could safely try it with other units and the same files. I'm pretty sure this unit is not soft-modded, BTW - while I never tried to load a burn on it, case seals and key combinations when booting point to no chip there in.

PS2's version information screen shows SCPH-77004 instead of any DTL.

The attached NVM file corresponds to the first one created with the first installation, though I saved it right after the first install entirely finished (the USB was connected for the whole process) - I'm not totally sure if, when you reboot the system and re-launch Mechapwn, it overwrights it. So I'm a bit afraid of restoring this NVM, especially when it doesn't seem to be a way to access the restoring option before a NVM is created anew (I guess because Mechapwn's not acknowledging the system's modded already?

[AKuHAK]

Doh, I hate all of that f..king tutorials that spread misinformation about mechapwn.
What is your problem, it is not directly related to mechapwn, but rather to the 77k model itself. For some reason, this slim model line has the worst laser ever. So basically, you cannot boot PS2 title not because an app or you did something wrong, but because the laser on 77k thinks that PS2 media quality is too low to be played. I still didnt found good solution for that so i keep this issue open.
Currently there is a workaround that you choose force unlock in patch menu. You will loose ps1 support, but for ps1 you can use DKWDRV app to launch it. At least PS2 titles will start to work normally.

[Bassa-Bassa]

Thanks for the quick reply, AKuHAK. So to confirm - I understand that the process as described is correct and not getting the line "Console: DTL-H77004" in the Version Information screen like in this pic:

https://i.imgur.com/ywGejv5.jpeg

...(and still getting "Console: SCPH-77004" instead) doesn't mean anything at this point?

Mechapwn, therefore, isn't asking you to pick your current console model and region and to choose a DEX/DTL region in the process anymore (but did in the past)?

Regarding console model, then, what's your all-round recommendation currently for PAL countries? Do 7500X units have the same laser as 7700X or are they better for PS2 discs? I have a 70004, but read that burns/bad-state discs may seriously harm the laser so I bought a couple of 7700X for this, lol.

I don't have any to test it myself and I guess this might be a silly question, but will PS2 DVD burns be the same as originals regarding this issue?

As for the Patch menu, have you explained anywhere what it is, please? Is the Restore factory defaults option the one to pick only when you want to uninstall force unlock? So, for a normal installation the user always picks Keep current patch, and in a case like mine (if the user wants every disc to be read as a PS2 DVD for whatever reason), Install force unlock should be picked, or there's more to it?

Whether you find out a solution for this or not, let me thank you for your amazing work anyway. Thanks to you, PS1 NTSC games can easily be played at their intended refresh on PAL consoles, which was never possible before.

[Bassa-Bassa]

Partially answering myself - Tried with a SCPH-75004 with the same files and process (DEX option, non-force unlock) and it does load original NTSC-J PS2 DVDs. The Version Information screen also keeps the original console model name, though.

All this stuff should go in a FAQ.

[AKuHAK]

Partially answering myself - Tried with a SCPH-75004 with the same files and process (DEX option, non-force unlock) and it does load original NTSC-J PS2 DVDs. The Version Information screen also keeps the original console model name, though.

All this stuff should go in a FAQ.

This is speculative information, we dont know the real reasons on why this is happening and why some people with 77k are affected for DVD, some are affected for CD only and some are nota affected at all.
Could you please confirm that on 77k Force Unlock doesnt resolve the problem for you?

[Bassa-Bassa]

Note that that second mod was made on a 75004; do you mean that 75k's are also affected by this issue?

So I tried force unlock on the 77004 unit and nope, it didn't read NTSC-J PS2 DVDs. Neither did PS1 discs, so the force unlock itself seemed to be succesful. I reverted the force unlock (with the Restore factory defaults option) to make it read PS1 discs again, which was my main purpose, anyway.

I noticed every time you run Mechapwn (unless it's mid-install process, when it asks you to unplug the console for the first time), a NVM dump is made without the option of skipping (Backing up NVRAM...). That is, it's an automated process that happens even if the console is already modded with Mechapwn, so the dump in these cases is from a patched NVM, which, I guess, overwrites the original good dump if it's on the USB drive's root? Isn't that a bit too dangerous?