

The certificate name/identity from the AP certificate is always set to AP0000000100000002, because it's always generated by the System Menu. Both values must be padded with two leading \x00 before each coordinate in order to be able to use them as part of crypto functions. Unlike the ECDSA signatures from the certificates in the next section, this is a full, untrimmed, 0x40-byte long signature.įor more information about each certificate layout, please refer to this page.Ĭopy of the console-specific device certificate (also known as NG certificate), usually found at /sys/device.cert in the NAND FS.Īpplication-specific certificate (also known as AP certificate), dynamically generated during the content.bin file creation.īoth certificates hold a trimmed ECDSA signature and a trimmed 0x3C-byte long ECC public key. This signature can be verified using the ECC public key from that very same AP certificate.

This is an ECDSA signature calculated over the entire embedded backup WAD during the content.bin file creation, using SHA-1 as the cryptographic hash function and the random ECC private key from the AP certificate in the plaintext certificate chain area. Shared contents are never included, although the System Menu doesn't complain if they're available in the embedded backup WAD package.
SAVE WII VC WADS TO NAND FULL
This is a full backup WAD package with all normal/private contents from the transferred channel. The decrypted icon.bin length field from the encrypted info header represents the unpadded icon.bin length after being decrypted. This is a copy of the /meta/icon.bin entry from the channel's opening.bnr U8 archive, zero padded for 0x40 alignment (if needed) and encrypted with AES-128-CBC using the SD Key and SD IV. Can be set to any title, even non-existant ones.Ĭopy of the IMET header from the channel's opening.bnr, with the MD5 hash at the end zeroed-out. Can be set to any title, even non-existant ones. Lower 32 bits from the title ID of another game/channel. MD5 hash of the decrypted icon.bin block (without discarding the 0x40 alignment zero padding, if available). MD5 hash of this header, with this field set to the MD5 Blanker.

When decrypted, it contains the following structure:ĭecrypted icon.bin length (align up to 0x40 to get the encrypted icon.bin block size). The info header is encrypted with the SD Key and SD IV using AES-128-CBC. The general layout of content.bin files is as follows: Put it in the same directory as a compiled version of Segher's Wii.git tools, since it depends on them. This is evidenced by the fact that plaintext sections within these files (like the TMD) are artificially padded with trailing zeroes, in order to make the next section start at an aligned offset.Įach content.bin file starts with a header that can be decrypted successfully by every Wii console, since the icon, banner, title and description of the channel are all readable in the Wii SD card menu, even if the file was not originally generated by the console it's being used with.Ī program to help parse and analyze the structure of content.bin files: parse-channel.c. Just like WAD files, each individual section from a content.bin file is aligned to a 0x40-byte boundary. Please refer to Savegame Files if you wish to know more about transferred savegames, and/or Backup WADs if you wish to know more about transferred DLCs. This page covers the content.bin format used by transferred channels. Renaming the directories where these files are stored will make the Wii not recognize them anymore, as expected. bin, where represents a specific content index value from a TMD content record, expressed as a 3-digit number in base 10 notation (e.g. Wii channels, savegames and downloadable content data (DLCs) from certain disc-based games can (almost everytime) be transferred from the internal NAND storage to a SD card inserted into the console.īoth channels and savegames are stored in /private/wii/title// as single content.bin and data.bin files, respectively, where is the ASCII representation of the lower 32 bits from the game-specific title ID.ĭLCs are stored in /private/wii/data// as multiple.
