- Joined
- Aug 6, 2017
- Messages
- 19,244
- Solutions
- 7
- Reaction score
- 10,211
- Trophies
- 2
- Age
- 31
- Location
- New York City
- XP
- 14,101
- Country

The data is collected in the form of yes and no questions. This eliminates nearly all guesswork of what is being asked of the user. Certain questions are even framed together to pinpoint the exact issue such as when a person is actively online or not when using CFW or homebrew. Also people escaping bans due to randomness is a phenomena that would occur when Nintendo bans in waves; there is no evidence that everyone flagged is banned during a wave. It also doesn't change the fact that not everyone who plays backups isn't banned just like how everyone who just uses CFW is also not banned.We are talking about self reported data, self reported data has always problems, especially for something like this, where we are talking about big time frames with a lot of differences in personal knowledge of the reporters. Especially since a small detail might be important for this, that are easily forgotten.
Also except for specific bans, bans normally happen in waves, to mitigate exactly the problem you mentioned. This is already enough, since you will probably not remember every detail you did in the last 1-3 months.
Complete randomness that keeps a lot of people unbanned on the other side would not make sense when bans happen because they think, that what you are doing is hurting their business. This would mean they are letting people do things for years by now that are hurting them.
But what we know is that Nintendo, like other companies, thinks piracy looses them money (whether or not it really does is another question), so it even makes sense from a business standpoint to ban everyone identified to use "backups". We also know there is enough info send while going online with a backup to directly identify them. We also know that nintendo has play logs of what people are playing, so we know that they can identify if we play a game that doesn't exist,, which in return means you install stuff, and thus easily identifies that you are using CFW and allows for a ban that will not hit someone innocent, so they ban.
Similar for cheating, we know that cheating makes the online experience worse, which is bad for the business, so they ban people if they identify it. Cheating often also can happen via multiple means, via direct memory manipulation, or via asset/rom manipulation (so directly cheatcodes or romhacking), so if they identify it via different means, depending on the game, they ban you.
Next we have the User Icon change. We know people misused this to use porn images as profile picture, which is not good for nintendos family friendly image. This likely is not an automatic ban, as long as the api is used the same as the switch does for stuff like miis, but they might have some automation that check for potential custom images, and then lets humans review this.
And even if its not the case, they will likely at least ban them if there are reports and they notice the image got tampered with.
As last guaranteed ban, we have the sketchy/weird eshop/requests part, that's a quick ban. This is probably a result from the 3DS and wiiu piracy vie nintendos CDN, which brings us back to the piracy topic, which nintendo doesn't want, so whenever they notice something weird they ban them, like it happened for some certificates of people running bots to check for game updates.
Last we have the logs. We know they keep some logs even after you factory reset the system, and we know that those files can only be modified by either using exploits to run code and access the raw files, or by dumping and restoring the Nand.
If those changes include a firmware downgrade that should not be possible because of fuses, nintendo can say for certain that there is CFW at work. We also don't really know if this be a guaranteed ban, or if this will just flag the switch to a potential ban if something else is detected, but at least we know that nintendo can identify that something got tampered with.
So those things are not just confirmed via the ban reports, and instead also via reversing/traffic analysis and understanding Nintendos position.
Now lets looks at why other things are potentially safe.
The usage of exostphere can not be detected by nintendo, since they cant make requests to things that don't exist to check for atmospheres extensions, since their trustzone would otherwise fatal.
Next to the kernel, devs would probably quickly notice, if nintendo started to call extensions there, so that is not happening.
Similar for the system modules implemented by atmosphere, its unlikely they are calling the apis from atmoshpere without noticing.
But what about timings? In theory they could use timings for detection. But the timings can change when the switch for example gets too hot and throttles down, even just the load through applications or switching between handheld and docked mode can probably change the timings of many things in the system.
Then how about the SD content. First, having specific files on the SD card doesn't mean its used, so you could wrongfully ban someone, just because the kid put some files on there. Seconds of a module would randomly start getting access to the SD and scanning the SD card, we would notice it.
Next lets continue with homebrew applications via album and title overwrite.
For the play log, it pretty much just looks like you are playing a lot of for example youtube, or really like to check your screenshots, nothing sus about that. what about errors and crashes that happen? Atmosphere re-implements fatal and creport, so those logs never get written to the system save.
So what about the missing telemetry? The same would happen if you just block the same urls atmosphere blocks, or if no problems happen, so nothing that proves you are using homebrew there.
So those are just the most important examples, as you see its not just user reports, its user reports, together with knowledge about the system and thinking about nintendos goals, which creates this list.
Is there always a rest risk? yeah, as mentioned before, but I normally mention what people should not do when using syscfw with clean atmosphere, so I already give them the required knowledge on the way, what they make out of it, is then their own doing.
Also my current personal reports are easier to proof, since proving you are not banned can easily be done by just playing online while using CFW. Proving why someone is banned on the other hand is hard, unless you documented everything you did, and even then its hard. Same for a report from me in case I get banned eventually, its unlikely I report everything I did, unless it was something that was causing a direct ban, instead of a wave ban.
I also do not see the point in divulging what Nintendo can or cannot see because they ultimately decide who gets banned and distribute a ban that may or may not match the offense. For example, people have mismatched fuse counts, myself included, but do not get banned despite that Nintendo can detect such a difference. Another example is the observation that people who have done save manipulation have received game bans as opposed to console bans. Why the discrepancy when some people who have only used homebew managed to full console bans can only be attributed to Nintendo's arbitrary behavior.
I disagree that it is easier to prove that you are not banned than banned. First off, bans never occur immediately so while you can showcase you are not banned at the moment, that doesn't prove you were doing said actions in the past. You might have done nothing for all I know. But this doesn't lead to a fruitful conversation because both parties can just accuse the other of lying or withholding information. That is why the truth-default theory exists; people are naturally more inclined to tell the truth than lie. If you start making assumptions that the data is incorrect, your argument is automatically less coherent because Occam's Razor states that the fewer assumptions you make, the closer to the truth you are. I reiterate, your own personal bias is preventing you from accepting the fact that people have been banned for use cases that don't conform with your definition of safe. If you believe that fact is false then provide the proof that it is because otherwise, it must be accepted as the truth and then you reform your conclusion from there.
Was it working before? If so, what was the last thing you did before it stopped working?When I try to load emummc sd card/atmosphere from hekate, it gives me a black screen and I have to force a reboot..help? It's not required because I just load sys cfw but I am curious why it doesn't work.
Well you'll have to follow a Switch hacking guide which will be a bit awkward for you because technically, your console is already hacked. But if you follow it, it will help contextualize everything that shop did for you and understand how to do it yourself should an issue ever arise. This is the guide I recommend for you to follow.Hi everyone.
I'm a complete noob on everything that has to do with this, so here are a few questions and some context.
i paid a local shop to do the whole process, im running hekate 6.2.0. no idea abouyt anything else (atmosphere, tinfoil, nut or anything else).
seeing a few vids on youtube i realize there is some access to "things" on the album section of the switch. also theres only two "sections" on the load screan of hekate one is emuMMC and the other one is the "original" instance of the switch.
i wanna get the most of it but im pretty sure the guys that did the whole process hide some stuff to avoid me downloading my ownstuff and having to pay them for every game or "app", so my "basic question" is where do i learn this whole thing and what do i need to lear so i can start squishing every single dime of this marvelous thing...
sorry about such and open question, but this is noob paradise, right?
Saves are affected by firmware version but only if you go down. Obviously, lower saves work on higher firmware versions because if they didn't, everyone would have issues when they update. Saves are also affected by game version. The same principle applies that lower versions work on higher versions but not vice versa. Its also fine if you update the game past the original version it was on.had issues with emuMMC so backed up saves using NxNandManager (Atmosphere 1.6.2 with firmware 17.0.0). created new eumMMC and installed Atmosphere 1.7.1 with firmware 18.1.0. will I have any issues restoring my saves using JKSV or another save restoring tool since the firmware version is different now than when I made the backups? wasn't sure if saves are affected by firmware version. do the installed game update versions affect whether saves can be restored? have installed some updates since making the new emuMMC so the game update versions differ from when I made the backups. thanks!











