3dbrew - User contributions [en]

Home Menu

2026-06-09T21:57:13Z

Gruetzig: meow

The '''Home Menu''' is the heart of the Nintendo 3DS. From there one can start games, applications, and access various processes including the friends list. It is launched by [[NS]], and is always running in the background in 3DS-mode except when other programID-high 00040030 applications like Internet Browser, Friend-List, etc are running. Home Menu is still running while [[System Settings]] is running, however the System Settings application does not allow directly returning to home-menu. The system will normally re-launch Home Menu when the Home Menu process crashes/terminates. When this re-launch occurs while Home Menu is active, Home Menu displays an error message which says to manually reboot the system.

== System Versions ==
Nintendo devised a system, whereby updates would be delivered via two channels:
*Card Updates (CUP) - The Nintendo 3DS is updated with data from an [[System Update CFA|update partition]] on retail gamecard title.
*Network Updates (NUP) - The Nintendo 3DS is updated by downloading data from Nintendo's [[Title list|CDN]].

CUPs will only deliver updates to core features, such as the Home Menu, [[Download Play]] etc. CUPs will not deliver updates to Network features, such as [[System Transfer]], [[Internet Browser]], [[StreetPass Mii Plaza]] or [[EShop|eShop]].

NUPs can deliver updates to core features as well as (updated) Network Features.

As a result of deciding to make a distinction between what content could be updated and how, Nintendo split the system version displayed by [[System Settings]] into two parts: [[CVer]] (Console Version) and [[NVer]] (Network Update Version). Represented as:
<CVer Major>.<CVer Minor>.<CVer Micro>-<NUP Version><NUP Region>

The Console Version represents the version of the collectively installed core features. And the NUP Version represents the version of the collectively installed network features.

