Team-Xecuter Presents SX OS v2.3 BETA

TX is on roll, release after release, and today's big release is brand-new SX OS v2.3 BETA
SX23.jpg

As you read thru TX's announcement below, you will quickly see that is jam-packed with all the features you have been requesting recently like SD EmuNAND and USB Homebrew, so check it out below:
Your favorite superheroes from Team Xecuter are back with another SX OS update.

In v2.3 beta of SX OS we have some exciting new functionality that you, the community, has been requesting a lot. As you know, we value your feedback and support.. so your wishes are our command!

Let's have a look at the changelog:
  • SD emuNAND support
    Since the introduction of our emuNAND feature we got a lot of comments about our initial decision to make the emuNAND data live on the actual system NAND. After lots of hard work we are happy to say we now have a workable solution for storing your emuNAND partition data on your microSD card. This has the upside of not using up any space on your Switch. In order to use the new microSD emuNAND system you will *not* have to format your microSD card. Simply enter the TX boot menu by holding Volume-+ while powering on your switch. Head into the options menu and select emuNAND on the left. Users of our existing emuNAND solution will see an option to migrate their existing emuNAND data. The migration process also cleans up the old emuNAND from the system NAND. Painless! We're interested in hearing your feedback about this exciting new functionality.
  • The 'Emutendo' folder
    In addition to the new microSD emuNAND system we also introduce the 'Emutendo' folder on your microSD card. As you've probably noticed, the Switch saves various data to a 'Nintendo' folder on your microSD card. To completely decouple this data between your Original Firmware and your EmuNAND enabled firmware we have made EmuNAND enabled systems use this differently named folder. If you want keep using your old SD card data with your emuNAND, simply copy/rename the 'Nintendo' folder to 'Emutendo'.
  • Added more directories to scan for content
    By popular demand we have added yet another list of subdirectories that will be scanned on your microSD card (or USB harddisk) for XCI/NSP/homebrew. The directories that have been added are:
    • – /sxos/updates
    • – /sxos/dlc
    • – /switch/updates
    • – /switch/dlc
  • Homebrew menu takeover of any title by holding R
    Homebrew is usually launched from either the TX menu or the Homebrew Launcher menu. Both of these applications run as an 'applet' on the Switch. Applets do not have access to all of the system's memory, and thus any homebrew apps or games launched from here are affected by this as well. The only way to allow full use of the system's memory was to build and install homebrew NSP files. But now we have added another way to give homebrew applications full memory access! You can now hold the (R) button while launching any regular title, and this will launch the Homebrew Launcher Menu. Any homebrew launched from here will run with the same capabilities as a regular Switch game/app. Enjoy!
  • Loading homebrew from USB
    More good news for homebrew lovers. You can now copy homebrew NRO files to your USB harddisk as well, and launch them directly from our SX OS menu.
  • Stability improvements
    Overall stability of many components has been improved. This includes LayeredFS and USB incompatibilities. We have also fixed a bug which would prevent people from launching more than 32 titles.
  • libusbfs update
    Last but not least a small update for developers. We've squashed a small bug in libusbfs pertaining the stat() function. If you had issues with this, grab an updated copy of libusbfs from our website!
The year 2018 is entering its final months. That does not mean we're taking a break from working on our beloved SX OS though. And yes, also those new 'unhackable' consoles are high up on the agenda. Don't worry, we will deliver.

Keep sending your feedback and ideas, they're very welcome.

See you all in the next update!

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

:arrow: Source: MaxConsole
 

Scubahood

Active Member
Newcomer
Joined
Nov 18, 2018
Messages
28
Trophies
0
Age
38
XP
142
Country
United Kingdom
Has anyone noticed on this latest update that it removed the ability to toggle between emunand enabled and disabled? Just booted up my console and it took me into CFW Sysnand. Then rebooted into the SX menu and noticed the toggle was gone. The annoying thing is where I booted into Sysnand all my nsp's on that memory card have now been deleted.
 

fixingmytoys

Well-Known Member
Member
Joined
Jan 4, 2018
Messages
536
Trophies
0
XP
884
Country
Australia
What I would love in the next update is the option to FTP in to the USB hard drive, then I would not have to unplug it just for homebrew etc
 

xerotyme

Member
Newcomer
Joined
Dec 9, 2006
Messages
6
Trophies
0
XP
330
Country
United States
I’m trying to get full system RAM access like it claims it is capable of when running Retroarch but I think I’m doing something wrong. Seeing as how the instructions are a tad vague. I’m clicking on the album icon then tapping the “R” button to get over to the home brew section, then I highlight Retroarch and launch with the “A” button then immediately hit & hold the “R” button. Under the information section in Retroarch it says I have 427/857 MB for memory, the same as if I didn’t attempt this. What am I doing wrong, could someone please help me with this? Thank you very much in advance! :)
 

