Hacking Luma3DS - Noob-proof 3DS Custom Firmware

[matpower]

How would one do it if they wanted to restore the ARM9 thread? Feels kind of strange to not see "Rei:." in system settings and makes updating EmuNand a horror movie.
Can a simple user even do it?

You just need to flash your backup from before ARM9LoaderHax to remove it if you want.
Also if your NANDs are unlinked, they should have different themes or something like that, also the obvious Ver. difference, after all, sysNAND is 9.2 while emuNAND is 9.3+

 

[Supster131]

That's the thing. My Sys and EmuNAND are on the same FW.

AuReiNAND automatically boots into emuNAND, so there's nothing to worry about. Just update away!

 

[Just Passing By]

That's the thing. My Sys and EmuNAND are on the same FW.

Well if you're on a9lh, just boot it up without any flags, and put a theme on your home menu. BOOM! Your new Rei:. tag. And yeah make sure you're NANDs are unlinked.

 

[RepeatingDigits]

Well if you're on a9lh, just boot it up without any flags, and put a theme on your home menu. BOOM! Your new Rei:. tag. And yeah make sure you're NANDs are unlinked.

Not using A9LH. I just found about it today and I don't even know how to install it.

 

[tvall]

btw, just updated sysnand from 9.2 to 10.6 in system settings while using a9lh and aureinand. so that firm protecting patch does seem to work

 

[Just Passing By]

Not using A9LH. I just found about it today and I don't even know how to install it.

Oh lol. Well doesn't that make it easier? If nothing's autobooted, you're on emuNAND. If you want to really, really, make sure you're on sysNAND, delete any cfw stuff on your sd card, and throw in some type of identifier on your sysNAND (probably not a theme since that will remove themehax).

Also if you're feeling brave:
https://gbatemp.net/threads/otp-guide.415140/

 

[RepeatingDigits]

Oh lol. Well doesn't that make it easier? If nothing's autobooted, you're on emuNAND. If you want to really, really, make sure you're on sysNAND, delete any cfw stuff on your sd card, and throw in some type of identifier on your sysNAND (probably not a theme since that will remove themehax).

Also if you're feeling brave:
https://gbatemp.net/threads/otp-guide.415140/

Eh, it's mostly just an OCD thing, It's not like I can't tell Sys from Emu this far into the game.

 

[Just Passing By]

Eh, it's mostly just an OCD thing, It's not like I can't tell Sys from Emu this far into the game.

Lol I had a little freak attack when I didn't see anything to indicate emuNAND and sysNAND. It feels wrong and still does, but you start to get over it.

 

[Jiro2]

I am using menuhax and CtrBootManager, O3DS, with 9.2 SysNAND. This setup works fine to boot Gateway or RX.

Does this use the same EmuNAND as Gateway/RX?

