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

[tsukimaru]

install SYS-Patch Sysmodule and restart your console

Didn't work, I just pasted and rewrote over the older folders and no dice. Same error. Do I need to edit anything?

 

[Luisgabriel]

I have a mariko unit that I just updated to 19.0.1 in stock. Rebooted and getting a blue screen. Same with sysmmc. I updated hekate and atmosphere to their respective latest versions, and stock/sysmmc is still giving me a blue screen. Emummc works fine tho, and also if I use Hekate -> Reboot -> OFW option then it boots fine into stock. What am I missing?

Boot atmosphere in your sysmmc... atmosphere will automatically fix the loading error of your stock system

Then return to hekate and boot stock as you normally do

 

[shadow256]

Didn't work, I just pasted and rewrote over the older folders and no dice. Same error. Do I need to edit anything?

Try the fix archive bit option in Hekate. If it doesn't work post the log of Sys-patch, "config/sys-patch/log.ini" file.

 

[tsukimaru]

Try the fix archive bit option in Hekate. If it doesn't work post the log of Sys-patch, "config/sys-patch/log.ini" file.

Here it is:

Spoiler: Fulll log

[options]
patch_sysmmc=1
patch_emummc=1
enable_logging=1
version_skip=1
[fs]
noacidsigchk1=1
noacidsigchk2=1
noncasigchk_old=1
noncasigchk_new=1
nocntchk_old=1
nocntchk_new=1
noncasigchk_new2=1
nocntchk_FW19_1=1
nocntchk_FW19_2=1
nocntchk=1
nocntchk2=1
[ldr]
noacidsigchk=1
[es]
es1=1
es2=1
es3=1
es4=1
es5=1
es6=1
es7=1
es7_FW18-19=1
[nifm]
ctest=1
[nim]
nim=1

 

[shadow256]

Here it is:

Spoiler: Fulll log

[options]
patch_sysmmc=1
patch_emummc=1
enable_logging=1
version_skip=1
[fs]
noacidsigchk1=1
noacidsigchk2=1
noncasigchk_old=1
noncasigchk_new=1
nocntchk_old=1
nocntchk_new=1
noncasigchk_new2=1
nocntchk_FW19_1=1
nocntchk_FW19_2=1
nocntchk=1
nocntchk2=1
[ldr]
noacidsigchk=1
[es]
es1=1
es2=1
es3=1
es4=1
es5=1
es6=1
es7=1
es7_FW18-19=1
[nifm]
ctest=1
[nim]
nim=1

You gave e the "config/sys-patch/config.ini", that's not the file that I have asked.

 

[HenryBaby]

Boot atmosphere in your sysmmc... atmosphere will automatically fix the loading error of your stock system

Then return to hekate and boot stock as you normally do

This issue is already resolved. Booting sysmmc also gave me a blue screen tho, just for future reference.

 

[Tommy7600]

For anyone interested, this is a build of fusee.bin commit c6014b533 with FS Patches Reenabled

Thanks. Will you continue patching fusee.bin with newer versions?

 

[bth]

Thanks. Will you continue patching fusee.bin with newer versions?

no reason to with sys-patch

.ips patches really should be considered deprecated at this point, atmosphere's code for 19.0.0 support added in some mechanics related to nso (exefs) region where it doesn't allow itself to read or write to it with kernel designations such as "execute only"

i had ES crash when loading correct offset, correct patch as ips patch for 19.0.0+, embedding patches into loader bypasses the restriction (usb 3.0 patches are loaded that way), and sys-patch which isn't atmosphere also is not bound by those new restrictions.

sources such as "sigmapatches" as example do not even include 19.0.0 es .ips patch, and instead now includes sys-patch


the altered fusee.bin you people use exclusively load .ips kip_patches anyway, which is pointless.

 

[impeeza]

Thanks. Will you continue patching fusee.bin with newer versions?

As mentioned by the great bth do not worth it now, just use SYS-Patch

 

[tsukimaru]

You gave e the "config/sys-patch/config.ini", that's not the file that I have asked.

Woops, my bad. Here it is:

Spoiler

[fs]
noacidsigchk1=Skipped
noacidsigchk2=Skipped
noncasigchk_old=Skipped
noncasigchk_new=Skipped
noncasigchk_new2=Patched (sys-patch)
nocntchk=Skipped
nocntchk2=Patched (sys-patch)
[ldr]
noacidsigchk=Patched (sys-patch)
[es]
es1=Skipped
es2=Skipped
es3=Patched (file)
[nifm]
ctest=Patched (file)
[nim]
nim=Patched (sys-patch)
[stats]
version=1.5.4-54441b6
build_date=26.10.2024 11:16:22
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.096s

 

