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

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! >--​

Source: MaxConsole

 

[Jayro]

«Rest assured, the team has already identified the issues and are working diligently to get an update out to resolve this situation»

https://team-xecuter.com/forums/threads/155435-WARNING-DO-NOT-UPDATE-TO-6-2-0

Can you stfu now?

That's really cool, considering they owe us nothing, and could have folded up shop and dipped like flash cart sellers do.

 

[NeoSlyde]

They also said they have an exploit for the patched switches, which hasn't seen the light of day in spite of patched switches being out now for a while.

They say lots of things, but have very little to show.

You don’t have any evidence.
Wait and see.

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

That's really cool, considering they owe us nothing, and could have folded up shop and dipped like flash cart sellers do.

True

 

[guitarheroknight]

They also said they have an exploit for the patched switches, which hasn't seen the light of day in spite of patched switches being out now for a while.

They say lots of things, but have very little to show.

Yeah, why not release all the exploits when a new revision of the switch is in the works. 10/10

 

[NeoSlyde]

For the patched console thing. I think that they wait that the exploit get patched or the new mariko models.

It’s totally logic and understandable.

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

Yeah, why not release all the exploits when a new revision of the switch is in the works. 10/10

Yes that what I say upper.
They are waiting that the exploit get patched or the new mariko models.

 

[Ev1l0rd]

You don’t have any evidence.
Wait and see.

There's historical proof that TX basically only fixes bugs the moment Atmosphere fixes bugs.

Their team mostly seems competent at sloppily taking other peoples software and selling it to people at a paid fee.

 

[NeoSlyde]

There's historical proof that TX basically only fixes bugs the moment Atmosphere fixes bugs.

Their team mostly seems competent at sloppily taking other peoples software and selling it to people at a paid fee.

Can you use your head?
Or you are mentally disabled ?

There no proof at all. You are based on lies.
Fucking ...

 

[Ev1l0rd]

Can you use your head?
Or you are mentally disabled ?

There no proof at all. You are based on lies.
Fucking ...

looks at hexkyz's twitter feed and the SX decryption scripts.

I think there's proof there.

 

[NeoSlyde]

looks at hexkyz's twitter feed and the SX decryption scripts.

I think there's proof there.

I don’t trust him. + His proofs aren’t valid.
Give me tangible proof or let it down.

 

[guitarheroknight]

Actually @Ev1l0rd is right. they do tend do "borrow" code from Atmosphere, but TBH SX OS was functional months before Atmosphere was.
Having that in mind, as far as i can tell they only improved upon the code and added new features - kuddos to that.
But the borrowing code part makes them seem incompetent.

 

[Ra1d]

Just wait for Atmosphere to fix it

I'm waiting, rumor says it Atmosphere will release a fix as soon as they release a working emuNAND. Oh wait...

 

[Ev1l0rd]

I don’t trust him. + His proofs aren’t valid.
Give me tangible proof or let it down.

I mean, do you have a copy of SX OS 1.0 at hand?

If so, open it in a hex editor and look for "inking seriously" in ASCII. It'll take you to a partially obfuscated easter egg string from nx-hbloader.

 

[NeoSlyde]

Actually @Ev1l0rd is right. they do tend do "borrow" code from Atmosphere, but TBH SX OS was functional months before Atmosphere was.
Having that in mind, as far as i can tell they only improved upon the code and added new features - kuddos to that.
But the borrowing code part makes them seem incompetent.

+ Let’s not forget TX announced their cfw and exploits waaaaaaaaaay before atmosphere started.

 

[Ev1l0rd]

+ Let’s not forget TX announced their cfw and exploits waaaaaaaaaay before atmosphere started.

They announced they would work on it ~a week after fusee-gelee became public. Atmosphere has been in some state of development before fusee-gelee became public. What you said here is just flat out false.

 

[NeoSlyde]

I mean, do you have a copy of SX OS 1.0 at hand?

If so, open it in a hex editor and look for "inking seriously" in ASCII. It'll take you to a partially obfuscated easter egg string from nx-hbloader.

What do you want?
You want them to make a new hb loader so that 99% of homebrews won’t be compatible with their and there will be 10000 version of the same homebrew?
They just wanted that the homebrews be universal.
That’s all.

 

[Ev1l0rd]

What do you want?
You want them to make a new hb loader so that 99% of homebrews won’t be compatible with their and there will be 10000 version of the same homebrew?
They just wanted that the homebrews be universal.
That’s all.

It's still proof of them taking other peoples work and selling it back to you.

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

https://www.ktemkin.com/faq-fusee-gelee/ : 4 April.

A, That second link has a switch decryption key, I'm afraid that violates the rules of GBATemp.
B. https://gbatemp.net/threads/team-xe...heir-first-sx-nintendo-switch-modchip.503868/ This is the first tangible discussion about their product in anything beyond a short video that just shows a boot logo, which was May. April comes after May.

On the other hand, Fusee-Gelee was released in February, the FAQ wasn't written until a few months later and it's likely that it was discovered before February and only released after they discovered Deja Vu: https://gbatemp.net/threads/fusee-gelee-coldboot-proof-of-concept-for-the-tegra-x1.496838/

 

[NeoSlyde]

It's still proof of them taking other peoples work and selling it back to you.

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


A, That second link has a switch decryption key, I'm afraid that violates the rules of GBATemp.
B. https://gbatemp.net/threads/team-xe...heir-first-sx-nintendo-switch-modchip.503868/ This is the first tangible discussion about their product in anything beyond a short video that just shows a boot logo, which was May. April comes after May.

On the other hand, Fusee-Gelee was released in February, the FAQ wasn't written until a few months later and it's likely that it was discovered before February and only released after they discovered Deja Vu: https://gbatemp.net/threads/fusee-gelee-coldboot-proof-of-concept-for-the-tegra-x1.496838/

TX was in 2 January.
I won.
Bye

 

[Ev1l0rd]

TX was in 2 January.
I won.
Bye

TX showed a modified bootlogo on 2nd of January. That's hardly proof of anything from their product at all. In fact, the Switch in that video does not even have any form of a modchip visible.

 

[NeoSlyde]

TX showed a modified bootlogo on 2nd of January. That's hardly proof of anything from their product at all. In fact, the Switch in that video does not even have any form of a modchip visible.

It was only a tease.
In their 2nd January post they also said:
« This solution will work on ANY Nintendo Switch console regardless of the currently installed firmware, and will be completely future proof. This is *the* solution for opening up CFW (Custom FirmWare) on the Nintendo Switch. We want to move the community forward and provide a persistent, stable and fast method of running your own code and custom firmware patches on Nintendo's latest flagship product. And we think we've succeeded! :-) »

 

[Ev1l0rd]

It was only a tease.
In their 2nd January post they also said:
« This solution will work on ANY Nintendo Switch console regardless of the currently installed firmware, and will be completely future proof. This is *the* solution for opening up CFW (Custom FirmWare) on the Nintendo Switch. We want to move the community forward and provide a persistent, stable and fast method of running your own code and custom firmware patches on Nintendo's latest flagship product. And we think we've succeeded! :-) »

TX says lots of things and has at the moment historically only come through on most of them when Atmosphere/ReSwitched does their job for them.

Also lol -> moving the community forward. A closed source product doesn't move the community forward at all, it just causes stagnation and dependency on the ones making the product.

 

[linuxares]

Really? You fight about who was first? It was a known exploit ages ago. I think even failoverflow hinted about it, since it was well documented in a tegra documentation.