SX OS 2.6 Beta released: full support for Nintendo Switch firmware 7.x

From Team Xecuter:

This new 2.6 BETA of SX OS adds full support for Nintendo Switch firmware 7.x, including ALL functionality you expect when using our product. We've been pioneering our own unique and proprietary solution for defeating any future firmware protection and we're quite happy with the results so far.

This release is marked as BETA because we changed things drastically under the hood to streamline future firmware updates and some things may inadvertently behave differently.

That does not mean it hasn't been vetted at all, so give it a shot today!

Of course, we haven't been sitting idly behind the scenes either. A lot of our development resources and attention has been dedicated to bringing SX OS to those "unhackable" switches. We are working hard to bring the SX OS experience to all of you who are stuck with an "unhackable" switch. Stay tuned for more news!

Download here: -REMOVED-
 
Last edited by linuxares,

oblid

Well-Known Member
Newcomer
Joined
Oct 1, 2018
Messages
49
Trophies
0
Age
41
XP
349
Country
Uruguay
https://twitter.com/balika011/status/1107748638095220738?s=19

Triszka Balázs says:
"There is more to the story, and this is gonna be EPIC! They store the root key in plaintext, but they are not using it. On 7.0+ they set the tsec_root_keys + 0x10 then don't even touch it. It's a leftover. What they are using is a seed decrypted using slot 7. That they not clear."

Somebody can explain?

Mike Heskin says:
"This means the plaintext key was left by accident and there was already a system in place to use an obfuscated version. As of v2.6.1, the plaintext key is no longer present in the binary and the obfuscated path is taken just like before."
 
Last edited by oblid,

V-Temp

Well-Known Member
Member
Joined
Jul 20, 2017
Messages
1,227
Trophies
0
Age
34
XP
1,342
Country
United States
https://twitter.com/balika011/status/1107748638095220738?s=19

Triszka Balázs says:
"There is more to the story, and this is gonna be EPIC! They store the root key in plaintext, but they are not using it. On 7.0+ they set the tsec_root_keys + 0x10 then don't even touch it. It's a leftover. What they are using is a seed decrypted using slot 7. That they not clear."

Somebody can explain?

Mike Heskin says:
"This means the plaintext key was left by accident and there was already a system in place to use an obfuscated version. As of v2.6.1, the plaintext key is no longer present in the binary and the obfuscated path is taken just like before."

Basically they left the key in plain-text out of oversight/rush, and it was in no capacity used (in its plain-text form, just loaded) much like the code remnants of sept, though those still seem to have been left over. It has been removed in plaintext from the boot, and the method is an obfuscated use of seed slot 7 as balika points out.
 
Last edited by V-Temp,
  • Like
Reactions: gizmomelb and oblid

Meepers55

Flintstones Regular
Member
Joined
Aug 7, 2018
Messages
318
Trophies
0
XP
949
Country
United States
https://twitter.com/balika011/status/1107748638095220738?s=19

Triszka Balázs says:
"There is more to the story, and this is gonna be EPIC! They store the root key in plaintext, but they are not using it. On 7.0+ they set the tsec_root_keys + 0x10 then don't even touch it. It's a leftover. What they are using is a seed decrypted using slot 7. That they not clear."

Somebody can explain?

Mike Heskin says:
"This means the plaintext key was left by accident and there was already a system in place to use an obfuscated version. As of v2.6.1, the plaintext key is no longer present in the binary and the obfuscated path is taken just like before."
So I was right about it being temporary after all. As I've stated before, all this arguing over nothing.
 
  • Like
Reactions: gizmomelb

josete2k

Well-Known Member
Member
Joined
Apr 24, 2009
Messages
678
Trophies
1
Age
43
Location
Spain
XP
1,603
Country
Spain
https://twitter.com/balika011/status/1107748638095220738?s=19

Triszka Balázs says:
"There is more to the story, and this is gonna be EPIC! They store the root key in plaintext, but they are not using it. On 7.0+ they set the tsec_root_keys + 0x10 then don't even touch it. It's a leftover. What they are using is a seed decrypted using slot 7. That they not clear."

Somebody can explain?

Mike Heskin says:
"This means the plaintext key was left by accident and there was already a system in place to use an obfuscated version. As of v2.6.1, the plaintext key is no longer present in the binary and the obfuscated path is taken just like before."

Ergo, SXOS is allowed to be linked here.
 
  • Like
Reactions: gizmomelb

ZachyCatGames

Well-Known Member
Member
Joined
Jun 19, 2018
Messages
3,398
Trophies
1
Location
Hell
XP
4,209
Country
United States
I’m pretty sure they still have the key in it, it’s just obfuscated/hidden now

(at least that’s how I read hexkyz’s tweet)

And even if the key is completely removed there’s still other stuff in it that makes it violate this website’s rules
 
Last edited by ZachyCatGames,

oblid

Well-Known Member
Newcomer
Joined
Oct 1, 2018
Messages
49
Trophies
0
Age
41
XP
349
Country
Uruguay
I’m pretty sure they still have the key in it, it’s just obfuscated/hidden now

Yes... You are right. Balázs and Heskin? Who know them...

Like before? Before that 2.6? 2.5.3 was ok by gbatemp.
And the censorship of link come for keys. Already say that 2.5.3 was ok.
 
Last edited by oblid,

AkGBA

Nope
Member
Joined
Feb 14, 2007
Messages
345
Trophies
1
XP
1,437
Country
France
I know one day TX will drop support of SXOS. I bought it knowingly, while thinking about Gateway.
In the mean time, I'm really glad they found a way to run on 7.0.x.
Don't know why, but I really prefer xci loading than nsp installing.
Anyway, keep up the good work TX.
 
  • Like
Reactions: gizmomelb

metal921

