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

 

[JJTapia19]

So I'm pretty sure this setups works but just to extra carefull, has someone tested this setup? Sysnand clean updated to 6.2 and sx sd emunand on 6.1. Logic says it should work I know. Just want to know if someone is already using that same setup and everything is fine. Thanks in advance!

 

[jakkal]

So iI' I pretty sure this setups works but just to really sure has someone testes this setup? Sysnand clean updated to 6.2 and sx sd emunand on 6.1. Logic says it should work I know. Just wnat to know if someone is already using that same setup and everything is fine. Thanks in advance!

others have confirmed it working

 

[JJTapia19]

others have confirmed it working

Awesome. Thanks.

 

[jakkal]

Awesome. Thanks.

i would recommend not to update yet if you dont have to

 

[Ev1l0rd]

They will always say that because they are intellectually challenged trolls. They do nothing but technobabble about things they don't understand. They bring nothing to the table except "Pikabrickers" and "how to guides". I mean, look at the websites linked in @Ev1l0rd 's signature. One's broken and the TX Hate one is formatted so poorly that it is bearly readable.

emunand = emulated nand.

What's broken about my signature?

There's a single outdated domain that I didn't replace (since I don't heavily frequent this site and don't often have to update my signature), which I just did.

The TX Hate one is my blog '_>' . It's neat and cleanly formatted.

In addition, I have two released pieces of Homebrew for the 3DS and one Homebrew for the Nintendo Switch as well as being the former maintainer of freeShop.

You on the other hand have no such technical skill or knowledge to show for yourself and yet you are the one accusing me of not knowing stuff? I don't like flaunting my knowledge or skills like this, but quite honestly, if you're gonna shittalk me with "he obviously doesn't know stuff", at least give some indication that you're not being someone elses mouthpiece and actually toss some more founded shade.

So please, I ask you. Who is the intellectually challenged troll here? The one that is currently trying to associate me with a dude that bricked devices based on the idea of "we both don't like TX" (while forgoing that that guys reasoning was based on the idea that a certain site was stealing his dumps and not even closely related to TX) or me, the one that has been making reasonable, well founded arguments against TX ever since this started.

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

....so hypothetically.... lets say TX announces and releases a solution to the patched switches, and also gets this 6.2.0 situation resolved..... will your view on TX change at all, or are you destined to just be a gbatemp TX hater forever?

I'd give them that if they were the ones that could pull it off. Unfortunately for them, they don't have any historical capability to pull this off that gives me any hope that they can do it.

It wouldn't change my view on them stealing code however.

 

[JJTapia19]

i would recommend not to update yet if you dont have to

Yeah this update is pretty scary I'll wait a couple of weeks but my intention was to have the sysnand as clean as possible, without autorcm or less fuses that what it's supposed to have. And enter rcm via jig and go to emunand when I want to do the hacky stuff. I think that's the most legit method of having the sysnand as clean and hacks as undetectable as possible for paranoids like me that don't want to get banned. I know I'll probably loose some cool exploits in the future with this method but I don't mind going into rcm via jig when I want to switch nands.

 

[Ev1l0rd]

Technically that bit is free in SX OS, you don't have to pay to use that feature, anyone can use it... I think you pay to use XCI loader? I don't believe I've seen anyone else support XCI loading or even announce they attempted it. I could be wrong, though.

https://gbatemp.net/threads/whats-the-challenge-with-the-xci-loader.520247/page-3#post-8324588

There's apparently legal ramifications in doing so.

 

[Fafner]

others have confirmed it working

And others more state that you can't even reach SX's menu. I didn't try it myself, and I won't until things become more clear. If I were you I'd wait, too many contradictory statements around.

 

[comput3rus3r]

can you create an sd emunand on a fat32 sd card?

 

[jakkal]

can you create an sd emunand on a fat32 sd card?

yes the emunand is created using split files

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

