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

[Blythe93]

Witaj, jeśli chcesz, aby Nintendo zmieniło oprogramowanie 20.0.1 i nie działa w mojej atmosferze.
co mogę zrobić, czekać na najnowsze cfw czy istnieje inny sposób.
Pozdrawiam

If I understood you correctly, just get the latest Atmosphere, Hekate and sys-patch and reboot. Do not downgrade as you might run into even more issues.

 

[rowletbrad]

Hi guys, sorry if the question has already been answered, but I couldn't find anything, I'm new to the forum.
I installed a couple of roms with dbi, and nothing opened, so I learned that I had to install sigpatches, and I installed the newest version, that I found on the OP. However there are still a couple of games/dlcs that dbi installs with the warning "SIGNATURE:invalid", and then the game does not start. Do you guys know by any chance the fix to this? Thanks in advance.

 

[impeeza]

Hi guys, sorry if the question has already been answered, but I couldn't find anything, I'm new to the forum.
I installed a couple of roms with dbi, and nothing opened, so I learned that I had to install sigpatches, and I installed the newest version, that I found on the OP. However there are still a couple of games/dlcs that dbi installs with the warning "SIGNATURE:invalid", and then the game does not start. Do you guys know by any chance the fix to this? Thanks in advance.

as always read before act, install SYS-Patch as stated on the OP.

 

[Blythe93]

However there are still a couple of games/dlcs that dbi installs with the warning "SIGNATURE:invalid", and then the game does not start.

Corrupted, incomplete downloads? Can you check whether the files are original, modified or corrupted with NxFileViewer?

 

[johnliu]

First install atmosphere v1.9.0, hekate v6.3.0 and the latest v1 sig patch here.
Then upgrade the horizon from v19.0.1 to v20.0.1 in sysMMC via WIFI officially.
After that, use the Tegra explorer to get the firmware v20.0.1 from sysMMC
and upgrade the firmware from v19.0.1 to v20.0.1 with daybreak.
2 switch OLED+ a switch lite works.
However they all become hot after charging.
There is no such problem before.
How to solve it?

I have searched online that the hot charging problem occured in many previous firmware upgrade too.
But for me, there is no such problem before.
Their suggestions include switching off the wifi by using flight mode and switch off the console.
However, I have tested them and they did not work.
I have set something in hekate_ipl.ini that it will keep on switching off after charging.
I saw it auto switched on and then off after plugging in the charing cable.
However, in the next day I found it is hot and still in sleep mode instead of switched off.

 

[OrGoN3]

First install atmosphere v1.9.0, hekate v6.3.0 and the latest v1 sig patch here.
Then upgrade the horizon from v19.0.1 to v20.0.1 in sysMMC via WIFI officially.
After that, use the Tegra explorer to get the firmware v20.0.1 from sysMMC
and upgrade the firmware from v19.0.1 to v20.0.1 with daybreak.
2 switch OLED+ a switch lite works.
However they all become hot after charging.
There is no such problem before.
How to solve it?

I have searched online that the hot charging problem occured in many previous firmware upgrade too.
But for me, there is no such problem before.
Their suggestions include switching off the wifi by using airplane mode and switch off the console.
However, I have tested them and they did not work.
I have set something in hekate_ipl.ini that it will keep on switching off after charging.
I saw it auto switched on and then off after plugging in the charing cable.
However, in the next day I found it is hot and still in sleep mode instead of switched off.

If they're still very hot while charging, you have options. If upgrading to 20.x.x didn't work, back up everything on your emummc and create a new one.

Your only other option is to disable WiFi ( airplane/flight mode) while the console is sleeping.

 

[BasedKiliK]

Hello. I recently updated my SysNAND to 20.0.1 but left the EmuNAND on 19.0.1, but after this I'm unable to boot any of my games on emunand despite changing nothing on that side. I updated Atmosphere + Hekate and attempted install both the latest sigpatches + sys-patch, and no change; still get the error "Unable to start software" for 90% of my installed titles.

I've also cleared out everything and tried only using sys-patch; still no change. What is going on or what did I do wrong? Is there something specific I'm missing?

 

[Blythe93]

I've also cleared out everything and tried only using sys-patch; still no change. What is going on or what did I do wrong? Is there something specific I'm missing?

