Hacking SX-OS emuNAND, what whould i do with my sysNAND?

[Phenj]

So that's the thing, i've just created a full and clean emuNAND for my Switch using SX-OS 2.0.
I was thinking to use my emuNAND for suspicious stuff, like installing .nsp and using homebrews, and use my sysNAND for online gaming and so on.
However i've got some doubts... Can i update my sysNAND and keep my emuNAND (Always offline) on 5.1?
I don't really care about future exploits/coldboot, i'm just concerned about not getting a ban.
Thank you!

 

[jajamundo]

Thats the point of having the emunand. Use emu tu all the hack stuff and use your sysnand for your online and original games. But this doesnt mean you are 100% safe of being banned.

 

[Phenj]

Thats the point of having the emunand. Use emu tu all the hack stuff and use your sysnand for your online and original games. But this doesnt mean you are 100% safe of being banned.

Yes indeed, i'm just trying to stay as safe as possible. So i can update my sysNAND without any problem?

 

[Kioku]

The Switch is so damn weird. I'd assume like the 3ds, you'd want OFW on the lowest possible FW. Whereas Emunand would be updated. So, I'd say emunand would be for your legitimate titles and online. Whereas your sysnand would be offline with homebrew and piracy.

 

[jajamundo]

Yes indeed, i'm just trying to stay as safe as possible. So i can update my sysNAND without any problem?

I really dont know how exactly works. If you dont care to burn fuse, first update your switch to 6.0, then create emunand. I think you can unlink emunand and sysnand with just formatting sysnand (OFW)

 

[Phenj]

I really dont know how exactly works. If you dont care to burn fuse, first update your switch to 6.0, then create emunand. I think you can unlink emunand and sysnand with just formatting sysnand (OFW)

I already created my emuNAND, and i don't think unlinking NANDs is still a problem. I mean, looks like my SYS and EMU are perfectly separated anyway

--------------------- MERGED ---------------------------

The Switch is so damn weird. I'd assume like the 3ds, you'd want OFW on the lowest possible FW. Whereas Emunand would be updated. So, I'd say emunand would be for your legitimate titles and online. Whereas your sysnand would be offline with homebrew and piracy.

According to this thread: https://gbatemp.net/threads/how-does-sx-os-emunand-work.518936/
sysNAND is safer than emuNAND for onlines tuff

 

[jajamundo]

I already created my emuNAND, and i don't think unlinking NANDs is still a problem. I mean, looks like my SYS and EMU are perfectly separated anyway

Some users has report that got semi brick while updating their emunands to a higher firmware. Always make a Nand backup first and go ahead

 

[Phenj]

Some users has report that got semi brick while updating their emunands to a higher firmware. Always make a Nand backup first and go ahead

I see. I wanna update my sysNAND though.

 

[DocBo]

I have created a COPY of my sysNAND with SXOS 2.0, so can i update/downgrade the COPY of the sysNAND without touching the sysNAND?!

 

[TheCyberQuake]

Isn't it well known that the emuNAND setup from SX os is extremely detectable? I would say it's less safe in the long term, because telemetry already includes info on nand partitions and their sizes so nintendo could easily flip a switch and ban everyone doing this. Safety should not be a reason to use SX OS emuNAND. Frankly for anyone really worried I would hold out until we get actual emuNAND, then keep hacks on emuNAND and clean sysNAND for OFW.

 

[Sticker]

don't use emmunand, my switch crash and my save game file (Doom and Resident Evil go away) The best way is waiting for next release of sx os

 

[lembi2001]

I was under the impression that SX OS EmuNand is not particularly safe to use as it created another partition on your SysNand.

 

[Phenj]

Isn't it well known that the emuNAND setup from SX os is extremely detectable? I would say it's less safe in the long term, because telemetry already includes info on nand partitions and their sizes so nintendo could easily flip a switch and ban everyone doing this. Safety should not be a reason to use SX OS emuNAND. Frankly for anyone really worried I would hold out until we get actual emuNAND, then keep hacks on emuNAND and clean sysNAND for OFW.

Wrong info. https://gbatemp.net/threads/how-does-sx-os-emunand-work.518936/

 

[Myron49485]

