Oh no! Where's the JavaScript?Your Web browser does not have JavaScript enabled or does not support JavaScript. Please enable JavaScript on your Web browser to properly view this Web site, or upgrade to a Web browser that does support JavaScript; Firefox, Safari, Opera, Chrome or a version of Internet Explorer newer then version 6.

Hey everyone – We’ve got an exciting new feature coming exclusively to PlayStation Plus subscribers. Included in the system software update (v3.60) coming tomorrow to PS3, PlayStation Network’s new online storage for game saves feature gives PlayStation Plus subscribers the capability to back up game save data to the cloud. Online storage for game saves is a great way for PlayStation Plus subscribers to ensure that their data files are secure and also for users who wish to access their files from other PS3 systems.

We were waiting for new developments about online game on custom firmware (see kmeaw, geohot and others) when one of the brightest minds of our team has produced what we might call, the fastest possible access for the PSN.

The firmware is based on Kmeaw’s custom firmware, to which were added 2 small patches which allow access to the PSN!

Access is fast,no PC is needed to serve as a ” bridge “and then programs like ****Psn or charles, skipping the check of the model (debug, retail, reftool, etc.) and setting of the PS3 fw at 3:56 .. (not in the XMB)

Of course the risk of BAN is still high and being a CFW, ps3ita assumes no responsibility for any brick during installation.

Naima from Elotrolado, has released a 3.55 CFW with similar abilities to that of Kmeaw 3.55 CFW. It has integrated the new PSN SSL bypass method so you don’t have to follow any lengthy guide just to access PlayStation Network on your 3.55 PS3; Naima 3.55 CFW does it for you.

Below is a rough translation using 'Google Translate' from elotrolado.net

Following the publication of which is news of the day for many, I mean the details of how to perform a man-in-the-middle authentication mechanism based on SSL using PSN in order to access their services from consoles PS3 firmware which is earlier than the last official, we can read widely in the forums to the large number of people expressing their problems for the process.
One of the most common problems is the replacement of a CA certificate in the flash needed for the attack to work.

Without CFW to integrate the certificate is replaced need to venture to write to the flash through more complex, which in principle should not present risks, but in inexperienced hands the possibility of causing damage.
After thinking seriously about to publish a CFW with this change made I decided to do so only to avoid any disaster that might cause someone to console and to offer a convenient solution for anyone wishing to investigate the SSL communications PS3 does.

What makes this CFW?
It brings no newly issued by the reason that I did not want a detailed explanation of the reasons you can find then
simply for comfort, convenience of which can have up to now.

What features do you have?
The minimum necessary in order to provide stability.
- Support for Peek / Poke through patching lv1, lv2_kernel (Thanks to Flukes)
- Add 'Install Package Files' by modifying category_game.xml
- Installing. Pkg unsigned nas_plugin.sprx by patching (the only method that does not mean Sony reveal key)
- Replacement of CA24.cer CA certificate by including in the implementation Charles Web Debugging Proxy

Why replace rather than add and we chose the 24?
Because it is not known if they add, and we chose the 24 because the license is included in the PS3 is outdated and therefore no longer valid.
The 27 also has expired. Replace an expired certificate is not therefore valid, would imply unwanted side effects.

Why replace it by including Charles?
Because any CA certificate which has the private key we serve, one that we generate for example, but since you are using the application for the MITM attack and certificate is as good as any other, we choose the same.

Research on the content of the CFW, lv1 files, lv2_kernel, category_game.xml, nas_plugin.sprx are different from those known so far used in other CFW, why?
For the simple reason that he 'changed' me and not exactly the same, the encryption also increases the differences.
But the functionality is the same as the patches.

Installation is safe?
100% sure there is nothing, not even an official firmware upgrade. Ta is safe as it can be an OFW or CFW of kmeaw.
Of course, I take responsibility for any accidents that may occur.

How I can avoid risks?
- Start from a OFW is ideal.
- Check the integrity of the original PS3UPDAT.PUP, it should be: = CA595AD9F3AF8F1491D9C9B6921A8C61 MD5, SHA1 = a3a0d1c61e17c6a58a5fa247a3dbb51524329e0a
- Check the integrity of the 'Custom PS3UPDAT.PUP', it should be: = A3BED5E37E33440EC276AC98A6C2C6AB MD5, SHA1 = a20ec86447a7f087e87e79061fa2e7f430b2a40b

You can help the rest of the steps?
I will not do, for various reasons.
One is that you are using a commercial application, Charles, requiring payment for its use.
I will not give support for a commercial application also know that many are using unlicensed.
This is not to say that let you use it, Charles is a simple tool use, in fact, using Linux with open source utilities would be a more complicated for ordinary users.
Moreover, at this point I think it is a tutorial available to almost everyone.

But the main reason is that some have ended my patience.
And communicated for some time that I have the great patience of others, such as Hermes, which I consider a person with the patience of a saint (especially after the incident of the dongles with your name)
Me, on my patience and tolerance is 0.
And that patience is over because of some who have placed special emphasis on required and especially disrespect.
Anyone who has followed the thread 'fw Bypass. 3.55 'and' Online with CFW 3.55 Kneaw 'know the situation perfectly.

