It's HERE! - TX Has Finally Done It! - Their SX OS Now Fully Supports v6.2!

Everyone been smashing their heads against the wall, and refreshing forums for over two weeks waiting, but no more do you have to wait as SX OS v2.4 is finally available for all Nintendo Switch owners to enjoy, and be able to update to v6.2 finally, its been a long wait, but as you read the change-log below you will quickly see that it was well worth the wait, and there is still more to come soon!

We are pleased to let you all know that SX OS v2.4 BETA is ready for release.​

First of all, sorry to keep you waiting longer than we initially anticipated. We have been working around the clock to bring you this new release. We want SX OS to be synonymous in your mind with constant quality. We are here to stay and we are here to keep supporting your purchase till end of life.

Now, lets have a look at what v2.4 brings to the table:

• Support for firmware 6.2.0
  Nintendo threw us a small curve-ball while we were in the middle of reworking some other parts of SX OS. That being said, SX OS is now fully compatible with the latest official firmware 6.2.0.
• EmuNAND functionality reworked
  Our initial release of EmuNAND used a storage mechanism that wasn't what a lot of people were looking for. In our last release we decided to switch to using the microSD for EmuNAND storage, which in turn made some users that *did* like the old method of storing EmuNAND on the system NAND unhappy. We have reintroduced the support for EmuNAND-on-system-NAND as well as introduced a third storage method for your EmuNAND partition. You can now also opt to use a separate partition (as opposed to files in the regular (ex)FAT filesystem) as a storage backend for your EmuNAND. With three flavors of EmuNAND storage supported now, all of you can rejoice!
  
  
  To recap, you now have three way of settings up EmuNAND now:
  

  • EmuNAND on system NAND: repurpose part of your Switch internal storage for EmuNAND
  • EmuNAND on microSD as partition: repartitions your microSD card with a separate EmuNAND partition
  • EmuNAND on microSD as files: EmuNAND is stored on microSD as files instead of repartitioning
  WARNING: Setting up your EmuNAND as partition on your microSD card will format your microSD card. After setup nothing but the boot.dat and license.dat will remain.
• Homebrew R button interfering with ingame L+R buttons fixed
  In the last release we introduced a method of invoking the homebrew launcher for any title by holding down the [R] button during application/game startup, this gives homebrew additional capabilities that it wouldn't normally have. However, this seems to have caused some interference with some games, this has been fixed.
• Embedded Homebrew Menu
  Previously, you had to copy a `hbmenu.nro` file to your microSD card in order to use the homebrew launcher. This has been fully integrated into the SX OS boot.dat file now. Effectively this means all you need for setup is to copy our boot.dat file, simple!

That's all we have for now, people. That doesn't mean we're done. Its not over until we have liberated every single console out there. A lot of our current attention is focused on bringing you a solution for these "unhackable" switches. That does not mean we're not improving SX OS as well. Keep those feature requests and bug reports coming!

Enjoy the festivities this month, and don't forget to pick up a SX Pro / SX OS for your loved ones!

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

​

Source: MaxConsole

 

[Vic_Vinegar]

Creating my partitioned emunand now
Can't wait to try this out

Please let me know how it goes. I already have an emunand installed and im curious how the new emunands will work / function

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

I don't use emunand myself so can't really comment on it sorry.

Just using the standard / basic functions and it all seems fine, updated to 6.2 and all seems well

appreciate it! I'm in the same boat as you as I only use the basic features. I only have emunand installed as I opted to update my firmware via emunand on choixdujour

 

[thaikhoa]

Please let me know how it goes. I already have an emunand installed and im curious how the new emunands will work / function

It works just fine. It creates an unallocated partition of 29GB or so. I have no idea how to dump the emunand partition out.

 

[Ra1d]

Can we make 3 emunand and then choose the one to boot?

You can do it with 3 microSD's, then pick the one that you want. As a built in feature, they probably can implement this, but why ? You will need like 64GB of space just for the hidden partition and stored as files, not to mention some of your systemNAND occupied for the 3rd.

 

[Localhorst86]

It works just fine. It creates an unallocated partition of 29GB or so. I have no idea how to dump the emunand partition out.

My guess is they are putting a RAW dump of the NAND on the partition. You could probably grab it by using a dd command in linux and maybe trim some excess bits and pieces from the beginning or end of the resulting file (like headers or similar).

 

[comput3rus3r]

so how do i go about updating sysnand to 6.2 and then updating my 6.1 emunand to 6.2?

 

[Localhorst86]

so how do i go about updating sysnand to 6.2

Boot into Sysnand, update via ChoidojourNX

and then updating my 6.1 emunand to 6.2?

Boot into Emunand, update via ChoidojourNX

 

[comput3rus3r]

Boot into Sysnand, update via ChoidojourNX



Boot into Emunand, update via ChoidojourNX

i'm not banned, i want to update online.

 

[Localhorst86]

i'm not banned, i want to update online.

Ok.

Boot into Sysnand, update online or via ChoidojourNX

Boot into Emunand, update via ChoidojourNX

 

[dsrules]

Creating my partitioned emunand now
Can't wait to try this out

does it allows you to choose the partition size when creating the partition on microsd?

 

[thaikhoa]

My guess is they are putting a RAW dump of the NAND on the partition. You could probably grab it by using a dd command in linux and maybe trim some excess bits and pieces from the beginning or end of the resulting file (like headers or similar).

That's what I'm doing but still having no idea.

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

does it allows you to choose the partition size when creating the partition on microsd?

The default setting is a full nand of ~32GB, there's no other settings at all.

 

[comput3rus3r]

Ok.

Boot into Sysnand, update online or via ChoidojourNX

Boot into Emunand, update via ChoidojourNX

I don't want to use autorcm. doesn't choidijour automatically enable it?

 

[jakkal]

does it allows you to choose the partition size when creating the partition on microsd?

no it doesnt

 

[comput3rus3r]

If i update sysnand to 6.2 then create a new emunand off that can i just recopy my emutendo folder to keep all the installed games?

 

[thaikhoa]

I don't want to use autorcm. doesn't choidijour automatically enable it?

Yes, it's automatically set autorcm-enabled by default.

 

[dsrules]

no it doesnt

Thanks
Guess, I will pass until I get a 200+GB microsd or could you still install games on to that 32GB emunand?

 

[comput3rus3r]

Yes, it's automatically set autorcm-enabled by default.

can that be turned off?

 

[Essasetic]

Sleep mode is broken (at least on EmuNAND on 6.2.0) (from at least what I've heard from a friend).

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

Also AutoRCM broke.

 

[thaikhoa]

If i update sysnand to 6.2 then create a new emunand off that can i just recopy my emutendo folder to keep all the installed games?

If your sysnand and emunand and all are on the same linking soul, yes you can keep all the data on Nintendo on sysnand and Emutendo on emunand.

 

[Vic_Vinegar]

can that be turned off?

Correct me if I am wrong, when I update my emunand to 6.2 via choixdujour, choixdujour will turn autorcm on by default correct?

 

[sergux]

i get some errors of reading when i tried to install game updates of ark and super smash through sx os (6.2 with 2.4 sx os) i used tinfoil and it worked.