Related
Originally Posted by nicbennett
*Daemon not running, starting it now on port 5037*(this does successfully start the adb.exe process)
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon*
Click to expand...
Click to collapse
Originally Posted by snovvman
W7/64.
ADB worked for me for months. I used it regularly. The last thing I did was *trying* to use Wireless ADB Widget and issueing ADB TCPIP command. I have made no changes to the system.
The error occurs when no device device connected. Same error when device IS connected.
-Downloaded ADB/SDK again to a different directory, same error
-Updated USB driver and SDK components, same error
-Disabled all firewall/anti-malware/anti-virus, same error
-Rebooted multiple times, same error off boot
-Port 5037 is not bound by any app or process
-ADB, upon failed load, is not listed in Taskmgr, nothing to kill
-Deleted temp files
-Issued at prompt: ADB Disconnect, ADB USB, ADB devices: All return same error as above
-Issued at prompt: ADB kill-server, only prompt returns
Read lots of posts on the web, nothing helps.
I am really interested in a solution and would like to understand what is causing the problem. If in fact it is a configuration issue, where is the ADB config file?
Thanks.
Edit: I am running the command prompt as an administrator.
Click to expand...
Click to collapse
I originally added my post to this thread in the Nook forum. I don't think there is enough expertise in that forum to help with this problem.
The bottom line is that ADB no longer works and I can't figure out why (see quoted text above). I would imagine that someone here would have an answer for this. Please help!
Thanks.
Only thing I would try it open Task Manager and go to processes and close anything that is adb or adb.exe.
DGreen1 said:
Only thing I would try it open Task Manager and go to processes and close anything that is adb or adb.exe.
Click to expand...
Click to collapse
In this case, ADB never starts. It does not work even after a fresh reboot. It is not found in Taskmgr nor Process Explorer.
snovvman said:
In this case, ADB never starts. It does not work even after a fresh reboot. It is not found in Taskmgr nor Process Explorer.
Click to expand...
Click to collapse
Is what he meant was to kill any process that is using adb. This is not only a process that is Android related etc. My buddy had your exact same problem because he had his external hd connected to his computer before trying to run adb. Restarting and killing processes that were using adb on his computer did the trick. Hope this helps!
My problem was Windows
snovvman said:
The error occurs when no device device connected. Same error when device IS connected.
. . .
I am really interested in a solution and would like to understand what is causing the problem.
Click to expand...
Click to collapse
In my case, the problem was Windows Vista. From day one, Windows refused to successfully install the USB drivers for the EVO (with the very helpful diagnostic message: "Windows encountered an error installing..."). I have never been able to use adb, and this meant that all the rooting (and update/upgrade) guides that required adb had to be adapted to getting the file(s) onto the SD card, and then using Terminal Emulator (or similar app) to get the job done.
I've just completed a disk-wipe-and-reinstall of Windows on my laptop, and hope to find the time next week to install all the SDK goodies and make sure that the USB subsystem recognizes my EVO. I'm fed up with not being able to use adb, and that, along with Windows Update failing to install over a dozen security patches, finally pushed me over the edge into a re-install. Auuugh! The pain!
Yellowcard8992 said:
Is what he meant was to kill any process that is using adb. This is not only a process that is Android related etc. My buddy had your exact same problem because he had his external hd connected to his computer before trying to run adb. Restarting and killing processes that were using adb on his computer did the trick. Hope this helps!
Click to expand...
Click to collapse
Interesting, but I haven't been able to find any other service that is bound to adb and I have no other USB devices connected. Thanks for chiming in though.
tgi007 said:
In my case, the problem was Windows Vista. From day one, Windows refused to successfully install the USB drivers for the EVO (with the very helpful diagnostic message: "Windows encountered an error installing..."). I have never been able to use adb, and this meant that all the rooting (and update/upgrade) guides that required adb had to be adapted to getting the file(s) onto the SD card, and then using Terminal Emulator (or similar app) to get the job done.
I've just completed a disk-wipe-and-reinstall of Windows on my laptop, and hope to find the time next week to install all the SDK goodies and make sure that the USB subsystem recognizes my EVO. I'm fed up with not being able to use adb, and that, along with Windows Update failing to install over a dozen security patches, finally pushed me over the edge into a re-install. Auuugh! The pain!
Click to expand...
Click to collapse
For me, I have been able to get two Vista and one Windows 7 computer to work with ADB and HTC drivers the first time. I also have an Epic, and the Samsung drivers installed fine as well (even though they are known to have issues).
Unfortunately, ADB just "broke" one day.
I keep thinking that the Evo community has enough brains and knowledge to sort this out quickly...
Have you updated the sdk recently?
The updated sdk moves the adb files from the tools folder to another folder called platform-tools.
I have adb working properly on both my vista machine and my ubuntu machine hosted on my vista machine.
If you have installed htc sync before uninstall it and the htc driver installer.
Redownload htc sync and the adb files (adb.exe and adbwinapi.dll is all you need). Since adb was working correctly before I'm assuming your java is installed correctly as well.
Reinstall htc sync. When that finishes I suggest a reboot. When you've rebooted uninstall htc sync but leave the htc driver installer. Reboot again.
When you've rebooted again enable usb debugging on your device and connect it to your pc choosing charge only.
This should hopefully reinstall the usb drivers correctly. On vista it installs as adb device or something along those lines.
If the drivers install correctly you should be able to run adb from the directory your two files are in (desktop for example).
If you want, send me a pm with your gtalk username and I can help you troubleshoot it.
lovethyEVO said:
Have you updated the sdk recently?
The updated sdk moves the adb files from the tools folder to another folder called platform-tools.
I have adb working properly on both my vista machine and my ubuntu machine hosted on my vista machine.
If you have installed htc sync before uninstall it and the htc driver installer.
Redownload htc sync and the adb files (adb.exe and adbwinapi.dll is all you need). Since adb was working correctly before I'm assuming your java is installed correctly as well.
Reinstall htc sync. When that finishes I suggest a reboot. When you've rebooted uninstall htc sync but leave the htc driver installer. Reboot again.
When you've rebooted again enable usb debugging on your device and connect it to your pc choosing charge only.
This should hopefully reinstall the usb drivers correctly. On vista it installs as adb device or something along those lines.
If the drivers install correctly you should be able to run adb from the directory your two files are in (desktop for example).
If you want, send me a pm with your gtalk username and I can help you troubleshoot it.
Click to expand...
Click to collapse
Thanks for replying. I had already updated ADB (in platform-tools) before started having this problem. I had also uninstalled HTC sync (reboot, launch ADB w/o HTC sync, same problem) and reinstalled HTC sync, same problem. I updated Java JVM, no change. I then re-downloaded the SDK to a different directory, no dice.
I usually open a command prompt "as Administrator" and run ADB from the directory. Even with a device disconnected, I get the same error. I test this way because if I issued "ADB devices" and it returns nothing, I know it's working. It appears that ADB doesn't even start to the point to poll for devices.
I have, just for laughs, connected my device (USB debugging/charge only), but no joy.
I won't have much time to poke around more until the weekend. If I don't come up with anything, I will take you up on the gtalk. Thanks again.
Windows Vista just makes it all that much harder to fix things...
lovethyEVO said:
If you have installed htc sync before uninstall it and the htc driver installer.
. . .
Reinstall htc sync. When that finishes I suggest a reboot. When you've rebooted uninstall htc sync but leave the htc driver installer. Reboot again.
. . .
This should hopefully reinstall the usb drivers correctly. On vista it installs as adb device or something along those lines.
Click to expand...
Click to collapse
In my case, I tried all these things and many more (lived with this problem since first getting my EVO on release date in June). No dice, as Windows Vista, once it installs a device driver, doesn't give the user the option to uninstall it (by Microsoft's expressly-stated intent -- a design decision I vehemently disagree with). At least the user could repair such problems in prior versions of Windows by simply uninstalling a device, choosing "yes" to the "remove driver files from the disk" question, and (after the obligatory and ubiquitous Windows reboot) re-connect the USB device. That would start fresh with that device's driver.
I never invested the time to learn how the USB subsystem registers devices and their drivers (in Windows Vista) in order to determine how to manually remove a driver from the Windows Registry adequately that it would treat the device as "new hardware detected" upon the next connection.
Once Windows Vista has scrambled some internals in the database/registry controlling the USB subsystem's driver knowledge, you're toast. Nothing I could find in Microsoft's Knowledge Base nor MSDN shed any light on how to tackle the removal-and-recreation-from-scratch of the USB system configuration.
Microsoft's stock answer was invariably "re-install Windows". Yeah, thanks for that. Windows, even more than 26 years later, is still not a real operating system, and still has bugs dating back to Windows 3.1.
Sigh.
Check Windows Firewall service.
In my case I just turned off the Windows Firewall and it started working.
regards
Gaurav
i had this problem.
disable any program like Proxifier and firewall
I accidently figured it out
so i was trying to find my cid number because i was flashing ICS firmware and stuff, and the adb deal in the prompt kept giving me the exact same error, and thus would'nt work. after trying everything (such as: installing drivers, killing the process, restarting my comp, reinstalling adb, etc.) for about an hour and a half, i just stumbled upon a page that was linked to in the ICS flash guide, that had a different adb folder download. this download has an entirely different effect on the command prompt and worked so i could get my cid number and rewrite superCid. here it is:
http://forum.xda-developers.com/attachment.php?attachmentid=872134&d=1327512033
Download it, click "start here", then treat it like normal
ADB server din't ACK
Please help....I was trying installing Hellkat 4.4.2 on my kindle fire by following http://forum.xda-developers.com/showthread.php?t=2570078
Downloaded all the files and flashed through TWRP and was successful. But after flashing, when it is rebooting it is getting stuck on the hellkat logo and not booting.
If I try to install TWRP again, i am getting error ADB server din't ACK *failed to start daemon*. and ADB status online and boot status unknown.
Please help......
orangeipod1gb said:
ADB server din't ACK
Please help....I was trying installing Hellkat 4.4.2 on my kindle fire by following http://forum.xda-developers.com/showthread.php?t=2570078
Downloaded all the files and flashed through TWRP and was successful. But after flashing, when it is rebooting it is getting stuck on the hellkat logo and not booting.
If I try to install TWRP again, i am getting error ADB server din't ACK *failed to start daemon*. and ADB status online and boot status unknown.
Please help......
Click to expand...
Click to collapse
your solution is
netsh advfirewall set currentprofile firewallpolicy allowinbound,allowoutbound
Ok... i've gone through the steps in the one thread to get the phone rooted and everything without tripping the flash counter. At least the rooting with ODIN part. Been trying to flash CWM Touch for it, but for the life of me can't get the S3 to enter debugging mode over USB so that it can be seen by ADB to do so. I have Debugging over USB checked in the settings on the phone, i've rebooted the phone several times... it just never seems to enter debugging mode (or at least not like on my old Atrix 4G, where it actually told you in the notification bar that debugging was enabled).
It doesn't say debugging enabled. Do you have Kies installed? If so make sure it isn't running. Plug in the phone and type adb devices. If detected adb will report a serial number.
gunnyman said:
It doesn't say debugging enabled. Do you have Kies installed? If so make sure it isn't running. Plug in the phone and type adb devices. If detected adb will report a serial number.
Click to expand...
Click to collapse
I had installed Kies... tried hooking it up, still wouldn't list in ADB. uninstalled Kies, but kept the drivers installed. And i only mentioned the idea of it saying Debugging enabled when you connect the USB cable because my Atrix 4G said that every time from the get-go.
Also odd.... looked into the SuperUser app... and the log shows several allowed access attempts from "shell"... yet never seemed that way in ADB.
I had the same problem... try going in to the "services" settings and update the driver to Android ADB composite. Other than that, my suggestion is to make sure Kies finds the drivers for both Camera mode and USB mode by toggling the selection while plugged in to Kies.
Sent from my SGH-I747M using xda app-developers app
Your last resort would be to remove the drivers and reinstall them... Don't install Kies...
Or do you think i might have better luck in Ubuntu? Have that installed on my desktop as well.
edit: well... that's odd. booted into Ubuntu, installed the linux Android SDK and everything, got everything set up. opened the terminal, and just checked the devices without being in the ADB Shell... and a device showed up. launched the adb shell... checked devices again... nothing showed up, as on Windows. Figured what the hell, and did the command to install the recovery, and it worked.
elementaldragon said:
Or do you think i might have better luck in Ubuntu? Have that installed on my desktop as well.
Click to expand...
Click to collapse
It seems to be a driver issue, kies interfering, or a component is missing, or all of that, so I'd start your windows driver and software over fresh...
Uninstall Kies
Uninstall the drivers
Reboot
Install the drivers
Install the Java JDK (64bit has never worked for me, even though the drivers are 64bit)
Install the Android SDK
Use the Android SDK to get the Platform Tools and the Google USB Driver
than adb devices should show a phone
---------- Post added at 11:25 AM ---------- Previous post was at 11:24 AM ----------
elementaldragon said:
edit: well... that's odd. booted into Ubuntu, installed the linux Android SDK and everything, got everything set up. opened the terminal, and just checked the devices without being in the ADB Shell... and a device showed up. launched the adb shell... checked devices again... nothing showed up, as on Windows. Figured what the hell, and did the command to install the recovery, and it worked.
Click to expand...
Click to collapse
sometimes ADB Devices returns nothing for me, but theres a phone there, it would say nothing connected or to some effect if it didn't find anything...
Yea... every time i entered "adb devices" in the Windows command prompt, it always said "List of detected devices" or whatever it says, but nothing would be there, and if i tried the command to install the recovery it would say it was not a valid directory or whatever. Didn't show up on Ubuntu either, but it still worked...
EDIT/UPDATE: I was using a USB 3.0 port which apparently ADB didn't like (though ODIN rooting on that USB port worked fine...). I switched to another USB port and suddenly it worked!
Sorry to resurrect an old thread but I guess it's better than creating a new one for the same purpose...
Doesn't seem like this was resolved and I haven't been able to get my S3 to connect to ADB. I'm running Windows 7 Ultimate 64 Bit.
I had this driver already installed:
ATT_I747_GSIII_Samsung_USB_Driver_v1_4_6_0
I enabled USB debugging and it wouldn't connect. I installed Kies, still wouldn't connect. I uninstalled the driver and Kies and rebooted. Reinstalled "ATT_I747_GSIII_Samsung_USB_Driver_v1_4_6_0", installed the Google USB driver, still won't connect.
I'm still not sure if I'm supposed to see any sort of notification in my bar showing that USB debugging mode has been executed but I'm definitely not getting anything like that.
Code:
D:\APPS\ANDROID\android-sdk-windows\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
891b0876 offline
D:\APPS\ANDROID\android-sdk-windows\platform-tools>adb devices
List of devices attached
Yea, when i finally was able to use ADB to push a recovery onto my S3, it never actually showed up if i checked the devices in ADB Shell. Well... it DID, but not if i already typed the SU command before "adb devices".
hey guys
i have same problem i wanna adb my galaxy s3 rogers (att) i am trying to do the root no tripping flash counter so i got to the adb shell part
i dont know what else to do to make my computer recognize my phone ??
i installed sdk and extract/installed it in the c:\android folder of my comp i let sdk installed all the things it needs to took a while
so whats left? i have my phone usb connected to comp and debuging on i type adb shell it says adb is not recognized internal or external command???
do i need to have somthing open on the phone b4 openning command?
pleaaase help lol
thanks
You need to navigate to the folder where adb is actually located (platform-tools)
You don't have to use adb, you can use the same commands on terminal emulator
Hello,
I've been able to use ADB to install and test apps that I'm writing under the stock ROM for my Epic, as well as under CM9 (and I think an early CM10, not sure about that though). After installing the 20130101 build of CM10.1 (keeping the included kernel), I am having issues trying to deploy and debug apps from my any of my computer to the phone (all of which previously worked). I've verified that Android Debugging is still enabled on my phone.
In the device manager on my computer, "SAMSUNG Android USB Modem" and "Unknown Device" are both showing the "problem" icon. I've tried uninstalling and reinstalling various versions of the Samsung USB drivers, I've tried a few versions of Kies, and even a few third-party tweaked USB drivers. It doesn't seem like anything wants to recognize my phone now that is running CM10.1 (or CM10.1 in addition to something peculiar with my installation).
Additionally, if I have USB debugging enabled on my phone, even if I enable USB mounting, the computer won't recognize the mount until I disable debugging mode on the phone. Once I do that, then the volume will appear on my computer. Previously, when ADB debugging in general worked, I wouldn't have to disable debugging to get the USB mass storage mounting to work.
These problems happened at once on all three of my computers that I've been using for Android development, so I'm fairly convinced these issues are directly related to the ROM I'm running. I've attempted to search the forum and Google for others that may have had this issue and what the resolution/work-around might be, but so far I've not found anything. Surely other people are using CM10.1 and developing apps, which makes be believe it could be something unusual with my installations, but I've tried full wipe without a data restore and it didn't seem to have any impact. I've also tried searching to see if there were special drivers needed for CM10.1, and didn't find anything with that either. I know reverting back to an earlier ROM is an option to get ADB working, but I'm really hoping to get ADB working with CM10.1.
Does anyone have any suggestions on what I can check/do to get USB debugging working on CM10.1 (epicmtd)?
Thank you very much for your time
--James
Re: [Q] Unable to use ADB to connect CM10.1/driver issue
I had the same problem, tried absolutely everything I could to get it to work and couldn't... had to roll back to a tw rom to get it to work (not a fan of the HUGE battery drain on cm9)
Edit- I know this doesn't help you, just wanted to point out you're not the only one with this problem....
Re: [Q] Unable to use ADB to connect CM10.1/driver issue
Locate the drivers for your phone on your computer and uninstall them. Then plug your phone in and let the computer reinstall the drivers. I had the same problem (although I wasn't making apps) and my suggestion above worked for me, so hopefully it'll work for you.
Sent from my SPH-D700 using Tapatalk 2
Re: [Q] Unable to use ADB to connect CM10.1/driver issue
jeffreyjicha said:
Locate the drivers for your phone on your computer and uninstall them. Then plug your phone in and let the computer reinstall the drivers. I had the same problem (although I wasn't making apps) and my suggestion above worked for me, so hopefully it'll work for you.
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
Tried this multiple times... it may have actually been a problem with my pc... get it back on Friday, so time will tell...
flastnoles11 said:
Tried this multiple times... it may have actually been a problem with my pc... get it back on Friday, so time will tell...
Click to expand...
Click to collapse
I've tried this with my previous uninstall/reinstall driver attempts, but tried it again anyway.
Unfortunately, it didn't' seem to have a positive impact. It looks like it reinstalled the mass USB storage driver, but it did not reinstall any other drivers (like the modem driver) so I'm still not able to do anything with ADB.
Re: [Q] Unable to use ADB to connect CM10.1/driver issue
Have you tried manually installing the drivers?
Here is the .exe that I used to install the drivers for my phone.
Sent from my SPH-D700 using Tapatalk 2
jeffreyjicha said:
Have you tried manually installing the drivers?
Click to expand...
Click to collapse
Hello again. Yes. I've tried installing various versions of USB drivers floating around the net as well as Kies (after uninstalling and deleting current drivers to try to avoid conflicts). Other versions of Epic ROMs (Stock, CM9, etc.) worked with ADB using my installed drivers until I installed CM10.1 (maybe starting with CM10) on my Epic.
As an aside, using ADB requires some additional (special) drivers beyond the drivers required for mass storage support.
I'm hoping one of the CM10.1 developers will chime in with what they did and/or installed to have ADB working with CM10.1 on Windows 7.
Thanks!
--James
I'm going to update to the most recent build of CM10.1 and see if ADB works for me. If it doesn't work, i'll try reinstalling drivers.
jeffreyjicha said:
I'm going to update to the most recent build of CM10.1 and see if ADB works for me. If it doesn't work, i'll try reinstalling drivers.
Click to expand...
Click to collapse
I don't know what I did differently in my search (I've been trying to find solutions for awhile now). I found this thread:
http://forum.xda-developers.com/showthread.php?t=1817954
I upgraded my Kies to 2.0, which includes the latest drivers from here:
http://www.samsung.com/us/kies/
I still had "Unknown Device" listed in my device manager. Based on that forum thread, I right-clicked on the "Unknown Device", selected "Update Driver", "Let me choose from software installed on computer" and then picked "ADB Interface". A list of a few Samsung ADB entries in it appeared, and I picked one (I had two with the same name, so not sure what the differences are between them) and after a few seconds I had no more alerts in the device manager and when I run "adb devices" I now see a device in the list. I fired up Eclipse to give it a real-world test and it worked: I'm now able to deploy and debug apps on my connected device.
Woot!
I'll be taking these actions on my other computers tonight.
Thank you very much for your assistance.
samej71 said:
I don't know what I did differently in my search (I've been trying to find solutions for awhile now). I found this thread:
http://forum.xda-developers.com/showthread.php?t=1817954
I upgraded my Kies to 2.0, which includes the latest drivers from here:
http://www.samsung.com/us/kies/
I still had "Unknown Device" listed in my device manager. Based on that forum thread, I right-clicked on the "Unknown Device", selected "Update Driver", "Let me choose from software installed on computer" and then picked "ADB Interface". A list of a few Samsung ADB entries in it appeared, and I picked one (I had two with the same name, so not sure what the differences are between them) and after a few seconds I had no more alerts in the device manager and when I run "adb devices" I now see a device in the list. I fired up Eclipse to give it a real-world test and it worked: I'm now able to deploy and debug apps on my connected device.
Woot!
I'll be taking these actions on my other computers tonight.
Thank you very much for your assistance.
Click to expand...
Click to collapse
No problem.
samej71 said:
I don't know what I did differently in my search (I've been trying to find solutions for awhile now). I found this thread:
http://forum.xda-developers.com/showthread.php?t=1817954
I upgraded my Kies to 2.0, which includes the latest drivers from here:
http://www.samsung.com/us/kies/
I still had "Unknown Device" listed in my device manager. Based on that forum thread, I right-clicked on the "Unknown Device", selected "Update Driver", "Let me choose from software installed on computer" and then picked "ADB Interface". A list of a few Samsung ADB entries in it appeared, and I picked one (I had two with the same name, so not sure what the differences are between them) and after a few seconds I had no more alerts in the device manager and when I run "adb devices" I now see a device in the list. I fired up Eclipse to give it a real-world test and it worked: I'm now able to deploy and debug apps on my connected device.
Woot!
I'll be taking these actions on my other computers tonight.
Thank you very much for your assistance.
Click to expand...
Click to collapse
Activating through developer options doesnt help? just go to about phone --> tap build number 7 times
I just went to device manager, uninstalled the failed USB device, and then plugged the phone back to the computer via USB.
Boom, just like that, all was well.
i tried everything and could not connect to my htc rezound (w/ CM10.1) thru adb. then i tried the following:
1. download the android adk from google (i can't post links)
2. connect phone thru usb
3. on your computer's adk download folder, navigate to sdk\platform-tools\
4. press shift + right click on the window, open command window here
5. type "adb devices" in the command window w/o the quotes
6. there should be a window pop up on ur phone asking for USB debugging permission. say OK.
7. type "adb devices" again and you should see ur phone connected thru adb.
I've been spending the better part of the day trying to resolve this problem, including poring through a good chunk of the 200+ pages of the 10.1 Nightlies thread over in development. I've been trying to set up ADB over USB with CM 10.1 however it does not register at all except as a USB mass storage device. I've tried uninstalling drivers and reinstalling them both directly from Samsung in the driver package as well as via Keis, having it auto-detect in Download mode, as well as using the modified INF drivers that have been floating around but nothing seems to work. I've tried right-clicking the four unknown Android devices in the Device Manager to install the aforementioned drivers but nothing seems to take. I've also attempted to follow the instructions at .ttp://itekblog.com/cyanogenmod-10-1-with-adb-tutorial to no avail. The most recent ADB from the SDK doesn't pull it up when listing devices either; please see the attached image.
Any help with this would be greatly appreciated.
You can use adb devices in command prompt and it should show your phone or use clockworkmod app and application for computer will work . Also easy tether pro works need the app on phone and computer as well.
Sent from my SGH-T989 using Tapatalk 2
ADB devices in the command prompt displays no devices as connected. From what I've been able to find, it seems to be a driver problem but I'm at a loss as to how to get it installed correctly. I have CM10.1 as well as TWRP installed and working fine, but I've been trying to do some application development recently and this is a major stumbling block, since if I can't get this sorted out I'll probably end up having to go back to using stock.
Edit: I have since been able to fix it. Here are the steps I followed.
1. Right click on the device in the device manager.
2. Click "Update Driver Software".
3. Click "Browse my computer for driver software".
4. Click "Let me pick from a list of drivers on my computer".
5. Select Manufacturer: Google Inc. and Model: Android ADB Interface.
6. You may receive a warning at this point. Ignore it and click yes.
7. It should be working at this point.
Stromgarde said:
ADB devices in the command prompt displays no devices as connected. From what I've been able to find, it seems to be a driver problem but I'm at a loss as to how to get it installed correctly. I have CM10.1 as well as TWRP installed and working fine, but I've been trying to do some application development recently and this is a major stumbling block, since if I can't get this sorted out I'll probably end up having to go back to using stock.
Edit: I have since been able to fix it. Here are the steps I followed.
1. Right click on the device in the device manager.
2. Click "Update Driver Software".
3. Click "Browse my computer for driver software".
4. Click "Let me pick from a list of drivers on my computer".
5. Select Manufacturer: Google Inc. and Model: Android ADB Interface.
6. You may receive a warning at this point. Ignore it and click yes.
7. It should be working at this point.
Click to expand...
Click to collapse
Is this fix also for my Xperia Mini? I'm using PAC Rom which based on CM10.1 as well and I also can't connect to my phone via ADB
My ADB is working whenever the phone is in Fastboot or Recovery but not when it is fully booted.
I can't find the developer "google inc". I guess i'll have to try some of the other steps that you have taken.
EDIT: i followed this guide even though it is for a Samsung phone and I have a HTC One X
hxxp://itekblog.com/cyanogenmod-10-1-with-adb-tutorial/
Howdy,
I'm trying to get my phone unlocked and rooted. As the first step, of course, I'm trying to get the Google USB drivers to install, but I simply can't. I feel like I'm the only person having this issue, though because I cannot find a solution... The steps I'm following:
Downloaded the latest driver zip from Google
Open Device Manager
Expand Portable Devices
Right-click on the Phone entry (notice, that's the entry, "Phone". Not Razer.)
Choose Update Drivers
Browse my way to the drivers folder and click Next.
Windows then returns immediately "The best drivers for your device are already installed", and shows that it's an MTP USB Device.
I noticed that under USB devices, there's an ADB Interface device listed, and I get the same results when I try to update that, too (excepting it says it's an "ADB Interface" device, of course). I have tried uninstalling both devices to get the drivers to install, but no such. I've rebooted both phone and computer as well.
On the phone, USB Debugging is turned on, and USB mode is set to MTP file transfer.
Please help!
Figured it out...
tkarakashian said:
Howdy,
I'm trying to get my phone unlocked and rooted. As the first step, of course, I'm trying to get the Google USB drivers to install, but I simply can't. I feel like I'm the only person having this issue, though because I cannot find a solution... The steps I'm following:
Click to expand...
Click to collapse
In case anyone else is seeing the same issues, I wanted to put my resolution up: I'd been trying to install the drivers with the Razer booted. On a whim, I rebooted it into Download Mode using "adb reboot bootloader". Once there, I had an Android Device listed in Device Manager. I ran the driver update wizard, and installed the "USB ADB Interface" option from the choices presented. I was then able to run the OEM unlock command and received the confirmation prompt on the Razer. Yay!
Now, since it's been so long, I've got to re-back-up everything so I can actually do this thing. LOL
Here's the PDF from Razer's how to install a factory image over PC guide. It explains how to do it all
s3.amazonaws(.)com/cheryl-factory-images/How_to_Install_Android_Fastboot_Drivers_on_Windows.pdf (remove parantheses)