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.

aos10

Yuuki chan
Member
Joined
Apr 10, 2012
Messages
4,756
Trophies
2
Age
38
XP
4,029
Country
Saudi Arabia
hmmm, when i press the external payload in SX menu, the system is freeze.

edit: i see, they know about that.
"- External Payloads: This is completely broken in 2.4. Your switch will freeze when you tap the option. Sorry about that. It was quickly corrected in the "in house" build and will be fixed in the next release."
 
Last edited by aos10,

guily6669

GbaTemp is my Drug
Member
Joined
Jun 3, 2013
Messages
2,333
Trophies
1
Age
34
Location
Doomed Island
XP
2,098
Country
United States
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.
Well the warmboot goes up to 4.1 and who knows if they might make it almost as good as coldboot...

I'm still using Gateway warmboot on my 3DS and I never cared for the more newer software coldboot exploits because it's just too easy and fast to launch Gateway that I never cared and I updated the emunand with some offline files beyond any supported GW update which is now dead...

Ps: anything is better than having to connect or install a device to inject the payload every single boot...
 
Last edited by guily6669,
  • Like
Reactions: Bumblecito

Bumblecito

Well-Known Member
Member
Joined
May 25, 2017
Messages
108
Trophies
0
Age
38
XP
404
Country
Mexico
So my switch's firmware is 4.1.0 I already know that sx os 2.4 is not compatible with that firm, but what if I update to 5.0.0 via ChoiDujourNX without burning fuses, create emunand, then go back sysnand to 4.1, could it work? Should I give it a try?
 

Deleted member 129634

Well-Known Member
Member
Joined
Jun 30, 2008
Messages
151
Trophies
0
XP
722
Country
United States
So my switch's firmware is 4.1.0 I already know that sx os 2.4 is not compatible with that firm, but what if I update to 5.0.0 via ChoiDujourNX without burning fuses, create emunand, then go back sysnand to 4.1, could it work? Should I give it a try?
You can go back to whatever you want if your fuse count allows it, just back up your nand and restore it when you want to go back, just be careful with your fuses
 

xabier

Well-Known Member
Member
Joined
Dec 10, 2006
Messages
577
Trophies
0
XP
1,202
Country
United States
So my switch's firmware is 4.1.0 I already know that sx os 2.4 is not compatible with that firm, but what if I update to 5.0.0 via ChoiDujourNX without burning fuses, create emunand, then go back sysnand to 4.1, could it work? Should I give it a try?
Probable, you dont need internal nand when you boot sysnand
 

Krazyeye

Hellooo Nurse!
Member
Joined
Aug 5, 2017
Messages
207
Trophies
0
Location
Mighty Jungle
XP
1,103
Country
Korea, South
My Switch was in OFW6.0 + SXOS2.3b for awhile. Here are steps I took to update my system firmware and SXOS2.4b:

Note: I do not plan on going online nor using online services from big N. I do not use AutoRCM nor Emunand.
1. Boot my switch to OFW6.0 then updated firmware via internet (official big N server)
2. Once downloaded and installed, powered off my switch then boot into SXOS2.4b (typical RCM payload blah blah)
3. SXOS2.4b works without any problem. SXOS Installer works as supposed to. I was able to install NSP updates for Smash, Diablo 3, Xenoblade Chronicles 2, etc. And they all loadup without any issues.
4. Oh, and the Sleep Mode works too.
 
Last edited by Krazyeye,
  • Like
Reactions: Frexxos

urherenow

Well-Known Member
Member
Joined
Mar 8, 2009
Messages
4,778
Trophies
2
Age
48
Location
Japan
XP
3,675
Country
United States
Well the warmboot goes up to 4.1 and who knows if they might make it almost as good as coldboot...

I'm still using Gateway warmboot on my 3DS and I never cared for the more newer software coldboot exploits because it's just too easy and fast to launch Gateway that I never cared and I updated the emunand with some offline files beyond any supported GW update which is now dead...

Ps: anything is better than having to connect or install a device to inject the payload every single boot...
umm... 3 things

1) There is no public warm or cold boot method that doesn't require hardware. At all.
2) None of the Gateway stuff is relevant. At all. And 3DS stuff in general (still not relevant) is all coldboot, unless you made a personal choice to not update to b9s (or a9lh, for that matter). All I need to do is turn on the 3ds, and it loads Luma. If I hold Down when I power on, Gateway boots.
3) The lowest backup the OP has is 5.0. So none of your post is relevant, even if you choose to believe that this phantom cold boot thing will come out, and work on 4.1.
 
Last edited by urherenow,
  • Like
Reactions: comput3rus3r

robbros

Well-Known Member
Newcomer
Joined
Jun 24, 2015
Messages
83
Trophies
0
Age
26
XP
500
Country
Italy
i'm on 6.2 sysnand and using sx os 2.4 on 6.1 emunand. sleep mode won't work. what do i have to do?
 

fringle

