Hacking [RCM Payload] Hekate - CTCaer mod

[CTCaer]

any luck on sleep mode on 3.0.1/2? ^^

Nothing yet for 3.0.0-3.0.2. :/
From my side, the last 2-3 days, I only had time for some small bugfixes.

Does the CFW included in this contain exFAT support or is it just in Hekate itself? Trying to figure out if I need a non SDXC card to actually run anything since after booting into CFW it tells me I need the update for SDXC.

Did some searching in the thread but all the SD card issues seemed to be related to backups in the bootloader, which worked fine, not in the CFW.

Are SDHC natively supported or should I get a base SD card?

Thank you!

EDIT: I found the SDfiles updated yesterday which answered the 5.1.0 support question but it appears to still not like SDXC cards so I'm assuming I'll need another SD card

Switch HW supports everything. SDSC/SDHC/SDXC.
The update nag you see, is actually not because you have such a card, but because it's formatted in exFAT.
It needs to enable the license, as explained by @Draxzelex

So, on a driver level, here's the support list
Hekate supports:
SDHC/SDXC
FAT32 / exFAT

Horizon OS:
SDSC/SDHC/SDXC
FAT32 / exFAT (if you have the micro update)

If you don't want to update, format it with FAT32.
Otherwise you update, or install it differently.

First, the CFW IS Hekate (if you consider Hekate a CFW). Second, exFAT support has to be installed onto the console whether from Nintendo's servers or by using a game dump that contains the same system update as your Switch. Third, yes homebrew menu now works on all firmwares. You can thank a 0-byte file titled rtld.stub

Bootloader here would be the payload.bin being sent via USB so there's no SD card involved whatsoever.

Well, hekate IS the bootloader (we call payload, because as you said, it is sent through RCM USB.).
CFW are the atmosphere files.

From a technical and more correct point of view, (based on the current implementation):
Hekate is the bootloader and patcher
Atmo is the Horizon OS loader, a patcher and a custom service manager
Both of them patch the stock Horizon OS and "create" a CFW.
And when you are in and in a boot finished state, only Atmosphere runs (sm).

 

[wicksand420]

Hey @CTCaer I was trying to use nx-dreport.kip on your latest version of hekate and it doesn't show up any more. Any idea whats going on?

This is how my ini looks

[stock]
[CFW]
[nx-dreport]
kip1=loader.kip1
kip1=sm.kip1
kip1=nx-dreport.kip

 

[CTCaer]

Hey @CTCaer I was trying to use nx-dreport.kip on your latest version of hekate and it doesn't show up any more. Any idea whats going on?

This is how my ini looks

[stock]
[CFW]
[nx-dreport]
kip1=loader.kip1
kip1=sm.kip1
kip1=nx-dreport.kip

What do you mean it does not show up?
The entry in hekate? or inside HOS (dreport has no UI)

Also the nx-dreport is intended to run once every time you want to clear the error reports. Not always.
And when it runs, it's best to reboot after checking that your error list is empty.

So the best config to do is:

[CFW]
kip1=loader.kip1
kip1=sm.kip1
[nx-dreport]
kip1=nx-dreport.kip

(stock entry is not needed. Use Reboot (Normal))

 

[wicksand420]

What do you mean it does not show up?
The entry in hekate? or inside HOS (dreport has no UI)

Also the nx-dreport is intended to run once every time you want to clear the error reports. Not always.
And when it runs, it's best to reboot after checking that your error list is empty.

So the best config to do is:

[CFW]
kip1=loader.kip1
kip1=sm.kip1
[nx-dreport]
kip1=nx-dreport.kip

(stock entry is not needed. Use Reboot (Normal))

I mean it doesn't show up in hekate, it did before, that's how I was using it, if I got errors from homebrew, I would run it from hekate and reboot the console.

 

[CTCaer]

Probably because you have 2 entries empty (that should not be a problem though).
Hmm, recheck that you didn't copy pasted any hidden char.
Hekate only supports ASCII. Not windows-1252 or sth else.
That also means that the newline should be LF, not CRLF.

 

[ekosfer147]

Do this implementation support exFAT microsd after we launch cfw? I know that hekate supports it but how about after we launch cfw does it show storage?

 

[CTCaer]

I explained it in the previous comment...
You have the exFAT micro update? Yes
You don't? No

 

[thaikhoa]

Do this implementation support exFAT microsd after we launch cfw? I know that hekate supports it but how about after we launch cfw does it show storage?