[shadow256]

Woops, my bad. Here it is:

Spoiler

[fs]
noacidsigchk1=Skipped
noacidsigchk2=Skipped
noncasigchk_old=Skipped
noncasigchk_new=Skipped
noncasigchk_new2=Patched (sys-patch)
nocntchk=Skipped
nocntchk2=Patched (sys-patch)
[ldr]
noacidsigchk=Patched (sys-patch)
[es]
es1=Skipped
es2=Skipped
es3=Patched (file)
[nifm]
ctest=Patched (file)
[nim]
nim=Patched (sys-patch)
[stats]
version=1.5.4-54441b6
build_date=26.10.2024 11:16:22
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.096s

OK so Sys-patch seems to work correctly but I see that you use files based sig_patches with Sys-patch, try to delete "atmosphere/exefs_patches/es_patches" and "atmosphere/exefs_patches/nfim_ctest" and "atmosphere/kip_patches" folders of your SD to only use Sys-patch. If you've used the reparation of corrupted contents when launching a game you also must reinstall it completly (game, update and DLCs). If your problem persist maybe it's the SD witch is the problem, maybe a fake SD (H2Test software could help to identify if it is) or a corrupted SD caused if it's formated in EXFAT or maybe an SD witch starts to die; or it also could be the source of your downloads witch doesn't work.

 

[tsukimaru]

OK so Sys-patch seems to work correctly but I see that you use files based sig_patches with Sys-patch, try to delete "atmosphere/exefs_patches/es_patches" and "atmosphere/exefs_patches/nfim_ctest" and "atmosphere/kip_patches" folders of your SD to only use Sys-patch. If you've used the reparation of corrupted contents when launching a game you also must reinstall it completly (game, update and DLCs). If your problem persist maybe it's the SD witch is the problem, maybe a fake SD (H2Test software could help to identify if it is) or a corrupted SD caused if it's formated in EXFAT or maybe an SD witch starts to die; or it also could be the source of your downloads witch doesn't work.

It worked!

I deleted the folders you described above, deleted the app I had installed, reinstalled the app and now it launches without an issue. Thank you!

 

[L3n_luvzz_p0t4to3s]

are there any 19.0.1 sigpatches????

 

[impeeza]

are there any 19.0.1 sigpatches????

YES, THE ONES ON THE OP, IF YOU READ THE PREVIOUS POST, THEY STATED 19.0.1 IS NOT SIGNIFICANT DIFFERENT FROM 19.0.0 AND THE PATCHES ARE THE SAME.

 

[Hayato213]

are there any 19.0.1 sigpatches????

The one for 19.0.0 work for 19.0.1

 

[L3n_luvzz_p0t4to3s]

YES, THE ONES ON THE OP, IF YOU READ THE PREVIOUS POST, THEY STATED 19.0.1 IS NOT SIGNIFICANT DIFFERENT FROM 19.0.0 AND THE PATCHES ARE THE SAME.

tysmmm :3

Post automatically merged: Nov 19, 2024

The one for 19.0.0 work for 19.0.1

tysmmmm :3

 

[Gontareczek]

Hi,

I updated the Switch to 19.0 and had problems running games, I did a sigipatches update and re-uploaded Tinfoil Folder 1.71.5 and set it to act as a forwarder. The Tinfoil store downloads old games for me and everything works, but I have a problem with running new games added recently, such as (new mario party, new sonic, dragon quest 3 remake)
Anyone have an idea how to fix this?

 

[impeeza]

Hi,

I updated the Switch to 19.0 and had problems running games, I did a sigipatches update and re-uploaded Tinfoil Folder 1.71.5 and set it to act as a forwarder. The Tinfoil store downloads old games for me and everything works, but I have a problem with running new games added recently, such as (new mario party, new sonic, dragon quest 3 remake)
Anyone have an idea how to fix this?

Did you upgrade SYS-Patch Sysmodule and then restarted the console?

 

[Gontareczek]

Did you upgrade SYS-Patch Sysmodule and then restarted the console?

unfortunately I didn't do this, could you tell me where I can find the files to update the sys-patch?

 

[alcab]

https://gbatemp.net/download/sys-patch-sysmodule.38874/