Talk:Resource Container (RCO)
RCO versioning
All RCO files contains a version number, the version increases with bigger firmwares but not for every firmware and is not directly associated with it. The same versioning sequence is used in PSP and PS3 RCO's
It seems all the RCO's of a specific firmware shares the same version (verifyed for firmware 4.76, all 4.76 .rco's are minFirmwareVer="unknownId0x130"). It seems to be the version of the "rco set", or the version of the "rco tool" used to compile the whole "rco set"
Is posible to create a correspondecy between the "rco set" version and the firmwares versions where a specific "rco set" version was used. RCOmage v1.1.1 (latest stable) identifyes the version with a list of hardcoded values associated with a "system firmware version"
Code Sample
After extracting the contents of the RCO with RCOmage, the "rco set" version is stored for rebuilding purposes in the RCOXML descriptor file as an attribute with the name minFirmwareVer
If the version is unknown is stored as unknownId0x%x using unknownId to specify the fact that is unknown + the real hex value 0x%x
Example... sysconf_plugin.rco from PS3 firmware 2.00 with "rco set" version 0x106
Code Sample
Speculation
There is no known formula to make a direct conversion from the hex value to the system firmware... speculative ideas post here
RCO versions
| RCO version | Firmware | Release date | Notes |
|---|---|---|---|
| 0x55 |  0.6.5 |
pre-retail | archaic rco format, header is 12 bytes smaller |
| 0x70 | 1.00 |
2004 / 12 / 12 | |
| 0x71 | 1.50~2.50 |
2005 / 3 / 24 | normal table section up to this version |
| 0x90 | 2.60 |
2005 / 11 / 29 | zlib compressed table section implemented |
| 0x95 | 2.70~2.71 |
2006 / 4 / 25 | rlz compressed table section implemented |
| 0x96 | 2.80~3.40 |
2006 / 7 / 27 | |
| 0x97 |  1.00~1.54 |
2006 / 11 / 11 | |
| 0x100 | 3.50~6.61 |
2007 / 5 / 31 | |
| 0x102 | 1.60~1.70 |
2007 / 3 / 22 | |
| 0x104 | 1.80~1.82 |
2007 / 5 / 24 | |
| 0x105 | 1.90~1.94 |
2007 / 7 / 24 | |
| 0x106 | 2.00~2.17 |
2007 / 11 / 8 | |
| 0x107 | 2.20~2.80 |
2008 / 3 / 25 | |
| 0x108 | 3.00~3.01 |
2009 / 9 / 1 | |
| 0x110 | 3.10~3.74 |
2009 / 11 / 19 | |
| 0x120 | 4.00~4.25 |
2011 / 11 / 29 | |
| 0x130 | 4.30~4.76 |
2012 / 10 / 24 |
RCO hashreport
all OFW 1.00-4.75 hashes: https://www.mirrorcreator.com/files/7KCMQKWQ/RCO-hashreport.7z_links <--- please someone convert this in a "human readable wiki table"
PSP 6.61 RCO MD5 hashreport
- PSP 6.60 and 6.61 firmware contains 63 .rco files (same files for both firmwares). Two of them are specific for PSPgo model (bluetooth_plugin.rco, slide_plugin.rco)
- Only 10 of them are compresed with ZLIB (dd_helper.rco, dnas_plugin.rco, htmlviewer_plugin.rco, lftv_rmc_univer3in1.rco, lftv_rmc_univer3in1_jp.rco, lftv_rmc_univertuner.rco, lftv_rmc_univertuner_jp.rco, lftv_tuner_jp_jp.rco, lftv_tuner_us_en.rco, oneseg_plugin.rco). All the others are compressed with RLZ (and RLZ decompression is not supported by rcomage, is needed to use Resurssiklunssi v0.3 to rebuild them)
- Resurssiklunssi rebuilds the .rco files and allows for two rebuild modes:
- TRIANGLE or CROSS - only rebuilds
- The converted files will have minFirmwareVer="1.5" (the original value is lost in the conversion)
- SQUARE or CIRCLE - rebuilds and recompress in ZLIB
- The converted files will have minFirmwareVer="2.6" (the original value is lost in the conversion)
- TRIANGLE or CROSS - only rebuilds
Code Sample
- PSP 6.60 and 6.61 firmware. RCO hashes after resurssiklunssi rebuild (cross option)
Code Sample
- PSP firmware 1.00 contains only 21 .rco files (all them uses ZLIB, none of them uses RLZ)
Code Sample