Editing Talk:Boot modes

Jump to navigation Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

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 7: Line 7:
   <jestero> so i disagree if you say that ylod it's a hardware stage problem
   <jestero> so i disagree if you say that ylod it's a hardware stage problem


  <mysis> i had ylod when booting into ps2 lpar, turned out to be dev_flash/file access error when replacing files there. pup reinstall solved it.


== Bluescreen without any information ==
example: http://www.youtube.com/watch?v=gv72yI8851s
===Problem description===
QA flagged 3.41 CECHC04 system (MinVerCheck says lowest applicable is 1.00), when downgrading to 1.02, 1.50, 1.51, 1.54, 1.60, 1.70  Retail/CEX in Recovery on 2.50 or higher, after installation the only output was a Blue filled screen (YPrPb/Component + Composite cable on multi-input TV).
Resetting videosettings by holding power until beep did not solve the issue.
'''Note:''' trying to use 2.43 Retail/CEX in Recovery on 2.50 or higher on the same downgrade QA flagged console results in abort of installation with reason: "The latest version of the system software is already installed. There is no need to update."
=== Solution ===
Used PSGrade JiG (PS3key) to trigger service mode (had noticed it still had USB activity) - after which system shutdown as expected, then lv2diag downgrader 3.50 and 2.50 PUP in root of USB for reinstall like a normal downgrade (expecting system would still be on 3.41 and failed the 1.02 before) and then the out of service mode lv2diag. Only after getting out of service mode the videooutput was restored and needed to do initial setup of userconfig again (also harddrive database needed to be restored and my old userdata was also reenabled).
== Redscreen without any information ==
===Problem description===
When experiencing above bluescreen, enabling factory service mode and trying to boot it normally to XMB will result in an empty full red screen.
=== Solution ===
See above reinstall of 2.50 (or higher) firmware in service mode.


== RSOD ==
== RSOD ==
Line 44: Line 26:
</pre>
</pre>


=== RSOD question from Rogero ===
=== RSOD question from Rogero (based on Abkarino/kado marked files) ===
==== How is it addressed? ====
==== How is it addressed? ====
   http://www.mediafire.com/?na6vdx9fkiac0v5 <--- RSOD
   http://www.mediafire.com/?na6vdx9fkiac0v5 <--- RSOD
Line 81: Line 63:
   (documentation purpose only, DO NOT USE! BRICK/CORRUPTION RISK)
   (documentation purpose only, DO NOT USE! BRICK/CORRUPTION RISK)
//-->
//-->
==== What's the strange patch? swindle explaination ====
What's the strange patch?
It patches basic_plugins.sprx so that whenever corruption is detected, it will not show RSOD, never error out to alert the user of the problem and FIX the issue and thus only blindfolds the user while the system corrupt it further and further, until beyond repair (in short: '''they use it to swindle their customers''' by NOT fixing the issue and LIE to the customer that it is solved)
It patches basic_plugins.sprx so that whenever corruption is detected, it will not show RSOD, never error out to alert the user of the problem and FIX the issue and thus only blindfolds the user while the system corrupt it further and further, until beyond repair (in short: '''they use it to swindle their customers''' by NOT fixing the issue and LIE to the customer that it is solved)


=== Abkarino ===
=== Abkarino ===
<pre>
  <Abkarino> he had teached me a lot of things
  <Abkarino> he had teached me a lot of things
  <Abkarino> like fixing RSOD consoles
  <Abkarino> like fixing RSOD consoles
Line 141: Line 125:
  <Abkarino> have to go
  <Abkarino> have to go
  [...] (long silence)
  [...] (long silence)
<n00b774> http://depositfiles.com/files/nti7olk5b
<Abkarino> http://www.mediafire.com/?86v681x9wl5o3qn
<eussNL> http://pastie.org/3149193 ^diff
NOTE: If you are crazy enough to want an RSOD, just 0x00 fill CVTRM. DO NOT DO THIS WITHOUT A FLASHER!!!
==Firmware Crashes==
This is a collection of crashes ordered from small to bigger (in order or importance), are separated by the behaviour the user see when the crash happens
All this "standard" crashes listed here are supposed to happen over a firmware that is running without problems, and the crash is not caused by a firmware modification
The firmware crashes when one of his threads/subprocess crashes, so when the firmware crash can be considerd a consequence of other crash (there is also the possibility of the thread to be "stuck" in a infinite bucle ... in this case the firmware doesnt crash, but is "stuck" in a black screen forever)
*The most common cause of a firmware crash is a problem in the thread that is running (app or game)
**Typicall in homebrew apps in beta stage, eboot game fixes, version spoofers, etc...
*The second common cause of a firmware crash is a "semi-corruption" of the [[XMB database]]
**Typicall when adding content manuallly in the hdd that needs to be managed by XMB (e.g: any content in XMB game category column)
Always try to avoid forcing one of this "turn-off" methods when the "HDD activity led" is blinking to avoid a problem with the filesystem. All this methods needs to be used in order, if the "eject crash" doesnt works try with the next one
===Eject===
Press the eject button 1 time. The "eject blue led" blinks, then the disc ejects, and you are "kicked out" to XMB
This only works when you have a real disc inserted in the BD drive
===PowerOFF #1===
Push 1 time "power off button". The red led of power button blinks for 1 or 2 minutes then the Ps3 turns off (can be long, wait calmly)
This can be considered a correct turn-off, in the next boot the firmware boots without problem
===PowerOFF #2===
Push "power off button" and keep it pressed. The red led doesnt blinks, after 1 or 2 minutes the PS3 turns-off suddenly (can be long, wait calmly)
This is not a correct turn-off, can generate corrupted files, and in the next boot the firmware can trigger one of the options in "recovery menu" automatically to repair the XMB database or the filesystem
===PowerOFF #3===
If nothing of the previous methods works... the last option is to disconnect the electricity power cord
This is the same case than the previous one, is not a correct turn-off
*Notes
Power-off button is connected to syscon. Is syscon who turns off the PS3, so this can be considered a "syscon crash" (in some way) because syscon is not responding correctly to the button
===Autocrash===
Nothing to do here, this happens automatically when booting a game or app, is the worst of all
===XMB database corruption===
This can be a consequence of some of the previous crashes, but also can be generated by adding manually content to the XMB (XMB database will try to make a copy of any file you make available to XMB, but this is not done in every boot to improve booting time... so there can be a mistmatch between what XMB database contains and what is displayed in XMB... also any corrupted or problematic files you use can be copyed to the database making the problem more annoying)
If the problematic file is not very important XMB can display a "corrupted icon" in his XMB position, but sometimes XMB doesnt know where is his position, this "corrupted icon" can be stuck forever, or the file is important enought to freeze XMB completly
To solve all the problems related with the "XMB database" or filesystem corruption, go to "recovery menu" and use the option "rebuild database"
Please note that all contributions to PS3 Developer wiki are considered to be released under the GNU Free Documentation License 1.2 (see PS3 Developer wiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following hCaptcha:

Cancel Editing help (opens in new window)