PS4 News on Facebook! PS4 News on Twitter! PS4 News on YouTube! PS4 News RSS Feed!

Home PS4 News - Latest PlayStation 4 and PS3 News

February 6, 2014 // 7:53 pm - Following up on his previous release, PlayStation 3 homebrew developer KW (via kokotonix) has updated to PSN Patch v2.22 for PS3 Custom Firmware, which allows users to temporarily disable their CFW, spoof their Console ID and more as detailed below.

Download: psnpatch / psnpatch_2.22_[STEALTH].pkg.576.v2.22.pkg

To quote: [2.22] Feb/06/2014 - PSNPatch 2.22 Changelog:

  • Corrects small bug importing cert when spoofing version. If you spoofed 4.46 cobra version with psnpatch 2.21, please use psnpatch 2.22 to remove spoof and activate again.
  • Spoofs cobra 4.46 firmware to version 4.55 (*);
  • Imports new certs from files/cert/ when spoofing version.
  • "cobra_version.txt" is now on files/ (older cobra_version.txt will be deleted at startup);
  • Integrity check is made when entering cobra menu;
  • Includes webMAN 1.29;

(*) If you already spoofing firmware version, first disable it then enable to the new version. Currently only Cobra 4.46 supports version spoofing (using cobra method). If you're using a cobra 4.53 system, make sure it supports version spoofing BEFORE using-it!


PSNPatch Noob FAQ

Q: What can I do with psnpatch ?
A: Psnpatch allows a safer (less "banneable" ) connection to PSN when using a CFW (custom firmware).
To do so, it "masks" cfw (simulates an official firmware version) and deletes all traces of homebrew (unlicensed ps3 software) been used in your console. If this is what you want to do, just run psidpatch pressing TRIANGLE until you ear 3 beeps - or wait for the user interface to appear and follow the on-screen instructions.

Note: If you want to play online, you should mount any game backup you may need BEFORE using psnpatch. After using psnpatch, it will NOT be possible to change the mounted backup UNTIL next reboot. You can also use psnpatch to do a temporary change of your console's ID (IDPS and PSID) and install RAPs, EDATs and unlock psn game demos.

Q: How can I confirm that CFW is properly masked ?
A: PSNPATCH does the test for you. After masking CFW it makes the proper testing and beeps if they were successfully.
You can do other tests until you trust psnpatch : just call multiman or iris manager - if the cfw is properly masked / disabled, you will get an error with both applications.

Q:But my console is banned ! what can I do ?
A: If you have the ConsoleID (IDPS) and the PSID from another unbanned console, you can "spoof" that console unbanning you current one.

1. Edit psnpatch.cfg file (see example that goes with psnpatch distribution) and apply the proper values.
2. Place psnpatch.cfg at the root of a usb stick.
3. Place the stick in the rightmost port of your ps3.

Q: How can I obtain an unbanned IDPS and PSID ?
A: Usually by having another (tipically dead / ylod) console and accessing its flash memory in order to get the IDPS and PSID.

Q: I don't like pressing so many keys. I will like to do a "all in one" idps & psid spoofing, cfw disabling/masking and execution history deletion. Can it be done ?
A: Yes ! Run psnpatch and keep CROSS pressed. Wait for the beeps and getting back to the xmb.

Q: I have here some RAP files and also some EDAT files. What are these ?
A: They are license files to allow you to execute certain PSN games or DLC (downloadable contents).

Q: How can I use them with psnpatch ?
A: Just place them in a exdata folder in a usb stick. Place the stick in the rightmost port of your ps3.
When running psnpatch, press L1 to install RAP & EDAT files.
After installation, you can remove the files from the exdata folder.

NOTE: RAP files are connected to the current console ID (IDPS). If you installed a RAP with a spoofed IDPS, the game will only work when that IDPS is spoofed in memory.
NOTE: I suggest you have a user to install content for one IDPS, and another user to run content of another IDPS.
NOTE: Oppostite to RAP files, EDAT files are system and user independent. Just install and play !

Q: In the readme.txt it says that PSNPATCH can unlock game demos. How ?
A: Simple: Just press R1. All PSN game demos (C00 type) will be unlocked.

Q: I have a 4.46 system that shows a black screen when playing the newer games. What can I do ?
A: Probalby those games are signed with the new 4.50 keys. Simply use psnpatch and press L2. A menu will allow you to choose were to scan for games, including a usb port. Note that usb port 0 is rightmost one. After patching the needed games, the ps3 will reboot.

Q: What does mean the cobra stealth extensions ?
A: These are a set of new opcodes specially designed to make a perfect cobra cfw "stealthing".
When these are installed and psnpatch "disable cfw" option is activated, it is virtually impossible to detect that a cfw is running. Note that this only work in 4.46 cobra editions and 4.53 habib cobra editions. 4.46 system can be of any author known at the moment, but for 4.53 only HABIB versions were tested.

