Hacking [Tutorial] How to update your backups using SX OS with the least ban risk

  • Thread starter Thread starter NeoSlyde
  • Start date Start date
  • Views Views 58,015
  • Replies Replies 169
  • Likes Likes 3
Yeah, sounds believable.

But since most online backups will be used a 100 or probably a lot more often it should be easy for Nintendo to detect those bad certificates.
Assuming that certs are stored outside of the carts once used in the system and removed. I don't remember this being confirmed, which is why this thread exists.
 
talking about Certificates when i backed up all my games i gotten .bin for all of them do i need them for SX OS? Say i just dump all my games onto a 128gb / 256gb card and put the .bin will i be safe? or how do i make sure the sx is using the cert bin?
 
I don't know what the case is for checking and downloading updates, but I wouldn't be surprised if it's the same as verifying before you can play online. Check out the write up by SciresM. Basically the game card, or digital file, contains an encrypted certificate that is created for whatever medium you have. This certificate is 100% unique to the digital download or the specific cart that you can physically touch.

If I'm right and this information is sent up when you request an update from Nintendo, then they can very easily use an algorithm to determine if what you are requesting an update for is a pirated copy.

However, lets say if you own the game card. You should be fine to dump it and install it and play/update it with no issues. Though, it does seem the certificate has other encrypted info, so Nintendo could tell if it was originally for a game card and is now a digital backup. Obviously they don't do this yet, but they may be able to. If you end up sell the game card, I'd think you should be fine. However, if Nintendo sees someone playing the game at the same time as you, then they will likely notice it.

If the certificate has already been marked as banned and you go to update, and I'm right, you can consider yourself banned.

I'd bet that In these early times no one will be getting banned. In about a week or so, however, I wouldn't be surprised if people stop being able to get updates, go online, etc.

I'm not an authority on this information and this is purely speculation. Stay safe.
 
  • Like
Reactions: Salazar-DE
Don't forget there is an option to match your version to a local user. You could find a friend with a legit copy and copy their update data... But honestly, if that's possible offline, why would Nintendo bother to check a cert for an update from their server? I'm taking the risk and updating stuff. I'll let you know if I get banned.
 
game-update are common tickets, it's not a personal ticket.
Also, banned ShinyQuagsire can still be updated the game.
This means Ninty has not checked user data when updating.
Probably, ninty doesn't ban user accounts even if you update with SX OS.
 
  • Like
Reactions: Batpeter
Sorry I have to ask but is it not possible to block certain servers like the one that ask for logs? On MacOs there are tools like Little Snitch which blocks every outgoing connection and asks for permission. Under Windows this can also be done with the host file. Wouldn't this also be possible on the switch, so that you can safely update but prevent the upload of specifig log files?
 
Did yall forget about Match Local Version?

Problem?
sjVLi6N.jpg

IqLaxVJ.jpg

rFWEEhy.jpg

8MSD7aH.jpg
I indeed forgot about that feature totally lol.
In case you can even download updates when you're banned, we only need a separate Switch which serves as a "download update unit", which might getting banned soon and use it to share the bloody updates via local WiFi to our "real unit". :D

By the way here's a possible solution:
Play a backup from SD through SX OS.
It should create an icon on your homescreen on Horizon.
Do a full NAND dump.
Look inside that dump whether the unique header of the game has been stored there or not. (It's better to use an own dump because BBB dumps don't have the headers)
If not we can update all backups without worrying.
 
Last edited by lordelan,
  • Like
Reactions: cearp and RapidRaid
Do not do this! The cart metadata is still saved by Horizon, and will be reported to Nintendo's servers = ban. SX OS is not the issue, the unique cart data is.

if i may ask what to do to clear the switch meta data and make it like it has never been used SXOS??? is a raw nand dump restore will do the trick???
 
And I have an idea, Simon' s HACDN tool. Its only send redownload request. And doesnt need header or other things. (But maybe ninty servers checks you habe the game, idk)
 
Its functionally equivalent to just powering on the Switch. The option for launching OFW is in case you are using AutoRCM in which case you cannot normally turn on your console without sending a payload. And yes, the latter portion still makes it unsafe as we are not sure of what information the console logs during CFW and stores it within the console only to be sent the next time the Switch is connected online.
??? if ur using autorcm you cant launch ofw without sending the payload. thats not what that options for.
 
You can actuqlly boot into OFW with hekate.

Sent from my SM-G950F using Tapatalk
read what i was quoting, i never said you couldn't boot into ofw with hekate or sx os. im saying that sx os having a ofw option wouldn't help get into ofw from autorcm
 
However, lets say if you own the game card. You should be fine to dump it and install it and play/update it with no issues. Though, it does seem the certificate has other encrypted info, so Nintendo could tell if it was originally for a game card and is now a digital backup.
iirc, sx still play the backup as cartridge game, not installed digital title.
 
By the way here's a possible solution:
Play a backup from SD through SX OS.
It should create an icon on your homescreen on Horizon.
Do a full NAND dump.
Look inside that dump whether the unique header of the game has been stored there or not. (It's better to use an own dump because BBB dumps don't have the headers)
If not we can update all backups without worrying.

Good idea, I will attempt to give this a go this afternoon.
 
By the way here's a possible solution:
Play a backup from SD through SX OS.
It should create an icon on your homescreen on Horizon.
Do a full NAND dump.
Look inside that dump whether the unique header of the game has been stored there or not. (It's better to use an own dump because BBB dumps don't have the headers)
If not we can update all backups without worrying.
This doesn't confirm anything as updating a game never requires the header. That's why people are able to update their backups. And as long the dumping tool you use is good enough, the header should remain there. What has not been confirmed is if running the CFW leaves traces within the console itself that may be present when booting into OFW.
 

Site & Scene News

Popular threads in this forum