Team-Xecuter Presents SX OS v2.4 BETA

It's HERE! - TX Has Finally Done It! - Their SX OS Now Fully Supports v6.2!
SX24.jpg

Everyone been smashing their heads against the wall, and refreshing forums for over two weeks waiting, but no more do you have to wait as SX OS v2.4 is finally available for all Nintendo Switch owners to enjoy, and be able to update to v6.2 finally, its been a long wait, but as you read the change-log below you will quickly see that it was well worth the wait, and there is still more to come soon! :)
We are pleased to let you all know that SX OS v2.4 BETA is ready for release.

First of all, sorry to keep you waiting longer than we initially anticipated. We have been working around the clock to bring you this new release. We want SX OS to be synonymous in your mind with constant quality. We are here to stay and we are here to keep supporting your purchase till end of life.

Now, lets have a look at what v2.4 brings to the table:
  • Support for firmware 6.2.0
    Nintendo threw us a small curve-ball while we were in the middle of reworking some other parts of SX OS. That being said, SX OS is now fully compatible with the latest official firmware 6.2.0.
  • EmuNAND functionality reworked
    Our initial release of EmuNAND used a storage mechanism that wasn't what a lot of people were looking for. In our last release we decided to switch to using the microSD for EmuNAND storage, which in turn made some users that *did* like the old method of storing EmuNAND on the system NAND unhappy. We have reintroduced the support for EmuNAND-on-system-NAND as well as introduced a third storage method for your EmuNAND partition. You can now also opt to use a separate partition (as opposed to files in the regular (ex)FAT filesystem) as a storage backend for your EmuNAND. With three flavors of EmuNAND storage supported now, all of you can rejoice!

    To recap, you now have three way of settings up EmuNAND now:
    • EmuNAND on system NAND: repurpose part of your Switch internal storage for EmuNAND
    • EmuNAND on microSD as partition: repartitions your microSD card with a separate EmuNAND partition
    • EmuNAND on microSD as files: EmuNAND is stored on microSD as files instead of repartitioning
    WARNING: Setting up your EmuNAND as partition on your microSD card will format your microSD card. After setup nothing but the boot.dat and license.dat will remain.
  • Homebrew R button interfering with ingame L+R buttons fixed
    In the last release we introduced a method of invoking the homebrew launcher for any title by holding down the [R] button during application/game startup, this gives homebrew additional capabilities that it wouldn't normally have. However, this seems to have caused some interference with some games, this has been fixed.
  • Embedded Homebrew Menu
    Previously, you had to copy a `hbmenu.nro` file to your microSD card in order to use the homebrew launcher. This has been fully integrated into the SX OS boot.dat file now. Effectively this means all you need for setup is to copy our boot.dat file, simple!
That's all we have for now, people. That doesn't mean we're done. Its not over until we have liberated every single console out there. A lot of our current attention is focused on bringing you a solution for these "unhackable" switches. That does not mean we're not improving SX OS as well. Keep those feature requests and bug reports coming!
Enjoy the festivities this month, and don't forget to pick up a SX Pro / SX OS for your loved ones! :)

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




:arrow: Source: MaxConsole
 
Last edited by garyopa, , Reason: formatting, broken link.

Localhorst86

Robert'); DROP TABLE members;--
Member
Joined
Jul 17, 2014
Messages
2,737
Trophies
1
Location
Nintendo works for my dad
XP
5,349
Country
Germany
I wonder why they couldn't just had made it to where you could use both formats without issue like on a phone or pc. Last thing anyone would ever want is a corrupt file or files because even when you may need to do a chdsk on it the sdcard wont be the same then you have to re-download everything taking up more time smh.
licensing costs. Microsoft holds patents to exFAT and they (nintendo) have to pay extra to use the exFAT filesystem, so any switch that doesn't have that update installed is like $0.20 saved.

When the exFAT update is installed, you can use both FAT32 and exFAT cards.
When it is not installed, you can only use FAT32 cards.
 
Last edited by Localhorst86,
  • Like
Reactions: BATMAN- and CTBC

starbury86

Member
Newcomer
Joined
Jun 28, 2018
Messages
17
Trophies
0
Age
37
XP
314
Country
Germany
Hi guys,

I have a switch on sysnand firmware 4.01 that was never used online. I just played my original Mario Odyssey and Zelda games on it.

When I baught the sxos licence I made a nand backup and then created emunand on a separate sd card. I updated it to 6.1 and right now I have the big sd card for my emunand to play xci and nsp files. The console is just being used offline.

