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

 

[Creatable]

Annnnd my device corrupt. Thanks a lot, asshole!

Jk, but could you explain why it would happen? Would it get corrupt?

Resizing your NAND partitions is a very delicate process, if it stops halfway through, shit just kinda... corrupts?

 

[mmajunkie77]

Well, I guess my 1.0.0 is still staying in the box for now

I've used SX from the beginning, and the progress in the scene is amazing. Like literally amazing. But I'm a bit disappointed in this one.

There's a also no need for so much negativity.. Jesus christ.

 

[The14thfly]

Resizing your NAND partitions is a very delicate process, if it stops halfway through, shit just kinda... corrupts?

I honestly have been resizing drives with data on them, and at some times id get issues or the drive would disconnect, but I have never got the data corrupt. But then again I was using another program , not TX's solution so it is most likely different.

 

[loler55]

question is how is the safest way to update emunand?? no words from xs to this im on 3.01 how should i update my emunand??

 

[Bedel]

An emunad at first, would not avoid bans. Don't?

But this really isn't a emunand. It emulates nothing, since it just copy the sysnand in a new patition of the main nand. Nothing is redirected to nowhere (well not really, they redirect to what partition the system have to start, but nothing major), nothing is really emulated. As people say, this will make your nand smaller, so Nintendo will know what you've done with the data they collect from your console once you start your main sysnand.
You don't have to think this as a emunand. It's something more like a second sysnand.

All of this is fine, and a good archievment, but as you can see, it doesn't have one use they say it has, and it shouldn't be called like this. Let's wait. If we are lucky, maybe in a few days we have another surprise and they bring us an actual emunand.

 

[TamarindoJuice]

But this really isn't a emunand. It emulates nothing, since it just copy the sysnand in a new patition of the main nand. Nothing is redirected to nowhere (well not really, they redirect to what partition the system have to start, but nothing major), nothing is really emulated. As people say, this will make your nand smaller, so Nintendo will know what you've done with the data they collect from your console once you start your main sysnand.
You don't have to think this as a emunand. It's something more like a second sysnand.

All of this is fine, and a good archievment, but as you can see, it doesn't have one use they say it has, and it shouldn't be called like this. Let's wait. If we are lucky, maybe in a few days we have another surprise and they bring us an actual emunand.

They told about not being a good idea to dump the whole 32GB NAND partition to the SD (obviosuly), maybe they run into some technical trouble to just dump the system and have it like a traditional emunand (3DS way), who knows?
I hope they keep improving it in the near future, let's wait.

 

[draxen]

Guys, are we 100% positive it repartitions the system NAND?
Could SX just be creating a virtual file system (as a single large file) inside the system NAND partition?
Has anyone tested it?

 

[Ashura66]

Guys, are we 100% positive it repartitions the system NAND?
Could SX just be creating a virtual file system (as a single large file) inside the system NAND partition?
Has anyone tested it?

TX says it themselves. This comes directly from their site:
"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"

 

[TamarindoJuice]

What's the dir to use the LFS mods on SX?
sx/titles?

 

[realjumy]

Stop crying, the whole open source scene could not code emunand support till now. Go back to your Reinand, Rajsomething or whaterver else you like to use.

Wrong. There was an emuNAND (a real one) in development. It was cancelled because the developer got enough of people using things half done without knowing what they were doing, and just for piracy. Therefore it's not a matter of the open source scene not being able to do an emuNAND support, but a matter of not wanting to. And I know at least of someone else with a funcional emuNAND developed, but I think it's extremely unlikely this person will publicly release it.

 

[draxen]

TX says it themselves. This comes directly from their site:
"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"

Their description is vague though. It doesn't actually say that the system NAND is being repartitioned. It only says that "your EmuNAND partition lives inside of your regular NAND". This could be using some kind of virtual file system (as a single large file) that sits in the system NAND partition (as a regular file).

I've *no idea* if this is what it's actually doing, I'm just wondering if anyone has actually verified that the system NAND is being repartitioned?
As in, installed SX 2.0, installed emuNAND and examined the partition table?

 

[Ashura66]

Their description is vague though. It doesn't actually say that the system NAND is being repartitioned. It only says that "your EmuNAND partition lives inside of your regular NAND". This could be using some kind of virtual file system (as a single large file) that sits in the system NAND partition (as a regular file).

I've *no idea* if this is what it's actually doing, I'm just wondering if anyone has actually verified that the system NAND is being repartitioned?
As in, installed SX 2.0, installed emuNAND and examined the partition table?

Creatable might have since they are a SX OS user though you'd have to ask them directly

 

[SecureBoot]

Since we have emunand, can we have custom certs?

 

[ChokingVictim87]

So put simply-should I download this update?

 

[alucard_xs]

There is probably something explaining that it's not an emunand (on SD). I think they do not know how to do it on SD card (a real emunand would have been great contrary to this hazardous copied sysNAND).

 

[Nincompoopdo]

So, my beloved SXOS - where is that external HD support?

 

[Ashura66]

Since we have emunand, can we have custom certs?

We DON'T have emunand

 

[Switchup]

So put simply-should I download this update?

To be honest I would wait until some clarification is given from appropriate sources. you can update but I would hold off installing "emuNAND".

 

[Essasetic]

This is the first SX OS release I'm legitimately disappointed about. Not only is the LayeredFS implementation not working properly on 6.0, but the homebrew NSP support only supports new NSP's. And """""emunand""""" gets you instantly banned.

Come on TX you can do better

 

[SecureBoot]

We DON'T have emunand

Okay. Since we have a secondary NAND, can we have custom certs?

 

[loler55]

sx os 2.0 dosnt boot on 3.01 after Nintendo Logo get blackscreen

only ofw boot up

 

[chest0r]

How should i update my firmware with that „emuNand“/„dualBoot“/„whatEverNand“ from 5.1 to 6.0? hope anyone can help out!

 

[ChokingVictim87]

To be honest I would wait until some clarification is given from appropriate sources. you can update but I would hold off installing "emuNAND".

Thanks-I'll update but wont do the EmuNAND

 

[Ashura66]

How should i update my firmware with that „emuNand“/„dualBoot“/„whatEverNand“ from 5.1 to 6.0? hope anyone can help out!

Don't. Several features are still broken with 6.0. Maybe they should focus on fixing that first

 

[TamarindoJuice]

Wrong. There was an emuNAND (a real one) in development. It was cancelled because the developer got enough of people using things half done without knowing what they were doing, and just for piracy. Therefore it's not a matter of the open source scene not being able to do an emuNAND support, but a matter of not wanting. And I know at least of someone else with a funcional emuNAND developed, but I think it's extremely unlikely this person will publicly release it.

Ok i got your point but... being open source or not but not releasing it, wasteful. When i talk about the scene, i talk about the scene releases, we can talk about something we can't test. I mean, having a cure to cancer but not releasing it is almost like not having a cure at all.

 

[chest0r]

and which things are broken? I heared that nsp's work, xci's work, homebrew also does and layeredfs now is also supported.

 

[Ashura66]

and which things are broken? I heared that nsp's work, xci's work, homebrew also does and layeredfs now is also supported.

LayeredFS is broken in 6.0.0 and homebrew NSP is indeed supported but it only supports NEW .NSP

 

[loler55]

sx os 2.0 cfw dosnt boot on 3.01 after Nintendo Logo get blackscreen and hang up
sx os 1.5 cfw boots fine....

only ofw boot up

now i create a emunand and look if it boots