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

[Temaps]

Hello everyone,

My turn to ask exactly the same questions as everyone already asked because I'm dumb and I cannot read and understand correctly...

So, the method has changed, there are now 2 "best" ways to use sigpatches :
- have this line in the hekate_ipl.ini : fss0=atmosphere/package3 as a replacement of the usual (maybe not usual for everyone but was for me) "payload=bootloader/payloads/fusee.bin" and get the sigpatches... somewhere
- use a complementary homebrew called "sys-patch" which is located... Well I found it on a russian website which link is provided in this thread but it seems that I need to register to get it.

Let's say I want to use "sys-patch" because it seems to be the system which will be the most adapted to me. Currently I am on a previous version of Atmosphere with Hekate/Nyx and Emunand on files.
0 - Take the SD card out of the switch
1 - Copy tesla files from here https://github.com/WerWolv/Tesla-Menu/releases/
a. It's not clear to me if this step is necessary
b. I can't tell if this would be enough for the tesla system as the gbatemp page (https://gbatemp.net/threads/tesla-the-nintendo-switch-overlay-menu.557362/) talks about 3 different parts, maybe all 3 are included in the file from the github I listed before ?)
c. The gbatemp page indicates that the tesla should not be used with old version of atmosphere. Mine is not old but also not up to date... Hopefully tesla is not required for "sys-patch" as it would require to first update atmosphere before using tesla but I first want to make sure that "sys-patch" is correctly installed.
2 - Test if installation is ok in the switch
3 - Copy "sys-patch" files => I see a problem here. Even if the switch works correctly, it could just mean that the previous already installed sigpatches still work but it would not mean that the newly installed "sys-patch" is working correctly as a replacement. Is there any way to check this before continuing ? Maybe I can just remove the already installed sigpatches but I don't remember where those are installed...
4 - Test if installation is ok in the switch
5 - Copy latest hekate/nyx files => Hold on here... What should I write in the hekate_ipl.ini as I want to boot using sys-patch and not the "hekate" way considering also that this is for an emunand ?
6 - Test if installation is ok in the switch
7 - Copy latest atmosphere files and install with daybreak
8 - Test if installation is ok in the switch

Thanks

 

[impeeza]

Hello everyone,

My turn to ask exactly the same questions as everyone already asked because I'm dumb and I cannot read and understand correctly...

So, the method has changed, there are now 2 "best" ways to use sigpatches :
- have this line in the hekate_ipl.ini : fss0=atmosphere/package3 as a replacement of the usual (maybe not usual for everyone but was for me) "payload=bootloader/payloads/fusee.bin" and get the sigpatches... somewhere
- use a complementary homebrew called "sys-patch" which is located... Well I found it on a russian website which link is provided in this thread but it seems that I need to register to get it.

Let's say I want to use "sys-patch" because it seems to be the system which will be the most adapted to me. Currently I am on a previous version of Atmosphere with Hekate/Nyx and Emunand on files.
0 - Take the SD card out of the switch
1 - Copy tesla files from here https://github.com/WerWolv/Tesla-Menu/releases/
a. It's not clear to me if this step is necessary
b. I can't tell if this would be enough for the tesla system as the gbatemp page (https://gbatemp.net/threads/tesla-the-nintendo-switch-overlay-menu.557362/) talks about 3 different parts, maybe all 3 are included in the file from the github I listed before ?)
c. The gbatemp page indicates that the tesla should not be used with old version of atmosphere. Mine is not old but also not up to date... Hopefully tesla is not required for "sys-patch" as it would require to first update atmosphere before using tesla but I first want to make sure that "sys-patch" is correctly installed.
2 - Test if installation is ok in the switch
3 - Copy "sys-patch" files => I see a problem here. Even if the switch works correctly, it could just mean that the previous already installed sigpatches still work but it would not mean that the newly installed "sys-patch" is working correctly as a replacement. Is there any way to check this before continuing ? Maybe I can just remove the already installed sigpatches but I don't remember where those are installed...
4 - Test if installation is ok in the switch
5 - Copy latest hekate/nyx files => Hold on here... What should I write in the hekate_ipl.ini as I want to boot using sys-patch and not the "hekate" way considering also that this is for an emunand ?
6 - Test if installation is ok in the switch
7 - Copy latest atmosphere files and install with daybreak
8 - Test if installation is ok in the switch

Thanks

Tltr


Use sys-patch

 

[Blythe93]

a. It's not clear to me if this step is necessary

It's not, as sys-patch should work on its own, provided it's installed properly. Tesla + nx-ovlloader allow you to see whether sys-patch is working properly, after you press L + D-pad Down + R (Stick) combo, select sys-patch, followed by Log. If it says:

