Toggle sidebar

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

  • Thread starter Thread starter ShadowOne333
  • Start date Start date
  • Views Views 5,179,577
  • Replies Replies 7,279
  • Likes Likes 266
hey so quick (probaby pointless imo) question here
So when I try to install my dumped games (including updates and DLCs) onto emuMMC, when I use goldleaf I get an error (Saying I need the missing patches) I grabbed the ones here and works fine and all.
However, After updating the switch to ver 21.2 (this was before 22.0+) none of my games work anymore.

When I updated the console to 21.2, did I also have to update the sigpatches to 21.2 as well? or do I just have to uninstall each game, then reinstall them after updating the sigpatches
 
I'm confused as hell, I have Atmosphère 1.11.1, I keep getting an error related to the sig patches (failed to apply nosigchk), I don't even use it for pirated games, just trying to play ult modded, what do I have to install? We can't use sigpatches anymore?
 
Formoball said:
I'm confused as hell, I have Atmosphère 1.11.1, I keep getting an error related to the sig patches (failed to apply nosigchk), I don't even use it for pirated games, just trying to play ult modded, what do I have to install? We can't use sigpatches anymore?
Click to expand...
On the main post the author says that sigpatches wont be used anymore from 22 and up.
just edit your hekate boot option like this:
[SEMI-OFW]
pkg3=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/stock.bmp

[CFW/EMUMMC]
pkg3=atmosphere/package3
emummcforce=1
icon=bootloader/res/emummc.bmp

and thats it.

even if you're going to use security backups or not.
for security backups you will require ultrahand + sys-patches
 
DrEmuler said:
On the main post the author says that sigpatches wont be used anymore from 22 and up.
just edit your hekate boot option like this:
[SEMI-OFW]
pkg3=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/stock.bmp

[CFW/EMUMMC]
pkg3=atmosphere/package3
emummcforce=1
icon=bootloader/res/emummc.bmp

and thats it.

even if you're going to use security backups or not.
for security backups you will require ultrahand + sys-patches
Click to expand...
Op said they will not be updating sigpatches or the usual tool to create them.

Other people are still creating and providing sigpatches and current ones can be found in this thread.

Edit: Pointless to not link to the patches. https://gbatemp.net/attachments/patches-fw22-1-0-atmo1-11-1-zip.567005/
 
Last edited by OrGoN3,
  • Like
Reactions: Blythe93
OrGoN3 said:
Op said they will not be updating sigpatches or the usual tool to create them.

Other people are still creating and providing sigpatches and current ones can be found in this thread.

Edit: Pointless to not link to the patches. https://gbatemp.net/attachments/patches-fw22-1-0-atmo1-11-1-zip.567005/
Click to expand...
i tried many other releases and have MANY issues, including that one in v22 and v22.1

are not working as intended.

If syspatch exist, there's no point to keep using sigpatches if yours are working open your thread and maintain the repo, i will be one of the users that will test and use your work.

for now syspatches its more complete, easier and stable than sigpatches.
 
DrEmuler said:
i tried many other releases and have MANY issues, including that one in v22 and v22.1

are not working as intended.

If syspatch exist, there's no point to keep using sigpatches if yours are working open your thread and maintain the repo, i will be one of the users that will test and use your work.

for now syspatches its more complete, easier and stable than sigpatches.
Click to expand...
I've had zero issues and completely disagree with the rest of your post.
 
  • Like
Reactions: DrEmuler
OrGoN3 said:
I've had zero issues and completely disagree with the rest of your post.
Click to expand...
its ok, thats why GBATemp its a good place, anyone can have their own POV 🌈

If you dont have issues that doesnt mean doesnt exist, or have you tried the full Switch catalog? (more than 9k games)
I dont think so.

Theres a good reason of why almost everyone left the support of sigpatches.
Have ZERO advantages vs syspatches and the issues could happen, and well, there’s NO standard with sigpatches, update it its harder everyday… i mean all is against sigpatches vs syspatches.

As i suggested before you should open and mantain your own repo if you want to keep using it
 
DrEmuler said:
its ok, thats why GBATemp its a good place, anyone can have their own POV 🌈

If you dont have issues that doesnt mean doesnt exist, or have you tried the full Switch catalog? (more than 9k games)
I dont think so.

Theres a good reason of why almost everyone left the support of sigpatches.
Have ZERO advantages vs syspatches and the issues could happen, and well, there’s NO standard with sigpatches, update it its harder everyday… i mean all is against sigpatches vs syspatches.

