Database Users

Can no longer connect via adb

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.

How to get ADB interface for Lenovo IdeaPad S2110AF

Since I bought the Lenovo IdeaPad S2110AF from NY, I was searching for how to root the device and I found this thread http://forum.xda-developers.com/showthread.php?t=1896899.
But I was unable to get the ADB interface on Windows 7 x64 laptop and I found the same problem is there for most of the users. Finally last night, I could fix this issue and root my tablet. How I did it:
Download the "S2110-Root.zip" file through the above URL. and extract it to a folder.
1. Enable USB debugging under Settings-> Developer options.
2. Connect tab to computer using the provided data cable.
3. The driver for OTP will be installed in Windows. But the ADB interface may not be installed automatically.
4. Go to Device Manager (Right click My Computer and Properties, the click Device Manager).
5. You can see Other Devices-> Android
6. Right click on that and click Update driver software.
7. Click "browse my computer for driver software"
8. Click "Let me pick from a list of device drivers on my computer" rather than browsing and selecting the driver folder.
9. Click Next and then click "Have Disk" .
10. Then choose the drivers folder and the inf file (in extracted files) - \S2110-Root\Drivers\android_winusb.inf
11. Then select the ADB interface and click OK.
12. Ignore any warning message (like not signed)
That is it. Now you got an ADB interface. You will see as Samsung device on the device manager, never mind it.
Now you got the ADB interface and follow instruction to root through the URL.
Note: I am not sure is this a right place, but I just wanted to post this, it may help someone

I had some problems getting root to work.
I found out to use root with adb the display must be on and unlocked.
I started to work on recovery.img, finally I extracted it and took a look on it. Seems not too hard to get it modified and after do some play with custom roms.

Diagnosing USB Driver and ADB issues in Windows

