Patches don't work.
Sys-patch doesn't work too
Sys-patch doesn't work too
Attachments
Last edited by josete2k,
How and where did you get Atmosphere 1.8.0?Patches don't work.
Sys-patch don't work too
Is the 1900_support branchHow and where did you get Atmosphere 1.8.0?
Do you create loader patch or patched AMS sources? If you do not do any of that that's why nothing works.Is the 1900_support branch
Yes, I patched fusee for kip ips supportDo you create loader patch or patched AMS sources? If you do not do any of that that's why nothing works.
Did you tried alone sigpatches and alone sys-patch?
Post automatically merged:
NSP does not work means ES not patched
Red means syspatch not found pattern. It does not mean that it is not patched by IPS. syspatch has no info about IPS.Red not patched
Sure.Red means syspatch not found pattern. It does not mean that it is not patched by IPS. syspatch has no info about IPS.
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.Yes.
Green means patched by sys-patch
Orange means patched by ips
Red not patched
Absolutely not. IPS does not search any pattern at all. It just patch at fixed address.But ips and sys-patch are searching same pattern...
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.
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 see now. I mean IPS patches made manually by disassembling fw.IPS patches are made with mrdude's ips patch generator...
Are generated by IPS Patch Creator with updated patterns for FW 19 as published before.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?
OK, i'll try in a few hours.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
https://disk.yandex.com/d/LEKGKbfDw-_pjAOK, i'll try in a few hours.
Where's the updated generator?
I am looking for them miniminx published them this week.Thanks... But... The patterns?
It's pointless for now that 19 branch still needs lots of work to be done (especially for fusee/loader):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
Thanks for the advice, sorry for abandon you fellow tempers, in a couple of hours will be riding my motorcycle going to the beach!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.
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.Tyring to test patches for now is pointless until everything is done,