Changes

Jump to navigation Jump to search

NCA (view source)

Revision as of 17:37, 30 March 2021

4,706 bytes added ,  17:37, 30 March 2021
m
Hexkyz moved page NCA Format to NCA: Consistency with other file format pages
Line 3: Line 3:  
The only known area which is not encrypted in the raw NCA is the logo section, when the NCA includes that section. Everything else documented on this page is for the plaintext version of that data.
 
The only known area which is not encrypted in the raw NCA is the logo section, when the NCA includes that section. Everything else documented on this page is for the plaintext version of that data.
   −
=Encryption=
+
= Encryption =
−
The first {at least 0xC00 bytes} are encrypted with AES-XTS with sector size 0x200, at least 6 sectors in total. Everything in this region uses same keydata.
+
The first 0xC00 bytes are encrypted with AES-XTS with sector size 0x200 with a non-standard "tweak" (endianness is reversed, see [https://gist.github.com/SciresM/fe8a631d13c069bd66e9c656ab5b3f7f here]), this encrypted data is an 0x400 NCA header + an 0x200 header for each section in the section table.
   −
=Header=
+
For pre-1.0.0 "NCA2" NCAs, the first 0x400 byte are encrypted the same way as in NCA3. However, each section header is individually encrypted as though it were sector 0, instead of the appropriate sector as in NCA3.
 +
 
 +
= Header =
 
{| class="wikitable" border="1"
 
{| class="wikitable" border="1"
 
|-
 
|-
Line 15: Line 17:  
| 0x0
 
| 0x0
 
| 0x100
 
| 0x100
−
| RSA-2048 signature over the 0x200-bytes starting at offset 0x200 using fixed key.
+
| RSA-2048 signature over the header (data from 0x200 to 0x400) using a fixed key
 
|-
 
|-
 
| 0x100
 
| 0x100
 
| 0x100
 
| 0x100
−
| RSA-2048 signature over the 0x200-bytes starting at offset 0x200 using key from [[NPDM]], or zeroes if not a program.
+
| RSA-2048 signature over the header (data from 0x200 to 0x400) using a key from [[NPDM]] (or zeroes if not a program)
 
|-
 
|-
 
| 0x200
 
| 0x200
 
| 0x4
 
| 0x4
−
| Magicnum "NCA3"
+
| Magicnum "NCA3" ("NCA2", "NCA1" or "NCA0" for pre-1.0.0 NCAs)
 
|-
 
|-
 
| 0x204
 
| 0x204
 
| 0x1
 
| 0x1
−
| 0 for system NCAs. 1 for a NCA from gamecard.
+
| DistributionType (0x00 = System NCA, 0x01 = Gamecard NCA)
 
|-
 
|-
 
| 0x205
 
| 0x205
 
| 0x1
 
| 0x1
−
| Content Type (0=Program, 1=Meta, 2=Control, 3=Manual, 4=Data)
+
| ContentType (0x00 = Program, 0x01 = Meta, 0x02 = Control, 0x03 = Manual, 0x04 = Data, 0x05 = PublicData)
 
|-
 
|-
 
| 0x206
 
| 0x206
 
| 0x1
 
| 0x1
−
| Crypto Type, must be 0-2. Only used stating with [[3.0.0]]. Normally 0. Value 2 is normally used by content using [[3.0.0]] crypto.
+
| KeyGenerationOld (0x00 = [[1.0.0]], 0x01 = Unused, 0x02 = [[3.0.0]])
 
|-
 
|-
 
| 0x207
 
| 0x207
 
| 0x1
 
| 0x1
−
| Key index, must be 0-2.
+
| KeyAreaEncryptionKeyIndex (0x00 = Application, 0x01 = Ocean, 0x02 = System)
 
|-
 
|-
 
| 0x208
 
| 0x208
 
| 0x8
 
| 0x8
−
| Size of the entire NCA.
+
| ContentSize
 
|-
 
|-
 
| 0x210
 
| 0x210
 
| 0x8
 
| 0x8
−
| titleID
+
| ProgramId
 +
|-
 +
| 0x218
 +
| 0x4
 +
| ContentIndex
 
|-
 
|-
 
| 0x21C
 
| 0x21C
 
| 0x4
 
| 0x4
−
| sdk_version. byte0 is normally 0? Compared with a required minimum-value(0x000B0000). Matches this string from codebin: "FS_ACCESS: { sdk_version: {byte3}.{byte2}.{byte1}, ...".
+
| SdkAddonVersion (used in "FS_ACCESS: { sdk_version: {byte3}.{byte2}.{byte1}, ..." with byte0 set to 0 and compared with a required minimum value: 0x000B0000)
 
|-
 
|-
 
| 0x220
 
| 0x220
−
| ?
+
| 0x1
−
| Crypto-Type2. 0x3 = Unknown added with [[3.0.1]].
+
| KeyGeneration (0x03 = [[3.0.1]], 0x04 = [[4.0.0]], 0x05 = [[5.0.0]], 0x06 = [[6.0.0]], 0x07 = [[6.2.0]], 0x08 = [[7.0.0]], 0x09 = [[8.1.0]], 0x0A = [[9.0.0]], 0x0B = [[9.1.0]], 0xFF = Invalid)
 +
|-
 +
| 0x221
 +
| 0x1
 +
| [9.0.0+] Header1SignatureKeyGeneration (0 or 1)
 +
|-
 +
| 0x222
 +
| 0xE
 +
| Reserved
 
|-
 
|-
 
| 0x230
 
| 0x230
 
| 0x10
 
| 0x10
−
| Rights ID ([[Ticket]])
+
| RightsId
 
|-
 
|-
 
| 0x240
 
| 0x240
−
| 0x10*0x4(0x40)
+
| 0x10 * 4
−
| Table for each section, see below.
+
| Array of [[#FsEntry|FsEntry]]
 
|-
 
|-
 
| 0x280
 
| 0x280
−
| 0x20*0x4(0x80)
+
| 0x20 * 4
−
| Table of SHA256 hashes, over each 0x200-byte Section Header Block.
+
| Array of SHA256 hashes (over each [[#FsHeader|FsHeader]])
 
|-
 
|-
 
| 0x300
 
| 0x300
−
| 0x10*0x4(0x40)
+
| 0x10 * 4
−
| Key area
+
| EncryptedKeyArea
 
|}
 
|}
    +
When the above '''KeyGenerationOld''' field is 0x2 on >= v3.0, different {crypto/keydata} is used for the sections' data. With system content, this is used with every ncatype except ncatype0. The only other exception is {data-content} for the firm titles: this is required in order for older-system-versions to install it.
   −
The header is 0x400-bytes, at NCA+0.
+
'''KeyGeneration''' 0x3 (with '''KeyGenerationOld''' set to 0x2) is used for all [[3.0.1]] sysmodules and the [[System_Version_Title]]. With [[3.0.2]], all updated titles use the crypto from [[3.0.1]] for non-ncatype0, except for firm {data-content}. In some cases various game content uses the above newer crypto as well.
−
 
  −
When the above "Crypto Type" field is 0x2 on >=v3.0, different {crypto/keydata} is used for the sections' data. With system content, this is used with every ncatype except ncatype0. The only other exception is {data-content} for the firm titles: this is required in order for older-system-versions to install it.
  −
 
  −
Crypto-Type2 0x3(with the above crypto-type value) is used for all [[3.0.1]] sysmodules and the [[System_Version_Title]].
     −
With [[3.0.2]], all updated titles use the crypto from [[3.0.1]] for non-ncatype0, except for firm {data-content}.
+
'''KeyGeneration''' is always '''MasterKeyVersion''' + 1, except for generations 0 and 1 which are both version 0.
   −
Note: in some cases various game content uses the above newer crypto as well.
+
The keyindex passed to <key-generation-related code> is determined as follows:
 +
* Pre-[[3.0.0]]: The '''KeyAreaEncryptionKeyIndex''' field (0x207) is passed directly.
 +
* [[3.0.0]]+: It's determined using the '''KeyAreaEncryptionKeyIndex''' field (0x207) and the '''KeyGenerationOld''' field (0x206). The latter field must be 0, 1 or 2. In each ncahdr_keyindex block, it executes "if(ncahdr_x206>=3)<panic>", but that won't trigger due to the earlier check. The end result is basically the same as pre-[[3.0.0]], except when ncahdr_x206 == 0x2, final_index is new_base_index+ncahdr_keyindex. Actual implementation loads index from u32_array[ncahdr_crypto_type], where the address of u32_array is different for each ncahdr_keyindex.
 +
* [[3.0.1]]+: The dedicated range check for the '''KeyGenerationOld''' field (0x206) was removed, since the updated code no longer needs it. The output from a function masked with 0xFF is now used instead of ncahdr_x206. The range check for that field was changed from {ncahdr_x206 check with panic described above}, to "if(index>=4)final_index=10;"(skips accessing the array and uses 10 directly). The arrays were updated with an additional entry: final_index=v301_base_index+ncahdr_keyindex.
 +
** The keydata for the above index10 is not(?) known to be initialized.
 +
** The new function called by the code described above does:
 +
** <code>if(ncahdr_x206 < ncahdr_x220){ret = ncahdr_x220; } else { ret = ncahdr_x206; } return ret;</code>
   −
==Section Table Entry==
+
== FsEntry ==
 
{| class="wikitable" border="1"
 
{| class="wikitable" border="1"
 
|-
 
|-
Line 94: Line 111:  
| 0x0
 
| 0x0
 
| 0x4
 
| 0x4
−
| Media offset
+
| StartOffset (in Media Units which are 0x200 bytes)
 
|-
 
|-
 
| 0x4
 
| 0x4
 
| 0x4
 
| 0x4
−
| Media end-offset
+
| EndOffset (in Media Units which are 0x200 bytes)
 
|-
 
|-
 
| 0x8
 
| 0x8
 
| 0x4
 
| 0x4
−
| Unknown
+
| Reserved
 
|-
 
|-
 
| 0xC
 
| 0xC
 
| 0x4
 
| 0x4
−
| Unknown
+
| Reserved
 
|}
 
|}
   −
Entry size is 0x10-bytes.
+
= FsHeader =
−
 
  −
Media offset is absoluteoffset/{mediasize}, where mediasize is hard-coded to 0x200.
  −
 
  −
=Section Header Block=
   
{| class="wikitable" border="1"
 
{| class="wikitable" border="1"
 
|-
 
|-
Line 121: Line 134:  
|-
 
|-
 
| 0x0
 
| 0x0
−
| 0x1
+
| 0x2
−
| ?
+
| Version (always 2)
−
|-
  −
|-
  −
| 0x1
  −
| 0x1
  −
| ?
   
|-
 
|-
 
| 0x2
 
| 0x2
 
| 0x1
 
| 0x1
−
| ?
+
| FsType (0 = RomFs, 1 = PartitionFs)
 
|-
 
|-
 
| 0x3
 
| 0x3
 
| 0x1
 
| 0x1
−
| Filesystem type. 0x2 = PFS0, 0x3 = RomFS, everything else is invalid.
+
| HashType (0 = Auto, 2 = HierarchicalSha256, 3 = HierarchicalIntegrity)
 
|-
 
|-
 
| 0x4
 
| 0x4
 
| 0x1
 
| 0x1
−
| Crypto type. 0 and >4 are invalid. 1 = none(plaintext from raw NCA). 2 = other crypto. 3 = regular crypto. 4 = unknown.
+
| EncryptionType (0 = Auto, 1 = None, 2 = AesCtrOld, 3 = AesCtr, 4 = AesCtrEx)
 
|-
 
|-
 
| 0x5
 
| 0x5
−
| 0x1
+
| 0x3
−
| Padding?
+
| Padding
 
|-
 
|-
 
| 0x8
 
| 0x8
−
|  
+
| 0xF8
−
| FS-specific superblock.
+
| [[#HashInfo|HashInfo]]
 
|-
 
|-
 
| 0x100
 
| 0x100
−
| ?
+
| 0x40
−
| Optional BKTR header. Can be used with any section, but only known to be used with game-updates RomFS.
+
| [[#PatchInfo|PatchInfo]] (only used with game updates RomFs)
 +
|-
 +
| 0x140
 +
| 0x4
 +
| Generation
 +
|-
 +
| 0x144
 +
| 0x4
 +
| SecureValue
 +
|-
 +
| 0x148
 +
| 0x30
 +
| SparseInfo (only used in sections with sparse storage)
 +
|-
 +
| 0x178
 +
| 0x88
 +
| Reserved
 
|}
 
|}
   −
The Section Header Block for each section is at absoluteoffset+0x400+(sectionid*0x200), where sectionid corresponds to the index used with the entry/hash tables.
+
The FsHeader for each section is at absoluteoffset+0x400+(sectionid*0x200), where sectionid corresponds to the index used with the entry/hash tables.
   −
The total size is 0x200-bytes.
+
== HashInfo ==
 +
This contains information specific to the hash type in use.
   −
==PFS0 superblock==
+
=== HierarchicalSha256 ===
 
{| class="wikitable" border="1"
 
{| class="wikitable" border="1"
 
|-
 
|-
Line 165: Line 190:  
! Description
 
! Description
 
|-
 
|-
−
| 0x8
+
| 0x0
 
| 0x20
 
| 0x20
−
| SHA256 hash over the hash-table at section-start+0 with the below hash-table size.
+
| SHA256 hash over the hash-table at section-start+0 with the below hash-table size
 
|-
 
|-
−
| 0x28
+
| 0x20
 
| 0x4
 
| 0x4
−
| Block size in bytes.
+
| Block size in bytes
 
|-
 
|-
−
| 0x2C
+
| 0x24
 
| 0x4
 
| 0x4
−
| Must be 0x2.
+
| Must be 0x2
 +
|-
 +
| 0x28
 +
| 0x8
 +
| Offset of hash-table (normally zero)
 
|-
 
|-
 
| 0x30
 
| 0x30
 
| 0x8
 
| 0x8
−
| Offset of hash-table. Normally zero?
+
| Size of hash-table
 
|-
 
|-
 
| 0x38
 
| 0x38
 
| 0x8
 
| 0x8
−
| Size of hash-table.
+
| Offset relative to section-start where the PFS0 header is located
 
|-
 
|-
 
| 0x40
 
| 0x40
 
| 0x8
 
| 0x8
−
| Offset relative to section-start where the PFS0 header is located.
+
| Actual byte-size of the PFS0 filesystem relative to the PFS0 header
 
|-
 
|-
 
| 0x48
 
| 0x48
−
| 0x8
+
| 0xB0
−
| Actual byte-size of the PFS0 filesystem relative to the PFS0 header.
+
| Reserved
−
|-
  −
| 0x50
  −
| 0xF4
  −
| Normally zeros.
  −
|-
  −
| 0x144
  −
| ?
  −
| 0x1?
  −
|-
  −
| 0x148
  −
| 0xB8
  −
| Normally zeros.
   
|}
 
|}
   −
This documents the structure of Section Header Block +0 for PFS0.
+
=== HierarchicalIntegrity ===
−
 
  −
==RomFS superblock==
   
{| class="wikitable" border="1"
 
{| class="wikitable" border="1"
 
|-
 
|-
Line 215: Line 230:  
! Description
 
! Description
 
|-
 
|-
−
| 0x8
+
| 0x0
−
| 0xE0
+
| 0x4
−
| IVFC header. Basically the same as [[Savegames]] IVFC except with 2 more levels and +0x0C is non-zero, see below.
+
| Magicnum "IVFC"
−
|}
  −
 
  −
This documents the structure of Section Header Block +0 for RomFS.
  −
 
  −
=== IVFC ===
  −
{| class="wikitable"
   
|-
 
|-
−
! Start
+
| 0x4
−
! Length
+
| 0x4
−
! Description
  −
|-
  −
| 0x00
  −
| 4
  −
| Magic ("IVFC")
  −
|-
  −
| 0x04
  −
| 4
   
| Magic Number (0x20000)
 
| Magic Number (0x20000)
 
|-
 
|-
−
| 0x08
+
| 0xC
−
| 4
+
| 0x4
 
| Master hash size?
 
| Master hash size?
 
|-
 
|-
−
| 0x0C
+
| 0x10
−
| 4
+
| 0x4
 
| Usually 7? Unknown, could be related to total number of levels maybe?
 
| Usually 7? Unknown, could be related to total number of levels maybe?
 
|-
 
|-
−
| 0x10
+
| 0x14
−
| 8
+
| 0x8
 
| Level 1 offset
 
| Level 1 offset
 
|-
 
|-
−
| 0x18
+
| 0x1C
−
| 8
+
| 0x8
 
| Level 1 size
 
| Level 1 size
 
|-
 
|-
 
| 0x20
 
| 0x20
−
| 4
+
| 0x4
−
| Level 1 block size, in log2
+
| Level 1 block size (in log2)
 
|-
 
|-
 
| 0x24
 
| 0x24
−
| 4
+
| 0x4
 
| Reserved
 
| Reserved
 
|-
 
|-
 
| 0x28
 
| 0x28
−
| 8
+
| 0x8
 
| Level 2 offset
 
| Level 2 offset
 
|-
 
|-
 
| 0x30
 
| 0x30
−
| 8
+
| 0x8
 
| Level 2 size
 
| Level 2 size
 
|-
 
|-
 
| 0x38
 
| 0x38
−
| 4
+
| 0x4
−
| Level 2 block size, in log2.
+
| Level 2 block size (in log2)
 
|-
 
|-
 
| 0x3C
 
| 0x3C
−
| 4
+
| 0x4
 
| Reserved
 
| Reserved
 
|-
 
|-
 
| 0x40
 
| 0x40
−
| 8
+
| 0x8
 
| Level 3 offset
 
| Level 3 offset
 
|-
 
|-
 
| 0x48
 
| 0x48
−
| 8
+
| 0x8
 
| Level 3 size
 
| Level 3 size
 
|-
 
|-
 
| 0x50
 
| 0x50
−
| 4
+
| 0x4
−
| Level 3 block size, in log2.
+
| Level 3 block size (in log2)
 
|-
 
|-
 
| 0x54
 
| 0x54
−
| 4
+
| 0x4
 
| Reserved
 
| Reserved
 
|-
 
|-
 
| 0x58
 
| 0x58
−
| 8
+
| 0x8
 
| Level 4 offset
 
| Level 4 offset
 
|-
 
|-
 
| 0x60
 
| 0x60
−
| 8
+
| 0x8
 
| Level 4 size
 
| Level 4 size
 
|-
 
|-
 
| 0x68
 
| 0x68
−
| 4
+
| 0x4
−
| Level 4 block size, in log2.
+
| Level 4 block size (in log2)
 
|-
 
|-
 
| 0x6C
 
| 0x6C
−
| 4
+
| 0x4
 
| Reserved
 
| Reserved
 
|-
 
|-
 
| 0x70
 
| 0x70
−
| 8
+
| 0x8
 
| Level 5 offset
 
| Level 5 offset
 
|-
 
|-
 
| 0x78
 
| 0x78
−
| 8
+
| 0x8
 
| Level 5 size
 
| Level 5 size
 
|-
 
|-
 
| 0x80
 
| 0x80
−
| 4
+
| 0x4
−
| Level 5 block size, in log2.
+
| Level 5 block size (in log2)
 
|-
 
|-
 
| 0x84
 
| 0x84
−
| 4
+
| 0x4
 
| Reserved
 
| Reserved
 
|-
 
|-
 
| 0x88
 
| 0x88
−
| 8
+
| 0x8
 
| Level 6 offset
 
| Level 6 offset
 
|-
 
|-
 
| 0x90
 
| 0x90
−
| 8
+
| 0x8
 
| Level 6 size
 
| Level 6 size
 
|-
 
|-
 
| 0x98
 
| 0x98
−
| 4
+
| 0x4
−
| Level 6 block size, in log2.
+
| Level 6 block size (in log2)
 
|-
 
|-
 
| 0x9C
 
| 0x9C
−
| 4
+
| 0x4
 
| Reserved
 
| Reserved
 
|-
 
|-
 
| 0xA0
 
| 0xA0
−
| 32
+
| 0x20
−
| Unknown, reserved?
+
| Reserved
 
|-
 
|-
 
| 0xC0
 
| 0xC0
−
| 32
+
| 0x20
 
| Hash
 
| Hash
 
|}
 
|}
   −
== BKTR ==
+
== PatchInfo ==
−
{| class="wikitable"
+
{| class="wikitable" border="1"
 
|-
 
|-
−
! Start
+
! Offset
−
! Length
+
! Size
 
! Description
 
! Description
 
|-
 
|-
Line 360: Line 361:  
| 0x8
 
| 0x8
 
| Offset
 
| Offset
−
|-
   
|-
 
|-
 
| 0x8
 
| 0x8
Line 368: Line 368:  
| 0x10
 
| 0x10
 
| 0x4
 
| 0x4
−
| "BKTR"
+
| Magicnum "BKTR"
 
|-
 
|-
 
| 0x14
 
| 0x14
Line 380: Line 380:  
| 0x1C
 
| 0x1C
 
| 0x4
 
| 0x4
−
| ?
+
|  
 
|-
 
|-
 
| 0x20
 
| 0x20
 
| 0x20
 
| 0x20
 
| Same as the above 0x20-bytes except with different data.
 
| Same as the above 0x20-bytes except with different data.
 +
|}
 +
 +
The above byte-offsets are relative to the start of the section-data.
 +
 +
The two sections specified by the two BKTR entries are usually(?) at the very end of the section data(section_endoffset-{size of BKTR sections}).
 +
 +
=== RomFs Patching ===
 +
The [[#PatchInfo|PatchInfo]] section enables combining data from an update NCA with the RomFs from a base NCA to create a single patched RomFS image.
 +
 +
The first BKTR entry describes how to map regions of the two RomFs images to create the patched RomFs. It has the following format:
 +
{| class="wikitable" border="1"
 +
|-
 +
! Offset
 +
! Size
 +
! Description
 +
|-
 +
| 0x0
 +
| 0x4
 +
| Padding/Unused?
 +
|-
 +
| 0x4
 +
| 0x4
 +
| Number of Buckets
 +
|-
 +
| 0x8
 +
| 0x8
 +
| Total Size of the Virtual RomFS Image
 +
|-
 +
| 0x10
 +
| 0x3FF0
 +
| Base Virtual Offset for each Bucket (u64s, padded with 0s until end)
 +
|-
 +
| 0x4000
 +
| 0x4000*X
 +
| Relocation Buckets
 +
|}
 +
 +
Where relocation buckets are as follows:
 +
{| class="wikitable" border="1"
 +
|-
 +
! Offset
 +
! Size
 +
! Description
 
|-
 
|-
−
| 0x40
+
| 0x0
−
| 0x4?
+
| 0x4
−
| ?
+
| Padding/Unused?
 +
|-
 +
| 0x4
 +
| 0x4
 +
| Number of Entries
 +
|-
 +
| 0x8
 +
| 0x8
 +
| End offset for this Bucket
 +
|-
 +
| 0x10
 +
| 0x3FF0
 +
| Relocation Entries
 +
|}
 +
 
 +
Where relocation entries are as follows:
 +
{| class="wikitable" border="1"
 +
|-
 +
! Offset
 +
! Size
 +
! Description
 +
|-
 +
| 0x0
 +
| 0x8
 +
| Address in Patched RomFs
 +
|-
 +
| 0x8
 +
| 0x8
 +
| Address in Source RomFs
 +
|-
 +
| 0x10
 +
| 0x4
 +
| 1=Is from Patch RomFS, 0=Is from Base RomFS
 +
|}
 +
 
 +
The second BKTR entry describes the subsections within the Patch RomFs. It has the following format:
 +
{| class="wikitable" border="1"
 +
|-
 +
! Offset
 +
! Size
 +
! Description
 +
|-
 +
| 0x0
 +
| 0x4
 +
| Padding/Unused?
 +
|-
 +
| 0x4
 +
| 0x4
 +
| Number of Buckets
 +
|-
 +
| 0x8
 +
| 0x8
 +
| Total Size of the Physical Patch Image
 +
|-
 +
| 0x10
 +
| 0x3FF0
 +
| Base Physical Offset for each Bucket (u64s, padded with 0s until end)
 +
|-
 +
| 0x4000
 +
| 0x4000*X
 +
| Subsection Buckets
 +
|}
 +
 
 +
Where subsection buckets are as follows:
 +
{| class="wikitable" border="1"
 +
|-
 +
! Offset
 +
! Size
 +
! Description
 +
|-
 +
| 0x0
 +
| 0x4
 +
| Padding/Unused?
 +
|-
 +
| 0x4
 +
| 0x4
 +
| Number of Entries
 +
|-
 +
| 0x8
 +
| 0x8
 +
| End offset for this Bucket
 
|-
 
|-
−
| 0x44
+
| 0x10
−
| 0x4?
+
| 0x3FF0
−
| ?
+
| Subsection Entries
 
|}
 
|}
   −
Using this header is enabled when offset 0x8 in this header is non-zero.
+
Where subsection entries are as follows:
 +
{| class="wikitable" border="1"
 +
|-
 +
! Offset
 +
! Size
 +
! Description
 +
|-
 +
| 0x0
 +
| 0x8
 +
| Address in Patch RomFs
 +
|-
 +
| 0x8
 +
| 0x4
 +
| Padding/Unused?
 +
|-
 +
| 0xC
 +
| 0x4
 +
| Value for subsection AES-CTR
 +
|}
   −
The above byte-offsets are relative to the start of the section-data.
+
Official code assumes the relocation entries are sorted, and performs a binary search when determining where to read from. Each subsection in the Patch RomFs has its CTR calculated separately from the others based on the value in its entry (the BKTR entries use normal crypto). Thus decrypting a Patch RomFS requires decrypting and parsing the BKTR entries before anything else.
   −
The two sections specified by the two BKTR entries are usually(?) at the very end of the section data(section_endoffset-{size of BKTR sections}).
+
= Logo Section =
 +
This is a PFS0.
   −
=Logo section=
+
See [[NCA_Content_FS|here]] for the mounted-FS logo contents.
−
This is a PFS0. See [[NCA_Content_FS|here]] for the mounted-FS logo contents.
     −
=ExeFS section =
+
= ExeFS Section =
 
This is a PFS0.
 
This is a PFS0.
    
See [[ExeFS|here]] for mounted-FS ExeFS contents.
 
See [[ExeFS|here]] for mounted-FS ExeFS contents.
   −
=PFS0=
+
= Game Updates =
 +
The section-data for ncatype1 RomFS section(section1) uses section-crypto-type 0x4.
 +
 
 +
Game updates also contain multiple ncatype6 content, which contain "section0_pfs0/fragment". Some of these are just NCAs, unknown for the rest(presumably NCAs with additional crypto?). The first ncatype6 content fragment file has a NDV0 header, with the NCA starting at offset 0x44.
 +
 
 +
= PFS0 =
 
{| class="wikitable" border="1"
 
{| class="wikitable" border="1"
 
|-
 
|-
Line 443: Line 589:  
| 0x0
 
| 0x0
 
| 0x4
 
| 0x4
−
| "PFS0" Magic
+
| Magicnum "PFS0"
 
|-
 
|-
 
| 0x4
 
| 0x4
Line 471: Line 617:     
Where File Entry Table consists of Number of Files FileEntries:
 
Where File Entry Table consists of Number of Files FileEntries:
−
   
{| class="wikitable" border="1"
 
{| class="wikitable" border="1"
 
|-
 
|-
Retrieved from "https://switchbrew.org/wiki/Special:MobileDiff/2598...10727"

Navigation menu