What does the sys-patch log say? There were some changes introduced in firmware 20.0.0 that broke a thing or two, I wonder if reverting back Atmosphere to 1.8.0 since you're still on 19.0.1 on your emuNAND would help make games work on emuNAND. Latest sys-patch should work without issue, though, but in case it doesn't, try this one instead. Just guesswork on my end, anyway.

 

[impeeza]

ND. Latest sys-patch should work without issue, though, but in case it doesn't, try this one instead. Just guesswork on my end, anyway.

Hello there, There are no difference between the codes, they are the same.

 

[Blythe93]

Hello there, There are no difference between the codes, they are the same.

Just in case you've missed, I've linked your v1.5.5 which came before your v1.5.6? It's the version that was created before 20.0.0 came out.
bth didn't change the version number when he updated his sys-patch release so his 1.5.6 should be the same as your 1.5.6, as you said.

Still, as far as I know, sys-patch should be backwards compatible? As long as you're on Atmosphere 1.8.0 or newer.

 

[impeeza]

Just in case you've missed, I've linked your v1.5.5 which came before your v1.5.6? It's the version that was created before 20.0.0 came out.
bth didn't change the version number when he updated his sys-patch release so his 1.5.6 should be the same as your 1.5.6, as you said.

Still, as far as I know, sys-patch should be backwards compatible? As long as you're on Atmosphere 1.8.0 or newer.

sorry I didn't get was the later version,

 

[BasedKiliK]

What does the sys-patch log say? There were some changes introduced in firmware 20.0.0 that broke a thing or two, I wonder if reverting back Atmosphere to 1.8.0 since you're still on 19.0.1 on your emuNAND would help make games work on emuNAND. Latest sys-patch should work without issue, though, but in case it doesn't, try this one instead. Just guesswork on my end, anyway.

[fs]
noacidsigchk1=Skipped
noacidsigchk2=Skipped
noncasigchk_old=Disabled
noncasigchk_new=Skipped
nocntchk=Unpatched
nocntchk2=Skipped
[ldr]
noacidsigchk=Patched (file)
[es]
es1=Skipped
es2=Skipped
es3=Patched (file)
[nifm]
ctest=Patched (sys-patch)
ctest2=Skipped
[nim]
nim=Skipped
[ssl]
disablecaverification1=Disabled
disablecaverification2=Disabled
disablecaverification3=Disabled
[stats]
version=1.5.6-2ca9ba8
build_date=05.05.2025 06:31:16
fw_version=16.1.0
ams_version=1.9.0
ams_target_version=1.0.0
ams_keygen=19
ams_hash=1d3f3c6e
is_emummc=1
heap_size=4096
buffer_size=4096
patch_time=0.098s

I actually reverted to a previous 16.1.0 backup as there was very little difference between my current one, and my games are affected the same way.

I found out that any titles installed directly on the emunand "eMMC" instead of the SD card do play. All others on the SD now read as 0 byes in DBI. And redumping directly from my game cards to the SD, now results in an error.

 

[johnliu]

If they're still very hot while charging, you have options. If upgrading to 20.x.x didn't work, back up everything on your emummc and create a new one.

Your only other option is to disable WiFi ( airplane/flight mode) while the console is sleeping.

Disable wifi by flight mode, Switch will also get hot while charging.
I perfer fixing the issue instead of building everything from the beginning since it takes a long time to do so due to the slow transferring speed.

 

[BasedKiliK]

Have your updated your emuNAND to horizon v20.0.1 by
daybreak yet?

I did before I loaded up an emunand backup, it had made no difference.

It seems the atmosphere update broke all games installed on the SD. I had to clear out the emunand's Nintendo folder and delete the tickets, and then reinstall for the games to work again.

 

[burhansalih]

Atmosphere does not break anything... people's misunderstanding breaks things....oh and OFW lol

 

[OrGoN3]

Have your updated your emuNAND to horizon v20.0.1 by daybreak yet?

Post automatically merged: May 19, 2025

Disable wifi by flight mode, Switch will also get hot while charging.
I perfer fixing the issue instead of building everything from the beginning as the slow speed takes a long time to do so.

As do I. I thought they said they updated to 20 but the issue persisted. If that was the case, then according to the issue thread about it on the Atmosphere GitHub, they'd need to recreate their emummc.

 

