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

jaysea

Well-Known Member
Member
Joined
Aug 17, 2009
Messages
287
Trophies
1
Age
46
XP
1,198
Country
Netherlands

impeeza

¡Kabito!
Member
Joined
Apr 5, 2011
Messages
6,695
Trophies
3
Age
46
Location
At my chair.
XP
19,973
Country
Colombia
I notice you have es6 patched (green) in your logs, but I don't see es7 anywhere which should be there.
Only patch that is still green for me is ctest and ofc the es6 unpatched.
Should I remove the config file for it to update to new version since in the log it says 1.5.0 still while I use your 1.5.2 file.
please this line of analysis on the SYS-Patch thread, on that thread some of your questions has been answered.
 

jaysea

Well-Known Member
Member
Joined
Aug 17, 2009
Messages
287
Trophies
1
Age
46
XP
1,198
Country
Netherlands
please this line of analysis on the SYS-Patch thread, on that thread some of your questions has been answered.
can you at least tell me what page I should look. I scanned quite a few and I see nothing of the info I should see according to you.

Edit: nvm I will just remove sys-patch and its config and log and just start over. Only other thing I could think of is the overlay in the 1.5.2 release not to be correct.

Edit2: the exefs.nsp seems to be different. Replaced it and will try again. The config didn't include the es7 and the log says it is 1.5.0. No idea where I messed up.

Edit3: cry, can't get it to make a proper config nor a proper log. I downloaded the version which is in the downloads section. Also the noacidsigchk is showing up as unpached now which It didn't before.

Edit4: I removed sys-patch folder, removed the overlay, removed config folder and the contents folder in atmosphere. Then unpacked the impeeza version of 1.5.2 and now the log is okay and includes es7. Not sure what wasn't replaced properly by overwriting files. Only ctest stays patched in green, but that is expected behaviour.
 
Last edited by jaysea,
  • Wow
  • Like
Reactions: Tokiwa and impeeza

BruceLee1972

Member
Newcomer
Joined
Oct 4, 2009
Messages
15
Trophies
1
XP
192
Country
Gambia, The
Sigpatches aren't working on your end. 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 modified Atmosphere's fusee.bin payload with ips kip patches support.
3) Use sys-patch instead of sigpatches.

Right now, sys-patch seems to work for everyone. I'm not sure what's wrong with sigpatches, to me it seems like they are incomplete. Therfore, just use sys-patch instead, for the time being or from now on.

Reboot after that and that's pretty much it, yes.


You can download sys-patch from here. Just drag and drop onto the root of your SD card. It should work on its own after reboot.
Optionally, you can install Tesla + nx-ovlloader as that will allow you to see whether sys-patch is working properly, after you press L + D-pad Down + R (Stick) combo, select sys-patch, followed by Log. If it says:
  1. Patched = the pattern it's searching for is already patched by sigpatches, so there's no need to patch it again;
  2. Patched = the pattern is patched by sys-patch (i.e. sigpatches are not present or haven't been applied on boot);
  3. Unpatched = the pattern wasn't found by sys-patch on the current system so there's no need to patch them (only present if you turn off the Version skip in the Options).


With that being said, I haven't tried sigpatches with modified fusee.bin yet. Not sure how different would that be compared to the loading Atmosphere's package3 via Hekate's FSS0? I've tried all of the sigpatches posted here as well and, based on what sys-patch log says, only ldr and es patches are Patched, nifm and fs are Patched. Sure, they may be searching for different patterns and stuff, but after I turned off sys-patch and rebooted, Paper Mario: The Thousand-Year Door stopped working for me and it returned an error that it may be corrupted. After I turned sys-patch on and rechecked the game, it worked just fine. My guess is that it didn't work because of fs patches didn't work for me and I've installed an unsigned/modified XCI or something.

Thankfully, sys-patch works properly, but it's a bit inconvenient for the people that are using sigpatches only.

3) Use sys-patch instead of sigpatches.
Thank you, now tinfoil works :)
 

alcab

