PS3 PSNpatch - Releases / Usage Information (Official Support Thread)

Yeah, I found that out the hard way when I was testing sman with deank trying to work out the network issues. :) (which he solved like a boss I might add. haha)

that's what makes this community great. we all discover new things regarding the ps3, ps vita, etc. and help one another out especially when something goes wrong. :)
 
Oh, one small side effect of removing the boot_plugins.txt via the recovery trick, due to the homebrew blocker in psnpatch (I'm currently using habibs cfw with deanks modified cobra 7.50, so no inbuilt homebrew blocker) if you have disabled psnpatch before shutting down to go into recovery (thus enabling the blocker) you won't be able to start any homebrew on restarting until the plugin is reloaded again. (80010006 error from memory).

Either re-installing the particular homebrew app you are trying to run over the top of itself (multiman, rebug toolbox etc. if you are using that to copy a boot_plugins.txt backup back into place) will get that particular app running again. Or reinstalling the psnpatch package and re-enabling the plugin that way will allow all homebrew to launch again after restarting.

Shouldn't be a problem in this situation since psnpatch is obviously still enabled. (Assuming frogman is running a debug mode cobra and it's not a different problem altogether).

But helpful information to know anyway. :)
 
Last edited:
i ended up just putting in a new drive. after taking out the old one to test a different one, it wouldn't read the old one without formatting. oh well!
 
i ended up just putting in a new drive. after taking out the old one to test a different one, it wouldn't read the old one without formatting. oh well!

Ahh yeah, it saves the drive information in flash.
Excerpt from my dump check showing the hdd it is expecting.
Code:
******* Additional information *******
HDD : HGST HTS721010A9E630 JR10046P13AR6N

If you didn't format the old drive, you should still be able to manually copy the data off it using a pc in combination with a copy of your eid_root_key. (rebug toolbox can dump that for you) :)

@aldostools ps3 toolkit has a built in reader that should handle the job.

Edit: Just make sure to say no if the computer asks about initialising the drive to MBR or GPT or something along those lines. Otherwise you will lose all your data due to the way the PS3 stores its encrypted information on the drive.
 
Last edited:
Psnpatch does not support Dex !

True, It was never mentioned if the console was dex or cex rebug. Either way it should still boot? (Did for me on dex anyway)

I was just mentioning that using the debug output enabled cobra (cex) will lock up the system upon loading psnpatch, as that's the only time I've ever had my system lock up on boot. (similar to what frogboy seemed to be experiencing.)

ie. using the cex stage 2 files on rebug from...
https://github.com/Joonie86/COBRA-7.3/tree/master/481/REX/BIN/debug + psnpatch = freeze on plugin load.
https://github.com/Joonie86/COBRA-7.3/tree/master/481/REX/BIN/release + psnpatch = fine.
 
Psnpatch does not support Dex !
Could you tell us what exactly Psnpatch does not support?
For example, is it unsafe to go online with DEX even if it beeps when X is pressed?
Or is it safe as long as a beep is heard?

Sorry for the confusion but I've looked through this thread and haven't found the answer.
 
Could you tell us what exactly Psnpatch does not support?
For example, is it unsafe to go online with DEX even if it beeps when X is pressed?
Or is it safe as long as a beep is heard?

For sure psnpatch in DEX console is not support locking psn at boot. Don't know that anything more. But assuming that you are "pressing X" you are not using plugin, so psn lock is not work anyway.
 
It's not recommended to rely on psnpatch in DEX mode as it's officially not supported.
If you want to know whether syscalls are disabled after you hear the beep, just try launching a backup manager & mounting a game for instance.
If you want to know whether history got deleted just check your file system.
If you want to know whether spoofing the console ids worked, launch the psnpatch app & check the current ids.
 
Well, it does work, it goes online, but when I try to connect to psn it says I have to update firmware ( I now use rebug 4.81). How can I override that update?
 
Well, it does work, it goes online, but when I try to connect to psn it says I have to update firmware ( I now use rebug 4.81). How can I override that update?

Your issue is related to your firmware version. Not with psnpatch.
Psnpatch is working exactly as planned.

As @bguerville already said: You have to wait for a new 4.82 CFW to be able to connect your PS3 to the PSN.
 
.rap seemed to be installed successfully, but the game did not get unlocked. Is there another step for "always online" games?

I'm running Ferrox Cobra 4.82 on a PS3 Slim.
 
Same thing hapened to me as @frogboy. Now I'm looking for solutions. I'm trying now rebuild database from recovery. I hope I will not have to change hdd

Can I somehow unload that toolbox from booting up??
 
Last edited:
.rap seemed to be installed successfully, but the game did not get unlocked. Is there another step for "always online" games?

I'm running Ferrox Cobra 4.82 on a PS3 Slim.

that should be it unless there are other checks with an always online game. you can check if it's unlocked by highlighting the game, pressing triangle, and going to information. look in the buyer's field.

edit: I forgot about this, but I think there are checks on the server end to determine if you've bought the game and on which ps3 system it was bought, so it may not work.
 
Same thing hapened to me as @frogboy. Now I'm looking for solutions. I'm trying now rebuild database from recovery. I hope I will not have to change hdd

Can I somehow unload that toolbox from booting up??
I think I screwed mine up also. I installed the new 4.82CFW and the newest PSNPatch. But after I ran the install utility from the XMB and rebooted it just freezes. I wants to do a disk check but then locks up. Any solutions yet or is reformatting the drive the only thing I can do?

Update: I had to reinstall the CFW and its fine now.
 
Last edited:

Similar threads

Back
Top