I installed AOSB rom and my PC won't recognize my phone as an adb interface. I have the drivers installed. I was going to update the driver software using he software already installed on my computer option. I selected adb interfaces, and I got a list of drivers, but I don't know which one to use. I'm thinking either Mot Composite adb interface or Mot Single adb interface, I'm not sure.
Sorry it's confusing, I'm in a hurry.
Can someone tell me what drivers they have installed for their moto g adb interface?
Sent from my iPad using Tapatalk
I believe this is related to the Hardware ID being different with custom ROMs. PC basically detects handset as a new device and existing drivers won't work because their config files are for the original ID. Maybe a dev can explain why it has changed and if it's possible to change it back.
It's also probably possible to edit the existing drivers for the new Hardware ID.
That's as good of an explanation as any I could come up with. I want to know how to fix it now ha ha.
I think I may have figured it out though.
I grabbed a fresh copy of android sdk and threw it on another computer. I then plugged in my phone and installed the Motorola drivers from their website. It all went well except the Motorola adb interface was still not recognized.
So, I went into device manager, right clicked on the problem device and chose update drivers. Then I picked from a list of drivers already installed. Under the Android section, I just picked Mot single adb interface. It seemed to work fine on one computer, hopefully it will work on the other.
Will post results when I get a chance.
Sent from my iPad using Tapatalk
did you find a solution?
i've recently changed the stock rom and installed C-Rom, and since then i can't install Motorola ADB Interface on MTP Mode, but... in PTP mode it works just fine (i need it for reverse tethering app)...
But in mtp mode i can't transfer files from my pc to my moto g without losing reverse tethering connection...
FaiTCRaH said:
did you find a solution?
i've recently changed the stock rom and installed C-Rom, and since then i can't install Motorola ADB Interface on MTP Mode, but... in PTP mode it works just fine (i need it for reverse tethering app)...
But in mtp mode i can't transfer files from my pc to my moto g without losing reverse tethering connection...
Click to expand...
Click to collapse
Yes, that was indeed the correct driver to use.
I was gonna try out that c-rom myself. If you would like I can grab more info on the driver so you can make sure you are using the right one.
Maybe when I switch in the next couple of days we can troubleshoot it together. If I have the same problem that is ( I'm sure I will ha ha).
Sent from my Moto G using Tapatalk
Related
Hi, I have a Thunderbolt, CM7.1.0 RC0-Thunderbolt-KANG, Kernel 2.6.35.9-cyanogenmod, Android 2.3.4
I've not updated to the one in http://forum.xda-developers.com/showthread.php?t=1049542 because of the Radio problems, and I can't push a Radio because of THIS problem (I've got a few, but a thread for each):
I can't get ADB to detect my device at all. The Android ADB Interface will show up for other rooted devices, just not this one. Laptop, XP SP3, bit old, but works fine. Similarly, I can't get PDANet to detect it, no matter which driver I use. The only device that shows up in Device Manager is "HTC Android Phone USB Device".
Oh, and I've run SDK Manager, making sure everything is up to date. If you want to double check this, just tell me what info to post, I'll gladly do so.
I can't do anything ADB without this. Help?
Bumping this because of how swiftly it got buried. Two hours it's up, and it was four pages down...
triaddraykin said:
Hi, I have a Thunderbolt, CM7.1.0 RC0-Thunderbolt-KANG, Kernel 2.6.35.9-cyanogenmod, Android 2.3.4
I've not updated to the one in http://forum.xda-developers.com/showthread.php?t=1049542 because of the Radio problems, and I can't push a Radio because of THIS problem (I've got a few, but a thread for each):
I can't get ADB to detect my device at all. The Android ADB Interface will show up for other rooted devices, just not this one. Laptop, XP SP3, bit old, but works fine. Similarly, I can't get PDANet to detect it, no matter which driver I use. The only device that shows up in Device Manager is "HTC Android Phone USB Device".
Oh, and I've run SDK Manager, making sure everything is up to date. If you want to double check this, just tell me what info to post, I'll gladly do so.
I can't do anything ADB without this. Help?
Click to expand...
Click to collapse
Quick Question! Are you trying to connect with a MAC or a Windows Computer? Oh... you said Laptop XP SP3... this is not the problem. You know how I made it work on a ViewPad7 connected to a Mac? Activating the USB Tethering...
Can you try if activating the USB Tethering the ADB is able to see your device?
Make sure you have installed the drivers first (adb driver + phone drivers) .... check that in Administrative Tools -> Computer Management (%windir%\system32\compmgmt.msc /s) -> Device Manager -> check if any devices with an ! mark on them, it means the driver for that device is not properly installed.
Right... Well, small new update, and sorry that I haven't responded in a while. Kinda hard to get internet lately.
Anyways, I got a hold of another phone I'd rooted a while back, and decided to test that device. ADB DEVICES worked perfectly for it, but it still can't detect mine. There's no unidentified devices on my laptop's Device Management.
Help?
*sighs* Bump!
I have a rooted Nexus 5. MTP and PTP refuse to work. Doesn't matter how I install/remove drivers or anything. I've tried every trick on the internet and no avail.
The PTP storage used to work when I didn't have root, so what's the deal?
Could this be due to my rooting process? To be honest, I don't remember how I rooted. I'm new to the Nexus scene, having come from a samsung device.
However, I was just having this issue with my older E4GT (GS2 variant) when running rooted/custom roms.
Now, I have a friend with a S4 who decided to get rooted/custom roms and is now having the same issues, except before, both his MTP and PTP worked!
I'm lost and losing hope for this stuff.
aaa12585 said:
I have a rooted Nexus 5. MTP and PTP refuse to work. Doesn't matter how I install/remove drivers or anything. I've tried every trick on the internet and no avail.
The PTP storage used to work when I didn't have root, so what's the deal?
Could this be due to my rooting process? To be honest, I don't remember how I rooted. I'm new to the Nexus scene, having come from a samsung device.
However, I was just having this issue with my older E4GT (GS2 variant) when running rooted/custom roms.
Now, I have a friend with a S4 who decided to get rooted/custom roms and is now having the same issues, except before, both his MTP and PTP worked!
I'm lost and losing hope for this stuff.
Click to expand...
Click to collapse
Is the device showing up under Device Manager (which would indicate that the driver is installed--see #2 here)? This is not a "root" issue. I've run rooted devices for over three years and have only had the problem in the early days with the Pandigital Novel. Have you used USBDeview to look at what you have for USB drivers and to make sure all drivers are being removed? Try another cable and another usb port. Some cables don't handle data, they just charge; cables are a variable in the process.
ritchea said:
Have you used USBDeview to look at what you have for USB drivers and to make sure all drivers are being removed? Try another cable and another usb port. Some cables don't handle data, they just charge; cables are a variable in the process.
Click to expand...
Click to collapse
Yes, I've tried all three of those things. This seems almost to be mission impossible.
I am running rooted stock and my friend is running a new rom altogether. using different computers, but getting the same issue.
See, while I can get Fastboot and ADB to work without a hitch, I can't get PTP or MTP working AT ALL.
ADB and Fastboot seems to be the only thing people are focusing on, and that's not my issue... so It's even harder to find solutions online
aaa12585 said:
Yes, I've tried all three of those things. This seems almost to be mission impossible.
I am running rooted stock and my friend is running a new rom altogether. using different computers, but getting the same issue.
See, while I can get Fastboot and ADB to work without a hitch, I can't get PTP or MTP working AT ALL.
ADB and Fastboot seems to be the only thing people are focusing on, and that's not my issue... so It's even harder to find solutions online
Click to expand...
Click to collapse
So it does show under device manager? Have you right-clicked and updated driver? Step #2 in the link pointed to USB drivers rather than adb. Yes, adb Is the usual culprit, but I've seen quite a few reports of your problem lately. Usually, removing the drivers and allowing the PC to reinstall works. Have you tried wireless to transfer files--at least a temporary solution?
If you're interested (desperate enough) to do a factory reset, I'd recommend WUGS toolkit. It will wipe do backup everything. Revert to stock and unroot. Then root and install custom recovery.
Sent from my Nexus 7 using Tapatalk 4
Happened to me when i rooted the device with wugs. I think because I used the RAW drivers. Just uninstall adb android driver from device manager and all the other drivers that resembles the nexus on usbdeview, reboot . Then put again the usb in the pc , and you are ready to go
ritchea said:
So it does show under device manager? Have you right-clicked and updated driver? Step #2 in the link pointed to USB drivers rather than adb. Yes, adb Is the usual culprit, but I've seen quite a few reports of your problem lately. Usually, removing the drivers and allowing the PC to reinstall works. Have you tried wireless to transfer files--at least a temporary solution?
If you're interested (desperate enough) to do a factory reset, I'd recommend WUGS toolkit. It will wipe do backup everything. Revert to stock and unroot. Then root and install custom recovery.
Click to expand...
Click to collapse
I have tried that too, but I end up with the same outcome. Same drivers I would normally have installed and give me no recognition of the device for file transferring.
Fortunately, knowing how this goes down, as it has happened before with me and my S2, I'm not desperate enough to factory reset. As I would ultimately reach the same issue.
I've been interested in wireless file transferring, but I much more prefer not having to upload the file to something like dropbox or manually setup a server. I'm more into the press-and-go (similar to the plug-and-go method... haha, get it?... made a funny there cause it relates to a cord ordeal) routine.
I haven't actively searched that route yet because I'm in hopes that there is a fix for this problem. I'll get to it if there really is no other choice. So, if there is a program that will allow me that ease of access, I'm open to suggestions!
AkaGrey said:
Happened to me when i rooted the device with wugs. I think because I used the RAW drivers. Just uninstall adb android driver from device manager and all the other drivers that resembles the nexus on usbdeview, reboot . Then put again the usb in the pc , and you are ready to go
Click to expand...
Click to collapse
Seeing this makes me question whether I'm confusing the purpose for each of these drivers or you haven't read what I wrote. However, our circumstances differ. I didn't root through conventional means of the toolkits, I just came across it through my search for driver issues. I have tried the method you are suggesting, as the toolkit driver installation steps take me through that step before I do anything else; but this doesn't work. I end up with the same outcome: Device is recognized and drivers are installed (if I allow windows to automatically search for them), but no PTP or MTP for any file transferring.
ok, silly question : Is it enabled on your android phone? under memory ->tap the 3 dots and you will see mtp/ptp try to uncheck and check.
Otherwise I don't really know anything u could do about it.
By using the NRT or toolkits to root, all of the pc's usb drivers were deleted and new/generic/universal ones installed to re-install custom recovery & achieve root. Go to Control Panel on the PC, do you see Portable Devices listing including the Nexus 5 ? Most likely, no - only Android Interface.
A simplistic approach that worked for me is to roll it back - if you are using PC running Windows OS, use System Restore to go back to a previous state to an earlier (earliest possible) time before - with the N5 disconnected. When the PC is restored, turn OFF USB debugging on the N5, connect via the OEM N5 cable - it should be recognized, then turn ON USB debugging if there are missing drivers - let Windows search & install.
At some point, N5 will be recognized as a Portable Device along wit Android Interface, and "Auto Play" would pop up, with full access to all the SD folders & files. Toggle MTP and PTP if necessary as it might install more drivers - you should be good to go.
Reboot the PC just to reconfirm that everything is back to normal, connect N5 and profit - enjoy.
If this work, please share & if it doesn't - please comment what didn't work.
The simplest and shortest way to connect google nexus5 with PC as MTP(Media device)
When I plugged it, there wasn't any yellow exclamation mark within Device Manager. So for me, the drivers were OK. But the device was not listed within my Eclipse DDMS. After a little bit of searching, it was just an option to change in the device settings. By default, the Nexus 5 USB computer connection is in MTP mode (Media Device).
What you have to do is:
Unplug the device from the computer
Go to Settings -> Storage.
In the ActionBar, click the option menu and choose "USB computer connection".
Then select Media device(MTP) or Camera(PTP) based on your requirement...
Plug the device and you should have a popup on the device allowing you to accept the computer's incoming connection..
I hope this will help!
Hi, I'm trying to go back to stock rom following this guide but I can't get adb to recognize my phone (even if I've already used adb in this pc to unlock the bootloader and flash the custom recovery). I'm on Liquid Smooth ROM and my pc has Windows 8.1.
I tried uninstalling motorola drivers and reinstalling again and uninstalling and letting windows install the drivers automatically but no luck either way (and USB debugging is activated in the phone).
When I access to the device manager in the pc it shows a warning sign on Motorola ADB Interface saying the controllers for that device are not installed, that the manufacturer is unknown and that there aren't compatible controllers for the device (I'm translating what the pic says for those who don't understand spanish xD). I tried to uninstall that Motorola ADB interface thing but it remains there.
What can I do?
SOLUTION: See last post.
You'll need to manually install the driver for the unknown devices. Point to your motorola driver folder.
Are you on CM11?
I had the same problem, tried Motorola USB Driver, Universal ADB driver, Google USB driver and also editing the USB.inf to match the hardwareID.. none of that worked until I set the USB computer connection to Camera (PTP)
Good luck!
neozen21 said:
Are you on CM11?
I had the same problem, tried Motorola USB Driver, Universal ADB driver, Google USB driver and also editing the USB.inf to match the hardwareID.. none of that worked until I set the USB computer connection to Camera (PTP)
Good luck!
Click to expand...
Click to collapse
That same thing happens to me, if I put it in camera mode it does work, the problem is that I need it to work in fastbood mode and it doesn't recognize my device there
gpz1100 said:
You'll need to manually install the driver for the unknown devices. Point to your motorola driver folder.
Click to expand...
Click to collapse
EDIT: I've found the solution, I noticed I had two Motorola ADB Interface controllers, one in "Android Devices" and the other in unknown controllers. I went to the unknown one and imported the same certificate the upper one had and now it works (though I have two Motorola ADB Interface in android devices).
binlalo said:
That same thing happens to me, if I put it in camera mode it does work, the problem is that I need it to work in fastbood mode and it doesn't recognize my device there
Click to expand...
Click to collapse
In fastboot mode, I made the USB work by using Koush's Universal ADB driver.
But if you are using Windows 8 or 8.1, you'll need to turn off the forced signature verification before you can install the drivers, since they are not signed.
Well... glad you got it..
binlalo said:
EDIT: I've found the solution, I noticed I had two Motorola ADB Interface controllers, one in "Android Devices" and the other in unknown controllers. I went to the unknown one and imported the same certificate the upper one had and now it works (though I have two Motorola ADB Interface in android devices).
Click to expand...
Click to collapse
Well... glad you got it..[/QUOTE]
can you explain how did you do this? i have the same problem on c-rom....
FaiTCRaH said:
Well... glad you got it..
Click to expand...
Click to collapse
can you explain how did you do this? i have the same problem on c-rom....[/QUOTE]
Go to device manager, you should see a device called "Android Device" (IIRC). Right click to update device drivers, select device driver, manually search for one but then pick choose from a list. You should be able to see the right driver that is normally used.
Hi,
I just bought a Nexus 5 and I'm having unbearable trouble getting it connected with my PC. I have spent the last 3 or 4 hours on Google and xda forums searching for a solution but nothing has worked so far.
My situation is as follows:
I'm using a laptop running Windows 8.1, I have tried both the original USB cable that came in the package as well as an older one and all the ports on my laptop.
I checked device manager and saw that it was connecting with ACER adb interface drivers. Some people had had the same problem, so I uninstalled the drivers. After that I installed Universal Naked Driver 0.73 (disabled checking for signatures first), my PC could not identify the Google package as a driver. Nexus still didn't show up in explorer although device manager now showed that it was connecting with the proper driver.
I downloaded the Nexus Root Toolkit and did the step-by-step driver setup. Toolkit itself connected perfectly well with my phone and stated that the drivers were successfully installed but my phone still doesn't show up anywhere in explorer.
I've really run out of ideas and cannot find anything online that's related to my problem that I haven't already tried. If anyone could help me, I'd really greatly appreciate it
Thanks,
Alselius
Alselius said:
Hi,
I just bought a Nexus 5 and I'm having unbearable trouble getting it connected with my PC. I have spent the last 3 or 4 hours on Google and xda forums searching for a solution but nothing has worked so far.
My situation is as follows:
I'm using a laptop running Windows 8.1, I have tried both the original USB cable that came in the package as well as an older one and all the ports on my laptop.
I checked device manager and saw that it was connecting with ACER adb interface drivers. Some people had had the same problem, so I uninstalled the drivers. After that I installed Universal Naked Driver 0.73 (disabled checking for signatures first), my PC could not identify the Google package as a driver. Nexus still didn't show up in explorer although device manager now showed that it was connecting with the proper driver.
I downloaded the Nexus Root Toolkit and did the step-by-step driver setup. Toolkit itself connected perfectly well with my phone and stated that the drivers were successfully installed but my phone still doesn't show up anywhere in explorer.
I've really run out of ideas and cannot find anything online that's related to my problem that I haven't already tried. If anyone could help me, I'd really greatly appreciate it
Thanks,
Alselius
Click to expand...
Click to collapse
Have you tried screwing with MTP and (the other) mode? Also is USB debugging on?
tevil said:
Have you tried screwing with MTP and (the other) mode? Also is USB debugging on?
Click to expand...
Click to collapse
Yeah, tried all the possible combinations, MTP, PTP, debug on and off. Responded the same, showed up in device manager and made the connected device sound effect but no folder.
Hi,
I have a very serious problem with my OnePlusOne (64GB) after updating to version YOG4PAS3JL. Since the update, ADB no longer recognizes my phone.
It doesn't depend on the computer I'm using, I have tried to use my phone on 3 different computers (Windows) that I use on a regular basis and none shows my phone with the command adb devices.
Connecting via MTP is no problem, but when I enable Android debugging with USB, my phone will not show up in Windows Explorer.
I have also attached a Samsung Galaxy Note 4 and a HTC phone, both are recognized by ADB.
If I change the mode to MTP, it will show up as portable device called A0001 in the windows device manager. If I switch to Android Debugging, it will simply disappear and not show up
as "other device" or usb device without driver. So I can't even reinstall Android ADB Interface, it also doesn't show up in the Device Manager any longer. If I try to install a driver for my OnePlus One when it is in MTP mode, it will also only allow me to install MTP drivers (no possibility to install the previously so fine working Samsung USB drivers).
I have literally tried every solution out there I have found, from unplugging and restarting my phone, using different USB ports, using different USB cables, reinstalling Samsung USB drivers (didn't help as phone did not show up as unrecognizes device any longer), uninstalling Google USB driver, adding OnePlusOne to the .inf usb driver file myself (which mostly resulted in an "no compatible driver was found in this folder"-error), installing fastboot (didn't change anything), universal adb driver setup, pdanet, using USDBDeview, removing drivers with the bacon root toolkit to removing mtp files from the inf folder of windows to prevent MTP driver installation, but nothing worked
I would prefer to go back to the version before YOG4PAS3JL, where ADB worked fine or install a different ROM, but I have seen that every guide states that you need to have ADB to install a new ROM. As my phone is not rooted and I can no longer use ADB with my phone, I'm basically pretty stuck and don't know what to do I'm pretty desperate after two days of trying to solve this problem without success and would be so thankful for any suggestion what I could do.
Same situation...let me know if you find any solution.
Same situation here. Anf I guess this might have a link with my lack of internet connection while tethering.
Did any of you tried the USB or wifi tether? Does it work?
Sent from my A0001 using XDA Free mobile app