Title Database - Revision history

Ihaveamac: /* Title Info Entry */ tickets may be larger than 0x350

2023-09-13T09:16:27Z

Title Info Entry: tickets may be larger than 0x350

← Older revision		Revision as of 13:16, 13 September 2023
Line 223:		Line 223:
	\| 0x0		\| 0x0
	\| 4		\| 4
	\| Ticket data size X (=0x350)		\| Ticket data size X (often 0x350 but some DLC tickets may be larger)
	\|-		\|-
	\| 0x4		\| 0x4

Ihaveamac: /* Title Info Entry */ document actual ticket.db title info (multiple tickets can be installed for one Title ID)

2023-09-13T09:13:12Z

Title Info Entry: document actual ticket.db title info (multiple tickets can be installed for one Title ID)

← Older revision		Revision as of 13:13, 13 September 2023
Line 198:		Line 198:
	\|}		\|}

	For ticket.db title info ~~contains~~ a ~~small~~ header ~~and~~ actual ticket data:		For ticket.db title info, there is a header indicates ticket count (as a Title ID can have more than one ticket installed). Then each entry contains the size, followed by the actual ticket data.
	{\| class="wikitable"		{\| class="wikitable"
			\|+ Header
	\|-		\|-
	! Start		! Start
Line 207:		Line 208:
	\| 0x0		\| 0x0
	\| 4		\| 4
	\| ~~Unknown (always 0x00000001?)~~		\| Amount of tickets X
	\|-		\|-
	\| 0x4		\| 0x4
			\| X * (size of tickets + 4)
			\| Ticket entries
			\|}
			{\| class="wikitable"
			\|+ Ticket entry
			\|-
			! Start
			! Length
			! Description
			\|-
			\| 0x0
	\| 4		\| 4
	\| Ticket data size X (=0x350)		\| Ticket data size X (=0x350)
	\|-		\|-
	\| ~~0x8~~		\| 0x4
	\| X		\| X
	\| [[Ticket\|Ticket]] data		\| [[Ticket\|Ticket]] data

Ihaveamac: /* Title Info Entry */ 0x350 appears here, not 0x530

2019-05-30T23:25:07Z

Title Info Entry: 0x350 appears here, not 0x530

← Older revision		Revision as of 03:25, 31 May 2019
Line 211:		Line 211:
	\| 0x4		\| 0x4
	\| 4		\| 4
	\| Ticket data size X (=~~0x530~~)		\| Ticket data size X (=0x350)
	\|-		\|-
	\| 0x8		\| 0x8

Wwylele: Migrate to Inner FAT

2019-05-03T20:03:21Z

Migrate to Inner FAT

Show changes

Wwylele: Redirect extdata to DIFF format; Remove dead link

2018-01-04T10:24:51Z

Redirect extdata to DIFF format; Remove dead link

← Older revision		Revision as of 13:24, 4 January 2018
Line 4:		Line 4:
	* 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 the [[2.0.0-2]] update and the SD dbs files are encrypted. These files are [[~~extdata~~]] ~~images~~. ~~The NAND extdata images are cleartext~~, ~~however some~~ of the ~~images contain data encrypted with a console-unique keyslot~~.		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 the [[2.0.0-2]] update and the SD dbs files are encrypted by [[SD Filesystem\|the general SD filesystem encryption rule]]. These files are [[DISA and DIFF\|DIFF containers]]. These DIFF files do not use external IVFC level 4, so all database data is duplicated in the container. In this page only the inner content of the container is described.

	These files are only created on SD (via [[Application_Manager_Services\|AM]]) if they don't exist when the [[eShop]] application is starting up, during network init etc (prior to showing the "system update required" dialog).		These files are only created on SD (via [[Application_Manager_Services\|AM]]) if they don't exist when the [[eShop]] application is starting up, during network init etc (prior to showing the "system update required" dialog).
Line 14:		Line 14:
	! Stored in CTR-NAND		! Stored in CTR-NAND
	! Filename		! Filename
	! [[~~Savegames~~#~~AES_MAC_header~~\|CTR-9DB0]] ID		! [[DISA and DIFF#CTR-9DB0\|CTR-9DB0]] ID
	! Description		! Description
	\|-		\|-
Line 54:		Line 54:
	\|}		\|}

	The SD dbs images use the same [[nand/private/movable.sed\|keyslot]] as the other SD/NAND savedata images for the AES-MAC. The NAND dbs images for the AES-MAC use a console-unique keyslot where the keyX and keyY for it are initialized by bootrom.		The inner content of the container consists of a pre-header with size of 0x80 identifying the Database Type, followed by a BDRI container. The offsets in the BDRI header are usually relative to the offset to the start of the BDRI header (0x80 in the file)

	~~The *.db [[extdata\|Extdata]] images do not use a DATA partition, so there are two versions~~ of the ~~database in the image, an active and old version (the active one is defined by the DIFF header). These database files consist~~ of a pre-header with size of 0x80 identifying the Database Type, followed by a BDRI container. The offsets in the BDRI header are usually relative to the offset to the start of the BDRI header (0x80 in the file)

	== Pre Header ==		== Pre Header ==
Line 455:		Line 453:

	Removing ticket.db from a New-3DS with signature checks disabled will not result in an unbootable system, however all icons except Slot-1 will disappear from Home. Applets can however still be used. Recovery can be accomplished via [[Hardware\|hardmod]] or [[arm9loaderhax]] plus a known good backup of the file (or the whole partition or disk); Gamecard exploits were not tested, and Browserhax did not work.		Removing ticket.db from a New-3DS with signature checks disabled will not result in an unbootable system, however all icons except Slot-1 will disappear from Home. Applets can however still be used. Recovery can be accomplished via [[Hardware\|hardmod]] or [[arm9loaderhax]] plus a known good backup of the file (or the whole partition or disk); Gamecard exploits were not tested, and Browserhax did not work.

	~~== Tools ==~~

	~~[https://github.com/ps3hen/ctr_toolkit/tree/master/extdata_tool extdata_tool] - parsing cleartext .db extdata images~~

Duke srg: ticket.db content format description added

2017-06-22T07:49:48Z

ticket.db content format description added

← Older revision		Revision as of 11:49, 22 June 2017
Line 73:		Line 73:
	\| 0x78		\| 0x78
	\| Reserved		\| Reserved
			\|}

			For ticket.db different pre header is used:

			{\| class="wikitable"
			\|-
			! Start
			! Length
			! Description
			\|-
			\| 0x00
			\| 4
			\| Database Type "Magic" (see below)
			\|-
			\| 0x04
			\| 0x04
			\| Unknown (always 0x00000001 ?)
			\|-
			\| 0x08
			\| 0x04
			\| Unknown
			\|-
			\| 0x0C
			\| 0x04
			\| Unknown (0x30 smaller than previous one)
	\|}		\|}

Line 81:		Line 106:
	! Database Type		! Database Type
	! Magic		! Magic
			\|-
			\| CTR-NAND ticket.db
			\| TICK
	\|-		\|-
	\| CTR-NAND import.db		\| CTR-NAND import.db
Line 206:		Line 234:
	! Length		! Length
	! Description		! Description
			! ticket.db only
	\|-		\|-
	\| 0x0		\| 0x0
	\| 4		\| 4
	\| Unknown		\| Unknown
			\| Unknown (0)
	\|-		\|-
	\| 0x4		\| 0x4
	\| 4		\| 4
	\| Active Flag. If this isn't = 0x1, then this entry slot is unused		\| Active Flag. If this isn't = 0x1, then this entry slot is unused
			\| same
	\|-		\|-
	\| 0x8		\| 0x8
	\| 0x8		\| 0x8
	\| Title ID		\| Title ID
			\| same
	\|-		\|-
	\| 0x10		\| 0x10
	\| 4		\| 4
	\| Title Entry Index		\| Title Entry Index
			\| same
	\|-		\|-
	\| 0x14		\| 0x14
	\| 4		\| 4
	\| Relative Title Info Offset, in blocks (see next field)		\| Relative Title Info Offset, in blocks (see next field)
			\| Unknown
	\|-		\|-
	\| 0x18		\| 0x18
	\| 0x4		\| 0x4
	\| Block Size (Usually 0x80; 0x200 for ticket.db)		\| Block Size (Usually 0x80; 0x200 for ticket.db)
			\| Relative Title Info Offset, in BDRI blocks
	\|-		\|-
	\| 0x1c		\| 0x1c
	\| 4		\| 4
	\| Reserved		\| Reserved
			\| Title Info size, in bytes
	\|-		\|-
	\| 0x20		\| 0x20
	\| 4		\| 4
	\| Unknown, occasionally this value is the title's "Title ID lower"		\| Unknown, occasionally this value is the title's "Title ID lower"
			\| Unknown (0)
	\|-		\|-
	\| 0x24		\| 0x24
	\| 0x4		\| 0x4
	\| Unknown		\| Unknown
			\| same
	\|-		\|-
	\| 0x28		\| 0x28
	\| 0x4		\| 0x4
	\| Unknown		\| Unknown
			\| same
	\|}		\|}

