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

kokotonix updated PSNpatch with a new update entry:

PSNPATCH 2017.02

2017.02/B
  • NEW HOMEBREW BLOCKER for PSNPatch plugin (read full usage details in docs);
  • Homebrew Blocker configurable trough PSNPatch main app TOOLBOX;
  • Instructions heavily updated to incorporate homebrew blocker - read them before placing questions !
  • Source code from the homebrew blocker module included with PSNPatch official distribution.
  • Source code for the PSN Servers lock module included in PSNPatch official distribution.
...
Click to expand...

Read the rest of this update entry...
 
As you can see from the previous post, psnpatch was updated to 2017.02/B.

A new homebrew blocker is included in the psnpatch plugin - in the plugin only.
It is enabled by default.
If you don't want to use it, go into psnpatch xmb application, toolbox menu, and disable it there.
The homebrew blocker blocks home brew excution when CFW Syscalls are disabled.
Execution will be locked until the next reboot.
The homebrew blocker runs in cobra, near-cobra (mamba) and non-cobra systems.
This implementation is compatible with eventually future cobra updates for core homebrew blockers.

The approach used is detailed in the homebrew_blocker module source code included in this pasnpatch distribution

It was heavily tested, namely simulating crashes, forced reboots, recovery menu accesses, file system recovery and database rebuilds. Up to know is failsafe proof, but as usual there is no warranty ;)

Please note that without @aldostools proposing and optimized detectiom algorithm, it would take a lot of time to release this.
(thank you aldo).


As usual, every detail is in the firs post of this thread.
And full DOCUMENTATION and FAQ is included in the distribution file

PLEASE READ THE RELEASE NOTES AND FAQS, NAMELY THE HOMEBREW BLOCKER PART TO FULLY UNDERSTAND HOW IT WORKS AND WHAT TO DO IF YOU HAVE ANY FUNCTIONALITY ISSUES.

Win some time for yourself and everybody: read first ask next

Or as I prefer to say: R T F M !!!
 
@Kokotonix @Aldostools


First off, some informations about my System/Setup:

PS3: CECH-2504 with installed E3-Flasher (incl. Dual-Boot)

Custom Firmware: REBUG_CFW-4.81.2-REX_COBRA-7.5

*Debug Settings: System Update Debug: "On"
Rebug-Toolbox: Target Type: "CEX (0x85)" & LV2 Kernel: "CEX"
Rebug-Toolbox: Toggle QA Flag: "enabled"
Rebug-Toolbox: System Mode: "REBUG"
Rebug-Toolbox: XMB Operation Mode: "Debug"
Rebug-Toolbox: Toggle XMB CFW settings: "enabled"
Rebug-Toolbox: Toggle COBRA Mode: "enabled"
Rebug-Toolbox: Toggle webMAN: "enabled"

REBUG_TOOLBOX_02.02.12.MULTI.15
webMAN_MOD_1.45.11 (Full)
PSN-Patch_V-2017.02-B
multiMAN_04.81.02

----------------------------------

My additional Setup:

First Local User "e.g.: User-1":
- with first PSN-Account "e.g.: [email protected]"
- for my standard valid IDPS & PSID (NOR-FLASH)
- activated RIF's only for the "standard valid ID's" under "User-1"

