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

  • Thread starter Thread starter ShadowOne333
  • Start date Start date
  • Views Views 5,307,305
  • Replies Replies 7,368
  • Likes Likes 266
The purpose of that configuration is allow forwarders created before FW 19 to run on FW 19. If you don't have Tesla Menu, edit/Create the SDMC:/config/sys-patch/config.ini file and put on it:

Code:
[options]
version_skip=0
<...>
Should version_skip be 0? The default is 1.
 

Attachments

  • Bild_2024-10-22_180247249.png
    Bild_2024-10-22_180247249.png
    331.9 KB · Views: 67
Should version_skip be 0? The default is 1.
Nop, the default is 0, that way only patches mean for the FW and ATM version are applied, when you enable that config, ALL PATCHES are tried to be applied even if they are not meant for your current versions. resulting in a lot of UNPATCHED red logs because that patterns will not be present..
Post automatically merged:

just like this, the UNPATCHED red are patches which do not apply to your setup, but you have another set of patches which are for your setup applied.
Post automatically merged:

if you like no see the unpatched red ones then go to options and disable the «skip vrersion» ITEM. restart and they will be gone.
 
  • Like
Reactions: Blythe93
first test-pre is:
#Loader Atmosphere-1.8.0
[Loader:D3FD950603AECC4D]
.nosigchk=0:0x602A:0x1:01,00

this new released pre is:
[Loader:A73B75768096EA90]
.nosigchk=0:0x602A:0x1:01,00

and also your must add new loader file to atmosphere\kip_patches\loader_patches
Looks like these sigpatches only work with eshop content, homebrew and fowarders don't work.
 
@JamesDeans : You can try to go to "tools", "fix archive bit" in Hekate, maybe tiy have a problem with this witch can result in strange reactions of the console. If it doesn't work post the log file of the module witch is in the "config/sys-patch" folder on your SD.
 
  • Love
Reactions: impeeza
Looks like these sigpatches only work with eshop content, homebrew and fowarders don't work.
Homebrew works fine, OLD forwarders need a new version of SYS-Patch

use the one on:
https://gbatemp.net/threads/sys-patch-sysmod-that-patches-on-boot.633517/page-28#post-10522345

or Do this:


And also be sure your Config.ini file is like the one on:

https://gbatemp.net/threads/sigpatc...kate-fss0-fusee-package3.571543/post-10522096

RESTART YOUR CONSOLE and test again.
 
  • Like
Reactions: Blythe93
Nop, the default is 0, that way only patches mean for the FW and ATM version are applied, when you enable that config, ALL PATCHES are tried to be applied even if they are not meant for your current versions. resulting in a lot of UNPATCHED red logs because that patterns will not be present..
Post automatically merged:

just like this, the UNPATCHED red are patches which do not apply to your setup, but you have another set of patches which are for your setup applied.
Post automatically merged:

if you like no see the unpatched red ones then go to options and disable the «skip vrersion» ITEM. restart and they will be gone.
According to https://github.com/impeeza/sys-patch?tab=readme-ov-file#config:
version_skip=1 ; 1=(default) skips out of date patterns, 0=search all patterns
so the default is Version skip = On, meaning to skip patches that are not needed for the currently running FW versions.
@JamesDeans had it Off, all patches are shown, those that are not meant for that FW show in red, and that is likely the root of the confusion.

@impeeza may I suggest editing version_skip=1 back here to prevent this?
 
Last edited by Nephiel,
  • Like
Reactions: Blythe93
According to https://github.com/impeeza/sys-patch?tab=readme-ov-file#config:

so the default is Version skip = On, meaning to skip patches that are not needed for the currently running FW versions.
@JamesDeans had it Off, all patches are shown, those that are not meant for that FW show in red, and that is likely the root of the confusion.

@impeeza may I suggest editing version_skip=1 back here to prevent this?
Yes I am looking troght the code the item «version_skip» control if the version is checked, I don't know why on my mind I think on my mind backwards.

The default setting is 1!

VERSION_SKIP = ini_load_or_write_default("options", "version_skip", 1, ini_path);

and if the Version Skip is true (1) then the target FW and ATM is verified BEFORE apply a patch.

if is 0 then no verification is performed and processed no matter what. I don't know in my mind I believe Version_skip was Version_check_skip, my bad.

I was using on my config version_skip as 0 to make a full investigation about which patterns are found on which firmware and ATM...
 
@impeeza : I've looked into your code (thanks for sharing it) and I have a small question, why have you have added a "constexpr" declaration for the "cmp" function and why you have removed it for the "mov2_ccond" function (for "mov_cond" function it is not removed)? I suppose it's not very important but I'm just curious.
 
Working here... Old and New forwarders.

Tested some apps with no errors.

What's the purpose of debug_flag_off?

