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

 

[johnsnow]

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

Are you saying TX emunaand causes corruption, or homebrew writing to exfat is causing corruption?

 

[Essasetic]

Are you saying TX emunaand causes corruption, or homebrew writing to exfat is causing corruption?

TX emunand causes corruption to exFAT SD cards.

 

[johnsnow]

How do you know? You tested this? Where is proof?

 

[Essasetic]

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.

That still doesn't answer the question why you literally warned nobody about it corrupting exFAT SD cards. "Let it corrupt on its own" isn't an excuse to let people with exFAT SD cards use it then when they screw up get everything deleted.

 

[maxx488]

How do you know? You tested this? Where is proof?

I see him as those hobbos with their " The end is near, theres no hope left" signs on their chests.

 

[Essasetic]

How do you know? You tested this? Where is proof?

The proof is the shitty implementation of exFAT support done by Nintendo. It's been known to corrupt for ages now. And with the scenarios I've given you and garyopa admitting (to an extent) that it can corrupt exFAT SD cards. Do I need anymore proof?

 

[garyopa]

TX emunand causes corruption to exFAT SD cards.

did it for you yet?

Here is test, set it up, on new switch grab like dozen xci files (all legit backups), and dozen nsp games (no homebrew), -- Running emunand without using emulators or cheats, play all dozen xci games, install all dozen nsp games (using sx installer, not tinfoil) and do that for 4 days no stop, and tell me if the exfat card is still working or not.

With our tests it did, infact a week with 7 different switches, only when the use ran emulators or use cheats or press home during nsp install there was corruption, and that still occurred 50% of time on sysnand without emunand.

 

[maxx488]

The proof is the shitty implementation of exFAT support done by Nintendo. It's been known to corrupt for ages now. And with the scenarios I've given you and garyopa admitting (to an extent) that it can corrupt exFAT SD cards. Do I need anymore proof?

Exactly, screw scientific method

 

[johnsnow]

I dont think TX uses Exfat driver from Nintendo. The boot1 had sectormap of eMMC! This is raw sector read/write, not filesystem based

 

[thaikhoa]

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.

It wont be easily corrupted by just pulling out SD while installing game. The one that causes corruption is from ported games as homebrew or emulators. Avoid using them when using exFAT.

 

[Ra1d]

TX emunand causes corruption to exFAT SD cards.

And you base your conclusion on a tweet by hexkeyz... Bro, you sound so awkward when someone calls you out and you're just redirecting everything to hexkeyz's tweet, basically saying : "I have no clue what I'm posting, but this guy does, so I'ma keep spamming this nonsense".

 

[Essasetic]

did it for you yet?

Here is test, set it up, on new switch grab like dozen xci files (all legit backups), and dozen nsp games (no homebrew), -- Running emunand without using emulators or cheats, play all dozen xci games, install all dozen nsp games (using sx installer, not tinfoil) and do that for 4 days no stop, and tell me if the exfat card is still working or not.

With our tests it did, infact a week with 7 different switches, only when the use ran emulators or use cheats or press home during nsp install there was corruption, and that still occurred 50% of time on sysnand without emunand.

Have you tested crashes/purposely crash the switch? These can happen at random sometimes.

 

[garyopa]

I dont think TX uses Exfat driver from Nintendo. The boot1 had sectormap of eMMC! This is raw sector read/write, not filesystem based

exfat driver part is used by homebrew when you running apps. -- outside of that sdmmc driver is used for redirection and mapping of raw sectors, you are correct in that area, and that means there is less chance for corruption on its own, still not perfect but its stepping stone in the right direction.

and remember it is beta release, there will be 'stable' release soon, i hope the same people bitching here also bitched to microsoft when their fast-ring windows 10 update start wiping out their data files, or now today's update blocks access to your iCloud.

 

[Essasetic]

I'm getting sick of responding every 30 seconds so I'm going to leave this thread with this.

Ev1l0rd can explain this way better than I can.

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

exfat driver part is used by homebrew when you running apps. -- outside of that sdmmc driver is used for redirection and mapping of raw sectors, you are correct in that area, and that means there is less chance for corruption on its own, still not perfect but its stepping stone in the right direction.

and remember it is beta release, there will be 'stable' release soon, i hope the same people bitching here also bitched to microsoft when their fast-ring windows 10 update start wiping out their data files, or now today's update blocks access to your iCloud.

Ironically the Windows October update actually did wipe a few directory's (documents, videos, pictures, etc.) It deleted everything on those directory's. The more you know.

 

[Deleted-172301]

Another user reported the same issue. Currently no solution from what I've seen. Either wait it out or simply don't use it.

The black screen issue? I'm going to be reviewing this once I get home, but its odd.

 

[Jordan9716]

FYI - for those that want to save space on the micro sd card.

You can remove the following emunand files from your emunand folder:

full.01.bin
full.02.bin
full.03.bin
full.04.bin
full.05.bin
full.06.bin


That will save quite a bit of space, and you can still boot emunand properly - if you have games/updates installed to emunad - they won't work, install to microsd instead (it doesn't matter as they will still take less space up than installing to emunand).

I deleted those folders and now SD emunand isn't recognized and as such doesn't work. This is wrong, you absolutely DO need these files if you want emunand to work.

That said, does anyone know how to revert back to your old emunand? I rather not have the full.01-full.06 bins on my SD card as they take up wayyy too much space.

 

[garyopa]

I deleted those folders and now SD emunand isn't recognized and as such doesn't work. This is wrong, you absolutely DO need these files if you want emunand to work.

That said, does anyone know how to revert back to your old emunand? I rather not have the full.01-full.06 bins on my SD card as they take up wayyy too much space.

I have suggested to team to put back the option (for smaller) emunand, but then it would also not be a full emunand then, as currently it setup to be legit complete emunand without changing partition sizes like before. So not sure if they will add that feature back in.

 

[jakkal]

get a bigger sdcard
stop being cheap

 

[comput3rus3r]

I have suggested to team to put back the option (for smaller) emunand, but then it would also not be a full emunand then, as currently it setup to be legit complete emunand without changing partition sizes like before. So not sure if they will add that feature back in.

I mean options are good. I prefer this emunand as I stayed away from the in Nand emunand. But I'm running this now. So far so good. I did backup my sd card just in case.

 

[Ev1l0rd]

Ev1l0rd can explain this way better than I can.

Side note to anyone here; It's no longer speculation. Hexkyz's tweets basically confirmed said suspicions making it no longer a case of me having to speak in "seems" and letting me say this with absolutes.

This is the same "emuNAND" hackjob from 2.0, just moved to the SD card. Using this will eventually corrupt your SD cards filesystem due to constant read/writes which will if interrupted (which is very easy to occur and can happen on accident) corrupt your entire SD cards filesystem, which if not fixed in time (and it's entirely possible to not notice until it's too late) will corrupt your entire SD card, which will brick your emuNAND and any titles installed on the SD from the sysNAND. A true emuNAND does not risk corrupting the entire filesystem because it exists outside of the filesystem (in free space).

w/r/t Nintendo's driver being shitty licensed from Microsoft, it's only an argument to actually not support the exFAT filesystem, but I can pretty safely say that that probably won't be done given how many users seem to think exFAT is awesome.