Team-Xecuter has been quiet since v6.0.0 officially rolled out for the Nintendo Switch last week, but they are back with this time an amazing revolutionary update to their SX OS

And you may ask why is it 'revolutionary', well because for first time a CFW for the Switch contains 'EmuNAND', just like back in the days of the 3DS scene, so check out their official PR announcement below:

Hello friends! Team Xecuter is happy to bring you the official 2.0 release of your beloved SX OS.

A lot has happened since the initial release of SX OS a few months ago. This is far from a simple proof of concept custom firmware anymore. With this major update we bring some exciting new functionality to the table. We suggest you grab a beverage of your choice and read on to learn more!

• EmuNAND

Lets start with the major new feature in 2.0: EmuNAND.

Those who have a background in the Nintendo 3DS hacking scene know what this is, but let's quickly elaborate for those of you who are new to the game:

The Switch uses a NAND Flash storage chip to store all of the system software, as well as your save games and other assets. With EmuNAND we create a shadow copy of this storage from which you can run SX OS. The benefits from doing this are that you keep your SX OS "world" separated from your original firmware. This also means you can keep your switch on an older firmware, while running the latest and greatest firmware inside of your EmuNAND. As we all know, older is better.. when it comes to defeating system security at least. And newer is better when it comes to enjoying the latest content!

Another upside of consolidating your SX OS usage from your original firmware usage is vastly reducing the risk of a network ban. You can run SX OS in EmuNAND, of course with our Stealth Mode enabled, and anything that is littered on the EmuNAND's filesystem is not visible to the switch in Original Firmware mode.

One thing to note is that SX OS EmuNAND works a bit differently compared to what some of you might think of as "traditional" EmuNAND where the entire NAND is copied to a separate partition on the MicroSD card. With SX OS EmuNAND your EmuNAND partition lives inside of your regular NAND. The primary reason for this is that occupying 32GB of a MicroSD card is a bit wasteful. The secondary reason is by utilizing the existing flash storage we can guarantee performance and reliability.

You can set up EmuNAND by booting into the SX OS boot menu (hold Volume + during boot) and going into the revamped "Options" menu. There you will find a section called EmuNAND which will guide you through the setup. By default SX OS will allocate 15GB for your EmuNAND partition. If you want to use a different size hit the "advanced" button before creating your EmuNAND.

SX OS will boot into EmuNAND by default if it finds a valid EmuNAND partition. If you don't want to boot into EmuNAND, there's a button in the SX OS Boot menu which will allow you to continue booting with EmuNAND disabled.

• NAND Dumping, Restoring, GPT Repair

As mentioned in the previous section we have revamped our SX OS boot menu's option screen quite a bit. For the tinkerers and advanced users we introduced an easy method of dumping/restoring your NAND flash storage. Another neat addition for people who had an unhappy accident while playing with their NAND is the "GPT Repair" option. This will repair your NAND's partition table if you ever need to. Again, this functionality is for advanced users who know what they're doing only. Please be cautious when using this functionality.

• LayeredFS working on 6.0

With our (early) support for 6.0 we introduced a regression where "LayeredFS" would no longer work. This has been corrected and you can now enjoy your game modifications/hacks again on the latest official firmware.

• Homebrew NSP Compatibility

We got word that the community has started distributing homebrew titles as NSP files recently. These NSP files cut some corners in the way they are crafted, but we decided to introduce support to make them usable with SX OS anyway. So you can now enjoy your favorite homebrew titles that comes as installable NSP files and launch them directly from the home screen!

• Closing Words

Whew, we're sorry for the wall of text. We tried to keep things as concise and easy to understand as possible. SX OS 2.0 is a big and important update, but certainly won't be the last. We know you're all waiting for even more functionality that is in high demand. Rest assured, we work as fast as we can to scrap these items off of the bucket list and bring them to you, the loyal end user, as fast as we can!

Enough chit-chat, you can update to SX OS 2.0 right *now* by using the built-in updater if you are running SX OS 1.9 or higher. Otherwise head to our website and grab a copy! Enjoy!

--< Team-Xecuter - Rocking the Switch in 2018 and beyond! >--​

Source: MaxConsole

 

[xabier]

So um... just to clarify: don't fucking use SX OS, especially this update. It doesn't reduce chances of a network ban, it practically guarantees it. Telemetry logs NAND size, and all this "emuNAND"* (its just a resized and then dual booted sysNAND) does is repartition the NAND. This will result in your switch reporting a different NAND size, which is like, super fucking easy for Nintendo to spot.

I can already imagine this becoming a pain for users that think TX handed them the "holy grail of CFW". They didn't. They handed you a wooden cup covered in wet gold paint.

Also: quoting posts by devs on discord is a valid practice. Don't really see why some people have an issue with it, but probably worth stating. Those devs know their shit, discrediting them because of their communication platform of choice is just silly.

*An emuNAND stands for "emulated NAND". This is not an emulated NAND.

Nand size cant be changed, its a physicall feature. Does nintendo's telemetry check nand size or nand partition size?

 

[hippy dave]

This update has broken some of my games; like The Messenger gives a black screen and error message now and closes back to dash. Same for Danger Mouse
I tried reinstalling them but still doesn't work.

2.0 uses an outdated layeredfs which breaks these games, hopefully they'll update it for 2.1 but in the meantime use 1.9

 

