-
Notifications
You must be signed in to change notification settings - Fork 565
Installation and upgrade
- Always copy
boot.firm
to the root of the SD. You don't need to do anything else if you're using boot9strap.
To boot 3.x-4.x NANDs, you need to load FIRM from the SD card.
Download this file and rename it to firmware.bin
, then this other file and rename it to cetk
, then copy both of them to the luma
folder.
As of Luma3DS 7.1, boot9strap is required for usage and all previous entrypoints are no longer supported. Refer to this for information on how to update from arm9loaderhax, or start from here if you do not yet have arm9loaderhax or boot9strap
While it is not recommended to use a boot manager (such as BootCtr9) to load Luma3DS as it tends to cause strange issues due to the nonstandard environments these managers setup, Luma3DS can be used with one. As of the release of boot9strap and Luma3DS 8.0, the payload's path should be passed by the chainloader, thus custom path support was removed from Luma. If you are not able boot into NDS or GBA VC games while using an external boot manager, this is not an issue with Luma, but rather, the boot manager itself. In this scenario, contact said boot manager's developer and tell them that it does not pass the payload paths properly.
Content is available under Creative Commons Attribution-ShareAlike unless otherwise noted.
Take a look at the FAQ and troubleshooting page for the most common issues you might run into. For other issues or general support with using Luma3DS, ask for help at Nintendo Homebrew on Discord. To report issues, create a Github issue. Check to see if it was reported already before creating a new one.