TX is on roll, release after release, and today's big release is brand-new SX OS v2.3 BETA

As you read thru TX's announcement below, you will quickly see that is jam-packed with all the features you have been requesting recently like SD EmuNAND and USB Homebrew, so check it out below:

Your favorite superheroes from Team Xecuter are back with another SX OS update.​

In v2.3 beta of SX OS we have some exciting new functionality that you, the community, has been requesting a lot. As you know, we value your feedback and support.. so your wishes are our command!

Let's have a look at the changelog:

• SD emuNAND support
  Since the introduction of our emuNAND feature we got a lot of comments about our initial decision to make the emuNAND data live on the actual system NAND. After lots of hard work we are happy to say we now have a workable solution for storing your emuNAND partition data on your microSD card. This has the upside of not using up any space on your Switch. In order to use the new microSD emuNAND system you will *not* have to format your microSD card. Simply enter the TX boot menu by holding Volume-+ while powering on your switch. Head into the options menu and select emuNAND on the left. Users of our existing emuNAND solution will see an option to migrate their existing emuNAND data. The migration process also cleans up the old emuNAND from the system NAND. Painless! We're interested in hearing your feedback about this exciting new functionality.
• The 'Emutendo' folder
  In addition to the new microSD emuNAND system we also introduce the 'Emutendo' folder on your microSD card. As you've probably noticed, the Switch saves various data to a 'Nintendo' folder on your microSD card. To completely decouple this data between your Original Firmware and your EmuNAND enabled firmware we have made EmuNAND enabled systems use this differently named folder. If you want keep using your old SD card data with your emuNAND, simply copy/rename the 'Nintendo' folder to 'Emutendo'.
• Added more directories to scan for content
  By popular demand we have added yet another list of subdirectories that will be scanned on your microSD card (or USB harddisk) for XCI/NSP/homebrew. The directories that have been added are:
  • – /sxos/updates
  • – /sxos/dlc
  • – /switch/updates
  • – /switch/dlc
• Homebrew menu takeover of any title by holding R
  Homebrew is usually launched from either the TX menu or the Homebrew Launcher menu. Both of these applications run as an 'applet' on the Switch. Applets do not have access to all of the system's memory, and thus any homebrew apps or games launched from here are affected by this as well. The only way to allow full use of the system's memory was to build and install homebrew NSP files. But now we have added another way to give homebrew applications full memory access! You can now hold the (R) button while launching any regular title, and this will launch the Homebrew Launcher Menu. Any homebrew launched from here will run with the same capabilities as a regular Switch game/app. Enjoy!
• Loading homebrew from USB
  More good news for homebrew lovers. You can now copy homebrew NRO files to your USB harddisk as well, and launch them directly from our SX OS menu.
• Stability improvements
  Overall stability of many components has been improved. This includes LayeredFS and USB incompatibilities. We have also fixed a bug which would prevent people from launching more than 32 titles.
• libusbfs update
  Last but not least a small update for developers. We've squashed a small bug in libusbfs pertaining the stat() function. If you had issues with this, grab an updated copy of libusbfs from our website!

The year 2018 is entering its final months. That does not mean we're taking a break from working on our beloved SX OS though. And yes, also those new 'unhackable' consoles are high up on the agenda. Don't worry, we will deliver.

Keep sending your feedback and ideas, they're very welcome.

See you all in the next update!

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

Source: MaxConsole

 

[virusburger101]

This sucks..
Lost all my games when I used Emunand.

You can fix this by just redownloading the last version of SXOS you were using. I ran into the same problem, just googled SXOS beta downloads and it came up with a link to the forums. After I restored SXOS I got all my games back and setting I have in my emunand.

 

[jakkal]

So how is this better for people that are hard ban or not interested on online playing ???

if you run brick code on emunand, only emunand will be affected

 

[matias3ds]

if you run brick code on emunand, only emunand will be affected

I run the games on sxos it that emunand ?

 

[Loko4]

thats what an emunand is
maybe you should do some research into it first

If I was talking about emunand on 3ds I dont even ask, however a lot of people say that the first emunand in sxos was so incomplete that couldnt be called emunand. Anyway thanks.

 

[nswuser007]

I believe the hdd capacity that works with the beta to run xcis from hdd is 2tb or lower. the 4tb says scanning/ some guy on youtube saying 2.2 beta only works with 2tb or less as well..

 

[longxa762]

