0

My android is 4.0.3 and is on an Acer Iconia Tablet A100. I have rooted it already using this process, and the rooting persists between reboots. I can confirm root access with the Root Checker app.

I have installed the Android SDK and it's required Java SDK.

When I run Droid Explorer I get this message:

Droid Explorer error

What do I do?

bgmCoder
  • 163
  • 1
  • 13

1 Answers1

1

Disclaimer: I am the lead developer of Droid Explorer

The dialog is telling you exactly what the problem it. It isn't saying you don't have root, it is saying that it cannot start ADB with root.

The more information link takes you here: Droid Explorer permission denied when accessing root-only folders.

Or you can go right to get ADBD Insecure. The app will exit because you need to install that app first, then start Droid Explorer.

Ultimately, you will need to install ADBD Insecure, or a custom kernel that allows ADB to run in root mode, or you will have limited access to some folders on the device.

Community
  • 1
Ryan Conrad
  • 22,673
  • 9
  • 58
  • 81
  • But I do have root. The applications on the android all request and use root permissions. Root checker confirms root. Droid Explorer is the only thing that thinks there is no root. On the Android, I can view any folder on the entire system with the file browsers on the device. – bgmCoder Oct 25 '15 at 15:20
  • 1
    Yes, I get that you have root. but you cannot start ADB in ROOT MODE unless it supports it, either with a custom kernel, or using ADBD Insecure. Running an app on the device that requests root is different than how Droid Explorer uses root. It requests it through ADB, and if adb does not run in root mode, it will not have access to folders that require root. – Ryan Conrad Oct 25 '15 at 20:15
  • Okay, I'm starting to get it now, Mr. Conrad. Thank you for explaining. – bgmCoder Oct 25 '15 at 23:05
  • Well, I'm not sure how it worked... I clicked on "Continue and show more information" and it opened the thread on my desktop browser (like you said it would) and then it showed my Android device and I opened it just fine and can explore just like you'd expect. – bgmCoder Nov 02 '15 at 04:45
  • it will continue to function, for the most part. You may have some issues accessing folders like /system/apps/ or opening a shell with root access (you should still be able to say "su" in the shell manually though) – Ryan Conrad Nov 02 '15 at 04:47
  • This is a neat thing and I'm glad to try it out. So, I notice the processes window doesn't work, but CPU does; Network and Memory (in Process Explore) are empty. I am able to browse /system/app just fine - it list all the contents. I wanted DroidExplorer in the first place just to try it's Full Backup Feature, hoping it would back up the entire device to my computer's hdd; I tried it, but I'm not sure what it did, exactly. Oh neat! The screen monitor works! – bgmCoder Nov 02 '15 at 04:53
  • For backup, droid explorer just uses the device backup and makes it a bit easier to use. The backups are saved in C:\Users<username>\Android Backups – Ryan Conrad Nov 02 '15 at 04:55
  • Ah; it's only 627 bytes even though I checked all the boxes... It should be several GBs. Anyway, the question is answered here and I'm getting us out of scope. Thanks for you help, Mr. Conrad. – bgmCoder Nov 02 '15 at 04:59