Hacking [RCM Payload] Hekate - CTCaer mod

[Maupiti]

Hey guys, can someone please tell me where I have to put the fusee-primary.bin file of atmosphere on my SD card?
Right now I have placed it to SD:/bootloader/payloads and I am able to start it, but I have to navigate to Payloads in order to launch it instead of the Launch button.

You need to create an entry in the .ini of Hekate in order to select it in the Launch section

 

[fenomeno0chris]

You need to create an entry in the .ini of Hekate in order to select it in the Launch section

Thank you!
Can you tell me what exactly I have to write in the .ini file in order to launch the atmosphere payload with the launch button?
My payload is located at: SD:/bootloader/payloads/fusee-primary.bin

 

[Krude]

Thank you!
Can you tell me what exactly I have to write in the .ini file in order to launch the atmosphere payload with the launch button?
My payload is located at: SD:/bootloader/payloads/fusee-primary.bin

Use the same entry type as memloader (also a payload) uses in the hekate .ini template

https://github.com/CTCaer/hekate/blob/master/res/hekate_ipl_template.ini

 

[fenomeno0chris]

Thanks for your answer!
My hekate_ipl.ini file (which is located here SD:/bootloader/hekate_ipl.ini) looks like this now:

[config]
autoboot=0
autoboot_list=0
bootwait=3
verification=1
backlight=100
autohosoff=0
autonogc=1
updater2p=0
payload=bootloader/payloads/fusee-primary.bin

But atmosphere still will not launch when Im hitting the Launch button
I can only launch it with the payload button.

 

[Maupiti]

Thanks for your answer!
My hekate_ipl.ini file (which is located here SD:/bootloader/hekate_ipl.ini) looks like this now:

[config]
autoboot=0
autoboot_list=0
bootwait=3
verification=1
backlight=100
autohosoff=0
autonogc=1
updater2p=0
payload=bootloader/payloads/fusee-primary.bin

But atmosphere still will not launch when Im hitting the Launch button
I can only launch it with the payload button.

The correct way to add an entry is :

{---- ATMOSPHERE 0.9.4 ----}
[Atmosphere]
payload=bootloader/payloads/atmosphere.bin
{ }
change whatever you need ...but keep the brakets, and my payload for atmo is named atmosphere, but it's a fusee.primary renamed for my convenience...

always keep this "format" to add entry for whatever you want to chainload from Hekate, ... I'm actually using Hekate for Atmo or Sxos, or whatever payload ,

You can change the icons also that will show up in the launch section... need to be located in /res folder of Hekate ...

 

[John2022]

This is mine:

It looks pretty good and works well with the other stuff I have such as custom icons and things like that.

Could you unleash your background.bmp please? Sure it does interest somes.

So I upgraded to a 256 samsung evo card but I've noticed every time I use reboot to payload (set to hekate and via HOS restart) and boot hekate (even if it's auto boot) there's a long 2-3 minute hang on the boot logo before anything happens.

Right now my autoboot is set to boot fusse_secondary



Whereas if I push fusse-primary.bin, sx or like even lakka, the switch boots straight into it. I know my card isn't a lemon because it hits it's advertised speeds in CrystalDiskMark and it's space is true according to sdtester. I currently have a 1 for 1 copy of my 128 sd card on it, (except for a few files) and if I reboot to payload using my 128gb sd card it's fast and instant.

Here's my hekate bootloader setup. Anyone know what the issue is? I know there's been talk about U3 cards acting up, and I'm not sure if this is one of those things.

[config]
autoboot=1
autoboot_list=0
bootwait=1
verification=1
backlight=76
autohosoff=0
autonogc=1

{-- Custom Firmware --}
[CFW]
emummc_force_disable=1
fss0=atmosphere/fusee-secondary.bin
kip1patch=nosigchk
atmosphere=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp
{}
[SX OS]
payload=bootloader/payloads/sx.bin
icon=bootloader/res/icon_sx.bmp
{}
[Lakka]
payload=lakka/boot/coreboot.rom
logopath=lakka/boot/splash.bmp
icon=bootloader/res/icon_lakka.bmp
{}

{---- Miscellaneous ---}
[Stock]
emummc_force_disable=1
fss0=atmosphere/fusee-secondary.bin
stock=1
icon=bootloader/res/icon_switch.bmp
{}

Same here. Legit 256Go Samsung Evo Plus Class10U3 and my partition emuNAND is terribly lagging (HOS menus, HBL, Homebrew and some games). Do you solve your problem, and how please?

 

[Maupiti]

Could you unleash your background.bmp please? Sure it does interest somes.



Same here. Legit 256Go Samsung Evo Plus Class10U3 and my partition emuNAND is terribly lagging (HOS menus, HBL, Homebrew and some games). Do you solve your problem, and how please?

The background...is the one by default with Hekate...

--------------------- MERGED ---------------------------

Could you unleash your background.bmp please? Sure it does interest somes.



Same here. Legit 256Go Samsung Evo Plus Class10U3 and my partition emuNAND is terribly lagging (HOS menus, HBL, Homebrew and some games). Do you solve your problem, and how please?

Stop using « kosmos shit »
Sorry......, Atlas shit
Use a clean proper Hekate, to chainload whatever you want..Atmo ..sxos...

 

[John2022]

The background...is the one by default with Hekate...

--------------------- MERGED ---------------------------


Stop using « kosmos shit »
Sorry......, Atlas shit
Use a clean proper Hekate, to chainload whatever you want..Atmo ..sxos...

