Hacking [RCM Payload] Hekate - CTCaer mod

  • Thread starter Thread starter CTCaer
  • Start date Start date
  • Views Views 1,198,308
  • Replies Replies 3,331
  • Likes Likes 128
Hi, its possible to make a custom layout for the menus ? Would be nice to boot into CFW with just the power button without the vol arrow.
 
is there an easy way to use athmosphere 0.8.5 with hekate or do we need an update for hekate?
You can move the necessary Atmosphère files to your SD, and then chainload fusee-primary via hekate's "payloads..." menu.
Or you can build the individual kips and launch it with those.
 
Last edited by 8BitWonder,
  • Like
Reactions: FunThomas
About the custom warmboot binary lp0fw.bin...
Not sure what exactly it is or where it's from. Is this something you need to update with new versions of atmosphere or hekate? Or is it more of a "get this once and keep it" kind of deal?

I got mine from a Kosmos pack but i don't usually use the pack, and it's not been updated for 0.8.5 yet. While i can get the newest atmosphere kips via the lavatech build bot, it doesn't include a warmboot binary, so i'm not sure i can update.
 
Other than compiling yourself, you may as well just wait a day for Kosmos to be updated.

what's there to compile?

no changes to hekate relating to 0.8.5 compatibility, so there's nothing to build

and the creator of kosmos doesn't compile anything, he just downloads everything like a normal user and puts everything in a zip file
 
but with this way i cant run any unsigned code from home menu
You need these patches with atmosphere to run your unsigned applications from home menu.

what's there to compile?

no changes to hekate relating to 0.8.5 compatibility, so there's nothing to build

and the creator of kosmos doesn't compile anything, he just downloads everything like a normal user and puts everything in a zip file
If memory serves, Kosmos builds Atmosphere's kips+secmon and loads those through hekate.
The kips+secmon aren't individually distributed in Atmo's releases and must be built by the user for use with hekate.
 
Last edited by 8BitWonder,
hekate v4.9 is released!

  • Support for parsing Atmosphere's Fusée Secondary Storage (FFS0)
    Aka, use a fusee-secondary.bin for exosphere/secmon/kips source.
  • Support for partial restore
  • Performance changes for Backup/Restore/Verification
    Aligned buffers will now up the speeds by a lot.
    Verfication is now set to Sparse mode by default.
    It protects from fake sd cards, bad sectors and frequent I/O corruption. Aka, ~100% of cases.
  • And many more

Warning: Because of the new versioning changes, please delete sept/payload.bin.


Check OP or HERE for changelog or more..
 
  • The payloads must go inside /bootloader/payloads.
  • Inis that have boot entries that use kips go to /bootloader/ini or the boot entries inside hekate_ipl.ini.
You access these from Launch->Payloads or Launch/Launch->More configs respectively.

If the folders are empty or hekate_ipl.ini does not have any entry, it will show empty.

Hello! I have a problem "no payloads or libraries found". How to fix it? Can I have some detailed information?
 

Attachments

  • Screenshot_5.jpg
    Screenshot_5.jpg
    13.3 KB · Views: 177
Hello! I have a problem "no payloads or libraries found". How to fix it? Can I have some detailed information?

The post that you quoted pretty much explains your issue, which isn't actually an issue in itself. Hekate doesn't really come with anything extra - You have to add the payloads inside the payload folder yourself. Same goes for the ini configurations. Either download the newest version of Kosmos, which will have most of the things you'll need, put that on your SD card - or go to https://www.sdsetup.com/ and select what you want for yourself. Once you have the necessary ini files etc. you can select a boot entry from Hekate
 
Probably a stupid question, but if i boot via the new FSS0, do i still need an extra warmboot binary / exosphere?
 
Nice! I noticed that in the modernized ini template, you don't use atmosphere=1 for most atmosphère boot entries. Does fss0 automatically include that option and it's only needed when you load modules on their own?

Would a stock 7+ entry that doesn't use the fusee secondary bin still need the atmo patching option? Like this:

Code:
[Stock (7.0.0+)]
secmon=modules/stock/exosphere.bin
warmboot=modules/stock/lp0fw.bin
atmosphere=1
stock=1
 
Oh yeah, would it be possible to get an option to reboot into hekate?

Usually when i need to take out my SD card to update stuff, i reboot into hekate to be able to take out the SD instead of powering off, so i don't need to fetch a dongle again. I also do this when i update hekate. It would be nice to have an option to reload the new update.bin from the hekate menu so i don't have to either go back to RCM and push hekate again or boot with the outdated hekate.
 
  • Like
Reactions: Notnagel

Site & Scene News

Popular threads in this forum