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

whitezombie

Well-Known Member
Newcomer
Joined
Apr 11, 2021
Messages
85
Trophies
0
XP
1,174
Country
United States
I do not understand what it is that I am doing wrong. I'll keep trying, but fortunately everything works flawlessly with sys-patch 1.5.2 or when using the sigpatches and booting with the modded version of fusee.bin.

Let's hope nothing breaks in the future!
Are you trying to use package3, sig patches, no sys-patch, or the unmodified fusee? I'm confused about what you are doing. Can you tell me more about your package3 set up , does Atmosphere not load, or games don't load?
 
Last edited by whitezombie,
  • Haha
Reactions: impeeza

impeeza

¡Kabito!
Member
Joined
Apr 5, 2011
Messages
6,743
Trophies
3
Age
46
Location
At my chair.
XP
20,255
Country
Colombia
all patched green but es7 is yellow
Post automatically merged:

#loader Atmosphere-1.07.1+FS Reenabled
[Loader:18B4834FE41572D5]
.nosigchk=0:0x5FBE:0x1:01,00

now is booting with no error
but nosigchk = patched yellow
Yellow means was already patched before running SYS-Patch sysmodule
 

alcab

Well-Known Member
Member
Joined
Nov 22, 2005
Messages
222
Trophies
1
Website
Visit site
XP
1,145
Country
Are you trying to use package3, sig patches, no sys-patch, or the unmodified fusee? I'm confused about what you are doing. Can you tell me more about your set up, does Atmosphere not load, or games don't load?

Ok. I was rebooting using hekate toolbox, and this is what happened:

When booting EmuMMC, console boots fine, but sigpatches do not work.
When booting EmuMMC, console boots fine, and games do work if I activate sys-patch.

When booting modded fusee, console boots fine, and sigpatches work flawlessly.
When booting modded fusee, console boots fine, and sys-patch works fine

BUT, when turning off the console and then injecting hekate I get this message:
HOS Panic ocurred!
Color "BLUE", code 01
Press any key...

If I inject fusee.bin, Switch boots just fine.

Thanks.
 

whitezombie

Well-Known Member
Newcomer
Joined
Apr 11, 2021
Messages
85
Trophies
0
XP
1,174
Country
United States
Ok. I was rebooting using hekate toolbox, and this is what happened:

When booting EmuMMC, console boots fine, but sigpatches do not work.
When booting EmuMMC, console boots fine, and games do work if I activate sys-patch.

When booting modded fusee, console boots fine, and sigpatches work flawlessly.
When booting modded fusee, console boots fine, and sys-patch works fine

BUT, when turning off the console and then injecting hekate I get this message:
HOS Panic ocurred!
Color "BLUE", code 01
Press any key...

If I inject fusee.bin, Switch boots just fine.

Thanks.

I am not sure why your boot package3 and sig patches don't work. There are so many things I don't know about your set up, like the hekate_ipl.ini file, and overlays.

HOS Panic ocurred! seems like you have old Hekate or Atmosphere files. I would back up your Atmosphere folder and bootloader folder to the PC, delete them on the Switch SD card, and put clean copies on the Switch with no overlays to debug.

https://github.com/CTCaer/hekate/issues/949
 
Last edited by whitezombie,
  • Like
  • Love
Reactions: alcab and impeeza

alcab

Well-Known Member
Member
Joined
Nov 22, 2005
Messages
222
Trophies
1
Website
Visit site
XP
1,145
Country
I'll keep trying later today, but last attempt was using a clean install (I renamed atmosphere and bootloader folders and unzipped the contents of the zip files posted by impeeza). hekate_ipl.ini file I used was the one provided by his sigpatches.
I am completely lost with this issue.

These are the files I am using:
sigpatches
Atmosphere
Hekate (v3)

This afternoon I'll try again using this Atmosphere
https://github.com/Atmosphere-NX/Atmosphere/releases/tag/1.7.1