SX emunand can be used for (only one or the other):

1. Keeping your sysnand on a low fw, and using latest fw with emunand.
- No going online.
- No need autorcm to prevent burning of fuses since sysnand is on original fw. (You can boot to ofw without sending a payload, shut down normally from horizon, etc).

2. Going online with sysnand, staying offline with emunand.
- Not impossible for Nintendo to detect since emunand is stored in the user partition.

#1 is for those who want to preserve their fw for future exploits. #2 is for those who want to risk going online without a 100% chance of being banned.

Since you are concerned about not getting a ban/ don't care about future exploits, then SX emunand doesn't really have a use for you.

 

[jajamundo]

#1 is for those who want to preserve their fw for future exploits. #2 is for those who want to risk going online without a 100% chance of being banned.

Since you are concerned about not getting a ban/ don't care about future exploits, then SX emunand doesn't really have a use for you.

Not exactly. He just want to be safe when we talk about playing online

So the best option here is to update to 6.0.0 and start using Emunand. I don't reccommended it, because it install on the real nand and not on a SD card. I never heard of a ban using this method, so stop with all this bullshit!

He can do whatever he wants and if he doesnt care about burning fuses, just update OFW and then make a emuNand

 

[Myron49485]

Not exactly. He just want to be safe when we talk about playing online

So the best option here is to update to 6.0.0 and start using Emunand. I don't reccommended it, because it install on the real nand and not on a SD card. I never heard of a ban using this method, so stop with all this bullshit!

He can do whatever he wants and if he doesnt care about burning fuses, just update OFW and then make a emuNand

Using SX emunand isn't exactly "safe". Unless you flash a clean backup or get another console, there is currently no safe way to play online.

To me, it just sounds like OP doesn't want to get a ban, hence using SX emunand is not the best option. But if he wants to take the risk, he could always do #2.

Even though no one got banned yet, we can't say that Nintendo won't ban for it in the future. Besides, SX emunand is relatively new.

 

[Phenj]

I'm pretty sure using nx-dreport makes your NAND almost perfectly safe. I've been doing this for MONTHS, and still no ban yet, at all.
And according to json's thread, the sysNAND is perfectly safe.

So from what we can conclude so far: OFW mode is actually perfectly safe. Nintendo would need to actively start detecting the EMUNAND0 magic in boot1 or start to detect the new files, which would be hilarious if they would start to do so. This detectable point is actually moot, because with EmuNAND stored on the microSD, Nintendo would be able to detect it too if they actively start to do so.

Soo i guess i'll update my sysNAND and use online with it, and keep my emuNAND always off for hacking stuff.

 

[FahQ]

don't use emmunand, my switch crash and my save game file (Doom and Resident Evil go away) The best way is waiting for next release of sx os

That sucks. You should always make backups. Use Checkpoint. It's fantastic.

 

[PT333]

Straightforward summary:
1. Backup your NAND and saves before creating emuNAND
2. You should use sysNAND for legit stuff and emuNAND for hacking, because in emuNAND your Switch will send bad NAND total size info in telemetry and that will very probably result in a ban

 

[DiscostewSM]

I'm pretty sure using nx-dreport makes your NAND almost perfectly safe. I've been doing this for MONTHS, and still no ban yet, at all.
And according to json's thread, the sysNAND is perfectly safe.

Soo i guess i'll update my sysNAND and use online with it, and keep my emuNAND always off for hacking stuff.

I've been holding off on updating my SysNAND simply because of some opportunity that could come to allow EmuNAND or some other solution to be used in a way for legit stuff and online along side homebrew and non-legit stuff, keeping my SysNAND at 5.1 for future exploitation, but I fear that my want to get access to online and future games requiring 6.0+ will drive me to abort my plan, to which I'd update SysNAND, then create an EmuNAND from that. Heck, I've been offline since prior to 6.0, having touched some homebrew through SX OS CFW on SysNAND, so it's possible that I may already be banned, but I won't know until I try updating. They can't patch out RCM, so that will always be an avenue for me with my current system. I wish I could just be able to "switch" between SysNAND and EmuNAND without having to undock my system to hook in the SX Pro or connect my Switch to a PC/smartphone.