1. Patched = the pattern it's searching for is already patched by sigpatches, so there's no need to patch it again;
2. Patched = the pattern is patched by sys-patch (i.e. sigpatches are not present or haven't been applied on boot);
3. Unpatched = the pattern wasn't found by sys-patch on the current system so there's no need to patch them (only present if you turn off the Version skip in the Options).

b. I can't tell if this would be enough for the tesla system as the gbatemp page (https://gbatemp.net/threads/tesla-the-nintendo-switch-overlay-menu.557362/) talks about 3 different parts, maybe all 3 are included in the file from the github I listed before ?)

Think of those 3 as individual modules which work with one another. For general usage, you'll need Tesla Menu and nx-ovlloader, libtesla is for developers.

c. The gbatemp page indicates that the tesla should not be used with old version of atmosphere. Mine is not old but also not up to date... Hopefully tesla is not required for "sys-patch" as it would require to first update atmosphere before using tesla but I first want to make sure that "sys-patch" is correctly installed.

Unless I'm wrong, it should work properly if Atmosphere's 1.5.1 or newer, since it hasn't been updated ever since (since official firmwmare 16.0.0) was released.

3 - Copy "sys-patch" files => I see a problem here. Even if the switch works correctly, it could just mean that the previous already installed sigpatches still work but it would not mean that the newly installed "sys-patch" is working correctly as a replacement. Is there any way to check this before continuing ? Maybe I can just remove the already installed sigpatches but I don't remember where those are installed...

As I've previously mentioned, you'll need Tesla menu and nx-ovlloader as well in order to see if it works or not.

5 - Copy latest hekate/nyx files => Hold on here... What should I write in the hekate_ipl.ini as I want to boot using sys-patch and not the "hekate" way considering also that this is for an emunand ?

My hekate_ipl.ini is the same one from the zip file in the sigpatches thread. However, if you're using sys-patch, you can just push fusee.bin payload and your game backups should work.

Now, since you'd like to update your current setup, I've posted a short guide here.

 

[SonGoku78]

@Blythe93
Hi there, just came by to ask about an unpatched "ES6" shown in the overlay log of syspatch as i updated my emufw to 18.0.0
I used sig patches from here: https://gbatemp.net/threads/sigpatc...kate-fss0-fusee-package3.571543/post-10406760
So everything works, but still i wanted to ask if that "unpatched ES6" in red could make troubles in the future ?
Thanks for the explanation for the colouring in the syspatch log.
So when i understand you correctly, that ES6 is just not needed to patch ?
Can you explain this in simple word for me please why that is not needed ?
As a noob, my understanding would be best case would be if everything is shown in green ?
Thanks and have a nice sunday

PS: Anybody feel free to answer please if you can, my question is not exclusively directed to blythe93

 

[Blythe93]

So everything works, but still i wanted to ask if that "unpatched ES6" in red could make troubles in the future ?

As far as I know, based on what impeeza said here, I believe they won't. Once the new firmware revision is released, if at least one of them is patched, the other one doesn't have to be. Of course, from time to time a new pattern will be needed so the sys-patch will need to be updated, but for now they should work just fine (18.0.1 should work fine with the latest sys-patch). I haven't run into any issue so far.

So when i understand you correctly, that ES6 is just not needed to patch ?
Can you explain this in simple word for me please why that is not needed ?

I'll quote what impeeza said:

ES6 and ES7 are the 2 versions of the set of patterns to seek ES6 is for FW 14 to 17 and ES7 is for FW 14 to 18 I think they booth are overlapping, but if one of the two is patched, then the patch is applied.:

As a noob, my understanding would be best case would be if everything is shown in green ?

I'd say that the best case would be that the all the patterns included in sys-patch patch everything they need to in order for apps and game backups to work without issues.

 

[4d1xlaan]

es patches are also completely unnecessary if you make ticketless nsp

 

[dogtygr]

@Blythe93
Hi there, just came by to ask about an unpatched "ES6" shown in the overlay log of syspatch as i updated my emufw to 18.0.0
I used sig patches from here: https://gbatemp.net/threads/sigpatc...kate-fss0-fusee-package3.571543/post-10406760
So everything works, but still i wanted to ask if that "unpatched ES6" in red could make troubles in the future ?
Thanks for the explanation for the colouring in the syspatch log.
So when i understand you correctly, that ES6 is just not needed to patch ?
Can you explain this in simple word for me please why that is not needed ?
As a noob, my understanding would be best case would be if everything is shown in green ?
Thanks and have a nice sunday

PS: Anybody feel free to answer please if you can, my question is not exclusively directed to blythe93

The pattern of es6 isn't found on the new firmware so it is stated as being unpatched. There's a mistake in the patch given by the link you have. es7 is supposed to replace es6 but it seems like the patch doesn't check which version you are when you test if you want to do the es6 check. I've corrected this issue here https://gbatemp.net/threads/sys-patch-sysmod-that-patches-on-boot.633517/post-10436132 (I think that below there's a compiled version of the modifications I've made).

You can leave it like this though it doesn't make an impact anyway. If you're unlucky and it finds this pattern elsewhere it can be problematic though

 

[SonGoku78]

thanks for your answers guys, much appreciated.
And after i wrote my post, i saw the other thread about sys-patch and your long explanation at the end @dogtygr
So are your findings from the long post are already included in that precompiled syspatch version just above your post in that thread ?
I wasnt sure if i should test that patched version or not, but if you say that should be better than the unpatched version, i will exchange syspatch on my system.

 

[mathew77]

New sigpatches for the new AMS 1.7.1, pretty please.

 

[impeeza]

New sigpatches for new AMS 1.7.1, pretty please.

I am coming, I am running as fast as I can, (I am not so ancient as @AncientBoi but almost)

The good news: FW 18.1.0 uses the EXACT SAME sigpatches than 18.0.0

The latest sigpatches for FW 18.1.0 and Atmosphère 1.7.1 are here:


******************************************************************
IMPORTANT
******************************************************************

With the help of:

Impeeza put working sigpatch files! Put this file

Does this still work with 18.1.0? I tried it last night and while loader, ES and NFIM all worked, FS failed with

Unable to decrypt the FS files​

​

It's possible that you need to update keys.dat with the latest key to decrypt the files, or you may need to adjust the FS NCA settings in the config page.​

Using 1.5.7 and the most recent lockpick rcm that I could find.

Patches seem are correct.

There are some descript.ion hidden files in the ips folders... I've deleted them.

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)

 

