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

  • Thread starter Thread starter ShadowOne333
  • Start date Start date
  • Views Views 5,305,219
  • Replies Replies 7,368
  • Likes Likes 266
Hey, I was wondering if someone could help if they have had the same issue. I upgraded to 20.0.1 by mistake after taking a year or so out of using cfw on the sitch. I have tried to install a few NSP files and most of them work. I am however having issues with some that keep showing the same error "software closed because a problem occoured".

Mainly on newer pokemon games

Edit* also on some DLC for older games

I have a fresh install of the Atmoshpere and have reinstalled the new sigpatches and the syspatch.

Has anyone had the same issue or got any advise.

Thanks in advance
install sys-patch sysmodule as stated on the OP
 
  • Like
Reactions: Blythe93
Thanks
Post automatically merged:

install sys-patch sysmodule as stated on the OP
Hey, thank you for the help.

Feel like I am missing something, What is the install sys-patch sysmodule and where can I find it. I was using hekate previously have have tried both with and without it having the same issue

Sorry I know you gusys probable get asked this question over and over
 
1747855926338.png
 
Last edited by DanD7755,
In my switch I have atmosphere installed with hekate and goldleaf to install the games.
I was trying to install Super Mario Jamboree but I receive the error "keygenerationmismatch". I tried to update the "atmosphere" and "bootloader" folders with the last one in this topic. Also, I updated the sys patches by adding the "contents" folder inside the atmosphere one. Anyway, the error still occur. Why? Am I missing something?
 
In my switch I have atmosphere installed with hekate and goldleaf to install the games.
I was trying to install Super Mario Jamboree but I receive the error "keygenerationmismatch". I tried to update the "atmosphere" and "bootloader" folders with the last one in this topic. Also, I updated the sys patches by adding the "contents" folder inside the atmosphere one. Anyway, the error still occur. Why? Am I missing something?
INSTALL SYS-PATCH SYSMODULE, restart your console

which homebrew are you using to install games?
 
  • Like
Reactions: Blythe93
INSTALL SYS-PATCH SYSMODULE, restart your console

which homebrew are you using to install games?
So I have now done a complete SD wipe and new files. insatalling the sys-patch sysmodule and the sig patches and am getting the same issue. I have tried both tinfoil and gold leaf with diffrent NSP files and the issue still occours. Do you have any other ideas at all? I have been stumped for days not gonna lie
 
So I have now done a complete SD wipe and new files. insatalling the sys-patch sysmodule and the sig patches and am getting the same issue. I have tried both tinfoil and gold leaf with diffrent NSP files and the issue still occours. Do you have any other ideas at all? I have been stumped for days not gonna lie
If you have sys-tweak on your SD (for example if you nedded it to display games icon on themes), delete it. It can cause these sort of issues with latest firmware
 
If you have sys-tweak on your SD (for example if you nedded it to display games icon on themes), delete it. It can cause these sort of issues with latest firmware
I can't see it on there, the most annoying thing is I have managed to get one of them working using the XCI file. maybe I have been super unlucky and had 4 bad NSP files in a row but I am not sure
 
Do you have any other ideas at all?
Did you try with DBI? I've never had any issues with it. Here's a good video on how to use it. You can use latest English release (should work for installs at least), but I'd recommend getting the latest Russian version as well (selecting the right options for installing games shouldn't be too hard).

maybe I have been super unlucky and had 4 bad NSP files in a row but I am not sure
Check their integrity with NxFileViewer.
 
I just have another 128GB microSD and used it to create a new emummc, but the hot charging poblem presist.
Backup your saves and profiles. Create a new profile. Delete the old profiles.

This issue is inconsistent and is most likely just an issue with HOS itself.
 
Hello,
After copying the latest atmosphere/hekate/syspatch and installing Firmware 20.0.0 I notice that installing titles to sd card with dbi, Is now extremly slow. But when running a title it doesn t seem to run slower or also navigating in the menu seem to be ok. Strange thing is that on another sd card I dont have this issue with dbi, also tried the latest version in russian (before I was using the latest english one). Is there maybe a tool that can control if everything is ok with the sd card I m having issues with ?

Also is this new firmware using more the switch battery ?
 
Last edited by Filetester,
INSTALL SYS-PATCH SYSMODULE, restart your console

which homebrew are you using to install games?
What do you mean with which homebrew? I am using goldleaf to install games
Am I wrongly installing sys-patch? I was unzipping the sys-patch file and copied the "contents" folder in the atmosphere folder. Do I have to do anything else?
 
Last edited by Davide57,
What do you mean with which homebrew? I am using goldleaf to install games
Am I wrongly installing sys-patch? I was unzipping the sys-patch file and copied the "contents" folder in the atmosphere folder. Do I have to do anything else?
Jst unzip everything to the root of your SD-card and reboot the console. Sys-patch work at console startup so it won't do anything until you reboot
 
Why this don't boot fusee


{--- Semi Stock start fusee.bin---}
[Semi Stock (SYSNAND)]
id=SMSTOCK
emummc_force_disable=1
payload=atmosphere/reboot_payload.bin
kernelprocid=1
 
  • Like
Reactions: impeeza
Why this don't boot fusee


{--- Semi Stock start fusee.bin---}
[Semi Stock (SYSNAND)]
id=SMSTOCK
emummc_force_disable=1
payload=atmosphere/reboot_payload.bin
kernelprocid=1
because you set nyx (hekate) to replace reboot_payload.bin with a copy of hekate.
What's baffling is that you want it to specifically launch fusee.bin for some reason, so why TF didn't you just point it to fusee.bin?

And that has nothing to do with sigpatches, so it doesn't belong here. Belongs in newb paradise.
 
  • Love
Reactions: impeeza
Why this don't boot fusee


{--- Semi Stock start fusee.bin---}
[Semi Stock (SYSNAND)]
id=SMSTOCK
emummc_force_disable=1
payload=atmosphere/reboot_payload.bin
kernelprocid=1
When doing "payload=whatever" every other command you input is ignored.

you're effectively doing:


[Semi Stock (SYSNAND)]
payload=atmosphere/reboot_payload.bin

and as mentioned above, you've set hekate replace reboot_payload.bin with itself.
 
  • Wow
Reactions: impeeza

Site & Scene News

Popular threads in this forum