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

  • Thread starter Thread starter ShadowOne333
  • Start date Start date
  • Views Views 5,184,693
  • Replies Replies 7,280
  • Likes Likes 266
Is it necessary to blank out the serial number?
what is that for?
to confuse nintendo so your device cant be banned? idk

This is a misinterpretation, you aren't blanking out your serial number. That's just a visible representation for you to know you blanked out your console unique ssl certificate.

that's what nintendo bans (blacklists) from dauth and rendering your console blocked from eshop/game updates. Your serial has very little to do with anything.
 
Hello everybody,

Recently I had to reinstall Atmosphere (1.10.2), Hekate (6.5.1), sigpatch (1.10.2) and syspatches (1.5.8) on my switch (21.2.0) and was able install/update my cartridge games via DBI and open cartridge and virtual games without any issue. But when I started the hbmenu (full mode) to open emulators, like duckstation, melonDS or retroarch, they had the "Application does not support the current ABI" and after initiating them they displayed the error "The software was closed because an error occurred".
As this ever happened to anyone or can anyone give me a hand?
 
Hello everybody,

Recently I had to reinstall Atmosphere (1.10.2), Hekate (6.5.1), sigpatch (1.10.2) and syspatches (1.5.8) on my switch (21.2.0) and was able install/update my cartridge games via DBI and open cartridge and virtual games without any issue. But when I started the hbmenu (full mode) to open emulators, like duckstation, melonDS or retroarch, they had the "Application does not support the current ABI" and after initiating them they displayed the error "The software was closed because an error occurred".
As this ever happened to anyone or can anyone give me a hand?
1) wrong thread for this trouble shoot
2) update your homebrew after firmware 21(? Not exactly sure firmware but roughly around there) there were changes to libnx so most if not all hb need to be recompiled with latest libnx
 
1) wrong thread for this trouble shoot
2) update your homebrew after firmware 21(? Not exactly sure firmware but roughly around there) there were changes to libnx so most if not all hb need to be recompiled with latest libnx
I was able to make it all work fine before by copying sigpatches/sys-patches to the microsd. I accidentally deleted emuMMC file and had to install everything again but this time, I get the ABI message in the non-applet mode and the error when it tries to load the APP.

Since this thread saved me the last time, I'm not totally sure that it is inadequate to ask this here.
 
So I've been using a modified fusee.bin based on the below text from the first page, which requires hunting down a file in this thread that another user has previously made each time I update Atmosphere. Is there a specific place where these are uploaded with each new Atmosphere version? If not...
  • Is there a quick guide to self building modified fusee?
  • Has everyone else mostly moved to using Sys-Patch Sysmodule instead of a modified fusee and I'm simply behind the times?
  • If I switch to Sys-Patch or Hekate pkg3 now will there be any data loss?

You can NO LONGER use OFFICIAL Atmosphere with signature patches. They're no longer supported.
You HAVE TO USE Hekate pkg3 (called FSS0 before) booting or Sys-Patch and/or use a custom build of fusee.bin with the code re-enabled, like the one made by
 
Last edited by protivakid,
Hello everybody,

Recently I had to reinstall Atmosphere (1.10.2), Hekate (6.5.1), sigpatch (1.10.2) and syspatches (1.5.8) on my switch (21.2.0) and was able install/update my cartridge games via DBI and open cartridge and virtual games without any issue. But when I started the hbmenu (full mode) to open emulators, like duckstation, melonDS or retroarch, they had the "Application does not support the current ABI" and after initiating them they displayed the error "The software was closed because an error occurred".
As this ever happened to anyone or can anyone give me a hand?
Nothing to do with sigpatches, you need to update each and every homebrew app you want to use. Here's a good list of them.
 
hey guys i just wondering in anyone plans to update atmosphere to work with the latest update which is now 22.00 i have not updated my console and will not until there is an update for atmosphere anyways im just curiouse thanks
 
hey guys i just wondering in anyone plans to update atmosphere to work with the latest update which is now 22.00 i have not updated my console and will not until there is an update for atmosphere anyways im just curiouse thanks
no one really knows whos going to carry on @SciresM work? we will wait and see.
 
no one really knows whos going to carry on @SciresM work? we will wait and see.
i already found out that a user by the name of AmeliaFox said if its done done within the next fewdays that she would do it herself with in the week so just be patient and i think well get an update at least thats what she said in the other thread
 
i already found out that a user by the name of AmeliaFox said if its done done within the next fewdays that she would do it herself with in the week so just be patient and i think well get an update at least thats what she said in the other thread
Cool thats good to know someone else may continue his work. :) thanks for letting us know.
 
  • Like
Reactions: froggy55
no yet, no body has been asked for it. I think I could make it this afternoon.
Post automatically merged:



Here it is!

you only need fusee.bin but if you like here is a full build of the most recent code of atmosphère with latest Homebrew Menu and HomebrewLoader.
Hi @impeeza - Is there a guide that can be used to build the modified fusee.bin so we don't have to bug you?
 
Hi @impeeza - Is there a guide that can be used to build the modified fusee.bin so we don't have to bug you?
The guide https://gbatemp.net/threads/building-atmosphere-on-windows-using-msys2.613446/ is aimed to teach how to build Atmosphère from Code.

now the changes you need to put on the source files I am not allowed to share, SciresM asked to no do it.

but you can compare the changes on the commit 46a4357 (Nov 13, 2023) https://github.com/Atmosphere-NX/Atmosphere/commit/46a43578829163cd08b9ddcaaacc6febd1e71e0e to learn what lines where removed and which ones you need to put back on the files before built it.
 

Site & Scene News

Popular threads in this forum