[Problem] Adb won't show up devices whatever I do... - Android Software Development

I Tried guides that try to solve this from everywhere, Including here,
I used latest version of the android usb-drivers that comes with the latest Android SDK (downloaded directly from google with the SDK download GUI thinggy).
Tried to uninstall all usb roots,
Tried force removal of driver using external app and re-installations
Tried different drivers from multiple locations,
And still, whatever I try - there is notihng on the "adb devices" list
"List of devices attached"
<CR>
<CR>
C:\.......>
Everything shows up okay, on first run of the adb the 'whatever' service starts and everything is fine
Device DOES appear properly on device manager "Android Composite ADB Interface".
Windows DOES the pnp beep whenever I check or uncheck the "Debugging mode"
This hapnned both on STOCK ROM (first or second software version of the phone released) and on latest Cyanogen 5.0.6
One thing I did noticed, "Android ADB Device" Either appear under "Android" type (usb debugging on) or under USB Controllers (When usb debugging is off).
Ho, I did not mentioned the phone, I'm talking about Nexus One.
Thanks for any help.

Amm, any ideas?

Try using a program named USBDEVIEW, remove the android driver and plug the phone to your PC again and wait to reinstal the drivers.

I take it your on Windows, so I might not be much help as I use Linux strictly but try to run the command prompt as Administrator (right click > run as I think) and then
adb kill-server
adb start-server
Not sure if that will help but I know in Linux you must start the ADB server as root in order to see the attached devices, so I assume in Windows you must start it as Administrator.

I ran into a similar issue with my sapphire. Turns out it was as simple as me having my tethering app on. Once I turned it off (pda net), it worked like a charm. Hope this helps

Beackman said:
Try using a program named USBDEVIEW, remove the android driver and plug the phone to your PC again and wait to reinstal the drivers.
Click to expand...
Click to collapse
I Ment just that when I said "Tried force removal of driver using external app and re-installations"
drew630 said:
adb kill-server
adb start-server
Click to expand...
Click to collapse
Tried that just now, on windows I'm in the Administrators group, that should work... It doesn't :/
bmxrideher said:
I ran into a similar issue with my sapphire. Turns out it was as simple as me having my tethering app on. Once I turned it off (pda net), it worked like a charm. Hope this helps
Click to expand...
Click to collapse
Good idea, but still no salvation :/

Try uninstalling the mass storage driver for the phone, this worked for me

Oh Ehm Gee!!!!
That was perfect! I did that and I got what I needed. Now I'm off to root that som'bish.
+1 to you sir, +1 indeed

Synestr said:
Oh Ehm Gee!!!!
That was perfect! I did that and I got what I needed. Now I'm off to root that som'bish.
+1 to you sir, +1 indeed
Click to expand...
Click to collapse
No problem, lol, almost a month later. Glad I could help.

Naemion said:
No problem, lol, almost a month later. Glad I could help.
Click to expand...
Click to collapse
Hells to the yea, I now has root and rom and I am a happy boy!
Thanks again

hmm >.< nothing is working for me this laptop is not detecting my (Nexus S) device in ADB
windows sees it fine, drivers are installed (for normal mode and ADB mode), mass storage works,
but ADB Devices list shows up empty
2 other phone works just fine (SGS & XT720)
Update: went to another computer and it shows up properly.... (you just gotta "luv" windows )

Try installing htc sense from htc website even if running vanilla. It will install the driver properly. Then un-install sense and keep drivers. It's the only thing that worked for me.
Sent from my HTC Vision using XDA App

Related

After Froyo - Can't get back into ADB

