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

  • Thread starter Thread starter ShadowOne333
  • Start date Start date
  • Views Views 5,359,800
  • Replies Replies 7,392
  • Likes Likes 266
How does one undo their prodinfo blanking?
Depends.

If you used incognito_rcm, you need to use it to restore it.
If you used tinfoil, you need to use it to restore it.

If you used Atmospheres exosphere file, just edit it and change the blank prodinfo to 0 instead of 1.
 
you can go straight to FW 17 but be sure of read the guide on updating and be sure you have setting DNS block to big N servers, DNS90 or Atmosphère's DNSMiTM
If I don’t care about online on my switch CFW, can I update it to 17.0.0 just like usual? update hekate > update atmos > sigpatches > update FW ?
 
  • Like
Reactions: Blythe93
If I don’t care about online on my switch CFW, can I update it to 17.0.0 just like usual? update hekate > update atmos > sigpatches > update FW ?
If you do not use Internet connection on your Switch, sure.
If you do, however, in case you've cleared your prodinfo in the past using Incognito_RCM or similar, you'll either need to restore it or use 90DNS and/or DNS MITM as well, which will do the trick. That way Atmosphere won't crash once you connect to the WiFi connection.

So, set up DNS blocking > Update Hekate and Atmosphere > Update Firmware via Daybreak and install latest sigpatches (for the appropriate firmware and Atmosphere revision).
 
Sorry bro I did looked I didn't see any link saying sigpatch update for the latest version
1699142420550.png

1699142523507.png


1699142565369.png
 
If you do not use Internet connection on your Switch, sure.
If you do, however, in case you've cleared your prodinfo in the past using Incognito_RCM or similar, you'll either need to restore it or use 90DNS and/or DNS MITM as well, which will do the trick. That way Atmosphere won't crash once you connect to the WiFi connection.

So, set up DNS blocking > Update Hekate and Atmosphere > Update Firmware via Daybreak and install latest sigpatches (for the appropriate firmware and Atmosphere revision).

Thanks for your info.

Currently I am using an older version of atmosphere; what's the safest way to update that these days? I've kept my hacked switch in airplane mode for over a year.

Also, would updating to the current sigpatches not work with this version of atmosphere?
 
  • Like
Reactions: Blythe93
Thanks for your info.

Currently I am using an older version of atmosphere; what's the safest way to update that these days? I've kept my hacked switch in airplane mode for over a year.

Also, would updating to the current sigpatches not work with this version of atmosphere?
The current sigpatches will work, since it includes the latest and all previous.

Safest away is to update Atmosphere first, make sure if you use fusee-primary it changed name to fusee.bin and fusee-secondary have changed name to package3 (that means you use Hekate).
If you use Hekate, you need to update it as well, plus edit your hekate_ipl.ini file to change fusee-secondary to package3 instead.

After your latest atmosphere works, you can then go ahead and download the FW from example Darthsteine and install it with Daybreak.

Then Bobs your Uncle!
 
I can't install them i got message " Key extraction from FS failed " then " Error while extracting the home menu ".

I'm in 17.0.0 ams 1.6.2 E . Any ideas please ?
Post automatically merged:

Hello !

I can't isntall them, a got the message " Error while extracting the home menu : Keys have not been initialized " then " Key extraction from FS failed ! "

I'm in 17.0.0 AMS 1.6.2 E .

Any ideas pls ?

Have a good day
 
I can't install them i got message " Key extraction from FS failed " then " Error while extracting the home menu ".

I'm in 17.0.0 ams 1.6.2 E . Any ideas please ?
Post automatically merged:

Hello !

I can't isntall them, a got the message " Error while extracting the home menu : Keys have not been initialized " then " Key extraction from FS failed ! "

I'm in 17.0.0 AMS 1.6.2 E .

Any ideas pls ?

Have a good day
Do you happen to use a Theme?
 
Hi folks, after my old CFW SD card got corrupted, I created a new one following the latest NH guide. I’m running Switch firmware 16.0.2 / AMS 1.6.2, the latest Atmosphere and Hekate, with a partitioned emuMMC. I updated sigpatches using the files in this thread.

However, whenever I attempt to launch any Switch game on emuMMC—even one from a game cart in the Switch—I receive the “Unable to start software, Return to the Home Screen and try again” error.

Anyone have a clue what might be the problem? I’ve already tried starting the entire process over twice with a freshly formatted SD card. I’m able to launch games in OFW, but not in emuMMC CFW.
 
I’m running Switch firmware 16.0.2 / AMS 1.6.2, the latest Atmosphere and Hekate, with a partitioned emuMMC. I updated sigpatches using the files in this thread.
For sigpatches to work properly, you need to pair them with the appropriate version of Atmosphere and firmware.
You're currently on 16.0.2|AMS 1.6.2 while the latest sigpatches in the first post of this thread are for 17.0.0|AMS 1.6.2.

If you really want to stay on that version of firmware, check this tutorial to see how to create your own sigpatches.
Since you're starting out with a fresh emuMMC, I'd suggest updating your emuMMC firmware to the current latest (i.e. 17.0.0) via Daybreak. Firmware files can be found easily by a quick Google search, just extract them to a folder on your microSD card, name doesn't matter as long as you can easily find it.

Firmware 17.0.0 had some major updates (check this post to learn more) so in case you ever cleared your prodinfo in order to avoid getting banned by Nintendo, you'll need to undo it and set up DNS MITM or similar instead in order to connect to the Internet (to update your homebrew and alike).
 

Site & Scene News

Popular threads in this forum