I am injecting fusee.bin or hekate.bin using Rekado. I will also try to inject them using another method to see what happens. But I am running out of ideas...

Thanks a lot.

EDIT: I am beginning to see the light at the end of the tunnel. Problem was related to rekado (the tool I use to inject the payload). For some reason it automatically downloaded a bad version of hekate.bin.

Injecting the last version of hekate (v3) with tegraRCMGui solved my problem. Sigpatches work perfectly (although I had to disable my exosphere.ini file, because it made my system to crash when connected to the net).

Sorry for bothering you with an issue that was obviously my fault.
 
Last edited by alcab,

teethmarks

Active Member
Newcomer
Joined
Feb 10, 2019
Messages
25
Trophies
0
Age
56
XP
163
Country
Antarctica
im having a problem that i suspect could be related to sigpatches.
certain game backups, even after deleting and reinstalling, say unable to start software and then give me the corrupted data check when i try to run again. i am at my wits end with this issue, does any one have any idea what could be wrong? im running latest atmosphere, latest sigpatches from this thread. ive wiped the atmosphere folder completely and even tried changing sdcards. please help!
 

dogtygr

Active Member
Newcomer
Joined
May 30, 2023
Messages
43
Trophies
0
XP
111
Country
United States
I'll keep trying later today, but last attempt was using a clean install (I renamed atmosphere and bootloader folders and unzipped the contents of the zip files posted by impeeza). hekate_ipl.ini file I used was the one provided by his sigpatches.
I am completely lost with this issue.

These are the files I am using:
sigpatches
Atmosphere
Hekate (v3)

This afternoon I'll try again using this Atmosphere
https://github.com/Atmosphere-NX/Atmosphere/releases/tag/1.7.1

I am injecting fusee.bin or hekate.bin using Rekado. I will also try to inject them using another method to see what happens. But I am running out of ideas...

Thanks a lot.

EDIT: I am beginning to see the light at the end of the tunnel. Problem was related to rekado (the tool I use to inject the payload). For some reason it automatically downloaded a bad version of hekate.bin.

Injecting the last version of hekate (v3) with tegraRCMGui solved my problem. Sigpatches work perfectly (although I had to disable my exosphere.ini file, because it made my system to crash when connected to the net).

Sorry for bothering you with an issue that was obviously my fault.
If you're using emummc I highly advise you to find why exosphere crashes when you try to connect to the net than disabling it.
 
  • Like
Reactions: alcab

RedColoredStars

Well-Known Member
Member
Joined
Aug 14, 2022
Messages
1,237
Trophies
1
Location
Angoche
XP
1,665
Country
Mozambique
im having a problem that i suspect could be related to sigpatches.
certain game backups, even after deleting and reinstalling, say unable to start software and then give me the corrupted data check when i try to run again. i am at my wits end with this issue, does any one have any idea what could be wrong? im running latest atmosphere, latest sigpatches from this thread. ive wiped the atmosphere folder completely and even tried changing sdcards. please help!

Did you run the corrupted data check? Is your SD card Fat32 or ExFat? Did you also update Hekate and your payload? Have you tried with sys-patch instead of sigpatches? Are you positive your nsp/xci's aren't bad?
 

teethmarks

Active Member
Newcomer
Joined
Feb 10, 2019
Messages
25
Trophies
0
Age
56
XP
163
Country
Antarctica
Did you run the corrupted data check? Is your SD card Fat32 or ExFat? Did you also update Hekate and your payload? Have you tried with sys-patch instead of sigpatches? Are you positive your nsp/xci's aren't bad?
i have and it does not find corrupted data but requires reinstall and the process starts over. fat 32. when i update atmosphere i also update fusee. ive never had to update hekate for a atmosphere install am i missing something. have not tried sys-patch. these nsps have worked in the past and on onther devices.
 

RedColoredStars

