Hacking My PSP refuses to play ISOs suddenly?

[godstriker8]

I have a PSP GO on 6.20 Pro C2. I've been using it fine for years like this, but today after trying to start a game, it says that it can't.

It says the "data is corrupted" and refuses to play any of my ISOs. Legitimate & unsigned eboots work fine though.

Anyone know how to solve this problem?

 

[jDSX]

Did you make sure to have the ISO file folder on the root of your SD?

 

[VinsCool]

Did you make sure to have the ISO file folder on the root of your SD?

Iso files has to be in a /iso folder.

 

[jonthedit]

Iso files has to be in a /iso folder.

You just repeated what jDSX said, though I can see the confusion "file folder" (translation error, on his part) - he meant the ISO file is in the ISO folder.

OP, I think you somehow changed the driver you are using.
Open the CFW menu and try cycling through the drivers and see if you are able to start games.

 

[VinsCool]

You just repeated what jDSX said, though I can see the confusion "file folder" (translation error, on his part) - he meant the ISO file is in the ISO folder.

Blame my bad english lol.

 

[godstriker8]

Yeah I have the proper folders, like I said in the OP everything has been fine for years. Just all of a sudden all my ISOs that have worked for years refuse to play. They still appear in the menu, they just refuse to boot.

 

[jDSX]

You could of messed something up in the vsh menu

 

[godstriker8]

You just repeated what jDSX said, though I can see the confusion "file folder" (translation error, on his part) - he meant the ISO file is in the ISO folder.

OP, I think you somehow changed the driver you are using.
Open the CFW menu and try cycling through the drivers and see if you are able to start games.

I also tried this before, with no success.

 

[nero99]

Try updating to a different CFW?

 

[rusty_train]

change your iso mode under vsh recovery to something else, inferno if its there or M33, its possible you could have bumped it

 

[godstriker8]

Well after further investigation, disabling the XMB plug ins in the VSH menu worked for some reason, despite me disabling all the individual XMB related plug ins.

Ah well, at least it works.