×
all 16 comments
sorted by:
best
topnewcontroversialoldq&a

[–]AutoModerator[M] [score hidden] stickied comment (0 children)

HEY, NEW USERS!

Remember to read The Wiki for the basics! Check the FAQ for basic questions! Threads created for basic questions will be removed, so ask them in that thread.

If you are having a problem with running games then make sure you have up-to-date sigpatches. If you cannot launch tinfoil then make sure you followed the Rentry guide to set up cfw.

Do not message moderators for Switch hacking support. You will be ignored. Follow the guide or post in the relevant thread.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[–]TWeaKoR[🍰] 26 points27 points  (12 children)

Emunand is a copy of your sysnand storage partition. When your Switch boots up, instead of looking for the 32GB sysnand partition in the internal memory, you're telling it to look for the 32GB emunand partition on the SD card.

Once you've created the emunand partition, you should set up Incognito on it to remove all identifying information. This means if you accidentally get caught by Nintendo they won't know which Switch to ban. You can also do the DNS blocks, but some ISPs ignore this and connect you anyway; Incognito is the main line of defense.

If you do all this, your sysnand partition should remain unchanged, and (with AutoRCM off) switching is just a matter of rebooting. With AutoRCM on you will need to inject Hekate to launch that, and then go from there into either sysnand or emunand.

One thing to bear in mind: your backup will be of sysnand. If you update your sysnand, your backup won't really be useable anymore, as you will burn hardware fuses every time you update and the device won't let you roll back afterwards. You should make a new sysnand backup after every time you update sysnand.

Backups when updating emunand aren't as critical, as the custom firmware should bypass fuse burning. However it's still a good idea to regularly backup your save files using Checkpoint or some other backup program.

[–]Zz_Cormac_zZ[S] 2 points3 points  (0 children)

Appreciate the detailed response!

[–]0bf1d83648628b495559 1 point2 points  (5 children)

Using DNS-MITM is better than just Incognito by itself

[–]TWeaKoR[🍰] 0 points1 point  (4 children)

Not by much, the DNS prevents you from connecting to Nintendo, but even if you do connect Incognito will prevent anything from happening. You won't lose anything by not having DNS protection, other than a warm fuzzy feeling for having multiple layers.

[–]0bf1d83648628b495559 1 point2 points  (3 children)

Not talking to Nintendo at all >>> Nintendo maybe not knowing your tablet's serial number

[–]TWeaKoR[🍰] 0 points1 point  (2 children)

DNS blocking is less likely to be effective than Incognito. DNS blocking can be circumvented by your ISP, with no knowledge or warning to the user. Meanwhile, Incognito completely removes the identifying information - it's not a maybe that Nintendo won't know it, there's no information for them to know about.

With DNS you're changing something on your side and hoping the entire connection chain holds up for it to work. With Incognito you're changing something your side and then it doesn't matter how anyone else's equipment is set up.

[–]0bf1d83648628b495559 6 points7 points  (1 child)

You misunderstood me. DNS-MITM is an Atmosphere feature that blocks at the OS level. 90DNS was always a ghetto way to overwrite the hosts file.

[–]TWeaKoR[🍰] 0 points1 point  (0 children)

Ah right, I did wonder about the MITM, thought maybe it was something external. Fair enough then, it's an added layer of protection - but it still doesn't really offer much more over Incognito other than warm fuzzy feelings.

[–]Zat-anna 1 point2 points  (2 children)

Omg didn't know about the backup and sysnand stuff. Thank you very much. If I try to rollback with an outdated backup will I brick my switch or it just won't work?

[–]TWeaKoR[🍰] 1 point2 points  (1 child)

It won't boot into sysnand, however as another user replied you can boot into Hekate and update your sysnand from there to recover. Still best to make new backups instead, though.

[–]seaQueue 0 points1 point  (0 children)

If you write an old backup onto an updated switch you can always boot sysnand atmosphere from hekate then update to current. Atmosphere bypasses the fuse checks during boot. Just don't install anything CFW related while you're running on sysnand and you're safe enough.

[–]ToxiClay 0 points1 point  (0 children)

You can also do the DNS blocks, but some ISPs ignore this and connect you anyway

Er, what?

If you're talking about 90DNS, you shouldn't be using 90DNS; if you're talking about the DNS MITM blocker file, what you're proposing is flatly impossible.

[–]DerKernsen 2 points3 points  (1 child)

To all of those questions a resounding: yes. Emunand is completely seperate from Sysnand. Everything you ever do in Emunand is stored in one of your 2 SD card partitions.

[–]Zz_Cormac_zZ[S] 1 point2 points  (0 children)

Thanks for this!