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

dogtygr · May 5, 2024

guily6669 said:
I don't get it, I changed back to my Hekate with fusee payload and all games work fine and I only have Hekate Sigpatches posted by Impeeza, the only thing that doesn't work is tinfoil however even with FSS0 was already getting corrupted due to beta testing new OC with erista CPU UV support.

Either that or tinfoil is working bad with atmos 1.7.0 cause it was self corrupting, then after a few restarts was OK, completely deleting and downloading it again just opening the installer would still throw a error sometimes, had to do it a few times until it worked (all of this with FSS0 and Hekate Sigpatches but never happened before beta testing the new upcoming OC for erista and Atmos 1.6.2)...

However now currently everytime I change to FSS0 tinfoil works and going back to fusee it stop working but all games work fine

I don't have sys-patch, shouldn't the installed games stop working with atmos 1.7.0 fusee??

My original hekate fusee payload settings:

Code:

[config] autoboot=0 autoboot_list=0 bootwait=3 backlight=47 noticker=0 autohosoff=0 autonogc=1 updater2p=0 bootprotect=0 [Atmosphere CFW] payload=bootloader/payloads/fusee.bin icon=bootloader/res/icon_payload.bmp [Stock SysNAND] fss0=atmosphere/package3 stock=1 emummc_force_disable=1 icon=bootloader/res/icon_switch.bmp

My FSS0 hekate settings:

Code:

[config] autoboot=0 autoboot_list=0 bootwait=3 noticker=0 autohosoff=0 autonogc=1 updater2p=0 backlight=47 [Atmosphere CFW] fss0=atmosphere/package3 kip1patch=nosigchk kip1=atmosphere/kips/loader.kip emummcforce=1 icon=bootloader/res/icon_payload.bmp [Atmosphere SAFE MODE] fss0=atmosphere/package3 kip1patch=nosigchk emummcforce=1 icon=bootloader/res/icon_payload.bmp [Stock - sysMMC] fss0=atmosphere/package3 emummc_force_disable=1 stock=1 icon=bootloader/res/icon_switch.bmp

Note: Had to add Safe mode cause hekate FSS0 is stupid enough not to boot if it doesn't detect loader.kip instead of just booting atmosphere without it like fusee payload which doesn't care if it's there or not...

Ps: I'm not using the modded fusee either... Does fusee only breaks new game installing and installed games still work fine???? (I thought without Sigpatches all games would stop working)

If you're not using sys-patch and you're using a custom fusee.bin file sigpatches don't include the kip ips files anymore because it is no longer officially supported you'll need to generate them yourself (via ips creator fron MrDude for example). That might be the reason why tinfoil doesn't work when you use fusee (because it needs the fs kip ips file) and your games work fine (you probably only have nsp files for your games and not xci ones)

Sunnyboy · May 5, 2024

i am on 18.0.1, every game i want to install wont work
is there a solution for this?

Blythe93 · May 5, 2024

Sunnyboy said:
i am on 18.0.1, every game i want to install wont work
is there a solution for this?

Did you update your sigpatches? If so, how are you booting into Atmosphere?

Atmosphere 1.7.0 no longer supports ips kip patches (check the release notes here) which are usually used for piracy reasons. Therefore you can:
1) Load Atmosphere's package3 via Hekate's FSS0 - You'll need to reboot to Hekate, go to Launch and select emuNAND CFW or sysNAND CFW (depending on which one you use). If you've downloaded the sigpatches from here. your bootloader/hekate_ipl.bin will already have everything you need to have configured.
2) Use sys-patch instead of sigpatches.
3) Use modified Atmosphere's fusee.bin payload with ips kip patches support.

Having both sigpatches and sys-patch at the same time should cause no conflict at all, but it's recommended to stick to one that works for you in order to reduce the clutter on your SD card since they are doing the same thing.

guily6669 · May 5, 2024

dogtygr said:
If you're not using sys-patch and you're using a custom fusee.bin file sigpatches don't include the kip ips files anymore because it is no longer officially supported you'll need to generate them yourself (via ips creator fron MrDude for example). That might be the reason why tinfoil doesn't work when you use fusee (because it needs the fs kip ips file) and you games work fine (you probably only have nsp files for your games and not xci ones)

And NSP games work without sigpatches??? cause I don't understand with original atmos 1.7.0 fusee payload using just latest hekate sigpatches and no sys-patch my games all worked just not tinfoil...

But anyway now I'm using latest Atmos sigpatches with modded fusee for sigpatches and without sys-patch and all is working nice, tinfoil is working again, but I still don't understand why would games work before if it was like it had no sigpatches since Fusee wouldn't load them...

