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
 

nswuser007

Well-Known Member
Member
Joined
Nov 14, 2018
Messages
116
Trophies
0
Age
42
XP
160
Country
United States
someone mentioned BAD xcis is causing the scan loop when using external hdd - I dont think i have any bad xcis so I dont think that is the case, HOWEVER they mentioned a program to verify/check the xcis. please advise and link to that so I can in fact run each and everyone run THRU to verify what I said is true or not before reporting back and stating in fact what I thought to begin with. I can ONLY hope there is at least ONE corrupt one on there for their statement to be correct and fix my issue, the hdd would save SO much time over SD card :P sd card would be great for portable but for at home docked whats the point.

never the less please if anyone can assist with getting the external hdd to work with the games please please much appreciated if so.!
 

shanefromoz

Well-Known Member
Member
Joined
Jun 18, 2007
Messages
1,950
Trophies
1
XP
4,246
Country
Australia
Hello,

I have a switch on 6.0.1 and is unbanned.
I use autorcm to boot into sxos.
Am i best to install emunand now or should i just update the firmware to 6.1.0 using ChoiDujourNX?
If i install emunand do i still use autorcm?
How would one boot into OFW against CFW?

Thanks
 

jakkal

Well-Known Member
Member
Joined
Apr 27, 2018
Messages
2,303
Trophies
1
Age
44
XP
3,982
Country
United States
Hello,

I have a switch on 6.0.1 and is unbanned.
I use autorcm to boot into sxos.
Am i best to install emunand now or should i just update the firmware to 6.1.0 using ChoiDujourNX?
If i install emunand do i still use autorcm?
How would one boot into OFW against CFW?

Thanks
Update first, then do emunand
You can still use autorcm
It does not affect your emunand in any way
I don't understand your last question
 

CecilioX3

Well-Known Member
Newcomer
Joined
Jun 16, 2018
Messages
54
Trophies
0
Age
28
XP
411
Country
United States
Emunand boots to Nintendo switch logo and nothing more.
Downgraded back to 2.2 and it works fine, but I was wondering if anyone had trouble or the same problem with SD card based emunand?
 

Stwert

Well-Known Member
Member
Joined
Jan 6, 2015
Messages
949
Trophies
1
Age
49
Location
Scotland
XP
2,533
Country
United Kingdom
This sounds easily corruptible and can corrupt the entire SD card.


exFAT in general is wonky on the switch and constant read/writes to any filesystem (wether its exFAT or FAT32) is just a recipe for corrupting it and the files on it.


The reason the emuNAND solutions from the 3DS scene repartitioned the SD was specifically to avoid this from occuring.


This is just the dualboot sysNAND hackjob moved to the SD except you can now also corrupt your entire SD card incredibly easy (exFAT already corrupts on regular HBL usage and constant read/writes to a file on the filesystem is just bad regardless of filesystem).


Leaving TX and SX OS aside for a moment as this has nothing specifically to do with them.


Constant read/writes to ANY file system is a recipe for disaster? Really?


I’ll give you eXFAT, it’s far from great when it comes to file systems.


But other than that, every computer with a hard drive for the OS, or floppy for software, heck even tape to a degree. Even pre-DOS. Smartphones since iOS and Android’s introduction, in fact even Symbian and to a lesser degree, pre-symbian. Consoles, smart TV’s, heck even my smart washing machine, heating system, security system and lighting all do constant read/writes to their storage medium.


I’ve got an old FAT32 network drive, still in operation going on a decade, which gets pretty consistent use, funnily enough it doesn’t corrupt every few weeks.


The point is, reading/writing to storage has been a part of our daily lives for a long, long time, even in devices you wouldn’t necessarily expect. File systems have improved and will continue to do so, but even FAT32 isn’t all that bad of a file system. EXFAT needs kicked to the kerb, it’s a bit shoddy, but that aside, they’re pretty robust.
 

aerios169

Well-Known Member
Member
Joined
Dec 30, 2012
Messages
706
Trophies
1
Age
31
XP
2,225
Country
Mexico
I'm not sure if this is a bug but - here's one for TX.

I had the following:
6.1.0 firmware on Emunand.
6.0.1 firmware on Retail Nand.

Above was working fine, so I use the option to create/move emunand to microsd card.

I have a 16gig emunand folder now in sxos folded containing boot0/boot1/full00/full01/full02/full04 bin files.

I can boot into retail, I can boot into custom firmware (non emunand).

I CAN'T boot into emunand - switch stays on a black screen - so I assume emunand is corrupt, and will need re-created - is this correct? and will I lose my game saves or will those be stored in the nintendo folder?

just rename the folder of nintendo for Emutendo, and it should remove the black screen, i had the same problem and i did that and works fine for me even with the installed games
 
Last edited by aerios169,

NazoXIII

Well-Known Member
Newcomer
Joined
Aug 10, 2008
Messages
97
Trophies
0
XP
599
Country
United States
So now that we have "true" emunand, theoretically I could restore my clean nand dump to before I had any kind of homebrew and not fear getting banned on OFW? because that's what I'm taking from this, am I wrong?
Otherwise, what does this really mean for us?
 
Last edited by NazoXIII,

Site & Scene News

Popular threads in this forum

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