I do.

Btw, I didn't find any bitmap in the Hekate default package. You means in the repo?

Ton pseudo, il vient de Maupiti Island sur Amiga/AtariST?

 

[JonJaded]

Could you unleash your background.bmp please? Sure it does interest somes.



Same here. Legit 256Go Samsung Evo Plus Class10U3 and my partition emuNAND is terribly lagging (HOS menus, HBL, Homebrew and some games). Do you solve your problem, and how please?

I did a complete wipe and reinstall. Still acts weird time to time but much lag seemed to dissapear. But then again this all happened during the AMS and Hekate optimization patches during October-November, so that could be a placebo.

 

[Maupiti]

I do.

Btw, I didn't find any bitmap in the Hekate default package. You means in the repo?

Ton pseudo, il vient de Maupiti Island sur Amiga/AtariST?

Sorry, I tought you were using Hekate -mod with Nyx...there’s no more.bmp...et non..mon pseudo..c’es Un ancien « popa » de tahitien..

 

[John2022]

@Jonhy Thanks, I plan to do the same. 220 Go is painfull to backup but it's not the first time. Does your emuNAND is minimized or is plain 29Gb?

@Maupiti No problem. I don't find this background btw. Maybe in old release of ArgonNX?

 

[Maupiti]

@Jonhy Thanks, I plan to do the same. 220 Go is painfull to backup but it's not the first time. Does your emuNAND is minimized or is plain 29Gb?

@Maupiti No problem. I don't find this background btw. Maybe in old release of ArgonNX?

Going to look if I can find it in old backups on my Pc and will let you Know

 

[bird333]

Can we boot OFW on emunand with the latest version?

 

[John2022]

Can we boot OFW on emunand with the latest version?

The purpose of the emunand is to don't boot on the OFW. The OFW is on the sysnand of your switch and can't be moved nowhere (and so, not on an emunand).
+ The only way to be able to use a emunand is to boot by a payload on a CFW.

Why do you do that?

 

[bird333]

The purpose of the emunand is to don't boot on the OFW. The OFW is on the sysnand of your switch and can't be moved nowhere (and so, not on an emunand).
+ The only way to be able to use a emunand is to boot by a payload on a CFW.

Why do you do that?

I as well as others would like to keep sysnand at a low firmware and have a 'clean' firmware on emunand. If I'm not mistaken this is something the developers are going to implement. I was just wondering if they had in the latest version.

 

[John2022]

You can do this, by using ChoixDuJour or ChoixDuJourNX (I don't know the exact difference between these two). It permit us to update our sysnand CFW or emunand CFW without connect the switch to the net, so, you could keep your sysnand CFW (or OFW stock) to a lower firmware version and push your emunand to the latest version of the firmware.

 

[LeMageFro]

I as well as others would like to keep sysnand at a low firmware and have a 'clean' firmware on emunand. If I'm not mistaken this is something the developers are going to implement. I was just wondering if they had in the latest version.

Unfortunately no booting stock emuMMC is still not possible. A new version hekate is going to be released very soon (source) but I would be surprised if it added the option, since emuMMC is m4xw's work and not CTCaer's.
I hope we'll be able to have low sysNAND + a clean emuMMC for online + another emuMMC for CFW soon, but I don't think m4xw is actively working on it right now, he seemed to be focused on emulators lately.

The purpose of the emunand is to don't boot on the OFW. The OFW is on the sysnand of your switch and can't be moved nowhere (and so, not on an emunand).
+ The only way to be able to use a emunand is to boot by a payload on a CFW.

Why do you do that?

The point is to have a low firmware on your sysNAND in order to use déjà vu to boot CFW on a first emuMMC without the need for any external device, while still being able to play legit games online from a second clean emuMMC.

 

[20mark]

hello, i can't seem to make hekate boot image work, it always boot with the default one.
here's my hekate_ipl.ini:
(of course i have in the /bootloader dir the bootlogo.bmp, doublechecked that file name is correct)

looks good to me..

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

[Atmosphere]
payload=bootloader/payloads/fusee-primary.bin
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_atmosphere.bmp
{}

[Stock (SYSNAND)]
emummc_force_disable=1
fss0=atmosphere/fusee-secondary.bin
stock=1
icon=bootloader/res/icon_stock.bmp
{}

[SXOS]
payload=bootloader/payloads/sxos.bin
icon=bootloader/res/icon_hekate-atmosphere.bmp
{}

[LOCKPICK]
payload=bootloader/payloads/Lockpick_RCM.bin
icon=bootloader/res/icon_lockpick.bmp
{}

[INCOGNITO]
payload=bootloader/payloads/Incognito_RCM.bin
icon=bootloader/res/icon_lakka.bmp
{}

 

[LSPD_Gamer]

Hi,
What do I need to do modelswap? I want to replace vanilla models with custome models. Can I only use Hekate to do that or do I need some other software?
I also want to play online with the custome models too. Can someone help please?

 

[BaamAlex]

Hi,
What do I need to do modelswap? I want to replace vanilla models with custome models. Can I only use Hekate to do that or do I need some other software?

??? And now again please. What do you want? Hekate is a custom bootloader to enable autorcm or creating a nand backup. Thats all. If you meant a cfw, then you need atmosphère.

I also want to play online with the custome models too. Can someone help please?

Using stuff like this will result in a ban. You can't use a cfw with online services.