Hacking Luma3DS - Noob-proof 3DS Custom Firmware

[Supster131]

10.6 doesn't update NATIVE_FIRM, so it's safe... it should patch browserhax and menuhax, but that's it

Yup! Just updated my sysNAND to 10.6. Everything works fine (including the HBL cia).

 

[Svaethier]

Yep everything is a OK on 10.6

 

[Disharmony16]

Updated the emunand to 10.6 and all work fine

 

[D34DL1N3R]

Why would a person update their sysNAND if browserhax & menuhax are patched? I don't think I'm understanding this entire arm9 thing at all. So you don't need an emunand anymore? I would think one is still needed. What if the arm9 thing get's blocked with a future update - thus requiring a hard mod to downgrade? I dunno. Like I said, I think I'm not understanding the entire thing.

 

[DocKlokMan]

Just wanted to say I've set this up using emuNAND (not quite willing to do the sysNAND <--> emuNAND swap yet) and it's beautiful! Running it with A9LH and couldn't be happier. I'm running the 10.4 firmware BIN file at the moment, but would like NTR for the CPU hack and screenshots. Any big differences between the 10.2 and 10.4 firmwares?

 

[Svaethier]

Why would a person update their sysNAND if browserhax & menuhax are patched? I don't think I'm understanding this entire arm9 thing at all. So you don't need an emunand anymore? I would think one is still needed. What if the arm9 thing get's blocked with a future update - thus requiring a hard mod to downgrade? I dunno. Like I said, I think I'm not understanding the entire thing.

Well since you can just swap emunand and sysnand around so your emunand stuff is on sysnand it's easier to just use sysnand now. Homebrew loader still works on 10.6 FYI.

 

[Kioku]

Well since you can just swap emunand and sysnand around so your emunand stuff is on sysnand it's easier to just use sysnand now. Homebrew loader still works on 10.6 FYI.

I feel it's still safer to have emunand as main. I haven't really seen a good enough explanation as to why I'd want to switch everything to sysnand.. Even with a9lh..

 

[stl25]

I agree with you @Mchief298. AuReiNand allows access to sysNAND 9.0 sigpatched where all homebrew like Decrypt9UI, hblauncher_loader and other installed cias can be run. This leaves emuNAND available to be updated to the latest and greatest FW for installed cia games and such.

Everything thus far in the 3DS scene has focused on leaving sysNAND as vanilla as possible (9.2 or earlier FW). I realize arm9loaderhax gives us more options with sysNAND, but we have direct boot cfw without the need for updating sysNAND and if GBA/GBC custom games are your thing boot into sigpatched 9.0 Firm mode by holding L (effectively pastacfw) and play away. No need to install to emunand. Just my 2 cents from a distance.

 

[Kioku]

I agree with you @Mchief298. AuReiNand allows access to sysNAND 9.0 sigpatched where all homebrew like Decrypt9UI, hblauncher_loader and other installed cias can be run. This leaves emuNAND available to be updated to the latest and greatest FW for installed cia games and such.

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

Everything thus far in the 3DS scene has focused on leaving sysNAND as vanilla as possible (9.2 or earlier FW). I realize arm9loaderhax gives us more options with sysNAND, but we have direct boot cfw without the need for updating sysNAND and if GBA/GBC custom games are your thing boot into sigpatched 9.0 Firm mode by holding L (effectively pastacfw) and play away. No need to install to emunand. Just my 2 cents from a distance.

I wish I left my sysnand as vanilla as possible. Installed a few things that I really shouldn't have. Everything still works. I can't wait for my system to come back so I can get a9lh up and running..

 

[shorty_bobert]

seems kinda like A9LH is nice and all, but I don't feel safe without a permanent back-up plan. I use menuhax on 9.2 sysNAND and a 10.5 emuNAND so if I mess something up I can just re-flash my emuNAND.

 

[DocKlokMan]

