Which homebrew?
Cause not any cfw will leave traces on the nand after a reboot (since you were not online while using it, it doesn't make sense).
Last edited by mariogamer,
Cause not any cfw will leave traces on the nand after a reboot (since you were not online while using it, it doesn't make sense).
So I just restored the NAND of my switch back to its original unhacked state, however I accidentally restored the slightly older backup rather than the newest one. That backup I also accidentally made with the wifi settings saved so it connected to the internet. They both had the exact same software but the only difference was that I had redownloaded several games to 'move' their save location.
Does anyone know if Nintendo can detect some sort of mismatch?
Does anyone know if Nintendo can detect some sort of mismatch?
I want to know this also. I have only 1 backup and that is the older one . I hope Nintendo don't keep track.
If they can detect cleared logs, I'm sure they can detect this. I made a bigger goof-up though, I started with 5.0.2 and upgraded (legit) to 5.1.0. When I restored, it was to 5.0.2. Whoops! So, as of a couple weeks ago (just before 6.0 came out) it doesn't look like it'd cause a ban (I upgraded to 6.0 and last I checked I'm still not banned).
If it's the same software version (i.e. we're talking about an older backup of 5.1.0, but you've been online since then), I'd recommend doing a factory reset before letting it connect. That could explain away some of the discrepancies. Anything you can do to make it look less suspicious.
My screw up is with and without exfat update. Also when i officially update exfat patch, I boot before to sxos. Not sure booting to sxos trigger error log even though I didn't install any nsp.
It doesn't "seem" that simply booting to SX OS is enough to trigger a ban. If it were me, I'd just lie low for a bit, don't do anything (else) that could cause a ban. No SX OS, no homebrew, just straight legit stuff until the next ban wave. If you're bored, you could go into maintenance mode and do a reset (have option of keeping save files, so you won't have to use homebrew to restore). Do a nand backup as soon as the reset is done, before you've setup anything.
Yea luckily my system version was still the same, as well as the logs. The backups were made only like a day apart. But I wonder if the sudden change in game location can be noticed, or alternatively, if two different download instances of the same application appear different to Nintendo. Well I guess we'll see what happens...
It's not that accurate. I'm using SXOS since July and updating XCI games from OFW and i'm still good.
You skipped the answers to a lot of questions so I posted the ones you missed down below. Please review and answer them.
If you cannot access the eShop, when was the last time you were able to?
Do you get error code 2137-7403 trying to update your system firmware? Y/N
Can you login to Nintendo's website using your linked Nintendo Account? Y/N
Connect to Internet w/ homebrew/non-TX CFW? Y/N
Connect to eShop while using CFW/homebrew? Y/N
Did you update your firmware using ChoiDujour or ChoiDujourNX? Y/N
Did you install the exFAT update offline? Y/N
receive-lp1.dg.srv.nintendo.net blocked and/or "Don't Share Usage Information" ticked under "Other Settings"? Y/N
Do you have eclct disabled (look for pm.kip under sysmodules/modules)? Y/N
Do you have creport enabled (look for a folder named 0100000000000036 under titles)? Y/N
What firmware(s) were you on when you cleared error logs prior to going online? Y: X.X.X/N
Disabled "Send Error Information" in System Settings? Y/N
Wi-Fi settings deleted in CFW? Y/N
Airplane mode? Y/N
Auto-Update Software Enabled in System Settings? Y/N
Console/Account Region(s)
What device(s) do you use to send payloads with?
It is accurate because its not just one or two instances of people banned. There is a difference between not being banned and being safe; the former implies there is an unconfirmed ban risk while the latter confers a risk of 0%. Need I remind you that it has only been 4 months since bans have been hammered out and Nintendo banned users for several years on the 3DS. Lastly, this is like saying that usage of .NSP files will lead to a ban when the data suggests otherwise. There are people banned for using .XCI or .NSP as well as people not banned for using .XCI or .NSP
So just to reiterate:
- Usage of .XCI files can get you banned, even if you update them in OFW
- Not being banned is not even close to something being confirmed as safe
- It hasn't even been half a year since bans have started
That person also cleared error logs on 5.X. As long as you never clear your error logs, you should be fine using a GBA emulator without a ban but I cannot 100% guarantee your safety.
If I remember correctly, in the PRODINFO partition, on the main physical partition. (Physical partition being boot0, boot1 and rawnand (which is the main one))
Last edited by mariogamer,
Hello, everyone.
I used ReiNX toolkit to make a backup of my NAND before installing any NSP or XCI on my Switch. This was before I found out that backups using Hekate are the truly clean ones.
I did not find any information about bans from people who restored a backup from ReiNX. The only thing that I found is that the ReiNX backups are not totally clean, but no real reports from people who used it and went back to OFW without getting ban.
Does anyone have ever been banned after restoring a ReiNX backup? Or the only way to know is to restore my backup and go online to find out?
I used ReiNX toolkit to make a backup of my NAND before installing any NSP or XCI on my Switch. This was before I found out that backups using Hekate are the truly clean ones.
I did not find any information about bans from people who restored a backup from ReiNX. The only thing that I found is that the ReiNX backups are not totally clean, but no real reports from people who used it and went back to OFW without getting ban.
Does anyone have ever been banned after restoring a ReiNX backup? Or the only way to know is to restore my backup and go online to find out?
Which emulator was this and with which packages? Creport should really make emulators largely innocuous unless something else went wrong somewhere.
Toolkit is too for any data to have been collected upon it just like TX's EmuNAND. If you backed up the NAND in the toolkit without doing anything else beforehand, the NAND should be clean but there is no way to tell.
