- Joined
- Sep 9, 2016
- Messages
- 1,930
- Reaction score
- 1,336
- Trophies
- 0
- Location
- The C: drive
- XP
- 1,656
- Country

>try before they buyExplain to me how mcu rebooting with sig patches and installing pokemon can brick your nand?
Everything is done as live patches in RAM.
Completely overwriting your new 3ds nand with old3ds firm 2.1 derived from someone else's system. What could go wrong.
Maybe you should consult @vb_encryption_vb and maybe he can better testify on the real risk of a9lh. Last I check, business was very good for him. Before you shout, "But, user error!", please note that not everybody has the same amount of computer literacy, and going through the plailect guide and it's dozens of steps is an accident waiting to happen for some people.
I'm not saying a9lh should be avoided - certainly not. I have it on several systems and love it. But for someone with a single system they can't afford to lose, I can see LCFW as a temporary way for a user to "try before they buy" and see if cfw is worth the risk for what they're getting in return.
>LCFW has no way to recover if something goes wrong
>risk
kek
The fact remains, all CFW, be it a9lh or LCFW, has risks. However, a9lh has a backup plan where you can load a nand backup and/or a CTRTransfer in order to "save" a device, but LCFW has none.









