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

  • Thread starter Thread starter ShadowOne333
  • Start date Start date
  • Views Views 5,197,155
  • Replies Replies 7,282
  • Likes Likes 266
Now, no loop but waiting...

signal-2025-12-16-174532_002.jpeg
 
which part of the guide?, on the guide you must to backup your emummc, sd files and others things.
@impeeza that of using the PC to back up the internal memory.
Post automatically merged:

Now, no loop but waiting...

View attachment 545787
@Metro City you need to use this
to eliminate the problem.
 
  • Like
Reactions: GoodmanBCN
Thanks for the support, I tried the mod version, the app works but it's in Chinese, no problem, I know how to read it a little :) I tried it anyway, restarted the console but it gives me the same error! Isn't it that I don't have good files? do you know where I can download the complete package? do you recommend this 21.0.0. or rather 21.1.0.?
 
@Metro City click on the image in my post above and you will be taken to the page where you can download Linkaho.
Yes, thank you, as I said previously it is in Chinese and the program started, but it didn't work for me, if I press a game it still loops :sad:

P.S. I found a working one v2.0.2, I disconnected the accounts, I start Mario Kart and it gives me an error it won't start, then I restart Linkalho, I reconnect the accounts and it stops me on wait...
 
Last edited by Metro City,
Yes, thank you, as I said previously it is in Chinese and the program started, but it didn't work for me, if I press a game it still loops :sad:
@Metro City mine isn't in chinese but in english
try this.
 

Attachments

Wow... Never seen!
isnt this the please wait loop just in italian if this is happening when you launch a game you need to use the linkhalo mod that i believe patches the sytem.ini in atmospher i was under the impressi0n that trhis happens because the switch is trying to reach out to nintendo servers but cant so it gets stuck in a loop which is also why putting it in airplane mode works also if ia m wrong about this in this case please feel free to correct me
 
@Metro City mine isn't in chinese but in english
try this.
Thanks for your help. I'll try this myself tonight, time permitting. I was going to "heart" your post, but the default for that is the heart eyes, which is strange. My eyes are not doing that. So I left a like.
 
  • Like
Reactions: NeoGranzon
Yes, thank you, as I said previously it is in Chinese and the program started, but it didn't work for me, if I press a game it still loops :sad:

P.S. I found a working one v2.0.2, I disconnected the accounts, I start Mario Kart and it gives me an error it won't start, then I restart Linkalho, I reconnect the accounts and it stops me on wait...
Try to iníciate the game with airplane Mode on
 
  • Like
Reactions: impeeza
Thanks for your help. I'll try this myself tonight, time permitting. I was going to "heart" your post, but the default for that is the heart eyes, which is strange. My eyes are not doing that. So I left a like.
@TPMJB i try to make myself as helpful as others if i can,since i've been part of this community for a while now.
Yes, thank you, as I said previously it is in Chinese and the program started, but it didn't work for me, if I press a game it still loops :sad:

P.S. I found a working one v2.0.2, I disconnected the accounts, I start Mario Kart and it gives me an error it won't start, then I restart Linkalho, I reconnect the accounts and it stops me on wait...
@Metro City did you set your DNS like this in your internet settings?
2025121706370000-0C7E8798D2996597BAFD59B427BF6132.jpg
 
Hi everyone, can anyone help me? when I launch a game it blinks in a loop like this. I updated to fw 21.0.0 with AMS 1.10.05
someone in a previous page mentioned that "you need to use "linkhalo" mod update to unlink and relink your account" to fix this looping. i haven't tried it myself because i downgraded firmware
 
*** Updated 2025 - 08 - 12 ***

Sigpatches updated for 21.1.0,

And Upgraded to Atmosphère 1.10.1

SYS-Patch should work fine with this FW too.
sys patch log shows

noncasigchk_new Unpatched
nocntchk2 Unpatched
noacidsigchk Patched (Green)
no_erpt Patched (Green)
es4 Unpatched
ctest3 Unpatched
nim_new Patched (Yellow)
disablecaverification1 Patched (Green)
disablecaverification2 Patched (Green)
disablecaverification3 Unpatched

version 1.5.8-8d4d183

fw version 21.1.0
ams_version 1.10.1
ams_target_version 1.0.0
ams_keygen 20




this is WITH the current BETA Sigpatches (Hekate+AMS-package3-sigpatches-1.10.1P-cfw-21.1.0_V0). is this normal to have so many Unpatched?
 
sys patch log shows

noncasigchk_new Unpatched
nocntchk2 Unpatched
noacidsigchk Patched (Green)
no_erpt Patched (Green)
es4 Unpatched
ctest3 Unpatched
nim_new Patched (Yellow)
disablecaverification1 Patched (Green)
disablecaverification2 Patched (Green)
disablecaverification3 Unpatched

version 1.5.8-8d4d183

fw version 21.1.0
ams_version 1.10.1
ams_target_version 1.0.0
ams_keygen 20




this is WITH the current BETA Sigpatches (Hekate+AMS-package3-sigpatches-1.10.1P-cfw-21.1.0_V0). is this normal to have so many Unpatched?
IPS patch detection is broken, it will say unpatched even if it was patched with IPS, you should disregard the log infomation. The trouble with the program is this:
1: It scans memory with a wildcard or fixed pattern for unpatched/untouched areas in memory.
2: IPS patches get applied before we scan the memory.
3: Because memory is already patched with IPS it's not "clean" anymore, so we can't find the pattern so it says unpatched.
4: To fix we need to scan memory again if we fail with the original pattern, then use a new pattern with the patch code inside the search pattern, we don't do this and that's why the IPS detection is broken.
5: Sometimes it will detect it's IPS patched when some bytes are changed in memory that are not patched with our patches but make it think it is because now it will match the wildcard pattern.

Just ignore the logs (unless using without any IPS patches). If using without IPS patches or bootloader/patches.ini (for fs and ldr) then the logs will be correct. You don't need IPS patches if using the same patch that this program patches, you can still use exefs IPS patches for other things, like game patching.
 
IPS patch detection is broken, it will say unpatched even if it was patched with IPS, you should disregard the log infomation. The trouble with the program is this:
1: It scans memory with a wildcard or fixed pattern for unpatched/untouched areas in memory.
2: IPS patches get applied before we scan the memory.
3: Because memory is already patched with IPS it's not "clean" anymore, so we can't find the pattern so it says unpatched.
4: To fix we need to scan memory again if we fail with the original pattern, then use a new pattern with the patch code inside the search pattern, we don't do this and that's why the IPS detection is broken.
5: Sometimes it will detect it's IPS patched when some bytes are changed in memory that are not patched with our patches but make it think it is because now it will match the wildcard pattern.

Just ignore the logs (unless using without any IPS patches). If using without IPS patches or bootloader/patches.ini (for fs and ldr) then the logs will be correct. You don't need IPS patches if using the same patch that this program patches, you can still use exefs IPS patches for other things, like game patching.
ok so issues with error 2168-0001 and 2168-0003 are not sigpatch (sys patch) related?
 

Site & Scene News

Popular threads in this forum