[Q] Turning USB Debugging on while Nexus connected to Toolkit/ PC, safe? - Nexus 10 Q&A, Help & Troubleshooting

Hi,
Was just wondering. When I had my Nexus 10 connected to the PC and wanted to make a backup with the toolkit I didn't see any serial number below "adb devices" even though I had the adb drivers installed . So i went on and activated USB debugging in the developer options while being in the main menu of the toolkit . The PC told me then that new drivers where installed.
So i started thinking : is it safe for the device / the internal storage to activate USB debugging just like that while it is connected to the PC and while being in the toolkit main menu?
Thanks for your help!

Maxey said:
Hi,
Was just wondering. When I had my Nexus 10 connected to the PC and wanted to make a backup with the toolkit I didn't see any serial number below "adb devices" even though I had the adb drivers installed . So i went on and activated USB debugging in the developer options while being in the main menu of the toolkit . The PC told me then that new drivers where installed.
So i started thinking : is it safe for the device / the internal storage to activate USB debugging just like that while it is connected to the PC and while being in the toolkit main menu?
Thanks for your help!
Click to expand...
Click to collapse
The toolkit itself doesn't keep a connection to your device so it shouldn't damage anything or be unsafe.
It just execute various ADB commands through it's interface.
Beamed from my CM10.1 Galaxy Nexus

Herman76 said:
The toolkit itself doesn't keep a connection to your device so it shouldn't damage anything or be unsafe.
It just execute various ADB commands through it's interface.
Beamed from my CM10.1 Galaxy Nexus
Click to expand...
Click to collapse
Thank you, that's kind of good to hear

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.

Not connecting in Windows 7

Windows cant find a driver for the phone, how do you use this on Windows?
You can install the drivers as part of the Android SDK, or you could search this forum for drivers, or you could goto the Development section and download mskip's Galaxy Nexus 4 Toolkit and install the drivers from there.
uberNoobZA said:
You can install the drivers as part of the Android SDK, or you could search this forum for drivers, or you could goto the Development section and download mskip's Galaxy Nexus 4 Toolkit and install the drivers from there.
Click to expand...
Click to collapse
installed the drivers and Windows sees it as an Android ADB device but it doesnt mount anything. How do I transfer files over USB?
I extracted the drivers from the Android SDK and posted it up. Check my sig for the link.
tried those too and its still not mounting anything
Windows 7 detected my phone without any drivers installed and I was able to mount the internal storage. The only thing the sdk drivers allow for are adb and fastboot interfacing, so they shouldn't be needed if all you are trying to do is mount the device.
try different usb port my pc did that at first.
I'm not sure why, but it worked for me on windows 7 and automatically updated the drivers. The weird thing is that adb recognizes the nexus 4 as a Samsung phone
idividebyzero said:
Windows cant find a driver for the phone, how do you use this on Windows?
Click to expand...
Click to collapse
Same issue here until I switched to the cable that came with the phone and it worked. Maybe just a fluke, not sure.
Sent from my Nexus 4 using xda app-developers app
idividebyzero said:
tried those too and its still not mounting anything
Click to expand...
Click to collapse
Sorry, misread your post. Try restarting, try a different USB port, try a different cable. Also, make sure MTP mode is enabled on your phone (Settings > Storage > Menu > then check Media Device).
idividebyzero said:
installed the drivers and Windows sees it as an Android ADB device but it doesnt mount anything. How do I transfer files over USB?
Click to expand...
Click to collapse
Have you found a solution yet? To transfer files from my PC to the phone, I have to make sure debugging is turned off and connect with MTP mode. But if I want to use ADB, I need to turn debugging on which loses the PC's ability to see the phone at all unless I connect in PTP mode. All a bit weird but at least it works. Have you tried uninstalling and reinstalling the drivers?
Phone mounts fine on 2 different computers, its something with my computer.
Its not the USB cable, tried different ports, I tried USB debugging on and off, camera mode and MTP. Device manager sees it as a Nexus 4 but says the drivers didnt install.
So my next question is why isnt Windows installing the drivers properly?
i have got two nexus 4
and with one of them i am not able to connect it to my main computer (with a second computer it works).
With the other nexus 4 i have no problems on any computer...
os is alway win 7.
just linking and sharing a similar thread [Q]Computer won't recognize phone? which covers same/similar issue and resolution.