[Blythe93]

[fs]
noacidsigchk1=Skipped
noacidsigchk2=Skipped
noncasigchk_old=Disabled
noncasigchk_new=Skipped
nocntchk=Unpatched
nocntchk2=Skipped
[ldr]
noacidsigchk=Patched (file)
[es]
es1=Skipped
es2=Skipped
es3=Patched (file)
[nifm]
ctest=Patched (sys-patch)
ctest2=Skipped
[nim]
nim=Skipped
[ssl]
disablecaverification1=Disabled
disablecaverification2=Disabled
disablecaverification3=Disabled
[stats]
version=1.5.6-2ca9ba8
build_date=05.05.2025 06:31:16
fw_version=16.1.0
ams_version=1.9.0
ams_target_version=1.0.0
ams_keygen=19
ams_hash=1d3f3c6e
is_emummc=1
heap_size=4096
buffer_size=4096
patch_time=0.098s

Additionally, I have these marked as patched as well:

• noncasigchk_new
• nocntchk2
• ctest2 instead of ctest
• disablecaverification1, disablecaverification2 and disablecaverification3

Not sure if that would make a difference?

Spoiler: My sys-patch log.ini

[fs]
noacidsigchk1=Skipped
noacidsigchk2=Skipped
noncasigchk_old=Skipped
noncasigchk_new=Patched (sys-patch)
nocntchk=Skipped
nocntchk2=Patched (sys-patch)
[ldr]
noacidsigchk=Patched (sys-patch)
[es]
es1=Skipped
es2=Skipped
es3=Patched (sys-patch)
[nifm]
ctest=Skipped
ctest2=Patched (sys-patch)
[nim]
nim=Patched (sys-patch)
[ssl]
disablecaverification1=Patched (sys-patch)
disablecaverification2=Patched (sys-patch)
disablecaverification3=Patched (sys-patch)
[stats]
version=1.5.6-d0f5451
build_date=05.05.2025 05:38:37
fw_version=20.0.1
ams_version=1.9.0
ams_target_version=0.1.0
ams_keygen=19
ams_hash=1d3f3c6e
is_emummc=1
heap_size=4096
buffer_size=4096
patch_time=0.089s

I had to clear out the emunand's Nintendo folder and delete the tickets, and then reinstall for the games to work again.

Ah, good. Well, at least you've got them working again.

 

[bth]

Additionally, I have these marked as patched as well:

• noncasigchk_new
• nocntchk2
• ctest2 instead of ctest
• disablecaverification1, disablecaverification2 and disablecaverification3

disable_ca_verification patches are only needed for people who normally for whatever reason force ssl comunication to be http and mitm it (communication with nintendo), if you have ctest patch running you don't need those ones enabled, they are disabled by default for a reason.

ctest2 instead of ctest to make new version backwards compatible with old method/older versions


which are marked as unpatched and which are marked as patched depends on firmware versions, if the user is loading in patches from hekate ("nosigchk"), or by .ips file, as at some point those started conflicting with sys-patch.

with no other patches present sys-patch should work down to at least 10.0.0 (last i checked anyway)

 

[Blythe93]

disable_ca_verification patches are only needed for people who normally for whatever reason force ssl comunication to be http and mitm it (communication with nintendo), if you have ctest patch running you don't need those ones enabled, they are disabled by default for a reason.

ctest2 instead of ctest to make new version backwards compatible with old method/older versions


which are marked as unpatched and which are marked as patched depends on firmware versions, if the user is loading in patches from hekate ("nosigchk"), or by .ips file, as at some point those started conflicting with sys-patch.

with no other patches present sys-patch should work down to at least 10.0.0 (last i checked anyway)

Thanks for the detailed reply!

 

[DanD7755]

Hey, I was wondering if someone could help if they have had the same issue. I upgraded to 20.0.1 by mistake after taking a year or so out of using cfw on the sitch. I have tried to install a few NSP files and most of them work. I am however having issues with some that keep showing the same error "software closed because a problem occoured".

Mainly on newer pokemon games

Edit* also on some DLC for older games

I have a fresh install of the Atmoshpere and have reinstalled the new sigpatches and the syspatch.

Has anyone had the same issue or got any advise.

Thanks in advance