Hacking Luma3DS - Noob-proof 3DS Custom Firmware

[Supster131]

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

It would technically be safe, but I can't vouch for it. If you're planning on using sysNAND as your main NAND, make sure you create the updatedsysnand flag. You should be safe to update normally (through system settings) by then.

I'd recommend having a 9.0-9.2 emuNAND so you can run some homebrew that doesn't work on 9.3+.

 

[Pacman`]

It would technically be safe, but I can't vouch for it. If you're planning on using sysNAND as your main NAND, make sure you create the updatedsysnand flag. You should be safe to update normally (through system settings) by then.

I'd recommend having a 9.0-9.2 emuNAND so you can run some homebrew that doesn't work on 9.3+.

Thanks for replying.

My aim is to boot into current version emunand to play 3ds games and update them on eshop.
I also want to be able to use L to boot into 9.2 Sysnand (never updating it under normal conditions), but only use it to play GBA games, say, or use apps like Decrypt9.

That's about it.

I had a few problems, going from capito's A9LH to dark-samus3's version, and using AuReiNand (from 3.5.3 to 3.6.1), but now everything works.

 

[Zyrmkel]

so I wanna know how safe is updating sysnand with a9lh with this mod is?

 

[Supster131]

so I wanna know how safe is updating sysnand with a9lh with this mod is?

Pretty safe, just make sure you create the updatedsysnand file in the /rei/ folder.

 

[Zyrmkel]

Pretty safe, just make sure you create the updatedsysnand file in the /rei/ folder.

so they've patched firm0+firm1 overwriting?

 

[Supster131]

so they've patched firm0+firm1 overwriting?

Yes, Aurora patched FIRM0/FIRM1, so you can update through System Settings normally. (With that updatedsysnand file)

 

[Zyrmkel]

Yes, Aurora patched FIRM0/FIRM1, so you can update through System Settings normally. (With that updatedsysnand file)

cool

 

[Aurora Wright]

Yes, Aurora patched FIRM0/FIRM1, so you can update through System Settings normally. (With that updatedsysnand file)

Actually the flag is not needed, the only requirement is that you're running on A9LH (so to be clear, you can update booting sysNAND with L or R without the flag).

 

[Supster131]

Actually the flag is not needed, the only requirement is that you're running on A9LH (so to be clear, you can update booting sysNAND with L or R without the flag).

I thought it was, thanks for clearing that up!

 

[Sachi]

What do the different flags do exactly?

 

[Supster131]

What do the different flags do exactly?

No flag means your emuNAND will boot automatically.
updatedsysnand flag means your sysNAND will boot automatically.

 

[Sachi]

No flag means your emuNAND will boot automatically.
updatedsysnand flag means your sysNAND will boot automatically.

What about "installeda9lh"?

 

[FenrirWolf]

IIRC that one is just a redundancy to make sure that FIRM writes are patched out during system updates. AuReiNand will autodetect if it's launching directly from A9LH, but suppose you instead launch a boot manager from A9LH that in turn launches AuReiNand. I don't know how good the autodetection of A9LH is, but maybe in that scenario it might think that it was just launched from Brahma instead of A9LH. So creating the "installeda9lh" helps make sure that you won't one day accept an update that overwrites your hax.

 

[Aurora Wright]

IIRC that one is just a redundancy to make sure that FIRM writes are patched out during system updates. AuReiNand will autodetect if it's launching directly from A9LH, but suppose you instead launch a boot manager from A9LH that in turn launches AuReiNand. I don't know how good the autodetection of A9LH is, but maybe in that scenario it might think that it was just launched from Brahma instead of A9LH. So creating the "installeda9lh" helps make sure that you won't one day accept an update that overwrites your hax.

It detects that FIRM hasn't already ran by detecting that the SPI registers are still disabled (a random thing FIRM does on boot).

 

[FenrirWolf]

Nice.

Redundancies don't hurt though, so I went and set the flag on my system anyway.

 

[matpower]

Hmm, I have a quick question about the patched sysNAND FIRM update, does AuReiNAND still load the newest one from firmware.bin on the updatedsysnand mode?

 

[dkabot]

What about "installeda9lh"?

That forces it to act as though it detected A9LH.
This is intended to be used for cases of booting the 3dsx later on, after the initial boot.

 

[ShadowOne333]

@Aurora Wright , I have one important question.

Seeing how your work and mod seems to be the most focused on A9LH at the moment, I was wondering if perhaps you could add an option to be able to boot emunand in the 2.1 firmware?
I know that this might require the firmware specific offsets, firm files and other stuff, but by being able to boot an emunand in 2.1 we will have a way to be ABSOLUTELY sure if we downgraded (and patched in N3DS case) the emunand correctly.
That way, we know for sure that flashing the sysnand with such emunand will be completely brick-free for those that want to get the OTP file.

Just a quick suggestion that would greatly increase the range and use of your AuReiNAND mod.

 

[Zyrmkel]

Aurora, I have one important question.

Seeing how your work and mod seems to be the most focused on A9LH at the moment, I was wondering if perhaps you could add an option to be able to boot emunand in the 2.1 firmware?
I know that this might require the firmware specific offsets, firm files and other stuff, but by being able to boot an emunand in 2.1 we will have a way to be ABSOLUTELY sure if we downgraded (and patched in N3DS case) the emunand correctly.
That way, we know for sure that flashing the sysnand with such emunand will be completely brick-free for those that want to get the OTP file.

Just a quick suggestion that would greatly increase the range and use of your AuReiNAND mod.

well if the patching for n3ds' nand dump goes wrong it'll cause a brick so imo having 2.1 emunand is irrelevant

 

[ShadowOne333]

well if the patching for n3ds' nand dump goes wrong it'll cause a brick so imo having 2.1 emunand is irrelevant

WHat do you mean?
We still could try booting up the patched N3DS NAND in emunand to verify it boots.