I managed to get my Froyo on and still keep root.
However, when in debug mode, my computer will not recognize/install driver for the X. I've uninstalled and re-installed the drivers a couple of times, and even tried to manually force it to see the Moto Composite ADB interface.
If I turn off debug, the drivers load just fine (but of course no ADB that way).
I'm on Win7 x64.
Any suggestions?
-Z
Zaphod-Beeblebrox said:
I managed to get my Froyo on and still keep root.
However, when in debug mode, my computer will not recognize/install driver for the X. I've uninstalled and re-installed the drivers a couple of times, and even tried to manually force it to see the Moto Composite ADB interface.
If I turn off debug, the drivers load just fine (but of course no ADB that way).
I'm on Win7 x64.
Any suggestions?
-Z
Click to expand...
Click to collapse
Hello,
If you put your phone into mass storage mode without development mode you will get a cdrom with motoconnect setup. Run that and fully install and then unplug out into dev and change to pc mode. Adb is all yours.
-tony
anthonygill13 said:
Hello,
If you put your phone into mass storage mode without development mode you will get a cdrom with motoconnect setup. Run that and fully install and then unplug out into dev and change to pc mode. Adb is all yours.
-tony
Click to expand...
Click to collapse
I honestly didn't expect this to work, but since I didn't have any better ideas, I might as well try it. Man was I wrong.
The reason I did not think this would work is that I had downloaded the Moto Drivers (just the drivers, not the full MotoConnect software) from the Moto website. I did not expect there to be any difference.
Evidently the software on the phone does have more drivers than the downloadable package from Moto.
Thanks for the help.
I've tried doing this...turning off Dev mode, and turning on USB Mass Storage mode, but still no motoconnect setup screen comes up. Any other way to get those drivers installed?
anthonygill13 said:
Hello,
If you put your phone into mass storage mode without development mode you will get a cdrom with motoconnect setup. Run that and fully install and then unplug out into dev and change to pc mode. Adb is all yours.
-tony
Click to expand...
Click to collapse
Like Zaphod, I very much appreciate the help and did not expect this to work lol. Thanks much.
Yesterday at work I couldn't get into adb either because the devices drivers no longer loaded. I had to edit the driver inf file. It seems like the usb diver id changed.I'm on my phoebe right now and works rcd wasn't working anyway. You can get the new id if you open up device manager sand open the properties for the phone.the last tab has device details and the first or second has the new id. Just add that in the inf. Should look like the other entries. Just try adding rfd drivers with that new inf.
media sync mode gets you adb.
might say driver not installed when you click on it but adb will startup and work properly.
least on mine it does. win7 64bit
anthonygill13 said:
Hello,
If you put your phone into mass storage mode without development mode you will get a cdrom with motoconnect setup. Run that and fully install and then unplug out into dev and change to pc mode. Adb is all yours.
-tony
Click to expand...
Click to collapse
while i got adb using the method i described above, this is still a nice find lol
i would of nvr saw this cause im always in debugging mode .
thanx for this
drewlamo1 said:
while i got adb using the method i described above, this is still a nice find lol
i would of nvr saw this cause im always in debugging mode .
thanx for this
Click to expand...
Click to collapse
cant get it to work, ive tried all the above? keep getting error: device not found
Zaphod-Beeblebrox said:
I managed to get my Froyo on and still keep root.
However, when in debug mode, my computer will not recognize/install driver for the X. I've uninstalled and re-installed the drivers a couple of times, and even tried to manually force it to see the Moto Composite ADB interface.
If I turn off debug, the drivers load just fine (but of course no ADB that way).
I'm on Win7 x64.
Any suggestions?
-Z
Click to expand...
Click to collapse
change from pc mode to media sync mode in the notification window
If turning on and off USB Debug mode doesn't work, then do this, it will almost certainly work:
http://alldroid.org/default.aspx?g=posts&m=7662#post7662
teenfaces said:
change from pc mode to media sync mode in the notification window
Click to expand...
Click to collapse
Exactly as this is the fastest and simplest way to fix it. I freaked about about a week ago when my X would not work threw ADB anymore and that is the trick that took care of it. And it is proven to work it has been posted hundreds of times on many other site/forums.

[Q] Windows ADB USB drivers?

