Hacking Luma3DS - Noob-proof 3DS Custom Firmware

[Aurora Wright]

I'm using the new reinand mod version 3.5 that was just pushed out like 15 minutes ago which auto boots the patched sysnand.

That's the whole reason I suggested to make a 9.0 emuNAND Decrypt9 and stuff can't work with a post-9.0 FIRM.

 

[lettuce]

What button do you need to press to boot into the homebrew launcher?

 

[Svaethier]

so I should just go back to 3.4 and run decrypt9 to extract those things mentioned then patch them into emunand and sysnand?

 

[Aurora Wright]

What button do you need to press to boot into the homebrew launcher?

This has nothing to do with reinand.

 

[AtlasFontaine]

Managed to boot with the "udpatedsysnand" dummy, I'm going to update the sysnand with system settings asap.

I hope this thing doesn't brick or I'm doomed lmao

 

[Supster131]

Let me get this straight.

I'll modify the things you told me about yesterday, Aurora. (For the multinand and different button configuration).


So, with this new update, I can update my sysNAND to 10.5 through MSET, and the 9.0 FIRM will work on 10.5 so I can continue to use Decrypt9, correct?

 

[lettuce]

Ok, so the reason i wanted to use Arm9LoaderHax method was because i understood that it fixed the 3D bug, but i forgot this bug doesn't effect the o3ds system, so dont really need to use Arm9LoaderHax and just stick with AuReiNand.

So all i have done, is extracted...

ReiNand.dat
Boot.3dsx (from the menuhax folder)
rei-o3ds folder (renamed to 'rei')

from the AuReiNand 3.5.zip file, and copied them to my SD card. When i boot my o3ds now it boots in emunand mode, looking in the system menu it reports 10.3.0-28e as my FW, should it not mention Rei in the fw name? In this mode is it safe for me update the FW via the system update menu in settings or not?

Also what advantage on a o3ds system, do i have of going down the Arm9LoaderHax path and having to downgrade my o3ds to 2.x to get the OTP of my system, over just using the normal Aureinand method, that i currently using?

 

[democracy]

New version!

• Fixed A9LH boot detection
• Added a new "updated sysNAND" mode, which is enabled by the "/rei/updatedsysnand" flag. In this mode, sysNAND is booted by default using the 9.6-10.4 FIRM, L boots emuNAND with 9.0 FIRM (for arm9 exploits and such) and L+R boots emuNAND with the 9.6-10.4 FIRM.
• When sysNAND is booted on a A9LH setup, a patch (courtesy of delebile) is applied that makes updates skip writing to FIRM0 and FIRM1. This way, sysNAND can be updated without losing A9LH.

Wow. Thank you. Anyone try updating their sysnand yet to latest using this very sweet package?

 

[subcon959]

Is there any benefit to using an updated sysNAND instead of continuing to use emuNAND?

 

[AtlasFontaine]

Updated sysnand, Ayy now I can say that I'm on the A9LH 10.5 sysnand master race to those menuhax peasants.

 

[Nintendo4DSXL]

Updated sysnand, Ayy now I can say that I'm on the A9lH 10.5 sysnand master race to those menuhax peasants.

So the mset update works this is good

 

[AtlasFontaine]

So the mset update works this is good

yeah, but you have to do it in "updatedsysnand" mode, creating a dummy file with that name and putting it on rei folder.

 

[DjoeN]

Ok to sum it up: (i don't need ntr)
I want to boot with arm9loaderhax to sysnand 10.5 on 1 system (O3DS) and emunand on my other system (2DS).

- Get latest rei mod (or compile yourself from source) and firms + my OTP.bin (have all that (compiled AuReiNand myself))

From \AuReiNand\out (or AuReiNandv5.7z)
- copy arm9loaderhax.bin to the root of my sd
- copy \rei-o3ds to sd and rename it rei
- copy \3ds to sd
- copy \menuhax to sd

From FIRMs.7z
- From \rei-o3ds -> copy firmware90.bin and firmware.bin to root of sd

What about:
- What to do with the installa9lh file?, just copy it to the root of my sd?
- What about my dumped OTP.bin?
- What about arm9loaderhax.3dsx?

 

[templeofhylia]

no, ignore it. sorry. What i want to say is sorry because I confused your post and.....

sorry for the late response but no worries!

anyway, is it possible to change what buttons boot the different sysnand firms, or make it so sysnand is autobooted instead? it might not be practical but it'd be cool to know how to provide myself with an alternative

 

[Svaethier]

Use Decrypt9 to extract the CTRNAND, TWLN, TWLP and AGBSAVE partitions (DON'T, DON'T do it with FIRM0 and FIRM1) from emuNAND, import them on sysNAND. IF you want, export them from sysNAND and import them into emuNAND first, so you have a 9.0 emuNAND.

well I tried this with the sysnand partitions injected into emunand but now emunand doesn't boot up.

 

[FenrirWolf]

Is there any benefit to using an updated sysNAND instead of continuing to use emuNAND?

Autobooting directly to an emunand on a fast SD card will probably work just as well as running from sysnand. I guess the main thing is if you care about recovering that extra 1/2GB of space from your SD card, or if you just like the idea of having total ownership of the sysnand.

EDIT: And in the case of the N3DS, booting to a CFW'd sysnand also makes it so you no longer have to put the console in and out of sleep mode to fix 3D display output.

 

[Supster131]

Autobooting directly to an emunand on a fast SD card will probably work just as well as running from sysnand. I guess the main thing is if you care about recovering that extra 1/2GB of space from your SD card, or if you just like the idea of having total ownership of the sysnand.

EDIT: And in the case of the N3DS, booting to a CFW'd sysnand also makes it so you no longer have to put the console in and out of sleep mode to fix 3D display output.

That's no longer the case with Arm9LoaderHax. A9LH fixes the "broken" 3D in emuNAND.

 

[JacksonS]

Could you change the button combination (L+R) or let us choose our own for booting into emuNAND with firmware.bin? I always end up starting up the camera...

 

[fate6]

EDIT: And in the case of the N3DS, booting to a CFW'd sysnand also makes it so you no longer have to put the console in and out of sleep mode to fix 3D display output.

This is not an issue with a9lh as 3D works fine in both NANDs with it.
Oh and yes you still need to close the lid on sysNAND if using any of the regular entry points afaik.

EDIT: Darn crafty ninjas!

 

[Supster131]

Could you change the button combination (L+R) or let us choose our own for booting into emuNAND with firmware.bin? I always end up starting up the camera...

You can, and Aurora told me how to yesterday not as easy as you think.