[Q] adb Mode/usb developing mode does not work

I'm using the Asus Google Nexus ToolKit V3.8.2 (donated version).
With my first N7 I was able to unlock and root.
Now I exchanged it against the N7 3G (HSPA+). I was able to unlock the device and able to install the bootloader 3.34. But root does not work. I think it is because ADB does not recognize the tablet.
What happens:
1.) the start screen of the ToolKit does not show the serial in the adb device list (If I restart the tablet in fastmode it list the serial in fastmode device list)
2.) if I start the Root and the ToolKit wants to reboot in Fastboot Mode it says "Waiting for adb Mode".
3.) If I restart on my own in Fastboot Mode and start the Root procedure then it reboots the device and says "Procedure will continue in 20 seconds Waiting for USB debugging to be enabled". It does not help to re-activate the usb debugging mode and it doesn't help to re-connect the usb cable.
4.) I started cmd and changed to the "Google Nexus 7 ToolKit" folder to call "adb-toolkit devices". But it does not show any device. adb-toolkit kill-server and start-server doesn't help. usb reconnect doesn't help.
P.S. As I'm a new member I'm not able to post inside the official support thread, sorry.
It could be a driver issue on the pc..
try this
download a pc app called usbdview . Do a google search to find it..
Run the program on the pc without the nexus plugged in. Delete all adb/ usb devices that you do not have physically plugged into your computer.
Plug in the nexus 7 refresh the list . Delete what ever comes up for the nexus 7..
Reboot the computer WITH the nexus not connected..
Install the NEXUS DRIVERS.. plug in the nexus and the computer should find the device as if its the first time used.
Try you tool kit again...
Sometimes when adb is started and stopped if there are several versions Windows can be confused and not stop the right driver but start a older version instead VERY Common windows usb issue. This works with any USB Trouble shooting for devices not just Android...
Good LUCK ..
It's pretty obvious that you need to install the correct drivers for the Nexus 7 HSPA+.
I'm not the lowest of the low, but I am the slowest of the slow.
exglynco said:
It's pretty obvious that you need to install the correct drivers for the Nexus 7 HSPA+.
I'm not the lowest of the low, but I am the slowest of the slow.
Click to expand...
Click to collapse
The nexus drives are a One driver for all Nexus Devices... This should only be a issue if there are multiple copies of usb adb in the windows registry . The usb drivers need to be removed then re installed or will just create more conflict. Usb Is NOT SO PLUG AND PLAY as it was intended.. Sometimes just plugging a usb device from one usb port to another in some computers can cause windows to install another copy of the driver. This is mostly on systems with a usb hub then a usb 2.o hub on a different port.. and so on.
I Use my notebook with several android devices . I often have issues with
erica_renee said:
It could be a driver issue on the pc..
Click to expand...
Click to collapse
This could it be. But I found a very simple solution:
stackoverflow.com/a/11991653/318765
When the Nexus 7 is plugged in there is a persistent notification that indicates "CONNECT AS / Media Device (MTP)". In this state adb devices will not show the Nexus, or undoubtedly any other device. Not exactly obvious, but if you select the second option "Camera (PTP)" the device is available for debugging (the lesson is ignore the camera, and focus on the protocol PTP).
This choice is persistent, and I'm guessing that with a band new device it will connect as MTP until told otherwise.
Click to expand...
Click to collapse

Nexus 4 cannot be recognized as MTP after root