After enabling USB debugging on my Nexus 7, I still can't get "adb devices" to list my Nexus 7. I also tried switching its USB connection type from "media" to "camera", to no effect. I have Windows 7; I see a "Nexus" device under Other Devices in my device manager, but when I try to install the Google USB drivers from the Android SDK, Windows refuses to take it.
This is going to make development difficult Anyone know where I can find working USB drivers for Windows 7?
beandog said:
After enabling USB debugging on my Nexus 7, I still can't get "adb devices" to list my Nexus 7. I also tried switching its USB connection type from "media" to "camera", to no effect. I have Windows 7; I see a "Nexus" device under Other Devices in my device manager, but when I try to install the Google USB drivers from the Android SDK, Windows refuses to take it.
This is going to make development difficult Anyone know where I can find working USB drivers for Windows 7?
Click to expand...
Click to collapse
If you have updated the drivers from the SDK, then your problem is probably coming from the cable.
PS: Try not to use an extension cable
When I have had this problem in the past I have found that installing PDA net solves it.
Sent from my Galaxy Nexus using Tapatalk 2
download a sync software,for example,chinese use 360 mobile assistant,it will help you to connected with PC
Sent from my SHW-M190S using xda premium
i got the problem too,just install 360 mobile assistant ,it worked.but i dont know ,any mobile assistant
used in your city?
Sent from my SHW-M190S using xda premium
You may try to use device manager to solve the issue.:
Firstly please connect your Nexus 7 to you computer using the USB cable
included in the box.
Then on the tablet,
choose "Settings" -> "Storage" -> open the menu -> choose "USB computer connection" -> choose "MTP" or "PTP".
On your computer,
1. Control Panel -> Hardare and Sound -> View devices and printers
2. Click on Nexus.
3. Click on "Hardware" tab
4. Click on "Properties"
5. Click on "Change settings"
6. Click on "Driver" tab
7. Click on "Update drivers".
I'd suggest that you repeat these steps for both "MTP" and "PTP" connection types mentioned above.
Then on your computer, run "adb devices", the Nexus 7 would be listed in the
output of the adb command.
Enjoy.
Works with PTP mode - MTP mode doesn't
just for future reference...
By default it uses the MTP mode for USB. ADB is not working in this mode, even after i follow all the steps in above post.
Change it to use PTP (Camera mode), and ADB works !! go figure.
driving me crazy too.
First, windows did not recognize the thing in AdB mode. I managed to get around that with PDA net. But in cmd mode running "fastboot oem unlock" it just sits there saying "waiting for device". Also switched to both usb modes under "storage" as well as tried all usb ports on my pc (running Win 7 64bit). Using original cable.
Any other clues on what to do next?
bytecollektr said:
driving me crazy too.
First, windows did not recognize the thing in AdB mode. I managed to get around that with PDA net. But in cmd mode running "fastboot oem unlock" it just sits there saying "waiting for device". Also switched to both usb modes under "storage" as well as tried all usb ports on my pc (running Win 7 64bit). Using original cable.
Any other clues on what to do next?
Click to expand...
Click to collapse
ADB and fastboot may have two different drivers, this is the case with most other devices.
Anywho here's a link to the all inclusive driver bundle. Drivers was one of the reasons I only use a linux distro these days.
Unlawful said:
ADB and fastboot have two different drivers.
Anywho here's a link to the all inclusive driver bundle. Drivers was one of the reasons I only use a linux distro these days.
Click to expand...
Click to collapse
Still nothing. Deleted the drivers, and it obviously installed the new ones, since the name under the "device manager" changed. I go to the Android sdk and it still says waiting for device. Is there different versions of fastboot? Maybe its the wrong command? (fastboot oem unlock)
reddweb said:
just for future reference...
By default it uses the MTP mode for USB. ADB is not working in this mode, even after i follow all the steps in above post.
Change it to use PTP (Camera mode), and ADB works !! go figure.
Click to expand...
Click to collapse
This is how i got my ADB drivers to actuallly work right!! listen to this guy.
Nexcellent said:
This is how i got my ADB drivers to actuallly work right!! listen to this guy.
Click to expand...
Click to collapse
I have it in that mode, and it does not do anything, even with the new drivers.
bytecollektr said:
I have it in that mode, and it does not do anything, even with the new drivers.
Click to expand...
Click to collapse
Oh and fastboot is not available during normal operations and it has to be booted into the bootloader to use fastboot. Try using adb reboot bootloader and then when it restarts fastboot oem unlock.
I'm in the exact same situation
I'm having the same problem. I'm not exactly sure how to use the Naked Drivers pack. Can someone advise?
Easy as ADB...
Use the step by step instructions in the Nexus Root Toolkit found here;
http://forum.xda-developers.com/showthread.php?t=1766475
Hope that helps,
-CC
Set it to ptp mode, install updated sdk, and you will find proper adb driver in extras/google/usb-driver directory. After those steps adb started to work in my case' no need for third party downloads.
Sent from my Nexus 7 using xda app-developers app
I've been having the same issues with all of the new android devices I've tried to use adb on my computer for. I as able to make them work by manually installing the drivers in device manager. When you choose browse for drivers manually you can look through pre installed drivers and select adb interface and manually choose the drivers for adb and fast boot. Only issue I have is that it won't give adb root access and says rot is not available in production builds. Not sue if that's related or not.
Sent from my Nexus 7 using xda app-developers app
Windows 7 - Nexus 7 ADB Recognition
For me, like others, choosing either MTP or PTP from the Nexus 7's USB computer connection options didn't solve the issue. Updated to the latest version of the Android SDK Tools within Eclipse [version 20.0.1], and even uninstalled and re-installed the Google USB Driver [Revision 6] within the Android SDK manager, but no luck.
What ended up clearing the issue for me was to go to Computer Management, find the Nexus device with the question mark next to it, update the driver by browsing a location on the computer, browse to the location on your computer where you saved the Android SDK [the one with the following directories: add-ons, docs, extras, platforms, platform-tools, etc], and choose that very folder containing those folders I mentioned. It should search for a while then ask you whether or not to install some Asus/Google driver.
After installing that driver, my N7 was recognized by the "adb devices" command.
NOTE: Turns out when I updated the driver, my N7 was in PTP mode, and when I switched it to MTP mode, it was no longer recognized under adb devices. adb kill-server then adb start-server should get it recognized again when you switch between MTP and PTP.
Hope this works for all of you out there, like me, who really didn't want to take the 3rd party software route to overcome this problem.
Cheers.
ADB driver
Try to root toolkit from Wugfresh
http://forum.xda-developers.com/showthread.php?t=1766475
There is a very complete and usable guide to install ADB driver for most version of windows (XP->win 7).
You don't have to unlock or root; just use the interactive guide for driver install.
Good luck
bytecollektr said:
Still nothing. Deleted the drivers, and it obviously installed the new ones, since the name under the "device manager" changed. I go to the Android sdk and it still says waiting for device. Is there different versions of fastboot? Maybe its the wrong command? (fastboot oem unlock)
Click to expand...
Click to collapse
rootblock said:
For me, like others, choosing either MTP or PTP from the Nexus 7's USB computer connection options didn't solve the issue. Updated to the latest version of the Android SDK Tools within Eclipse [version 20.0.1], and even uninstalled and re-installed the Google USB Driver [Revision 6] within the Android SDK manager, but no luck.
What ended up clearing the issue for me was to go to Computer Management, find the Nexus device with the question mark next to it, update the driver by browsing a location on the computer, browse to the location on your computer where you saved the Android SDK [the one with the following directories: add-ons, docs, extras, platforms, platform-tools, etc], and choose that very folder containing those folders I mentioned. It should search for a while then ask you whether or not to install some Asus/Google driver.
After installing that driver, my N7 was recognized by the "adb devices" command.
NOTE: Turns out when I updated the driver, my N7 was in PTP mode, and when I switched it to MTP mode, it was no longer recognized under adb devices. adb kill-server then adb start-server should get it recognized again when you switch between MTP and PTP.
Hope this works for all of you out there, like me, who really didn't want to take the 3rd party software route to overcome this problem.
Cheers.
Click to expand...
Click to collapse
i'm having the issue with the mtp not being recognized in adb. can you be more specific in the adb kill-server and adb start-server.

