Good day, friends! We are pleased to announce the release of SX OS 2.7 beta.

Well, if you been waiting to try out 'boost mode' in Zelda or play MK11, well no more waiting, you can now update and enjoy!

This update brings full compatibility with firmware 8.0.0 and 8.0.1. All your favorite SX OS functionality (emuNAND, XCI emulation, cheats, etc.) should work as intended.

SX OS v2.7 beta is available on our website and through our Online Update right now!

We keep getting excellent feedback from our users, and have accumulated a nice todo list for new SX OS functionality. Its been almost a year since our initial release, but we promise we're still actively working on adding new features and improving existing ones.

Of course, behind the scenes we are also still working hard on our solution for those "unhackable" switches. Good progress is being made, so hang in there!

That's it for today, keep checking back for more updates!

—< Team-Xecuter - Rocking the Switch in 2019 and beyond! >—​

Source: MaxConsole

 

[magico29]

another ko victory for TX.

 

[Dark Ronin]

another ko victory for TX.

More like late rounds technical stopage, but who cares anyway!

 

[cloudfe]

I know nobody has a crystal ball (or a uncle working there), but...
Do you guys think a stable release supporting 8.0.0/8.0.1 will take a while? I don't have much insight in the release history of SX OS.
As a follow-up, are the SX OS beta releases considered generally safe?

 

[stewacide]

...

The one thing you missed is being able to grab game updates directly from Nintendo with XCIs. Big hassle saver.

If SX implemented overclocking it'd indisputably be better than CFW. I'm sticking with SX for now to avoid a ban (so I can grab the aforementioned updates) but it sucks to know my games could be performing / looking much better with an overclock.

 

[cloudfe]

The one thing you missed is being able to grab game updates directly from Nintendo with XCIs. Big hassle saver.

I did not know about this difference between XCI and NSP.
So with XCI (I suppose through the Stealth mode in SX OS) we can still install updates via Nintendo servers (if not banned of course)? Can the XCI be installed, or needs to stay as it is in the SD card?

 

[Redferne]

I did not know about this difference between XCI and NSP.
So with XCI (I suppose through the Stealth mode in SX OS) we can still install updates via Nintendo servers (if not banned of course)? Can the XCI be installed, or needs to stay as it is in the SD card?

No we assume that when you use an XCI it behaves like a real cartridge. So when you reboot in stock firmware and it appears to be like any cartridge game you played and you can update it the same way and it will raise no flag.
If you install it, it is then exactly like an nsp and a big flag for ban. Of course if you're already banned, one or the other doesn't matter.

The key word here is "assume" as we don't really know for sure. I only used XCI, no homebrew, and updated my "xci" games through stock firmware and I'm still not ban but that's only me and I won't say it is safe as we really don't know.

 

[cloudfe]

No we assume that when you use an XCI it behaves like a real cartridge. So when you reboot in stock firmware and it appears to be like any cartridge game you played and you can update it the same way and it will raise no flag.

Perhaps I'm missing something.
How can the OFW see the XCI in the SD card? Shouldn't this be something for which a homebrew is required?

 

[RedHunter]

Autorcm it seems it's still broken. I can boot fine into 7.0.1 emunand but if I choose 8.1 sysnand it gives me blackscreen.
Someone else with this problem?

 

[ZachyCatGames]

You forgot one thing . You need to add to Pro ..
We can play online
Still not banned

wdym. I’ve been playing online with atmosphere for about a year and haven’t been banned

Will you publically apologise and say you were wrong if TX release an exploit first?

Just like all the people posting that SX OS would NEVER be supported and work under OS 7.0.1?

Oh wait.. none of them did either.

to this date they haven’t discovered a single exploit on Switch, I somehow don’t think that’ll change

 

[Hayato213]

Autorcm it seems it's still broken. I can boot fine into 7.0.1 emunand but if I choose 8.1 sysnand it gives me blackscreen.
Someone else with this problem?

I doubt it has to do with AutoRCM, problem is probably your NAND.

 

[rockbmi]

I doubt it has to do with AutoRCM, problem is probably your NAND.

I have the same issue, when AutoRCM is enabled I cant boot stock firmware, when its disabled I can. SXOS works regardless though.

 

[RedHunter]

I doubt it has to do with AutoRCM, problem is probably your NAND.

What could it be? Maybe recreate the emunand? It was working fine on 7.0.1 sysnand.

 

[Hayato213]

I have the same issue, when AutoRCM is enabled I cant boot stock firmware, when its disabled I can. SXOS works regardless though.

Should check the hekate_ipl if you guys are using kosmos file pack, I am loading mine through Hekate then SX_OS, and Sysnand work fine, even though my sysnand is on a much lower firmware.

 

[stick267]

I know nobody has a crystal ball (or a uncle working there), but...
Do you guys think a stable release supporting 8.0.0/8.0.1 will take a while? I don't have much insight in the release history of SX OS.
As a follow-up, are the SX OS beta releases considered generally safe?

Just use the beta. They're generally pretty stable.

 

[RedHunter]

I have the same issue, when AutoRCM is enabled I cant boot stock firmware, when its disabled I can. SXOS works regardless though.

OK thanks so it's not just me, what's the mail to contact SX about this bug?

 

[gizmomelb]

OK thanks so it's not just me, what's the mail to contact SX about this bug?

there is no email address.. go to the SX OS forums and post there.

 

[rockbmi]

Should check the hekate_ipl if you guys are using kosmos file pack, I am loading mine through Hekate then SX_OS, and Sysnand work fine, even though my sysnand is on a much lower firmware.

Im not using kosmos or hekate, just the SXOS bootloader.

 

[sergux]

i just updated OFW and CFW to 8.0.1 when i press to boot OFW throught launch menu with autorcm installed it doesnt boot. Could anyone explain me what happens?

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

Autorcm it seems it's still broken. I can boot fine into 7.0.1 emunand but if I choose 8.1 sysnand it gives me blackscreen.
Someone else with this problem?

Its caused by the diference of efuses burned, you need to run the same version of firmware, thats how i solved it in the past but now its broken i have the same problem

Can i update to 8.0.1 from 7.0.1 using choidujour? or do I have to update to 8.0.0 first?

Thanks in advance

You can update directly to 8.0.1

 

[ady199]

Can i update to 8.0.1 from 7.0.1 using choidujour? or do I have to update to 8.0.0 first?

Thanks in advance

 

[chest0r]

Can i update to 8.0.1 from 7.0.1 using choidujour? or do I have to update to 8.0.0 first?

Thanks in advance

no you can directly update to 8.0.1.