Talk:More System Information: Difference between revisions
Strike Venom (talk | contribs) |
m (superbrick notes) |
||
| Line 31: | Line 31: | ||
The SoftID versions are ordered chronologically, and are dependant of this hardware revisions of syscon. As an example the chronologicall order of SoftID availables for CXR713120-201GB is 0B67--->0B8E--->0C16--->0D52--->0DBF--->0E69. After this SoftID the increasing numeration stops. In the next hardware revision of syscon (SW-30x series) the SoftID starts in 065D (is smaller than the previous series)... is not clear if this series continues with SW2-30x and later with SW3-30x because the numbers matches but the syscon hardware is a different series | The SoftID versions are ordered chronologically, and are dependant of this hardware revisions of syscon. As an example the chronologicall order of SoftID availables for CXR713120-201GB is 0B67--->0B8E--->0C16--->0D52--->0DBF--->0E69. After this SoftID the increasing numeration stops. In the next hardware revision of syscon (SW-30x series) the SoftID starts in 065D (is smaller than the previous series)... is not clear if this series continues with SW2-30x and later with SW3-30x because the numbers matches but the syscon hardware is a different series | ||
The value used in SoftID is not an identifyer of syscon hardware itself, actually each syscon has several SoftiID compatibles (but this doesnt means that all the compatible versions can be installed because the | The value used in SoftID is not an identifyer of syscon hardware itself, actually each syscon has several SoftiID compatibles (but this doesnt means that all the compatible versions can be installed because the syscon firmware contains code to initialize/manage/communicate with other components of the motherboard as cell, southbridge, starship?, sata/pata adaptor?, etc...). In the case of a syscon firmware installed in a compatible syscon but with an incorrect SoftID some components of the motherboard can stop working, the whole system unable to boot or permanently bricked | ||
===Example tables (please help to fill it)=== | ===Example tables (please help to fill it)=== | ||
Revision as of 06:14, 22 November 2012
Screenshot examples
- FW 3.55 with strings spoofed to "True Blue v2.4"
- FW 3.41ofw CECH-25xx example
- FW 3.55 example
- FW CECHJ04 3.55 example
- FW 3.55 CECHG example
- FW 3.55 (DEX) DevelopmentTool
- FW 3.56 example
- FW 3.56 Demonhades example
- FW 3.65 example
- FW 4.00 example
- FW 4.00 example
- FW 4.00 example (SHOP)
- FW 4.00 example (DEX)
- FW 3.41+ example (CEX)
- FW 4.11 ofw example (CEX)
- FW 4.11 ofw example CECHAxx or CECHBxx
Syscon string format speculation
There are motherboards with 4.00 firmware with a string filled with zeroes after the "." (0000000000000000). This zeroes means that his SoftID includes all the needed patches (in other words... 4.00ofw contains no patches aplicables to this syscon)
There is a direct relationship between the numbers used in the names of the .pkg's and the info shown after the "." e.g: SYS_CON_FIRMWARE_01040402.pkg will be shown in screen as: 0E69.0001000400040002 (to convert the string just add a zeroed byte before every byte)
Based in the numbers used in the patches them can be ordered in a timeline from "older to newer": 0100****.pkg 0101****.pkg 0102****.pkg 0103****.pkg 0104****.pkg 0105****.pkg (there are only patches for 6 different syscons in 4.00 firmware, but probably there are more syscon generations used in newer motherboards that doesn't need patches yet)
The only patch that doesn't follow this rules is SYS_CON_FIRMWARE_S1_00010002083E0832.pkg whose numbers string doesn't need conversion, but it keeps the format 00010002******** (its unknown why this patch is speciall, and if it uses a different install method than the others)
Note there are only 5 syscon hardware series known in this order: CXR713F120A, CXR713120-201GB, SW-30x, SW2-30x, and SW3-30x
The SoftID versions are ordered chronologically, and are dependant of this hardware revisions of syscon. As an example the chronologicall order of SoftID availables for CXR713120-201GB is 0B67--->0B8E--->0C16--->0D52--->0DBF--->0E69. After this SoftID the increasing numeration stops. In the next hardware revision of syscon (SW-30x series) the SoftID starts in 065D (is smaller than the previous series)... is not clear if this series continues with SW2-30x and later with SW3-30x because the numbers matches but the syscon hardware is a different series
The value used in SoftID is not an identifyer of syscon hardware itself, actually each syscon has several SoftiID compatibles (but this doesnt means that all the compatible versions can be installed because the syscon firmware contains code to initialize/manage/communicate with other components of the motherboard as cell, southbridge, starship?, sata/pata adaptor?, etc...). In the case of a syscon firmware installed in a compatible syscon but with an incorrect SoftID some components of the motherboard can stop working, the whole system unable to boot or permanently bricked
Example tables (please help to fill it)
| PS3 Model | Syscon serial | Bigger firmware installed | SoftID.SysconPatch@SC | Syscon software generation | syscon patch installed | Notes |
|---|---|---|---|---|---|---|
| DECR-1000/1000A | CXR713F120A | 4.30 (CP ver 1.33) | 03FB.0000000000000000@SC | generation 0 | v1.0.5c1_TMU510_u.bin | Updated through CP updates, no patches, full firmware overwritten |
| DEH-H1000A(S)(-E(S)) | 4.30 | 0B67.0000000000000000@SC | generation 0 | - | No patches available | |
| DEH-H1001-D | 4.30 | 0B67.0000000000000000@SC | generation 0 | - | No patches available | |
| CECHAxx | CXR713120-201GB | 3.41+ | 0B8E.0001000000000006@SC | generation 1 | 01000006.pkg | |
| CECHBxx | ???? | 0B8E.XXXXXXXXXXXXXXXX@SC | generation 1 | ???? | probably generation 1 | |
| CECHCxx | 3.15 | 0C16.0001000100030002@SC | generation 2 | 01010302.pkg | Old patch because never updated over 3.40 | |
| CECHCxx | 3.55 | 0C16.0001000100030003@SC | generation 2 | 01010303.pkg | ||
| CECHCxx | 3.70 | 0C16.0001000100030003@SC | generation 2 | 01010303.pkg | ||
| CECHGxx | 3.55 | 0D52.0001000200030002@SC | generation 3 | 01020302.pkg | ||
| CECHHxx | 3.60 | 0DBF.0001000300030002@SC | generation 4 | 01030302.pkg | ||
| CECHHxx | 4.00 | 0DBF.0001000300030002@SC | generation 4 | 01030302.pkg | ||
| DECR-1400/1400A | 4.30 | 0E69.0001000400040001@SC | generation 5 | n/a | Never updated (no existing patches for the target) | |
| CECHJxx | 3.55 | 0E69.0001000400040002@SC | generation 5 | 01040402.pkg | ||
| CECHKxx | 3.55 | 0E69.0001000400040002@SC | generation 5 | 01040402.pkg | ||
| CECHLxx | SW-30x | 3.65 | 065D.0000000000000000@SC | generation 8? | No patches installed | generation needs comfirmation |
| CECHPxx | 4.00 | 065D.0000000000000000@SC | generation 8? | No patches installed | generation needs comfirmation | |
| CECHQxx | 4.00 | 065D.0000000000000000@SC | generation 8? | No patches installed | generation needs comfirmation | |
| CECH-20xx | SW2-30x | 4.00 | 0832.00010002083E0832@SC | generation 9? | 00010002083E0832.pkg | First model of slim with fat components |
| CECH-21xx | ???? | ???? | ???? | ???? | Needed example | |
| CECH-25xx | 3.41 | 08C2.0000000000000000@SC | generation 10? | No patches installed | generation needs comfirmation | |
| CECH-25xx | 4.00 | 08C2.0000000000000000@SC | generation 10? | No patches installed | generation needs comfirmation | |
| CECH-30xx | 4.00 | 0918.0000000000000000@SC | generation 11? | No patches installed | generation needs comfirmation | |
| CECH-40xx | SW3-30x | ????? |
i think that this will explain everything: http://pastebin.com/k8KHGkzB and these are the generation of the SC http://pastebin.com/aJ3gxRKx (probably the first group is the correct one).
03FB -> 001111111011 0B67 -> 101101100111 0B8E -> 101110001110 0C16 -> 110000010110 0D52 -> 110101010010 0DBF -> 110110111111 0E69 -> 111001101001 065D -> 011001011101 0832 -> 100000110010 08C2 -> 100011000010 0918 -> 100100011000
Deroad 19:06, 21 November 2012 (MSK)