Install Mihon Extensions in Bulk with Shizuku (No Repeated Prompts)

Short answer: install the Shizuku app, start it (via wireless debugging pairing or ADB), then set Mihon’s installer to Shizuku under More → Settings → Advanced → Installer. Extension installs and bulk updates then run in the background without a confirmation prompt for every single package.

Why you would bother

Modern Android asks for confirmation when one app installs another. With a handful of extensions that is a shrug; when you are migrating from Tachiyomi and reinstalling dozens of extensions — or bulk-updating them later — it is dozens of interruptions. Shizuku lets apps use system-level APIs with your permission, and Mihon can use it as its installer to skip the repetitive prompts.

Set up Shizuku

  1. Install Shizuku from Google Play or its official GitHub project page.
  2. Enable Developer options on your phone (tap Build number seven times in About phone), then turn on Wireless debugging.
  3. In Shizuku, tap Start via Wireless debugging → Pairing, enter the pairing code Android shows, then start the Shizuku service. Its home screen should report that Shizuku is running.
  4. (Alternative: start Shizuku with a one-time ADB command from a computer.)

Point Mihon at Shizuku

  1. Force-close and reopen Mihon after Shizuku is running.
  2. Go to More → Settings → Advanced → Installer and switch the installer from the legacy/package installer option to Shizuku.
  3. Approve the system authorization prompt for Mihon (choose the always-allow option if offered).
  4. Install or bulk-update extensions from Browse → Extensions — packages now go in without a prompt per item.

Caveats

  • Shizuku stops when the phone reboots; restart it (a quick pairing/start on the same Wi-Fi) before your next bulk session.
  • Shizuku changes how extensions install, not what is safe to install. Only install extensions from repositories you added deliberately (repository safety notes).
  • If an extension still fails with “app not installed”, that is a different problem — signature conflicts and Android version issues are covered in app not installed / parse error fixes.

Related: all tutorials · migration guide

Similar Posts