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

 

[drizztbsd]

If you have problem with emunand or disappearing files on exfat partition you should remove the archive bit from the files.
To semplify my work I created noattrib.cmd in the root on Switch SD with only the following command inside:
attrib -A /S
So each time I copy a new XCI or I do something on the SD, I only need to double click the cmd before ejecting the sd card from my PC and sx-os always read the files.

It can probably be used on the USB hard disk too, but I don't use it.

 

[CTBC]

Fixed black screen on emunand 5.1.0 by deleting newly created emunand boot0 and boot1 files and replacing with backup boot0 and boot1 files

 

[jakkal]

Tx is sitting on their hands waiting for someone to dump 6.2 keys for them lol.

 

[SpaceJump]

Fixed black screen on emunand 5.1.0 by deleting newly created emunand boot0 and boot1 files and replacing with backup boot0 and boot1 files

Did you use boot0 and boot1 files from a 5.1.0 backup?

 

[CTBC]

Did you use boot0 and boot1 files from a 5.1.0 backup?

Yes

 

[Raymond7]

Tx is sitting on their hands waiting for someone to dump 6.2 keys for them lol.

Agreed, the wait is getting ridiculous

 

[alexj9626]

How big is the EmuNAND suppose to be? The folder with it is about 30gb (maybe more, cant remember) with lots of 3-4gb files (part 1, 2, 3, etc)

I thought it would be 14 or so GB from what people said here.

 

[guily6669]

Tx is sitting on their hands waiting for someone to dump 6.2 keys for them lol.

Is there any ETA already for 6.2 update? Though I don't need it at the moment, my emunand is at 6.1...

I hope TX updates their manuals, it doesn't even say anything about emunand and even folder structures and all the other missing info making everyone have to go into forums to search 4 it which is kinda stupid 4 a paid service...

Edit: BTW does your SD emunand all run a bit slow?

I have a slow M-SD 128GB from Toshiba, I'm waiting for the new Kingston 128GB A1 to arrive to test the difference.

 

[Jaysus88]

Hello guys!
I´ve been looking on the forums for 3 hours and im not 100% sure and want some clarification:

I´m on Sysnand 5.1 and dont have EmuNand. Now i want EmuNand on SD and dont know if this is the right way.
Btw. I have a Backup of my 5.1 Nand and dont want to play online.

Can i only Download newest TX - Activate Emunand - rename Nintendo do Emutendo folder - done ?

And the most important part to me - because i read of some FW 6.2 "unhackable" - can I only update Emunand and let Sysnand on 5.1? Are there any downsides and is it possible via booted Emunand and the official FW Update Option in Horizon?


Thank you all!

 

[scroeffie]

any one know wat cluster size the hdd needs ? i know it has to be formated to exfat and gpt but what cluster size ?

 

[jakkal]

How big is the EmuNAND suppose to be? The folder with it is about 30gb (maybe more, cant remember) with lots of 3-4gb files (part 1, 2, 3, etc)

I thought it would be 14 or so GB from what people said here.

If it's making a 1 to 1 copy of a 32gb sysnand why would it be 14gb?

 

[m4076348]

Is there any way to shrink/trim the emunand files? I love the option to have it sit on SD storage - but also pushed me towards managing SD space quite a lot, recently

 

[comput3rus3r]

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

I've been using it no problems taking the precautions he mentioned. That being said, I have my Msd backed up to my pc.

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

Tx is sitting on their hands waiting for someone to dump 6.2 keys for them lol.

good, I'd rather them focus on improving gui and other sxos features since 6.2 keys will inevitably be dumped by someone else anyway.

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

any one know wat cluster size the hdd needs ? i know it has to be formated to exfat and gpt but what cluster size ?

i used 512 for a 2tb hdd and it worked.

 

[Ranshiro]

Fixed black screen on emunand 5.1.0 by deleting newly created emunand boot0 and boot1 files and replacing with backup boot0 and boot1 files

