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

 

[SpaceJump]

USER size is reported. See my conversation with @V-Temp for evidence on that.

Can you go more into detail? USER size doesn't tell me anything. Really curious about what is reported and how to find out.

 

[Deleted User]

Yes please tell me the name of the telemetry parameter please.... Because there is no such telemetry parameter as "UserTotalSize" or "UserSize" or even remotely similar to that..

 

[Ev1l0rd]

Can you go more into detail? USER size doesn't tell me anything. Really curious about what is reported and how to find out.

USER = one of the switch's system partitions. Specifically, it's the partition that has your games, saves, screenshots, all that shit.

SX OS resizes USER to make room for their own USER partition, which also contains the relatively smaller other NAND partitions. This means the reported size for USER is inaccurate to what it should be.

As to what is reported: use wireshark and analyze send traffic.

 

[Deleted User]

Hah I am using wireshark and sniffing the traffic. I don't see the telemetry parameter you claim exists.. So I am asking.. what is the NAME of the telemetry parameter?

It's simple. You claim something, I am ready to verify. Now stop your bullshit and tell me the parameter name

 

[lolboy]

What they should've done is actual SD EmuNAND. That would have no chance of bricking you. Official Switch updates have something that recovers you if you die, SX does not unless you manually backup your NAND.

True, SD EmuNAND would have been perfect but for now I believe this is not that bad.

Well I've just wiped my switch clean, in Original Firmware - set up internet and a white theme.

Then the following:
1: Made a 6.0 nand backup.
2: Installed emu nand.
3: Tested emu nand and set a black them - also enabled stealth mode, tried getting game updates - not working (so all good).
4: Switched back to O/F - able to get game updates :-) and access online features.
5: Went back to emunand - so all good with game updates.
6: Next to try installing nsp in emunand as these should be playable without being banned - due to not being on the original nand.

7: Happy days!

How about burning fuses?

 

[taxco]

Well I've just wiped my switch clean, in Original Firmware - set up internet and a white theme.

Then the following:
1: Made a 6.0 nand backup.
2: Installed emu nand.
3: Tested emu nand and set a black them - also enabled stealth mode, tried getting game updates - not working (so all good).
4: Switched back to O/F - able to get game updates :-) and access online features.
5: Went back to emunand - so all good with game updates.
6: Next to try installing nsp in emunand as these should be playable without being banned - due to not being on the original nand.

7: Happy days!

Can you boot to emunand without autorcm? Without a payload

 

[SpaceJump]

USER = one of the switch's system partitions. Specifically, it's the partition that has your games, saves, screenshots, all that shit.

SX OS resizes USER to make room for their own USER partition, which also contains the relatively smaller other NAND partitions. This means the reported size for USER is inaccurate to what it should be.

As to what is reported: use wireshark and analyze send traffic.

According to jsons findings (Link) none of the partitions resized. So how did you find out this USER partition is resized?

 

[RY0M43CH1Z3N]

According to jsons findings (https://gbatemp.net/threads/how-does-sx-os-emunand-work.518936/#post-8297682) none of the partitions resized. So how did you find out this USER partition is resized?

Because you need your 15GB from switch internal storage...

 

[Flying Scotsman]

If anyone's interested - hexkyz did a technical rundown on how this dual boot Nand thing works.

You'll find the Twitter thread here.

 

[Cha0tic]

Hah I am using wireshark and sniffing the traffic. I don't see the telemetry parameter you claim exists.. So I am asking.. what is the NAME of the telemetry parameter?

It's simple. You claim something, I am ready to verify. Now stop your bullshit and tell me the parameter name

Lol dude is ignoring you and arguing with other people.

 

[JJTapia19]

How can it - it's a separate O/S? nothing gets written to your O/F bit of the nand, only to emunand and microsd card.

If it's separated how were you able to download your game updates on official firmware and then had the game updates on emunand? Thats what I understood from your post.

Well I've just wiped my switch clean, in Original Firmware - set up internet and a white theme.

Then the following:
1: Made a 6.0 nand backup.
2: Installed emu nand.
3: Tested emu nand and set a black them - also enabled stealth mode, tried getting game updates - not working (so all good).
4: Switched back to O/F - able to get game updates :-) and access online features.
5: Went back to emunand - so all good with game updates.
6: Next to try installing nsp in emunand as these should be playable without being banned - due to not being on the original nand.

7: Happy days!

 

[Purple_Shyguy]

If it's separated how ware you able to download your game updates on official firmware and then had the game updates on emunand? Thats what I understood from your post.

Hmm... Good point.

 

[SpaceJump]

Because you need your 15GB from switch internal storage...

That's not an answer to my question...

 

[D-Jay]

Rip people who updated to 6.0.0 for switch ness online app,

so layerdfs emunand. I thought xecuter can do better.

What are you telling? God, I can't read people like you anymore.

 

[mrdude]

After you installed a nsp game on "emunand" does it shows up on official firmware?

I can confirm that I installed an NSP called Dream Alone in emu nand, I played the game (told me there was an update - even though I had no internet). I then switched to O/F and the game doesn't show up.
So now we can install nsp - without fear of being banned - only you will need to download updates for these elsewhere in emunand.

 

[ov3rkill]

Truly revolutionary. xD

 

[tpax]

Oh wow, TX GODS did it again I guess. So many great updates for such a low priced device. Really, there's just no competition. Best spent 30$ in my entire life.

 

[JJTapia19]

I can confirm that I installed an NSP called Dream Alone in emu nand, I played the game (told me there was an update - even though I had no internet). I then switched to O/F and the game doesn't show up.
So now we can install nsp - without fear of being banned - only you will need to download updates for these elsewhere in emunand.

Awesome! Thanks for reporting back.

 

[machinoman]

while they have certainly tested it and it works, nintendo could certainly query the system to ask about the size difference, but i find it difficult to believe they didn't think of that ahead of time. it is likely already prepared to lie when asked how big the partition is, like a TB micro SD card does.
if this thing actually works, i would recommend buying one before nintendo destroys this company like they did Bung, M3, and the others, if only to flip it later.

edit: oh wait its a software update. derp

 

[mrdude]

Awesome! Thanks for reporting back.

No worries, also when in emunand - switch to a black theme, in O/F or CWF(non emunand) - use a white theme. That way you won't get confused which firmware you are in, and accidentally install nsp in the wrong nand.