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

[impeeza]

When I install the Vampire Survivors NSP game and update (1.10.102) then open the game I get this

https://gbatemp.net/threads/sigpatches-for-atmosphere-hekate-fss0-fusee-package3.571543/post-9162146

and depending the installarion method you are using I do recommend to continuate the question on the installator thread.

 

[Blythe93]

When I install the Vampire Survivors NSP game and update (1.10.102) then open the game I get this

I usually clear the system cache whenever that error appears on my Switch (happened to me 2-3 times so far, so not that much?).
Do the following:

1. Make sure that your Internet connection is disabled if you're connected right now and remove any saved connections as well (unless you have DNS MITM in place).
2. Turn off your console (when in home menu, hold the power button for a few seconds and select power off).
3. Right before you send your fusee.bin payload, hold volume + and volume - at the same time. Keep holding until you get into maintenance mode (you'll see Atmosphere bootlogo first, Switch logo after that one). After a while your Switch should enter into the maintenance mode. At this point any pending updates and cache is cleared, you don't need to press and/or select anything.
4. Press the power button once again. It'll shut down the console.
5. Boot into CFW the way you usually do and make sure to activate flight mode. (Connecting to the Internet is safe only if you have DNS MITM in place.)
6. Hopefully, you won't see the error anymore.

Otherwise, check the troubleshooting thread that impeeza posted for more possible fixes.

 

[cta]

I usually clear the system cache whenever that error appears on my Switch (happened to me 2-3 times so far, so not that much?).
Do the following:

1. Make sure that your Internet connection is disabled if you're connected right now and remove any saved connections as well (unless you have DNS MITM in place).
2. Turn off your console (when in home menu, hold the power button for a few seconds and select power off).
3. Right before you send your fusee.bin payload, hold volume + and volume - at the same time. Keep holding until you get into maintenance mode (you'll see Atmosphere bootlogo first, Switch logo after that one). After a while your Switch should enter into the maintenance mode. At this point any pending updates and cache is cleared, you don't need to press and/or select anything.
4. Press the power button once again. It'll shut down the console.
5. Boot into CFW the way you usually do and make sure to activate flight mode. (Connecting to the Internet is safe only if you have DNS MITM in place.)
6. Hopefully, you won't see the error anymore.

Otherwise, check the troubleshooting thread that impeeza posted for more possible fixes.

That worked! Been trying to fix this all weekend long. Thank you!. Thanks to everybody else who tried to help

 

[impeeza]

That worked! Been trying to fix this all weekend long. Thank you!. Thanks to everybody else who tried to help

you can also delete all that pending files using DBI or Checkpoint.

 

[warquezho]

I am on v18.1 and have switch v1 unpatch. I read that using fussee.bin can bypass hekate. I followed instructions from here, put fussee.bin (from atmosphere in git) in sd:\bootloader\payloads, Then Iaunch tegra, inject hekate.bin but still goes hekate instead of atmosphere directly?

How to do boot to atmosphere directly? I have emuNand setup.

 

[impeeza]

I am on v18.1 and have switch v1 unpatch. I read that using fussee.bin can bypass hekate. I followed instructions from here, put fussee.bin (from atmosphere in git) in sd:\bootloader\payloads, Then Iaunch tegra, inject hekate.bin but still goes hekate instead of atmosphere directly?

How to do boot to atmosphere directly? I have emuNand setup.

View attachment 449074

Go to the correct thread this is about sigpatches no console bootloader.

please read this post: https://gbatemp.net/threads/sigpatc...kate-fss0-fusee-package3.571543/post-10291762

and do not forget to read the guide:
Guide: https://rentry.org/SwitchHackingIsEasy

your post show us you do not have the basic concepts clear.

 

[warquezho]

Go to the correct thread this is about sigpatches no console bootloader.

please read this post: https://gbatemp.net/threads/sigpatc...kate-fss0-fusee-package3.571543/post-10291762

and do not forget to read the guide:
Guide: https://rentry.org/SwitchHackingIsEasy

your post show us you do not have the basic concepts clear.

yeah I just recently use switch, thank for this Guide: https://rentry.org/SwitchHackingIsEasy. I only use the guide I posted pic above with some information here.

---
I can boot to atmosphere:

directly by tegra -> fussee.bin
indirectly tegra -> hekate -> launch -> sd emunand

I was just thinking what this chain loading that I am reading. I don't have fusee.bin anywhere in my sd:/ but I am reading and seeing some guides that they have it in sd:/bootloader/payloads.

I also notice that sys-patch module 1.5.2 you posted is enough for either hekate and fusee load games. But when I only use the sigpatches you post here https://gbatemp.net/threads/sigpatc...-fusee-package3.571543/page-177#post-10438165, only loading games with hekate works, not working with fusee and corrupts the game. I read maybe because exefs_patches and kip_patches is not being used by hekate, but fusee does. So I stick with your sys-patch module 1.5.2 for now until I need the sigpatches.

Post automatically merged: Jul 25, 2024

And doing further backread and testing, seems like using the modified fusee.bin from https://gbatemp.net/threads/sigpatc...-fusee-package3.571543/page-172#post-10437379 solves the issue when only Sigpatches are applied

 

[Lamcza]

you can also delete all that pending files using DBI or Checkpoint.

by cleaning orphaned files or what?

Post automatically merged: Jul 26, 2024

yeah I just recently use switch, thank for this Guide: https://rentry.org/SwitchHackingIsEasy. I only use the guide I posted pic above with some information here.

---
I can boot to atmosphere:

directly by tegra -> fussee.bin
indirectly tegra -> hekate -> launch -> sd emunand

I was just thinking what this chain loading that I am reading. I don't have fusee.bin anywhere in my sd:/ but I am reading and seeing some guides that they have it in sd:/bootloader/payloads.

I also notice that sys-patch module 1.5.2 you posted is enough for either hekate and fusee load games. But when I only use the sigpatches you post here https://gbatemp.net/threads/sigpatc...-fusee-package3.571543/page-177#post-10438165, only loading games with hekate works, not working with fusee and corrupts the game. I read maybe because exefs_patches and kip_patches is not being used by hekate, but fusee does. So I stick with your sys-patch module 1.5.2 for now until I need the sigpatches.

Post automatically merged: Jul 25, 2024

And doing further backread and testing, seems like using the modified fusee.bin from https://gbatemp.net/threads/sigpatc...-fusee-package3.571543/page-172#post-10437379 solves the issue when only Sigpatches are applied

hmm how do you even booting viu fusee i have only quick splash of atmo logo and thats it black screen aa ok i should probably try this https://gbatemp.net/threads/sigpatc...kate-fss0-fusee-package3.571543/post-10291762

 

[sobasoba]

Hi there, I'm in need of a bit of troubleshooting. Updated to latest atmosphere, firmware and sigpatches including the sys-patch modules.

I'm experiencing massive slowdowns on boot (it hangs on the switch logo for very long) and overall whatever I open, homebrew menu included, takes forever to load. Installing software with NUT takes forever (1 to 3 mbp/s transfer speed) it happened just after this update, was previously sitting on a atmosphere 1.6.2 and 17.0.1 fw build

Tried to disable the syspatches because I know that sys modules can add onto loading times, but at this point I'm wondering if super coincidentially the sd half-died during the cfw update process, which seemed to be going smooth by the way.

Has this happened to anyone else?

 

[impeeza]

Hi there, I'm in need of a bit of troubleshooting. Updated to latest atmosphere, firmware and sigpatches including the sys-patch modules.

I'm experiencing massive slowdowns on boot (it hangs on the switch logo for very long) and overall whatever I open, homebrew menu included, takes forever to load. Installing software with NUT takes forever (1 to 3 mbp/s transfer speed) it happened just after this update, was previously sitting on a atmosphere 1.6.2 and 17.0.1 fw build

Tried to disable the syspatches because I know that sys modules can add onto loading times, but at this point I'm wondering if super coincidentially the sd half-died during the cfw update process, which seemed to be going smooth by the way.

Has this happened to anyone else?

No and has nothing to do with sigpatches, could you go to https://gbatemp.net/threads/switch-noob-paradise-ask-questions-here.488277 and do not try to hijack a unrelated thread.

 

[sobasoba]

No and has nothing to do with sigpatches, could you go to link and do not try to hijack a unrelated thread.

sorry about that, since it happened while adding sys patches and tesla for the first time I thought it might have something to do with it, but evidently not

 

[dragonneus]

******************************************************************
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 am about too lose my mind. 8+ hrs now trying, even with a fresh install and rehack. I can dump the games fine and even used the hecate sigpatches here. I am still getting "insert the game card". Please before I throw this switch against the wall, what could I possibly be missing here?

 

[impeeza]

I am about too lose my mind. 8+ hrs now trying, even with a fresh install and rehack. I can dump the games fine and even used the hecate sigpatches here. I am still getting "insert the game card". Please before I throw this switch against the wall, what could I possibly be missing here?

a damage card reader or fpga connector

 

[Stormflora]

Hi all. Just before I go ahead and update my Switch to the latest everything, is there anything I should keep in mind about the current versions of Hekate/Atmosphere/sigpatch/etc.?

I am currently on 17.0.1|AMS 1.6.2 on my emuNAND. Works perfectly fine with everything set up. But that's old news now.

Will I encounter any issues updating Hekate, Atmosphere and the sigpatches by replacing the files on the SD with the latest releases of those, and using Daybreak to install OFW 18.1.0 on the emuNAND?

Also, do the Exosphere + DNS MITM and NIM ProdInfo Fix things need updating as well? Or do they rollover to the latest FW?

Thanks everyone. Just want to make sure there aren't any weird problems I might overlook with the latest 18.1.0 FW.

 

[impeeza]

Hi all. Just before I go ahead and update my Switch to the latest everything, is there anything I should keep in mind about the current versions of Hekate/Atmosphere/sigpatch/etc.?

I am currently on 17.0.1|AMS 1.6.2 on my emuNAND. Works perfectly fine with everything set up. But that's old news now.

Will I encounter any issues updating Hekate, Atmosphere and the sigpatches by replacing the files on the SD with the latest releases of those, and using Daybreak to install OFW 18.1.0 on the emuNAND?

Also, do the Exosphere + DNS MITM and NIM ProdInfo Fix things need updating as well? Or do they rollover to the latest FW?

Thanks everyone. Just want to make sure there aren't any weird problems I might overlook with the latest 18.1.0 FW.

Really there is no major issues, but always you must to upgrade Atmosphère and Hekate BEFORE upgrade the firmware.

A detailed steps are on:
https://gbatemp.net/threads/firmware-and-nand-questions.612782/post-9835101

A very comprehensive guide on:
https://gbatemp.net/threads/updating-hekate-atmosphere-and-hos.631739/


upgrade any SYS-Module, and sigpatches also when upgrading Atmosphère and be sure remove themes before.

 

[Stormflora]

Really there is no major issues, but always you must to upgrade Atmosphère and Hekate BEFORE upgrade the firmware.

A detailed steps are on:
https://gbatemp.net/threads/firmware-and-nand-questions.612782/post-9835101

A very comprehensive guide on:
https://gbatemp.net/threads/updating-hekate-atmosphere-and-hos.631739/


upgrade any SYS-Module, and sigpatches also when upgrading Atmosphère and be sure remove themes before.

Hi Impeeza, thanks for the confirmation!

I have done firmware updates a few times in the past, so it is not foreign territory to me. But I was simply asking to make sure nothing funky may happen when trying to go to 18.1.0 with the same process.

I don't have anything fancy installed on my Switch, so sys-modules and themes will not be an issue for me.

Anywho, update time

Post automatically merged: Jul 29, 2024

Popping in again to say that the update went flawlessly, without issue. Thanks @impeeza!

All I did was update Hekate, Atmosphere, and the sigpatches by overwriting the old files on the SD card, and then I updated the firmware to 18.1.0 via Daybreak.

I also updated the NIM ProdInfo Fix, as that had been changed. The Exosphere thing remained the same.

Luigi's Mansion 2 HD runs just fine on this Switch, and it apparently required FW 18.0.0.

See you again in a few months time when the next few Nintendo games are released and the OFW gets updated again.

 

[osaka35]

******************************************************************
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)

If you'd like to create a new thread (for maintaining the sig patches), let me know and I'll take care of all the forwarding/redirecting to the new thread. might help with all the questions you're getting inundated with as well. Let me know if I can help with any of the making of it.

 

[impeeza]

If you'd like to create a new thread (for maintaining the sig patches), let me know and I'll take care of all the forwarding/redirecting to the new thread. might help with all the questions you're getting inundated with as well. Let me know if I can help with any of the making of it.

Thank you brother, I don't know what is better, but you are right this thread is crowded with lots of repeated questions. so many people asking the exactly same.

As far I understand you, your proposal is create a new thread with the sigpatches and instructions about their installations, and leave this for further questions?

 

[osaka35]

Thank you brother, I don't know what is better, but you are right this thread is crowded with lots of repeated questions. so many people asking the exactly same.

As far I understand you, your proposal is create a new thread with the sigpatches and instructions about their installations, and leave this for further questions?

absolutely. that could work. i could disable comments on the new thread, and just tell people to ask questions in this one.

another option is to just disable this thread and move the discussions and postings over to a new thread. I would setup a fowarder in this thread to go to the new one.

Really, whatever you think would make your life easier.

 

[impeeza]

absolutely. that could work. i could disable comments on the new thread, and just tell people to ask questions in this one.

another option is to just disable this thread and move the discussions and postings over to a new thread. I would setup a fowarder in this thread to go to the new one.

Really, whatever you think would make your life easier.

Let me to talk with @ShadowOne333 and back to you, thanks a lot.