Second Local User "e.g.: User-2":
- with second PSN-Account "e.g.: [email protected]"
- for my spoofed valid IDPS & PSID (other valid ID's in the "psnpatch.cfg")
- activated RIF's only for the "spoofed valid ID's" under "User-2"

----------------------------------

PSN-Patch-Plugin interferes with "My additional Setup":
With this setup, I have problems with the usage of your plugin.
Because when I use the shortcut "L3+R3+R2" to disable CFW-SYSCALLS, unlock PSN-Access, block Homebrews etc.,
or if the plugin is enabled and I push the "triangle-button", it also spoofs my IPDS & PSID.
--> "triangle-button" is therefore the same as "x-button".

You have explaind it to me here (Post-Nr.: #38):
http://www.psx-place.com/threads/ps...ew-improvements-from-kw.12211/page-2#comments

But with this, I cannot solve the problem, regarding to "My additional Setup":
###- activated RIF's only for the "standard valid ID's" under "User-1"###
Because I am also interested in the new function: "HOMEBREW BLOCKER".
Otherwise, the activation for "User-1" must be done each time, with enabled plugin and also with disabled plugin.

----------------------------------

What do you thing about a possibility to separate this in the PSN-Patch-Toolbox?
E.g.: There could be under "install/remove PSNPatch plugin" an additinal function,
which is called: "Plugin without spoofing the IDPS & PSID".
Another suggestion could be to use two plugins, one with "IDPS & PSID - Spoofing" and the other one without it.

Like this:

--- install/remove PSNPatch plugin with included IDPS & PSID - SPOOFING --- (standard)
--- install/remove PSNPatch plugin without IDPS & PSID - SPOOFING --- (additional)

I think, it is not a big deal for "KW" and it could be done without great efforts.


Greetz
 
kokotonix said:
I suggest to spoof idps at boot and then install every license if every game you need.
Click to expand...


Yes of course, I understand. This is perfect for the standard user.

But for users, who want to separate between two licenses for two valid CID's under two different local users, this makes problems.

Is it really not possible to think about my suggestion?


Greetz
 
WTF-IGO said:
Yes of course, I understand. This is perfect for the standard user.

But for users, who want to separate between two licenses for two valid CID's under two different local users, this makes problems.

Is it really not possible to think about my suggestion?


Greetz
Click to expand...

A objective of psnpatch plugin is to be the simplest as possible.
1 shortcut to all.
1 shortcut to display status.


The usage you want can be done with psnpatch application.
Psnpatch documentation explain how to do what you want.


But note that there is no objective advantage in doing what you want. Just put every license in the same user profile is the only needed approach.
 
kokotonix said:
A objective of psnpatch plugin is to be the simplest as possible.
1 shortcut to all.
1 shortcut to display status.


The usage you want can be done with psnpatch application.
Psnpatch documentation explain how to do what you want.


But note that there is no objective advantage in doing what you want. Just put every license in the same user profile is the only needed approach.
Click to expand...

Ok, then I have to respect this. But my issue remains with this solution.
Therefore I must to forego the plugin (and also, HOMEBREW BLOCKER). It is a pity.


Declaration, why:

When I activate RAP's for both local users under the first IDPS and after that I activate RAP's for both local users under the second IDPS,
the first activision becomes overwritten and doesn't work anymore.
Therefore I have to do this each time. That means a disadvantage for me.
 
WTF-IGO said:
Ok, then I have to respect this. But my issue remains with this solution.
Therefore I must to forego the plugin (and also, HOMEBREW BLOCKER). It is a pity.


Declaration, why:

When I activate RAP's for both local users under the first IDPS and after that I activate RAP's for both local users under the second IDPS,
the first activision becomes overwritten and doesn't work anymore.
Therefore I have to do this each time. That means a disadvantage for me.
Click to expand...
True, but your setup is very uncommon. In MY opinion there is no reason to use two IDPS when you are connecting both of them to PSN. I know that you probably have different content on both psn accounts, but you can just make 1 IDPS and 2 PSN accounts setup.
 
WTF-IGO said:
Ok, then I have to respect this. But my issue remains with this solution.
Therefore I must to forego the plugin (and also, HOMEBREW BLOCKER). It is a pity.


Declaration, why:

When I activate RAP's for both local users under the first IDPS and after that I activate RAP's for both local users under the second IDPS,
the first activision becomes overwritten and doesn't work anymore.
Therefore I have to do this each time. That means a disadvantage for me.
Click to expand...

What ? No !
You install raps for one user and one idps.
Then you change idps and install raps for another user (use left/right keys to select user).

This is detailed in docs.

But again ... you don't need to do that. You can have everything in just one user and one idps.
I don't understand why you want to have licenses installed for different idps.
 
@kokotonix

I have read your "docs" very carefully since the begining over and over again.
They are perfect and very nice to understand. Thx for this.


@kozarovv

Yes: "Different content on both PSN-Axx's".

I am using my first IDPS (User-1 with first PSN-Axx) only for "offline" playing.
With this I want "additionally" to minimize a ban, because this PSN-Axx is very important for me.
And i want to manage my "offline" savegames and trophies under this user.

And the second spoofed IDPS (User-2 with second PSN-Axx) I am using to play PSN-Games online.
In the second case it would be not really tragic, when this spoofed IDPS and the second PSN-Axx get banned.

--------------------------------------

Regarding to my posts, it can only be done, by using an additional alternative PSN-Patch-Plugin, which doesn't spoofing IDPS & PSID.
 
Last edited:
Pitchounet said:
Hi kokotonix.

Really happy of this update of my favorite hide secure tool.

In your faq you say:



I don't use them and try to be careful of this, but with children on the ps3 too, do you think it could be interesting and possible to have an option or plugin to check homebrews ps3 installations (we nearly know all them) and blocking their start or them when triangle option is used?

Regards.
Click to expand...
kokotonix said:
That was tried like 2 years ago :)
First by the usage of a psnpatch payload to intercept the fileopen and the execute syscalls which would look into a blacklist.txt file (containing the apps to block).
The changing cobra code itself to directly support this codes.

But these approaches meant changes to the syscall table which would be reverted when psnpatch disables syscalls or, if kept, would be against psnpatch policy of restoring the syscall table as in OFW.

For all this, and some instability in the code, KW gave up on it.
Click to expand...

kokotonix said:
As you can see from the previous post, psnpatch was updated to 2017.02/B.

A new homebrew blocker is included in the psnpatch plugin - in the plugin only.
It is enabled by default.
If you don't want to use it, go into psnpatch xmb application, toolbox menu, and disable it there.
The homebrew blocker blocks home brew excution when CFW Syscalls are disabled.
Execution will be locked until the next reboot.
The homebrew blocker runs in cobra, near-cobra (mamba) and non-cobra systems.
This implementation is compatible with eventually future cobra updates for core homebrew blockers.

The approach used is detailed in the homebrew_blocker module source code included in this pasnpatch distribution

It was heavily tested, namely simulating crashes, forced reboots, recovery menu accesses, file system recovery and database rebuilds. Up to know is failsafe proof, but as usual there is no warranty ;)

