Only a few days later and here we are with SX OS v2.4.1 from TX.

The release of SX OS v2.4 BETA a few days ago, was very successful, but there was a 'few minor' bugs in it, and Team-Xecuter as usual was quick to listen to feedback and they have now just release v2.4.1 BETA which fixes those minor issues, but that is not all if you read thru the changelog below, you will noticed they have added some cool new functions for all to enjoy, so check it out now!

Hot on the heels of our 2.4 beta release!​

We are happy to bring you a small update which fixes some outstanding bugs and introduces some new functionality.

• Fixed payload menu freeze
  It was reported that since v2.4 the "payload" menu used for launching external payloads was freezing up. This has been fixed, you can now enjoy your external payloads again!
• Fixed installer incompatibility with recent NSP files
  Some recent NSP content (like the Super Smash Bros update) wasn't installable using our NSP installer. All your recent NSP's will work now!
• Firmware 4.1 booting again
  A small regression got introduced in SX OS v2.4 leaving users with a (emunand) firmware on 4.1 unable to boot. We wasted no time to figure out the root cause, and SX OS should now be compatible with every firmware version again!
• White squares on split XCI files
  Some split XCI content was not showing the icons properly, instead rendering a white rectangle. This is a thing of the past now!
• Add support for split NSP files
  We've had support for splitting XCI content for a while now. This is needed for bigger games for people who enjoy SX OS from a FAT32 formatted microSD card. NSP content is now also supported in a split format. The file extensions used should be in the format of: .ns0, .ns1, .ns2, etc.

That's it for this small stopgap release. Keep an eye out for our coming updates!

(As usual, please remember all our latest releases & apps, can be found on our sx.xecuter.com portal website)

--< Team-Xecuter - Rocking the Switch in 2018 and beyond! >--​

Source: MaxConsole

 

[Deleted User]

Hi!
I've been keeping my sysnand on 3.0.1 while upgrading my system memory emunand from 6.0 to 6.1 and yesterday night to 6.2 and all is working great with sx os 2.2 and 2.3 (previously) and now with 2.4 and 2.4.1...
Best of luck!

Yeah I think it was just exfat. I just bit the bullet and formatted it back to fat32 and copied emunand back on and it started working so it is what it is.

 

[Shoruk3n]

What do the install matching Game Updates/DLC Packages do? Being in airplane mode I don't see how the installer can fetch updates or DLC. Anyone tried these options?

 

[TinyBilbo]

What the easiest way to transfer my existing SD Emunand (file) to the hidden partition?

Do I have to backup my Emunand saves, copy my (empty) Sysnand to the new Emunand partition, reinstall all games and updates and then restore the saves, or is there a quicker way?

Thanks

 

[nachuz]

Great update again

Where's the great part? Is just a bug fix
Is like saying that an update on smash patching the isabelle bug is a great update

 

[Wiiunator]

Hey guys, I'de like to report a bug with SXOS 2.4.1. I'm getting error 2144-0001 very often after using SX installer or Tinfoil 0.99. Always happen the same way, I get the "No license found" from the TX menu, go back to main switch menu, re-entre homebrew menu, crash... I've OFW on 5.1.0, Emunand Hidden partition on 6.2.0 (SXOS 2.4.1), 400gb Sandisk SD Card, 1tb toshiba hard drive plugged to the switch via powered USB hub. Anyone else with this?

 

[SuperNintendho]

I try the setup for a hidden emunand partition and it it fails right away saying there is not enough space on my 64GB microsd, even tho it is almost completely empty. Any ideas?

 

[chest0r]

I try the setup for a hidden emunand partition and it it fails right away saying there is not enough space on my 64GB microsd, even tho it is almost completely empty. Any ideas?

yes format your sd card to fat32 and then try to create partitioned emunand in sx menu. Copy all of your content from sd card first!

 

[Deleted User]

Hey guys, I'de like to report a bug with SXOS 2.4.1. I'm getting error 2144-0001 very often after using SX installer or Tinfoil 0.99. Always happen the same way, I get the "No license found" from the TX menu, go back to main switch menu, re-entre homebrew menu, crash... I've OFW on 5.1.0, Emunand Hidden partition on 6.2.0 (SXOS 2.4.1), 400gb Sandisk SD Card, 1tb toshiba hard drive plugged to the switch via powered USB hub. Anyone else with this?

Anything in particular you're doing in SX installer? I've seen something like this when running homebrew that leak resources, usually event handles which are not properly closed.
Because of the leak, eventually it hits the resource limit and everything starts to break down. I'm guessing this is an issue present in both SX installer and Tinfoil.

It could also be thread resource exhaustion. @Wiiunator did you use USB or HTTP install?

 

[guily6669]

Can some great soul PLZ answer my questions:

1- Is it safe to use SX installer? Where does it download\search from?

2- Can I read the new emunand partition with windows explorer?

