When I use the MTP mode with USB debugging, the list of devices attached in adb (Command:adb devices) has nothing on it.
However, the PTP mode with USB debugging works with ADB. The system will show the dialog with the RSA-key of my computer and ask me to "Enable USB Debugging" when I change the connection type from MTP to PTP.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is there any solution that using ADB with MTP mode? Thanks a lot.:laugh:
I'd blame the drivers on the system. Remove all and reinstall them, using least amount of drivers first. I had the same issue.
This posting may be of interest to you in fixing the problem. http://forum.xda-developers.com/showthread.php?t=2391236
That thread is actually the reversed problem. MTP only works with USB debugging turned on.
I think OP is saying USB debugging is only working with MTP turned on.
My guess is old driver issue. Use Device Manager to remove device *and* remove drivers, then reboot, then install latest Google USB drivers.
sfhub said:
That thread is actually the reversed problem. MTP only works with USB debugging turned on.
I think OP is saying USB debugging is only working with MTP turned on.
My guess is old driver issue. Use Device Manager to remove device *and* remove drivers, then reboot, then install latest Google USB drivers.
Click to expand...
Click to collapse
I believe he has the same issue I have MTP + USB debugging does not allow adb to work. However, keeping USB debugging on and switching to PTP (the camera mode) does allow adb to see the nexus 7 and pop-up the authorization prompt. I've uninstalled the drivers many times trying to get adb working when using MTP and USB debugging, but it never, ever takes. Must be something in the system config, not the driver.
Is this the stock ROM?
sfhub said:
Is this the stock ROM?
Click to expand...
Click to collapse
Yes, I have updated to JSS15R.
This is just a drivers conflicts..its really annoying just keep configuring
true. when mtp or ptp, your nexus is not treated as an android machine any more
Sent from my Nexus 7 using XDA Premium 4 mobile app
Related
My AT&T Samsung Galaxy S III suddenly no longer works with usb. It can charge with the connection, but it does not show up as any kind of device. No MTP, no PTP, no usb debugging, no anything!
I tried:
- Factory resetting
- Plugging it into a different computer
- Switching to a different ROM
- I even tried to restore to stock firmware, but Odin couldn't see it.
No computer can notice my phone. It doesn't even notify me that it is unrecognized. The usb on my phone is locked out from any connection other than charging.
I use the phone for Android development and I use Eclipse ADT to compile my apps.
Is there any other solution I haven't tried?
jperry73 said:
Try a different cable, preferably an OEM one. Use a USB slot on the back.
Click to expand...
Click to collapse
Used the cable that came with my phone on different USB ports. Didn't work.
jperry73 said:
Uninstall Kies
Install these drivers:
Reboot
Click to expand...
Click to collapse
Already had the drivers installed. Reinstalled, rebooted, still doesn't work.
Here are a couple of other things to check. This menu can be achieved by using dialer code *#7284# on a Tw based rom.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then choose Qualcomm usb settings to check this
jperry73 said:
This was Windows 8 and solved by:
Uninstalling the Samsung Drivers
Running CCleaner
Rebooting
Hooking up the phone in each connection type: D/L Mode, MTP, and Debugging
Windows Update loaded the drivers properly
Click to expand...
Click to collapse
Don't forget pulling out the battery from my phone and going into download mode without the battery. Thanks a lot for your help!
The true fix for this annoying issue is to reboot the phone into download mode. Then hold the power and home buttons down for a few seconds to force a power down. When the phone is off, power it back on like normal, and you can then connect to usb again. This is a pain but it works EVERYTIME, guaranteed.
Sent from my Nexus 7 using xda premium
jperry73 said:
true fix is Windows 7
Click to expand...
Click to collapse
No. I use Windows 7 and this still happens all the time.
Sent from my Nexus 7 using xda premium
Yea. That.
Drivers seem good:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can get into it from the computer.
I've tried different cables.
I've tried every USB port on my computer.
I can unplug the cable from the N7 and go directly into my N4, adb devices it, good to go.
I've noticed that, on my N4, I plug it in and I can get into it through Windows Explorer AND it shows up on ADB. On the N7, if USB Debugging is checked, I can't get into it through Explorer or ADB. If I uncheck it USB Debugging, Windoze does its little unplug noise, then the plug in noise and I can get into it. Is this a 4.3 thing?
Has anyone else had this happen? Is this a bug or am I the bug?
Any help greatly appreciated. Thanks!!
I don't have an N7 2013 (thinking about getting one though ) but passing on something a friend told me about her older N7 model: it didn't allow ADB while MTP was enabled. So you might try disabling that and seeing if it helps.
Maybe you have some permission problem and need to run the shell as administrator. It looks like the tablet was recognized from a driver standpoint.
Are you sure that's the right driver? It says Android Phone/Google Nexus ADB Interface.
Seems like you have the drivers installed for your N4 but not your N7.
Geodude074 said:
Are you sure that's the right driver? It says Android Phone/Google Nexus ADB Interface.
Seems like you have the drivers installed for your N4 but not your N7.
Click to expand...
Click to collapse
Yours says something different? Mine says Android Phone and I don't think I've seen it say anything else, whether phone or tablet were connected.
I'm having the EXACT same problem and it's driving me nuts, my Device Manager says Google Nexus ADB Interface
EDIT: Solved it, go to settings > Storage > click the menu on the top right and select USB connections > Select PTP instead of MTP.
w0ng3r said:
I'm having the EXACT same problem and it's driving me nuts, my Device Manager says Google Nexus ADB Interface
EDIT: Solved it, go to settings > Storage > click the menu on the top right and select USB connections > Select PTP instead of MTP.
Click to expand...
Click to collapse
If you want to get it working with MTP and USB debugging enabled see this post:
http://forum.xda-developers.com/showthread.php?t=2391236
aletthi fess
I'd just like to throw in that I was having the same issues with ADB and the only time I got it to work was after I disabled MTP/PTP on the phone. Im sure there are better fixes in this thread but thats my two cents.
After updating to the latest driver version 8.0 it should say "Android Composite ADB Interface".
I'm having the same problem and it's driving me crazy!!! This is funny longest I've EVER went without rooting, assuming root was available for that particular device. I'm gonna try disabling both MTP and PTP, like mentioned earlier.
Sent from my '13 Nexus 7 using XDA Premium HD app
Whenever I connect my device to PC in download mode, I get a notification from my PC "Your USB device is malfunctioned, it may not work properly, please try again later" something like that.
Odin is unable to detect my device, what should I do?
quanlim said:
Whenever I connect my device to PC in download mode, I get a notification from my PC "Your USB device is malfunctioned, it may not work properly, please try again later" something like that.
Odin is unable to detect my device, what should I do?
Click to expand...
Click to collapse
Hey, it's you again
Have you enabled "USB Debugging" in CM11 settings?
What about your Windows drivers? my device manager shows:
- "SAMSUNG USB Composite Device"
- "SAMSUNG Mobile Modem"
LS.xD said:
Hey, it's you again
Have you enabled "USB Debugging" in CM11 settings?
What about your Windows drivers? my device manager shows:
- "SAMSUNG USB Composite Device"
- "SAMSUNG Mobile Modem"
Click to expand...
Click to collapse
It shows as Android Device, PC can detect phone in normal boot
quanlim said:
It shows as Android Device, PC can detect phone in normal boot
Click to expand...
Click to collapse
In download mode you get only the error and the device manager doesn't show the device?
Have you uninstalled/reinstalled usb drivers?
LS.xD said:
In download mode you get only the error and the device manager doesn't show the device?
Have you uninstalled/reinstalled usb drivers?
Click to expand...
Click to collapse
I tried =(
quanlim said:
I tried =(
Click to expand...
Click to collapse
Also tried deactivating/activating "USB Debugging"?
May u use adb commands while phone is started and connected?
Try also installing ADB/fastboot drivers again please. http://forum.xda-developers.com/showthread.php?t=2588979
If you're not sure if your drivers have been uninstalled correctly, you can follow these steps:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I purchased an LG-G3. Performed an OTA update to latest: 47A. I connected to my Windows 10 box, enabled debugging, worked fine.
I downgraded using TOT method to 10B. The device is now running 4.4. Reconnected device to Windows 10 box, enabled USB debugging, does not work.
The device only shows up in device manage as a portable device
I have tried the sticky on this forum, unfortunately it does not apply as I do not have any of the items listed to remove
I have uninstalled all LG Driver/LG Verizon Driver/Google driver etc.
I have used USBDeview to remove anything named LG/ADB/Google
I have rebooted my machine, double checked the USB list with USBDeview
I have enabled/disabled/revoked USB Debugging, switched between MTP/PTP, rebooted phone
I feel like every time I google the problem a different way, I end up back at the Google USB driver download page or the LG Verizon driver download page
I would appreciate a fresh set of brains, I have a feeling I am now tunnel visioned and won't ever get out, please help ;0 I never get that prompt on the phone to allow the computer access to the phone, is that permission still on the PC is some fashion and needs to be revoked?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I ran a system update and the phone downloaded ~200mb file, applied and rebooted. Looks like that was 35B bootstack and now the phone does enable USB Debugging. Unfortunately if I take the phone back to stock USB Debugging still does not work
I also connected the fresh stock phone to another Windows 10 machine with the LG G3 Verizon Drivers installed and could not get USB Debugging to enable...
Cmd as admin, cd *adb path* , adb devices and an authorization should appear on your phone, usually works with me.
myclarity said:
Cmd as admin, cd *adb path* , adb devices and an authorization should appear on your phone, usually works with me.
Click to expand...
Click to collapse
Appreciate the suggestion, tried that and adb devices command just reports no devices connected and no prompt on the phone
mhum said:
Appreciate the suggestion, tried that and adb devices command just reports no devices connected and no prompt on the phone
Click to expand...
Click to collapse
The cmd part as admin is very important, dunno why but it wouldn't recognize my phone unless cmd was started like that.
Any way to disable Samsung's 'cable detection' feature? USB tethering doesn't work because device doesn't recognize cable. I'm using original one and tried new and older cables also. I've had similar problems with another Samsung devices before and it's pretty annoying. WIFI is too slow and bluetooth even slower compared to USB so I don't like using them. Device just keeps telling use original cable and starts charging slowly.
Also the usb c port is cleaned, tried restarting device several times, tried all usb ports of my pc. I'm using Windows 10 pro. All drivers are updated and I have newest Samsung drivers.
Turn on Developer options and try setting it up there. No blocked or disabled Samsung system apps, right?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
blackhawk said:
Turn on Developer options and try setting it up there. No blocked or disabled Samsung system apps, right?
View attachment 5713053
Click to expand...
Click to collapse
Tried that but it doesn't work. Also Windows is saying it can't recognize usb-device. I have disabled YouTube only because I use another app for that.
Slixy said:
Tried that but it doesn't work. Also Windows is saying it can't recognize usb-device. I have disabled YouTube only because I use another app for that.
Click to expand...
Click to collapse
Hit take no action in the Windows connect popup*. Then go to Disk Management and punch scan for new devices. Access the drive in that window and do the transfers there. Command line can also be used to access Disk Management etc.
Try rolling back or updating the driver. Installing the latest version of SmartSwitch on Windows should load the correct driver.
*you must authorize the connection first on the Android via a popup window that should appear after being connected.
Not working. Reinstalled all usb drivers including Samsung ones. Smartswitch is not working because Windows can't recognize this device at all. Maybe I just reinstall Windows some day and try if it works then. Thanks for the help.
Slixy said:
Not working. Reinstalled all usb drivers including Samsung ones. Smartswitch is not working because Windows can't recognize this device at all. Maybe I just reinstall Windows some day and try if it works then. Thanks for the help.
Click to expand...
Click to collapse
You're welcome.
Try another port and cable.
Reboot, always reboot Windows.
Check Event Viewer for error messages.
For Windows to recognize the device you sometimes need to use the scan for new devices command in Disk Management. The solution is likely simple and right in front of you.
Play with it... fun times.