i am trying to use usbdeview to uninstall my droid software, since when i type in "adb devices" in cmd, my phone does not show up.
thanks!
Related
I am trying to access my phone through ADB to register w/o data. My device center and device manager both see the phone ("Android Phone" in DC, and "ADB Interface > HTC Dream" in DM). However, when I run ADB from the command line it cannot find my device. I have tried reinstalling drivers, killing and starting the ADB server, and even re-flashing my phone.
Note: When booting the phone from a fresh flash I DON'T have to enter "<enter>setprop persist.service.adb.enable 1<enter>" to initialize ADB. It is automatically seen as an ADB device, and after entering the command it is only seen as a storage device.
Thanks in advance.
(unlocking a Dream on Windows 7 x64)
Solved it by installing the drivers from here: http://www.mydigitallife.info/2009/08/24/workaround-for-htc-hero-sync-problem-in-windows-7/
New:
About 2 minutes after I posted this I typed "adb devices" again and it was listed. This was after 20 minutes of trying the various things listed below.
New explorers, be forewarned.
Was:
I've installed the Samsung USB drivers and I see the Samsung Android USB Composite device in my devices list. I have USB debugging turned on. I've rebooted my PC. My device is not listed when I do "adb devices" (nothing is). When I reboot and type that, it starts the daemon up succesfully and then presents an empty list. I'm running Vista 64.
Doing a search for this has yielded nothing - everyone seems to assume it just works. So why doesn't mine?
This guide is for people that have always problems with drivers, ADB or fastboot problems, with this guide you will clear all.
Tested and working with windows 8.1 (it will work with all other versions of windows, probably not with Windows 10 preview).
*0) Unplug of course the phone from the PC
1) Download USBDeview (32bit version here http://www.nirsoft.net/utils/usbdeview.zip - 64bit version here http://www.nirsoft.net/utils/usbdeview-x64.zip) to erase every driver on the pc (look under "Description" tab and uninstall all Asus things, MOOREFIELD, delete also your previous phones drivers or unused devices)
2) Reboot
3) If you are on windows 8 or 8.1 disable driver signature verification and than install
1- Intel Drivers https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
2- ADB Installer http://forum.xda-developers.com/showthread.php?p=48915118#post48915118 (don't change installation path)
4) Reboot
5) Go in C:/adb, hold shift on keyboard, right click in the folder and "Open command prompt here"
6) Go to recovery with the phone plugged in
7) Tap apply update from ADB Sideload
7) Type in the previous cmd window: adb devices
If you can see your device, congratulations!
Thanks to @cangcan to this other tip:
If you installed bluestack on your pc, adb will show 'device emulator' something like that and you need to turn off the bluestack service..
1. Go to start and type services.msc
2. Look for Bluestack android service
3. Stop or disable the service
Its messing up my adb connection in windows 7 and now the zf2 device is recognised on adb after disabled Bluestack services..
Thanks to- Everyone in this section
Snoop05 for "15 seconds ADB Installer"
another thing i found for adb device not recognised for example in my case before..
if you installed bluestack on your pc or laptop, adb will show 'device emulator' something like that..
you need to turn off the bluestack service..
1. go to start and type services.msc
2. look for bluestack android service
3. stop or disable the service
its messing up my adb connection in windows 7 and now the zf2 device is recognised on adb after disabled bluestack services..
type adb devices to confirm it.
cangcan said:
another thing i found for adb device not recognised for example in my case before..
if you installed bluestack on your pc or laptop, adb will show 'device emulator' something like that..
you need to turn off the bluestack service..
1. go to start and type services.msc
2. look for bluestack android service
3. stop or disable the service
its messing up my adb connection in windows 7 and now the zf2 device is recognised on adb after disabled bluestack services..
type adb devices to confirm it.
Click to expand...
Click to collapse
I will add this to first post, thanks
Hello, I badly need someones assistance. I accidentally installed the OTA update on my rooted zenfone 2 causing it to be bricked. I have spent the last 3 hours uninstalling and then reinstalling the drivers per the above directions. My PC recognized when I connect the phone via USB, and it is showing up as a working device in the device manager screen. It shows the drivers are installed properly and everything but I just cannot view it. I tried disabling the bluestack (it actually was not turned on but I made sure to disable it in case) and that did not work as well. I now have a zenfone 2 that is currently a paperweight and I cannot for the life of me figure out what to do next. Any help would be greatly appreciated.
Thank you for this
Trying to run adb results in the USB notification to cycle off/on on the new Moto G5 Plus. I've tried multiple cables, computers, and a factory reset of the phone (both times with the factory image).
Has anyone encountered such an issue?
Basically, I can enable debugging mode and connect my computer, but the moment I issue `adb start-server` the USB notification on the phone begins to cycle. There is no message to authorize the device or anything. For what it's worth, this computer works fine with another device (as does the other). I've deleted the .android directory and saw no change, too.
badhat said:
Trying to run adb results in the USB notification to cycle off/on on the new Moto G5 Plus. I've tried multiple cables, computers, and a factory reset of the phone (both times with the factory image).
Has anyone encountered such an issue?
Basically, I can enable debugging mode and connect my computer, but the moment I issue `adb start-server` the USB notification on the phone begins to cycle. There is no message to authorize the device or anything. For what it's worth, this computer works fine with another device (as does the other). I've deleted the .android directory and saw no change, too.
Click to expand...
Click to collapse
I'm confused... What are you trying to do? I've never used that command...
acejavelin said:
I'm confused... What are you trying to do? I've never used that command...
Click to expand...
Click to collapse
The `start server` command just begins to run the adb daemon. It is run without explicitly issuing this command if you run something like `adb devices`. It's like setting up the environment without actually querying anything on the device.
badhat said:
The `start server` command just begins to run the adb daemon. It is run without explicitly issuing this command if you run something like `adb devices`. It's like setting up the environment without actually querying anything on the device.
Click to expand...
Click to collapse
I tried this just out of interest... revoked all ADB authorizations, rebooted my phone and PC, and connected and did a "adb start-server". It popped up the authorization windows like normal, I approved it and it worked like normal. Subsequent kill-server and start-server commands had no unusual effects either after revoking authorizations or not.
acejavelin said:
I tried this just out of interest... revoked all ADB authorizations, rebooted my phone and PC, and connected and did a "adb start-server". It popped up the authorization windows like normal, I approved it and it worked like normal. Subsequent kill-server and start-server commands had no unusual effects either after revoking authorizations or now.
Click to expand...
Click to collapse
OK, I tried using a different Android SDK (grabbed from https://dl.google.com/android/repository/platform-tools-latest-linux.zip) and now it's working. There must be something about the one my distribution packaged that is broken.
Code:
$ adb version
Android Debug Bridge version 1.0.39
Revision 8.0.0_r11
$ LD_LIBRARY_PATH=$PWD ./adb version
Android Debug Bridge version 1.0.39
Revision 3db08f2c6889-android
Installed as /home/badhat/Downloads/adb/platform-tools/adb
Been trying to get an adb connection to this phone. I'm on the latest Sprint available OTA (NMJ32F). Have not side loaded the later version. Never rooted.
When connecting the phone to PC, device manager shows "Essential Phone ADB" is working properly. I also tried the Google generic ADB driver. The phone also shows a notification "ADB debugging is connected. Tap to disable".
"adb devices” always returns empty. I am able to adb other devices.
I think the problem is the phone is not asking me to authorize the ADB connection as my other phones and tablets normally do.
Any idea?
Did you get permissions on your phone when popup appears?
No. The phone doesn't pop up the permission question. But I don't know why.
Don't know but as long as you don't give permission you can't sideload
Euclid's Brother said:
Been trying to get an adb connection to this phone. I'm on the latest Sprint available OTA (NMJ32F). Have not side loaded the later version. Never rooted.
When connecting the phone to PC, device manager shows "Essential Phone ADB" is working properly. I also tried the Google generic ADB driver. The phone also shows a notification "ADB debugging is connected. Tap to disable".
"adb devices” always returns empty. I am able to adb other devices.
I think the problem is the phone is not asking me to authorize the ADB connection as my other phones and tablets normally do.
Any idea?
Click to expand...
Click to collapse
Try the usb driver and SDK platform tools directly from Essential website:
https://www.essential.com/developer/current-builds
I am using the drivers from Essential website. However, I was using the lastest Unified Android Toolkit for the adb command. Looks like it may be outdated, as the adb.exe and it's dll's in the link from Essential website is newer. I will try the platform tools from there and see if there is a difference.
Thanks!
Is USB debugging enabled in Developer settings?
Are you in Fastboot? Did you try "fastboot devices"?
ADB devices returns your device is offline?