Hacking Luma3ds only boots into SysNAND

[CesiumBullets]

I'm a super noob following Plailect's guide to installing A9LH (https://github.com/Plailect/Guide/wiki/Part-3-(RedNAND)), and I'm stuck at steps 22-25 (booting Red/EmuNAND).

So, when I turn on the 3ds, it auto-boots into menuhax as usual. I scroll down to Luma3DS and open it. If I hold select, I'm brought into the configuration menu. The only option I have selected is "Show current NAND in System Settings," as the guide has told me to select.

Once Luma3DS boots, I hold the right trigger button so menuhax doesn't reload. It takes me to the home menu, but once I enter system settings, instead of seeing 'Emu' next to the firmware number, I see 'SysE.' Apparently this means that Luma3DS booted into SysNAND from EmuNAND. Wut. How can I boot into regular EmuNAND?

I looked it up, and one thread gave the vague suggestion of "checking to see of the 'Use second EmuNAND as default' was checked," so I tried out booting with said option checked, but I was given the same result.



Tl;dr: when I boot with Luma3DS, System Settings says I'm in SysNAND (SysE 9.2.0-20 US) when it should be saying that I'm in EmuNAND (Emu 9.2.0-20 US). If you'd like, you could also explain to me in layman's terms what the heck the difference between Red and EmuNAND is. I'll give you a cookie.

I have an Old3ds, the SysNAND firm is 9.2.0-20 US, and the EmuNAND firm should be the same, but of course I can't really check. I'm using Luma3DS v5.5.

Thanks in advance for putting up with my silly noob brain.

 

[KunoichiZ]

Do you have the luma folder in your SD card's root?

RedNAND is just a smaller emuNAND, meaning it takes up less space on your SD card.

 

[CesiumBullets]

Yes, I do. I have both the luma folder and the Luma3DS.dat file on the root of my SD.

 

[exdeath255]

RedNAND [redirected NAND] and EmuNAND [Emulated NAND] are the same thing except rednand is smaller and they are located in a different part on the sd card , one at the start and one at the end or something.

 

[Quantumcat]

You should uninstall menuhax in emuNAND so you don't have to hold the trigger button (as simple as changing the theme). You should also have menuhax setup as per the guide (holding down button to boot, not autoboot and having to hold a button to not boot).

 

[Hayleia]

RedNAND [redirected NAND] and EmuNAND [Emulated NAND] are the same thing except rednand is smaller and they are located in a different part on the sd card , one at the start and one at the end or something.

From what I understood, they are both at the "beginning" of the SD card actually. It's just that the emuNAND puts the beginning of the NAND at the end of the NAND's data, meaning that even if there is a lot of unused space, it has to use padding to know where that beginning was; and the redNAND just puts everything in the normal order, but shifted, meaning that it can trim the end and that's why it's smaller.

 

[CesiumBullets]

You should uninstall menuhax in emuNAND so you don't have to hold the trigger button (as simple as changing the theme). You should also have menuhax setup as per the guide (holding down button to boot, not autoboot and having to hold a button to not boot).

Wow. I first thought that that'd be the dumbest thing to try, but it miraculously worked! All I did was go into menuhax manager and changed the trigger button to down on the d-pad, and now when I enter Luma3DS, I'm booted into EmuNAND. Thanks!

Oh and thanks to everyone else for the explanation of RedNAND and EmuNAND. I just gave you a telepathic cookie.

 

[Vanth88]

Wow. I first thought that that'd be the dumbest thing to try, but it miraculously worked! All I did was go into menuhax manager and changed the trigger button to down on the d-pad, and now when I enter Luma3DS, I'm booted into EmuNAND. Thanks!

Oh and thanks to everyone else for the explanation of RedNAND and EmuNAND. I just gave you a telepathic cookie.

In case you or anyone is curious why this worked look here: https://github.com/AuroraWright/Luma3DS/wiki/Options-and-usage


SysNAND is updated (A9LH-only): This option does two things.

• On:
  1. Use FIRM from SysNAND to boot EmuNAND with R (You can't boot 10.x with 9.x NATIVE_FIRM).
  2. luma/firmware.bin will be used as a replacement for the SysNAND FIRM.
• Off:
  1. Use FIRM from EmuNAND to boot SysNAND with R (You can't boot 10.x with 9.x NATIVE_FIRM).
  2. luma/firmware.bin will be used as a replacement for the EmuNAND FIRM.