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

 

[Freezerbomb]

You on the other hand have no such technical skill or knowledge to show for yourself and yet you are the one accusing me of not knowing stuff

In this SJW filled world that desires to ruin your life if you disagree with them, I've wisely chosen to have this separate account for my opinions. If you had "technical skills" you wouldn't waste your time tearing down someone that is more accomplished than you. TX has been in the console hacking scene since 2002. What were you doing during that time? Wearing diapers maybe?

 

[thaikhoa]

I have sysnand 6.2 and emunand 6.1 with 8 burnt fuses (6.1 expects 7 burnt fuses).
I can use 6.2 sysnand without problem. But when I boot emunand 6.1, getting into sleep mode freezes the device.
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.
So 7 burnt fuse + sysnand 6.2 combination seems impossible for now..



I trusted this and now I'm screwed.. Sleep mode is broken in emunand!

Confirmed sleep mode was broken on emunand 6.1. But it doesn't matter at all. It's fun to try as I rarely put the device in the sleep mode.

Cheers

 

[lufeig]

I sold my cartridges

I don't play online

So I have emunand on 6.1.0 - to play games without the "firmware update required" hassle - and sysnand on 5.1.0 because it's the cleanest/lowest nand backup I have, so I don't have to worry about autorcm to avoid burning fuses.

with all that said, sleep mode works perfectly for me.

 

[mattytrog]

Did you burn fuses while going to 6.2? If so, did you test going in and out of sleep on 6.1 EmuNAND? I saw someone theorizing about a fuse count check being made when the Switch wakes up, causing it to panic.

Btw, I've been following your modchip thread closely for months and would like to thank you for all the work you put into it.

Very welcome. Yep burnt fuses. But now we can dual boot and have SD emunand, there is no reason to save fuses. At least for us modchip users.

 

[thaikhoa]

If someone could know how to burn "fuse" on emunand. It will probably fix the sleeping issue. Oops I'm so wrong about lol.

 

[Ev1l0rd]

In this SJW filled world that desires to ruin your life if you disagree with them, I've wisely chosen to have this separate account for my opinions. If you had "technical skills" you wouldn't waste your time tearing down someone that is more accomplished than you. TX has been in the console hacking scene since 2002. What were you doing during that time? Wearing diapers maybe?

TX may have been in the scene since 2002, but I have reason to assume they're not the same people anymore. Instead, it seems much more likely that it's Team Gateway who is running TX nowadays. And Team Gateway has little faith from me in any form of competence, given how they stole arm9loaderhax wholesale.

 

[lufeig]

English is not my native language, so sorry if my question is dumb.

I don't know if I understood correctly, but you have no proofs at all, all your post is based in "I have reason to assume" and "it seems", am I right?

 

[Ev1l0rd]

I don't know if I understood correctly, but you have no proofs at all, all your post is based in "I have reason to assume" and "it seems", am I right?

Only reason I say assume and seems is because the proof is mostly circumstantial, although when put together it's rather damning.

 

[doofdilla]

I sold my cartridges

I don't play online

So I have emunand on 6.1.0 - to play games without the "firmware update required" hassle - and sysnand on 5.1.0 because it's the cleanest/lowest nand backup I have, so I don't have to worry about autorcm to avoid burning fuses.

with all that said, sleep mode works perfectly for me.

Did you enable autorcm in emunand when updating the emunand? I am on sys 5.1.0 and emu 5.1.0 myself atm and i want to update emu to 6.1.0 (got the files) but no matter how much i read i can't figure out the 100% right steps to do so.

I would try to:

1) Boot into emunand 5.1.0
2) Load ChoiDujour 1.01
3) enable AutoRCM and Update to 6.1.0
4) Reboot into 6.1.0 Emunand and profit?

Did i miss something?

 

[fadx]

It's strange that updating sysnand to 6.2.0 breaks emunand sleep mode (also happening to me with 6.0.1 emunand). Seems very strange considering the nands are supposed to be completely seperate and the nintendo folders are supposed to be completely seperate.

 

[tinkle]

Only reason I say assume and seems is because the proof is mostly circumstantial, although when put together it's rather damning.

Circumstantial evidence is damning, yall.

 

[thaikhoa]

It's strange that updating sysnand to 6.2.0 breaks emunand sleep mode (also happening to me with 6.0.1 emunand). Seems very strange considering the nands are supposed to be completely seperate and the nintendo folders are supposed to be completely seperate.

It might be the difference of the burned fuse counts between the two nands or broken warmboot.

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

Only reason I say assume and seems is because the proof is mostly circumstantial, although when put together it's rather damning.

We all understand what you're worrying about, but we take the risk here and be happy to do so. Please just stop taking care of us.

 

[lufeig]

Did you enable autorcm in emunand when updating the emunand? I am on sys 5.1.0 and emu 5.1.0 myself atm and i want to update emu to 6.1.0 (got the files) but no matter how much i read i can't figure out the 100% right steps to do so.

I would try to:

1) Boot into emunand 5.1.0
2) Load ChoiDujour 1.01
3) enable AutoRCM and Update to 6.1.0
4) Reboot into 6.1.0 Emunand and profit?

Did i miss something?

this is what I would do:

1. boot emunand 5.1.0
2. run choidujournx, load fw files 6.1.0
3. enable exfat patch and disable autorcm (no need to use it since you will never boot emunand using official bootloader)
4. reboot emunand 6.1.0 and profit

 

[doofdilla]

this is what I would do:

1. boot emunand 5.1.0
2. run choidujournx, load fw files 6.1.0
3. enable exfat patch and disable autorcm (no need to use it since you will never boot emunand using official bootloader)
4. reboot emunand 6.1.0 and profit

thanks for the fast answer!

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

Follow Up Question:

I can swap out my emunand files at will? So i could backup my 5.1.0 emunand (And emutendo folder) and then just swap them both hence and force between 5.1.0 and 6.1.0?

 

[Ev1l0rd]

Circumstantial evidence is damning, yall.

I never said that. I said it's rather damning. Rather means "to a significant degree". At the very least I can pretty safely say there's a GW member amongst TXs ranks. At worst, it's just GW under a new name.

 

[lufeig]

thanks for the fast answer!

glad to help

that is exactly what I did, except that my sysnand was 6.0.1 autorcm. fuse count for fw 5.1.0

so after updating my emunand to 6.1.0, I restored sysnand to 5.1.0 because I could and because I prefer to keep autorcm disabled (it was enabled to preserve my 5.1 fuse count at 6.0.1 fw)

 

[JJTapia19]

Omg stop with the hate! We are on page 33 and you're still going strong. Stop saying the same things already. This thread is not your blog.

 

[Dissaor]

Im about to start setting up my switch with this new emunand, do you recommend if I use a separate SD card for TX/Emunand and other for Horizon?

 

[JJTapia19]

Im about to start setting up my switch with this new emunand, do you recommend if I use a separate SD card for TX/Emunand and other for Horizon?

Is not necessary but if you're paranoid like me and want to keep the sysnand as separated from anything hack related and be able to relax while playing online on sysnand you definitely can use a different sd card exclusively for each nand.

 

[fadx]

Im about to start setting up my switch with this new emunand, do you recommend if I use a separate SD card for TX/Emunand and other for Horizon?

Just use the same SD card if you've a good amount of space just for convenience. It's theoretically possible that Nintendo could detect certain files on your SD card but even still, that isn't evidence you've booted CFW and would be absolutely ridiculous for them to ban based on that.