Hacking Question Safety and future proofness of SX-Core?

4ur0r

Well-Known Member
OP
Member
Joined
Feb 7, 2015
Messages
392
Trophies
0
XP
599
Country
Italy
Can the vulnerability be patched?
If I hypothetically solder the modchip and mod my Switch, but never get into emunand, will I get banned if I go online on sysnand? What about just installing the chip and not modding it?

If I get banned, will my library be unaccessible as it was for the Nintendo 3DS days?

Kind regards.
 

Kubas_inko

"Something funny goes here."
Member
Joined
Feb 3, 2017
Messages
6,324
Trophies
1
Age
24
Location
I gues on earth.
XP
5,166
Country
Czech Republic
Considering that the SX Core is most likely glitching the Switch, it can't be fixed via update.
If you never ran CFW on sysnand, you are safe.
Unless ninty bans your account (which they almost never do on Switch), then your account and thus library will still be accessible.
 
  • Like
Reactions: 4ur0r

hartleyshc

Well-Known Member
Member
Joined
Oct 2, 2008
Messages
512
Trophies
2
Age
42
Location
Gainesville, FL
XP
1,419
Country
United States
Can the vulnerability be patched?
If I hypothetically solder the modchip and mod my Switch, but never get into emunand, will I get banned if I go online on sysnand? What about just installing the chip and not modding it?

If I get banned, will my library be unaccessible as it was for the Nintendo 3DS days?

Kind regards.

As said above, the way it glitches is based on the chip hardware itself. So it should be good for the life of the switch.

Theoretically yes installing it and only running sysnand is safe. It still modifies the boot0 and boot1 and modifies the fuses not blowing during an update (which if you update your sysnand, you should use the genuine boot feature). But as far as online play for sysnand, just clicking the button in the bootloader should be just fine.

The biggest issue you need to know is that you need to make sure that you're always booting into sysnand. If you click the cfw button without setting up emunand first, it's going to be running cfw on your sysnand and not the emunand.

Your library is still safe, however you'll no longer be able to access it if you don't have it already downloaded. To redownload games, etc, you'll need a new switch. However your account will be just fine.

I only reason Nintendo will ban your account is because of some sort of payment fraud. Either by doing a credit card chargeback on a purchase, or by installing a game by game code that has had payment issues (like buying a game from a CD key website. You have no idea if the credit card used to buy a key was stolen or not. If it was, your account will be the one that gets banned because of it).

Sent from my ONEPLUS A6013 using Tapatalk
 
  • Like
Reactions: 4ur0r

4ur0r

Well-Known Member
OP
Member
Joined
Feb 7, 2015
Messages
392
Trophies
0
XP
599
Country
Italy
Thank you both for your reply.

I understand that Nintendo usually doesn't ban whole Nintendo accounts and that's good, but could you please elaborate more on the " If you click the cfw button without setting up emunand first, it's going to be running cfw on your sysnand and not the emunand"?
I intend to backup my sysnand as soon as the chip is soldered and make an emunand completely separate from my sysnand. Is that possible? Is there a guide maybe?
 

hartleyshc

Well-Known Member
Member
Joined
Oct 2, 2008
Messages
512
Trophies
2
Age
42
Location
Gainesville, FL
XP
1,419
Country
United States
Thank you both for your reply.

I understand that Nintendo usually doesn't ban whole Nintendo accounts and that's good, but could you please elaborate more on the " If you click the cfw button without setting up emunand first, it's going to be running cfw on your sysnand and not the emunand"?
I intend to backup my sysnand as soon as the chip is soldered and make an emunand completely separate from my sysnand. Is that possible? Is there a guide maybe?
Yep. That's exactly what you want to do. You made it sound like you wanted to install the chip but only run sysnand and not really use the chip at all.


There's a thread here in this sub forum that lists the step by step on what you need to do. It's called like "sx after installation checklist" or something like that.



Sent from my ONEPLUS A6013 using Tapatalk
 
  • Like
Reactions: 4ur0r

4ur0r

Well-Known Member
OP
Member
Joined
Feb 7, 2015
Messages
392
Trophies
0
XP
599
Country
Italy
Thanks again for your reply.
Yeah I guess I wasn't clear enough.

I was under the impression the SX Core modchip was just an entrypoint for any exploit to be used and then install a cfw and emunand but I seem to understand now it's actually a device that Switches (sorry for the dumb joke) cfw and sysnad mode during the first boot after installing it. Am I right?
 

hartleyshc

Well-Known Member
Member
Joined
Oct 2, 2008
Messages
512
Trophies
2
Age
42
Location
Gainesville, FL
XP
1,419
Country
United States
Thanks again for your reply.
Yeah I guess I wasn't clear enough.

I was under the impression the SX Core modchip was just an entrypoint for any exploit to be used and then install a cfw and emunand but I seem to understand now it's actually a device that Switches (sorry for the dumb joke) cfw and sysnad mode during the first boot after installing it. Am I right?

You can load your own cfw, it's just software hasn't been updated to work with the SX Core/Lite.
V1 patched units with SX Core can apparently load their choice of cfw. But I can't confirm this as I've heard mixed reports and I have a Mariko device so I can't confirm for myself.

So for this moment, the thing that is confirmed to be working fully is SX OS through the bootloader. It's the same bootloader you'd load using the SX Pro.

Sent from my ONEPLUS A6013 using Tapatalk
 

4ur0r

Well-Known Member
OP
Member
Joined
Feb 7, 2015
Messages
392
Trophies
0
XP
599
Country
Italy
Sadly there is no "future" proof since it's closed source. Same thing happened with Gateway 3DS that they just one day said "fuck it" and left it high and dry.
I see your point, but then Gateway basically was using the same entrypoint as free custom firmwares.
What I meant by "future proofness" was more oriented to the patchability of said hardware entrypoint that from what I understand the SX-Core is.
Please correct me as the purpose of this thread was more a way of getting infos about Switch hacking.
 

linuxares

The inadequate, autocratic beast!
Global Moderator
Joined
Aug 5, 2007
Messages
13,135
Trophies
2
XP
17,846
Country
Sweden
I see your point, but then Gateway basically was using the same entrypoint as free custom firmwares.
What I meant by "future proofness" was more oriented to the patchability of said hardware entrypoint that from what I understand the SX-Core is.
Please correct me as the purpose of this thread was more a way of getting infos about Switch hacking.
As far as I know, no they can't patch this. It's a bug they abuse and inject the payload. But the SXOS itself is harder to say about.
 

4ur0r

Well-Known Member
OP
Member
Joined
Feb 7, 2015
Messages
392
Trophies
0
XP
599
Country
Italy
when they add support for the chips properly yeah

atmosphere works on v1 switches running core if you launch it through hekate first
This is good news for me as I have a V1 Switch and don't intend to use SX-OS but Atmosphere.

Thank you for your reply.
 

ZachyCatGames

Well-Known Member
Member
Joined
Jun 19, 2018
Messages
3,398
Trophies
1
Location
Hell
XP
4,207
Country
United States
Note: Hardware glitching != not patchable
If they were glitching during, ex. pk1ldr, it would absolutely be patchable via a software update.
But in this case, they’re glitching during bootrom execution (albeit very late in the bootrom, so some fun stuff is locked :(), so it is not patchable via a software update.
 
  • Like
Reactions: mathew77

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    LeoTCK @ LeoTCK: im going off now...I'll turn off my brain