NO ROOT ACCESS · TWO STARTUP METHODS · ANDROID 8+
Qmovi Without Root: Complete No-Root Setup Guide
You can run Qmovi without rooting your Android phone. This complete guide explains the easiest wireless debugging method for Android 11 and newer, the computer ADB method for older devices, permissions, reboot behavior, supported apps, manufacturer-specific settings, and practical fixes when the service will not start.

Root required?
No. Qmovi can start with Android Debug Bridge privileges without unlocking the bootloader, patching the boot image, or installing a root manager.
Best method
Use wireless debugging on Android 11 or newer. It completes pairing and startup on the same phone without a computer or USB cable.
After a reboot
The ADB-based service commonly stops after a restart. Qmovi 13.6.0 can auto-start without root on Android 13+ when connected to a trusted WLAN, but keep the manual Start method available because device behavior varies.
Can Qmovi work without root?
Yes. Qmovi supports an ADB startup mode that works on unrooted Android devices. Instead of granting permanent superuser access, Android starts the Qmovi server under the temporary shell identity. Compatible apps can then request access through Qmovi and use selected system APIs with the permissions available to ADB.
This is why Qmovi without root can help with app management, debloating, split APK installation, local ADB commands, permission control, file operations, backup tools, and other advanced tasks. It does not turn every app into a root app, and a feature that specifically requires full root access may remain unavailable.
If you still need the APK and version details, begin with our complete Qmovi APK guide. The file provided on this site is scanned with VirusTotal and checked on compatible Android devices before publishing.
Choose the correct no-root method
Your Android version determines the easiest route. Both methods start Qmovi with ADB shell privileges rather than root privileges.
| Method | Best for | Computer | What happens after reboot |
|---|---|---|---|
| Wireless debugging | Android 11 and newer | Not required | Start the service again; pairing often stays saved |
| Computer ADB | Android 8 to Android 10, TVs, or wireless pairing problems | Required for startup | Reconnect and run the Qmovi start command again |
Qmovi no-root methods at a glance
This visual compares the two startup routes. Use wireless debugging on Android 11 and newer, or computer ADB when the phone runs Android 8 to Android 10 or on-device pairing is unavailable.

What you get without rooting the phone
No-root mode is useful because it provides controlled, temporary access instead of changing the device permanently.
No bootloader changes
You do not need to unlock the bootloader, flash a patched image, wipe the phone, or install a superuser manager.
Per-app approval
A compatible app asks for Qmovi permission. You can approve or deny it and review authorized apps from inside Qmovi.
ADB-level access
Apps receive the capabilities available to Android’s shell user. This is more powerful than normal app access but still below full root.
Method 1: Start Qmovi without root or a PC
On Android 11 and newer, wireless debugging is the recommended method. The phone creates a local ADB pairing session and Qmovi uses that session to start its service. Keep the phone connected to a trusted Wi-Fi network during pairing.
Before you begin
- Install the current Qmovi APK from the download button on this page.
- Connect the phone to a private Wi-Fi network.
- Allow Qmovi notifications so the pairing-code prompt can appear.
- Remove battery restrictions for Qmovi if your phone aggressively closes background apps.
Wireless debugging steps
- Open Settings and enable Developer Options by tapping Build number seven times.
- Open Developer Options and turn on USB debugging and Wireless debugging.
- Open Qmovi, select Start via wireless debugging, and tap Pairing.
- In Wireless debugging, tap Pair device with pairing code.
- Expand the Qmovi notification and enter the current six-digit pairing code before it expires.
- Return to Qmovi and tap Start. Confirm that the status says Qmovi is running.
For screenshots, manufacturer menu paths, and pairing-error fixes, use our dedicated Qmovi Wireless Debugging guide.
Method 2: Start Qmovi with computer ADB
Use this route on Android 10 and older, when wireless debugging is unavailable, or when on-device pairing repeatedly fails. You need a Windows, macOS, or Linux computer, a data-capable USB cable, and Google Platform Tools.

