So is there really a "need" to use this? I'm on SXOS 1.9 and don't really feel the need to move to 2.0 as I don't really understand the benefits of the emunand. All I do is boot into CFW when I wanna play XCI's and boot into OFW when I wanna play my games online. Is it best to just hold off for now? Or is the emunand an important feature that I don't get the point of since I'm a scrub?
Hacking How does SX OS Emunand work?
You've been known to not know anything about anything. Even if he's wrong, which he isn't, I still would believe him instead of you
Just so everyone knows, this doesn't matter if you go online, even in emunand and get banned, you will be banned on ofw, because it uses the same cert, which you cannot change.
- Joined
- Jun 24, 2007
- Messages
- 12,010
- Trophies
- 3
- Location
- In the Murderbox!
- Website
- www.twitch.tv
- XP
- 16,162
- Country
You'd think so... But there needed to be a few threads before anybody clarified HOW their process worked.
My point is you can do all your hack and just dont go online (as always) in emunand then do all your legit stuff in OFW.
Oh really because a lot of people seem to feel that emunand is either going to let them play online without ban, or it's going to unban them.
Not really, mostly kids that don't know what they're doing, just followed a YouTube video named "h4x switch" or something....
What about if you have 1 SD card for OFW and another for CFW? If emuNand would be stored on the SD card and you want to boot into OFW with no fear of being banned, you would just have to swap the SD cards, right?
You can be sure that Big N cannot see NSP on OFW but they can see the NAND size and ban-hammer because you used emuNAND
By what I’ve veen reading in this post, nothing changes in NAND partition not size, so Nintendo wouldn’t see anything obvious.You can be sure that Big N cannot see NSP on OFW but they can see the NAND size and ban-hammer because you used emuNAND
Well, we all hope so, but we cannot sure what BigN could see in their telemetry report
There are about 3 things they can see:
- The modification made to boot1
- An up to 15 GB file stored in the USER partition which is full of files that are not supposed to be in there such as PRODINFO, boot0/boot1, etc.
- Loading EmuNAND is going to create a mismatch in the NAND size which the Switch can document. It is unclear if TX is patching that or not
Similar threads