So if a 3DS' System Firmware read '''2.1.0-2U''', it would indicate a console version of '''2.1.0''' and a NUP version of '''2U'''.

NOTES:
* CUPs can only update core content, so [[NVer]] is never updated with CUPs.
* NUPs will not update [[NVer]] if network features are not updated. (Best seen with the USA vs JPN/EUR 6.0.0 NUP)

CUPs are implemented by adding a [[System Update CFA]] to retail NCSD gamecard images. Nintendo generally creates CUPs after NUPs are released.

When updating the system from 4.5.0-6 to 4.5.0-10, the following titles are updated(in the order of title download+install): [[Health and Safety Information]], [[Nintendo 3DS Camera]], [[eShop]], [[System Transfer]], [[Internet Browser]], [[Title_list|0004009B00014102]], [[Title_list|0004009B00014202]], [[Title_list|0004009B00014302]], [[NVer]], and [[FIRM|AGB_FIRM]].

=== System Versions List ===
{| class="wikitable"
|-
! System version
! Home Menu title version
! Release date
! Changelog
! System security [[3DS_System_Flaws|flaws]] fixed*
! Userland security [[3DS_Userland_Flaws|flaws]] fixed*
! 3DS-mode homebrew affected*
! CUP Released
! CDN Availability
! CDN Post Date
|-
| [[1.0.0-0|1.0.0-0]]
| 0
| February 26, 2011
| Shipped with 3DS on launch
|
|
|
| Yes
| Available
| February 18, 2011
|-
| [[1.1.0-1|1.1.0-1]]
| 0
| February ?, 2011
| General bug fixes
Added 3D Video title to menu. ("For a Limited Time Only")
|
|
|
| Yes
| Available
| March 1, 2011
|-
| [[2.0.0-2|2.0.0-2]]
| 1029
| June 6/7, 2011
| [[eShop]] added, web browser available, [[System Transfer]] added. Full DSiWare data management available. [[Automatic_System_Update_Download|Automatic]] downloading for system updates added. Video stubbed.
|
|
|
| No
| Available
| June 6, 2011
|-
| [[2.1.0-3|2.1.0-3]]
| 2049
| June 15, 2011
| Fixes the Ridge Racer freeze.
|
|
|
| Yes
| Available
| June 15, 2011
|-
| [[2.1.0-4|2.1.0-4]]
| Not updated
| July 25, 2011
| System stability improvements and other adjustments.
|
|
|
| No
| Available
| July 25, 2011
|-
| [[2.2.0-X|2.2.0]]
| ?
| November 6, 2011
| CUP Only Release. Add "join game" feature to [[Friend List]]. Update from some game cards such as Super Mario 3D Land.
|
|
|
| Yes
| Unavailable
| ?
|-
| [[3.0.0-5|3.0.0-5]]
| 4111
| December 7, 2011
| Added 3D video recording to the camera title, updated Mii Streetpass Plaza, [[System Transfer]] between 3DS systems available, improved eShop, home menu QR code scanning with QR codes containing URLs. [[Nintendo Zone]] is now always accessible, 3D video streaming support was added to NZone. This added support for running GBA VC titles via AGB_FIRM as well, support for GBA VC titles was also added to NATIVE_FIRM.
|
|
|
| Yes
| Available
| December 7, 2011
|-
| [[3.0.0-6|3.0.0-6]]
| Not updated
| December 21, 2011
| Only StreetPass Mii Plaza and the [[NVer]] title were updated. From Nintendo's release notes: "System stability improvements and other adjustments".
|
|
|
| No
| Available
| December 21, 2011
|-
| [[3.1.0-6|3.1.0-6]]
| Not updated
| Unknown
| Unknown. Sighted preinstalled on some early European 3DS XLs.
|
|
|
| ?
| Unknown
| Unknown
|-
| [[4.0.0-7|4.0.0-7]]
| 5131
| April 24, 2012
| Add folders to Home Menu, game patching added, buy more expensive games than 1000 yen in JPN. System titles for CHN, TWN, and KOR became available.
| Yes
|
|
| Yes
| Available
| April 24, 2012
|-
| [[4.1.0-8|4.1.0-8]]
| Not updated
| May 14, 2012
| From changelog: "improvements to overall system stability and other minor adjustments". Once updated to [[4.1.0-8]], the parental-controls PIN is no longer required for future system updates.
| Yes
|
|
| Yes
| Available
| May 14, 2012
|-
| [[4.2.0-9|4.2.0-9]]
| 6146
| June 26, 2012
| Improved eShop safety for entering credit-card info, and behind the scenes improvements. Stored CC info will be deleted by this updated eShop, and can be re-entered again.
|
|
|
| Yes
| Available
| June 26, 2012
|-
| [[4.3.0-10|4.3.0-10]]
| Not updated
| July 24, 2012
| Updated eShop, bad word list and NZone hotspot list updated.
|
|
|
| Yes
| Available
| July 24, 2012
|-
| [[4.4.0-10|4.4.0-10]]
| Not updated
| September 19, 2012
| NZone hotspot list updated and TWL_FIRM updated for blocking flash cards.
|
|
|
| Yes
| Available
| September 19, 2012
|-
| [[4.4.0-10|4.4.0-10C]]
| Not updated
| October 17, 2012
| China-only, the *only* updated title was [[System Settings]]. This title was updated to a version already available in TWN/KOR.
|
|
|
| ?
| Available
| October 17, 2012
|-
| [[4.5.0-10|4.5.0-10]]
| Not updated
| December 4, 2012
| Flash-card block via updated TWL_FIRM and whitelist. NZone hotspot list updated as well.
|
|
|
| Yes
| Available
| December 4, 2012
|-
| [[5.0.0-11|5.0.0-11]]
| 7172
| March 25, 2013
| Many system titles including NATIVE_FIRM were updated, multiple vulnerabilities were fixed as well.
| Yes
|
| Yes
| No
| Available
| March 25, 2013
|-
| [[5.1.0-11|5.1.0-11]]
| Not updated
| April 4, 2013
| NATIVE_FIRM and NS were updated. According to the official change-log: "Resolves an issue that may prevent access to the System Settings or other features."
| No
|
| No
| Yes
| Available
| April 4, 2013
|-
| [[6.0.0-11|6.0.0-12 (-11U)]]
| 8198
| June 17, 2013
| Official change-log: "Users can now back up save data for downloadable versions of Nintendo 3DS software and most Virtual Console games". For EUR/JPN, the [[StreetPass Mii Plaza]] application and the [[Nintendo 3DS Camera]] application were updated. Other titles for all regions were updated as well.
| Yes
|
|
| No
| Available
| June 17, 2013
|-
| [[6.1.0-11|6.1.0-12 (-11U)]]
| Not updated
| June 27, 2013
| Official change-log: "Further improvements to overall system stability and other minor adjustments have been made to enhance the user experience."
|
|
|
| Yes
| Available
| June 27, 2013
|-
| [[6.1.0-12U]]
| Not updated
| July 11, 2013
| This USA-only update added the updated network features applications which were first released in JPN/EUR with the [[6.0.0-11|6.0.0-12 NUP]] update.
|
|
|
| No
| Available
| July 11, 2013
|-
| [[6.2.0-12]]
| Not updated
| August 6, 2013
| This update added support for the StreetPass relay feature, updated TWL_FIRM, and updated the Nintendo Zone hotspots list.
|
|
|
| Yes
| Available
| August 6, 2013
|-
| [[6.3.0-12]]
| Not updated
| September 13, 2013
| See [[6.3.0-12|this]].
| No
|
| No
| No
| Available
| September 13, 2013
|-
| [[6.4.0-12]]
| ?
| November 11, 2013
| See [[6.4.0-12|this]](Only for the KOR and TWN regions).
|
|
|
| No
| Available
| November 11, 2013
|-
| [[7.0.0-13]]
| 9230
| December 9, 2013
| See [[7.0.0-13|this]].
| Yes
| Yes
|
| No
| Available
| December 9, 2013
|-
| [[7.1.0-14]]
| Not updated
| December 19, 2013
| See [[7.1.0-14|this]].
| No
|
|
| Yes
| Available
| December 19, 2013
|-
| [[7.1.0-15]]
| Not updated
| January 22, 2014
| See [[7.1.0-15|this]].
| No
|
| No
| No
| Available
| January 22, 2014
|-
| [[7.1.0-16]]
| Not updated
| February 26, 2014
| See [[7.1.0-16|this]].
| No
|
| No
| No
| Available
| February 26, 2014
|-
| [[7.2.0-17]]
| Not updated
| May 12, 2014
| See [[7.2.0-17|this]].
|
|
| No
| Yes
| Available
| May 12, 2014
|-
| [[8.0.0-18]]
| Not updated
| July 7, 2014
| See [[8.0.0-18|this]].
| No
|
| No
| Yes
| Available
| July 7, 2014
|-
| [[8.1.0-18]]
| Not updated
| July 24, 2014
| See [[8.1.0-18|this]].
| No
|
| No
| Yes
| Available
| July 24, 2014
|-
| [[8.1.0-19]]
| Not updated
| August 7, 2014
| See [[8.1.0-19|this]].
| No
|
| No
| No
| Available
| August 7, 2014
|-
| [[8.1.0-0 New3DS]]
| Not updated
| September 26, 2014
| See [[8.1.0-0 New3DS|this]].
|
|
| No
| No
| Available
| September 26, 2014
|-
| 8.1.0-19
| Not updated
| October 2, 2014
| Japan-only "update", see [http://yls8.mtheall.com/ninupdates/reports.php?date=10-02-14_02-05-03&sys=ctr here]. The only change was that a new title([[New_3DS]]-only system application) was added, CVer/NVer titles were not even updated. The initial version of this [[Title_list|title]] is a stub.
| No
|
| No
| No
| Available
| October 2, 2014
|-
| [[9.0.0-20]]
| v11272
| October 6, 2014
| See [[9.0.0-20|this]].
|
|
| No
| Yes (K)
| Available
| October 6, 2014
|-
| [[9.1.0-20J]]
| v14336(JPN-region title)
| October 10, 2014
| Japan-only, see [[9.1.0-20J|this]].
| No
|
| No
| No
| Available
| October 10, 2014
|-
| [[9.2.0-20]]
|
| October 29, 2014
| See [[9.2.0-20|this]].
| No
|
| No
| Yes (U/E)
| Available
| October 29, 2014
|-
| [[9.3.0-21]]
|
| December 8, 2014
| See [[9.3.0-21|this]].
| Yes
|
| Yes
| No
| Available
| December 8, 2014
|-
| [[9.4.0-21]]
|
| December 11, 2014
| See [[9.4.0-21|this]].
| No
|
| No
| No
| Available
| December 11, 2014
|-
| [[9.5.0-22]]
|
| February 2, 2015
| See [[9.5.0-22|this]].
| Yes
|
|
| Yes (J/U/E)
| Available
| February 2, 2015
|-
| [[9.5.0-23]]
|
| March 2, 2015
| See [[9.5.0-23|this]].
| No
| Yes
|
| As above
| Available
| March 2, 2015
|-
| [[9.6.0-24]]
|
| March 23, 2015
| See [[9.6.0-24|this]].
| See [[9.6.0-24|here]].
|
|
| Yes (J/U/E)
| Available
| March 23, 2015
|-
| [[9.7.0-25]]
|
| April 20, 2015
| See [[9.7.0-25|this]].
| Probably none?
|
| No
| Yes (J/U/E)
| Available
| April 20, 2015
|-
| [[9.8.0-25]]
|
| June 1, 2015
| See [[9.8.0-25|this]].
| No
| No
| No
| Yes (J/U/E)
| Available
| June 1, 2015
|-
| [[9.9.0-26|9.9.0-26]]
|
| July 13, 2015
| See [[9.9.0-26|this]].
|
|
|
| Yes (J/U/E/K)
| Available
| July 13, 2015
|-
| [[10.0.0-27|10.0.0-27]]
|
| September 8, 2015
| See [[10.0.0-27|this]].
| Yes
| No
| No
| No
| Available
| September 8, 2015
|-
| [[10.1.0-27|10.1.0-27]]
|
| September 14, 2015
| See [[10.1.0-27|this]].
| No
| No
| No
| Yes (J/U/E/K)
| Available
| September 14, 2015
|-
| [[10.2.0-28|10.2.0-28]]
|
| October 19, 2015
| See [[10.2.0-28|this]].
|
|
|
| Yes (J/U/E)
| Available
| October 19, 2015
|-
| [[10.3.0-28|10.3.0-28]]
|
| November 9, 2015
| See [[10.3.0-28|this]].
|
|
|
| Yes (J/U/E)
| Available
| November 9, 2015
|-
| [[10.4.0-29|10.4.0-29]]
|
| January 18, 2016
| See [[10.4.0-29|this]].
| Yes
| Launching old Ironfall was blocked.
| Yes
| No
| Available
| January 18, 2016
|-
| [[10.5.0-30|10.5.0-30]]
|
| January 25, 2016
| See [[10.5.0-30|this]].
|
|
|
| Yes (J/U/E)
| Available
| January 25, 2016
|-
| [[10.6.0-31|10.6.0-31]]
|
| February 22, 2016
| See [[10.6.0-31|this]].
| Yes
| Yes
| Yes
| Yes (J/U)
| Available
| February 22, 2016
|-
| [[10.7.0-32|10.7.0-32]]
|
| March 14, 2016
| See [[10.7.0-32|this]].
| No
| Yes
| Yes
| Yes (J/U/E)
| Available
| March 14, 2016
|-
| [[11.0.0-33|11.0.0-33]]
|
| May 9, 2016
| See [[11.0.0-33|this]].
| Yes
| No
| Yes
| Yes (J/U/E)
| Available
| May 9, 2016
|-
| [[11.1.0-34|11.1.0-34]]
|
| September 13, 2016
| See [[11.1.0-34|this]].
|
|
|
| Yes (J/U/E)
| Available
| September 13, 2016
|-
| [[11.2.0-35|11.2.0-35]]
|
| October 24, 2016
| See [[11.2.0-35|this]].
|
|
|
| No
| Available
| October 24, 2016
|-
| [[11.3.0-36|11.3.0-36]]
|
| February 6, 2017
| See [[11.3.0-36|this]].
| Yes
| Yes
| Yes
| No
| Available
| February 6, 2017
|-
| [[11.4.0-37|11.4.0-37]]
|
| April 10, 2017
| See [[11.4.0-37|this]].
| Yes
| Yes
| Yes
| No
| Available
| April 10, 2017
|-
| [[11.5.0-38|11.5.0-38]]
|
| July 10, 2017
| See [[11.5.0-38|this]].
|
|
|
| No
| Available
| July 10, 2017
|-
| [[11.6.0-39|11.6.0-39]]
|
| September 18, 2017
| See [[11.6.0-39|this]].
|
|
|
| No
| Available
| September 18, 2017
|-
| [[11.7.0-40|11.7.0-40]]
|
| June 18, 2018
| See [[11.7.0-40|this]].
|
|
|
| No
| Available
| June 18, 2018
|-
| [[11.8.0-41|11.8.0-41]]
|
| July 30, 2018
| See [[11.8.0-41|this]].
|
|
|
| No
| Available
| July 30, 2018
|-
| [[11.9.0-42|11.9.0-42]]
|
| December 3, 2018
| See [[11.9.0-42|this]].
|
|
|
| No
| Available
| December 3, 2018
|-
| [[11.10.0-43|11.10.0-43]]
|
| May 27, 2019
| See [[11.10.0-43|this]].
|
|
|
| No
| Available
| May 27, 2019
|-
| [[11.11.0-43E|11.11.0-43E]]
|
| August 26, 2019
| See [[11.11.0-43E|this]].
|
|
|
| No
| Available
| August 26, 2019
|-
| [[11.12.0-44|11.12.0-44]]
|
| November 4, 2019
| See [[11.12.0-44|this]].
|
|
|
| No
| Available
| November 4, 2019
|-
| [[11.13.0-45|11.13.0-45]]
|
| December 2, 2019
| See [[11.13.0-45|this]].
|
|
|
| No
| Available
| December 2, 2019
|-
| [[11.14.0-46|11.14.0-46]]
|
| November 17, 2020
| See [[11.14.0-46|this]].
|
|
|
| No
| Available
| November 17, 2020
|-
| [[11.15.0-47|11.15.0-47]]
|
| July 27, 2021
| See [[11.15.0-47|this]].
|
|
|
| No
| Available
| July 27, 2021
|-
| [[11.16.0-48|11.16.0-48]]
|
| August 30, 2022
| See [[11.16.0-48|this]].
|
|
|
| No
| Available
| August 30, 2022
|-
| [[11.16.0-49|11.16.0-49]]
|
| September 13, 2022
| See [[11.16.0-49|this]].
|
|
|
| No
| Available
| September 13, 2022
|-
| [[11.17.0-50|11.17.0-50]]
|
| May 23, 2023
| See [[11.17.0-50|this]].
|
|
|
| No
| Available
| May 23, 2023
|}

"[[3DS_System_Flaws|System]]/[[3DS_Userland_Flaws|Userland]] security flaws fixed*": This includes known flaws, and any fixed flaws discovered via code bin-diff.

"[[3DS_System_Flaws|System]]/[[3DS_Userland_Flaws|Userland]] security flaws fixed*" and "3DS-mode homebrew affected" only apply to the changes done with that specific system-update("affected" does not include hax codebases breaking *just* due to updated codebins).

[[Category:Nintendo Software]]

== Auto-Boot Function ==
When the Home Menu is initially loaded by [[NS]], it checks the gamecard ExeFS:/[[SMDH|icon]] for the auto-boot flag. If the auto-boot flag is set, it will load the application on the cartridge and the home menu will not remain running in the background, or at least not in an operational state. Using software cues to return to the home menu, or sleep menu while in this state, causes a shutdown.

Notable features of demo titles:
*Auto-boot demos generally disable the functionality of the home button.
*The ''New Super Mario Bros 2'' demo, retained the functionality of the home button, and had an timer which triggered the demo to quit after a period of inactivity.

Auto-boot cartridges, can bypass some of the functions of the Home Menu. Auto Booted software:
* Doesn't show usage history in the [[Activity Log]]
* Bypasses Parental controls
* Bypasses Forced Game Card Updates
* Bypasses Initial 3DS Setup
* The console does not have a friends list presence.
* Is still subject to region lock(see below).

Region lock is still active, so the home menu will refuse to launch demos with incorrect region lock will not load, displaying "An Error has Occurred". However, game card update partition checks are not done, which allows launching demos that have region free encoding, but have an alternate(or even invalid) region update partition.

The following auto-boot paths can be used by Home Menu, checked in the same order listed below(the above gamecard auto-boot is checked before this):
{| class="wikitable"
! Key-combo / requirements for this path
! Description
|-
| R, L, and X
| This launches [[System Settings]] for touchscreen calibration.
|-
| R, L, and Y
| This launches [[System Settings]] for circlepad calibration.
|}

The following is only checked when the low u16 from [[Config_Savegame|config]] block 0x00110000 is value zero(normally this is non-zero). Thus, the below is only handled when a system setup is required.
{| class="wikitable"
! Key-combo / requirements for this path
! Description
|-
| R, X, Y, A, and B, a 3DS gamecard must be inserted as well.
| This launches the gamecard application. Note that pressing the HOME button in the gamecard application launched this way will only result in the system shutting down.
|-
| This is used when the above path isn't used.
| This launches System Settings for the system setup.
|}

== Region Lockout ==

One of the Home Menu's functions, is to regulate region lockout. The region lockout data for any given title is held in the [[SMDH#BNR Region|ICN data]]. There are 6 regions of which have their own region lockout, Japan, USA, Europe(including Nintendo Australia), China, Taiwan and Korea. There is also a value which makes a title exempt from region lockout, and consequently accessible from any region of 3DS.

The region-field stored in the [[SMDH|ICN-data]] is only checked when Home Menu itself launches a title, not when other titles use NS to have Home Menu launch titles. This isn't actually useful for gamecard region-free however, due to the gamecard system-updates, see below.

Also note that while some gamecard games are mostly region-free(main CXI is identical for all regions of the gamecard), those gamecards can't actually be launched with all 3DS regions due to the gamecard system-update, see below. Note that the main CXI being identical for all regions of a gamecard also means the savedata keyY is identical for all regions of that gamecard too(except for old system-version <v2.2 games, in some cases, due to different cardIDs).

=== Effects of Region Lockout ===
Every 3DS title regardless of location (NAND/SD Card/Game Card) is subject to region lockout scrutiny by the Home Menu. And the home menu treats 'out-of-region' titles by simply refusing to show them on the home menu. No messages are shown on the home menu to notify the user, the title is simply ignored. However out-of-region SD Card titles, will appear and quickly disappear, while all the SD Titles are being processed. In cases where access to the home menu GUI is not needed to launch the title (like in the case of kiosk demos), the home menu states an error has occurred, and launching of the title is stopped.

=== Game Card Updates ===
Either intentionally a region lock mechanism or not, the function which checks the game card update partition returns an error when it is detected the update is for a region other than the 3DS's region (Most likely triggered by the absence of the correct CVer title). And errors returned from checking the update partition, will result in the home menu displaying "This Game Card cannnot be used", when the user attempts to launch the title.

== Home-menu [[SpotPass]] usage ==

Home-menu originally used two domains with HTTPS for SpotPass. SpotPass stores this content in Home-menu's NAND shared extdata.

* The system notifications are downloaded from: <nowiki>https://a248.e.akamai.net/f/248/103046/10m/npdl.c.app.nintendowifi.net/p01/nsa/<regionID>/<filename>/<langcode>/<filename></nowiki> Where langcode is the two-character language codes from [[Config Savegame#Languages|config]], and regionID is from the below table. <filename> is bashoX/sysmsgX where X is 0-3.
* https://pls.c.shop.nintendowifi.net/pl/upload This URL is used for uploading data from the home menu NAND shared extdata, it's unknown what this is used for. This data is uploaded every 24 hours.
* <nowiki>https://npul.c.app.nintendowifi.net/p01/recv/<regionID>/<filename></nowiki> This is used for uploading unknown data from extdata. <filename> can be one of the following:
** "phu"
** "tiu" The POST data contains a list of [[BOSS_Services|BOSS]] taskIDs etc. This seems to be only for Nintendo titles?(system+eShop apps)
** "splu"
** "sendmgn" For this it appears SpotPass does a HTTP POST with data originally from Launcher.dat?

{| class="wikitable"
|-
! Region
! ID
|-
| JPN
| gWr4JXxb2mKTG3lq
|-
| NA
| uuI82221UKkqmtbp
|-
| EUR / Others
| UrXSeurnxhPrq7AS
|}

The SpotPass content payload for notifications begin with a header, followed by an [[SMDH|icon]] and the UTF-16 text, and various metadata.

=== VersionList ===
During startup, Home Menu loads "/versionList.dat" from NAND extdata 0xf000000e. This is downloaded via SpotPass, the file-data downloaded via HTTPS here is raw (no SpotPass container):
* Retail: [https://tagaya-ctr.cdn.nintendo.net/tagaya/versionlist]
* Dev-unit: [https://tagaya-dev-ctr.cdn.nintendo.net/tagaya/versionlist] The titles listed in this are not available on the [[Title list|normal]] CDN.

This is a list of title-updates available on the eShop, for regular app titles and update-titles. This is what Home Menu checks to determine whether the currently selected application needs to be updated or not. When an Internet connection is not available or wifi is disabled, Home Menu will skip VersionList handling/messages when you launch applications.

File structure:
{| class="wikitable"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x10
| The first u32 is normally 0x1, the rest is normally all-zero.
|-
| 0x10
| <Filesize-0x10>
| Title entries, 0x10-bytes each.
|}

Title entry structure:
{| class="wikitable"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x8
| u64 TitleID
|-
| 0x8
| 0x4
| u32 titleversion
|-
| 0xC
| 0x4
| Unknown u32, usually zero?
|}

=== [[BOSS_Services|BOSS]] usage notes ===
Home Menu uses 4 hard-coded NsDataIds: 0x1, 0x2, 0x3, and 0x4, under a loop in the same function for writing to "bashotorya.dat".

== Automatic System Update Download ==
See [[Automatic System Update Download]].

== Home Menu Error Messages ==
{| class="wikitable"
|-
! Dialog Text
! Description
|-
| "An error has occured. Please save your data ... then restart the system"
| This dialog is displayed when a system applet(including Home Menu) crashes/terminates. This dialog is also displayed for system errors as well.
|}

== Home Menu Themes ==
See [[Home_Menu/Themes|here]].

As of [[11.0.0-33]] Home Menu themes are only supported with USA, EUR, and JPN. CHN Home Menu was last updated with v7.0, and TWN doesn't even have a Home Menu settings menu(just the old screen brightness config menu + an [[amiibo Settings]] icon on the right side of the browser icon).

KOR Home Menu doesn't have the theme-settings menu button. While this does have the theme handling code, it isn't actually usable since extdataID 0x0 is used for theme-extdata for non-<JPN/USA/EUR> regions(which is invalid).

== Home Menu [[System_SaveData|NAND]] savedata ==
=== Launcher.dat ===
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x1
| Launcher.dat format version.
|-
| 0x1
| 0x1
| Padding?
|-
| 0x2
| 0x2
| u16, cart launcher position on the home menu
|-
| 0x4
| 0x4
| Unknown, normally 0x0.
|-
| 0x8
| 0xB40
| 360 u64s, list of NAND titleIDs. For an unused entry, the u64 value is ~0(in that case, the corresponding entries at 0xD9A/0x106A for this titleID are not used either). This is used for the icons displayed on the main Home Menu screen.
|-
| 0xB51
| 0x1
| u8, numbers of rows on the home menu, minus 1 (range 0..5) (with the enlarge/reduce option)
|-
| 0xB5C
| 0x2
| u16, position of the cursor on the home menu
|-
| 0xB5E
| 0x2
| u16, horizontal scrolling level (divided by the number of rows to get the actual number of columns hidden) on the home menu
|-
| 0xD80
| 0x2 or 0x4
| u16 or u32, number the next created folder will have (starts at 1)
|-
| 0xD9A
| 0x2D0
| Array of 360 s16 fields, each one corresponds to the titleIDs at the array located at offset 0x8. This is used for icon position, 0x0 for the very first icon, 0x1 for the next one and so on. This is completely linear, no X/Y coordinates. Implemented with the format-version for [[4.0.0-7|4.0.0-X]].
|-
| 0x106A
| 0x168
| Array of 360 s8 fields, each one corresponds to the titleIDs at the array located at offset 0x8. This is used for icon position. When an s8 here is -1(which is the normal value), the icon is located with the first chunk of icons(outbuf+0), otherwise the base address is outbuf+0xB40+<s8val*0x1E0>(which is equivalent to 60 icons * s8val). Implemented with the format-version for [[4.0.0-7|4.0.0-X]]. Corresponds to the id of the folder the icon is in, range -1..59, with -1 meaning not in a folder
|-
| 0x11DC
| 0x78
| Array of 60 s16 fields, corresponding to folders position (with -1 meaning the folder is deleted/not yet created)
|-
| 0x1434
| 0x3C
| Array of 60 u8 fields, the number of rows in each corresponding folder (defaults to 2)
|-
| 0x1470
| 0x78
| Array of 60 u16 fields, the position of the cursor in each corresponding folder (defaults to 0)
|-
| 0x14E8
| 0x78
| Array of 60 u16 fields, the horizontal scroll level in each corresponding folder (divided by the number of rows to get the actual number of columns hidden) (defaults to 0)
|-
| 0x1560
| 0x7F8
| Array of 60 utf-16 strings of length 0x22 (in bytes, so only 0x11 utf-16 characters) (not NULL-terminated), the name of each corresponding folder
|-
| 0x1D58
| 0xF0
| Array of 60 u32, the number of each corresponding folder
|}

== SD ExtData ==
The SD ExtData [[Extdata#Filesystem|File System]] for Home Menu introduced with [[2.0.0-2|2.0.0-X]] is as follows:

root
├── icon
├── boss
└── user
├── SaveData.dat
├── Cache.dat
└── CacheD.dat

{| class="wikitable" border="1"
|-
! File
! Details
! Size
! FW Introduced
! Plaintext
|-
| icon
| Stubbed. Always image 00000002.
| 0x4 Bytes
| n/a
|
|-
| SaveData.dat
| Always image 00000003.
| 0x2cb0 Bytes (0x2da0 starting with [[4.0.0-7]])
| [[2.0.0-2]]
| [https://dl.dropboxusercontent.com/u/60710927/CTR/Sample/HomeMenuExtdata/SaveData.dat Download]
|-
| Cache.dat
| Indexes and records details for the cached icon data. Always image 00000004.
| 0x1688 Bytes
| [[2.0.0-2]]
| [https://dl.dropboxusercontent.com/u/60710927/CTR/Sample/HomeMenuExtdata/Cache.dat Download]
|-
| CacheD.dat
| Cached icon data for Home Menu. Always image 00000005.
| 0x4cfe00 Bytes
| [[2.0.0-2]]
| [https://dl.dropboxusercontent.com/u/60710927/CTR/Sample/HomeMenuExtdata/CacheD.dat Download]
|}

=== Cache.dat & CacheD.dat ===
These two files work in tandem to allow the home menu to cache icon data for applications which are presented on the Home Menu. The size of both files suggests a maximum cache size of 360 icons. Cache.dat stores details about the cache icon data, and CacheD.dat stores the icon data. The icon cache stores icon data for *all* applications shown on the Home Menu, this includes DSi NAND Titles, and DS(i) cartridges. The format of cached DS(i) icon data is not understood, but they are the same size as 3DS icon data (0x36c0).

In Cache.dat the first 8 bytes are a header where the first byte is the format-version, then follows each icon slots's entry in the format:
{| class="wikitable" border="1"
|-
! OFFSET
! SIZE
! DESCRIPTION
|-
| 0x0
| 8
| Title ID in Little Endian
|-
| 0x8
| 4
| Title Version
|-
| 0xc
| 4
| Unknown
|}

All unused entries have the Title IDs filled with "0xff".

In CacheD.dat, the icon data is concatenated together, with the first icon at offset 0x0.

=== SaveData.dat ===
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x1
| SaveData.dat format version.
|-
| 0x8
| 0xB40
| 360 u64s, list of titleIDs(used with icons). Equivalent to the same array in Launcher.dat, but for SD titles.
|-
| 0xB48
| 0x168
| s8 bool array with 360 entries. Some SD-only icon array. Probably an array for each icon present status? Each entry is only known to be set to 0x00 or 0x01, with the former being the default.
|-
| 0xCB0
| 0x2D0
| s16 array with 360 entries, used with icons. Equivalent to the same array in Launcher.dat. Implemented with format-version 2.
|-
| 0xF80
| 0x168
| s8 array with 360 entries, used with icons. Equivalent to the same array in Launcher.dat. Implemented with format-version 2.
|-
| 0x13b8
| 0x8
| Theme entry structure for the regular theme.
|-
| 0x13c0
| 0x8*10(0x50)
| Array of theme entry structures for theme [[9.3.0-21|shuffling]].
|-
| 0x141b
| 0x1
| 0 = one regular theme, 1 = multiple themes for theme [[9.3.0-21|shuffle]].
|}

The icon arrays above are handled exactly the same way as Launcher.dat.

When the theme cache is enabled via the above fields, Home Menu loads the cache at startup(if the used theme structure is valid).

Theme entry structure:
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x4
| Theme index: for DLC this is the content-index, for built-in themes this is an index for an array selecting the built-in theme.
|-
| 0x4
| 0x1
| Normally zero. This is the low 8-bits in the DLC titleID that this theme was originally loaded from.
|-
| 0x5
| 0x1
| Theme type, the valid range is 0..5. 0 = none, 1 = built-in theme from Home Menu RomFS, 2 = theme data loaded from SD cache / content archive. 3 = ?, 4 = ?, 5 = ?
|-
| 0x6
| 0x1
| Normally zero?
|-
| 0x7
| 0x1
| Normally zero?
|}

When the theme-type is value1 the themeindex must be <9. When the theme-type is value2 the themeindex has to be non-zero, and the u8 at offset 0x4 must not be >=10.

The theme-loader code (besides the AM <is-current-themeindex-DLC-installed> code) handles all theme-types >=2 the same way. However, it seems all DLC AM code involving checking the currently-used theme DLC only gets executed when the theme-type is value2. The code in the theme-loader for that also checks that a certain Home Menu state flag is non-zero, before running the AM DLC code(it's unknown where this flag value comes from).

==== SaveData.dat format versions ====
{| class="wikitable" border="1"
|-
! Version value
! Filesize
! Implemented with Home Menu system-version
|-
| 0
| 0x2CB0
| [[2.0.0-2|2.0.0-X]]
|-
| 2
| 0x2DA0
| [[4.0.0-7|4.0.0-X]]
|-
| 3
| 0x2DA0
| [[9.0.0-20|9.0.0-X]]
|-
| 4 (Latest version as of v10.6-v11.0 Home Menu)
| 0x2DA0
| [[9.3.0-21|9.3.0-X]]
|}

The Home Menu code for writing the updated SaveData.dat to FS is broken when the filesize is smaller than expected due to being from an older format-version originally. When writing to the file, Home Menu checks the filesize then attempts to use [[FSFile:SetSize]] on mismatch, but [[FSFile:SetSize]] can't be used with extdata(error from [[FSFile:SetSize]] appears to be ignored). When writing to SaveData.dat the write-size is the one for the current format-version, but since extdata files are fixed-size this will only result in the first {original filesize} bytes being written(result-code = 0xE0E046C1).

Basically, unless the extdata is deleted from the SD card FS manually, the SaveData.dat filesize will never be successfully updated from an old filesize to the current-format filesize by Home Menu.

== Home Menu [[Home_Menu/Themes|Theme]] SD [[Extdata|ExtData]] ==
The filesystem for this extdata is as follows:

root
├── icon
├── boss
└── user
├── ThemeManage.bin
├── BodyCache.bin
├── BgmCache.bin
└── nsalist

{| class="wikitable" border="1"
|-
! File
! Details
! Size
! Extdata image ID
! FW Introduced
! Plaintext
|-
| ThemeManage.bin
| Theme management info. The filesize must match 0x800, otherwise the Home Menu code returns an error.
| 0x800
| 00000003
| [[9.0.0-20]]
|-
| BodyCache.bin
| Contains cached data from the last loaded [[Home_Menu/Themes|theme]] RomFS body_LZ.bin file. The filesize must match 0x150000, otherwise the Home Menu code returns an error.
| 0x150000
| 00000004
| [[9.0.0-20]]
|
|-
| BgmCache.bin
| Contains cached data from the last loaded [[Home_Menu/Themes|theme]] RomFS bgm.bcstm file. The filesize must match 0x337000, otherwise the Home Menu code returns an error.
| 0x337000
| 00000005
| [[9.0.0-20]]
|-
| nsalist
| Contains the list of DLC themes(IDs+prices), downloaded via [[SpotPass]].
|
| 00000007
| [[9.0.0-20]]
|}

BodyCache.bin and BgmCache.bin contain cached theme data for the currently used DLC theme. ThemeManage.bin is loaded by Home Menu during startup. The cached theme data is loaded at startup when a DLC theme is selected. This also contains theme-shop [[SpotPass]] data.

BodyCache.bin and BgmCache.bin are all-zero when no theme is selected.

Starting with [[9.3.0-21|9.3.0-X]] Home Menu can use more files in this extdata, for theme shuffling. "theme:/ThemeManage.bin" "theme:/BgmCache_%02d.bin" "theme:/BodyCache_rd.bin"

=== ThemeManage.bin ===
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x4
| Unknown, normally value 0x1?
|-
| 0x4
| 0x4
| Unknown, normally zero?
|-
| 0x8
| 0x4
| Actual size of the cached body_LZ.bin data.
|-
| 0xC
| 0x4
| Actual size of the cached bgm.bcstm data.
|-
| 0x10
| 0x4
| Unknown
|-
| 0x14
| 0x4
| Unknown
|-
| 0x18
| 0x4
| When a DLC theme is selected, this is the content-index of the DLC theme.
|-
| 0x1C
| 0x4
| Unknown, usually value 0x200 when the data in theme-cache is actually used?
|}

The total filesize is 0x800-bytes, normally the data starting at offset 0x1C is all-zero.

When no theme is actually used, the only non-zero fields are the following: the u32 stored at offset 0x0 in ThemeManage.bin is value 0x1, with offset 0x10 u32 set to value 0x1.

== Home Menu badge SD [[Extdata|ExtData]] ==
The filesystem for this extdata(when it actually exists) is as follows:

root
├── icon
├── boss
└── user
├── BadgeData.dat
└── BadgeMngFile.dat

{| class="wikitable" border="1"
|-
! File
! Details
! Size
! Extdata image ID
! FW Introduced
|-
| BadgeData.dat
| [[Home_Menu#BadgeData.dat|See below.]]
| 0xF4DF80
|
| [[9.0.0-20]]
|-
| BadgeMngFile.dat
| [[Home_Menu#BadgeMngFile.dat|See below.]]
| 0xD4A8
|
| [[9.0.0-20]]
|}

=== BadgeData.dat ===
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 100 * 16 * 0x8A
| UTF-16 Badge Set Titles (16 per set for different languages)
|-
| 0x35E80
| 1000 * 16 * 0x8A
| UTF-16 Badge Titles (16 per set for different languages)
|-
| 0x250F80
| 100 * 0x2000
| [http://en.wikipedia.org/wiki/Z-order_curve Tiled] RGB565 64x64 Badge Set Icons
|-
| 0x318F80
| 1000 * 0x2800
| [http://en.wikipedia.org/wiki/Z-order_curve Tiled] RGB565 64x64 + Tiled A4 64x64 Badge Icons
|-
| 0xCDCF80
| 1000 * 0xA00
| [http://en.wikipedia.org/wiki/Z-order_curve Tiled] RGB565 32x32 + Tiled A4 32x32 Badge Icons
|}

=== BadgeMngFile.dat ===
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x4
| u32, Must Be Zero
|-
| 0x4
| 0x4
| u32, Number of Badge Sets
|-
| 0x8
| 0x4
| u32, Number of Unique Badges
|-
| 0xC
| 0x4
| u32, Number of Placed Badges
|-
| 0x10
| 0x4
| u32, Selected Badge Set in Home Menu (0xFFFFFFFF = All Badges)
|-
| 0x14
| 0x4
| u32, Selected Badge Column in All Badges
|-
| 0x18
| 0x4
| u32, Number of Total Badges
|-
| 0x1C
| 0x4
| u32, Nintendo Network ID Number
|-
| 0x20
| 0x338
| Unknown (always zeros? unused?)
|-
| 0x358
| 0x80
| Used Badge Slots (each bit = 1 slot)
|-
| 0x3D8
| 0x10
| Used Badge Set Slots (each bit = 1 slot)
|-
| 0x3E8
| 1000 * 0x28
| [[Home_Menu#BadgeInfo|BadgeInfo]] Entries
|-
| 0xA028
| 100 * 0x30
| [[Home_Menu#BadgeSetInfo|BadgeSetInfo]] Entries
|-
| 0xB2E8
| 360 * 0x18
| [[Home_Menu#BadgeLayoutSlot|BadgeLayoutSlot]] Entries
|}

==== BadgeIdentifier ====
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x4
| u32, Unknown
|-
| 0x4
| 0x4
| u32, Badge ID
|-
| 0x8
| 0x4
| u32, Badge Set ID
|-
| 0xC
| 0x2
| u16, Badge Index
|-
| 0xE
| 0x2
| u16, Badge Sub ID (used for multi-part badges)

{| class="wikitable" border="1"
! Value
! Meaning
|-
| 0x0
| Badge is a standalone badge
|-
| 0x0100
| Badge is the left piece of a horizontal 2x1 badge
|-
| 0x0101
| Badge is the right piece of a horizontal 2x1 badge
|-
| 0x1000
| Badge is the top piece of a vertical 1x2 badge
|-
| 0x1010
| Badge is the bottom piece of a vertical 1x2 badge
|-
| 0x1100
| Badge is the top left piece of a 2x2 badge
|-
| 0x1101
| Badge is the top right piece of a 2x2 badge
|-
| 0x1110
| Badge is the bottom left piece of a 2x2 badge
|-
| 0x1111
| Badge is the bottom right piece of a 2x2 badge
|}
|}

==== BadgeSetIdentifier ====
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x4
| u32, Unknown (Usually 0xFFFFFFFF)
|-
| 0x4
| 0x4
| u32, Unknown (Usually 0xFFFFFFFF)
|-
| 0x8
| 0x4
| u32, Unknown (Usually 0x0)
|-
| 0xC
| 0x4
| u32, Unknown (Usually 0x2710)
|-
| 0x10
| 0x4
| u32, Badge Set ID
|-
| 0x14
| 0x4
| u32, Badge Set Index
|}

==== BadgeInfo ====
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x10
| [[Home_Menu#BadgeIdentifier|BadgeIdentifier]]
|-
| 0x10
| 0x2
| u16, Number Placed
|-
| 0x12
| 0x2
| u16, Quantity
|-
| 0x14
| 0x4
| u32, Unknown (packed data?)
|-
| 0x18
| 0x10
| u64[2], Shortcut Title ID (twice, once per u64)
|}

==== BadgeSetInfo ====
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x18
| [[Home_Menu#BadgeSetIdentifier|BadgeSetIdentifier]]
|-
| 0x18
| 0x4
| u32, Unknown (usually 0xFFFFFFFF)
|-
| 0x1C
| 0x4
| u32, Number of Unique Badges
|-
| 0x20
| 0x4
| u32, Number of Total Badges
|-
| 0x24
| 0x4
| u32, Start Badge Index
|-
| 0x28
| 0x4
| u32, Unknown (usually 0x0)
|-
| 0x2C
| 0x4
| u32, Unknown (usually 0x0)
|}

==== BadgeLayoutSlot ====
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x10
| [[Home_Menu#BadgeIdentifier|BadgeIdentifier]]
|-
| 0x10
| 0x4
| u32, Position
|-
| 0x14
| 0x4
| u32, Folder (0xF0FF = Icon of a folder, 0xFFFFFFFF = No folder)
|}

The file size must match 0xD4A8, otherwise the Home Menu code returns an error.

== Home Menu theme layout SD [[Extdata|ExtData]] ==
The filesystem for this extdata(when it actually exists) is as follows:

root
├── icon
├── boss
└── user
└── MngFile.dat

{| class="wikitable" border="1"
|-
! File
! Details
! Size
! Extdata image ID
! FW Introduced
! Plaintext
|-
| MngFile.dat
| See below.
| 0x004D1280
| 00000003
| [[9.6.0-24]]
|}

=== MngFile.dat ===
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x4
| u32, must be zero.
|-
| 0x4
| 0xC
| array of 8 u8, 0 if the corresponding layout slot is not set, 1 if it is
|-
| 0xC
| 0x3000 * 8
| Start of the layout entries.
|-
| 0x1800C
| 0xC
| Padding
|-
| 0x18010
| 0x2DA0 * 8
| Start of the [[Home_Menu#SaveData.dat|SaveData.dat]] entries.
|-
| 0x2ED10
| 0xD4A8 * 8
| Start of the [[Home_Menu#BadgeMngFile.dat|BadgeMngFile.dat]] entries.
|-
| 0x99250
| 0x30
| Padding
|-
| 0x99280
| 256*3*8 * 400/8 * 8
| Start of the top screen (400x240) screenshots, in BGR8 tiled format, rotated 90 degrees and with 8 rows per "chunk", and actually 256 pixels wide instead of 240, with the last 16 being all black
|-
| 0x2F1280
| 256*3*8 * 320/8 * 8
| Start of the bottom screen (320x240) screenshots, in BGR8 tiled format, rotated 90 degrees and with 8 rows per "chunk", and actually 256 pixels wide instead of 240, with the last 16 being all black
|}

Layout entries structure:
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x2558
| Exact copy of the entire Home Menu [[System_SaveData]] [[Home_Menu#Launcher.dat|Launcher.dat]], this is the actual layout data.
|-
| 0x2558
| 0xAA8
| Padding
|}

The filesize must match 0x004D1280, otherwise the Home Menu code returns an error. The saved Home Menu layouts are stored here.

When saving a layout, the total layout field is increased, then a new layout entry is created with the contents of the current Home Menu [[System_SaveData]](NAND savedata) Launcher.dat + a screenshot of the main Home Menu screen is written. When loading a layout, Launcher.dat in savedata is written with the current Launcher.dat data already stored in memory(unknown if any data gets changed for it here), then data from the layout entry is copied into the Home Menu [[System_SaveData]] Launcher.dat.

Home Menu *only* accesses this file with the Home Menu layout-settings menu / when entering that menu.

== Home Menu Jump Parameters ==

Parameters can be provided to [[APT:JumpToHomeMenu]] to perform certain actions when jumping to the home menu.

=== Command Header ===
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x4
| Magic Value "ASHP"
|-
| 0x4
| 0x1
| Command ID
|}

If the command requires extra arguments, this header will be padded and the arguments will start at offset 0x8. Otherwise it is just 0x5 bytes large as presented here.

=== Command IDs ===
{| class="wikitable" border="1"
|-
! ID
! Description
! Extra Arguments
|-
| 0x0
| Does Nothing
| None
|-
| 0x1
| Open Instruction Manual
| None
|-
| 0x2
| Download Theme from Theme Shop
| 4-byte ID of the theme (total command size 0xC bytes). This is divided by 1000000 to determine the [[Titles#Title_IDs|title ID variation]], and the remainder corresponds to the theme's DLC content index. If the value is 0 the theme shop will not open correctly, and if the ID isn't valid the theme shop will just return to the home screen after initializing the DLC title.
|-
| 0x3
| Open Badge Picker
| None
|}

== Home Menu startup ==
The following is what Home Menu does at startup(converted from cmd-logs), from [[9.4.0-21]], in the same order Home Menu does it.

Originally Home Menu mounted sdmc in main(), starting(?) with [[6.0.0-11]] Home Menu only has sdmc mounted while handling [[SD_Savedata_Backups]].

{| class="wikitable" border="1"
|-
! Archive
! Filename
! Read size
! Notes
|-
|
|
|
| srv_init(), then srv_GetServiceHandle is used to initialize the service handles for the following services: [[NS_and_APT_Services|ns:s]], [[PTM_Services|ptm:sysm]], and [[Config_Services|cfg:s]].
|-
|
|
|
| [[CfgS:SecureInfoGetByte101]] and [[CfgS:GetLocalFriendCodeSeed]] are used, the output data from these are not used. If either of these return an error, Home Menu uses [[ERR:Throw]].
|-
|
|
|
| [[Cfg:GetSystemModel]] is then used to initialize a Home Menu state field.
|-
|
|
|
| Home Menu then loads the system language via [[CfgS:GetConfigInfoBlk2]], and uses [[Cfg:SecureInfoGetRegion]], to initialize Home Menu region/language state. Home Menu then uses [[Cfg:SecureInfoGetRegion]] again, then loads the [[Config_Savegame|CountryInfo]] via [[CfgS:GetConfigInfoBlk2]].
|-
|
|
|
| Home Menu initializes [[Filesystem_services|fs:USER]] here. Home Menu then mounts the Home Menu CXI RomFS. Then Home Menu uses [[Filesystem_services|FSUSER:GetPriority]].
|-
|
|
|
| Home Menu starts APT initialization / using APT service commands here. Eventually Home Menu then [[NSS:LaunchTitle|launches]] various system-modules.
|-
|
|
|
| Here Home Menu attempts to open NAND shared-[[extdata]] 0xe0000000, which will normally fail since it doesn't exist.
|-
|
|
|
| Here Home Menu uses [[Application_Manager_Services|AM]] command 0x00130040, with input u8 = value 0x0. Home Menu continues using APT commands after this.
|-
|
|
|
| [[HID_Services|hid:SPVR]] service initialization is done here.
|-
|
|
|
| [[PTM_Services|PTMSYSM:GetShellStatus]] is used here.
|-
|
|
|
| [[Filesystem_services|FSUSER:GetCardType]] is used here. AM commands are then used to get the inserted gamecard programID, when successful the gamecard ExeFS:/icon is then read to check the auto-boot flag(see the auto-boot section on this page). The system-setup-required flag is then read here if needed, as mentioned under the auto-boot section of this page.
|-
|
|
|
| Home Menu then uses cfg commands to load system language, region, and CountryInfo.
|-
| Home Menu CXI RomFS
| "/message/<Region>_<Language>/menu_msbt_LZ.bin"
| Presumably loaded from the filesize.
|
|-
| Home Menu CXI RomFS
| "/message/<Region>_<Language>/RI_mstl_LZ.bin"
| Presumably loaded from the filesize.
|
|-
| Home Menu CXI RomFS
| "/message_hud/<Region>_<Language>/hud_msbt_LZ.bin"
| Presumably loaded from the filesize.
|
|-
| Home Menu CXI RomFS
| "/message_hud/<Region>_<Language>/RI_mstl_LZ.bin"
| Presumably loaded from the filesize.
|
|-
|
|
|
| [[NS_and_APT_Services|APT:GetSharedFont]] is used here.
|-
| Home Menu CXI RomFS
| "/font/Hud_JP.bcfnt"
|
|
|-
|
|
|
| Here Home Menu loads the [[Config_Savegame|cfg]] state for blkID 0x50005.
|-
|
|
|
| Here Home Menu loads the GPU shaders from RomFS.
|-
|
|
|
| Here Home Menu does DSP initialization then starts using DSP commands etc + loads sound data from RomFS.
|-
|
|
|
| Here Home Menu does GSP initialization.
|-
|
|
|
| [[APT:GetCaptureInfo]] is used here.
|-
| Home Menu CXI RomFS
|
|
|
|-
|
|
|
| Here Home Menu uses [[PTM_Services|PTMSYSM:GetShellStatus]], [[PTMSYSM:GetSoftwareClosedFlag]], and [[PTMSYSM:ClearSoftwareClosedFlag]]. Home Menu then uses [[PTM_Services|PTMSYSM:GetShellStatus]] 3 times in a row. Starting from here, Home Menu uses [[PTM_Services|PTMSYSM:GetShellStatus]] frequently(presumably from a separate thread).
|-
|
|
|
| Home Menu opens the archive for the Home Menu [[System_SaveData]] here. Then Home Menu attempts to open "/Launcher.dat" for reading, when successful Home Menu just closes the file.
|-
| Home Menu [[System_SaveData]]
| "/Launcher.dat"
| 0x2490
| Prior to doing the read, Home Menu uses [[FSFile:GetSize]].
|-
| System CFA, titleID for USA: 0004009B00013302
| "/country.bin"
|
|
|-
| [[NS CFA]]
| "/ctr_backup_black_list"
|
| Home Menu first reads 0x10-bytes from offset 0x0, then after that it reads the rest of the file.
|-
| Home Menu CXI RomFS
|
|
| Home Menu reads various RomFS files here.
|-
|
|
|
| Home Menu [[NSS:LaunchTitle|launches]] the camera system-module here.
|-
| Home Menu CXI RomFS
|
|
| Home Menu reads various RomFS files here.
|-
| NGWord bad word list CFA
| "/version.dat"
| 0x4
| Home Menu mounts the ngword archive here, then reads version.dat. Home Menu then loads the [[Config_Savegame|cfg]] data for blkID 0x000A0000.
|-
|
|
|
| Home Menu [[NSS:LaunchTitle|launches]] various system-modules here(from a separate thread?).
|-
|
|
|
| Home Menu opens the following NAND shared extdata archives here: 0xf0000001, 0xf0000002, 0xf0000009, 0xf000000b, 0xf000000c, 0xf000000d, and 0xf000000b again.
|-
| NAND [[extdata]] 0xf000000b
| "/ubll.lst"
| 0x2ee0
| Prior to doing the read, Home Menu uses [[FSFile:GetSize]].
|-
|
|
|
| Home Menu opens NAND shared extdata archive 0xf000000b again.
|-
| NAND extdata 0xf000000b
| "/CFL_DB.dat"
| 0xe4c0
| Home Menu only does one read with size 0xe4c0 for this, even though the value it loads from [[FSFile:GetSize]] is larger than that.
|-
| NAND extdata 0xf000000b
| "/CFL_OldDB.dat"
|
| Home Menu just closes this file immediately after opening it, when opening it was successful at least.
|-
|
|
|
| Home Menu loads the [[Config_Savegame|cfg]] data for blkID 0x000C0000 here.
|-
|
|
|
| Home Menu opens NAND shared extdata archive 0xf000000b again.
|-
| NAND extdata 0xf000000b
| [[Extdata|"/gamecoin.dat"]]
| 0x14
| Home Menu first tries to use [[FS:CreateFile]] with this, which will fail when the file already exists. This file is then opened with openflags=RW. After reading this file, Home Menu then uses [[PTM:GetTotalStepCount]], then uses [[FSFile:GetSize]]. Then the service handle for [[NDM_Services|"ndm:u"]] is initialized with srv_GetServiceHandle(done from a separate thread perhaps?). Then Home Menu writes to the already opened gamecoin.dat file.
|-
|
|
|
| [[Filesystem_services|FSUSER:CardSlotIsInserted]] and [[Filesystem_services|FSUSER:GetCardType]] is used here. AM commands are then used to get the inserted gamecard programID, when successful the gamecard ExeFS:/icon is then read.
|-
|
|
|
| [[BOSS_Services|"boss:P"]] service handle initialization with srv_GetServiceHandle is done here. Then [[Services|srv_Subscribe]] is used with various noticationIDs. Home Menu then uses [[FS:IsSdmcDetected]] and [[FS:IsSdmcWritable]]. Home Menu then loads the [[Config_Savegame|cfg]] data for blkID 0x000D0000. Home Menu uses boss:P command 0x4010082, then uses srv_GetServiceHandle for initializing service handles with the following services: [[News_Services|"news:s"]] and "cecd:s".
|-
|
|
|
| srv_GetServiceHandle is used to initialize the service handle for service [[Friend_Services|"frd:a"]], then various service commands are used for that.
|-
| NAND [[extdata]] 0xf000000c
|
|
| Home Menu first attempts to use [[FS:CreateFile]] with "/bashotorya.dat", which normally fails since that file already exists. Home Menu then repeats this with "/bashotorya2.dat".
|-
|
|
|
| Here, Home Menu opens the following SD extdata archives: Home Menu badge SD extdata, Home Menu SD extdata, and the theme-cache SD extdata.
|-
| Home Menu SD extdata
| "/SaveData.dat"
| 0x2da0
| Prior to doing the read, Home Menu uses [[FSFile:GetSize]].
|-
| Home Menu SD extdata
| "/Cache.dat"
| 0x1688
| Prior to doing the read, Home Menu uses [[FSFile:GetSize]].
|-
| Home Menu SD extdata
| "/CacheD.dat"
| 0x36c0
| This is used to read the cached icon data for the currently inserted gamecard, if any. Prior to doing the read, Home Menu uses [[FSFile:GetSize]]. After opening the file and before [[FSFile:GetSize]] is used, Home Menu uses AM commands 0x10070102(for theme DLC) and 0x30084(gamecard "title-listing").
|-
|
|
|
| Home Menu uses the following AM commands for theme DLC here: 0x10050084 and 0x10020104.
|-
| Home Menu Theme SD extdata
| "/BodyCache.bin"
| 0x150000
| Before opening the file, Home Menu firsts opens this archive under a new archive-handle again, then closes it. Prior to doing the read, Home Menu uses [[FSFile:GetSize]].
|-
| Home Menu Theme SD extdata
| "/ThemeManage.bin"
| 0x8
| Prior to doing the read, Home Menu uses [[FSFile:GetSize]](the result is filesize 0x800).
|-
| Home Menu Theme SD extdata
| "/BgmCache.bin"
|
| The data is read from here as needed. After opening the file, Home Menu uses [[FSFile:GetSize]].
|-
|
|
|
| boss:P commands 0x00040000 and 0x04040080 are used here. Home Menu opens NAND shared-extdata 0xf000000e, then closes it when the archive was opened successfully. Then Home Menu uses boss:P command 0x04500102 with the theme extdata, with string "thmtop".
|-
|
|
|
| boss:P command 0x04040080 is used, with the input programID set to the gamecard one. Then boss:P commands 0x000E0000 and 0x00160082 are used.
|-
|
|
|
| [[AMNet:GetTitleIDList|AM:GetTitleIDList]] is used with mediatype=SD and maxTIDs = 0x1c00.
|-
|
|
|
| boss:P command 0x00160082 is used.
|-
|
|
|
| [[PTM_Services|PTM:GetStepHistory]] is used.
|-
|
|
|
| srv_GetServiceHandle is used to initialize the service handle for [[AC_Services|"ac:u"]], then [[AC_Services|ACU:SetClientVersion]] is used. [[Services|srv_Subscribe]] is used, then ACU command 0x002F0004 is used.
|-
|
|
|
| [[AMNet:GetTitleIDList|AM:GetTitleIDList]] is used with mediatype=NAND and maxTIDs = 0x1c00.
|-
| NAND extdata 0xf000000b
| "/gamecoin.dat"
| 0x14
| Home Menu first tries to use FS:CreateFile with this, which will fail when the file already exists. This file is then opened with openflags=RW. After reading this file, Home Menu then uses [[PTM_Services|PTM:GetTotalStepCount]], then uses FSFile:GetSize. Then Home Menu writes to the already opened gamecoin.dat file.

At the same time as doing the above, Home Menu also uses(probably from a different thread) [[AMNet:GetTitleIDList3|AM:GetTitleIDList3]] with mediatype=NAND and maxTIDs=0x2000. Then Home Menu uses [[AMNet:ListTitles|AM:ListTitles]] with the NAND promotional-video titleID. Then Home Menu attempts to open the ExeFS:/icon in the NAND promotional-video title.
|-
| Home Menu [[System_SaveData]]
| "/Launcher.dat"
|
| Prior to doing the write, Home Menu uses [[FSFile:GetSize]]. Home Menu writes 0x2490-bytes to the file here. From a separate thread(?) at the same time, Home Menu also uses [[AM:ReloadDBS]] and AM command 0x00130040 with input=0x1.
|-
|
|
|
| Home Menu loads the u8 value from [[Config_Savegame|cfg]] blkID 0x000E0000 here.
|-
|
|
|
| [[AM:ReloadDBS]], AM command 0x10070102(for theme DLC), AM command 0x00130040, and AM command 0x10050084(for theme DLC) are used here.
At the same time(from a different thread?), the "act:u" service handle is initialized with srv_GetServiceHandle. Then ACTU commands 0x00010084 and 0x000600C2 are used.
|-
|
|
|
| The [[NIM_Services|"nim:u"]] service handle is initialized with srv_GetServiceHandle. Then NIMU commands 0x000F0042, 0x00170042, 0x00150000, and 0x00050000 are used.
|-
|
|
|
| AM command 0x10020104(theme DLC) is used here. Then Home Menu CXI RomFS data is read.
|-
|
|
|
| Home Menu CXI RomFS data is read. [[Filesystem_services|FS:GetSpecialContentIndex]] for the gamecard is used, then MICU initialization is done here(separate thread maybe?).
|-
|
|
|
| [[ACU:GetWifiStatus]] is used, the NAND shared-extdata 0xf000000b archive is then opened here.
|-
| NAND extdata 0xf000000b
| "/idb.dat"
| 0x2008
| This first opens the file for writing, then uses [[FSFile:GetSize]](output filesize is 0x6d4000). Then it writes to the file using size 0, then closes the file. Then [[PTM_Services|PTM:GetStepHistory]] is used. Then Home Menu opens "/idbt.dat", then reads 0x2008-bytes.
|-
|
|
|
| Home Menu starts using [[News_Services|"news:s"]] commands here. While Home Menu is doing this, it also uses(from another thread?) [[NS_and_APT_Services|APT:PrepareToStartNewestHomeMenu]], [[NIM_Services|NIMU:GetState]], and [[NDM_Services|NDMU:OverrideDefaultDaemons]] with input value 0xF.
Later with that news-command code still running, Home Menu also uses the following commands: [[ACU:GetWifiStatus]], [[NDM_Services|NDMU:QueryExclusiveMode]], and CECDS command 0x000E0000. Then [[Config_Savegame|cfg]] blkID 0x000D0000 is loaded.
|-
| NAND extdata 0xf000000b
| "/idbt.dat"
|
| Home Menu writes 0x2008-bytes to this file.
|-
| NAND extdata 0xf000000e
| "/versionList.dat"
| Loaded from the filesize.
|
|-
|
|
|
| boss:P command 0x00200082 is used with string "mmVerDl".
|-
|
|
|
| ...
|-
| Home Menu [[System_SaveData]]
| "/Launcher.dat"
|
| When Home Menu is terminating(?), Home Menu writes 0x2490-bytes to the file here. After doing this, Home Menu opens, writes, and closes the file again.
|}

=== Hardware reboot ===
During Home Menu start-up it uses [[APT:PrepareToStartNewestHomeMenu]]. If that doesn't return an error(normally NS returns 0xC8A0CFFC for that), Home Menu starts a hardware reboot with [[APT:StartNewestHomeMenu]] etc.

On retail this essentially means a hardware-reboot will automatically trigger if [[Configuration_Memory|configmem]] SYSCOREVER doesn't match FIRM_SYSCOREVER, or when the current APPMEMTYPE doesn't match the default APPMEMTYPE for this Old3DS/New3ds model. The latter can happen with running New3DS NATIVE_FIRM with Old3DS system-titles, for example.

== Returning to Home Menu from a crashed application ==
When returning to Home Menu from an application that didn't properly shutdown(like with an exception), PTM module writes data to the PTM system savedata. Then the system terminates Home Menu, and starts Home Menu again.

== See Also ==
* http://www.nintendo.com/consumer/systems/3ds/en_na/menu_update.jsp
* http://www.nintendo.co.jp/netinfo/3ds/JPN/ja.html
* https://yls8.mtheall.com/ninupdates/reports.php

DARC

2026-05-06T10:23:18Z

Gruetzig: might be worth mentioning

[[Category:File formats]]
This page documents the format of DARC.

== Overview ==

DARC files are archives. Containers of files.

This is very similiar to NARC (the DS archives).

== ARC header ==
{| class="wikitable" border="1"
! Offset !! Size !! Type !! Description
|-
| 0x000 || 4 || char[4] || Magic Number 'darc'
|-
| 0x004 || 2 || uint16 || Endianess (=0xFEFF [FF FE]: Little)
|-
| 0x006 || 2 || uint16 || Header's length
|-
| 0x008 || 4 || uint32 || Version
|-
| 0x00C || 4 || uint32 || File's length
|-
| 0x010 || 4 || uint32 || [[DARC#File_table|File table]] offset (from the beginning of the file)
|-
| 0x014 || 4 || uint32 || [[DARC#File_table|File table]] length (includes the names that come after the file structs)
|-
| 0x018 || 4 || uint32 || [[DARC#Files_data|Files data]] offset
|}

=== File table ===

The file table starts at 0x01C.

Each file struct consists of 3 uint32:
{| class="wikitable" border="1"
! Offset !! Size !! Type !! Description
|-
| 0x000 || 4 || uint32 || File name offset (from the end of the table)

if (offset & 0x01000000) then this is a folder (i.e. first two nodes 'null' & '.')
|-
| 0x004 || 4 || uint32 || File offset
|-
| 0x008 || 4 || uint32 || File length
|}

* Folder's length is end-index of the folder in the table.

=Tools=
* [https://github.com/yellows8/darctool]

Filesystem services

2026-01-02T19:53:10Z

Gruetzig: grgre

= Services =
{{Anchor|FS}}{{Anchor|FSUSER}}{{Anchor|fs:USER}}
== Filesystem service "fs:USER" ==
You can at most have 32 FS archive handles.

{| class="wikitable" border="1"
|-
! Command Header
! Available since system version
! Description
! scope="col" width="400" | Required [[NCCH/Extended_Header|exheader]] access info bitmask
|-
| 0x000100C6
|?
| [[FS:Dummy1|Dummy1]]
| None
|-
| 0x040100C4
|?
| [[FS:Control|Control]]
| None
|-
| 0x08010002
|?
| [[FS:Initialize|Initialize]]
| None
|-
| 0x080201C2
|?
| [[FS:OpenFile|OpenFile]]
| None
|-
| 0x08030204
|?
| [[FS:OpenFileDirectly|OpenFileDirectly]]
| None
|-
| 0x08040142
|?
| [[FS:DeleteFile|DeleteFile]]
| None
|-
| 0x08050244
|?
| [[FS:RenameFile|RenameFile]]
| None
|-
| 0x08060142
|?
| [[FS:DeleteDirectory|DeleteDirectory]]
| None
|-
| 0x08070142
|?
| [[FS:DeleteDirectoryRecursively|DeleteDirectoryRecursively]]
| None
|-
| 0x08080202
|?
| [[FS:CreateFile|CreateFile]]
| None
|-
| 0x08090182
|?
| [[FS:CreateDirectory|CreateDirectory]]
| None
|-
| 0x080A0244
|?
| [[FS:RenameDirectory|RenameDirectory]]
| None
|-
| 0x080B0102
|?
| [[FS:OpenDirectory|OpenDirectory]]
| None
|-
| 0x080C00C2
|?
| [[FS:OpenArchive|OpenArchive]]
| Each archive ID code has separate access info bitmasks, if it has any
|-
| 0x080D0144
|?
| [[FS:ControlArchive|ControlArchive]]
| None
|-
| 0x080E0080
|?
| [[FS:CloseArchive|CloseArchive]]
| None
|-
| 0x080F0180
|?
| [[FS:Obsoleted_2_0_FormatThisUserSaveData|Obsoleted_2_0_FormatThisUserSaveData]]
| None
|-
| 0x08100200
|?
| [[FS:Obsoleted_3_0_CreateSystemSaveData|Obsoleted_3_0_CreateSystemSaveData]]
| 0x4, for when the input saveID doesn't match the exheader saveID
|-
| 0x08110040
|?
| [[FS:Obsoleted_3_0_DeleteSystemSaveData|Obsoleted_3_0_DeleteSystemSaveData]]
| 0x1004, for when the input saveID doesn't match the exheader saveID
|-
| 0x08120080
|?
| [[FS:GetFreeBytes|GetFreeBytes]]
| None
|-
| 0x08130000
|?
| [[FS:GetCardType|GetCardType]]
| 0x1017
|-
| 0x08140000
|?
| [[FS:GetSdmcArchiveResource|GetSdmcArchiveResource]]
| None
|-
| 0x08150000
|?
| [[FS:GetNandArchiveResource|GetNandArchiveResource]]
| 0x1007
|-
| 0x08160000
|?
| [[FS:GetSdmcFatfsError|GetSdmcFatfsError]]
| 0x2
|-
| 0x08170000
|?
| [[FS:IsSdmcDetected|IsSdmcDetected]]
| None
|-
| 0x08180000
|?
| [[FS:IsSdmcWritable|IsSdmcWritable]]
| None
|-
| 0x08190042
|?
| [[FS:GetSdmcCid|GetSdmcCid]]
| 0x2
|-
| 0x081A0042
|?
| [[FS:GetNandCid|GetNandCid]]
| 0x2
|-
| 0x081B0000
|?
| [[FS:GetSdmcSpeedInfo|GetSdmcSpeedInfo]]
| 0x2
|-
| 0x081C0000
|?
| [[FS:GetNandSpeedInfo|GetNandSpeedInfo]]
| 0x2
|-
| 0x081D0042
|?
| [[FS:GetSdmcLog|GetSdmcLog]]
| 0x2
|-
| 0x081E0042
|?
| [[FS:GetNandLog|GetNandLog]]
| 0x2
|-
| 0x081F0000
|?
| [[FS:ClearSdmcLog|ClearSdmcLog]]
| 0x2
|-
| 0x08200000
|?
| [[FS:ClearNandLog|ClearNandLog]]
| 0x2
|-
| 0x08210000
|?
| [[FS:CardSlotIsInserted|CardSlotIsInserted]]
| 0x1017
|-
| 0x08220000
|?
| [[FS:CardSlotPowerOn|CardSlotPowerOn]]
| 0x2
|-
| 0x08230000
|?
| [[FS:CardSlotPowerOff|CardSlotPowerOff]]
| 0x2
|-
| 0x08240000
|?
| [[FS:CardSlotGetCardIFPowerStatus|CardSlotGetCardIFPowerStatus]]
| 0x2
|-
| 0x08250040
|?
| [[FS:CardNorDirectCommand|CardNorDirectCommand]]
| 0x2
|-
| 0x08260080
|?
| [[FS:CardNorDirectCommandWithAddress|CardNorDirectCommandWithAddress]]
| 0x2
|-
| 0x08270082
|?
| [[FS:CardNorDirectRead|CardNorDirectRead]]
| 0x2
|-
| 0x082800C2
|?
| [[FS:CardNorDirectReadWithAddress|CardNorDirectReadWithAddress]]
| 0x2
|-
| 0x08290082
|?
| [[FS:CardNorDirectWrite|CardNorDirectWrite]]
| 0x2
|-
| 0x082A00C2
|?
| [[FS:CardNorDirectWriteWithAddress|CardNorDirectWriteWithAddress]]
| 0x2
|-
| 0x082B00C2
|?
| [[FS:CardNorDirectRead_4xIO|CardNorDirectRead_4xIO]]
| 0x2
|-
| 0x082C0082
|?
| [[FS:CardNorDirectCpuWriteWithoutVerify|CardNorDirectCpuWriteWithoutVerify]]
| 0x2
|-
| 0x082D0040
|?
| [[FS:CardNorDirectSectorEraseWithoutVerify|CardNorDirectSectorEraseWithoutVerify]]
| 0x2
|-
| 0x082E0040
|?
| [[FS:GetProductInfo|GetProductInfo]]
| 0x1005
|-
| 0x082F0040
|?
| [[FS:GetProgramLaunchInfo|GetProgramLaunchInfo]]
| 0x1005
|-
| 0x08300182
|?
| [[FS:Obsoleted_3_0_CreateExtSaveData|Obsoleted_3_0_CreateExtSaveData]]
| 0xC, for when the input extdataID doesn't match the exheader extdataID
|-
| 0x08310180
|?
| [[FS:Obsoleted_3_0_CreateSharedExtSaveData|Obsoleted_3_0_CreateSharedExtSaveData]]
| 0x1005
|-
| 0x08320102
|?
| [[FS:Obsoleted_3_0_ReadExtSaveDataIcon|Obsoleted_3_0_ReadExtSaveDataIcon]]
| 0x100D, for when the input extdataID doesn't match the exheader extdataID
|-
| 0x08330082
|?
| [[FS:Obsoleted_3_0_EnumerateExtSaveData|Obsoleted_3_0_EnumerateExtSaveData]]
| 0x1005
|-
| 0x08340082
|?
| [[FS:Obsoleted_3_0_EnumerateSharedExtSaveData|Obsoleted_3_0_EnumerateSharedExtSaveData]]
| 0x1005
|-
| 0x08350080
|?
| [[FS:Obsoleted_3_0_DeleteExtSaveData|Obsoleted_3_0_DeleteExtSaveData]]
| 0x100D, for when the input extdataID doesn't match the exheader extdataID
|-
| 0x08360080
|?
| [[FS:Obsoleted_3_0_DeleteSharedExtSaveData|Obsoleted_3_0_DeleteSharedExtSaveData]]
| 0x1005
|-
| 0x08370040
|?
| [[FS:SetCardSpiBaudRate|SetCardSpiBaudRate]]
| 0x2
|-
| 0x08380040
|?
| [[FS:SetCardSpiBusMode|SetCardSpiBusMode]]
| 0x2
|-
| 0x08390000
|?
| [[FS:SendInitializeInfoTo9|SendInitializeInfoTo9]]
| None
|-
| 0x083A0100
|?
| [[FS:GetSpecialContentIndex|GetSpecialContentIndex]]
| 0x1005
|-
| 0x083B00C2
|?
| [[FS:GetLegacyRomHeader|GetLegacyRomHeader]]
| 0x1015
|-
| 0x083C00C2
|?
| [[FS:GetLegacyBannerData|GetLegacyBannerData]]
| 0x1015
|-
| 0x083D0100
|?
| [[FS:CheckAuthorityToAccessExtSaveData|CheckAuthorityToAccessExtSaveData]]
| 0x44
|-
| 0x083E00C2
|?
| [[FS:QueryTotalQuotaSize|QueryTotalQuotaSize]]
| None
|-
| 0x083F00C0
|?
| [[FS:Obsoleted_3_0_GetExtDataBlockSize|Obsoleted_3_0_GetExtDataBlockSize]]
| None
|-
| 0x08400040
|?
| [[FS:AbnegateAccessRight|AbnegateAccessRight]]
|?
|-
| 0x08410000
|?
| [[FS:DeleteSdmcRoot|DeleteSdmcRoot]]
| 0x1005
|-
| 0x08420040
|?
| [[FS:DeleteAllExtSaveDataOnNand|DeleteAllExtSaveDataOnNand]]
| 0x1005
|-
| 0x08430000
|?
| [[FS:InitializeCtrFileSystem|InitializeCtrFileSystem]]
| None
|-
| 0x08440000
|?
| [[FS:CreateSeed|CreateSeed]]
| 0x2
|-
| 0x084500C2
|?
| [[FS:GetFormatInfo|GetFormatInfo]]
|?
|-
| 0x08460102
|?
| [[FS:GetLegacyRomHeader2|GetLegacyRomHeader2]]
| 0x1015
|-
| 0x08470180
|?
| [[FS:Obsoleted_2_0_FormatCtrCardUserSaveData|Obsoleted_2_0_FormatCtrCardUserSaveData]]
| 0x6
|-
| 0x08480042
|?
| [[FS:GetSdmcCtrRootPath|GetSdmcCtrRootPath]]
| 0x100D
|-
| 0x08490040
|?
| [[FS:GetArchiveResource|GetArchiveResource]]
|?
|-
| 0x084A0002
|?
| [[FS:ExportIntegrityVerificationSeed|ExportIntegrityVerificationSeed]]
| 0x4000
|-
| 0x084B0002
|?
| [[FS:ImportIntegrityVerificationSeed|ImportIntegrityVerificationSeed]]
| 0x4000
|-
| 0x084C0242
|?
| [[FS:FormatSaveData|FormatSaveData]]
| 0x6, in some cases this write isn't needed however
|-
| 0x084D0102
|?
| [[FS:GetLegacySubBannerData|GetLegacySubBannerData]]
| 0x1015
|-
| 0x084E0342
|?
| [[FS:UpdateSha256Context|UpdateSha256Context]]
| 0x5
|-
| 0x084F0102
|?
| [[FS:ReadSpecialFile|ReadSpecialFile]]
| None
|-
| 0x08500040
|?
| [[FS:GetSpecialFileSize|GetSpecialFileSize]]
| None
|-
| 0x08510242
| [[3.0.0-5]]
| [[FS:CreateExtSaveData|CreateExtSaveData]]
| Shared extdata: 0x101005. Regular extdata in certain cases: 0xC
|-
| 0x08520100
| [[3.0.0-5]]
| [[FS:DeleteExtSaveData|DeleteExtSaveData]]
| Shared extdata: 0x101005. Regular extdata in certain cases: 0x10100D
|-
| 0x08530142
| [[3.0.0-5]]
| [[FS:ReadExtSaveDataIcon|ReadExtSaveDataIcon]]
| 0x10100D (this doesn't apply in certain cases, however)
|-
| 0x08540100
| [[3.0.0-5]]
| [[FS:GetExtDataBlockSize|GetExtDataBlockSize]]
| 0x10100D (this doesn't apply in certain cases, however)
|-
| 0x08550102
| [[3.0.0-5]]
| [[FS:EnumerateExtSaveData|EnumerateExtSaveData]]
| 0x101005
|-
| 0x08560240
| [[3.0.0-5]]
| [[FS:CreateSystemSaveData|CreateSystemSaveData]]
| 0x4 (this doesn't apply in certain cases, however)
|-
| 0x08570080
| [[3.0.0-5]]
| [[FS:DeleteSystemSaveData|DeleteSystemSaveData]]
| 0x1004 (this doesn't apply in certain cases, however)
|-
| 0x08580000
| [[3.0.0-5]]
| [[FS:StartDeviceMoveAsSource|StartDeviceMoveAsSource]]
| 0x2004
|-
| 0x08590200
| [[3.0.0-5]]
| [[FS:StartDeviceMoveAsDestination|StartDeviceMoveAsDestination]]
| 0x2004
|-
| 0x085A00C0
| [[3.0.0-5]]
| [[FS:SetArchivePriority|SetArchivePriority]]
| None
|-
| 0x085B0080
| [[3.0.0-5]]
| [[FS:GetArchivePriority|GetArchivePriority]]
| None
|-
| 0x085C00C0
| [[3.0.0-5]]
| [[FS:SetCtrCardLatencyParameter|SetCtrCardLatencyParameter]]
| 0xE
|-
| 0x085D01C0
| [[3.0.0-5]]
| [[FS:SetFsCompatibilityInfo|SetFsCompatibilityInfo]]
| 0x100001
|-
| 0x085E0040
| [[3.0.0-5]]
| [[FS:ResetCardCompatibilityParameter|ResetCardCompatibilityParameter]]
| 0xE
|-
| 0x085F0040
| [[3.0.0-5]]
| [[FS:SwitchCleanupInvalidSaveData|SwitchCleanupInvalidSaveData]]
| 0x12004
|-
| 0x08600042
| [[3.0.0-5]]
| [[FS:EnumerateSystemSaveData|EnumerateSystemSaveData]]
| 0x2004
|-
| 0x08610042
| [[3.0.0-5]]
| [[FS:InitializeWithSdkVersion|InitializeWithSdkVersion]]
| None
|-
| 0x08620040
| [[3.0.0-5]]
| [[FS:SetPriority|SetPriority]]
| None
|-
| 0x08630000
| [[3.0.0-5]]
| [[FS:GetPriority|GetPriority]]
| None
|-
| 0x08640000
| [[3.0.0-5]]
| [[FS:Obsoleted_4_0_GetNandInfo|Obsoleted_4_0_GetNandInfo]]
| Stubbed, this returns an error
|-
| 0x08650140
| [[4.0.0-7]]
| [[FS:SetSaveDataSecureValue|SetSaveDataSecureValue]]
| 0x121004 (in certain cases this doesn't apply, however)
|-
| 0x086600C0
| [[4.0.0-7]]
| [[FS:GetSaveDataSecureValue|GetSaveDataSecureValue]]
| 0x121004 (in certain cases this doesn't apply, however)
|-
| 0x086700C4
| [[4.0.0-7]]
| [[FS:ControlSecureSave|ControlSecureSave]]
| 0x121004
|-
| 0x08680000
| [[4.0.0-7]]
| [[FS:GetMediaType|GetMediaType]]
| None
|-
| 0x08690000
| [[4.0.0-7]]
| [[FS:Obsoleted_4_0_GetNandEraseCount|Obsoleted_4_0_GetNandEraseCount]]
| Stubbed, this returns an error.
|-
| 0x086A0082
| [[4.0.0-7]]
| [[FS:ReadNandReport|ReadNandReport]]
| None
|-
| 0x086B00C2
|?
| [[FS:SetOtherSaveDataSecureValue|SetOtherSaveDataSecureValue]]
| 0x121004
|-
| 0x086C00C2
|?
| [[FS:GetOtherSaveDataSecureValue|GetOtherSaveDataSecureValue]]
| 0x121004
|-
| 0x086D0080
|?
| [[FS:BeginSaveDataMove|BeginSaveDataMove]]
| 0x20004
|-
| 0x086E00C0
|?
| [[FS:SetThisSaveDataSecureValue|SetThisSaveDataSecureValue]]
|None
|-
| 0x086F0040
|?
| [[FS:GetThisSaveDataSecureValue|GetThisSaveDataSecureValue]]
| None
|-
| 0x087000C2
|?
| [[FS:CheckArchive|CheckArchive]]
|None
|-
| 0x08710140
| ?
| [[FS:TransferSaveDataCMAC|TransferSaveDataCMAC]]
| 0x20004
|-
| 0x08720200
|?
| [[FS:RegisterTitleContentOverlay|RegisterTitleContentOverlay]]
| 0x80004
|-
| 0x08730100
|?
| [[FS:UnregisterTitleContentOverlay|UnregisterTitleContentOverlay]]
| 0x80004
|-
| 0x08740000
|?
| [[FS:UnregisterAllTitleContentOverlays|UnregisterAllTitleContentOverlays]]
| 0x80004
|-
| 0x08750140
|?
| [[FS:SetSaveArchiveSecureValue|SetSaveArchiveSecureValue]]
|None
|-
| 0x087600C0
|?
| [[FS:GetSaveArchiveSecureValue|GetSaveArchiveSecureValue]]
|None
|-
| 0x08770140
|?
| [[FS:RegisterSpecialTitleContent|RegisterSpecialTitleContent]]
| 0x80004
|-
| 0x08780100
|?
| [[FS:UnregisterSpecialTitleContent|UnregisterSpecialTitleContent]]
| 0x80004
|-
| 0x087900C2
| ?
| Same as [[FS:GetLegacyBannerData|GetLegacyBannerData]], except for the last parameter this internally passes u8 value 0x1 instead of 0x0, for the FSPXI command.
| 0x101015
|-
| 0x087A0180
| [[9.6.0-24|9.6.0-X]]
| [[FS:AddSeed|AddSeed]]
| 0x200000
|-
| 0x087B0080
| [[9.6.0-24|9.6.0-X]]
| [[FS:GetSeed|GetSeed]]
| 0x200000
|-
| 0x087C0080
| [[9.6.0-24|9.6.0-X]]
| [[FS:DeleteSeed|DeleteSeed]]
| 0x200000
|-
| 0x087D0000
| [[9.6.0-24|9.6.0-X]]
| [[FS:GetNumSeeds|GetNumSeeds]]
| 0x200000
|-
| 0x087E0042
| [[9.6.0-24|9.6.0-X]]
| [[FS:ListSeeds|ListSeeds]]
| 0x200000
|-
| 0x087F0100
| [[9.6.0-24|9.6.0-X]]
| [[FS:TitleContentHasSeed|TitleContentHasSeed]]
| 0x200000
|-
| 0x08800880
| [[9.6.0-24|9.6.0-X]]
| [[FS:AddTitleTag|AddTitleTag]]
| 0x200000
|-
| 0x08810080
| [[9.6.0-24|9.6.0-X]]
| [[FS:GetTitleTag|GetTitleTag]]
| 0x200000
|-
| 0x08820080
| [[9.6.0-24|9.6.0-X]]
| [[FS:DeleteTitleTag|DeleteTitleTag]]
| 0x200000
|-
| 0x08830000
| [[9.6.0-24|9.6.0-X]]
| [[FS:GetNumTitleTags|GetNumTitleTags]]
| 0x200000
|-
| 0x08840042
| [[9.6.0-24|9.6.0-X]]
| [[FS:ListTitleTags|ListTitleTags]]
| 0x200000
|-
| 0x088500C0
| [[9.6.0-24|9.6.0-X]]
| [[FS:CheckTitleSeed|CheckTitleSeed]]
| 0x200000
|-
| 0x088600C0
| [[11.1.0-34|11.1.0-X]]
| [[FS:CheckUpdatedDat|CheckUpdatedDat]]
| 0x80000
|}

Note: The question marks from Dummy1 to GetSpecialFileSize on the "available since system version" field are mainly there because I think that most of these are necessary for the main system to function, so theoretically that would mean that since the creation of the 3DS these were available, or since launch if that makes more sense. But because of the peculiar nature of some of the functions, they will remain question marks until they can be confirmed 100%.

When access rights are required for a command, at least one of the bits in the process access info specified in the above table for the command must be set. Error 0xD9004676 is returned when a process attempts to use a command which it doesn't have access rights for the command. The exheader access info field is all zero's for most applications. Note that the permissions listed in the above table is for system-version v2.x, therefore permission bit(s) added with newer FIRM may be missing from this.

Each session for fs:USER has separate permissions, initially these are set to all zero's for new fs:USER sessions. The permissions/etc for fs:USER sessions are initialized via [[FS:Initialize]](loaded from the user process exheader).

{{Anchor|FSLDR}}{{Anchor|fs:LDR}}

== Filesystem service "fs:LDR" ==
This service is identical to fs:USER, except [[FS:OpenArchive]] archive 0x2345678E can only be accessed with fs:LDR.

{{Anchor|FSReg}}{{Anchor|FSREG}}{{Anchor|fs:REG}}
== ProgramRegistry service "fs:REG" ==
{| class="wikitable" border="1"
|-
! Command Header
! Description
|-
| 0x000100C6
| [[FSReg:Dummy1|Dummy1]]
|-
| 0x040103C0
| [[FSReg:Register|Register]]
|-
| 0x04020040
| [[FSReg:Unregister|Unregister]]
|-
| 0x040300C0
| [[FSReg:GetProgramInfo|GetProgramInfo]]
|-
| 0x04040100
| [[FSReg:LoadProgram|LoadProgram]]
|-
| 0x04050080
| [[FSReg:UnloadProgram|UnloadProgram]]
|-
| 0x04060080
| [[FSReg:CheckHostLoadId|CheckHostLoadId]]
|}

Only two sessions can be opened for this service at a time, hence no other processes can use this due to [[Process_Manager_Services|pm-module]] and [[Loader_Services|loader]] using this.

=File and directory access=
==Files==
File session handles obtained via [[FS:OpenFile]] and [[FS:OpenFileDirectly]] can be used to access files through a service-like interface, despite not being an actual service registered using [[SRV:RegisterService]]. To use this service-like interface, simply call the SendSyncRequest SVC with a file session handle, using the IPC buffer in thread-local storage for parameters and responses, just like you would with a proper service.

{| class="wikitable" border="1"
|-
! Command Header
! Description
|-
| 0x000100C6
| [[FSFile:Dummy1|Dummy1]]
|-
| 0x040100C4
| [[FSFile:Control|Control]]
|-
| 0x08010100
| [[FSFile:OpenSubFile|OpenSubFile]]
|-
| 0x080200C2
| [[FSFile:Read|Read]]
|-
| 0x08030102
| [[FSFile:Write|Write]]
|-
| 0x08040000
| [[FSFile:GetSize|GetSize]]
|-
| 0x08050080
| [[FSFile:SetSize|SetSize]]
|-
| 0x08060000
| [[FSFile:GetAttributes|GetAttributes]]
|-
| 0x08070040
| [[FSFile:SetAttributes|SetAttributes]]
|-
| 0x08080000
| [[FSFile:Close|Close]]
|-
| 0x08090000
| [[FSFile:Flush|Flush]]
|-
| 0x080A0040
| [[FSFile:SetPriority|SetPriority]]
|-
| 0x080B0000
| [[FSFile:GetPriority|GetPriority]]
|-
| 0x080C0000
| [[FSFile:OpenLinkFile|OpenLinkFile]]
|-
| 0x0C010100
| [[FSFile:GetAvailable|GetAvailable]]
|}

==Directories==
Directory session handles obtained via [[FS:OpenDirectory]] are usable via a service-like interface, following the exact same procedure described above for file sessions.
{| class="wikitable" border="1"
|-
! Command Header
! Available since system version
! Description
|-
| 0x000100C6
| [[1.0.0-0]]
| [[FSDir:Dummy1|Dummy1]]
|-
| 0x040100C4
| [[1.0.0-0]]
| [[FSDir:Control|Control]]
|-
| 0x08010042
| [[1.0.0-0]]
| [[FSDir:Read|Read]]
|-
| 0x08020000
| [[1.0.0-0]]
| [[FSDir:Close|Close]]
|-
| 0x08030040
| ?
| [[FSDir:SetPriority|SetPriority]]
|-
| 0x08040000
| ?
| [[FSDir:GetPriority|GetPriority]]
|}

= Archives =
{| class="wikitable" border="1"
|-
! ArchiveId
! Description
! Accessible via [[Filesystem_services|FS]]
! Accessible via [[Filesystem_services_PXI|FSPXI]]
! Only accessible by Process9 internally
! Requires binary [[FS:OpenFile|Lowpath]]
! Required exheader FS access info bitmask
|-
| 0x00000003
| SelfNCCH (including [[#RomFS|RomFS]])
| Yes
| No
| No
| No
| None
|-
| 0x00000004
| SaveData (the saveID/mediatype for this is loaded from data originally from the user process' exheader)
| Yes
| No
| No
| No
| None
|-
| 0x00000006
| ExtSaveData
| Yes
| No
| No
| Yes
| 0x100D, when the input extdataID isn't listed in the exheader.
|-
| 0x00000007
| Shared ExtSaveData
| Yes
| No
| No
| Yes
| None
|-
| 0x00000008
| SystemSaveData
| Yes
| No
| No
| Yes
| 0x4, when the input saveID doesn't match the exheader system-saveID.
|-
| 0x00000009
| SDMC
| Yes
| Yes
| No
| No
| 0x8E
|-
| 0x0000000A
| SDMC Write-Only
| Yes
| No
| No
| No
| 0x808E
|-
| 0x12345678
| ExtSaveData for BOSS
| Yes
| No
| No
| Yes
| 0x44
|-
| 0x12345679
| CARD SPI FS
| Yes
| Yes
| No
| No
| 0x16
|-
| 0x1234567B
| ExtSaveData, and ExtSaveData for BOSS
| No
| Yes
| No
| Yes
|
|-
| 0x1234567C
| SystemSaveData
| No
| Yes
| No
| Yes
|
|-
| 0x1234567D
| NAND RW
| Yes
| Yes
| No
| No
| 0x800
|-
| 0x1234567E
| NAND RO
| Yes
| Yes
| No
| No
| 0x200
|-
| 0x1234567F
| NAND RO Write FS
| No
| Yes
| No
| No
| ?
|-
| 0x12345680
| Extdata transfer. Used for transferring [[Extdata#NAND_Shared_Extdata|NAND Shared Extdata]] during [[System_Transfer#System_Save_Data_/_Shared_Extdata_Transfer|system tranfers]].
| Yes
| Yes
| No
| Yes
| ?
|-
| 0x12345681
| System Savedata transfer. Used for transferring [[System_SaveData|System Save Data]] during [[System_Transfer#System_Save_Data_/_Shared_Extdata_Transfer|system tranfers]].
| Yes
| Yes
| No
| Yes
| ?
|-
| 0x12345682
| Unknown. There's code for this in spider v9.9, but that code isn't actually used.
| Yes
| No
| No
| Yes
| ?
|-
| 0x2345678A
| Title access. With FS, this allows accessing NCCH/NCSD contents (ExeFS, RomFS, checking if a content uses a seed, checking the validity of the installed seed). FSPXI, additionally, allows opening raw NCCH/NCSD NCCH contents and DSiWare contents for reading, along with encrypted save data.
| Yes
| Yes
| No
| Yes
| 0x1005
|-
| 0x2345678B
| Used internally by Process9 as the lowest level title access archive. Allows for opening various sections of a title (TMD, CMD, raw contents, DLC contents, raw save data (including public/private/banner saves for DSiWare), title and/or content import context files and /data directories for save data.
| No
| No
| Yes
| Yes
|
|-
| 0x2345678C
| Used internally to access [[Title_Database|Title Database (/dbs)]] files. For SD, <code>title.db</code> and <code>import.db</code>. For NAND, <code>title.db</code>, <code>import.db</code>, <code>tmp_t.db</code>, <code>tmp_i.db</code>, and <code>jumpid.db</code>.
| No
| No
| Yes
| Yes
|
|-
| 0x2345678D
| Used internally to access non-title /dbs files on the NAND: <code>certs.db</code> and <code>ticket.db</code>.
| No
| No
| Yes
| No
|
|-
| 0x2345678E
| FSPXI: Program Access (limited subset of merged main title + update/patch title access). For fs:LDR(used by the "loader" FIRM ARM11-process), only <code>exefs:/.code</code>. Not accessible with fs:USER.
| Yes
| Yes
| No
| Yes
| None, see description.
|-
| 0x567890AB
| NAND CTR FS
| No
| Yes
| No
| No
| ?
|-
| 0x567890AC
| TWL PHOTO
| Yes
| Yes
| No
| No
| ?
|-
| 0x567890AD
| TWLS (DSi Sound stores recordings here). This is mapped to the FAT12 image stored in the file at [[Twln/shared2/0000]].
| No
| Yes
| No
| No
| ?
|-
| 0x567890AE
| NAND TWL FS
| Yes
| Yes
| No
| No
| 0x100
|-
| 0x567890AF
| NAND W FS
| Yes
| Yes
| No
| No
| 0x100
|-
| 0x567890B0
| Internally creates the same "ID Storage" wrapper over the NAND that is used for SystemSaveData and Shared ExtData, but all operations are stubbed and return 0xE0C046F8.
| No
| Yes
| No
| No
|
|-
| 0x567890B1
| Gamecard SaveData (for check). This is a wrapper for UserSaveDataForCheck: the OpenArchive code for that is called with archive-lowpath TID=0/mediatype=2(gamecard).
| Yes
| No
| No
| No
| 0x6
|-
| 0x567890B2
| UserSaveData (for check). This is the same as the regular SaveData archive, except with this the savedata ID and mediatype is loaded from the input archive lowpath.
| Yes
| No
| No
| Yes
| 0x6
|-
| 0x567890B3
| [[3DS_Virtual_Console#NAND_Savegame|AGB Save Data]]
| No
| No
| Yes
| No
| -
|-
| 0x567890B4
| Similar to 0x567890B2 but can only access Accessible Save specified in [[NCCH/Extended_Header#Storage_Info|exheader]]?
| Yes
| No
| No
| Yes
| ?
|}

Archives listed as not requiring a binary lowpath, use lowpath type [[FS:OpenFile|empty]].

The above permission bitmasks are from v2.x, see the above Services section for how these are handled.

Archives CTR NAND, NAND RO Write FS, TWL NAND, NAND W FS, and CARD SPI FS require the corresponding process exheader access control mount flag to be set, in the exheader for any of the currently running ARM11 processes, for [[Filesystem_services_PXI|FSPXI]]. The access rights checked by [[Filesystem services|FS]] module for archive mounting with fs:USER, are stored in the process' exheader accessinfo.

The CARDSPI archive allows access to the gamecard CARD1 raw savedata flash(aka "cardspi:/" in [[FIRM|Process9]]), the file lowpath must be WCHAR "/". The "NAND W FS" archive allows access to the raw NAND image(aka "wnand:/" in Process9), the file lowpath must be WCHAR "/".

= Filenames and Paths =
{{Anchor|PathType}}
==PathType==
{| class="wikitable" border="1"
|-
! Value
! Description
|-
| -1
| Returned internally by Process9, when errors occur it seems(in particular when no nul-terminator was found in the input path). The data ptr is set to NULL.
|-
| 0x0
| INVALID - Specifies an invalid path
|-
| 0x1
| EMPTY - Specifies an empty path
|-
| 0x2
| BINARY - Non-text based path. Meaning is per-archive
|-
| 0x3
| ASCII - Text-based path with 7-bit ASCII characters padded to 8-bits each (signed char)
|-
| 0x4
| UTF16 - Text-based path with UTF-16 characters
|}

In IPC requests, sizes of ASCII and UTF16 paths must include space for the null-terminator.

== Binary LowPath ==
The format of the data that a binary LowPath points to is custom per archive.

=== SystemSaveData / Extdata / Shared Extdata Archive Path Data Format ===

==== DataAccessPath ====

{| class="wikitable" border="1"
|-
! Offset !! Size !! Description
|-
| 0x0 || 0x1 || u8 [[Mediatypes|Mediatype]]
|-
| 0x1 || 0x1 || only for NAND data (System Savedata / Shared Extdata), otherwise left 0:
{| class="wikitable" border="1"
|-
! Value !! Description
|-
| 0 || Accesses from/to <code>nand:/data/<ID0 of current system></code>
|-
| 1 || Accesses from/to <code>nand:/fixdata</code>
|-
| 2 || Accesses from/to <code>nand:/data/<ID0 from [[Filesystem_services#DeviceMoveContext|Device Move Context]]></code>
|}
|-
| 0x2 || 0x2 || padding
|}

==== SystemSaveData ====

===== FS =====

====== Archive Path ======
{| class="wikitable" border="1"
|-
! Index word
! Description
|-
| 0
| [[Filesystem_services#DataAccessPath|DataAccessPath]]
|-
| 1
| save ID low (save ID high is 0)
|}

====== File Path ======
The file path is a cleartext ASCII or UTF16 file path (<code><file path></code>).

The file path would access the file at <code><base path>/sysdata/<save ID low>/<save ID high>/<file path></code>.
Note that <code>/<file path></code> refers to the virtual file system inside the </code><save ID high></code> file.

===== FSPXI / FS System Savedata Transfer / FSPXI System Savedata Transfer =====

====== Archive Path ======
{| class="wikitable" border="1"
|-
! Index word
! Description
|-
| 0
| [[Filesystem_services#DataAccessPath|DataAccessPath]]
|}

====== File Path ======
{| class="wikitable" border="1"
|-
! Index word !! Description
|-
| 0 || save ID low
|-
| 1 || save ID high
|}

The file path would access the file at <code><base path>/sysdata/<save ID low>/<save ID high></code>.

==== Extdata / Shared Extdata ====

===== FS / FS Extdata Transfer / FSPXI Extdata Transfer =====

====== Archive Path ======
{| class="wikitable" border="1"
|-
! Index word
! Description
|-
| 0
| [[Filesystem_services#DataAccessPath|DataAccessPath]]
|-
| 1
| ext save ID low
|-
| 2
| ext save ID high
|}

This refers to the extdata filesystem structure's base directory at <code><base path>/extdata/<ext save ID low>/<ext save ID high></code>.

====== File Path ======
The file path is a cleartext ASCII or UTF16 file path (<code><file path></code>).

For FS Extdata, this would acccess <code><base path>/extdata/<save ID low>/<save ID high>/<directory ID>/<file ID>/<file path></code>, and <code>/<file path></code> refers to the virtual file system inside the </code><file ID></code> file.

For FS / FSPXI Extdata Transfer, this accesses <code><base path>/extdata/<save ID low>/<save ID high>/<file path></code>.

=== UserSaveDataForCheck Archive Path Data Format ===
{| class="wikitable" border="1"
|-
! Index word
! Description
|-
| 0
| [[Mediatypes|Mediatype]] (must be non-zero)
|-
| 1
| Lower word saveid
|-
| 2
| Upper word saveid
|}

The file/directory lowpath for this FS archive is a text path in the [[Savegames|savegame]] filesystem.

=== 0x567890B4 Archive Path Data Format ===
{| class="wikitable" border="1"
|-
! Index word
! Description
|-
| 0
| [[Mediatypes|Mediatype]]
|-
| 1
| <code><nowiki>Lower_word_saveid >> 8</nowiki></code> ?
|-
| 2
| Unknown. Game calculate this using formula <code><nowiki>0xFFFFFF00 | unknown_b</nowiki></code>
|}

=== Title Access Archive Path Data Format ===
==== Title Access Type ====
{| class="wikitable" border="1"
|-
! Value !! Description
|-
| 0 || High-level NCCH content access
|-
| 1 || Save data access (high-level, decrypted)
|-
| 2 || Raw content (low-level NCCH/SRL) access
|-
| 3 || Banner save data access (for DSiWare titles)
|-
| 4 || FS only: Save data transfer (internally uses generated data from [[FS:BeginSaveDataMove]] as the IV for "Save data access (low-level, encrypted)")
|-
| 5 || Save data access (low-level, encrypted)
|}

==== NCCH Access Type ====
{| class="wikitable" border="1"
|-
! Value !! Description
|-
| 0 || RomFS
|-
| 1 || <code>exefs:/.code</code>
|-
| 2 || System Menu Data (<code>exefs:/icon</code>, <code>exefs:/banner</code>, <code>exefs:/logo</code>)
|-
| 3 || NCCH Header(s)
|-
| 4 || "is seeded" check
|-
| 5 || Seed verify/validate
|}

==== NCCH Header Access Type ====
{| class="wikitable" border="1"
|-
! Value !! Description
|-
| 0 || [[NCCH/Extended_Header|Extheader]] (0x0-0x400)
|-
| 1 || [[NCCH/Extended_Header|Extheader]] AccessDesc (0x400-0x800)
|-
| 2 || Raw [[NCCH#NCCH_Header|NCCH Header]]
|}

==== Archive Path ====

{| class="wikitable" border="1"
|-
! Offset !! Size !! Description
|-
| 0x0 || 0x8 || Program ID (Title ID)
|-
| 0x9 || 0x1 || [[Mediatypes|Media Type]]
|-
| 0xA || 0x7 || padding
|}

==== File Path ====

{| class="wikitable" border="1"
|-
! Offset !! Size !! Description
|-
| 0x0 || 0x4 || [[Filesystem_services#Title_Access_Type|Title Access Type]]
|-
| 0x4 || 0x10 || Dynamic data depending on [[Filesystem_services#Title_Access_Type|Title Access Type]]:

{| class="wikitable" border="1"
|-
! High Level NCCH Access !! Save Data Access (high level) !! Raw Content !! FS only: Save Data Transfer
|-
|
{| class="wikitable" border="1"
|-
! Offset !! Size !! Description
|-
| 0x0 || 0x4 || Content index from TMD for NAND/SD titles
NCSD partition index for gamecards
|-
| 0x4 || 0x4 || [[Filesystem_services#NCCH_Access_Type|NCCH Access Type]]
|-
| 0x8 || 0x8 || Dynamic data depending on [[Filesystem_services#NCCH_Access_Type|NCCH Access Type]]:
For ExeFS, (System Menu Data / <code>exefs:/.code</code>),

{| class="wikitable" border="1"
| 8-byte ExeFS file name
|}

For Header Access,

{| class="wikitable" border="1"
| [[Filesystem_services#NCCH_Header_Access_Type|u64, NCCH Header Access Type]]
|}

For RomFS,

{| class="wikitable" border="1"
| [[NCCH#Content_Types|u64, Allowed content types flag]]
(<code>(1 << allowed_type_a) |

(1 << allowed_type_b)...</code>)
|}

|}
|
{| class="wikitable" border="1"
|-
! Offset !! Size !! Description
|-
| 0x0 || 0x10 || 16-byte IV for save data crypto
|}
|
{| class="wikitable" border="1"
|-
! Offset !! Size !! Description
|-
| 0x0 || 0x4 || Content index from TMD for NAND/SD titles
NCSD partition index for gamecards
|-
| 0x4 || 0xC || padding
|}
|
{| class="wikitable" border="1"
|-
! Offset !! Size !! Description
|-
| 0x0 || 0x4 || Save data transfer key from [[FS:BeginSaveDataMove]]
|-
| 0x4 || 0xC || padding
|}
|}
|-
| 0x14 || 0x10 || 16-byte seed for titles that require one, or for validating a seed against the check value in the [[NCCH#NCCH_Header|NCCH Header]]'s check value.
If the title does not use a seed, this should not be included and size 0x14 should be used instead of 0x24.
|}

For encrypted save data access and banner save data access, the entire 0x10 portion of the dynamic data is left blank.

The "is seeded check" NCCH access type opens a virtual 1-byte file that reads either 0 or 1; this value is generated on-the-fly and will be 1 if ncchflags[7] has bit5 set (content uses seed), and 0 otherwise.

For NCCH sections that require a seed (e.g. <code>.code</code>, RomFS, etc.), the additional seed portion of the low path must be populated with the correct seed.

The "Seed Verify/Validate" NCCH access type also requires the seed portion of the lowpath. The target NCCH content is opened (with the opened file interface being stubbed, meaning no real reads/writes can be performed on it), and the given seed is used to calculate the seed check hash, and part of it is compared to the check value in the NCCH header. If it matches, opening the "file" succeeds, otherwise 0xD900458C is returned. If attempt is made to use the seed validation type on a content that does not use a seed, error 0xC92044E6 is returned.

==== FS Limitations ====

For FS, this archive functions the same, except for the following limitations:

- Only the title access types "High Level NCCH Access" and "High Level Save Data Access", and "Save Data Transfer" are allowed.

- For high level NCCH access, the types "RomFS", "System Menu Data", "Seeded check", and "Seed Check/Verify" are allowed.

- For "Seed Check/Verify", rather than providing the title seed in the file path (as is the case for FSPXI), the seed is retrieved from the seed database (meaning the file lowpath size is always 0x14 for FS).

=== Program Access / SelfNCCH access ===

Provides access to a "merged" archive of a base title and, optionally, a separate update (patch) title.

If no patch title exists, the base title is considered to be the patch title, i.e. turning all "patch" accesses into accesses to the base title.

==== Program Access Type ====
{| class="wikitable" border="1"
|-
! Value !! Description !! Accesses
|-
| 0 || RomFS ("unspecified" [[NCCH#Content_Type|content type]], the default) || Base title
|-
| 1 || <code>exefs:/.code</code> || Patch title
|-
| 2 || System Menu Data (<code>exefs:/icon</code>, <code>exefs:/banner</code>, <code>exefs:/logo</code>) || Base title
|-
| 3 || Save Data (high level, decrypted) || -
|-
| 4 || RomFS (all [[NCCH#Content_Type|content types]]) || Base title
|-
| 5 || RomFS ("unspecified" [[NCCH#Content_Type|content type]], the default) || Patch title
|}

==== Archive Path ====
{| class="wikitable" border="1"
|-
! Offset !! Size !! Description
|-
| 0x0 || 0x8 || u64, Program Handle from [[PXIPM:RegisterProgram]]
|}

==== File Path ====
{| class="wikitable" border="1"
|-
! Offset !! Size !! Description
|-
| 0x0 || 0x4 || [[Filesystem_services#Program_Access_Type|Program Access Type]]
|-
| 0x4 || 0x8 || Dynamic data depending on [[Filesystem_services#Program_Access_Type|Program Access Type]]:
{| class="wikitable" border="1"
|-
! ExeFS files (System Menu Data, etc.) !! RomFS of base title (all [[NCCH#Content_Type|content types]])
|-
|
{| class="wikitable" border="1"
| 8-character ExeFS filename
|}
|
{| class="wikitable" border="1"
|-
! Offset !! Size !! Description
|-
| 0x0 || 0x4 || u32, content index of target content
|-
| 0x4 || 0x4 || padding
|}
|}
|}

==== FS Limitations ====

- FSPXI allows all access types.

- When used through fs:LDR by loader, FS only provides access to <code>exefs:/.code</code>.

- For SelfNCCH access, the only allowed access types are "RomFS ("unspecified" [[NCCH#Content_Type|content type]], the default)" of the Base or Patch title, and "System Menu Data". Attempting to access "Save Data" results in error 0xE0E046BE, "RomFS (all [[NCCH#Content_Type|content types]])" in 0xF9604784, and "<code>exefs:/.code</code>" in 0xD9004676.

=== [[RomFS]] ===

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.

With FSPXI the returned data for RomFS is the entire RomFS section from the NCCH, starting at the IVFC header.

The 0x3 archive is an interface for the 0x2345678E archive with the current process programID+mediatype. The file lowpath is 3-words. These words are written to 0x2345678E-archive file_lowpath+0, with the rest of that lowpath set to all-zero(lowpath is different from archive 0x2345678A). File lowpath:
{| class="wikitable" border="1"
|-
! Index word
! Description
|-
| 0
| See above. The only values which FS-module doesn't allow to be used here are:
* 0x1: Error 0xE0E046BE.
* 0x3: Error 0xE0E046BE.
* 0x4: FS-module executes svcBreak when using this.
|-
| 1-2
| See above. Not validated by FS-module.
|}

=Anti Savegame Restore=
Anti Savegame Restore, internally referred to as ''Save Data Rollback Prevention'', is a feature originally implemented in the FS module with [[4.0.0-7]], which prevents the user from restoring previous versions of a savegame image. This feature is not used (in practice) for gamecard games. When an old version of the save is detected, the application will display an error regarding old savegame version, then delete and recreate the save data (similar to when it is corrupted).

==Implementation==
When creating the savedata, the application generates a secure value (a 64 bit unsigned integer), then stores it in either the [[DISA_and_DIFF#DISA_header|DISA save image header]] or the [[Filesystem_services#Anti_Savegame_Restore_Save_Data|Anti Savegame Restore Save Data]]. The application then uses the anti-savegame-restore commands ([[FS:SetSaveDataSecureValue]], [[FS:GetSaveDataSecureValue]], [[FS:SetOtherSaveDataSecureValue]], [[FS:GetOtherSaveDataSecureValue]], [[FS:SetThisSaveDataSecureValue]], [[FS:GetThisSaveDataSecureValue]], [[FS:SetSaveArchiveSecureValue]] and [[FS:GetSaveArchiveSecureValue]]) to verify the value known to the game for comparison with the value returned by FS, and to update the value in the corresponding storage location.

Each time the application writes to the savegame, the value should be updated by both the application and through FS. Usually, applications update this value by incrementing it. However, generating a new random-number or other methods of updating it can be used as well.

==Anti Savegame Restore Save Data==
The save data used for this feature is stored in [[System_SaveData|System Save Data]] ID 0x00010011 and contains only one file, named <code>DB</code>:

===Main Structure===
{| class="wikitable" border="1"
|-
! Offset !! Size !! Description
|-
| 0x0 || 0x1000 || Header
{| class="wikitable" border="1"
|-
! Offset !! Size !! Description
|-
| 0x0 || 0x1 || u8, version (usually 0)
|-
| 0x1 || 0x3 || padding
|-
| 0x4 || 0x4 || u32, number of secure value entries
|-
| 0x8 || 0xFF8 || completely unused, padding
|}
|-
| 0x1000 || 0x1C000 (8 * 14336) || [[Filesystem_services#SecureValueKey|Secure value keys]]
|-
| 0x1D000 || 0x1C000 (8 * 14336) || u64s, Secure values
|}

===SecureValueKey===
Depending on which command is used, secure value keys can be interpreted as:
{| class="wikitable" border="1"
|-
! Offset !! Size !! Description
|-
| 0x0 || 0x8 || u64, Title ID
|}
or:
{| class="wikitable" border="1"
|-
! Offset !! Size !! Description
|-
| 0x0 || 0x4 || u32, [[Filesystem_services#SecureValueSlot|Secure Value Slot]]
|-
| 0x4 || 0x4 || u32, Unique ID
|}

==Applications using this feature==
* Animal Crossing: New Leaf
* Pokemon X & Y
* Pokemon Omega Ruby & Alpha Sapphire
* Pokemon Omega Ruby & Alpha Sapphire Demo
* Pokemon Shuffle
* Super Smash Bros
* Pokemon Red,Blue and Yellow (GB(C) VC)
* Rusty's Real Deal Baseball
* Megami Meguri

=SEEDDB and TITLETAG=
With [[9.6.0-24|9.6.0-X]] new [[System_SaveData]] with save ID 0x0001000F was added. This save data contains both the NCCH seed database (SEEDDB) and the title tag database (TITLETAG).

These databases are managed by the commands [[FS:AddSeed]], [[FS:GetSeed]], [[FS:DeleteSeed]], [[FS:GetNumSeeds]] and [[FS:ListSeeds]] for SEEDDB, and [[FS:AddTitleTag]], [[FS:GetTitleTag]], [[FS:DeleteTitleTag]], [[FS:GetNumTitleTags]], and [[FS:ListTitleTags]] for TITLETAG respectively.

Both the [[Home_Menu|HOME Menu]] and the [[NIM_Services|NIM]] module have access to these commands.

==SEEDDB==

Stored in the system savedata archive 0x0001000F as a file named <code>SEEDDB</code>, it contains the title-unique seed-data used for the new [[NCCH]] keyY generation added with FIRM [[9.6.0-24|9.6.0-X]].

The file follows a simple key-value format allowing the storage of seed data for up to 2000 unique title IDs.

{| class="wikitable" border="1"
|-
! Offset !! Size !! Description
|-
| 0x0 || 0x1000 || Header
{| class="wikitable" border="1"
|-
! Offset !! Size !! Description
|-
| 0x0 || 0x1 || u8, version (usually 0)
|-
| 0x1 || 0x3 || padding
|-
| 0x4 || 0x4 || u32, number of seed entries
|-
| 0x8 || 0xFF8 || completely unused, padding
|}
|-
| 0x1000 || 0x3E80 (8 * 2000) || u64s, Title IDs
|-
| 0x4E80 || 0x7D00 (16 * 2000) || Seed data, 16 bytes per seed
|}

==TITLETAG Database==

Stored in the system savedata archive 0x0001000F as a file named <code>TITLETAG</code>, it contains information used by the [[Home_Menu|HOME Menu]] to handle cases when a to-be-released title has been purchased already, that is, to properly install the seed required for [[NCCH]] keyY generation added with FIRM [[9.6.0-24|9.6.0-X]].

When a to-be-released title is purchased, the [[NIM_Services|NIM]] module installs a [[Filesystem_services#TitleTag|title tag]] with enough information about the title for the [[Home_Menu|HOME Menu]] to be able to initiate a seed import once the title has been released (and thus, the title's NCCH content lock seed). Until the title's seed is released, and while the title tag remains in the database, the HOME Menu will prevent the user from launching the software as it would not run without the seed. Once released, information from the title tag is used to download the seed, and, if successful, the title tag is removed from the database, making the software playable.

The file follows a simple key-value format allowing the storage of title tag data for up to 2000 unique title IDs.

{| class="wikitable" border="1"
|-
! Offset !! Size !! Description
|-
| 0x0 || 0x1000 || Header
{| class="wikitable" border="1"
|-
! Offset !! Size !! Description
|-
| 0x0 || 0x1 || u8, version (usually 0)
|-
| 0x1 || 0x3 || padding
|-
| 0x4 || 0x4 || u32, number of entries
|-
| 0x8 || 0xFF8 || completely unused, padding
|}
|-
| 0x1000 || 0x3E80 (8 * 2000) || u64s, Title IDs
|-
| 0x4E80 || 0x3E800 (0x80 * 2000) || [[Filesystem_services#TitleTag|Title Tag]] data, 0x80 bytes per entry
|}

= Common Types =
== MediaType ==
{| class="wikitable" border="1"
|-
! Value
! Description
|-
| 0
| NAND
|-
| 1
| SD
|-
| 2
| Game Card
|}

== SystemMediaType ==
{| class="wikitable" border="1"
|-
! Value
! Description
|-
| 0
| CTR NAND
|-
| 1
| TWL NAND
|-
| 2
| SD
|-
| 3
| TWL Photo
|}

== OpenFlags ==
{| class="wikitable" border="1"
|-
! Bit
! Description
|-
| 0
| Read
|-
| 1
| Write
|-
| 2
| Create
|}

== Attributes ==
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x1
| Is Directory
|-
| 0x1
| 0x1
| Is Hidden
|-
| 0x2
| 0x1
| Is Archive
|-
| 0x3
| 0x1
| Is Read-Only
|}

== WriteOption ==
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x1
| Flush
|-
| 0x1
| 0x1
| Update Time Stamp
|-
| 0x2
| 0x1
| Reserved
|-
| 0x3
| 0x1
| Reserved
|}

== DirectoryEntry ==
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x20C
| UTF-16 Entry Name
|-
| 0x20C
| 0xA
| 8.3 short filename name
|-
| 0x216
| 0x4
| 8.3 short filename extension
|-
| 0x21A
| 0x1
| Always 1
|-
| 0x21B
| 0x1
| Reserved
|-
| 0x21C
| 0x4
| [[Filesystem_services#Attributes|Attributes]]
|-
| 0x220
| 0x8
| Entry Size
|}

== ArchiveResource ==
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x4
| Sector byte-size
|-
| 0x4
| 0x4
| Cluster byte-size
|-
| 0x8
| 0x4
| Partition capacity in clusters
|-
| 0xC
| 0x4
| Available free space in clusters
|}

== ProgramInfo ==
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x8
| Program ID
|-
| 0x8
| 0x1
| [[Filesystem_services#MediaType|Media Type]]
|-
| 0x9
| 0x7
| Padding
|}

== ProductInfo ==
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x10
| Product Code
|-
| 0x10
| 0x2
| Company Code
|-
| 0x12
| 0x2
| Remaster Version
|}

== IntegrityVerificationSeed ==
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x10
| AES-CBC MAC over a SHA256 hash, which hashes the first 0x110-bytes of the cleartext SEED.
|-
| 0x10
| 0x120
| The [[nand/private/movable.sed]], encrypted with AES-CBC using the above MAC for the counter.
|}

== ExtSaveDataInfo ==
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x4
| [[Filesystem_services#DataAccessPath|DataAccessPath]]
|-
| 0x4
| 0x8
| Save ID
|-
| 0xC
| 0x4
| Reserved
|}

== SystemSaveDataInfo ==
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x4
| [[Filesystem_services#DataAccessPath|DataAccessPath]]
|-
| 0x4
| 0x4
| Save ID
|}

== SecureValueSlot ==
{| class="wikitable" border="1"
|-
! Value
! Description
|-
| 0x1000
| SD Application
|}

== SecureValueEntry ==
{| class="wikitable" border="1"
|-
! Offset !! Size !! Description
|-
| 0x0 || 0x4 || u32, [[Filesystem_services#SecureValueSlot|Secure Value Slot]]
|-
| 0x4 || 0x1 || When used as an input entry:
{| class="wikitable" border="1"
|-
! Value !! Description
|-
| 0 || This entry should be removed.
|-
| 1 || This entry should be updated with the given value.
|}
When returned from a command:
{| class="wikitable" border="1"
|-
! Value !! Description
|-
| 0 || No entry with the given slot and title ID was found, or: this entry is unused.
|-
| 1 || The entry with the given slot and title ID was found, or: this entry is used.
|}
|-
| 0x5 || 0x3 || padding
|-
| 0x8 || 0x8 || u64, Secure Value
|}

== TitleTag ==
{| class="wikitable" border="1"
|-
! Offset !! Size !! Description
|-
| 0x0 || 0x4 || Magic, <code>PREP</code> (PREPurchase install)
|-
| 0x4 || 0x4 || s32, Release date year
|-
| 0x8 || 0x1 || u8, Release date month
|-
| 0x9 || 0x1 || u8, Release date day
|-
| 0xA || 0x2 || u16, Country code
|-
| 0xC || 0x4 || u32, Seed status (0: not downloaded yet, 1: last download attempt failed, 2: seed installed successfully)
|-
| 0x10 || 0x4 || Result code from last seed installation attempt
|-
| 0x14 || 0x4 || Support error code from last seed installation attempt
|-
| 0x18 || 0x68 || reserved padding (unused)
|}

== CardSpiBaudRate ==
{| class="wikitable" border="1"
|-
! Value
! Description
|-
| 0x0
| 512KHz
|-
| 0x1
| 1MHz
|-
| 0x2
| 2MHz
|-
| 0x3
| 4MHz
|-
| 0x4
| 8MHz
|-
| 0x5
| 16MHz
|}

== CardSpiBusMode ==
{| class="wikitable" border="1"
|-
! Value
! Description
|-
| 0x0
| 1-bit
|-
| 0x1
| 4-bit
|}

== SpecialContentType ==
{| class="wikitable" border="1"
|-
! Value
! Description
! Found in
|-
| 0x1
| CTR (Old3DS) Update Partition
| Gamecards
|-
| 0x2
| Manual
| Gamecards, Digital titles
|-
| 0x3
| DLP Child
| Gamecards, Digital titles
|-
| 0x4
| KTR (New3DS) Update Partition
| Gamecards
|-
|}

== DeviceMoveContext ==
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x10
| IVs (ID0 of source console)
|-
| 0x10
| 0x10
| Encrypt Parameter (used to calculate the IV for encryption)
|}

=Errors=
See [[Filesystem_services_PXI]].

[[Category:Services]]

APT:StoreSysMenuArg

2025-12-24T13:53:50Z

Gruetzig: meow

=Request=
{| class="wikitable" border="1"
|-
! Index Word
! Description
|-
| 0
| Header code [0x00370042]
|-
| 1
| Size (capped to 0x40)
|-
| 2
| <nowiki>(Size << 14) | 2</nowiki>
|-
| 3
| void*, Input Buffer
|}

=Response=
{| class="wikitable" border="1"
|-
! Index Word
! Description
|-
| 0
| Header code
|-
| 1
| Result code
|}

=Structure=
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x4
| Type?
|-
| 0x4
| 0x4
| Title Unique ID of the applet which set this SysMenuArg structure
|-
| 0x8
| 0x8
| u64, Program ID of the title to launch
|-
| 0x10
| 0x4
| Media Type
|-
| 0x14
| 0x4
| 1 + <bit value loaded from [[Config_Savegame|Cfg]] block 0xC0000>
|}

The above is the structure of the 0x18-byte buffer used with Home Menu for StoreSysMenuArg/LoadSysMenuArg. The uniqueID is for a NAND title with tid-high 000400030, this title must be installed in NAND. Only certain uniqueIDs can be used here.

=Description=
This copies the input buffer to [[FIRM|FIRM-launch params]]+0x500, in NS state.

Filesystem services

2025-08-28T00:01:25Z

Gruetzig: this doesnt match observations nor the header in the page for the command

= Services =
{{Anchor|FS}}{{Anchor|FSUSER}}{{Anchor|fs:USER}}
== Filesystem service "fs:USER" ==
You can at most have 32 FS archive handles.

{| class="wikitable" border="1"
|-
! Command Header
! Available since system version
! Description
! scope="col" width="400" | Required [[NCCH/Extended_Header|exheader]] access info bitmask
|-
| 0x000100C6
|?
| [[FS:Dummy1|Dummy1]]
| None
|-
| 0x040100C4
|?
| [[FS:Control|Control]]
| None
|-
| 0x08010002
|?
| [[FS:Initialize|Initialize]]
| None
|-
| 0x080201C2
|?
| [[FS:OpenFile|OpenFile]]
| None
|-
| 0x08030204
|?
| [[FS:OpenFileDirectly|OpenFileDirectly]]
| None
|-
| 0x08040142
|?
| [[FS:DeleteFile|DeleteFile]]
| None
|-
| 0x08050244
|?
| [[FS:RenameFile|RenameFile]]
| None
|-
| 0x08060142
|?
| [[FS:DeleteDirectory|DeleteDirectory]]
| None
|-
| 0x08070142
|?
| [[FS:DeleteDirectoryRecursively|DeleteDirectoryRecursively]]
| None
|-
| 0x08080202
|?
| [[FS:CreateFile|CreateFile]]
| None
|-
| 0x08090182
|?
| [[FS:CreateDirectory|CreateDirectory]]
| None
|-
| 0x080A0244
|?
| [[FS:RenameDirectory|RenameDirectory]]
| None
|-
| 0x080B0102
|?
| [[FS:OpenDirectory|OpenDirectory]]
| None
|-
| 0x080C00C2
|?
| [[FS:OpenArchive|OpenArchive]]
| Each archive ID code has separate access info bitmasks, if it has any
|-
| 0x080D0144
|?
| [[FS:ControlArchive|ControlArchive]]
| None
|-
| 0x080E0080
|?
| [[FS:CloseArchive|CloseArchive]]
| None
|-
| 0x080F0180
|?
| [[FS:Obsoleted_2_0_FormatThisUserSaveData|Obsoleted_2_0_FormatThisUserSaveData]]
| None
|-
| 0x08100200
|?
| [[FS:Obsoleted_3_0_CreateSystemSaveData|Obsoleted_3_0_CreateSystemSaveData]]
| 0x4, for when the input saveID doesn't match the exheader saveID
|-
| 0x08110040
|?
| [[FS:Obsoleted_3_0_DeleteSystemSaveData|Obsoleted_3_0_DeleteSystemSaveData]]
| 0x1004, for when the input saveID doesn't match the exheader saveID
|-
| 0x08120080
|?
| [[FS:GetFreeBytes|GetFreeBytes]]
| None
|-
| 0x08130000
|?
| [[FS:GetCardType|GetCardType]]
| 0x1017
|-
| 0x08140000
|?
| [[FS:GetSdmcArchiveResource|GetSdmcArchiveResource]]
| None
|-
| 0x08150000
|?
| [[FS:GetNandArchiveResource|GetNandArchiveResource]]
| 0x1007
|-
| 0x08160000
|?
| [[FS:GetSdmcFatfsError|GetSdmcFatfsError]]
| 0x2
|-
| 0x08170000
|?
| [[FS:IsSdmcDetected|IsSdmcDetected]]
| None
|-
| 0x08180000
|?
| [[FS:IsSdmcWritable|IsSdmcWritable]]
| None
|-
| 0x08190042
|?
| [[FS:GetSdmcCid|GetSdmcCid]]
| 0x2
|-
| 0x081A0042
|?
| [[FS:GetNandCid|GetNandCid]]
| 0x2
|-
| 0x081B0000
|?
| [[FS:GetSdmcSpeedInfo|GetSdmcSpeedInfo]]
| 0x2
|-
| 0x081C0000
|?
| [[FS:GetNandSpeedInfo|GetNandSpeedInfo]]
| 0x2
|-
| 0x081D0042
|?
| [[FS:GetSdmcLog|GetSdmcLog]]
| 0x2
|-
| 0x081E0042
|?
| [[FS:GetNandLog|GetNandLog]]
| 0x2
|-
| 0x081F0000
|?
| [[FS:ClearSdmcLog|ClearSdmcLog]]
| 0x2
|-
| 0x08200000
|?
| [[FS:ClearNandLog|ClearNandLog]]
| 0x2
|-
| 0x08210000
|?
| [[FS:CardSlotIsInserted|CardSlotIsInserted]]
| 0x1017
|-
| 0x08220000
|?
| [[FS:CardSlotPowerOn|CardSlotPowerOn]]
| 0x2
|-
| 0x08230000
|?
| [[FS:CardSlotPowerOff|CardSlotPowerOff]]
| 0x2
|-
| 0x08240000
|?
| [[FS:CardSlotGetCardIFPowerStatus|CardSlotGetCardIFPowerStatus]]
| 0x2
|-
| 0x08250040
|?
| [[FS:CardNorDirectCommand|CardNorDirectCommand]]
| 0x2
|-
| 0x08260080
|?
| [[FS:CardNorDirectCommandWithAddress|CardNorDirectCommandWithAddress]]
| 0x2
|-
| 0x08270082
|?
| [[FS:CardNorDirectRead|CardNorDirectRead]]
| 0x2
|-
| 0x082800C2
|?
| [[FS:CardNorDirectReadWithAddress|CardNorDirectReadWithAddress]]
| 0x2
|-
| 0x08290082
|?
| [[FS:CardNorDirectWrite|CardNorDirectWrite]]
| 0x2
|-
| 0x082A00C2
|?
| [[FS:CardNorDirectWriteWithAddress|CardNorDirectWriteWithAddress]]
| 0x2
|-
| 0x082B00C2
|?
| [[FS:CardNorDirectRead_4xIO|CardNorDirectRead_4xIO]]
| 0x2
|-
| 0x082C0082
|?
| [[FS:CardNorDirectCpuWriteWithoutVerify|CardNorDirectCpuWriteWithoutVerify]]
| 0x2
|-
| 0x082D0040
|?
| [[FS:CardNorDirectSectorEraseWithoutVerify|CardNorDirectSectorEraseWithoutVerify]]
| 0x2
|-
| 0x082E0040
|?
| [[FS:GetProductInfo|GetProductInfo]]
| 0x1005
|-
| 0x082F0040
|?
| [[FS:GetProgramLaunchInfo|GetProgramLaunchInfo]]
| 0x1005
|-
| 0x08300182
|?
| [[FS:Obsoleted_3_0_CreateExtSaveData|Obsoleted_3_0_CreateExtSaveData]]
| 0xC, for when the input extdataID doesn't match the exheader extdataID
|-
| 0x08310180
|?
| [[FS:Obsoleted_3_0_CreateSharedExtSaveData|Obsoleted_3_0_CreateSharedExtSaveData]]
| 0x1005
|-
| 0x08320102
|?
| [[FS:Obsoleted_3_0_ReadExtSaveDataIcon|Obsoleted_3_0_ReadExtSaveDataIcon]]
| 0x100D, for when the input extdataID doesn't match the exheader extdataID
|-
| 0x08330082
|?
| [[FS:Obsoleted_3_0_EnumerateExtSaveData|Obsoleted_3_0_EnumerateExtSaveData]]
| 0x1005
|-
| 0x08340082
|?
| [[FS:Obsoleted_3_0_EnumerateSharedExtSaveData|Obsoleted_3_0_EnumerateSharedExtSaveData]]
| 0x1005
|-
| 0x08350080
|?
| [[FS:Obsoleted_3_0_DeleteExtSaveData|Obsoleted_3_0_DeleteExtSaveData]]
| 0x100D, for when the input extdataID doesn't match the exheader extdataID
|-
| 0x08360080
|?
| [[FS:Obsoleted_3_0_DeleteSharedExtSaveData|Obsoleted_3_0_DeleteSharedExtSaveData]]
| 0x1005
|-
| 0x08370040
|?
| [[FS:SetCardSpiBaudRate|SetCardSpiBaudRate]]
| 0x2
|-
| 0x08380040
|?
| [[FS:SetCardSpiBusMode|SetCardSpiBusMode]]
| 0x2
|-
| 0x08390000
|?
| [[FS:SendInitializeInfoTo9|SendInitializeInfoTo9]]
| None
|-
| 0x083A0100
|?
| [[FS:GetSpecialContentIndex|GetSpecialContentIndex]]
| 0x1005
|-
| 0x083B00C2
|?
| [[FS:GetLegacyRomHeader|GetLegacyRomHeader]]
| 0x1015
|-
| 0x083C00C2
|?
| [[FS:GetLegacyBannerData|GetLegacyBannerData]]
| 0x1015
|-
| 0x083D0100
|?
| [[FS:CheckAuthorityToAccessExtSaveData|CheckAuthorityToAccessExtSaveData]]
| 0x44
|-
| 0x083E00C2
|?
| [[FS:QueryTotalQuotaSize|QueryTotalQuotaSize]]
| None
|-
| 0x083F00C0
|?
| [[FS:Obsoleted_3_0_GetExtDataBlockSize|Obsoleted_3_0_GetExtDataBlockSize]]
| None
|-
| 0x08400040
|?
| [[FS:AbnegateAccessRight|AbnegateAccessRight]]
|?
|-
| 0x08410000
|?
| [[FS:DeleteSdmcRoot|DeleteSdmcRoot]]
| 0x1005
|-
| 0x08420040
|?
| [[FS:DeleteAllExtSaveDataOnNand|DeleteAllExtSaveDataOnNand]]
| 0x1005
|-
| 0x08430000
|?
| [[FS:InitializeCtrFileSystem|InitializeCtrFileSystem]]
| None
|-
| 0x08440000
|?
| [[FS:CreateSeed|CreateSeed]]
| 0x2
|-
| 0x084500C2
|?
| [[FS:GetFormatInfo|GetFormatInfo]]
|?
|-
| 0x08460102
|?
| [[FS:GetLegacyRomHeader2|GetLegacyRomHeader2]]
| 0x1015
|-
| 0x08470180
|?
| [[FS:Obsoleted_2_0_FormatCtrCardUserSaveData|Obsoleted_2_0_FormatCtrCardUserSaveData]]
| 0x6
|-
| 0x08480042
|?
| [[FS:GetSdmcCtrRootPath|GetSdmcCtrRootPath]]
| 0x100D
|-
| 0x08490040
|?
| [[FS:GetArchiveResource|GetArchiveResource]]
|?
|-
| 0x084A0002
|?
| [[FS:ExportIntegrityVerificationSeed|ExportIntegrityVerificationSeed]]
| 0x4000
|-
| 0x084B0002
|?
| [[FS:ImportIntegrityVerificationSeed|ImportIntegrityVerificationSeed]]
| 0x4000
|-
| 0x084C0242
|?
| [[FS:FormatSaveData|FormatSaveData]]
| 0x6, in some cases this write isn't needed however
|-
| 0x084D0102
|?
| [[FS:GetLegacySubBannerData|GetLegacySubBannerData]]
| 0x1015
|-
| 0x084E0342
|?
| [[FS:UpdateSha256Context|UpdateSha256Context]]
| 0x5
|-
| 0x084F0102
|?
| [[FS:ReadSpecialFile|ReadSpecialFile]]
| None
|-
| 0x08500040
|?
| [[FS:GetSpecialFileSize|GetSpecialFileSize]]
| None
|-
| 0x08510242
| [[3.0.0-5]]
| [[FS:CreateExtSaveData|CreateExtSaveData]]
| Shared extdata: 0x101005. Regular extdata in certain cases: 0xC
|-
| 0x08520100
| [[3.0.0-5]]
| [[FS:DeleteExtSaveData|DeleteExtSaveData]]
| Shared extdata: 0x101005. Regular extdata in certain cases: 0x10100D
|-
| 0x08530142
| [[3.0.0-5]]
| [[FS:ReadExtSaveDataIcon|ReadExtSaveDataIcon]]
| 0x10100D (this doesn't apply in certain cases, however)
|-
| 0x08540010
| [[3.0.0-5]]
| [[FS:GetExtDataBlockSize|GetExtDataBlockSize]]
| 0x10100D (this doesn't apply in certain cases, however)
|-
| 0x08550102
| [[3.0.0-5]]
| [[FS:EnumerateExtSaveData|EnumerateExtSaveData]]
| 0x101005
|-
| 0x08560240
| [[3.0.0-5]]
| [[FS:CreateSystemSaveData|CreateSystemSaveData]]
| 0x4 (this doesn't apply in certain cases, however)
|-
| 0x08570080
| [[3.0.0-5]]
| [[FS:DeleteSystemSaveData|DeleteSystemSaveData]]
| 0x1004 (this doesn't apply in certain cases, however)
|-
| 0x08580000
| [[3.0.0-5]]
| [[FS:StartDeviceMoveAsSource|StartDeviceMoveAsSource]]
| 0x2004
|-
| 0x08590200
| [[3.0.0-5]]
| [[FS:StartDeviceMoveAsDestination|StartDeviceMoveAsDestination]]
| 0x2004
|-
| 0x085A00C0
| [[3.0.0-5]]
| [[FS:SetArchivePriority|SetArchivePriority]]
| None
|-
| 0x085B0080
| [[3.0.0-5]]
| [[FS:GetArchivePriority|GetArchivePriority]]
| None
|-
| 0x085C00C0
| [[3.0.0-5]]
| [[FS:SetCtrCardLatencyParameter|SetCtrCardLatencyParameter]]
| 0xE
|-
| 0x085D01C0
| [[3.0.0-5]]
| [[FS:SetFsCompatibilityInfo|SetFsCompatibilityInfo]]
| 0x100001
|-
| 0x085E0040
| [[3.0.0-5]]
| [[FS:ResetCardCompatibilityParameter|ResetCardCompatibilityParameter]]
| 0xE
|-
| 0x085F0040
| [[3.0.0-5]]
| [[FS:SwitchCleanupInvalidSaveData|SwitchCleanupInvalidSaveData]]
| 0x12004
|-
| 0x08600042
| [[3.0.0-5]]
| [[FS:EnumerateSystemSaveData|EnumerateSystemSaveData]]
| 0x2004
|-
| 0x08610042
| [[3.0.0-5]]
| [[FS:InitializeWithSdkVersion|InitializeWithSdkVersion]]
| None
|-
| 0x08620040
| [[3.0.0-5]]
| [[FS:SetPriority|SetPriority]]
| None
|-
| 0x08630000
| [[3.0.0-5]]
| [[FS:GetPriority|GetPriority]]
| None
|-
| 0x08640000
| [[3.0.0-5]]
| [[FS:Obsoleted_4_0_GetNandInfo|Obsoleted_4_0_GetNandInfo]]
| Stubbed, this returns an error
|-
| 0x08650140
| [[4.0.0-7]]
| [[FS:SetSaveDataSecureValue|SetSaveDataSecureValue]]
| 0x121004 (in certain cases this doesn't apply, however)
|-
| 0x086600C0
| [[4.0.0-7]]
| [[FS:GetSaveDataSecureValue|GetSaveDataSecureValue]]
| 0x121004 (in certain cases this doesn't apply, however)
|-
| 0x086700C4
| [[4.0.0-7]]
| [[FS:ControlSecureSave|ControlSecureSave]]
| 0x121004
|-
| 0x08680000
| [[4.0.0-7]]
| [[FS:GetMediaType|GetMediaType]]
| None
|-
| 0x08690000
| [[4.0.0-7]]
| [[FS:Obsoleted_4_0_GetNandEraseCount|Obsoleted_4_0_GetNandEraseCount]]
| Stubbed, this returns an error.
|-
| 0x086A0082
| [[4.0.0-7]]
| [[FS:ReadNandReport|ReadNandReport]]
| None
|-
| 0x086B00C2
|?
| [[FS:SetOtherSaveDataSecureValue|SetOtherSaveDataSecureValue]]
| 0x121004
|-
| 0x086C00C2
|?
| [[FS:GetOtherSaveDataSecureValue|GetOtherSaveDataSecureValue]]
| 0x121004
|-
| 0x086D0080
|?
| [[FS:BeginSaveDataMove|BeginSaveDataMove]]
| 0x20004
|-
| 0x086E00C0
|?
| [[FS:SetThisSaveDataSecureValue|SetThisSaveDataSecureValue]]
|None
|-
| 0x086F0040
|?
| [[FS:GetThisSaveDataSecureValue|GetThisSaveDataSecureValue]]
| None
|-
| 0x087000C2
|?
| [[FS:CheckArchive|CheckArchive]]
|None
|-
| 0x08710140
| ?
| [[FS:TransferSaveDataCMAC|TransferSaveDataCMAC]]
| 0x20004
|-
| 0x08720200
|?
| [[FS:RegisterTitleContentOverlay|RegisterTitleContentOverlay]]
| 0x80004
|-
| 0x08730100
|?
| [[FS:UnregisterTitleContentOverlay|UnregisterTitleContentOverlay]]
| 0x80004
|-
| 0x08740000
|?
| [[FS:UnregisterAllTitleContentOverlays|UnregisterAllTitleContentOverlays]]
| 0x80004
|-
| 0x08750140
|?
| [[FS:SetSaveArchiveSecureValue|SetSaveArchiveSecureValue]]
|None
|-
| 0x087600C0
|?
| [[FS:GetSaveArchiveSecureValue|GetSaveArchiveSecureValue]]
|None
|-
| 0x08770140
|?
| [[FS:RegisterSpecialTitleContent|RegisterSpecialTitleContent]]
| 0x80004
|-
| 0x08780100
|?
| [[FS:UnregisterSpecialTitleContent|UnregisterSpecialTitleContent]]
| 0x80004
|-
| 0x087900C2
| ?
| Same as [[FS:GetLegacyBannerData|GetLegacyBannerData]], except for the last parameter this internally passes u8 value 0x1 instead of 0x0, for the FSPXI command.
| 0x101015
|-
| 0x087A0180
| [[9.6.0-24|9.6.0-X]]
| [[FS:AddSeed|AddSeed]]
| 0x200000
|-
| 0x087B0080
| [[9.6.0-24|9.6.0-X]]
| [[FS:GetSeed|GetSeed]]
| 0x200000
|-
| 0x087C0080
| [[9.6.0-24|9.6.0-X]]
| [[FS:DeleteSeed|DeleteSeed]]
| 0x200000
|-
| 0x087D0000
| [[9.6.0-24|9.6.0-X]]
| [[FS:GetNumSeeds|GetNumSeeds]]
| 0x200000
|-
| 0x087E0042
| [[9.6.0-24|9.6.0-X]]
| [[FS:ListSeeds|ListSeeds]]
| 0x200000
|-
| 0x087F0100
| [[9.6.0-24|9.6.0-X]]
| [[FS:TitleContentHasSeed|TitleContentHasSeed]]
| 0x200000
|-
| 0x08800880
| [[9.6.0-24|9.6.0-X]]
| [[FS:AddTitleTag|AddTitleTag]]
| 0x200000
|-
| 0x08810080
| [[9.6.0-24|9.6.0-X]]
| [[FS:GetTitleTag|GetTitleTag]]
| 0x200000
|-
| 0x08820080
| [[9.6.0-24|9.6.0-X]]
| [[FS:DeleteTitleTag|DeleteTitleTag]]
| 0x200000
|-
| 0x08830000
| [[9.6.0-24|9.6.0-X]]
| [[FS:GetNumTitleTags|GetNumTitleTags]]
| 0x200000
|-
| 0x08840042
| [[9.6.0-24|9.6.0-X]]
| [[FS:ListTitleTags|ListTitleTags]]
| 0x200000
|-
| 0x088500C0
| [[9.6.0-24|9.6.0-X]]
| [[FS:CheckTitleSeed|CheckTitleSeed]]
| 0x200000
|-
| 0x088600C0
| [[11.1.0-34|11.1.0-X]]
| [[FS:CheckUpdatedDat|CheckUpdatedDat]]
| 0x80000
|}

Note: The question marks from Dummy1 to GetSpecialFileSize on the "available since system version" field are mainly there because I think that most of these are necessary for the main system to function, so theoretically that would mean that since the creation of the 3DS these were available, or since launch if that makes more sense. But because of the peculiar nature of some of the functions, they will remain question marks until they can be confirmed 100%.

When access rights are required for a command, at least one of the bits in the process access info specified in the above table for the command must be set. Error 0xD9004676 is returned when a process attempts to use a command which it doesn't have access rights for the command. The exheader access info field is all zero's for most applications. Note that the permissions listed in the above table is for system-version v2.x, therefore permission bit(s) added with newer FIRM may be missing from this.

Each session for fs:USER has separate permissions, initially these are set to all zero's for new fs:USER sessions. The permissions/etc for fs:USER sessions are initialized via [[FS:Initialize]](loaded from the user process exheader).

{{Anchor|FSLDR}}{{Anchor|fs:LDR}}

== Filesystem service "fs:LDR" ==
This service is identical to fs:USER, except [[FS:OpenArchive]] archive 0x2345678E can only be accessed with fs:LDR.

{{Anchor|FSReg}}{{Anchor|FSREG}}{{Anchor|fs:REG}}
== ProgramRegistry service "fs:REG" ==
{| class="wikitable" border="1"
|-
! Command Header
! Description
|-
| 0x000100C6
| [[FSReg:Dummy1|Dummy1]]
|-
| 0x040103C0
| [[FSReg:Register|Register]]
|-
| 0x04020040
| [[FSReg:Unregister|Unregister]]
|-
| 0x040300C0
| [[FSReg:GetProgramInfo|GetProgramInfo]]
|-
| 0x04040100
| [[FSReg:LoadProgram|LoadProgram]]
|-
| 0x04050080
| [[FSReg:UnloadProgram|UnloadProgram]]
|-
| 0x04060080
| [[FSReg:CheckHostLoadId|CheckHostLoadId]]
|}

Only two sessions can be opened for this service at a time, hence no other processes can use this due to [[Process_Manager_Services|pm-module]] and [[Loader_Services|loader]] using this.

=File and directory access=
==Files==
File session handles obtained via [[FS:OpenFile]] and [[FS:OpenFileDirectly]] can be used to access files through a service-like interface, despite not being an actual service registered using [[SRV:RegisterService]]. To use this service-like interface, simply call the SendSyncRequest SVC with a file session handle, using the IPC buffer in thread-local storage for parameters and responses, just like you would with a proper service.

{| class="wikitable" border="1"
|-
! Command Header
! Description
|-
| 0x000100C6
| [[FSFile:Dummy1|Dummy1]]
|-
| 0x040100C4
| [[FSFile:Control|Control]]
|-
| 0x08010100
| [[FSFile:OpenSubFile|OpenSubFile]]
|-
| 0x080200C2
| [[FSFile:Read|Read]]
|-
| 0x08030102
| [[FSFile:Write|Write]]
|-
| 0x08040000
| [[FSFile:GetSize|GetSize]]
|-
| 0x08050080
| [[FSFile:SetSize|SetSize]]
|-
| 0x08060000
| [[FSFile:GetAttributes|GetAttributes]]
|-
| 0x08070040
| [[FSFile:SetAttributes|SetAttributes]]
|-
| 0x08080000
| [[FSFile:Close|Close]]
|-
| 0x08090000
| [[FSFile:Flush|Flush]]
|-
| 0x080A0040
| [[FSFile:SetPriority|SetPriority]]
|-
| 0x080B0000
| [[FSFile:GetPriority|GetPriority]]
|-
| 0x080C0000
| [[FSFile:OpenLinkFile|OpenLinkFile]]
|-
| 0x0C010100
| [[FSFile:GetAvailable|GetAvailable]]
|}

==Directories==
Directory session handles obtained via [[FS:OpenDirectory]] are usable via a service-like interface, following the exact same procedure described above for file sessions.
{| class="wikitable" border="1"
|-
! Command Header
! Available since system version
! Description
|-
| 0x000100C6
| [[1.0.0-0]]
| [[FSDir:Dummy1|Dummy1]]
|-
| 0x040100C4
| [[1.0.0-0]]
| [[FSDir:Control|Control]]
|-
| 0x08010042
| [[1.0.0-0]]
| [[FSDir:Read|Read]]
|-
| 0x08020000
| [[1.0.0-0]]
| [[FSDir:Close|Close]]
|-
| 0x08030040
| ?
| [[FSDir:SetPriority|SetPriority]]
|-
| 0x08040000
| ?
| [[FSDir:GetPriority|GetPriority]]
|}

= Archives =
{| class="wikitable" border="1"
|-
! ArchiveId
! Description
! Accessible via [[Filesystem_services|FS]]
! Accessible via [[Filesystem_services_PXI|FSPXI]]
! Only accessible by Process9 internally
! Requires binary [[FS:OpenFile|Lowpath]]
! Required exheader FS access info bitmask
|-
| 0x00000003
| SelfNCCH (including [[#RomFS|RomFS]])
| Yes
| No
| No
| No
| None
|-
| 0x00000004
| SaveData (the saveID/mediatype for this is loaded from data originally from the user process' exheader)
| Yes
| No
| No
| No
| None
|-
| 0x00000006
| ExtSaveData
| Yes
| No
| No
| Yes
| 0x100D, when the input extdataID isn't listed in the exheader.
|-
| 0x00000007
| Shared ExtSaveData
| Yes
| No
| No
| Yes
| None
|-
| 0x00000008
| SystemSaveData
| Yes
| No
| No
| Yes
| 0x4, when the input saveID doesn't match the exheader system-saveID.
|-
| 0x00000009
| SDMC
| Yes
| Yes
| No
| No
| 0x8E
|-
| 0x0000000A
| SDMC Write-Only
| Yes
| No
| No
| No
| 0x808E
|-
| 0x12345678
| ExtSaveData for BOSS
| Yes
| No
| No
| Yes
| 0x44
|-
| 0x12345679
| CARD SPI FS
| Yes
| Yes
| No
| No
| 0x16
|-
| 0x1234567B
| ExtSaveData, and ExtSaveData for BOSS
| No
| Yes
| No
| Yes
|
|-
| 0x1234567C
| SystemSaveData
| No
| Yes
| No
| Yes
|
|-
| 0x1234567D
| NAND RW
| Yes
| Yes
| No
| No
| 0x800
|-
| 0x1234567E
| NAND RO
| Yes
| Yes
| No
| No
| 0x200
|-
| 0x1234567F
| NAND RO Write FS
| No
| Yes
| No
| No
| ?
|-
| 0x12345680
| Extdata transfer. Used for transferring [[Extdata#NAND_Shared_Extdata|NAND Shared Extdata]] during [[System_Transfer#System_Save_Data_/_Shared_Extdata_Transfer|system tranfers]].
| Yes
| Yes
| No
| Yes
| ?
|-
| 0x12345681
| System Savedata transfer. Used for transferring [[System_SaveData|System Save Data]] during [[System_Transfer#System_Save_Data_/_Shared_Extdata_Transfer|system tranfers]].
| Yes
| Yes
| No
| Yes
| ?
|-
| 0x12345682
| Unknown. There's code for this in spider v9.9, but that code isn't actually used.
| Yes
| No
| No
| Yes
| ?
|-
| 0x2345678A
| Title access. With FS, this allows accessing NCCH/NCSD contents (ExeFS, RomFS, checking if a content uses a seed, checking the validity of the installed seed). FSPXI, additionally, allows opening raw NCCH/NCSD NCCH contents and DSiWare contents for reading, along with encrypted save data.
| Yes
| Yes
| No
| Yes
| 0x1005
|-
| 0x2345678B
| Used internally by Process9 as the lowest level title access archive. Allows for opening various sections of a title (TMD, CMD, raw contents, DLC contents, raw save data (including public/private/banner saves for DSiWare), title and/or content import context files and /data directories for save data.
| No
| No
| Yes
| Yes
|
|-
| 0x2345678C
| Used internally to access [[Title_Database|Title Database (/dbs)]] files. For SD, <code>title.db</code> and <code>import.db</code>. For NAND, <code>title.db</code>, <code>import.db</code>, <code>tmp_t.db</code>, <code>tmp_i.db</code>, and <code>jumpid.db</code>.
| No
| No
| Yes
| Yes
|
|-
| 0x2345678D
| Used internally to access non-title /dbs files on the NAND: <code>certs.db</code> and <code>ticket.db</code>.
| No
| No
| Yes
| No
|
|-
| 0x2345678E
| FSPXI: Program Access (limited subset of merged main title + update/patch title access). For fs:LDR(used by the "loader" FIRM ARM11-process), only <code>exefs:/.code</code>. Not accessible with fs:USER.
| Yes
| Yes
| No
| Yes
| None, see description.
|-
| 0x567890AB
| NAND CTR FS
| No
| Yes
| No
| No
| ?
|-
| 0x567890AC
| TWL PHOTO
| Yes
| Yes
| No
| No
| ?
|-
| 0x567890AD
| TWLS (DSi Sound stores recordings here). This is mapped to the FAT12 image stored in the file at [[Twln/shared2/0000]].
| No
| Yes
| No
| No
| ?
|-
| 0x567890AE
| NAND TWL FS
| Yes
| Yes
| No
| No
| 0x100
|-
| 0x567890AF
| NAND W FS
| Yes
| Yes
| No
| No
| 0x100
|-
| 0x567890B0
| Internally creates the same "ID Storage" wrapper over the NAND that is used for SystemSaveData and Shared ExtData, but all operations are stubbed and return 0xE0C046F8.
| No
| Yes
| No
| No
|
|-
| 0x567890B1
| Gamecard SaveData (for check). This is a wrapper for UserSaveDataForCheck: the OpenArchive code for that is called with archive-lowpath TID=0/mediatype=2(gamecard).
| Yes
| No
| No
| No
| 0x6
|-
| 0x567890B2
| UserSaveData (for check). This is the same as the regular SaveData archive, except with this the savedata ID and mediatype is loaded from the input archive lowpath.
| Yes
| No
| No
| Yes
| 0x6
|-
| 0x567890B3
| [[3DS_Virtual_Console#NAND_Savegame|AGB Save Data]]
| No
| No
| Yes
| No
| -
|-
| 0x567890B4
| Similar to 0x567890B2 but can only access Accessible Save specified in [[NCCH/Extended_Header#Storage_Info|exheader]]?
| Yes
| No
| No
| Yes
| ?
|}

Archives listed as not requiring a binary lowpath, use lowpath type [[FS:OpenFile|empty]].

The above permission bitmasks are from v2.x, see the above Services section for how these are handled.

Archives CTR NAND, NAND RO Write FS, TWL NAND, NAND W FS, and CARD SPI FS require the corresponding process exheader access control mount flag to be set, in the exheader for any of the currently running ARM11 processes, for [[Filesystem_services_PXI|FSPXI]]. The access rights checked by [[Filesystem services|FS]] module for archive mounting with fs:USER, are stored in the process' exheader accessinfo.

The CARDSPI archive allows access to the gamecard CARD1 raw savedata flash(aka "cardspi:/" in [[FIRM|Process9]]), the file lowpath must be WCHAR "/". The "NAND W FS" archive allows access to the raw NAND image(aka "wnand:/" in Process9), the file lowpath must be WCHAR "/".

= Filenames and Paths =
{{Anchor|PathType}}
==PathType==
{| class="wikitable" border="1"
|-
! Value
! Description
|-
| -1
| Returned internally by Process9, when errors occur it seems(in particular when no nul-terminator was found in the input path). The data ptr is set to NULL.
|-
| 0x0
| INVALID - Specifies an invalid path
|-
| 0x1
| EMPTY - Specifies an empty path
|-
| 0x2
| BINARY - Non-text based path. Meaning is per-archive
|-
| 0x3
| ASCII - Text-based path with 7-bit ASCII characters padded to 8-bits each (signed char)
|-
| 0x4
| UTF16 - Text-based path with UTF-16 characters
|}

In IPC requests, sizes of ASCII and UTF16 paths must include space for the null-terminator.

== Binary LowPath ==
The format of the data that a binary LowPath points to is custom per archive.

=== SystemSaveData / Extdata / Shared Extdata Archive Path Data Format ===

==== DataAccessPath ====

{| class="wikitable" border="1"
|-
! Offset !! Size !! Description
|-
| 0x0 || 0x1 || u8 [[Mediatypes|Mediatype]]
|-
| 0x1 || 0x1 || only for NAND data (System Savedata / Shared Extdata), otherwise left 0:
{| class="wikitable" border="1"
|-
! Value !! Description
|-
| 0 || Accesses from/to <code>nand:/data/<ID0 of current system></code>
|-
| 1 || Accesses from/to <code>nand:/fixdata</code>
|-
| 2 || Accesses from/to <code>nand:/data/<ID0 from [[Filesystem_services#DeviceMoveContext|Device Move Context]]></code>
|}
|-
| 0x2 || 0x2 || padding
|}

==== SystemSaveData ====

===== FS =====

====== Archive Path ======
{| class="wikitable" border="1"
|-
! Index word
! Description
|-
| 0
| [[Filesystem_services#DataAccessPath|DataAccessPath]]
|-
| 1
| save ID low (save ID high is 0)
|}

====== File Path ======
The file path is a cleartext ASCII or UTF16 file path (<code><file path></code>).

The file path would access the file at <code><base path>/sysdata/<save ID low>/<save ID high>/<file path></code>.
Note that <code>/<file path></code> refers to the virtual file system inside the </code><save ID high></code> file.

===== FSPXI / FS System Savedata Transfer / FSPXI System Savedata Transfer =====

====== Archive Path ======
{| class="wikitable" border="1"
|-
! Index word
! Description
|-
| 0
| [[Filesystem_services#DataAccessPath|DataAccessPath]]
|}

====== File Path ======
{| class="wikitable" border="1"
|-
! Index word !! Description
|-
| 0 || save ID low
|-
| 1 || save ID high
|}

The file path would access the file at <code><base path>/sysdata/<save ID low>/<save ID high></code>.

==== Extdata / Shared Extdata ====

===== FS / FS Extdata Transfer / FSPXI Extdata Transfer =====

====== Archive Path ======
{| class="wikitable" border="1"
|-
! Index word
! Description
|-
| 0
| [[Filesystem_services#DataAccessPath|DataAccessPath]]
|-
| 1
| ext save ID low
|-
| 2
| ext save ID high
|}

This refers to the extdata filesystem structure's base directory at <code><base path>/extdata/<ext save ID low>/<ext save ID high></code>.

====== File Path ======
The file path is a cleartext ASCII or UTF16 file path (<code><file path></code>).

For FS Extdata, this would acccess <code><base path>/extdata/<save ID low>/<save ID high>/<directory ID>/<file ID>/<file path></code>, and <code>/<file path></code> refers to the virtual file system inside the </code><file ID></code> file.

For FS / FSPXI Extdata Transfer, this accesses <code><base path>/extdata/<save ID low>/<save ID high>/<file path></code>.

=== UserSaveDataForCheck Archive Path Data Format ===
{| class="wikitable" border="1"
|-
! Index word
! Description
|-
| 0
| [[Mediatypes|Mediatype]] (must be non-zero)
|-
| 1
| Lower word saveid
|-
| 2
| Upper word saveid
|}

The file/directory lowpath for this FS archive is a text path in the [[Savegames|savegame]] filesystem.

=== 0x567890B4 Archive Path Data Format ===
{| class="wikitable" border="1"
|-
! Index word
! Description
|-
| 0
| [[Mediatypes|Mediatype]]
|-
| 1
| <code><nowiki>Lower_word_saveid >> 8</nowiki></code> ?
|-
| 2
| Unknown. Game calculate this using formula <code><nowiki>0xFFFFFF00 | unknown_b</nowiki></code>
|}

=== Title Access Archive Path Data Format ===
==== Title Access Type ====
{| class="wikitable" border="1"
|-
! Value !! Description
|-
| 0 || High-level NCCH content access
|-
| 1 || Save data access (high-level, decrypted)
|-
| 2 || Raw content (low-level NCCH/SRL) access
|-
| 3 || Banner save data access (for DSiWare titles)
|-
| 4 || FS only: Save data transfer (internally uses generated data from [[FS:BeginSaveDataMove]] as the IV for "Save data access (low-level, encrypted)")
|-
| 5 || Save data access (low-level, encrypted)
|}

==== NCCH Access Type ====
{| class="wikitable" border="1"
|-
! Value !! Description
|-
| 0 || RomFS
|-
| 1 || <code>exefs:/.code</code>
|-
| 2 || System Menu Data (<code>exefs:/icon</code>, <code>exefs:/banner</code>, <code>exefs:/logo</code>)
|-
| 3 || NCCH Header(s)
|-
| 4 || "is seeded" check
|-
| 5 || Seed verify/validate
|}

==== NCCH Header Access Type ====
{| class="wikitable" border="1"
|-
! Value !! Description
|-
| 0 || [[NCCH/Extended_Header|Extheader]] (0x0-0x400)
|-
| 1 || [[NCCH/Extended_Header|Extheader]] AccessDesc (0x400-0x800)
|-
| 2 || Raw [[NCCH#NCCH_Header|NCCH Header]]
|}

==== Archive Path ====

{| class="wikitable" border="1"
|-
! Offset !! Size !! Description
|-
| 0x0 || 0x8 || Program ID (Title ID)
|-
| 0x9 || 0x1 || [[Mediatypes|Media Type]]
|-
| 0xA || 0x7 || padding
|}

==== File Path ====

{| class="wikitable" border="1"
|-
! Offset !! Size !! Description
|-
| 0x0 || 0x4 || [[Filesystem_services#Title_Access_Type|Title Access Type]]
|-
| 0x4 || 0x10 || Dynamic data depending on [[Filesystem_services#Title_Access_Type|Title Access Type]]:

{| class="wikitable" border="1"
|-
! High Level NCCH Access !! Save Data Access (high level) !! Raw Content !! FS only: Save Data Transfer
|-
|
{| class="wikitable" border="1"
|-
! Offset !! Size !! Description
|-
| 0x0 || 0x4 || Content index from TMD for NAND/SD titles
NCSD partition index for gamecards
|-
| 0x4 || 0x4 || [[Filesystem_services#NCCH_Access_Type|NCCH Access Type]]
|-
| 0x8 || 0x8 || Dynamic data depending on [[Filesystem_services#NCCH_Access_Type|NCCH Access Type]]:
For ExeFS, (System Menu Data / <code>exefs:/.code</code>),

{| class="wikitable" border="1"
| 8-byte ExeFS file name
|}

For Header Access,

{| class="wikitable" border="1"
| [[Filesystem_services#NCCH_Header_Access_Type|u64, NCCH Header Access Type]]
|}

For RomFS,

{| class="wikitable" border="1"
| [[NCCH#Content_Types|u64, Allowed content types flag]]
(<code>(1 << allowed_type_a) |

(1 << allowed_type_b)...</code>)
|}

|}
|
{| class="wikitable" border="1"
|-
! Offset !! Size !! Description
|-
| 0x0 || 0x10 || 16-byte IV for save data crypto
|}
|
{| class="wikitable" border="1"
|-
! Offset !! Size !! Description
|-
| 0x0 || 0x4 || Content index from TMD for NAND/SD titles
NCSD partition index for gamecards
|-
| 0x4 || 0xC || padding
|}
|
{| class="wikitable" border="1"
|-
! Offset !! Size !! Description
|-
| 0x0 || 0x4 || Save data transfer key from [[FS:BeginSaveDataMove]]
|-
| 0x4 || 0xC || padding
|}
|}
|-
| 0x14 || 0x10 || 16-byte seed for titles that require one, or for validating a seed against the check value in the [[NCCH#NCCH_Header|NCCH Header]]'s check value.
If the title does not use a seed, this should not be included and size 0x14 should be used instead of 0x24.
|}

For encrypted save data access and banner save data access, the entire 0x10 portion of the dynamic data is left blank.

The "is seeded check" NCCH access type opens a virtual 1-byte file that reads either 0 or 1; this value is generated on-the-fly and will be 1 if ncchflags[7] has bit5 set (content uses seed), and 0 otherwise.

For NCCH sections that require a seed (e.g. <code>.code</code>, RomFS, etc.), the additional seed portion of the low path must be populated with the correct seed.

The "Seed Verify/Validate" NCCH access type also requires the seed portion of the lowpath. The target NCCH content is opened (with the opened file interface being stubbed, meaning no real reads/writes can be performed on it), and the given seed is used to calculate the seed check hash, and part of it is compared to the check value in the NCCH header. If it matches, opening the "file" succeeds, otherwise 0xD900458C is returned. If attempt is made to use the seed validation type on a content that does not use a seed, error 0xC92044E6 is returned.

==== FS Limitations ====

For FS, this archive functions the same, except for the following limitations:

- Only the title access types "High Level NCCH Access" and "High Level Save Data Access", and "Save Data Transfer" are allowed.

- For high level NCCH access, the types "RomFS", "System Menu Data", "Seeded check", and "Seed Check/Verify" are allowed.

- For "Seed Check/Verify", rather than providing the title seed in the file path (as is the case for FSPXI), the seed is retrieved from the seed database (meaning the file lowpath size is always 0x14 for FS).

=== Program Access / SelfNCCH access ===

Provides access to a "merged" archive of a base title and, optionally, a separate update (patch) title.

If no patch title exists, the base title is considered to be the patch title, i.e. turning all "patch" accesses into accesses to the base title.

==== Program Access Type ====
{| class="wikitable" border="1"
|-
! Value !! Description !! Accesses
|-
| 0 || RomFS ("unspecified" [[NCCH#Content_Type|content type]], the default) || Base title
|-
| 1 || <code>exefs:/.code</code> || Patch title
|-
| 2 || System Menu Data (<code>exefs:/icon</code>, <code>exefs:/banner</code>, <code>exefs:/logo</code>) || Base title
|-
| 3 || Save Data (high level, decrypted) || -
|-
| 4 || RomFS (all [[NCCH#Content_Type|content types]]) || Base title
|-
| 5 || RomFS ("unspecified" [[NCCH#Content_Type|content type]], the default) || Patch title
|}

==== Archive Path ====
{| class="wikitable" border="1"
|-
! Offset !! Size !! Description
|-
| 0x0 || 0x8 || u64, Program Handle from [[PXIPM:RegisterProgram]]
|}

==== File Path ====
{| class="wikitable" border="1"
|-
! Offset !! Size !! Description
|-
| 0x0 || 0x4 || [[Filesystem_services#Program_Access_Type|Program Access Type]]
|-
| 0x4 || 0x8 || Dynamic data depending on [[Filesystem_services#Program_Access_Type|Program Access Type]]:
{| class="wikitable" border="1"
|-
! ExeFS files (System Menu Data, etc.) !! RomFS of base title (all [[NCCH#Content_Type|content types]])
|-
|
{| class="wikitable" border="1"
| 8-character ExeFS filename
|}
|
{| class="wikitable" border="1"
|-
! Offset !! Size !! Description
|-
| 0x0 || 0x4 || u32, content index of target content
|-
| 0x4 || 0x4 || padding
|}
|}
|}

==== FS Limitations ====

- FSPXI allows all access types.

- When used through fs:LDR by loader, FS only provides access to <code>exefs:/.code</code>.

- For SelfNCCH access, the only allowed access types are "RomFS ("unspecified" [[NCCH#Content_Type|content type]], the default)" of the Base or Patch title, and "System Menu Data". Attempting to access "Save Data" results in error 0xE0E046BE, "RomFS (all [[NCCH#Content_Type|content types]])" in 0xF9604784, and "<code>exefs:/.code</code>" in 0xD9004676.

=== [[RomFS]] ===

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.

With FSPXI the returned data for RomFS is the entire RomFS section from the NCCH, starting at the IVFC header.

The 0x3 archive is an interface for the 0x2345678E archive with the current process programID+mediatype. The file lowpath is 3-words. These words are written to 0x2345678E-archive file_lowpath+0, with the rest of that lowpath set to all-zero(lowpath is different from archive 0x2345678A). File lowpath:
{| class="wikitable" border="1"
|-
! Index word
! Description
|-
| 0
| See above. The only values which FS-module doesn't allow to be used here are:
* 0x1: Error 0xE0E046BE.
* 0x3: Error 0xE0E046BE.
* 0x4: FS-module executes svcBreak when using this.
|-
| 1-2
| See above. Not validated by FS-module.
|}

=Anti Savegame Restore=
Anti Savegame Restore, internally referred to as ''Save Data Rollback Prevention'', is a feature originally implemented in the FS module with [[4.0.0-7]], which prevents the user from restoring previous versions of a savegame image. This feature is not used (in practice) for gamecard games. When an old version of the save is detected, the application will display an error regarding old savegame version, then delete and recreate the save data (similar to when it is corrupted).

==Implementation==
When creating the savedata, the application generates a secure value (a 64 bit unsigned integer), then stores it in either the [[DISA_and_DIFF#DISA_header|DISA save image header]] or the [[Filesystem_services#Anti_Savegame_Restore_Save_Data|Anti Savegame Restore Save Data]]. The application then uses the anti-savegame-restore commands ([[FS:SetSaveDataSecureValue]], [[FS:GetSaveDataSecureValue]], [[FS:SetOtherSaveDataSecureValue]], [[FS:GetOtherSaveDataSecureValue]], [[FS:SetThisSaveDataSecureValue]], [[FS:GetThisSaveDataSecureValue]], [[FS:SetSaveArchiveSecureValue]] and [[FS:GetSaveArchiveSecureValue]]) to verify the value known to the game for comparison with the value returned by FS, and to update the value in the corresponding storage location.

Each time the application writes to the savegame, the value should be updated by both the application and through FS. Usually, applications update this value by incrementing it. However, generating a new random-number or other methods of updating it can be used as well.

==Anti Savegame Restore Save Data==
The save data used for this feature is stored in [[System_SaveData|System Save Data]] ID 0x00010011 and contains only one file, named <code>DB</code>:

===Main Structure===
{| class="wikitable" border="1"
|-
! Offset !! Size !! Description
|-
| 0x0 || 0x1000 || Header
{| class="wikitable" border="1"
|-
! Offset !! Size !! Description
|-
| 0x0 || 0x1 || u8, version (usually 0)
|-
| 0x1 || 0x3 || padding
|-
| 0x4 || 0x4 || u32, number of secure value entries
|-
| 0x8 || 0xFF8 || completely unused, padding
|}
|-
| 0x1000 || 0x1C000 (8 * 14336) || [[Filesystem_services#SecureValueKey|Secure value keys]]
|-
| 0x1D000 || 0x1C000 (8 * 14336) || u64s, Secure values
|}

===SecureValueKey===
Depending on which command is used, secure value keys can be interpreted as:
{| class="wikitable" border="1"
|-
! Offset !! Size !! Description
|-
| 0x0 || 0x8 || u64, Title ID
|}
or:
{| class="wikitable" border="1"
|-
! Offset !! Size !! Description
|-
| 0x0 || 0x4 || u32, [[Filesystem_services#SecureValueSlot|Secure Value Slot]]
|-
| 0x4 || 0x4 || u32, Unique ID
|}

==Applications using this feature==
* Animal Crossing: New Leaf
* Pokemon X & Y
* Pokemon Omega Ruby & Alpha Sapphire
* Pokemon Omega Ruby & Alpha Sapphire Demo
* Pokemon Shuffle
* Super Smash Bros
* Pokemon Red,Blue and Yellow (GB(C) VC)
* Rusty's Real Deal Baseball
* Megami Meguri

=SEEDDB and TITLETAG=
With [[9.6.0-24|9.6.0-X]] new [[System_SaveData]] with save ID 0x0001000F was added. This save data contains both the NCCH seed database (SEEDDB) and the title tag database (TITLETAG).

These databases are managed by the commands [[FS:AddSeed]], [[FS:GetSeed]], [[FS:DeleteSeed]], [[FS:GetNumSeeds]] and [[FS:ListSeeds]] for SEEDDB, and [[FS:AddTitleTag]], [[FS:GetTitleTag]], [[FS:DeleteTitleTag]], [[FS:GetNumTitleTags]], and [[FS:ListTitleTags]] for TITLETAG respectively.

Both the [[Home_Menu|HOME Menu]] and the [[NIM_Services|NIM]] module have access to these commands.

==SEEDDB==

Stored in the system savedata archive 0x0001000F as a file named <code>SEEDDB</code>, it contains the title-unique seed-data used for the new [[NCCH]] keyY generation added with FIRM [[9.6.0-24|9.6.0-X]].

The file follows a simple key-value format allowing the storage of seed data for up to 2000 unique title IDs.

{| class="wikitable" border="1"
|-
! Offset !! Size !! Description
|-
| 0x0 || 0x1000 || Header
{| class="wikitable" border="1"
|-
! Offset !! Size !! Description
|-
| 0x0 || 0x1 || u8, version (usually 0)
|-
| 0x1 || 0x3 || padding
|-
| 0x4 || 0x4 || u32, number of seed entries
|-
| 0x8 || 0xFF8 || completely unused, padding
|}
|-
| 0x1000 || 0x3E80 (8 * 2000) || u64s, Title IDs
|-
| 0x4E80 || 0x7D00 (16 * 2000) || Seed data, 16 bytes per seed
|}

==TITLETAG Database==

Stored in the system savedata archive 0x0001000F as a file named <code>TITLETAG</code>, it contains information used by the [[Home_Menu|HOME Menu]] to handle cases when a to-be-released title has been purchased already, that is, to properly install the seed required for [[NCCH]] keyY generation added with FIRM [[9.6.0-24|9.6.0-X]].

When a to-be-released title is purchased, the [[NIM_Services|NIM]] module installs a [[Filesystem_services#TitleTag|title tag]] with enough information about the title for the [[Home_Menu|HOME Menu]] to be able to initiate a seed import once the title has been released (and thus, the title's NCCH content lock seed). Until the title's seed is released, and while the title tag remains in the database, the HOME Menu will prevent the user from launching the software as it would not run without the seed. Once released, information from the title tag is used to download the seed, and, if successful, the title tag is removed from the database, making the software playable.

The file follows a simple key-value format allowing the storage of title tag data for up to 2000 unique title IDs.

{| class="wikitable" border="1"
|-
! Offset !! Size !! Description
|-
| 0x0 || 0x1000 || Header
{| class="wikitable" border="1"
|-
! Offset !! Size !! Description
|-
| 0x0 || 0x1 || u8, version (usually 0)
|-
| 0x1 || 0x3 || padding
|-
| 0x4 || 0x4 || u32, number of entries
|-
| 0x8 || 0xFF8 || completely unused, padding
|}
|-
| 0x1000 || 0x3E80 (8 * 2000) || u64s, Title IDs
|-
| 0x4E80 || 0x3E800 (0x80 * 2000) || [[Filesystem_services#TitleTag|Title Tag]] data, 0x80 bytes per entry
|}

= Common Types =
== MediaType ==
{| class="wikitable" border="1"
|-
! Value
! Description
|-
| 0
| NAND
|-
| 1
| SD
|-
| 2
| Game Card
|}

== SystemMediaType ==
{| class="wikitable" border="1"
|-
! Value
! Description
|-
| 0
| CTR NAND
|-
| 1
| TWL NAND
|-
| 2
| SD
|-
| 3
| TWL Photo
|}

== OpenFlags ==
{| class="wikitable" border="1"
|-
! Bit
! Description
|-
| 0
| Read
|-
| 1
| Write
|-
| 2
| Create
|}

== Attributes ==
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x1
| Is Directory
|-
| 0x1
| 0x1
| Is Hidden
|-
| 0x2
| 0x1
| Is Archive
|-
| 0x3
| 0x1
| Is Read-Only
|}

== WriteOption ==
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x1
| Flush
|-
| 0x1
| 0x1
| Update Time Stamp
|-
| 0x2
| 0x1
| Reserved
|-
| 0x3
| 0x1
| Reserved
|}

== DirectoryEntry ==
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x20C
| UTF-16 Entry Name
|-
| 0x20C
| 0xA
| 8.3 short filename name
|-
| 0x216
| 0x4
| 8.3 short filename extension
|-
| 0x21A
| 0x1
| Always 1
|-
| 0x21B
| 0x1
| Reserved
|-
| 0x21C
| 0x4
| [[Filesystem_services#Attributes|Attributes]]
|-
| 0x220
| 0x8
| Entry Size
|}

== ArchiveResource ==
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x4
| Sector byte-size
|-
| 0x4
| 0x4
| Cluster byte-size
|-
| 0x8
| 0x4
| Partition capacity in clusters
|-
| 0xC
| 0x4
| Available free space in clusters
|}

== ProgramInfo ==
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x8
| Program ID
|-
| 0x8
| 0x1
| [[Filesystem_services#MediaType|Media Type]]
|-
| 0x9
| 0x7
| Padding
|}

== ProductInfo ==
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x10
| Product Code
|-
| 0x10
| 0x2
| Company Code
|-
| 0x12
| 0x2
| Remaster Version
|}

== IntegrityVerificationSeed ==
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x10
| AES-CBC MAC over a SHA256 hash, which hashes the first 0x110-bytes of the cleartext SEED.
|-
| 0x10
| 0x120
| The [[nand/private/movable.sed]], encrypted with AES-CBC using the above MAC for the counter.
|}

== ExtSaveDataInfo ==
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x4
| [[Filesystem_services#DataAccessPath|DataAccessPath]]
|-
| 0x4
| 0x8
| Save ID
|-
| 0xC
| 0x4
| Reserved
|}

== SystemSaveDataInfo ==
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x4
| [[Filesystem_services#DataAccessPath|DataAccessPath]]
|-
| 0x4
| 0x4
| Save ID
|}

== SecureValueSlot ==
{| class="wikitable" border="1"
|-
! Value
! Description
|-
| 0x1000
| SD Application
|}

== SecureValueEntry ==
{| class="wikitable" border="1"
|-
! Offset !! Size !! Description
|-
| 0x0 || 0x4 || u32, [[Filesystem_services#SecureValueSlot|Secure Value Slot]]
|-
| 0x4 || 0x1 || When used as an input entry:
{| class="wikitable" border="1"
|-
! Value !! Description
|-
| 0 || This entry should be removed.
|-
| 1 || This entry should be updated with the given value.
|}
When returned from a command:
{| class="wikitable" border="1"
|-
! Value !! Description
|-
| 0 || No entry with the given slot and title ID was found, or: this entry is unused.
|-
| 1 || The entry with the given slot and title ID was found, or: this entry is used.
|}
|-
| 0x5 || 0x3 || padding
|-
| 0x8 || 0x8 || u64, Secure Value
|}

== TitleTag ==
{| class="wikitable" border="1"
|-
! Offset !! Size !! Description
|-
| 0x0 || 0x4 || Magic, <code>PREP</code> (PREPurchase install)
|-
| 0x4 || 0x4 || s32, Release date year
|-
| 0x8 || 0x1 || u8, Release date month
|-
| 0x9 || 0x1 || u8, Release date day
|-
| 0xA || 0x2 || u16, Country code
|-
| 0xC || 0x4 || u32, Seed status (0: not downloaded yet, 1: last download attempt failed, 2: seed installed successfully)
|-
| 0x10 || 0x4 || Result code from last seed installation attempt
|-
| 0x14 || 0x4 || Support error code from last seed installation attempt
|-
| 0x18 || 0x68 || reserved padding (unused)
|}

== CardSpiBaudRate ==
{| class="wikitable" border="1"
|-
! Value
! Description
|-
| 0x0
| 512KHz
|-
| 0x1
| 1MHz
|-
| 0x2
| 2MHz
|-
| 0x3
| 4MHz
|-
| 0x4
| 8MHz
|-
| 0x5
| 16MHz
|}

== CardSpiBusMode ==
{| class="wikitable" border="1"
|-
! Value
! Description
|-
| 0x0
| 1-bit
|-
| 0x1
| 4-bit
|}

== SpecialContentType ==
{| class="wikitable" border="1"
|-
! Value
! Description
! Found in
|-
| 0x1
| CTR (Old3DS) Update Partition
| Gamecards
|-
| 0x2
| Manual
| Gamecards, Digital titles
|-
| 0x3
| DLP Child
| Gamecards, Digital titles
|-
| 0x4
| KTR (New3DS) Update Partition
| Gamecards
|-
|}

== DeviceMoveContext ==
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x10
| IVs (ID0 of source console)
|-
| 0x10
| 0x10
| Encrypt Parameter (used to calculate the IV for encryption)
|}

=Errors=
See [[Filesystem_services_PXI]].

[[Category:Services]]

APT:StartNewestHomeMenu

2025-06-14T22:17:56Z

Gruetzig: fix numbering

=Request=
{| class="wikitable" border="1"
|-
! Index Word
! Description
|-
| 0
| Header code [0x00200044]
|-
| 1
| Parameters Size
|-
| 2
| 0x0
|-
| 3
| Handle Parameter
|-
| 4
| (Parameters Size << 14) <nowiki>|</nowiki> 2
|-
| 5
| void*, Parameters
|}

=Response=
{| class="wikitable" border="1"
|-
! Index Word
! Description
|-
| 0
| Header code
|-
| 1
| Result code
|}

=Description=
None of the input parameters are used by NS. [[APT:PrepareToStartNewestHomeMenu]] must be used prior to using this command. After initializing [[FIRM]] params and [[PMApp:SetFIRMLaunchParams|setting]] the FIRM params, this uses command [[PTMSYSM:LaunchFIRMRebootSystem]] with timeout 1000000000*4.