Hacking Who hasn't yet installed arm9loaderhax? Why?

[owek1]

when i hacked my N3DS i followed the older guide where you downgrade to 2.1 and risk bricking if you accidentaly put it to sleep, in other words the non-otpless method..lucky for those who are into 9.2 N3DS now where you could follow the guide and have it set up in less than an hour.. there is really no safe method as the risk of bricking is still there even with the newer guide..i think you just brick your device faster this time around if you are not careful..im not saying this to discourage anyone but my point is i understand why some members here are hesitant to switch from their current setup..luck also has a huge factor here as many followed the guide and still brick..

 

[SonicCloud]

there is really no safe method as the risk of bricking is still there even with the newer guide

True , everytime you modify something on NAND a brick can happen








but still 2.1 downgrade bricks could be user fault and otpless way is random brick

 

[Arkansaw]

Not unnecessary. Never saw any of these "accidentally updated sysNAND" for example?

Also, you seem to think that a9lh means that you need to live your life on sysNAND.
This is not true.
You can perfectly keep living your life on an emuNAND, keeping your sysNAND on 9.2 but have the 100% boot rate + 0 second boot time given by a9lh.

You still don't get it. As long as a9lh is in place the sysnand has been tampered with. If mset/homemenu breaks, there is still stock. If a9lh breaks usually stock will be broken too so other entry points will not work. Now hardmod is needed to fix a9lh brick

 

[Hayleia]

You still don't get it. As long as a9lh is in place the sysnand has been tampered with. If mset/homemenu breaks, there is still stock. If a9lh breaks usually stock will be broken too so other entry points will not work. Now hardmod is needed to fix a9lh brick

But a9lh doesn't break. I mean, sure, installation can fail (not saying the chances are high or low, no one cares, installation can always fail due to user error or weather conditions or whatever), and your argument is perfectly valid there since even if menuhax's installation failed, just remove files on your SD card and stock still works. But once installed, a9lh never fails, it's just code execution that doesn't even rely on random events like menuhax (which doesn't have a 100% bootrate for this reason).

 

[Decorations]

It's honestly stupid easy if you have sysnand 9.2 I helped three people already in one day and they all got a9lh less then 30 mins if you like and wanna put the work in just dm me

 

[owek1]

It's honestly stupid easy if you have sysnand 9.2 I helped three people already in one day and they all got a9lh less then 30 mins if you like and wanna put the work in just dm me

brick rates on installation aside, i agree it is extremely easy and not that time consuming anymore to setup a 9.2 N3DS to a9lh.. it is just a matter of being really determined to have a9lh or not.. it's a do or die situation once you decide to install it.. but once you are done, it's totally worth it..

 

[Arkansaw]

But a9lh doesn't break. I mean, sure, installation can fail (not saying the chances are high or low, no one cares, installation can always fail due to user error or weather conditions or whatever), and your argument is perfectly valid there since even if menuhax's installation failed, just remove files on your SD card and stock still works. But once installed, a9lh never fails, it's just code execution that doesn't even rely on random events like menuhax (which doesn't have a 100% bootrate for this reason).

a9lh can be broken by the same way used to put it in place, which means any tampering with sysnand, including normal system updates, cfw bugs and incompatible a9lh payloads/updates. Unless sysnand will never be touched again, the risk is always present as long as a9lh is in use.

 

[Hayleia]

a9lh can be broken by the same way used to put it in place, which means any tampering with sysnand, including normal system updates, cfw bugs and incompatible a9lh payloads/updates. Unless sysnand will never be touched again, the risk is always present as long as a9lh is in use.

If your CFW isn't from 2011, system updates can't touch a9lh due to firm protections. Then yeah, nothing prevents people from booting GodMode9 and wiping stuff, but you can't use that argument since you say you always avoid tampering with sysNAND (and nothing prevents anyone from doing this kind of stupid stuff with menuhax too).

 

[Arkansaw]

If your CFW isn't from 2011, system updates can't touch a9lh due to firm protections. Then yeah, nothing prevents people from booting GodMode9 and wiping stuff, but you can't use that argument since you say you always avoid tampering with sysNAND (and nothing prevents anyone from doing this kind of stupid stuff with menuhax too).

and the firm protection comes from cfw (which is a risk by itself). As long as the stock firmware is exploitable, a9lh is an additional risk since it replaces stock and becomes a dependency for other entry points to remain usable

 

[Hayleia]

and the firm protection comes from cfw (which is a risk by itself). As long as the stock firmware is exploitable, a9lh is an additional risk since it replaces stock and becomes a dependency for other entry points to remain usable

Yes, but since you used "Nintendo updates" as an argument to potentially "break" a9lh on a potentially bad CFW, I have to use it too as an argument to "break" your exploitable firmware on sysNAND. So where is the additional risk when the first thing that boots is something you control rather than an environment closed on purpose by the ones who don't like you tampering?

 

[bytar]

emunand is safe. forget about %95 bootrate and waiting 5 seconds. i don't blame who takes the risk though.

 

[Hayleia]

emunand is safe. forget about %95 bootrate and waiting 5 seconds. i don't blame who takes the risk though.

a9lh can be broken by the same way used to put it in place, which means any tampering with sysnand, including normal system updates, cfw bugs and incompatible a9lh payloads/updates. Unless sysnand will never be touched again, the risk is always present as long as a9lh is in use.

Sorry, got brought back to this topic by the above post
But once again, you can perfectly use a9lh as a way to boot to an emuNAND and then even with a CFW from 2011, even normal system updates don't touch your sysNAND and you fall in the "sysnand will never be touched again" category in fact.

 

[phazonknight]

I haven't installed it, mostly cause I don't know what it is and I have gateway that works just fine for all my needs and my motto don't fix if it ain't broke lol

 

[Jeph]

Well,

Guess I had to change my vote. Just Hardmodded my 4 2ds's. Guess I'm part of that master race!

 

[Patodox]

2 ols 3dsxl sucessfully installed a9lh, 1 new 3dsxl bricked permanently

 

[Janina]

Can someone link me working links of aeskeydb.bin file input and FBI injectable the ones on the guide don't seem to be working for me.

 

[Osmosis]

I don't know if anyone has seen the gorgeous new Plailect Guide site... I almost cried. Makes life so much easier.

Can someone link me working links of aeskeydb.bin file input and FBI injectable the ones on the guide don't seem to be working for me.

https://3ds.guide/

You might need a simple torrent downloader like Transmission-QT.

 

[m37r01d]

really nobody should be afraid, everytime i do another 3ds, it process gets easier and easier, but also quicker and quicker

 

[SoarSpeed]

It was too easy for me on my 2DS when it was back at stock 6.0 after I purchased it. Fully hackable, followed the guide and sucessfully installed A9LH and Luma3DS CFW.

 

[DesuIsSparta]

I haven't installed A9LH yet because I feel like i'm going to screw it up.. I believe the only way that I could brick my console is if I use/delete(?) the incorrect region file at that one step..

I also don't really understand the benefits, even though I know there are some.

Edit: I've since installed it, and it's great.