Hacking Question Playing Online after restoring old nand

[pablo67340]

Hey there, recently I saw a few threads on users using EMUNAND to separate their SYSNAND (CLEAN) from their CFW EMUNAND. I'd like to try this, as I have some official gamecards and e-store purchases I'd like to use. My Switch has been using 90DNS since before it was modded, and I can be certain it is not banned. Currently my switch is running Atmosphere 11.0.1 with 14 burned fuses. My NAND Backup I have is 8.0.1 (FULL). I am not 100% on the steps, but here's what I've gathered from researching, and wanted to be crystal clear before starting this.

1. Backup my current 11.0.1 CFW (Just in case)
2. Create EMUNAND on my current 11.0.1 CFW using Hekate on another partition (So it stays intact)
3. Restore my old NAND/BOOT to my 8.0.1 CLEAN Backup
4. Boot into OFW using Hekate (bypassing fuse checks)
5. Update OFW to 11.0.1 using official Ninty Servers
6. Backup CLEAN OFW on 11.0.1 (Just in case again)

At this point, I have a ton of questions.

1. Now that my switch will have 15 burnt fuses on 11.0.1, will I be required to use Hekate to launch OFW every time?
2. Can I enable Auto-RCM after this? This would only be used for quick booting into CFW. Never to boot into OFW. If I plan on booting into OFW, I'd be disabling Auto-RCM.
3. Will I be able to play online using my Sysnand using my officially purchased games now?
4. In your professional opinion, do you think my ban risk would be high? (Obviously I know there's always a risk )

Please let me know! I'd love to be clear on this before making the attempt or possibly just wasting a crap ton of time. Your input is much appreciated <3

 

[Lacius]

1. If you update to 11.0.1 on your sysMMC, you don't have to worry about using Hekate to boot OFW on your sysMMC. There won't be a fuse mismatch if you update, so you will be able to boot OFW on your sysMMC normally.

2. Yes, you can install AutoRCM at any time, but this will require you to use Hekate again to launch OFW on your sysMMC. Or, as you strangely described, you can disable AutoRCM each time you want to enter OFW on your sysMMC.

3. If the Switch isn't already banned, you should be able to play online using OFW on your clean sysMMC if you pay for Switch Online.

4. Assuming you haven't connected your Switch to the internet without 90DNS or Incognito since you made your clean sysMMC backup, I would say your ban risk is very low. I recommend installing Incognito to the emuMMC, so you don't accidentally get your Switch banned.

 

[pablo67340]

1. If you update to 11.0.1 on your sysMMC, you don't have to worry about using Hekate to boot OFW on your sysMMC. There won't be a fuse mismatch if you update, so you will be able to boot OFW on your sysMMC normally.

2. Yes, you can install AutoRCM at any time, but this will require you to use Hekate again to launch OFW on your sysMMC. Or, as you strangely described, you can disable AutoRCM each time you want to enter OFW on your sysMMC.

3. If the Switch isn't already banned, you should be able to play online using OFW on your clean sysMMC if you pay for Switch Online.

4. Assuming you haven't connected your Switch to the internet without 90DNS or Incognito since you made your clean sysMMC backup, I would say your ban risk is very low. I recommend installing Incognito to the emuMMC, so you don't accidentally get your Switch banned.

Thank you so much for your input, just to be 1000% clear, 14 burned fuses appears to be the correct amount for 11.0.1. When I update again in the 8.0.1 OFW, this should set my fuses to 15. Are you sure that the bootloader will still work? Feels weird as I'll be +1 fuses higher than everyone else on that version.

 

[Lacius]

Thank you so much for your input, just to be 1000% clear, 14 burned fuses appears to be the correct amount for 11.0.1. When I update again in the 8.0.1 OFW, this should set my fuses to 15. Are you sure that the bootloader will still work? Feels weird as I'll be +1 fuses higher than everyone else on that version.

If you update your sysMMC to 11.0.1, you will have 14 burnt fuses, and that will be your fuse count. You can update to 11.0.1 a hundred times, and 14 will still be the fuse count. You will not have a fuse count of 15 unless Nintendo releases a system update in the future that is designed to burn 15 fuses. 11.0.0 and 11.0.1 only burn 14 fuses.

A system will always boot normally if the system version matches the expected fuse count (or the fuse count is lower, which it will immediately change to the expected fuse count).

 

[pablo67340]

If you update your sysMMC to 11.0.1, you will have 14 burnt fuses, and that will be your fuse count. You can update to 11.0.1 a hundred times, and 14 will still be the fuse count. You will not have a fuse count of 15 unless Nintendo releases a system update in the future that is designed to burn 15 fuses. 11.0.0 and 11.0.1 only burn 14 fuses.

A system will always boot normally if the system version matches the expected fuse count (or the fuse count is lower, which it will immediately change to the expected fuse count).

So I completed the steps and re-wrote my 8.0.1 nand/boot to sysnand. Now, for some reason, I can boot into Hekate and select my Emunand and boot no problem. But when I choose my Stock sysnand, I see the nintendo logo, then a black screen. What could be the cause?

 

[Draxzelex]

So I completed the steps and re-wrote my 8.0.1 nand/boot to sysnand. Now, for some reason, I can boot into Hekate and select my Emunand and boot no problem. But when I choose my Stock sysnand, I see the nintendo logo, then a black screen. What could be the cause?

Because booting into emuMMC involves a custom bootloader that bypasses the fuse check. Booting into a firmware lower than your fuse count without a custom bootloader will simply not work.