• The 'Emutendo' folder
  In addition to the new microSD emuNAND system we also introduce the 'Emutendo' folder on your microSD card. As you've probably noticed, the Switch saves various data to a 'Nintendo' folder on your microSD card. To completely decouple this data between your Original Firmware and your EmuNAND enabled firmware we have made EmuNAND enabled systems use this differently named folder. If you want keep using your old SD card data with your emuNAND, simply copy/rename the 'Nintendo' folder to 'Emutendo'.

Aren't this is the reason peoples are losing all their installed game and data? Has anyone renamed the folder after turning on their new emuNAND?

 

[jakkal]

If I was talking about emunand on 3ds I dont even ask, however a lot of people say that the first emunand in sxos was so incomplete that couldnt be called emunand. Anyway thanks.

but this isnt the first emunand
this one is on the microsd card

i dont get the confusion

 

[lufeig]

I was on real nand 6.0.1 autorcm. no emunand at all.

I already have nand backups.

I updated my savegames backups using checkpoint.

updated boot.dat to 2.3 beta

copied Nintendo folder to Emutendo

created an sd emunand, enabled it and booted sx os.

100% functional until now.

1,000% profit

 

[jakkal]

I was on real nand 6.0.1 autorcm. no emunand at all.

I already have nand backups.

I updated my savegames backups using checkpoint.

updated boot.dat to 2.3 beta

copied Nintendo folder to Emutendo

created an sd emunand, enabled it and booted sx os.

100% functional until now.

1,000% profit

finally someone with a brain
its so simple to set up

 

[shanefromoz]

I was on real nand 6.0.1 autorcm. no emunand at all.

I already have nand backups.

I updated my savegames backups using checkpoint.

updated boot.dat to 2.3 beta

copied Nintendo folder to Emutendo

created an sd emunand, enabled it and booted sx os.

100% functional until now.

1,000% profit

How would you then update to 6.1.0?

 

[Don Jon]

How would you then update to 6.1.0?

you can maybe update in emunand mode?

 

[Hernie]

I was on real nand 6.0.1 autorcm. no emunand at all.

I already have nand backups.

I updated my savegames backups using checkpoint.

updated boot.dat to 2.3 beta

copied Nintendo folder to Emutendo

created an sd emunand, enabled it and booted sx os.

100% functional until now.

1,000% profit

So you copied the entire contents from the "Nintendo" folder to the "Emutendo" folder before you actually created the emuNand?

I was going to do it after, but if that worked for you, that's the way I'm going to do it.

I'm sure I would just boot into SD emuNand then use ChoidujourNX to update?? I'm still on 4.1.0

 

[thaikhoa]

if you run brick code on emunand, only emunand will be affected

Confirmed. Tried to brick my Switch using PIKASHIT. EMUNAND will be bricked but SYSNAND.

 

[Brusier]

buggy.....gonna wait

 

[Lilphish]

I'm on 6.1 and when I try to hold 'R' when launching a title to go into homebrew, it just tries loading the game and nothing happens. Is there something else I need to do to set this up?

 

[Shadowfied]

exFAT in general is wonky on the switch and constant read/writes to any filesystem (wether its exFAT or FAT32) is just a recipe for corrupting it and the files on it.

The reason the emuNAND solutions from the 3DS scene repartitioned the SD was specifically to avoid this from occuring.

Are you saying one partition has less chance of being corrupted because you are writing to another partition on the same storage device instead......?

 

[shanefromoz]

Once set up how does one update once in emunand?
Do we just use ChoiDujourNX but in emunand mode?

 

[JJTapia19]

@garyopa Found a Bug here! After starting the game Overcooked 2 after the company logos the game ask me to press R and L to start. As soon as I do the Homebrew Menu pops up and it takes over the game and I must close the game via the home menu to exit. I assume it must have something to do with the new Homebrew menu takeover of any title by holding R feature. Not sure if other games have similar problems I'm on 2.3 beta sd emunand Fw 6.1.0-4.0 sd exfat format.

 

[Kubas_inko]

SD EmuNAND. Finaly. Although, if it works as their """EmuNAND""" it is still not an EmuNAND which everyone wants and love (partitioned SD)

 

[Fafner]

Aren't this is the reason peoples are losing all their installed game and data? Has anyone renamed the folder after turning on their new emuNAND?

Me not,and everything seems ok. Doesn't that folder contain legit games as well? I checked before moving my Emunand and it contained 60+GBs of stuff. If one renames that folder, I can imagine OFW will have to redownload everything.

This point is the only part of 2.3's changelog I didn't really understand. If you want to keep your old SD data...but which data edactly?