johnsnow

Active Member
Newcomer
Joined
Oct 7, 2018
Messages
44
Trophies
0
Age
48
XP
145
Country
Australia
I’m trying to get full system RAM access like it claims it is capable of when running Retroarch but I think I’m doing something wrong. Seeing as how the instructions are a tad vague. I’m clicking on the album icon then tapping the “R” button to get over to the home brew section, then I highlight Retroarch and launch with the “A” button then immediately hit & hold the “R” button. Under the information section in Retroarch it says I have 427/857 MB for memory, the same as if I didn’t attempt this. What am I doing wrong, could someone please help me with this? Thank you very much in advance! :)

You need to hold R when launching a GAME, not Album
 

aerios169

Well-Known Member
Member
Joined
Dec 30, 2012
Messages
706
Trophies
1
Age
31
XP
2,225
Country
Mexico
uhmmm i am on 6.1 and 6.0.1 on emunand, so is there any posibility to avoid sleep mode breaks on emunand if i updapte, also i am looking for not burn fuses.
 

Khar00f

Well-Known Member
Member
Joined
Mar 12, 2006
Messages
193
Trophies
0
XP
686
Country
Canada
listen
if you cant do any better just move along if you dont have anything good to say
you cant write your own so what gives you the right to bash others work

go away man...or whatever you are

Hey Jakkal, I'm as much a fan of TX as the next guy and while on most posts your feedback is helpful and diversified when it comes to anyone providing criticism whether positive or negative right away you start trashing their opinion and suggest if they can't do better themselves then to STFU (not necessarily in those words) but along the lines of.

People are allowed and encouraged to share their feedback and provide their opinions on shared hobbies (even when they diverge from ours) on a public forum otherwise we wouldn't have the thriving and diverse communities we have here at GBATemp.

We don't have to be devs or experts to provide feedback on a piece of software that we like or dislike.

While there was a lot of TX hate previously it seems to have mostly died down as of late which is great let's try and maintain that instead of bashing each other at every opportunity.

Just some food for thought, what @Ev1l0rd is referring to for exFat corruption is a valid concern and one that every user should be made aware of, it's not vaporware and one that's made to scare away users, while not everyone experiences corruption it could be simply due to habits that generate it shutting down properly, not playing the same software's etc...

No, I'm not.

I came here to level a valid criticism against their emuNAND (high corruption risk) which is now being nitpicked and twisted by shills and idiots.

Hey @Ev1l0rd thank for your contributions to the community and sharing your awareness, we can never have enough warnings, just looking at how many people didn't backup their NAND with the Pikachu corruption goes to show you can never have enough warnings and people will still manage to miss/skip them until it's too late.


This post is a lot mushier than intended.

TLDR; Can't we all get along even if/when our opinions diverge, let's keep it fun, we're all sharing in the same hobby(ies).

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

@garyopa can you forward this question/feedback to TX.

Is it possible to have an option to reboot into OFW from within SX OS CFW without having to physically enter SX software on boot and selecting OFW. when playing mostly docked I think that would be a great option if possible (not sure of the technical requirements/feasability).
 

Bellebite2000

Well-Known Member
Member
Joined
Jul 31, 2018
Messages
180
Trophies
0
Age
64
XP
256
Country
Afghanistan
Okay... so I have a clean 6.1.0 sysnand backup ..... I am currently on 6.2.0 , I have no emunand or SX OS set up yet , could I some how manually create an emunand on the sd cArd using my 6.1.0 back up so that I can boot sx os loader and boot cfw using emunand 6.1.0,if someone knows the exact steps on how to create an emunand could they explain thanks

It has been explained 200 millions time already. People are so lazy and always expect to find the answer to their stupid question on the last post of the last thread every single time. This is not how it works. Why did you update and burn a fuse in the first place? NOTHING requires 6.2 as of right now. Same story on 3DS, just a bunch of kids with "my dog updated my console" left and right crying and whining. People just never learn. Enjoy 6.2 and pray Scires and TX every day for a miracle!
 
  • Like
Reactions: jakkal

mrdude

Developer
Developer
Joined
Dec 11, 2015
Messages
3,076
Trophies
1
Age
56
XP
8,193
Okay... so I have a clean 6.1.0 sysnand backup ..... I am currently on 6.2.0 , I have no emunand or SX OS set up yet , could I some how manually create an emunand on the sd cArd using my 6.1.0 back up so that I can boot sx os loader and boot cfw using emunand 6.1.0,if someone knows the exact steps on how to create an emunand could they explain thanks
Yes if you previously made the nand backup with sx os.

Just create an emunand folder in sxos - then put your nand dump files in that.

Now boot the switch while holding down power + v+, then enable emnunand from the the menu.

That's all you need to do.
 

guily6669

