Skip navigation

Earn a $25 promo card when you buy $150 in gift cards online. Ends May 10.  See Restrictions

0
Main content

Adb+shell+sh+storage+emulated+0+android+data+moeshizukuprivilegedapi+startsh Access

The Android filesystem hierarchy separates internal application storage from shared external storage. The path /storage/emulated/0/Android/data/ contains the external private data directories for applications. On standard non-rooted devices, these directories are accessible only to their respective applications.

However, the Android Debug Bridge (ADB) provides a "shell" user context that possesses elevated permissions compared to standard apps but is still restricted compared to the "root" user. The package identifier moeshizukuprivilegedapi suggests a specialized application designed to expose privileged APIs or files to the shell user.

This paper documents the process, syntax, and implications of the command string: adb shell sh [path]/startsh.

You might wonder: Why can’t Shizuku simply start itself when the app opens?

The answer is Android’s security model. Modern Android runs every app in a sandbox. An app cannot elevate its own privileges or start system-level processes. However, the shell user (accessible via ADB) can execute certain privileged commands that apps cannot. Without the ADB shell command, Shizuku would have

The start.sh script, when executed by the shell user, can:

Without the ADB shell command, Shizuku would have no way to bootstrap its service. This is why the command is required—it’s the one-time (or per-boot) elevation event.

In the world of Android power users and developers, few tools have bridged the gap between user-friendly automation and low-level system access as elegantly as Shizuku. If you have ever stumbled upon the command:

adb shell sh /storage/emulated/0/Android/data/moe.shizuku.privileged.api/start.sh

you might have wondered: What exactly does this long, intimidating string do? Why does it point into Android/data? And how does it unlock privileged APIs without root? In the world of Android power users and

This article breaks down every component of that command—adb, shell, sh, /storage/emulated/0, Android/data, moe.shizuku.privileged.api, and start.sh. By the end, you will not only understand what the command does but also how to leverage Shizuku for advanced Android development and automation.

The script must be re-run every time the device reboots. Shizuku does not survive reboots because the service runs in volatile memory. Power users often automate this using:

Obviously, the path won’t exist. Install Shizuku from Google Play or GitHub first.

Do not move or modify the start.sh script from its original location inside /data/data/. Copying it to /storage/emulated/0/ will break: Google has enforced scoped storage :

Since Android 11 (API 30) , Google has enforced scoped storage:

Check current permissions:

adb shell ls -la /storage/emulated/0/Android/data/moeshizukuprivilegedapi/

→ You will likely see opendir failed: Permission denied.

The path /storage/emulated/0/Android/data/moeshizukuprivilegedapi refers to the external storage directory assigned to an application with the package name moeshizukuprivilegedapi.