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


From Hacks Guide Wiki
< 3DS:Luma3DS
Revision as of 18:48, 10 March 2024 by StarlitSkies (talk | contribs) (s/Homebrew autoboot/Hbmenu autoboot to match current wording)

(diff) ← Older revision | Approved revision (diff) | Latest revision (diff) | Newer revision → (diff)

The Luma3DS configuration menu is a menu that can be accessed by holding Select while turning on your 3DS. In the menu, you can:

  • See what version of Luma3DS is currently installed
  • Modify some of Luma3DS's 'optional' settings (settings that will, in general, not affect the overall functionality of your 3DS)
  • See where Luma3DS is booting from

By default, our custom firmware installation guide uses the default configuration that is generated when Luma3DS is first run. This page will contain explanations for the various options contained in Luma3DS configuration so that you can make an informed decision on what options (if any) to change.

Luma3DS configuration will often be reset to default settings if:

  • You change to a different version of Luma3DS
  • You are switching between Luma3DS forks

Luma3DS also keeps separate configuration files for the SD card and CTRNAND (internal memory). The files' locations are SD:/luma/config.ini and CTRNAND:/rw/luma/config.ini, respectively.

Navigating Luma3DS configuration

OOjs UI icon information-progressive.svg If your Select, , , or A buttons are broken, you will be unable to use the Luma3DS configuration. As an alternative, you can manually modify all options that are in the Luma3DS configuration by modifying the config.ini file in the luma folder (as of Luma3DS v12.0).

You can access Luma3DS configuration by holding Select while powering on your device.
When in the Luma3DS configuration menu, you can use the and buttons to highlight different options. Press A to enable, disable, or cycle through the options. The currently highlighted option will be coloured differently from the rest of the configuration menu, and an option that is currently enabled will be indicated with (x). For example, (x) Show NAND or user string in System Settings indicates that the "Show NAND or user string in System Settings" option is enabled.
Once you are done configuring Luma3DS, either select the Save and exit option or press the Start button to save your configuration. If the PIN setting is enabled, you will be told to set it; otherwise, the 3DS will immediately reboot.

Luma3DS configuration options


Screen brightness

Changes the brightness of the Luma3DS configuration screen. Takes effect instantly.


Determines whether Luma3DS will attempt to display a splash screen (a custom boot image) while booting your 3DS. This option will not do anything unless you have splash images in the luma folder, and will not affect whether a PIN splash shows up. For more information, see 3DS:Splash screens.

PIN lock

Determines whether Luma3DS will require a PIN to be entered when powering on your device. You will be prompted to set the PIN after saving the configuration. For more information, see 3DS:Luma3DS/PIN lock.


OOjs UI icon information-progressive.svg This option can only be used on a new 3DS/2DS.

When enabled, allows the New 3DS's enhanced clock speed and L2 cache to be used in all titles, not just New 3DS-exclusives. This may improve performance for some games, but it may also reveal hidden bugs in games when the Clock+L2 setting is enabled - this can result in anything up to a crash. This option is the same as the one found in the Rosalina menu.

Hbmenu autoboot

When enabled, automatically boots to the selected homebrew launcher instead of the HOME Menu.
If 3DS is chosen, this will always be the normal Homebrew Launcher.
if DSi is chosen, by default this will attempt to boot to the nds-hb-menu - if this is not installed, it will boot to an exception instead.

The title IDs used for each of these options can be configured in the config.ini file.

Enable loading external FIRMs and modules

When enabled, Luma3DS will load customized FIRMs and system modules (basically, for modifying non-game elements on the 3DS). This option will not do anything unless you have the necessary files in luma or /luma/sysmodules.

You will most likely only use this option for specific applications like TWPatch (for widescreen DS games) and rverse (a custom Miiverse server). For more information, consult their respective installation guides.

Enable game patching