As i suggested before you should open and mantain your own repo if you want to keep using it
Click to expand...
i'm supporting three different means

sys-patch (mostly my patterns)
sigpatches (i make them every firmware version as i verify my patterns anyway)
and third means is this:
https://tinfoil.io/ams
https://github.com/borntohonk/Atmosphere/commit/e2a141647f8be7d90002d1a7151076927a188a07
a fork of atmosphere with them all integrated, removing the need for both sys-patch and sigpatches, doesn't matter if hekate, doesn't matter if fusee.

there is merit to using "sigpatches" as opposed to "sys-patch", unfortunately. as sys-patch uses a svc debug memory edit function after an application has been launched and is in memory, while "sigpatches", apply the patches before the modules are launched into memory and executed

and the forked equivelant, obviously has the merit of it already being in the codebase, need atmosphere on sd card, done.
 
Last edited by bth,
  • Like
Reactions: Night007 and Blythe93
Hi

I'm currently on firmware 18.1.0 + Atmo 1.7.1.
From what I can see, to keep as many homebrew applications compatible as possible, a fairly safe firmware would be 20.5.

I want to keep many homebrew applications like Tinfoil, awoo, Linkalho, etc.
My goal is to be able to keep as many homebrew applications as possible and also be able to play Nintendo games online.

What's the best way to do this?
I have download Atmo 1.9.5 + Hakate 6.3.1.
But I can't find the sigpatches.
 
bth said:
sys-patch (mostly my patterns)
sigpatches (i make them every firmware version as i verify my patterns anyway)
Click to expand...
Question about your ams fork. If you still creating sigpatches (validate pattern), why to use patterns in the ams code and not direct patch offsets? In any case ams will need to be recompiled for new ofw.

I understand that patterns will take less place in code itself, but they are require more supporting code for apply. Also direct offsets will be faster to apply.
 
  • Like
Reactions: Blythe93 and proconsule54
duckbill007 said:
Question about your ams fork. If you still creating sigpatches (validate pattern), why to use patterns in the ams code and not direct patch offsets? In any case ams will need to be recompiled for new ofw.

I understand that patterns will take less place in code itself, but they are require more supporting code for apply. Also direct offsets will be faster to apply.
Click to expand...
https://github.com/borntohonk/Switch-Ghidra-Guides/blob/master/scripts/known_patterns.py
https://github.com/borntohonk/Switch-Ghidra-Guides/blob/master/scripts/pattern_diffs.py


the short answer is, i validate the patterns by just processing firmware files. I find the offset, by validating the pattern, if pattern is not valid, i reverse the functions (with ghidra) and diff it, and make a new pattern or, if alignment wills it, alter the pattern to include the new anomaly.

While I could hardcode offsets, i think the gimmicks are more fun. as for time saved, Sys-patch as a sysmodule uses 0.08 seconds, and all I have done is add a "sys-patch" into mesosphere for FS only (1 patch less than sys-patch because of loader hardcode patch), and another into loader for exefs patches.

I'm more or less doing it for the gimmick, but also because I make the patterns anyway.

code.gif
 
  • Like
Reactions: Night007 and Blythe93
bth said:
https://github.com/borntohonk/Switch-Ghidra-Guides/blob/master/scripts/known_patterns.py
https://github.com/borntohonk/Switch-Ghidra-Guides/blob/master/scripts/pattern_diffs.py


the short answer is, i validate the patterns by just processing firmware files. I find the offset, by validating the pattern, if pattern is not valid, i reverse the functions (with ghidra) and diff it, and make a new pattern or, if alignment wills it, alter the pattern to include the new anomaly.

While I could hardcode offsets, i think the gimmicks are more fun. as for time saved, Sys-patch as a sysmodule uses 0.08 seconds, and all I have done is add a "sys-patch" into mesosphere for FS only (1 patch less than sys-patch because of loader hardcode patch), and another into loader for exefs patches.

I'm more or less doing it for the gimmick, but also because I make the patterns anyway.

View attachment 570603
Click to expand...
I see. From a technical standpoint, sigpatches are superior because they are applied before execution, making them more stable. I used to use them before, but the catch with sigpatches and custom Atmosphere builds is that they are maintained individually essentially your own personal projects. If for any reason you were to stop providing support, that support is lost and we’d have to look for a new provider, both for your fork and the sigpatches. This is contrary to sys-patch, which involves more contributors and offers better long term support stability. For a regular user, the difference is virtually non-existent at the end of the day.


