Hacking [RCM Payload] Hekate - CTCaer mod

  • Thread starter Thread starter CTCaer
  • Start date Start date
  • Views Views 1,188,973
  • Replies Replies 3,330
  • Likes Likes 128
Hi I recently switched to booting atmosphere through hekate and fss0. What has immediately astonished me was its speed in booting. One thing I noticed is that the sept's boot screen isn't showed whereas fusee-primary shows it on every single boot. I thought that for booting 7.0+ sept was mandatory and that the sept payload was precisely designed to always shows that screen but why on hekate doesn't show up?
Another unrelated thing I'm curious about is which patches are applied when atmosphere=1 is set?
Hekate runs sept once per-firmware then caches the keys and uses those cached keys for future boots.
 
5.3.3 does not work with the RCM Loader, and will not display the GUI of Hekate. The error thrown is: "Missing LP0, Missing or old Minerva Lib. Update bootloader folder".

I've tried putting the bootloader folder into the root of the RCM Loader, and into the folder where the Hekate payload.bin is located.
 
I want to test ubuntu. Is it enough to just create a new partition (with the partition manager from hekate) on my sd card without formatting it?
It won't work, the partition manager from Hekate is destructive it formats the whole SD card. Make a backup from your SD card and copy the files back after formatting.
 
5.3.3 does not work with the RCM Loader
It works with this dongle ;)

It won't work, the partition manager from Hekate is destructive it formats the whole SD card. Make a backup from your SD card and copy the files back after formatting.
Is a backup from the emuMMC useful in this case?
 
Auto boot doesn't work for me. When I turn the Switch off it won't turn on again without injecting a payload. When I used to have Atmosphere it could turn off and back on again and it would auto launch Atmosphere, not with Hekate :(

I try editing my ini it looks like this but still doesn't work

[config]
updater2p=1
{------ Atmosphere ------}
[Atmosphere FSS0 SYS]
fss0=atmosphere/fusee-secondary.bin
kip1=atmosphere/kips/*
emummc_force_disable=1
icon=bootloader/res/sys_cfw_boot.bmp
{}
{-------- Stock ---------}
[Stock SYS]
fss0=atmosphere/fusee-secondary.bin
stock=1
emummc_force_disable=1
icon=bootloader/res/stock_boot.bmp
[Atmosphere CFW]
payload=bootloader/payloads/fusee-primary.bin
icon=bootlogo.bmp

I have the fusee-primary on the payloads folder
 
Auto boot doesn't work for me. When I turn the Switch off it won't turn on again without injecting a payload. When I used to have Atmosphere it could turn off and back on again and it would auto launch Atmosphere, not with Hekate :(

I try editing my ini it looks like this but still doesn't work

[config]
updater2p=1
{------ Atmosphere ------}
[Atmosphere FSS0 SYS]
fss0=atmosphere/fusee-secondary.bin
kip1=atmosphere/kips/*
emummc_force_disable=1
icon=bootloader/res/sys_cfw_boot.bmp
{}
{-------- Stock ---------}
[Stock SYS]
fss0=atmosphere/fusee-secondary.bin
stock=1
emummc_force_disable=1
icon=bootloader/res/stock_boot.bmp
[Atmosphere CFW]
payload=bootloader/payloads/fusee-primary.bin
icon=bootlogo.bmp

I have the fusee-primary on the payloads folder
You are misunderstanding what autoboot does. Autoboot does not auto-inject payloads. That is what an internal modchip is for. Autoboot automatically boots a Hekate configuration so you do not have to navigate the Hekate menu to boot CFW/OFW.
 
  • Like
Reactions: BaamAlex
Is there a way to overwrite raw emummc with a backup from within hekate?
The backup is pretty old, from late 2018.
 

Attachments

  • Screenshot_20201201-212738935.jpg
    Screenshot_20201201-212738935.jpg
    441.6 KB · Views: 292
Last edited by BaamAlex,
This has nothing to do with the switch os. Android, lakka or linux runs outside from the os. With other words said, the firmware doesn't matter here.
Huh. I was watching a tutorial video to install switchroot/android on switch and said I needed to use tegraRcmGui to inject the latest hekate payload to enter rcm so I can run it.
You're saying I can run android without that step?
 
hekate runs before the switch firmware and is completely separate from it. Android and all other non-Nintendo OSes literally do not interact with the switch firmware at all. You only need to update hekate if you want to run the newest Nintendo firmware.
 
hekate runs before the switch firmware and is completely separate from it. Android and all other non-Nintendo OSes literally do not interact with the switch firmware at all. You only need to update hekate if you want to run the newest Nintendo firmware.
Thank you! Seems then even after updating to 11.0.0 FW I can still inject latest Hekate Payload from the github and proceed with the tutorial to run android?
 

Site & Scene News

Popular threads in this forum