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

  • Thread starter Thread starter ShadowOne333
  • Start date Start date
  • Views Views 5,460,593
  • Replies Replies 7,460
  • Likes Likes 266
I'll strike point 1 from my guide and replace it with: "23.0.0 frees ~9mb for sysmodules on stock AMS 1.12 (embedded memory-saving patches, per bth). Yellow/blank boot hangs trace to outdated sysmodules like HOC, not memory."

Second correction, same rule as the last one: data beats my inference, and your data is better than my inference was. Thanks for keeping the thread honest.
you write like LLM (very claude-esque to use the word inference, very grok like to mention honesty)
 
you write like LLM (very claude-esque to use the word inference, very grok like to mention honesty)

fair cop. i let a local llm tidy my grammar before posting (i build local ai stuff so it's habit). claims are mine/yours/hexkyz's, the polish is the machine's, and yeah it shows. sorry for the slop, plainer from here on
 
  • Like
Reactions: Blythe93
here's .ips sigpatches for 23.0.0 and atmosphere 1.12.0;

sys-patch does not need an update for 23.0.0 or atmosphere 1.12.0 (no need to ask)
Your .ips sigpatches for 23.0.0 and atmosphere 1.12.0 makes all titles reborn, and no firmware downgrade is necessary.
Thanks alot.
Although I know my Switches will be banned very soon, just let them go.
We seldom use OFW although we have it for a long time.
Banning means no more OFW update, right? It can reduce alot of problems later on indeed.

I found the latest Ultrahand overlay works with v23.0.0 firmware.
 
Last edited by johnliu,
Banning means no more OFW update, right? It can reduce alot of problems later on indeed.
banning means you get banned from dauth, which prevents you from obtaining edgetokens, which are required to download games, updates, dlc and access eshop.

it does not ban you from accessing atum, which is what provides you firmware updates.

(sys-patch should have a patch that blocks firmware updates, and it is distributed in the .ips form as well)


(23.0.1 changes nothing, no need for new sigpatches or sys-patch, or even new version of atmosphere)
 
Last edited by bth,
banning means you get banned from dauth, which prevents you from obtaining edgetokens, which are required to download games, updates, dlc and access eshop.

it does not ban you from accessing atum, which is what provides you firmware updates.

(sys-patch should have a patch that blocks firmware updates, and it is distributed in the .ips form as well)


(23.0.1 changes nothing, no need for new sigpatches or sys-patch, or even new version of atmosphere)

I thought sigpatch was of no use when using syspatch?
 
banning means you get banned from dauth, which prevents you from obtaining edgetokens, which are required to download games, updates, dlc and access eshop.

it does not ban you from accessing atum, which is what provides you firmware updates.

(sys-patch should have a patch that blocks firmware updates, and it is distributed in the .ips form as well)


(23.0.1 changes nothing, no need for new sigpatches or sys-patch, or even new version of atmosphere)
has the problem of nintendo not being blocked on emmumc in atmosphere 1.12.0 been fixed because i do not want my switch to be banned. as of right now i have not and will not update until i know this has been fixed and for those that posted about the problem thank you very much you just saved my switch from being banned
 
has the problem of nintendo not being blocked on emmumc in atmosphere 1.12.0 been fixed because i do not want my switch to be banned. as of right now i have not and will not update until i know this has been fixed and for those that posted about the problem thank you very much you just saved my switch from being banned
supposedly will be corrected on 1.12.1
 
  • Like
Reactions: Blythe93
has the problem of nintendo not being blocked on emmumc in atmosphere 1.12.0 been fixed because i do not want my switch to be banned. as of right now i have not and will not update until i know this has been fixed and for those that posted about the problem thank you very much you just saved my switch from being banned
Just don't update?

It seems some people is being held at gunpoint they feel the need to update their system otherwise they going to die.
 
  • Like
Reactions: lwiz and impeeza
there is a way to fix warmboot sleep mode problem
problem most likely introduced by non-atmosphere, non-syspatch, non-sigpatches related components.

removing unnecessary bloat, updating hekate and atmosphere will usually fix that.
all those other sysmodules, delete, reboot, and problem should fix itself
 
Never had that issue whatsoever when updating because I always use the latest Hekate coupled with the prior version of AMS. I'm not sure what you people are doing. My OFW 22.5 -> 23.0 while CFW EMU remains on 22.5
But but but...how can you live with youself without having newest updates?😭
 
Remember to ensure your Switch is completely offline first, both LAN and WIFI, before updating emuNAND to v23.0.0+ firmware!
Or you will be banned soon because the Nintendo server blocking will be voided after updating to v23.0.0+ firmware.
Althought it seems that it's too late to say so.

Updating to the latest hekate and atmosphere which supports v23.0.1 firmware may fix warmboot problem.
 
Last edited by johnliu,
  • Like
Reactions: impeeza
to my knowledge, no, there is not a need for a new version for firmware 23.0.0

there is however a new IPC service interface in FS which seem related to file handling, which both qlaunch and auth (system-applets) call for;

but none of the existing patches need any changes.
A super minor tweak would be changing am patch to only apply to 22.0.0, but not important or necessary
Minecraft Dungeons 2 doesn't launch successfully when using sys-patch 1.6.2.3; I've tested it on three different consoles running firmware 23.0.1 with the same result. Do you know if this is caused by sys-patch?
 
Minecraft Dungeons 2 doesn't launch successfully when using sys-patch 1.6.2.3; I've tested it on three different consoles running firmware 23.0.1 with the same result. Do you know if this is caused by sys-patch?
it's not caused by sys-patch.
it most likely is a dynamic heap game,

but i cannot know, you have not provided a crash report or fatal report
 
  • Like
Reactions: impeeza

Site & Scene News

New Hot Discussed User Submitted