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

bth · 2026-08-12T12:34:04+0100

kyuuemu said:
After installing this fork all homebrew apps instantly crashed Atmosphere and threw me back into Hekate. Reverting to the original Atmosphere fixed it. Using it with with sys-patch and everything seems to work.

that doesnt make much sense, most likely have homebrew of the outdated ABI.

my fork doesn't crash homebrew that has the new homebrew ABI.

kyuuemu · 2026-08-12T15:58:44+0100

bth said:
that doesnt make much sense, most likely have homebrew of the outdated ABI.

my fork doesn't crash homebrew that has the new homebrew ABI.

no it has nothing to do with the ABI, it affected literally every homebrew app including the ones Atmosphere ships with

and reverting to same original Atmosphere version fixed it which is the exact same ABI

bth · 2026-08-12T18:56:10+0100

kyuuemu said:
no it has nothing to do with the ABI, it affected literally every homebrew app including the ones Atmosphere ships with

and reverting to same original Atmosphere version fixed it which is the exact same ABI

That doesn't make much sense. When compiling atmosphere, you compile every homebrew atmosphere normally ships with.

even if theoretically something was compiler linked to libnx version, other ABI, and so on, those homebrew would be compile time linked to the atmosphere fork.

for atmosphere, the only included homebrew .nro's are the usb mtp one, daybreak (firmware upgrade/downgrader) and reboot_to_payload, all of which is compiled while compiling atmosphere

that and /atmosphere/hbl.nsp (homebrew launcher ship/trampoline) + ./hbmenu.nro (what you launch opening album) (these two are not compiled fresh during releases, but rather includes the latest versions from switchbrew)

tl:dr sounds like problem caused by something else, not my fork.

TheOnlyUser2431 · 2026-08-13T01:43:05+0100

getting a bit of conflicting answers that kind of confuses me
so to clarify:

Blythe93 said:
Yes and yes. bth is actually the mastermind behind that fork and the sys-patch and so far he's been pretty quick to release the updates whenever they were necessary.

kyuuemu is stting that the fork is bad (which im confused on since the HB app doesn't work) does this mean that when i use bth's build, i have to reinstall every homebrew app? (or is each HB app coded to only the official atmosphere version)

Also, if I replace the current sigpatches with sys-patches when I update, i won't be able to boot into any games? (As in I have to reinstall each one).

bth · 2026-08-13T07:24:12+0100

TheOnlyUser2431 said:
getting a bit of conflicting answers that kind of confuses me
so to clarify:

kyuuemu is stting that the fork is bad (which im confused on since the HB app doesn't work) does this mean that when i use bth's build, i have to reinstall every homebrew app? (or is each HB app coded to only the official atmosphere version)

Also, if I replace the current sigpatches with sys-patches when I update, i won't be able to boot into any games? (As in I have to reinstall each one).

you don't "install" homebrew, if you people mean pirated games, stop calling those "homebrew apps".

so no, you don't have to "reinstall" any homebrew, and whatever problems he has is not with the fork. (providing crash report / fatal report proof of crash would easily allow me to debunk or correct whatever is alleged wrong)

(more than probable he's using a modified package3 bundle unrelated to my fork to force compatability with tinfoil or dbi - which are on the old ABI - which would also overwrite the fork entirely - as the fork makes changes to mesosphere and loader to embed pattern based patch mechanisms directly into the kernel and loader kernel plugin, and both are provided to atmosphere via package3 / hekate's boot method also loads package3

reminder that this is open source:
https://github.com/borntohonk/Atmosphere/commit/6e84ebbde51fa8cde12ff73f5f1e77f406260c0f
)

kyuuemu · 2026-08-13T07:50:42+0100

bth said:
That doesn't make much sense. When compiling atmosphere, you compile every homebrew atmosphere normally ships with.

even if theoretically something was compiler linked to libnx version, other ABI, and so on, those homebrew would be compile time linked to the atmosphere fork.

for atmosphere, the only included homebrew .nro's are the usb mtp one, daybreak (firmware upgrade/downgrader) and reboot_to_payload, all of which is compiled while compiling atmosphere

that and /atmosphere/hbl.nsp (homebrew launcher ship/trampoline) + ./hbmenu.nro (what you launch opening album) (these two are not compiled fresh during releases, but rather includes the latest versions from switchbrew)

tl:dr sounds like problem caused by something else, not my fork.

yes daybreak and usb mtp also broke and crashed atmosphere

sure it could be something else im not making a diagnosis, merely that for me when i used the fork launching any homebrew apps crashed atmosphere

it could be something else, my install is very very old by now so maybe I have some random stuff in there, point being original atmosphere works fine if someone has the same experience they know they're not alone

if you want i can collect logs or something when i have time

bth · 2026-08-13T08:12:47+0100

kyuuemu said:
yes daybreak and usb mtp also broke and crashed atmosphere

sure it could be something else im not making a diagnosis, merely that for me when i used the fork launching any homebrew apps crashed atmosphere

it could be something else, my install is very very old by now so maybe I have some random stuff in there, point being original atmosphere works fine if someone has the same experience they know they're not alone

if you want i can collect logs or something when i have time

im doubting the very existence of alleged problem, and am requesting crash and/or fatal crash reports to substantiate claim. As the more likely outcome is something foreign causing whatever problem (which the fatal/crash report would indicate to me almost instantly)

kyuuemu · 2026-08-13T10:03:08+0100

bth said:
im doubting the very existence of alleged problem, and am requesting crash and/or fatal crash reports to substantiate claim. As the more likely outcome is something foreign causing whatever problem (which the fatal/crash report would indicate to me almost instantly)

here are the crash logs from yesterday

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

Well-Known Member

Member

Well-Known Member

Member

Well-Known Member

Member

Well-Known Member

Member

Attachments

Similar threads

Popular threads in this forum