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
 

bundat

¿
Member
Joined
Jul 25, 2018
Messages
456
Trophies
0
XP
481
Country
Antarctica
@garyopa Found a Bug here! After starting the game Overcooked 2 after the company logos the game ask me to press R and L to start. As soon as I do the Homebrew Menu pops up and it takes over the game and I must close the game via the home menu to exit. I assume it must have something to do with the new Homebrew menu takeover of any title by holding R feature. Not sure if other games have similar problems
I think the R button takeover is the only bad thing with this update.
I never really needed to load homebrew from any other location than from the SX OS homebrew menu from the Album.
Don't really know who was asking for this "feature" that they thought they needed to implement it. :P
 
  • Like
Reactions: THYPLEX

JimmyCall

Active Member
Newcomer
Joined
Jul 17, 2018
Messages
36
Trophies
0
Age
44
XP
307
Country
Australia
Having your emuNAND on a SD is risky as there are times a SD will messup and need reformtting, losing all your save games.
 

Fafner

Member
Newcomer
Joined
Nov 12, 2018
Messages
14
Trophies
0
Age
47
XP
88
Country
Switzerland
Retro
I think the R button takeover is the only bad thing with this update.
I never really needed to load homebrew from any other location than from the SX OS homebrew menu from the Album.
Don't really know who was asking for this "feature" that they thought they needed to implement it. :P

Retroarch's Mupen64Plus core component (Nintendo 64) emulator can't work with the memory which the standard launcher allows. That's why they released an NSP version as well, which avoids this limitation. Stuff started from the hokescreen seem to get much more memory allocated. Why Team Xecuter can't do it in its own launcher, I don't know. I can imagine other memory intensive homebrew could have the same issue. Maybe team executer wanted to offer a solution for such a situation?
 
Last edited by Fafner,
  • Like
Reactions: THYPLEX

thaikhoa

Well-Known Member
Member
Joined
Sep 16, 2008
Messages
2,236
Trophies
1
XP
2,590
Country
Australia
Again OK guys. There's a critical bug in SX OS 2.3. After moving Emunand from NAND to mSD it'll restore the whole BOOT1 to its original form and backup a copy to sx\emunand\boot1.bin. And a modified sx\emunand\boot0.bin when it compares to original BOOT0. For some reason I don't know yet. When having black screen after moving Emunand from NAND to mSD I replaced BOOT0 and BOOT1 from BACKUP to sxos\emunand\boot0.bin and sxos\emunand\boot1.bin > It boots to Emunand on mSD just fine. After checking sxos\emunand\boot1.bin don't need to have EMUNAND recognition. But the sxos\emunand\boot0.bin always fixs itself (might be for the Emutendo folder solution) when booting if replaced with original BOOT0 from NAND.

Good news here: We won't touch BOOT0/1 anymore.

Solution: Before moving Emunand to mSD, backup BOOT0.
After moving EMunand to mSD, rename backup BOOT0 to boot0.bin and copy>paste it to sxos\emunand\ (overwrite when asked)

After updating to newer firmware. If there is a failed boot to Emunand, manually copy backup BOOT0 from newer firmware to sxos\emunand\boot0.bin and might be BOOT1 as well.

UPDATE: The black screen issue after moving Emunand is from sxos\emunand\boot0.bin. Copy BOOT0 from backup and rename to sxos\emunand\boot0.bin

Such a headache

Cheers.
 
Last edited by thaikhoa,

Essasetic

General Spectator
Member
Joined
Jun 16, 2018
Messages
1,573
Trophies
1
XP
3,304
Country
United Kingdom
Hexkyz hasn't decrypted it yet (don't worry yet lol). But Ev1l0rd is right. (Especially on exFAT SD Cards) since this doesn't create a partition it could easily corrupt the whole SD Card. That's what I'm concerned about. I imagine corruption to the SD Card happening a lot and people losing their licences. This almost seems too good to be true. I'd say be careful especially because it hasn't been revealed what it actually is yet.
 

lordelan

Well-Known Member
Member
Joined
Jan 4, 2015
Messages
5,792
Trophies
1
Age
44
XP
6,547
Country
Germany
Can you add ntfs compatibility next time ?
also thanks for this big update !

Although I'm pretty sure they are reading things here from time to time I don't think this is the best place to ask them things. Use their official forum or even their mail.

Not sure if this is the right place to report a bug, but here I go:
- After migrating the emunand to the microsd I get a black screen. I had to delete it and now I'm creating a new one.

Also: Wheres the Emunand folder? Theres no emutendo folder by default right? Why did you guys decide to remove the "Advanced options" when creating an emunand?

See above.

I created a nand backup before running any homebrew. Is this the correct process to follow now?
1. Restore nand backup
2. Boot into sxos and create emunand based on original nand backup
3. Any other steps?

Also I have been playing games through sxos without emunand, so I assume the game saves are stored on my switch.
1. Restoring nand backup will wipe my game saves right?
2. How should I copy my saves over so that after booting into emunand, games will read/write to my microsd card instead?

Correct. You need an "unhacked" sysnand to prevent getting banned. If you have one in a backup, you could restore it. From there you can create an emunand in which you do things and hack while staying offline or using 90dns of course.

Obviously restoring a nand backup will restore the state in which your Switch was at the time of the backup. If you started savegames after creating that backup, those saves will be gone after the restore. Use checkpoint to make backups first.

Since your sysnand is "hacked" (isn't it?) it might be less work to just make an emunand out of your actual sysnand and then (while having a hacked emunand) restore your nand backup into your sysnand. However I don't know if this is wise and if and how linking/unlinking sysnand<->emunand is a thing here.

Also if I were you I would wait a bit (for other people testing it first) until you make your move.

As a last addition I read a few times that people had problems restoring their nand backup. Do some research on that as well before you do that. Wouldn't be nice to end up with a bricked Switch, right?

Make the cheat engine better to support exfat 32 please !!!!!!!!!
There's no exfat32 file system but since I'm pretty sure you mean exFAT (and not FAT32 which is superior) let me tell you that they can't make better support for it. It's the way exFAT works that makes it suck. This has been explained so many times in so many threads already. Just don't use exFAT if you're using anything homebrew related!
 
Last edited by lordelan,
  • Like
Reactions: THYPLEX

retrofan_k

Well-Known Member
Member
Joined
May 31, 2013
Messages
2,077
Trophies
2
Location
Caves
XP
2,462
Country
Belarus
Having your emuNAND on a SD is risky as there are times a SD will messup and need reformtting, losing all your save games.

It's not, as emunand on the previous sysnand partiton solution is far more risky. One bad read or write function could cause real problems and without nand backups your fkd. Having emunand on a SD card is safer (just have backups of the SD card and saves with Checkpoint)
 

Essasetic

General Spectator
Member
Joined
Jun 16, 2018
Messages
1,573
Trophies
1
XP
3,304
Country
United Kingdom
It's not, as emunand on the previous sysnand partiton solution is far more risky. One bad read or write function could cause real problems and without nand backups your fkd. Having emunand on a SD card is safer (just have backups of the SD card and saves with Checkpoint)
Hahahaha.
No. Since they didn't decide to make a partition on the SD Card. That exact scenario that you described could literally happen to anyone using it. (Especially if it's an exFAT SD card.)
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    Xdqwerty @ Xdqwerty: @salazarcosplay, I heard herbert stopped appearing on the show