Tutorial
Updated
How to switch your MenuHax CFW Setup to Luma3DS
I've noticed a lot of this questions related to switching CFWs popping up lately on the forum, so here's a quick tutorial on how to switch to Luma3DS from other outdated CFW solutions, such as rxTools, AuReiNAND, or a handful of other outdated CFW options.
This guide is kind of a WIP, but it should be simple enough to get most people running Luma3DS at the very least. Feedback on how I can make steps clearer is appreciated, but please be civil, of course. (:
Why switch to Luma3DS? Easy, you lose nothing, it's being well maintained, and it's a lot faster and more consistent than many of the older CFW options.
Need all those Tools from rxTools? Switch to using Decrypt9WIP and EmuNAND9 to perform the various functions that it's menu had and more. These tools are being well maintained, while rxTools is not*. This means they are safer tools for you, the end user.
*dukesrg made an effort to try to fix some bugs in them with his fork "Yet another rxtools" but this doesn't resolve any of the CFW related things, and that fork is still not recommended for use
MenuHax Users:
For MenuHax users running CTRBootManager, here is the entry you must add to the top of your boot.cfg, either replacing your old CFW's entry, or adding it if you for some reason like being able to boot multiple CFWs.
For MenuHax users running BootCTR, replace your existing [DEFAULT] entry in boot_config.ini with the following. BootCTR's default values for offset and delay handle the Luma3DS dat properly by default and do not need to be specified.
Writer's Notes:
This guide is what it is. It's a supplement for people that used outdated guides in this forum to get them on the right track to running something modern and fast, rather than bloated and slow, but not requiring them to go through Plailect's Guide necessarily, even if they should. I didn't like the way existing guide's of this nature were handled or laid out, so I did one myself.
If I've made any mistake, please feel free to tell me about it in this thread and I'll correct it.
This guide is kind of a WIP, but it should be simple enough to get most people running Luma3DS at the very least. Feedback on how I can make steps clearer is appreciated, but please be civil, of course. (:
Why switch to Luma3DS? Easy, you lose nothing, it's being well maintained, and it's a lot faster and more consistent than many of the older CFW options.
Need all those Tools from rxTools? Switch to using Decrypt9WIP and EmuNAND9 to perform the various functions that it's menu had and more. These tools are being well maintained, while rxTools is not*. This means they are safer tools for you, the end user.
*dukesrg made an effort to try to fix some bugs in them with his fork "Yet another rxtools" but this doesn't resolve any of the CFW related things, and that fork is still not recommended for use
MenuHax Users:
- Download the latest Luma3DS (non-dev) build from the github here.
- Place your 3DS's SD Card in your computer.
- Copy over the "3DS" folder, the "luma" folder, and "Luma3DS.dat" from the archive to your SD card.
- Delete your other CFW's files.
- Add an entry in your Boot Manager Configuration to load the Luma3DS.dat with offset 0x12000. See "Additional Information" below for the exact text to copy if you are unsure. If you have no boot manager and do not wish to set one up, but wish to load Luma3DS instantly once MenuHax runs, you may use the "boot.3dsx" inside the "menuhax" folder of the Luma3DS archive.
- Insert SD Card back into your 3DS.
- Start up Luma3DS CFW and turn on:
"Show current NAND in System Settings." - You may also set "New 3DS CPU" to "Clock+L2" if you have a New 3DS and would like better performance in titles that do not support the New 3DS features normally.
- You may also enable "Show GBA boot screen in patched AGB_FIRM" should you have the desire to see the old GBA Logo flash when running GBA games.
- When done press start to boot CFW EmuNAND.
- Future boots of Luma3DS will no longer show the Config, should you need to get into it to change things, you may do so by holding Select while you start it up, should you want to boot CFW SysNAND, you may do so by holding L while starting Luma3DS. For additional information on how Luma3DS works and it's options, read the Luma3DS Wiki.
- Consider switching to Arm9LoaderHax by following Plailect's Guide because it is an objectively better entrypoint, especially for CFW users. If you decide to do this, make sure your boot.3dsx is the Homebrew Launcher.
For MenuHax users running CTRBootManager, here is the entry you must add to the top of your boot.cfg, either replacing your old CFW's entry, or adding it if you for some reason like being able to boot multiple CFWs.
Code:
{
title = "Luma3DS";
path = "/Luma3DS.dat";
offset = "0x12000";
},For MenuHax users running BootCTR, replace your existing [DEFAULT] entry in boot_config.ini with the following. BootCTR's default values for offset and delay handle the Luma3DS dat properly by default and do not need to be specified.
Code:
[DEFAULT]
path = /Luma3DS.datWriter's Notes:
This guide is what it is. It's a supplement for people that used outdated guides in this forum to get them on the right track to running something modern and fast, rather than bloated and slow, but not requiring them to go through Plailect's Guide necessarily, even if they should. I didn't like the way existing guide's of this nature were handled or laid out, so I did one myself.
If I've made any mistake, please feel free to tell me about it in this thread and I'll correct it.
Last edited by CheatFreak47,