Line 315:		Line 354:
	\| 0x2c		\| 0x2c
	\| Reserved		\| Reserved
			\|}

			For ticket.db title info contains a small header and actual ticket data:
			{\| class="wikitable"
			\|-
			! Start
			! Length
			! Description
			\|-
			\| 0x0
			\| 4
			\| Unknown (always 0x00000001?)
			\|-
			\| 0x4
			\| 4
			\| Ticket data size X (=0x530)
			\|-
			\| 0x8
			\| X
			\| [[Ticket\|Ticket]] data
	\|}		\|}

Duke srg: Title Entry Table header alignment

2017-06-20T18:59:21Z

Title Entry Table header alignment

← Older revision		Revision as of 22:59, 20 June 2017
Line 125:		Line 125:
	\| 0x10		\| 0x10
	\| 8		\| 8
	\| File Size(including pre header), ~~divided by the value at relative offset 0x18~~ (~~usually = 0x80~~)		\| File Size (including pre header), in blocks (see next field)
	\|-		\|-
	\| 0x18		\| 0x18
	\| 4		\| 4
	\| Usually 0x80		\| Block Size (Usually 0x80; 0x200 for ticket.db)
	\|-		\|-
	\| 0x1C		\| 0x1C
Line 181:		Line 181:
	\|-		\|-
	\| 0x30		\| 0x30
	\| ~~0x50~~		\| X - 0x30
	\| ~~Reserved~~		\| Alignment padding for X = BDRI Block Size
	\|-		\|-
	\| ~~0x80~~		\| X
	\| 4		\| 4
	\| MAX Number of Title Entries		\| MAX Number of Title Entries
	\|-		\|-
	\| ~~0x84~~		\| X + 0x04
	\| 4		\| 4
	\| Unknown		\| Unknown
	\|-		\|-
	\| ~~0x88~~		\| X + 0x08
	\| 0x20		\| 0x20
	\| Reserved		\| Reserved
