Hacking [RCM Payload] Hekate - CTCaer mod

jkyoho · Mar 31, 2024

I have been using fss0 from hekate and emummc on 16.0.3 install and running system required OFW 17+ game no issue, all games install by DBI though

urherenow · Mar 31, 2024

guily6669 said:
it's likely to not be as stable as when SciresM officially had the feature that we could load sigpatches.

And... I'd ask why you say that, but the answer is clear. You have no clue what you're talking about. About anything really. When the feature is enabled, it's not like somebody tried to re-code it. Github repositories keep a thorough history of changes. You revert the change (the change being, IPS parsing code was deleted), then what do you think happens? All of the ORIGINAL code is back. The extent of "coding" required is literally: git revert 46a4357. From the command line/terminal.

Update your shit. Seriously.

guily6669 · Apr 1, 2024

jkyoho said:
I have been using fss0 from hekate and emummc on 16.0.3 install and running system required OFW 17+ game no issue, all games install by DBI though

I never needed to use dbi or mod any game to run on a much lower FW than game requires with the fusee payload.

It's just install with tinfoil which doesn't care for the FW requirement and play, I just needed to update fusee Sigpatches from time-to-time.

Never needed to reset game FW bypasses\checks or reset version with dbi or anything at all.

But off course there will always be a point certain games will simply really need a newer FW...

urherenow said:
And... I'd ask why you say that, but the answer is clear. You have no clue what you're talking about. About anything really. When the feature is enabled, it's not like somebody tried to re-code it. Github repositories keep a thorough history of changes. You revert the change (the change being, IPS parsing code was deleted), then what do you think happens? All of the ORIGINAL code is back. The extent of "coding" required is literally: git revert 46a4357. From the command line/terminal.

Update your shit. Seriously.

No thanks I'm not ready to say bye bye to Lineon conf5 OC which is just a magnitude better for Erista at least until he updates it.

And there's 0 reasons to update when atmosphere 1.6.2 is still the latest stable one and everything and every game works fine on my FW16.1.0...

urherenow · Apr 1, 2024

EDIT: Nevermind... saw the relevant info on the previous page.

Ewiko · May 22, 2024

In the rentry guide or on the sigmapatches site, for hekate_ipl.ini with emuMMC there is no option emummcforce=1, do you know if it is activated by default if I do not put it under the emummc atmosphere block?

Hayato213 · May 22, 2024

Ewiko said:
In the rentry guide or on the sigmapatches site, for hekate_ipl.ini with emuMMC there is no option emummcforce=1, do you know if it is activated by default if I do not put it under the emummc atmosphere block?

For emummc yes

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

{--- Custom Firmware ---}
[CFW (SYSMMC)]
fss0=atmosphere/package3
kip1patch=nosigchk
emummc_force_disable=1
icon=bootloader/res/sysnand.bmp
{}

[CFW (EMUMMC)]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
icon=bootloader/res/emummc.bmp
{}

Ewiko · May 22, 2024

Hayato213 said:
For emummc yes

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

{--- Custom Firmware ---}
[CFW (SYSMMC)]
fss0=atmosphere/package3
kip1patch=nosigchk
emummc_force_disable=1
icon=bootloader/res/sysnand.bmp
{}

[CFW (EMUMMC)]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
icon=bootloader/res/emummc.bmp
{}

My atmosphere block looks like this

[Atmosphere CFW]
payload=bootloader/payloads/fusee.bin
icon=bootloader/res/icon_payload.bmp

should I add emummcforce=1 ?

In the hekate doc it says "if emummc.ini is disabled or not found, then it causes an error", this is perhaps a good solution to avoid nonsense and start atmosphere on the sysnand

Hayato213 · May 22, 2024

Ewiko said:
My atmosphere block looks like this

[Atmosphere CFW]
payload=bootloader/payloads/fusee.bin
icon=bootloader/res/icon_payload.bmp

should I add emummcforce=1 ?

In the hekate doc it says "if emummc.ini is disabled or not found, then it causes an error", this is perhaps a good solution to avoid nonsense and start atmosphere on the sysnand

You don't need it since you are using fusee.bin, it auto boot emunand if you have an emunand.

Ewiko · May 22, 2024

Hayato213 said:
You don't need it since you are using fusee.bin, it auto boot emunand if you have an emunand.

thank you

Tyvar1 · Jun 11, 2024

hekate v6.2.0 & Nyx v1.6.2 Released!

https://github.com/CTCaer/hekate/releases/tag/v6.2.0

Blythe93 · Jun 11, 2024

I've just updated Hekate on my Switch and I'm unable to load Atmosphere's package3 via Hekate's FSS0 anymore. Prior to updating, it would boot into black screen, now it boots into solid blue screen. Launching Atmosphere via latest fusee.bin works, however, so I'm not sure what may be the issue. Here's my hekate_ipl.ini (similar to the one provided in the sigpatches thread):

Code:

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

[Atmosphere FSS0 emuMMC]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
atmosphere=1
icon=bootloader/res/emu_boot.bmp

[Atmosphere FSS0 sysMMC]
fss0=atmosphere/package3
kip1patch=nosigchk
atmosphere=1
emummc_force_disable=1
icon=bootloader/res/sys_cfw_boot.bmp