Well-Known Member
Member
Joined
Nov 22, 2005
Messages
211
Trophies
1
Website
Visit site
XP
1,127
Country
******************************************************************
IMPORTANT
******************************************************************

With the help of:






A NEW SET OF SIGPATCHES FOR 18.1.0 has been created some changed and some where added. PLEASE TAKE NOTE AND UPGRADE YOURS (Note V2 was added to the end of the new file)

Thanks a lot! This new set of sigpatches seems to work properly when booting with this modified version of fusee.bin.


But I am still experiencing problems with some games when booting with Hekate's FSS0 package3 loading method.
 
  • Wow
Reactions: impeeza

whitezombie

Well-Known Member
Newcomer
Joined
Apr 11, 2021
Messages
85
Trophies
0
XP
1,168
Country
United States
I updated Atmosphere, Hekate, installed FW 18.1.0 via Daybreak, got updated keys from Lock_pick_RCM, put them in the tools folder in Sigpatch-IPS-Creator_1.5.7, created new Loader, ES, FS, NFIM patches, added them, updated the patches.ini, and everything works fine with the modified fusee using an unpatched Erista emuNAND. I disabled the sig patches, used sys-patch-1.5.2, and everything worked fine. Enabled sig patches, left sys-patch-1.5.2 enabled, and everything worked fine.

I tested this with below set up.

{------Atmosphere Emu------}
[Atmosphere (emuMMC)]
payload=bootloader/payloads/fusee.bin (modified)
{}

I also tested package3, no issues with sig patches only, no issue with sys-patch-1.5.2 only, no issue with both enabled.

{------Atmosphere Emu------}
[Atmosphere (emuMMC)]
fss0=atmosphere/package3
kip1patch=nosigchk
{}

Everything works fine for me, the same way I always update.
 
Last edited by whitezombie,

alcab

Well-Known Member
Member
Joined
Nov 22, 2005
Messages
211
Trophies
1
Website
Visit site
XP
1,127
Country
Please kindly confirm that everything works fine when having sys-patch disabled and booting with Hekate's FSS0 package3 loading method and having your self-made patch.ini file in the bootloader folder.

Because it doesn't work for me, even when using sigpatch-IPS-creator.

Thanks.
 

impeeza

¡Kabito!
Member
Joined
Apr 5, 2011
Messages
6,695
Trophies
3
Age
46
Location
At my chair.
XP
19,973
Country
Colombia
Well people, just for you people I just Upgraded my Main setup to FW 18.1.0 made the next tests:

Erista V1 Unpatched
Hekate 6.2.0
Atmosphere 1.7.1-e85bc4d (build by me)
Sigpatches from OP
Sys-Patch 1.5.2 https://gbatemp.net/download/sys-patch-1-5-2-binary-fw-18-1-0-atmosphere-1-7-1.38686/ OR https://disk.yandex.com/d/F-sKYz3dbLo-Sw

Tested booting Hekate's FSS0 loading of Package3 and booting directly fusee.bin and the Forwarders, Titles installed from XCI and NSP and a converted NSP work flawless.

Also tested with official atmosphere-1.7.1-master-39c201e37+hbl-2.4.4+hbmenu-3.6.0.zip and everything work fine!
Post automatically merged:

Please kindly confirm that everything works fine when having sys-patch disabled and booting with Hekate's FSS0 package3 loading method and having your self-made patch.ini file in the bootloader folder.

Because it doesn't work for me, even when using sigpatch-IPS-creator.

Thanks.
will do, please give me one moment.
Post automatically merged:

Please kindly confirm that everything works fine when having sys-patch disabled and booting with Hekate's FSS0 package3 loading method and having your self-made patch.ini file in the bootloader folder.

Because it doesn't work for me, even when using sigpatch-IPS-creator.

Thanks.
I just disabled SYS-Patch.

Loaded Latest Atmosphere using Hekate's FSS0 loading Package 3 method, and everything worked fine.

Even Booting Modified Fusee.bin to re enable FS patch loading all work fine

I am using the sigpatches at OP.
 
