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

 

[gizmomelb]

SX OS could call home to verify the license footprint

ahhaha so can you imagine the uproar if the SX OS did a call home to verify the licence every time you boot? not to mention with the switch going online, unless you have ALL nintendo servers blocked then you risk the accidental connection with Nintendo and possibly blocking your console?

Think before typing, please.

 

[Wiiunator]

been getting a weird thing with SXOS 2.4.1. I'm on EmuNAND with 6.2.0 intalled. OFW on 5.1.0 When using the TX installer 1.0, or tinfoil 0.99 sometime when wanting to install a game it will go back to the tx License menu. tell me "No License Found", I then have to exit and come back to the menu for it to find the license again and sometime it just crashed the Switch... have to reboot. Wondering if anyone encountered the same issue?

 

[MattKimura]

You mean you turn off your switch? O.o what a total mad lad!

Nah I only turn it off when I'm not gonna use it for a week. Also the switch crashes sometimes for various reasons (Not often though). And I forget to re-enable ftp. When I was busy with classes and writing essays, I had my switch turned off completely.

 

[thaikhoa]

Using exfat too
Tried again and nope not working
Have you made a brand new emunand using 2.4.1 ?

Yes, when testing I created a new emunand. Make sure your nand has supported exfat.

 

[Deleted User]

Anyone tried with a sysNAND lower than 4.1? Have a 3.0.1 console that works fine with either FAT32 or EXFat on 6.1 emu with 2.3, but the 2.4 and 2.4.1 both blackscreen when booting.

 

[wadisnake]

Same here, did you try creating a new nand ?

 

[Regingz]

Anyone tried with a sysNAND lower than 4.1? Have a 3.0.1 console that works fine with either FAT32 or EXFat on 6.1 emu with 2.3, but the 2.4 and 2.4.1 both blackscreen when booting.

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!

 

[wadisnake]

We're both using emunand on microsd.. I guess that's the source of the problem

 

[linuxares]

Curious question about the EmuNAND. If you use anything on the SD card, does it change anything on the Switch itself? To "load this instead". Or does the CFW take care of it all?

 

[TheZander]

Curious question about the EmuNAND. If you use anything on the SD card, does it change anything on the Switch itself? To "load this instead". Or does the CFW take care of it all?

Are you talking about the thing similar to wiiu emunand where you would see channel icons but nothing was actually installed?

 

[linuxares]

Are you talking about the thing similar to wiiu emunand where you would see channel icons but nothing was actually installed?

more or less, but I'm thinking more if boot0 or boot1 is affected. Since it boots a payload first and then does something more. Does it actually editing anything on the nand?

 

[TheZander]

more or less, but I'm thinking more if boot0 or boot1 is affected. Since it boots a payload first and then does something more. Does it actually editing anything on the nand?

I think it brought up when those bricking nsps were around, because they messed with those partitions you mentioned but i can't recall what the consensus was

 

[Rg87]

need help.
bought a banned nintendo switch running 6.2.0
i managed to boot into rcm and inject a payload it said it was successful but immediately turned on normally meaning my system is patched correct?
serial number is XAW100815...
can i buy the sx os dongle and get this to work (BETA 2.4.1 works on OS 6.2.0)
please help!!!!!!!!!!!!!!!!!!!!!

 

[TheZander]

need help.
bought a banned nintendo switch running 6.2.0
i managed to boot into rcm and inject a payload it said it was successful but immediately turned on normally meaning my system is patched correct?
serial number is XAW100815...
can i buy the sx os dongle and get this to work (BETA 2.4.1 works on OS 6.2.0)
please help!!!!!!!!!!!!!!!!!!!!!

You didn't see the tx logo when you booted? So you haven't been able to activate your license?

 

[Rg87]

You didn't see the tx logo when you booted? So you haven't been able to activate your license?

Im such a noob. I am starting off for the first time. I barely managed to boot rcm with the paper clip. I used a test payload to see if it works and it said it did on the switch. But moments later it booted outside of rcm again

 

[guily6669]

How do I enter SX payload menu now? Pressing L doesnt work on this version, it boots straight to emunand created with SX OS 2.3...

 

[JJTapia19]

How do I enter SX payload menu now? Pressing L doesnt work on this version, it boots straight to emunand created with SX OS 2.3...

It was never L, you need to hold volume + at startup.

 

[guily6669]

Oh forget it lol, I couldnt even remember the button since I barely used my Switch and last time I turned it ON was like a week or more ago... .

 

[icyrainz]

I started the CFW game very late when my switch was already on 6.1.0.
Now my sysNAND is on 6.2.0 with SX 2.4.1. Everything seems OK so far. Is EmuNAND needed?

 

[guily6669]

Depends on what you want... Emunand is safer in case you load up something that screw all the software or that can lock the nand with a password or any crap like that, you can simply make a new emunand or load some backup files, while using CFW you may have to recover the whole console and in case its something that makes it lockes with password and you can't read it or some shit like that you will be screwed...

Other than that, emunand is mostly 4 people who want more safety too by using emunand for backups, then completely remove that M-SD from the Switch and load up the console all original with no bad logs so it makes more safty to use the console with both backups and original games for online on Stock\original\horizon\nintendo FW...