There actually a way to do that by extracting the driver from a specific updated fw of a XCI rom to get kep file.
Method 2, CFW
https://gbatemp.net/threads/how-to-install-the-exfat-driver-without-updating-2-x.505176/

 

[ekosfer147]

I explained it in the previous comment...
You have the exFAT micro update? Yes
You don't? No

Oh you are right. How about when we get emuNAND will it have exFAT support for this kind of situation?

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

There actually a way to do that by extracting the driver from a specific updated fw of a XCI rom to get kep file.
Method 2, CFW
https://gbatemp.net/threads/how-to-install-the-exfat-driver-without-updating-2-x.505176/

Warning: Because we install the driver without ever requesting this from Nintendo, this could be detected if you go online and result in a ban.
This warning keeps me not to do it

 

[CTCaer]

There actually a way to do that by extracting the driver from a specific updated fw of a XCI rom to get kep file.
Method 2, CFW
https://gbatemp.net/threads/how-to-install-the-exfat-driver-without-updating-2-x.505176/

Yeah method 2 is great for anyone that does not have the exFat driver, because it does not modify the emmc.
But you can't share it normally (copyrighted).

And yes. Atmosphere will have custom filesystem module

 

[Azel]

Nothing yet for 3.0.0-3.0.2. :/
From my side, the last 2-3 days, I only had time for some small bugfixes.

Thanks for the answer ^^

 

[jimmyj]

I heard there is a boot reason meaning that nintendo can see how I booted. Is there a way to clear this? does your fork of hekate clear it?

 

[SleepyPrince]

I heard there is a boot reason meaning that nintendo can see how I booted. Is there a way to clear this? does your fork of hekate clear it?

Hekate and this fork already clear them

 

[mariogamer]

Warning:
Don't forget your console into RCM. This will drain your battery without a cable. And because, it does not have a battery cuttoff, it will completely drain it.
If this happens, you should power of your console, and let it charge into normal mode (red battery icon top-left) for 20-30 minutes, to open. Better remove the sd card, if it has payloads/homebrew/eMMC files, because it will boot into Horizon OS.

Is it the same behavour in hekate?

 

[CTCaer]

Is it the same behavour in hekate?

Probably, no. Because the hardware is initialized.

But, either way, why someone will leave the console into hekate?

I made this warning because you can't check if the console is ON or OFF in this mode, without plugging it in a PC.

 

[WTFsandwich]

Nothing yet for 3.0.0-3.0.2. :/
From my side, the last 2-3 days, I only had time for some small bugfixes.

Switch HW supports everything. SDSC/SDHC/SDXC.
The update nag you see, is actually not because you have such a card, but because it's formatted in exFAT.
It needs to enable the license, as explained by @Draxzelex

So, on a driver level, here's the support list
Hekate supports:
SDHC/SDXC
FAT32 / exFAT

Horizon OS:
SDSC/SDHC/SDXC
FAT32 / exFAT (if you have the micro update)

If you don't want to update, format it with FAT32.
Otherwise you update, or install it differently.



Well, hekate IS the bootloader (we call payload, because as you said, it is sent through RCM USB.).
CFW are the atmosphere files.

From a technical and more correct point of view, (based on the current implementation):
Hekate is the bootloader and patcher
Atmo is the Horizon OS loader, a patcher and a custom service manager
Both of them patch the stock Horizon OS and "create" a CFW.
And when you are in and in a boot finished state, only Atmosphere runs (sm).

Yeah I just formatted the card to FAT32, I dunno why I was getting SD standards and file systems confused. Thought I was smarter than that XD

Thanks for the clarification on the implementation, I love the technical stuff but it does get over my head sometimes. My understanding of this sort of low level stuff is pretty limited but it sure can be fascinating.

And lastly, thank you for the hard work!

 

[ekosfer147]

Is it the same behavour in hekate?

Probably, no. Because the hardware is initialized.

But, either way, why someone will leave the console into hekate?

I made this warning because you can't check if the console is ON or OFF in this mode, without plugging it in a PC.

Also what about if you enabled auto rcm and charge drained off to %0? Pure lose? Since we can not recharge it in rcm and it will boot into rcm because of auto rcm

 

[CTCaer]

Also what about if you enabled auto rcm and charge drained off to %0? Pure lose? Since we can not recharge it in rcm and it will boot into rcm because of auto rcm

You can charge in RCM. The battery controller and USB-PD still work

 

[ekosfer147]

You can charge in RCM. The battery controller and USB-PD still work

Oh so fake information spreads like hell. Thanks for informing us

 

[CTCaer]

Vote for your favorite hekate - ipl logo!

This will show up by default, if no custom image found in sd card.