PS2 ISO's Crashing CFW PS3

Good evening.

Recently I purchased a FAT Model PS3 (PH01 I believe) and loaded this console up with CFW. The custom CFW is the latest verson of Evilnat.

Now, full disclosure. I have absolutely no problem in admitting that for most of this, I have no actual clue what I am doing. Especially when it comes to knowing what and what not to do with installing and uninstalling homebrew apps. I just followed some tutuorials on youtube and bingo presto, I got working CFW. Naturally, I wanted to see if the main uses of a CFW were working.

So I got a PS3 backup on the console and it works. The problems arise however, whenever I get a PS2 iso backup to try and run.

What is kind of strange about this, is that on first day, PS2 emulation was working fine save for one caveat. Whenever I would press the PS button on the controller to take me back to the console screen (I think its called the XMB officially?), it would force my PS3 to turn off. I think, okay, no problem I'll just continue to work on it after I get back from work. So I get home and turn it on again and launch the PS2 iso...

Now, from this point onwards, the PS2 iso just crashes the PS3 once the PS2 splashscreen appears. I have tried doing my own research on the matter and have come up short, so I am hoping I can get some help here.

I was using Managunz at first to run this game. The 2 ISO's in question were Shadow Hearts, and Wild Arms Alter Code F. Both ISO's exhibit the same immediate behaviors. I downloaded Rebug Toolbox and Webman to see if any of those could solve the problem. They didn't. Any PS2 ISO crashes the system no matter what launcher is used (I haven't tried Irisman or PS2 Classics Launcher yet).

So I thought, maybe it could be a heat thing. I went into Cobra settings and set those fans to blow at max when a PS2 game was to be ran. Same result, craches immediately after. I uninstalled ALL launchers except for Multiman. After some research I heard that some people have ran into issues with Managunz crashing their system so I removed that app from the equation. It still crashes even when Multiman is the only launcher left to use.

So yeah, I am a bit perplexed on why it was working before and then just stopped working now when PS3 ISOs work just fine? I know technically these PS3 models don't do as well with PS2 emulation as those with the emotion engine but it is strange that they were working at first and then now it just decides not to. The optimist in me believes this is just a simple setting issue, but the realist in me is saying that I bought a PS3 halfway through the paper work of buying the farm.

Anyone got any suggestions? I'll try and answer any you throw to the best of my ability.
 
PS2 ISO and PS2 Classics .BIN.ENC must be stored in /dev_hdd0/PS2ISO
They crash if launched from USB. webMAN MOD makes a copy to HDD before mount the game. But I don't think any other backup manager does that.

You can try also playing a physical PS2 disc (backup or original).

PS2 Classics installed as PKG should work fine if you have a PSN account activated. They are installed to HDD.
 
Last edited:
Hello! Thanks for replying.

I have tried these steps before. The ISOs as well as the BIN.ENC all appear in the PSISO folder. I use FTP to put them directly in there or the Multiman File Manager to take them from the USB to that specified path. The 2 won't show up otherwise.

The PS3 switches off whenever you attempt to run through either method. The PS2 Splash Screen will appear, and then the PS3 will just switch off.
 
I suggest that try a PS2 ISO game that is confirmed working.
For instance, you can install PS2 Classics Launcher and test if the default game that comes with it (just launch it after install).

If the game works, then the issue probably is your ISO (maybe a bad dump) or a compatibility issue. Some games don't work or require a CONFIG file from https://ps3.aldostools.org/ps2config.html

If the default game in the PS2 Classics Launcher doesn't work, it could be an issue with your CFW installation (e.g. corrupted ps2 emulator) or perhaps a hardware issue. You could try reinstalling your CFW.
 

Similar threads

Back
Top