nexus 10 usb connection issues - Nexus 10 Q&A, Help & Troubleshooting

yes i have sdk and google driver and checked my usb cable and deleted all instances in usbdev and usb deg enabled.
when plugged into pc pc says mtp found and nexus notification bar first says connected as a media device then usb debugging enabled.
hardware manager shows adb interface but will not update driver.
what simple thing am i missing

After downloading the SDK did you also download the adb and fastboot binaries? As far as I know simply downloading the SDK won't auto give you these.
Also it sounds like you using windows, did you add the path to environmental vrialbles or are you running cmd in the location you have adb downloaded too?
Sent from my Nexus 4 using XDA Premium 4 mobile app

Install universal adb ans mais fpdeleting former entries. Of USB. Try wug's tooltik would help you there is a step by step instruction

Related

[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.

[Q] Nexus 4 ADB on Windows 7 Home

After several hours of frustration, I'm just going to ask.
I have USB debugging enabled. When I plug in the Nexus 4 Windows auto installs drivers for MTP.
It's listed under portable devices in device manager. I am trying to uninstall the driver and install the Naked driver. But as soon as I uninstall in device manager, Windows reinstalls, despite me having turned off auto-installation of drivers. I am not able to use the advanced method listed here http://www.addictivetips.com/window...utomatic-driver-installation-in-windows-vista because gpedit.msc doesn't exist for Home users.
I have unplugged the device and manually put it into Fastboot and plugged it in. Windows does not try to autoinstall drivers. I am able to install Naked drivers and the device appears as "Android Phone" in device manager.
How can I proceed?
Donteventrii said:
After several hours of frustration, I'm just going to ask.
I have USB debugging enabled. When I plug in the Nexus 4 Windows auto installs drivers for MTP.
It's listed under portable devices in device manager. I am trying to uninstall the driver and install the Naked driver. But as soon as I uninstall in device manager, Windows reinstalls, despite me having turned off auto-installation of drivers. I am not able to use the advanced method listed here http://www.addictivetips.com/window...utomatic-driver-installation-in-windows-vista because gpedit.msc doesn't exist for Home users.
I have unplugged the device and manually put it into Fastboot and plugged it in. Windows does not try to autoinstall drivers. I am able to install Naked drivers and the device appears as "Android Phone" in device manager.
How can I proceed?
Click to expand...
Click to collapse
Try checking the drivers thread link in my signature.
Stryder5 said:
Try checking the drivers thread link in my signature.
Click to expand...
Click to collapse
The problem is that Windows is auto-installing the driver as soon as I uninstall it from device manager. I have this setting disabled in Device Installation Settings but nevertheless it continues auto-installing.
Donteventrii said:
The problem is that Windows is auto-installing the driver as soon as I uninstall it from device manager. I have this setting disabled in Device Installation Settings but nevertheless it continues auto-installing.
Click to expand...
Click to collapse
When you plug in your n4 in your pc, does it allow you to open the folder for your phone. If it does the drivers are installed. Mine n4 did the same as you when I plugged it in my PC, and did show Android in the device manager.
Use the nexus 4 toolkit to do it.
http://forum.xda-developers.com/showthread.php?t=1995688
jt.61 said:
When you plug in your n4 in your pc, does it allow you to open the folder for your phone. If it does the drivers are installed. Mine n4 did the same as you when I plugged it in my PC, and did show Android in the device manager.
Click to expand...
Click to collapse
It's showing up as portable device, not as Android when MTP is connected. If I manually boot into fastboot, and connect to PC it will show as Android.
Nexus 4 toolkit doesn't work. When I connect the device, it still only shows up as MTP device connected.
How can I stop the "Nexus 4" driver from auto installing the MTP driver?
Nobody else is having this problem?
Sent from my Nexus 4 using Tapatalk 2
Donteventrii said:
Nobody else is having this problem?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Bump
For the love of bump
...
Sent from my Nexus 4 using Tapatalk 2
You could try this installer. If a prompt ever says not to install a driver just do it anyway.
http://www.junefabrics.com/android/download.php
I was having the same issues, toolkit didnt work, auto kept auto installing MTP only, junefabrics.com didn't work by itself, LG drivers didn't work. finally I tried the drivers in sig and adb was installed but the tool kit still didn't recognize it. I ran the one from junefabrics.com after that and hit no to not reinstall the drivers when it asks, but it's hanging when installing pdanet on my phone.
TCMan5190 said:
I was having the same issues, toolkit didnt work, auto kept auto installing MTP only, junefabrics.com didn't work by itself, LG drivers didn't work. finally I tried the drivers in sig and adb was installed but the tool kit still didn't recognize it. I ran the one from junefabrics.com after that and hit no to not reinstall the drivers when it asks, but it's hanging when installing pdanet on my phone.
Click to expand...
Click to collapse
im in the same boat
I'm having these same issues. Very frustrating.
Just fixed the problem by following the directions in this post - http://forum.xda-developers.com/showpost.php?p=34154052&postcount=7
His instructions about cmd prompt didn't work for me, so in device manager I selected View -> Show Hidden Devices.
I removed all android, nexus, other android phones and then reinstalled the drivers via the toolkit. Seems to be working so far!
The MTP driver will always install as that's nothing to do with adb. If you open Device Manager it should have the other option - you then manually install the driver by browsing the the drivers folder when using the 'Update driver' option in the right-click menu when you click on it in Device Manager
BUMP
Donteventrii said:
...
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I am having the same problem my windows xp is not reading I install a couple of different drivers still nothing. This the only phone/tablet I am having this issu that my pc is it's not reading the files of my phone.
OTA JOP40D
2nd Batch phone
hello, now nexus 4 updated to 4.2.2 and when i connect to computer the device could not be found
i updated SDK , all the required things inside android 4.2 but still device not found
is there drivers that i can install instead of checking for updates and so on?
jasonmiracle said:
hello, now nexus 4 updated to 4.2.2 and when i connect to computer the device could not be found
i updated SDK , all the required things inside android 4.2 but still device not found
is there drivers that i can install instead of checking for updates and so on?
Click to expand...
Click to collapse
Try downloading pdanet on your pc or downliad a nexys4 toolkit from here and they let u install the drivers
Sent from my Nexus 4 using xda premium
casonswag said:
Try downloading pdanet on your pc or downliad a nexys4 toolkit from here and they let u install the drivers
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
tried pda but failed
its caused by the android 4.2.2 update...
For anyone still having problems, these are the steps I followed that fixed it for me. (After updating to the latest sdk version and downloading the google usb driver)
1. Uninstalled the driver from Device Manager
2. Let it automatically install the generic 'MTP device driver'
3. Right clicked on the new device and selected 'Update Driver'
4. Selected 'Have Disk' and pointed it to [android-sdk-dir]\extras\google
5. Watched an 'ADB' driver install.
6. Opened Eclipse to successfully run on my N4.

[Q] Nexus 4 usb file transfer

Hi,
This is my first Nexus device (N4), I know they have an emulated SD card, so I expected to connect it to my Win 7 PC via USB, and for the SD card directory to be shown as a file system / drive in Windows. This doesn't happen.
Phone is in MTP mode, screen isn't locked. Am I missing something here, a driver perhaps, or does this functionality no longer exist?
Thanks,
Des
You should get a Nexus 4 device along with your drives, you open that, then go to 'internal storage'
If you're not getting that, then it's probably driver related.
If it doesn't detect by USB at all, you may have a faulty device like me.
If you plug your phone into the wall with the AC adapter, does it constantly say " charging (USB)" in the battery settings?
This defect means I cannot root or charge the phone properly... It sucks..
Sent from my Nexus 4 using Tapatalk 2
Most likely a driver issue. When I have use the adb driver I cannot see my device as a storage device. Switching to the default driver Windows installs lets me see it but adb no longer works.
I ended up just using AirDroid to do any file transfers.
There are a few reports of the stock charger being reported as USB charging actually, so it might not be all bad.
The phone might be in MTP mode, but has it installed the MTP driver ? Check Device Manager.
On my own XP system, MTP wouldn't work for me until I turned off USB debugging.
Sent from my Nexus 4 using xda premium
steviewevie said:
The phone might be in MTP mode, but has it installed the MTP driver ? Check Device Manager.
On my own XP system, MTP wouldn't work for me until I turned off USB debugging.
Click to expand...
Click to collapse
^ This.
On XP, MTP does not work if USB Debugging is turned on. It may be the same for Windows 7 as well.
Same behavior on Windows 7, just fixed my issues. Thanks!
I got similar problem with my N4, yesterday I flashed Mahdi-ROM 2.4[1/02] then my USB stopped working. I can view files through PC, but cannot upload to phone. It says device has been disconnected, but it's still connected Turning off USB debuging didn't help.
I cannot even flash kernel uploaded through Airdroid, recovery gives error - cannot open zip file.
Edit: Nevermind, its PC problem. With other PC it works normal.
use universal naked drivers.
fastboot adb and mtp and ptp working.
efrant said:
^ This.
On XP, MTP does not work if USB Debugging is turned on. It may be the same for Windows 7 as well.
Click to expand...
Click to collapse
After I rooted my N4 a few months ago same thing, cannot get MTP on WinXP
Works fine on my Win7 machines though, its pretty annoying
Tried ALL the fixes I could find, no go
Uninstal all drivers, reconnect N4 let Windows install drivers, it will probably be adb device drivers, then select in device manager adb device drivers update drivers and check install from specific location and on next screen check don't search!
Then you could be able to select mtp. All of this should be done with USB debugging turned off and USB connection as mtp!
Sent from my Nexus 4 using Tapatalk
Nexus 4
zvecka said:
Uninstal all drivers, reconnect N4 let Windows install drivers, it will probably be adb device drivers, then select in device manager adb device drivers update drivers and check install from specific location and on next screen check don't search!
Then you could be able to select mtp. All of this should be done with USB debugging turned off and USB connection as mtp!
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Hey Buudy thanks this helps me

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. :/

How to get USB Debugging mod to work?

I have a nexus 7 2012 and i am trying to install 4.3. Of course since i have rooted it and have twrp on it i cant just ota update, so i tried plugging it up to my computer. Right now everytime i plug in the device and use it as a media device it works until i turn on developer mode and enable usb debugging. As soon as i turn on debugging the device disconnects at the bottom right showing my N7 (on windows 7), and whenever i look in my computer its not there also. The only way i can find it in this mode is in device manager in which it says "android phone". I figured maybe i have a driver problem, but if you look for drivers and try to install it says it already has them.
So does anybody know how to get it to work so i can reset it?
Delete the current drivers than manually choose the n7 drivers you downloaded from xda.
Or use a free program called usbdeview for windows to seek out all drivers associated with a device to make sure you uninstalled them correctly. Also I highly recommend dual booting a Linux distro which is much less finicky than windows when using android
Best of puck
Sent from my Nexus 7 using Tapatalk 2
demkantor said:
Delete the current drivers than manually choose the n7 drivers you downloaded from xda.
Or use a free program called usbdeview for windows to seek out all drivers associated with a device to make sure you uninstalled them correctly. Also I highly recommend dual booting a Linux distro which is much less finicky than windows when using android
Best of puck
Sent from my Nexus 7 using Tapatalk 2[/Q
Can you inform me on how to delete the current drivers?
when i connect with usb debugging mode turned on it connects as nexus 7 with a description as Android Composite ADB Interface. Also it is not recognized under the my computer setting at all. In usb deview it also has a purple dot all the way to the left beside the name instead of a green dot.
When i connect to the pc without usb debugging on the computer recognizes it as nexus 7 \ media device and i can use it as storage back and forth and in usb deview it has a green dot beside the name
Click to expand...
Click to collapse

Categories

Resources