Hacking Luma3DS - Noob-proof 3DS Custom Firmware

[daxtsu]

guys, what actually could potentially brick your console having A9LH installed.
like what is it that we should avoid doing while using A9LH+CFW for example.
i myself am only needing emuNAND/and firm90 sysNAND at times, thats about it.

i only have d9 just in case , but i never play with it unless i absolultely am needing to do certain things with it.

so other than that, what should one not do , to not mess anything up with a9lh.
i just want to be safe with it because i love a9lh !

The main thing is to never boot sysNAND without a CFW that provides FIRM0/FIRM1 protection (they all do now except for RxTools), since updating without this protection will either A) brick your console if it's an N3DS, or B) remove A9LH if it's an O3DS.

 

[astronautlevel]

guys, what actually could potentially brick your console having A9LH installed.
like what is it that we should avoid doing while using A9LH+CFW for example.
i myself am only needing emuNAND/and firm90 sysNAND at times, thats about it.

i only have d9 just in case , but i never play with it unless i absolultely am needing to do certain things with it.

so other than that, what should one not do , to not mess anything up with a9lh.
i just want to be safe with it because i love a9lh !

Almost nothing can brick you unless you fuck with FIRM0/1.

 

[leonmagnus99]

I'm not sure myself either, but the one thing I can say 100% is to never install ANYTHING into the NAND partition(you don't have to have much of a brain to know you never install anything in there). Other than that I can't think of something that could brick you. Maybe a bad .CIA but I haven't seen one and I don't think I will.(The guys @ chaos/iso site do a good work imo).

true, i also know that NAND is a sensitive subject..

thus i am always very cautious always whenever i use FBI LOL... i always check if im installing the cia into NAND or SD.

but my main cia installer is SOON/BBM.

The main thing is to never boot sysNAND without a CFW that provides FIRM0/FIRM1 protection (they all do now except for RxTools), since updating without this protection will either A) brick your console if it's an N3DS, or B) remove A9LH if it's an O3DS.

perfect, thanks for the reply.

i shall be very careful with what CFW i am using then before booting into sysNAND..thanks my dude.

Edit: Aurei is my main now obviously, and to my knowledge and reading, it does protect your firms.. thingie.. sorry i am noobish yiiis.
but i did not quite understand the "since updating without this protection" < that , by updating what exactly .. XD

and lets say GW drops support for 10.3 sysNAND tomorrow, and i update my sysNAND will my Aurei emuNAND still boot fine ? but then Aurei has to give support to 10.3 sys nay?

like from firm90 to firm10.x? x_x

 

[WiiUBricker]

Just a quick emergency question because I'm dumb: What buttons do I need to press on boot to get to the config menu?

 

[fr3quency]

Select~

 

[stl25]

oops wrong thread

 

[fr3quency]

 

[driverdis]

Just a quick emergency question because I'm dumb: What buttons do I need to press on boot to get to the config menu?

Select

 

[Yami Anubis ZX]

true, i also know that NAND is a sensitive subject..

thus i am always very cautious always whenever i use FBI LOL... i always check if im installing the cia into NAND or SD.

but my main cia installer is SOON/BBM.



perfect, thanks for the reply.

i shall be very careful with what CFW i am using then before booting into sysNAND..thanks my dude.

Edit: Aurei is my main now obviously, and to my knowledge and reading, it does protect your firms.. thingie.. sorry i am noobish yiiis.
but i did not quite understand the "since updating without this protection" < that , by updating what exactly .. XD

and lets say GW drops support for 10.3 sysNAND tomorrow, and i update my sysNAND will my Aurei emuNAND still boot fine ? but then Aurei has to give support to 10.3 sys nay?

like from firm90 to firm10.x? x_x

Actually I had A9LH installed on my new 3dsxl and I still bricked it, you can brick it by using the safe A9LH installer stage 2 with any of the forks, so make sure you use full install and not stage 2, even if you have the correct fork.

Another reason why I used it was due to the fact that none of the button things would work like Decrypt 9, emunand9 and Uncart, so I thought running safeA9LH installer would fix it. I also did not know there were different forks as I already had A9LH already installed and thought I was safe from bricks.

 

[driverdis]

Actually I had A9LH installed on my new 3dsxl and I still bricked it, you can brick it by using the safe A9LH installer stage 2 with any of the forks, so make sure you use full install and not stage 2, even if you have the correct fork.

Another reason why I used it was due to the fact that none of the button things would work like Decrypt 9, emunand9 and Uncart, so I thought running safeA9LH installer would fix it. I also did not know there were different forks as I already had A9LH already installed and thought I was safe from bricks.

why would you use stage2 when full install does not take any time at all over stage2?

 

[Yami Anubis ZX]

why would you use stage2 when full install does not take any time at all over stage2?

Because I didn't know where to find all the files.

 

[fr3quency]

I just made my life easier x100 xD (and I don't know why I hadn't thought of that before, as I have pinned some buttons there... wtf brain)

I want to cry from happiness. ;_;

 

[BooBooBear]

SecureInfo_C is your private SecureInfo_A from SysNAND modified accordingly of what your destination region you want. I don't have a tutorial on hand sadly but I think all necessary informations are on GBATemp.

I checked my secureinfo_a, and it has the right region value (1 for US). Is there anything else I could try?

 

[driverdis]

Spoiler

Well, why not? it's free space after all

 

[Svaethier]

I checked my secureinfo_a, and it has the right region value (1 for US). Is there anything else I could try?

If you're getting a '007' error then you'll have to wait for a fix

 

[driverdis]

If you're getting a '007' error then you'll have to wait for a fix

 

[BooBooBear]

If you're getting a '007' error then you'll have to wait for a fix

I am also getting error 005-5958. I am able to link my NNID and access miiverse.

 

[Svaethier]

I am also getting error 005-5958. I am able to link my NNID and access miiverse.

I can make an nnid if I updated from 9.2 but I don't want to do that right now so I'm not getting that error.

 

[BooBooBear]

I can make an nnid if I updated from 9.2 but I don't want to do that right now so I'm not getting that error.

So should I use a preexisting NNID then?

 

[Svaethier]

So should I use a preexisting NNID then?

You can try that