[Dan-the-Rebirth]

The simplest way would be to create a emunand now with all stuff installed and then restor the old backup befor i used sx osright?

Edit: Nevermind if the info about resized sysnand is true that wont work

 

[RY0M43CH1Z3N]

The 20 minutes of EmunNAND is 2 hours...

 

[Ev1l0rd]

Nand size cant be changed, its a physicall feature. Does nintendo's telemetry check nand size or nand partition size?

The latter. Apologies, it was slightly misphrased on my part.

 

[loler55]

80 minutes

The 20 minutes of EmunNAND is 2 hours...

 

[Purple_Shyguy]

It doesn't reduce chances of a network ban, it practically guarantees it. Telemetry logs NAND size, and all this "emuNAND"* (its just a resized and then dual booted sysNAND) does is repartition the NAND. This will result in your switch reporting a different NAND size, which is like, super fucking easy for Nintendo to spot
.

Proof?

 

[NeoSlyde]

i'm already banned, i can update to 2.0 fine?
just did update to 6.0.0 thanks to @rajkosto 's choidujournx

 

[V-Temp]

The latter. Apologies, it was slightly misphrased on my part.

It actually has checks for both. There's a report on chipsize which is direct info from the NAND chip itself. The other is USER, this is the partition for user data. The Switch actually only ever shows the former, because if you change the chip it will resize to the new size of the chip. But if you split it, it will still only show the size of the chip and if you use this SX OS split it will still tell you you have a 32GB chip.

However, the telemetry on USER will be fucked up.

Also, the other issue is that Horizon will potentially try to install past 16GBs because its looking at available space vs. NAND chip size. I have no idea what would happen if Horizon or SX's clone tried to install past 16GB but it can't be pretty. Probably a non-negligible chance of corrupting whatever is on the other half.

 

[RY0M43CH1Z3N]

i'm already banned, i can update to 2.0 fine?
just did update to 6.0.0 thanks to @rajkosto 's choidujournx

Yes, i'm banned too and i can update from switch (for 1.9 version)

 

[snails1221]

make a tutorial

http://pascoe.pw/2018/09/switchnand.html

 

[Ev1l0rd]

Proof?

On what specifically?

TX outright states that they install it to your actual NAND chip instead of the SD card.

NAND size being part of telemetry can be seen if you analyze the send traffic w/ something like wireshark.

It actually has checks for both. There's a report on chipsize which is direct info from the NAND chip itself. The other is USER, this is the partition for user data. The Switch actually only ever shows the former, because if you change the chip it will resize to the new size of the chip. But if you split it, it will still only show the size of the chip and if you use this SX OS split it will still tell you you have a 32GB chip.

However, the telemetry on USER will be fucked up.

Also, the other issue is that Horizon will potentially try to install past 16GBs because its looking at available space vs. NAND chip size. I have no idea what would happen if Horizon or SX's clone tried to install past 16GB but it can't be pretty. Probably a non-negligible chance of corrupting whatever is on the other half.

Ah thanks, I just knew the relevant NAND size (the one that fucks over SX OS users rn) was reported to Nintendo.

 

[Solid924]

Xenoblade Cronicles 2 also crashs after updating to 2.0 lol.

 

[Purple_Shyguy]

On what specifically?

TX outright states that they install it to your actual NAND chip instead of the SD card.

NAND size being part of telemetry can be seen if you analyze the send traffic w/ something like wireshark.


Ah thanks, I just knew the relevant NAND size (the one that fucks over SX OS users rn) was reported to Nintendo.

Proof you will get banned. All im seeing from this thread is conjecture, assumption and fearmongering. Mostly from people who don't own or even use TX OS

 

[DKB]

Revolutionary my ass. More like revolutionary in mental retardation if you update to this.

 

[aerios169]

So to summarize, 2.0 isnt safe because nity can detect the size of the nand, in other words is waste of space of your nand and a big red flag. The only option that can save us is make the nand bigger, then give the original nand the correct space that was inccluded in the console, the rest of space to the “emunand”. The problem is that for the end user this is almost imposible because is a bit tedius, also you need a new chip for your nand or somthing like that

 

[V-Temp]

Ah thanks, I just knew the relevant NAND size (the one that fucks over SX OS users rn) was reported to Nintendo.

That's USER.

NandTotalSize is the chip's actual size.

 

[Ev1l0rd]

Proof you will get banned. All im seeing from this thread is conjecture, assumption and fearmongering. Mostly from people who don't own or even use TX OS

Nintendo has been provably agressive with banning users that have strange/incorrect telemetry reports. I'll just point to the entire SX OS ban thread you can find on this very site as evidence for that.

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

That's USER.

NandTotalSize is the chip's actual size.

I get you, but for your average user, they wont get the difference between USER and the actual NAND, so saying it's the NAND size being fucked will probably be the most accurate definition for your average user without going into what USER is.

 

[Purple_Shyguy]

Nintendo has been provably agressive with banning users that have strange/incorrect telemetry reports. I'll just point to the entire SX OS ban thread you can find on this very site as evidence for that.

So your proof that installing shit on this emunand will get you banned is that "people have been like banned before and stuff".

Lol ok. Those people were banned because they didn't have a feature like THIS in the first place.

 

[xIce101x]

This update is a mess lol