- Joined
- Feb 26, 2017
- Messages
- 4,046
- Trophies
- 2
- Age
- 20
- Location
- Hollister, CA
- Website
- dionicio3.com
- XP
- 7,224
- Country
Before I even start this thread, I'm aware that talking about anything that heavily deviates from 3ds.hacks.guide will attract some rather unsavory opinions. I'm not asking why using either emuNAND or sysNAND is better, or which CFW is superior, I just wanna ask two main questions.
- What is your reasoning for continuing to stick with an emuNAND solution rather that using CFW on sysNAND?
- How is your sys/emuNAND setup configured?
- "It allows me to keep sysNAND on an exploitable firmware and have emuNAND on the latest to play the latest games & play online." Nowadays, the entry point for CFW is firmware independent, with all firmwares being exploitable anyways.
- "It helps prevent hard bricks." Hard bricks aren't really possible anymore due to ntrboot, the only way I can think of is messing with the MCU, which an emuNAND wouldn't protect against anyways.
- "It makes making NAND backups easier (simply insert SD into PC to backup)." While this is true, most users, even advanced users, won't be doing anything that directly touches critical parts of the NAND (in fact the only thing I can think of that the average user does that touches the NAND is installing .cias, but that's not necessary a "critical" part unless you're directly overriding system titles, which most users won't). Additionally, most users only need a single backup, from when they initially installed CFW.
- "It allows me to safely run a custom version of [insert sysmodule/system title here]." Correct me if I'm wrong, but nowadays Luma3DS allows for this via LayeredFS and the "Enable loading external FIRMs" option.
- "It works already, why change how I run things?" This is honestly the only legitimate reason I can think of that still applies today. I understand not wanting to change how things are done because they "just work."