Sony Suspends PS3 Consoles, PSN Ban Wave Error 8002A227
Update: Many users including namdlo and nannou have pointed out the picture is dated, and have determined this scare to be more of a wake-up call than a true Sony PS3 ban wave over the PS JailBreak PS3 modchip.
As expected, with the release of the PSGroove open-source PS JailBreak PS3 exploit Sony is fighting back and now banning PS3 consoles, with the PSN ban wave error code being 8002A227.
Forum user StandardBus of Italian site ModdingStudio.com (linked above) first reported this, and based on the PSJB Backup Manager ID apparently Sony is banning the OpenPSID or PS3 MAC address... meaning another PSN account won't do you any good.
Needless to say, PlayStation 3 consoles will soon be shipping with an updated PS3 Firmware revision to patch the exploit.
Below is the rough translation from StandardBus on the PS JailBreak PS3 console bans:
"Predictably, in the end it happened. Maybe some of you were already aware of it, but because of the holidays (and the lack of coverage for data traffic in the area where I was on vacation) I could not actively follow the scene as I usually do.
For anyone who had missed the news, Sony is left with its hands seeing copies of his JigKey distributed at an impressive speed to all major retailers of mod chips for consoles.
Some users who have rushed to buy the key in question and abuse them without getting too many problems on the legality of their actions, recently could not help but note that their console was excluded from the use of any online service offered by Sony.
This exclusion / limitation (in computer terms "BAN") is the inclusion of the NDP registered user nickname to a "blacklist" servers in this Sony.
But we are talking about... JigKey. Sony plans to block all online console those who make use of that key, just like Microsoft with the Xbox 360 some time ago.
We said that several users, after purchasing the key, received an unusual error code trying to access the game online. Viewing the code is 8002A227.
Analyzing the backup loader pkg PSJailbreak released by the team, you may notice that the ID program is LAUNE-12345.
The initiation of programs (with its ID) is recorded in a sort of log in the HDD of the PS3, and Sony is sent to the server for statistical analysis anything but anonymous when the console is connected to Internet (yes, they know who we are, what games we play, how we play and how often, but this is just the tip of the iceberg of data Aquisito on our behalf every day).
Wii also uses this system, but is more discreet in the aspect that the user is given opportunity to view the log in question.
Once you understand this simple mechanism, it is natural to understand how the servers can automatically identify the Sony console and PSN account of people using the key: once considered the log and found the ID-12345 LAUNE simply discover the IP connect the console to find the nickname of the user who has used it and proceed with the ban by adding a nickname to blacklist PSN.
And there's more: some users may forward the idea of changing the nickname to allow console access again the NDP, and partly as a solution may seem effective, but it seems that Sony has also thought of this possibility by request to the consoles connected to PSN their Mac address, uniquely identify the console without the possibility of error, and allowing the permanent ban console all online.
Remains to understand why the team PSJailbreak not activated to change promptly to their application ID, allowing Sony to go to the bank account to account, the console on the console.
Arise at this point spontaneous questions: This is the first demonstration that the team has the sole intention of selling as much as possible and then disappear leaving the customers?
The key upgradeable firmware has been described by many experts as a feature useless, really need to dupe more people can fool with the possibility of updates that do not ever exist?
We hope for those already effected the purchase of JigKey is not so. The seriousness of the team has been challenged on many forums, react to plug this big problem or let it go?"