So basically I had my v1 switch since launch and modded it as soon as I found out and read that it was mostly safe to do with the right steps. Since you can't go online with a modded switch anyway I blocked Nintendo servers and just never tried to go online anymore anyway until I found out about emunand later on in the game. I remember not fully understanding about burning efuses but I've always just followed guides and was able to do system updates as soon as the latest atmosphere dropped. I would hack my games but only for single player purposes never for anything related to online. Near the end, I got brave enough to mod the system with a teensy board, which allows me to boot without a a joycon jig or external payload injector device.
Eventually, I moved on to steam deck and back to my pc. I was planning to sell the modded switch so i erased the sysnand and used something in hekate I think to basically nuke sysnand and start over from scratch. I eventually just never got around to selling the switch until I recently turned the system on again. I'm able to link my Nintendo account on sysnand that I'm pretty sure is clean. The system boots up normal, and I have emunand set up on SD card. I updated Sysnand to 22.1.0 normally and emunand to the same version using daybreak.
So far it's been about 24 hours and the modded switch is still able to connect to eShop and other Nintendo services, while I'm able to jump from sysnand to emunand. The system boots up fine, so here are my questions since it's been so long:
* Did I somehow manage to not burn all my efuses after all this time since the sysnand still boots normally and connects to Nintendo?
* Is the teensyboard mod chip detectable and still bannable even if the sysnand is clean?
* Is it safe to run sysnand with emunand and cfw content on the SD card only for emunand purposes?
* The whole reason for reviving my old modded switch is we recently bought a switch 2 and trying to transfer old saves to it. From what I've read, if my sysnand is clean I just disable wifi and reboot sysnand into cfw using hekate to launch jksv in applet mode and nothing else, transfer save data, then power off and eject SD card before booting into ofw again to transfer save data. All of this should be safe, right?
Eventually, I moved on to steam deck and back to my pc. I was planning to sell the modded switch so i erased the sysnand and used something in hekate I think to basically nuke sysnand and start over from scratch. I eventually just never got around to selling the switch until I recently turned the system on again. I'm able to link my Nintendo account on sysnand that I'm pretty sure is clean. The system boots up normal, and I have emunand set up on SD card. I updated Sysnand to 22.1.0 normally and emunand to the same version using daybreak.
So far it's been about 24 hours and the modded switch is still able to connect to eShop and other Nintendo services, while I'm able to jump from sysnand to emunand. The system boots up fine, so here are my questions since it's been so long:
* Did I somehow manage to not burn all my efuses after all this time since the sysnand still boots normally and connects to Nintendo?
* Is the teensyboard mod chip detectable and still bannable even if the sysnand is clean?
* Is it safe to run sysnand with emunand and cfw content on the SD card only for emunand purposes?
* The whole reason for reviving my old modded switch is we recently bought a switch 2 and trying to transfer old saves to it. From what I've read, if my sysnand is clean I just disable wifi and reboot sysnand into cfw using hekate to launch jksv in applet mode and nothing else, transfer save data, then power off and eject SD card before booting into ofw again to transfer save data. All of this should be safe, right?
