I won't tell you what you should do, that's your choiceI'm planning to do the following to my 4.1.0U o3DS (n3DS is at A9LH with 11.0.0U SysNAND and 11.0.0E RedNAND for European CIAs):
- Fix modified AGB_FIRM and TWL_FIRM
- Upgrade to 9.2.0U and create a NAND dump
- Follow Plialect's guide, except after the 2.1.0 OTP part, going back to 9.2.0U
- Install v1 of A9LH
- Install Luma3DS arm9loaderhax on my regular SDCard with 11.0.0U RedNAND
- Use GW's arm9loaderhax.bin on a separate SDCard with 11.0.0U EmuNAND (yes I already have one with Pasta, no I don't mind swapping)
That *should* give me one SD card with Luma, where GBA and DSiWare works (when installed to SysNAND) and one SD card with GW, where everything works what is working now (4.1.0U-MSET+11.0.0U EmuNAND ==> 9.2.0U-A9LH+11.0.0U EmuNAND) with the benefit being on the latest version of GW, not having to worry about the MSET or any other entrypoint anymore), and being able to update the RedNAND (to e.g. 11.1.0U) while leaving the EmuNAND on 11.0.0U, waiting for GW support.
Anything I should do differently?
But what you could do is save an SD card maybe, to avoid card swapping and transferring saves. I see two ways to do this:
- Have Luma boot to sysNAND by default (sysNAND is updatable without losing a9lh if you use Luma) and Gateway boot on emuNAND
- Or if you don't like doing stuff on your sysNAND, have two emuNANDs. The first one is for Gateway (since you can't configure that, GW always boots there) and the second one is for Luma (look for the "Use second EmuNAND as default" option)