do you have to go thru hekate to turn it on or just reboot it ?Downloading from https://gbatemp.net/download/sys-patch-1-5-2-binary-fw-18-1-0-atmosphere-1-7-1.38686/ and extract the zip to the root of your sd card, then restart the console.
do you have to go thru hekate to turn it on or just reboot it ?Downloading from https://gbatemp.net/download/sys-patch-1-5-2-binary-fw-18-1-0-atmosphere-1-7-1.38686/ and extract the zip to the root of your sd card, then restart the console.

Any of them.do you have to go thru hekate to turn it on or just reboot it ?
ok i did and i dont see any actions of sys-patch saying if it is patched or notAny of them.

Use the Sys-patch overlay to look into the log of the last time they runok i did and i dont see any actions of sys-patch saying if it is patched or not
i just run hekate cfw emcmu auto run fine just fuck it for nowUse the Sys-patch overlay to look into the log of the last time they run
Post automatically merged:
Any questions about SYS-Patch can be on https://gbatemp.net/threads/sys-patch-sysmod-that-patches-on-boot.633517

This fusee got the usb 3.0 working in atmosphere?Atmosphere still works with sig-patches if loaded via package3 and hekate. Or you can just use a modded fusee.bin such as this one that I compiled for the latest atmosphere which has ips kip patches support.

It's the exact same Fusee.bin than original, only the process of KIP patches reenabled.This fusee got the usb 3.0 working in atmosphere?
Newbie questionIt's the exact same Fusee.bin than original, only the process of KIP patches reenabled.

If you have sys-patch, you don't need sigpatches or the modified fusee.bin.If fusee.bin is regular one.
Do I need change with KIP patches enabled?
Could I have sigpatches and sys-patch together?
Could I delete sigpatches?
Sorry, I think I understand but a little confusing with this sentence

For loading sigpatches, loading Atmosphere's package3 via Hekate's FSS0 or using the modified fusee.bin with support for the kip patches restored results with sigpatches being properly loaded and game backups working again.“package 3” is equivalent to modified fusee.bin?
As of lately, I've noticed that some users were experiencing problems with sigpatches (games worked for some, but not for the others), while sys-patch worked for pretty much everyone, including those that had problems with sigpatches. Therefore, I personally recommend sys-patch.Why is better or not sys-patch vs sigpatches?

https://gbatemp.net/threads/can-onl...n-results-in-blackscreen.642958/post-10290324Sorry, I think I understand but a little confusing with this sentence
“package 3” is equivalent to modified fusee.bin?
Why is better or not sys-patch vs sigpatches?
Well, thank youFor loading sigpatches, loading Atmosphere's package3 via Hekate's FSS0 or using the modified fusee.bin with support for the kip patches restored results with sigpatches being properly loaded and game backups working again.
As of lately, I've noticed that some users were experiencing problems with sigpatches (games worked for some, but not for the others), while sys-patch worked for pretty much everyone, including those that had problems with sigpatches. Therefore, I personally recommend sys-patch.
As for the differences between two, sys-patch requires less frequent updates and it's easier to update among other things. TotalJustice, the original author, made a thread here, explaining what makes sys-patch good.

. LoL
May be it depends if you start a SysNAND or an EmuNANDI replaced my standard hekate.ini with this one and all my games is now gone. Is that normal?
I transferred a game. Transfer is ok, signature is invalid. Line 2,3,4 XCI=NSP
Line 5: signature invalid
Thanks. Noticed sysnand is nr1 and emunand nr 2 nowMay be it depends if you start a SysNAND or an EmuNAND