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]

Yes, need to add the boot.dat to my sdcard. I'm hoping it's just that simple.

Me too! If it is, I'll keep my emunand, if its not, i'm going to disable it and remove it

 

[SaggyBeans]

Anyone having an issue with the payload menu freezing in the SX OS menu? (pwr&vol+ menu)

 

[Ra1d]

Do I need to leave a copy of emunand on my sd card???

No. If you previously had emuNAND installed as files on your microSD, and you want to use the hidden partition emuNAND introduced in this version, there's no way to migrate your old emuNAND to the hidden partition(as far as I know). It will create a new emuNAND, so make sure you backup your data and saves(via checkpoint), after you've backed everything up you might as well delete everything from your microSD except for license.dat and boot.dat.

Note the new emuNAND will be linked to sysNAND again. So if you care about this you will have to restore your emuNAND's factory settings to unlink.

 

[burial]

No. If you previously had emuNAND installed as files on your microSD, and you want to use the hidden partition emuNAND introduced in this version, there's no way to migrate your old emuNAND to the hidden partition(as far as I know). It will create a new emuNAND, so make sure you backup your data and saves(via checkpoint), after you've backed everything up you might as well delete everything from your microSD except for license.dat and boot.dat.

Note the new emuNAND will be linked to sysNAND again. So if you care about this you will have to restore your emuNAND's factory settings to unlink.

I never made a emunand before until now and I picked the 2nd option......so its ok to delete it off my card?

 

[Scitzo]

What's the method to go from

Emunand on SD as files
to
Emunand on SD as partition

Delete emunand + start over
Or there's a migration option
Something else?

Dont quote me on this yet, because im at work and cant verify it 100% until I get home later and do this myself. But im in the same boat as you, and this is what i will do:

1)Copy my entire current microsd over to my computer hard drive (the ENTIRE microsd, including emunand folder, nintendo folder, everything.
2) Format entire microsd as fat32 with 32kb cluster size using guiformat on quick format.
3) place sx os 2.4 boot.dat and license file on root of now empty microsd.
4) Boot into sx os options bootloader menu.
5) create NEW (not migrate, NEW) microsd PARTITIONED emunand.
6) Once done, turn off system, and insert microsd into pc.
7) replace everything OTHER than emunand folder into the normal root of the microsd.
8) cut and paste the sxos and emunand folders into the partitioned part of the microsd.
9) Replace the old boot.dat on the microsd (you just copied over) with the newer sx os 2.4 boot.dat
10)???
11) profit.

In theory, this should allow us to have partitioned the microsd while copying our old microsd emunand into the new partitioned area properly. I will have to wait until i get home to know the exact specifics on their file setup and if it changed, but this is the gist. Enjoy.

Edit: because im not at home yet to verify, i dont know if theyll leave the emunand folder on the root of microsd, or if theyll move it into the partitioned area and rename it nintendo. Youll have to test this yourself. Ill report back later.

 

[Ra1d]

I never made a emunand before until now and I picked the 2nd option......so its ok to delete it off my card?

If you want to use the new version emuNAND (the hidden partition one) you can delete it.

 

[Scitzo]

No. If you previously had emuNAND installed as files on your microSD, and you want to use the hidden partition emuNAND introduced in this version, there's no way to migrate your old emuNAND to the hidden partition(as far as I know). It will create a new emuNAND, so make sure you backup your data and saves(via checkpoint), after you've backed everything up you might as well delete everything from your microSD except for license.dat and boot.dat.

Note the new emuNAND will be linked to sysNAND again. So if you care about this you will have to restore your emuNAND's factory settings to unlink.

See my post on how to migrate manually.

 

[Ra1d]

See my post on how to migrate manually.

Wouldn't work for me, cuz I migrated first from emuNAND that was installed on system memory where I could choose the size of emuNAND, so I picked 16gb, and the new partitioned emuNAND doesn't let you chose the size and auto installs the 30gb version.

 

