Toggle sidebar

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

  • Thread starter Thread starter ShadowOne333
  • Start date Start date
  • Views Views 5,475,206
  • Replies Replies 7,492
  • Likes Likes 266
how to fix minecraft dungeons 2 not installing on 23.0.0:

1. boot atmosphere on sysnand with access to eshop
2. buy the game (non-optional, otherwise step 4 will be disregarded)
3. watch as it fails to install
4. submit github issue at https://github.com/Atmosphere-NX/Atmosphere/issues
5. wait for whomever to address new FS disrepancies in ncm
 
bth said:
how to fix minecraft dungeons 2 not installing on 23.0.0:

1. boot atmosphere on sysnand with access to eshop
2. buy the game (non-optional, otherwise step 4 will be disregarded)
3. watch as it fails to install
4. submit github issue at https://github.com/Atmosphere-NX/Atmosphere/issues
5. wait for whomever to address new FS disrepancies in ncm
Click to expand...

So...the answer is "there's nothing wrong with the software" and "the dump is bad" and "I'm more qualified to have an opinion" until a handful of screenshots are shoved in your face, at which point you no longer engage and say..."Buy the game"?

You are well within your rights to say "I don't support piracy, I won't address issues related to it". That's fine and dandy. But you spent a page of replies telling people a.) they didn't know what they were talking about b.) they had a bad dump c.) nothing you maintain is at fault, they were all doing it wrong, and then d.) quietly asking people to submit a github issue.

You sound real qualified to have an opinion.
 
Blythe93 said:
NxFileViewer under BuildID says: Not available (content sparse)
I assume that's the indicator of the sparse type NCA? The proper dump should have a valid BuildID?
Click to expand...
this sparse nca doesn't have a real exefs partition, it's empty and doesn't layer onto primary update nca either.
min req version is the first update.

sparse nca's have a hard requirement of installing both the base and update in succession using special BKTR formula.

it layers section 0 and section 1 of both ncas to form one big data unit. cant install without doing that.
 
  • Love
Reactions: Blythe93
bth said:
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)
Click to expand...
Just to make sure I'm reading this right, but if I upgrade my Atmosphere to 1.12.0, which added support for 23.0.1, and use the Hekate+AMS-package3-sigpatches-Atmosphere-1.12.0-master-28d6a2e11-cfw-23.0.0 sigpatches that you graciously shared, could I update my firmware to 23.0.1 right away?
 
Nynrah said:
Just to make sure I'm reading this right, but if I upgrade my Atmosphere to 1.12.0, which added support for 23.0.1, and use the Hekate+AMS-package3-sigpatches-Atmosphere-1.12.0-master-28d6a2e11-cfw-23.0.0 sigpatches that you graciously shared, could I update my firmware to 23.0.1 right away?
Click to expand...
there's zero official nintendo sysmodules that changed in 23.0.1, so yes.
 
  • Like
Reactions: Nynrah and Blythe93
Nynrah said:
Just to make sure I'm reading this right, but if I upgrade my Atmosphere to 1.12.0, which added support for 23.0.1, and use the Hekate+AMS-package3-sigpatches-Atmosphere-1.12.0-master-28d6a2e11-cfw-23.0.0 sigpatches that you graciously shared, could I update my firmware to 23.0.1 right away?
Click to expand...
Just make sure you don't go online with it so your system doesn't get banned right now DNS.MTIM is in the process of being incorporated into the new atmosphere 1.12.1
 
  • Like
Reactions: Nynrah
froggy55 said:
Just make sure you don't go online with it so your system doesn't get banned right now DNS.MTIM is in the process of being incorporated into the new atmosphere 1.12.1
Click to expand...
I play disconnected in airplane mode 99,9% of the time, but I suppose it can't hurt to wait for atmosphere 1.12.1.
 
bth said:
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)
Click to expand...
Dude, I just made an account in this forum to thank you, I updated my Switch today to try out the nextendo thing and all my games crashed each time, using this patch fixed the issue, the 22.0 sigpatch didn't work and the sys-patch thing I also have it there but doesn't work either (I can access that stuff from the tesla shortcut and modify configs), I was about to nuke the console until I find your update.

