Hacking Question If i wanted to create an emunand

[jacopastorius]

If i wanted to create emunand, what should I do?

Restore the clean nand and then create the emunand of that clean? In that way i can go online with the clean nand. Is it correct?

 

[stick267]

If you plan to keep the emunand offline then there's no reason to make it clean.

 

[aos10]

If you plan to keep the emunand offline then there's no reason to make it clean.

he meant keep the original NAND for online play and keep it clean, not the emunand.

 

[stick267]

he meant keep the original NAND for online play and keep it clean, not the emunand.

I must've misread then.. In any case, he can restore his clean NAND in order to use sysnand online, but he doesn't have to do it before creating the emunand.

 

[CanIHazWarez]

It would be easiest to create emunand first. That way, you don't have to backup any saves. Then do a NAND restore on your sysnand. Your emunand will continue to appear as your system was and the sysnand will appear as it did at the time of backing it up.

 

[LapCheong]

I think you should always restore your clean lowest nand. The one your switch comes with originally. So you don't have to worry about autorcm and burning your fuses. Then wait for a exploit for that version of yours while you update your emunand to play latest games

 

[pLaYeR^^]

You don’t have to restore the clean NAND backup before creating EmuNAND. You will only use EmuNAND for offline CFW purpose. After you have created EmuNAND, you can simply restore your clean NAND backup with hekate. Now your SysNAND is clean and you can use it for online things while you use EmuNAND for CFW.

 

[gizmomelb]

as has been said a couplke of times.. use SX OS and create emuNAND - it will make an exact copy of your CURRENT NAND - saves games, settings, everything (just uninstall any themes you have as they may not work with SX OS 2.7.1, if your current firmware is 8.0.1!)

then if you want to go online you need to restore the very first NAND backup you made.. which may not work if say your original NAND backup was firmware 4.something and you have upgraded to firmware 7.0.1 (the fuse counts will be different and not work).

You can only DOWNGRADE to the lowest firmware which supports the number of fuses you've burned.

If you have NEVER upgraded your firmware then restore the NAND backup and it will overwrite all logfiles which may cause you to be banned.

If you cannot go back to the first NAND backup then there is no guarantee your switch will not be banned when you go online, due to system logs containign details of NSPs etc you have installed.

 

[CanIHazWarez]

Good reply, but I wanted to add a few things for OP or lurkers.

then if you want to go online you need to restore the very first NAND backup you made.. which may not work if say your original NAND backup was firmware 4.something and you have upgraded to firmware 7.0.1 (the fuse counts will be different and not work).

As long as you're not using the official bootloader, fuses don't matter. The SX bootloader won't burn fuses, but it also doesn't check fuses. You can have too many fuses burnt and it won't matter as long as you're using autoRCM, which you probably should be using anyway. The only issue might be if your SD card is exFat and the NAND image you're restoring doesn't have exFat support. Then you'll have to use a Fat32 formatted card to run ChoidujourNX and get exFat support before switching back to your exFat card.

If you have NEVER upgraded your firmware then restore the NAND backup and it will overwrite all logfiles which may cause you to be banned.

This would only be the case if you've gone online after you did your NAND backup. If you haven't gone online since then, Nintendo would have no way of knowing that your logs don't match your actual activity.
Even if you have gone online, I'm not sure how great of a risk of being banned that would pose. It might just be theoretical. You could check the sticky about bans to maybe see if it's actually happened or someone else can chime in if they're aware of it.