I got asked this question and didn't know what to say. I guess it's safe to take a backup of your original nand and Nintendo can't notice but I want to be sure.
Hacking Can you get banned for NAND Backup?
- Thread starter ABigMoustache
- Start date
- Views 11,576
- Replies 27
Listen if you're so worried about getting banned
Just avoid everything homebrew and RCM
Haha if you're not going to help please don't reply. As I said, it was a question someone made me, I don't really care.
Backing up your NAND is only just the very start of things that might and probably will get you banned. If that worries you then you're playing the wrong game man.
I have resigned to the fact that the moment I decided to mess with it was the moment I kissed goodbye to my legit account and any thoughts of online until I get another legit one. If you're not prepared for that then you're going to have a bad time.
I have resigned to the fact that the moment I decided to mess with it was the moment I kissed goodbye to my legit account and any thoughts of online until I get another legit one. If you're not prepared for that then you're going to have a bad time.
Last edited by Albytrozz,
There isn't as nobody knows for sure exactly what Nintendo can see, I don't know whether we ever will either, however over time we will make a note of what works and what doesn't and can give a more informed answer, however as of this moment in time we can't.
If you don't wanna get banned don't do anything you're not supposed to
no, is impossible for nintendo as cannot see you entered rcm mode as long as you dont start the os with hekate. nothing is written anywhere. so if you just do the rcm, hekate, then nand backup, then poweroff from hekate, then start swicht normaly, then nintendo wont ban you because they cannot see you did nand backup..
Truth of the matter is, we just don't know for sure, rcm shouldn't log it but the console might log its been in rcm which could get you banned. Nobody knows for sure
again, it cannot.. it doesnt have anywhere to log it.. rcm does not and cannot wrote to anything, which should be obvious as it is the cpu itself recovery mode. you can even start it with nand physically removed... and obviously, hekate itself doesnt wrote specific files to the nand, not only because not mounted as long as os isnt started, but also because devs wouldnt do it obviously..
once sagain, might be different if you boot from hekate, even stock (although probably not), but if you poweroff after you booted from hekate wothot launch switch os, then impossible to be banned.
also if it was, you could also be ban for linux..
Source, I'm wondering how you know this definitively. Like I said, it's unlikely but it's not impossible.
for source of what are you asking for exactly? if you don't believe rcm is the cpu "recovery mode", you can read around for a bit on this forum, or from the developpers themself, or even from the tegra documentation, which is on nvidia website
for the "cannot write to anything", simply because there is nowhere to write to. ram and cpu cache? clean after poweroff. nand? nowhere to write to. boot partitions and such must be signed, and write to would break. safe system and user partitions are not mounted, so cannot write any file to. the last remaining bits of nand, which are most likely not use by nintendo except fpr the service and not by horizon os, do not contain a "number of rcm boot"..
is bother to find link because on phone, but can search on switchbrew for boot sequnce and flash flashsystem.
then for them to find out you used rcm, must be some physical separate hidden flash storage on motherboard made specially for counting number of rcm reboot. but i think we can all agree that would be conpiricy theory and wouldve found about it by now, especially since have dumped bootrom
OK, all I said is its not impossible. But I'm done with this discussion cause we seem to be going round in circles and that's not very productive for anyonefor source of what are you asking for exactly? if you don't believe rcm is the cpu "recovery mode", you can read around for a bit on this forum, or from the developpers themself, or even from the tegra documentation, which is on nvidia website
for the "cannot write to anything", simply because there is nowhere to write to. ram and cpu cache? clean after poweroff. nand? nowhere to write to. boot partitions and such must be signed, and write to would break. safe system and user partitions are not mounted, so cannot write any file to. the last remaining bits of nand, which are most likely not use by nintendo except fpr the service and not by horizon os, do not contain a "number of rcm boot"..
is bother to find link because on phone, but can search on switchbrew for boot sequnce and flash flashsystem.
then for them to find out you used rcm, must be some physical separate hidden flash storage on motherboard made specially for counting number of rcm reboot. but i think we can all agree that would be conpiricy theory and wouldve found about it by now, especially since have dumped bootrom
and what is source for your claim of it being not impossible? i provided you with evidence for why i am positive is impossible to detect. now do the same and explain why you think it is possible.. else it is based on absolutely nothing and isnt good advice at all..
It's pretty much impossible for you to get banned by making a NAND backup. However, if you RESTORE that backup then that could potentially result in a ban, depending on the situation. Particularly if you've been online between the time the backup was made and the time the restore was done.
For example, say you were running on firmware 5.0.2, and made a NAND backup. Then, Nintendo releases 5.0.3, and some jackass that borrowed your Switch went ahead and updated it. Afterwards they played a little Splatoon 2 online, and because of the telemetry data Nintendo knows that your console has been updated to 5.0.3.
So you get your Switch back, and give your jackass friend a good lashing. Then you decide to restore your NAND backup, so that you'll be downgraded back to 5.0.2. Afterwards, you play online.
Nintendo sees that you're on 5.0.2, but, wait a minute, you were on 5.0.3 earlier, how could that have happ-
BAM!!! DROPS THE BANHAMMER!!!
That's only one example, Nintendo could have other data fields that would work for this too. Like, total hours played. If it was 1,000 yesterday, and you restored a backup from when you only had 700 hours logged, Nintendo could potentially see the discrepancy and ban you.
But so far, I don't think we've had any concrete evidence that Nintendo has ever banned anyone based on that sort of data. At least not yet. Only time will tell.
For example, say you were running on firmware 5.0.2, and made a NAND backup. Then, Nintendo releases 5.0.3, and some jackass that borrowed your Switch went ahead and updated it
. Afterwards they played a little Splatoon 2 online, and because of the telemetry data Nintendo knows that your console has been updated to 5.0.3.So you get your Switch back, and give your jackass friend a good lashing. Then you decide to restore your NAND backup, so that you'll be downgraded back to 5.0.2. Afterwards, you play online.
Nintendo sees that you're on 5.0.2, but, wait a minute, you were on 5.0.3 earlier, how could that have happ-
BAM!!! DROPS THE BANHAMMER!!!
That's only one example, Nintendo could have other data fields that would work for this too. Like, total hours played. If it was 1,000 yesterday, and you restored a backup from when you only had 700 hours logged, Nintendo could potentially see the discrepancy and ban you.
But so far, I don't think we've had any concrete evidence that Nintendo has ever banned anyone based on that sort of data. At least not yet. Only time will tell.
Similar threads
