PS3 [Exclusive] PSNpatch v2015.7/A has now been released by KW

PlayStation 3 Homebrew developer KW has informed us that he has released the latest version of PSNpatch released exclusively for PSX-Place user's and a reminder that this is KW's Official Support forum here at PSX-Place.com . PSNpatch has seen some changes with this update such as a new version numbering system, since a several updates ago the developer has made the application/plugin firmware independent [break]ss[/break], meaning a firmware update does not break compatibility as we seen when PSNpatch did not need an update for 4.75 CFW (so to save some confusion the new numbering system was adopted). Also in the update there has been added support for plugin Management for MAMBA plus various other changes and a fix that you can see in the latest changelog provided by the developer:

​

PSNpatch v 2015.7/A
​

What is PSNpatch ?

CORE Features (compatible with ALL 4.XX firmwares):

• Spoofs IDPS (console ID) and PSID;
• Disables cfw syscalls (emulates official firmware);
• Auto-Deletes game and homebrew launch history;
• BLOCKS PSN access at boot until cfw syscalls are disabled (if plug-in is running. read below);
• Installs RAPs and EDATs.
• Unlocks PSN (c00) game demos.
• Unlocks ps2classics launcher.
• It Patches new games to run in lower firmware (4.46) systems - both ISO and folder formats;
• PSNPatch plug-in for easy usage with COBRA and NON-COBRA cfw including PSN access control;
• Firmware version independent;
• Includes a webMAN-mod plug-in version certified to run with PSNPatch.

Latest Update -- VERSION 2015.7/A [01-JULY-2015]

• New version numbering system (year.month/subversion);
• Added support for mamba plugins management - proper identification and plugin management (mamba_plugins.txt);
• Included webman 1.42.01 MOD-KW (lite) for cobra/mamba and non-cobra systems;
• Re-launch of XMB menu add-ons handling into PSNPatch TOOLBOX (for cobra, non-cobra and mamba, not for rebug);
• Fixed a bug in which PSNPatch may crash with with an empty bootplugins.txt file;
• Removed superfluous message about "cobra enhanced / cobra extensions" from main menu.
• Confirmed support for 4.75 CFW - just a confirmation: no changes were made in the source code - psnpatch being full cfw independent
  

PSNPatch 4.70.07 [11-APR-2015]

• New "STEALTH3" extensions for cobra
• non-cobra plugin installer improved for speed and compatibility;
• XMB menus handling for WEBMAN removed (webman-mod automatically updates the XMB GAMES menus).
• Includes Webman-mod 1.41.35-KW lite edition, english language.
• psnpatch.pkg file is now LESS THAN 1MB !!!!
• Official support forum: psx-place.com (http://www.psx-place.com/forum/psnpatch/psnpatch-information-releases-125.html)

Download: PSNPatch 2015.7/A

Source: www.psx-place.com
​

---

Usage Details and Tutorials can be found at the Official Support Forum for PSNpatch (PSX-Place.com)
​

 

Thanks for the update KW !!!!!

 

LUV Ya K-Dub!!!!

 

Thanks mate!

With this update I'm able to use Habib 4.75 CFW properly and I have found out the real cause of my problems!!

What I did was to tick and untick the option Not scanning drives on startup :

I cannot plug any USB drive to right USB port as it gives me a black screen in all the circunstances (Unticking USB drive 06 fixed it or at least solved once)
With the option unticked I had a freeze when XMB waves appear, independently if I use NTFS drives or USB drive.
With the option ticked everything is fine.

All tests were done removing the power source before turning PS3 on.

These tests were done using both Ferrox and Habib CFW's so it is not related with CFW but WEBMAN MOD, hope they fix it!

 

Thanks mate!

With this update I'm able to use Habib 4.75 CFW properly and I have found out the real cause of my problems!!

What I did was to tick and untick the option Not scanning drives on startup :

I cannot plug any USB drive to right USB port as it gives me a black screen in all the circunstances
With the option unticked I had a freeze when XMB waves appear, independently if I use NTFS drives or USB drive.
With the option ticked everything is fine.

All tests were done removing the power source before turning PS3 on.

These tests were done using both Ferrox and Habib CFW's so it is not related with CFW but WEBMAN MOD, hope they fix it!

excellent observation

 

thank you very much KW

 

Hi, I had Hard Corps Uprising (PSN game) installed on my PS3, with a "fix" pkg to unlock it. It was working perfectly including the DLC.

At a later date I installed PSN Patch and at some point I accidentally pressed R1 while PSN Patch was running. After this, the game (and some other PSN games I had) reverted to the demo version. Deleting the game and re-installing and re-applying the fix did not work...

Please help!?

There should be a confirmation dialogue when pressing R1 to prevent this accident!

 

No accident should happen.
Make sure you sign the game with the same idps you pretend to run it.
Make sure you don't have one user with the games sign with one idps and another user with another idps.

Suggestion:
Resign the games for every user using always the same idps

 

Love this app Great work

 

No accident should happen.
Make sure you sign the game with the same idps you pretend to run it.
Make sure you don't have one user with the games sign with one idps and another user with another idps.

Suggestion:
Resign the games for every user using always the same idps

Thanks, I don't really know how to "resign" games but I fixed the problem by re-installing the game without the fix .pkg and then using .rap files instead. (Note: I bought the game a while ago with my original PSN account which eventually got banned for using CFW and I'm not going to pay for it again)

