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

[Hayato213]

I've uninstalled the game, reinstalled, used JKSV to remove save data. Nothing works. In addition, some NROs are crashing on me too.

Check to see what sysmodules are running pokémon game refuse to run when there is lack of system memory.

 

[SoraNoize]

Check to see what sysmodules are running pokémon game refuse to run when there is lack of system memory.

Thanks for the great advice guys. I found out the problem. It's a corrupted save data and my JKSV nro was corrupted or something. I redownloaded the NRO and deleted the save data and I'm good now. I'm gonna painstakingly redownload my NROs again manually cos the HB shop keeps telling me it can't connect to the internet.

Again, thanks everyone!

 

[sergilun]

Hey guys, thanks for all your work. I have some doubts from the sigpatches for latest atmosphere. From the sigpatches post, it says that they are updated for firmware 21.2.0 but not for atmosphere 1.10.2. But atmosphere 1.10.2 is the one for firmware 21.2.0. So if I update firmware to 21.2.0 and atmosphere 1.10.2, will the sigpatches from this thread work, or do I need to use sys patch instead?

 

[bth]

Hey guys, thanks for all your work. I have some doubts from the sigpatches for latest atmosphere. From the sigpatches post, it says that they are updated for firmware 21.2.0 but not for atmosphere 1.10.2. But atmosphere 1.10.2 is the one for firmware 21.2.0. So if I update firmware to 21.2.0 and atmosphere 1.10.2, will the sigpatches from this thread work, or do I need to use sys patch instead?

sys-patch will do the job without you needing to go grab a new .zip every time atmosphere updates.
in some events, you might have to fetch a new version of sys-patch when a new firmware version releases, but not always.

you will always have to fetch new sigpatches for firmware version changes.

that's the main difference basically is this:

atmosphere related patches = sys-patch does without needing to update sys-patch
firmware related patches = sys-patch can in theory continue without updates assuming nintendo didn't change too much stuff
sigpatches specifically, not sys-patch, for both = always requires to update, for both atmosphere versions and firmware versions
5 versions of atmosphere, 1 firmware version? you need new sigpatches for those 5 versions of atmosphere, indepedently, if you update atmosphere those 5 times. sys-patch wont need that at all.

 

[sergilun]

sys-patch will do the job without you needing to go grab a new .zip every time atmosphere updates.
in some events, you might have to fetch a new version of sys-patch when a new firmware version releases, but not always.

you will always have to fetch new sigpatches for firmware version changes.

that's the main difference basically is this:

atmosphere related patches = sys-patch does without needing to update sys-patch
firmware related patches = sys-patch can in theory continue without updates assuming nintendo didn't change too much stuff
sigpatches specifically, not sys-patch, for both = always requires to update, for both atmosphere versions and firmware versions
5 versions of atmosphere, 1 firmware version? you need new sigpatches for those 5 versions of atmosphere, indepedently, if you update atmosphere those 5 times. sys-patch wont need that at all.

Hi, thanks for the answer. I understand sys patch will work and is probably a better option. But I have always used sigpatches, and since 1.10.2 will probably be the last atmosphere release at least for the time being, I just want to know if the latest sigpatches work on that atm version so that I don't need to mess with sys-patch

 

[bth]

Hi, thanks for the answer. I understand sys patch will work and is probably a better option. But I have always used sigpatches, and since 1.10.2 will probably be the last atmosphere release at least for the time being, I just want to know if the latest sigpatches work on that atm version so that I don't need to mess with sys-patch

Just because scires has announced he intends to retire, does not mean there aren't more members contributing to atmosphere, which is an open source project.

myself am fully capable of pushing out enum, key source update and emummc/nogc patches within less than a day of any firmware update.

just because scires has done all of that by himself, does not mean others cannot do it too.

 

[LloydFowler]

Hello guys, what would you say is the most stable CFW version to play Legends Z-A?

 

[RRuinous]

tinfoil isn't supported on atmosphere 1.10 yet.

