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

 

[Reecey]

Before creating emunand, I made sure I had about 20gb free. It's all good now... the process finally completed lol

How long did yours take to complete in the end I was trying my EmuNAND setup and it’s been going over an hour now? I made sure I had over 20gb of space before I began.

 

[halvfast]

Prison Architect crashes after starting the game with SX OS 2.0.

 

[digipimp75]

How long did yours take to complete in the end I was trying my EmuNAND setup and it’s been going over an hour now? I made sure I had over 20gb of space before I began.

It took about 1hr 15min, give or take.

 

[Reecey]

It took about 1hr 15min, give or take.

Thanks mine just finished it took 3hrs. 45mins! so much for the 20mins. Emunand seems to work all ok as it should I can’t find anything wrong sleep mode works fine some are saying it doesn’t.

It worked fine as well doing it with autorcm, if anyone else is wandering it didn’t go flat or turn off or go into sleep mode I had the charger plugged in so no “potential bricks” and it setup exactly as it should.

I’m just thinking if I turned the stealth mode of in Emunand would it still be activated in regular cfw? If this is the case I cannot see why then online can’t be used to its full potential in Emunand with nsp/xci titles.

 

[SoCALCat]

You would have to upgrade your nand backup to 6.0 for it to boot normally.

Although you could boot into RCM and then use a dongle to disable the fuse checks.

Ok. I'll make sure to create a new nand backup now that I'm running on OFW 6.0 and delete the nand backup from when I was on OFW 5.1
Thanks for your input

 

[HardMind]

Quick Q, 6.0 officially update is save now? I mean the SX OS can work with it with no problem?

 

[TheZander]

Quick Q, 6.0 officially update is save now? I mean the SX OS can work with it with no problem?

People say some games don't work also issues with autorcm and sleep mode.

 

[HardMind]

People say some games don't work also issues with autorcm and sleep mode.

You mean EmuNAND or the original has these problems? because im not interesting about EmuNAND.

 

[TheZander]

You mean EmuNAND or the original has these problems? because im not interesting about EmuNAND.

I believe just regular. Games like the messenger do not work because of them putting layeredfs back I believe. Also i saw autorcm issues, I have no idea ow they are coming to that conclusion but if you are able to sift threw the post for valuable info it's there.


I don't know how much of this is 6.00 specific vs SXOS specific however.

 

[TheDarkGreninja]

It kinda does. Not brick but iPhones are designed to become useless. As the battery gets older the phone is programmed to actively bottleneck itself, which coupled with each ios being harder to run than the last forces you to upgrade.

Off topic, but that's only half true, each ios update doesn't cause a decrease in performance, (I mean 12 has caused a boost). It's the requirements for apps that cause issues.
Also as the battery gets older it bottlenecks itself to make sure the phone still has good battery life, though this feature is gone now afaik.

 

[kamesenin888]

You mean EmuNAND or the original has these problems? because im not interesting about EmuNAND.

With 1.9 everything works as intended, its 2.0 that might break some things, if you get 1.9 everything should work on 6.0 except layered fs

 

[HideoKojima]

With 1.9 everything works as intended, its 2.0 that might break some things, if you get 1.9 everything should work on 6.0 except layered fs

Officially updated to 6.0 everything works (no Layeredfs, auto rcm or sleep mode user though)

 

[frostii]

Hi all,

I'm curious.... with the 6.0 update out now (officially), can anyone confirm if they ran into problems just updating the 'legitimate' way?
For example, I'm currently on 5.1, SX OS 1.9, Auto RCM, several NSPs installed, currently not banned (would like to stay that way but not bothered if I do).

I would like to be on 6.0, SX OS 2.0, Auto RCM, but if I update through OFW, can anyone confirm if any of the following happened to them:
- Did you get banned through the detection of unofficial NSPs?
- Was the update successful?
- Was Auto RCM removed and you had to 'reinstate' it?
- Anything else to be wary of? (not concerned about efuses, just the ability to play all games when they are released)

I'm still weighing up the pros and cons - ultimately when Smash comes out I will likely need 6.0 to play it.

Thanks for your time.

 

[uludag]

