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

 

[jakkal]

Given how poorly the Switch handles ExFAT I dont know why yall arent using FAT32

So... using the Switch at all?

Nintendo's exFAT drivers are the epitome of "poorly made", corruption just happens on exFAT by default if you use it on your Switch.

yeah i wonder why ive never gotten one instance of corruption and i have been using exfat since the day the update came out

i dont think you know much about anything

 

[Kubas_inko]

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.

No, because you give us no data.

 

[Ev1l0rd]

yeah i wonder why ive never gotten one instance of corruption and i have been using exfat since the day the update came out

i dont think you know much about anything

No, because you give us no data.

I mean, I was just feeling kinda lazy, but here:

https://gbatemp.net/threads/poll-fat32-vs-exfat-issue-discussion.514801/

This is just a general Nintendo exFAT issue, not to do with TX, although if you use exFAT for the SDs emuNAND, you are affected by it

 

[WiiUBricker]

wonder if the emuNAND on sd could help playing online safely with bought cartridges

Several people asked the same question in this thread and so far nobody has anserwed the question, probably due to uncertainty. I’m not sure either but what I’m sure of is that -emuNAND or sysNAND - you need a Nintendo account with a Nintendo Switch Online Subscription in order to play online. The question now is whether or not they can detect emuNAND while you’re in unhacked sysNAND and if a banned emuNAND has any effect on the sysNAND since both share some data about your Switch. To minimize the risk of your online account being banned, you should use separate accounts for sys- and emuNAND in case you accidently performed some online activity while in hacked emuNAND (I suggest deleting the internet settings in emuNAND).

 

[Kubas_inko]

I mean, I was just feeling kinda lazy, but here:

https://gbatemp.net/threads/poll-fat32-vs-exfat-issue-discussion.514801/

This is just a general Nintendo exFAT issue, not to do with TX, although if you use exFAT for the SDs emuNAND, you are affected by it

All I can see is majority using exFAT, which means that majority will have problems with exFAT. That's pretty normal correlation.

 

[SwitchHack]

boom baby!

 

[JoeBloggs777]

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.

using which CFW ? I know its not SX OS as your a TX hater.

 

[KHEOPS]

Well, here's sd emunand....
Hate to see the reports, on reliability ,after restoring 6 times my hekate nand (1h20 each time) ,still not banned,will I be able to do without this? Played fortnite ?

 

[jacopastorius]

Anyone sure about ban risk of using FTP in emunand?

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

Well, here's sd emunand....
Hate to see the reports, on reliability ,after restoring 6 times my hekate nand (1h20 each time) ,still not banned,will I be able to do without this? Played fortnite ?

I feare xecuter team do not even know that. Otherwise they should have written something about that in the release notes

 

[Ev1l0rd]

All I can see is majority using exFAT, which means that majority will have problems with exFAT. That's pretty normal correlation.

exFAT corrupts if you just exit the homebrew menu from personal experience. FAT32 has much less issues.

 

[Kubas_inko]

exFAT corrupts if you just exit the homebrew menu from personal experience. FAT32 has much less issues.

Never happened to me. So you are just unlucky.

 

[notimp]

All I can see is majority using exFAT, which means that majority will have problems with exFAT. That's pretty normal correlation.

Its possible - but, then again, I've never seen so many potentially bricked filesystem related issues on a platform in my entire console hacking life.

And being on fat32, I'm in the same boat as you - never had an issue since the beginning. Hrm.

It cant all be stuff that comes from user error.... But in terms of probability you are right.

Still - argument could be made as follows. SX OS are the cause for the majority going with exfat > causing the biggest file system integrity problem seen so far in any hacking scene... (Nintendo might also play a part in that.. Libnx might as well.)

 

[jakkal]

exFAT corrupts if you just exit the homebrew menu from personal experience. FAT32 has much less issues.

ive exited homebrew all the time
thats all i do

never once ever i had corrruption

 

[thaikhoa]

Never happened to me. So you are just unlucky.

Don't ever use emulators/ ported games such as doom, quake 3 or half-life etc then exfat shouldn't be a problem at all. I got corrupted when quake 3 was crashed while playing. The corruptions were just some of the kips /nros or so, no major thing will be occurred.

 

[SwitchHack]

checkpoint, it does not work anymore!

 

[Kubas_inko]

Don't ever use emulators/ ported games such as doom, quake 3 or half-life etc then exfat shouldn't be a problem at all. I got corrupted when quake 3 was crashed while playing. The corruptions were just some of the kips /nros or so, no major thing will be occurred.

Played quake and doom (for shirt periods of time) and used a few emulators. Still no problems.

 

[thaikhoa]

checkpoint, it does not work anymore!

Works perfectly for me.

 

[jakkal]

checkpoint, it does not work anymore!

it does work
you need to load the game first at least once so it creates the title folder on the sdcard

then it will show up in checkpoint
come on.

 

[SwitchHack]

Works perfectly for me.

the console hangs, after the update

 

[skydancer93]

I’d like to be able to actually install stuff to the USB drive. That would actually be helpful. Especially for certain games that require an install like LA Noire and NBA 2K19