D
Deleted-236924
Guest
OP
Hi, I wish to switch over to arm9loaderhax, but I want to keep running emunand and keep sysnand untouched on 9.2 (I wanna be as safe as possible.)
I've read plenty of things over the past few hours. Supposedly possible to get arm9loaderhax to have cfw coldboot from power on, being able to unbrick without hardmod, all that good stuff, and it was said that coldbooting emunand cfw was pretty much just as fast as booting sysnand cfw, which is great.
I want to just be able to update emunand and keep sysnand on 9.2; that way, if a future 3DS system update manages to break arm9loaderhax, well, I'm just running emunand anyway, so if something breaks, I revert to previous emunand firmware version until a fix is found or something. Sounds simple enough and safe enough to me, because I've read there could be multiple ways to break arm9loaderhax when updating sysnand, and it could possibly be broken by Nintendo at some point, so I don't really want to take any risks.
But the guides I was able to find are all about running sysnand cfw on coldboot, nothing about being able to just carry on running emunand. It's really unclear how I would have to proceed to just have arm9loaderhax boot an emunand cfw while completely ignoring sysnand (which would only be there for purposes of hosting arm9loaderhax and booting emunand automatically, so it'd never be seen again.)
How do? Halp pls
Several hours of reading and searching did not answer my questions.
I've read plenty of things over the past few hours. Supposedly possible to get arm9loaderhax to have cfw coldboot from power on, being able to unbrick without hardmod, all that good stuff, and it was said that coldbooting emunand cfw was pretty much just as fast as booting sysnand cfw, which is great.
I want to just be able to update emunand and keep sysnand on 9.2; that way, if a future 3DS system update manages to break arm9loaderhax, well, I'm just running emunand anyway, so if something breaks, I revert to previous emunand firmware version until a fix is found or something. Sounds simple enough and safe enough to me, because I've read there could be multiple ways to break arm9loaderhax when updating sysnand, and it could possibly be broken by Nintendo at some point, so I don't really want to take any risks.
But the guides I was able to find are all about running sysnand cfw on coldboot, nothing about being able to just carry on running emunand. It's really unclear how I would have to proceed to just have arm9loaderhax boot an emunand cfw while completely ignoring sysnand (which would only be there for purposes of hosting arm9loaderhax and booting emunand automatically, so it'd never be seen again.)
How do? Halp pls
Several hours of reading and searching did not answer my questions.