Well-Known Member
Member
Joined
Apr 16, 2009
Messages
704
Trophies
1
XP
1,107
Country
Canada
How do you guys boot OFW when you want to go online? Just power down the unit and reboot without the dongle?

I usually full power off and remove my sd card as well just to be safe. Never know if the big N will implement the ability to see whats on it.
 

guily6669

GbaTemp is my Drug
Member
Joined
Jun 3, 2013
Messages
2,333
Trophies
1
Age
34
Location
Doomed Island
XP
2,098
Country
United States
umm... 3 things

1) There is no public warm or cold boot method that doesn't require hardware. At all.
2) None of the Gateway stuff is relevant. At all. And 3DS stuff in general (still not relevant) is all coldboot, unless you made a personal choice to not update to b9s (or a9lh, for that matter). All I need to do is turn on the 3ds, and it loads Luma. If I hold Down when I power on, Gateway boots.
3) The lowest backup the OP has is 5.0. So none of your post is relevant, even if you choose to believe that this phantom cold boot thing will come out, and work on 4.1.
You got it wrong...

I was talking for the people on 4.1 and below...

The exploits are known to exist but we still need people to fully leak the 2 known and get a good way to use them. They don't require hardware...

And it's not all about coldboot, the warmboot can be good too depending on what we have to do to use it.

GW original emunand is warmboot and no, I never updated to the newer exploits neither I care, I just have to press settings and profile, not a big hassle for this warmboot method on the 3DS...
I believe your emunand needs to be 6.2 also (correct me if i'm wrong).
Yep I think that's it, because he has more e-fuses burned on the console (sysnand) than on the emunand...
How can I convert\move my current emunand on the M-SD created with SX OS 2.3 to the new formatted partition?

Can I just read it on the PC without any program and just move my emunand files?
BUMP!

Can someone plz respond to my above quote, though I won't use SX OS 2.4 since my sysnand is at 3.02 and I won't update it...
 
Last edited by guily6669,

noreason4

Well-Known Member
Newcomer
Joined
May 17, 2016
Messages
99
Trophies
0
Age
45
XP
751
Country
United States
Quick question regarding the Installation of NSP files: In tinfoil (the one without a GUI) you can choose wether you want to install on SD or NAND. Now that we have EMUNAND on a hidden partition (that takes 30 GB off the actual side of the sd) I wonder, wether tinfoil might install on this hidden EMUNAND partition when its started while being in EMUNAND and NAND is selected as destination instead of SD
 

guily6669

GbaTemp is my Drug
Member
Joined
Jun 3, 2013
Messages
2,333
Trophies
1
Age
34
Location
Doomed Island
XP
2,098
Country
United States
Quick question regarding the Installation of NSP files: In tinfoil (the one without a GUI) you can choose wether you want to install on SD or NAND. Now that we have EMUNAND on a hidden partition (that takes 30 GB off the actual side of the sd) I wonder, wether tinfoil might install on this hidden EMUNAND partition when its started while being in EMUNAND and NAND is selected as destination instead of SD
After loading emunand everything installing\installed in system storage\nand = emunand...

You never really lose the 30 something GB because you can use most of the space to install games\updates\DLC... So you mostly only lose the OS size for emunand which I don't know exactly how much it is...

If I'm wrong plz someone correct me!
 
  • Like
Reactions: Bumblecito

Bloodlust

Well-Known Member
Member
Joined
May 25, 2006
Messages
1,122
Trophies
0
Website
Visit site
XP
609
Country
Hong Kong
My Switch was in OFW6.0 + SXOS2.3b for awhile. Here are steps I took to update my system firmware and SXOS2.4b:

Note: I do not plan on going online nor using online services from big N. I do not use AutoRCM nor Emunand.
1. Boot my switch to OFW6.0 then updated firmware via internet (official big N server)
2. Once downloaded and installed, powered off my switch then boot into SXOS2.4b (typical RCM payload blah blah)
3. SXOS2.4b works without any problem. SXOS Installer works as supposed to. I was able to install NSP updates for Smash, Diablo 3, Xenoblade Chronicles 2, etc. And they all loadup without any issues.
4. Oh, and the Sleep Mode works too.
Is your switch banned? Does ninty still let you update to 6.2 if it is?

Sent from my MI MAX 3 using Tapatalk
 

Bloodlust

Well-Known Member
Member
Joined
May 25, 2006
Messages
1,122
Trophies
0
Website
Visit site
XP
609
Country
Hong Kong
I think there's a glitch on the tx forums now. Whenever I try to access page 2 in their forums it's reporting as not found
83afc794028947f9e44f1753427f5ce4.jpg


Sent from my MI MAX 3 using Tapatalk
 

M7L7NK7

Well-Known Member
Member
Joined
Oct 16, 2017
Messages
3,902
Trophies
1
Website
youtube.com
XP
5,970
Country
Australia
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.

Sorry about your fuses
 
  • Like
Reactions: Bumblecito

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    K3Nv2 @ K3Nv2: I'll just pretend like I know what's going on