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

[Blythe93]

sysmmc cfw doesn't boot for me, I get a yellow screen. I updated atmosphere hekate and signpatches and used the ipl from latest signpatches. I ve never tried to boot cfw sysmmc before, Its in the latest official firmware. emummc on version 19 is running ok...

You can find the list of panic color codes here. For yellow, it says "Bootloader (booting SafeMode) [1.0.0-3.0.2]". Sadly, I've never run into that issue so I' m not sure what to suggest about that.

 

[SatsuJin]

I accidentally hit the update button on my switch and it updated to 20.1.1 (I assume) and now it wont start if I try initianting Atmosphere as expected. So I updated to the latest hekate, atmosphere 1.9.1 and dowloaded the latest sigpatches here. I can start hekate normally now, but if I try starting atmosphere it gives an error again.

I'm a little confused about the whole 20.1.1 is a Switch 2 update thing. Anyways, any suggestion to what I am doing wrong? I did everything the same as I did everytime I update FW, so my guess is that Atmos 1.9.1 does not support fw 20.1.1 yet

 

[Blythe93]

Atmos 1.9.1 does not support fw 20.1.1 yet

It apparently works but it probably needs an update, yeah. Which error are you getting?

dowloaded the latest sigpatches here

I'd suggest using sys-patch instead.

 

[froggy55]

It apparently works but it probably needs an update, yeah. Which error are you getting?


I'd suggest using sys-patch instead.

also make sure your mission control is the latest which is 13.2 this not being updated caused me an error where ams crashed and yes 20.1.1 works i havenot had any issues with my switch i got everything working

 

[kingrychu109]

new to this part i am trying to get breath of the wild on tinfoil it gave me failed to import ticket! this is usually caused by missing sigpatches for your firmware or a corrupted ticket database can some one send me to a place for a walkthrough or guide or instruct me how to fix this?

 

[SatsuJin]

It apparently works but it probably needs an update, yeah. Which error are you getting?


I'd suggest using sys-patch instead.

This is the error I'm getting when trying to initiate Atmosphere, but I did replace the fisee so Im not sure. I heard about the sys-patch but im not sure how to use it. Just drop it on the sd card or should i have something else with it?

 

[bth]

View attachment 511590
This is the error I'm getting when trying to initiate Atmosphere, but I did replace the fisee so Im not sure. I heard about the sys-patch but im not sure how to use it. Just drop it on the sd card or should i have something else with it?

You're booting with "fusee.bin", which you have to replace every single time atmosphere updates.

 

[Blythe93]

Just drop it on the sd card or should i have something else with it?

Yep. I'd suggest removing sigpatches once you copy over the sys-patch as you don't need two things doing the same thing. Here's how.

This is the error I'm getting when trying to initiate Atmosphere, but I did replace the fisee so Im not sure.

What bth said, you're probably sending the wrong payload so double-check that. Are you using some custom Atmosphere pack? They might have compiled their own version of Atmosphere and you might need their version of fusee.bin as well, but I'm not sure about that. Do you have a modchip installed?

 

[SatsuJin]

Yep. I'd suggest removing sigpatches once you copy over the sys-patch as you don't need two things doing the same thing. Here's how.


What bth said, you're probably sending the wrong payload so double-check that. Are you using some custom Atmosphere pack? They might have compiled their own version of Atmosphere and you might need their version of fusee.bin as well, but I'm not sure about that. Do you have a modchip installed?

