Interesting. Good to know for future reference.
A lot of people have copped bans from trying this at this point. So, ya, don't do it.
Interesting. Good to know for future reference.
Just combed through them again and you're mostly right; majority of the homebrew only bans were due to connecting online with homebrew (with the exception of 2 with one of them for clearing error logs). Doesn't mean what you're doing is 100% safe but 99% safe is pretty good too I guess.It seems like not make any sense to me and most homebrew bans only used access to online (WiFi setting enabled) and eShop simultaneously that wasn’t case for me when I used strictly offline, also I cleared the logs before go to online as you said that clear the logs are dangerous if went online with hack at same time until I unlinked and sold my Switch without any ancknowledge about ban and Nintendo told me that many people tried to unlink had banned Switch. I spent all night to check the ban reports.
I said that homebrew will be used in 3.0.2 to import saves only and remove afterwards, so no hacks will be continued after upgrade to 6.0. Restore clean NAND removes any saves that import?
What about use creport instead of clear logs?
Just combed through them again and you're mostly right; majority of the homebrew only bans were due to connecting online with homebrew (with the exception of 2 with one of them for clearing error logs). Doesn't mean what you're doing is 100% safe but 99% safe is pretty good too I guess.
A clean NAND would wipe out evidence of everything from homebrew to CFW to .NSP.
Creport has replaced nx-dreport. Nx-dreport was deemed so dangerous that it was depreciated by the original author.
Creport is a sysmodule reimplemented by Atmosphere that you can download from RajNX, Kosmos, or the official Atmosphere releases.It looks like they possibly docked Switch by accident with airplane mode enabled and what's tricky move from Nintendo.
Where I find to enable creport? Is it accessible on Hekate?
Creport is a sysmodule reimplemented by Atmosphere that you can download from RajNX, Kosmos, or the official Atmosphere releases.
Yes, dreport wasn't built into Hekate; it had to be compiled separately and then manually added.Just like nx-dreport did?
Yes, dreport wasn't built into Hekate; it had to be compiled separately and then manually added.
If "changing the colour of your Joy-Cons" means swapping the plastic case out or painting it. Then there's no ban risk for that. Nintendo doesn't care about that kinda thing. They would probably think it's cool.This may sound really dumb but can you get banned for changing the colour of your Joy-Cons? I’ve done this but have not used them since I’ve updated.
Creport is basically the ...36 folder. And to go back to OFW, you have to restart the console.Ok, I have a question.
Can I delete stuffs in creport folder 0100000000000036?
How I can go back to stock firmware OFW after use with CFW? Power Switch off?
How are you getting that impression? I certainly hope not as I just did that with one of my stock 6.1 Switches. Just running Hekate to dump stuff shouldn’t cause a problem becuase no CFW is run. Though I didn’t get the BIS keys as I beleive CFW has to run for those.Seems like just about nothing is safe then? I currently have a stock 6.1 Switch, and was planning on using fusee gelee to just simply dump a backup of my keys/nand/fuses before updating it to 6.2 without actually installing any CFW or homebrew or emunand or anything, I figured at least that might be safe but it seems as if not even that is the case?
The Switch can log if it was booted via RCM but from what I am told, Hekate resets this flag so the console doesn't know any better. Don't know if the same logic can be applied to SX OS but I'm assuming the other open-source bootloaders (namely ReiNX and Fusee for Atmosphere) do the same reset as Hekate.RCM mode does not in any way log anything? I was directed to this topic when someone mentioned to me that it's possible the Switch has some sort of RCM count or something.
Obviously I know that but there’s the software that changes the joy-con colour code on the chipIf "changing the colour of your Joy-Cons" means swapping the plastic case out or painting it. Then there's no ban risk for that. Nintendo doesn't care about that kinda thing. They would probably think it's cool.
The Switch can log if it was booted via RCM but from what I am told, Hekate resets this flag so the console doesn't know any better. Don't know if the same logic can be applied to SX OS but I'm assuming the other open-source bootloaders (namely ReiNX and Fusee for Atmosphere) do the same reset as Hekate.
Hekate is not a CFW, it is a bootloader aka the tool used to run CFW like Atmosphere, ReiNX, or SX OS.I see, I was looking up what that Hekate thing is, and it appears to be a CFW? I was trying to avoid installing anything on my Switch. Are all these warnings about 6.2 something I need to worry about if I am not planning to hack my Switch yet for another year or so? I thought that since my Switch is vulnerable to Fusee I could wait until I was ready to do so and had more or less played the games I wanted so I wouldn't have to worry about screwing it up, but now I heard that apparently I would lose some keys permanently if I don't back then up before updating to 6.2? Are those keys just for downgrading to 6.1 or do they have some other importance that would still matter a year or so from now if I wanted to hack my Switch that's on whatever the latest firmware would be by then?
Yup. Pretty much confirms bans are random. Some people do everything possible and don't get banned while others do the minimum but are not so lucky. Also I find it weird you checked "Yes" to using non-SX OS LayeredFS online but indicated no to using it offline (using it online means you used it offline by default).I've hacked my Switch around... I'd say from May to August. I then stopped because I was scared of getting banned. What's weird is that, many MANY people that have used CFW and then stopped got banned. I guess either I'm lucky or... I honestly don't know lol