Hacking Question Does using SX OS comprimise my Switch for using Atmosphère in the future?

  • Thread starter Thread starter Ian095
  • Start date Start date
  • Views Views 5,506
  • Replies Replies 19

Ian095

Well-Known Member
Member
Joined
Jun 25, 2018
Messages
387
Reaction score
118
Trophies
0
XP
879
Country
United Kingdom
So Hexkyz discovered brick code in SX OS which I believe further lead to the discovery that SX OS creates a random password on the eMMC (correct?).
So what I'm wondering is what issues could this cause for somebody who first used or tried SX OS but then went onto use Atmosphère once it is released?

I was tempted to use SX OS especially if by Late-October nothing matching it (Atmosphère surely will be released by then I hope) with similar capabilities to do what SX OS can do in regards to 'backups'. Now hearing there is brick code and that SX OS creates a random password on the eMMC is it even worth using at all when Atmosphère will one day likely take over when SX OS loses support?

Just to make it clear I'm not 100% sure on what the eMMC is, to begin with, which is why I'm asking this question if anyone even knows the possible implications due to this.

To summarise my question I'm asking if SX OS creating a password on the eMMC could cause issues with Atmosphère in the future if switching over.
 
So Hexkyz discovered brick code in SX OS which I believe further lead to the discovery that SX OS creates a random password on the eMMC (correct?).
So what I'm wondering is what issues could this cause for somebody who first used or tried SX OS but then went onto use Atmosphère once it is released?

I was tempted to use SX OS especially if by Late-October nothing matching it (Atmosphère surely will be released by then I hope) with similar capabilities to do what SX OS can do in regards to 'backups'. Now hearing there is brick code and that SX OS creates a random password on the eMMC is it even worth using at all when Atmosphère will one day likely take over when SX OS loses support?

Just to make it clear I'm not 100% sure on what the eMMC is, to begin with, which is why I'm asking this question if anyone even knows the possible implications due to this.

To summarise my question I'm asking if SX OS creating a password on the eMMC could cause issues with Atmosphère in the future if switching over.
You are confused. The brick code is when a random password is put on emmc (The nand of the switch) in order to Brick the console. This will only happen if you are trying to crack the os (at least that is what team xecuter says). You can use both sx os and atmosphere / hekate. It's worth it if you care about piracy or back up loading if you don't then just use hekate.
 
You are confused. The brick code is when a random password is put on emmc (The nand of the switch) in order to Brick the console. This will only happen if you are trying to crack the os (at least that is what team xecuter says). You can use both sx os and atmosphere / hekate. It's worth it if you care about piracy or back up loading if you don't then just use hekate. Oops some how tripple posted?

Oh, I understand now. So SX OS does absolutely nothing to the system that would cause issues for Atmosphère unless the brick code is somehow triggered, which from what I've heard is very unlikely anyway. Great to know, thank you!
 
  • Like
Reactions: gamemasteru03
Short answer: nope
Long answer: the only "compromise" I can see would be using Emunand. If you didn't backup your nand earlier before using SX no one is certain if there will be traces of CFW when you go online with emunand, therefore possibly warranting a ban. That's just my speculation tho, because that is not to say that by backing up your nand before would make you immune to ban anyways...
 
Last edited by lukhart,
  • Like
Reactions: Ian095
TX will support custom payloads from their device so the brick code if it exist shouldnt ever affect it.

Theoretically speaking, if the brick code is there it should only be made to protect against TX OS tampering...

But some things from TX OS are bad since data is saved on sysnand, it will be filled of crap stuff that may lead to bans so you will probably technically speaking loose the ability of being highly protected against bans (maybe fixable if you made a backup before running any hack or SX OS).

This is because with atmosphere emunand, you can update the console to last FW and use it online all original with no hacks, then you put the emunand SD in the console, enter in RCM, send payload and use atmosphere for backups and all other stuff completely offline, all FW data will be saved on the M-SD and nothing on the sysnand.

This will probably be the most safest option for online, as I can only see nintendo detecting only if they could log the RCM data, which is very unlikely...
 
  • Like
Reactions: lukhart and Ian095
shouldn't it be the other way around? use emunand for online, sysnand for piracy?
That's what we've said. But Emunand comes from the Sysnand, so if you used hacks on sys and then made a Emunand from it it would essentially have the same traces

Edit: I mistook the reply. Yes, the "correct" way would be emu for online and sys for offline
 
Last edited by lukhart,
shouldn't it be the other way around? use emunand for online, sysnand for piracy?
thats only if you really want to go online and dont want to update the console ever.

However atmosphere being a CFW surely will make it less safer than using the all original untouched code nintendo FW with original backups than using something with custom code running on latest FW for online stuff.
 
Well probably everything as its not emunand... so saves, caching, logs, profile data....... Probably just simply everything other than boot.dat, license.dat and the game backups which I think its the only things that go into the M-SD.

But I don't own TX OS and I'm also not expert, I just think it goes like that pretty much, while if it was emunand it would have everything emulated inside the M-SD and after changing M-SD everything would be gone, including saves, logs and whatever
 
