FolkPatch

English

简体中文

English

简体中文

Appearance

Shizuku Service

About 767 wordsAbout 3 min

2026-08-10

Shizuku is a powerful system permission service that lets ordinary apps call system APIs directly through ADB-level APIs, without requiring Root access. Many well-known utility apps (such as LSPatch, LibChecker, Thanox, etc.) support enhanced features through Shizuku.

Flagship Feature

FolkPatch bundles a complete Shizuku server — no third-party Shizuku app installation required. Just toggle it on!

Why Shizuku?

  • Safer app authorization: Apps authorized via Shizuku only get ADB-level permissions, not full Root
  • Broader tool compatibility: Many Shizuku-supported apps (LSPatch, Shizuku ecosystem tools, etc.) can be used directly
  • No third-party dependency: The traditional approach requires installing the official Shizuku app and starting it via ADB; FolkPatch has everything built in
  • More powerful with Root: Compared to the official ADB mode, Root-level Shizuku can access /data and other system directories, offering greater capability

Quick Start

  1. Open FolkPatch and go to Settings → Function
  2. Find Shizuku Service and turn on the toggle
  3. Wait for the service to start (Root access required); "Shizuku service is running" appears below the toggle
  4. Authorize within any Shizuku-supported app to use it

Permission Management

Once the service is enabled and running, tap Manage Authorized Apps to open the permission management page:

  • Lists all Shizuku-compatible apps with their UIDs (authorized / denied status at a glance)
  • Allow / deny Shizuku access per app individually
  • Permission mode selection: choose the execution permission per app individually —
    • Root access (On): the app runs commands with root privileges through Shizuku, able to read protected data
    • Shell basic mode (Off): the app runs as shell (UID 2000), unable to read protected data
  • Persisted authorization: Survives server restarts, no re-authorization needed

About Permission Modes

The permission mode selection is only meaningful when the server runs as root (in shell mode, all commands are naturally shell-privileged). Apps with Root access gain much stronger capability — only enable it for trusted apps.

How It Works

  • Root-level startup: The service prefers to start as root (uid 0), matching the official Shizuku root mode — commands executed through Shizuku have root privileges by default and can read protected directories like /data; it automatically falls back to shell (uid 2000) startup when the su implementation doesn't support it
  • Per-app permission control: The service bundles the fpdrop privilege-dropping tool, letting you control the execution permission per app (Root access / Shell basic mode); when fpdrop is unavailable, it falls back to executing as the current identity (per-app control inactive)
  • The built-in server runs via app_process; its lifecycle is fully managed by FolkPatch: startup, status detection, and shutdown (graceful exit + fallback cleanup)
  • Auto-start on boot: while the toggle stays on, the server is automatically launched after boot (waits for Root to be ready, with up to 6 retries)

FAQ

Shizuku Service Q&A

User

What's the difference between Shizuku and Root?

Shizuku provides ADB-level permissions (shell uid 2000), which are less powerful than full Root. It suits apps that need system APIs but not full Root, offering finer-grained and safer authorization. FolkPatch's built-in Shizuku also supports per-app permission mode selection: enable Root access individually for apps that need stronger capability while keeping others in the safe Shell basic mode.

User

Why does my Shizuku service fail to start?

Please confirm: 1. The device has Root access (FolkPatch starts the service at Root level; it cannot start without Root) 2. KernelPatch and APD are ready 3. Try toggling the switch again. If it still fails, export the logs and report it.

User

Do I need to install the official Shizuku app?

No. FolkPatch bundles a complete Shizuku server; just toggle it on — no third-party apps required.

User

Do I need to re-enable it after a reboot?

No. As long as the Shizuku Service toggle stays on, the server is auto-started after boot (waits for Root to be ready, then launches it, with up to 6 retries), and your authorization records are preserved. If the auto-start fails (e.g., Root not ready in time), you can manually re-toggle the switch to start it.

Copyright Ownership:FolkPatch Team

License under:Attribution 4.0 International (CC-BY-4.0)