[skorz]

hi i actualize all and got panic
i need to do something diferent?
tittle id:010000000000BD00
error: std: abort (0xFFE)

 

[impeeza]

hi i actualize all and got panic
i need to do somethind diferent?
tittle id:010000000000BD00
error: std: abort (0xFFE)

yeah, you need to disable Mission control sysmodules (and all sysmodules) and re enable when they get updated for latest firmware.

 

[Tyvar1]

I’m updating for the first time since the sigpatches changes. Just to make sure, I always booted from Hekate and used the bootloader hekate_ipl.ini so for me I don’t need to change anything? Thanks

 

[impeeza]

I’m updating for the first time since the sigpatches changes. Just to make sure, I always booted from Hekate and used the bootloader hekate_ipl.ini so for me I don’t need to change anything? Thanks

don't worry, be sure you are using Hekate's FSS0 loading of package3 and/or using SYS-PATCH sysmodule (latest one from GBAtemp's downloads section).

Post automatically merged: Jun 11, 2024

by the way there is a report of Mission Control SYSMODULE crashing with the most recent Atmosphère, so remember to delete/disable no needed sysmodules.

 

[josete2k]

don't worry, be sure you are using Hekate's FSS0 loading of package3 and/or using SYS-PATCH sysmodule (latest one from GBAtemp's downloads section).

Post automatically merged: Jun 11, 2024

by the way there is a report of Mission Control SYSMODULE crashing with the most recent Atmosphère, so remember to delete/disable no needed sysmodules.

Mission control has been updated

 

[impeeza]

Mission control has been updated

yes as stated on the guide, UPGRADE YOUR SIGPATCHES AND SYSMODULES before upgrade your atmosphère, and only when everything is working you can upgrade your firmware.

 

[luccabelinsky]

I am coming, I am running as fast as I can, (I am not so ancient as @AncientBoi but almost)

The good news: FW 18.1.0 uses the EXACT SAME sigpatches than 18.0.0

The latest sigpatches for FW 18.1.0 and Atmosphère 1.7.1 are here:

Is it necessary to update them? Just yesterday I installed Atmosphere 1.7.0 on firmware 18.0.1, sigpatches were taken for these versions. Today I updated CFW, should I update the sigpatches?

 

[impeeza]

Is it necessary to update them? Just yesterday I installed Atmosphere 1.7.0 on firmware 18.0.1, sigpatches were taken for these versions. Today I updated CFW, should I update the sigpatches?

No is not necessary, if you kept on firmware <= 18.0.1 you can stay on Atmosphère 1.7.0prerelease.

just wait until everything get updated.

 

[Blythe93]

I wonder if loading Atmosphere's package3 via Hekate's FSS0 still works? I've updated Atmosphere, sigpatches, sys-patch and firmware (and MissionControl) to the latest and, for some reason, it boots into the black screen. But, if I push the latest fusee.bin payload, it boots up just fine and everything works. Maybe Hekate needs to be updated as well? Or it's just me? My hekate_ipl.ini is pretty much the same as the one from this thread.

 

[Tyvar1]

I wonder if loading Atmosphere's package3 via Hekate's FSS0 still works? I've updated Atmosphere, sigpatches, sys-patch and firmware (and MissionControl) to the latest and, for some reason, it boots into the black screen. But, if I push the latest fusee.bin payload, it boots up just fine and everything works. Maybe Hekate needs to be updated as well? Or it's just me? My hekate_ipl.ini is pretty much the same as the one from this thread.

New update: https://x.com/ctcaer/status/1800466258900685162?s=46&t=ze8hUEylbwJqTh3RUS6Jqg

https://github.com/CTCaer/hekate/releases/tag/v6.2.0