Hacking [RCM Payload] Hekate - CTCaer mod

[Deleted User]

Alright, here's a premade ini file for those who want to autoboot into either ReiNX or sxos. Throw your bin files into bootloader/payloads/

This is for use within the hekate_ipl ini file

backlight=100
autohosoff=1

{-- Custom Firmwares --}
[SXOS]
payload=bootloader/payloads/SXOS.bin
[ReiNX]
payload=bootloader/payloads/ReiNX.bin
{ }

 

[CTCaer]

For the new auto power off function, it's useful in general when you're using a dongle, but can i recommend adding the ability to hold VOL- like with auto-boot to enter hekate proper instead of automatically shutting down? Just so you don't have to go through two boot cycles when you power off your switch or it crashed or whatever and you want to boot it up again immediately.

Well it's possible, but not VOL-. With VOL+ maybe.

But if you use dongle or modchip, you can skip it if you use it inside 15 seconds of a power off..

 

[SirByte]

Does kip1patch=nogc still work with atmosphere 0.7 when booting using Hekate CTCaer Mod 4.2, given that it now loads a payload instead of .kip files? Is there any (easy) way to get nogc back?

 

[Maupiti]

So something like this?

{------ SXOS ------}
[SXOS]
payload=/bootloader/payloads/SXOS.bin
{ }

Yep

 

[CTCaer]

Does kip1patch=nogc still work with atmosphere 0.7 when booting using Hekate CTCaer Mod 4.2, given that it now loads a payload instead of .kip files? Is there any (easy) way to get nogc back?

Nope. Chainloading a payload is clean.

This patch is done when using hekate to load the kips.

 

[notimp]

Please elaborate. "Nope" as in - there is currently no way to have hekate load Atmosphere 0.7.* while disabling the gamecard slot update?

Do you know?

 

[CTCaer]

Please elaborate. "Nope" as in - there is currently no way to have hekate load Atmosphere 0.7.* while disabling the gamecard slot update?

Do you know?

There is.

You need to get HOS side of atmosphere in kips.
(loader/sm/pm/fs_mitm/etc)

 

[notimp]

Sorry, too high concept. HOS is horizon OS? You are describing, that the kips have to be modified on the Horizon side of atmosphere now, correct? As in "modify code there", not as in "as an enduser, place something already premade there", correct?

 

[CTCaer]

Sorry, too high concept. HOS is horizon OS? You are describing, that the kips have to be modified on the Horizon side of atmosphere now, correct? As in "modify code there", not as in "as an enduser, place something already premade there", correct?

As in, compile atmosphere and take its compiled parts, instead of fusee secondary (which includes them into one big binary).

And then use them via hekate.
If you don't want to use exosphere, you can now only comment one line, for all kips to be compatible with ninty's secmon.

So there's nothing premade right now that matches the 0.7.x changes. But keep an eye out there for builds (like sdfiles or sdsetup. I don't distribute any atmo builds, btw).

 

[notimp]

Thank you for spelling it out. I'll at least learn some new component names and functions today.

 

[SirByte]

So if you have the d502f3f build from lavatech, which includes exosphere.bin and the four .kip files, you can at least partially implement Atmosphere 0.7.1 with nogc (wonder if the nosigchk still works too?), but you'd miss out on creport and perhaps boot (which may be needed for <4.0.0 firmwares) which the build script does not compile.

EDIT: In another Switch sections you can find some "sweet patches", one for 4.0.0+ that includes a nogc patch for Atmosphere 0.7.1

 

[Mysuke]

I would like to enter Maintenance Mode without disabling autorcm, it's possible to do that after booting Hekate?

 

[shchmue]

I would like to enter Maintenance Mode without disabling autorcm, it's possible to do that after booting Hekate?

yes. hold vol +/- immediately after selecting a launch profile. if you booted to rcm or hekate in the first place, you’re not burning fuses, period.

 

[CTCaer]

I would like to enter Maintenance Mode without disabling autorcm, it's possible to do that after booting Hekate?

yes. hold vol +/- immediately after selecting a launch profile. if you booted to rcm or hekate in the first place, you’re not burning fuses, period.

This ^

You have time to press and hold both vol buttons, as the launching process unravels, until you see the screen turn off/on with nintendo logo.

 

[Mysuke]

Thanks guys, it worked.

 

[Drillakilla]

I use the autoboot feature to load the custom firmware.

When inside autoboot, the only options I see are

CFW, Newest LayeredDFS, stock.

If i choose CFW, I believe it loads atmosphere as that is saved in the Bootlader/inifolder. My question is, how do I add other firmwares here, as I have Reinx but it's in bin format?

I can load Reinx but I usually do this through the payloads feature.

 

[Drillakilla]

Alright, here's a premade ini file for those who want to autoboot into either ReiNX or sxos. Throw your bin files into bootloader/payloads/

This is for use within the hekate_ipl ini file

backlight=100
autohosoff=1

{-- Custom Firmwares --}
[SXOS]
payload=bootloader/payloads/SXOS.bin
[ReiNX]
payload=bootloader/payloads/ReiNX.bin
{ }

How do I do this mate, do I create a new ini file?

 

[Nononoki]

Can't do a backup with any version later than 2.3. It says "Fatal Error (1)" when I try to. What am I doing wrong? MicroSD card is exfat btw.

 

[CTCaer]

Can't do a backup with any version later than 2.3. It says "Fatal Error (1)" when I try to. What am I doing wrong? MicroSD card is exfat btw.

Check that your sd card reader is properly seated. Fatal errors 1, are disk errors on the low level.

 

[paranormalCrystal]

So i've been trying to set this up for a while, but every time I try launch CFW, after it says ''applying patch nosigchk on fs kip1 sect 0'', it suddenly just cuts to a black screen and never loads anything. It shouldn't be a sd corruption because reinx worked fine.