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

impeeza · Jun 3, 2024

masagrator said:
Dunno why loader ips patch works for you at all since it is a kip patch, and support for kip patches was removed with 1.7.0 release.

The Atmosphere code was modded to add again the code removed on commit 46a4357, for load KIP Patches using fusee.bin to load system.

I load Atmosphère with Hekate's FSS0 method, so the code removed on commit 46a4357 code doesn't matter.

Also Sys-Patch should take care of that even if you are using the official Atmosphere, and on this case is not happening.

E1ite007 · Jun 3, 2024

impeeza said:
What exactly LDR stands for?

Long distance relationship (?).

Isn't it refering to the loader services? The ones that're divided onto shell, debug monitor, and the process manager AFAK.

Dutt · Jun 4, 2024

Small Question tho while ppl are talking about it but why was Sys-patch removed from the hub.

burhansalih · Jun 4, 2024

Dutt said:
Small Question tho while ppl are talking about it but why was Sys-patch removed from the hub.

The Big N

Dutt · Jun 4, 2024

burhansalih said:
The Big N

ah yep doesn't surprise me..

ItsJustANick · Jun 4, 2024

impeeza said:
Guys, good night, Just for fun yesterday I build Atmosphère from latest code and discovered some weird behavior discovered by @josete2k

Let me describe the issue, first If I run the latest official release of Atmosphère (atmosphere-1.7.0-prerelease-35d93a7c4+hbl-2.4.4+hbmenu-3.6.0.zip) from GitHub and using the set of patches generated by the latest IPS Patch Creator: (I personally like ES2 version of IPS files)
View attachment 440521

And the SYS-Patch sysmodule shows everything as expected

View attachment 440520

Now I build the 05fde7b commit from Atmosphere GitHub repo, and created the Sigpatches also using IPS Patch Creator for this new Package3

View attachment 440523
View attachment 440524

Then updated my SD Card, and ensured to update the sigpatches too (even patches.ini)

Reboot the console and the noacidsigchk is mark as UNPATCHED (RED):
View attachment 440525

Two Questions:

What exactly LDR stands for?

Why on the latest version appears as not patched even if the IPS file generated by IPS Patch creator is on the SD Card?

any of the goods of patching have idea?

if any insterested, here are the build and sigpatches

Dunno but here's why it may not work if you build it from master :

Check the most recent commits on master (not included in 1.7.0)
Huge changes in ldr

ldr stands for Loader

Current sys-patch 1.5.1 may not work for the next atmosphere release, but still works for 1.7.0-35d93a7c4

1.7.0 was released on March 29th
Breaking commit 548b48b on master is from May 28th, will be integrated in the next release
"loader: update to reflect latest 18.0.0 changes"

Not even sure the sigpatches generated from ips patch creator 1.5.7 are still working neither
Next atmosphere release may completely break Loader patches, both generated and sys-patched

It's waaayyyy above my skills, better check with MrDude on this, i'm just pointing out the potential breaking changes here
Why are you building it from master anyway ? You are one step ahead from SciresM

impeeza · Jun 5, 2024

R3m0ved said:
Dunno but here's why it may not work if you build it from master :

View attachment 440764

Check the most recent commits on master (not included in 1.7.0)
Huge changes in ldr

ldr stands for Loader

Current sys-patch 1.5.1 may not work for the next atmosphere release, but still works for 1.7.0-35d93a7c4

1.7.0 was released on March 29th
Breaking commit 548b48b on master is from May 28th, will be integrated in the next release
"loader: update to reflect latest 18.0.0 changes"

Not even sure the sigpatches generated from ips patch creator 1.5.7 are still working neither
Next atmosphere release may completely break Loader patches, both generated and sys-patched

It's waaayyyy above my skills, better check with MrDude on this, i'm just pointing out the potential breaking changes here
Why are you building it from master anyway ? You are one step ahead from SciresM

It's supposed sys-patch do not needs upgrade for future Atmosphère updates, IPS Patch Creator was able to create patches but sys-patch is struggling

Post automatically merged: Jun 5, 2024

R3m0ved said:
You are one step ahead from SciresM

Master have the latest commits for be able to build using latest DevKitPro

ghjfdtg · Jun 5, 2024

burhansalih said:
The Big N

It has been explained some pages ago but sys-patch has been taken down as precaution when the author got a DMCA takedown for sigpatch updater. I have yet to hear from any takedowns of sys-patch and even if they try we can change sys-patch to load the pattern from the SD card so sys-patch doesn't contain anything that breaks the DMCA.

