Database Develop

ADB Driver - Access is Denied

So I just installed Windows 7 on my machine and was trying to ADB with my Android since I used it ALL the time on Windows XP.
I put the phone in Debug mode and plugged into my computer and told it the location of the driver. It seems to work well for a second and then it tells me that there was a problem installing the driver. It then says:
HTC ADB Composite Device Driver (not sure exactly of this...)
Access is Denied
Click to expand...
Click to collapse
Anyone else seeing anything similar on Vista or Windows 7? BTW I already tried this in Safe Mode as well.

Stigy said:
So I just installed Windows 7 on my machine and was trying to ADB with my Android since I used it ALL the time on Windows XP.
I put the phone in Debug mode and plugged into my computer and told it the location of the driver. It seems to work well for a second and then it tells me that there was a problem installing the driver. It then says:
Anyone else seeing anything similar on Vista or Windows 7? BTW I already tried this in Safe Mode as well.
Click to expand...
Click to collapse
I have mines working perfectly on Win7. Maybe you don't have admin rights on your computer? Just a guess

xidominicanoix said:
I have mines working perfectly on Win7. Maybe you don't have admin rights on your computer? Just a guess
Click to expand...
Click to collapse
Nope I have administrative rights and even tried it in safe mode.
Would you be able to zip up the drivers you used or link to where you downloaded them from?
So strange.

Even if you have admin rights, UAC can f it up.
Make sure you right click on command prompt and click "Run as Administrator"
Also, do you have x64? That requires a signed drivers. I don't remember if the ADB drivers were signed by microsoft, but if they aren't, it won't work unless you apply the work around

http://forum.xda-developers.com/showthread.php?t=532719
The link in this thread usbdeview seems to fix alot of driver issues

Stigy said:
Nope I have administrative rights and even tried it in safe mode.
Would you be able to zip up the drivers you used or link to where you downloaded them from?
So strange.
Click to expand...
Click to collapse
i got mines from the 1.6 sdk .. x64

Simple Solution
Here is a simple solution without having to read that long thread:
For future reference, here is how to install the drivers or fix the drivers should they not be working.
Everything you need is contained within this:
http://www.divshare.com/download/8845496-f72
This is the howto documentation
This is how to get your android phone to connect to you PC
to use functions like adb and other developer tools.
If you have installed the phone before but adb function dont work
then:
1) Run USBDeview
2) Select the list item(s) that have the word "android" within the description
3) Right Click > Uninstall
If you have done the above, or are plugging your phone in for the first time:
1) Plug in phone
2 a) When prompted to install drivers select the "android driver" folder
contained within this tutorial
2 b) If no message appears or you get a message saying drivers failed
to install. Goto device manager
2 b i) start > All Programs > accessories > run
type devmgmt.msc and press ok.
3 b) find the android device in device manager, it will have a warning icon
next to it and be in a section like unknown.
4 b) Right click and install driver
5 a) When prompted to install drivers select the "android driver" folder
contained within this tutorial
Click to expand...
Click to collapse

USBDeview is awesome but....
Even after removing all of the drivers associated with my device, as soon as I try to install the fresh new drivers, I still get "Access Denied" at the end of the install.

digimancer said:
Even after removing all of the drivers associated with my device, as soon as I try to install the fresh new drivers, I still get "Access Denied" at the end of the install.
Click to expand...
Click to collapse
I have this same issue on an Ideos U8150 and on XP... At one point in the past it was working (before I flashed Cyanogen 7). Since then I have tried numerous driver packages, both specific to my phone and generic, and have had no luck getting past the access denied error.. I have even gone as far as changing the registry permission as well as checking all of my folder permissions... I am stumped.

Adb root - run that from command prompt.

B-man007 said:
Even if you have admin rights, UAC can f it up.
Make sure you right click on command prompt and click "Run as Administrator"
Also, do you have x64? That requires a signed drivers. I don't remember if the ADB drivers were signed by microsoft, but if they aren't, it won't work unless you apply the work around
Click to expand...
Click to collapse
I know it a while ago since you posted this but still, it helped me fix the "Access denied" thing which i didn't know how to fix. I installed ADB drivers 3 times... anyways, tnx :good:

So If you are like me you had this same issue in 2022. Idk if it will be a fix for you but it was for me.
follow this youtube video for the exact setup so you can get hopfully the same out com to the T.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1. make sure you're in administrator mode for command prompt.
2. The file name has changed from what it was so instead of doing
cd adb\platform-tools_r30.0.4-windows\platform-tools
It's now this
cd adb\platform-tools\
This will get you to the correct path if you followed the file placement in the video.
next all you have to do is type
adb devices on the command prompt. to test if it worked
other things that you might have to try is seeing if the driver it self is being blocked. you might also have to turn off and back on developer mode. View other posts in this thread if it's still stuck for you. Hopefully I helped one person at least.