Even tested 3 FW18 required games and work fine on FW 17.0.1 thanks to fusee payload instead of hekate FSS0

Sunnyboy · May 5, 2024

@

Blythe93

just reboot to emuNAND CFW
works perfect now THNX

dogtygr · May 5, 2024

guily6669 said:
And NSP games work without sigpatches??? cause I don't understand with original atmos 1.7.0 fusee payload using just latest hekate sigpatches and no sys-patch my games all worked just not tinfoil...

But anyway now I'm using latest Atmos sigpatches with modded fusee for sigpatches and without sys-patch and all is working nice, tinfoil is working again, but I still don't understand why would games work before if it was like it had no sigpatches since Fusee wouldn't load them...

Even tested 3 FW18 required games and work fine on FW 17.0.1 thanks to fusee payload instead of hekate FSS0

Nsp games work with the es patch which is still included in sigpatches the fusee bin doesn't load kip patches anymore but atmosphere still keeps the other patches

Entryjyt · May 7, 2024

impeeza said:
Well thanks to MrDude and the release of latest IPSPatchCreator here are the sigpatches for FW18.0.0

~~OP will be updated when full set of patches get available, there is no new Atmosphère Patches, well, because there is no new Atmosphère yet~~

Happy (pre)June 15th everybody! and the new COMPLETE set of sigpatches is Here, remember to use the latest Hekate on FSS0 Package 3 mode to be able to load the sigpatches, and/or use SYS-Patch Sysmodule.

I tried this and it still doesn't work. Now it says my games are corrupted.

Blythe93 · May 7, 2024

Entryjyt said:
I tried this and it still doesn't work. Now it says my games are corrupted.

Did you try with the latest patches? The ones from the post you've quoted are the 2nd latest.

impeeza · May 7, 2024

Try SYS-PAtch Sysmodule:

download latest from: https://gitflic.ru/project/impeeza/sys-patch/release

and follow the guide:

https://www.gamebrew.org/wiki/Sys-patch_Switch

on installation

Entryjyt · May 7, 2024

Blythe93 said:
Did you try with the latest patches? The ones from the post you've quoted are the 2nd latest.

That download said to have the latest sigpatches. Before downloading that one I tried getting sigpatches from the official site and it CLAIMED to support 18.0.0, but it didn't work for me.

Blythe93 · May 7, 2024

Entryjyt said:
That download said to have the latest sigpatches. Before downloading that one I tried getting sigpatches from the official site and it CLAIMED to support 18.0.0, but it didn't work for me.

How do you boot into Atmosphere? Via fusee.bin or via Hekate?

Atmosphere 1.7.0 no longer supports ips kip patches (check the release notes here) which are usually used for piracy reasons. That means that sigpatches won't work unless you:
1) Load Atmosphere's package3 via Hekate's FSS0 - You'll need to reboot to Hekate, go to Launch and select emuNAND CFW or sysNAND CFW (depending on which one you use). If you've downloaded the sigpatches from here. your bootloader/hekate_ipl.bin will already have everything you need to have configured.
2) Use modified Atmosphere's fusee.bin payload with ips kip patches support.

Your other option would be sys-patch that impeeza linked to. Having both sigpatches and sys-patch at the same time should cause no conflict at all, but it's recommended to stick to one that works for you in order to reduce the clutter on your SD card since they are doing the same thing.

Stellar · May 7, 2024

If I load Atmosphere's package3 via Hekate's FSS0, do I still need atmosphere/exefs_patches/ and atmosphere/kip_patches/, or did you only include those for people who may want to boot from a modified fusee.bin?

Draxzelex · May 7, 2024

Stellar said:
If I load Atmosphere's package3 via Hekate's FSS0, do I still need atmosphere/exefs_patches/ and atmosphere/kip_patches/, or did you only include those for people who may want to boot from a modified fusee.bin?

You need the exefs patches regardless of fusee or FSS0 because those patch ES. Loading Atmosphere via FSS0 uses the patches.ini to patch FS and Loader while the kip patches do that when booting using fusee.

impeeza · May 8, 2024

Stellar said:
If I load Atmosphere's package3 via Hekate's FSS0, do I still need atmosphere/exefs_patches/ and atmosphere/kip_patches/, or did you only include those for people who may want to boot from a modified fusee.bin?

only loading Atmosphère from Hekate's FSSO can load Kip patches.

Stellar · May 8, 2024

Well, I'm experiencing rare panic crashes on a clean emuNAND, made from a newly formatted sysNAND, on a fresh new card, and all I have installed is Atmosphere and sigpatches and nothing else.

