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

  • Thread starter Thread starter ShadowOne333
  • Start date Start date
  • Views Views 5,313,526
  • Replies Replies 7,368
  • Likes Likes 266
OP = Original Post, i.e. the first post in the thread.
original post in from July 14 and it says updated to 20.3.0, that update was not even out so... and page 1 says beta, is it still in beta? can someone link one that actually works?
 
original post in from July 14 and it says updated to 20.3.0, that update was not even out so... and page 1 says beta, is it still in beta? can someone link one that actually works?

That linked file works fine. Posts can be edited long after the date you are talking about.

Instead of looking at that date at the top left of the post, look for the date at the bottom right of the post after "Last edited by".
 
  • Like
Reactions: Blythe93
Hey guys first time poster here
I’m on atmosphere 1.9.3 and firmware 19.0.1
My Zelda game cartridge isn’t being read in atmosphere I asked ChatGPT and it said the problem is I need to install the proper sigpatches

The problem is it’s been a headache to find the proper sigpatches for my combination.

Could anyone direct me to where I could find it and if that will solve my game cartridge problem?
 
no need for sigpatches just use SYS-Patch
I can open nsps and use dlcs no problem on my switch the problem is only the game cartridges can’t be read

I think I’m already using syspatch since my nsps work fine
Any idea on how to fix this issue?
Post automatically merged:

I can open nsps and use dlcs no problem on my switch the problem is only the game cartridges can’t be read

I think I’m already using syspatch since my nsps work fine
Any idea on how to fix this issue
I just sent chatgpt a picture of the text in my hekate_ipl.ini file in bootloader folder and it said I’m not using SYS-patches but I’m using fusee and it advices me to fix the issue to insert a line in my file like this


[Atmosphere CFW]
payload=bootloader/payloads/fusee.bin
icon=bootloader/res/icon_payload.bmp

Add the following line

[Atmosphere CFW]
payload=bootloader/payloads/fusee.bin
kip1patch=nosigchk
icon=bootloader/res/icon_payload.bmp

Will this actually fix the issue?
 
Last edited by Tobtob-123,
AMS for firmware 20.3.0 here.
Hekate for firmware 20.3.0 here.
Modded AMS (fusee.bin) for firmware 20.3.0 that allows the use of sigpatches (not yet available).
Sigpatches for firmware 20.3.0 here.
Sys-patch for firmware 20.3.0 here.
Lockpick RCM for firmware 20.3.0 here.
Mission Control for firmware 20.3.0 here.

Instructions on how to migrate from sigpatches to sys-patch here (read three messages).
Instructions on how to modify hekate_ipl.ini for the new version of Hekate here.
Ultimate guide by impeeza on how to update your firmware/Atmosphère here.


thank you @impeeza and @Blythe93!

PD: As soon as someone tells me where to find the modded fusee.bin file for using sigpatches under firmware 20.3.0, I'll update this message. In the meantime, I recommend booting with hekate, or even better, migrating from sigpatches to sys-patch.
 
@alcab
I have done everything you posted, result is I can install programs on emunand but they requires to connect to eshop when trying lunching them . Any idea why ?
 
I have done everything you posted, result is I can install programs on emunand but they requires to connect to eshop when trying lunching them . Any idea why ?
Get Tesla menu + nx-ovlloader as well and extract them to your SD card, reboot and press L + D-pad Down + R (Stick) combo to open up a Tesla menu, select sys-patch and check logs. It should say Patched for everything (either green or orange is fine).
 
Get Tesla menu + nx-ovlloader as well and extract them to your SD card, reboot and press L + D-pad Down + R (Stick) combo to open up a Tesla menu, select sys-patch and check logs. It should say Patched for everything (either green or orange is fine).
Why? no reason to.

just booting with sys-patch produces a log file in "/config/sys-patch/log.ini"

adding unnecessary sysmodules isn't really the meta these days.
 
Why? no reason to.

just booting with sys-patch produces a log file in "/config/sys-patch/log.ini"

adding unnecessary sysmodules isn't really the meta these days.
Just for the ease of access to the logs from the console itself. But yeah, if sys-patch is the only module they are using, those two are not necessary.
 
as the other user said I saw the log files and some was unpatched ( think "new_something "). Question is , what to do ?
 
as the other user said I saw the log files and some was unpatched ( think "new_something "). Question is , what to do ?
if it says noncasigchk_new and the console is above fw 17.0.0, delete /bootloader/patches.ini, change hekate_ipl.ini to no longer load kip patches.

if below 17.0.0, it doesnt matter, it only applies 17.0.0+
 
  • Like
Reactions: Blythe93
if it says noncasigchk_new and the console is above fw 17.0.0, delete /bootloader/patches.ini, change hekate_ipl.ini to no longer load kip patches.

if below 17.0.0, it doesnt matter, it only applies 17.0.0+
noncasigchk_new unpatched . Console is 20.3.0 . Emulated is 20.3.0. Hekate already is set not to use kip patches .
 
No, you can remove that and remove the NoSigCHK set on the Hekate_ipl.ini file.
Hi Impeeza, along the same lines, can we also delete all the IPS files in the “KIPS Patches” and “loader_patches” folders?
And a second question: why do pack makers like Shadow Team LS and Zoria keep those files and keep the lines
kip1=atmosphere/kips/* in hekate_ipl.ini as well as pkg3ex=1?
I’m building my own pack too and have kept those elements out of habit, but they’re logically useless, aren’t they?
In that case, why do you publish sigpatches at all, since sys-patch already does the job with the folder atmosphere/contents/420000000000000B/?
Thx for your ansewer
 

Site & Scene News

Popular threads in this forum