Q: Are there any additional PSN unban suggestions ?
A: A couple of points I've compiled:
1. Stay off-line !
2. Stay off-line !!
3. Stay off-line !!!
4. Never configure your ps3 to auto-connect to psn on boot time;
5. Use psnpatch BEFORE connecting to the psn;
6. DON'T use any homebrew AFTER connecting to the PSN;
7. If you already connect to the psn with a firmware version (ex: 4.50) never try to connect with a lower version afterwards - this will mean INSTANT BAN !!!

Q: What is the XMB ?
A: It's the PS3 menu !

Q: What is a Ps3 ?
A: Well... If you're asking this, you should not be reading this document

Q: You say that "Psnpatch condemns piracy". So, why have you made psnpatch ?
A: KW had a PS3 which Bluray player was damaged for playing disc games. He had to wait for 30 days to receive a "new" reconditioned (repaired) ps3.And was afraid of getting again the same problem. Some time after this, started the cfw wave.

According to the laws of KW country, he has the legal right of doing a backup of legally obtained material (for personal use only). So, he decided to have his ps3 with cfw to play his (long list of legally obtained) games from the internal HDD - sparing the BR drive.

Some time after, He needed to replace the ps3 HDD for a bigger one, but Sony decided to ban his psn account and his console's ID. During the HDD switching he lost all the licenses of the legally obtained psn games !!! So he made this tool, sharing it with the community. Hoping that the ones that will use it, will do it for the same reasons.


PSNPatch v2.22 PS3 App by KW via Kokotonix for CFW Updated

Follow us on Twitter, Facebook and drop by the PS3 Hacks and PS3 CFW forums for the latest PlayStation 3 scene and PS4 Hacks & JailBreak updates with PlayStation 4 homebrew PS4 Downloads.

#141 - genki90 - December 8, 2014 // 7:27 pm
genki90's Avatar
Hi all,

i would like to uninstall PsnPatch. i'm looking for a way to do it.


#140 - lobopt - December 8, 2014 // 7:35 am
lobopt's Avatar
Amazing stuff

#139 - engowen - December 8, 2014 // 6:34 am
engowen's Avatar
Thanks for the update.

#138 - azam0333 - December 8, 2014 // 4:38 am
azam0333's Avatar
Thanks. It's very useful

#137 - MitsuruOkubo - December 8, 2014 // 3:41 am
MitsuruOkubo's Avatar
wow, nice update!

#136 - omarboflot - December 7, 2014 // 7:39 pm
omarboflot's Avatar
This will come really handy

#135 - IndraEMC - December 7, 2014 // 4:19 pm
IndraEMC's Avatar
Since you guys mentioning rebug, I hope rebug will release their CFW 4.65.2 since their 4.65.1 is already removed.

#134 - felipepa - December 7, 2014 // 8:09 am
felipepa's Avatar

#133 - topantita - December 7, 2014 // 5:27 am
topantita's Avatar
great update...


#132 - PS4 News - December 7, 2014 // 4:30 am
PS4 News's Avatar
Following up on his previous revision, PlayStation 3 homebrew developer KW (via kokotonix) has updated PSN Patch to v4.66.22 for PS3 Custom Firmware, which allows users to temporarily disable their CFW, spoof their Console ID and more on as detailed below.

Download: psnpatch


[4.66.22] 06/DEZ/2014

  • Added new Stealth Extensions for future Rebug 4.65.2 with Cobra 7.03;
  • PSNPatch plugin updated;
  • Disabled semi-permanent OFW mode - it is not properly compatible with some newer homebrews;
  • Readme.txt and FAQ.txt updated;


In Rebug 4.65.2, for auto version spoofing to 4.66 go into REBUG TOOLBOX and activate REBUG SYSTEM MODE.


To update psnpatch plugin, stealth extensions or version spoofing, install & run psnpatch homebrew and follow on-screen instructions;

a) ALL non-cobra & COBRA firmware, past and future, SHOULD WORK OK (but note that cobra stealth extensions need to be updated per version);
b) For proper CFW disabling IN COBRA (REBUG and NON-rebug), stealth extensions are recommended (but NOT mandatory).
c) Stealth extensions are made PER CFW VERSION and need the CFW author to release its stage2 source code.
d) KW will try to keep PSNPatch updated to support the most current firmware versions (at the moment: 4.65 for REBUG, 4.66 for all the others) and also 4.46.
e) Rebug versions needs a special processing mode, but even without stealth extensions, psnpatch plugins uses a "rebug cobra mode" to disable CFW.
f) Rebug CFW should always be run in "REBUG" mode - use rebug toolbox for that.
g) Don't ask if or when cfw XPTO version XX.XX will be supported as there are no plans to make stealth extensions for every cfw flavour. What it is, is what it is.
h) If you have any issue, before starting to say that "PSNPATCH doesn't work", try to "search, browse and explore". 99 in 100 questions are answered just by reading PSNPATCH provided docs. And google is your friend