Active Member
Newcomer
Joined
Aug 28, 2018
Messages
41
Trophies
0
Age
31
XP
139
Country
United States
Anybody still have issues getting this to run? I have sys on 7.0.1 and emunand on 6.2 but for some reason I still can’t boot just blackscreens :/
 

jacopastorius

Well-Known Member
Member
Joined
Oct 24, 2018
Messages
164
Trophies
0
Age
44
XP
316
Country
Italy
I know one day TX will drop support of SXOS. I bought it knowingly, while thinking about Gateway.
In the mean time, I'm really glad they found a way to run on 7.0.x.
Don't know why, but I really prefer xci loading than nsp installing.
Anyway, keep up the good work TX.
what is gateway?
 

JJTapia19

I fight for my friends.
Member
Joined
May 31, 2015
Messages
2,171
Trophies
1
Age
32
XP
2,438
Country
Puerto Rico
Anybody still have issues getting this to run? I have sys on 7.0.1 and emunand on 6.2 but for some reason I still can’t boot just blackscreens :/
Try a couple of times. I'm also getting low boot rate on my emunand since 2.6. I've reported it on their forums.
 
  • Like
Reactions: metal921

_hexkyz_

Well-Known Member
Newcomer
Joined
Oct 4, 2018
Messages
60
Trophies
0
XP
447
Country
United States
I’m pretty sure they still have the key in it, it’s just obfuscated/hidden now

(at least that’s how I read hexkyz’s tweet)

And even if the key is completely removed there’s still other stuff in it that makes it violate this website’s rules

What happens is that a key is set in keyslot 7 at the end of payload_98000000 and then patcher_BFC70000 does:
- Initialize tmp_buf as 16 0xAA bytes;
- Call se_aes_ecb_decrypt_block(0x07, tmp_buf, 0x10, seed_buf, 0x10);
- Call decrypt_data_into_keyslot(0x0C, 0x07, seed_buf, 0x10).

The se_aes_ecb_decrypt_block is useless and was likely there just for testing (it's still there on v2.6.1 and you can find it by looking for 0xAAAAAAAA in the disassembled code).
This was already being used in v2.6, but they also had a piece of code that would load the actual plaintext key from memory. On v2.6.1 the key and this leftover code was removed.

The user @Falo has shared an accurate screenshot comparison of v2.6 vs. v2.6.1 here: https://gbatemp.net/threads/sx-os-2...license-activation.533956/page-3#post-8559251
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • Sicklyboy @ Sicklyboy:
    I'm not familiar with the technicalities of the differences between the two versions, but I'm wondering if at least some of those differences are things that you could port over to the US version in your patch without having to include copyrighted assets from the EU version
  • TwoSpikedHands @ TwoSpikedHands:
    @Sicklyboy I am wanting to fully change the game and bend it to my will lol. I would like to eventually have the ability to add more characters, enemies, even have a completely different story if i wanted. I already have the ability to change the tilemaps in the US version, so I can basically make my own map and warp to it in game - so I'm pretty far into it!
  • TwoSpikedHands @ TwoSpikedHands:
    I really would like to make a hack that I would enjoy playing, and maybe other people would too. swapping to the EU version would also mean my US friends could not legally play it
  • TwoSpikedHands @ TwoSpikedHands:
    I am definitely considering porting over some of the EU features without using the actual ROM itself, tbh that would probably be the best way to go about it... but i'm sad that the voice acting is so.... not good on the US version. May not be a way around that though
  • TwoSpikedHands @ TwoSpikedHands:
    I appreciate the insight!
  • The Real Jdbye @ The Real Jdbye:
    @TwoSpikedHands just switch, all the knowledge you learned still applies and most of the code and assets should be the same anyway
  • The Real Jdbye @ The Real Jdbye:
    and realistically they wouldn't

    be able to play it legally anyway since they need a ROM and they probably don't have the means to dump it themselves
  • The Real Jdbye @ The Real Jdbye:
    why the shit does the shitbox randomly insert newlines in my messages
  • Veho @ Veho:
    It does that when I edit a post.
  • Veho @ Veho:
    It inserts a newline in a random spot.
  • The Real Jdbye @ The Real Jdbye:
    never had that i don't think
  • Karma177 @ Karma177:
    do y'all think having an sd card that has a write speed of 700kb/s is a bad idea?
    trying to restore emunand rn but it's taking ages... (also when I finished the first time hekate decided to delete all my fucking files :wacko:)
  • The Real Jdbye @ The Real Jdbye:
    @Karma177 that sd card is 100% faulty so yes, its a bad idea
  • The Real Jdbye @ The Real Jdbye:
    even the slowest non-sdhc sd cards are a few MB/s
  • Karma177 @ Karma177:
    @The Real Jdbye it hasn't given me any error trying to write things on it so I don't really think it's faulty (pasted 40/50gb+ folders and no write errors)
  • DinohScene @ DinohScene:
    run h2testw on it
    +1
  • DinohScene @ DinohScene:
    when SD cards/microSD write speeds drop below a meg a sec, they're usually on the verge of dying
    +1
  • Psionic Roshambo @ Psionic Roshambo:
    Samsung SD format can sometimes fix them too
  • Purple_Heart @ Purple_Heart:
    yes looks like an faulty sd
  • Purple_Heart @ Purple_Heart:
    @Psionic Roshambo i may try that with my dead sd cards
    +1
  • Psionic Roshambo @ Psionic Roshambo:
    It's always worth a shot
  • TwoSpikedHands @ TwoSpikedHands:
    @The Real Jdbye, I considered that, but i'll have to wait until i can get the eu version in the mail lol
  • I @ I-need-help-with-wup-wiiu:
    i need help with nusspli failed downloads, can someone respond to my thread? pretty please:wub: