Changes

The 3DS uses an SD Card for general storage of additional game data, music and photos taken with the 3DS.

The 3DS uses an SD Card for general storage of additional game data, music and photos taken with the 3DS.

/DCIM - Photos and images downloaded with the Internet Browser.

(Most 3DS SD card data is stored under "/Nintendo 3DS/<ID0>/<ID1>", where ID0 is the first 0x10-bytes from a SHA256 [[nand/private/movable.sed|hash]].

/Music - Music Files

/Nintendo 3DS - Game Data

/DCIM with [[3.0.0-5]] also stores .avi 3D videos from the camera title, video frames use MJPG.

* sdmc/DCIM - Photos/Videos and images downloaded with the Internet Browser. Video feature introduced with [[3.0.0-5]]  

Most 3DS SD card data is stored under "/Nintendo 3DS/<ID0>/<ID1>", where ID0 is the first 0x10-bytes from a SHA256 [[nand/private/movable.sed|hash]].

(the 3D videos are in .avi format and the video frames use MJPG.)

== Extdata ==

== Extdata ==

All "extra data" under [[extdata]] is encrypted. Extdata can't be decrypted with the xorpad fail used for old FLASH saves. All "extra data" files can't be copied to other 3DS SD cards, they are locked to the console.

All "extra data" under [[extdata]] is encrypted. Extdata can't be decrypted with the xorpad fail used for old FLASH saves. All "extra data" files can't be copied to other 3DS SD cards, they are locked to the console.

== import.db and title.db ==

== dbs ==

These two files, introduced with the [[2.0.0-2]] update, are used to manage 3DS titles installed to the SD Card and are part of the DRM for SD Card Titles. They are encrypted.

Introduced with the [[2.0.0-2]] update, this directory contains two files which are used to manage 3DS titles installed to the SD Card and are part of the DRM for SD Card Titles. They are encrypted.

  /Nintendo 3DS/<SomeID>/<SomeID>/dbs/import.db

  /dbs/import.db

                                    /title.db

    /title.db

"'''title.db'''" - The "title.db" file (among other things perhaps), archives data about titles installed on the SD Card which includes their [[Serials#Product Code|Product Code]], whether the title uses an [[NCCH#CFA|electronic manual]], Title ID, Title size and Title Version(the title version determines the name of the [[SD Filesystem#title|.cmd]] file which contains data from the title TMD used for anti-tampering purposes). This file '''does not''' store a hash of the [[SD Filesystem#title|.cmd]] file for each given title, but the title.db expects to find a [[SD Filesystem#title|.cmd]] with a name specific to the title version, and the nature of the [[SD Filesystem#title|.cmd]] file makes re-naming/editing or using under a different title ID(by the end user) detectable (finding/creating an additional .cmd file for a specific title i.e. having two different sets of app data from the same version/title ID is not feasible for retail units). This data is taken from the title's [[SD Filesystem#title|TMD]] and [[NCCH#CXI|executable NCCH]] during install, this is also party why the encrypted TMD found in each title directory is redundant, as the important information is moved to the ".db" and ".cmd" files during title installation.  

"'''title.db'''" - The "title.db" file (among other things perhaps), archives data about titles installed on the SD Card which includes their [[Serials#Product Code|Product Code]], whether the title uses an [[NCCH#CFA|electronic manual]], Title ID, Title size and Title Version(the title version determines the name of the [[SD Filesystem#title|.cmd]] file which contains data from the title TMD used for anti-tampering purposes). This file '''does not''' store a hash of the [[SD Filesystem#title|.cmd]] file for each given title, but the title.db expects to find a [[SD Filesystem#title|.cmd]] with a name specific to the title version, and the nature of the [[SD Filesystem#title|.cmd]] file makes re-naming/editing or using under a different title ID(by the end user) detectable (finding/creating an additional .cmd file for a specific title i.e. having two different sets of app data from the same version/title ID is not feasible for retail units). This data is taken from the title's [[SD Filesystem#title|TMD]] and [[NCCH#CXI|executable NCCH]] during install, this is also party why the encrypted TMD found in each title directory is redundant, as the important information is moved to the ".db" and ".cmd" files during title installation.