Team-Xecuter Presents SX OS v2.4 BETA

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

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




:arrow: Source: MaxConsole
 
Last edited by garyopa, , Reason: formatting, broken link.

KirovAir

Alcoholic Programmer
Member
Joined
Dec 7, 2006
Messages
768
Trophies
1
Age
32
Location
Netherlands
Website
www.jessesander.nl
XP
2,420
Country
Netherlands
I don't like that they integrated the Homebrew Menu... Now we can't update it ourselves anymore?

It will probably check if a file exists on your SD card. If it's not there it will load the integrated one. (At least I hope so, I'll have to check when I'm home)
 
  • Like
Reactions: Brawl345

Brawl345

Well-Known Member
Member
Joined
Jan 14, 2012
Messages
776
Trophies
2
Website
wiidatabase.de
XP
2,841
Country
Germany
It will probably check if a file exists on your SD card. If it's not there it will load the integrated one. (At least I hope so, I'll have to check when I'm home)
You are right, if I have the hbmenu.nro it says 3.0.0 (/3.0.1, didn't update). If I delete it, it says 3.0.0-2a3564f
 
Last edited by Brawl345,
  • Like
Reactions: Condemned87

gameboy

Well-Known Member
Member
Joined
Dec 9, 2015
Messages
2,035
Trophies
1
Age
44
XP
2,166
Country
United States
whoa, is this dual boot? and can big N read that partition? interesting... i wait for more to get banned first....
 

Localhorst86

Robert'); DROP TABLE members;--
Member
Joined
Jul 17, 2014
Messages
2,731
Trophies
1
Location
Nintendo works for my dad
XP
5,276
Country
Germany
whoa, is this dual boot? and can big N read that partition? interesting... i wait for more to get banned first....
technically, they probably could check for that partition in OFW if they wanted. But they could also just check for the EMUNAND files on either the NAND (first emunand solution) or SD (second emunand solution). They don't do that at the moment and tbh, I would not assume they will.

In the end, the Emunand partition is no more or less detectable than emunand solutions before it. The biggest advantage a dedicated partition has, is increased stability. The Emunand is no no longer a regular file on the SD card filesystem but it's separate partition. So if your SD filesystem corrupts (as it sometimes seems to happen), your emunand will now be unaffected (Note: Emunand is still susceptible to flash degradation, though. So if the SD card ever dies because the flash wears out, Emunand will still be affected, that's unavoidable).
 
Last edited by Localhorst86,

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    Sicklyboy @ Sicklyboy: oh shit where??? :ph34r: :ph34r: :ph34r: