Hacking [RCM Payload] Hekate - CTCaer mod

[CTCaer]

I wanted to do that after the appearance customlogo appeared menu Hekate for further action.
I created an ini file with a download of Hekate and put autoboot. But in this case customlogo goes into recursive loading until I press the vol button.
Is it possible to fix it with some configurations?

Never put hekate on hekate on autoboot. xD
Either autoboot with an atmosphere config, or use other payloads that are not hekate.

Yeah you can stop this, by going to the menu and disabling autoboot to hekate or choosing another option.
(All versions of hekate read the same file and do the same actions. The only supported way for self chainloading and updated hekate, is update.bin)

 

[annson24]

Well I just encountered the "Sleep Mode Library is Missing" error a while ago. I was just playing and decided to quintuple check my burnt fuse via hekate's menu (because I'm a little bit paranoid as I only have 1 burnt fuse, heh) so I turn off my switch and injected the payload, it went on a black screen so what I did was to force shut down the switch, reinjected the payload but still the same. I then force shut down again and removed the sdcard then injected the payload and this time it entered hekate's menu. That's when I found out about the error. Tried to reboot into hekate's menu again and still the same. Last thing I did was I shut down again, reinserted the sdcard, this time I held down Vol- before injecting the payload and this time it booted into the menu without the error. After that it's back to normal, tried rebooting couple of times and I cannot reproduce the error anymore. Weird.

 

[CTCaer]

Well I just encountered the "Sleep Mode Library is Missing" error a while ago. I was just playing and decided to quintuple check my burnt fuse via hekate's menu (because I'm a little bit paranoid as I only have 1 burnt fuse, heh) so I turn off my switch and injected the payload, it went on a black screen so what I did was to force shut down the switch, reinjected the payload but still the same. I then force shut down again and removed the sdcard then injected the payload and this time it entered hekate's menu. That's when I found out about the error. Tried to reboot into hekate's menu again and still the same. Last thing I did was I shut down again, reinserted the sdcard, this time I held down Vol- before injecting the payload and this time it booted into the menu without the error. After that it's back to normal, tried rebooting couple of times and I cannot reproduce the error anymore. Weird.

You use exfat?
If yes better check and repair it under windows. Then copy the files again.

Seems like a corruption problem.
Except if the sd reader connector is not properly seated.

 

[annson24]

You use exfat?
If yes better check and repair it under windows. Then copy the files again.

Seems like a corruption problem.
Except if the sd reader connector is not properly seated.

Yeah, I do. But even after removing the sdcard the error still appeared, is that still an sdcard issue?

 

[CTCaer]

Yeah, I do. But even after removing the sdcard the error still appeared, is that still an sdcard issue?

The sleep mode configuration is inside /bootloader/sys/libsys_lp0.bso. so if you remove the card, it will say it's missing.

 

[annson24]

The sleep mode configuration is inside /bootloader/sys/libsys_lp0.bso. so if you remove the card, it will say it's missing.

Ahh. Yes. Thanks a lot. Will monitor it for a few more days. If the problem arise again I will try to reformat the sdcard.

 

[Sno0t]

Hey everyone
Could anone help me please?
I am trying to load SX OS with additional system modules.
Is this even possible at all?
Wihtin my hekate ipl I have something similar to this:

[SXOS + synet]
payload=bootloader/payloads/sxos.bin
kip1=[...]/sys-netcheat.kip1
secmon=[...]/exosphere.bin
debugmode=1
atmosphere=1
kip1patch=nosigchk
fullsvcperm=1

Does the order matter here?
SX OS starts up quite fine, but I can't connect via sysnet client.
Any help is appreciated
thanks in advance and kind regards

(Btw. is there a list of ALL available custom kips and their meanings? )

 

[Huntereb]

I am trying to load SX OS with additional system modules.
Is this even possible at all?

No.

 

[mariogamer]

Is it possible to have an in-place encryption/decryption with modules? I remember someone talking about it on the old hekate repo.

 

[minomore]

ive just picked up a 256gb sd card and all i keep getting is failed to int. im just wondering what my options are if any? many thanks

 

[Dothackjhe]

What are the attached ".txt" files for?

Also, how do I configure Hekate to autoboot as soon as the custom splash screen is shown? See, as soon as I plugged the device to the computer via a USB Type-C cable in RCM Mode and injected the Hekate 4.2 payload, a custom splash screen appears only to leave a black screen afterwards. I was able to circumvent this problem by hitting the "power" button once so as to terminate whichever state the Switch is in and then re-do the process again. Only after doing this *every single time,* since the version 4.2 update, that I manage to boot the bootloader successfully. I'm guessing that it has something to do with Hekate 4.2's default configuration?

 