(your firmware version is unrelated as to tinfoil being supported or not, it's atmosphere 1.10 that is the problem)

the correct combination is atmosphere 1.9.5, sys-patch 1.5.6 and firmware version 20.5.0 max

Would you recommend to downgrade atmosphere 1.10.2 and sys patch 1.5.9 to atmosphere 1.9.5 and sys patch 1.5.6? I do not know the process of downgrading AMS and whether it is different than downgrading FW so I'm curious if it's "risky"

Oh yeah if you can, could u link the sys patch 1.5.6 on this forum? thanks

 

[bth]

Would you recommend to downgrade atmosphere 1.10.2 and sys patch 1.5.9 to atmosphere 1.9.5 and sys patch 1.5.6? I do not know the process of downgrading AMS and whether it is different than downgrading FW so I'm curious if it's "risky"

Oh yeah if you can, could u link the sys patch 1.5.6 on this forum? thanks

you put the files on your sd card and overwrite when asked, just like when you "upgrade".

the only addition for when you downgrade firmware (not atmosphere, just the firmware) is having to run that kind of payload https://github.com/sthetix/DowngradeFixer/releases/tag/1.0.0 afterward to make the console/emummc boot again

you also can just google search any of the keywords, such as "sys-patch 1.5.6", and it would take you to that https://gbatemp.net/download/sys-patch-sysmodule.39124/

 

[Xmortal]

After updating the Hekate and Atmosphere files from their duplicate GitHub repository, and then applying the official update to SysMMC 21.2.0, when I open SysCFW I get a "nosigchk" error message, even with the sigpatch file from this thread. Even so, I only use SysCFW in airplane mode to back up my game save files, and some games that I later transfer to EmuMMC to add cheats.

 

[bth]

After updating the Hekate and Atmosphere files from their duplicate GitHub repository, and then applying the official update to SysMMC 21.2.0, when I open SysCFW I get a "nosigchk" error message, even with the sigpatch file from this thread. Even so, I only use SysCFW in airplane mode to back up my game save files, and some games that I later transfer to EmuMMC to add cheats.

that means the patches.ini provided doesn't have the entries for the FS 21.2.0 has from whatever sigpatch file you used.

try this, if the issue is gone then the file you grabbed was just out of date

if it still says nosigchk error, then that'd be weird.

(i just generated that)

#FS 21.0.0-FAT32 - SDKVersion: 21.4.0.0
[FS:EE4B3012A6840225]
.nosigchk=0:0x026960:0x4:00090036,1F2003D5
.nosigchk=0:0x07FA88:0x4:128C0394,E0031F2A

#FS 21.0.0-EXFAT - SDKVersion: 21.4.0.0
[FS:6E2BD9BAA3B910F1]
.nosigchk=0:0x026960:0x4:00090036,1F2003D5
.nosigchk=0:0x07FA88:0x4:6AB80394,E0031F2A

#FS 21.2.0-FAT32 - SDKVersion: 21.4.0.0
[FS:AF1DBDC782983CBD]
.nosigchk=0:0x026960:0x4:00090036,1F2003D5
.nosigchk=0:0x07FA88:0x4:128C0394,E0031F2A

#FS 21.2.0-EXFAT - SDKVersion: 21.4.0.0
[FS:562517A192C3C8F0]
.nosigchk=0:0x026960:0x4:00090036,1F2003D5
.nosigchk=0:0x07FA88:0x4:6AB80394,E0031F2A

#loader Atmosphere-1.10.2-master-eb34f9789 (fw: 21.2.0)
[LOADER:213B2B2A183241EC]
.nosigchk=0:0x005F78:0x4:1F00016B,1F00006B

 

[Xmortal]

that means the patches.ini provided doesn't have the entries for the FS 21.2.0 has from whatever sigpatch file you used.

try this, if the issue is gone then the file you grabbed was just out of date

if it still says nosigchk error, then that'd be weird.

(i just generated that)

#FS 21.0.0-FAT32 - SDKVersion: 21.4.0.0
[FS:EE4B3012A6840225]
.nosigchk=0:0x026960:0x4:00090036,1F2003D5
.nosigchk=0:0x07FA88:0x4:128C0394,E0031F2A

#FS 21.0.0-EXFAT - SDKVersion: 21.4.0.0
[FS:6E2BD9BAA3B910F1]
.nosigchk=0:0x026960:0x4:00090036,1F2003D5
.nosigchk=0:0x07FA88:0x4:6AB80394,E0031F2A

#FS 21.2.0-FAT32 - SDKVersion: 21.4.0.0
[FS:AF1DBDC782983CBD]
.nosigchk=0:0x026960:0x4:00090036,1F2003D5
.nosigchk=0:0x07FA88:0x4:128C0394,E0031F2A

#FS 21.2.0-EXFAT - SDKVersion: 21.4.0.0
[FS:562517A192C3C8F0]
.nosigchk=0:0x026960:0x4:00090036,1F2003D5
.nosigchk=0:0x07FA88:0x4:6AB80394,E0031F2A

#loader Atmosphere-1.10.2-master-eb34f9789 (fw: 21.2.0)
[LOADER:213B2B2A183241EC]
.nosigchk=0:0x005F78:0x4:1F00016B,1F00006B

Before writing my previous message, I updated the exam with the file from post number 5494 and it still has the error.

 

[bth]

Before writing my previous message, I updated the exam with the file from post number 5494 and it still has the error.

if the one from the post you just replied to also says nosigchk error, then the only thing i can think of is you not putting the folders on sd card correctly after unzipping the sigpatch zip archive.

that or symptomatic of macosx/linux/android user needing archive bit fix in hekate, or, if neither of that, sd card corruption/sd card reader problem

 

[Sukalibur]

Deleted

 

[Xmortal]

if the one from the post you just replied to also says nosigchk error, then the only thing i can think of is you not putting the folders on sd card correctly after unzipping the sigpatch zip archive.

that or symptomatic of macosx/linux/android user needing archive bit fix in hekate, or, if neither of that, sd card corruption/sd card reader problem

Using your file and booting SysCFW completely bricked my Switch Lite. It used to work fine and the memory card was good. Now it won't turn on.

 

[Hayato213]

Using your file and booting SysCFW completely bricked my Switch Lite. It used to work fine and the memory card was good. Now it won't turn on.

Not sure what you did , but what he provided shouldn't brick switch, as they are just patches.

 

[bth]

Using your file and booting SysCFW completely bricked my Switch Lite. It used to work fine and the memory card was good. Now it won't turn on.

That sounds very funny to me, but no, that's completely unrelated.

 

[Xmortal]

That sounds very funny to me, but no, that's completely unrelated.

Your file has a problem; I just copied, pasted, and replaced it. When loading the emuMMC, after the Atmosphere logo, the screen stays black, and then Hekate doesn't start.

 

[bth]

Your file has a problem; I just copied, pasted, and replaced it. When loading the emuMMC, after the Atmosphere logo, the screen stays black, and then Hekate doesn't start.

There's zero file in the archive i attatched to that post which is able of doing that.

it's just patches.ini (which hekate uses) and .ips files for modified fusee.bin (kip_patches), and regular exefs_patches.

Your problem is entirely unrelated.

see my previous post (you more or less already were having symptoms before even touching "my file"):

if the one from the post you just replied to also says nosigchk error, then the only thing i can think of is you not putting the folders on sd card correctly after unzipping the sigpatch zip archive.

that or symptomatic of macosx/linux/android user needing archive bit fix in hekate, or, if neither of that, sd card corruption/sd card reader problem

 

[Xmortal]

There's zero file in the archive i attatched to that post which is able of doing that.

it's just patches.ini (which hekate uses) and .ips files for modified fusee.bin (kip_patches), and regular exefs_patches.

Your problem is entirely unrelated.

see my previous post (you more or less already were having symptoms before even touching "my file"):

It's your file because after copying my backup it started working again. I'm not doing anything different.