Hacking Hekate 4.5 problem

[gianm93]

Hi. I updated my switch to 6.2.0. I can boot without problems with fusee primary but if I try to use hekate 4.5 I have to inject the payload twice. What did I wrong?

 

[Draxzelex]

That is the Auto HOS Power Off feature you are experiencing. When a console with AutoRCM enabled enters RCM from Horizon, such as when turning the console off or rebooting it, sending the Hekate payload with this feature causes the console to shut down (and you will see the Hekate logo as well). More explanation and instructions can be found on the Hekate GitHub page.

 

[Frank1905]

That is the Auto HOS Power Off feature you are experiencing. When a console with AutoRCM enabled enters RCM from Horizon, such as when turning the console off or rebooting it, sending the Hekate payload with this feature causes the console to shut down (and you will see the Hekate logo as well). More explanation and instructions can be found on the Hekate GitHub page.

This features seems a little buggy if used with autoboot. Am I wrong? I set Auto HOS Power Off as enabled and Autoboot of Atmosphere enabled with 0s boot delay.
When I turn off the console from Atmosphere it correctly goes in RCM, but when I inject Hekate payload again, it just launches Atmosphere again.

Inviato dal mio Nexus 5X utilizzando Tapatalk

 

[Draxzelex]

This features seems a little buggy if used with autoboot. Am I wrong? I set Auto HOS Power Off as enabled and Autoboot of Atmosphere enabled with 0s boot delay.
When I turn off the console from Atmosphere it correctly goes in RCM, but when I inject Hekate payload again, it just launches Atmosphere again.

Inviato dal mio Nexus 5X utilizzando Tapatalk

That's expected. Shutting down the console from Horizon with AutoRCM enabled causes it to reboot into RCM and with Autoboot, the console will automatically boot the CFW when the payload is sent.

 

[Frank1905]

That's expected. Shutting down the console from Horizon with AutoRCM enabled causes it to reboot into RCM and with Autoboot, the console will automatically boot the CFW when the payload is sent.

So the two features can't be used together in any way? I'm sad [emoji3525]

Inviato dal mio Nexus 5X utilizzando Tapatalk

 

[Draxzelex]

So the two features can't be used together in any way? I'm sad [emoji3525]

Inviato dal mio Nexus 5X utilizzando Tapatalk

I believe Hekate will default to Auto HOS Power Off before Autoboot since Auto HOS Power Off is designed to turn off the console when you enter RCM from Horizon not a powered off state. Autoboot doesn't care how you entered RCM, just that the Switch is currently in RCM and a payload was pushed.

 

[Frank1905]

Gotcha. Thank you!

I believe Hekate will default to Auto HOS Power Off before Autoboot since Auto HOS Power Off is designed to turn off the console when you enter RCM from Horizon not a powered off state. Autoboot doesn't care how you entered RCM, just that the Switch is currently in RCM and a payload was pushed.

Inviato dal mio Nexus 5X utilizzando Tapatalk

 

[gianm93]

I believe Hekate will default to Auto HOS Power Off before Autoboot since Auto HOS Power Off is designed to turn off the console when you enter RCM from Horizon not a powered off state. Autoboot doesn't care how you entered RCM, just that the Switch is currently in RCM and a payload was pushed.

Can I disable auto HOS? What it does?

 

[gianm93]

I changed autohosoff from 1 to 0 and it worked. But I want to know what I changed

 

[Frank1905]

Can I disable auto HOS? What it does?

Auto HOS off is useful for people who have Auto RCM enabled. In fact, when you turn off your console from Horizon (Ninendo Switch OS) using the power off menu, the console automatically reboots to RCM. So, thanks to Auto HOS off, if you re-inject Hekate's payload, it will truly turn your console off.

Inviato dal mio Nexus 5X utilizzando Tapatalk

 

[gianm93]

Auto HOS off is useful for people who have Auto RCM enabled. In fact, when you turn off your console from Horizon (Ninendo Switch OS) using the power off menu, the console automatically reboots to RCM. So, thanks to Auto HOS off, if you re-inject Hekate's payload, it will truly turn your console off.

Inviato dal mio Nexus 5X utilizzando Tapatalk

You are telling that I had to inject payload twice because the first time (after i turned off my switch) hekate turned my switch off for real?

 

[Frank1905]

Ok let's assume it's the first time you launch Hekate and you activate Auto HOS off and Auto RCM.
In Hekate you boot your CFW, let's say Atmosphere. When you are done playing and you want to turn off your console (not RCM) using the power off menu is not enough, in fact your console will automatically reboot to RCM.
But thanks to Auto HOS off, if you inject Hekate NOW it will turn off your console. Then, if you want to turn it on again, you will have to press the power button and thanks to Auto RCM the console will boot in RCM, so you can inject the Hekate payload.

You are telling that I had to inject payload twice because the first time (after i turned off my switch) hekate turned my switch off for real?

Inviato dal mio Nexus 5X utilizzando Tapatalk