Related
Now I know your first thought “I bet this tool didn’t even use Search like the rest of the shlubs on here”. Well you are mistaken. I have not only searched xda but even tried Google and Yahoo (just in case) as well. I have found numerous posts (like HERE and HERE and many others) with similar situations but haven’t seen a resolution. Here is the rundown:
Running JF’s 1.5 CRB21 ROM
Hard SPL (HSPL10.95.3000)
JF’s 1.43 Recovery Image
SDK 1.5_r1
Fastboot.exe placed in System32
Haykuro’s Updated Drivers placed in System32
Windows XP 2002 SP3
I have been able to flash nandroid backups without issue in the past but adb started intermittently not recognizing my phone when I flashed from JF’s RC33 to JF’s 1.5. I was able to restore a backup once but now adb will not recognize my phone at ALL. Tried different USB plugs and cables with no result. If I mount the phone to view the SD card via Windows Explorer it shows as “HTC Dream Composite ADB Interface” in Device Manager. However if I boot into the Bootloader (which I have the Hard SPL HSPL10.95.3000) , connect via USB, hit back to go into Fastboot, and try to flash a nandroid backup I get "Waiting on Device" infinitely. “Adb shell” yields “Device Not Found”. The "adb devices" command yields a blank list. But if I type "Fastboot Reboot" it will reboot the phone so I know it is communicating and the cable is in good order. I have deleted my SDK and drivers and re-downloaded/installed them and STILL cannot get adb to connect. It has to be something simple I am missing here right? Any idea why this would have worked without issue in the past and now not at all? Could it have been a Windows Security update? (That's about the only thing I can thing that has changed other than the newer ROM)
Thank you for your help.
Did you update you USB Drivers or try reloading them?
Also.... Settings > Applications > Development > USB debugging has to be checked....
and stop being a tool.
nah im jk.
USB Debugging is checked - thanks Senorkabob for at least trying to help.
Phoenix - I apologize for posting in the wrong place. If I could move it, I would. I apparently missed the "How to be a Good Xda Citizen" thread... I shall repent
Could you choose View -> "Devices by Connections" in Device Manager and uninstall the USB Root Hub device your android is connected to. This should clean up all the device nodes and allow you a clean start. Click "Scan for hardware changes" in the toolbar and wait for the system to detect your phone. In the new hardware detected wizard, make sure you specify the path to drivers folder of the correct architecture, i.e. x86 or x64.
gPhunk said:
USB Debugging is checked - thanks Senorkabob for at least trying to help.
Phoenix - I apologize for posting in the wrong place. If I could move it, I would. I apparently missed the "How to be a Good Xda Citizen" thread... I shall repent
Click to expand...
Click to collapse
Repent .. Repent..
Did reloading the USB Driver work?.. Did for me =)
billc.cn said:
Could you choose View -> "Devices by Connections" in Device Manager and uninstall the USB Root Hub device your android is connected to. This should clean up all the device nodes and allow you a clean start. Click "Scan for hardware changes" in the toolbar and wait for the system to detect your phone. In the new hardware detected wizard, make sure you specify the path to drivers folder of the correct architecture, i.e. x86 or x64.
Click to expand...
Click to collapse
How do I know which one to install? (I am running Vista Home Premium 32bit)
Thank you for your help
Use the x86 drivers. Also try installing them in safe mode. That made it work for me
ubernicholi said:
Use the x86 drivers. Also try installing them in safe mode. That made it work for me
Click to expand...
Click to collapse
Thanks man - I was able to install the drivers but am still unable to view my device. It shows as "HTC Dream" in Device Manager but when I run "adb devices" in the command line, it yields a blank list. Further commands (I.e. adb shell) say "cannot find device. Running fastboot commands result in "waiting on device". This happens on both my laptop and my home pc so I am beginning to think it's the phone. Should I have something loaded on the phone? I have USB Debugging checked so that's not it. Any ideas?
possibly the problem is that ADB does not work in Bootloader mode, it is designed to work while the phone is running.
However if I boot into the Bootloader (which I have the Hard SPL HSPL10.95.3000) , connect via USB, hit back to go into Fastboot, and try to flash a nandroid backup I get "Waiting on Device" infinitely. “Adb shell” yields “Device Not Found”. The "adb devices" command yields a blank list. But if I type "Fastboot Reboot" it will reboot the phone so I know it is communicating and the cable is in good order.
Click to expand...
Click to collapse
Yuo are obviously trying this in bootloader mode, underline for emphasis.
try >fastboot devices
see if that shows you your phone
Otherwise try ADB while in the OS already.
Hi,
Have upgraded MB526 to CM11, but now my phone is not recognized by AndroidCommander or EasyADB.
It says "no device connected".
Any help?Thank
karl1957 said:
Hi,
Have upgraded MB526 to CM11, but now my phone is not recognized by AndroidCommander or EasyADB.
It says "no device connected".
Any help?Thank
Click to expand...
Click to collapse
Did you enable ADB in Settings > Developer options > Android debugging?
Note: If you don't see "Developer options" in your settings menu, go to Settings > About phone, and tap 7 times on "Build number" to enable developer options.
Yes, Android debugging is enabled.Debugging icon figures on status bar.
karl1957 said:
Hi,
Have upgraded MB526 to CM11, but now my phone is not recognized by AndroidCommander or EasyADB.
It says "no device connected".
Any help?Thank
Click to expand...
Click to collapse
AndroidCommander wasn't able to recognize my phone either.
Sent from my Nexus 7 using Tapatalk
karl1957 said:
Yes, Android debugging is enabled.Debugging icon figures on status bar.
Click to expand...
Click to collapse
Can you connect using a command prompt, with the "adb shell" command?
This is what I get: "unauthorized device"
karl1957 said:
This is what I get: "unauthorized device"
Click to expand...
Click to collapse
Oh, that's very strange. I just tried connecting ADB on my own phone, and discovered I had the same issue! (Sorry I didn't think to try that earlier.)
It's working now, though. Here's what I did to fix it:
First, I disconnected the USB cable, went to "developer options" on the phone and selected "Revoke USB debugging authorization." Then I disabled and re-enabled USB debugging, plugged in the USB cable again, and this time I saw a prompt on my phone to authorize ADB access for my computer.
Thanks.That worked for adb.
Android commander and easyadb still say "device not connected"
karl1957 said:
Thanks.That worked for adb.
Android commander and easyadb still say "device not connected"
Click to expand...
Click to collapse
I don't use Android commander or easyadb, so I can't help you there. Sorry!
Copied updated platform-tools to Android Commander.
It is working now.Thanks for help.
so i'm trying to root my phone, and connected into fastmode...usb debugging is turned on.... but when i
try to run the adb device command ,my 996 is isn't showing up as devices connected in windows or mac....any suggestions?
Try changing the USB connection type?
For some reason, I had to select the option to connect my device for transferring photos instead of the usual file transfer for it to show up. Is there a particular guide you are using?
Perhaps someone with more knowledge could shed more light on the matter.
If you are in fastboot mode it wont show up in adb devices. it will show up in fastboot devices
me2151 said:
If you are in fastboot mode it wont show up in adb devices. it will show up in fastboot devices
Click to expand...
Click to collapse
thanks, i did notice that...but there's an error device not recognized whenever i type in commands to try to root the phone...
laughingcolors said:
so i'm trying to root my phone, and connected into fastmode...usb debugging is turned on.... but when i
try to run the adb device command ,my 996 is isn't showing up as devices connected in windows or mac....any suggestions?
Click to expand...
Click to collapse
laughingcolors said:
thanks, i did notice that...but there's an error device not recognized whenever i type in commands to try to root the phone...
Click to expand...
Click to collapse
That's because you have to manually chose the driver. Do that and it will work
Still_living714 said:
That's because you have to manually chose the driver. Do that and it will work
Click to expand...
Click to collapse
could you explain a bit? i'm trying to do this mostly in terminal on mac if possible...i thought i installed the drivers for the phone....
laughingcolors said:
could you explain a bit? i'm trying to do this mostly in terminal on mac if possible...i thought i installed the drivers for the phone....
Click to expand...
Click to collapse
Go to the 430 mark
If it helped remember to press the thanks button
Can someone guide me how to get ADB working on OnePlus 5?
stalvekio said:
Can someone guide me how to get ADB working on OnePlus 5?
Click to expand...
Click to collapse
i'm using 'block this!'
What's the problem about it?
download android platform tools or minimal adb and fastboot, make sure drivers are installed and activate ADB Debugging in Developer Options
colin.pohle said:
What's the problem about it?
download android platform tools or minimal adb and fastboot, make sure drivers are installed and activate ADB Debugging in Developer Options
Click to expand...
Click to collapse
I have tried all of those. All i get is emty list. It cant detect my phone.
Probably i havent found the right drivers
stalvekio said:
I have tried all of those. All i get is emty list. It cant detect my phone.
Probably i havent found the right drivers
Click to expand...
Click to collapse
Try these.
I had driver issue for side loading even after Installing OnePlus drivers windows wanted to use standard ADB drivers
Download the Android SDK kit first. Then plug in your OP5 to your PC and you should see something called "CD Drive (F: ) OnePlus Drivers". Click on it and it will install the OP5 drivers. Then enable developer options on your phone, by hitting the build number 7 times. Then go into developer settings and enable USD debugging. After that, go to the Android SDK folder and go to tools/platform tools, then hold shift and right click and open a command/powershell window and type adb devices. After that you should receive a fingerprint notification on your phone so just say yes to it. Ten type in adb devices again in the command/powershell window and it should be able to detect your device. I said everything from scratch so I hope it sort of helps!
What exactly do you want to accomplish. Because I just flashed everything on my phone. When the phone was running normal ADB was not recognized in my phone. However when I was in bootloader mode I got to unlock my bootloader and flash TWRP.
ddaharu said:
What exactly do you want to accomplish. Because I just flashed everything on my phone. When the phone was running normal ADB was not recognized in my phone. However when I was in bootloader mode I got to unlock my bootloader and flash TWRP.
Click to expand...
Click to collapse
Adb still somehow has to work... The drivers are there (although all my win 10 devices installed the correct ones automatically) and it doesn't even really matter which adb he is using
shadowstep said:
Try these.
Click to expand...
Click to collapse
I tried. Device manager still shows adb interface yellow.
d0nsman said:
Download the Android SDK kit first. Then plug in your OP5 to your PC and you should see something called "CD Drive (F: ) OnePlus Drivers". Click on it and it will install the OP5 drivers. Then enable developer options on your phone, by hitting the build number 7 times. Then go into developer settings and enable USD debugging. After that, go to the Android SDK folder and go to tools/platform tools, then hold shift and right click and open a command/powershell window and type adb devices. After that you should receive a fingerprint notification on your phone so just say yes to it. Ten type in adb devices again in the command/powershell window and it should be able to detect your device. I said everything from scratch so I hope it sort of helps!
Click to expand...
Click to collapse
I did that. ADB devices gives me empty list.
stalvekio said:
I tried. Device manager still shows adb interface yellow.
Click to expand...
Click to collapse
Do you have Windows? If yes, what version? With 10, I know they work a 100% for sure. With 7, after installing these, there is still a yellow exclamation mark in Device Manager. To resolve that, right click on the device in Device Manager, uninstall the driver. Then, reconnect the device after enabling USB Debugging, and then let windows download the required drivers from Windows Update. It should be ~8.5 MB. Once it's downloaded and installed automatically, you should be good to go.
shadowstep said:
Do you have Windows? If yes, what version? With 10, I know they work a 100% for sure. With 7, after installing these, there is still a yellow exclamation mark in Device Manager. To resolve that, right click on the device in Device Manager, uninstall the driver. Then, reconnect the device after enabling USB Debugging, and then let windows download the required drivers from Windows Update. It should be ~8.5 MB. Once it's downloaded and installed automatically, you should be good to go.
Click to expand...
Click to collapse
win 8.1.
Did as you sugsested but no change .... adb interface is yellow
stalvekio said:
win 8.1. Did as you sugsested but no change .... adb interface is yellow
Click to expand...
Click to collapse
Stop using the worst windows ever! Jokes apart, try using the these or these. I had them installed before, and they worked fine, in Windows 7 & 10 at least. Good luck! :good:
shadowstep said:
Stop using the worst windows ever! Jokes apart, try using the these or these. I had them installed before, and they worked fine, in Windows 7 & 10 at least. Good luck! :good:
Click to expand...
Click to collapse
Nope. No help.
I think it´s something very easy i have missed
Finaly - got it working.
This guide helped:
http://www.asunsoft.com/android/how-to-manually-install-usb-driver-for-android-phone.html
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?