My setup used to work
Windows 7
CM11S
MTP work just fine. Can browse OPO /sdcard from windows 7
adb device work just fine. I can run all adb commands without problem: devices, shell, push, pull, etc
Now that I have upgraded to CM12S
MTP still work. I can browse OPO /sdcard from windows 7
adb device does not work.
adb devices report nothing. No error, just nothing. As if the phone is not plugged into the computer [see attached screenshot].
But I already installed usb driver, both google's latest and koush's universal adb driver, and tried ADB Interface and ADB Composite Interface
Currently, phone is setup as follow
Setting -> Storage -> USB Computer Connection : MTP
Setting -> Developer Option -> Android Debugging : on
With Android Debugging on, adb device won't show my phone serial when USB Computer Connection is MTP or PTP
When USB Computer Connection is set to charge only, Android Debugging is disabled
With Android Debugging off, I can browse the whole /sdcard when USB Computer Connection is set to MTP
With Android Debugging off, I can browse only DCIM and Pictures from /sdcard when USB Computer Connection is set to PTP
Back in CM11S
When USB Computer Connection is set to MTP, and Android Debugging off, I can browse the whole /sdcard from PC
When USB Computer Connection has NOTHING selected (no MTP, no PTP), and Android Debugging is on, I can use adb.exe on command line: devices, shell, push, pull, etc all work just fine
On CM12S, one of these options MUST be selected in USB Computer Connection: MTP, PTP, Charge Only. This is changed from CM11S
Does anyone have any success with adb.exe on command line on Windows 7 and CM12S (stock kernel)?
If yes, what is your phone setup for adb.exe to work, and which usb driver you installed on your winodws 7?
Thanks!
EDIT: fastboot work just fine
When you're on CM12S you can't have MTP enabled if you want to use adb. Disable MTP temporarily and adb should work.
Transmitted via Bacon
timmaaa said:
When you're on CM12S you can't have MTP enabled if you want to use adb. Disable MTP temporarily and adb should work.
Transmitted via Bacon
Click to expand...
Click to collapse
timmaaa, this is what i could figure out
my only problem is: how do I disable MTP on CM12S?
On CM11S, I can
On CM12S, I must choose one of the options: MTP, PTP, Charge Only
If I am on MTP, and I press it again, the screen just grey out
and then I push back button to go back to main storage screen
and now I choose USB Computer Connection again, and MTP is still selected/enabled
Have you tried to do adb devices on windows on CM12S?
If you can, did you ever enable MTP or PTP?
Thanks
animefans said:
timmaaa, this is what i could figure out
my only problem is: how do I disable MTP on CM12S?
On CM11S, I can
On CM12S, I must choose one of the options: MTP, PTP, Charge Only
If I am on MTP, and I press it again, the screen just grey out
and then I push back button to go back to main storage screen
and now I choose USB Computer Connection again, and MTP is still selected/enabled
Have you tried to do adb devices on windows on CM12S?
If you can, did you ever enable MTP or PTP?
Thanks
Click to expand...
Click to collapse
Instead of pressing MTP again, select PTP.
Transmitted via Bacon
timmaaa said:
Instead of pressing MTP again, select PTP.
Transmitted via Bacon
Click to expand...
Click to collapse
I will try to reconfirm, but I believe I tried that already
regardless of MTP or PTP, adb devices does not find my phone
EDIT: yup, regardless of MTP or PTP, when adb debug is on in developer tools, adb device does not show serial number, so can't connect to phone via adb shell
Same exact problem here, adb worked fine until I turned on MTP now I can't turn it back off and thus adb not working.
No matter what I select or disable I always end up with MTP back on and no ADB working. Someone else who just got their OPO yesterday having same issue and what caused me to mess with MTP setting breaking my ability to ADB :/
Also another new behavior to me is that I cannot access "USB Computer Connection" screen unless I am plugged into PC. When not connected to PC it just rescans internal storage and go's nowhere.
Quick dirty screencast showing how MTP can't be turned off (sorry rushed and kid in background)
https://drive.google.com/file/d/0Bwwwt8cZbp9rYXRGa0Y1dFBfY1k/view?usp=sharing
Good to hear, in a way...
Good is that it's not just me
Bad is that this problem exist
BTW, created this problem in jira
https://jira.cyanogenmod.org/browse/BACON-3358
Hopefully this is a bug in the setting app where USB Computer Connection option is not required. Right now options are required
PS: and yes, I notice the same thing where USB Computer Connection is not even available until you plugged it into PC
PPS: I wonder what is the behavior of USB Computer Connection under OxygenOS and Stock Android (ie Nexus 5/6/etc). Having this data point can narrow down if issue is cyanogenmod OS specific issue, or it's a general Lollipop AOSP issue
is this can be problem why I couldn't install custom recovery?? I try install TWRP, device have unlocked bootloader
if running adb devices on your PC can not see the phone (ie phone serial), then yes you can't install TWRP this way
However, I believe there are other ways to install custom recovery onto your phone without PC
Try TWRP Manager on play store
I used this to update my TWRP recently in order to update to CM12S without going through OTA
Yeah I have the same issue as well and now i don't have Twerp or root . and i can confirm i never had the issue on my nexus 4 with stock LP and Dirty unicorns so it looks like a CM bug to me my phone feels incomplete without root
Solodude said:
Yeah I have the same issue as well and now i don't have Twerp or root . and i can confirm i never had the issue on my nexus 4 with stock LP and Dirty unicorns so it looks like a CM bug to me my phone feels incomplete without root
Click to expand...
Click to collapse
Thank you for the data Solodude!
Quick update on my current situation on this issue
http://forum.xda-developers.com/showpost.php?p=61975450&postcount=4
Well guys, from the title you will think that its a regular windows drivers problem, but its not that straight. My Moto G is not even detecting to my laptop having windows 10 system (no yellow exclamation mark in device manager, not even an error message atleast) But at the same time my friends Moto G and Moto E is connecting in seconds and able to see that in device manager, also able to access files from mobile storage.
First time in my life I am feeling clueless even after trying every option to fix it.
First the basic system information for you:
Laptop: Dell Inspiron 1545 , Windows 10 OS Pro version (not K and KN version )
Drivers installed: Motorola device manager, Google SDK pack is also installed with its ADB driver.
About phone:
Moto G XT1033 16GB model[/COLOR]
OS: non rooted stock Lollipop 5.1 OS, Developer options enabled-USB debugging enabled
Now things I've already tried to fix this:
With Windows 10:
1) Downloaded Motorola device drivers from mototola website for Moto G. Installed, checked for update drivers. Thoroughly gone through Device manager and checked there but no sign of device at all.
2) NO problem with data cable because it can transfer data and not just a charging cable. confirmed and verified.
3) Checked USB ports for loose contacts at both sides of wire. Connected in every port for hope. No such problem.
4) Even after my Windows 10 is a Pro version I still tried to install Media Feature Pack as suggested by Microsoft site in case to overcome this problem but no luck.
5) Whenever I tried to run Motorola device manager, it just checks for new device software and goes off saying no updates.
Now even you can tell that there is no issue with windows system.
With Moto G:
1) Checked USB debugging, stay awake options In developer options.
2) Tried changing MTP option to PTP and reverse in setting - storage menu.
3) Checked every setting menu from android settings and apps to make sure no one is preventing this device from connecting.
4) Tried reseting mobile with to factory.
5) Pen drive is connecting to mobile via USB OTG and data transfer is working to and fro.
Important:
1) I can transfer my mobile files to PC by wireless method using apps, but I want to root my device. For that I have to connect it to PC to unlock the boot loader.
2) Before 2 months with the same system and windows 10, this moto g was connecting to PC and I was able to transfer files. But for now its not connecting at all.
Sorry for the long post but help me guys !!! What can you suggest me here if I am missing something ?
Thanks in advance.:good:
Things you could try:
- Use a Linux OS (live CD/USB) and run lsusb to see if anything shows up
- Put the phone into bootloader mode (fastboot) and see if the PC detects any USB device
If both of the above fail, the USB port in your phone may be defective.
_that said:
Things you could try:
- Use a Linux OS (live CD/USB) and run lsusb to see if anything shows up
- Put the phone into bootloader mode (fastboot) and see if the PC detects any USB device
If both of the above fail, the USB port in your phone may be defective.
Click to expand...
Click to collapse
Thanks for the quick reply. I tried to connect mobile in fastboot mode and now its saying [device descriptor request failed] in device manager. I am trying further and will also check linux os option that you suggested.
Tried both of your workarounds
When connected in fastboot mode it is showing [device descriptor request failed] in device manager.
Searched about it a lot and tried different solutions suggested for it..but its still not connecting properly.
2) checked with live cd and using command lsusb but no luck there ..
Now I'm really thinking that it's a USB port problem/hardware problem of mobile..but how that port is working fine for charging ??
Plzz suggest me any other methods of fix thus problem or is there any other way rather than connecting mobile to pc for unlocking Motorola devices bootloader ???
After a couple of hours trying to fix this problem with my XT1039, I solved it with this windows update: https://www.microsoft.com/en-us/download/confirmation.aspx?id=49919 .
All over the internet ppl say that Media Feature Pack for N and KN versions of Windows 10 should be installed but all the mirrors and 1st results goes to the PREVIOUS version which didn't solve my problem. With this latest version, everything is working now.
Anyone knows any method to set USB host mode (OTG mode) when not having a ID/Sense pin on the cable?
Be it with some sort of "echo 1 > /sys/something" command
Or a ADB command
Or a ready made app?
Or anything?
I did find this app, which seems to do this, but it is just stuck on my tablet.
https://play.google.com/store/apps/details?id=org.psypeople.OTG_patch&hl=en
The reason for this request is that I cannot find any of those "magnet cables" that connect all 5 pins. Always only 4.
And I want my car-tablet to be connected with a magnet cable.
Many thanks
have same problem, is there any way activate USB HOST mode on android 7.1.1 if no SENSE/ID PIN but hardware/kernel support USB OTG?
cybermaus said:
Anyone knows any method to set USB host mode (OTG mode) when not having a ID/Sense pin on the cable?
Be it with some sort of "echo 1 > /sys/something" command
Or a ADB command
Or a ready made app?
Or anything?
I did find this app, which seems to do this, but it is just stuck on my tablet.
https://play.google.com/store/apps/details?id=org.psypeople.OTG_patch&hl=en
The reason for this request is that I cannot find any of those "magnet cables" that connect all 5 pins. Always only 4.
And I want my car-tablet to be connected with a magnet cable.
Many thanks
Click to expand...
Click to collapse
Bumerangas said:
have same problem, is there any way activate USB HOST mode on android 7.1.1 if no SENSE/ID PIN but hardware/kernel support USB OTG?
Click to expand...
Click to collapse
If the device does not have the hardware to support OTG, it won't work no matter what you try.
If it has the hardware but does not have the software, it will require building a new kernel with OTG support implemented in the kernel, or if the device is rooted, you can try something like the Stickmount app to force enable OTG support(the app still requires the device to have the hardware to support OTG, otherwise, it won't work).
Sent from my SM-S767VL using Tapatalk
I have latest Android Studio installed and Android Debug Bridge version 1.0.41.
In Android Studio SDK Tools I have installed Google USB Driver v12.
My ONePlus One has Carbonfibers ROM, has developer options turned on and Android Debugging turned on.
When I plug in OnePlous One I get no mobile notifications and nothing in Win 10 Pro.
Device Manager / Portable or Other devices does not have the phone beneathn it.
When I run adb devices in cmd there are no devices attached.
I cannot find a OnePlus One adb usb driver.
Any suggestions how to diagnose this problem and get my OnePlus One recognised by adb?
Unable to connect to usb
I installed Carbon-cr-5.1-moo-release-bacon-20180202-1444.
I am unable to get usb connection working and having tried many different things...
-I have latest Android Studio installed and Android Debug Bridge version 1.0.41.
-In Android Studio SDK Tools I have installed Google USB Driver v12.
-I have developer options turned on and Android Debugging turned on.
-When I plug in OnePlous One I get no mobile notifications and nothing in Win 10 Pro.
- when I go into developer options and hit 'select usb configuration' my selection of mtp or whatever is always ignored and charging selectiomn remains
-Device Manager / Portable or Other devices does not have the phone beneathn it.
-When I run adb devices in cmd there are no devices attached.
-I cannot find a OnePlus One adb usb driver. I thought I found one but I have no way to verify and after installing it made no difference
I want to update to the latest rom in case this may be the cause, but after I download it to the phone and click flash
I just get the oneplus icon forever and the recover app twrp does not come up. It used to be there but then after I installed
the first rom after a couple of uses it disappeared for some reason or at least will not boot to it.
When I installed that first custom rom I folowed instructions for rooting and on completion it says to open up the installed
su app but when you open it it says there is a more up to date version but when you try to install that it fails.
Now all the apps that will not run if your app is rooted say it is rooted and all the apps that will not run unless it is rooted
say it is not rooted.
I think I need connection via usb in order to reinstall the twrp recovery app in order to install an up to date rom, hoping this may help
me solve the usb issue, but I cannot get the usb connection working as described above,
any hehlop would be appreciated.
Same Situation
hardya said:
I have latest Android Studio installed and Android Debug Bridge version 1.0.41.
In Android Studio SDK Tools I have installed Google USB Driver v12.
My ONePlus One has Carbonfibers ROM, has developer options turned on and Android Debugging turned on.
When I plug in OnePlous One I get no mobile notifications and nothing in Win 10 Pro.
Device Manager / Portable or Other devices does not have the phone beneathn it.
When I run adb devices in cmd there are no devices attached.
I cannot find a OnePlus One adb usb driver.
Any suggestions how to diagnose this problem and get my OnePlus One recognised by adb?
Click to expand...
Click to collapse
but my phone connects in edl mode just for 10 seconds and then automatic
Need Lenovo Vibe P1ma40 to be rooted. Unfortunately, the device is not getting recognized. Device only charges. Have changed the Micro USB port suspecting any physical damage but of no use. So, currently I can't use the USB. Is there any way to run adb commands wirelessly without using USB?
Note: The system can recognise another p1ma40 device implying no driver issue in the computer.
Have you ever enabled USB-Debugging in Android's settings what is required to make use of ADB-commands?
jwoegerbauer said:
Have you ever enabled USB-Debugging in Android's settings what is required to make use of ADB-commands?
Click to expand...
Click to collapse
Yes, I did. Even then not recognised.