Hacking Question Restoring NAND backup (Will I be banned?)

[IdahoNate153]

Creating a NAND backup before running and homebrew, exploits, or backups and staying offline is the best way to not risk being banned, correct? Well at a later date say I do want to take my Switch online. Can I just restore my NAND backup and be safe to go online?

My Switch's firmware is 4.1 if that's of any use.

 

[Mr. Wizard]

Technically, you have to exploit the switch to get your backup so even your backup could have traces of you violating their terms of service.

 

[mr_switch]

I believe this is the best method to prevent a ban while still hacking your switch. I personally backup my boot0, boot1 & raw nand before installing SX pro. Currently only playing all backups offline and waiting for a more comprehensive way to prevent a ban. Planning to backup all my saves with checkpoint and restore them once emunand and other ban prevention tools are made available.

 

[benson733]

That is probably the best chance of not being banned imo.

 

[Ian095]

I restored my NAND before updating my Firmware, not banned yet... So yes, if you want to go online, restore your NAND.

 

[SnAQ]

Hopefully you'll get banned.
If you don't want to risk it, don't hack it.

And by the way, learn to search.

Sent from my Samsung Galaxy S9 via Tapatalk

 

[IdahoNate153]

Hopefully you'll get banned.
If you don't want to risk it, don't hack it.

And by the way, learn to search.

Sent from my Samsung Galaxy S9 via Tapatalk

I clearly did search which is why I asked to confirm the information I found. Not my first time using the forums.

Could I have this thread closed as I have found my answer? Thanks.

 

[Tasemu]

Just make sure you don't update your firmware without the non-fuse-burning method. otherwise you will restore your nand to the old FW and the fuse will be already burned and it wont boot (i think it wont boot).

 

[Mr. Wizard]

Just make sure you don't update your firmware without the non-fuse-burning method. otherwise you will restore your nand to the old FW and the fuse will be already burned and it wont boot (i think it wont boot).

I thought the fuse checks are no longer an issue with Hekate and SXOS.

 

[Tasemu]

I thought the fuse checks are no longer an issue with Hekate and SXOS.

Do you mean, updating while booted into SXOS? I'm not sure how I would accomplish that in airplane mode.

 

[Mr. Wizard]

Do you mean, updating while booted into SXOS? I'm not sure how I would accomplish that in airplane mode.

From a cartridge but that has nothing to do with what I meant.

What I meant was, I thought that using a hekate or sxos payload from rcm would bypass any fuse checks so you can run any firmware? That was my understanding as I am currently on 5.1.0 with 3 fuses blown when should be 6.

So does that mean I can't downgrade to lets say 2.0 and use a payload to bypass the fuse check? I can only downgrade back to 3.0.0? And if I have all fuses blown I can't downgrade at all?

 

[Tasemu]

From a cartridge but that has nothing to do with what I meant.

What I meant was, I thought that using a hekate or sxos payload from rcm would bypass any fuse checks so you can run any firmware? That was my understanding as I am currently on 5.1.0 with 3 fuses blown when should be 6.

So does that mean I can't downgrade to lets say 2.0 and use a payload to bypass the fuse check? I can only downgrade back to 3.0.0? And if I have all fuses blown I can't downgrade at all?

Ah, i'm not actually sure sorry.

The scenario I was thinking of was the following:

- User is on 5.1 clean OFW
- User creates NAND backup of clean OFW
- User installs *insert CFW here*
- 5.2 FW is released
- User updates FW (unsure how, assuming here that a fuse would be burned?)
- User one day decides he wants to play online and restores the NAND backup
- Switch is now back on 5.1 but the fuse is burned
- Switch wont boot? (not sure on what happens here)

 

[Mr. Wizard]

Ah, i'm not actually sure sorry.

The scenario I was thinking of was the following:

- User is on 5.1 clean OFW
- User creates NAND backup of clean OFW
- User installs *insert CFW here*
- 5.2 FW is released
- User updates FW (unsure how, assuming here that a fuse would be burned?)
- User one day decides he wants to play online and restores the NAND backup
- Switch is now back on 5.1 but the fuse is burned
- Switch wont boot? (not sure on what happens here)

Well there is a tutorial for updating without burning fuses.
And if you can still boot into RCM I don't see the problem, you can change to whatever firmware you want from rcm.

 

[Tasemu]

Well there is a tutorial for updating without burning fuses.
And if you can still boot into RCM I don't see the problem, you can change to whatever firmware you want from rcm.

Fair enough, it was just a warning not to update without the guide. If the user ever wants to quit CFW and RCM and just go back to his clean switch, he could be screwed if he doesn't follow the (quite complicated) process of updating without burning fuses.

 

[Mr. Wizard]

Fair enough, it was just a warning not to update without the guide. If the user ever wants to quit CFW and RCM and just go back to his clean switch, he could be screwed if he doesn't follow the (quite complicated) process of updating without burning fuses.

It wasn't complicated, just have to read through it. And once you understand what you are doing (mounting USB disk partitions and copying data to them) it's really pretty straight forward.

I had more trouble getting the damn keys!

 

[Tasemu]

Fair enough, still worth the warning to OP in my opinion.