ADB Root Command will allow you to “adb push/pull” the system to the system directors and run different important commands such as “adb disable-verify” or “adb remount”.
However, many users have voiced their concern that they’re trying to run level commands but are instead greeted with the ADBD Cannot Run as Root in Production Builds error. This is happening despite the fact that their smartphone is rooted using Magisk.
If you’re getting the same error, then this guide will be helpful. In this guide, you will get to know how to fix ADBD Cannot Run as Root in Production Builds.
Steps to fix ADBD Cannot Run as Root in Production Builds
Method 1: Using Magisk Module
This module will work only if “adbd” is located in /system/bun instead of /sbin. It needs to be an arm64 device. Here are the steps you should follow –
- First, you need to download the module on your smartphone from GitHub
- After that, launch Magisk, head over to Modules, choose the module, and then tap OK
- Wait for the module to get flashed
- Once it is done, you should hit Reboot
- Check if the “ADBD Cannot Run as Root in Production Builds” error
Method 2: Using SU command
The ADBD from the CMD window will execute commands on your smartphone as user:shell. If you need the ADBD to act as user:root, then you will need to execute adb root. However, it may not be possible on stock ROMs to grant ADBD root permissions. You can take the alternate route by executing the following commands and seeing if you can get the job done.
- First, you should download and extract Android SDK Platform Tools on your computer
- Enable USB debugging on your smartphone and connect it to your PC
- Open CMD in platform tools and give the following commands –
adb shell su
- You’ll see a Magisk request on your device, you need to tap on “Grant”
- Lastly, execute the desired command and check if the ADB Cannot Run as Root in Production Builds is fixed