total noob question. but how did you do this? with hekate? or is it just copy and paste on the sd card directly?

 

[Rabita]

https://team-xecuter.com/about-nint...wB8OHqKmEwrrHjqe7-hueq0TPk-8Sub5TZ_JIVpWjoHQQ

 

[Raymond7]

https://team-xecuter.com/about-nint...wB8OHqKmEwrrHjqe7-hueq0TPk-8Sub5TZ_JIVpWjoHQQ

In other words, they don't know where/how to fix it .

I also get some major creepy vibes from that TX message. It reminds me of the GateWay3DS message:
"For now, please do not update your Emunand until you can read the confirmation of support for 11.3/11/4 here.
Thank you for your patience, more to come very soon."

.... As of current nothing... Hope this is not the case with TX

 

[NeoSlyde]

In other words, they don't know where/how to fix it .

I also get some major creepy vibes from that TX message. It reminds me of the GateWay3DS message:
"For now, please do not update your Emunand until you can read the confirmation of support for 11.3/11/4 here.
Thank you for your patience, more to come very soon."

.... As of current nothing... Hope this is not the case with TX

Let’s not jump into conclusions like that
Let’s wait and see

 

[Greyfux27]

Hello everyone!

I've looked up for this information on the forums but could not find a detailed answer.

When updating my Emunand (I will update it from 3.02 to 5.1) for the first time should I leave the AutoRCM on? If I leave it off is there a risk of burning fuses?

I've never used autorcm just to keep my sysnand as clean as possible

Thanks in advance!

 

[guily6669]

I updated my emunand for the 1st time too and I disabled that option and my Original FW still works fine... But I have seen some people leaving it ON and was still working, so no idea whats best... (Go to album and make sure it says SX OS EMUNAND, don't update the CFW or you will update the console sysnand).

Don't insert is a game cart after updating or it will update the game cart reader and you won't be able to use the original game cart games on your original older FW (I was dumb and inserted my Zelda cart in emunand 6.01 and now the console doesnt even boot on the OFW if the cart is inserted it gives a error, I must remove it).

Hello guys!
I´ve been looking on the forums for 3 hours and im not 100% sure and want some clarification:

I´m on Sysnand 5.1 and dont have EmuNand. Now i want EmuNand on SD and dont know if this is the right way.
Btw. I have a Backup of my 5.1 Nand and dont want to play online.

Can i only Download newest TX - Activate Emunand - rename Nintendo do Emutendo folder - done ?

And the most important part to me - because i read of some FW 6.2 "unhackable" - can I only update Emunand and let Sysnand on 5.1? Are there any downsides and is it possible via booted Emunand and the official FW Update Option in Horizon?


Thank you all!

Inject the SX OS payload, go to options, emunand and create emunand, if it works right away thats all for the emunand (make sure to activate it, where it says boot CFW on SX OS payload, make sure above it says emunand active or something like that).

If the emunand blacks out, copy and paste boot0 and boot1 from hekate backup to SXOS\Emunand (you have to rename boot0 and boot1 from hekate backup to boot0.bin and boot1.bin respectively), and see if it boots...

If you manage to boot to emunand, just use ChoiDijourNX and use FW 6.1, dont use 6.2, but before updating go to the album and make sure it says SX OS EMUNAND (right corner above if im not mistaken).

 

[xs4all]

I updated my emunand for the 1st time too and I disabled that option and my Original FW still works fine... But I have seen some people leaving it ON and was still working, so no idea whats best... (Go to album and make sure it says SX OS EMUNAND, don't update the CFW or you will update the console sysnand).

I thought the purpose of using AutoRCM is so you don't burn a fuse after using ChoiDujourNX to update the FW in Emunand and/or OFW?

Or am I getting my info confused? Unless the info I read was for the older SX OS BETA versions where the Emunand was on the NAND and not the SD CARD?