And others more state that you can't even reach SX's menu. I didn't try it myself, and I won't until things become more clear. If I were you I'd wait, too many contradictory statements around.

which is why 2 posts down i recommended not to update
can you scroll down a bit first before rushing to click reply?

 

[mattytrog]

So I'm pretty sure this setups works but just to extra carefull, has someone tested this setup? Sysnand clean updated to 6.2 and sx sd emunand on 6.1. Logic says it should work I know. Just want to know if someone is already using that same setup and everything is fine. Thanks in advance!

Yes. Works perfectly.

 

[tinkle]

thanks to your sides

It's not a war, there're no sides.

 

[comput3rus3r]

yes the emunand is created using split files

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


which is why 2 posts down i recommended not to update
can you scroll down a bit first before rushing to click reply?

ok good. I created one yesterday on a exfat sd card now i'm making one for my other switch that has fat32. I'll test to see if the exfat really does create issues vs the fat32. so far exfat emuand has been working flawlessly.

 

[thaikhoa]

Yes. Works perfectly.

Are you sure about? I heard SX even couldn't boot to emunand when being on 6.2.

 

[mattytrog]

Are you sure about? I heard SX even couldn't boot to emunand when being on 6.2.

You read wrong.

6.2 sysnand, 6.1 emunand works perfectly. Updated 5 consoles today.

Have the dual boot version of my modchip bootloader and stuff.

Yeah. Works well.

 

[fluggy2013]

This update has screwed up both my Switch's 400GB SD and my son's 200GB one. No idea whats going on. Had to format mine yesterday and try and reinstall 400GB of games. Hadn't touched my son's since yesterday ... only thing I did yesterday was update SXOS to latest version on his Switch. Wouldnt turn on after school today. Just put it into PC and his 200GB micro sd now has 180GB of free space. His games disappeared too. Nightmare. Son's wouldnt boot either. His boot.dat and his sx licence have vanished AS WELL AS THE GAMES. Weird coz the folders i put retro roms in for Retroarch and the apps folder I put on are still there. On the plus side (a low highlight) ... his saves are still there! PHEW!

 

[JJTapia19]

Guys. I had the switch from day one and I just made the "switch" from exfat to fat32. I selected on the options fat32 and allocation size 327668. Got all my files back to the card but now I've noticed that when I select the boot emunand option it takes like a good 30 seconds to get out of the sx menu and boot the emunand. After that everything looks good but that haves me worried. Is it normal on fat 32 for that to happen? Should I use another allocation size? The sd card is a good 200gb sandisk one so I'm sure that's not the problem. Any help wold be appreciated.

 

[protomouse]

Yes. Works perfectly.

Did you burn fuses while going to 6.2? If so, did you test going in and out of sleep on 6.1 EmuNAND? I saw someone theorizing about a fuse count check being made when the Switch wakes up, causing it to panic.

Btw, I've been following your modchip thread closely for months and would like to thank you for all the work you put into it.

 

[thaikhoa]

You read wrong.

6.2 sysnand, 6.1 emunand works perfectly. Updated 5 consoles today.

Have the dual boot version of my modchip bootloader and stuff.

Yeah. Works well.

I was wrong, I meant sysnand 6.2 emunand 6.1.

I'll give it a shot. Thanks for the heads up.

 

[Dean_]

I have sysnand 6.2 and emunand 6.1 with 8 burnt fuses (6.1 expects 7 burnt fuses).
I can use 6.2 sysnand without problem. But when I boot emunand 6.1, getting into sleep mode freezes the device.
To avoid burning fuse, I tried to install autorcm right after sysnand update, but SX OS and hekate bootloader was not working sysnand 6.2.
So 7 burnt fuse + sysnand 6.2 combination seems impossible for now..

You read wrong.
6.2 sysnand, 6.1 emunand works perfectly. Updated 5 consoles today.
Have the dual boot version of my modchip bootloader and stuff.
Yeah. Works well.

I trusted this and now I'm screwed.. Sleep mode is broken in emunand!