I feel it's still safer to have emunand as main. I haven't really seen a good enough explanation as to why I'd want to switch everything to sysnand.. Even with a9lh..

I agree with you. Essentially A9LH makes booting emuNAND effortless, so besides the 1-2 GBs taken up by the emuNAND partition, I don't see enough to pull me away. Some benefits do entice me though, such as being able to remove my SD card while the system is on, only needing to install GBA games on one NAND, not having to worry about linked NANDs.

Things I'm worried about: System transfer to another 3DS, accidently updating FIRM 0 and FIRM 1 and erasing my A9LH, not having a test NAND for new system updates. Plus I can always resort to menuHax to boot my emuNAND if A9LH breaks. Overall, I'll stick with emuNAND as my main and just enjoy the improved booting.

 

[stl25]

A9LH despite being the new kid on the block has already given most users the basic functionality the scene has been clamoring for. I can't wait to see some of the unique ways the talented devs will incorporate it into their projects.

 

[D34DL1N3R]

I think that's what I'll do. Use arm9loaderhax but keep sysNAND @ 9.2 and emuNAND at the latest. Like others have said, I see zero reason to get rid of emuNAND and use strictly sysNAND only. Seems pretty risky to me.

 

[DocKlokMan]

Once we figure out LCD init, then we'll have an A9LH boot menu I'm assuming. Then we can choose what to run without button combos and also have some new homebrew that takes advantage of this new boot method that would otherwise not be possible.

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

seems kinda like A9LH is nice and all, but I don't feel safe without a permanent back-up plan. I use menuhax on 9.2 sysNAND and a 10.5 emuNAND so if I mess something up I can just re-flash my emuNAND.

You can keep using emuNAND, just replace menuhax with A9LH. You'll see vastly improved boot times, 100% boot success and still have a way to recover with your 9.2 sysNAND. Plus future opportunities to other things only possible with A9LH.

 

[shorty_bobert]

You can keep using emuNAND, just replace menuhax with A9LH. You'll see vastly improved boot times, 100% boot success and still have a way to recover with your 9.2 sysNAND. Plus future opportunities to other things only possible with A9LH.

Maybe if I get the time to compile it I'll replace menuhax then. I already auto-boot to reiNAND, but I'm starting to get annoyed with having to boot twice to load reiNAND every time I take the SD card out.

 

[Svaethier]

Some people want to use sysnand over emunand now because the ability to have a sysnand as cfw with a9lh using reinand mod is now possible where months ago it wasn't. People still will use their emunand but as a testing ground to make sure new things work before using them on sysnand.

 

[stl25]

@Svaethier, I see the the pros of what you listed, but the devs who make these great projects probably do test in an emunand environment. Even if you mess up emunand you can use tools like emuNAND9 to restore it. With mulitple emuands now possible that would be even easier, use 1 for testing another for everyday use.

 

[RednaxelaNnamtra]

I think that's what I'll do. Use arm9loaderhax but keep sysNAND @ 9.2 and emuNAND at the latest. Like others have said, I see zero reason to get rid of emuNAND and use strictly sysNAND only. Seems pretty risky to me.

The other way would to swap emunand and sysnand(that what I have done). And it worked without a problem for me(already bricked my sysnand once with arm9loaderhax, but I simply booted up emunand and loaded decrypt9 from there to restore the ctrnand partition).

 

[Svaethier]

@Svaethier, I see the the pros of what you listed, but the devs who make these great projects probably do test in an emunand environment. Even if you mess up emunand you can use tools like emuNAND9 to restore it. With mulitple emuands now possible that would be even easier, use 1 for testing another for everyday use.

Yea you could but who wants to go through all that trouble to make a emunand that you'll barely use when you could just have the one you already have as the testing environment? It just doesn't make sense

 

[stl25]

Brick and sysNAND in the same sentence will never make anyone comfortable. If something happened to arm9loaderhax and you can not access emuNAND, you would have no way to restore sysNAND.