Nexus 4 ADB Connection

I am trying to connect my Nexus 4 to my PC and use the ADB commands. I have the following problems:
ADB driver is installed and "USB Debugging" turned on the Nexus 4. Device shows up on Device Manager, however "adb devices" does not list the device and unable to communicate with the attached device.
The Nexus drive, regardless of MTP or PTP disappears from Windows Explorer when "USB Debugging" is turned on, Turning off "USB Debugging" brings back the drive.
USBView shows the device with a RED light, but it appears working on Device Manager.
I do not have this problem with my other laptop and desktop.
Using Windows 7 x64 Ultimate and Nexus 4 - Stock 4.2.2
Any help would be appreciated. Thanks.
akashi said:
I am trying to connect my Nexus 4 to my PC and use the ADB commands. I have the following problems:
ADB driver is installed and "USB Debugging" turned on the Nexus 4. Device shows up on Device Manager, however "adb devices" does not list the device and unable to communicate with the attached device.
The Nexus drive, regardless of MTP or PTP disappears from Windows Explorer when "USB Debugging" is turned on, Turning off "USB Debugging" brings back the drive.
USBView shows the device with a RED light, but it appears working on Device Manager.
I do not have this problem with my other laptop and desktop.
Using Windows 7 x64 Ultimate and Nexus 4 - Stock 4.2.2
Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
I had sort of the same problem, try uninstalling the driver in device manager, then unplug and replug your USB. Then when you plugged in the USB go to device manager and right click on the device and click scan for hardware changes. See if that works.
I'm not sure if this is a problem caused by windows update or the new updated SDK, but it has been a big problem for me.
heat361 said:
I had sort of the same problem, try uninstalling the driver in device manager, then unplug and replug your USB. Then when you plugged in the USB go to device manager and right click on the device and click scan for hardware changes. See if that works.
I'm not sure if this is a problem caused by windows update or the new updated SDK, but it has been a big problem for me.
Click to expand...
Click to collapse
Thanks for the quick reply.
I tried your suggestion but it did not solve the problem. After re-plugging the USB, Windows listed the device as "Nexus 4" and did not find any drivers for it. I manually installed the Naked Drivers (proven to work on my laptop and desktop) but still facing the same problem
I really do not want to reinstall Windows!
Thanks.
akashi said:
Thanks for the quick reply.
I tried your suggestion but it did not solve the problem. After re-plugging the USB, Windows listed the device as "Nexus 4" and did not find any drivers for it. I manually installed the Naked Drivers (proven to work on my laptop and desktop) but still facing the same problem
I really do not want to reinstall Windows!
Thanks.
Click to expand...
Click to collapse
OK try right clicking on the the device in device manager and choose update driver, then Browse my computer, then let me pick From a list of devices. After choose have disk on and find the file where your USB drivers are and click next. It may prompt you that windows can't verify the publisher Just click install this driver software anyway.
See if this works.
heat361 said:
OK try right clicking on the the device in device manager and choose update driver, then Browse my computer, then let me pick From a list of devices. After choose have disk on and find the file where your USB drivers are and click next. It may prompt you that windows can't verify the publisher Just click install this driver software anyway.
See if this works.
Click to expand...
Click to collapse
I have tried installing the drivers from the latest SDK and also the "Naked Drivers" found here: http://forum.xda-developers.com/showthread.php?t=1996051
Still have the problem.
akashi said:
I have tried installing the drivers from the latest SDK and also the "Naked Drivers" found here: http://forum.xda-developers.com/showthread.php?t=1996051
Still have the problem.
Click to expand...
Click to collapse
Try pointing the path to the Google drivers in the android-sdk in device manager and not the naked drivers.
akashi said:
I have tried installing the drivers from the latest SDK and also the "Naked Drivers" found here: http://forum.xda-developers.com/showthread.php?t=1996051
Still have the problem.
Click to expand...
Click to collapse
This is what I did and waited for the PC to install the adb drivers.
I plugged the phone in and with the USB plugged in turned it off while holding the volume up and down keys. This made my nexus 4 go into download mode and the PC automatically installed the adb drivers. After I just unplugged and held the power button to restart the device hope this helped.
Sent from my Nexus 4 using xda premium
akashi said:
Thanks for the quick reply.
I tried your suggestion but it did not solve the problem. After re-plugging the USB, Windows listed the device as "Nexus 4" and did not find any drivers for it. I manually installed the Naked Drivers (proven to work on my laptop and desktop) but still facing the same problem
Thanks.
Click to expand...
Click to collapse
When you uninstalled what's there now, you did make sure to check the box that will remove the old drivers from your PC?
Just in case, HERE is another source for the drivers.
dinhume echoes
Thanks to everyone for their help.
Just to confirm I have already tried:
Uninstalling the ADB driver via Device Manager and selecting "Delete the driver software for this device" and rebooting.
After reboot, Windows could not locate any drivers and I manually selected the drivers found inside the SDK (08/27/2012,7.0.0000)
The device shows up on Device Manager as working but does not work with adb commands. However, fastboot commands work!
I tried the above with the Naked Driver and had the exact result.
If I boot into the bootloader, I am able to run fastboot commands perfectly!
I have already ruled out my USB port as it works perfectly on VMware.
I am thinking my Windows 7 is messed up somehow and re-installation is looking like the only solution :crying:
akashi said:
Thanks to everyone for their help.
Just to confirm I have already tried:
Uninstalling the ADB driver via Device Manager and selecting "Delete the driver software for this device" and rebooting.
After reboot, Windows could not locate any drivers and I manually selected the drivers found inside the SDK (08/27/2012,7.0.0000)
The device shows up on Device Manager as working but does not work with adb commands. However, fastboot commands work!
I tried the above with the Naked Driver and had the exact result.
If I boot into the bootloader, I am able to run fastboot commands perfectly!
I have already ruled out my USB port as it works perfectly on VMware.
I am thinking my Windows 7 is messed up somehow and re-installation is looking like the only solution :crying:
Click to expand...
Click to collapse
4.2.2 requires updated adb and fastboot. It looks like you have an older version.
Click on the ota help desk link in my signature. The new version is attached to the first post. Replace the old adb and fastboot files with the new ones. Then try again.
Sent from my Nexus 4 using xda premium
El Daddy said:
4.2.2 requires updated adb and fastboot. It looks like you have an older version.
Click on the ota help desk link in my signature. The new version is attached to the first post. Replace the old adb and fastboot files with the new ones. Then try again.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thanks. I tried version 16.01 and still have this problem.
The problem is whenever I uninstall/install the ADB driver or disconnect/reconnect the USB, **ONLY** the "Nexus 4" appears on the Device Manager which I manually install the ADB drivers to. There is not a second "Nexus 4" on the Device Manager for the MTP or PTP.
On my laptop when I remove all drivers and reconnect the USB cable, I always see 2 "Nexus 4" listed on Device Manager. One for the ADB interface and the other for the MTP or PTP.
Please help!
Any ideas please?
Any Solution to ADB connection problems?
Hi was there any solution to this, as I seem to have the same issue.
I have tried different drivers and MTP & PPP modes as well as loading the PDAnet drivers and software.
Each time now I take care to remove all the drivers and also delete the drivers in all modes (Android running and Bootloader running)!
MTP & PPP load different copies of the drivers.
I can get either "Nexus 4" showing up in the device driver or "Google ADB Interface" or Android ADB interface" according to the driver loaded.
I can see the device when Android is running ie "ABD Devices" gives me the serial number and connected, then I can send an ADB command "adb Reboot-bootloader" the Nexus then reboots into the bootloader screen, the device driver changes to the bootloader driver (installs if not installed) however then I loose connection to the Nexus phone! "ADB Devices" returns none connected.:fingers-crossed:
I also tried unplugging and plugging back in the phone in bootloader mode but do not get adb to see the handset or it to react to commands.
I'm just about ready to try a toolkit to see if I can get past this roadblock!!!
Current computer is Win7-x64
This weekend I will try on a different computer.....Win8-X64
All comments appreciated
That's because you cant use adb when in boot loader. You use fastboot
Sent from my Nexus 4 using xda app-developers app
I have same problem on my work laptop DELL when my custom desktop machine works just fine with both Nexus 4 and 7. :/