Finally, from kokotonix: Hi Guys: I've just waked up with a lot a messages here I thought it were "good" messages, but BRICKS ??? No ! Never !!! PSNPatch was (as always) heavily tested before being released. The only things that changed in code were:

a) cobra stealth extensions for rebug 4.65.2 (which are also compatible with .1 - tested in both rebug and normal modes)
b) removed semi permanent ofw mode as it was not giving the expect result with some newer homebrews.
c) and of course, the version numbering reporting (4.66.22) in both psnpatch homebrew and plugin.

Nothing more was changed. When you first start a new psnpatch version, it will report that new version spoofing files are available.

This means that if in the future you pretend to use psnpatch version spoofer, the information is included inside psnpatch - it is only an internal issue. it does not imply anything else. And if it ever implies something will be only in cobra based systems.

In the past weeks there were many users starting to have issues that were ultimately discovered as related to corrupted databases or file systems.

It is not unusual to ignore (my self included) when our ps3 ask to scan the file system and that it may take up to 2 hours time.

This said, it is a good practice, from time to time, to enter in the recovery menu and choose to restore the file system and rebuild the database (options 3 and 4).

Even so, if you ever come to a brick, it can not be more than a "SOFT" brick. The practical difference between a SOFT brick and a HARD brick, is that YOU DO NOT NEED A FLASHER A FLASHER TO RECOVER A SOFT BRICK:

Still, I don't believe that psnpatch produces soft bricks, but being the main objective of a forum to help each other, here is a quick guide on How to Recover from a Soft Brick:

Needed material: an additional sata hdd to insert in your ps3.

a) remove your original hdd;
b) insert another (windows / linux or pc formatted) hdd in your ps3;
c) ps3 will format the new disk and ask to reinstall the firmware (use the same firmware version);
e) after installing the firmware remove the new hdd;
f) place back you original hdd;
g) now the ps3 will ask to re-install the firmware WITHOUT NEEDING TO FORMAT THE ORIGINAL HDD;

You have just recovered from a brick without using a flash nor formatting your hard-disk.

Please report here anything you have regarding psnpatch 4.66.22. When doing so, you have to report exactly what you have done, what is your firmware version, if you are using any kind of version spoofer, which homebrews you are using etc.

I don't believe in the reported bricks. But I will appreciate that once the reporters of the bricks agree it was not a psnpatch issue, that they report it here.

Anyway, we are making a new stealth approach in psnpatch that will not need to touch the cobra payload ever again. This has been thinking in order to assure compatibility with every cobra version PAST & FUTURE and this way, each time a new firmware version is released, there will be no need to update psnpatch (as already happens with non-cobra firmwares).

Either way, following the last reports, it will be also a way of assuring that no brick will ever be imputable to psnpatch.

Update: While new PSNPatch is being prepared, namely adapting the new stage2 changes recently released by deank, there is something we would like to ask the community of PSNPatch users:

A) list of games which you had issues with the previous stage2 code and that now are fixed.

B) list of games which were ok before,but not working in the same way for now.

For both lists, it is very important to understand if the tests are from internal/external and JB/ISO, and also the game ID (blesxxxxx, blusxxxxx, npebxxxcx, .....)

Thank you very much. Psnpatch 4.66.30 is almost ready.

It should mark a big change in psnpatch cfw disabling for cobra. Until now, for a perfect disabling, stage2 needed to be recompiled with the stealth extensions. This is needed because cobra protects the syscalls table and so we needed to place this code inside cobra core.

In the past weeks KW has made many changes to this, in order to inject the stealth extensions in to the cobra core at run-time without the need to recompile the stage2.

The biggest advantage to this approach is that it will be possible to assure compatibility with every (past, present and most certainly future) cobra and non-cobra 4.XX firmwares without ever needing to update psnpatch again.

This way, KW will focus in developing and adding new awesome functionalities to psnpatch without worrying again with new version releases or stage2 changes.

Psnpatch will continue to support the traditional stealth extensions. The psnpatch plugin boot message will continue to display the working mode:

  • stealth cobra (when traditional stealth extensions are detected);
  • enhanced cobra - when using the new stealth technique;

Both approaches will guarantee the same level of protection.

Note: as a reference, stealth extensions source code will be released with the new psnpatch version.

More PlayStation 3 News...