[APP] QtADB Easy ADB, File Manager, Apps etc

QtADB is an app based on adb. It requires working android sdk (command “adb"), Qt libs version 4.7, ROOT and busybox installed on phone.
Features:
File manager
copying files and dirs between phone and computer
removing files and dirs
creating new dir
and other
App manager
installing apps[/B]
removing apps
creating backup of apps with data
restoring backups of apps with data
Shell
opens android shell
Screenshot
take screenshot of your device
save screenshot to png file
Fastboot
flash bootloader, radio and recovery
boot recovery
Recovery
nandroid backup/restore
wipe data
flash rom
wipe battery stats
fix uid mismatches
Reboot
to bootloader
to recovery
normal reboot
Settings
set font used by app
set starting paths (or remember paths on exit)
and other
Logcat
Automatically detects phone (device, fastboot and recovery mode)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download QtADB for windows, linux & mac os.
Connect with Cable and WiFi
Download adbWireless scan with Barcode App

really great app. surprised no ones posted about it. i see there has been updates in a while cuz there looking for devs to help. one problem i have is my phones apps only show up if i have an app moved using the system move to sd, i use link2sd. when i view system apps they all show.

Nice app. Everything works well except the sms-tab. I allways get an error.
But I have one question: what setting does this app modify on my phone when i toggle wifi connection? It works, but when i toggled wifi, I cant swith back to usb-connection and also cannot mount my SD to windows anymore..

doumer said:
Nice app. Everything works well except the sms-tab. I allways get an error.
But I have one question: what setting does this app modify on my phone when i toggle wifi connection? It works, but when i toggled wifi, I cant swith back to usb-connection and also cannot mount my SD to windows anymore..
Click to expand...
Click to collapse
Have you got QtADB.apk installed and running when you try to access the sms-tab?

ah no, wasn't running. sometimes the solution is so simple ^^
thank you

doumer said:
Nice app. Everything works well except the sms-tab. I allways get an error.
But I have one question: what setting does this app modify on my phone when i toggle wifi connection? It works, but when i toggled wifi, I cant swith back to usb-connection and also cannot mount my SD to windows anymore..
Click to expand...
Click to collapse
Got the same question, except not for the sms part, the wifi function screw me up.
help would be appreciated
Edit: problem resolved, download the apk, enable and disable the wireless adb on your phone, change connection type to diskdrive and solves the problem.

hey all,
FAQ on the official site solves 99% problems You can find there some info about using WiFi connection, SMS Manager and more.

burimii said:
QtADB is an app based on adb. It requires working android sdk (command “adb"), Qt libs version 4.7, ROOT and busybox installed on phone.
Features:
File manager
copying files and dirs between phone and computer
removing files and dirs
creating new dir
and other
App manager
installing apps[/B]
removing apps
creating backup of apps with data
restoring backups of apps with data
Shell
opens android shell
Screenshot
take screenshot of your device
save screenshot to png file
Fastboot
flash bootloader, radio and recovery
boot recovery
Recovery
nandroid backup/restore
wipe data
flash rom
wipe battery stats
fix uid mismatches
Reboot
to bootloader
to recovery
normal reboot
Settings
set font used by app
set starting paths (or remember paths on exit)
and other
Logcat
Automatically detects phone (device, fastboot and recovery mode)
Download QtADB for windows, linux & mac os.
Connect with Cable and WiFi
Download adbWireless scan with Barcode App
Click to expand...
Click to collapse
good one mate I use this app for one year or so, and it's amazing

Finally... exactly what I was looking for.
Can't thank you enough for posting this. I've been rooting around for a good all-in-one toolbox for a while. Blows DroidExplorer, etc., out of the water.
Any possibility you could add some more tags to improve other's chances of finding it? I'm certain there are lots more folks looking for exactly this kinda tool.

hey so this seems like a good use of getting around some bugs for usb mount... but quick question, im trying to open the QtADB.exe file, and then it asks me for the path to adb and aapt binaries. I've installed the adroid-sdk package, so where do I point the directory to? my android sdk path is on c:/-program files (x86)- Android. The FAQ doesn't really help in answering questions...

awesome tool!
wifi connection doesnt work.. i downloaded the apk and tried connecting but didnt work..

The most awesomest PC app for android ever! Sammy better learn something from you, and FAST!

dr. xp55 said:
hey so this seems like a good use of getting around some bugs for usb mount... but quick question, im trying to open the QtADB.exe file, and then it asks me for the path to adb and aapt binaries. I've installed the adroid-sdk package, so where do I point the directory to? my android sdk path is on c:/-program files (x86)- Android. The FAQ doesn't really help in answering questions...
Click to expand...
Click to collapse
Point it to the exact directory in which adb and aapt are found should be something like c:/program files (x86) - android/tools
Sent from my HTC Desire HD using Tapatalk

I've been using this for a while now and it works great, very useful via wifi. Thanks!

I was looking for something like this for some time. Awesome app, thank you!

It stops responding whenever I try to copy a file from the device. P6800 CWM

Dont open Qt-Adb site, contains Trojan Redirector

nice man, tnx

After much anguish, I finally started it, nice app.

Cant connect my phone to QTADB via usb or wifi
Hi,
I cant seem to connect my phone to QTADB via usb or wifi. Tried checking the faqs but no answer there.
Can anyone help?

How to take screenshots of Xoom?

I started this to discuss how to take screenshots with the Xoom. Here are the instructions that work for me. If something is not working for you, reply here and we will see if we can get you up and running.
You have to have the Android SDK loaded on your computer:
http://developer.android.com/sdk/index.html
You will also need Java Development Kit installed (make sure you download the proper version for your OS. Use Windows for 32-bit and Windows x64 for 64-bit):
https://cds.sun.com/is-bin/[email protected]_Developer
You run the ddms.bat file from the Android SDK tools folder in a CMD window (to see if there are any errors). While you can just double click the file, if it doesn't bring up the application window, there may be an error that will not be displayed unless you launch it from a CMD window. If you didn't change the default installation path when installing the Android SDK, you will find the ddms.bat in C:\Program Files\Android\Android-SDK\tools.
The Xoom will need to be in debug mode under Settings > Applications > Development. When you launch ddms.bat successfully, a window will launch and you select your device from the list and choose Device > Screen Capture. You do not have to be rooted. See attached screenshot of the main application window.
If you still have problems especially getting the computer to recognize the Xoom in debug mode, follow the instructions here: http://www.motorola.com/Support/US-...vers/USB-and-PC-Charging-Drivers?pubid=987654
EDIT: I will tweak the instructions based on input provided in replies.

Ok, I uninstalled everything and reinstalled... still the same issue. Here is what I get when I run in the CMD window (notice that I installed the Android SDK in C: Program Files (x86) \ instead of C:\Programs Files\ like I did in the other thread. The reason being is that I installed the Java in Program Files (x86) also and I didn't know if that mattered. For some reason I have a Program Files folder and a Program Files (x86) Folder and most of my programs, it seems, are in the Program Files (x86) Folder.
Anyway, here is the screen shot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I changed the path in System Variables, I replaced everything that was on that line with what you wrote in the other thread. I have a feeling I may have replaced something that may have been needed.
Right now, this is what I have in System Variables in the Path section:
;C:\Program Files (x86)\Android\Android-SDK\tools;C:\Program Files (x86)\Android\Android-SDK\platform-tools
Also, I am not sure if I need the USB Drivers. I can drag and drop files to my xoom with no problems but when I plug it up with USB Debugging selected, it tries to find drivers unsuccessfully so I just "X" out of it.

ghoticov said:
Ok, I uninstalled everything and reinstalled... still the same issue. Here is what I get when I run in the CMD window (notice that I installed the Android SDK in C: Program Files (x86) \ instead of C:\Programs Files\ like I did in the other thread. The reason being is that I installed the Java in Program Files (x86) also and I didn't know if that mattered. For some reason I have a Program Files folder and a Program Files (x86) Folder and most of my programs, it seems, are in the Program Files (x86) Folder.
Anyway, here is the screen shot:
When I changed the path in System Variables, I replaced everything that was on that line with what you wrote in the other thread. I have a feeling I may have replaced something that may have been needed.
Right now, this is what I have in System Variables in the Path section:
;C:\Program Files (x86)\Android\Android-SDK\tools;C:\Program Files (x86)\Android\Android-SDK\platform-tools
Also, I am not sure if I need the USB Drivers. I can drag and drop files to my xoom with no problems but when I plug it up with USB Debugging selected, it tries to find drivers unsuccessfully so I just "X" out of it.
Click to expand...
Click to collapse
For one, you should not have replaced everything in the line for the path. That may cause system instability and other applications to stop working. You should have appended to the end of the line! The path variable is important because it allows Windows to know where to look for things without specifically entering the path.
Do you have regular Java installed?
http://java.com
I know you installed the JDK but try installing regular java too and see if that helps. By the way, I do not have to launch anything as Administrator.

Please also post what version of Windows 7 you have... is it 32-bit or 64-bit?

keitht said:
For one, you should not have replaced everything in the line for the path. That may cause system instability and other applications to stop working. You should have appended to the end of the line! The path variable is important because it allows Windows to know where to look for things without specifically entering the path.
Do you have regular Java installed?
http://java.com
I know you installed the JDK but try installing regular java too and see if that helps. By the way, I do not have to launch anything as Administrator.
Click to expand...
Click to collapse
Yes, I have regular JAVA. I went to the site to check and got this:
Verified Java Version
Congratulations!
You have the recommended Java installed (Version 6 Update 24).
My system seems to be running ok even thought I replaced everything in the Path with what I put above. Could there have been something there that I deleted that could mess up the process?
Also, Is there any way to find out what I deleted? lol

keitht said:
Please also post what version of Windows 7 you have... is it 32-bit or 64-bit?
Click to expand...
Click to collapse
I am running Windows Vista 64 bit.

ghoticov said:
Yes, I have regular JAVA. I went to the site to check and got this:
Verified Java Version
Congratulations!
You have the recommended Java installed (Version 6 Update 24).
My system seems to be running ok even thought I replaced everything in the Path with what I put above. Could there have been something there that I deleted that could mess up the process?
Also, Is there any way to find out what I deleted? lol
Click to expand...
Click to collapse
No but it may be possible to do a system restore to the last checkpoint to restore what you had in the path variable.
Vista ick. It should work on Vista but it is nothing but a bag of problems.
The error is complaining that it cannot find java in c:\program files\java. With 64-bit systems, there are two Program Files:
C:\Program Files and C:\Program Files (x86).
Do you have a java folder in c:\program files? If you open that in Explorer, do you see what I have in mine? Screen attached.

keitht said:
No but it may be possible to do a system restore to the last checkpoint to restore what you had in the path variable.
Vista ick. It should work on Vista but it is nothing but a bag of problems.
The error is complaining that it cannot find java in c:\program files\java. With 64-bit systems, there are two Program Files:
C:\Program Files and C:\Program Files (x86).
Do you have a java folder in c:\program files? If you open that in Explorer, do you see what I have in mine? Screen attached.
Click to expand...
Click to collapse
no, I do not have a java folder in c:\program files. I only have a Java folder in C:\Program files (x86)

ghoticov said:
no, I do not have a java folder in c:\program files.
Click to expand...
Click to collapse
That may be the issue. Did you install Windows x64 version from here?
https://cds.sun.com/is-bin/[email protected]_Developer

keitht said:
That may be the issue. Did you install Windows x64 version from here?
https://cds.sun.com/is-bin/[email protected]_Developer
Click to expand...
Click to collapse
Ah ha! I believe I installed the "Windows" version and not the "Windowx64" version. Do I need to uninstall the other version first?

ghoticov said:
Ah ha! I believe I installed the "Windows" version and not the "Windowx64" version. Do I need to uninstall the other version first?
Click to expand...
Click to collapse
That is what I did. But uninstall the other one first then install x64 since you have 64-bit vista.

keitht said:
That is what I did. But uninstall the other one first then install x64 since you have 64-bit vista.
Click to expand...
Click to collapse
I think I am almost there!!!!
I got the Dalvik Debug Monitor to come up. Now do I just plug my xoom in and it will come up on the screen?
Btw... I tried to run the ddms.bat file in the CMD window again but it told me to add : "C:\Program Files\Java\jdk1.6.0_24\bin\java.exe" to the end, so I did. I ran it again and got the Debug Monitor.

ghoticov said:
I think I am almost there!!!!
I got the Dalvik Debug Monitor to come up. Now do I just plug my xoom in and it will come up on the screen?
Btw... I tried to run the ddms.bat file in the CMD window again but it told me to add : "C:\Program Files\Java\jdk1.6.0_24\bin\java.exe" to the end, so I did. I ran it again and got the Debug Monitor.
Click to expand...
Click to collapse
At this point it is a matter of connecting to the Xoom. Your Xoom needs to be in Debug mode to connect as seen in screenshot. Once selected, plug in and it should work unless you get an error in Windows.
Debug mode on the Xoom can be enabled in Settings > Applications > Development.

Ok, I plugged up the xoom and it tried to find the drivers (which it didn't). Just clicked the "X" to get out of the driver search.
I then ran ddms.bat and got this:
My xoom is plugged up and USB Debugging is checked but apparently it isn't recongnizing the device as being plugged up because of not having the drivers. Do you know where I can get those?

ghoticov said:
Ok, I plugged up the xoom and it tried to find the drivers (which it didn't). Just clicked the "X" to get out of the driver search.
I then ran ddms.bat and got this:
My xoom is plugged up and USB Debugging is checked but apparently it isn't recongnizing the device as being plugged up because of not having the drivers. Do you know where I can get those?
Click to expand...
Click to collapse
In Windows 7, there are no additional drivers needed so I do not know what to do at this point unfortunately. You can try this although I am not sure if that will work since you can already transfer files from Vista to Xoom?
http://www.gigadroid.com/androidtalk/viewtopic.php?f=14&t=41
Hate to keep beating a dead horse but Vista really sucks especially with drivers and devices.

keitht said:
In Windows 7, there are no additional drivers needed so I do not know what to do at this point unfortunately. You can try this although I am not sure if that will work since you can already transfer files from Vista to Xoom?
http://www.gigadroid.com/androidtalk/viewtopic.php?f=14&t=41
Click to expand...
Click to collapse
yes, I have been able to transfer files from my laptop to my xoom... pictures and movies. I will take a look at that link though.
Should the xoom just show up as a device once it is plugged in?

keitht said:
In Windows 7, there are no additional drivers needed so I do not know what to do at this point unfortunately. You can try this although I am not sure if that will work since you can already transfer files from Vista to Xoom?
http://www.gigadroid.com/androidtalk/viewtopic.php?f=14&t=41
Hate to keep beating a dead horse but Vista really sucks especially with drivers and devices.
Click to expand...
Click to collapse
Yea I would love to go to Windows 7 but I am not that great with computers and I assume it would take a lot of time (backing everything up) to do it.

ghoticov said:
yes, I have been able to transfer files from my laptop to my xoom... pictures and movies. I will take a look at that link though.
Should the xoom just show up as a device once it is plugged in?
Click to expand...
Click to collapse
Yes and since you copied files already, it is working for that. USB debug does not appear to use the same protocol. What is the error you are getting?
Also try: http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers

keitht said:
Yes and since you copied files already, it is working for that. USB debug does not appear to use the same protocol. What is the error you are getting?
Also try: http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
Click to expand...
Click to collapse
Well, when I plug my xoom in (when I have USB debug clicked), it starts searching for drivers. Then it asked for me to insert the installation disk for MZ600. I click check for solutions and then the attached error comes up.
View attachment 535149

ghoticov said:
Well, when I plug my xoom in (when I have USB debug clicked), it starts searching for drivers. Then it asked for me to insert the installation disk for MZ600. I click check for solutions and then the attached error comes up.
View attachment 535149
Click to expand...
Click to collapse
Did you try that link I sent you from Moto?

Droid 4 Utility for Windows/Mac/Linux

Hey all! This is the new home of the Droid 4 Utility (NOW WITH SAFESTRAP THANKS TO HASHCODE) for Windows/Mac/Linux!
There are (still) no fastboot files as of writing this (2/28/2012) so use Safestrap at your own risk
Once they come out I will be making a full version that includes fastboot restore. For now, the utility is only a few MB compared to a GB+.
From this point forward I will be taking charge of updating the Droid 4 Utility for Windows/Mac/Linux
This way mattlgroff has a little less work on his hands and can focus more on IMPORTANT things like bootloaders, ICS, etc...
MAC/LINUX: Be sure to read the instructions below (or README file) if you are not familiar with using terminal as root or executing bash scripts!
-Changes
~~as of 2/18/ 11:30PM PST
Fixed bug where Superuser.apk was pushed to /data instead of /system/app/
Fixed unroot script to properly remove Superuser.apk
~~as of 2/19 4:30 PM PST
Fixed chmod in root method from 4775 to 6775
~~as of 2/28 6:15PM PST
Added Safestrap recovery!!
~~as of 3/2
fixed script to chmod +x ./files -R so that you can actually run the files on mac and linux (that would be important huh?)
DOWNLOADS
WINDOWS
Size: 7.75 MB
MD5: f82bf8d8a085ff95b696712b8caa0f1b
Link: http://tinyw.in/KKB8
MAC
Size: 7.19 MB
MD5: dc8468d051d59963914a0b8a054b83b8
Link: http://tinyw.in/vx2A
LINUX
Size: 7.26 MB
MD5: 0c082efbff48e614b9d8ebffc7eca3eb
Link: http://tinyw.in/tpt0
Here's how:
Windows:
Simply Unzip the files, and run Droid4Windows.bat as administrator (right click>run as administrator)
Mac/Linux:
Simply extract the zip then
Code:
su
Then enter the root password NOTE: This is not YOUR password, this is the ROOT password. If you dont know it, you can always use
Code:
sudo passwd
to reset the root password
Next run:
Code:
cd /the path to where you extracted the files/
for example, heres what I have to type:
Code:
cd /home/skylar/Desktop/Droid4UtilityLinux/
next run the appropriate bash script:
Code:
bash Droid4linux
OR
Code:
bash Droid4mac
I'm sorry to say I don't actually own a Droid 4, so I'm doing this blind. Please report any problems or bugs you have.
Have fun and I hope you enjoy! [/SIZE]
CLICK HERE TO DONATE
SCREENSHOTS
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CLICK HERE TO DONATE

I can not get this to unroot.
---------------------------------------------------------------
Easy rooting toolkit (v1.0)
UNROOTING SCRIPT
created by DooMLoRD
based heavily on FlashTool scripts (by Bin4ry and Androxyde)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
MAKE SURE THAT THE SCREEN IS UNLOCKED
and if you get Superuser prompts ACCEPT/ALLOW THEM
ELSE THIS WILL NOT WORK
Note: This removes superuser from both possible locations
So seeing one error of now finding Superuser is NORMAL!
---------------------------------------------------------------
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
The system cannot find the path specified.
--- TESTING FOR SU PERMISSIONS
MAKE SURE THAT THE SCREEN IS UNLOCKED
and if you get Superuser prompts ACCEPT/ALLOW THEM
ELSE THIS WILL NOT WORK
The system cannot find the path specified.
--- cleaning
The system cannot find the path specified.
--- pushing busybox
The system cannot find the path specified.
--- correcting permissions
The system cannot find the path specified.
--- remounting /system
MAKE SURE THAT THE SCREEN IS UNLOCKED
and if you get Superuser prompts ACCEPT/ALLOW THEM
ELSE THIS WILL NOT WORK
The system cannot find the path specified.
--- pushing unroot script
The system cannot find the path specified.
--- correcting permissions
The system cannot find the path specified.
--- executing unroot
MAKE SURE THAT THE SCREEN IS UNLOCKED
and if you get Superuser prompts ACCEPT/ALLOW THEM
ELSE THIS WILL NOT WORK
The system cannot find the path specified.
--- cleaning
The system cannot find the path specified.
--- rebooting
The system cannot find the path specified.
ALL DONE
Press any key to continue . . .
The system cannot find the path specified.
Please make a selection or hit ENTER to return:
Click to expand...
Click to collapse

prodigyweb said:
I can not get this to unroot.
Click to expand...
Click to collapse
Sounds like you aren't running this inside the folder that also contains the /files/ folder. If you have it by itself of course the path's won't find it...because you moved it or you aren't "cd" into the directory of the utility.

appears after a phone/computer reboot and canceling the ADB process in my tasks it now is rebooting the phone and working. Thanks!

prodigyweb said:
My setup is: http://i.imgur.com/Surbz.png
should it be within the adb package from android itself?
Click to expand...
Click to collapse
Is your USB Debugging Mode enabled and "Unknown Sources" in your application settings?

Hm, I turned on USB Debugging in the settings, but it's not starting up when I plug in a USB cable, and adb can't find the device. ???

highlandsun said:
Hm, I turned on USB Debugging in the settings, but it's not starting up when I plug in a USB cable, and adb can't find the device. ???
Click to expand...
Click to collapse
While your phone is plugged in, see what drivers are in device manager and remove them. Then restart your phone while its still connected through USB. See if that reinstalls all the necessary drivers and try again.

reigndropz said:
While your phone is plugged in, see what drivers are in device manager and remove them. Then restart your phone while its still connected through USB. See if that reinstalls all the necessary drivers and try again.
Click to expand...
Click to collapse
This is Linux, so no device manager. I think I needed to add the Motorola vendorID to my udev rules first, I got it working eventually. Rooted, great. Now to go and fix the character maps so I can fully use Connectbot.

highlandsun said:
This is Linux, so no device manager. I think I needed to add the Motorola vendorID to my udev rules first, I got it working eventually. Rooted, great. Now to go and fix the character maps so I can fully use Connectbot.
Click to expand...
Click to collapse
Ah ok.....how are you with deodexing? I have been trying to deodex the SystemUI but I am not having any success. I add the jars but it keeps going and going and doesnt seem to end. Soon as I get the SystemUI deodexed, I'll throw a battery percent icon here....

reigndropz said:
Ah ok.....how are you with deodexing? I have been trying to deodex the SystemUI but I am not having any success. I add the jars but it keeps going and going and doesnt seem to end. Soon as I get the SystemUI deodexed, I'll throw a battery percent icon here....
Click to expand...
Click to collapse
Hm, haven't done anything with theming tweaks. Dunno, sorry.
You need adb to be enabled at boot time, so you can adb logcat during the startup and see what failed.
By the way, the Linux archive is not immediately usable, you need to chmod +x everything under the files/ subdirectory to make them executable first.

highlandsun said:
Hm, haven't done anything with theming tweaks. Dunno, sorry.
You need adb to be enabled at boot time, so you can adb logcat during the startup and see what failed.
By the way, the Linux archive is not immediately usable, you need to chmod +x everything under the files/ subdirectory to make them executable first.
Click to expand...
Click to collapse
Hey thanks for pointing that out! I didnt notice because they were already executable on my computer. I added
Code:
chmod +x ./files -R
to the script on startup so no one should have to manually do it anymore, sorry about that

prodigyweb said:
I can not get this to unroot.
Click to expand...
Click to collapse
Make sure you have done all of the steps below
Prework
1. Plug in phone to computer.
2. Turn on USB Debugging. Menu -> Settings -> Application -> Development -> USB Debugging
3. Confirm latest Moto driver is installed. Go to Device Manager on Windows while the D4 is plugged into it and confirm you see ADB Interface listed with Mot Composite ADB Interface listed in the group. If you see that, skip #4 & #5. There are other ways to go about this, but this is the simplest and surefire way to confirm the driver is there and compatible.
4. Go get Moto driver and install it: USB and PC Charging Drivers - Motorola Mobility, Inc. USA It is an exe file that must be run and your computer has to restart when completed.
5. Go back into your Device Manager after reboot with the phone plugged in and confirm ADB Interface is there and no error exists.
Done.

I can't get this to root, it appeared to have rooted once since Superuser was installed but TBU said not root access. Now I get message " error more than one device and emulator" when I try to root again or unroot. any idea?

contemplating getting this through a client, any word on fastboot and unlocked updates?
or is the droid 4 destined to be like all other moto phones and lack a soul...
I really wanted the Photon, but dev on it was strangled to death!

Hammerfest said:
contemplating getting this through a client, any word on fastboot and unlocked updates?
or is the droid 4 destined to be like all other moto phones and lack a soul...
I really wanted the Photon, but dev on it was strangled to death!
Click to expand...
Click to collapse
The phone itself is great. Good build quality, fantastic keyboard, fast, etc. I have not heard any news on fastboot files yet. I assume it's just a matter of time but who really knows for sure. Unlock updates? As in unlock the bootloader? I don't ever expect to see that happen, personally.
Despite that, development seems to be coming along nicely with very usable AOSP CM9, AOKP, and Gummy ROMs. The relative ease with which Razr ROMs can be ported to the D4 (due to almost identical internal components) should help on that front as well as Razr development is seems very strong.

Does this Utility still work after the latest update?
I had previously rooted via this utility and had frozen a bit of bloatware w/ TB. I have since unfrozen the bloatware and unrooted. As soon as the install message pops up again I plan to run the update, but was wondering if I will be able to re-root the same way once I do that.

mancowmilitia said:
Does this Utility still work after the latest update?
I had previously rooted via this utility and had frozen a bit of bloatware w/ TB. I have since unfrozen the bloatware and unrooted. As soon as the install message pops up again I plan to run the update, but was wondering if I will be able to re-root the same way once I do that.
Click to expand...
Click to collapse
I've heard people having mixed results trying to re-root using the utility. Some seem to have no problem but others said they had to run the exploit directly. Not sure why.
I just used the Voodoo OTA Root Keeper app to hide root while the update was being applied and then restored root.

kwyrt said:
I've heard people having mixed results trying to re-root using the utility. Some seem to have no problem but others said they had to run the exploit directly. Not sure why.
I just used the Voodoo OTA Root Keeper app to hide root while the update was being applied and then restored root.
Click to expand...
Click to collapse
I installed the upgrade with no issues. I was able to re-root without complication as well. The only message I received was that the Superuser.apk installation "failed" because it was already there. Others have noted that unrooting doesn't delete the file. But, its presence did not stop my upgrade.
This time I installed Voodoo and will go that route for the next OTA.

Is there a mirror link for the Windows Utility? The download keeps timing out on me.

heres a link for an older copy
http://goo.im/apps/mattlgroff/Droid4Utility0.3.zip

How to install the correct drivers for fastboot to a Windows 10 laptop?

Hi there, I'm a software developer but not an Android developer at all (I have no experience), so answers that are understandable to newbies would be very appreciated
My Moto X4 power button stopped working a few days ago (the phone doesn't register when it is pressed). Based on my Google searching this seems to be a common problem among many users of the phone. Luckily, it wasn't a big issue for me because I could still use the fingerprint scanner to lock/unlock the phone. The problem arose last night when I accidentally let my phone run completely out of battery. With no working power button, I could no longer turn on the phone!
This is especially an issue because I am in a foreign country right now so I can't send my phone in anywhere to get fixed. Yet I really need it for WhatsApp to contact some people today.
I have been following this guide (reddit - How to turn on your phone if/when your power button breaks) to install fastboot and use the reboot command to turn the phone on. Almost every step works fine for me (I successfully installed the Android SDK "platform tools", I can get my phone to go to the fastboot screen by holding the volume down button when plugging in the USB), the only problem is when I plug my phone (in fastboot mode) into my Windows 10 laptop, it does not seem to have the correct drivers installed to communicate with the device. So when I try to run the fastboot reboot command, it just gets stuck at <waiting for any devices> .
I have tried downloading the Motorola Device Manager executable (from here: https://support.motorola.com/us/en/drivers) to install the correct drivers, but even after doing that, when I plug my phone in, the Windows Device Manager still shows my phone as having the incorrect drivers.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I think that it is a compatibility issue. The first time after installing the Motorola software, Windows created a pop-up about the program potentially installing incorrectly and provided the option to re-install using compatibility settings, but since I hadn't tried the drivers at all yet at that point, I ignored it. I have not been able to reproduce the pop-up since.
How do I install the correct drivers so that I can run the fastboot reboot command?
I'm running 64-bit Windows 10 on an HP Envy laptop.
Any help is extremely appreciated, thank you so much!

Omninano said:
Hi there, I'm a software developer but not an Android developer at all (I have no experience), so answers that are understandable to newbies would be very appreciated
My Moto X4 power button stopped working a few days ago (the phone doesn't register when it is pressed). Based on my Google searching this seems to be a common problem among many users of the phone. Luckily, it wasn't a big issue for me because I could still use the fingerprint scanner to lock/unlock the phone. The problem arose last night when I accidentally let my phone run completely out of battery. With no working power button, I could no longer turn on the phone!
This is especially an issue because I am in a foreign country right now so I can't send my phone in anywhere to get fixed. Yet I really need it for WhatsApp to contact some people today.
I have been following this guide (reddit - How to turn on your phone if/when your power button breaks) to install fastboot and use the reboot command to turn the phone on. Almost every step works fine for me (I successfully installed the Android SDK "platform tools", I can get my phone to go to the fastboot screen by holding the volume down button when plugging in the USB), the only problem is when I plug my phone (in fastboot mode) into my Windows 10 laptop, it does not seem to have the correct drivers installed to communicate with the device. So when I try to run the fastboot reboot command, it just gets stuck at <waiting for any devices> .
I have tried downloading the Motorola Device Manager executable (from here: https://support.motorola.com/us/en/drivers) to install the correct drivers, but even after doing that, when I plug my phone in, the Windows Device Manager still shows my phone as having the incorrect drivers.
I think that it is a compatibility issue. The first time after installing the Motorola software, Windows created a pop-up about the program potentially installing incorrectly and provided the option to re-install using compatibility settings, but since I hadn't tried the drivers at all yet at that point, I ignored it. I have not been able to reproduce the pop-up since.
How do I install the correct drivers so that I can run the fastboot reboot command?
I'm running 64-bit Windows 10 on an HP Envy laptop.
Any help is extremely appreciated, thank you so much!
Click to expand...
Click to collapse
Hi, you can try uninstall from device manager, and run cmd cleanmgr-> clean system files, find device driver and click Ok, this erase all obsolete drivers, and install again Moto Device Manager
Or in the device manager, "update driver"->find driver on my pc->chose driver list, and find adb driver.
Good luck
pd. Sorry for my english, isnt y native languaje and my SO is in Spanish

Datclefxuj said:
Hi, you can try uninstall from device manager, and run cmd cleanmgr-> clean system files, find device driver and click Ok, this erase all obsolete drivers, and install again Moto Device Manager
Or in the device manager, "update driver"->find driver on my pc->chose driver list, and find adb driver.
Good luck
pd. Sorry for my english, isnt y native languaje and my SO is in Spanish
Click to expand...
Click to collapse
Hi Datclefxuj! No problem about the English, I understand what it is like to not be using your first language
I tried what you suggested, but there are a few small issues I ran into.
First, I uninstalled my phone from the device manager.
Then I ran 'cleanmgr' and clicked my C: drive.
But when you say "find device driver and click Ok", I don't know where the device drivers are located on my computer. Where would I typically find those? This is what my cleanmgr looks like:
Also, when you say "in the device manager, 'update driver'->find driver on my pc->chose driver list, and find adb driver", I do not have an adb driver to choose. Where would I download that from? Do I need an adb driver, anyway? I just want to be able to access fastboot on my phone.
I hope that makes sense. Thank you very much!

Omninano said:
Hi Datclefxuj! No problem about the English, I understand what it is like to not be using your first language
I tried what you suggested, but there are a few small issues I ran into.
First, I uninstalled my phone from the device manager.
Then I ran 'cleanmgr' and clicked my C: drive.
But when you say "find device driver and click Ok", I don't know where the device drivers are located on my computer. Where would I typically find those? This is what my cleanmgr looks like:
Also, when you say "in the device manager, 'update driver'->find driver on my pc->chose driver list, and find adb driver", I do not have an adb driver to choose. Where would I download that from? Do I need an adb driver, anyway? I just want to be able to access fastboot on my phone.
I hope that makes sense. Thank you very much!
Click to expand...
Click to collapse
it's here
or after to install motorola drivers
this is my drivers
https://drive.google.com/file/d/1chPe7UJpDC-rkSBoOGcmC0rJDYKmf966/view?usp=sharing
:good:

Datclefxuj said:
it's here
or after to install motorola drivers
this is my drivers
https://drive.google.com/file/d/1chPe7UJpDC-rkSBoOGcmC0rJDYKmf966/view?usp=sharing
:good:
Click to expand...
Click to collapse
MUCHAS GRACIAS!!!!
After following your steps, it worked! I am able to use my phone again!
En serio, thank you so much! I cannot thank you enough!

Omninano said:
MUCHAS GRACIAS!!!!
After following your steps, it worked! I am able to use my phone again!
En serio, thank you so much! I cannot thank you enough!
Click to expand...
Click to collapse
Great! You're welcome!