I've built a sys-patch without this "off" patch and all seems ok.
sys-patch can be run any time you like with a sysmodule manager. The off patch is useful if you cheat because as shipped dmnt don't have the flag and if you elevate games to higher level dmnt can no longer hack them.

Solution is either turn off the debug_flag with the off patch or use a dmnt with the debug flag set.
 
@impeeza : I've looked into your code (thanks for sharing it) and I have a small question, why have you have added a "constexpr" declaration for the "cmp" function and why you have removed it for the "mov2_ccond" function (for "mov_cond" function it is not removed)? I suppose it's not very important but I'm just curious.
Hello there, is not my code, I am just consolidating code from the gurus, I really do not shy they are making the change I saw it and ask why, but no answer yet.
 
sys-patch can be run any time you like with a sysmodule manager. The off patch is useful if you cheat because as shipped dmnt don't have the flag and if you elevate games to higher level dmnt can no longer hack them.

Solution is either turn off the debug_flag with the off patch or use a dmnt with the debug flag set.
Hmm... I see...

But that's a nuisance for the final user...

I hope that only with debug_flag patch all will be ok.
 
Encontrei outra versão do package3 funcionando os forwarders, desta vez a splash screen tem apenas umas hashtags pedindo ajuda para a ukraine, bem melhor que a anterior do "costela br".
1729660292608.jpeg

Post automatically merged:

Just need to replace the package3 file in the atmosphere folder with the one I attached above.


And if anyone wants to try to remove the image, here is its source:
github . com /rashevskyv/Kefirosphere
apparently it is necessary to modify the file "stratosphere/boot/source/boot_splash_kefir.inc" which contains in each line a pixel of the image in binary form, and then build again.
Can anyone here do this?
 

Attachments

Last edited by SouORubsu,
Hmm... I see...

But that's a nuisance for the final user...

I hope that only with debug_flag patch all will be ok.
Yes definetively is a nuisance, now What we understand I Think the DEBUG_FLAG_OFF should be removed, and if the end user want disable the flag patch do it like any other, going on options disabling it and restarting the console.

What do you think should we remove it?
 
Hello everyone
I accidentally updated the switch to version 19.0.0 and unfortunately games and Tinfoil stopped running. I uploaded the latest version of atmopshere after 19.0 and sigipatches - no improvement. I also tried to reinstall Tinfail - unfortunately it doesn't run. I wanted to return to an earlier version of the Switch system 18.1.0 via Daybreak - an error related to information appears. Is there anything else I can do? I only enjoyed my Atmosphere for a few days :(

Some people wrote that removing Mission Control helps - how to do it?


EDIT:
I just uploaded the latest file from user impeez and the games started running. Tinfoil still doesn't work - does anyone have any ideas? Reinstallation didn't help. The message appears: A server communication error has occurred. Please try again later.
same happened to me. I updated my switch by mistake 2 weeks ago and haven't got it booted until last night after updating atmosphere, but then the games weren't working... I merged the 2 folders from the download link from Impeeza to the root of my switch sd and my games still won't start. it says "unable to start software rerun to home menu"... someone please help. peace and love
Post automatically merged:

if any knows a fix you're more than welcome to dm me please I just wanna play some games with the kiddos
 
Last edited by sillybillywilly,
same happened to me. I updated my switch by mistake 2 weeks ago and haven't got it booted until last night after updating atmosphere, but then the games weren't working... I merged the 2 folders from the download link from Impeeza to the root of my switch sd and my games still won't start. it says "unable to start software rerun to home menu"... someone please help. peace and love
Post automatically merged:

if any knows a fix you're more than welcome to dm me please I just wanna play some games with the kiddos
Heyyy, I accidentally updated a game in switch and boom I got fucked. Did what I could from updating hekate, atmosphere, sigpatches etc nothing worked. Tried this vid and everything went back to normal.
There might be some UI changes when you boot up hekate but other than that, everything is okay.
 
the game Eternights (without or with update) has a bug after installation everything is ok the game works but after restarting the console and therefore atmosphere it runs in a loop with verification it must be missing a patch or something in atmosphere and having to reinstall each time it restarts its not great everything is up to date atmo 1.8 and switch 19.0 and the latest sigpatch and sis patch ect its the only game that seems to pose a problem I haven't tested everything either but everything seems ok for the other

Does anyone have any idea how to fix it?


ps: the game also crashes dbi when selecting
 
Heyyy, I accidentally updated a game in switch and boom I got fucked. Did what I could from updating hekate, atmosphere, sigpatches etc nothing worked. Tried this vid and everything went back to normal.
There might be some UI changes when you boot up hekate but other than that, everything is okay.

never ever follow youtube videos thet are outdated the very same moment are published. please read and understand what you are doing.
 

Site & Scene News

Popular threads in this forum