When enabled, Luma3DS will load modded game files. This option will not do anything unless you have any files to load, which should be placed in /luma/titles/(title ID of game).
You will often enable this option if you are planning to use game mods via LayeredFS, such as translation patches or ROM hacks.
You will also need this option if you need to manually specify the locale for games that fail to work despite Luma3DS's region-free patch. For more information, see 3DS:Setting game locales.

Redirect app. syscore threads to core2

OOjs UI icon information-progressive.svg This option can only be used on a new 3DS/2DS.

When enabled, Luma3DS will move some application threads to core2, which usually goes unused despite being intended for applications. This will boost performance on resource-intensive games (like Pokemon US/UM) by around 10%, but may also break some games and applications.

Show NAND or user string in System Settings

When enabled, Luma3DS will show its own (or a user-specified) version string in System Settings. For example, the default version string of an unmodded 3DS on 11.16.0-49U would be Ver. 11.16.0-49U. With this option enabled, the version string would instead show Sys. 11.16.0-49U. This serves as a decent custom firmware check, but it is not comprehensive since the option can be disabled at will.

A custom version string of up to 19 characters can also be manually specified by creating a file with the custom string called customversion_sys.txt and putting it inside the luma folder.

Show GBA boot screen in patched AGB_FIRM

When enabled, Luma3DS will show the GBA boot screen when loading a GBA game through the built-in GBA firmware of the 3DS (such as through virtual console).

Force routing audio output through headphones

Forces all audio output except for the camera shutter to go to the headphones. Because Luma3DS only directly affects NATIVE_FIRM, this will not work in DS games, GBA games, payloads such as GodMode9, or Safe Mode.

Due to software limitations, this will stop working temporarily if you unplug and then replug headphones. Close and reopen the screen when this happens to fix it.

EmuNAND/RedNAND only

OOjs UI icon information-progressive.svg These options will only appear if your currently inserted SD card has an EmuNAND/RedNAND set up. These are almost entirely unneeded by now, however, and should instead be moved into the SysNAND unless you are using them to deal with Chinese/Korean fonts.

Default EmuNAND

It is possible to have multiple EmuNANDs on one SD card. This option changes which one to boot into by default. If you only have one EmuNAND, this option will not do anything.
You can also manually specify which EmuNAND to boot into by holding a certain direction on the D-Pad while powering on: for 1, for 2, for 3, for 4.

Autoboot EmuNAND