Well-Known Member
Member
Joined
Aug 14, 2022
Messages
1,237
Trophies
1
Location
Angoche
XP
1,665
Country
Mozambique
i have and it does not find corrupted data but requires reinstall and the process starts over. fat 32. when i update atmosphere i also update fusee. ive never had to update hekate for a atmosphere install am i missing something. have not tried sys-patch. these nsps have worked in the past and on onther devices.

First thing I would try is updating Hekate. Both on your SD card and also for your payloader method. Also, when you update Atmosphere be sure you rename a copy of the latest hekate_ctcaer bin file to reboot_payload.bin and place it in your atmosphere folder. Overwrite any existing one that may already be in there.

If that doesn't work, come back and post the contents of your hekate_ipl.ini and can go from there.
 

whitezombie

Well-Known Member
Newcomer
Joined
Apr 11, 2021
Messages
85
Trophies
0
XP
1,174
Country
United States
EDIT: I am beginning to see the light at the end of the tunnel. Problem was related to rekado (the tool I use to inject the payload). For some reason it automatically downloaded a bad version of hekate.bin.

Injecting the last version of hekate (v3) with tegraRCMGui solved my problem. Sigpatches work perfectly (although I had to disable my exosphere.ini file, because it made my system to crash when connected to the net).

Sorry for bothering you with an issue that was obviously my fault.
Glad you fixed your issue! I never heard of Rekado as I always used TegraRcmGUI (I learn something new here everyday!). That's the problem when things auto download, they are never up to date until the author updates the tool. I always get the Atmoshpere and Hekate files from their Github.
 
  • Like
Reactions: alcab

teethmarks

Active Member
Newcomer
Joined
Feb 10, 2019
Messages
25
Trophies
0
Age
56
XP
163
Country
Antarctica
First thing I would try is updating Hekate. Both on your SD card and also for your payloader method. Also, when you update Atmosphere be sure you rename a copy of the latest hekate_ctcaer bin file to reboot_payload.bin and place it in your atmosphere folder. Overwrite any existing one that may already be in there.

If that doesn't work, come back and post the contents of your hekate_ipl.ini and can go from there.
i downloaded the latest hekate, launched with hekate via tegra, did another corrupted data check and launched after it found no corruption. and it worked? i have no idea what is going on. what did launching atmosphere via fusee do differently than launching with hekate?
 

RedColoredStars

Well-Known Member
Member
Joined
Aug 14, 2022
Messages
1,237
Trophies
1
Location
Angoche
XP
1,665
Country
Mozambique
EDIT: I am beginning to see the light at the end of the tunnel. Problem was related to rekado (the tool I use to inject the payload). For some reason it automatically downloaded a bad version of hekate.bin.

That was fixed very quickly by the Rekado dev. It updated when the first version of Hekate 6.2.0 was released, but since the version numbers didn't change Rekado thought it was already up to date and didn't pull the fixed version. It was reported on the git and fixed near immediately. You just needed to use "Check for updates" in Rekado. :)
 

whitezombie

Well-Known Member
Newcomer
Joined
Apr 11, 2021
Messages
85
Trophies
0
XP
1,174
Country
United States
i have and it does not find corrupted data but requires reinstall and the process starts over. fat 32. when i update atmosphere i also update fusee. ive never had to update hekate for a atmosphere install am i missing something. have not tried sys-patch. these nsps have worked in the past and on onther devices.
Always update Hekate when you update Atmosphere.
 

RedColoredStars

Well-Known Member
Member
Joined
Aug 14, 2022
Messages
1,237
Trophies
1
Location
Angoche
XP
1,665
Country
Mozambique
i downloaded the latest hekate, launched with hekate via tegra, did another corrupted data check and launched after it found no corruption. and it worked? i have no idea what is going on. what did launching atmosphere via fusee do differently than launching with hekate?

My best guess is when you updated fusee you used stock vanilla release? It no longer supports sigpatches so you have to use a modified fusee, sys-patch, or boot with hekates fss0.
 

Jakkal666

