Changes

* followed by a plain binary region,

* followed by a plain binary region,

* followed by an embedded executable filesystem ([[ExeFS]]) - (contains ARM11 code, Home menu icn/bnr and logo),

* followed by an embedded executable filesystem ([[ExeFS]]) - (contains ARM11 code, Home menu icn/bnr and logo),

* and finally followed by a read-only filesystem (RomFS) - (Used for external file storage).

* and finally followed by a read-only filesystem ([[RomFS]]) - (Used for external file storage).

There are CXI files which are not executable, but are used in conjunction with executable CXI files. For instance the DLP Child Container and the Home Menu App Manual. (There is a system update CXI which follows this format, but is used by the 3DS rather than the Application CXI, and only works when embedded in the [[CCI]] format because the nVer is kept in the header of retail [[CCI]] files instead of the application CXI)

There are CXI files which are not executable, but are used in conjunction with executable CXI files. For instance the DLP Child Container and the Home Menu App Manual. (There is a system update CXI which follows this format, but is used by the 3DS rather than the Application CXI, and only works when embedded in the [[CCI]] format because the nVer is kept in the header of retail [[CCI]] files instead of the application CXI)

Non-Executable CXI files are structured in the following order:

Non-Executable CXI files are structured in the following order:

* first a NCCH header,

* first a NCCH header,

* followed by a read-only filesystem (RomFS)

* followed by a read-only filesystem ([[RomFS]])

Non-Executable CXI file examples(Includes Decrypted RomFS):

Non-Executable CXI file examples(Includes Decrypted [[RomFS]]):

[http://depositfiles.com/files/d8ej64571 DLPChildContainer]

[http://depositfiles.com/files/d8ej64571 DLPChildContainer]