Hacking Issue with Sleep mode & device boot

[lolapaloooza]

Hi!

I am facing biiiiig issues with my switch

Issue 1 -> Sleep mode:
So.. i use the jig & i plugin the palyload injector (NS-Atmosphere wiht Hekate 4.5)
After loading CFW or the stock FW from the Hekate menu if i put it in sleep mode (by pressing once the power button).. it doesn't get back to normal by any means..
(the only solution i found in this one was to keep pressing the power button for 15 seconds and then reinject the payloads)

Issue 2 -> Device coot:
Then i thought "why not restore the nand" and start from scratch. I did so.. it was a successful procedure but the "sleep mode" issue was still there. (regardless the FW i was running)

BUT there is the boot issue, when i plug in NS-Atmosphere, i go to RCM mode and chose the "shut down"
Next i remove the sd card, i remove the jig and replace it with the right joycon and press the power button.
You should expect that the device would turn on as before it was "hacked) but the device does not turn on by any means.
The only way to turn it on is via the NS-Atmosphere. (that happened before and after i restored the nand)

Can you help me out with any of these ones? especially the last one!!!

 

[Scitzo]

You updated and blew too many fuses. Now your sleep mode is broken until you go back to the highest fw, and you wont be able to boot normal fw without using rcm.

Do people even read anymore?

 

[lolapaloooza]

You updated and blew too many fuses. Now your sleep mode is broken until you go back to the highest fw, and you wont be able to boot normal fw without using rcm.

Do people even read anymore?

Thank you for the reply!!

So.. my next question is.. how can i check the number of fuses i accidentally blew? What is the correct number of fusses?
And.. if i update it again to 6.2.0 will the sleep mode work again as before? (if i remember correct i was facing the same issues with sleep mode in 6.2.0 as well)
Shall i update it if via internet or via ChoiDujoir?

And yes i read a lot.. but this one was an accident

 

[mrcroket]

If you have the lastest atmosphere, you can activate autorcm from hekate and then update the system via internet from atmosphere, lastest atmosphere prevents that the system update from disabling autorcm when the console its updated via internet.

I recommend you always use autorcm to prevent burnt fuses.

 

[Scitzo]

Thank you for the reply!!

So.. my next question is.. how can i check the number of fuses i accidentally blew? What is the correct number of fusses?
And.. if i update it again to 6.2.0 will the sleep mode work again as before? (if i remember correct i was facing the same issues with sleep mode in 6.2.0 as well)
Shall i update it if via internet or via ChoiDujoir?

And yes i read a lot.. but this one was an accident

You can check your fuses by booting hekate v4.5 and checking your fuse info.

I dont know the correct number of fuses for 6.2, im currently on 5.1 system ofw (clean nand restore) and 5.1 emunand microsd cfw.

If youve ever been online in cfw, chances are youre already banned or will be banned eventually, so the choice to use online or choi is up to you.

Long story short, once you blow fuses that correspond to a certain fw version, for instance the fuses for 6.2, then your system wont boot another fw version like 5.1 because the fuses dont match. The workaround for that is to boot via RCM, which avoids the fuse check and allows the system to boot. HOWEVER, even if you boot via this way, the system will still crash on sleep because there is another fuse check at sleep awake. So youd need to reinject a payload and boot again to wake from sleep if youre fw version doesnt match the correct fuse account.

This can be avoided by using the correct fw that corresponds to your fuses, or you can live with the inconvenience of workarounds.

 

[lolapaloooza]

If you have the lastest atmosphere, you can activate autorcm from hekate and then update the system via internet from atmosphere, lastest atmosphere prevents that the system update from disabling autorcm when the console its updated via internet.

I recommend you always use autorcm to prevent burnt fuses.

You can check your fuses by booting hekate v4.5 and checking your fuse info.

I dont know the correct number of fuses for 6.2, im currently on 5.1 system ofw (clean nand restore) and 5.1 emunand microsd cfw.

If youve ever been online in cfw, chances are youre already banned or will be banned eventually, so the choice to use online or choi is up to you.

Long story short, once you blow fuses that correspond to a certain fw version, for instance the fuses for 6.2, then your system wont boot another fw version like 5.1 because the fuses dont match. The workaround for that is to boot via RCM, which avoids the fuse check and allows the system to boot. HOWEVER, even if you boot via this way, the system will still crash on sleep because there is another fuse check at sleep awake. So youd need to reinject a payload and boot again to wake from sleep if youre fw version doesnt match the correct fuse account.

This can be avoided by using the correct fw that corresponds to your fuses, or you can live with the inconvenience of workarounds.

A big Thanks to both of you!! a combination of the suggestions you made and case closed..
- i restored the Nand i backed up some time ago (5.1.0)
- run hekate 4.5 and used CFW with atmosphere 0.8.1 (while in 5.1.0)
- updated again via internet to 6.2.0
- and i am just booting every time to CFW with atmosphere 0.8.1 (since the reason for all this mess with upgrading and downgrading was a result of the incompatibility of ReinX )
- everything works great as before, both sleep mode and stock FW (as it was with ReinX)


faith in humanity and switch and CFW restored

Thanx again!!

 

[Kafluke]

The part people dont ever read is that you cant just simply restore an older firmware with a nand backup.

You have to take measures ahead of time and update through the process with choi leaving autorcm on so you dont blow fuses. Then downgrading is simple but if you didnt follow those steps when you upgraded then simply restoring an older nand will require you to always boot into a hacked bootlaoder or nothing is going to work.