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

 

[Andalitez]

Thanks for the confirmation.
I started it one last time again to see if I get anywhere tonight

Let it run overnight while on charge.
Saw it had the full 29.1gb nand dump in the Emunand folder. It booted to a black screen when I tried it, but that might be because I didn't rename the Nintendo folder.

Will try it when I get home later

 

[Nym5]

One thing that I'm not sure that can be answered yet and I'm thinking about far into the future here:
If I'm playing a game on my Emunand and, let's say, in the future, I decide to buy this game and play it on my OFW. Do we have any signs that it will be possible to transfer the save from my Emunand and inject it into my OFW someday? I know it might be a premature question since the future of the scene is unknown right now, but I get scared of investing a lot of time in a game (like Diablo 3), decide to buy it in the future and have absolutely no way to make use of my progress.

Oh, one more doubt:
In the proccess of creating my emunand I renamed the Nintendo folder of my SD card to Emutendo. If someday I decide to delete my Emunand, will the folder be deleted with it? Should I keep a copy of my original Nintendo folder in my PC in case I want to go back to using my OFW?

 

[Reecey]

Has anyone else tried the hold R button for homebrew menu on booting any title and it works? I have tried it and it doesn’t seem to work on anything for me, it just sits at the Nintendo loading screen.

 

[jakkal]

still no 6.2 support. meh.

It's been like 4 days man. Relax

 

[guily6669]

Im thinking to buy SX OS today, but the nice small On\Off button candidate for my Joy-Con got broken into pieces while removing it from a super small RC helicopter I had ...

Can I activate and create a SX OS SD emunand without even ever opening the normal SX CFW?

 

[ichibaka]

One thing that I'm not sure that can be answered yet and I'm thinking about far into the future here:
If I'm playing a game on my Emunand and, let's say, in the future, I decide to buy this game and play it on my OFW. Do we have any signs that it will be possible to transfer the save from my Emunand and inject it into my OFW someday? I know it might be a premature question since the future of the scene is unknown right now, but I get scared of investing a lot of time in a game (like Diablo 3), decide to buy it in the future and have absolutely no way to make use of my progress.

Oh, one more doubt:
In the proccess of creating my emunand I renamed the Nintendo folder of my SD card to Emutendo. If someday I decide to delete my Emunand, will the folder be deleted with it? Should I keep a copy of my original Nintendo folder in my PC in case I want to go back to using my OFW?

You just have to back up the game save from emunand, load up real nand in cfw and restore it.

 

[noX1609]

I have a question: Migrated my emuNAND to SD Card but it‘s only 14GB big (no games installed yet only migrated the emuNAND.
The emuNAND i created within the eMMC was 20GB.
Is that normal and it get‘s expanded if space is used completely or is there a problem and i would need to create a new one? Because i read that for people who don‘t had one with the old method and migrated their emuNAND does have the „normal“ size (32GB like sysnand).

 

[Hodorian]

Has anyone else tried the hold R button for homebrew menu on booting any title and it works? I have tried it and it doesn’t seem to work on anything for me, it just sits at the Nintendo loading screen.

the same here. Only the loading screen shows up.

 

[Reecey]

the same here. Only the loading screen shows up.

Thanks it’s not just me then it must be an issue.

 

[Bushido1992]

Thanks it’s not just me then it must be an issue.

Works perfect 4 me on 6.1.0 / 2.3beta

 

[Reecey]

Works perfect 4 me on 6.1.0 / 2.3beta

I must be doing it wrong then I’m on 6.1.0/2.3b so you pick any title anyone hold the R shoulder button down start the title and it should boot the homebrew menu? Is that correct that’s the way I am doing it. Just thought does the hbmenu.nro file have to be on the route of your sd card?

Edit: yes it does work. The hbmenu.nro has to be on the route of your sd card that’s why it didn’t work for me mines setup in my switch folder I have my own made nsp hbmenu, also it crashes loading with nsp homebrew I’ve just found out.

 

[WiiuGold]

SSB works on SX 2.3

 

[jakkal]

SSB works on SX 2.3

it will work on any cfw bro

 

[WiiuGold]

it will work on any cfw bro

I hope but i only use SX buddy

 

[guily6669]

I just bought SX OS a few hours ago, my emunand is also not working, I didnt even tried booting to normal CFW...

I copied boot0.bin and boot1.bin from hekate backup to SX emunand folder, but it still goes to black screen.

 

[jakkal]

I just bought SX OS a few hours ago, my emunand is also not working, I didnt even tried booting to normal CFW...

I copied boot0.bin and boot1.bin from hekate backup to SX emunand folder, but it still goes to black screen.

did you create the emunand using sx os RCM menu?

 

[urherenow]

yea you have to 1) create the emunand in the first place, and 2) Enable emunand before launching CFW by tapping the box that would currently say "EMUNAND DISABLED".

But if you already have a 6.2 sysnand, you can't make an emunand from that (yet). Thought I read somewhere (maybe this thread) that people were having trouble with migrating from internal to external emunand. I didn't mess with emunand yet, and placed my Switch in airplane mode for some reason the last time I messed with it, so I don't have any of these problems

 

[guily6669]

did you create the emunand using sx os RCM menu?

Yep, my sysnand is either 100% clean or 99% as I only entered RCM 4 the 1st time today, never booted any CFW neither SX OS CFW (and went to bed today at like 8am here, I lost more than a hour searching 4 the god damn Joy-con R button spring that I lost lol, I added a crap ON\OFF button).

I just did a backup with SX OS RCM and with Hekate.

My console is at 3.02 and I want it to remain at 3.02 4 ever...

I created a emunand 4 the 1st time and copied boot0.bin and boot1.bin from hekate (renamed the files off course...).

I know its giving problems 4 a lot of ppl, but it might also be because I'm using exFat without the update 4 it, so it might be locking emunand from booting.

 

[jakkal]

Yep, my sysnand is either 100% clean or 99% as I only entered RCM 4 the 1st time today, never booted any CFW neither SX OS CFW (and went to bed today at like 8am here, I lost more than a hour searching 4 the god damn Joy-con R button spring that I lost lol, I added a crap ON\OFF button).

I just did a backup with SX OS RCM and with Hekate.

My console is at 3.02 and I want it to remain at 3.02 4 ever...

I created a emunand 4 the 1st time and copied boot0.bin and boot1.bin from hekate (renamed the files off course...).

I know its giving problems 4 a lot of ppl, but it might also be because I'm using exFat without the update 4 it, so it might be locking emunand from booting.

Why are you copying the files?
Everything should be done automatically

 

[WiiuGold]

SSBU xci file works on SX !!