So I opened up my console and took it apart and unplugged the battery in the ps3 for five minutes then I put it back together and it works perfect and connects to psn so if your willing to void your warranty then its a easy fix. Also I would recommend this fix since I'm certain sony will sneak something into the update to fix this that will render geohots exploit useless
Good to know,thanks for sharing.
I open my 60 once every 6 months for cleaning anyway, it has been 3 months or so since the last cleaning, if tomorrow nothing comes out from sony i ll give it a try.
i have tried everything else and fail, lets see if that works for me too.
Is this a debilitating issue? I don't sign onto the PSN much anyway, so I'm not about to get that fix or open up my PS3 if it doesn't absolutely call for it.
yes games that from playstation store will not work and certain games will not work even offline like heavy rain but now they are saying the problem will fix itself by tomorrow so if you can wait a day do that
Service Temporarily Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
it is advised on the fourms you don't take your battery out as you will lose your data copied from psn fourms before it went downThere was no need to have 20 odd threads all about this issue this morning. We can just as easily see one thread with many pages as we can a forum full of threads. We do look at reply count for busy threads. If you wish to discuss this issue please use this thread in the PlayStation Network forum: http://community.eu.playstation.com/t5/P...ion-Network/... Here's the announcement I have for you. Some consumers are experiencing a network connection failure when signing into PSN and may receive the error code 8001050F. We are aware of this issue and it's currently under investigation however at this time there is no estimated time to fix. Please refrain from calling your local PlayStation call centre and keep watching this space for further updates...
[b]from a member [/b]word of advice dont attempt to log into your playstation network or even play a offline game that that might try and upload information onto your profile.
Alright, I have worked out multiple theories as to why the PS3's are crashed based on available information. Boss feel free to move this to the front page if you wish. First off; as far as we know only fat PS3's are effected; (Forgive me if I am incorrect, that doesn't hurt my hypothesis, but does poke holes in my solution).
That all PS3's went down yesterday 2-28-2010 at around 5PM Eastern. Also that PS3's are effected whether or not they are on the internet. That only a few games work currently, and trophies are down. PSN, is still up; and that some systems were bricked as a result.
Now that we know that, lets review possible theories.
1: Sony is trying to stop Geo Hotz hacking.
Though at first this seems likely, 'Maybe Sony made a mistake when trying to block hacking of the ps3' you might say. But even though I also believed this before it's now impossible. Sony couldn't have bricked consoles that were offline, and since that problem is arising, it's obviously not some online update or anything related to being connected.
2: A problem with the latest firmware.
Again, this one is possible, but not likely. The theory goes that since the date on the PS3 was set to 1999, there was a problem in the latest firmware. What the problem is no one knows, but some speculate that because Sony changed the father files in the PS3 to say 'PS3' upon start up instead of 'Sony computer entertainment' Sony might have screwed something up. I find this unlikely. Just changing two basic files isn't likely to crash an entire system this far after the changes. So I find this unlikely.
3: The Date & Time Problem of K2Y.
Simply put, when Sony wet up the PS3 they accidentally screwed up when programing the calender they messed up 2010 with a leap year. Which may explain why the PS3 had the problem happen on the twenty-eighth of February. However, this doesn't account for the fact that resetting the date doesn't fix the console. On top of that, 1999 isn't a valid year for it to be set to in the first place. It wasn't programmed into it.
4: Sony was hacked?
Sorry to admit this, but the best theory I have is that Sony mus have been hacked. Sony may have had a hacker put some files that were set to activate at a specific date. Which if you take into account that the PS3 slim hasn't been effected, means that all firmware after 3.0 has this problem. So the only thing I can assume is that the PS3 will start working again if Sony releases an update with the Slims architecture. Sorry, but this is the only theory that explains everything. The 1999 date, all the license rights being void, the discs inability to start up, trophies being deleted. You name it, this explains it.
What can I do?
First off, I recommend not playing any games you have that you want to keep your trophies on, even if they do work.
Don't turn on your ps3 if you can avoid it for the time being, lord knows you don't want your system bricked. Wait for the latest firmware to come out, then make sure it's unplugged from the internet when you turn it on the first time. This doesn't matter if you already turned on your ps3, and finally...
i have been playing cod mw2 in single player mode today i got to the third mission i gained trophys also nothing has happened, is it because im not signed in the internet, i have never signed in the net yet. any help pls? thanks
If i got it right,
What he is saying is that someone hacked the FW before sony released it?wile it was still in development?
and sony never knew about the hack or the hacker.
yeap...... that sounds really really believable.
Later on the day that i will have a discussion with Zeus, i'll ask he's opinion on this.
i have another theory, that Sony knew about this error but for some unexpected reasons they failed to deliver the new FW on time.
Another theory says that they just made a mistake.
Either way I'll stick with the Human mistake theory.
Seems to have been that the internal clock on the Phat PS3's look at every even year to be a leap year when it should obviously be every 4 years and the reason this wasn't an issue in 2008 is because it was a leap year. So when GMT hit to March 2 a few hours ago the PS3's fixed themselves. All you may have to do is adjust your date from 3/1/2010 to 3/2/2010.
