In memory of Ben “bushing” Byer, who passed away on Monday, February 8th, 2016.

Difference between revisions of "Content.bin file structure"

From WiiBrew
Jump to navigation Jump to search
(New page: ==The content.bin file structure == VC games and Wii channels, when saved to a SD card, will be stored in a file named "private/wii/title/XXXX/content.bin", where XXXX is the four-characte...)
 
(Redirecting to Content.bin#File structure)
 
(24 intermediate revisions by 10 users not shown)
Line 1: Line 1:
−
==The content.bin file structure ==
+
#REDIRECT [[Content.bin#File_structure]]
−
VC games and Wii channels, when saved to a SD card, will be stored in a file named "private/wii/title/XXXX/content.bin", where XXXX is the four-character name of the game/channel.
 
−
 
 
−
The general layout of this file is as follows. Most of the data here is sketchy, at best.
 
−
 
 
−
{| style="border-collapse: collapse; padding: 0.2em 0.2em 0.2em 0.2em;"
 
−
|- style="background-color: #ddd;"
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #ccc;" | '''Length'''
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #dcc;" | '''Description'''
 
−
|- style="background-color: #ddd;"
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #ddd;" | 0x0640
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #edd;" | Part A: Encrypted header
 
−
|- style="background-color: #ddd;"
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #ddd;" | variable, padded to 64-byte boundary
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #edd;" | Part B: Encrypted game info
 
−
|- style="background-color: #ddd;"
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #ddd;" | 0x70, padded to 64-byte boundary
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #edd;" | Part C: Cleartext "Bk" header
 
−
|- style="background-color: #ddd;"
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #ddd;" | 0x1E4 + num_contents*0x24, padded to 64-byte boundary
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #edd;" | Part D: Cleartext TMD block, including content_records for the following files
 
−
|- style="background-color: #ddd;"
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #ddd;" | num_contents*variable, padded to 64-byte boundary
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #edd;" | Part E: Encrypted data contents
 
−
|- style="background-color: #ddd;"
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #ddd;" | 0x340
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #edd;" | Part F: Cleartext certificates
 
−
|}
 
−
 
 
−
===Part A: Encrypted header===
 
−
The header is encrypted by the SD key and SD IV. When decrypted, it contains the following structure:
 
−
{| style="border-collapse: collapse; padding: 0.2em 0.2em 0.2em 0.2em;"
 
−
|- style="background-color: #ddd;"
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #cdc;" | '''Start'''
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #ccd;" | '''End'''
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #ccc;" | '''Length'''
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #dcc;" | '''Description'''
 
−
|- style="background-color: #ddd;"
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #ded;" | 0x000
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #dde;" | 0x007
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #ddd;" | 8
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #edd;" | Title ID (which is 00 01 00 01 followed by the four-character code)
 
−
|- style="background-color: #ddd;"
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #ded;" | 0x008
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #dde;" | 0x00B
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #ddd;" | 4
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #edd;" | Size of part B
 
−
|- style="background-color: #ddd;"
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #ded;" | 0x00C
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #dde;" | 0x01D
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #ddd;" | 16
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #edd;" | MD5 Hash of header
 
−
|- style="background-color: #ddd;"
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #ded;" | 0x01C
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #dde;" | 0x63F
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #ddd;" | 0x624
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #edd;" | As of yet un-analyzed data
 
−
|}
 
−
 
 
−
===Part B: Encrypted game info===
 
−
 
 
−
This part is is also encrypted by the SD key and SD IV. The contents of this part has not yet been fully analyzed. It seems to contain information of what kind of system that is emulated, and probably the image to dislay on the channel selector for this VC game.
 
−
 
 
−
===Part C: Cleartext "Bk" header===
 
−
 
 
−
This part is not encrypted. It is similar to the Bk header found in savegames, but the contents only partially match.
 
−
The header could also be exactly 0x80 long; the size of 0x70 is a guess based on the first field being a size parameter.
 
−
 
 
−
{| style="border-collapse: collapse; padding: 0.2em 0.2em 0.2em 0.2em;"
 
−
|- style="background-color: #ddd;"
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #cdc;" | '''Start'''
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #ccd;" | '''End'''
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #ccc;" | '''Length'''
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #dcc;" | '''Description'''
 
−
|- style="background-color: #ddd;"
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #ded;" | 0x000
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #dde;" | 0x003
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #ddd;" | 4
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #edd;" | Size of this part (presumably; always 0x70)
 
−
|- style="background-color: #ddd;"
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #ded;" | 0x004
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #dde;" | 0x007
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #ddd;" | 4
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #edd;" | Magic word, always 0x42 0x6B 0x00 0x01 (Bk..)
 
−
|- style="background-color: #ddd;"
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #ded;" | 0x008
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #dde;" | 0x00B
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #ddd;" | 4
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #edd;" | NG-id
 
−
|- style="background-color: #ddd;"
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #ded;" | 0x00C
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #dde;" | 0x06F
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #ddd;" | 0x64
 
−
| style="border: 1px solid #ccc; padding: 0.2em; background-color: #edd;" | As of yet un-analyzed data, mostly zero.
 
−
|}
 
−
 
 
−
===Part D: Cleartext TMD block===
 
−
This part is not encrypted. It is well described on the [[Tmd_file_structure|TMD file format]] page. Some things to note:
 
−
* Only the tmd struct is included here, not the certificates.
 
−
* As described on the TMD file format page, after the main struct (with a size of 0x1E4), there follows an array of content_record structs.
 
−
* There is as many structs as the num_contents field in the tmd struct indicates. For VC, this seems to be always 7.
 
−
* The type and size file of the content_record is of special interest, since they describe part E.
 
−
* If type is 0x80 0x01, then the content is included in part E, and the size of the content is given by the size field.
 
−
* Otherwise, type will be 0x00 0x01, and the content is (presumably) shared between VCs and stored elsewere on the Wii.
 
−
 
 
−
===Part E: Encrypted data contents===
 
−
This part is encrypted. The encryption key is currently unknown. It might be unique to the Wii which saved the VC.
 
−
It consists of several separate "files", one for each of the contents with the 0x80 type flag in the TMD content_record, padded to 64-byte boundary.
 
−
 
 
−
===Part F: Cleartext certificates===
 
−
This part is not encrypted. The exact details of this field is not yet analyzed, but it is likely related to the chain of certificates as described on the [[Tmd_file_structure|TMD file format]] page.
 

Latest revision as of 01:39, 26 October 2008

Redirect to:

Retrieved from "https://wiibrew.org/w/index.php?title=Content.bin_file_structure&oldid=30944"