Ok so I replaced Atmosphere with 1.9.1 from here, including the fusee for that version. Replaced to the most recent Hekate 6.3.1 (I'm using the same one with tegra to inject the payload), cleaned the sigpatches stuff and put the sys-patch files.

Unfortunally the same error keeps happening happening. And no, mine doesn't have a modchip, it's a V1 and have been modded for years already. I use the RCM piece + Tegra to inject payload.

 

[impeeza]

Seems The current set of Sigpatches are the same for Firmware 20.1.5 so no need to upgrade.

SYS-Patch sysmodule seems to works fine too.

 

[froggy55]

Ok so I replaced Atmosphere with 1.9.1 from here, including the fusee for that version. Replaced to the most recent Hekate 6.3.1 (I'm using the same one with tegra to inject the payload), cleaned the sigpatches stuff and put the sys-patch files.

Unfortunally the same error keeps happening happening. And no, mine doesn't have a modchip, it's a V1 and have been modded for years already. I use the RCM piece + Tegra to inject payload.

i would google atmosphere go to the latest version on github there you will find both atmosphere and the correct fuse.bin i would reccomend you replace your atmospherefiles with the ones there and replace with the latest fusee.bin which you can also download there here is the link https://github.com/Atmosphere-NX/Atmosphere/releases

 

[impeeza]

i would google atmosphere go to the latest version on github there you will find both atmosphere and the correct fuse.bin i would reccomend you replace your atmospherefiles with the ones there and replace with the latest fusee.bin which you can also download there here is the link https://github.com/Atmosphere-NX/Atmosphere/releases

Ok so I replaced Atmosphere with 1.9.1 from here, including the fusee for that version. Replaced to the most recent Hekate 6.3.1 (I'm using the same one with tegra to inject the payload), cleaned the sigpatches stuff and put the sys-patch files.

Unfortunally the same error keeps happening happening. And no, mine doesn't have a modchip, it's a V1 and have been modded for years already. I use the RCM piece + Tegra to inject payload.

Homebrew Tutorial  Thread 'Ultimate guide to upgrade your firmware/Atmosphère'

Sep 22, 2024

ONLY UPDATE YOUR CONSOLE TO 2x.x.x IF ALL THE HOMEBREW YOU USE IS UPGRADED

Sometimes you need to upgrade your console, upgrade the firmware or upgrade Atmosphère, using the @l7777 's guide (https://gbatemp.net/threads/updating-hekate-atmosphere-and-hos.631739/) as base I hope to create a list of necessary steps to successful upgrade your console.

This guide uses Hekate, if you don't want to use Hekate skip the steps about it. You may loose some features.

---

Make a backup.​

Always make a full backup of your console, so if...​

• impeeza
• Replies: 84
• Forum: Nintendo Switch

• 
• 
• 

 

[bth]

sys-patch should still work for 2.0.1.5

Patch changelog for 20.1.5:


# Firmware version number generated keys for is: 20.1.5

# key revision generated keys for ends with _13

# mariko_master_kek_source_13       = 1A316287A809CAF****************

a "MOV" arm instruction with ending of 0x2A was found within the pattern

Sys-patch for ES string still valid for: 20.1.5

Sys-patch ES pattern found at: 076A18

The ghidra-equivalent pattern used was: .. .. 00 .. .. .. 00 94 a0 .. .. d1 .. .. ff 97 .. .. .. .. .. .. .. a9

An arm "MOV" condition is what is supposed to be patched at this offset

20.1.5 ES build-id: 8B2E677DE5991C87B35E84F7DDB8056F62D4582E


an "STP" arm instruction with ending of 0xA9 was found proceding the pattern

Sys-patch for NIFM string still valid for: 20.1.5

Sys-patch NIFM pattern found at: 087AC0

The ghidra-equivalent pattern used was: 14 .. .. .. .. .. .. .. .. .. .. .. 91 .. .. .. .. .. .. .. .. .. .. .. 97 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 14

An arm "STP" condition is what is supposed to be patched at the offset right after the branch arm condition tested ("B")

20.1.5 NIFM build-id: 523D2C6E08D9BE4B512AD20AA5628B7BB06D73C2


a "ADR" arm instruction with ending of 0x10 was found within the pattern

Sys-patch for NIM string still valid for: 20.1.5

Sys-patch NIM pattern found at: 190DF8

The ghidra-equivalent pattern used was: .. 0F 00 35 1F 20 03 D5 .. .. .. ..

An arm "ADR" condition is what is supposed to be patched at the offset right after the "CBNZ and "NOP" conditions the pattern finds

20.1.5 NIM build-id: CC269DEA7E3AE16FAA39215F5A1CEF5C82FA1C00


a "TBZ" arm instruction with ending of 0x36 was found within the pattern, first pattern verified

a "BL" arm instruction with ending of 0x94 was found within the pattern, second pattern verified

both sys-patch strings are valid for FS-FAT32 for: 20.1.5

20.1.5 First Sys-patch FS-FAT32 pattern found at: 023C88

The ghidra-equivalent pattern used was (11.0.0+) : .. 94 .. .. 00 36 .. 25 80 52

An arm "TBZ" condition is what is supposed to be patched, it is found within the pattern.

20.1.5 Second Sys-patch FS-FAT32 pattern found at: 07A880

The ghidra-equivalent pattern used was (19.0.0+) : 40 f9 .. .. .. 94 .. .. 40 b9 .. .. 00 12

An arm "BL" condition is what is supposed to be patched, it is found within the pattern.

20.1.5 Second Sys-patch FS-FAT32 pattern found at: 07A880

20.1.5 FS-FAT32 SHA256 hash: ED34B450584A5B43150CFF94D6A7C49F6B7F4C649B7CC6A0D8A0BB316EB52B76


FS-exFAT was skipped for: 20.1.5, due to missing NCA file for exfat in the provided firmware files.

 

[Blythe93]

Unfortunally the same error keeps happening happening. And no, mine doesn't have a modchip, it's a V1 and have been modded for years already. I use the RCM piece + Tegra to inject payload.

Do you have Tesla menu + nx-ovlloader? If not, please add that one as well and check whether sys-patch works properly on your console? To open up menu press L + D-pad Down + R (Stick) combo, select sys-patch, followed by Log. It should say Patched for all the entries.

 

[SatsuJin]

i would google atmosphere go to the latest version on github there you will find both atmosphere and the correct fuse.bin i would reccomend you replace your atmospherefiles with the ones there and replace with the latest fusee.bin which you can also download there here is the link https://github.com/Atmosphere-NX/Atmosphere/releases

Thats what I did. I only get the new Atmosphere updates from there. And yes I also downloaded the new fusee. This is not my first time updating, I have been doing this for years thats why Im confused about the error.

I assumed the new atmosphere just didnt support FW 20.1.1 (updated by accident), but many people said that it does.

 

[SatsuJin]

Homebrew Tutorial  Thread 'Ultimate guide to upgrade your firmware/Atmosphère'

Sep 22, 2024

ONLY UPDATE YOUR CONSOLE TO 2x.x.x IF ALL THE HOMEBREW YOU USE IS UPGRADED

Sometimes you need to upgrade your console, upgrade the firmware or upgrade Atmosphère, using the @l7777 's guide (https://gbatemp.net/threads/updating-hekate-atmosphere-and-hos.631739/) as base I hope to create a list of necessary steps to successful upgrade your console.

This guide uses Hekate, if you don't want to use Hekate skip the steps about it. You may loose some features.

---

Make a backup.​

Always make a full backup of your console, so if...​

• impeeza
• Replies: 84
• Forum: Nintendo Switch

• 
• 
• 

Lol I try, but I have over 600gb in there and I only have an old notebook at home that doesnt have rnough space for a full back up.

Ugh this is all that stupid "theres a new update" message that reappered after I connecte to use Tinfoil. I hit the update button by accident, otherwise I eould have stayed on 19.0 for longer coz I know how annoying this is. But people kept saying that the recent Atmosphere supports 20.1.1 so I took a shot. Guess I'll just have to wait for a new version of Atmosphere and patches

 

[OrGoN3]

Lol I try, but I have over 600gb in there and I only have an old notebook at home that doesnt have rnough space for a full back up.

Ugh this is all that stupid "theres a new update" message that reappered after I connecte to use Tinfoil. I hit the update button by accident, otherwise I eould have stayed on 19.0 for longer coz I know how annoying this is. But people kept saying that the recent Atmosphere supports 20.1.1 so I took a shot. Guess I'll just have to wait for a new version of Atmosphere and patches

They already exist ....

 

[Nynrah]

Just to be clear, the latest version of Atmosphere, Hekate etc. supports 20.1.1? I know the github pages mention 20.1.0, but in my experience those minor numbers at the right were never problematic unless explicitely mentioned otherwise. As far as I could tell, everything's good to go for updating to 20.1.x, but when I'm hearing too many conflicting sounds I start feeling uncomfortable about going through the with CFW update.

 

[Blythe93]

Just to be clear, the latest version of Atmosphere, Hekate etc. supports 20.1.1? I know the github pages mention 20.1.0, but in my experience those minor numbers at the right were never problematic unless explicitely mentioned otherwise. As far as I could tell, everything's good to go for updating to 20.1.x, but when I'm hearing too many conflicting sounds I start feeling uncomfortable about going through the with CFW update.

My emuNAND is on 20.1.0 and I probably won't update until new Atmosphere is out as there's no need to as far as I know. Everything I use works on my end but your use case might be different. I'd stay on 20.1.0 for now if I were you.

If you're using a lot of sys-modules and mods for certain games, 18.1.0 is probably the best, 19.0.1 being the second, based on the amount of memory available for those modules.
18.1.0 has 40MB, 19.x.x 24MB and 20.x.x 14MB.

 

[impeeza]

Just to be clear, the latest version of Atmosphere, Hekate etc. supports 20.1.1? I know the github pages mention 20.1.0, but in my experience those minor numbers at the right were never problematic unless explicitely mentioned otherwise. As far as I could tell, everything's good to go for updating to 20.1.x, but when I'm hearing too many conflicting sounds I start feeling uncomfortable about going through the with CFW update.

yes it does.