Signature patches are created to be used alongside Atmosphere for loading certain homebrew from the home menu.
-
Download the latest release.
- If you use
fusee-primary.bin
to boot into atmosphere, downloadfusee.zip
. - If you use
fusee-secondary.bin
to boot into atmosphere, downloadhekate.zip
. - If you're unsure on which release to get then check your
hekate_ipl.ini
file located in your/bootloader/
folder.- If you have no such file, then get the
fusee.zip
release. - If you see the following line
payload=bootloader/payloads/fusee-primary.bin
in yourhekate_ipl.ini
file, downloadfusee.zip
. - If you see the following line
fss0=atmosphere/fusee-secondary.bin
in yourhekate_ipl.ini
file, downloadhekate.zip
.
- If you have no such file, then get the
- If you use
-
Unzip the release you've chosen into the root of your SD card.
- Make sure to click yes for overwriting any files and merging folders.
- Make sure the
/atmosphere/
folder in the zip merges with the atmosphere folder on your SD card! You should not have an/atmosphere/atmosphere/
folder, nor should you have an/sd/
,/fusee/
, or/hekate/
folder on your SD card.
-
Boot into atmosphere. You should now be using signature patches.
If you wish to start your CFW with Hekate, we highly suggest chainloading fusee-primary. This is the best method to boot Atmosphere without directly pushing fusee-primary.bin.
To chainload atmosphere place the latest fusee-primary.bin in /bootloader/payloads/
then edit your hekate_ipl.ini to contain the following,
[Atmosphere CFW]
payload=bootloader/payloads/fusee-primary.bin
I do not boot this way, and I suggest you don't either. The important thing to know about this method is that you need to grab the special hekate.zip and then edit your hekate_ipl.ini to contain kip1patch=nosigchk
. Like this:
[CFW - FSS0 SYS]
fss0=atmosphere/fusee-secondary.bin
kip1patch=nosigchk
emummc_force_disable=1
[CFW - FSS0 EMU]
fss0=atmosphere/fusee-secondary.bin
kip1patch=nosigchk
emummcforce=1
Usual sources are:
Repo is mostly automated.
This is just for educational purposes. Ask a homebrew developer if you need help with signature patches and remember to always respect all intellectual property rights and all local/international laws!