No ES Sigpatches found!

[Zeromaster]

I'm tired of doing this with no results.
I'm on fw 19.0.1
The latest version of Hekate
The latest version of Atmosphere
The latest sigpatches
The latest sys-patches
In the files of the atmosphere folder in exefs_patches there is es_patches and nfim_patches there.
Everything runs perfectly.
Nothing is preventing me from downloading the nsp. that I have for my switch
I've tried the most recent Tinfoil applet version, DBI (using not only MTP but also DBIbackend), and EVERTHING IS RUNNING PERFECTLY, except when it comes to sigpatches.
In DBI, it says "ES Sigpatches not found."
"Importing ticket...[FAILED]"

And in Tinfoil, it says "Failed to import ticket".
I've been at this for the whole week and weekend, and i'm at my limit. I've done EVERYTHING THAT I COULD FIND, and yet the ticket won't import.
Any help will be appreciated and I would be most grateful if you could help me find a solution.

 

[thesjaakspoiler]

Hekate also has sigpatches.
The patches.ini file needs to go into the bootloader folder.

The sigpatches for Atmosphere are 3 folders that need to go into the atmosphere folder.
Don't manually pick the files and copy them over.
Just move over those 3 folders.

If you work with a MAC, boot into Hekate after copying the files and there is somewhere a tool to fix the archive-bit for files/folders. Sometimes the MAC sets the archive bit, which makes the files unreadable/non-existent for the Switch.

 

[Zeromaster]

Hekate also has sigpatches.
The patches.ini file needs to go into the bootloader folder.

The sigpatches for Atmosphere are 3 folders that need to go into the atmosphere folder.
Don't manually pick the files and copy them over.
Just move over those 3 folders.

If you work with a MAC, boot into Hekate after copying the files and there is somewhere a tool to fix the archive-bit for files/folders. Sometimes the MAC sets the archive bit, which makes the files unreadable/non-existent for the Switch.

I probably didn't explain myself well, but when I mentioned all of the files, I was just trying to say that they were in the correct spots, but yes, everything is in it's place

 

[urherenow]

There is an entire thread just for sigpatches that I'm willing to bet has your answer in there. How exactly are you launching things? Are you using fusee at all? Because you need a CUSTOM fusee for those ips patches to work. Bottom line, you really only need the latest sys-patch. If you're missing patches, you don't have the latest (or it didn't run because you didn't copy the boot2 flag), even if you think you do. Sys-patch runs on bootup, so you need to restart your console after putting it on your card. Open the tesla menu and post a screenshot of the sys-patch log. It will take several shots to get the whole thing...

https://gbatemp.net/threads/sigpatches-for-atmosphere-hekate-fss0-fusee-package3.571543/

 

[mrgone]

funny, i had the same problem yesterday with an emummc installation

in the end i installed a sys-clk 1.5.4
while my regular non emummc switch (banned) has a sys-clk 2.0.1 which workes totally fine

 

[urherenow]

funny, i had the same problem yesterday with an emummc installation

in the end i installed a sys-clk 1.5.4
while my regular non emummc switch (banned) has a sys-clk 2.0.1 which workes totally fine

I'm a bit skeptic about that. I Don't think sys-clk has anything to do with patches at all. But I suppose weird things can happen when playing around with APU and RAM timings. On the other hand, TInfoil claims to not work with sys-clk installed. I happen to have it on my card, but I don't use it. All settings are default.

 

[Zeromaster]

There is an entire thread just for sigpatches that I'm willing to bet has your answer in there. How exactly are you launching things? Are you using fusee at all? Because you need a CUSTOM fusee for those ips patches to work. Bottom line, you really only need the latest sys-patch. If you're missing patches, you don't have the latest (or it didn't run because you didn't copy the boot2 flag), even if you think you do. Sys-patch runs on bootup, so you need to restart your console after putting it on your card. Open the tesla menu and post a screenshot of the sys-patch log. It will take several shots to get the whole thing...

I think I might've not added the sys-patches correctly then after reading. I assumed adding the sys-patch 1.5.4 file would be the same process as adding sigpatches. All I did for sys-patch's was extract the download and copied it to the root of my SD Card. I also have heard and read a bit about the telsa menu, and when I tried to open it up with L + DPad Down + Clicking the right joystick, nothing would happen.

