27w ago - Today Sony Japan (linked above) and in North America have issued a PSN consumer alert against unauthorized software resulting in the start of a PS3 ban wave with PlayStation 3 Custom Firmware users receiving error code 8002A231.
Below is the Press Release, as follows: "Consumer Alerts - Important Notice: Access to the PlayStation Network and Access to Sony Entertainment Network Services
Dear valued PlayStation 3 customers,
Unauthorized software for the PlayStation 3 system was recently released by hackers. Use of such software violates the terms of the "System Software License Agreement for the PlayStation 3 System" and the "Terms of Services and User Agreement" for the PlayStation Network/Sony Entertainment Network and its Community Code of Conduct provisions.
Violation of the System Software License Agreement for the PlayStation 3 system invalidates the consumer's right to access that system. Consumers running unauthorized or pirated software may have their access to the PlayStation Network and access to Sony Entertainment Network services through PlayStation 3 system terminated permanently.
Please do not use the unofficial one that some bad guys released broken some days ago. That version does not send console ID on PSN servers when you connect, so you are quite anonymous! Please do not download that version that is not official and it does not work.
FckPSN is a simple SSL proxy, used to spoof your PSN version and re-enable PSN access for your console.
CA27.cer, dev_blind.pkg, fckPsn-v0.6.exe
OpenPS3FTP v1.3 or later
v0.6: Use an empty consoleid. Warning: be sure to get my 0.6 version
1. Install dev_blind.pkg and OpenPS3FTP on your PS3 (using FTP, external USB or what else)
2. Launch dev_blind and make it mount the flash
3. Open OpenPS3FTP
4. Connect via FTP to PS3 (using username root and password openbox)
5. Go to /dev_blind/data/cert
6. Rename CA27.cer to CA27.cer.bak
7. Put my CA27.cer as /dev_blind/data/cert/CA27.cer
8. Set the PS3’s PRIMARY and...
122w ago - There have been quite a few articles about possible things that Sony could end up doing to try and stop PS3 homebrew, and here are all the potential solutions I have noticed thus far.
PS3's will start sending a recently played list to check for homebrew titles / flagged names:
Pretty obvious solution here. Just start naming the homebrews after currently existing titles, Or titles of bad games. Such as we can take the game name / BLUS for the game FLOCK (worst game ever that nobody will play) and install a master manager under that name.
So while it looks like everyone is playing FLOCK, We will actually be using a multimanager for FTP's, Backups, and Emulators.
Sony disabling update by USB in the next patch:
There are a few options we can take if we end up accidentally getting hit with this.
For people who update and can no longer install from usb:
Either the firmware will need a pre-installed pkg manager with firmware update options, Or they will have to do a dnas redirect to their computer to check for an update.
For people who have not updated to the new firmware that disables...
131w ago - Update: As confirmed by many users now (including DJLO who posted the pictures below), along with stopping PSN gamesharing Sony has blocked PlayStation Network access for PS3 Debug (8002A212 Error) and PS3 JailBreak users who now are asked to update their console through a message prompt.
Just over a month ago PS3 JailBreak users had a PSN ban wave scare, and today a new PAN/Europe TOS update may indicate that Sony is finally planning to begin banning JailBroken PS3 consoles on PlayStation Network.