search

MechaResearch / MechaPwn

GNU General Public License v3.0
373 stars 22 forks source link

[ISSUE]: Patch not applied to SCPH-79001 (but app thinks it was) #186

Closed TheRadGasm closed 8 months ago

TheRadGasm commented 8 months ago

Checks

Console model

SCPH-79001

Describe the issue

PXL_20231009_182830370~2

When going through the MechaPWN process, I am never given the option to choose which console model I have - only which region. I follow the instructions (unplug, run the app again), but after I finish and return to the home menu, my system is unchanged, - I still do not have a DEX console.

If I run MechaPWN again, it only offers me the option to keep the existing patch, change region, or force unlock; but none of these choices actually affect my system when selected.

nvm_6.12_5355435.zip SCPH-79001_specs.txt PS2Ident_Results.zip

PXL_20231009_211927041

AKuHAK commented 8 months ago

Since mechapwn 3.0 there is no indication that mechapwn is applied. You can only check it by launching some burned media. But anyway thanks for the provided data.

TheRadGasm commented 8 months ago

Since mechapwn 3.0 there is no indication that mechapwn is applied. You can only check it by launching some burned media. But anyway thanks for the provided data.

@AKuHAK Thanks for the fast reply - sorry it didn't turn out to be a bug.

Any idea what might actually be going wrong here? I've been pulling my hair out all weekend trying to make this work.

AKuHAK commented 8 months ago

I can only say that mechapwn is applied and is working fine on your console. Just check any burned ps1 game from your console region. And yes, exfat is not supported.

TheRadGasm commented 8 months ago

I can only say that mechapwn is applied and is working fine on your console. Just check any burned ps1 game from your console region. And yes, exfat is not supported.

Thanks for the replies.

I was trying to boot burned copies of SOTN and FF7 and they weren't working, the PS2 browser just showing blue data blocks instead of booting them up;

UNTIL:

I used MechaPWN to restore my original NVRAM; then formatted the (backed up) PS2 memory card; then did a fresh, non-exFAT, install of FreeMCBoot; and then FAT32-formatted a flash-drive and put ONLY MechaPWN on it. So Virgin-everything, vanilla-everything, basically. This time the hack process looked exactly the same as before (backup, unplug, re-run MechaPWN.ELF, retail->DEX, set region to USA multi-7, chose "factory default", unplug, reboot.), only now the burned media is actually working!

Did it again on a 77001 just to be sure, and it worked great there, too.

Weird. Wish I could pinpoint the failure-point for you. I've been wracking my brain, and I have three possibilities:

  1. I was originally using the exFAT install of FMCB instead of the vanilla. FreeMCBoot's installer package comes with two versions now when you unpack it - standard ("vanilla") or exFAT, and I have a MX4SIO on-the-way, so I thought (guessed) that exFAT was the one that I needed. (Maybe it was the wrong choice, and I'm actually unclear on the proper use-case for the FreeMCBoot's exFAT installer?) Either way, when I did the successful "fresh start", I used the vanilla (non-exFAT) FMCB installer instead, so that seems like a factor.

  2. I'm curious if it's possible that some extraneous stuff in mc0:/BOOT/ or perhaps mass:/BOOT/, could have been interfering, like the uLE_kHn files used for Popstarter, for example?

  3. Something in the FMCB, ODSYS, OPNPS2L, or wLaunchELF config files, that was fixed when they were wiped?

Anyway, three possibilities, in my stab-in-the-dark at descending likelihood. Again, total noob here.

Thanks again, @AKuHAK. That's all I've got. Please put the virgin/vanilla "fresh-start" approach that fixed things for me into the tutorial for any fellow noobs who got as stuck/frustrated as I did.

So happy I got things working!