Well-Known Member
Newcomer
Joined
Jul 14, 2018
Messages
49
Trophies
0
XP
225
Country
Sweden
******************************************************************
IMPORTANT
******************************************************************

With the help of:






A NEW SET OF SIGPATCHES FOR 18.1.0 has been created some changed and some where added. PLEASE TAKE NOTE AND UPGRADE YOURS (Note V2 was added to the end of the new file)
Just curious, is anyone able to play Super Mario Bros Wonder and Mario Kart 8 Deluxe using these sigpatches on FW 18.1.0 and Atmosphere 1.7.1? Gave me errors with invalid NCA tickets and corrupted data on these two specific titles.

Update:
Used the modified fusee.bin posted by Krejza9, which I also renamed to and used as reboot_payload.bin and everything seems to work.
Quite a hassle getting stuff running when returning to and updating the system once half-a-year.

 
Last edited by Jakkal666,

LordK77

Well-Known Member
Newcomer
Joined
Nov 9, 2020
Messages
55
Trophies
0
XP
931
Country
Brazil
******************************************************************
IMPORTANT
******************************************************************

With the help of:






A NEW SET OF SIGPATCHES FOR 18.1.0 has been created some changed and some where added. PLEASE TAKE NOTE AND UPGRADE YOURS (Note V2 was added to the end of the new file)
I updated in cnx update to cnx 18.1.0-1 ams 1.7.1 (11-06-2024) When the installation completed and restarted, this appears: Emummc is forced but not enabled! failed to launch hos!press any key...What can I do to fix this? Thanks! I don't use emunand, but sysnand
 
Last edited by LordK77,

condector

Member
Newcomer
Joined
Jan 5, 2022
Messages
17
Trophies
0
XP
62
Country
Brazil
I updated in cnx update to cnx 18.1.0-1 ams 1.7.1 (11-06-2024) When the installation completed and restarted, this appears: Emummc is forced but not enabled! failed to launch hos!press any key...What can I do to fix this? Thanks! I don't use emunand, but sysnand
If you're unsure why emuMMC is required, consider reaching out to the package developer. They can explain the specific risks involved and help you decide the best course of action. If the package requires emuMMC, it's best to use it for safety and to avoid potential bans. Bypassing emuMMC might seem convenient, but it could have unintended consequences.

While the Hekate documentation (https://github.com/CTCaer/hekate/releases/) might explain how to bypass emuMMC, it's generally not recommended. The developer likely has a good reason for requiring it, and ignoring it could lead to issues.
 

impeeza

¡Kabito!
Member
Joined
Apr 5, 2011
Messages
6,743
Trophies
3
Age
46
Location
At my chair.
XP
20,255
Country
Colombia
I updated in cnx update to cnx 18.1.0-1 ams 1.7.1 (11-06-2024) When the installation completed and restarted, this appears: Emummc is forced but not enabled! failed to launch hos!press any key...What can I do to fix this? Thanks! I don't use emunand, but sysnand

If you're unsure why emuMMC is required, consider reaching out to the package developer. They can explain the specific risks involved and help you decide the best course of action. If the package requires emuMMC, it's best to use it for safety and to avoid potential bans. Bypassing emuMMC might seem convenient, but it could have unintended consequences.

While the Hekate documentation (https://github.com/CTCaer/hekate/releases/) might explain how to bypass emuMMC, it's generally not recommended. The developer likely has a good reason for requiring it, and ignoring it could lead to issues.
You really should stay away of all in one packages IF YOU DON'T KNOW REALLY WHAT EACH THING IS AND HOW WORKS. read the https://rentry.org/SwitchHackingIsEasy guide to understand the basics and then you can handle your console by yourself.
 
Last edited by impeeza,

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • No one is chatting at the moment.
    Psionic Roshambo @ Psionic Roshambo: Ughhhh so hard to find, "Marmalade Boy" lol my girlfriend wants this weird movie.... I wonder if...