Hacking Sigpatches for Atmosphere (Hekate, fss0, fusee & package3)

[urherenow]

I'm gonna ask a stupid question. The fusee.bin in the atmosphere github page, what is the difference between that and the hekate_ctcaer_x.x.x.bin?
Previously i've been using the fusee.bin from Atmosphere and transferred into bootloader>payloads folder
while i renamed hekate_ctcaer_x.x.x.bin into reboot_payload.bin and place it in the Atmosphere root folder, and everything works fine.

For the current new fw, i've seen ppl use the modified fusee.bin by user Krejza9 as payload as well as renamed to reboot.payload.bin and worked.
So my question is by normal practice, is hekate_ctcaer_x.x.x.bin also a fusee.bin that i can just put into payloads folder as well as atmosphere root (reboot_payload.bin)?

Short answer: NO.

Long answer: Don't hijack the thread. This is for sigpatches, not for CFW support. Fusee from the github page no longer can use sigpatches at all. You have to use sys-patch, build your own fusee.bin with ips patching added back in, or download the modified one from this thread (which has been uploaded/linked several times, so you better be sure you're getting the LATEST modified fusee). hekate is a bootloader that can chainload fusee.bin, or directly load package3, depending on your settings (hekate_ipl.ini).

 

[chower]

Fusee from the github page no longer can use sigpatches at all

Thank you, that's kinda also what i wanted to know regarding how the fusee and sigpatches are related and apologise for the noobie questions as a result.
Update: I've updated with the modified fusee and works fine now, thanks~

 

[arabtm]

Tesla is required as well?

apparently not. I also just realised this, based on the other comments
but having tesla is a nice addition, such as the ability to use emuiibo in supported games can only be used with tesla GUI.

Post automatically merged: Jun 20, 2024

What issues with the modified fusee.bin, just those games you mentioned?

I just recently updated to 18.1.0 using sigpatches and the fusee.bin with KIP support and all games tested so far loaded fine and Edizon cheats (Tesla overlay) 1.08. However, for Tinfoil 18 R1 i did have to apply the latest sys_patch as that would not work at all without it.

well. the game that I tested, sometimes doesn't work. at first, I tried everything seems fine. but some other time, I tried to start the game, it shows game corrupted error. I only tested 2 games, I didn't bother to test all games, but at least for me, it seems the modified fusee.bin not working properly. with sys-patch, it's quite straightforward and all games, including XCI dump all works fine again.

 

[RedColoredStars]

I'm gonna ask a stupid question. The fusee.bin in the atmosphere github page, what is the difference between that and the hekate_ctcaer_x.x.x.bin?
Previously i've been using the fusee.bin from Atmosphere and transferred into bootloader>payloads folder
while i renamed hekate_ctcaer_x.x.x.bin into reboot_payload.bin and place it in the Atmosphere root folder, and everything works fine.

For the current new fw, i've seen ppl use the modified fusee.bin by user Krejza9 as payload as well as renamed to reboot.payload.bin and worked.
So my question is by normal practice, is hekate_ctcaer_x.x.x.bin also a fusee.bin that i can just put into payloads folder as well as atmosphere root (reboot_payload.bin)?

lol. What is the difference? One is hekate and one is fusee. Ask yourself... when you launch fusee, does it take you to hekate? No. Also, the majority are renaming hekate to reboot_payload. Not fusee.

 

[Jakkal666]

Did you try again? Because under certain circumstances that is normal behavior due to the "autohosoff" setting in hekate.

I currently have Auto HOS Power Off at "OFF" in Hekate. If I use the package posted a few posts back containing Tesla, sys-patch etc. should I enable or disable this setting to circumvent the behaviour of the user Clutt? I've never tinkered with this option to my knowledge and I'm not that familiar with either sys-patches nor Tesla considering sigpatches in the past.

 

[impeeza]

I'm gonna ask a stupid question. The fusee.bin in the atmosphere github page, what is the difference between that and the hekate_ctcaer_x.x.x.bin?