My question is now, if I can update my sysnand with the official update to use my switch online for original games and eshop and if I should deactivate autorcm? I don't really see the advantage of keeping my fuses unburned.

I would like to use a separate sd card for using sysnand to keep it as clean as possible but I don't know if it is better to deactivate autorcm. Can Nintendo detect it? If autorcm is deactivated I would boot the normal system and if I would like to play my backups I would use the jig to enter the sxos menu and boot into emunand with my big sd card.

Is this a good method to keep my switch as clean as possible to avoid a ban?
 

CapoCEO

Member
Newcomer
Joined
Apr 26, 2016
Messages
21
Trophies
0
Location
The blood and heart of the U.S.A.
XP
114
Country
United States
licensing costs. They have to pay extra to use the exFAT filesystem, so any switch that doesn't have that update installed is like $0.20 saved.

When the exFAT update is installed, you can use both FAT32 and exFAT cards.
When it is not installed, you can only use FAT32 cards.

good little switch history lesson!
 

BATMAN-

Well-Known Member
Newcomer
Joined
Jul 13, 2018
Messages
52
Trophies
0
Age
32
XP
642
Country
Poland
Hi guys,

I have a switch on sysnand firmware 4.01 that was never used online. I just played my original Mario Odyssey and Zelda games on it.

When I baught the sxos licence I made a nand backup and then created emunand on a separate sd card. I updated it to 6.1 and right now I have the big sd card for my emunand to play xci and nsp files. The console is just being used offline.

My question is now, if I can update my sysnand with the official update to use my switch online for original games and eshop and if I should deactivate autorcm? I don't really see the advantage of keeping my fuses unburned.

I would like to use a separate sd card for using sysnand to keep it as clean as possible but I don't know if it is better to deactivate autorcm. Can Nintendo detect it? If autorcm is deactivated I would boot the normal system and if I would like to play my backups I would use the jig to enter the sxos menu and boot into emunand with my big sd card.

Is this a good method to keep my switch as clean as possible to avoid a ban?

I am also having headaches about updating from 5.1.0. I don't ever plan on going online with my switch as it is only for offline purposes. I don't know if I should update with choidujournx to 6.1 or directly to 6.2 and whether or not turn auto rcm on to save the fuses from being burned or not...really don't know what to do right now
 

brollikk

Well-Known Member
Member
Joined
Mar 8, 2018
Messages
353
Trophies
0
XP
1,136
Country
United States
I am also having headaches about updating from 5.1.0. I don't ever plan on going online with my switch as it is only for offline purposes. I don't know if I should update with choidujournx to 6.1 or directly to 6.2 and whether or not turn auto rcm on to save the fuses from being burned or not...really don't know what to do right now

I would go to 6.2 directly because you have access to the newest updates for games like smash. As long as your switch is hackable and the newest firmware is supported, why not?
 
  • Like
Reactions: BATMAN-

BATMAN-

Well-Known Member
Newcomer
Joined
Jul 13, 2018
Messages
52
Trophies
0
Age
32
XP
642
Country
Poland
I would go to 6.2 directly because you have access to the newest updates for games like smash. As long as your switch is hackable and the newest firmware is supported, why not?
Do you think it is worth it in my case to save fuses from being burned and thus turn auto rcm on? Appreciate your response
 

urherenow

Well-Known Member
Member
Joined
Mar 8, 2009
Messages
4,777
Trophies
2
Age
48
Location
Japan
XP
3,678
Country
United States
interesting. I remember making a clean nand backup on 5.0.0 so i guess making a 6.0.0 backup would be waste anyway.
If your lowest backup is 5.0, then it’s still not much use trying to save fuses. Even the people who are crazy about saving fuses, are doing it because of some remote possibility that 3.0 might have cold boot CFW someday. I personally don’t see that ever happening though. Above 3, there isn’t even a rumor for something that would justify sweating over the fuses.

(These forums need to support phone emojis already...)
 
Last edited by urherenow,
  • Like
Reactions: comput3rus3r

proffk

Well-Known Member
Member
Joined
Aug 14, 2013
Messages
575
Trophies
1
XP
1,072
Country
United Kingdom
Theres a major bug in this release by TX. SX OS 2.4 beta can not load external payloads. When I try to load external payloads using the boot menu the console freezes. Its has been reported to by other users on TX forums. Guess I will have to use my laptop to power off my NSW with hekate.
 
  • Like
Reactions: CapoCEO

MasterJ360

