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

impeeza · 2024-11-26T14:56:39+0000

Stigmatic said:
Wow. That was a really long way of saying you didn't understand that the patches impeeza made was improperly made.

If you read the posts I explicitly let everyone to know: I am not the creator, I just a mere hoarder and consolidate the code made by the masters, AND NO, the patches are not Wrong nor bad made, the patches are OK, BUT Atmosphère changed the way it works and now if you uses Fusee.bin as you bootloader some patches will be NOT APPLIED, so you need:

Use Hekate's FSS0 bootloader.
Use a modified Atmosphère code.
Use SYS-Patch, as complementary/replacement.

Your choice.

Stigmatic · 2024-11-26T15:37:05+0000

impeeza said:
If you read the posts I explicitly let everyone to know: I am not the creator, I just a mere hoarder and consolidate the code made by the masters, AND NO, the patches are not Wrong nor bad made, the patches are OK, BUT Atmosphère changed the way it works and now if you uses Fusee.bin as you bootloader some patches will be NOT APPLIED, so you need:

Use Hekate's FSS0 bootloader.

Use a modified Atmosphère code.

Use SYS-Patch, as complementary/replacement.

Your choice.

I'll be a lot more clear. The current (V5!) version of patches shared here seems to be fine after the few revisions made.
You made a fuckup originally and fixed it.

And bth said stupid things like:
"Right so.... .ips sigpatches should be considered deprecated for high level modules such as ES."
"if anything, i would consider this thread to be... redundant now? it doesn't serve purpose anymore other than for archival reasons as how things currently are."

When there's no issue when using Hekate with `kip1patch=nosigchk`. Which would've been working on day 1 if the patches were made correctly.

And yes fusee.bin doesn't load sigpatches like before but a modified version could be used like you both mentioned in a roundabout way.

impeeza · 2024-11-26T15:46:59+0000

Stigmatic said:
I'll be a lot more clear. The current (V5!) version of patches shared here seems to be fine after the few revisions made.
You made a fuckup originally and fixed it.

And bth said stupid things like:
"Right so.... .ips sigpatches should be considered deprecated for high level modules such as ES."
"if anything, i would consider this thread to be... redundant now? it doesn't serve purpose anymore other than for archival reasons as how things currently are."

When there's no issue when using Hekate with `kip1patch=nosigchk`. Which would've been working on day 1 if the patches were made correctly.

And yes fusee.bin doesn't load sigpatches like before but a modified version could be used like you both mentioned in a roundabout way.

Was 5 versions because the patches had to accommodate to different discoveries of the just released Firmware, and then versions 3 -5 was optimizations, initially two memory regions where patched, and after better understanding of the changes introduced by ninjas, the gurus realized that tow memory regions could be consolidated on one only. so both versions worked just fine, but latest version is more efficient.

bth · 2024-11-26T20:03:34+0000

Stigmatic said:
Wow. That was a really long way of saying you didn't understand that the patches impeeza made was improperly made.

I literally am the one who reverse engineered the ES patch and am credited for the pattern, among other things.
offset:
06 A3 F8
size:
00 04
patch:
E0 03 1F AA

as ips patch for moduleID 4A258ADE9176A7F263532C2A4C30187A0B00C012 (19.0.0+) loaded by atmosphere will cause the behavior the user who i replied to, for the reasons stated in the reply.

Stigmatic said:
When there's no issue when using Hekate with `kip1patch=nosigchk`. Which would've been working on day 1 if the patches were made correctly.

And yes fusee.bin doesn't load sigpatches like before but a modified version could be used like you both mentioned in a roundabout way.

hekate has nothing to do with any exefs patches, it only loads kip patches.

Blythe93 · 2024-11-26T22:05:06+0000

Is there any advantage of using sigpatches instead of sys-patch nowadays?

I've switched to sys-patch only few months ago and never had an issue with it. If it were up to me, It's still nice to have alternatives in form of sigpatches as well, but makes me wonder whether there's really any notable benefit of using them over sys-patch.

impeeza · 2024-11-26T22:05:43+0000

Blythe93 said:
Is there any advantage of using sigpatches instead of sys-patch nowadays?

I've switched to sys-patch only few months ago and never had an issue with it. If it were up to me, It's still nice to have alternatives in form of sigpatches as well, but makes me wonder whether there's really any notable benefit of using them over sys-patch.

No today, today SYS-Patch is the easy way to patch your console

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

¡Kabito!

Well-Known Member

¡Kabito!

Active Member

The Treasure Tracker

¡Kabito!

Similar threads

Popular threads in this forum