Before anyone drops a "use the search function first", I hope you provide a link because I have scoured over 200 posts trying to find the answer to this question and its either not there, or EXTREMELY well hidden.
So...ADB worked fine for me on Windows 7 x64, untill I had to uninstall and reinstall some drivers when helping a buddy root his g1.
Now, ADB doesn't work. Whenever I try to run an adb command, even just to list devices, I get this error:
Code:
* daemon not running. starting it now *
CreateProcess failure, error 2
* failed to start daemon *
error: cannot connect to daemon
I have scoured Google, and I haven't found a single post that is android related (there are similair errors on android forums, just not this one) and am sorrily stumped. If anyone can help, I'd be ever so grateful.
This definitely sounds driver related although I'm not sure how you can "roll back" drivers in 7. I've heard that 7 pretty much keeps every driver you've ever used around and for whatever reason it's using an older ADB driver. I'd put money on me being wrong though.
if you are using a 1.5 image, use the drivers from the 1.5 SDK. If you are still on the RC builds, use the drivers in the 1.0 SDK.
win32 error code 2 means: 2 The system cannot find the file specified. ERROR_FILE_NOT_FOUND
and from the source code this is after a call to CreateProcess() and the file name is given by GetModuleFileName(), so it seems that the latter failed in a strange way.
What's the full path to your adb.exe?
billc.cn said:
win32 error code 2 means: 2 The system cannot find the file specified. ERROR_FILE_NOT_FOUND
and from the source code this is after a call to CreateProcess() and the file name is given by GetModuleFileName(), so it seems that the latter failed in a strange way.
What's the full path to your adb.exe?
Click to expand...
Click to collapse
D:\G1\android\tools\adb.exe
No spaces or odd characters. Like I said this worked fine for a month or so before I started ****ing with the drivers. I havent moved anything, my PATH and CLASSPATH are pointed correctly to the right directory. I also have a copy of adb in my /system32 directory (along with we .dll file it needs) so I can run it from wherever at a cmd prompt.
it might have something to do with wow64 messing the path up (it may rewrite system32 to syswow64). try launching the program under D:\G1\android\tools\ path. even if GetModuleFileName() failed, system should still be able to find adb.exe if you're under that path. also check file permissions and antivirus...
you can also try the command "adb fork-server server" in the path that contains adb. (you'll have to leave that console open)
Related
Somebody please help me out of my misery. I followed the rooting directions to the letter, but when I type "adb devices" I get the following error:
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
I'm in the right directory ( AndroidSDK\tools\ ), I have the android driver installed, I have USB debugging checked, I don't understand why this is not working.
Please help me out here.
I had no problem rooting my palm pre, which was infinately more complicated than this.
Thank you in advance.
flaav8r said:
Somebody please help me out of my misery. I followed the rooting directions to the letter, but when I type "adb devices" I get the following error:
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
I'm in the right directory ( AndroidSDK\tools\ ), I have the android driver installed, I have USB debugging checked, I don't understand why this is not working.
Please help me out here.
I had no problem rooting my palm pre, which was infinately more complicated than this.
Thank you in advance.
Click to expand...
Click to collapse
had a pre and "rooted" it as well..... using putty is more complicated that this but this is a little more like hacking... whereas on the pre you are just accessing root rather than breaking into it.
anyway... try these
nstall htc sync from htc's website, can you sync?
run cmd as administrator
cd untill you are in the same directory as your adb
type "adb devices"
does it display your hero?
type "adb shell"
does is display "$" ?
johnsongrantr said:
had a pre and "rooted" it as well..... using putty is more complicated that this but this is a little more like hacking... whereas on the pre you are just accessing root rather than breaking into it.
anyway... try these
nstall htc sync from htc's website, can you sync?
run cmd as administrator
cd untill you are in the same directory as your adb
type "adb devices"
does it display your hero?
type "adb shell"
does is display "$" ?
Click to expand...
Click to collapse
Yes, I can sync with HTC Sync. When I do the adb devices I get the error I described above and I cannot do adb shell because I cannot communicate via android sdk.
flaav8r said:
Yes, I can sync with HTC Sync. When I do the adb devices I get the error I described above and I cannot do adb shell because I cannot communicate via android sdk.
Click to expand...
Click to collapse
windows 7? VISTA? XP?
restart phone/computer
unplug/plugin usb
also find another copy of adb.exe i heard there's a old copy floating out there that doesn't reccognize the hero for some reason but if you got it from a guide you shouldn't have a problem.
download sprint RUU and wipe your phone (if it will connect) also if you want to dig down the ruu has a working adb.exe twisted into their install they dump in your %TEMP% folder
johnsongrantr said:
windows 7? VISTA? XP?
restart phone/computer
unplug/plugin usb
also find another copy of adb.exe i heard there's a old copy floating out there that doesn't reccognize the hero for some reason but if you got it from a guide you shouldn't have a problem.
download sprint RUU and wipe your phone (if it will connect) also if you want to dig down the ruu has a working adb.exe twisted into their install they dump in your %TEMP% folder
Click to expand...
Click to collapse
Windows XP, and I got the files from this site and androidsdk from the google site linked from theunlockr.com.
flaav8r said:
Windows XP, and I got the files from this site and androidsdk from the google site linked from theunlockr.com.
Click to expand...
Click to collapse
try this known good version
http://forum.xda-developers.com/attachment.php?attachmentid=244916&stc=1&d=1257827184
johnsongrantr said:
try this known good version
http://forum.xda-developers.com/attachment.php?attachmentid=244916&stc=1&d=1257827184
Click to expand...
Click to collapse
I tried the new files, and still got the exact same error.
well i'm out of ideas.... and i'm tired.... anyone else throw a little help this guy's way?
if by tomorrow you/they haven't figured it out I'll see if I can't think of something else for ya
johnsongrantr said:
well i'm out of ideas.... and i'm tired.... anyone else throw a little help this guy's way?
if by tomorrow you/they haven't figured it out I'll see if I can't think of something else for ya
Click to expand...
Click to collapse
Thank you for your help. Greatly appreciated.
The ADB server binds and listen to port 5037. If that port is taken and/or if the daemon is already running, you'll see that error message.
Start task manager and kill adb.exe (all the instances of it).
If that don't work, try rebooting your computer and your phone, and trying again.
If it still don't work, try this:
http://groups.google.com/group/android-developers/msg/dfae5da4a3c80aa8
simplyphp said:
The ADB server binds and listen to port 5037. If that port is taken and/or if the daemon is already running, you'll see that error message.
Start task manager and kill adb.exe (all the instances of it).
If that don't work, try rebooting your computer and your phone, and trying again.
If it still don't work, try this:
http://groups.google.com/group/android-developers/msg/dfae5da4a3c80aa8
Click to expand...
Click to collapse
I'm gonna give it a shot right now.
simplyphp said:
The ADB server binds and listen to port 5037. If that port is taken and/or if the daemon is already running, you'll see that error message.
Start task manager and kill adb.exe (all the instances of it).
If that don't work, try rebooting your computer and your phone, and trying again.
If it still don't work, try this:
http://groups.google.com/group/android-developers/msg/dfae5da4a3c80aa8
Click to expand...
Click to collapse
Haha, success. I'm gonna try and root it now.
Thank you so much.
flaav8r said:
Haha, success. I'm gonna try and root it now.
Thank you so much.
Click to expand...
Click to collapse
Np glad to help
simplyphp said:
Np glad to help
Click to expand...
Click to collapse
Sucussfully rooted, thanks again.
Sorry for reviving an ancient post, but I just wanted to say that I ran into the same issue and opening up "taskmgr" and killing the active instance of "adb.exe" resolved the issue.
Just for help :
I had the same issue and it was my Firewall which blocked the starting of deamon.
Turn off your Firewall can fix the problem
cheers guys, followed the instructions and flashed rec. radio
This solved it for me: edit adb_usb.ini
This solved it for me:
Edit ~/.android/adb_usb.ini file to make sure that there is no extra empty line after the 0x0006 line entry
For other users: I also found this:
After killing ADB.exe run netstat (just "netstat", no parameters) and
see if port 5037 is opened. It probably will be. Wait a while. Run
netstat again, now there are less connections on the port. After a
port 5037 is no longer opened. Only then it's OK to run ADB again.
Please note that this worked for when I killed the ADB.exe process &
process tree from Sysintenal's Process Explorer.
Also, I still don't know why running ADB again before all connection
are closed led to the port never being freed (albeit netstat didn't
show any open connections anymore). Moreover, the problem that forced
me to kill ADB in the first place needs to be solved and there's
enough on that in the forum.
AsafR.
Click to expand...
Click to collapse
Problem is HTC Sync
lucbloom said:
This solved it for me:
Edit ~/.android/adb_usb.ini file to make sure that there is no extra empty line after the 0x0006 line entry
For other users: I also found this:
Click to expand...
Click to collapse
HTC Sync Manager has adb.exe at location C:\Program Files\htc\htc sync manager\htc sync\adb.exe
You have 2 options now:-
1) Delete this adb.exe
2) Copy latest adb.exe from android sdk to this path.
Note: You need to make the 2 copies of adb.exe in sync always(when android sdk is updated) else this problem will come up again.
On windows 7, you can make a link of adb.exe from android sdk to this folder, which will avoid copying manually.
C:\> cd "C:\Program Files\htc\htc sync manager\htc sync"
C:\Program Files\htc\htc sync manager\htc sync\> mklink adb.exe C:\<path to your sdk>\platform-tools\adb.exe
kill htc sync
nevermind someone already posted
trying to root 2.1 sprint hero, had the patched .6 version but redownloaded the .5 version on my phone, now says 2.27.651.5! Good right? Then I'm trying the regaw method for rooting. Downloaded the sdk, downloaded HTC Sync 2.0.33, downloaded hero-root. Renamed them to C:\android-sdk-windows\tools, went to the command prompt and typed it in. Then I type in adb devices and I get an error: adb not recognized as an internal or external command, operable program or batch file. I've checked debugging, and still get same error. Deleted files and redownloaded everything again and STILL get same error. Any help would be much appreciated
make sure you cd to that directory, or you can click-n-drag adb.exe (adb-windows.exe in some cases) into your CMD promt and type your command after... Little work around for odd computer setups
EDIT - you could also try to append the ".exe" at the end, i.e. >adb.exe devices
Thanks, I gave it a try! Still nothing,
Did you run the setup or did you just download, extract, and then run straight to CMD? try running the setup, don't download anything if you don't want to, and then try again.
I must be an idiot, the folder size is 54.2 mb. I'm at a loss. I will continue trying!!!!
Ok, total noob here! I've been at this for a while now and still can not get adb devices to recognize my phone. Device manager says everything working properly, drivers installed properly. I have searched and searched for an answer and still I can"t find one. Is there something I am doing wrong or have I not set up. All I want to do is root my phone, any answers would be a godsend.
Solved:
thanks to a good friend of mine he directed me to this file on GRP dev-site
http://greenromproject.com/showthread.php?269-ADB-The-Easier-Way
open this file in ubuntu software manager, let the package install and reboot system, then adb should work in any directory
Original Post:
ok guys i really didn't want to do this... i followed over 6 different guides now and am getting confused.. there too many methods and they all do not work.... i keep getting .../adb no such file or directory
i spent the last 2 days trying to set up adb on my 10.10 ubuntu, 64-bit system... i edited the bashrc file with the correct path, even typed it in myself because of known issues with ' " ' those things.. i also made the 71-android.rules file with about 3 different variations of this
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
reboot the system, i ran adb kill-server and sudo adb start-server and im still getting message saying .../adb no such file or directory...
only thing i can think of to cause an issue is i updated the system, (not upgrade to 11.04) only update!! installed java jdk and all the needed parts for compiling roms... but just cant seem to get adb working
has anyone else had this type of issue or know how to solve it...? sdk version r12
please someone help
Click to expand...
Click to collapse
...
i keep getting .../adb no such file or directory
...
Click to expand...
Click to collapse
If you get this message, there is no need to look for autoconfig rules or something else, you need to check your path. Try to type
Code:
which adb
if adb cannot be found, you should do a
Code:
export PATH=$PATH:<path to your adb directory>
after that you should be fine for starting adb. If you would like to have it in your path permanently, you shoud add the line above to you .profile file in your home directory.
yeah i already did all that... added the correct path and everything... i tried all these diff methods and none worked, and none were even close to the same as far as what to add to bashrc and the rules.. but i got the issue solved thanks to a file i installed via update manager... rebooted system and adb worked fine
Hi all,
I had built my own Nook-color on a Ubuntu machine before and I finally get around to have a VM based on the latest Ubuntu 14.02.
I followed most of the instructions here: http://wiki.cyanogenmod.org/w/Build_for_ovation.
When I get to the ./get-prebuilts, I got an error that the file doesn't exist, and this maybe my issue. I ignored this error and continue down the path.
Now when I do the "./extract-files.sh' part, I am getting the "device not found' errors.
I have the device plugged in, and when it does, the VM popped up the device folder (SD etc.), so I assume at least the device was recognized by the system.
If I ran "adb devices", it shows a empty list, so what gone wrong? (My HD+ has the adb enable and the icon showed up on the top left corner.
I'd searched the forum and found no solution related to mine.
Any help is appreciated.
Instead of extracting prebuilts (requires adb), add the Muppets proprietary vendor to your local_manifests (or just download and place in vendor/bn).
https://github.com/TheMuppets/proprietary_vendor_bn
Thanks Jon.
Actually I already have those files in the folder.
After searching the net for answer, I finally found the problem. It is that the usb's ini file in the ~/.android folder is empty, I need to add the BN's vendor id (x2080) to it. I also need to set its ANDROID_SDK_HOME to the PATH.
My problem doesn't stop me from making the build, but it will prevent me from using the adb for debugging down the line.
First of all, kudos to jcs for this op. While fairly new at this, I found it very complete. I had to do alot of reading and downloading behind the scenes to get it this far, but so far everything has worked.
As the title suggests, I am stuck on step 7c, in particular where I am trying to run "novacom....certs.sh". I am using ubuntu and had to load "Wine" to get it to recognize the "palmenv.bat" file. So, is there an easy way to run the "nova...." file in ubuntu? Other than finally figuring out how to get and use java in ubuntu, I've been very impressed with that OS.
Here is the error message:
Z:\home\mds\Downloads\WebOS>novacom run file:///bin/sh < fix-webOS-certs.sh
File not found.
The "Z" directory was the result of running the "wine cmd" as the directory originally was "C". Initially after running the "wine cmd" command, I ran the "palmenv.bat" and it accepted it. However, I was unable to run the "novacom...certs.sh" file, even though it was in the same location.
PS: I have deleted and added spaces in combinations around "<" in the above as I could not tell for sure the correct way.
golfnut22 said:
First of all, kudos to jcs for this op. While fairly new at this, I found it very complete. I had to do alot of reading and downloading behind the scenes to get it this far, but so far everything has worked.
As the title suggests, I am stuck on step 7c, in particular where I am trying to run "novacom....certs.sh". I am using ubuntu and had to load "Wine" to get it to recognize the "palmenv.bat" file. So, is there an easy way to run the "nova...." file in ubuntu? Other than finally figuring out how to get and use java in ubuntu, I've been very impressed with that OS.
Here is the error message:
Z:\home\mds\Downloads\WebOS>novacom run file:///bin/sh < fix-webOS-certs.sh
File not found.
The "Z" directory was the result of running the "wine cmd" as the directory originally was "C". Initially after running the "wine cmd" command, I ran the "palmenv.bat" and it accepted it. However, I was unable to run the "novacom...certs.sh" file, even though it was in the same location.
PS: I have deleted and added spaces in combinations around "<" in the above as I could not tell for sure the correct way.
Click to expand...
Click to collapse
Did you fully read post #2, part C of the TPTB thread? You should be able to just unzip the TPTB into a folder, open a terminal session in that folder, and run the .sh file that's there. You may need to run it with sudo; that I don't recall.
shumash said:
Did you fully read post #2, part C of the TPTB thread? You should be able to just unzip the TPTB into a folder, open a terminal session in that folder, and run the .sh file that's there. You may need to run it with sudo; that I don't recall.
Click to expand...
Click to collapse
Yes thanks. The problem boils down to running a ".bat" file then running a ".sh" file. Using Ubuntu, I have been unable to run the .bat file without "wine", then, in "wine", I have been unable to run the ".sh" file.
In windows 7, I can run the ".bat" file, but unable to run the ".sh" file. This is the final step in jcs's op to do a clean install of webos and this particular step fixes the certificates. Ref here step 7d: http://forum.xda-developers.com/showthread.php?t=2756314&page=7
Ubuntu command:
sudo ./tptb_v42_nix.sh
You have to be in the same directory where tptb is...of course the listed command is for version 42.
The .sh file is for Linux not for windows. You cannot run it in "wine".
golfnut22 said:
Yes thanks. The problem boils down to running a ".bat" file then running a ".sh" file. Using Ubuntu, I have been unable to run the .bat file without "wine", then, in "wine", I have been unable to run the ".sh" file.
In windows 7, I can run the ".bat" file, but unable to run the ".sh" file. This is the final step in jcs's op to do a clean install of webos and this particular step fixes the certificates. Ref here step 7d: http://forum.xda-developers.com/showthread.php?t=2756314&page=7
Click to expand...
Click to collapse
You're not getting the message. You don't run the batch file in Ubuntu; it's for Windows only. Follow the above post's advice (note the period before the /. It's essential).
shumash said:
You're not getting the message. You don't run the batch file in Ubuntu; it's for Windows only. Follow the above post's advice (note the period before the /. It's essential).
Click to expand...
Click to collapse
Ok gotcha. I will try it again. Thanks
shumash said:
You're not getting the message. You don't run the batch file in Ubuntu; it's for Windows only. Follow the above post's advice (note the period before the /. It's essential).
Click to expand...
Click to collapse
golfnut22 said:
Ok gotcha. I will try it again. Thanks
Click to expand...
Click to collapse
So, below is an exact copy (ctrl c, then ctrl v) from page 7 of jcs' op for reinstalling webos.
then run "palmenv" and then run "novacom run file:///bin/sh < fix-webOS-certs.sh"
Just got back on this project again and have a follow-up question.
From your comment above, I need to add a period here either before the "///" or ".///" slashes or after "bin" or "bin./"?
Here is also a direct copy out of the text file of "fix-webOS-certs.sh"
novacom run file:///bin/sh < fix-webOS-certs.sh
So, neither place has a period before either of the /'s as you mentioned. Please advise...thanks again.
Thanks and Sorry, I did not see the previous post to yours. In the meantime, I did run it again without knowing where to put the period and I am a little closer to completing the reinstall...but still don't know why I can't get the last line "novacom run file.....certs.sh" to run.
I redid every step again on the tp and got to the screen where you select the "language". I then opened up the command prompt in windows 7, tp still connected, cd'd until I got to the directory where both "palmenv" and "novacom run file..." is located. I ran "palmenv" and got "Setting Novacom Path ....".
I then immediately ran the "novacom run file....." and got "unable to find device".
I checked my device manager under disk drives and the "HP Webos-usb device" was listed with no flags.
I tried it again, but same message.
One other comment on the "novacom run file....". In windows, when I hit the download button on the "goo" website, it actually opens up. In order to download, I had to select all, paste it in notepad, open up notepad and save as the ".sh" file. So, I don't know if that is screwing something up or not. Otherwise, it would not down load or I would not have it. Strangely, it did download in Ubuntu, but that file did not work either.
So, any advice on how I can complete the very final step on running the "novacom run file....certs.sh"?
gtallmadge said:
Ubuntu command:
sudo ./tptb_v42_nix.sh
You have to be in the same directory where tptb is...of course the listed command is for version 42.
The .sh file is for Linux not for windows. You cannot run it in "wine".
Click to expand...
Click to collapse
Thanks. I had thought the .sh file was for Ubuntu, but I received a message that said those sequence of commands from jcs was to be run in windows. Anyway, I believe the above instructions are how to get the tptb running in Ubuntu. If so, that is not the problem. If not, then from that and other messages received, I would run the .bat file from windows, reboot my system and then run the .sh file in Ubuntu adding "sudo ./ to the "novacom run file:///bin/sh < fix-webOS-certs.sh"?
So, for a recap, per jcs's op, one would open the command prompt in windows, and cd to the correct directory where the palmenv,bat file and fix-webOS-certs.sh reside. Then run "palmenv" the run "novacom run file:///bin/sh < fix-webOS-certs.sh" file.
For some reason, I doubt he was suggesting changing from windows to Ubuntu when running these commands, but I may be wrong...as I often am.
I know I'm dumber than a hay rake, but really, can someone please explain in detail for this newbie, what he needs to do to run both of those commands? Refer to a previous post link if unfamiliar with what op I'm trying to perform...and am on the last step 7d
I think the issue is that you are trying to install WebOS.
Not sure of the help you are going to get with that as many of us have moved on a while ago and no
longer have the interest in it. You might want to check on other threads where it is relevant.
gtallmadge said:
I think the issue is that you are trying to install WebOS.
Not sure of the help you are going to get with that as many of us have moved on a while ago and no
longer have the interest in it. You might want to check on other threads where it is relevant.
Click to expand...
Click to collapse
Yes, that is what the procedure does that jcs has outlined. And thanks for the reply. I have got webos installed which was the easy part, however, running the last two commands appear to be a matter of proper input...which several advices have been given, but none have worked. I was hoping that someone, other than the author of the procedure, had tried it or at least someone may be familiar enough with this type of input to help. Oh well, thanks again.
Progress with novacom run file:///bin/sh < fix-webOS-certs.sh
Was able to finally run novacom run file:///bin/sh < fix-webOS-certs.sh after previously receiving unable to locate device message by booting HP Touchpad into developer/USB mode and running novaterm.bat from the terminal folder and connecting from the menu. I was then able to run novacom run file:///bin/sh < fix-webOS-certs.sh from the Command Prompt but it does not appear to have run successfully.
C:\Program Files\Palm, Inc>novacom run file:///bin/sh < fix-webOS-certs.sh
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
FAILED: rc=${rc}: ${@}
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
FAILED: rc=$rc: ((create /tmp/asb.crt))
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
FAILED: rc=$rc: ((create /t1/pssb.crt))
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
OK
I am trying everything I can to get the HP Touchpad wifi working after having done a complete wipe before a system restore and learning the HP Servers are no longer supporting. I have Cyanogenmod 11 installed and wifi worked for approximately one day after each install. When I try to connect to any access point it only says "saved" afterward and the signal seems to drop to zero while connecting. Another strange occurrence is the fact that the wifi mac address that shows in the advanced menu of Cyanogenmod does not match the previously saved mac address on my home wifi set up as an extra security measure. The mac is the same in the device info menu of WebOS when trying to install but getting the message that servers can not be accessed to finish the install. When it was connected for a short time after Cyanogenmod install the MAC address was correct but since it has changed will not connect and the new address gives an unsupported message when trying to add to my network devices list. I have tried all posted troubleshooting steps as well as having installed Busy Box and attempting to change the Mac address manually. I get operation not supported at that prompt in the Terminal Emulator on the Touchpad. Has anyone come across this or been able to get their HP Touchpad working properly with Cyanogenmod 11?