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

 

[jonesy101]

I have a question about emunand.

If I create one on the hidden partition, do I still need the Emutendo folder in the root of the SD card?

 

[jakkal]

I have a question about emunand.

If I create one on the hidden partition, do I still need the Emutendo folder in the root of the SD card?

Yes emunand uses that folder. It creates it automatically

 

[HardMind]

I installed emuNand in sd card, and update it to 6.2.
Is it normal that, Emunand on sd card slowly in responding by almost 2 times compared to SysNAND or there is somthing i dont do it well?

 

[jonesy101]

Thanks for the reply!

I did not know that SXOS creates that Emutendo folder. I just made a copy of the Nintendo folder and renamed it Emutendo like I did for SXOS 2.3.

Yes emunand uses that folder. It creates it automatically

 

[Huge_Heffner]

Does that Emutendo/Nintendo folder contain system settings? Or is it only game related content?

 

[Sir]

can i install NSP files to an external drive and have them run fine

 

[Wezaa]

The just need to delete the old console fingerprint in their servers and replace it with the new one. Done, I got banned with previous console and had to buy a new license because of their greediness

Erm, you would still have the licence.dat file. So deleting the fingerprint on their server would archive a grand total to fekall..

 

[jakkal]

Erm, you would still have the licence.dat file. So deleting the fingerprint on their server would archive a grand total to fekall..

???
i mean if they delete the footprint from their sever all you would have to do is generate a new license.bat



obviously

 

[Wezaa]

???
i mean if they delete the footprint from their sever all you would have to do is generate a new license.bat



obviously

I mean in therms of TX preventing you from abusing their license system....

If they delete the FP, he can make a new licence.dat, BUT he will still have the licence.dat for the old console, so 2 licences for the price of one, which TX obviously aren't going to do.

They have no proof you have deleted your old license.dat.

 

[jakkal]

I mean in therms of TX preventing you from abusing their license system....

If they delete the FP, he can make a new licence.dat, BUT he will still have the licence.dat for the old console, so 2 licences for the price of one, which TX obviously aren't going to do.

They have no proof you have deleted your old license.dat.

SX OS could call home to verify the license footprint

 

[rrocha]

SX OS could call home to verify the license footprint

But that would reflect on all of us having to be online for each boot (or whenever the call home code triggers).
And lets be honest: forking 25 bucks one time for "all available games" is not that steep. I know everyone's wallet is different, but come on: you have a 300 bucks gaming machine and each new game costs at least double the price of 1 SX license... If integrated XCI loading + USB HD + emuNAND (just to state the major unique features) isn't worth the price of admission for someone, we can always go with the free alternatives

 

[jakkal]

But that would reflect on all of us having to be online for each boot (or whenever the call home code triggers).
And lets be honest: forking 25 bucks one time for "all available games" is not that steep. I know everyone's wallet is different, but come on: you have a 300 bucks gaming machine and each new game costs at least double the price of 1 SX license... If integrated XCI loading + USB HD + emuNAND (just to state the major unique features) isn't worth the price of admission for someone, we can always go with the free alternatives

If people want license transfer so bad they have to give up some convenience

 

[ken28]

Thinking of upgrading my SD CARD to something bigger, currently have EmuNand as a hidden partition on the SD CARD. Is there anyway to clone/copy/etc.. this partition to a new SD CARD? Or do I have to start over and do another EmuNand setup?

just use a tool that clones entire SD cards.

 

[Wezaa]

If people want license transfer so bad they have to give up some convenience

And those of us who don't want to transfer licensen and aren't stupid enough to try and play online with a switch that has been running CFW will also suffer.
Having to be always online to verify the fingerprint/license would be shit for a handheld console that you take out of the home with you.

 

[RitchieRitchie]

Looking for confirmation to check that I'm doing this right? I want to update my 5.1 switch to the latest fw. I'm using sxos pro. So these are the steps I am planning to take:
1. Update my sxos to latest version via the update feature in the album. Switch off and re-enter cfw.
2. Transfer 6.2 files to a 'firmware' folder on my sd card via ftp.
3. Transfer ChoidujourNX.nro to my sd card via ftp.
4. Load ChopidujourNX.nro and select fw to update with ex fat option (haven't used this before but assume it's fairly obvious?)
5. The switch should now be on 6.2 with ex fat? Do I need to switch off the console and re-enter cfw? I'm not bothered about burning fuses (there doesn't seem to be much point as i have no plans to downgrade etc - unless i am missing something?) do I have to select burning fuses in choidujour before updating?

Appreciate any help!

EDIT: To use the new installer, do i simply download it, put it on my sd card and then access it from the album to install nsp files etc?

 

[Bonovox40]

Just curious, is there any negative reason to update to 6.01 fw, (from 5.x) instead of 6.2? I usually like to wait awhile to update to latest, just in case there's some delayed issues found out with brand new OFW updates. I'm don't want to keep having to bypass firmware checks for titles, and I understand newer titles require 6.x to work properly anyway.
Will moving up to 6.01 be enough at this point in title/dlc fw requirements and such?

 

[nexxusty]

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

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!

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

No KIP support?

Jesus TX, can you take a fucking hint or what? Smash is out and everyone who wants to play it online, can't with your OS ONLY. THE ONLY PAID ONE!!!! At least tell us if it's coming or not. You had two things to do, 6.2 and KIP. Nothing else was worth your time. So foolish.... It's really frustrating.

Pretty much done with you chumps. Likely the last time I ever buy anything TX or support you in any way.

GaryOPA is a TX shill now? Or owner. That's sad dude. I remember when you were a respected Xbox 360 firmware modder. This?

Lol. Wow.

 

[JoeBloggs777]

I have the version of pong with the paddles that must have been from 1976 (i think?) Found it the other day in my parents attic. Not tried it but I bet it would still work!

it was probably made by binatone

 

[rory2005]

Ooooh you are angry. Didn't know TX had been informed this was on there schedule and had to be implemented by now, So you dont like the bug fixes then on an interim BETA release?

 

[Sunnyboy]

Hi,
i have update the switch to 6.2, use mine licence.dat and the switch boot in rcm and see everything, but now i got a new licence.dat for that switch, now when i boot with the power + the switch boot, see for 2 second the menu and the switch goes to the cfw, i can you everything but no payload menu of nand menu, is this a bug or ?

 

[JJTapia19]

Please add fixed sleep mode for downgraded fw with burned fuses on the next release. That way if a new firmware comes out. We can update sysnand burning fuses and leave emunand on the older firmware without loosing sleep mode until you tell us it's ok to update again. Hekate 4.6 figured it out so please credit the open source devs responsable to avoid having more drama related post. Thanks for your amazing continued support.