[Vic_Vinegar]

No. If you previously had emuNAND installed as files on your microSD, and you want to use the hidden partition emuNAND introduced in this version, there's no way to migrate your old emuNAND to the hidden partition(as far as I know). It will create a new emuNAND, so make sure you backup your data and saves(via checkpoint), after you've backed everything up you might as well delete everything from your microSD except for license.dat and boot.dat.

Note the new emuNAND will be linked to sysNAND again. So if you care about this you will have to restore your emuNAND's factory settings to unlink.

What about if I already have emunand installed on my sd card and I don't want to touch/make modifications to my emunand? Do I just update the boot.dat file and thats it?

Will my Emutendo folder be okay?

 

[Ra1d]

What about if I already have emunand installed on my sd card and I don't want to touch/make modifications to my emunand? Do I just update the boot.dat file and thats it?

Yep, 2.4 is fully compatible with old emunand versions.

Edit** Yes your Emutendo folder will be okay.

 

[Vic_Vinegar]

Yep, 2.4 is fully compatible with old emunand versions.

Mint! You sir are tits!

I was worried for a second that it wouldn't be compatible because of the new emunand features they introduced in 2.4. Looks like updating to 6.2 should be easy

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

Yes, need to add the boot.dat to my sdcard. I'm hoping it's just that simple.

Hey @kublai @Ra1d provided us with an excellent answer to the question we both had. Just check the posts above.

TL;DR no need to worry about your current emunand, just add the new boot.dat file and upgrade to 6.2 using choixdujour (while keeping your emunand enabled)

 

[burial]

Okay....after updating none of my NSPs are working, it says I need to download them again.

Help?

 

[Suthek]

I have emunand on internal storage. (Didn't bother moving to sd last release)
If I select move to SD via 2.4 will it make a partition? Or do the file method still?

Edit.
Used the move emunand option and it just made the folder version. Not partition version.
Don't do that. Will waste your time.

 

[JeepX87]

Finally, I'm definitely sure that y'all are happy about SX supports 6.2.

I don't have to offer Kleenex anymore but watch out for Nintendo.

 

[hippy dave]

SX's current installer, like tinfoil, uses horizon's built in file services to decrypt the files automatically. I decrypt them by hand, which is why I require keys.txt and they do not.

Why doesn't the SX OS release include the keys for your installer to use? It's not like "copyright" is a relevant answer. It breaks the whole thing about SX OS only needing boot.dat

 

[MRDOCA]

version 1.1.0 works perfect

I get a error trying to use the unmodified 1.1.0 update in the TX installer. Did you use another way? Thought I had a bad download so tried another one and same error. Any help would be great

Sent from my SM-G955F using Tapatalk

 

[roamin]

@SonyUSA you said to me in another thread that i would go back to sxos when it drops because exciting stuff was happening.

well its dropped now and well there aint nothing exciting going on.

as for emunand who cares. it brings nothing to me, its not like a 3ds where you play online on nintendo's servers with emunand.

so please inform us of what exciting stuff is actually coming to sxos that makes it worth my time going back to it.

 

[jakkal]

@SonyUSA you said to me in another thread that i would go back to sxos when it drops because exciting stuff was happening.

well its dropped now and well there aint nothing exciting going on.

as for emunand who cares. it brings nothing to me, its not like a 3ds where you play online on nintendo's servers with emunand.

so please inform us of what exciting stuff is actually coming to sxos that makes it worth my time going back to it.

Nobody cares about your excitement level

 

[yonasz]

I have error as well with VENOM 1.1.0 update

 

[Ra1d]

Okay....after updating none of my NSPs are working, it says I need to download them again.

Help?

You have to reinstall the NSP's on emuNAND. They will work on your sysNAND like they did, but they won't work on emuNAND until you reinstall them, also backup your save files with checkpoint and then restore them on emuNAND after you reinstall them.