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

 

[Jordan9716]

Look at the button (Emunand enabled) on the top of Boot To CFW button in sx bootloader. Make sure it is [Emunand enabled]. After moving emunand to SD, the emunand is disabled by default.

That options not even showing up. It did at one point but it isn't now.

Could it be because I got rid of the folder that had backups in it like boot01 and stuff? It was around 30gb in size.

 

[tinkle]

ie. through the dev menu using the nsp files? does this not increase ban risk as I'd be using nsp?

thanks!

No, you use NSC Builder to create custom XCI's that slipstream the updates and DLCs into the XCI's themselves.

 

[skydancer93]

No games require installs if you patch your XCIs. Ideal Switch workflow now is to never use any NSPs, and just install them to your XCIs, then store all your XCI's on a USB-C Thumbdrive. That way you can use your internal MicroSD as FAT32 and reduce all risks.

Yeah, I’m sure that works on the titles I mentioned where the rest of the game is in an update....

 

[icegold]

No, you use NSC Builder to create custom XCI's that slipstream the updates and DLCs into the XCI's themselves.

got ya, thanks. Sadly as I'm using a mac I think I'll have to risk updating the games in OFW

 

[tinkle]

Yeah, I’m sure that works on the titles I mentioned where the rest of the game is in an update....

It does, actually. I have DOOM for example, with the update integrated into a single XCI that doesn't require any installation. So check your snark at the door, mate.

--------------------- MERGED ---------------------------

got ya, thanks. Sadly as I'm using a mac I think I'll have to risk updating the games in OFW

Just use a VM for this.

 

[comput3rus3r]

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

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:


Source: MaxConsole

Any confirmation on whether or not this protects against malicious NSPs?

 

[mattytrog]

Any confirmation on whether or not this protects against malicious NSPs?

Well by default it will, as you cannot hard brick from emunand.

 

[comput3rus3r]

Well by default it will, as you cannot hard brick from emunand.

people were claiming with the previous on Nand "emunand" that it wouldn't protect you from nsp jumbling up your prodinfo because supposedly the emunand only emulated user partition and the sysnand prodinfo was still being affected. Did this change in this version of emunand? Does this sd emunand copy the entirety of the sysnand including prodinfo?

 

[mattytrog]

people were claiming with the previous on Nand "emunand" that it wouldn't protect you from nsp jumbling up your prodinfo because supposedly the emunand only emulated user partition and the sysnand prodinfo was still being affected. Did this change in this version of emunand? Does this sd emunand copy the entirety of the sysnand including prodinfo?

From my understanding, boot0/1 and prodinfo are all copied. Not 100% though as I've not been through the emunand yet

 

[comput3rus3r]

From my understanding, boot0/1 and prodinfo are all copied. Not 100% though as I've not been through the emunand yet

we need verification on this. I've asked @garyopa but he hasn't responded. I've emailed xecuter and they haven't responded either.

 

[mattytrog]

Wouldn't really be emunand if they weren't copied though would it

 

[bostonBC]

Would personal experience count?

I've had my exFAT filesystem corrupt a bunch of times before I gave up and just moved back to FAT32.

Perhaps you are using a substandard microSD or it is flaky. Or you are running apps that corrupt it.

I've had no problems on any of my 3 Switch's.

 

[Jordan9716]

listen
if you cant do any better just move along if you dont have anything good to say
you cant write your own so what gives you the right to bash others work

go away man...or whatever you are

--------------------- MERGED ---------------------------


look in the sxos folder
youll see a folder called backup

its a backup of your nand. you can delete it
so theres actually 2 copies of your nand in that folder

the backup and the emunand

How do I go about restoring my emunand backup? When I did the SD card emunand it deleted everything?

 

[jakkal]

Wouldn't really be emunand if they weren't copied though would it

They're copied. They are all in the emunand folder

--------------------- MERGED ---------------------------

How do I go about restoring my emunand backup? When I did the SD card emunand it deleted everything?

Read the op
Or do you need a chart? Everything is there for you

 

[youcantseeme421]

I'm not having an issue with it deleting games. I've having an issue with the emuNAND not even being recognized after going to 2.3

There's no "emuNAND enabled/disabled" option above "boot cfw" after updating. And when I do try to boot cfw, it just gives an error. It doesn't create an Emutendo folder. It's as if the emuNAND was never there at all. I'm not sure if I should wait for an update, or recreate the emuNAND. For now, I went back to 2.2.1 and the emuNAND appeared again. It's strange.

 

[mcsdoode]

I'm not having an issue with it deleting games. I've having an issue with the emuNAND not even being recognized after going to 2.3

There's no "emuNAND enabled/disabled" option above "boot cfw" after updating. And when I do try to boot cfw, it just gives an error. It doesn't create an Emutendo folder. It's as if the emuNAND was never there at all. I'm not sure if I should wait for an update, or recreate the emuNAND. For now, I went back to 2.2.1 and the emuNAND appeared again. It's strange.

You have to go to the emunand settings. I'm to paste my explanation on how I did it, from another thread I replied to in case it may help you; the process isn't automatic.


"...After updating your SX payload, boot into the SX settings menu (Vol+ and power button combo).

I would say go ahead and confirm you have ample space on your SD card for the Emunand. After, go to the Emunand settings and choose the option to move the Emunand.

Next, rename your (Nintendo) directory on the root of your SD to (Emutendo). The process took about 40 minutes on my console.
The first time I booted the Emunand from SD, I thought my Switch had frozen, as I only saw a black screen. I gave it a bit and it loaded eventually. I assume read times will be a bit slower from the SD."

--------------------- MERGED ---------------------------

You have to go to the emunand settings. I'm to paste my explanation on how I did it, from another thread I replied to in case it may help you.


"...After updating your SX payload, boot into the SX settings menu (Vol+ and power button combo).

I would say go ahead and confirm you have ample space on your SD card for the Emunand. After, go to the Emunand settings and choose the option to move the Emunand.

Next, rename your (Nintendo) directory on the root of your SD to (Emutendo). The process took about 40 minutes on my console.
The first time I booted the Emunand from SD, I thought my Switch had frozen, as I only saw a black screen. I gave it a bit and it loaded eventually. I assume read times will be a bit slower from the SD."

 

[realjumy]

Ok. This is finally a great breakthrough.

 

[noX1609]

That‘s a really great update!!

But one question: Is it possible to keep the emuNAND in emmc or do i have to change to the new one? That‘s a thing i found nowhere. I think most users will switch to the NAND on the sd card and because of that i’m worried tx will remove the emuNAND in emmc feature. So i‘m not really sure what to do because for Games i only use xci files so space on the microSD is more important then the space on the emmc.
So are there any great features that only work with emuNAND on SD Card?

And has anyone tested if the bug is fixed that on splitted xci card 2 Games it displays a white icon and no infoarmation like publisher etc.?

 

[Waywatcher]

EmuNAND sounds great and all, but is there any point on getting it if you are already banned?

 

[comput3rus3r]

EmuNAND sounds great and all, but is there any point on getting it if you are already banned?

Allegedly, more brick protection.