Again THANK YOU, that package recover my console!!
 
  • Like
Reactions: Blythe93
Price023 said:
Dude, I just made an account in this forum to thank you, I updated my Switch today to try out the nextendo thing and all my games crashed each time, using this patch fixed the issue, the 22.0 sigpatch didn't work and the sys-patch thing I also have it there but doesn't work either (I can access that stuff from the tesla shortcut and modify configs), I was about to nuke the console until I find your update.

Again THANK YOU, that package recover my console!!
Click to expand...
the sys-patch overlay has nothing to do with sys-patch, you seeing and editing anything it it, is purely cosmetic.
it's only function is to read and edit config file (which sys-patch reads, sure, but it is not a confirmation sys-patch is even on the sd card)

it does not indicate sys-patch being active, the log files do.
sys-patch has the exact same patches, so "them not working" is indicator of not actually running sys-patch


edit:
honestly, my atmosphere fork with embedded patches which are agnostic of hekate/fusee, and makes the question of sys-patch or "sigpatches" not working not matter, is most likely a counter to people doing dumb things.

https://github.com/borntohonk/Atmosphere/releases/latest

(naturally if you're dum-dum and overwrite package3 with anything else, it stops being my fork)



(not sure why so many people enter this thread seemingly with sys-patch not running, but for some reason have the overlay? is some small brained bundle creator only including the overlay....?

does sys-patch not work at all on 23.0.0/ 23.0.1? im getting conflicting messages here.... someone is doing something stupid or it doesnt work at all on 23.0.0/ 23.0.1)


can someone who doesn't heave peanut sized brain, confirm if it (sys-patch 1.6.2.3) works on 23.0.0/ 23.0.1 (no .ips patches present - no kip1patch hekate_ipl.ini - nosigchk line gone - no patches.ini)

what works or not:
xci cartridge install work on 23.0.0 / 23.0.1(y/n?)
forwarder install work on 23.0.0/ 23.0.1 (y/n?)
both work after install or existing install on 23.0.0/ 23.0.1 (y/n?)

regular .nsp install work on 23.0.0/ 23.0.1 (y/n?)


if one or more parts of this doesn't work, then svc debug memory edits dont work on 23.0.0/ 23.0.1


if cause is a bundle creator only including overlay, please message the bundle creator and tell him that he is stupid.
 
Last edited by bth,
  • Like
Reactions: Ngacoi and Blythe93
bth said:
the sys-patch overlay has nothing to do with sys-patch, you seeing and editing anything it it, is purely cosmetic.
it's only function is to read and edit config file (which sys-patch reads, sure, but it is not a confirmation sys-patch is even on the sd card)

it does not indicate sys-patch being active, the log files do.
sys-patch has the exact same patches, so "them not working" is indicator of not actually running sys-patch


edit:
honestly, my atmosphere fork with embedded patches which are agnostic of hekate/fusee, and makes the question of sys-patch or "sigpatches" not working not matter, is most likely a counter to people doing dumb things.

https://github.com/borntohonk/Atmosphere/releases/latest

(naturally if you're dum-dum and overwrite package3 with anything else, it stops being my fork)



(not sure why so many people enter this thread seemingly with sys-patch not running, but for some reason have the overlay? is some small brained bundle creator only including the overlay....?

does sys-patch not work at all on 23.0.0/ 23.0.1? im getting conflicting messages here.... someone is doing something stupid or it doesnt work at all on 23.0.0/ 23.0.1)


can someone who doesn't heave peanut sized brain, confirm if it (sys-patch 1.6.2.3) works on 23.0.0/ 23.0.1 (no .ips patches present - no kip1patch hekate_ipl.ini - nosigchk line gone - no patches.ini)

what works or not:
xci cartridge install work on 23.0.0 / 23.0.1(y/n?)
forwarder install work on 23.0.0/ 23.0.1 (y/n?)
both work after install or existing install on 23.0.0/ 23.0.1 (y/n?)

regular .nsp install work on 23.0.0/ 23.0.1 (y/n?)


if one or more parts of this doesn't work, then svc debug memory edits dont work on 23.0.0/ 23.0.1


if cause is a bundle creator only including overlay, please message the bundle creator and tell him that he is stupid.
Click to expand...
mariko
ofw 23.0.1-->emummc 23.0.1
atmosphere 1.12.0v4 749dccba6

sys-patch 1.6.2.3-76d48fa
noncasigchk_17.0.0+ orange
nocntchk_19.0.0+ orange
am_homebrew:fix22.0.0+ red

[exosphere]
debugmode=1
debugmode_user=0
disable_user_exception_handlers=0
enable_user_pmu_access=0
blank_prodinfo_sysmmc=1
blank_prodinfo_emummc=1
allow_writing_to_cal_sysmmc=0
log_port=0
log_baud_rate=115200
log_inverted=0

hekate_ipl
emummc
pkg3=atmosphere/package3
emummcforce=1
cal0blank=1

dump card xci ->ok
forwarder ----->ok
Installazione NSP --->ok

go to eshop account nnid -crash atmosphere 2210-1024 program 010...1042
go to eshop account local generic error (no crash atmosphere) 2123-0011
error to exit homebrew
 
Last edited by LuigiGad,
LuigiGad said:
mariko
ofw 23.0.1-->emummc 23.0.1
atmosphere 1.12.0v4 749dccba6

sys-patch 1.6.2.3-76d48fa
noncasigchk_17.0.0+ orange
nocntchk_19.0.0+ orange
am_homebrew:fix22.0.0+ red

[exosphere]
debugmode=1
debugmode_user=0
disable_user_exception_handlers=0
enable_user_pmu_access=0
blank_prodinfo_sysmmc=1
blank_prodinfo_emummc=1
allow_writing_to_cal_sysmmc=0
log_port=0
log_baud_rate=115200
log_inverted=0

hekate_ipl
emummc
pkg3=atmosphere/package3
emummcforce=1
cal0blank=1

dump card xci ->ok
forwarder ----->ok
Installazione NSP --->ok

go to eshop account nnid -crash atmosphere 2210-1024 program 010...1042
go to eshop account local generic error (no crash atmosphere) 2123-0011
error to exit homebrew
Click to expand...
well yes, i know my fork works, i asked about sys-patch paired with official atmosphere, my fork doesn't use sys-patch or sigpatches, and does patching different than how sys-patch does it (sys-patch requires using svc debugmemory edit)

my fork blocks nintendo domains and also forces exosphere blanker, cannot go to eshop.

https://github.com/borntohonk/Atmosphere/releases/tag/1.12.1_dns_mitm_and_qlaunch_fix (this is regular atmosphere latest commit)
https://github.com/impeeza/sys-patch/releases/tag/v1.6.2.3

tl:dr i need confirmation sys-patch works, without my fork, plain atmosphere, no sigpatches (zero .ips, zero hekate patches)


xci cartridge install work on 23.0.0 / 23.0.1(y/n?) (no, not if you can "dump" cartridge)
forwarder install work on 23.0.0/ 23.0.1 (y/n?)
both work after install or existing install on 23.0.0/ 23.0.1 (y/n?)

regular .nsp install work on 23.0.0/ 23.0.1 (y/n?)

all that was installed plays / starts (y/n?)

I need to know the real answer, because if it doesn't work, then sys-patch might be deprecated as i doubt atmosphere will fix that svc debugmemoryedit if it's broken

(also naming colors from sys-patch overlay (orange/red/green) means nothing to me. provide log file from /config/sys-patch/log.ini instead - from plain atmosphere, no .ips sigpatches, only sys-patch)
(am_homebrew) only required 22.0.0, not 22.5.0+, worthless 23.0.0. only FS patches + es patch matters and result of if installs work)

josete2k said:
Yes, it's an issue with latest AMS.

It will be fixed in 1.12.1
Click to expand...


I am keeping the patches for more memory in my fork, so unless 1.12.1 fixes it without removing it, i am keeping it that way. - dont care about crash eshop, cant use eshop with my fork anyway
 
Last edited by bth,
  • Like
Reactions: Blythe93

Site & Scene News

New Hot Discussed User Submitted

Go to forum More news

Popular threads in this forum