Adb Shell Su Works But Adb Root Does Not

adb shell su, not getting root permission

Solved. I tried it on my other phone and it was due to the superuser app popping up a notification to allow the computer root access, sadly I could not see the popup and tap it on the phone with a broken screen

ADB root is not working on emulator (cannot run as root in production builds)

To enable root access: Pick an emulator system image that is NOT labelled "Google Play". (The label text and other UI details vary by Android Studio version.)

Exception: As of 2020-10-08, the Release R "Android TV" system image will not run as root. Workaround: Use the Release Q (API level 29) Android TV system image instead.

Test it: Launch the emulator, then run adb root. It should say

• restarting adbd as root

or

• adbd is already running as root

not

• adbd cannot run as root in production builds

Alternate test: Run adb shell, and if the prompt ends with $, run su. It should show a # prompt.

Steps: To install and use an emulator image that can run as root:

1. In Android Studio, use the menu command Tools > AVD Manager.
2. Click the + Create Virtual Device... button.
3. Select the virtual Hardware, and click Next.
4. Select a System Image.
   
   • Pick any image that does NOT say "(Google Play)" in the Target column.
   • If you depend on Google APIs (Google Sign In, Google Fit, etc.), pick an image marked with "(Google APIs)".
   • You might have to switch from the "Recommended" group to the "x86 Images" or "Other Images" group to find one.
5. Click the Download button if needed.
6. Finish creating your new AVD.
   
   • Tip: Start the AVD Name with the API level number so the list of Virtual Devices will sort by API level.
7. Launch your new AVD. (You can click the green "play" triangle in the AVD window.

[Credit belongs to @Merk but this should be posted as an answer rather than a comment.]

adb root command returns adbd cannot run as root in production builds even on an emulator?

I checked some emulator provided by Google.
They are all user binary, not engineer binary.
You can check it yourself by using "adb shell" command.
If command line starts with "#", it's engineer build. If it starts with "$", it's user build. For example:

• jackpot2lte:/ # => engineer build
• jackpot2lte:/ $ => user build

Only engineer build can give you root permission. You can not change user build to engineer build but you can 'root' it.
Please check "How to get root access on Android emulator?" for more information.

Unable to run 'adb root' on a rooted Android phone

I finally found out how to do this! Basically you need to run adb shell first and then while you're in the shell run su, which will switch the shell to run as root!

$: adb shell
$: su

The one problem I still have is that sqlite3 is not installed so the command is not recognized.

---

Related Topics