both are bootloaders, they do the same thing in different ways, also Hekate have a graphical interface.

Previously i've been using the fusee.bin from Atmosphere and transferred into bootloader>payloads folder
while i renamed hekate_ctcaer_x.x.x.bin into reboot_payload.bin and place it in the Atmosphere root folder, and everything works fine

It's a way to do it, no problem.

For the current new fw, i've seen ppl use the modified fusee.bin by user Krejza9 as payload as well as renamed to reboot.payload.bin and worked.

That's is needed if you like to load FS Patches and use Fusee.bin as your payload (even if you chainload fusee from Hekate)

So my question is by normal practice, is hekate_ctcaer_x.x.x.bin also a fusee.bin that i can just put into payloads folder as well as atmosphere root (reboot_payload.bin)?

Yes you can but will no work.

 

[kidkat210]

Thank you, that's kinda also what i wanted to know regarding how the fusee and sigpatches are related and apologise for the noobie questions as a result.
Update: I've updated with the modified fusee and works fine now, thanks~

Just wanted to mention that fusee.bin is the same payload as reboot_payload.bin by default. So replacing reboot_payload.bin with fusee.bin is pointless

 

[RedColoredStars]

I currently have Auto HOS Power Off at "OFF" in Hekate. If I use the package posted a few posts back containing Tesla, sys-patch etc. should I enable or disable this setting to circumvent the behaviour of the user Clutt? I've never tinkered with this option to my knowledge and I'm not that familiar with either sys-patches nor Tesla considering sigpatches in the past.

Perhaps this may help, but I'm not so sure on vs off really makes that much of a difference. Mine is set to on and when I get the logo followed by power-off, I just push the payload again and then it works.

 

[GDT]

I just tried to boot hekate with @impeeza hekate_ipl.ini file, modded for my necessities.
I can start atmosphere with fusee (1st choose) but if I select the second one it doesn't load and goes to RCM mode, inject hekate with tegraRCM and got "HOS panic occurred!" with code01 screen.
What's wrong?

 

[alcab]

I think you are using the wrong version of Hekate. The same happened to me a few pages ago.

Go here:
https://gbatemp.net/threads/sigpatc...kate-fss0-fusee-package3.571543/post-10438484

And then keep reading my next messages. Hope this helps.

 

[impeeza]

I just tried to boot hekate with @impeeza hekate_ipl.ini file, modded for my necessities.
I can start atmosphere with fusee (1st choose) but if I select the second one it doesn't load and goes to RCM mode, inject hekate with tegraRCM and got "HOS panic occurred!" with code01 screen.
What's wrong?

Upgrade Hekate, Atmosphère, sigpatches and SYS-Patch from the official repo.

On the Post:
https://gbatemp.net/threads/sys-patch-sysmod-that-patches-on-boot.633517/post-10438920

There are the links:

https://github.com/Atmosphere-NX/Atmosphere/releases
https://github.com/CTCaer/Hekate/releases
https://gbatemp.net/threads/sigpatches-for-atmosphere-hekate-fss0-fusee-package3.571543/ (on the OP)
https://gbatemp.net/download/sys-patch-1-5-2-binary-fw-18-1-0-atmosphere-1-7-1.38686/

 

[chower]

Yes you can but will no work.

Thank you for answering my queries. I've only just figured out that hekate_ctcaer_x.x.x.bin is really just to reboot to hekate and then chainload fusee.bin from there on, and that reboot_payload.bin is just whichever payload i want it to reboot to (whether hekate or fusee). And due to this new fw requiring a whole new modified fusee just messed up my understanding of it all since i hardly update them often. So thanks again for all your patience!!

 

[urherenow]

apparently not. I also just realised this, based on the other comments
but having tesla is a nice addition, such as the ability to use emuiibo in supported games can only be used with tesla GUI.

Post automatically merged: Jun 20, 2024

well. the game that I tested, sometimes doesn't work. at first, I tried everything seems fine. but some other time, I tried to start the game, it shows game corrupted error. I only tested 2 games, I didn't bother to test all games, but at least for me, it seems the modified fusee.bin not working properly. with sys-patch, it's quite straightforward and all games, including XCI dump all works fine again.

