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

  • Thread starter Thread starter ShadowOne333
  • Start date Start date
  • Views Views 5,317,311
  • Replies Replies 7,368
  • Likes Likes 266
Hi everyone!

For your information, I've updated to Atmosphere 1.10.2 and Hekate v6.5.0, and no games will launch with v1.5.9.

To say they're necessary would be an exaggeration. I'm just warning you that they don't work.
I can wait.

You seem to have a misconception going on...

the patches for 21.2.0 and atmosphere 1.10.2 aren't wrong, or whats the issue. (sys-patch 1.5.9 is valid for both)

You having booted without the ES patch, just a single time, is enough to invalidate your tickets.
(adding patches after having done that, wont make your games magically work again.)
You have to reinstall your games.




anyway i will entertain you, here you go, here's your patches (generated just now)


Code:
→ Created 194 Atmosphere .ips patches

Generating Hekate patches/bootloader\patches.ini...
   Processing patch_database/fs_kip_patches.txt...
      Added 68 FS sections
   Processing patch_database/ldr_kip_patches.txt...
      Added 7 Loader sections

Done! Generated patches/bootloader\patches.ini with 75 patch sections and blank lines between entries.
Detected highest supported firmware: 21.2.0 (from latest Loader patch)

Created archive: Hekate+AMS-package3-sigpatches-1.10.2-cfw-21.2.0.zip


 

Attachments

Last edited by bth,
A doubt I always had but never bothered on looking about.

What happens if you update the sigpatches but not HOS and Atmos? Or if you only update Atmos but not HOS? Weird how I've working on the scene for 5 years without looking at this.
 
A doubt I always had but never bothered on looking about.

What happens if you update the sigpatches but not HOS and Atmos? Or if you only update Atmos but not HOS? Weird how I've working on the scene for 5 years without looking at this.
Nothing happens in either case.
 
  • Like
Reactions: LeyendaV
My issue currently is I can boot SysMMC Semi Stock and EMUMMC by not my SYSMMC CFW. Which is annoying as I use it for save file transfers to switch 2 from cfw.

Edit: fixed it!
 
Last edited by UtsuNova2801,
You seem to have a misconception going on...

the patches for 21.2.0 and atmosphere 1.10.2 aren't wrong, or whats the issue. (sys-patch 1.5.9 is valid for both)

You having booted without the ES patch, just a single time, is enough to invalidate your tickets.
(adding patches after having done that, wont make your games magically work again.)
You have to reinstall your games.




anyway i will entertain you, here you go, here's your patches (generated just now)


Code:
→ Created 194 Atmosphere .ips patches

Generating Hekate patches/bootloader\patches.ini...
   Processing patch_database/fs_kip_patches.txt...
      Added 68 FS sections
   Processing patch_database/ldr_kip_patches.txt...
      Added 7 Loader sections

Done! Generated patches/bootloader\patches.ini with 75 patch sections and blank lines between entries.
Detected highest supported firmware: 21.2.0 (from latest Loader patch)

Created archive: Hekate+AMS-package3-sigpatches-1.10.2-cfw-21.2.0.zip



I updated my firmware to 21.2.0 without knowing the sigpatches/syspatches were out. Naturally it did not boot. Later today I updated hekate to 6.5.0 and atmosphere to 1.10.2 but were missing the patches still. Then I installed these but my games still do not launch after installing them. Do I have to reinstall everything?
 
I updated my firmware to 21.2.0 without knowing the sigpatches/syspatches were out. Naturally it did not boot. Later today I updated hekate to 6.5.0 and atmosphere to 1.10.2 but were missing the patches still. Then I installed these but my games still do not launch after installing them. Do I have to reinstall everything?
Install sys-patch sysmodule
 
  • Like
Reactions: BigOnYa
Install sys-patch sysmodule
I did but I am still not able to launch any games. I'm getting this error "the software was closed because an error occurred". Also, whenever I try to launch DBI and press browse, my atmosphere crashes due to "010000000000000D" app eventhough I deleted that folder. Should I just delete everything and downgrade atp?
 
I did but I am still not able to launch any games. I'm getting this error "the software was closed because an error occurred". Also, whenever I try to launch DBI and press browse, my atmosphere crashes due to "010000000000000D" app eventhough I deleted that folder. Should I just delete everything and downgrade atp?
 
Hi all,

Running 21.2.0 updated by the system update tool.

I have updated everything as directed, Atmos/Hekate/Sigs etc. However when I try to boot into emummc it just hangs on the hekate splash screen. Ive tried reformatting and starting from scratch. Still the same. Any ideas please?

Edit: Also I have noticed that When I try to see my sd card via Hekate it no longer pops up on my computer. It shows as Status: Started UMS. You cannot eject either as the "close" button is greyed out. Works fine in an sd reader.

Edit 2: It boots into cfw sysnand no issues, and sd card can be seen on pc using the usb app.
 
Last edited by Demon1982,
I updated everything but I get a black screen trying to boot into Cfw-sysnand through Hekate. NVM, had to manually boot into the fusee.bin and it works.
 
Last edited by Fox420,
Hi all,

Running 21.2.0 updated by the system update tool.

I have updated everything as directed, Atmos/Hekate/Sigs etc. However when I try to boot into emummc it just hangs on the hekate splash screen. Ive tried reformatting and starting from scratch. Still the same. Any ideas please?

Edit: Also I have noticed that When I try to see my sd card via Hekate it no longer pops up on my computer. It shows as Status: Started UMS. You cannot eject either as the "close" button is greyed out. Works fine in an sd reader.

Edit 2: It boots into cfw sysnand no issues, and sd card can be seen on pc using the usb app.
Same issue here. Booting into emummc it hangs on splash screen indefinitely
 
Last edited by josete2k,
  • Like
Reactions: Blythe93
Last edited by Chaoticmewmew,
Could you explain more please? A lot of us are hanging at the splash screen when choosing emummc. Is this similar to what you had? What do you mean by booting manually into fusee.bin.
I updated everything but I get a black screen trying to boot into Cfw-sysnand through Hekate. NVM, had to manually boot into the fusee.bin and it works.
 

Site & Scene News

Popular threads in this forum