Well-Known Member
Member
Joined
Jan 10, 2016
Messages
2,801
Trophies
1
Age
35
XP
3,453
Country
United States
Everyone says lower is better. But on OFW 6.0, there is nothing useful from using choidujournx. I personally think there is zero reason to save your fuses for a 3.0 downgrade, but people would argue with me on that. Don’t think many would argue about 6.0 though.

TL;DR
Don’t bother. Just update.
Its b/c ppl are still holding on old hope for a coldboot, honestly the low firmware requirement could change since hacking has gradually evolved since then.
Choidujournx is definitely useless towards 6.2.0 since the update itself checks for the correct number of fuses if ppl care for bans.
 
Last edited by MasterJ360, , Reason: can't spell

Vic_Vinegar

Well-Known Member
Member
Joined
Jun 21, 2018
Messages
112
Trophies
0
Age
38
XP
229
Country
Canada
For those of you who currently have emunand enabled and aren't planning on using the new emunand features that are available on sx os 2.4, then do the following:

Add the latest boot.dat file onto your micro sd card and boot up your switch using the jig and dongle, that's it lol.
Since you didn't touch your emunand settings, it will still operate as it did before you did update to sx os 2.4. My emutnedo folder is still there and I didn't lose any saves.

To upgrade your firmware to 6.2, use choixdujour. If you're worried about burning fuses, on the main screen of choixdujour, you'll see a button that says "Prevent fuse burning (enable AutoRCM)" just make sure that button says enabled and not disabled

I upgraded my switch yesterday and I haven't noticed any issues with it, I even installed a bunch of .nps that required 6.2 to operate and it works fine
 

Bumblecito

Well-Known Member
Member
Joined
May 25, 2017
Messages
108
Trophies
0
Age
38
XP
404
Country
Mexico
My sysNAND is on 4.1.0 when I try to do a clean emuNAND partition I get a black screen when boot from emuNAND, how can i fix it?
 

Vic_Vinegar

Well-Known Member
Member
Joined
Jun 21, 2018
Messages
112
Trophies
0
Age
38
XP
229
Country
Canada
My sysNAND is on 4.1.0 when I try to do a clean emuNAND partition I get a black screen when boot from emuNAND, how can i fix it?
Sadly I cannot help you. My sysnand is on 5.1 but I opted not to do any partitions (nor use any new emunand feature).

I'm sure someone will have an answer for you eventually! sx os 2.4 only came out yesterday so give it time.
 

Ranshiro

Well-Known Member
Newcomer
Joined
Aug 2, 2018
Messages
82
Trophies
0
Age
59
XP
1,129
Country
Japan

comput3rus3r

Well-Known Member
Member
Joined
Aug 20, 2016
Messages
3,580
Trophies
1
Age
123
XP
4,921
Country
United States
Hi guys,

I have a switch on sysnand firmware 4.01 that was never used online. I just played my original Mario Odyssey and Zelda games on it.

When I baught the sxos licence I made a nand backup and then created emunand on a separate sd card. I updated it to 6.1 and right now I have the big sd card for my emunand to play xci and nsp files. The console is just being used offline.

My question is now, if I can update my sysnand with the official update to use my switch online for original games and eshop and if I should deactivate autorcm? I don't really see the advantage of keeping my fuses unburned.

I would like to use a separate sd card for using sysnand to keep it as clean as possible but I don't know if it is better to deactivate autorcm. Can Nintendo detect it? If autorcm is deactivated I would boot the normal system and if I would like to play my backups I would use the jig to enter the sxos menu and boot into emunand with my big sd card.

Is this a good method to keep my switch as clean as possible to avoid a ban?
Get rid of autorcm. Update sysnand officially. create an emunand on a hidden partition on the sd card (new emunand option on 2.4) this eliminates the need to have two separate sd cards.

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

Theres a major bug in this release by TX. SX OS 2.4 beta can not load external payloads. When I try to load external payloads using the boot menu the console freezes. Its has been reported to by other users on TX forums. Guess I will have to use my laptop to power off my NSW with hekate.
I wouldn't call that a major bug when most people are not loading external payloads.
 

metal921

Active Member
Newcomer
Joined
Aug 28, 2018
Messages
41
Trophies
0
Age
31
XP
139
Country
United States
Its b/c ppl are still holding on old hope for a coldboot, honestly the low firmware requirement could change since hacking has gradually evolved since then.
Choidujournx is definitely useless towards 6.2.0 since the update itself checks for the correct number of fuses if ppl care for bans.

Uhhh that’s false I updated to 6.2 sysnand using choidujour and can still play online just fine. No banhammer yet
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • No one is chatting at the moment.
    OctoAori20 @ OctoAori20: Nice nice-