Hacking [RCM Payload] Hekate - CTCaer mod

[hippy dave]

Thanks, so can this actually chainload SX for real now?
edit: had a chance to test. Yes it does

 

[Skonikol]

update.bin is not loaded at me. Tried many times.

 

[DJravingMonkey]

I have a backup done on a fat32 sdcard. How do i join the split files? Can i just use copy /b in windows?

 

[Skonikol]

I have a backup done on a fat32 sdcard. How do i join the split files? Can i just use copy /b in windows?

https://github.com/CTCaer/hekate/releases/download/v4.2/joiner_scripts_for_windows_linux_macos.zip

 

[ScarletDreamz]

Since Hekate 4.1, when turning on the console, it just pop up a hekate splash screens and then turns off again. whats the cause of this? :c

 

[sj33]

Since Hekate 4.1, when turning on the console, it just pop up a hekate splash screens and then turns off again. whats the cause of this? :c

This is expected behaviour.

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).

The console should fully power off after displaying the Hekate logo.

 

[ScarletDreamz]

This is expected behaviour.



The console should fully power off after displaying the Hekate logo.

Alright, so it is normal. and not something weird lol. i was like what the fuck, since im using AUTORCM.

 

[daxtsu]

Alright, so it is normal. and not something weird lol. i was like what the fuck, since im using AUTORCM.

If you don't want it to work that way, and you're using 4.2, you can add autohosoff=0 to the boot entries in your hekate_ipl.ini file to get the old behaviour back, if I'm understanding the readme correctly.

 

[CTCaer]

update.bin is not loaded at me. Tried many times.

Since Hekate 4.1, when turning on the console, it just pop up a hekate splash screens and then turns off again. whats the cause of this? :c

It's what sj33 said. It's for protecting your battery, as long as you push the payload again after a HOS power off.

If you don't want it to work that way, and you're using 4.2, you can add autohosoff=0 to the boot entries in your hekate_ipl.ini file to get the old behaviour back, if I'm understanding the readme correctly.

You got that right.
But there's no need to manually edit it. Go to "Options -> Auto HOS power off" and disable it from there. ^^

(As a reminder, this will remain default on. To annoy any user and find out what's the benefit. And if it matches the personal use case, keep it. Otherwise disable it.)

 

[Apel]

is there a error list for hekate? wanted to restore nand and got error 4

 

[CTCaer]

https://github.com/CTCaer/hekate/blob/master/bootloader/libs/fatfs/ff.h#L231
File not found.

As you can see, there's a path above the error. The file must go there.
/backup/<your eMMC S/N>/Restore/

 

[CTCaer]

update.bin is not loaded at me. Tried many times.

Up the update.bin and the one you inject here.

(reminder, the update.bin goes to /bootloader/update.bin)

 

[tom2199]

i think i've found a bug, if I set bootwait to 1 second the switch doesn't boot properly. It just has a black screen and doesn't show anything not even the bootlogo.

 

[Skonikol]

Up the update.bin and the one you inject here.

(reminder, the update.bin goes to /bootloader/update.bin)

I put everything in the right folder. And I even 1-2 times can start 4.2, but then I have a black screen.

 

[210modz]

How would I set sx os to autoboot? I don't see anywhere to select sx os under the autoboot menu. I have it in the payloads folder.

 

[CTCaer]

i think i've found a bug, if I set bootwait to 1 second the switch doesn't boot properly. It just has a black screen and doesn't show anything not even the bootlogo.

hmm strange. It does boot eventually (maybe it puts a big number)? Can you do me a favor and check hekate_ipl.ini? what number it has on delay (I can't check it right now)?

I put everything in the right folder. And I even 1-2 times can start 4.2, but then I have a black screen.

You also see a breathing backlight with hekate's logo? That's auto power off if the console woke up from HOS power off.
So, in 4.2 you can disable it. In 4.1 it's always on. If you want to disable it completely, you'll have to use v4.2 as your injected one.
But if you use autorcm, better keep it. It will protect your battery, if you use a modchip/dongle/etc.

Also breathing backlight is not just black screen. It's sth important to note.

--------------------

@210modz
just read previous comments.
I said many times that a payload must be declared into an .ini for autoboot.

 

[Resaec]

There is a way to actually revert the GC firmware.

Is there an update to this, or something to read up?
Thanks ;D

BTW: Is it possible to add the nogc patch when loading a payload like reinx?
I know it has its nogc file to request patching, but I was able to see my cartridge while installing 5.1.0 using ChoiduJourNX in ReiNX so im concerned.

 

[cherup]

How would I set sx os to autoboot? I don't see anywhere to select sx os under the autoboot menu. I have it in the payloads folder.

You have to add a section for sx and the payload path.
I have created a sx.ini and put in in there.
Using this with autoboot works - not sure if it also works when this in a section in the hetake_ipl.ini ( had some problems yesterday, but maybe more a user problem than the tool)

 

[tom2199]

hmm strange. It does boot eventually (maybe it puts a big number)? Can you do me a favor and check hekate_ipl.ini? what number it has on delay (I can't check it right now)?

falsem alarm, after starting with a new hekate_ipl.ini everything works as expected. the old one was borked i guess

 

[Skonikol]

You also see a breathing backlight with hekate's logo? That's auto power off if the console woke up from HOS power off.
So, in 4.2 you can disable it. In 4.1 it's always on. If you want to disable it completely, you'll have to use v4.2 as your injected one.
But if you use autorcm, better keep it. It will protect your battery, if you use a modchip/dongle/etc.

I made a video