Nintendo 2DS & 3DS · CFW & core setup

Choose the model-specific setup guide and find Luma3DS, GodMode9 and the core tools for an existing CFW installation.

Start with your model and CFW

The maintained guide covers original 3DS / 3DS XL / 2DS and New 3DS / New 3DS XL / New 2DS XL. Select the exact model, region and installed firmware on the guide. An app download does not install CFW on a stock console.

  1. Check the existing setupPower off, hold Select and power on. Compare the result with Checking for CFW before updating or replacing boot files.
  2. Complete the matching installation routeFor a stock system, use Get Started and follow its current model and firmware selector to boot9strap and Luma3DS.
  3. Keep the system backupsFinish Finalizing Setup and keep NAND and essential-file backups on another device before installing more applications.

CFW & core setup

6 resources shown

Keep your core setup

The six established resources and their pinned releases are preserved.

Checkpoint artwork

Checkpoint

5.3.0Save managerBackups3DS CIA

Back up and restore supported game saves and extdata. Use the 3DS CIA on a prepared 2DS / 3DS, and keep an original backup before restoring or editing saves.

ftpd · Nintendo 3DS build artwork

ftpd · Nintendo 3DS build

3.2.1FTPSD files2DS / 3DS

Access SD-card files from an FTP client on your local network. This CIA is the 2DS / 3DS build, separate from the Nintendo DS binary.

Choose CIA, 3DSX or FIRM

  1. Prepare storageUse a genuine SD / microSD with FAT32 and an MBR partition table. The maintained guide recommends 2–128 GB; larger cards can introduce GBA graphics and custom-theme issues. Keep the entire existing Nintendo 3DS folder and your saves backed up.
  2. CIA apps: install to HOME MenuCopy a CIA to a convenient SD folder such as /cias/, then use FBI on your prepared CFW system to install it. Read the app requirements first. Universal-Updater is another route for supported apps.
  3. 3DSX apps: launch through Homebrew LauncherPut the executable in /3ds/ or its documented app subfolder. Copy bundled data directories separately to their specified SD paths. A lone 3DSX is not a replacement for required game data.
  4. FIRM files: boot payloadsFor tools that document it, put the FIRM under /luma/payloads/ and use the Luma chainloader at boot. Luma boot.firm itself belongs at the SD root; do not replace it with an app FIRM.
  5. DS mode: use the 3DS packageFollow TWiLight Menu++’s 3DS installation page. The DS flashcart and DSi packages use different instructions.
  6. Keep versions and dependencies togetherEach new download has an expandable file record with its original URL, exact version, byte count and SHA-256. Preserve supplied folders and follow the linked readme for BIOS, ROM or game-data requirements.