I installed adb in my desktop successfully last night. when I type adb devices it showed me my devices is attached.
I pulled out framework-res.apk from the x10 then I went to sleep.
but, ****ty happened this morning, after I pluged in my phone, its showed nothing for adb devices.
debugging mode is on, I can see SE sa0101 ADB Interface Driver in Device Manager and also the same usb port from last night.
so what I did wrong ? or is there anything I have missed?
Thanks !
Mod. edit: not dev related, moved to general
Related
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.
Tried to reply to http://forum.xda-developers.com/showthread.php?t=1766475 but as this is my first post, I'm not able to post in development forums :noob:
I've just rooted by Nexus 7 and it took a few hours to do so; for the vast majority of that time I was stuck at the point where I had the drivers installed, tablet was connected to the machine but 'adb devices' showed no devices. Occasionally I would see one line with the serial number of my tablet followed by 'offline'. Running adb devices again would show that the device had disappeared.
I tried various drivers including the ones supplied with the root toolkit, the android sdk, pdanet and the Universal Naked Driver and although all would install and appear correctly in the device manager, my tablet just would not show up in adb devices list. :crying:
Finally, I removed all the drivers by repeating a process of connecting the tablet in usb debugging mode, finding the entry in device manager and uninstalling the device with the checkbox in the dialog ticked to uninstall the drivers, and then disconnecting and reconnecting the tablet (still in usb debugging mode) until it shows up under Other with a name of 'Nexus 7' with an exclamation mark against it.
Next step, I selected to update the drivers and selected the drivers from the android sdk in c:\program file (x86)\Android\android-sdk\extras\google\usb-driver which changed the device to appear as 'Samsung Android Phone -> Android Composite ADB Interface'. I disconnected and reconnected the tablet to ensure everything initialised properly and did 'adb kill-server' followed by 'adb devices'.
At this point, 'adb devices' still did not show the tablet so I spent a good hour searching the internet, with most results suggesting one driver or another that I'd already tried, or the fairly useless 'adb kill-server' followed by 'adb start-server'. Finally I got a result - try moving the device to another USB port on your computer.
I have a Gigabyte GA-Z68AP-D3 motherboard which has 6 USB ports on the back panel; the tablet had been connected to the set next to the HDMI port which are USB 3.0/2.0 ports and are blue in colour. Moving the connector to the USB 2.0/1.1 ports which are red in colour immediately made the tablet visible in the 'adb devices' list. :victory:
TL;DR If your tablet shows up in device manager but not adb devices, try a different USB port
Big thanks to WugFresh for the great tool
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?
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?
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.