I'm running Windows 7 64bit and followed the Ultimate guide to unlock and root my Nexus 4.
Everything went well but now it looks like that Windows won't recognize my phone as a device. When I plug in the phone, the auto-play window will pop out and recognize it as Nexus 4, but there is no other options. (Normally the auto-play will ask if open folder to view files or transfer photos). I can't see my phone in device manager either.
If I turn on the USB debugging mode, I can see it in device manager but still cannot see it in My Computer. Looks like Windows can't access the SD card at all.
I tried switching to the camera mode but the problem remained. Please help.
desperate bump. can anyone help?
Maybe it's a stupid advice, but have you tried change the USB port in PC?
glancer2315 said:
desperate bump. can anyone help?
Click to expand...
Click to collapse
Plug in the phone, uninstall the drivers from Device manager, then unplug, and replug.
Colourkey said:
Maybe it's a stupid advice, but have you tried change the USB port in PC?
Click to expand...
Click to collapse
yes, i did.
abaaaabbbb63 said:
Plug in the phone, uninstall the drivers from Device manager, then unplug, and replug.
Click to expand...
Click to collapse
thanks for your advice. the problem is that, without USB debugging mode on, I can't see Nexus 4 in Device manager, even though the Windows Auto-play will say Nexus 4 connected. (Nothing in My Computer either)
With USB debugging mode on, I uninstalled the driver and Windows would try installing the driver. Now it shows up as MTP device with an exclamation mark. I tried manually update the driver (direct it to the Google SDK folder and pick the android_windowsusb.inf) but it says it does not support x64. I don't think the 64 bit driver is digitally signed.
I think I had a similar problem as yours. If you deleted the drivers while on debugging mode and reconnected after and it's showing the exclamation mark of a unknown device, try restarting your computer and plugging your phone back in.
SovereigN7 said:
I think I had a similar problem as yours. If you deleted the drivers while on debugging mode and reconnected after and it's showing the exclamation mark of a unknown device, try restarting your computer and plugging your phone back in.
Click to expand...
Click to collapse
i did and it remains the same.
Is there anyway I can know all the files names of the drivers so that I can manually delete them from system folder? When I uninstalled it from the device manager, I don't see the option "Delete the driver software for this device".
I can still see it under "adb devices" list.
I think there are some conflicts in the drivers.
Now when I connect Nexus 4 (without USB debugging mode on), it will show up in device manager under Android Device.
With USB debugging, it will then show up under Portable Devices.
However, it's supposed to work the other way around. that is (no USB debugging --> portable device; with USB debugging --> Android Device).
How can i solve this?
Have you tried manually installing the drivers before plugging in the phone, vs letting windows choose the drivers it wants to install? One option you could try is installing PDA Net on your pc. It will install reliable drivers on your pc.
i also had this same problem after flashing my first custom rom on the n4, and i also run windows 7 Ultimate x64
here is the process i use for full clean installation of device
on phone
goto SETTINGS > STORAGE > (menu) USB Computer Connection
make sure Media Device (MTP) is checked
With USB Debugging On
On your PC go to device manager
there should be 2 devices (Android Phone > Android Composite ADB Interface & Portable Devices > Nexus 4) - this is on a fully working n4 so you might only have 1 of them
Right click on each of them and click uninstall
The popup box should have another check box to delete the driver also, if this is available check it then confirm (note mine only has the box for Android Phone > Android Composite ADB Interface, but if yours has it on both then check it on both)
your computer will now ask you to restart, dont do it yet
repeat previous step for the other device if you have 2 then reboot
upon rebooting it will automatically start reinstalling drivers
by expanding the selection you should see 2 devices
Nexus 4 - Successful - Ready To Use (this is your MTP connection)
Nexus 4 - Unsuccessful - No Driver Found (this is your ADB Connection)
at this point you should be able to access internal storage however ADB will not work
go back into device manager
you should now have
Portable Devices > Nexus 4
and Other Devices > Nexus 4 (with yellow exclamation mark)
right click on the Other Devices > Nexus 4 (with yellow exclamation mark)
hit Update Driver Software
click Browse my computer for driver software
click Let Me Pick Drom a List of Device Drivers On My Computer
double click Show All Devices
click Have Disk...
click Browse
navigate to the download directory for the google usb drivers (for me this was "C:\Program Files (x86)\Android\Android-SDK\Extras\Google\Usb_Driver")
double click on the android_winusb.inf file
click OK
double click "Android Composite ADB Interface"
it will then install the driver for ADB
you should now have full access to internal storage and ADB
Alex240188 said:
i also had this same problem after flashing my first custom rom on the n4, and i also run windows 7 Ultimate x64
here is the process i use for full clean installation of device
on phone
goto SETTINGS > STORAGE > (menu) USB Computer Connection
make sure Media Device (MTP) is checked
With USB Debugging On
On your PC go to device manager
there should be 2 devices (Android Phone > Android Composite ADB Interface & Portable Devices > Nexus 4) - this is on a fully working n4 so you might only have 1 of them
Right click on each of them and click uninstall
The popup box should have another check box to delete the driver also, if this is available check it then confirm (note mine only has the box for Android Phone > Android Composite ADB Interface, but if yours has it on both then check it on both)
your computer will now ask you to restart, dont do it yet
repeat previous step for the other device if you have 2 then reboot
upon rebooting it will automatically start reinstalling drivers
by expanding the selection you should see 2 devices
Nexus 4 - Successful - Ready To Use (this is your MTP connection)
Nexus 4 - Unsuccessful - No Driver Found (this is your ADB Connection)
at this point you should be able to access internal storage however ADB will not work
go back into device manager
you should now have
Portable Devices > Nexus 4
and Other Devices > Nexus 4 (with yellow exclamation mark)
right click on the Other Devices > Nexus 4 (with yellow exclamation mark)
hit Update Driver Software
click Browse my computer for driver software
click Let Me Pick Drom a List of Device Drivers On My Computer
double click Show All Devices
click Have Disk...
click Browse
navigate to the download directory for the google usb drivers (for me this was "C:\Program Files (x86)\Android\Android-SDK\Extras\Google\Usb_Driver")
double click on the android_winusb.inf file
click OK
double click "Android Composite ADB Interface"
it will then install the driver for ADB
you should now have full access to internal storage and ADB
Click to expand...
Click to collapse
thank you for your long and detailed reply.
this is what i wanted to do, but the problem is that when I uninstall them, I don't get to see the option "delete the driver software for this device". What should I? cuz every time I plug in Windosws just tries to automatically install the driver for me.
Have you tried toggling to ptp mode then back to mtp on your phone. It's odd indeed.
The fact that you can't remove the driver is because that is the mtp one which is built in to media player. Let me give this some more thought
EDIT: You said that with USB debugging disabled your device is listed under device manager as an android device
can you check and verify exactly what it is listed as? as it should be portable device
Sent from my Nexus 4 using xda app-developers app
Alex240188 said:
Have you tried toggling to ptp mode then back to mtp on your phone. It's odd indeed.
The fact that you can't remove the driver is because that is the mtp one which is built in to media player. Let me give this some more thought
EDIT: You said that with USB debugging disabled your device is listed under device manager as an android device
can you check and verify exactly what it is listed as? as it should be portable device
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
hi under android device it shows up as Android adb device
under portable device i can it now showing up as MTP USB device with exclamation mark.
glancer2315 said:
hi under android device it shows up as Android adb device
under portable device i can it now showing up as MTP USB device with exclamation mark.
Click to expand...
Click to collapse
does adb work?
i.e. adb devices
or is USB debugging turned off at this point
Also. The one with the exclamation mark. Right click and go to properties. What does it say in device status
Alex240188 said:
does adb work?
i.e. adb devices
or is USB debugging turned off at this point
Also. The one with the exclamation mark. Right click and go to properties. What does it say in device status
Click to expand...
Click to collapse
hi, adb devices works. (will list my device when usb debugging is on)
with usb debugging off, under portable device, the device status says "This device cannot start. (Code 10)". thanks.
still looking for solutions. maybe i should try uninstalling the ADB driver, but the problem is that when i uninstall the device from the device manager I don't see the option "delete the driver software for this device", any help?
glancer2315 said:
still looking for solutions. maybe i should try uninstalling the ADB driver, but the problem is that when i uninstall the device from the device manager I don't see the option "delete the driver software for this device", any help?
Click to expand...
Click to collapse
I have this same issue I'm trying to find a fix, that's how I found your thread. Alex gave very good info make sure you go back to his posts and hit his "Thanks" button, I did it on everyone one of his posts in this thread. I'm starting to think it's a hardware issue and not a software issue, I've never had this issue on any device. When I got it new running stock 4.2.2 MTP didn't work. ADB works and PTP works, just not MTP no matter what I try. I recommend you learn to use, ADB push and pull to move your files if you don't already know how to use it (To use ADB I need to check PTP for it to work and not MTP) you might need to do the same. I will keep you posted if I find a fix.
Sent from my Nexus 10 Pimpin AOKP 4Life
I'm just getting more and more confused with this.
If Adb works then you must have an Adb driver installed for the phone. However your also stating that you get no box for uninstall driver.
With USB debugging disabled you said that it appears as an android phone rather than a portable device. This should not be.
With debugging disabled what happens if you Try to uninstall in device manager
Sent from my Nexus 4 using xda app-developers app
---------- Post added at 01:54 PM ---------- Previous post was at 01:51 PM ----------
My theory still stands that you have updated the mtp driver with adb drivers. Hence why mtp doesn't work but ptp does.
The problem is getting to a position where you can uninstall the adb drivers from the mtp device and let it reinstall the proper drivers
Sent from my Nexus 4 using xda app-developers app
I plugged another Nexus 4 in, and all the drivers loaded perfectly. I then tried my Nexus 4 phone, and nothing happens. No mtp, no adb, no boot loader drivers. Its my phone. My next step is to find a zip file that I can flash via custom recovery, which will bring all the binaries and ROM back to stock. Anybody know where I can find this? I'll probably lose the custom recovery, but hopefully it will be fixed and I can flash the custom recovery again.
LG-E960

