Homebrew Homebrew app sys-patch - sysmod that patches on boot

I don't want to convince you in any way to add erpt patch....but, isn't sys-patch already messing with atmosphère way of work ?? As sciresM stated numerous times, he is against piracy, and sys-patch is obviously used a lot for that :ph34r:

so adding erpt patch would just mess a little bit more with atmosphère way of work :bow:
and it could be added as an opt-in, so every user would have CHOICE.


erpt reports are useless for 99.9% of users....even if I respect the work behind atmosphere, forcing debug is NOT a good behavior (on any software).



BTW, even without erpt patch, thanks impeeza and bth for updating sys-patch.
And thanks josete2k for giving us the choice :wink:

Seconded.
ERPT is mainly useful to nintendo, and to atmos developers as a collateral effect so they can debug obscure bugs. For the average user, it has no use, and may cause slowdowns.
Furthermore, it hammers the flash media, which is bad in the long term. Especially, in an emunand environment. I guess that while in stock mode it is fine, though.
 
To be fair, it should only write enough ERPT reports to cause a slowdown if something else went really wrong, and those slowdowns might well be the only clue the average user gets about that.
 
if it's to be merged in, it should default to disabled, just like the ssl patches i added in (which really should be enabled by no one aside from the people who even knows what it is for)

*should be noted i don't really agree with erpt patch
DONE!!!

ERPT patch is disabled by default.

EDIT: removed
 
Last edited by josete2k,
Does SYS-Patch needs to be upgraded to latest Atmosphère?

On my log file the line noacidsigchk=Patched (sys-patch) obviously I can not see the overlay because UltraHand crashes so far. but seems SYS-Patch 1.5.7 patches Atmosphère; right?
Post automatically merged:

DONE!!!

ERPT patch is disabled by default.
If you like to share the source I will try to put on the next version of the github. so far a upgrade to Atmosphère 1.10.0 acidsigcheck work again.
 
Last edited by impeeza,
Does SYS-Patch needs to be upgraded to latest Atmosphère?

On my log file the line noacidsigchk=Patched (sys-patch) obviously I can not see the overlay because UltraHand crashes so far. but seems SYS-Patch 1.5.7 patches Atmosphère; right?
Post automatically merged:


If you like to share the source I will try to put on the next version of the github. so far a upgrade to Atmosphère 1.10.0 acidsigcheck work again.
UltraHand is already compatible with latest AMS

Here's the recompiled SYS-PATCH


EDIT: seems we need new loader patch
EDIT2: reverted to previous LDR patch
Post automatically merged:

Does SYS-Patch needs to be upgraded to latest Atmosphère?

On my log file the line noacidsigchk=Patched (sys-patch) obviously I can not see the overlay because UltraHand crashes so far. but seems SYS-Patch 1.5.7 patches Atmosphère; right?
Post automatically merged:


If you like to share the source I will try to put on the next version of the github. so far a upgrade to Atmosphère 1.10.0 acidsigcheck work again.
Revert LDR patch is needed
 

Attachments

Last edited by josete2k,
NICEEEEE. Tested and working.

with no erpt
Post automatically merged:

I still can't boot a game with this.
Do you have extra sysmodules?

I can launch freshly installed games with no issue (fresh and clean emunand too).
 

Attachments

  • Like
Reactions: Blythe93 and Tyvar1
NICEEEEE. Tested and working.

with no erpt
Post automatically merged:


Do you have extra sysmodules?

I can launch freshly installed games with no issue (fresh and clean emunand too).
same errors as before. only have the new status monitor overlay and ultrahand
 
I still can't boot a game with this.

Strange all releases i test of sys-patch can't boot somes games, if i re-install a game it's ok

unrelated, you (both) have booted without ES patch (at least once) and invalidated your ncm records / ticketbin entries. you have to redo the titlekey installation for all affected games that aren't cartridge ncas

seeing as most people do not have just the titlekeys easily at hand, that means re-installing "the entire game", yes

for reference, sys-patch's es string was not broken at all for 21.0.0, so you (both) for whatever reason either booted "stock", or no cfw at all, or for reasons unknown to me, booted without patches at all.


the only thing missing FS and acidsigpatches (from atmosphere's loader) does, is being unable to start tinfoil and/or homebrew, all which need to be recompiled for atmosphere 1.10.0 / 21.0.0 anyway, so yeah. you will be unable to start forwarders and tinfoil regardless, but installed games should not be affected at all(* unless they are signature broken or cartridge/xci installs/xci to nsp conversions)) , as the es string was not broken in even sys-patch 1.5.6 (for 21.0.0 !)
 
Last edited by bth,
I mention this because previously, when updating the pack and firmware, I didn't have this need to reinstall.
After that, you can simply reinstall if needed; it's not a real problem.
:)
thanks for the feedback, but unfortunately user-caused errors mishandling basic cfw usage, is beyond the scope of what can be addressed.

sys-patch requires being on the sd card, and to be loader by atmosphere's "loader" module, which requires not booting with "stock" (hekate-concept). The end user choosing to boot without sys-patch, and also not an exefs .ips patch for ES, will have their non-genuine tickets invalidated. (* not that having the exefs .ips patch matters in booting "stock", as that also is loaded from atmospere's "loader".)

non-genuine tickets being invalidated, means your software/games won't start, without re-installing them in an enviroment where ES's signature check for the ticketbin is... removed
 
not working for me either not with 158 or sys-patch_noerpt
Post automatically merged:

thanks for the feedback, but unfortunately user-caused errors mishandling basic cfw usage, is beyond the scope of what can be addressed.

sys-patch requires being on the sd card, and to be loader by atmosphere's "loader" module, which requires not booting with "stock" (hekate-concept). The end user choosing to boot without sys-patch, and also not an exefs .ips patch for ES, will have their non-genuine tickets invalidated. (* not that having the exefs .ips patch matters in booting "stock", as that also is loaded from atmospere's "loader".)

non-genuine tickets being invalidated, means your software/games won't start, without re-installing them in an enviroment where ES's signature check for the ticketbin is... removed
So what is the correct procedure ?
 
tried reinstalling with awoo since it is the only installer updated (i think) and it just tries to connect to internet and verify info

Same for me. Anyway I just needed to check if my ldn_mitm version was working. NRO at least doesn't crash but I can't test it with games.
 

Site & Scene News

Popular threads in this forum