[Maupiti]

What are the attached ".txt" files for?

Also, how do I configure Hekate to autoboot as soon as the custom splash screen is shown? See, as soon as I plugged the device to the computer via a USB Type-C cable in RCM Mode and injected the Hekate 4.2 payload, a custom splash screen appears only to leave a black screen afterwards. I was able to circumvent this problem by hitting the "power" button once so as to terminate whichever state the Switch is in and then re-do the process again. Only after doing this *every single time,* since the version 4.2 update, that I manage to boot the bootloader successfully. I'm guessing that it has something to do with Hekate 4.2's default configuration?

You mean Autoboot Hekate itself ? You can’t ... goes in a loop.. You can only Autoboot Atmosphere or other payloads.
Go back to Hekate menu to disable Autoboot to change this behavior.

 

[CTCaer]

What are the attached ".txt" files for?

Also, how do I configure Hekate to autoboot as soon as the custom splash screen is shown? See, as soon as I plugged the device to the computer via a USB Type-C cable in RCM Mode and injected the Hekate 4.2 payload, a custom splash screen appears only to leave a black screen afterwards. I was able to circumvent this problem by hitting the "power" button once so as to terminate whichever state the Switch is in and then re-do the process again. Only after doing this *every single time,* since the version 4.2 update, that I manage to boot the bootloader successfully. I'm guessing that it has something to do with Hekate 4.2's default configuration?

You mean Autoboot Hekate itself ? You can’t ... goes in a loop.. You can only Autoboot Atmosphere or other payloads.
Go back to Hekate menu to disable Autoboot to change this behavior.

Nuh.
This is

• Auto full power off when the device woke up from HOS' power off
  Usefull with modchips/dongles when using AutoRCM. (You can see it as a breathing backlight with hekate's logo).

It basically detects that the console woke up from an alarm set by HOS and powers off to protect your battery and not stay in Autorcm (as long as you inject the payload ofc).

In 4.2, there's an option to disable it, if it does not meet your use case. Options -> Auto HOS power off -> Disable.

 

[Maupiti]

Nuh.
This is

• Auto full power off when the device woke up from HOS' power off
  Usefull with modchips/dongles when using AutoRCM. (You can see it as a breathing backlight with hekate's logo).

It basically detects that the console woke up from an alarm set by HOS and powers off to protect your battery and not stay in Autorcm (as long as you inject the payload ofc).

In 4.2, there's an option to disable it, if it does not meet your use case. Options -> Auto HOS power off -> Disable.

I was thinking about that also, but I understood he wanted to Autoboot Hekate...

 

[Dothackjhe]

I was thinking about that also, but I understood he wanted to Autoboot Hekate...

Version 4.0 of Hekate booted just fine with me. It's only in version 4.2 that it no longer does it.

I've yet to check out what CTCaer refers to.

Nuh.
This is

• Auto full power off when the device woke up from HOS' power off
  Usefull with modchips/dongles when using AutoRCM. (You can see it as a breathing backlight with hekate's logo).

It basically detects that the console woke up from an alarm set by HOS and powers off to protect your battery and not stay in Autorcm (as long as you inject the payload ofc).

In 4.2, there's an option to disable it, if it does not meet your use case. Options -> Auto HOS power off -> Disable.

What is it do you mean when you spoke of "HOS?" What does it do?

 

[Maupiti]

Version 4.0 of Hekate booted just fine with me. It's only in version 4.2 that it no longer does it.

I've yet to check out what CTCaer refers to.



What is it do you mean when you spoke of "HOS?" What does it do?

It means that if you have AutoRCM enable and you power off the switch from Horizon it goes back to RCM and from there injecting again Hekate payload truly powers off the switch...

This feature was not present in 4.0. Appeared in 4.1 and can be enabled or disabled in 4.2

 

[Dothackjhe]

It means that if you have AutoRCM enable and you power off the switch from Horizon it goes back to RCM and from there injecting again Hekate payload truly powers off the switch...

This feature was not present in 4.0. Appeared in 4.1 and can be enabled or disabled in 4.2

Thanks. I did not know this was the case until now.

 

[Maupiti]

Makes it faster to truly power off without entering again in Hekate´s menu.

 

[Sonansune]

can someone tell me what does the update.bin do? it's identical to the normal payload.

 

[soniczeki]

How can i disable autoboot? I can't go the options menu while booting. It just boots