Hi all,

I'm curious.... with the 6.0 update out now (officially), can anyone confirm if they ran into problems just updating the 'legitimate' way?
For example, I'm currently on 5.1, SX OS 1.9, Auto RCM, several NSPs installed, currently not banned (would like to stay that way but not bothered if I do).

I would like to be on 6.0, SX OS 2.0, Auto RCM, but if I update through OFW, can anyone confirm if any of the following happened to them:
- Did you get banned through the detection of unofficial NSPs?
- Was the update successful?
- Was Auto RCM removed and you had to 'reinstate' it?
- Anything else to be wary of? (not concerned about efuses, just the ability to play all games when they are released)

I'm still weighing up the pros and cons - ultimately when Smash comes out I will likely need 6.0 to play it.

Thanks for your time.

Why do you all want to update as soon as an update is released?
Smash comes on December 7th. That's more than two months from now. Why not just chill until then and wait for SXOS and all other solutions to be modified for better stability?
I think it's too early to ask these questions.

 

[Paulsar99]

Hi all,

I'm curious.... with the 6.0 update out now (officially), can anyone confirm if they ran into problems just updating the 'legitimate' way?
For example, I'm currently on 5.1, SX OS 1.9, Auto RCM, several NSPs installed, currently not banned (would like to stay that way but not bothered if I do).

I would like to be on 6.0, SX OS 2.0, Auto RCM, but if I update through OFW, can anyone confirm if any of the following happened to them:
- Did you get banned through the detection of unofficial NSPs?
- Was the update successful?
- Was Auto RCM removed and you had to 'reinstate' it?
- Anything else to be wary of? (not concerned about efuses, just the ability to play all games when they are released)

I'm still weighing up the pros and cons - ultimately when Smash comes out I will likely need 6.0 to play it.

Thanks for your time.

Updated to 6.0 the legit way without any issues and everything works fine for me, I'm surprised that I'm still not banned eventhough I've been pretty careless lately. Can't answer the autorcm part because I don't use it but a lot of user said that it doesn't work for them or they have issues with it.

 

[chest0r]

Hi all,

I'm curious.... with the 6.0 update out now (officially), can anyone confirm if they ran into problems just updating the 'legitimate' way?
For example, I'm currently on 5.1, SX OS 1.9, Auto RCM, several NSPs installed, currently not banned (would like to stay that way but not bothered if I do).

I would like to be on 6.0, SX OS 2.0, Auto RCM, but if I update through OFW, can anyone confirm if any of the following happened to them:
- Did you get banned through the detection of unofficial NSPs?
- Was the update successful?
- Was Auto RCM removed and you had to 'reinstate' it?
- Anything else to be wary of? (not concerned about efuses, just the ability to play all games when they are released)

I'm still weighing up the pros and cons - ultimately when Smash comes out I will likely need 6.0 to play it.

Thanks for your time.

i have updated my FW 5.1.0 on booted SXOS EmuNAND to 6.0.0 Exfat with ChoidujourNX without any problems.
AutoRCM was enabled, custom nsps installed, LayeredFS stuff and homebrew apps on sd card as well.
My fuses are not burnt and my console isnt banned.

after the update to EmuNAND 6.0.0 everything works like a charme. Also the standby stuff and so on. Dont have any issues with SXOS 2.0 and FW 6.0.0

 

[lazyolandy]

Interesting release, although I'll be holding out for an SD based emunand.

A few questions:

• Is the Auto RCM issue a 6.0 problem, or does it only happen when using the emunand feature?
• Does the nand dump process replace the original nand backup process from Canna's tutorial?

 

[stewacide]

The autorcm issue is SX2.0 unrelated to emunand, you can enable autorcm some other way and it works fine.

 

[brollikk]

we need 2.1 asap.

 

[lazyolandy]

The autorcm issue is SX2.0 unrelated to emunand, you can enable autorcm some other way and it works fine.

Ah ok, thanks. I haven't received my dongle yet, so haven't touched my Switch.
I'm pretty new to the scene - how else can I enable Auto RCM?
Would it be safer to update to 6.0 but stay on SX 1.9 for now?