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

 

[Bloodlust]

So it's 100% safe to update to 6.2 ofw online now? I heard that ninty allows the update regardless of whether the switch is banned or not...

Sent from my MI MAX 3 using Tapatalk

 

[Sunnyboy]

Apparently SX Installer will get cool new features that TinfoilDZ doesn’t have.

You seen it somewhere, on the filmp there is a sx installer from TX but not in de boot.dat

 

[mbze430]

Having no luck installing new NSP (GRIS).... old ones seems to work

 

[Spider_Man]

Is there really any setup that will prevent bans 100%?

Nope, it's a game of cat and mouse, all Nintendo have to do is see what users have emunand, even stealth mode isn't fail safe because if your playing online yet Nintendo servers fail to see any info of your system then it says it all.

People who pirate need to learn that pirating never comes with fill features, if you want full features then go buy the fucking game and stop bitching that the game you illegally downloaded can't play online and/Or you got your console banned.

Things like this are not endorsed by Nintendo, it alters their code, violates their ToS, so why the fuck would they let you download games for fuck all and play them.

You wouldn't let people take your business and not pay for anything.

 

[CapoCEO]

Guys i been away for quite sometime now got back and have some personal time to be apart of the scene So i need some tips advice etc. I am ofw 6.0.0 and am on sx 2.0.1. I see 6.2.0 is the latest ofw. And sx os has a beta at 2.4 but 3.0 base is coming soon. Should i update using choidujournx? Also how should i go about NAND AND SYSNAND because this looks like a new feature. Don't know if its like how the nand sysnand was on 3ds where you can go online with your ofw and then use the sysnand for cfw smh dont remember the order but yeah i think you guys get my point. Thanks in advance for a layout on what to do.

 

[subcon959]

Doesn't the built in installer have access to new keys?

 

[CapoCEO]

Doesn't the built in installer have access to new keys?

sub can you lend a helping snout i mean hand : )

 

[Frexxos]

And again: awesome!
“soon™“ was early. I am really happy with my sx pro. Money definitly well spent!

 

[subcon959]

sub can you lend a helping snout i mean hand : )

I don't use emunand or play online so can't help with that.

 

[CapoCEO]

I don't use emunand or play online so can't help with that.

ok i dont play online at all either. I just want a stairway to heaven when it comes to a safe process of the help i asked about is all.

 

[urherenow]

Guys i been away for quite sometime now got back and have some personal time to be apart of the scene So i need some tips advice etc. I am ofw 6.0.0 and am on sx 2.0.1. I see 6.2.0 is the latest ofw. And sx os has a beta at 2.4 but 3.0 base is coming soon. Should i update using choidujournx? Also how should i go about NAND AND SYSNAND because this looks like a new feature. Don't know if its like how the nand sysnand was on 3ds where you can go online with your ofw and then use the sysnand for cfw smh dont remember the order but yeah i think you guys get my point. Thanks in advance for a layout on what to do.

Everyone says lower is better. But on OFW 6.0, there is nothing useful from using choidujournx. I personally think there is zero reason to save your fuses for a 3.0 downgrade, but people would argue with me on that. Don’t think many would argue about 6.0 though.

TL;DR
Don’t bother. Just update.

 

[subcon959]

ok i dont play online at all either. I just want a stairway to heaven when it comes to a safe process of the help i asked about is all.

All you have to do is update to 6.2 and stick the new boot.dat on sd. I guess ChoidujourNX is the recommended way.

 

[radicalwookie]

So...any ban hammers yet?

 

[hexdump]

Having no luck installing new NSP (GRIS).... old ones seems to work

Did you manage to fix the problem? I'm having same exact problem (Can't read NSP error and icon in the installation list of NSP's appears white).

Any one found a solution to this?

Cheers.

 

[subcon959]

Did you manage to fix the problem? I'm having same exact problem (Can't read NSP error and icon in the installation list of NSP's appears white).

Any one found a solution to this?

Cheers.

The solution can only be done by TX. But you can work around it by using tinfoil.

 

[CapoCEO]

Everyone says lower is better. But on OFW 6.0, there is nothing useful from using choidujournx. I personally think there is zero reason to save your fuses for a 3.0 downgrade, but people would argue with me on that. Don’t think many would argue about 6.0 though.

TL;DR
Don’t bother. Just update.

interesting. I remember making a clean nand backup on 5.0.0 so i guess making a 6.0.0 backup would be waste anyway. I just want to make sure that being on 6.2.0 isnt a mistake and that scene support wont have issues with homebrews or tools for dumping my own games etc. And since i did use choijournx to update to 6.0.0 its always in autorcm which i wonder if this can be prevented with the whole sysnand nand new options i dont know how to go about that.

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

All you have to do is update to 6.2 and stick the new boot.dat on sd. I guess ChoidujourNX is the recommended way.

Yeah thats pretty much what urherenow said but its like i what i said in the previous message i posted. Its in autorcm to prevent the fuses from getting smoked. And am wondering how to go about not having it with the sysnand option replacing it at least thats what i was reading.

 

[subcon959]

Yeah thats pretty much what urherenow said but its like i what i said in the previous message i posted. Its in autorcm to prevent the fuses from getting smoked. And am wondering how to go about not having it with the sysnand option replacing it at least thats what i was reading.

I'm sure autorcm is retained to prevent fuse burning. The only part you have to pay attention to is whether or not you need exfat.

 

[CapoCEO]

I'm sure autorcm is retained to prevent fuse burning. The only part you have to pay attention to is whether or not you need exfat.

i know thats what the autorcm has been doing ever since i updated to 6.0.0 I am on exfat because it was the first thing that popped up when i first put my sdcard in when the switch was on 3.0.1

 

[subcon959]

i know thats what the autorcm has been doing ever since i updated to 6.0.0 I am on exfat because it was the first thing that popped up when i first put my sdcard in when the switch was on 3.0.1

I use fat32 but I still select exfat as you can't restore a nand backup with fat32 so it seems like a stupid choice to be given in the first place.

 

[CapoCEO]

I use fat32 but I still select exfat as you can't restore a nand backup with fat32 so it seems like a stupid choice to be given in the first place.

I wonder why they couldn't just had made it to where you could use both formats without issue like on a phone or pc. Last thing anyone would ever want is a corrupt file or files because even when you may need to do a chdsk on it the sdcard wont be the same then you have to re-download everything taking up more time smh.