Last edited by guily6669,
Well probably everything as its not emunand... so saves, caching, logs, profile data....... Probably just simply everything other than boot.dat, license.dat and the game backups which I think its the only things that go into the M-SD.

But I don't own TX OS and I'm also not expert, I just think it goes like that pretty much, while if it was emunand it would have everything emulated inside the M-SD and after changing M-SD everything would be gone, including saves, logs and whatever
Ok it just read that sx os writes stuff to sysnand which I doubt it does. Yes logs and stuff that horizon usually does but nothing sx os specific

Sent from my SM-G935F using Tapatalk
 
It doesn't exactly mean it necessarily needs to be SX OS adding stuff, but your account data will probably have saved in it games loaded and there timestamps and some other data, I have no proof, but 4 now all we know is that almost everything seems to be leading to bans as there is pretty random reports of bans including ppl who never even tried playing a backup and claimed to just try SXOS and ban...

It doesnt mean the bans are coming directly from SXOS, but indirectly since if you played backups and other stuff, you will have games registered somewhere that you never owned and that comes from the ability of being able to play games on SX OS, so we can't say its safe 4 now...

No idea on anything 4 now, GBATemp in my opinion is doing a nice job collecting banned people's data to see if later we can match every report and get better ideas on what might be causing and what seems safe...

ps: I just don't know how the bans came fast, it seems the beautiful tradition of banwaves is dead :rofl2:. Though if I was nintendo main boss, I would totally let everyone online enjoying, then put the paid online on, wait a few time until there is a big drop in hacked switches buying it then ban everyone and grab their money from the online paid service :toot: (But I think nintendo 4 now is not as evil as me:P).
 
Last edited by guily6669,
It doesn't exactly mean it necessarily needs to be SX OS adding stuff, but your account data will probably have saved in it games loaded and there timestamps and some other data, I have no proof, but 4 now all we know is that almost everything seems to be leading to bans as there is pretty random reports of bans including ppl who never even tried playing a backup and claimed to just try SXOS and ban...

It doesnt mean the bans are coming directly from SXOS, but indirectly since if you played backups and other stuff, you will have games registered somewhere that you never owned and that comes from the ability of being able to play games on SX OS, so we can't say its safe 4 now...

No idea on anything 4 now, GBATemp in my opinion is doing a nice job collecting banned people's data to see if later we can match every report and get better ideas on what might be causing and what seems safe...

ps: I just don't know how the bans came fast, it seems the beautiful tradition of banwaves is dead :rofl2:. Though if I was nintendo main boss, I would totally let everyone online enjoying, then put the paid online on, wait a few time until there is a big drop in hacked switches buying it then ban everyone and grab their money from the online paid service :toot: (But I think nintendo 4 now is not as evil as me:P).
Yeah that's what Microsoft did back on the Xbox 360, waited for a big game like MW2 to come out and ban everyone in waves.
 
Yep, at least it always left a lot of ppl convinced to be completely stealth and safe so they could buy XBL and when the time is right they get hammered with a ban :D.
 
I am on the same boat, mate. I bought the Switch to play backups, but it being too early in the 'scene' it is not easy to tell which option is the most complete or how long one should wait for it. I do not care about online play, but I do care about updating games and DLC, things that are still on a grey area. Then again, my Switch is collecting dust, which is not very smart either.
 
I am on the same boat, mate. I bought the Switch to play backups, but it being too early in the 'scene' it is not easy to tell which option is the most complete or how long one should wait for it. I do not care about online play, but I do care about updating games and DLC, things that are still on a grey area. Then again, my Switch is collecting dust, which is not very smart either.

It'll definitely pay off at the end of the year when Pokémon and Super Smash Bros. come out.

I've not played my console properly in months, hence why I've managed to stay on 4.1.0 because I haven't used the console in ages.

I'm sure as soon as Atmosphére is released it won't take long for a version that plays backups to be released.
If not I'll either pay for SX OS or if people actually crack it as they've been claiming to be trying to do then I'd maybe take the risk if it hasn't bricked peoples consoles.

I'd love to jump on board with SX OS right now but I don't want to update so I'd get little use out of its primary function. Plus nobody seems to know what causes them to be banned.
 
I've not played my console properly in months, hence why I've managed to stay on 4.1.0 because I haven't used the console in ages.

I'd love to jump on board with SX OS right now but I don't want to update so I'd get little use out of its primary function. Plus nobody seems to know what causes them to be banned.
Tell me about it. My Switch is still on 4.0.1, and I have only played it once, to check that the hardware worked as expected.

I would gladly pay for SX OS, Atmosphere or an alternative, if the cons of each option were clear (bans, firmware changes, loading options, etc.) Right now, it is trial an error, and thus I prefer to keep reading and learning.
 
What about the reverse. does the use of atmosphere on 6.2.0 compromise the use of sx os in the future?
 
can nintendy scan your sd??

like for when you go online, can they scan all the illegal shit you got on your sd card??
 
Last edited by gundamu,

Site & Scene News

Popular threads in this forum