And don't forget you'll be added to the list. @Queno138I'm not rich enough to afford multiple 3ds consoles and was also nervous about sacrificing my 3ds for improved CFW boot rate and time. I did however hate that I needed Internet to access rxtools cfw (as it was the only one that seemed to work for me) and having an extra partition on my SD so I decided to make the jump to arm9lh. I researched as much as I could and read through each section in the guide multiple times and it worked really well. The only time it went wrong was when I incorrectly used a game cart to update and messed up my system temporarily. So if you work through the guide at a snails pace and keep gbatemp close by for anything you're unsure about you will be ok.
If you are ok with where you are at with emunand + cfw then you don't HAVE to make the switch but know that arm9lh is far superior once installed and that the community will always favor arm9lh now because of that
Most bricks are user error.I didn't install AL9H because I'm extremely paranoid.
While I'm okay with downgrading a unit for the first time (because getting emunand+CFW, and all my normal downgrades have succeeded so far),
there are too many things that can go wrong with AL9H setup.
And no matter how many people may argue it is safer now,
even if I follow the guide to the letter, if some cosmic chance screws it up,
I'm the one that has to live with a $300 brick.
I've been considering, but the risk is too high, especially when I have a system that has a working CFW.
Slightly faster boot time (and considerably awesome boot rate) apparently doesn't outweigh the risks for me.
And you're actually MORE susceptible to bricks without A9LH because you can't start Decrypt9 on boot to restore a SysNAND backup. If you mess up your SysNAND there's no way to fix it without a hardmod unless you have A9LH.
Last edited by Margen67,