Hacking Luma3DS - Noob-proof 3DS Custom Firmware

[Games&Stuff]

It's so you can boot 9.2. Place the file in the /rei/ folder, alongside the firmware.bin file.

Do I always need to delete it if I want to boot 10.6?

 

[Supster131]

Do I always need to delete it if I want to boot 10.6?

No, it's recommended to have both of them.
That way you can boot into emuNAND and sysNAND when ever you want.

 

[Games&Stuff]

No, it's recommended to have both of them.
Nvm. Do you know how I can create the file that supports the latest sysnand version?

 

[Supster131]

Okay, do I need to have ctrbootmanager9 for that or...

No, if you're on the latest build, L boots you into your other NAND, while pressing nothing at boot boots you into your main NAND.

 

[Games&Stuff]

No, if you're on the latest build, L boots you into your other NAND, while pressing nothing at boot boots you into your main NAND.

I get a glitchy screen when pressing L, and have menuhax with autoboot setup.

 

[Supster131]

I get a glitchy screen when pressing L, and have menuhax with autoboot setup.

Turn off your 3DS. Press L for one second when turning your 3DS on. Then change the theme.

 

[Svaethier]

I get a glitchy screen when pressing L, and have menuhax with autoboot setup.

delete menuhax

 

[Games&Stuff]

Turn off your 3DS. Press L for one second when turning your 3DS on. Then change the theme.

Still get the glitchy screen.

 

[Supster131]

Still get the glitchy screen.

Delete the menuhax files from your SD card, then try again.

 

[Games&Stuff]

Delete the menuhax files from your SD card, then try again.

Payload too?

 

[Supster131]

Payload too?

Menuhax payload? Yes.

 

[Games&Stuff]

Thanks it worked!

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

No, if you're on the latest build, L boots you into your other NAND, while pressing nothing at boot boots you into your main NAND.

Now, when I hold L, I get the glitchy screen, and after that I get the "an error has ocurred" message.

 

[Supster131]

Thanks it worked!

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


Now, when I hold L, I get the glitchy screen, and after that I get the "an error has ocurred" message.

Press it for 1 second only.

 

[Lacius]

yes. Replace firmware.bin with firmware90.bin and make a file called "updatedsysnand"

I thought I tried that and it didn't work. I will try again and let you know if it works.

 

[Aurora Wright]

lol I didnt even mention I made some small modifications myself to it yesterday over on my github:
-if a /rei/use_patched_fw file exists then AuReiNand will only write the patched firmware needed for reboots once and after that re-use this existing one, making the startup ever so slightly faster and saving some sd write cycles
-split patched_firmware to now also create patched_emu_firmware, this is done just in case somebody uses this option and needs a patched firmware for both sysnand and emunand
-added another reboot code file to handle that new firmware name for emunand exclusively
if you wanna check it out for whatever reason here is a build. I also made a pull request for it here cause I think this would be neat to have in the main build.

This has drawbacks though. People are working "behind the scenes" for working arm9 hooks, and people would need to delete the patched_firmware's every time the output FIRM changes.
Also it borks N3DS. As it is, arm9loader "decrypts" the arm9bin, but in reality it re-encrypts it, all the keys are set wrong and it tries to boot the encrypted arm9bin
I'll think if it's feasible to implement this differently.

 

[FIX94]

This has drawbacks though. People are working "behind the scenes" for working arm9 hooks, and people would need to delete the patched_firmware's every time the output FIRM changes.

Thats why I thought it would be a good idea to only make it optional with having that extra file.

Also it borks N3DS. As it is, arm9loader "decrypts" the arm9bin, but in reality it re-encrypts it, all the keys are set wrong and it tries to boot the encrypted arm9bin

Interesting, I'm on o3ds so I guess thats why I never noticed an issue like that. Thanks for letting me know.

 

[gameking66]

Is there a way to disable the FIRM write blocks? Unless I'm misunderstanding, it's preventing me from overwriting/deleting TWL_FIRM (I corrupted mine and need to fix it).

EDIT: Actually, I can't seem to install anything with FBI after launching A9LH AuReiNAND

 

[Aurora Wright]

Thats why I thought it would be a good idea to only make it optional with having that extra file.

Interesting, I'm on o3ds so I guess thats why I never noticed an issue like that. Thanks for letting me know.

You really can't imagine how many people on here would enable that and then come here complaining that the new patches don't work. XD
I get endless help requests from people who are unable to place firmware.bin and firmware90.bin and tell me that "it doesn't work". Or people who didn't read that you had to press A with the old reboot patch to make GBA/DS games work.

 

[Lacius]

yes. Replace firmware.bin with firmware90.bin and make a file called "updatedsysnand"

Tried again. This boots into sysNAND/menuhax, but "Updated sysNAND" Mode doesn't allow for other emuNANDs to be run, even if I replace firmware.bin with firmware90.bin. If I hold L in Regular Mode, other emuNANDs run fine after booting into sysNAND/menuhax.

 

[OctopusRift]

Tried again. This boots into sysNAND/menuhax, but "Updated sysNAND" Mode doesn't allow for other emuNANDs to be run, even if I replace firmware.bin with firmware90.bin. If I hold L in Regular Mode, other emuNANDs run fine after booting into sysNAND/menuhax.

weird.