Hacking Question Why is the sleep mode broken on my switch?

[darrenhuang22]

Let's say I am stupid and for some reason upgrade to 6.2.0 (My switch was 6.1.0), so I restored the NAND and BOOT 0/1, everything cool, boot through RCM and get into CFW, and sleep mode seems broken, when I hit sleep and try to bring switch back, power button does not wake it up. And it seems I can not boot into OFW, any idea why this happens?

When I try to wake it up, the screen is just black, I have to hold the power button for a long time and boot through CFW. Well, this sucks cause I can not put switch back to sleep? Any idea how to fix this?

 

[brickmii82]

The update burned a efuse in the processor. When sleep mode wakes up, the unit does a fuse check and expects to see a certain number burned. If the amount differs from what’s expected, it locks up. I think it’s 8 fuses burned so far if your on 6.2, so 6.1 wants to see 7 fuses burned. Since it’s incorrect, the console locks. The reason it doesn’t do it at booting CFW is that the fuse checks are bypassed in the bootloaders. Idk why sleep mode fuse checks can’t be bypassed so maybe someone can chime in.

 

[Kubas_inko]

The update burned a efuse in the processor. When sleep mode wakes up, the unit does a fuse check and expects to see a certain number burned. If the amount differs from what’s expected, it locks up. I think it’s 8 fuses burned so far if your on 6.2, so 6.1 wants to see 7 fuses burned. Since it’s incorrect, the console locks. The reason it doesn’t do it at booting CFW is that the fuse checks are bypassed in the bootloaders. Idk why sleep mode fuse checks can’t be bypassed so maybe someone can chime in.

Why does it boot with less fuses then? Hmm?

Just kidding. Warmboot checks for fuses on boot and on wake up. If the number of fuses is lower, it will continue to boot/ wake up (and will burn fuses on boot obviously). If the number is higher, it straight up refuses to boot, so it refuses to wake up from sleep too.

 

[brickmii82]

Why does it boot with less fuses then? Hmm?

Just kidding. Warmboot checks for fuses on boot and on wake up. If the number of fuses is lower, it will continue to boot/ wake up (and will burn fuses on boot obviously). If the number is higher, it straight up refuses to boot, so it refuses to wake up from sleep too.

I see. Thanks for the full clarification.

 

[Kubas_inko]

I see. Thanks for the full clarification.

Thats just my "educated" guess. But it makes sense.

 

[Roster]

do we have a solution as to how to fix this issue when the switch is stuck in sleep mode? Thanks.

 

[Albytrozz]

do we have a solution as to how to fix this issue when the switch is stuck in sleep mode? Thanks.

Yup, either downgrade it back to 6.1 with ChoiDuJourNX (which will ignore fuse count with AutoRCM) or officially upgrade it back to 6.2 (or whatever version your burnt fuses allow).

That said with Choi there's no reason anyone should be using a lower FW. My console fuses are still at 5.1 but I'm running the latest OS just fine and every title actually boots. Makes no sense staying on a lower firmware and dealing with all the patched NSPs and non-booting titles BS that goes with it.

 

[Roster]

Yup, either downgrade it back to 6.1 with ChoiDuJourNX (which will ignore fuse count with AutoRCM) or officially upgrade it back to 6.2 (or whatever version your burnt fuses allow).

That said with Choi there's no reason anyone should be using a lower FW. My console fuses are still at 5.1 but I'm running the latest OS just fine and every title actually boots. Makes no sense staying on a lower firmware and dealing with all the patched NSPs and non-booting titles BS that goes with it.

Thanks Albytrozz. Sorry for the noob question but how do I launch ChoiDujourNX as my switch stays blank upon trying to boot. It boots into Hekate so im assuming there is a way to launch ChoiDujourNX? Please explain the steps. Thank you.