Thanks, so can this actually chainload SX for real now?
edit: had a chance to test. Yes it does
edit: had a chance to test. Yes it does
Last edited by hippy dave,
https://github.com/CTCaer/hekate/releases/download/v4.2/joiner_scripts_for_windows_linux_macos.zipI have a backup done on a fat32 sdcard. How do i join the split files? Can i just use copy /b in windows?
This is expected behaviour.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
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).
Alright, so it is normal. and not something weird lol. i was like what the fuck, since im using AUTORCM.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.
update.bin is not loaded at me. Tried many times.
It's what sj33 said. It's for protecting your battery, as long as you push the payload again after a HOS power off.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
You got that right.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.
Up the update.bin and the one you inject here.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)
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 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.
You also see a breathing backlight with hekate's logo? That's auto power off if the console woke up from HOS power off.I put everything in the right folder. And I even 1-2 times can start 4.2, but then I have a black screen.
Is there an update to this, or something to read up?There is a way to actually revert the GC firmware.
You have to add a section for sx and the payload path.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.
falsem alarm, after starting with a new hekate_ipl.ini everything works as expected. the old one was borked i guesshmm 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 made a videoYou 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.