1. Prepare the phone
- Open Settings, About phone, and tap Build number seven times.
- Return to Settings, open Developer Options, and enable USB debugging.
- Connect the phone to the computer with a working data cable.
- When Android asks whether to allow USB debugging, verify the computer and tap Allow. Select Always allow from this computer only if it is your own trusted device.
2. Check the ADB connection
Extract Platform Tools, open PowerShell or Terminal inside that folder, and run:
adb devices
PowerShell, macOS, and Linux may require ./adb devices. Your phone should appear with the status device. If it says unauthorized, unlock the phone and approve the debugging prompt.
3. Start the Qmovi service
Open Qmovi and view the command shown under Start via connecting to a computer. Copy that exact command because current releases can use a version-specific executable path. Paste it into the same terminal and press Enter. Return to Qmovi and confirm that the service is running.
Older Qmovi builds used adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh, but the current in-app command should be preferred because startup files and paths can change between versions.
Authorize companion apps
Open a compatible app, select Qmovi as its working mode, and approve the permission prompt. Reject access for apps you do not recognize.
Check the running mode
The Qmovi home screen should show that the service is running with ADB. This confirms no-root shell mode is active.
Explore compatible tools
See our Qmovi supported apps list for app managers, terminal tools, installers, backup utilities, and file tools.
Limitations of Qmovi without root
ADB mode is powerful, but it is not identical to root mode. Understanding the limits prevents incorrect expectations and unnecessary troubleshooting.
- The service commonly needs to be started again after a reboot, although Qmovi 13.6.0 adds no-root auto-start support on Android 13+ when connected to a trusted WLAN.
- ADB permissions vary by Android version and manufacturer software.
- Some companion-app features may require true root even when the app supports Qmovi.
- Work profiles, device management policies, parental controls, or restricted ROMs can disable Developer Options or debugging.
- Turning off Developer Options, USB debugging, or wireless debugging may stop the service or remove authorization.
- Android updates can change access to protected folders or system APIs.
If a current release causes a documented compatibility problem on your device, compare the tested downloads on our QMOvi Old Versions page. Use an older build only for a specific compatibility reason.
Developer Options on Samsung, Xiaomi, OnePlus, OPPO, and other phones
Menu names differ between Android skins. On Pixel and many stock Android phones, Developer Options appears under Settings, System. Samsung places Build number under About phone, Software information. Samsung’s Developer Options instructions confirm that Build number must be tapped seven times and that the menu appears at the bottom of Settings.
- Samsung Galaxy: Settings → About phone → Software information → Build number. Remove Qmovi from Sleeping apps if the service stops.
- Xiaomi, Redmi, POCO: Enable USB debugging and, when a companion feature lacks permission, USB debugging (Security settings). Do not run an optimizer that disables Developer Options.
- OnePlus and OPPO: Check Developer Options for Permission monitoring if ADB actions are blocked. Battery optimization may also need adjustment.
- Vivo and iQOO: Allow background activity and confirm the debugging authorization again if Funtouch OS revokes it.
- Huawei and Honor: Some builds include Allow ADB debugging in charge-only mode. Availability differs by Android and regional firmware.
Common Qmovi no-root problems and fixes
Try the matching fix before reinstalling the app or changing versions.
Qmovi is not running
Enable Developer Options and the required debugging toggle again. For wireless mode, create a fresh pairing code. For computer ADB, reconnect and rerun the command shown inside Qmovi.
ADB shows unauthorized
Unlock the phone, disconnect and reconnect the cable, run adb devices, and accept the RSA authorization prompt. Revoke USB debugging authorizations only if the prompt never returns.
Service stops in background
Allow Qmovi background activity, disable battery optimization for it, keep Developer Options enabled, and exclude it from manufacturer memory-cleaning tools.
App cannot use Qmovi
Confirm Qmovi is running, open Authorized applications, approve the companion app, and check whether that specific feature needs root instead of ADB access.
Is Qmovi without root safe?
No-root mode avoids bootloader unlocking and permanent superuser access, which reduces the changes made to the device. However, Qmovi still gives approved apps access to elevated ADB capabilities. Treat every authorization as a security decision.
- Install the VirusTotal-scanned Qmovi file provided on this page.
- Use wireless debugging only on a private network you trust.
- Connect ADB only to your own computer and approve only its RSA key.
- Grant Qmovi permission only to apps you understand and intend to use.
- Review Authorized applications in Qmovi and revoke unused access.
- Do not paste unknown ADB commands from comments, videos, or random forums.
After completing a task, you can stop Qmovi from its home screen. If you no longer need debugging, turn off wireless debugging or USB debugging in Developer Options.
Qmovi without root FAQs
Start Qmovi without root
Download the current APK, choose the method that matches your Android version, and approve only the companion apps you trust.