Another question: I used SEN Enabler to do a persistent 4.75 spoof (I don't have to run SEN Enabler again). When I load PSN Patch it correctly shows me that I'm spoofing to 4.75, and I just press triangle to disable syscalls etc. before going online. Is it safe to use your plugin for blocking PSN access at boot time or will it conflict with whatever SEN enabler has done?

Does the "aa" user account need to stay on my system or can I delete it? I'm on Darknet 4.70 Cobra.

 

I used SEN Enabler to do a persistent 4.75 spoof (I don't have to run SEN Enabler again). When I load PSN Patch it correctly shows me that I'm spoofing to 4.75, and I just press triangle to disable syscalls etc. before going online. Is it safe to use your plugin for blocking PSN access at boot time or will it conflict with whatever SEN enabler has done?

Version spoofing is permanent. You can (and you should) use psnpatch plugin.
Nevertheless, you should think in updating to a 4.75 firmware and forget about version spoofing.

Does the "aa" user account need to stay on my system or can I delete it? I'm on Darknet 4.70 Cobra.

Providing you have a valid psn user account, you don't need the 'aa' account with psnpatch.
If you have doubts in how to create a psn valid user account, please take a look into psnpatch docs and faqs - it is all there !

 

Thanks, waiting for 4.75 Cobra but I don't like having to update the firmware too often..

 

So is staying on newest firmware CFW considered less ban-risky than using spoofer? Or was that only when they changed the servers where they were firmware dependent - connecting with old firmware connected to old servers which resulted in ban??

 

So is staying on newest firmware CFW considered less ban-risky than using spoofer? Or was that only when they changed the servers where they were firmware dependent - connecting with old firmware connected to old servers which resulted in ban??

I personally have connected to PSN more so with Spoofer then latest firmwares. IMO of over 3 years. Spoofer are just as safe. There is no added risk. NOW I HAVE SEEN SOME SPOOFERs not put together properly and cause issues... Using Sen Enabler for example to spoof i have had no issues..

In v4.70 (i think that was the version) Sony ditched SSLv3 (because of security issues (this was a good thing)) thus spoofer do not work on those firmwares without some extra editing of files, but those lower firmwares can be spoofed just more involved there is articles here on it.

Thanks, waiting for 4.75 Cobra but I don't like having to update the firmware too often..

TBH 4.70 REBUG spoofed with SEN Enabler will be EXACTLY the same as Rebug 4.75 (Unless there is some extra rebug features that they add) but if its just an update of existing features there is really no difference. Actually at this point 4.70 is better as more apps/tools support it. Sony did not add a single feature in 4.75. Too often user's think they must be on the latest firmware and that simply is not the case now days. in the past it was like 3.55 era. in the 4.xx era no as the system is more open thanks to developer's. Also the keys have not been changed as there is no point for Sony to change them as we can always find them now.

 

I totally agree with STL im stick rocking 4.46 with spoof and have been ising same cid for 3 years on retail disk/psn games

 

I personally have connected to PSN more so with Spoofer then latest firmwares. IMO of over 3 years. Spoofer are just as safe. There is no added risk. NOW I HAVE SEEN SOME SPOOFERs not put together properly and cause issues... Using Sen Enabler for example to spoof i have had no issues..

In v4.70 (i think that was the version) Sony ditched SSLv3 (because of security issues (this was a good thing)) thus spoofer do not work on those firmwares without some extra editing of files, but those lower firmwares can be spoofed just more involved there is articles here on it.


Too often user's think they must be on the latest firmware and that simply is not the case now days.

Yeah, that's my feeling but PSNPatch developer removed spoofing when 4.70 came out because he seemed to think it wasn't as safe as it used to be? Why is kokotonix advising to avoid spoofing?

I've been online many times with SEN Enabler 4.75 spoofing without a problem....

 

Yeah, that's my feeling but PSNPatch developer removed spoofing when 4.70 came out because he seemed to think it wasn't as safe as it used to be? Why is kokotonix advising to avoid spoofing?

I've been online many times with SEN Enabler 4.75 spoofing without a problem....

PSNPatch removed spoofing because the way it did it was blocked by Sony, he might be advising against spoofing done the improper way, a lot of research and development goes into the SEN ENABLER spoofs as to why it's probably the safest out there

 

I just want to know why the rebug team doesn't update their spoofer like they used to. Eg. So when you changed to rebug mode it spoofed to the higher version.
If everything is the same and working safely.

 

I just want to know why the rebug team doesn't update their spoofer like they used to. Eg. So when you changed to rebug mode it spoofed to the higher version.
If everything is the same and working safely.

the spoofing process is a little more complicated then it used to be, especially with Cobra, Sony patching the old method, new certs (vsh cert calls) it takes time. Time they could be using to develop a new CFW

 

Some words

Hi guys:

Some words about the last posts that I would like to share with you all:


1) VERSION SPOOFING

Version spoofing is more complicated that what it seems at a first glance.

Usually, to spoof the firmware version, we need to replace version specific files and a patched vsh.self of the original firmware version to the new version – previously and manually patched in a PC.
This makes psnpatch to handle all these files from every original firmware version and (at least) the patched (spoofed) files.

An alternative approach would be to connect to PlayStation update site, detect the current version and dynamically unsign vsh.self, patch-it accordingly, and sign it back. This would support spoofing every older firmware versions to any current version (even if not advisable for original firmwares older than 4.70 - keep reading).

(Unfortunately KW doesn't have the time to investigate and code this in the next couple of months )


Apart of all the "fizzle" around these approaches, when 4.70 was released a new set of protocols and certificates were issued. Meaning that when connecting to psn with a firmware lower than 4.70, even spoofed, is easily detected.

We all know that connecting to the psn with cfw is always a risk. But it must be a calculated risk. We need to be conservative and mitigate risks the most we can.



2) FIRMWARE INDEPENDENT

Currently, psnpatch is fully firmware independent. No hard coding is used for any particular version, everything is dynamically made in order to support any firmware version in run time.
This also includes the "Plug in manager" for non-cobra (and non-mamba) systems). This plug-in manager is not more than a prx-loader patched at install-time to support every currently running firmware version – more details are in the source code included in the official psnpatch distribution.
An approach is planned to do the same with mamba in order to automatically patch-it at install time to work with every firmware version (and webman will also automatically support new firmware version, providing it would run over mamba).
Again, and unfortunately, there's no time to do-it in the next couple of months.


I'm insisting in this "thing" of psnpatch being firmware independent.
Why ?

Having the "firmware independent" approach, guarantees that once a new firmware is released psnpatch will immediately support it once a new firmware is released.
(And don't know if you noticed, but webman is almost firmware version independent providing we use cobra or mamba …)

And even if Rogero and Habib have retired from the scene, there will still be fantastic developers working in new CFW, as Joonie or Alexander (just to name a few).