English | 中文
Standalone implementation of KPM support for Magisk / KernelSU / APatch
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
Open the PatchNest WebUI → KPM Repository → it auto-fetches the default manifest on first run.
- Fork Zhanfg/Kpm-Repo
- Add your KPM sources in
modules/<id>/(see Kpm-Repo README) - Push to
main— GitHub Actions will compile, sign, and release the.kpmZIPs automatically - In the PatchNest WebUI → KPM Repository → Add Repository
- Paste your fork's manifest URL:
https://raw.githubusercontent.com/<your-username>/Kpm-Repo/main/kpm_repo.json
Full forking guide: Kpm-Repo README
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):
- Fork both PatchNest-Module and Kpm-Repo
- In your PatchNest fork, create a file
repos.jsonat the module root:[{ "url": "https://raw.githubusercontent.com/<you>/Kpm-Repo/main/kpm_repo.json", "name": "Acme KPMs" }] - Rebuild your PatchNest module. The
customize.shinstaller will copyrepos.jsonto/data/adb/patchnest/repos.jsonon device; the WebUI reads this file before any localStorage or default URL.
- Patch scripts from APatch
- PatchNest binaries from Zhanfg/PatchNest
- magiskboot binary from Magisk