Mistyped title, what I am wondering is of course if OFW could be on emunand instead of sysnand! Sorry.
My switch got CFW before emunand was a thing. It's the hackable release version. As far as I know it has never been banned, and hasn't been online in ages.I have a clean NAND backup, but it is really, really old, probably running 2.0.1 or something similar. I have been thinking about getting the switch online again. I probably wouldn't play online much anyway, but to see if it works, and accessing the store would be nice as well.
Instead of creating an emunand for continued CFW, restoring the very old clean NAND, and then updating that, it seems easier to just create an emunand from the NAND backup, keep the sysnand dirty, and use emunand for OFW. I know this is not what the guides tell you to do if you are hacking a switch from scratch, but is there any reason not to do this? I wouuld think performance is slightly better on sysnand, and as CFW is what I'll be running primarily, it seems a good place to have the CFW.
My switch got CFW before emunand was a thing. It's the hackable release version. As far as I know it has never been banned, and hasn't been online in ages.I have a clean NAND backup, but it is really, really old, probably running 2.0.1 or something similar. I have been thinking about getting the switch online again. I probably wouldn't play online much anyway, but to see if it works, and accessing the store would be nice as well.
Instead of creating an emunand for continued CFW, restoring the very old clean NAND, and then updating that, it seems easier to just create an emunand from the NAND backup, keep the sysnand dirty, and use emunand for OFW. I know this is not what the guides tell you to do if you are hacking a switch from scratch, but is there any reason not to do this? I wouuld think performance is slightly better on sysnand, and as CFW is what I'll be running primarily, it seems a good place to have the CFW.
Last edited by Naguz,