_padder · Jun 7, 2024

Just I am very confused about everything... sigpatches... sys-patch... whatever.
Please explain, what should I install? I installed cfw with the guide

Code:

nh-server github io /switch-guide/

.

Now booting to "Hekate" and start "Atmosphere fss0" on EmuNand with "fss0=atmosphere/package3" inside hekate_ipl.ini..
Hekate, Atmosphere, FW is all latest Version

Now what? I would like to install syspatch / sigpatches. But nothing is working currently. Thanks for helping ^^

impeeza · Jun 7, 2024

_padder said:
Just I am very confused about everything... sigpatches... sys-patch... whatever.
Please explain, what should I install? I installed cfw with the guide

Code:

nh-server github io /switch-guide/

.

Now booting to "Hekate" and start "Atmosphere fss0" on EmuNand with "fss0=atmosphere/package3" inside hekate_ipl.ini..
Hekate, Atmosphere, FW is all latest Version

Now what? I would like to install syspatch / sigpatches. But nothing is working currently. Thanks for helping ^^

You could read all about that on the OP and next post. A summary:

Atmosphere is a re-implementation of the Original OS of the console (HOS) with minor modifications to allow to run Homebrew.

You can apply SigPatches to your console to modify some behavior, like:

Change the Console BootLogo.
Disable FS checks -Needed to run XCI software and modified NSP-
Disable ES (E-ticket Services) checks -Needed to run NSP software-
Disable Internet Checking For some Software -NFIM-
etc.

So, if you want to run unsigned software you need to apply patches, the patches can be applied by several methods (or combination of them):

You can change the Atmosphère's source code to not check any signature and build a custom version.
Apply sigpatches trough .IPS files on Atmosphere/exefs_patches & Atmosphere/kip_patches folders (you need to load Atmosphère using Hekate's FSS0 method. (Well you can also change the Atmosphère's source code to reenable FS KIPs loading).
Run a sysmodule at startup of the console called SYS-PATCH which patch the memory «on the fly»

If you do not apply any Sigpatches to your console YOU ONLY WILLL BE ABLE TO RUN LEGAL AND SIGNED SOFTWARE and some Homebrew.

_padder · Jun 7, 2024

Ok. Thanks for the summary. I think it is very helpful for many other newcomers. I just need one thing. Why it is not working for me?...
Or in better:
What is currently recommended? (I guess sys-patch, thats why I am here.)
How to install it correctly ? (Well I can read this here, download and unpack on sd root, or something like this.)
Is Atmosphere latest compatible, or should we use another build? (I read something about that here, but iirc, that this applies to sigpatches.)

impeeza · Jun 7, 2024

_padder said:
Ok. Thanks for the summary. I think it is very helpful for many other newcomers. I just need one thing. Why it is not working for me?...
Or in better:
What is currently recommended? (I guess sys-patch, thats why I am here.)
How to install it correctly ? (Well I can read this here, download and unpack on sd root, or something like this.)
Is Atmosphere latest compatible, or should we use another build? (I read something about that here, but iirc, that this applies to sigpatches.)

https://rentry.co/SwitchHackingIsEasy

For noobs install sys-patch

ItsJustANick · Jun 8, 2024

impeeza said:
It's supposed sys-patch do not needs upgrade for future Atmosphère updates, IPS Patch Creator was able to create patches but sys-patch is struggling

Post automatically merged: Jun 5, 2024

Master have the latest commits for be able to build using latest DevKitPro

Something changed in they way loader module check NCA ACID Signatures
I would not be surprised if something broke during the update process

Did you try to install and launch some XCI's after the update ? What about NSP's ?

A good test suite to make sure all ES/FS/LDR sigpatches are working after updating atmo would be :
1- Install some XCI game cartridge dump
2- Patch it with NSP update
3- Run the game

4- Install some NSP eShop game
5- Run the game

Repeat all of the above with both generated sigpatches and sys-patch eboot methods

dogtygr · Jun 8, 2024

impeeza said:
Guys, good night, Just for fun yesterday I build Atmosphère from latest code and discovered some weird behavior discovered by @josete2k

Let me describe the issue, first If I run the latest official release of Atmosphère (atmosphere-1.7.0-prerelease-35d93a7c4+hbl-2.4.4+hbmenu-3.6.0.zip) from GitHub and using the set of patches generated by the latest IPS Patch Creator: (I personally like ES2 version of IPS files)
View attachment 440521

And the SYS-Patch sysmodule shows everything as expected

View attachment 440520

