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

 

[Essasetic]

but that is nintendo's bug -- if they updated the exfat driver to the one that samsung re 1:1 from microsoft's licensed code, they use on android phones then it would not be a problem.

Like I said not your fault that the exFAT driver is so shit. What is your team's fault is how they went about it. You didn't seriously think this would corrupt people's SD Cards? At least put a warning out saying "not recommended on exFAT SD cards" to prevent people from losing everything.

 

[maxx488]

exFAT SD cards are known for corruption. And this writes the same files over and over again. So pretty safe to assume it would cause a lot of damage.

Then put some flex tape on it. Problem solved.

 

[Essasetic]

Then put some flex tape on it. Problem solved.

Phil Swift should join TX and save the day.

 

[johnsnow]

exFAT SD cards are known for corruption. And this writes the same files over and over again. So pretty safe to assume it would cause a lot of damage.

What do you mean writes the same files over and over?

 

[Essasetic]

What do you mean writes the same files over and over?

https://twitter.com/hexkyz/status/1064600732618248192?s=19

 

[johnsnow]

I dont get it

 

[WiiuGold]

1064600724070252544
1064600726117052416
1064600728319062016
1064600730495942656
1064600732618248192

And it point is ?

 

[maxx488]

I dont get it

Just says that uses your sd card to read and write, like any other homebrew does. Dont worry, unless you do some really stupid shit like removing the sd card while saving you wont be having any issues.

 

[Essasetic]

I dont get it

Writes the boot 0 and 1 files, checks for files on the SD card, verifies the files and boot chains the NAND into a read/write process. So it continues to rewrite to the NAND.

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

And it point is ?

Rewrites to the NAND after the chain redirection. Like with the previous EmuNAND solution before it.

 

[johnsnow]

Writes the boot 0 and 1 files, checks for files on the SD card, verifies the files and boot chains the NAND into a read/write process. So it continues to rewrite to the NAND.

what? thats not what hexzyk means by bootchain

 

[garyopa]

https://twitter.com/hexkyz/status/1064600732618248192?s=19

There is no stopping you from using FAT32 for your emunand.

Personally, i don't see why people can't just buy two microsd cards.

Use one as exFAT with Nintendo folder and only for online usage.

And second one as FAT32 with Emutendo folder and custom firmware and homebrew like retroarch and cheats, and everything else that can cause exfat to fail, and they can install nsp's from usb hdd (which can be exfat) and xcis from there, -- or if they don't want to split xci's because they don't want to use a hdd, put just those on their exfat one.

Even if there was another custom firmware that offer emunand, it would still run into corruption issues on exfat, they would tell people to use fat32, just like they telling people to use fat32 for retroarch, same thing.

 

[thaikhoa]

Writes the boot 0 and 1 files, checks for files on the SD card, verifies the files and boot chains the NAND into a read/write process. So it continues to rewrite to the NAND.

God, I did backup and restore with verification of full nand using Hekate all the time. I haven't encountered any issue yet... Really!!!

 

[Vieela]

Awesome! It's really great to see that TX is working towards adding actual new stuff into their product and actually making it an interesting choice to buy. This one update made me gain quite the respect.

 

[Essasetic]

There is no stopping you from using FAT32 for your emunand.

Personally, i don't see why people can't just buy two microsd cards.

Use one as exFAT with Nintendo folder and only for online usage.

And second one as FAT32 with Emutendo folder and custom firmware and homebrew like retroarch and cheats, and everything else that can cause exfat to fail, and they can install nsp's from usb hdd (which can be exfat) and xcis from there, -- or if they don't want to split xci's because they don't want to use a hdd, put just those on their exfat one.

Even if there was another custom firmware that offer emunand, it would still run into corruption issues on exfat, they would tell people to use fat32, just like they telling people to use fat32 for retroarch, same thing.

Still doesn't excuse the fact that you didn't warn any exFAT users from not using the solution knowing full well what could happen if something went wrong.

 

[jakkal]

Tx puts emunand on nand
Idiots: this is so bad. This is not real emunand. Huehuehue

Tx puts emunand on sd: OMG wtf, this is not real emunand. Emunand should be on its own partition. Exfat bad


You guys are like npcs

 

[Essasetic]

what? thats not what hexzyk means by bootchain

He says it work similarly to the previous EmuNAND solution and seeing this is a port of the emunand from the actual NAND to the SD card this won't be any different.

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

Tx puts emunand on nand
Idiots: this is so bad. This is not real emunand. Huehuehue

Tx puts emunand on sd: OMG wtf, this is not real emunand. Emunand should be on its own partition. Exfat bad


You guys are like npcs

And you should develop some legitimate argument before calling everyone who complained about it out.

 

[johnsnow]

What is bad about it? To me it seem simple, redirect all eMMC read/write to SD. That is exactly what TX is doing ?

 

[Essasetic]

What is bad about it? To me it seem simple, redirect all eMMC read/write to SD. That is exactly what TX is doing ?

That it could cause corruptions to exFAT SD cards and they literally gave no indication it would. :/

 

[maxx488]

Tx puts emunand on nand
Idiots: this is so bad. This is not real emunand. Huehuehue

Tx puts emunand on sd: OMG wtf, this is not real emunand. Emunand should be on its own partition. Exfat bad


You guys are like npcs

Oblivion npcs*

 

[garyopa]

That it could cause corruptions to exFAT SD cards and they literally gave no indication it would. :/

In alot of testing, we let to have 'emunand' corrupt on its own, unless the user was doing something else, like pushing 'home' button while in retroarch or tinfoil, and that will cause corruption anyway even with emunand, so the user still would have to reformat his card even if he was using just sysnand and another cfw other than sx os.