Don't get me wrong, you are doing an admirable and excellent job with all three methods. However, in this very post, while looking for sigpatches, I realized it is more stable and wiser to follow your collaborative work on sys-patch rather than clinging to sigpatches, which, to be honest, are being used less and less.
 
DrEmuler said:
its ok, thats why GBATemp its a good place, anyone can have their own POV 🌈

If you dont have issues that doesnt mean doesnt exist, or have you tried the full Switch catalog? (more than 9k games)
I dont think so.

Theres a good reason of why almost everyone left the support of sigpatches.
Have ZERO advantages vs syspatches and the issues could happen, and well, there’s NO standard with sigpatches, update it its harder everyday… i mean all is against sigpatches vs syspatches.

As i suggested before you should open and mantain your own repo if you want to keep using it
Click to expand...
Going off topic, but I guess that's normal here.

Sigpatches are binary. They either patch the necessary parts or they don't. I don't need to try over 9000 (source: mistranslated Vegeta) games to ensure they work. They either patch what they're supposed to or they don't.

You don't speak for everyone. Almost everyone left the support of sigpatches because of sys-patch? No. Are you talking devs? They left for other reasons. Are you talking users? Ones that know what they are doing use them just fine.

I will not open and maintain something that has a history of getting DMCA'd.

I'd prefer to not go further with this bit as it's off topic, but I'll respond if needed.
 
OrGoN3 said:
Going off topic, but I guess that's normal here.

Sigpatches are binary. They either patch the necessary parts or they don't. I don't need to try over 9000 (source: mistranslated Vegeta) games to ensure they work. They either patch what they're supposed to or they don't.

You don't speak for everyone. Almost everyone left the support of sigpatches because of sys-patch? No. Are you talking devs? They left for other reasons. Are you talking users? Ones that know what they are doing use them just fine.

I will not open and maintain something that has a history of getting DMCA'd.

I'd prefer to not go further with this bit as it's off topic, but I'll respond if needed.
Click to expand...
You’re basing your stance on a personal opinion.
I’m talking about current facts that can be verified and proven.

Whether you like it or not, at the end of the day, SysPatch is maintained in a single place; it’s easier to find and easier to use for regular users.
I can speak for everyone when I tell you that nobody cares if you got the sigpatches working, even "if you know what you’re doing to use them correctly"
not to mention there’s no centralized source to get them.

Even though people like bth are still behind them, syspatches are simpler to obtain, use, and maintain, especially for the devs who are the ones actually doing the heavy lifting.
The fact that sigpatches load before execution, making them more stable, doesn't necessarily make them more practical today.
At the end of the day, they do exactly the same thing for the end user, for the reasons described above.
Things are what they are, whether you accept them or not;
the facts, the information, the data, and the sources are all there.

If you didn't want to continue with the off-topic, it wasn't necessary for you to comment that 'you can use them without issues' as if you knew something the rest of us don't...
If you didn't agree with the rest of my post, you could have just ignored it like everyone else.

Instead, bth gave a technical, valid, and supported answer beyond just:
'I've had zero issues.' Bro, nobody cares if you don't have problems with it;
That’s not the point of the discussion.
The point is ease of use and the support provided for syspatches.
The author of that very post stated that they will no longer be released starting from version 22. Now, people will have to hunt them down, test them, and invest more time, things that the regular users is unlikely to be able or willing to do.

Meanwhile, syspatches achieve the same result with a centralized download source on GitHub. I don't want to waste any more time trying to make you understand.

If you're happy using sigpatches, go ahead.
The rest of us likely prefer the more practical and accessible option called syspatches.
Let’s remember that the point is to use our Switch and have fun, not to spend more time trying to make the console work than actually playing
 
OrGoN3 said:
Going off topic, but I guess that's normal here.

Sigpatches are binary. They either patch the necessary parts or they don't. I don't need to try over 9000 (source: mistranslated Vegeta) games to ensure they work. They either patch what they're supposed to or they don't.

You don't speak for everyone. Almost everyone left the support of sigpatches because of sys-patch? No. Are you talking devs? They left for other reasons. Are you talking users? Ones that know what they are doing use them just fine.

I will not open and maintain something that has a history of getting DMCA'd.

I'd prefer to not go further with this bit as it's off topic, but I'll respond if needed.
Click to expand...

as someone (me) who actually have received an actual C&D from nintendo, unlike these people who shut down their repositories voluntarily, or received a FAKE dmca (!!!! actual thing in the switch scene out of petty reasons !!!!) and called it quits, it's more nuanced.

