Hacking Sleep mode crash after downgrade from 6.1 OFW to 5.1 CFW with NAND backup?

pingtendo

Member
OP
Newcomer
Joined
Sep 20, 2016
Messages
17
Trophies
0
Age
37
XP
173
Country
United States
It's for my friend, who doesn't speak English very well...

He was on 5.1 (fuse count = 6) but accidentally updated to 6.1 (fuse count = 7) couple days ago.

He has 5.1 NAND backup, and uses ChoiDujour to downgrade to 5.1 cfw already. However after the downgrade, his console will crash as soon as entering into sleep mode, and he needs to inject the payload to be able to boot again.

Is there any way to fix the sleep mode crash issue on at all? (I know 6.2 to 6.1 seems impossible at the moment, but how about 6.1 to 5.1)

Thank you for your help!
 

Shift-X

Well-Known Member
Newcomer
Joined
Nov 16, 2018
Messages
70
Trophies
0
XP
141
Country
United States
It's for my friend, who doesn't speak English very well...

He was on 5.1 (fuse count = 6) but accidentally updated to 6.1 (fuse count = 7) couple days ago.

He has 5.1 NAND backup, and uses ChoiDujour to downgrade to 5.1 cfw already. However after the downgrade, his console will crash as soon as entering into sleep mode, and he needs to inject the payload to be able to boot again.

Is there any way to fix the sleep mode crash issue on at all? (I know 6.2 to 6.1 seems impossible at the moment, but how about 6.1 to 5.1)

Thank you for your help!
You're safe on 6.1. Do a NAND backup and delete Wi-Fi settings so you don't make the same mistake again. I personally use 90DNS so I can go online without connection to Nintendo Servers (USE AT YOUR OWN RISK... Nintendo is unpredictable). Do not update to 6.2
 

jsherm101

Member
Newcomer
Joined
Sep 25, 2012
Messages
14
Trophies
0
XP
196
Country
United States
to add more context - when you update via normal nintendo update (aka without using choidujour) you will burn fuses for whatever number of fuses that version has (some updates, like 6.0.0 to 6.0.1 have the same fuse count)

When you use Choidujour you're forcing autoRCM after the update which prevents the fuses from being checked/burned for that version. That's what allows you to upgrade/downgrade without the sleep crash because your fuse count still thinks you're on the previous version -- since you've burned those fuses your switch now thinks it's on 6.1.0 -

in the future always update using choidujour to prevent this, but keep in mind you'll have to live with autorcm

the sleep/warm boot crash is because the fuses check themselves at that point, notice a mismatch, and shut down your device, so you can "downgrade" but your switch will always crash once it does a fuse check so you can't let it sleep
 

guaycuru

Member
Newcomer
Joined
Apr 29, 2018
Messages
5
Trophies
0
Age
36
XP
313
Country
Brazil
the sleep/warm boot crash is because the fuses check themselves at that point, notice a mismatch, and shut down your device, so you can "downgrade" but your switch will always crash once it does a fuse check so you can't let it sleep

I'm sorry if this has been answered before, but does it mean that a downgrade with AutoRCM enabled AND booted via Hekate (obviously) also crashes when going into sleep mode? Or does Hekate's fuse checking / burning prevention prevent that sleep crash?
 

tikanot

Member
Newcomer
Joined
Nov 22, 2018
Messages
8
Trophies
0
Age
41
XP
64
Country
France
6.2 resolve sleep mode? because it s hard for my children to use it. for cancel update i have format my sd card and switch To delete all and now no wifi
 

jsherm101

Member
Newcomer
Joined
Sep 25, 2012
Messages
14
Trophies
0
XP
196
Country
United States
I'm sorry if this has been answered before, but does it mean that a downgrade with AutoRCM enabled AND booted via Hekate (obviously) also crashes when going into sleep mode? Or does Hekate's fuse checking / burning prevention prevent that sleep crash?

I don't believe so. Choidujour is skipping the step where fuses get burned when it installs an update and keeps AutoRCM on in order to preserve this later, so if you install via official Nintendo update, you've burned the fuse and will have the downgrade issues previously described

6.2 resolve sleep mode? because it s hard for my children to use it. for cancel update i have format my sd card and switch To delete all and now no wifi
do not update to 6.2 at this time
 

tikanot

Member
Newcomer
Joined
Nov 22, 2018
Messages
8
Trophies
0
Age
41
XP
64
Country
France
the switch is very hard to use for kid.I have say at my son to ask me when he see something but he have 4years
 

BlackTSQ

Well-Known Member
Newcomer
Joined
Oct 9, 2018
Messages
97
Trophies
0
Age
28
XP
551
Country
Austria
the switch is very hard to use for kid.I have say at my son to ask me when he see something but he have 4years

Thats a long sentence for a child...

Jk

So if i understand it correctly, you accidentally updated to 6.1, and then you downgraded to 5.1 with choidujourNX and now sleepmode isn't working anymore. If thats the case you can just update to 6.1 with choidujourNX again and it should work fine.

However, if you have been on 6.2 allready you are pretty much out of options. Until a custom firmware for 6.2 comes out you can either use it the way you are using it right now (with broken sleep mode), or use it on original firmware 6.2 and lose the benefits of custom firmware.
 
  • Like
Reactions: Rushhour77

tikanot

Member
Newcomer
Joined
Nov 22, 2018
Messages
8
Trophies
0
Age
41
XP
64
Country
France
child update To 6.2 i downgrade To 6.1 but lot of bug not only sleep mode hard To go in rcm and in boot switch power off and after computer reconized it at usb no descriptor.i must wait long time To computer reconized good. i have put autorcm in order no more fuse burn
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    K3Nv2 @ K3Nv2: https://www.ebay.com/itm/386617469929?mkcid=16&mkevt=1&mkrid=711-127632-2357-0&ssspo=2T8UwYf_Qse&...