there are no stupid questions, you can read all about the sysmodule on the OP and the github repo.
https://github.com/ITotalJustice/sigpatch-updater
https://github.com/ITotalJustice/sigpatch-updater
Homebrew Homebrew app sys-patch - sysmod that patches on boot
- Thread starter TotalJustice
- Start date
- Views 104,919
- Replies 358
- Likes 108
nah, only a question about being a stupid question... wait, my room is spinning, all colors are blending, see you later...
So to use this we just drag and drop to the folders "atmosphere" and "switch" to the root of the micro SD card and has the same effect as sigpatches? How do we access the overlay? Where do we download sigpatches from if we still need them?
Yes that's how you install it. I've linked the sigpatches in the readme for sys-patch, however the URL will be updated soon.
Love how casually this was dropped, despite being bossmade as hell as a module functionality.
"oh here, a little dodad that circumvents the need to update all game type patches with Amos updates every time they roll out so that you can seamlessly continue playing games without stress of finding patches that let them launch properly.... but yeah, It's pretty cool I guess.. i was gonna just toss it in the bin, but here.."
touche on this though. very slick.
"oh here, a little dodad that circumvents the need to update all game type patches with Amos updates every time they roll out so that you can seamlessly continue playing games without stress of finding patches that let them launch properly.... but yeah, It's pretty cool I guess.. i was gonna just toss it in the bin, but here.."
touche on this though. very slick.
i'm not following how to install this.. even though I have installed the devkit and then copied and pasted the code required to generate some files in out switch. which were then copied to the nintendo switch.. after this point i'm lost.
Where is the interface which confirms what has been patched? I just don't follow beyond this.
Yes I do struggle with these instructions. I am autistic and usually prefer to watch somebody doing something, so please refrain from any harsh criticism.
Where is the interface which confirms what has been patched? I just don't follow beyond this.
Yes I do struggle with these instructions. I am autistic and usually prefer to watch somebody doing something, so please refrain from any harsh criticism.
You can either use the overlay to view the log output (as well as mess around with the settings) https://github.com/ITotalJustice/sys-patch#overlay
Or you can manually read the log which can be found at "/config/sys-patch/log.ini"
Yes skipped is normal. Patches are skipped if they're no longer valid for that fw version. You can enable checking for all patches using the config.ini or the overlay, although this really isn't needed.
As for the overlay, look into Tesla menu. It's a homebrew for the switch that allows you to display an overlay (like holding the home button).
Thanks man.
I think I won't install Tesla. If it's a replacement for Hekate or atmosphere. As I'm only just beginning to wrap my head around all this homebrew stuff anyway. I think I'll end up bricking the whole device .
But thanks again man
You can start at:
https://rentry.co/SwitchHackingIsEasy
Tesla is a Homebrew which allows the use of "Overlays", they are small homebrew what shows like the power menu or others system notifications, so can be run even if you are on a game and allows you to do several functions.
ok yes, it's really cool and i would like to use it. but i'm struggling to to understand just the basics : o
I was getting this error on boot/launch: (after installing sys-patch)
Failed to apply nosigchk
Press power to continue
Press VOL to go to menu
When I pressed power it would boot fine and everything worked fine - it was just really annoying.
So I wanted to post my solution here in case it helps anyone else.
Before sys-patch, I was on fw 15.0.1 and hekate 6.0.1 / nyx 1.5.1 - a lot of things have changed in the past year or so, so I wanted to update to latest fw 16.0.3 and update all of atmosphere/hekate (then move to adding tesla menu, overclocking, and themes)
I had AIO updater but had never used it, and I found that sigpatches are no longer included with it, so I wanted to find the most efficient way to update. Thats when I found sys-patch and so I installed that and then ran the rest thru AIO updater. Everything updated fine, but I was getting the Failed to Apply nosigchk error above.
I had originally modded using the rentry guide but I could not find a fix that tied this with now migrating to using sys-patch.
After tons of searching I somehow got to editing hekate_ipl.ini (I'm sure plenty of you already know what the issue is - but it doesn't seem to be explicitly clear. Although I may have easily missed it - the amount of old/deprecated information about switch modding vs modern relevant information is pretty daunting and can make it quite overwhelming.)
I did not install fw16.0.3 sigpatches and I know in the sys-patch install it says recommended to still install sigpatches, but I've seen people say they haven't updated them so I figured may as well try it out now.
So the solution was to remove this line from hekate_ipl.ini:
kip1patch=nosigchk
It would be nice if this was included on the git readme. Or some sort of example hekate_ipl.ini file. I didn't see any reference in this thread either. Again my apologies if I overlooked it.
I somehow had the line cal0blank=1 also - I'm not sure what that did, I thought maybe it was related - I removed that first and everything still seems to work fine, so I left it out.
After removing the line above, I no longer get the error during launch, and all seems well. I hope this info helps!
Thanks to everyone who develops these mods!
Failed to apply nosigchk
Press power to continue
Press VOL to go to menu
When I pressed power it would boot fine and everything worked fine - it was just really annoying.
So I wanted to post my solution here in case it helps anyone else.
Before sys-patch, I was on fw 15.0.1 and hekate 6.0.1 / nyx 1.5.1 - a lot of things have changed in the past year or so, so I wanted to update to latest fw 16.0.3 and update all of atmosphere/hekate (then move to adding tesla menu, overclocking, and themes)
I had AIO updater but had never used it, and I found that sigpatches are no longer included with it, so I wanted to find the most efficient way to update. Thats when I found sys-patch and so I installed that and then ran the rest thru AIO updater. Everything updated fine, but I was getting the Failed to Apply nosigchk error above.
I had originally modded using the rentry guide but I could not find a fix that tied this with now migrating to using sys-patch.
After tons of searching I somehow got to editing hekate_ipl.ini (I'm sure plenty of you already know what the issue is - but it doesn't seem to be explicitly clear. Although I may have easily missed it - the amount of old/deprecated information about switch modding vs modern relevant information is pretty daunting and can make it quite overwhelming.)
I did not install fw16.0.3 sigpatches and I know in the sys-patch install it says recommended to still install sigpatches, but I've seen people say they haven't updated them so I figured may as well try it out now.
So the solution was to remove this line from hekate_ipl.ini:
kip1patch=nosigchk
It would be nice if this was included on the git readme. Or some sort of example hekate_ipl.ini file. I didn't see any reference in this thread either. Again my apologies if I overlooked it.
I somehow had the line cal0blank=1 also - I'm not sure what that did, I thought maybe it was related - I removed that first and everything still seems to work fine, so I left it out.
After removing the line above, I no longer get the error during launch, and all seems well. I hope this info helps!
Thanks to everyone who develops these mods!
Last edited by elptarkus,
Out of curiosity, would anyone happen to know why my sys-patch log shows the ldr patch as green (being patched by sys-patch), while the rest are orange? Not that it's causing any issues, I'm just wondering if that's considered normal. I applied sigpatches manually and expected all to appear orange in the sys-patch log. This happens with both downloaded sigpatches and ones I created myself.
This is so amazing. Thank you for creating this. I'm so sick of having to do new patches every single time anything changes... It has been a serious problem -- especially since sometimes the patches seem to get taken down (esp. from GitHub it seems) or people just get tired of constantly having to generate new patches over and over. I've had troubles with the tools to generate several times too (ironically I had the most luck with a much older one then couldn't seem to get working patches with newer ones.) I feel like the whole patch mechanism is just fundamentally a mess. A sysmodule like this sounds like a much cleaner and overall better solution. I can't guess how well this module will continue working, but it is a wonderful idea and I hope there will be good support for it and its idea throughout the future.
The ctest patch is a nice little bonus.
The ctest patch is a nice little bonus.
dont take LSD then lmaonah, only a question about being a stupid question... wait, my room is spinning, all colors are blending, see you later...
Post automatically merged:
idc if late reply i had to do it xD
Similar threads
-
- Locked
- Portal
- No one is chatting at the moment.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
@
RedColoredStars:
There is an actual trailer with footage too. lol. Going to watch it tonight. Grabbed it from... a place. -
-
@
SylverReZ:
@Psionic Roshambo, JonTron's back yet again until he disappears into the void for another 6 or so months.+1 -
-