So do not expect any other contribution on my part on indefinitely, that is, until one day I want to.
There seem to be 'ready' eager to share his wisdom to those who can ask for me,
ready to sow the two wires above their wise contributions, which unfortunately were obliterated dozens of moderation, but with a quick review of the post you can identify their names. Ask them to them.

For years, the security system of PS3 remained unbreached because Sony had a
very good defense mechanism: Consumers could use it for more than just gaming
by installing Linux via the “Other OS” feature. Therefore there was little
motivation for security researchers to investigate the PS3. However, then Sony
(or SCE, SCEA, SCEE or whatever, we aren’t exactly sure what is going on there
anymore) made an unprecedented move: Not only did they introduce a new PS3
model that no longer allowed the installation of an Other OS, but with a
firmware “upgrade” they removed it from previously sold consoles.
While removing advertised features from a product (several years after its
purchase!) is blatantly unlawful, having highly paid lawyers apparently allows
you to get away with it- in a legal sense.

But when the law fails to protect the people, then some of those people, being
clever and resourceful, help themselves. And that is what happened here. Sony
sunk its own battleship.

PS3MFW is the next step in the process of returning to consumers control over
their own hardware. Your PS3 belongs to you. You didn’t lease it, and you
signed no contract when you purchased it. It is your right to use it however
you choose. It is your responsibility to do so within the legal boundaries.

PS3MFW allows you to tailor your PS3′s firmware to your specific needs, giving
you a level of control you previously lacked. PS3MFW is open source. That
means it is completely transparent, and anyone with the necessary programming
knowledge can help to improve it and create new plugin tasks.

It is with great pleasure and joy that we are now able to present you with the
first public release of PS3MFW Builder. A lot of hard work went into this
during the past five weeks, by some incredibly dedicated and inspired people.
We would like to thank everyone who contributed, the people who got this
project underway, and those who did all the programming and testing.

PS3MFW Builder v0.1 has been successfully tested on all major PS3 hardware
revisions, and in conjunction with OFW 3.10 – 3.55. It is NOT compatible with
OFW 3.56.

Remember that this is only the very first release of PS3MFW Builder, version
0.1. With your support and feedback, we intend to create the definitive PS3
firmware solution that makes all other closed-source custom firmwares obsolete.

PS3MFW Builder is not distributed with any program code copyrighted by third
parties.

READ CAREFULLY BEFORE YOU PROCEED WITH UPDATE (FW 3.55)!
- No payload of any kind included in the distribution
- Support for "Black screen games" using external USB HDD
* BDEMU.BIN or external payload required to enable following functionality:
- Support for AVCHD/BDMV structures saved on internal HDD (AVCHD HDD)
- Path redirections for /dev_bdvd and /app_home
- BDEMU.BIN is not distributed with install packages

For those who bricked their console using v1 of the Wanikoko CFW, here is a way to recover from it. Albeit very difficult, but those without any other option should be happy.

OK, so we all know about how the original Waninkoko firmware broke the older large NAND consoles, that was due to him overwriting some portions of Cell-OS Lv2 and the segment boundaries, god knows about the signature also. He also zeroed out a good section of the kernel, and also breaks some NAND consoles due to that. Now, you want to fix this issue? Well, you have to have:

OK, so you first have to dump both NAND chips (2 128MB NANDs for a total of 256MB) and interleave them using Flow Rebuilder, then decrypt the CORE_OS package to give you a raw core OS image, then open your combined NAND dump in a hex editor and search for “6F FF E0″ in the search for hex section. Once there, you should see:

Right after the second “6F FF E0″, remove the next 7,340,000 bytes, then, insert the unpacked Core OS (7,340,000 bytes). Then split the image using Flow Rebuilder (use ECC!) and flash. Hopefully it should work, and then you can just Lv2diag your way out.

8.0.0 - This version is Compatible with OFW3.41+Dongle/Hermes CFW3.41/CFW3.55/Kmeaw/Waninkoko.
8.0.0 - Changed from using LV2_patcher/PL3 to Dean's implementation of Syscall36.
8.0.0 - The Manager can be started with Disc In + USB inserted without any problems.
8.0.0 - Updated the Payload Auto-Detection to support all types of Payloads/CFWs.
8.0.0 - Fixed the FTP Server, FTP always on by default, login as "anonymous".
8.0.0 - Added Auto-Fix Permissions on Game Load, can be Enabled/Disabled from Settings Menu.
8.0.0 - Fixed the scrolling lag on D-pad Up/Down, now scrolling with any button is fluid.
8.0.0 - "Protected Mode" now can be Enabled/Disabled by pressing [L2+R2+R3] from the Menu.
8.0.0 - Added the option to Enable/Disable the Clean History function from Settings Menu.
8.0.0 - Optimized the Fix-Permissions function,now it outputs the path of the folder being fixed.
8.0.0 - Added Full Auto-Detection of the Games folder at initial Setup or from Settings Menu.
8.0.0 - The Games folder will be moved automatically to a safer path if found necessary.
8.0.0 - Fixed the Copy function to prevent the Abort-Copy error that was encountered by some users.
8.0.0 - Added A Screensaver after 3 minutes of inactivity,can be Enabled/Disabled from Settings.
8.0.0 - Simplified the Initial Setup wizard,select [Yes] on all steps for default settings.