By entering this site you need to consent to the use of cookies and their functional use according to this privacy policy. Cookies help us to provide the functional services of the website. Kindly read the below message of use and consent to the use.
The following cookies are stored and shared when accessing this website:
- Internal cookies for the MediaWiki site. This is used for user authentication and article modifications.
- Third-party cookies from Google providing services for Google AdSense and Google Analytics
We will never use data collected outside of the above scope.
Rephrase for clarity. In particular it's more clear that this is exactly the lvl3 image, not more and not less.
Line 1,141:
Line 1,141:
=== [[RomFS]] ===
=== [[RomFS]] ===
−
The raw FS image for the main CXI RomFS(for the current app this is accessible via archiveid 0x3) can be accessed via an all-zero 0xc-byte binary file-lowpath. The update RomFS for the current app can be accessed with the first u32 in the binary file-lowpath being set to 0x5. This allows access to the raw [[RomFS#Level_3_Format|level-3 IVFC image]]: the user process must handle parsing the filesystem used in this image itself.
+
+
Archives 0x3 and 0x2345678E both allow for accessing the [[RomFS#Level_3_Format|level-3 IVFC images]] for RomFS access. The main CXI RomFS is accessible via an all-zero 0xc-byte binary file-lowpath. The update RomFS can be accessed with the first u32 in the binary file-lowpath being set to 0x5. The user must handle parsing the filesystem used in the exposed image itself.
In this scenario, OpenFile returns a handle to the RomFS archive.
In this scenario, OpenFile returns a handle to the RomFS archive.