Please note that without @aldostools proposing and optimized detectiom algorithm, it would take a lot of time to release this.
(thank you aldo).


As usual, every detail is in the firs post of this thread.
And full DOCUMENTATION and FAQ is included in the distribution file

PLEASE READ THE RELEASE NOTES AND FAQS, NAMELY THE HOMEBREW BLOCKER PART TO FULLY UNDERSTAND HOW IT WORKS AND WHAT TO DO IF YOU HAVE ANY FUNCTIONALITY ISSUES.

Win some time for yourself and everybody: read first ask next

Or as I prefer to say: R T F M !!!
Click to expand...

Happy to see that you solved the answer to my question about this option. Really great news and update, and many thanks for all this to you and aldo!
 
I saw a user post something that I personally think might be a good feature for PSN Patch. The feature I speak of is to do with IDPS and PSID showing in the notification. There could be an option in the toolbox to hide IDPS+PSID from showing using asterisks (CID=********** - PSID=**********) instead of showing the actual CID+PSID (CID=1234567890 - PSID=1234567890).

My brother actually asked me about this a few months ago but I wasn't using PSN Patch then as I never went online with CFW so I couldn't answer his question. It was just an idea anyway. :)
 
Casavult said:
I saw a user post something that I personally think might be a good feature for PSN Patch. The feature I speak of is to do with IDPS and PSID showing in the notification. There could be an option in the toolbox to hide IDPS+PSID from showing using asterisks (CID=********** - PSID=**********) instead of showing the actual CID+PSID (CID=1234567890 - PSID=1234567890).

My brother actually asked me about this a few months ago but I wasn't using PSN Patch then as I never went online with CFW so I couldn't answer his question. It was just an idea anyway. :)
Click to expand...
Not sure it is useful at all, there are various ways to display the ids anyway. If you want to hide the ids because you are afraid someone might steal those, your must remember that anybody with either a network connection to your lan or access to the console can get the spoofed ids in less than a minute!
Also the ids don't get displayed long enough for someone to remember them unless that person has an amazing "photographic" memory!
As to making videos, that cannot be a reason for a new feature....
 
Last edited:
Casavult said:
I saw a user post something that I personally think might be a good feature for PSN Patch. The feature I speak of is to do with IDPS and PSID showing in the notification. There could be an option in the toolbox to hide IDPS+PSID from showing using asterisks (CID=********** - PSID=**********) instead of showing the actual CID+PSID (CID=1234567890 - PSID=1234567890).

My brother actually asked me about this a few months ago but I wasn't using PSN Patch then as I never went online with CFW so I couldn't answer his question. It was just an idea anyway. :)
Click to expand...

The ids should be displayed to make sure we are using the right ones.

You surely agree that adding one more option to psnpatch to mask idps display just to help making videos, is something to much specific, and out of the ordinary usage.

I am sorry but I cannot find a cabal justification to ask KW to make that.
 
You must log in or register to reply here.

Similar threads

Back
Top