Source review: October 11, 2026. Follow the linked DSi Guide and DS-Homebrew documentation for your exact setup. Their supported installers and procedures can change.
Identify the system and preserve its state
Nintendo DSi and DSi XL have their own homebrew workflow. They are separate from DS Lite and from running DS software on a Nintendo 3DS. Read the case label and system-version display, record the region and installed applications, and privately retain the serial number. Test both screens, touch calibration, buttons, cameras, sound, charging and an ordinary game card before changing software. Homebrew cannot repair a broken charging connector or a torn display cable.
Check an already modified console
A used DSi may already contain Unlaunch. The DSi Guide checks this by holding A and B immediately after powering on and looking for the Unlaunch menu. If it appears, record the boot configuration instead of blindly starting a first-install procedure. An SD card with TWiLight Menu++ files alone does not establish whether Unlaunch is installed on the internal storage. Conversely, an installed boot modification can remain present when its SD card is missing.
Understand the layers
An entry point starts homebrew from an existing application. Memory Pit uses Nintendo DSi Camera and the DSi Guide documents it across system firmware versions. Temporary entry does not automatically give every program unrestricted hardware access. Unlaunch is a separate bootcode modification stored on the console. TWiLight Menu++ is a menu and application-launching environment, while nds-bootstrap provides the loading path for supported DS(i) software. These names describe different parts of the setup, so a title screen from one program is not proof that the whole chain works.
Prepare before choosing an installer
Copy the entire SD card to another storage device, including photographs and existing homebrew files. Use the current SD preparation procedure and test the card. Then follow the DSi Guide's branch for your present state and installed applications. Its starting page currently prepares dumpTool as a correctly named boot.nds on the SD root; an accidental nested folder or extra filename extension can prevent the intended program from loading. Retain the source release and the steps used so later troubleshooting does not depend on memory.
Set a practical goal
Decide whether you want occasional homebrew, direct boot to a menu, save preservation or development. Make and archive a NAND backup before a permanent modification. Do not update, uninstall or restore internal storage merely because a new menu has a different appearance. New DSi Shop purchases ended in 2017, so a modern setup guide should not depend on buying a particular DSiWare title today. Preserve content already on your own console and use current project-supported entry points. When something fails, record the exact application and screen rather than describing every issue as a failed jailbreak.
Sources and project documentation
- Nintendo: DSi and DSi XL operations manuals
- DSi Guide: starting checks and Memory Pit
- Nintendo: DSi Shop purchase closure announcement
Next, read SD card preparation and backup planning.