Hello! I tried to help, the guys that are making the CM9, and i want to give them the LOGCAT info. The problem is that, on win 7, the device isn't recognised. So I need a tutorial for Ubuntu. Thank's!
Why isn't your device recognized in Windows?
Try to remove any leftover cellphone-related drivers that might interfere, uninstall Kies, or at least make sure it is shutdown completely.
Extract the Samsung USB drivers installer from the Kies installer and install only those.
Make sure your Android SDK install is correct, and debugging enabled on the phone. I suggest you add the various SDK tools to your PATH environment variable too, since this will make your life much easier.
You can also use DDMS to access the logcat information.
Good luck,
Darkshado
Hello! On windows, since I move to the 7.2 rom, only appears 3 points on the remove device area. I install KIES 3 times so...
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
Hi guys
I did own a Sapphire/Magic back in the days and came back to Android after some skipping done during the last year. Back then installing usb drivers and adb was easy: plug in the Sapphire, point Windows to the drivers folder, done.
With the Vision/Desire Z it was much more complicated. I did use the old drivers from back then and ran into problems. Device manager had an ADB device listed, ADB couldn't find it though. Once I got it working in Android, it wouldn't interface with the recovery adb though. Once I got that working, it wouldn't show/mount the SD card anymore. Short: a huge mess.
Right now I have everything more or less working (still using the old drivers I used with the Sapphire) but it's not really right, I tried an RUU the other day and it would fail because my ADB/RUU ADB/Driver combination wouldn't match.
Long story short: where did you guys get your drivers from to interface the Vision with ADB/Fastboot?
Update the SDK ...this time its in platform tools. run the sdk update and download the usb drivers. Refresh your SDK.
If you don't want to do that...then install pdanet just to grab the drivers
Or go to cyanogenmod the drivers may be avail in a post from ciwrl in vision.dz download section.
All right, I'm d/ling the Java JDK as prompted by the latest SDK installer
Thanks!
I did this too (SDK + Platform tools) to get ADB/shell. However, I never got fastboot to work (even tried fastboot-mac). Not sure what I was missing, but flashing via SD (including radio) has been working thus far for me. Any recommendations on where to get more info on "fastboot" process, specifically on a Mac?
Hmm... you did notice that the fastboot binary is - at least on Windows - in a different folder than ADB, right?
On Windows its two different paths pointing to either ADB or Fastboot.
[posted on the go]
I am having problems with my EPIC 4g Touch and my desktop connecting properly to be able to transfer files and such (Code10).
USB Debugging is on and the latest Epic4g Touch Drivers are installed from the Samsung Site.
Upon Connecting my Phone (Regardless of which port or cable), i get the following
Uploaded with ImageShack.us
If i disable both of the composite devices and then enable them manually, the majority of the time they will work and show up in my computer as drives This doesn't occur on other computers, i am assuming its some sort of driver issue ?
Help would be appreciated.
Pete
Win7 64Bit OS.
pasta1234 said:
I am having problems with my EPIC 4g Touch and my desktop connecting properly to be able to transfer files and such (Code10).
USB Debugging is on and the latest Epic4g Touch Drivers are installed from the Samsung Site.
Upon Connecting my Phone (Regardless of which port or cable), i get the following
Uploaded with ImageShack.us
If i disable both of the composite devices and then enable them manually, the majority of the time they will work and show up in my computer as drives This doesn't occur on other computers, i am assuming its some sort of driver issue ?
Help would be appreciated.
Pete
Win7 64Bit OS.
Click to expand...
Click to collapse
Have you tried installing Kies?
See this post:
http://forum.xda-developers.com/showpost.php?p=19443755&postcount=142
The section about changing the location for driver install on 64-bit machines.
It might help.
I have tried reinstalling the drivers and correcting the install path as mentioned for a 64bit os as well as attempting Kies software package.
Similarly both result in...
Uploaded with ImageShack.us
Is there a way i can completely remove all android drivers off my comp and install them freshly ?
pete
pasta1234 said:
I have tried reinstalling the drivers and correcting the install path as mentioned for a 64bit os as well as attempting Kies software package.
Similarly both result in...
Uploaded with ImageShack.us
Is there a way i can completely remove all android drivers off my comp and install them freshly ?
pete
Click to expand...
Click to collapse
You can see if there is an package to uninstall under add/remove programs or you can try using system restore to go back to an earlier point before you started installing the drivers.
I've been able to randomly replicate this problem on my epic and have not been able to figure out how to fix it. I ended up setting up a virtualbox VM with 32bit windows and it works fine. When I do a 64bit VM it works sometimes, and others not.
I have Uninstalled all of the Android items in device manager and used control panel add/remove programs to remove the Samsung Drivers with little changes to the behavior.
I am looking for a better way to clean out the driver installs ? ?
Pete
I need help! FKU 0.9.5. Drivers set. Kindle is seen by the system (Windows) as Android Phone\Android Composite ADB Interface . When you run status of the ADB is offline, the status of unknown boot. FKU ustonovlena in C / FKU. What is the problem?
Thanks in advance for your help.
sergei pan said:
I need help! FKU 0.9.5. Drivers set. Kindle is seen by the system (Windows) as Android Phone\Android Composite ADB Interface . When you run status of the ADB is offline, the status of unknown boot. FKU ustonovlena in C / FKU. What is the problem?
Thanks in advance for your help.
Click to expand...
Click to collapse
Ustonovlena? What is that? Serbian? Nevertheless. Even when Windows says the drivers are installed, if adb doesn't connect, it's a driver issue. Uninstall and delete your current drivers then reinstall with the device turned off. When you turn the device back on, KFU should recognize it.
If not, try to issue the command you need anyway. Sometimes it will work anyway. Either way, it is a driver issue. Keep working at it. You may have to reboot your computer to get it to work but as long as you understand that it's the drivers causing problems, you should be able to get it working.
try to change to another user,or worst still use another pc.
Not sure if this can work,but its worth a try since mine work this way.
Sorry. I am writing through Google. Russian. Already endured, and once again put the driver. It did not help.
What rom are you using?
Rom?
If I understand you correctly, a native Amazon 6.3.
The reason I ask is that some custom roms have USB debugging turned off by default and others have trouble with adb to begin with.
But, considering that is not the case, it is a driver issue, plain and simple.Just keep trying. Uninstall/delete/reinstall your drivers. It may help to get the Android SDK and configure them yourself.
It has been repeatedly reinstalled the driver. It does not help. Tried on two computers (XP and Vista). The result is the same. The question-whether the Kindle can be seen in My Computer? I have Windows does not see it.
Programmes at the request of the developer to KFU (Vashypooh) to help. Write in the subject can not have enough rights-http://forum.xda-developers.com/showthread.php?t=1399889.
I beg to inform him of my request for help.
Im having the same issue
I cant tell you how many times i have re installed the drivers. Reboots in between.. u name it
One time i did get adb to see my device. But it still wouldn't fast boot
Im on 2.2.. its a brand new refurb..got it today
Sent from my DROID RAZR using XDA
What type of drivers are there for the S3?
I understand that you need drivers installed on the computer for it to reecognize the S3
How many driver are there?
Are there any more aside from this?
Where can i download these drivers?
I think ADB has a driver for thisas well?
Thanks!
mikoal said:
What type of drivers are there for the S3?
I understand that you need drivers installed on the computer for it to reecognize the S3
How many driver are there?
Are there any more aside from this?
Where can i download these drivers?
I think ADB has a driver for thisas well?
Thanks!
Click to expand...
Click to collapse
Here is the link to the Driver package for i747 and i747m (AT&T/Bell/Rogers/Telus) With this, you don't need Keis...unless you want to use Keis. Also, TRY a WINDOWS UPDATE after installing this driver package.
I found their to be side issues on my Win7 and XP pc's....too long a story. If you have issues, I will send you a link.
themadproducer said:
Here is the link to the Driver package for i747 and i747m (AT&T/Bell/Rogers/Telus) With this, you don't need Keis...unless you want to use Keis. Also, TRY a WINDOWS UPDATE after installing this driver package.
I found their to be side issues on my Win7 and XP pc's....too long a story. If you have issues, I will send you a link.
Click to expand...
Click to collapse
Thanks mad producer. Is this driver package all the drivers I'll need?
I noticed these drivers are from the samsung site.
Are there any custom drivers or drivers for rooted phone, on custom roms etc?
Are there different kinds/type, I recall reading about ADB drivers or ADB connections.
Can you also send me the link to the issues with the drivers?
Thanks a bunch!
mikoal said:
Thanks mad producer. Is this driver package all the drivers I'll need?
I noticed these drivers are from the samsung site.
Are there any custom drivers or drivers for rooted phone, on custom roms etc?
Are there different kinds/type, I recall reading about ADB drivers or ADB connections.
Can you also send me the link to the issues with the drivers?
Thanks a bunch!
Click to expand...
Click to collapse
If/when you need ADB (I don't use it) then just look around for ADB. I don't have a link for that.
When I first connected my S3 to my Win7, XP, 2nd XP machine, each one had an issue with the MTP protocol. This is what's used to transfer files to and from phone internal and external storage. I did my homework and massive experimenting and solved the issues. (pretty pathetic really) I just don't have a turn key absolute solution but here are some tips. Try one or all of these till it works...and it WILL!
(Backup your PC before attempting and use at your own risk)
XP
- plug your Ss in via usb
- install the samsung drivers
- after any/each of these steps, unplug/replug usb S3 to PC
- check Device Manager in XP for any Yellow exclamation marks. If there are none, then go see if you can transfer large files (eg mp3) to your S3 and back via USB
- if you can then your done
- if not, download this and install
- if it's still not working, (which I doubt) then update windows. After the Samsung drivers are installed on some windows machines, windows updates provides a specific update that helps. I watched it happen/work on 2 machines.
- still not working, get ready....sounds crazy...but install Windows Media Player 11. It is tied into the MTP framework somehow. This is the version I used
Win7
- plug your Ss in via usb
- install the samsung drivers
- after any/each of these steps, unplug/replug usb S3 to PC
- check Device Manager in Win7 for any Yellow exclamation marks. If there are none, then go see if you can transfer large files (eg mp3) to your S3 and back via USB
- if you can then your done
- if it's still not working, (which I doubt) then update windows. (remember to unplug/replug usb after.
- install wmp11 or higher
- if it's still not working, try this file (sorry...can't elaborate on it)
- STILL NOT WORKING...doubt it...but last chance, download this file and place it into c/windows/inf directory and reboot.