I've had ADB working successfully in the past, but now nothing is listed after an "adb devices" command, and a "device not found" error for other commands. I was on Royal Ginger 2, and just updated to the latest CM7 nightly - then wanted to use ADB to tweak a few things and found out something was wrong. What else do I need to do to get adb to recognize my device?
I haven't changed anything on my laptop, which is Win7 64bit, and I've updated everything in SDK Manager. Device Manager on the laptop shows T-Mobile myTouch4g USB Device under Disk drives on the Device Manager, and I believe I have the latest mt4g drivers installed. I'm connecting via USB with debugging turned on, and without turning on USB storage.
Any ideas?
I was finally able to get adb to recognize my device again. FYI, I tried a few different things, but I think what finally got it working was tweaking the *.inf file in the usb_driver folder in SDK, the uninstalling/reinstalling the drivers - as outlined here:
http://forum.xda-developers.com/archive/index.php/t-881324.html
Related
Hi all,
I've searched the forums (honestly), but I can't find an answer to my problem.
I have a Vodafone branded 32B phone.
I installed the AndroidSDK as supposed to, added the path, made the phone root, booted into the recovery console using fastboot and flashed my phone with different operating systems... but during all this time I hever got ADB to work.
Whatever I do, adb never finds the phone. Fastboot works and finds it, when it's in fastboot mode, but ADB never. So, I can't permanently install the recovery console nor do any of the other funky stuff.
ADB doesn't work when the phone is in fastboot mode nor normally operating. I have USB Debugging turned on. The phone works normally and I can access the SDCard just fine.
Any help?
Suggestion.
Look into purchasing a G1 to be kept as a spare and used for development. That's what I've done with my G1. GParted is within most recovery images nowadays, therefore you can do most anything there, well...important functions that is. Keep that in mind.
You might need to uninstall the driver that recognizes your phone, then manually install the updated driver.
Reignzone said:
You might need to uninstall the driver that recognizes your phone, then manually install the updated driver.
Click to expand...
Click to collapse
that's what i had to do to get it to recognise my phone.
i'm pretty sure the driver came with SDK. either way i've attached the one i used.
go into device manager and update the driver it's currently using with the attached one.
Incorrect driver.
It should be the 1st driver listed in the Android SDK file.
As far as I know, you could also choose to push ADB to your system32 file folder under the C: drive in your computer. That is if you're using a Windows machine.
just a thought
Are you on windows or linux? If you're in ubuntu try sudo adb ... the default unprivilaged user doesnt automatically have access to the device.
If you're in Windows I would uninstall the Android Phone device in device manager and reboot with the phone disconnected. Then connect it and install the usb driver from the sdk when prompted. Might also pay to download the sdk again.
Install HTC Sync
Another known way to fix the issue is to download and install HTC Sync http://www.htc.com/au/SupportViewNews.aspx?dl_id=573&news_id=169
This seems to install the correct drivers
For more info check the Wiki:
http://wiki.xda-developers.com/index.php?pagename=HTC_Sapphire_Hacking#sec02
Hey Guys,
Forgot to mention I'm on Windows Vista 64 bits.
That last suggestion did the trick. I went to the site and downloaded the HTCDriverUpdate_Vista_64bits.exe, and within seconds I had an ADB connection.
Thanks for your help!
Hello folks,
I had a WinXP computer, and I installed android SDK, and I was able to connect to my nook via ADB. As it was aging and having fan problem, I bought a new Dell (i5, win7, 4Gb RAM, 500 Gb HD). I installed android SDK, but never tried to ADB my nook. Yesterday I tried it, and whenever I try to connect via IP, or use adb devices, nothing shows up. I tried messing with the firewall, but it was not working at all.
Does anybody have any idea to help me? And also on how to get my firewall back (removed Norton, which I believe is a bloating spyware, and installed avast antivirus, but firewall was not released either, and it gives a 0x80070424 error).
Try this
Attach the usb cable to the NST and see if it is visible in device manager. Ideally if no driver is installed, you would just see it there with an exclamation mark.
Then follow ros87's instructions here. If adb_usb.ini doesnt exist create it.
Then from device manager, update device drivers for the unrecognized nook and point it to the i386/amd folder within the android drivers folder.
once that is done, restart adb, run "adb usb", then try "adb devices". If it worked it should show you the device.
ADB wifi was easier. In fact, it was such a long time since I last used it (before 1.1.1), that I forgot to add the adbwireless button to turn it on.
But thanks anyway. I've never dared to use USB due to inner messiness of the process.
I am hoping someone can help me before the ICS OTA hits in the US.
I am trying to root, but I can NOT get ADB to see the TPT.
I am using win 7 64 bit, and have downloaded the adb driver and modified the .inf. It shows up in dev man under android phone as thinkpad adb, but when I run adb devices...nothing.
I installed that latest Java dev and android stk but still nothing.
The TPT is on OTA 2.5.
I have searched everywhere but cannot fined any answer.
Any ideas?
Thanks!
Is USB debugging enabled on your tpt? Did you try a different USB cable/port? On your PC are you in the same directory as adb.exe?
Yes, Yes, and Yes.
ADB is running fine...it just cant see the TPT even tho windows can.
I'm sure you're a little frustrated. I had that happen, and it turned out there were two adb processes running. A reboot fixed that. I'm sorry I don't have the answer.
It IS frustrating, but I appreciate your suggestions!
try running the emulator and make sure you can connect to it via adb, as a check to make sure adb deamon is starting up correctly.
True. Worked for me.
For whatever reason, it was my system that I do all my adb work on....just refuses to see the TPT.
Used my notebook with nothing installed and it went just fine.
My Win7-64 PC could only see my TPT as a portable device, and was listed between drive letters. I wanted to see it under "Android Phones."
After about 6 hours of searching, having installed the Lenovo-provided drivers probably 40 times, I went out on a limb and opened the Device Mangler, individually uninstalled each of the portable devices, including the TPT. Rebooted my PC. Plugged in the TPT, and finally it appeared under Android Phones, and ADB recognized it (I typed "adb devices" in the command prompt and it was listed).
What it came down to is the driver that wanted to be the default was trumping the one I wanted. Beware the Diva. She's not all that.
I should add that I also unplugged a usb card reader (that was making all the drive letters) because I thought that might be the culprit, but it still showed up in the Device Mangler, so I don't think unplugging it made a difference.
I miss Win2K.
Hi, my problem is this: my phone is recognized as an ADB device but I cannot see it under adb devices.
Currently running PA RC2 3.99
Fastboot and Recovery do recognize it but ADB does not.
I have the drivers from here installed them as described in the instructions with uninstalling + deleting the old ones and rebooting.
I also have the most updated version of ADB from Android SDK.
One weird thing is that if i uninstall + delete the current drivers and try to install the ones i got from the SDK and not from the thread I mentioned then it does not install them. So maybe that is where my problem...
Any advice??
Thanks in advance.
akrabi said:
Hi, my problem is this: my phone is recognized as an ADB device but I cannot see it under adb devices.
Currently running PA RC2 3.99
Fastboot and Recovery do recognize it but ADB does not.
I have the drivers from here installed them as described in the instructions with uninstalling + deleting the old ones and rebooting.
I also have the most updated version of ADB from Android SDK.
One weird thing is that if i uninstall + delete the current drivers and try to install the ones i got from the SDK and not from the thread I mentioned then it does not install them. So maybe that is where my problem...
Any advice??
Thanks in advance.
Click to expand...
Click to collapse
Did you enable usb debugging?
Also check that you have an option selected under Settings>Storage>USB Computer connection, not having either MTP or PTP selected there will also bork adb.
If you still can't get it to work, try Koush's universal drivers: Link
still not working...
1. Yes, usb debugging is on.......
2. Already tried toggling MTP/PTP/None - When on MTP driver installs successfully but I cannot see the device under adb devices. on the other two options (PTP/None) I am unable to install the driver (tried both the ones on XDA and the ones from MDK)
3. Tried Koush's universal driver - on PTP/None still not able to install drivers. On MTP didn't do much except for changing device name from Android ADB Device to Google Nexus ADB Interface
Thanks for all the quick replies,
Any other suggestions???
akrabi said:
1. Yes, usb debugging is on.......
2. Already tried toggling MTP/PTP/None - When on MTP driver installs successfully but I cannot see the device under adb devices. on the other two options (PTP/None) I am unable to install the driver (tried both the ones on XDA and the ones from MDK)
3. Tried Koush's universal driver - on PTP/None still not able to install drivers. On MTP didn't do much except for changing device name from Android ADB Device to Google Nexus ADB Interface
Thanks for all the quick replies,
Any other suggestions???
Click to expand...
Click to collapse
what does it say when you issue the "adb devices" command? Please write it out here so we can help you. Does it say "device offline"? If yes, then your device is not registered by digital fingerprint by Android SDK.
taodan said:
what does it say when you issue the "adb devices" command? Please write it out here so we can help you. Does it say "device offline"? If yes, then your device is not registered by digital fingerprint by Android SDK.
Click to expand...
Click to collapse
Ok, so I'm with my Nexus connected as an MTP device, with the driver from XDA installed (see attached image), USB Debugging enabled:
Code:
C:\>adb kill-server
C:\>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\>adb devices
List of devices attached
C:\>
Any advice???
Anyone has any advice??
I really have not idea what to do. Tried everything...
Thanks
Works on a different computer
I've connected the phone to my borther's PC and installed the drivers from the SDK. It worked without any problem.
I really can't figure out why it's not working on my laptop.
[Solved]
OK...
So as I said before I tried connecting when PTP is checked and when neither PTP nor MTP are checked and on both couldn't install the drivers properly (neither from xda nor from sdk).
What worked for me:
1. Uncheck both PTP & MTP
2. Device Manager -> Nexus 4 -> Update Driver Software -> Browse my computer for driver software
3. Now instead of browsing to the location I went to "Let me pick from a list..."
4. It should show a list of devices/manufacturers. Clicked "Show All Devices"
5. On the bottom right click "Have a disk"
6. Point to the android_winusb.inf file from Android SDK
7. Choose Android ADB Interface from the list
8. Let driver install
Click to expand...
Click to collapse
Hoped it will help someone.
Thanks to everyone that tried to help. :good:
I downloaded latest ADB/Fastboot package to my Win 7 PC.
I installed the Zadig drivers exec to load drivers (as seen in another thread).
Enabled USB debug
Connected phone
ADB devices ... doesn't show phone
Phone shows ADB icon in task bar
In device manager I can see libusbK USB Devices .. ADB Interface (Interface 1) .. when I plug the phone in
I have revoked previous computers and rebooted both PC and phone with no changes
... now I am a bit lost
* Bump * .. I can't do much without ADB ... could someone at least point me to the correct drivers - what I have downloaded from Zadig do't seem to work.
I'm currently having the same problem of not being detected when I type in "ADB devices" in Windows 10 after an auto-update which can't be stopped screwed up my drivers. I found this thread while searching for an answer myself. I tried reinstalling all Qualcomm and fastboot drivers and even though my phone can be detected in Windows again (after manually selecting "MTP USB Device" as a driver update for the A7 in the device manager) I still get nothing when I type in ADB devices. Though I tried flashing something to it anyway (same TWRP recovery I already have since the file was already there) and it seemed to work? Have you tried flashing something to your phone anyway?