Hacking [RCM Payload] Hekate - CTCaer mod

  • Thread starter CTCaer
  • Start date
  • Views 1,087,011
  • Replies 3,311
  • Likes 128

urherenow

Well-Known Member
Member
Joined
Mar 8, 2009
Messages
4,823
Trophies
2
Age
48
Location
Japan
XP
3,760
Country
United States
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.
 
Last edited by urherenow,

guily6669

GbaTemp is my Drug
Member
Joined
Jun 3, 2013
Messages
2,379
Trophies
1
Age
34
Location
Doomed Island
XP
2,187
Country
United States
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...
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...
 
  • Like
Reactions: impeeza

Ewiko

Member
Newcomer
Joined
Aug 17, 2018
Messages
15
Trophies
0
Age
44
XP
75
Country
France
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

Newcomer
Member
Joined
Dec 26, 2015
Messages
20,150
Trophies
1
XP
21,412
Country
United States
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

Member
Newcomer
Joined
Aug 17, 2018
Messages
15
Trophies
0
Age
44
XP
75
Country
France
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

Newcomer
Member
Joined
Dec 26, 2015
Messages
20,150
Trophies
1
XP
21,412
Country
United States
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.
 

Blythe93

The Treasure Tracker
Member
Joined
Oct 19, 2022
Messages
1,026
Trophies
1
XP
2,398
Country
Serbia, Republic of
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

UDE GA NARU ZE!
Member
Joined
Jul 23, 2018
Messages
6,109
Trophies
1
Age
29
Location
Lampukistan
Website
hmpg.net
XP
6,263
Country
Germany
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

The Treasure Tracker
Member
Joined
Oct 19, 2022
Messages
1,026
Trophies
1
XP
2,398
Country
Serbia, Republic of
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.
 

Ethelbert

Well-Known Member
Member
Joined
May 4, 2023
Messages
140
Trophies
0
Age
38
XP
221
Country
Serbia, Republic of

4d1xlaan

Well-Known Member
Member
Joined
Apr 21, 2024
Messages
329
Trophies
0
XP
275
Country
United States
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
 
Last edited by 4d1xlaan,

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    SylverReZ @ SylverReZ: https://www.youtube.com/watch?v=5aRVjiaM88Y