Nexus 4 appears as unknown device

Hello, I am trying to connect my nexus 4 to my computer to put some music on. This used to work, but now it is being detected as an unknown device. I tried updating the drivers to the Universal Naked driver, but it just says the best driver is already installed. I tried with USB debugging on and off, no difference. Also tried 2 different usb cables.
Cyanogenmod Version: 10.1.1-mako
Build: JDQ39E
Thank you for any help!
jining said:
Hello, I am trying to connect my nexus 4 to my computer to put some music on. This used to work, but now it is being detected as an unknown device. I tried updating the drivers to the Universal Naked driver, but it just says the best driver is already installed. I tried with USB debugging on and off, no difference. Also tried 2 different usb cables.
Cyanogenmod Version: 10.1.1-mako
Build: JDQ39E
Thank you for any help!
Click to expand...
Click to collapse
What OS are you using? Windows? Mac? A linux distro?
Also, are you sure you're using MTP instead of PTP (Settings > Storage > menu > Usb Computer Connection) ?
You can try to install google's drivers from the android sdk as well.
vorbatello said:
What OS are you using? Windows? Mac? A linux distro?
Also, are you sure you're using MTP instead of PTP (Settings > Storage > menu > Usb Computer Connection) ?
You can try to install google's drivers from the android sdk as well.
Click to expand...
Click to collapse
I am using Windows 7, it was set to PTP, I just set to MTP, but it still does the same thing. I have turned off my USB debugging in the developer menu as well.
jining said:
I am using Windows 7, it was set to PTP, I just set to MTP, but it still does the same thing. I have turned off my USB debugging in the developer menu as well.
Click to expand...
Click to collapse
I know this is a silly thing to ask, but have you tried rebooting your phone? Something like this happened to me before and a reboot fixed it.
Also, if you have a custom kernel, check that you have USB fast charge disabled. And after that fails, try installing google's drivers. Sorry, I'm just spouting out random ideas at this point.
vorbatello said:
I know this is a silly thing to ask, but have you tried rebooting your phone? Something like this happened to me before and a reboot fixed it.
Also, if you have a custom kernel, check that you have USB fast charge disabled. And after that fails, try installing google's drivers. Sorry, I'm just spouting out random ideas at this point.
Click to expand...
Click to collapse
Thanks for the suggestions. I am using Franco kernel, how do I turn off fast charge?
jining said:
Thanks for the suggestions. I am using Franco kernel, how do I turn off fast charge?
Click to expand...
Click to collapse
Use trickster mod and go to the Kernel Specific page. If fast charge is ticked off, there's not much we can do from there.
https://play.google.com/store/apps/details?id=com.bigeyes0x0.trickstermod&hl=en
Also, have you tried to install google's drivers or make a nandroid and reflash a clean rom?
EDIT: You could also try Koush's universal driver: https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
I'm afraid I'm out of ideas at this point
vorbatello said:
Use trickster mod and go to the Kernel Specific page. If fast charge is ticked off, there's not much we can do from there.
https://play.google.com/store/apps/details?id=com.bigeyes0x0.trickstermod&hl=en
Also, have you tried to install google's drivers or make a nandroid and reflash a clean rom?
EDIT: You could also try Koush's universal driver: https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
I'm afraid I'm out of ideas at this point
Click to expand...
Click to collapse
Hmm I am in the trickster mod on the kernel specific screen, but I don't see anything about USB fast charge Where might I get googles drivers? I can't seem to install any drivers because as soon as I uninstall the unknown device, it auto installs some drivers.
Thanks for the help!
jining said:
Hmm I am in the trickster mod on the kernel specific screen, but I don't see anything about USB fast charge Where might I get googles drivers? I can't seem to install any drivers because as soon as I uninstall the unknown device, it auto installs some drivers.
Thanks for the help!
Click to expand...
Click to collapse
So I tried installing the newest Franco kernel Milestone (3), and the USB fast charge is off. I also tried installing a different CM mod, but there is no difference. I also tried installing the universal you gave me, but that didn't work, and i installed the google driver from SDK and that didn't work.
I don't know what else to do...
Hi, try to completly unninstall ALL drivers for nexus, samsung or android related, than install official drivers for nexus 4 and then connect nexus 4. Should work.
maxiiik said:
Hi, try to completly unninstall ALL drivers for nexus, samsung or android related, than install official drivers for nexus 4 and then connect nexus 4. Should work.
Click to expand...
Click to collapse
I tried that, no luck...I don't know what else to do, I have tried 3 different cables. I tried using the drivers that come with the nexus 4 toolkit, but no luck. It charges when plugged in, but i get nothing else. Also it seems like half the time its not even in the device manager as an unrecognized device, and then it intermittently pops up a window saying unrecognized device detected... maybe my USB port is broken on the phone?
Is there something simple I have overlooked to get 4.2.2 to work with my computer?
jining said:
I tried that, no luck...I don't know what else to do, I have tried 3 different cables. I tried using the drivers that come with the nexus 4 toolkit, but no luck. It charges when plugged in, but i get nothing else. Also it seems like half the time its not even in the device manager as an unrecognized device, and then it intermittently pops up a window saying unrecognized device detected... maybe my USB port is broken on the phone?
Is there something simple I have overlooked to get 4.2.2 to work with my computer?
Click to expand...
Click to collapse
Have you managed to solve this? I'm facing almost the same problem!
No, I tried for hours with no luck. I am glad I am not the only one, hopefully a solution will come to us. I have been using airdroid to transfer files from my phone in the mean time.
Im also having the same issue except my computer only recognizes my phone when its connected as a camera.
Sent from my Nexus 4 using xda app-developers app
I am having a similar problem with my daughter's Nexus 4 phone, which is not rooted nor unlocked - it is still completely stock. It was just updated to Android 4.3, however I can't say that this is the cause of the problem because she never attempted to connect her phone to the desktop machine before.
I have a Windows 7 x64 box at home, and spent over two hours last night trying to get the computer to correctly recognize the Nexus 4 phone. I was hoping that the standard MTP Windows driver would handle it perfectly, but no luck. I tried the Google usb drivers, and the ADB interface was recognized, but still no access to the internal storage. I then gave the Naked Drivers a try, and no joy there either.
I am beginning to suspect that the MTP drivers on my desktop are munged, but do not relish the thought of a Win 7 wipe and reinstall.
Anyone else have any ideas?
Thanks much!
I am having a similar problem where I have USB storage set to MTP and Windows doesn't pick it up, whereas PTP Windows will pick up but I can't access any folders other than the camera related folders like DCIM.
So my workaround is doing it the old fashioned way through CMD in windows using adb push.
Example:
Assuming you have all the stuff you want to transfer in a folder called stuff, adb is located in C:\adb, and your folder known as stuff is also in C:\adb:
C:\adb>adb push stuff /data/media/0
The above command starting from the ">" will transfer all files in the folder called stuff to the root of /sdcard. In the N4, /sdcard is symbolically linked to /data/media/0.
Of course you need USB debugging enabled for this to work...
Device Manager (Hopefully this helps)
In the start menu type device manager, in that window you should see android and or something similar at the top. You want to drop the menu down and right click what should say Google ADB Interface and delete it, make sure you check the confirmation box. After reboot your computer! Once booted plug your phone in a viola!!!
I'm having a similar issue.
I can open device manager but there in no Android anything listed. All that comes up when I plug my phone in is 'unrecognized usb device'. I have 5 different cable I have tired. The OS will only bring up the usb error in a USB 3.0 port. It will not do anything if I use the 2.0 port.
I have gone and tried to manually update the drivers through the device manager but when I select the drivers from Android SKD or any of the other driver packs I get an error that it is not a x64 driver.
I found one suggestion about modding the driver to include the device but windows will not even recognize the device other than a unknown usb.
I'm going to have a bricked computer soon. Any help would be appreciated.
Roktgr said:
I'm having a similar issue.
I can open device manager but there in no Android anything listed. All that comes up when I plug my phone in is 'unrecognized usb device'. I have 5 different cable I have tired. The OS will only bring up the usb error in a USB 3.0 port. It will not do anything if I use the 2.0 port.
I have gone and tried to manually update the drivers through the device manager but when I select the drivers from Android SKD or any of the other driver packs I get an error that it is not a x64 driver.
I found one suggestion about modding the driver to include the device but windows will not even recognize the device other than a unknown usb.
I'm going to have a bricked computer soon. Any help would be appreciated.
Click to expand...
Click to collapse
First, Google universal naked drivers xda. Try those. If they don't work go into device manager and go to where it says let me choose drivers from my computer. Then look for the android composite adb interface.
If you're on win 8 you'll need to allow unsigned drivers. Google how to do that
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
First, Google universal naked drivers xda. Try those. If they don't work go into device manager and go to where it says let me choose drivers from my computer. Then look for the android composite adb interface.
If you're on win 8 you'll need to allow unsigned drivers. Google how to do that
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Windows 7x64 on all machines. I am trying this on 2 work computers and getting the same result. I have 2 issues that I think are the root of the issue.
#1 is the phone doesn't do anything in USB debug mode. I keep seeing references to having to approve the computer connection but I haven't seen that yet. I have tired 9 usb ports. 6 on my main computer will not bring anything, not even the usb drive. 3 on the labtop will only bring up a 'unrecognized usb drive'.
#2 is the computer will not recognize the device in anything other than a 'unrecognized usb drive' (UUD). Everyone keeps mentioning the Android Composite ADB interface. It's not there, it doesn't show up or as an option. I can go into the device manager and find the UUD and try and update the driver via the manual method with a disk but it doesn't list any type of hardware that is related to Android or ADB.
Roktgr said:
Windows 7x64 on all machines. I am trying this on 2 work computers and getting the same result. I have 2 issues that I think are the root of the issue.
#1 is the phone doesn't do anything in USB debug mode. I keep seeing references to having to approve the computer connection but I haven't seen that yet. I have tired 9 usb ports. 6 on my main computer will not bring anything, not even the usb drive. 3 on the labtop will only bring up a 'unrecognized usb drive'.
Click to expand...
Click to collapse
Hello,
"#1 is the phone doesn't do anything in USB debug mode." This is normal!
How I experienced the USB debugging option is that, if turned ON:
1. The Nexus does not appear in my Windows env
2. BUT when in recovery mode, I can use the "adb" commands
If USB debugging turned OFF:
1. Then I CAN see the Nexus in my Windows env
2. BUT I cannot use the "adb" commands in recovery mode.
So you definitely need to have the USB debugging option turned off if you want to see your nexus in Windows, IMO
---------- Post added at 04:16 PM ---------- Previous post was at 04:02 PM ----------
Roktgr said:
Windows 7x64 on all machines. I am trying this on 2 work computers and getting the same result. I have 2 issues that I think are the root of the issue.
#2 is the computer will not recognize the device in anything other than a 'unrecognized usb drive' (UUD). Everyone keeps mentioning the Android Composite ADB interface. It's not there, it doesn't show up or as an option. I can go into the device manager and find the UUD and try and update the driver via the manual method with a disk but it doesn't list any type of hardware that is related to Android or ADB.
Click to expand...
Click to collapse
I think you really have an issue with the drivers. I would install the Google USB drivers. Maybe a bit heavy but then you can be sure that drivers are fine:
http://developer.android.com/sdk/win-usb.html

Categories

Resources