Where Does Shizuku Store Grants and Data?
Shizuku grants API access to apps via wireless debugging or ADB, reactivated each boot. Authorized apps list lives in Shizuku private storage.
Last updated
Shizuku is a permission broker, not a data store. It lets chosen apps call system APIs through ADB privileges, with the service started fresh after every reboot. The authorized-apps list and service state live in Shizuku private storage.
That boot reset confuses newcomers: everything works until a restart, then every dependent app fails at once. Restart the Shizuku service first when automation, managers, or installers break. Revoke grants from inside Shizuku when retiring an app, since Android permissions screens show only half the picture.
Where Shizuku stores this, by platform
/storage/emulated/0/Android/data/moe.shizuku.privileged.api/files
Grants reset each reboot by design. Start via wireless debugging pairing in the app. Exact folder names may vary by version; manage grants in-app, not the filesystem.
Frequently asked questions
Why did apps lose Shizuku access?
Open Shizuku and start the service through wireless debugging pairing, then re-authorize requesting apps. The grant resets every reboot by design. Apps that stop working after an update usually need re-authorization, not reinstallation.
How do I start Shizuku without a PC?
Enable Developer options and wireless debugging, pair with the code Shizuku shows, and start. No computer needed on modern Android. The classic ADB-over-USB path still works when wireless pairing refuses to stick.
Notice an outdated path? Let us know.