Determines whether the emuNAND will automatically boot when you turn on your 3DS without holding any buttons. If this option is disabled, you will boot into the sysNAND by default. Holding L when powering on will invert this logic, meaning the 3DS will boot into sysNAND even when this option is enabled (or into emuNAND if it's disabled).

Configuration options in config.ini

As of Luma3DS v11.0, certain options have been moved and can only be edited in the config.ini file, located in both SD:/luma/config.ini and [1]:/rw/luma/config.ini. This section documents those options.

config_version_major, config_version_minor

OOjs UI icon information-warning.svg There is no reason to touch this option, and doing so may reset your Luma3DS configuration.

Luma3DS uses these lines to determine what revision of config.ini is being used to prevent inconsistencies between Luma3DS updates. Do not touch these options.


Determines for how many milliseconds the splash screen should be displayed, up to 2,147,483,647 milliseconds. For more information, see 3DS:Splash screens.


Determines the DSi title to boot into when autoboot_3ds_homebrew is set to 2. The selected title must be installed on the NAND, or it will instead crash on boot - the default app used is nds-hb-menu.

Rosalina menu options

The following options can be altered in some way via the Rosalina menu.


The title ID that is input here will launch the Homebrew Launcher instead of whatever application is actually run. In most cases, this will be set to the Homebrew Launcher Wrapper that is installed in the guide (000400000d921e00).


Determines what keys you need to press to open the Rosalina menu. By default, this is set to L++SELECT.
For example, if one of the default keys is broken, you can set it to X+Y to change the menu combination to X+Y.


Determines your timezone to set the time correctly. The value is the number of minutes your timezone is from UTC.
For example, Eastern Standard Time (EST) is UTC-5, so the offset would be 60 * -5 = -300.

Screen filter options

All of the following options can be configured for each screen, and thus have two variables.


Determines the Correlated Color Temperature (cct). Can be set to any integer between 1000 and 25100.


Adjusts the gamma of the screen. Can be set to any integer between 0 and 1411. Increasing this above 1 will make colors look more saturated.


Adjusts the contrast of the screen. Can be set to any integer between 0 and 255.


Adjusts the brightness of the screen. Can be set to any number between -1 and 1.


If set to 1, inverts the colors of the screen.

Options you shouldn't touch

You shouldn't touch these options unless you know what you're doing.


OOjs UI icon information-warning.svg This option is only of interest for developers. Changing it without knowing what you are doing may result in frequent crashes.

When set to anything but 0, uses an alternate memory layout when autoboot_3ds_homebrew is set to 1.


OOjs UI icon information-warning.svg This option will break most retail features while enabled - this includes online play, eShop, amiibo, and all retail games.

When set to 1, this option changes a flag in the 3DS firmware so that it thinks it is a development unit, allowing you to run development applications.


OOjs UI icon information-warning.svg This option usually does not stop errors from happening - it only makes them harder to troubleshoot.

When set to 1, this option disables the An exception occurred message that occurs when an application crashes, normally replacing it with a black screen or a generic error message.


OOjs UI icon information-progressive.svg Luma3DS should not be active in SAFE_FIRM since SAFE_FIRM is meant as a 'rescue mode' - it's relatively unlikely anything bad will happen, but don't enable this option without a specific good reason.

When set to 1, this option does two things:

  • Allows Rosalina to function when using Safe Mode (for example, if you need to take screenshots of Safe Mode or perform whatever other functions Rosalina allows)
  • Suppresses the 0xF96183FE QTM error, which notably allows the New 2DS XL to work on firmwares below 11.3.0

Troubleshooting with Luma3DS configuration

The Luma3DS configuration menu contains two pieces of information that can be used for troubleshooting: the currently installed Luma3DS version and the location from which Luma3DS is booting.
If you are starting on a new SD card or upgrading from an old (2017 or older) custom firmware setup, you can follow the instructions here to find out the correct course of action.
As of Luma3DS v9.0, the location from which Luma3DS is booting will be displayed in yellow on the bottom screen. The following lines are known to be possible:

  • Booted from SD via B9S
    • Indicates that Luma3DS is being booted from the boot.firm file on the root of your SD card (or wherever else on the SD you may have it configured if you are using fastboot3DS).
  • Booted from CTRNAND via B9S
    • Indicates that Luma3DS is being booted from the boot.firm file on the root of SYSNAND CTRNAND (or wherever else on SYSNAND CTRNAND you may have it configured if you are using fastboot3DS). If an SD card is inserted and you still see this message, one of three things is possible: 1. you are missing boot.firm from the root of your SD card, 2. your SD card isn't being read, or 3. you have configured fastboot3DS to try to boot from Luma on the CTRNAND before trying the SD.
  • Booted from SD via B9S (ntrboot)
    • Indicates that Luma3DS is being booted from the boot.firm file on the root of your SD card, but that you are running B9S via ntrboot. If you're trying to install CFW, you should instead use SafeB9SInstaller as your boot.firm file.
  • Booted from SD via FIRM0 or FIRM1
    • Indicates that Luma3DS has been installed to your FIRM partitions (where boot9strap or fastboot3DS would normally go). This is known to break some custom firmware functions, so unless this you intended to do this, you should follow these instructions to install boot9strap to your FIRM partitions.
  • Booted from CTRNAND via FIRM0 or FIRM1
    • Indicates that Luma3DS has been installed to your FIRM partitions and that the SD is not being read. You will need a usable SD card if you wish to install boot9strap to your FIRM partitions as above, so try to fix that first by reformatting - if this does not work, your SD may be corrupted and should be tested for errors.