3- how can I move my current emunand on M-SD to the new partition M-SD emunand?

4- If I create a new emunand partition how can I have my M-SD formatted to exFat if my sysnand is on 3.02 and without the update exFat? (When I created M-SD emunand with SX OS 2.3 I used Fat32, then updated emunand to 6.1 with ChoidijourNX with exFat update, then backed up the emunand, formatted mSD to exFat and put the updated emunand back in it).

Note: I don't want to install exFat update offline on my Original 3.02 sysnand...

 

[Ra1d]

Can some great soul PLZ answer my questions:

1- Is it safe to use SX installer? Where does it download\search from?

Safe. It searches locally, basically, hdd, sd, nand, etc. It doesn't go online to magically install any game you wish, you still need to download all the games. It's just more organized and has more options.

2- Can I read the new emunand partition with windows explorer?

No. It's "locked" you can't open or interact with it at the moment.

3- how can I move my current emunand on M-SD to the new partition M-SD emunand?

You can't migrate your emuNAND at the moment, you will have to install a fresh emuNAND if you want to use the hidden partition option.

4- If I create a new emunand partition how can I have my M-SD formatted to exFat if my sysnand is on 3.02 and without the update exFat?

You can't, you either install the exfat update, or you use a splitter to split your xci's into pieces to fit a fat32 drive.

 

[guily6669]

Safe. It searches locally, basically, hdd, sd, nand, etc. It doesn't go online to magically install any game you wish, you still need to download all the games. It's just more organized and has more options.


You can't, you either install the exfat update, or you use a splitter to split your xci's into pieces to fit a fat32 drive.

But doesn't the app have a auto game updates search and download them?

And about the exFat, then screw that crap, I will keep using M-SD emunand files... Unless maybe after updating the emunand with exFat update, maybe I could rip the whole M-SD data with a hex editor and inject it later on the M-SD formatted as exFat somehow....

 

[Wiiunator]

Anything in particular you're doing in SX installer? I've seen something like this when running homebrew that leak resources, usually event handles which are not properly closed.
Because of the leak, eventually it hits the resource limit and everything starts to break down. I'm guessing this is an issue present in both SX installer and Tinfoil.

It could also be thread resource exhaustion. @Wiiunator did you use USB or HTTP install?

Hey mate. Thanks for the reply. Now that you mention it, there is the possibility that the issue occured when I closed the app with the home button instead of exiting it the proper way... in saying that I’m also pretty sure this happened to me also when I launched the app through TX hold R option which gives access to the full memory.

I have checked on the team executor forum and it seems of few people had the issue, even the forum admin guy had it and reported the issue to TX. I will try to avoid quitting the app the “wrong” way and see if it still occurs.FYI and only used the USB install

 

[Deleted User]

Hey mate. Thanks for the reply. Now that you mention it, there is the possibility that the issue occured when I closed the app with the home button instead of exiting it the proper way... in saying that I’m also pretty sure this happened to me also when I launched the app through TX hold R option which gives access to the full memory.

I have checked on the team executor forum and it seems of few people had the issue, even the forum admin guy had it and reported the issue to TX. I will try to avoid quitting the app the “wrong” way and see if it still occurs.FYI and only used the USB install

OK well there is the culprit: USB. Libnx has a bug in USB handling that prevents proper cleanup for event handles.

 

[Wiiunator]

OK well there is the culprit: USB. Libnx has a bug in USB handling that prevents proper cleanup for event handles.

Right... if it’s a libnx issue, am I correct in thinking it’s not really something that is fixable by TX then is it? Do you know any possible way to minime the issue from happening? In saying that I have used the old TX built in installer in the past to install @400gb worth of NSPs in one go without an issue... never ever crashed on me using USB. Tried to do the same here with TX installer overnight and I woke up to a crashed console... still installed about 90% of my NSPs though.

 

[Deleted User]

Right... if it’s a libnx issue, am I correct in thinking it’s not really something that is fixable by TX then is it? Do you know any possible way to minime the issue from happening? In saying that I have used the old TX built in installer in the past to install @400gb worth of NSPs in one go without an issue... never ever crashed on me using USB. Tried to do the same here with TX installer overnight and I woke up to a crashed console... still installed about 90% of my NSPs though.

Can't help you there. We just have to wait for someone to fix it

 

[atrocious123]

I asked this in another chat but would like to know from here too. Can anyone give me a clarification on all the updates?

Hi guys, i have updated my switch to 6.1 without burning fuses. My NAND backup was at 4.1 iirc. Now that i think about it, i dont really think there's any advantage of keeping a low fuse fw and would like to know if there's any advantages?

I've been thinking of burning my fuse to OFW 6.2 and then SX OS w/ emuNAND partition and using all of the features in emuNAND. Can i check that whatever i do in emuNAND is separated from OFW which means i could install NSP and not get detected?