Hacking Luma3DS - Noob-proof 3DS Custom Firmware

[Nikolay]

Makes sense. I guess I have the firmware90.bin in the wrong place (in the rei folder) because I just get the "an error has occured" black screen when booting with L.

Firmware90.bin does go into the rei folder. Is it possible that you're using the N3DS firmware90.bin instead of the O3DS one?

 

[katrain]

Firmware90.bin does go into the rei folder. Is it possible that you're using the N3DS firmware90.bin instead of the O3DS one?

I definitely have the O3DS firmware90.bin
edit: figured out the issue (kinda)

 

[Pacman`]

I definitely have the O3DS firmware90.bin

Put BOTH firmware.bin AND firmware90.bin in your Rei folder.
Now, copy installeda9lh (it's an empty file) to your Rei folder.
Press L then press on power. You can stop pressing L after like 3-4 secs.

This will boot you into 9.0 sysnand and Decrypt9 will then work.
If ever you can't boot into sysnand 9.0, make sure "installeda9lh" is there in your Rei folder

 

[democracy]

Just want to say thank you to Aurora and team for AuReiNand

Thank you

 

[erest0r]

Hi,
I'm on O3ds 10.6 emuNAND 9.2 sysNAND.
I followed the guide but I can't boot emuNAND, only sysNAND works with pressing L/R at boot.

 

[jackb994]

Just want to say thank you to Aurora and team for AuReiNand

Thank you

+1

 

[peteruk]

+1

+2

 

[mungry]

Is it normal if there is no string added to the firmware in emunand? Using v3.6.1

 

[jackb994]

Is it normal if there is no string added to the firmware in emunand? Using v3.6.1

yeh

 

[Rohul1997]

+2

+3

--------------------- MERGED ---------------------------

Hi,
I'm on O3ds 10.6 emuNAND 9.2 sysNAND.
I followed the guide but I can't boot emuNAND, only sysNAND works with pressing L/R at boot.

did you put the firmware.bin and firmware90.bin files in the rei folder?

 

[katrain]

Put BOTH firmware.bin AND firmware90.bin in your Rei folder.
Now, copy installeda9lh (it's an empty file) to your Rei folder.
Press L then press on power. You can stop pressing L after like 3-4 secs.

This will boot you into 9.0 sysnand and Decrypt9 will then work.
If ever you can't boot into sysnand 9.0, make sure "installeda9lh" is there in your Rei folder

I already had both bins but adding the empty installeda9lh file didn't help.
edit: Just added decrypt9 to the boot manager so this doesn't matter too much now
edit2: Held L for less time and it worked. Weird.

 

[Sumea]

I already had both bins but adding the empty installeda9lh file didn't help.
edit: Just added decrypt9 to the boot manager so this doesn't matter too much now

You also need "updatedsysnand" emptyfile to trigger the different behaviour if you update your sysnand and have emunand on 9.2

 

[Aurora Wright]

installeda9lh isn't needed unless for some reason you're planning to use the .dat after booting 9.0 with a9lh you'll probably only ever need the updatedsysnand flag.
It autodetects that you're using a9lh to boot.

 

[Pacman`]

installeda9lh isn't needed unless for some reason you're planning to use the .dat after booting 9.0 with a9lh you'll probably only ever need the updatedsysnand flag.
It autodetects that you're using a9lh to boot.

With 3.6.1 + A9LH, I now notice that I no longer need installeda9lh in the Rei folder in order to boot to sysnand 9.0 (aka pastamode) using L.
However, now I'm seeing a patched_firmware.bin in the folder.

Edit: N3DS XL

 

[Aurora Wright]

With 3.6.1 + A9LH, I now notice that I no longer need installeda9lh in the Rei folder in order to boot to sysnand 9.0 (aka pastamode) using L.
However, now I'm seeing a patched_firmware.bin in the folder.

Edit: N3DS XL

That file is needed, it's automatically generated on boot to make the reboot patch work (this makes the 178 MB cias work ). It already existed on Old 3DS.

 

[dkabot]

That file is needed, it's automatically generated on boot to make the reboot patch work (this makes the 178 MB cias work ). It already existed on Old 3DS.

Would that be why my first boot after the update took notably longer than any subsequent one?
Just curious.

 

[Pacman`]

So, holding L on boot takes us to pastamode on sysnand?
Please confirm this. Tkx

 

[OrGoN3]

Aurora, thanks for all of your hardwork. This just keeps getting better and better!

 

[Supster131]

So, holding L on boot takes us to pastamode on sysnand?
Please confirm this. Tkx

Yeah, something like that.
sysNAND with the 9.0 FIRM and sig-patched.

 

[Pacman`]

Yeah, something like that.
sysNAND with the 9.0 FIRM and sig-patched.

So in the event I had to use sysUpdater on sysnand, for whatever reason, it would be safe?