I went over of course, the C&D with an actual lawyer (like you're supposed to), and was told which parts i have to "comply" with, and which parts are not enforcable by law here, and was told, "complete removal or complete stop to your activities is not necessary", Amend this and that, remove this and that, don't do this or that again, add this or that disclaimer here, and so on.

I know "a lot of people" left after ryan (pedophile) got indicted on federal charges + posession of child pornography, if we are to call that first wave of people leaving scene, that did cause a considerable amount of noticable vaccum of knowledge in the scene, and second wave of people leaving is of course, the entire constellation of people affeliated with "archbox", which has merit for legal reasons, as conspiracy charges under RICO are not fun.

both ryan and "archbox" causing people to leave is both a RICO situation, as ryan, aside from his pedophilic tendencies and charges for posession of child pornography, did some actual hacking of nintendos backend, and shared that with a lot of people. i.e. source codes for every single game nintendo has, every single BDK for every single console

people spook very easily and are afraid of extradition after gary/TX situation, and there are a lot of lawyers (or have been) in the scene telling people to stop doing stupid stuff.
 
Last edited by bth,
  • Like
Reactions: DrEmuler
DrEmuler said:
You’re basing your stance on a personal opinion.
I’m talking about current facts that can be verified and proven.

Whether you like it or not, at the end of the day, SysPatch is maintained in a single place; it’s easier to find and easier to use for regular users.
I can speak for everyone when I tell you that nobody cares if you got the sigpatches working, even "if you know what you’re doing to use them correctly"
not to mention there’s no centralized source to get them.

Even though people like bth are still behind them, syspatches are simpler to obtain, use, and maintain, especially for the devs who are the ones actually doing the heavy lifting.
The fact that sigpatches load before execution, making them more stable, doesn't necessarily make them more practical today.
At the end of the day, they do exactly the same thing for the end user, for the reasons described above.
Things are what they are, whether you accept them or not;
the facts, the information, the data, and the sources are all there.

If you didn't want to continue with the off-topic, it wasn't necessary for you to comment that 'you can use them without issues' as if you knew something the rest of us don't...
If you didn't agree with the rest of my post, you could have just ignored it like everyone else.

Instead, bth gave a technical, valid, and supported answer beyond just:
'I've had zero issues.' Bro, nobody cares if you don't have problems with it;
That’s not the point of the discussion.
The point is ease of use and the support provided for syspatches.
The author of that very post stated that they will no longer be released starting from version 22. Now, people will have to hunt them down, test them, and invest more time, things that the regular users is unlikely to be able or willing to do.

Meanwhile, syspatches achieve the same result with a centralized download source on GitHub. I don't want to waste any more time trying to make you understand.

If you're happy using sigpatches, go ahead.
The rest of us likely prefer the more practical and accessible option called syspatches.
Let’s remember that the point is to use our Switch and have fun, not to spend more time trying to make the console work than actually playing
Click to expand...
You're literally saying the same type of things I am. You are providing no sources for anything you're claiming. You're just saying stuff that you think is correct and generalizing it to the entire switch community.

I speak of personal experience and of the experience of the people successfully I help every day.

I had to reply because you keep on giving misinformation. So either stop and I'll stop replying, or I'll continue to defend your accusations.

Sigpatches work or they don't. There's no middle ground there. You and your buddies having problems with them has no bearing on their validity.

The point of your post was that people had issues with them. But now all of a sudden it's not a point? The data and sources are all there? You haven't linked to a single example.

There are single places to get updated sigpatches. You not knowing them doesn't mean they don't exist.

You also gave zero technical details.

I'm not unhappy with sys-patch nor have I ever stated that. Either defend what you say or keep pivoting. You are providing zero benefit to this conversation and simply I am doing the same. Yet you keep on making generalized statements, seemingly speaking for the majority of the community, when you're wrong and have no way of backing up what you're saying.

Either provide real details or stop.
Post automatically merged:

bth said:
as someone (me) who actually have received an actual C&D from nintendo, unlike these people who shut down their repositories voluntarily, or received a FAKE dmca (!!!! actual thing in the switch scene out of petty reasons !!!!) and called it quits, it's more nuanced.

I went over of course, the C&D with an actual lawyer (like you're supposed to), and was told which parts i have to "comply" with, and which parts are not enforcable by law here, and was told, "complete removal or complete stop to your activities is not necessary", Amend this and that, remove this and that, don't do this or that again, add this or that disclaimer here, and so on.

I know "a lot of people" left after ryan (pedophile) got indicted on federal charges + posession of child pornography, if we are to call that first wave of people leaving scene, that did cause a considerable amount of noticable vaccum of knowledge in the scene, and second wave of people leaving is of course, the entire constellation of people affeliated with "archbox", which has merit for legal reasons, as conspiracy charges under RICO are not fun.

both ryan and "archbox" causing people to leave is both a RICO situation, as ryan, aside from his pedophilic tendencies and charges for posession of child pornography, did some actual hacking of nintendos backend, and shared that with a lot of people. i.e. source codes for every single game nintendo has, every single BDK for every single console

people spook very easily and are afraid of extradition after gary/TX situation, and there are a lot of lawyers (or have been) in the scene telling people to stop doing stupid stuff.
Click to expand...
And me not wanting to have to spend the money on a lawyer to make sure I'm in compliance is a perfectly valid reason. I didn't say the DMCA's were valid. I just said they existed and will end up costing the end use money one way or another.
 
OrGoN3 said:
You're literally saying the same type of things I am. You are providing no sources for anything you're claiming. You're just saying stuff that you think is correct and generalizing it to the entire switch community.

I speak of personal experience and of the experience of the people successfully I help every day.

I had to reply because you keep on giving misinformation. So either stop and I'll stop replying, or I'll continue to defend your accusations.

Sigpatches work or they don't. There's no middle ground there. You and your buddies having problems with them has no bearing on their validity.

The point of your post was that people had issues with them. But now all of a sudden it's not a point? The data and sources are all there? You haven't linked to a single example.

There are single places to get updated sigpatches. You not knowing them doesn't mean they don't exist.

You also gave zero technical details.

I'm not unhappy with sys-patch nor have I ever stated that. Either defend what you say or keep pivoting. You are providing zero benefit to this conversation and simply I am doing the same. Yet you keep on making generalized statements, seemingly speaking for the majority of the community, when you're wrong and have no way of backing up what you're saying.

Either provide real details or stop.
Post automatically merged:


And me not wanting to have to spend the money on a lawyer to make sure I'm in compliance is a perfectly valid reason. I didn't say the DMCA's were valid. I just said they existed and will end up costing the end use money one way or another.
Click to expand...
Bro, I didnt waste my time reading what you wrote;
it’s probably just a bunch of nonsense.
Get over it and use whatever you want I’m not spending any more of my time on you.
bth said:
as someone (me) who actually have received an actual C&D from nintendo, unlike these people who shut down their repositories voluntarily, or received a FAKE dmca (!!!! actual thing in the switch scene out of petty reasons !!!!) and called it quits, it's more nuanced.

I went over of course, the C&D with an actual lawyer (like you're supposed to), and was told which parts i have to "comply" with, and which parts are not enforcable by law here, and was told, "complete removal or complete stop to your activities is not necessary", Amend this and that, remove this and that, don't do this or that again, add this or that disclaimer here, and so on.

I know "a lot of people" left after ryan (pedophile) got indicted on federal charges + posession of child pornography, if we are to call that first wave of people leaving scene, that did cause a considerable amount of noticable vaccum of knowledge in the scene, and second wave of people leaving is of course, the entire constellation of people affeliated with "archbox", which has merit for legal reasons, as conspiracy charges under RICO are not fun.

both ryan and "archbox" causing people to leave is both a RICO situation, as ryan, aside from his pedophilic tendencies and charges for posession of child pornography, did some actual hacking of nintendos backend, and shared that with a lot of people. i.e. source codes for every single game nintendo has, every single BDK for every single console

people spook very easily and are afraid of extradition after gary/TX situation, and there are a lot of lawyers (or have been) in the scene telling people to stop doing stupid stuff.
Click to expand...
Btw, wonderful explanations as always. I’d like to get in touch with the lawyer who advised you, if possible.
I’d like to consult with them on a few things (paying their fees, of course)
 

Site & Scene News

Go to forum More news

Popular threads in this forum

Dusk for switch (TLoZ Twilight Princess port)

Homebrew  New Homebrew "Foil Server"?

Homebrew  Full List of N64 Recompilation Switch ports

Hacking  WiFi chip failing and can't boot. is it possible to enable Airplane Mode by editing system save files directly?

Homebrew Tutorial Translation Project  CS2SX — Write Nintendo Switch Homebrew in C#

Is it fixable

Homebrew  Sonic Unleashed Recompiled (Homebrew Port)

Hacking Emulation  Switch Prod Keys downloading from sites okay?