My PS3 doesn't turn on.
I attempted to do an update to my PS3 and it failed the update 2 times so I thought that I would power cycle it to see if it would finally work.
When I power cycled it I flipped the power button on the back off and pulled the power cord out for 20 seconds. When I turned the device back on the red light on the front came on showing that it has power.
I pressed the on/off button on the front of the PS3 and then the green light came on showing that it was booting up, but the green light only stayed on for 10-20 seconds then it immediately went back to red.
I can't really hear anything turning on in that 20 seconds that the green light is on and am wondering what went bad? Does anybody have any suggestions to help me find a solution?
Can I pull out the hard drive and re-format it and put it back in to see if the file system was bad?
Any suggestions would be super helpful!
Oh boy, this isn't good. You don't want to format the hard drive because you will loose the update data that the system is trying to read. Try this:
- Make sure the system is off and the light on the front is solid red.
- Hold down the power button and it will beep a few times and turn back off.
- Let go and hold it down again until you hear a double beep.
- Let go and see if a menu comes up asking you to plug your controller in.
- Plug it in and go to system update.
This is a manual update. Go to http://us.playstation.com/support/system... and follow the instructions on there for the manual update using your thumb drive. Hopefully this will fix the problem.
The idiot that suggested this "double beep" needs
to drink bleach and die.
I'm having this same problem now, but this isn't the first time. About two months ago I hit the power button on my PS3 only to find a black screen. I had never had this problem before so I called support. They took me through the quick step that was already mentioned about (holding the power button until a second beep) then it worked. It took me through a step confirming that there was now a picture on my screen and the connection was working properly.
Tonight, I'm having the same problem all over again. I hit the power button and nothing but a black screen. So, I tried the same step with holding down the power button until I heard the second beep, and nothing happened. Still a black screen. Less than 20 minutes ago I was on the phone with support wondering what to do now? He took me through the same step I had already tried and nothing again. Once this did not work, I turned the system off again using the power button. Once the system was off, he had me hold the button down until I heard a THIRD beep. After you heard the third beep, the system immediately cuts off (as it is supposed to). Once the system was off again, he had me press and hold the power button until 1....2...3,4 beeps (third and fourth beep are much closer together this time). I still had a black screen after that. The support agent tells me I need to try a new HDMI cable, which I will do but have not had the chance to do yet as it's nearly 11pm and there's nowhere open to buy a new cord.
Just out of curiosity I asked what I should do if the new HDMI cord does not work... Well, since I've had my PS3 for two years now and it's outside of the manufacturers warranty, they will require $149 plus shipping and handling fees to have my system sent off to be fixed. That is total BS! I've paid $300 for a system that I've taken extremely good care of, only for it to just quit on me after two years! And Sony wants another $149+ because of something that isn't human error, but mechanical error. Regardless of whether or not a new HDMI cable works to fix this issue, that's a smack in the face to hear them say they want that much more money to resolve something like this. I'm disappointed in you, Sony. You gave me two years of gaming+ at a rate of $150 per year...and that's not to mention the amount of money spent on the games. What a way to rob someone. I'm certain others have been a victim of this, lets hope I'm not. If the new HDMI cable does not work, I'll be raising some serious *#&#, and so should anyone else dealing with this problem.