Skip to content

Latest commit

 

History

History
66 lines (47 loc) · 2.44 KB

File metadata and controls

66 lines (47 loc) · 2.44 KB

PatchNest Module

English | 中文

Standalone implementation of KPM support for Magisk / KernelSU / APatch


KPM Module Repository

KPMs (KernelPatch Modules) are distributed via a standalone Kpm-Repo project. You don't need to rebuild PatchNest to add or remove KPMs.

Default repo: Zhanfg/Kpm-Repo

Use the default repo

Open the PatchNest WebUI → KPM Repository → it auto-fetches the default manifest on first run.

Add a custom/forked repo

  1. Fork Zhanfg/Kpm-Repo
  2. Add your KPM sources in modules/<id>/ (see Kpm-Repo README)
  3. Push to main — GitHub Actions will compile, sign, and release the .kpm ZIPs automatically
  4. In the PatchNest WebUI → KPM RepositoryAdd Repository
  5. Paste your fork's manifest URL:
    https://raw.githubusercontent.com/<your-username>/Kpm-Repo/main/kpm_repo.json
    

Full forking guide: Kpm-Repo README

Ship a custom default repo in your PatchNest fork

If you maintain a PatchNest fork and want to ship a non-default default KPM repo (e.g. pointing users at your own Kpm-Repo fork):

  1. Fork both PatchNest-Module and Kpm-Repo
  2. In your PatchNest fork, create a file repos.json at the module root:
    [{ "url": "https://raw.githubusercontent.com/<you>/Kpm-Repo/main/kpm_repo.json",
       "name": "Acme KPMs" }]
  3. Rebuild your PatchNest module. The customize.sh installer will copy repos.json to /data/adb/patchnest/repos.json on device; the WebUI reads this file before any localStorage or default URL.

Credits

License

  • PatchNest-Module is licensed under GNU General Public License v3 GPL-3.0
  • PatchNest binaries is licensed under GNU General Public License v2 GPL-2.0
  • magiskboot binary from Magisk is licenced under GNU General Public License v3 GPL-3.0
  • WebUI is licensed under MIT License MIT