Hi All,
Before I begin, I just want to say this isn't another "I-uPdAtEd-mY-SwItCh-aNd-NoW-iT-DoEsNt-WeRk...WhAt-Do?" thread. I own 3 V1 Switches all running Atmosphere, and until today none have had any issues whatsoever. I know what sigpatches are, and the difference between EmuNAND and SysNAND etc. Hopefully this makes me sound like less of a noob!
One of my V1 switches is used by my son, who DID accidentally update it to FW17 and stopped working how he wanted it to (to be expected). This was before Atmosphere was updated 1.6.2, and sigpatches weren't available at the time. I managed to successfully downgrade the Firmware to 16.1.0 with Daybreak, and everything started to work again. Problem solved, or so I thought...
I updated everything again, properly, when I knew it was safe to do so. This includes Atmosphere 1.6.2 and Hekate 6.0.7. According to my son, he was "playing a game and all of a sudden the screen went black". Weird, I thought, I'll just boot back into Atmosphere and that should solve the problem. Except it didnt. The console is now completely unresponsive, and wont even boot into OFW from cold boot. Auto RCM is disabled, and even my PC cant detect it.
My only thought is that some time ago, Hekate informed me that the eMMC module was running slowly and was unable to boot. This warning went away and hasn't appeared in months. I have a spare eMMC module for the Switch as well as backups of my sons eMMC BOOT0 & BOOT1 and eMMC RAW GPP in case this caused a problem again after the warning went away.
I'm now out of ideas short of opening it up. This is where my expertise sadly ends. Anything in particular to look for inside? Are we now screwed? or is only option is to get a new console?
Before I begin, I just want to say this isn't another "I-uPdAtEd-mY-SwItCh-aNd-NoW-iT-DoEsNt-WeRk...WhAt-Do?" thread. I own 3 V1 Switches all running Atmosphere, and until today none have had any issues whatsoever. I know what sigpatches are, and the difference between EmuNAND and SysNAND etc. Hopefully this makes me sound like less of a noob!
One of my V1 switches is used by my son, who DID accidentally update it to FW17 and stopped working how he wanted it to (to be expected). This was before Atmosphere was updated 1.6.2, and sigpatches weren't available at the time. I managed to successfully downgrade the Firmware to 16.1.0 with Daybreak, and everything started to work again. Problem solved, or so I thought...
I updated everything again, properly, when I knew it was safe to do so. This includes Atmosphere 1.6.2 and Hekate 6.0.7. According to my son, he was "playing a game and all of a sudden the screen went black". Weird, I thought, I'll just boot back into Atmosphere and that should solve the problem. Except it didnt. The console is now completely unresponsive, and wont even boot into OFW from cold boot. Auto RCM is disabled, and even my PC cant detect it.
My only thought is that some time ago, Hekate informed me that the eMMC module was running slowly and was unable to boot. This warning went away and hasn't appeared in months. I have a spare eMMC module for the Switch as well as backups of my sons eMMC BOOT0 & BOOT1 and eMMC RAW GPP in case this caused a problem again after the warning went away.
I'm now out of ideas short of opening it up. This is where my expertise sadly ends. Anything in particular to look for inside? Are we now screwed? or is only option is to get a new console?