If sys-patch works, but modified fusee.bin doesn’t, then you’re missing the latest sigpatches. Or the sigpatches you have are just plain wrong. But it would be very strange for them to work on some games but not others… the sigpatches are per-Atmosphere and Firmware version, not whatever firmware version the game was made for. 1 game works, they should all work. Unless you’re not actually on the latest firmware and didn’t convert the game to standard crypto during install (in which case it seems fusee should work anyway, but not hekate).

 

[GDT]

I think you are using the wrong version of Hekate. The same happened to me a few pages ago.

Go here:
https://gbatemp.net/threads/sigpatc...kate-fss0-fusee-package3.571543/post-10438484

And then keep reading my next messages. Hope this helps.

I'm using the latest version of Hekate and Atmosphere, the ones you posted.

 

[arabtm]

If sys-patch works, but modified fusee.bin doesn’t, then you’re missing the latest sigpatches. Or the sigpatches you have are just plain wrong. But it would be very strange for them to work on some games but not others… the sigpatches are per-Atmosphere and Firmware version, not whatever firmware version the game was made for. 1 game works, they should all work. Unless you’re not actually on the latest firmware and didn’t convert the game to standard crypto during install (in which case it seems fusee should work anyway, but not hekate).

yes, perhaps.

I really didn't bother to investigate that much. All I remember was that I use the sigpatches from the 1st post, atmosphere 1.7.1 and firmware 18.0.0. maybe the firmware that is wrong? it should be firmware 18.1.0? when I was doing the upgrade, firmware 18.1.0 was not available in the usual place, so I just use 18.0.0 which was available at that time.

I always thought that sigpatches + latest atmosphere is backward compatible with old firmware.

then I tried to replace the sigpatches with the one that was released when firmware 18.0.0 was released and atmosphere 1.7.0, yet I still got the same result.

usually, I never experienced this problem with sigpatches, fusee.bin etc, and I've been doing this since atmosphere was released. so, I'm still not sure what did I miss. but again, maybe I did something wrong, but at least for me the sys-patches method works

 

[urherenow]

Every BUILD of Atmosphere needs different patches. Even if you build your own, using the latest source, it will need different sigpatches than the official release. The bundle has all of them (for OFFICIAL releases/builds... build your own Atmosphere, then you need to use sys-patch, or make your own patches for your build), so the latest should always work no matter which version you're using, as long as you're using a modified fusee.bin, or loading package3 with hekate. Atmosphere + Hekate versions should match up though, or there will be dragons...

 

[H4X0R46]

I noticed new patches got posted to sigma, there's no mention of needing to boot with package3 or a modified fusee.bin, but I'm gonna assume those patches still need one of the above?

 

[impeeza]

I noticed new patches got posted to sigma, there's no mention of needing to boot with package3 or a modified fusee.bin, but I'm gonna assume those patches still need one of the above?

that set of patches got updated to FW 18.1.0 recently. and they included SYS-PATCH inside the sigpatches zip file. that's the only change

Post automatically merged: Monday at 2:17 AM

sadly the version of SYS-Patch included on the kities sigpatches is a old one ;(

 

[H4X0R46]

that set of patches got updated to FW 18.1.0 recently. and they included SYS-PATCH inside the sigpatches zip file. that's the only change

Post automatically merged: Monday at 2:17 AM

sadly the version of SYS-Patch included on the kities sigpatches is a old one ;(

Oh.... Well correct me if I'm wrong here, but I thought that if you have a working build of sys-patch, then there's zero reason to even need sigpatches right? Or no?

 

[RedColoredStars]

Oh.... Well correct me if I'm wrong here, but I thought that if you have a working build of sys-patch, then there's zero reason to even need sigpatches right? Or no?

I do not use sigpatches whatsoever. They aren't even on my card and I removed the sigpatch line from my hekate_ipl,ini. Only sys-patch and everything works fine.