[Stock sysMMC]
fss0=atmosphere/package3
emummc_force_disable=1
stock=1
icon=bootloader/res/stock_boot.bmp

I've also updated Atmosphere, firmware, sigpatches, sys-patch and MissionControl to the latest versions.

BaamAlex · Jun 11, 2024

Blythe93 said:
I've just updated Hekate on my Switch and I'm unable to load Atmosphere's package3 via Hekate's FSS0 anymore. Prior to updating, it would boot into black screen, now it boots into solid blue screen. Launching Atmosphere via latest fusee.bin works, however, so I'm not sure what may be the issue. Here's my hekate_ipl.ini (similar to the one provided in the sigpatches thread):

Code:

[config] autoboot=0 autoboot_list=0 bootwait=0 autohosoff=0 autonogc=1 updater2p=1 backlight=100 [Atmosphere FSS0 emuMMC] fss0=atmosphere/package3 kip1patch=nosigchk emummcforce=1 atmosphere=1 icon=bootloader/res/emu_boot.bmp [Atmosphere FSS0 sysMMC] fss0=atmosphere/package3 kip1patch=nosigchk atmosphere=1 emummc_force_disable=1 icon=bootloader/res/sys_cfw_boot.bmp [Stock sysMMC] fss0=atmosphere/package3 emummc_force_disable=1 stock=1 icon=bootloader/res/stock_boot.bmp

I've also updated Atmosphere, firmware, sigpatches, sys-patch and MissionControl to the latest versions.

Does your setup work with this config?

Blythe93 · Jun 11, 2024

BaamAlex said:
Does your setup work with this config?

Nope. Atmosphere CFW works only if I push the fusee.bin payload. No issues in that case, only if I try to load Atmosphere's package3 via Hekate's FSS0.

BaamAlex · Jun 11, 2024

Same here. Booting via hekate doesn't work. It ends in a black screen, or in my case for example with a blue screen.

Blythe93 · Jun 11, 2024

BaamAlex said:
Same here. Booting via hekate doesn't work. It ends in a black screen, or in my case for example with a blue screen.

Same here. Before I updated it was the black one, but now it's the solid blue one after the update. Thankfully, pushing Atmosphere's fusee.bin and using sys-patch still works.

BaamAlex · Jun 11, 2024

Blythe93 said:
Same here. Before I updated it was the black one, but now it's the solid blue one after the update. Thankfully, pushing Atmosphere's fusee.bin and using sys-patch still works.

Sys patch works? I also use this, but I can't start my games.

Blythe93 · Jun 11, 2024

BaamAlex said:
Sys patch works? I also use this, but I can't start my games.

I'm using this one. Apparently, it's the latest one for now. Note that I've tested only ACNH to see if it works and it does indeed work. Logs show that they work as well.

BaamAlex · Jun 11, 2024

Blythe93 said:
I'm using this one. Apparently, it's the latest one for now. Note that I've tested only ACNH to see if it works and it does indeed work. Logs show that they work as well.

I love you. It works.

Ethelbert · Jun 11, 2024

In the Hekate commit that adds the 18.1.0 support,
https://github.com/CTCaer/hekate/commit/68408bbb798c8cf478365cbdf5f2df6703d776e2
is it right that the newly added lines are still _fs_patches_1800 and _fs_patches_1800_exfat?
I'm no expert, but the previous pattern seems different.

EmuMMC commit has a separate 1810.
https://github.com/m4xw/emuMMC/commit/804d56f69cded846e4911d8a40aab728da3c8359

Deleted member 702243 · Jun 11, 2024

Ethelbert said:
In the Hekate commit that adds the 18.1.0 support,
https://github.com/CTCaer/hekate/commit/68408bbb798c8cf478365cbdf5f2df6703d776e2
is it right that the newly added lines are still _fs_patches_1800 and _fs_patches_1800_exfat?
I'm no expert, but the previous pattern seems different.

EmuMMC commit has a separate 1810.
https://github.com/m4xw/emuMMC/commit/804d56f69cded846e4911d8a40aab728da3c8359

There was no update to fs module since 18.0.0

Or so I'm told since it was said the patches were the same as before...

But you can check yourself, no fs updated in 18.1.0

https://switchbrew.org/wiki/18.1.0

but yes it is weird they'd add new lines with different pattern when it didnt even change, it doesnt look like they ever did that before? it may be a mistake causing bugs

Edit: no, looking further up, this happened in 8.1.0 also. It's probably nothing, the kip ids maybe changed for some reason but because the module itself is the same, the patches are the same as before

Hacking [RCM Payload] Hekate - CTCaer mod

Well-Known Member

Well-Known Member

GbaTemp is my Drug

Well-Known Member

Member

Newcomer

Member

Newcomer

Member

Well-Known Member

The Treasure Tracker

UDE GA NARU ZE!

The Treasure Tracker

UDE GA NARU ZE!

The Treasure Tracker

UDE GA NARU ZE!

The Treasure Tracker

UDE GA NARU ZE!

Well-Known Member

Well-Known Member

Similar threads

Popular threads in this forum