Now I build the 05fde7b commit from Atmosphere GitHub repo, and created the Sigpatches also using IPS Patch Creator for this new Package3

View attachment 440523
View attachment 440524

Then updated my SD Card, and ensured to update the sigpatches too (even patches.ini)

Reboot the console and the noacidsigchk is mark as UNPATCHED (RED):
View attachment 440525

Two Questions:

What exactly LDR stands for?

Why on the latest version appears as not patched even if the IPS file generated by IPS Patch creator is on the SD Card?

any of the goods of patching have idea?

if any insterested, here are the build and sigpatches

So as someone who has made a homebrew app that generates the sigpatches (it can do both; generate the sigpatches ala sys-patch or ala Mrdude) (that I cant share for obvious reasons) I have checked the code of MrDude and the sys patch one and the way the wildcards work on the different programs are different. commit 548b48b2a6351ecf8e373f0789be1cf38509df8d has made some huge modifications on the loader that might be the reason why one of the patches doesn't locate the right place to replace their patch. The only way to be sure which one does it correctly is to study the loader via IDA and check if the patches modify the loader in the right place. I might do that later on to check.

FRbaron · Jun 8, 2024

Maybe someone will need it. I made a fork with auto-assembly using GitHub actions.
ns-sys-patch in my profile pgalonza

@dogtygr Can you share articles, notes, code about patches? I am interested in this topic and study it a little in my free time.

impeeza · Jun 8, 2024

FRbaron said:
Maybe someone will need it. I made a fork with auto-assembly using GitHub actions.
ns-sys-patch in my profile pgalonza

@dogtygr Can you share articles, notes, code about patches? I am interested in this topic and study it a little in my free time.

ha ha ha, I know the one you forked from

dogtygr · Jun 8, 2024

So I checked the changes made in the atmosphere code. They made some tiny changes on the validation of the Acid signature that's why the usual way the patches look for the right place doesnt wprk. The thing is it is pretty easy to change the atmosphere code to not check for the acidsignature all you have to do is change two lines on the code. Below is a patch of what needs to be modified. It seems to work on my hand but I haven't fully tested it. With that it is easy to know what to change to make a sigpatch. I'll look into it maybe tomorrow or next week

@FRbaron it is a combination of reading the code and documenting yourself by reading articles on https://switchbrew.org/.

josete2k · Jun 8, 2024

dogtygr said:
So I checked the changes made in the atmosphere code. They made some tiny changes on the validation of the Acid signature that's why the usual way the patches look for the right place doesnt wprk. The thing is it is pretty easy to change the atmosphere code to not check for the acidsignature all you have to do is change two lines on the code. Below is a patch of what needs to be modified. It seems to work on my hand but I haven't fully tested it. With that it is easy to know what to change to make a sigpatch. I'll look into it maybe tomorrow or next week

@FRbaron it is a combination of reading the code and documenting yourself by reading articles on https://switchbrew.org/.

One question...

As Mr Dude's ips patch creator can patch the loader with the new AMS commit, could its pattern be added to sys-patch?

dogtygr · Jun 9, 2024

josete2k said:
One question...

As Mr Dude's ips patch creator can patch the loader with the new AMS commit, could its pattern be added to sys-patch?

yes it can

Edit: I havent tested MrDude patches did you guys test it with them? Does it work?

ItsJustANick · Jun 9, 2024

josete2k said:
One question...

As Mr Dude's ips patch creator can patch the loader with the new AMS commit, could its pattern be added to sys-patch?

I thought it was the same pattern, MrDude's repo is hidden, no way to be sure but ask him directly
Also generated sigpatches from IpsPatchCreator might be also bugged, depends on his code and error handling but again, sources are hidden for now

An OK status from a software does not mean everything works
My guess is pattern must be adjusted for both IpsPatchCreator and sys-patch

Is anyone have sourcecode from IpsPatchCreator 1.5.7 ?
Only way to be sure is to run a test suite like i mentioned before with generated sigpatches, or read and compare the sourcecode
Fresh install of XCIs, NSPs and run those fresh installs
Launching already installed games is not enough to test all LDR/ES/FS sigpatches as tickets have already been converted

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

¡Kabito!

wierd avatar guy

Well-Known Member

Well-Known Member

Well-Known Member

Active Member

¡Kabito!

Well-Known Member

Member

¡Kabito!

Member

¡Kabito!

Active Member

Active Member

New Member

¡Kabito!

Active Member

Attachments

Well-Known Member

Active Member

Active Member

Similar threads

Popular threads in this forum