RCO archive: Difference between revisions
Jump to navigation
Jump to search
Cfwprophet (talk | contribs) |
Cfwprophet (talk | contribs) |
||
| Line 510: | Line 510: | ||
==Other Usefull Links== | ==Other Usefull Links== | ||
So what of old but still handy [http:// | So what of old but still handy [http://www.filedropper.com/vag2wav VAG2WAV WAV2VAG Source] | ||
Revision as of 01:26, 17 September 2016
RCO
- The PS4 and Vita RCOs are the same with only one single difference: The PS4 ones are not zlib compressed.
- In PS4 the RCO's uses a cxml structure, with a header size of 0x50 and the magic identifyer RCOF
- RCOF header is 0x10 bytes bigger than any cxml header in PS3 (this means there are 2 new tables added for the new cxml variant used in vita rco's). And endianess changed
- Some of the extracted files are another variant of a cxml structure with identifyer RCSF. After a second extraction (with a cxml decompiler tool) the resulting file is a .xml containing only text strings (this double cxml method is used for .xml files that stores language translations)
| Offset | Size | Example | Name | Notes |
|---|---|---|---|---|
| CXML Header | ||||
| 0x00 | 0x04 | RCOF | Magic | |
| 0x04 | 0x04 | 10 01 00 00 | Version | |
| 0x08 | 0x04 | 50 00 00 00 | Tree absolute start offset, also header size | in PS3 = Tree absolute start offset |
| 0x0C | 0x04 | 2C 15 00 00 | Tree size | in PS3 = Tree size |
| 0x10 | 0x04 | 80 15 00 00 | ID STR table absolute start offset | in PS3 = ID table absolute start offset |
| 0x14 | 0x04 | B0 00 00 00 | ID STR table size | in PS3 = ID table size |
| 0x18 | 0x04 | 30 16 00 00 | ID INT table absolute start offset | in PS3 = Strings table absolute start offset |
| 0x1C | 0x04 | 98 00 00 00 | ID INT table size | in PS3 = Strings table size |
| 0x20 | 0x04 | D0 16 00 00 | Strings table absolute start offset | in PS3 = Integer array absolute start offset |
| 0x24 | 0x04 | F1 01 00 00 | Strings table size | in PS3 = Integer array size |
| 0x28 | 0x04 | D0 18 00 00 | overlapped (not used, but present in the header to keep the structure standards) | in PS3 = Float array absolute start offset |
| 0x2C | 0x04 | 00 00 00 00 | empty | in PS3 = Float array size |
| 0x30 | 0x04 | D0 18 00 00 | Styles ID INT table absolute start offset | in PS3 = File table absolute start offset |
| 0x34 | 0x04 | 34 00 00 00 | Styles ID INT table size | in PS3 = File table size |
| 0x38 | 0x04 | 10 19 00 00 | Integer array absolute start offset | in PS3 = Unknown area absolute start offset |
| 0x3C | 0x04 | 2C 00 00 00 | Integer array size | in PS3 = Unknown area size |
| 0x40 | 0x04 | 40 19 00 00 | Float array absolute start offset | in PS3 = Not present |
| 0x44 | 0x04 | 8C 00 00 00 | Float array size | in PS3 = Not present |
| 0x48 | 0x04 | D0 19 00 00 | File table absolute start offset | in PS3 = Not present |
| 0x4C | 0x04 | 60 89 00 00 | File table size | in PS3 = Not present |
| Tables | ||||
| 0x50 | Tree starts here | |||
Container Common Structure
RCOF
RCOF (Resources Container Flat?)
- Example from FW?? notification_settings_plugin.rco:
Offset(h) 00 01 02 03 04 05 06 07 00000000 52 43 4F 46 10 01 00 00 RCOF....
| Name | Offset | Size | Example | Remark |
|---|---|---|---|---|
| Magic | 0x00 | 0x04 | 52 43 4F 46 | 'RCOF' |
| Version | 0x04 | 0x04 | 00 00 01 10* | CXML version '1.10' |
* reversed little endian
Main Header
The header contains an identifier of the container (magic), his version, and allows to store the "absolute start offset" and "size" of 9 tables (or areas)
When a "not used table" is placed before a "used table"... the start offset of the "not used table" and his size (as zero) are stored in the main header to preserve his position in the structure. The "used table" that comes later starts in the same offset than the previously "not used table" (an intuitive way to think in this is imagining are overlapped because starts in the same position but only the one at the top is used)
- The container format is generic (used also by PS3 files like .RAF, .QRC and .P3T with some variations) so the usage of this tables can vary, in this example there is 1 "not used table":
- one of the "not used table" (at offset 0x18D0 with a size of 0) is placed before an used table (also at offset 0x18D0 but with a size of 0x34)
Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 00000000 52 43 4F 46 10 01 00 00 50 00 00 00 2C 15 00 00 RCOF....P...,... 00000010 80 15 00 00 B0 00 00 00 30 16 00 00 98 00 00 00 €...°...0...˜... 00000020 D0 16 00 00 F1 01 00 00 D0 18 00 00 00 00 00 00 Ð...ñ...Ð....... 00000030 D0 18 00 00 34 00 00 00 10 19 00 00 2C 00 00 00 Ð...4.......,... 00000040 40 19 00 00 8C 00 00 00 D0 19 00 00 60 89 00 00 @...Œ...Ð...`‰..
| Name | Offset | Size | Example | Remark |
|---|---|---|---|---|
| Magic | 0x00 | 0x04 | 52 43 4F 46 | 'RCOF' |
| Version | 0x04 | 0x04 | 00 00 01 10* | CXML version '1.10' |
| Tree Table Offset | 0x08 | 0x04 | 00 00 00 50* | |
| Tree Table Size | 0x0C | 0x04 | 00 00 15 2C* | |
| ID String Table Offset | 0x10 | 0x04 | 00 00 15 80* | |
| ID String Table Size | 0x14 | 0x04 | 00 00 00 B0* | |
| ID Integer Table Offset | 0x18 | 0x04 | 00 00 16 30* | |
| ID Integer Table Size | 0x1C | 0x04 | 00 00 00 98* | |
| String Table Offset | 0x20 | 0x04 | 00 00 16 D0* | |
| String Table size | 0x24 | 0x04 | 00 00 01 F1* | |
| overlapped | 0x28 | 0x04 | 00 00 18 D0* | Overlapped |
| empty | 0x2C | 0x04 | 00 00 00 00 | Not used |
| Styles ID Integer Table Offset | 0x30 | 0x04 | 00 00 18 D0* | |
| Styles ID Integer Table Size | 0x34 | 0x04 | 00 00 00 34* | |
| Integer Array Table Offset | 0x38 | 0x04 | 00 00 19 10* | |
| Integer Array Table Size | 0x3C | 0x04 | 00 00 00 2C* | |
| Float Array Table Offset | 0x38 | 0x04 | 00 00 19 40* | |
| Float Array Table Size | 0x3C | 0x04 | 00 00 00 8C* | |
| File Table Offset | 0x38 | 0x04 | 00 00 19 D0* | |
| File Table Size | 0x3C | 0x04 | 00 00 89 60* |
* reversed little endian
- Notes
- The sizes doesn't includes the (possible) padding at the end of all tables
Tree Table
from notification_settings_plugin.rco FW??
| Offset | Size | Example | Remark |
|---|---|---|---|
| 0x00 | 0x04 | 00 00 00 00 | Root Element (Offset within String Table, in this case it will be <resource>) |
| 0x04 | 0x04 | 00 00 00 02 | Attribute Counter |
| 0x08 | 0x04 | FF FF FF FF | Parent |
| 0x0C | 0x04 | FF FF FF FF | Previous Brother |
| 0x10 | 0x04 | FF FF FF FF | Next Brother |
| 0x14 | 0x04 | 00 00 00 3C | First Child within the root Element <resource> (which will also our Next Child Element to read) |
| 0x18 | 0x04 | 00 00 0D 74 | Last Child within the root Element <resource> (which will also our Next Child Element to read) |
| 0x1C | 0x04 | 00 00 00 09 | String Pointer (Offset within String Table, in this case it will be "version") |
| 0x20 | 0x04 | 00 00 00 02 | Type descriptor (2 == Float) |
| 0x24 | 0x04 | 3D CC CC CD | Float value (0.1) [version="0.1"] |
| 0x28 | 0x04 | 00 00 00 00 | empty value |
| 0x2C | 0x04 | 00 00 00 11 | String Pointer (in this case "type") |
| 0x30 | 0x04 | 00 00 00 03 | Type descriptor (3 == String) |
| 0x34 | 0x04 | 00 00 00 16 | Offset within String Table of String to read |
| 0x38 | 0x04 | 00 00 00 06 | Length of String to read (0x06 == "normal") [type="normal"] |
| 0x3C | 0x04 | 00 00 00 1D | Next Element (Offset within String Table, in this case it will be <stringtable>) |
| 0x40 | 0x04 | 00 00 00 00 | Attribute Count |
| 0x44 | 0x04 | 00 00 00 00 | Parent (Offset within XML Table, pointing to Root Element) |
| 0x48 | 0x04 | FF FF FF FF | Previous Brother |
| 0x4C | 0x04 | 00 00 07 88 | Next Brother |
| 0x50 | 0x04 | 00 00 00 58 | First Child |
| 0x54 | 0x04 | 00 00 07 2C | Last Child |
| 0x58 | 0x04 | 00 00 00 29 | String Pointer (in this case <local>) |
| 0x5C | 0x04 | 00 00 00 04 | Attribute Count |
| 0x60 | 0x04 | 00 00 00 3C | Parrent <stringtable> |
| 0x64 | 0x04 | FF FF FF FF | Previous Brother |
| 0x68 | 0x04 | 00 00 00 B4 | Next Brother |
| 0x6C | 0x04 | FF FF FF FF | First Child |
| 0x70 | 0x04 | FF FF FF FF | Last Child |
| 0x74 | 0x04 | 00 00 00 30 | String Pointer (in this case origsize="") |
| 0x78 | 0x04 | 00 00 00 01 | Attribute identifyer (in this case 1 so a integer value) |
| 0x7C | 0x04 | 00 00 04 10 | Hex integer size (1040 bytes when converted so origsize="1045") |
| 0x80 | 0x04 | 00 00 00 00 | empty value |
| 0x84 | 0x04 | 00 00 00 39 | String Pointer (in this case src="") |
| 0x88 | 0x04 | 00 00 00 08 | Attribute identifyer (in this case 8 so a file) |
| 0x8C | 0x04 | 00 00 00 00 | Offset within File Table |
| 0x90 | 0x04 | 00 00 01 BA | Size of file to read |
| 0x94 | 0x04 | 00 00 00 3D | String Pointer (in this case compress="") |
| 0x98 | 0x04 | 00 00 00 03 | Attribute identifyer (in this case 3 so a string) |
| 0x9C | 0x04 | 00 00 00 46 | Offset of the string to read within String Table |
| 0xA0 | 0x04 | 00 00 00 02 | Size of the string to read (in this case will be 'on' so compress="on") |
| 0xA4 | 0x04 | 00 00 00 49 | String Pointer (in this case id="") |
| 0xA8 | 0x04 | 00 00 00 09 | Attribute identifyer (in this case 9 so a ID String with Loopback offset) |
| 0xAC | 0x04 | 00 00 00 00 | Offset of the id to read within ID String Table (in this case 'ja' so id="ja" and after the loopback src="/xmls/ja.xml") |
| 0xB0 | 0x04 | 00 00 00 00 | empty value |
- Note: the folder string within the src="" Attribute is a custom one which need to be handled by the app or which is dependend to the developer who will write the CXML Tool (so me)
- Note2: All values are reversed little endian
Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 00000000 00 00 00 00 02 00 00 00 FF FF FF FF FF FF FF FF ........ÿÿÿÿÿÿÿÿ 00000010 FF FF FF FF 3C 00 00 00 74 0D 00 00 09 00 00 00 ÿÿÿÿ<...t....... 00000020 02 00 00 00 CD CC CC 3D 00 00 00 00 11 00 00 00 ....ÍÌÌ=........ 00000030 03 00 00 00 16 00 00 00 06 00 00 00 1D 00 00 00 ................ 00000040 00 00 00 00 00 00 00 00 FF FF FF FF 88 07 00 00 ........ÿÿÿÿˆ... 00000050 58 00 00 00 2C 07 00 00 29 00 00 00 04 00 00 00 X...,...)....... 00000060 3C 00 00 00 FF FF FF FF B4 00 00 00 FF FF FF FF <...ÿÿÿÿ´...ÿÿÿÿ 00000070 FF FF FF FF 30 00 00 00 01 00 00 00 10 04 00 00 ÿÿÿÿ0........... 00000080 00 00 00 00 39 00 00 00 08 00 00 00 00 00 00 00 ....9........... 00000090 BA 01 00 00 3D 00 00 00 03 00 00 00 46 00 00 00 º...=.......F... 000000A0 02 00 00 00 49 00 00 00 09 00 00 00 00 00 00 00 ....I........... 000000B0 00 00 00 00 ....
String Table
from notification_settings_plugin.rco FW?? This area is composed by a consecutive list of all the tags (elements or attributes) from the xml that was used to create the container. Are stored "from-top-to-bottom" in the exact same order that they was ordered in the xml (althougth it looks in some cases the theme compiler reorders them to his convenience). This list doesn't makes differences of the "directory hierarchy" of the tags neither is specified if the tag is an element or an attribute (this parent-child hierarchy is defined in other place of the container by making references to this area by using "byte counters" to locate a tag)
Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 00000000 72 65 73 6F 75 72 63 65 00 76 65 72 73 69 6F 6E resource.version 00000010 00 74 79 70 65 00 6E 6F 72 6D 61 6C 00 73 74 72 .type.normal.str 00000020 69 6E 67 74 61 62 6C 65 00 6C 6F 63 61 6C 65 00 ingtable.locale. 00000030 6F 72 69 67 73 69 7A 65 00 73 72 63 00 63 6F 6D origsize.src.com 00000040 70 72 65 73 73 00 6F 6E 00 69 64 00 74 65 78 74 press.on.id.text 00000050 75 72 65 74 61 62 6C 65 00 74 65 78 74 75 72 65 uretable.texture 00000060 00 74 65 78 74 75 72 65 2F 67 69 6D 00 64 69 76 .texture/gim.div 00000070 5F 72 61 74 69 6F 5F 68 00 6D 61 72 67 69 6E 5F _ratio_h.margin_ 00000080 76 00 6D 61 72 67 69 6E 5F 68 00 64 69 76 5F 6D v.margin_h.div_m 00000090 6F 64 65 00 33 78 31 00 73 74 79 6C 65 74 61 62 ode.3x1.staletab 000000A0 6C 65 00 73 74 79 6C 65 5F 62 75 74 74 6F 6E 00 le.style_button. 000000B0 62 67 5F 6F 62 6A 00 67 6C 6F 77 5F 6F 62 6A 00 bg_ogj.glow_obj. 000000C0 70 6C 61 6E 65 6F 62 6A 00 74 65 78 74 75 72 65 planeobj.texture 000000D0 30 00 62 6C 65 6E 64 00 73 74 79 6C 65 5F 74 65 0.blend.style_te 000000E0 78 74 00 74 65 78 74 6F 62 6A 00 66 6F 6E 74 5F xt.textobj.font_ 000000F0 73 69 7A 65 00 62 6F 6C 64 00 63 6F 6C 6F 72 00 size.bold.color. 00000100 6D 61 78 5F 6C 69 6E 65 5F 63 6F 75 6E 74 00 6C max_line_count.l 00000110 69 6E 65 5F 70 69 74 63 68 00 77 6F 72 64 5F 77 ine_pitch.word_w 00000120 72 61 70 00 65 6C 6C 69 70 73 69 73 00 73 74 79 rap.ellipsis.sty 00000130 6C 65 5F 70 6C 61 6E 65 00 70 61 67 65 74 61 62 le_plane.pagetab 00000140 6C 65 00 74 65 6D 70 6C 61 74 65 74 61 62 6C 65 le.templatetable 00000150 00 74 65 6D 70 6C 61 74 65 00 66 69 6C 65 5F 6C .template.file_l 00000160 69 73 74 00 73 74 79 6C 65 00 6C 61 79 6F 75 74 ist.style.layout 00000170 5F 68 69 6E 74 00 61 6C 69 67 6E 00 73 69 7A 65 hint.align.size. 00000180 00 70 6F 73 00 66 61 73 74 5F 6F 70 65 6E 00 6C .pos.fast_open.l 00000190 69 73 74 5F 69 74 65 6D 00 74 65 78 74 00 61 64 ist_item.text.ad 000001A0 6A 75 73 74 00 70 6C 61 6E 65 00 61 6C 70 68 61 just.plane.alpha 000001B0 00 61 6E 63 68 6F 72 00 63 68 65 63 6B 5F 62 6F .anchor.check_bo 000001C0 78 00 66 6F 63 75 73 5F 68 69 6E 74 00 66 6F 63 x.focus_hint.foc 000001D0 75 73 5F 73 68 61 70 65 00 66 6F 63 75 73 5F 73 us_shape.focus_s 000001E0 69 7A 65 00 62 75 74 74 6F 6E 00 73 6F 75 6E 64 ize.button.sound 000001F0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
- Notes:
- yellow: used bytes
- red: padding to align to 0x10 bytes
- The integer values and text strings of some attributes tags from the xml (e.g: "themename=mytheme", or "fontcolor=2") are stored in this area too at the right of his tag, the presence of an integer value displaces the next tag (this only happens in themes and rafs, not in QRC, RCO files so is added here as a note but is very important for the structure of the other containers when using "byte counters" to locate the tags)
ID Table
In a PS4 RCO we have 3 diffrent ID Tables which we will take a deeper look now.
The loopback offset is market as red.
The id is marked as yellow.
- Note: All loopback offset are reversed little endian.
ID String
from notification_settings_plugin.rco FW??
Is a Table that only hold Strings and will be readed till the first 0x00 byte and then stop. The first 4 bytes before the string are the loopback offset to add the id string to the src="" Attribute value.
- Note: If all loopback offset's are used depends on the used Attribute identifyer (9-will use loopback- or A-will not use loopback-). But for string's they will always loopback
Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 00000000 00 00 00 58 6A 61 00 00 00 00 00 B4 65 6E 2D 67 X...ja..´...en-g 00000010 62 00 00 00 00 00 01 10 65 6E 00 00 00 00 01 6C b.......en..l... 00000020 66 72 00 00 00 00 01 C8 65 73 00 00 00 00 02 24 fr..È...es..$... 00000030 64 65 00 00 00 00 02 80 69 74 00 00 00 00 02 DC de..€...it..Ü... 00000040 6E 6C 00 00 00 00 03 38 70 74 2D 62 72 00 00 00 nl..8...pt-br... 00000050 00 00 03 94 70 74 00 00 00 00 03 F0 72 75 00 00 ”...pt..ð...ru.. 00000060 00 00 04 4C 6B 6F 00 00 00 00 04 A8 7A 68 2D 74 L...ko..¨...zh-t 00000070 00 00 00 00 00 00 05 04 7A 68 2D 73 00 00 00 00 ........zh-s.... 00000080 00 00 05 60 66 69 00 00 00 00 05 BC 73 76 00 00 `...fi..¼...sv.. 00000090 00 00 06 18 64 61 00 00 00 00 06 74 6E 6F 00 00 ....da..t...no.. 000000A0 00 00 06 D0 70 6C 00 00 00 00 07 2C 74 72 00 00 Ð...pl..,...tr..
ID Integer
from notification_settings_plugin.rco FW??
Is a Table that only hold Integer values. The values to read are always size of 4 so seems to be an little endian. The first 4 bytes before the Integer value are the loopback offset to add the id int value to the src="" Attribute value.
- Note: All values are reversed little endian
- Note2: Not all loopback offset's are used, that depends on the used Attribute identifyer (B-will use loopback- or C-will not use loopback-)
Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 00000000 00 00 07 A4 1D DD 0E 08 00 00 08 10 21 33 CE EB ...¤.Ý......!3Îë 00000010 00 00 08 7C F7 98 83 12 00 00 08 E8 6F 57 E2 51 ...|÷˜ƒ....èoWâQ 00000020 00 00 09 54 86 64 5D 41 00 00 09 C0 29 B9 1F 26 ...T†d]A...À)¹.& 00000030 00 00 0A 6C D0 A2 72 A1 00 00 0B 34 2F 65 20 05 ...lТr¡...4/e.. 00000040 00 00 0C 08 3C 28 8E E9 00 00 0C E0 C7 2C F1 D7 ....<(Žé...àÇ,ñ× 00000050 FF FF FF FF 18 45 D1 0D 00 00 0D 90 3F 18 74 91 ÿÿÿÿ.EÑ.....?.t‘ 00000060 FF FF FF FF 70 38 36 4B 00 00 0E 54 AF 37 FB 60 ÿÿÿÿp86K...T¯7û` 00000070 FF FF FF FF F3 48 8F 99 FF FF FF FF 5F 7B 33 2B ÿÿÿÿóH.™ÿÿÿÿ_{3+ 00000080 FF FF FF FF 9F 20 F8 98 00 00 11 6C E8 0C 86 23 ÿÿÿÿŸ.ø˜...lè.†# 00000090 FF FF FF FF 20 41 32 74 ÿÿÿÿ.A2t
ID Style
from notification_settings_plugin.rco FW??
Is a Table that only hold Integer values. The values to read are always size of 4 so seems to be an little endian. There are no loopback offset's within this table and one integer value is placed after another without any padding. Additional are thoes value's only used for the Attribute Tag id="" from the <styletable> Element.
- Note: All values are reversed little endian
Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 00000000 9C 96 91 8B 22 FF 88 BD 01 F8 75 B1 E9 5F 16 28 œ–‘‹"ÿˆ½�øu±é_.( 00000010 38 B6 2B E4 0A 2F 2C D9 63 67 8F EE 2F BC DE AE 8¶+ä./,Ùcg.î/¼Þ® 00000020 DA 39 A3 EE 20 2F 57 0C 86 D6 DE 69 22 43 90 D9 Ú9£î./W.†ÖÞi"C.Ù 00000030 DD 31 50 3B Ý1P;
Integer Array
from notification_settings_plugin.rco FW??
This Array hold integer values. It is little endian alligned. That means for one integer value we have to read 4 bytes. This need also to be respected for the Offset and Length to read. Like if the given offset is 9 then we can say 9 * 4(bytes) == offset 0x24. We start to read on offset 0x24. Also we have to use the same calculation for the given values to read, if length is 2 then we calc 2 * 4(bytes) == 8 bytes to read where a union of 4 bytes is one single integer value.
*To complete our example: given offset to read from = 9 ~ 0x24, given length of value = 2 ~ 0x08 == 0x00000002 & 0x00000000 =~ attribute="2, 0"
*Note: All values are reversed little endian
Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 00000000 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 01 00000010 00 00 00 04 00 00 00 00 00 00 00 02 00 00 00 01 00000020 00 00 00 05 00 00 00 02 00 00 00 00
Float Array
from notification_settings_plugin.rco FW??
This Array hold single float values. In case of a single float value consit's of 4 bytes we need to use the same calculation then for the Integer Array.
* As example: Given offset * 4 == Offset within float Array to start to read from. Given value length * 4 == length to read from the float Array. Where a union of 4 bytes is one single float value.
*Note: All values are reversed little endian (hex values!!)
Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F Converted Float's 01 02 03 04 00000000 3E FA E1 48 3F 80 00 00 3F 80 00 00 3F 80 00 00 00000000 0,49 1 1 1 00000010 3F 80 00 00 44 70 00 00 43 E0 00 00 00 00 00 00 00000010 1 960 448 0 00000020 00 00 00 00 44 52 00 00 42 A0 00 00 43 E7 00 00 00000020 0 840 80 462 00000030 00 00 00 00 C3 88 00 00 00 00 00 00 C1 F0 00 00 00000030 0 -272 0 -30 00000040 00 00 00 00 42 70 00 00 42 70 00 00 42 38 00 00 00000040 0 60 60 46 00000050 42 38 00 00 44 16 80 00 00 00 00 00 42 3C 00 00 00000050 46 602 0 47 00000060 42 3C 00 00 44 70 00 00 42 A0 00 00 43 C7 00 00 00000060 47 960 80 398 00000070 00 00 00 00 C3 4E 00 00 00 00 00 00 C2 20 00 00 00000070 0 -206 0 -40 00000080 00 00 00 00 43 A5 00 00 00 00 00 00 00000080 0 330 0
File Table
The files are concatenated in the same order than in the Tree Table & ID's Table (ID String & Integer). The xml's are stored as CXML Container's as well. Additional will a PS4 RCO hold the most common file format's that Sony allready used in the past for resource files. Which are as follow: VAG, GTF, DDS, GIM
Summary
How all the Tables work together you can check below on a example from the HeavyRain.p3t PS3 Theme:
* Don't worry that it is a PS3 Theme. The work down of the CXML is the same like for a PS4 RCO
Table Description
Tree Table of HeavyRain.p3t ID Table of HeavyRain.p3t Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 00000050 [...] 00 00 00 15 00 00 00 03 00 00 00 1D ............ 00000000 00 00 01 24 65 6E 00 00 00 01 60 6A 70 00 00 00 ...$en....`jp... 00000060 00 00 00 06 00 00 00 24 00 00 00 01 00 07 E9 80 .......$......é€ 00000010 01 C8 69 63 6F 6E 5F 75 73 65 72 00 00 00 02 14 .Èicon_user..... 00000070 00 00 00 00 00 00 00 30 00 00 00 03 00 00 00 35 .......0.......5 00000020 69 63 6F 6E 5F 73 65 74 74 69 6E 67 00 00 00 02 icon_setting.... 00000080 00 00 00 10 00 00 00 46 00 00 00 03 00 00 00 4D .......F.......M 00000030 60 69 63 6F 6E 5F 70 68 6F 74 6F 00 00 00 02 AC `icon_photo....¬ 00000090 00 00 00 0C 00 00 00 5A 00 00 00 03 00 00 00 5E .......Z.......^ 00000040 69 63 6F 6E 5F 6D 75 73 69 63 00 00 00 02 F8 69 icon_music....øi 000000A0 00 00 00 1B 00 00 00 7A 00 00 00 01 00 00 40 80 .......z......@€ 00000050 63 6F 6E 5F 76 69 64 65 6F 00 00 00 03 44 69 63 con_video....Dic 000000B0 00 00 00 00 00 00 00 89 00 00 00 06 00 00 00 00 .......‰........ 00000060 6F 6E 5F 67 61 6D 65 00 [...] on_game [...] 000000C0 00 00 1A 0B 00 00 00 94 00 00 00 01 00 00 40 80 .......”......@€ 000000D0 00 00 00 00 00 00 00 9D 00 00 00 03 00 00 00 A5 ...............¥ String Table of HeavyRain.p3t 000000E0 00 00 00 0B 00 00 00 B1 00 00 00 03 00 00 00 B7 .......±.......· 000000F0 00 00 00 0E 00 00 00 C6 00 00 00 03 00 00 00 CC .......Æ.......Ì Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 00000100 00 00 00 06 00 00 00 D3 00 00 00 06 00 00 1A 10 .......Ó........ 00000000 74 68 65 6D 65 00 69 6E 66 6F 74 61 62 6C 65 00 theme.infotable. 00000110 00 02 12 99 00 00 00 DB 00 00 00 06 00 02 2C B0 ...™...Û......,° 00000010 69 6E 66 6F 00 63 6F 6D 6D 65 6E 74 00 45 6E 6A info.comment.Enj 00000120 00 00 1F CE 00 00 00 E0 00 00 00 02 00 00 00 1C ...Î...à........ 00000020 6F 79 2E 00 70 72 65 76 69 65 77 73 69 7A 65 00 oy..previewsize. 00000130 00 00 00 38 00 00 01 60 FF FF FF FF FF FF FF FF ...8...`ÿÿÿÿÿÿÿÿ 00000030 6E 61 6D 65 00 48 45 41 56 59 20 52 61 69 6E 20 name.HEAVY.Rain. 00000140 00 00 00 EE 00 00 00 07 00 00 00 00 00 00 00 00 ...î............ 00000040 74 68 65 6D 65 00 61 75 74 68 6F 72 00 51 75 61 theme.author.Qua 00000150 00 00 00 30 00 00 00 03 00 00 00 35 00 00 00 10 ...0.......5.... 00000050 6E 74 69 63 44 72 65 61 6D 00 75 72 6C 00 68 74 nticDream.url.ht 00000160 00 00 00 E0 00 00 00 03 00 00 00 1C 00 00 01 24 ...à...........$ 00000060 74 70 3A 2F 2F 77 77 77 2E 71 75 61 6E 74 69 63 tp://www.quantic 00000170 FF FF FF FF FF FF FF FF FF FF FF FF 00 00 00 EE ÿÿÿÿÿÿÿÿÿÿÿÿ...î 00000070 64 72 65 61 6D 2E 63 6F 6D 00 61 75 74 68 6F 72 dream.com.author 00000180 00 00 00 07 00 00 00 07 00 00 00 00 00 00 00 15 ................ 00000080 69 63 6F 6E 73 69 7A 65 00 61 75 74 68 6F 72 69 iconsize.authori 00000190 00 00 00 03 00 00 00 F5 00 00 00 33 00 00 00 30 .......õ...3...0 00000090 63 6F 6E 00 69 63 6F 6E 73 69 7A 65 00 76 65 72 con.iconsize.ver 000001A0 00 00 00 03 00 00 00 35 00 00 00 10 00 00 01 29 .......5.......) 000000A0 73 69 6F 6E 00 76 65 72 73 69 6F 6E 20 31 2E 30 sion.version.1.0 000000B0 00 6D 74 69 6D 65 00 32 30 30 39 31 30 33 30 31 .mtime.200910301 000000C0 36 31 33 34 33 00 67 65 6E 72 65 00 6F 74 68 65 61343.genre.othe 000000D0 72 73 00 70 72 65 76 69 65 77 00 69 63 6F 6E 00 re.preview.icon. 000000E0 6C 6F 63 61 6C 69 7A 65 64 69 6E 66 6F 00 6C 6F localizedinfo.lo 000000F0 63 61 6C 65 00 E3 81 93 E3 82 8C E3 81 AF E3 82 cale.ã“ã‚Œã¯ã‚ 00000100 B5 E3 83 B3 E3 83 97 E3 83 AB E3 83 86 E3 83 BC µãƒ³ãƒ—ルテー 00000110 E3 83 9E E3 83 95 E3 82 A1 E3 82 A4 E3 83 AB E3 マファイルã 00000120 81 A7 E3 81 99 E3 80 82 00 69 63 6F 6E 74 61 62 §ã™ã€‚.icontab 00000130 6C 65 00 73 72 63 00 69 64 00 73 69 7A 65 00 70 le.src.id.size.p 00000140 6F 69 6E 74 65 72 74 61 62 6C 65 00 70 6F 69 6E ointertable.poin 00000150 74 65 72 00 62 61 73 65 5F [...] ter.base_ [...]
String Pointer Points to a Offset within String Table which represents a string (in this case a Attribute <comment>) Previous Element Typ Descriptor A Integer value which describe the Typ of the Attribute (3 == String) Next Element String Offset A Integer value which describe the Offset of a String within String Table First Entry Length of String A Integer value which describe the Length of the String to read from String Table Last Entry String Pointer -"- (in this case a Attribute <previewsize>) String Pointer -"- (in this case a Attribute <local>) Typ Descriptor A Integer value which describe the Typ of the Attribute (1 == Integer) Typ Descriptor -"- (7 == ID) Integer Hex Value A Integer Value which describe the size of the icon "preview" ID Offset String Pointer -"- (in this case a Attribute <name>) String Pointer -"- (in this case a Attribute <name>) Typ Descriptor -"- (3 == String) Typ Descriptor -"- (3 == String) String Offset String Offset Length of String Length of String String Pointer -"- (in this case a Attribute <author>) String Pointer -"- (in this case a Element <localizedinfo>) Typ Descriptor -"- (3 == String) Attribute Counter (0x03 == 3) String Offset Parent Length of String Previous Element String Pointer -"- (in this case a Attribute <url> Next Element Typ Descriptor -"- (3 == String)) First Entry String Offset Last Entry Length of String String Pointer -"- (in this case a Attribute <local>) String Pointer -"- (in this case a Attribute <authoriconsize>) Typ Descriptor -"- (7 == ID) Typ Descriptor -"- (1 == Integer) ID Offset Integer Hex Value -"- "authoriconsize" String Pointer -"- (in this case a Attribute <comment>) String Pointer -"- (in this case a Attribute <authoricon>) Typ Descriptor -"- (3 == String) Typ Descriptor -"- (6 == File) String Offset Offset of Filedata Length of String Size of Filedata String Pointer -"- (in this case a Attribute <name>) [...] this repeats till the last Attribute. I will describe on the right side the <localizedinfo> Elements. So we jump back in on Offset 0x124 [...] String Pointer -"- (in this case a Element <localizedinfo>) Typ Descriptor -"- (3 == String) Attribute Counter (0x02 == 2) String Offset Parent Length of String
Other Usefull Links
So what of old but still handy VAG2WAV WAV2VAG Source