Does this require a firmware.bin in order to boot EmuNAND? (SysNAND with patched signature checks will boot for me, even without a firmware.bin, but I can't get EmuNAND to run.)

What exactly should firmware.bin be? Does it have to match your EmuNAND and/or your SysNAND? Is there a way to tell it to just use the firmware in your EmuNAND, rather than having to supply a firmware.bin?

Where should the ReiNand.dat be placed? Root or rei folder?

What is the difference between the menuhax/boot.3dsx and the 3ds/ReiNand/boot.3dsx? They are almost but not quite the same size.

If I want to get a firmware.bin, can I just dump my NAND and use the result?

 

[Noelemahc]

Weren't 78% of your questions answered on the first page of the thread?

Firmware.bin from other CFWs cannot be used. It is necessary though. It's in this project's thread on that iso site. Make sure you use the correct one for your 3DS type.

The menuhax folder 3dsx is if you autoboot through menuhax and the DAT loads with problems for some reason. If you use a boot manager (CtrBoot or otherwise), you feed the DAT to it. The homebrew folder 3dsx is for running through the HBL, all depends on how your system is set up.

You put the DAT in root.

 

[MgARBITER]

Hello! Im a little confused on the "recovery" part of using Arm9LH. I have sysnand in 9.2. Emunand in 10.6 with AuRereiNand and so far everything works great. Boots right into emunand and when i hold R it goes to sysnand. (For some reason holding L does nothing. Idk if that is normal). My question is how do i get Decrypt9 to load up and act as a "recovery"? I cant seem to find any guide that explains setting up decrypt9 (unless i'm just that blind).

For what its worth, this is what my root and rei folder look like. Those check out, right? http://imgur.com/a/fskww

 

[OrGoN3]

Noob question. I'm planning things out. It seems arm9lh with aureinand on sysnand 10.6 and emunand 9.0. in this setup, how would one go about installing anything (.cia) or running homebrew (.3dsx)? Would I have to reboot into emunand to load up HBL to do this or can this be done through sysnand? (Or can HBL be installed to sysnand?)

 

[Noelemahc]

Noob question. I'm planning things out. It seems arm9lh with aureinand on sysnand 10.6 and emunand 9.0. in this setup, how would one go about installing anything (.cia) or running homebrew (.3dsx)? Would I have to reboot into emunand to load up HBL to do this or can this be done through sysnand? (Or can HBL be installed to sysnand?)

The idea for such a setup is that AuReiNAND will give you access to do yo sysnand what you currently do in emunand, and the 9.0 emunand serves as a recovery/emergency partition, as i understand.

 

[DjoeN]

Hello! Im a little confused on the "recovery" part of using Arm9LH. I have sysnand in 9.2. Emunand in 10.6 with AuRereiNand and so far everything works great. Boots right into emunand and when i hold R it goes to sysnand. (For some reason holding L does nothing. Idk if that is normal). My question is how do i get Decrypt9 to load up and act as a "recovery"? I cant seem to find any guide that explains setting up decrypt9 (unless i'm just that blind).

For what its worth, this is what my root and rei folder look like. Those check out, right? http://imgur.com/a/fskww

Your firmware90.bin belongs into the "rei" folder
then booting sysnand by golding 'L' with firmware90.bin will work.

[EDIT]
You really also should have the latest "Decrypt9WIP" on your SD
Once this is installed and the firmware*.bins in the rei folder, you can boot into Sysnand 9.2 with firmware90.bin by holding the 'L' button and run HBL from there, then you can use Decrypt9 to make a A9LH sysNAND backup (and Emunand backup to)

Tip:
Hold 'L' first, then power on while holding 'L', same for holding 'R'

 

[GBHAKC75]

Your firmware90.bin belongs into the "rei" folder
then booting sysnand by golding 'L' with firmware90.bin will work.

[EDIT]
You really also should have the latest "Decrypt9WIP" on your SD
Once this is installed and the firmware*.bins in the rei folder, you can boot into Sysnand 9.2 with firmware90.bin by holding the 'L' button and run HBL from there, then you can use Decrypt9 to make a A9LH sysNAND backup (and Emunand backup to)

Tip:
Hold 'L' first, then power on while holding 'L', same for holding 'R'

He should setup CtrBoot instead. That way booting Decrypt9 is way faster, and it can be started even with bricked SysNAND+EmuNAND.

 

[DjoeN]

He should setup CtrBoot instead. That way booting Decrypt9 is way faster, and it can be started even with bricked SysNAND+EmuNAND.

Ah, nice to know (bit to late for me) i shipped my N3DSXL to @gamesquest1 to get it fixed form a corrupt sysnand flash (when trying to get OTP.bin) maybe that should have worked to get it recovered

 

[GBHAKC75]

Ah, nice to know (bit to late for me) i shipped my N3DSXL to @gamesquest1 to get it fixed form a corrupt sysnand flash (when trying to get OTP.bin) maybe that should have worked to get it recovered

No, it needs A9LH to be recovered. If you tried to get OTP that means you didn't had A9LH installed so there were nothing you can do.

 

[OrGoN3]

"Updated sysNAND" mode:
- For this, you NEED A9LH. You can toggle it by creating a "/rei/updatedsysnand" file.
- Normally sysNAND is autobooted.
- If you hold L on boot, emuNAND will be booted with the firmware90.bin on the SD card so you can use exploits (you need to create a 9.0/9.2 emuNAND for this!).
- If you hold R on boot, emuNAND will be booted with the firmware.bin on the SD card.

If your emuNAND is 9.0/9.2, and you hold R on boot, how is it that I can no longer use exploits that exist on 9.0/9.2? I'm a little confused by what Aurora meant by this.

 

[DjoeN]

No, it needs A9LH to be recovered. If you tried to get OTP that means you didn't had A9LH installed so there were nothing you can do.

Right, forgot about that
Anyway it was a good decision to ship it out then

 

[MgARBITER]

Your firmware90.bin belongs into the "rei" folder
then booting sysnand by golding 'L' with firmware90.bin will work.

[EDIT]
You really also should have the latest "Decrypt9WIP" on your SD
Once this is installed and the firmware*.bins in the rei folder, you can boot into Sysnand 9.2 with firmware90.bin by holding the 'L' button and run HBL from there, then you can use Decrypt9 to make a A9LH sysNAND backup (and Emunand backup to)

Tip:
Hold 'L' first, then power on while holding 'L', same for holding 'R'

OK, i moved the file. So there doesnt need to be one on the root either ,right? Just in the rei folder?

He should setup CtrBoot instead. That way booting Decrypt9 is way faster, and it can be started even with bricked SysNAND+EmuNAND.

Have a good guide on how to do so? Or give me a quick explanation. I was able to find and download CtrBoot, but dont know what my boot config should be like.