Last edited by impeeza,

whitezombie

Well-Known Member
Newcomer
Joined
Apr 11, 2021
Messages
85
Trophies
0
XP
1,168
Country
United States
Please kindly confirm that everything works fine when having sys-patch disabled and booting with Hekate's FSS0 package3 loading method and having your self-made patch.ini file in the bootloader folder.

Because it doesn't work for me, even when using sigpatch-IPS-creator.

Thanks.

Yes it works fine with package3, no sys-patch, sig patches. I tested that scenario as posted above.
 
Last edited by whitezombie,

alcab

Well-Known Member
Member
Joined
Nov 22, 2005
Messages
211
Trophies
1
Website
Visit site
XP
1,127
Country
Thanks a lot to both of you.
I do not understand what it is that I am doing wrong. I'll keep trying, but fortunately everything works flawlessly with sys-patch 1.5.2 or when using the sigpatches and booting with the modded version of fusee.bin.

Let's hope nothing breaks in the future!
 
  • Like
Reactions: Blythe93

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • K3Nv2 @ K3Nv2:
    Sparking zero is looking pretty good but not $70 good
  • HiradeGirl @ HiradeGirl:
    okay
  • BakerMan @ BakerMan:
    isn't sparking zero supposed to be accurate to their canon power too?
  • BakerMan @ BakerMan:
    meaning unlike dbfz a weaker character like nappa wouldn't stand a chance against someone stronger like broly
  • BakerMan @ BakerMan:
    aaalllright then, i guess i should hit the hay
  • K3Nv2 @ K3Nv2:
    People are complaining about flying in it I'm like wut that's half of what it is
    +1
  • BigOnYa @ BigOnYa:
    Surprise surprise, @HiradeGirl is back today
  • BigOnYa @ BigOnYa:
    Alright @SylverReZ you win, lets go double or nothing.
  • cearp @ cearp:
    good morning
    +2
  • O @ Olqase93:
    Hi, I need help whit my r4 r4itt new please
  • AncientBoi @ AncientBoi:
    🛌 Shhhhhhh
  • DinohScene @ DinohScene:
    homebrew your DSi and forgo the flashcard with NDS bootstrap or something along those lines
    +1
  • DinohScene @ DinohScene:
    it allows utilisation of the SD card for ROM storage
    +1
  • Psionic Roshambo @ Psionic Roshambo:
    Get a 3DS and do the same 🥰
  • AncientBoi @ AncientBoi:
    Nah. Just get a 3rd [3000 series] gen PSP.
    +2
  • Psionic Roshambo @ Psionic Roshambo:
    I like PSP on my Pi lol
  • Psionic Roshambo @ Psionic Roshambo:
    Gameboy Advanced SP emulator or GASP for short lol
    +1
  • RedColoredStars @ RedColoredStars:
    Finally got an appointment with an ENT, but it's not for another month. It's already been 4- days of loud ringing in my left ear, substantial pain on left side of my neck and left side on the back of my head. Doctors here at the regular clinic put me on a couple different meds for a month that did absolutely nothing, then they told me there's nothing more they can do for me despite being in pain and my ear sounding like im underwater and ringing.
  • RedColoredStars @ RedColoredStars:
    Then three chiropractor appointments which also didn't help at all so i didn't go to the 4th. Been trying to get ahold of this ENT clinic out of town for a week and finally got an appointment set up. But its not til the 17th of July so I have to suffer all this shit for nearly another month.
  • RedColoredStars @ RedColoredStars:
    I hope relief from all of this is on the way because I've felt so defeated and severaly lacking in sleep because of the pain and ringing.
  • AncientBoi @ AncientBoi:
    :sad::sad::sad: for RCS
  • Psionic Roshambo @ Psionic Roshambo:
    @RedColoredStars, Vegas nerve compression?
  • Psionic Roshambo @ Psionic Roshambo:
    Sometimes caused by spinal fluid buildup in that area
    Psionic Roshambo @ Psionic Roshambo: Sometimes caused by spinal fluid buildup in that area