6,264
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − + − + − (where ID0 is the first 0x10-bytes from a SHA256 [[nand/private/movable.sed|hash]]) (The installation of [[SD Filesystem|SD Card]] titles was introduced in [[2.0.0-2]] update and the SD Card dbs files are encrypted.)+ − + Line 12:
Line 12: − +
no edit summary
These files contain data relating to install/usage/management of installed 3DS titles. Currently, only the directory location for the [[SD Filesystem|SD Card]] is known:
These files contain data relating to install/usage/management of installed 3DS titles. The database files are located at:
* nand/???/dbs
* nand/data/<ID0>/dbs
* sdmc/Nintendo 3DS/<ID0>/<ID1>/dbs
* sdmc/Nintendo 3DS/<ID0>/<ID1>/dbs
ID0 is the first 0x10-bytes from a SHA256 [[nand/private/movable.sed|hash]]. (The installation of [[SD Filesystem|SD Card]] titles was introduced in [[2.0.0-2]] update and the dbs files are encrypted.)
There are only two files in this directory:
There are only two files in this directory, for SD card:
/import.db
/import.db
/title.db
/title.db
"'''title.db'''" - This 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 [[Title Data Structure|.cmd]] file which contains data from the title TMD used for anti-tampering purposes).
"'''title.db'''" - This 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 [[Title Data Structure|.cmd]] file which contains data from the title TMD used for anti-tampering purposes).
*This data is taken from the title's [[Title Data Structure|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.
*This data is taken from the title's [[Title Data Structure|TMD]] and [[NCCH#CXI|executable NCCH]] during install, this is also partly 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.
*This file '''does not''' store a hash of the [[Title Data Structure|.cmd]] file for each given title, but the title.db expects to find a [[Title Data Structure|.cmd]] with a name specific to the title version, and the nature of the [[Title Data Structure|.cmd]] file makes re-naming/editing or using under a different title ID(by the end user) detectable (users of retail consoles are not going to have more than one .cmd files for a given titleID/title version).
*This file '''does not''' store a hash of the [[Title Data Structure|.cmd]] file for each given title, but the title.db expects to find a [[Title Data Structure|.cmd]] with a name specific to the title version, and the nature of the [[Title Data Structure|.cmd]] file makes re-naming/editing or using under a different title ID(by the end user) detectable (users of retail consoles are not going to have more than one .cmd files for a given titleID/title version).
*Since this file controls what titles are accessible to the 3DS, it is possible to move between different versions of a title if you have the title.db and title data for each version of that specific title.
*Since this file controls what titles are accessible to the 3DS, it is possible to move between different versions of a title if you have the title.db and title data for each version of that specific title.