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

  • Thread starter Thread starter ShadowOne333
  • Start date Start date
  • Views Views 5,323,438
  • Replies Replies 7,368
  • Likes Likes 266
Patches don't work.

Sys-patch doesn't work too
 

Attachments

  • 17284594850986437942374142084467.jpg
    17284594850986437942374142084467.jpg
    1.8 MB · Views: 95
  • 17284595102117399506838425082483.jpg
    17284595102117399506838425082483.jpg
    1.9 MB · Views: 93
Last edited by josete2k,
Do you create loader patch or patched AMS sources? If you do not do any of that that's why nothing works.
Yes, I patched fusee for kip ips support
Loader is patched by sys-patch


So:
Forwarders ok
Nsp ko
 

Attachments

  • 17284618297862704012870204868945.jpg
    17284618297862704012870204868945.jpg
    1.8 MB · Views: 85
Last edited by josete2k,
Yes.

Green means patched by sys-patch
Orange means patched by ips

Red not patched
If you have red lines: your syspatch not up to date and can not patch all needed places. If you have green - it means you missed some IPS patches. If you have both: your setup not complete.
Post automatically merged:

But ips and sys-patch are searching same pattern...
Absolutely not. IPS does not search any pattern at all. It just patch at fixed address.
Post automatically merged:

That's why I use only sigpatches. I want to be sure that files are patched at correct place and not at any first place that matches pattern. Are you aware that sys-patch only search for first match of the pattern and does not check if there are others?
 
  • Like
Reactions: josete2k
If you have red lines: your syspatch not up to date and can not patch all needed places. If you have green - it means you missed some IPS patches. If you have both: your setup not complete.
Post automatically merged:


Absolutely not. IPS does not search any pattern at all. It just patch at fixed address.

I think we are writing the same. Sorry if I can't explain fine...


IPS patches are made with mrdude's ips patch generator... So I mean that patches generated with that app are generated by searching that pattern. And it seems that's not found in the firmware files (the pattern)...

That's why I use only sigpatches. I want to be sure that files are patched at correct place and not at any first place that matches pattern. Are you aware that sys-patch only search for first match of the pattern and does not check if there are others?


I absolutely don't know 🥲
 
I see now. I mean IPS patches made manually by disassembling fw.
Post automatically merged:

@impeeza, are your sigpatches auto-generated or you made it youself?
Are generated by IPS Patch Creator with updated patterns for FW 19 as published before.

@josete2k can you test creating sigpatches for your Atmosphère build using also IPS Patch Creator and test with the full set of patches
 
Are generated by IPS Patch Creator with updated patterns for FW 19 as published before.

@josete2k can you test creating sigpatches for your Atmosphère build using also IPS Patch Creator and test with the full set of patches
OK, i'll try in a few hours.

Where's the updated generator?
 
I am looking for them miniminx published them this week.

For firmware 19 you need to add:
https://gbatemp.net/threads/switch-...tibility-with-atmosphere.661715/post-10511594

for new atmosphere normally you don´t need change nothing
It's pointless for now that 19 branch still needs lots of work to be done (especially for fusee/loader):

https://github.com/Atmosphere-NX/Atmosphere/issues/2386

Tyring to test patches for now is pointless until everything is done, don't waste your time.
 
Tyring to test patches for now is pointless until everything is done,
Why not? If you know what to test toy can test. I just tested sigpatches and they are working. No big changes. I do not use auto patcher, because prefer to do sig patches the old way.
 

Site & Scene News

Popular threads in this forum