Editing E3
Jump to navigation
Jump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 180: | Line 180: | ||
From this point on, follow [[Downgrading_with_Hardware_flasher#Reinstall_firmware_in_Factory_Service_Mode|the main guide starting from ''Reinstall firmware in Factory Service Mode'']] | From this point on, follow [[Downgrading_with_Hardware_flasher#Reinstall_firmware_in_Factory_Service_Mode|the main guide starting from ''Reinstall firmware in Factory Service Mode'']] | ||
== E3 De-Bricking == | |||
See also: [[Boot_modi#Errors_on_boot|Error on boot]] | |||
:'''Remark:''' ''In this small section, the few examples are assuming a fully working console, without broken hardware and the reason of its error behaviour only to be caused by flash (CoreOS/ROS).''<br /><br /> | |||
Signs you are bricked: | |||
* PS3 turns on but instantly turns off (Behaves exactly like the YLOD) | |||
* Black screen | |||
* No HD activity (No flickering light) | |||
* Combinations of the above | |||
The console can be bricked when installing unpatched firmware. For example: Going from Rogero 3.55 3.7 to Rogero 4.30 without [http://www.ps3devwiki.com/wiki/Template:QA_dehashing dehashing]. | |||
In case syscon has 3.56+ hashes, you need prepatched LV1. | |||
When this happens the PS3 either produces nothing (black screen) or more commonly it gives you the RLOD/YLOD and won't turn on.<br /> | |||
Generally de-bricking is the same as reinstalling the firmware, but sometimes it can be easier or harder. | |||
<!--// | |||
editor note: alot of this E3 De-Bricking section is duplicate and simplified to single cause/effect, which is wrong //--> | |||
== Error Codes == | == Error Codes == |