GbaTemp is my Drug
Member
Joined
Jun 3, 2013
Messages
2,280
Trophies
1
Age
34
Location
Doomed Island
XP
2,033
Country
United States
And to update this SD emunand if I buy SX OS, I create a SD emunand and still have to use ChoiDujour trough emunand and chose the FW I put in the M-SD and update trought there or does TX have a better method built-in?

Also if I'm updating M-SD emunand do I still have to apply the option so it doesn't burn efuses that activate auto RCM or I can just skip it?

Ps: I'm on 3.02 if I even remember well and want my console to stay there 4 ever or maybe downgrade to 3.01 as it shares the same e-fuse...
 
Last edited by guily6669,

nero99

Well-Known Member
Member
Joined
Sep 18, 2014
Messages
3,135
Trophies
1
Age
31
XP
3,728
Country
United States
Is it possible to transfer the sd card EmuNAND to a larger sd card if needed? I’m using a 128GB card and plan on updating to a 256GB soon
 

bundat

¿
Member
Joined
Jul 25, 2018
Messages
456
Trophies
0
XP
481
Country
Antarctica
To avoid burning fuse, I tried to install autorcm right after sysnand update, but SX OS and hekate bootloader was not working sysnand 6.2.
Just to confirm, did you do that method where you update sysnand using the OFW update method, then hold vol+ while you have a jig inserted, to prevent the reboot from burning fuses and go straight into RCM?

Then you tried to install AutoRCM and it didn't work?
i.e. they modified BOOT0/1 so that AutoRCM installation attempts don't work?

Can I confirm this is what happened?

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

Is it possible to transfer the sd card EmuNAND to a larger sd card if needed? I’m using a 128GB card and plan on updating to a 256GB soon
You should be good to go just copy-pasting the files.
This is one reason why I prefer SX's emunand method than the "separate partition" thing those people have been throwing around.
Easier to transfer/backup to PC, just copy it.
 

leonmagnus99

Well-Known Member
Member
Joined
Apr 2, 2013
Messages
3,704
Trophies
2
Age
33
Location
Seinegald
XP
2,875
Country
Iraq
Several people asked the same question in this thread and so far nobody has anserwed the question, probably due to uncertainty. I’m not sure either but what I’m sure of is that -emuNAND or sysNAND - you need a Nintendo account with a Nintendo Switch Online Subscription in order to play online. The question now is whether or not they can detect emuNAND while you’re in unhacked sysNAND and if a banned emuNAND has any effect on the sysNAND since both share some data about your Switch. To minimize the risk of your online account being banned, you should use separate accounts for sys- and emuNAND in case you accidently performed some online activity while in hacked emuNAND (I suggest deleting the internet settings in emuNAND).
that makes sense, but im still abit confused about emunand on switch.

iirc. on the 3ds it was like a complete seperate nand? and then it was updated sysNAND where we had copied emuNAND into sysNAND (im still abit confused about it all) but i never was banned on either on my 3ds.
but things look alot different on the switch and im not even sure if i need emuNAND on the switch that is why i am asking if itd be safer to have one :l

and like if i make emuNAND on my switchs sd card i guess it would take around 30gb of space?
also lastly what would my emuNAND boot off ? i mean would it mean my emuNAND is tx os cfw?
and if i booted into ofw through tx menu, that then is the sysNAND ?
hope someone could clarify that one for me , thanks <3
 

WiiUBricker

News Police
Banned
Joined
Sep 19, 2009
Messages
7,827
Trophies
0
Location
Espresso
XP
7,485
Country
Argentina
  • Like
Reactions: leonmagnus99

leonmagnus99

Well-Known Member
Member
Joined
Apr 2, 2013
Messages
3,704
Trophies
2
Age
33
Location
Seinegald
XP
2,875
Country
Iraq
That’s right.


Exactly. emuNAND = TX CFW, sysNAND = OFW


Yes.
thank you so much , i think i will do it then because i plan to buy Nintendo sub and i will buy a physical copy of SSB.
and also you mentioned nintendo ids, i still do not have any and lets say i make one from where i boot ofw through tx menu.

that would be my sysnand , its safest to create a nintendo id in sys and buy a sub there and also play the original games there ,thats all right?
 

WiiUBricker

News Police
Banned
Joined
Sep 19, 2009
Messages
7,827
Trophies
0
Location
Espresso
XP
7,485
Country
Argentina
that would be my sysnand , its safest to create a nintendo id in sys and buy a sub there and also play the original games there ,thats all right?
If your sysNAND is unhacked and emuNAND not detectable, yes. But like I said, I don’t know if they can detect your emuNAND if you go online with your sysNAND. I would wait for more information, let alone better emuNAND support without corruption issue.
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • No one is chatting at the moment.
    K3Nv2 @ K3Nv2: Sorry for accidentally bending over