[Q] ADB not working in MTP mode

I'm wondering if anyone has run into this. ADB works fine if I have my phone connected and set to PTP. But if it is set to MTP, adb devices returns nothing connected. MTP itself still works fine to copy files over, and device manager shows the Android ADB device. It's not a huge issue to need to switch it, but it would be nice if there was a simple fix.
raptir said:
I'm wondering if anyone has run into this. ADB works fine if I have my phone connected and set to PTP. But if it is set to MTP, adb devices returns nothing connected. MTP itself still works fine to copy files over, and device manager shows the Android ADB device. It's not a huge issue to need to switch it, but it would be nice if there was a simple fix.
Click to expand...
Click to collapse
3 possible steps:
i) update SDK manager on your computer
ii) check USB debugging is..... well......checked in the phone settings
iii) update the drivers ( SDK manager or Google platform)
Another possibility is to ask your question in the window "search this forum of this thread.
Good luck
raptir said:
I'm wondering if anyone has run into this. ADB works fine if I have my phone connected and set to PTP. But if it is set to MTP, adb devices returns nothing connected. MTP itself still works fine to copy files over, and device manager shows the Android ADB device. It's not a huge issue to need to switch it, but it would be nice if there was a simple fix.
Click to expand...
Click to collapse
Hmm, it works fine for both of mine. I'd say try to uninstall and delete your ADB drivers, and reinstall them. Follow this thread
gunner1937 said:
3 possible steps:
i) update SDK manager on your computer
ii) check USB debugging is..... well......checked in the phone settings
iii) update the drivers ( SDK manager or Google platform)
Another possibility is to ask your question in the window "search this forum of this thread.
Good luck
Click to expand...
Click to collapse
Hey, while your reply was very informative and useful, you did not read his post properly. ADB works for him only in PTP mode. MTP doesn't work.
exb0 said:
Hmm, it works fine for both of mine. I'd say try to uninstall and delete your ADB drivers, and reinstall them. Follow this thread
Hey, while your reply was very informative and useful, you did not read his post properly. ADB works for him only in PTP mode. MTP doesn't work.
Click to expand...
Click to collapse
As surprising as it might be I did read the post.
My answer is based on my own experience. The Nexus 7 was seen in PTP mode but not in MTP.
To address the issue, after a thorough reading in the XDA forum and thanks to the knowledge of our Forum members, I updated the SDK manager and re-install the drivers.
Hope I answer your concern.
gunner1937 said:
As surprising as it might be I did read the post.
My answer is based on my own experience. The Nexus 7 was seen in PTP mode but not in MTP.
To address the issue, after a thorough reading in the XDA forum and thanks to the knowledge of our Forum members, I updated the SDK manager and re-install the drivers.
Hope I answer your concern.
Click to expand...
Click to collapse
Ah, my mistake. I'm sorry!
I did try searching but most of the posts I found were eith er than MTP was not working at all or ADB was not working at all.
I have uninstalled and reinstalled the ADB driver, but I will try completely removing the SDK next.
gunner1937 said:
As surprising as it might be I did read the post.
My answer is based on my own experience. The Nexus 7 was seen in PTP mode but not in MTP.
To address the issue, after a thorough reading in the XDA forum and thanks to the knowledge of our Forum members, I updated the SDK manager and re-install the drivers.
Hope I answer your concern.
Click to expand...
Click to collapse
This is 99% a driver issue.
I had a similar experience when first setting up my n4.
Debugging on = adb but no mtp
Debugging off = not and obviously no adb
I uninstalled the adb drivers where possible.
Plugged in with mtp mode on and debugging off
Let it automatically install mtp drivers
Switch debugging on
Wait for it to install what it can by itself then manually install the adb driver
Results in fully functional adb & mtp
Sent from my Nexus 4 using xda app-developers app
Well, uninstalling the SDK did not work. I was able to get it working. After uninstalling the ADB drivers and plugging the device back in I saw that the device was still showing up as the ADB interface. I repeated the process a few times and it eventually stopped appearing. After that I reinstalled the driver and everything seems to be working.
i have the same problem
everything works, including PTP, but MTP refuses to work
ther's no error, no missing driver, it just don't appear
i have tried a lot of reinstall and removals

Oneplus 5 ADB

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

Categories

Resources