Hacking [RCM Payload] Hekate - CTCaer mod

  • Thread starter Thread starter CTCaer
  • Start date Start date
  • Views Views 1,193,061
  • Replies Replies 3,330
  • Likes Likes 128
I cant find this background.bmp in the github repo, can someone share it?
60391751-95605580-9afe-11e9-9e20-f84163247dcf.png
 
I have a question. if I have in my root atmosphere and sxOS without eMMC and I do not want eMMC. I just want to load NYX and be able to choose the CFW with which to start. what should I do?
 
I cant get the custom icons to show in the launch menu, it keeps using the default ones.

Here is my hekate_ipl.ini inside the bootloader folder.


Code:
[config]
autoboot=0
autoboot_list=0
bootwait=3
verification=1
backlight=100
autohosoff=0
autonogc=1

[Atmosphere]
fss0=atmosphere/fusee-secondary.bin
kip1patch=nosigchk
atmosphere=1
logopath=bootloader/res/atmosphere.bmp
icon=bootloader/res/atmosphere.bmp

[Stock]
fss0=atmosphere/fusee-secondary.bin
stock=1
icon=bootloader/res/atmosphere.bmp

[Atmosphere-emuMMC]
payload=bootloader/payloads/fusee-primary.bin
icon=bootloader/res/atmosphere-emc.bmp

all assets and files are inside the correct folder. So why wont hekate find them?

Also what is the difference between Icon and logo path?
Bit depth of your bmp should be 32, i couldn't make it to work too at first when i tried to make my own icons, was saving them as 24 bit depth bmp and nyx didn't see them... As for the logo path, if im not mistaken it's for the boot logo.
 
  • Like
Reactions: KTroopA and enol
Bit depth of your bmp should be 32, i couldn't make it to work too at first when i tried to make my own icons, was saving them as 24 bit depth bmp and nyx didn't see them... As for the logo path, if im not mistaken it's for the boot logo.

Thanks I spoke to CTCaer on discord and discovered this is very important yes. All working now.
 
  • Like
Reactions: Hanekawa
  • Like
Reactions: crow132
Is there a reason I may not want to use the Nyx GUI? Is everything done while in Hekate prior to detectable/bannable activity? I still have AutoRCM from way back and have been using stock firmware (except to manually update firmware from 5.1.0 to 7~something, then to 8.0.1). In other words, if I was still okay (not banned) for having AutoRCM, having booted Atmosphere twice for manual updates, and using stock firmware until now, is there anything about the new Hekate that will flag my system and add to the ban potential?
 
Is there a reason I may not want to use the Nyx GUI? Is everything done while in Hekate prior to detectable/bannable activity? I still have AutoRCM from way back and have been using stock firmware (except to manually update firmware from 5.1.0 to 7~something, then to 8.0.1). In other words, if I was still okay (not banned) for having AutoRCM, having booted Atmosphere twice for manual updates, and using stock firmware until now, is there anything about the new Hekate that will flag my system and add to the ban potential?

The core of hekate is largely the same, it added support for new atmos and emuemmc stuff, nyx is a module, you can remove it from the sys dir and use the old text interface if you wanted to. There isn't any risk of hekate getting you banned, same with autorcm.
 
Threw together some miscellaneous icons, figured I'd post them up if any of you are interested.
(Maybe someone ought to make a Hekate icon thread similar to the bootlogo thread? :unsure:)

Don't save these preview images for use, you need to use the actual BMPs in the .7z archive.
CjOlpJa.png
v2PINih.png
wr7gcNN.png
XZSA26d.png
 

Attachments

The core of hekate is largely the same, it added support for new atmos and emuemmc stuff, nyx is a module, you can remove it from the sys dir and use the old text interface if you wanted to. There isn't any risk of hekate getting you banned, same with autorcm.

Thank you for the reply. With the addition of emuMMC support, do I need to add a line to disable it (if I read correctly, it's enabled by default).

I'm not looking to change my Hekate setup at all... I just want the added support for 8.1.0 so I can safely update.

Here are the relevant lines of my current config:
Code:
[CFW]
fss0=atmosphere/fusee-secondary.bin
kip1patch=nosigchk
atmosphere=1
logopath=bootloader/bootlogo.bmp
{ }

[Stock]
fss0=atmosphere/fusee-secondary.bin
stock=1
{ }

Do I need to add/change anything? I'm just looking to boot Atmosphere to update without burning fuses, then continue using stock firmware as I have been.
 
Thank you for the reply. With the addition of emuMMC support, do I need to add a line to disable it (if I read correctly, it's enabled by default).

I'm not looking to change my Hekate setup at all... I just want the added support for 8.1.0 so I can safely update.

Here are the relevant lines of my current config:
Code:
[CFW]
fss0=atmosphere/fusee-secondary.bin
kip1patch=nosigchk
atmosphere=1
logopath=bootloader/bootlogo.bmp
{ }

[Stock]
fss0=atmosphere/fusee-secondary.bin
stock=1
{ }

Do I need to add/change anything? I'm just looking to boot Atmosphere to update without burning fuses, then continue using stock firmware as I have been.

You can leave it as is

emummc_force_disable=1 -- Disabled emuMMC if it's enabled.

If you haven't setup emuemmc, you don't need to use that.
 
i have a problem with emummc. I tried migrating my EmuMMC (old method "makemu"), it worked but I'm stuck on the start screen now.
And how do I copy the Emunand folder?
 
If anyone is looking for a cool icon to be used with ReiNX, I've converted an existing photo from the internet that will just work. It adds fancy to the "Launch" menu. I am personally using this myself right now.
 

Attachments

Last edited by Dothackjhe,

Site & Scene News

Popular threads in this forum