Are you getting errors like "device not found" or "device offline" while trying to run ADB commands? Here's a quick way to troubleshoot your problem on Windows.
Steps
1. Ensure USB Debugging is enabled in Developer Options.
2. Verify current Google USB Driver is installed and that Device Manager is using that driver.
3. Update to latest version of ADB.
1. Ensure USB Debugging is enabled in Developer Options.
Enable Developer Options by going to Settings -> About Phone and tapping on "Build Number" multiple repeated times. You will be greeted with "You are a developer."
Now, under Settings -> Developer Options, ensure you check the box for "USB debugging."
2. Verify current Google USB Driver is installed and Device Manager is using that driver.
You may skip this step if Device Manager lists your phone as "Android Phone -> Android Composite ADB Interface." If it does not, this is likely your root cause.
Go to the Google USB Driver page and download the latest driver directly from Google. Extract the zip file to a folder you know and will remember in the future.
Open up Device Manger in Windows with your Nexus 5 connected. Whatever your Nexus 5 is currently detected as, right click on it and select Properties. Then, in the Driver tab, hit "Uninstall." If available, select "Delete the driver software for this device." and hit "OK." It will remove the old drivers.
Restart your computer.
After restarting, reconnect your Nexus 5. It should be recognized as an unknown device in the Device Manager. (If it isn't, try the previous driver deletion steps again.)
Right click on the unknown Nexus 5 device, choose Properties, and in the Driver tab again select "Update driver." Browse your computer manually by putting in the path to the new Google USB Drivers you unzipped to a folder of your choice in the beginning of this step. Choose next and your drivers should install! You'll know everything completed successfully when you see the phone listed under "Android Phone -> Android Composite ADB Interface" in Device Manager.
This is the most finicky process, so don't be afraid to reboot your computer a time or two and repeat these steps if they don't work on the first try.
3. Update to latest version of ADB.
This is a crucial step. The new version of ADB is required to work with the "USB debugging authorizations" setting.
Perhaps you know how to update ADB, in which case, just do it. However, here's a detailed manual approach to download JUST the adb suite from the SDK:
Go to the Google Android SDK website and choose "Use An Existing IDE" and click the "Download the SDK Tools for Windows." This will allow you to download only an 80 MB file rather than the whole 400 MB suite.
Install the SDK tools exe to a folder of your choosing.
Run SDK Manager and uncheck everything except for "Android SDK Platform-tools." This is the ADB and Fastboot bundle. Install that.
Navigate to your SDK Path as indicated at the top of your Android SDK Manager window. You will now see a freshly downloaded platform-tools folder containing ADB.exe, Fastboot.exe, and a host of other files. That folder is now your updated, portable ADB tools folder. You can move it anywhere you like as long as you run ADB from a command prompt window set to that directory.
After you've followed these procedures, running "ADB Devices" should trigger a prompt on your device to accept the RSA fingerprint of your computer. Accept it, and now all should be working as intended!
Questions? Ask below!
Thanks to:MaxRabbit

Other solutions
Windows 8 Diagnosis
Originally Posted by Yorus
The following worked for me, since all of the suggestions mentioned here didn't work for me:
If you use a Windows 8.1 enterprise N or KN edition, install the Microsoft Media Feature Pack :
http://support.microsoft.com/kb/2929699/en
Sounds too simple to be true but work instantly for me.
Hope it works you some of the people here looking for a solution
Click to expand...
Click to collapse

[GUIDE] Bypass FRP Tested on 6.0

Hi All,
After seeming that I'm locked out of my own device for 72 hours, I managed to scour the net and use parts of other tutorials to successfully bypass the "you're device was reset, please log in" loop.
So I should point out I was running a Pure Nexus rom running 6.0 with a custom recovery, you're results may differ but you've got nothing to loose.
Pre Requisite
ADB and Fastboot - You don't need to spend an hour installing the whole kit, just visit http://developer.android.com/sdk/index.html and scroll right down to the section where it says "SDK Tools Only" and click on "installer_r24.4.1-windows.exe"
Once installed the SDK manager will open, now make sure the top 3 are checked which are:
Android SDK Tools
Android SDK Platform-tools
Android SDK Build-tools
And also scroll down in the list to find Google USB Driver
Once all of that is done download the latest Google USB drivers (although the SDK installs USB drivers it still shown an exclamation mark in device manager") http://developer.android.com/sdk/win-usb.html
To install those USB drivers just go into device manager and if you se Nexus 6 under "Other Devices" just right click and click update driver software and then click browse my computer and get it to scan the Google USB driver folder you downloaded.
restart your phone into recovery (Volume Down and Power button)
now again in device manager make sure the Nexus 6 doesn't have a yellow icon identifying there's a problem with drivers or that the nexus 6 is listed in other devices. If either of those are present right click and update drivers > browse from computer and select the Google USB drivers you downloaded previously.
Bypass FRP
With all that confirmed restart your Nexus and leave it on the Welcome screen.
Now, you need to get into platform tools which is located:
C:\Users\YOURUSERNAME\AppData\Local\Android\android-sdk\platform-tools
if you can't see AppData you need to enable hidden files and folders
once in platform tools hold SHIFT and right click any blank space and click "Open command window here"
then type "adb devices" and it should list your nexus under devices, if it doesn't open device manager and check your drivers.
If it does show your nexus execute this command which edited from another source:
"adb shell am start -n com.android.settings/.Settings"
Your nexus will now open the settings menu =] in settings go to "Backup & reset" then click "Factory data reset" (although it says it wipes user data, mine was untouched, I can't say the same for so you may lose some data if you proceed)
your phone will reboot and in my case it opened my custom recovery and executed a script, the phone will restart again and go to boot, hold the power button to force shut down the nexus and boot into recovery mode. In recovery mode flash a ROM, if you don't have a ROM download one on your PC and then connect your Nexus to your PC via USB and copy it over.
Once the ROM is installed you won't get the "you're device was reset" screen.
"

You left out some key details which are covered in the guide I wrote up a few days ago. Here's the link.
http://forum.xda-developers.com/showthread.php?t=3261846
Sent from my Nexus 6 using Tapatalk

this does not work, because in order to adb devices to populate anything you would of had to enable usb debugging from within the phone, and if you're locked our from FRP, you cant access the settings to turn on the usb debugging

Bootloader LOCKED .. and asking for gmail ID ??

Guide: If your android (pixel 2) ADB works in Window but NOT in recovery mode

I ran into a very weird issue lately. My PC running Windows 10 (previous Windows 7) and having gone through more than 4 phones with me without cleaning out my system had a ton of old drivers for different phones attached to the computer. Whenever I'd plug my Pixel 2 into the computer ADB worked fine but for some reason when I go into recovery it wouldn't recognize my phone. I rummaged through hours worth of forums/reddit posts guides/youtube videos and everyone kept coming up with the obvious answers being; install the latest adb drivers or force install the google ones or you're entering recovery completely wrong. Being quite savvy in this I tried everything and have sideloaded in the past through recovery on this very phone so it was a real head scratcher what had happened. I went through device manager uninstalled and reinstalled pretty much every adb/mobile device driver associated with the phone. However through some oversight it just wasn't clicking with me when I was in device manager my ADB was listed as "LeMobile Android Device" and even when I uninstalled restarted my computer/phone used different USB cables and ports it never clicked that it shouldn't say LeMobile Android Device because obviously my phone is a Google Pixel 2. Again seeing that I have used this very computer and phone before in the past and have sideloaded OTAs I assumed my old setting would've stuck. But I guess the latest OTA or something on my computer reverted my ADB drivers to a LeMobile Android Device thus causing my ADB to NOT work in recovery anymore but still functioned fine inside Windows.
Through more digging I found a guide on reddit: https://www.reddit.com/r/Nexus6P/comments/5nc64z/adb_drivers_showing_up_as_lemobile_android_device/
Pretty much the top comment/solution is as follows:
A few steps to get rid of the LeMobile pesky driver.
1-Have the device manager opened "devmgmt.msc". Make sure the LeMobile is visible in the device tree by connecting your phone or tablet.
2-Open the Command Prompt with Admin privilege. type "pnputil /enum-drivers" This should generate a list, lookup the "Published Name" value of the LeMobile driver, should be something like "oem??.inf" Remember this name.
3-Use the following command in the Command Prompt with Admin rights: "pnputil /delete-driver oem??.inf /force" Of course oem??.inf should be the name you found in step 2.
4-Go to the device manager. Right-click on the LeMobile device still shown in the device manager and select "Update Driver Software". Now you can browse to your preferred driver like the one in location "C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver"
5-And You're done! Cool thing is that you will have to do it again if you connect a tablet or something new and Microsoft decides the LeMobile driver is better then Googles driver...
So yes in the future I may have to do this setup again because Microsoft is just dumb and doesn't let settings stick but I went through the list and force deleted all my old phones from Motorola and Samsung as well so when I installed the ADB drivers finally the Google one's stuck. Hopefully this will fix many other people's problems when they can ADB in windows but NOT in Recovery. My other option would be to format my computer and have a fresh install but ain't no one got time for that. There are other guides online to fully delete drivers but it is very time consuming so I'm going to skip that for now.