This did not happen to me before updating from OFW16.X.X to 18.0.1 w/latest AMS.

I've tried my best to rule out the culprit: I was using sys-patch module with no sigpatches and using fusee.bin to boot and had this issue twice, and now I am using the latest sigpatches provided in this thread with no modules or anything else, and had this crash last night.

Partition based emuNAND, brand new microSD card, clean AMS with new patches.

TotalJustice · May 8, 2024

Info on the panic would be helpful, such as the module and error code. Sigpatches / sys-patch do not cause fatals, so you can already rule that out.

I'd wager it's nim causing the fatal as you probably wildcard block *nintendo* connection which causes a fatal on fw 17+

Stellar · May 8, 2024

TotalJustice said:
Info on the panic would be helpful, such as the module and error code. Sigpatches / sys-patch do not cause fatals, so you can already rule that out.

I'd wager it's nim causing the fatal as you probably wildcard block *nintendo* connection which causes a fatal on fw 17+

Oh my god you're right! I do use a hosts file with that exact wildcard.

Panic occurred while running Atmosphere.
Title ID: 010041544D530000
ERROR: DABRT (0x101)

Post automatically merged: May 8, 2024

This is my hosts file:

# Nintendo telemetry servers
127.0.0.1 receive-%.dg.srv.nintendo.net receive-%.er.srv.nintendo.net
# Block Nintendo Servers
127.0.0.1 *nintendo.*
127.0.0.1 *nintendo-europe.com
127.0.0.1 *nintendoswitch.*
95.216.149.205 *conntest.nintendowifi.net
95.216.149.205 *ctest.cdn.nintendo.net

TotalJustice · May 8, 2024

Stellar said:
Oh my god you're right! I do use a hosts file with that exact wildcard.

Panic occurred while running Atmosphere. Title ID: 010041544D530000 ERROR: DABRT (0x101)

Post automatically merged: May 8, 2024

This is my hosts file:

# Nintendo telemetry servers 127.0.0.1 receive-%.dg.srv.nintendo.net receive-%.er.srv.nintendo.net # Block Nintendo Servers 127.0.0.1 *nintendo.* 127.0.0.1 *nintendo-europe.com 127.0.0.1 *nintendoswitch.* 95.216.149.205 *conntest.nintendowifi.net 95.216.149.205 *ctest.cdn.nintendo.net

Oh that's not a nim fatal. Is your SD card exfat by any chance? Or you use Mac? Googling 010041544D530000 shows that it's either a corrupt SD card or archive bit.

Stellar · May 8, 2024

TotalJustice said:
Oh that's not a nim fatal. Is your SD card exfat by any chance? Or you use Mac? Googling 010041544D530000 shows that it's either a corrupt SD card or archive bit.

I really don't think it's a corrupt SD card.

I had this exact problem with a 1TB Sandisk I was using earlier with no issues on 16.X.X (and then started having issues on 18.0.1 with that card), but this card that I'm on right now is a completely brand new Samsung 512GB, I tested both cards and came up with no damaged sectors.

I'm not on a mac either.

I'm also using FAT32.

guily6669 · May 8, 2024

Stellar said:
Oh my god you're right! I do use a hosts file with that exact wildcard.

Panic occurred while running Atmosphere. Title ID: 010041544D530000 ERROR: DABRT (0x101)

Post automatically merged: May 8, 2024

This is my hosts file:

# Nintendo telemetry servers 127.0.0.1 receive-%.dg.srv.nintendo.net receive-%.er.srv.nintendo.net # Block Nintendo Servers 127.0.0.1 *nintendo.* 127.0.0.1 *nintendo-europe.com 127.0.0.1 *nintendoswitch.* 95.216.149.205 *conntest.nintendowifi.net 95.216.149.205 *ctest.cdn.nintendo.net

Always used it 4 years and 0 issues except I don't use sys-patch...

I'm using modded fusee with Sigpatches and no sys-patch.

I'm using atmos 1.7.0 and FW 17.0.1 here...

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

Member

Well-Known Member

The Treasure Tracker

GbaTemp is my Drug

Well-Known Member

Blythe93​

Member

Active Member

The Treasure Tracker

¡Kabito!

Active Member

The Treasure Tracker

Well-Known Member

Well-Known Member

¡Kabito!

Well-Known Member

Well-Known Member

Well-Known Member

Attachments

Well-Known Member

Well-Known Member

Attachments

GbaTemp is my Drug

Similar threads

Popular threads in this forum

Blythe93