Toggle menu
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

3DS:Rebuild Title Database: Difference between revisions

From Hacks Guide Wiki
(link to 3DS:Dump system files for dumping boot9.bin and movable.sed, instead of including the steps here (makes it easier if someone already has these files))
 
(7 intermediate revisions by 2 users not shown)
Line 1: Line 1:
This article will guide you in rebuilding the <code>title.db</code> file in your SD card.  
This page is a guide to rebuilding the <code>title.db</code> file in your SD card.  


<code>title.db</code> is a file on both the 3DS' SD card and its CTRNAND which contains a list of all installed 3DS titles for its respective place (e.g. The SD card's <code>title.db</code> only has entries for titles installed to the SD card). For more information, check out [[3dbrew:Title Database|3dbrew]].
<code>title.db</code> is the name for two files - one on the 3DS' SD card, and one on its CTRNAND - which contain a list of all installed 3DS titles for its respective part of the filesystem (e.g. your SD card's <code>title.db</code> only has entries for titles installed to your SD card). For more information, check out [[3dbrew:Title Database|3dbrew]].


=== What you need ===
=== What you need ===


* The latest release of [https://github.com/wwylele/save3ds/releases save3ds] for your operating system
* The latest release of {{GitHub|wwylele/save3ds/releases/latest|save3ds}} for your operating system
* A version of [https://www.python.org/downloads/ Python 3]
* A version of [https://www.python.org/downloads/ Python 3.8 or later]
* A 3DS console with custom firmware
* A 3DS console with custom firmware
* [https://github.com/ihaveamac/3DS-rom-tools/raw/master/seeddb/seeddb.bin seeddb.bin]
* {{GitHub|ihaveamac/3DS-rom-tools/raw/master/seeddb/seeddb.bin|seeddb.bin}}
* boot9.bin (same for all consoles) and movable.sed (specific to yours only) - dump with [[3DS:Dump system files]]


=== Section I - Preparing the files ===
=== Section I - Preparing the files ===


# Launch GodMode9 by holding {{B|START}} on boot
# Navigate into <code>[M:] MEMORY VIRTUAL</code>
# Press {{B|A}} on <code>boot9.bin</code> then select '''Copy to 0:/gm9/out'''
# Press {{B|A}} to continue
# Press {{B|B}} once to return to the main menu
# Navigate into <code>[1:] SYSNAND CTRNAND</code> -> <code>private</code>
# Press {{B|A}} on <code>movable.sed</code>, then select '''Copy to 0:/gm9/out'''
# Turn the 3DS off
# Turn the 3DS off
# Insert the SD card into your computer
# Insert your SD card into your computer
# Go to [https://github.com/ihaveamac/rebuild-title-database the GitHub repo for Rebuild Title Database]
# Go to the {{GitHub|ihaveamac/rebuild-title-database|Rebuild Title Database}} repo's page
# Click the <big><span style="background:#008000">Code</span></big> button, then click '''Download ZIP'''
# Click the <big><span style="background:#008000">Code</span></big> button, then click '''Download ZIP'''
# Extract the contents of the downloaded <code>.zip</code> into a folder
# Extract the contents of the downloaded <code>.zip</code> into a folder
#* This folder will be referred to as the "rebuild folder" from now on
#* This folder will be referred to as the "rebuild folder" from now on
# Go to <code>gm9</code> -> <code>out</code> on your SD card
# Copy <code>movable.sed</code> and <code>boot9.bin</code> to the rebuild folder
# Copy <code>movable.sed</code> and <code>boot9.bin</code> into the rebuild folder
#* If you had just dumped them from your console, both are most likely in <code>sd:/gm9/out</code>
# Create a folder called <code>3ds</code> in your user directory
# Copy <code>seeddb.bin</code> into the rebuild folder
#* On Windows, the user directory is <code>C:/Users/[your username]/</code>
# Copy the <code>save3ds_fuse</code> binary from the save3ds <code>.zip</code> file into the rebuild folder
#* On macOS, the user directory is <code>/Users/[your username]</code>
#* On Linux, the user directory is <code>/home/[your username]</code> (often shortened to <code>~</code>)
# Copy <code>seeddb.bin</code> into the new <code>3ds</code> folder
# Copy <code>save3ds_fuse.exe</code> from the save3ds <code>.zip</code> file into the rebuild folder


=== Section II - Rebuilding the Database ===
=== Section II - Rebuilding the database ===
{{info|If you are not on Windows, replace <code>py -3</code> with <code>python3</code> in all commands.}}
{{info|If you are not on Windows, replace <code>py -3</code> with <code>python3</code> in all commands.}}
{{warning|The commands in this section are case-sensitive. Enter them exactly as written, or there may be unintended consequences.}}


# Navigate to the rebuild folder in file explorer
# Navigate to the rebuild folder in file explorer
# Hold SHIFT and right-click anywhere in the folder's empty space, then click the option that opens a terminal, PowerShell, or Command Prompt
# Hold SHIFT and right-click anywhere in the folder's empty space, then click the option that opens a terminal, PowerShell, or Command Prompt
# In this new window, enter the following commands one at a time:  
# In this new window, enter the following commands one at a time:
## <code>py -3 -V</code>
##* If this does not print the Python version, it is either not installed correctly, or the wrong command was used. Please read the note above.
## <code>py -3 -mpip install --user -r requirements.txt</code>
## <code>py -3 -mpip install --user -r requirements.txt</code>
## <code>py -3 fix-titledb.py -b boot9.bin -m movable.sed -s X:</code>
## <code>py -3 fix-titledb.py -b boot9.bin -m movable.sed -s X:</code>
## <code>py -3 rebuild-title-database.py -b boot9.bin -m movable.sed -s X: -o out</code>
##* If you are on Windows, replace <code>X:</code> with your SD card's drive letter. If you are not on Windows, replace <code>X:</code> with your SD card's mount point.
##* replace <code>X:</code> with your SD card's drive letter
## <code>py -3 rebuild-title-database.py -b boot9.bin -m movable.sed -S seeddb.bin -s X: -o out</code>
## <code>save3ds_fuse --db sdtitle out --import --boot9 boot9.bin --movable movable.sed --sd X:</code>
## <code>./save3ds_fuse.exe --db sdtitle out --import --boot9 boot9.bin --movable movable.sed --sd X:</code>
##* replace <code>X:</code> with your SD card's drive letter
##* If you are not on Windows, remove <code>.exe</code> from this command
# If you didn't get any errors, your apps should reappear on the HOME Menu immediately  
# If you didn't get any errors, your apps should reappear on the HOME Menu immediately  
#* If they only appear in '''System Settings -> Data Management''' and they have an X through their icons there, run [[3DS:Faketik|faketik]].
#* If they only appear in '''System Settings''' -> '''Data Management''', follow '''one''' of these sets of steps based on how they appear.
#* If they do not appear anywhere in the system, you should [[Checking SD card integrity|check your SD card for errors]] - the apps are likely gone.
#** Appear normally: Check the contents of <code>sd:/Nintendo 3DS/<id0>/<id1>/title/00040000</code>; there should only be more folders inside that folder.
#*** If there is a file inside this folder, your apps are at least partially corrupted - backup your SD card to your PC, [[Formatting an SD card|reformat it]], and then try to move the backed-up files back to the SD. If this fails or the apps do not reappear afterward, [[Checking SD card integrity|check your SD card for hardware damage]].
#** Appear with a grey block count indicator and an X through their icons: Run [[3DS:Faketik|faketik]].
#** Appear with white/corrupted icons, 0 block count, and/or corrupted name: Whatever destroyed your <code>title.db</code> has also permanently corrupted your apps. Backup your SD card to your PC,[[Formatting an SD Card|reformat it]], and then [[Checking SD card integrity|check it for hardware damage]].
#* If they do not appear anywhere in the system, you may want to [[Checking SD card integrity|check your SD card for hardware damage]], as the apps are likely gone.


=== Troubleshooting ===
=== Troubleshooting ===


* boot9.bin is missing in <code>[M:] MEMORY VIRTUAL</code>
* <code>boot9.bin</code> is missing from <code>[M:] MEMORY VIRTUAL</code>
** You are not using boot9strap. You should [[3DS:Luma3DS to boot9strap|switch to boot9strap]] or consult the documentation of the bootloader you use, such as [[3DS:fastboot3DS|fastboot3DS]].
** Follow the steps to [[3DS:Dump system files|dump your system files]] for more in-depth instructions, including those for bootloaders other than [[3DS:boot9strap|boot9strap]].
* The first command in Section II gave the error <code>ERROR: Could not open requirements file: [Errno 2] No such file or directory: 'requirements.txt'</code>
* The first command in Section II gave the error <code>ERROR: Could not open requirements file: [Errno 2] No such file or directory: 'requirements.txt'</code>
** Make sure you are in the rebuild folder and that you extracted the contents of <code>rebuild-title-database-master.zip</code> into it.  
** Make sure you are in the rebuild folder and that you extracted the contents of <code>rebuild-title-database-master.zip</code> into it.  
*** Once this is fixed, delete the out folder and try the command again.
*** Once this is fixed, delete the <code>out</code> folder and try the command again.
* The second or third command in Section II failed
* The third or fourth command in Section II failed
** Make sure you have <code>boot9.bin</code> and <code>movable.sed</code> in the rebuild folder.
** Make sure you have <code>boot9.bin</code> and <code>movable.sed</code> in the rebuild folder.
** Make sure the SD card is inserted and you can view and edit its contents.
** Make sure your SD card is inserted and you can view and edit its contents.
* The fifth command in Section II failed
** If you are on macOS, try installing {{GitHub|osxfuse/osxfuse/releases/latest|osxfuse}}, either via its GitHub page or via [https://brew.sh Homebrew].


[[Category:Nintendo 3DS guides]]
[[Category:Nintendo 3DS guides]]

Latest revision as of 04:20, 16 November 2024

This page is a guide to rebuilding the title.db file in your SD card.

title.db is the name for two files - one on the 3DS' SD card, and one on its CTRNAND - which contain a list of all installed 3DS titles for its respective part of the filesystem (e.g. your SD card's title.db only has entries for titles installed to your SD card). For more information, check out 3dbrew.

What you need

Section I - Preparing the files

  1. Turn the 3DS off
  2. Insert your SD card into your computer
  3. Go to the Rebuild Title Database repo's page
  4. Click the Code button, then click Download ZIP
  5. Extract the contents of the downloaded .zip into a folder
    • This folder will be referred to as the "rebuild folder" from now on
  6. Copy movable.sed and boot9.bin to the rebuild folder
    • If you had just dumped them from your console, both are most likely in sd:/gm9/out
  7. Copy seeddb.bin into the rebuild folder
  8. Copy the save3ds_fuse binary from the save3ds .zip file into the rebuild folder

Section II - Rebuilding the database

OOjs UI icon information-progressive.svg If you are not on Windows, replace py -3 with python3 in all commands.
OOjs UI icon information-warning.svg The commands in this section are case-sensitive. Enter them exactly as written, or there may be unintended consequences.
  1. Navigate to the rebuild folder in file explorer
  2. Hold SHIFT and right-click anywhere in the folder's empty space, then click the option that opens a terminal, PowerShell, or Command Prompt
  3. In this new window, enter the following commands one at a time:
    1. py -3 -V
      • If this does not print the Python version, it is either not installed correctly, or the wrong command was used. Please read the note above.
    2. py -3 -mpip install --user -r requirements.txt
    3. py -3 fix-titledb.py -b boot9.bin -m movable.sed -s X:
      • If you are on Windows, replace X: with your SD card's drive letter. If you are not on Windows, replace X: with your SD card's mount point.
    4. py -3 rebuild-title-database.py -b boot9.bin -m movable.sed -S seeddb.bin -s X: -o out
    5. ./save3ds_fuse.exe --db sdtitle out --import --boot9 boot9.bin --movable movable.sed --sd X:
      • If you are not on Windows, remove .exe from this command
  4. If you didn't get any errors, your apps should reappear on the HOME Menu immediately
    • If they only appear in System Settings -> Data Management, follow one of these sets of steps based on how they appear.
      • Appear normally: Check the contents of sd:/Nintendo 3DS/<id0>/<id1>/title/00040000; there should only be more folders inside that folder.
        • If there is a file inside this folder, your apps are at least partially corrupted - backup your SD card to your PC, reformat it, and then try to move the backed-up files back to the SD. If this fails or the apps do not reappear afterward, check your SD card for hardware damage.
      • Appear with a grey block count indicator and an X through their icons: Run faketik.
      • Appear with white/corrupted icons, 0 block count, and/or corrupted name: Whatever destroyed your title.db has also permanently corrupted your apps. Backup your SD card to your PC,reformat it, and then check it for hardware damage.
    • If they do not appear anywhere in the system, you may want to check your SD card for hardware damage, as the apps are likely gone.

Troubleshooting

  • boot9.bin is missing from [M:] MEMORY VIRTUAL
  • The first command in Section II gave the error ERROR: Could not open requirements file: [Errno 2] No such file or directory: 'requirements.txt'
    • Make sure you are in the rebuild folder and that you extracted the contents of rebuild-title-database-master.zip into it.
      • Once this is fixed, delete the out folder and try the command again.
  • The third or fourth command in Section II failed
    • Make sure you have boot9.bin and movable.sed in the rebuild folder.
    • Make sure your SD card is inserted and you can view and edit its contents.
  • The fifth command in Section II failed
    • If you are on macOS, try installing osxfuse, either via its GitHub page or via Homebrew.