FORUMS

HTC Delivering Ads Straight to Sense Home

HTC’s 2015 has been a year marked by a desperate search for revenue.The HTC One M9 … more

Galaxy S6 & Edge get €100 Price Cut—New Models Incoming

Samsung has dropped the price of both the Galaxy S6 and S6 Edge by … more

How To Port Fully Featured Sony Xperia Z4 Camera

Xperia Z4’s hardware may not impress, but its software is definitely … more

Experimental TWRP Available For Moto G 2015

XDA Senior Member squid2 has posted experimental builds of TWRP for the Moto G … more

[Solved] ADB device not found

407 posts
Thanks Meter: 49
 
By binlalo, Senior Member on 9th March 2014, 12:16 AM
Post Reply Subscribe to Thread Email Thread
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.
Attached Thumbnails
Click image for larger version

Name:	Sin título.png
Views:	541
Size:	49.7 KB
ID:	2620829  
Last edited by binlalo; 9th March 2014 at 03:43 PM.
 
 
9th March 2014, 05:41 AM |#2  
gpz1100's Avatar
Senior Member
Thanks Meter: 296
 
More
You'll need to manually install the driver for the unknown devices. Point to your motorola driver folder.
The Following User Says Thank You to gpz1100 For This Useful Post: [ View ]
9th March 2014, 10:06 AM |#3  
neozen21's Avatar
Senior Member
Flag Henderson, NV
Thanks Meter: 119
 
More
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!
The Following User Says Thank You to neozen21 For This Useful Post: [ View ]
9th March 2014, 02:45 PM |#4  
OP Senior Member
Thanks Meter: 49
 
More
Quote:
Originally Posted by neozen21

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!

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
9th March 2014, 02:54 PM |#5  
OP Senior Member
Thanks Meter: 49
 
More
Quote:
Originally Posted by gpz1100

You'll need to manually install the driver for the unknown devices. Point to your motorola driver folder.

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).
Last edited by binlalo; 9th March 2014 at 03:42 PM.
9th March 2014, 06:59 PM |#6  
neozen21's Avatar
Senior Member
Flag Henderson, NV
Thanks Meter: 119
 
More
Quote:
Originally Posted by binlalo

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

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..
1st April 2014, 08:29 PM |#7  
Member
Thanks Meter: 5
 
More
Quote:
Originally Posted by binlalo

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

Well... glad you got it..[/QUOTE]

can you explain how did you do this? i have the same problem on c-rom....
Last edited by FaiTCRaH; 1st April 2014 at 09:00 PM.
2nd April 2014, 12:05 PM |#8  
Junior Member
Thanks Meter: 4
 
More
Quote:
Originally Posted by FaiTCRaH

Well... glad you got it..

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.
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes