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

 

[nero99]

Is it normal for sd EmuNAND to have the old sleep function bug? I have my EmuNAND on 6.1 and sysnand on 6.2.

 

[jakkal]

Is it normal for sd EmuNAND to have the old sleep function bug? I have my EmuNAND on 6.1 and sysnand on 6.2.

Yes

 

[garyopa]

Would you please please be able to send me the 2.2.1 beta as I am unable to find it and need to boot into an emunand created on the sysnand to enable exfat so then I can move the emunand to sd card using 2.3

Older versions are available here:

https://team-xecuter.com/forums/threads/155006-SX-OS-BETA-Downloads-Discussion

 

[lufeig]

Is it normal for sd EmuNAND to have the old sleep function bug? I have my EmuNAND on 6.1 and sysnand on 6.2.

yes, it is normal when you emunand requires a lower "burnt fuse count" than it finds in the system.

in other words, when you officially updated your sysnand to a higher firmware than your emunand's.

 

[nero99]

Yes

yes, it is normal when you emunand requires a lower "burnt fuse count" than it finds in the system.

in other words, when you officially updated your sysnand to a higher firmware than your emunand's.

thank you both for the answers.

 

[guily6669]

Bump!

And to update this SD emunand if I buy SX OS, I create a SD emunand and still have to use ChoiDujour trough emunand and chose the FW I put in the M-SD and update trought there or does TX have a better method built-in?

Also if I'm updating M-SD emunand do I still have to apply the option so it doesn't burn efuses that activate auto RCM or I can just skip it?

Ps: I'm on 3.02 if I even remember well and want my console to stay there 4 ever or maybe downgrade to 3.01 as it shares the same e-fuse...

 

[Hellboybeats]

Okay.... could anyone help me set up an emunand on my sd card from a nand back up manually , or do I really hve to create an emunand through sx os , from what I understand , it’s just a nand back up in the right directories on your sd card , is this correct ? And could anyone perhaps show me exactly what the nand back up must look like on your sd card to work as an emunand

 

[comput3rus3r]

Okay.... could anyone help me set up an emunand on my sd card from a nand back up manually , or do I really hve to create an emunand through sx os , from what I understand , it’s just a nand back up in the right directories on your sd card , is this correct ? And could anyone perhaps show me exactly what the nand back up must look like on your sd card to work as an emunand

I don't' think that's how it works. sx-os creates a nand image for emunand split in a specific way. I could be wrong.

 

[Hellboybeats]

I don't' think that's how it works. sx-os creates a nand image for emunand split in a specific way. I could be wrong.

Ahhh I figured so , so my current issue is.... I just restored a 6.1 back up with no exfat support , I booted sx os 2.2.1 to create an emunand on the sysnand but I want to move it to sd so I can restore my 6.2.0 current nand back up so I have the 6.1.0 emunand on the sd and I’m on my current sys nand again , but am I able to do this without some how enabling exfat support on my 6.1 back up without booting ofw ? If anyone could help me pls

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

Does the sx os boot loader require exfat update to support exfat and move the nand to the sd card , or is there a way to enable exfat without booting it to ofw since iv “downgraded”

 

[Andalitez]

Ahhh I figured so , so my current issue is.... I just restored a 6.1 back up with no exfat support , I booted sx os 2.2.1 to create an emunand on the sysnand but I want to move it to sd so I can restore my 6.2.0 current nand back up so I have the 6.1.0 emunand on the sd and I’m on my current sys nand again , but am I able to do this without some how enabling exfat support on my 6.1 back up without booting ofw ? If anyone could help me pls

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

Does the sx os boot loader require exfat update to support exfat and move the nand to the sd card , or is there a way to enable exfat without booting it to ofw since iv “downgraded”

Nope SX boot menu doesn't require OFW to have exFat to read an exFat sd

 

[robbros]

hi guys i just created an emunand and it took like 32 gb, even if i only have 5gb used on sysnand. i read i can choose emunand storage (10-15-20..gb) in advanced options but i cant find the option on sx os 2.3, what do i have to do?

 

[Hellboybeats]

Nope SX boot menu doesn't require OFW to have exFat to read an exFat sd

Thanks for the help I ended up figuring this out once I created the nand and tried to move it to the sd , so now I should be able to restore my 6.2.0 nand and sxos 2.3 should boot from the emunand on the sd card card correct ?

 

[Khar00f]

SD corruption issues since TX chose not to partition the SD for emuNAND. There has been lots of discussion about it lately.

It's crazy the amount of fear and blame you guys have towards TX, go spread your propaganda elsewhere and educate yourself instead.

oh there are corruption issues with emuNAND? what kind of ? game dissappear not loading or saves not working?
also yes i dont have anything in ofw

Forget about what the guy above said, partitions have nothing to do with corruption nor prevent them for that matter. There is a chance of corruption in the event where you close an app and it's in the middle of writing something to the mSD then the card can get corrupted (it's the equivalent of pulling your usb stick out of your pc while you're writing files on it). You can take steps to help avoid that by simply making sure before you shut down a suspended software that it's it's not saving or loading.

The biggest worry is homebrew like emulators, when you're done playing just make sure to save state and exit the emulator by the regular options menu before loading anything else.

If you follow these steps you should be able to prevent corruption just as I and many others have.

Hope that helps

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

Seems I cant create an emunand on my SD.
it takes very long to get to 10% whether its exFAT or FAT32.
I used 2.2.1 to create an internal one and try migrating with 2.3 as well, no dice.

Im wondering if its my SD card thats the problem.Unfortunately dont have another one I can test with.

What do you guys use to format 64GB+ cards?

You can use Rufus (open source) a great app for formatting and it provides option to scan you mSD in the same process to make sure there's no issues with it.

Also the process that you're describing is it the NAND backip or just the creation of the EmuNAND?

Because the backup does take a long time to process, if you're doing the backup, I would recommend you do it using Hekate instead of SX (just my opinion).

I don't remember how much time it took for my EmuNAND to get created but my NAND was empty so it wasn't that big to start with.

Keep us posted,

Good luck,

 

[WiiUBricker]

@leonmagnus99 Don’t listen to the misinformed fanboy above, for the sake of your mSD data.

 

[tinkle]

For the hundredth time, the data corruption has to do with exfat formatted SD cards due to Nintendo being awful programmers. Nothing to do with TX or SXOS.

 

[bundat]

I was thinking...

Just when SX finally comes out with an SD card based emunand (which many people were hoping to use to have a dirty emunand to play backups with, while having a clean sysnand for online play/eshop)...

Nintendo suddenly releases a new FW that not only breaks all CFW (so that you can't use it in emunand), but also BURNS A FUSE (breaking any lower FW version emunand's sleep mode, if you want the latest sysnand for online).

After Xecuter worked all that time to get their SD emunand to work, the "perfect setup" barely lasted a day before getting marred with the "broken sleep mode" disadvantage.

If I were a part of Team Xecuter, I'd feel terrible lol. They were probably rushing it hoping to get quite a few sales by being the first and only to have this feature, just to get it gimped within a day by Nintendo.

 

[Michael Morsette]

Personally the sleep mode issue is minor for me. I boot CFW for homebrew and reboot to OFW for online play. For me SXOS is perfect, even with its flaws it does what I need it to do dispite everything Nintendo has thrown at it.

 

[lilnoob]

I can not boot with an exfat formatted sdcard, only fat32. With which tool can I format the sdcard into exfard and use it with sx os? What is the right folder structure to use?

 

[Andalitez]

You can use Rufus (open source) a great app for formatting and it provides option to scan you mSD in the same process to make sure there's no issues with it.

Also the process that you're describing is it the NAND backip or just the creation of the EmuNAND?

Because the backup does take a long time to process, if you're doing the backup, I would recommend you do it using Hekate instead of SX (just my opinion).

I don't remember how much time it took for my EmuNAND to get created but my NAND was empty so it wasn't that big to start with.

Keep us posted,

Good luck,

Thanks for that Rufus tip.
Will give it a go.

Its actually taking super long to create the emunand. I assume it's dumping the sysnand (I did a restore so it's a fresh system) yet when it's part of the process creating the Emunand on the SD card it dumps boot0+boot1 very quickly then starts dumping the raw nand. This process takes really long (still part of the Emunand creation on my device). The percentage varies from time to time but it seems to take really long regardless.

I let it run overnight, I got 16gb worth of files,but I don't know how many files should be in sxos/Emunand because the switch lost power during the night. I don't know if the process failed or not

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

I have the following files in my sxos/emunand folder
boot0.bin - 4096KB
boot1.bin - 4096KB
full.00.bin - 4194 176KB
full.01.bin - 4194 176KB
full.02.bin - 4194 176KB
full.03.bin - 4194 176KB
full.04.bin - 0KB

Is that correct?Clean sysnand on OFW 5.1.0 with nothing installed
The total is 16GB, should it be 29.1GB?

 

[nxci]

Thanks for that Rufus tip.
Will give it a go.

Its actually taking super long to create the emunand. I assume it's dumping the sysnand (I did a restore so it's a fresh system) yet when it's part of the process creating the Emunand on the SD card it dumps boot0+boot1 very quickly then starts dumping the raw nand. This process takes really long (still part of the Emunand creation on my device). The percentage varies from time to time but it seems to take really long regardless.

I let it run overnight, I got 16gb worth of files,but I don't know how many files should be in sxos/Emunand because the switch lost power during the night. I don't know if the process failed or not

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

I have the following files in my sxos/emunand folder
boot0.bin - 4096KB
boot1.bin - 4096KB
full.00.bin - 4194 176KB
full.01.bin - 4194 176KB
full.02.bin - 4194 176KB
full.03.bin - 4194 176KB
full.04.bin - 0KB

Is that correct?Clean sysnand on OFW 5.1.0 with nothing installed
The total is 16GB, should it be 29.1GB?

There should be a few more. I think 10 files in total. I think there may be some issue with your sd. It should take just an hour or so. If the SD is that slow, I wonder how it will run later. You should be able to boot up even though you are missing a few files. Give it a try and see if you need to get yourself a different card