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

  • Thread starter Thread starter ShadowOne333
  • Start date Start date
  • Views Views 5,316,624
  • Replies Replies 7,368
  • Likes Likes 266
dont try to update your sysnand with day break for that you will have to use nintendos servers to update otherwise you risk a ban for sysnand you will have no choice to update to 21.01 but as long as you have the latest hekate you should be fine
Yes that I know.

The issue I'm running into now is that I want to use Daybreak to install 21.0.0, but OFW version is 21.0.1. So if i update my EMUMMC to 21.0.0 manually using daybreak, when I go to install an update on OFW with Nintendo's official servers, my OFW will be 21.0.1, and the emummc version will be different than my SYS. Does this matter at all? Can't really find a full answer anywhere online.
 
Yes that I know.

The issue I'm running into now is that I want to use Daybreak to install 21.0.0, but OFW version is 21.0.1. So if i update my EMUMMC to 21.0.0 manually using daybreak, when I go to install an update on OFW with Nintendo's official servers, my OFW will be 21.0.1, and the emummc version will be different than my SYS. Does this matter at all? Can't really find a full answer anywhere online.
no this does not matter you can have two different versions think of it as running two different switches on the same hardware
 
Either that or use Sys-Patch (recommended)

Yeah I may have just screwed up I got fatal error I transfered files over atmosphere 20.5 and firmware 20.5 installed via daybreak.
Post automatically merged:

So I forgot to copy the files from hekate and now I can't boot into hekate and I don't have an sd card reader. Is there any payloads I can use to boot via usb into my sd card?
 
Last edited by Jayinem,
Yeah I may have just screwed up I got fatal error I transfered files over atmosphere 20.5 and firmware 20.5 installed via daybreak.
Post automatically merged:

So I forgot to copy the files from hekate and now I can't boot into hekate and I don't have an sd card reader. Is there any payloads I can use to boot via usb into my sd card?
you can send hekate_ctcaer_xxx.bin to your console with TegraRcmGUI
 
  • Like
Reactions: Jayinem
Forgive the ignorance here. I've never had any issues before now with this sort of thing so this is one of my first times posting.

I'm assuming the latest sigpatches are 1.9.5 and there is nothing for 1.10 based on this thread?

I've successfully updated hekate and atmosphere so I can boot in but getting the nosig error. I obviously should have just updated to 1.9.5 but I went a step too far.

I'm assuming because I updated at this point, I need to watch for a stable atmosphere release and sig patches to correspond to them?

Any help would be welcome.
 
Forgive the ignorance here. I've never had any issues before now with this sort of thing so this is one of my first times posting.

I'm assuming the latest sigpatches are 1.9.5 and there is nothing for 1.10 based on this thread?

I've successfully updated hekate and atmosphere so I can boot in but getting the nosig error. I obviously should have just updated to 1.9.5 but I went a step too far.

I'm assuming because I updated at this point, I need to watch for a stable atmosphere release and sig patches to correspond to them?

Any help would be welcome.

I used to only get sigpatches when updating, I switched to syspatch for FW 21.0.1 since it's "simpler" and didn't regret it so far.

My advice is :

- remove anything related to sigpatches (folders in atmosphere directory, patches.ini in hekate and so on => check the folders & files that sigpatches add, and remove only those)
- get the latest syspatch release (impeeza github, latest with the "-v5" in the filename)
- get latest hekate & atmosphere, even if the later is still in "pre-release" state (if you're on older FW than 21, it'll still work)
- edit you hekate IPL file and remove the line kip1patch=nosigchk

If I recall correctly, I had this type of problem only once, when I updated only one and not the other (mismatch between atmosphere / stigpatches).
 
  • Love
Reactions: mcjmetroid
I used to only get sigpatches when updating, I switched to syspatch for FW 21.0.1 since it's "simpler" and didn't regret it so far.

My advice is :

- remove anything related to sigpatches (folders in atmosphere directory, patches.ini in hekate and so on => check the folders & files that sigpatches add, and remove only those)
- get the latest syspatch release (impeeza github, latest with the "-v5" in the filename)
- get latest hekate & atmosphere, even if the later is still in "pre-release" state (if you're on older FW than 21, it'll still work)
- edit you hekate IPL file and remove the line kip1patch=nosigchk

If I recall correctly, I had this type of problem only once, when I updated only one and not the other (mismatch between atmosphere / stigpatches).
Thank you very much editing the Hekate IPL file worked. Very odd.
It also rings a bell. I think I had to do this once before as well.

Thanks again
 
My switch is on 21.0.1 how can I dawngrade from 21.0.1 to 20.5?
It will probably crash and get stuck in a boot loop if you do that. There's a payload called tegraexplorer and a script for it called "downgradefix.te", (these are posted in this forum). Once you downgrade (with daybreak) your switch will crash, so boot with tegraexplorer, then use that to run the script. It will delete a save file and then you will be able to boot again and be on 20.5.
 
Yes that I know.

The issue I'm running into now is that I want to use Daybreak to install 21.0.0, but OFW version is 21.0.1. So if i update my EMUMMC to 21.0.0 manually using daybreak, when I go to install an update on OFW with Nintendo's official servers, my OFW will be 21.0.1, and the emummc version will be different than my SYS. Does this matter at all? Can't really find a full answer anywhere online.
If you have never booted the version on sysnand with atmosphere you may have trouble. The solution is to do just that.
 
Last edited by TomSwitch,
It will probably crash and get stuck in a boot loop if you do that. There's a payload called tegraexplorer and a script for it called "downgradefix.te", (these are posted in this forum). Once you downgrade (with daybreak) your switch will crash, so boot with tegraexplorer, then use that to run the script. It will delete a save file and then you will be able to boot again and be on 20.5.
My tegraexplorer payload have no Script dawngradefix.te
 
Metroid Prime 4 works on 21.0.1 using sys-patch. Installed it with DBI 849.
Most homebrew also seems to be updated for FW 21 too. (Personally I was waiting for OC Switchcraft and that got updated recently.)
Dont see a point in downgrading to FW 20.
 
Prime 4 requires 21.0.0 or it runs on 20.5.0?
Because I will remain on this FW until all homebrew are updated to work with the latest Atmosphere with support for 21.0.0
I am currently on Atmosphere 1.9.5 myself since the broken homebrew still works on that version, with Switch on 20.5.0 FW
 
Prime 4 requires 21.0.0 or it runs on 20.5.0?
Because I will remain on this FW until all homebrew are updated to work with the latest Atmosphere with support for 21.0.0
I am currently on Atmosphere 1.9.5 myself since the broken homebrew still works on that version, with Switch on 20.5.0 FW
Is there anything that does not work with 20?
 
Question, I'm on 18.1.0 and would like to remain on this firmware as all of my games, mods, overclocking tools and homebrew work perfectly. I've been able to patch every newer game with SAK to work on 18.1.0 including Pokemon Legends Z-A. However, it seems like Metroid Prime 4 is the first game that won't load for me after patching - I get "The software was closed because an error occurred." I have sys-patch and the most recent sigpatches installed as well. I would just like to see if anyone knows whether I may have missed a step, or if this is the furthest I can go with new game installs on this firmware.
 

Site & Scene News

Popular threads in this forum