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

  • Thread starter Thread starter ShadowOne333
  • Start date Start date
  • Views Views 5,304,285
  • Replies Replies 7,368
  • Likes Likes 266
I think FW 18.1.0 brings more problems than expected. I am having serious problems when booting with Hekate. I am also having problems when using sigpatches. I think I'm going back to 18.0.1 until all these issues are solved.

The only thing that seems to work properly in FW 18.1.0 is booting from latest version of fusee.bin and using sys-patch_1.5.1_patched.
 
I think FW 18.1.0 brings more problems than expected. I am having serious problems when booting with Hekate. I am also having problems when using sigpatches. I think I'm going back to 18.0.1 until all these issues are solved.

The only thing that seems to work properly in FW 18.1.0 is booting from latest version of fusee.bin and using sys-patch_1.5.1_patched.
yes you must no upgrade your fimware until all loaders/sysmodules/homebrew get updated
 
noob question here, sorry in advance: if the sys-patch module solution works, why are people going through the hassle of making, releasing and using patched versions of atmosphere bring back support of syspatches? Is there a tradeoff of some sort using one instead of the other?
 
noob question here, sorry in advance: if the sys-patch module solution works, why are people going through the hassle of making, releasing and using patched versions of atmosphere bring back support of syspatches? Is there a tradeoff of some sort using one instead of the other?
It's a matter of taste, some people like peanut butter and Jelly and other jelly and peanut jelly, others only jelly or only peanut butter...

Sigpatches and SYS-Patch are two ways to do the same but also are complementary so is up to you.
 
  • Like
Reactions: Blythe93
noob question here, sorry in advance: if the sys-patch module solution works, why are people going through the hassle of making, releasing and using patched versions of atmosphere bring back support of syspatches? Is there a tradeoff of some sort using one instead of the other?
There are another kip patches, not only sigpatches...
 
  • Love
Reactions: impeeza
The version displayed on the NRO and Overlay ha ha ha ha, just for remove the -dirty tag, my OCD was killing me.
Thanks for explaining

Here they are, Atmosphère with FS patches re enabled and the correspondent sigpatches.
So is this an alternative to the patched fusee.bin? An alternative way of re-enabling kip patches?
Sorry I am a little confused :)
 
  • Like
Reactions: Blythe93
The only way to load FS KIP patches at boot are:
  • If you inject fusee.bin as your payload, Modifying the atmosphère code to reenable that and build a new version.
  • Using Hekate's FSS0 package 3 loading method.
period.
Sorry for my noob questions. Is it fusee.bin that needs to be modified or Atmosphere modules themselves? I was under the impression that fusee.bin should be modified to enable FS KIP patches but your released a modified Atmosohere package so now I am not sure anymore :)

Thank you for your patience with my questions
 
Sorry for my noob questions. Is it fusee.bin that needs to be modified or Atmosphere modules themselves? I was under the impression that fusee.bin should be modified to enable FS KIP patches but your released a modified Atmosohere package so now I am not sure anymore :)

Thank you for your patience with my questions
I made a full built of atmosphère the only change on the code was reenable fusee FS KIP loading, so you can use only the fusee.bin or all the set including the sigpatches.

the package 3 is different even using the same code 1 minute after to build a new batch.
 
  • Like
Reactions: petspeed

Site & Scene News

Popular threads in this forum