Now, when it comes to the topic of fusee and fss0 i'm lost. I'm by no means an expert when it comes to understanding switch modding(as I only modded my switch a week ago and it's my first time modding a switch), and i've heard the term fusee and fss0 thrown around, but I don't exactly know what it they mean.
I'll read up on the terms that you and questions that you asked me, and see if I can learn a bit more.

Oh yeah, I launch my switch into hekate using TetraRCM, injecting "hekate_ctcaer_6.2.2.bin", and load into my emuMMC on my SD Card. My emuMMC reads "Atmosphere FSS0 emuMMC", which leads me to believe that i'm using FSS0.

And one more thing, is it normal for my Switch to say "Failed to initialize SD card!" on any other payload besides "hekate_ctcaer_6.2.2.bin"? It concerns me because I hope this isn't the cause of all my problems. Mostly because whenever I launch into hekate, the first pop-up is:
"SD Card Issues Check
The SD Card is initialized in 1-bit mode! This might mean detached or broken connector!
You might want to check
Console Info -> microSD"

 

[urherenow]

Yep. In this case, you caren't using fusee. You're probably missing the tesla menu.

 

[Zeromaster]

Yep. In this case, you caren't using fusee. You're probably missing the tesla menu.

I have the boot2.flag file in my contents folder of atmosphere, but when I open it, it doesn't show anything in notepad. Is that normal, since it ends with ".flag"?

 

[Deleted member 702243]

Hekate also has sigpatches.

hekate doesnt do exefs patches

 

[urherenow]

Yes, boot2 flag is an empty file. Its presence signals the system to load it at startup. Tesla menu isn’t required for it to work, but it’s required for you to be able to see that it’s working, and to configure it easily.

Not sure what the post above this is trying to say. The loader executes the exefs, and that execution is what does the patching… nothing patches an exefs.

 

[Zeromaster]

Okay, after a bit of troubleshooting, I got the tesla menu to work and appear on my CFW. Since i'm still a newbie and Level 1 on GBATemp, I can't send images but I can type what the sys-patch log says.
Logs: fs, ldr, es, nfim & nim are all shown as "Patched"

Post automatically merged: Dec 3, 2024

Could I run everything normally now?

Edit: I FINALLY GOT THE GAME TO RUN! The ticket FINALLY was imported correctly and now I can actually go inside the game and run it
But there's another issue now. I can't interact with the game at ALL, but I can navigate the switch's home menu just fine. How do I even begin to approach this?

 

[The Real Jdbye]

I think I might've not added the sys-patches correctly then after reading. I assumed adding the sys-patch 1.5.4 file would be the same process as adding sigpatches. All I did for sys-patch's was extract the download and copied it to the root of my SD Card. I also have heard and read a bit about the telsa menu, and when I tried to open it up with L + DPad Down + Clicking the right joystick, nothing would happen.

Now, when it comes to the topic of fusee and fss0 i'm lost. I'm by no means an expert when it comes to understanding switch modding(as I only modded my switch a week ago and it's my first time modding a switch), and i've heard the term fusee and fss0 thrown around, but I don't exactly know what it they mean.
I'll read up on the terms that you and questions that you asked me, and see if I can learn a bit more.

Oh yeah, I launch my switch into hekate using TetraRCM, injecting "hekate_ctcaer_6.2.2.bin", and load into my emuMMC on my SD Card. My emuMMC reads "Atmosphere FSS0 emuMMC", which leads me to believe that i'm using FSS0.

And one more thing, is it normal for my Switch to say "Failed to initialize SD card!" on any other payload besides "hekate_ctcaer_6.2.2.bin"? It concerns me because I hope this isn't the cause of all my problems. Mostly because whenever I launch into hekate, the first pop-up is:
"SD Card Issues Check
The SD Card is initialized in 1-bit mode! This might mean detached or broken connector!
You might want to check
Console Info -> microSD"

1-bit mode will cause issues. My cousin who has this message gets frequent crashes in CFW emuNAND and even sometimes in OFW.

 

[Zeromaster]

1-bit mode will cause issues. My cousin who has this message gets frequent crashes in CFW emuNAND and even sometimes in OFW.

I think the issue is something to do with the actual inside of the switch, which more than likely will be something i'll just have to put up with, but do you know how to fix/begin how to fix the issue my game not being able to register my controller inputs?

 

[The Real Jdbye]

I think the issue is something to do with the actual inside of the switch, which more than likely will be something i'll just have to put up with, but do you know how to fix/begin how to fix the issue my game not being able to register my controller inputs?

Dunno, what game is it?

 

[Zeromaster]

Dunno, what game is it?

The Binding of Isaac Afterbirth+
The only inputs ingame while playing that are work are the Screenshot and HOME buttons.
I'm using a nintendo switch pro controller (I'm pretty sure at least)
I'm just using a wireless powerA controller