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

[jelbo]

Does sigpatch-updater update sys-patch?

 

[Blythe93]

Does sigpatch-updater update sys-patch?

This one should work.

 

[jelbo]

This one should work.

Yes, I have both, but I didn't look close enough. sigpatch-updater can update both sigpatches and sys-patch. At least, that's what it says in the app. My sys-patch 1.5.0 didn't get updated to 1.5.1 though, I had to do that myself.

 

[penna]

I need to know if I'm understanding this correctly.

We have two options:

Option 1 is install sys-patch by unzipping it to the root of the SD card, and then doing nothing else it just works.
Option 2 is update hetake_ipl.ini with the text in the OP, and then drag and drop the contents of the "Latest Sigpatches File" zip linked in the first post into the root of the SD card. After that you're good.

Am I missing anything? Why would I choose one of these avenues over the other?

 

[Blythe93]

We have two options:

Option 1 is install sys-patch by unzipping it to the root of the SD card, and then doing nothing else it just works.
Option 2 is update hetake_ipl.ini with the text in the OP, and then drag and drop the contents of the "Latest Sigpatches File" zip linked in the first post into the root of the SD card. After that you're good.

Option 1 is correct.
Option 2 - I'd add that you'll need to load Atomsphere's package3 via Hekate's FSS0 i.e. you'll need to boot into Hekate first and select one of the CFW options, based on whether you have emuMMC or sysMMC setup.
There's also an Option 3 - Use modified Atmosphere's fusee.bin payload with ips kip patches support. In that case, sigpatches will work just like they did before.

Why would I choose one of these avenues over the other?

I'd say that sys-patch is a bit better because:

• Requires updating only if something major breaks. (source) - e.g. when firmware 18.0.1 was released, sys-patch that was released for 18.0.0 worked just fine.
• Patching ldr will (likely) never need to be updated. (source) - Apparently, sigpatches used to break from time to time whenever a silent Atmosphere update was released.
• sys-patch outputs a log where you can see which patches are applied, which one failed and some other useful data, either via Tesla overlay or by reading the logs manually.
• Works with all of the standard CFW setups (i.e. whether you boot into Atmosphere via Hekate or fusee.bin)
• Has less files?

In the end, both of them do their job so it really comes down to whatever works better for you.
Using both of them is fine, too, but oftentimes unnecessary.

 

[viper3344]

Seems the NFIM patches indeed need a new IPS file.

New full set of patches:

Tried these. Says game cannot start. Then scans data and says its corrupted....
I am using the latest deepsea and sigpatches from this post.

FIXED IT!!

I was copying the sigpatches first THEN the deepsea files. The deepsea ini does not contain the below. So: when updating deepsea, replace the deepsea files first THAN the sigpatches


Ensure that hekate_ipl.ini in the bootloader folder has:
kip1patch=nosigchk
In the 2 sections below.

It prob wont when you update the deepsea files and overwrite that file. No matter, just go into the file and add that line so it reads like below

{--- Custom Firmware ---}
[CFW (SYSNAND)]
emummc_force_disable=1
fss0=atmosphere/package3
atmosphere=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp
kip1patch=nosigchk
{}

[CFW (EMUMMC)]
emummcforce=1
fss0=atmosphere/package3
atmosphere=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp
kip1patch=nosigchk
{}