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 ==
== Bluescreen without any information ==
example: http://www.youtube.com/watch?v=gv72yI8851s
===Problem description===
===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).
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).
Line 157: Line 155:


*The most common cause of a firmware crash is a problem in the thread that is running (app or game)
*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...
**typicall 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]]
*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)
**Typicall when adding content manuallly in the hdd that needs to be managed by XMB (e.g: any content in XMB game category column)


Line 182: Line 180:


This is the same case than the previous one, is not a correct turn-off
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===
===Autocrash===
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)