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

[Tyvar1]

How do you update to 19.0.1?

Post automatically merged: Jan 19, 2025

is Lockpick still working with latest 19.0.1? and How do I update to 19.0.1?

Follow this: https://gbatemp.net/threads/ultimate-guide-to-upgrade-your-firmware-atmosphere.661148/

Also latest lockpick:
https://gbatemp.net/threads/lockpick_rcm-payload-official-thread.532916/post-10564466

 

[KiiWii]

How do you update to 19.0.1?

Post automatically merged: Jan 19, 2025

is Lockpick still working with latest 19.0.1? and How do I update to 19.0.1?

I used daybreak and downloaded the update from darthsternies site IIRC.

 

[RedColoredStars]

I used daybreak and downloaded the update from darthsternies site IIRC.

No, you did not. That site doesn't have 19.0.1. (yes, I know what iirc means. Im just kidding around)

 

[FanNintendo]

I used daybreak and downloaded the update from darthsternies site IIRC.

i see only 19.0.0 missing 19.0.1

 

[KiiWii]

No, you did not. That site doesn't have 19.0.1.

Ah then it was THZoria

 

[FanNintendo]

I'd suggest getting the latest sys-patch v1.5.6 (v1.5.5 provided by impeeza is fine as well, just make sure to remove any previous config file for the sys-patch as it may have redundant entries). If you're using sigpatches only, I believe that you do need the kip1patch=nosigchk line in your hekate_ipl.ini. Regardless, I've been using sys-patch v1.5.6 without any issues so far.


You can follow this guide to update your setup. I'd suggest getting the latest sys-patch instead of sigpatches from now on, mainly because I've seen people having less issues with the sys-patch, sys-patch having less files to maintain than sigpatches and some extra features.


sys-patch v1.5.6 is currently the latest one, but it should be the same as the 1.5.5 with one exception which is the config clean-up on the first run, I believe. You don't need the sigpatches at all, you can safely remove them (just make sure to remove kip1patch=nosigchk line in your hekate_ipl.ini and you'll be good.

Im having problem now again I cannot open sys-patch menu like you mention hold L + down pad and R3 ? nothing happen. i updated to 18.0.0 latest amtosphere and hekate stay on 18.0.1 to make sure everything is ok before i go ahead update the firmware to 19.0.1. Im Re-reading all over from start 1st post. (sigh)

Post automatically merged: Jan 20, 2025

Im having problem now again I cannot open sys-patch menu like you mention hold L + down pad and R3 ? nothing happen. i updated to 18.0.0 latest amtosphere and hekate stay on 18.0.1 to make sure everything is ok before i go ahead update the firmware to 19.0.1. Im Re-reading all over from start 1st post. (sigh)

i installed 19.0.1 firmware seems no issues so far but sys-patch 1.5.6 wouldnt open telsa menu for sys-patch to check if its patched so i tried v1.5.5 sys-patch still same as v1.5.6

 

[Blythe93]

i installed 19.0.1 firmware seems no issues so far but sys-patch 1.5.6 wouldnt open telsa menu for sys-patch to check if its patched so i tried v1.5.5 sys-patch still same as v1.5.6

Do you have both Tesla menu and nx-ovlloader? Not having those could be the reason why you can't open sys-patch menu.

 

[FanNintendo]

Do you have both Tesla menu and nx-ovlloader? Not having those could be the reason why you can't open sys-patch menu.

Thanks for check on me and did not have nx-ovllloader. Now the Telsa Menu open up and all is patched green.

 

[Rizsparky]