Line 225:		Line 225:
	\| 0x14		\| 0x14
	\| 4		\| 4
	\| Relative Title Info Offset, ~~divided by the value at offset 0x18~~ in ~~this Title Entry~~ (~~usually 0x80~~)		\| Relative Title Info Offset, in blocks (see next field)
	\|-		\|-
	\| 0x18		\| 0x18
	\| 0x4		\| 0x4
	\| Usually 0x80		\| Block Size (Usually 0x80; 0x200 for ticket.db)
	\|-		\|-
	\| 0x1c		\| 0x1c

Ryccardo: Effect of removing ticket.db

2016-04-19T19:00:40Z

Effect of removing ticket.db

← Older revision		Revision as of 23:00, 19 April 2016
Line 394:		Line 394:

	These NAND/SD /dbs images seem to be loaded by the ARM9 while NATIVE_FIRM is booting.		These NAND/SD /dbs images seem to be loaded by the ARM9 while NATIVE_FIRM is booting.

			Removing ticket.db from a New-3DS with signature checks disabled will not result in an unbootable system, however all icons except Slot-1 will disappear from Home. Applets can however still be used. Recovery can be accomplished via [[Hardware\|hardmod]] or [[arm9loaderhax]] plus a known good backup of the file (or the whole partition or disk); Gamecard exploits were not tested, and Browserhax did not work.

	== Tools ==		== Tools ==

	[https://github.com/ps3hen/ctr_toolkit/tree/master/extdata_tool extdata_tool] - parsing cleartext .db extdata images		[https://github.com/ps3hen/ctr_toolkit/tree/master/extdata_tool extdata_tool] - parsing cleartext .db extdata images

Neobrain at 13:42, 23 October 2015

2015-10-23T11:42:02Z

← Older revision		Revision as of 15:42, 23 October 2015
Line 6:		Line 6:
	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 the [[2.0.0-2]] update and the SD dbs files are encrypted. These files are [[extdata]] images. The NAND extdata images are cleartext, however some of the images contain data encrypted with a console-unique keyslot.		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 the [[2.0.0-2]] update and the SD dbs files are encrypted. These files are [[extdata]] images. The NAND extdata images are cleartext, however some of the images contain data encrypted with a console-unique keyslot.

	These files are only created on SD(via [[Application_Manager_Services\|AM]]) if they don't exist when the [[eShop]] application is starting up, during network init etc(prior to showing the "system update required" dialog).		These files are only created on SD (via [[Application_Manager_Services\|AM]]) if they don't exist when the [[eShop]] application is starting up, during network init etc (prior to showing the "system update required" dialog).

	These files are stored under this directory:		These files are stored under this directory:
Line 21:		Line 21:
	\| ticket.db		\| ticket.db
	\| 0x0		\| 0x0
	\| This contains the installed tickets(NAND and SD).		\| This contains the installed tickets (NAND and SD).
	\|-		\|-
	\| No		\| No
Line 33:		Line 33:
	\| title.db		\| title.db
	\| 0x2		\| 0x2
	\| Title database, this contains entries for all installed titles (TWL & CTR) on the 3DS(Each database is responsible for titles installed on its medium).		\| Title database, this contains entries for all installed titles (TWL & CTR) on the 3DS (Each database is responsible for titles installed on its medium).
	\|-		\|-
	\| Yes		\| Yes
Line 39:		Line 39:
	\| import.db		\| import.db
	\| 0x3		\| 0x3
	\| This is an Import Database, it contains entries for titles(or versions of titles) not yet installed, ready for transferring to the title.db. (Automatic Update uses this, so completing the update takes seconds)		\| This is an Import Database, it contains entries for titles (or versions of titles) not yet installed, ready for transferring to the title.db. (Automatic Update uses this, so completing the update takes seconds.)
	\|-		\|-
	\| No		\| No

Plutooo: /* BDRI */

2015-02-28T19:38:23Z

BDRI

← Older revision		Revision as of 22:38, 28 February 2015
Line 117:		Line 117:
	\| 0x4		\| 0x4
	\| 4		\| 4
	\| ~~Magic Number~~ (0x30000)		\| File Format Version (0x30000)
	\|-		\|-
	\| 0x8		\| 0x8