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

[xXSoulGeoXx]

https://gbatemp.net/threads/ultimate-guide-to-upgrade-your-firmware-atmosphere.661148/

thanks
though, will following the Switch Guide for a clean install work as well, right?

already got most of the updated homebrew I use myself
did made a NAND backup though

 

[Blythe93]

Will I need to do a clean install for this new updates? or simply drag-n-drop will be find for me?

Ever since I hacked my Switch I don't think i ever needed to do a clean install of Atmosphere/Hekate/etc. in order to update, just drag and drop did it for me. The problems people usually run into are usually outdated sys-modules or all-in-one updaters. If you've done a clean install recently,

I believe that drag and drop will do just fine for you but it depends on what kind of setup you have. For example, I manually change Atmosphere's reboot_payload.bin to the Hekate's payload because I use Atmosphere's reboot_to_payload.nro in order to reboot to Hekate so I have to remember to do that every time I update.

Is there something we need to change manually for AMS for 20.0.1? its the thing I am confused about

It's optional but you can replace every instance of fss0 with pkg3 in your hekate_ipl.ini as it's now obsolete and will be fully replaced in the future. From the Hekate v6.3.0 release notes:

Config: Added pkg3 key support that replaces fss0 with the same exact functionality
fss0 will still work for compatibility reasons but it's now deprecated.
At some point fss0 will become obsolete, so make sure you update your configs to use pkg3 instead.
The templates were updated to use that.

Again, it's optional.

If you're using sigpatches, make sure to use modified Atmosphere's fusee.bin payload with ips kip patches support restored or Load Atmosphere's package3 via Hekate's FSS0.
If you're using sys-patch, you should only update it to the latest version and everything should work properly.

though, will following the Switch Guide for a clean install work as well, right?

Technically, yeah, but why would you waste your time on that? Especially if you're using emuMMC CFW and if you're about to e.g. update your sysMMC to the latest and create a new emuMMC from that. Just pointless as far as I can tell. You're needlessly making things more difficult for yourself.

 

[xXSoulGeoXx]

Technically, yeah, but why would you waste your time on that? Especially if you're using emuMMC CFW and if you're about to e.g. update your sysMMC to the latest and create a new emuMMC from that. Just pointless as far as I can tell. You're needlessly making things more difficult for yourself.

I'm using sysMMC myself
as my Switch its banned from using the eShop

my brother Switch on the other hand its using emuMMC since installing a modchip, would need to update it when 20.0.1 its needed

at the moment, I did a clean install of everything, only keeping my Nintendo and Switch folder in the process
haven't updated to 20.0.1 FW yet but at least, most of the stuff I need been updated
may wait for the other homebrew to get 20.0.1 but will remain at 19.0.1 for the moment, maybe update to 20.0.1 next month

from the Switch Guide, their hekate_ipl.ini I believe all have PKG3, with fss0 nowhere to be found in the ini file given on that guide

what else?
also, avoided to download some overlays that still haven't been updated to the newest firmwire in case, checking if they either run well or causes crashes on each of their github issues pages

 

[froggy55]

does anybody know if its possible to revert to an previouse fw only on emmumc i want to go back to 19.01 because tinfoil is working terrible on the latest fw

 

[impeeza]

does anybody know if its possible to revert to an previouse fw only on emmumc i want to go back to 19.01 because tinfoil is working terrible on the latest fw

yes reading the documentation.

use Daybreak Homebrew to install any previous firmware SO DO NOT DOWNGRADE FROM FW 20 BECAUSE YOUR USER PARTITION WILL BE BROKEN.

 

[froggy55]

yes reading the documentation.

use Daybreak Homebrew to install any previous firmware

thank you so much for your reply im doing it right now ill let you know how it goes

Post automatically merged: May 13, 2025

thank you so much for your reply im doing it right now ill let you know how it goes

ok so i down graded but now atmosphere is crashing with error code 2002-3005 program 0100000000000025 do i need to use the sig patches for 19.01 for this to go away

 

[impeeza]

ok so i down graded but now atmosphere is crashing with error code 2002-3005 program 0100000000000025 do i need to use the sig patches for 19.01 for this to go away

or as is stated on atmosphere release, remove the blanking of the productid. SYS-Patch also take care of that, or a full set of sigpatches can help.

 

[josete2k]

yes reading the documentation.

use Daybreak Homebrew to install any previous firmware

Dont do that.

User partition will be corrupted and you'll need to format from recovery!

 

[impeeza]

User partition will be corrupted and you'll need to format from recovery!

there are a bug on Dyabreak?

 

[josete2k]

there are a bug on Dyabreak?

Nope.

Seems that 20.0.x changes more than "stability"

 

[impeeza]

Nope.

Seems that 20.0.x changes more than "stability"

Thanks for let us to know.

 

[josete2k]

Luckily... You can access to recovery (hold vol+ and vol- while AMS logo and don't release them until recovery appears) and format your emunand.

 

[froggy55]

yes reading the documentation.

use Daybreak Homebrew to install any previous firmware

how do i remove prod id blanking do i need to delete the exosphere file

 

[josete2k]

Try, but I think you will have to format...

 

[froggy55]

Try, but I think you will have to format...

ok i deleted the exsophere file but i am still getting atmosphere crash 2002-3005 program 0100000000000025 do you know what the fix is thanks

 

[impeeza]

Nope.

Seems that 20.0.x changes more than "stability"

humm, may be that had something to do with the crash after upgrade to 20.0.0 «resolved» on 20.0.1?

 

[josete2k]

Read two posts before...

 

[LuigiGad]

Luckily... You can access to recovery (hold vol+ and vol- while AMS logo and don't release them until recovery appears) and format your emunand.

But if you format the emummc, won’t there be issues recognizing the microsd when switching back to stock? It will indicate that the microsd is being used on another console, etc.

 

[josete2k]

humm, may be that had something to do with the crash after upgrade to 20.0.0 «resolved» on 20.0.1?

I don't know... Maybe sciresM could fix it...

Post automatically merged: May 13, 2025

But if you format the emummc, won’t there be issues recognizing the microsd when switching back to stock? It will indicate that the microsd is being used on another console, etc.

Nope... Nintendo folders are not the same...

 

[froggy55]

Read two posts before...

whom are you responding to i checked the posts for the fix but i did not see any explanation