I'm having the 2155-8007 error on any game I install now, using newest sigpatches in this thread, I'm still on firmware 16.0.1, any ideas?
[

 

[Blythe93]

I'm having the 2155-8007 error on any game I install now, using newest sigpatches in this thread, I'm still on firmware 16.0.1, any ideas?

Which Atmosphere are you on? For anything 1.7.0 or newer sigpatches won't work properly unless you boot into Atmosphere through Hekate (i.e. load Atmosphere's package3 via Hekate's FSS0) or if you use modified fusee.bin [1.7.0][1.7.1][1.8.0] with kip patches support restored.

 

[Rizsparky]

Which Atmosphere are you on? For anything 1.7.0 or newer sigpatches won't work properly unless you boot into Atmosphere through Hekate (i.e. load Atmosphere's package3 via Hekate's FSS0) or if you use modified fusee.bin [1.7.0][1.7.1][1.8.0] with kip patches support restored.

Im on the latest version, I decided to be brave and update firmware to 18.0.1 and that seemed to do the trick, thanks for your help really appreciate it.

 

[Blythe93]

Im on the latest version, I decided to be brave and update firmware to 18.0.1 and that seemed to do the trick, thanks for your help really appreciate it.

Glad you fixed it! If there's a bit more bravery in you, I'd say that it's pretty safe to update to 19.0.1 and switch to sys-patch as well. Working perfectly on my end since the update was released (I skipped the 19.0.0).

 

[zat3am]

Glad you fixed it! If there's a bit more bravery in you, I'd say that it's pretty safe to update to 19.0.1 and switch to sys-patch as well. Working perfectly on my end since the update was released (I skipped the 19.0.0).

hi, i skipped the 19.0.0 as well, but for some reason sys-patch (both 1.5.5 and 1.5.6) don't work on my end, all recent games/updates give out the corrupted data error (code 2002-4153).
i'm on 19.0.1 on both ofw and cfw with atmosphere 1.8.0.
but i don't see any fusee.bin on my root sd

could you please suggest what i can try next? i'm kinda new to the scene

 

[Blythe93]

hi, i skipped the 19.0.0 as well, but for some reason sys-patch (both 1.5.5 and 1.5.6) don't work on my end

Did you reboot your console after copying the sys-patch files?

all recent games/updates give out the corrupted data error (code 2002-4153)

That's a bit troublesome as it might be that the SD card got corrupted for some reason. I'd try reinstalling the problematic games with the latest DBI and see if that fixes the errors.

But, if that's not the case and unless someone else has a better idea, you'll probably need to remake your emuMMC from scratch. If you can backup your saves, do it as soon as possible just to be on a safe side (and copy them from your SD card to your PC as well).

In case you decide to go with the fresh emuMMC route, I'd highly recommend that you check your SD card for errors with the h2testw tool. If it happens to be a faulty SD card, I'd recommend getting a SanDisk Extreme SD card as it works flawlessly for me on two of my hacked Switches for two years now, no issues ever since.

 

[zat3am]

Did you reboot your console after copying the sys-patch files?

i did yes from hekate, rebooted onto cfw without problems, currently using sys-patch 1.5.6

That's a bit troublesome as it might be that the SD card got corrupted for some reason. I'd try reinstalling the problematic games with the latest DBI and see if that fixes the errors.

i had a slower sd card but wasn't corrupted, and now using a brand new 256 kingstone one which is working just fine with older games, tinfoil and all .nro applets; booting up is significantly faster too.

i'm pretty sure i'm missing something in the patches area, just tried with DBI 598 installing a recent update to a game that was working fine without the update and it has a transfer crc error in red, not quite sure what does that mean, and when i remove the update via tinfoil the base game works just fine.

But, if that's not the case and unless someone else has a better idea, you'll probably need to remake your emuMMC from scratch. If you can backup your saves, do it as soon as possible just to be on a safe side (and copy them from your SD card to your PC as well).

i did consider the fresh emuMMC route with HATS but i feel it'll be such a hassle somehow.
i do have basic backup of the working SD on my pc, just haven't started on the hekate emuMMC backup version yet.

 

[shadow256]

hi, i skipped the 19.0.0 as well, but for some reason sys-patch (both 1.5.5 and 1.5.6) don't work on my end, all recent games/updates give out the corrupted data error (code 2002-4153).
i'm on 19.0.1 on both ofw and cfw with atmosphere 1.8.0.
but i don't see any fusee.bin on my root sd

could you please suggest what i can try next? i'm kinda new to the scene

I've explained all most problems of sig_patches in this message:
https://gbatemp.net/threads/sigpatc...kate-fss0-fusee-package3.571543/post-10568595

If you've always some problems post the log of Sys-patch.

 

[The_Chaotician]

i did yes from hekate, rebooted onto cfw without problems, currently using sys-patch 1.5.6

i had a slower sd card but wasn't corrupted, and now using a brand new 256 kingstone one which is working just fine with older games, tinfoil and all .nro applets; booting up is significantly faster too.

i'm pretty sure i'm missing something in the patches area, just tried with DBI 598 installing a recent update to a game that was working fine without the update and it has a transfer crc error in red, not quite sure what does that mean, and when i remove the update via tinfoil the base game works just fine.


i did consider the fresh emuMMC route with HATS but i feel it'll be such a hassle somehow.
i do have basic backup of the working SD on my pc, just haven't started on the hekate emuMMC backup version yet.

Since you are using Hekate to boot, and sys-patch to apply sigpatches, the latter are now redundant. Suggest you remove the line "kip1patch=nosigchk" from your hekate_ipl.ini for your EmuNAND setup in case of a (rare) conflict, if its still there.

Also, I STRONGLY recommend not to use HATS packs for this purpose - you really have no idea what you are putting on to your SD card if you use these, as well as installing potentially redundant (or even harmful) homebrew for your purposes. Helps to keep to SD card free of clutter in case you need to troubleshoot again.

 

[zat3am]

I've explained all most problems of sig_patches in this message:

If you've always some problems post the log of Sys-patch.

Hello, thanks for replying and your suggestion, i've followed deleting and modifying the files you mentioned (everything is backed up so no worries if i messed up somehow) but the problem still is present, old games work fine, new stuff doesn't work (either corrupt data error or can't start software);

this is the current log:

and this was the old one before removing the sig-patch files but i think i already had the kip1patch from hekate_ipl removed:

it's kinda weird, i feel they should be reversed ?

i also attached few images for the toggles from Tesla menu, maybe i missed changing something basic or they do resonate somehow with applying the patches accordingly.

Post automatically merged: Jan 24, 2025

Also, I STRONGLY recommend not to use HATS packs for this purpose - you really have no idea what you are putting on to your SD card if you use these, as well as installing potentially redundant (or even harmful) homebrew for your purposes. Helps to keep to SD card free of clutter in case you need to troubleshoot again.

thank you for your suggestion, the problem still is present unfortunately,

right now i think my options are :

1- redo the update process from a previous backup again (my latest in cfw is 18.1.0) and i also have a fairly old one (cfw 16.x.x)
before i started updating with my beginner hands; maybe following the impeeza guide this time.

2 - try the fusee.bin method with sig-patch since it works for some people (but i'm not sure i quite understand what i should do for this option yet), i keep this switch offline on both ofw and cfw unless i need to update the stock system from normal settings.

3- start from scratch but i have no clue where to get the required files if the HATs pack is not trustworthy.

 

[shadow256]

Hello, thanks for replying and your suggestion, i've followed deleting and modifying the files you mentioned (everything is backed up so no worries if i messed up somehow) but the problem still is present, old games work fine, new stuff doesn't work (either corrupt data error or can't start software);

this is the current log:

View attachment 482283

and this was the old one before removing the sig-patch files but i think i already had the kip1patch from hekate_ipl removed:

View attachment 482284

it's kinda weird, i feel they should be reversed ?

i also attached few images for the toggles from Tesla menu, maybe i missed changing something basic or they do resonate somehow with applying the patches accordingly.

Post automatically merged: Jan 24, 2025

thank you for your suggestion, the problem still is present unfortunately,

right now i think my options are :

1- redo the update process from a previous backup again (my latest in cfw is 18.1.0) and i also have a fairly old one (cfw 16.x.x)
before i started updating with my beginner hands; maybe following the impeeza guide this time.

2 - try the fusee.bin method with sig-patch since it works for some people (but i'm not sure i quite understand what i should do for this option yet), i keep this switch offline on both ofw and cfw unless i need to update the stock system from normal settings.

3- start from scratch but i have no clue where to get the required files if the HATs pack is not trustworthy.

Post the log text, not a screenshot, for me screenshots have less fiability than text cause I need OCR to read them.

And as I say in my explication message if you have made the data verification proposed by the console and if it has failed one time you must completly reinstall the concerned content (base, update and eventual DLCs).

 

[zat3am]

Post the log text, not a screenshot, for me screenshots have less fiability than text cause I need OCR to read them.

And as I say in my explication message if you have made the data verification proposed by the console and if it has failed one time you must completly reinstall the concerned content (base, update and eventual DLCs).

here is the log file after reinstalling couple of the new games with that problem:

[clean_config_file]
result=not needed
[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=Patched (sys-patch)
[nim]
nim=Patched (sys-patch)
[ssl]
disablecaverification1=Disabled
disablecaverification2=Disabled
disablecaverification3=Disabled
[stats]
version=1.5.6-7aaaba2
build_date=15.12.2024 13:51:28
fw_version=19.0.1
ams_version=1.8.0
ams_target_version=0.1.0
ams_keygen=18
ams_hash=c6014b53
is_emummc=1
heap_size=4096
buffer_size=4096
patch_time=0.119s