The above video goes away if you are a member and logged in, so log in now!
Possible brick? Obvious fail anyways. HELP!
Possible brick? Obvious fail anyways. HELP! –
I left the PSBreak 1.2 programmed as downgrader by my PS3 and my sis tried to turn it on the old way, i had CFW3.55 at the time. When i got back from work, i found a big black brick with a PS logo on it. It turns on to factory mode but shuts down after some 3 seconds. Any ideas?
Come on guys, I've googled and read forums for past two weeks, please don't abandon me. The biggest problem is that I can't get it to recovery mode, after holding the power button until it shuts down and then holding it for the two beeps it just shuts down.
You can't go into recovery mode through factory mode. You're suppose to have the Lv2diag.self on a tumbdrive connected the usb closes to the BD drive, just turn on your system and it should be back to retail from factory mode, then from there you can go into recovery mode.
note: But then again I've never heard of a PS3 that automatically shutdown while in factory mode. I've only heard of auto shutdowns with YLOD and Waninkoko_v1 CFW, your sis might have created a new problem for you.
Thanks mate, i will try this ASAP.
Yah... I've got to the recovery mode and started updating to OFW 3.55. After pressing start + select and inserting a thumbdrive at 0% (blinks for a microsecond) i got the 8002F281.
After googling for a while i found that this is a HDD related error. There are some old tutorials on how to format it to NTFS, others say that in this case you have to remove the battery, and i also found this:
http://psx-scene.com/forums/f149/blu...-55-cfw-74794/ (BluRay Drive bypass 3.55 CFW)
Any advice on what to do next?
DON"T FORMAT your hdd to ntfs the PS3 can't even recodnize ntfs. 8002f81 error could come from your thumbdrive, there are some brands the PS3 can't read. If you have another thumbdrive try that. Format your thumbdrive and make sure no other files other then the firmware is on the stick.
I had that error code before, it's definately from your thumb drive. Try a different thumb drive, that has a brand name on it. I got mines to work with a Sandisk thumb drive, that i normally use for school.
But seriously, i have used my Apacer thumb-drive for numerous firmware updates, launching games from it and so on. How could this possibly have gone wrong. But yeah, i will try it.
Same here, i've used other thumb drives when updating, i didn't understand why my other thumb drives refused or either failed to update the PUP file. If you still don't believe it, do an MD5 Check of your PUP file on your desktop and then once it's on your flash drive do another MD5 check there. You will see that MD5 Hashes are completely different on your thumb drive from when it was on your desktop.
Here is the MD5 Hash for 3.55: ca595ad9f3af8f1491d9c9b6921a8c61
If it isn't the same on your thumb drive, then you already know what the problem is.