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
Once i got my new nook color i rooted it with auto nooter, and im running 1.0.1, on my previous nook i rooted it and adb worked right then, now i cant get adb access, im using the same computer and everything, all thats diferent is its a new nook. I have full root access and can install apps and everything. Any help?
Seems to be a common problem. You can launch NookColorTools and fix it temporarily. Go to "Development" and then unchecked and then recheck the USB Debugging box.
Ok I've been doing that for a while and finnaly got the message that USB debugging is only for development. It works now......
Sent from my LogicPD Zoom2 using XDA App
Get ADB wireless, it works great.
I've had zero luck using usb adb, but adb wireless works great!
I was having similar issues so after many many attempts I just decided to go with adb wireless and would definitely recommend going that route if you can't get it working over usb.
Yeah, getting ADB to work requires a lot of uninstalling/reinstalling drivers and unplugging/replugging the device, it's very temperamental.
can someone link me to a link on how to use/setup adb wireless
beezy69 said:
can someone link me to a link on how to use/setup adb wireless
Click to expand...
Click to collapse
https://market.android.com/details?id=siir.es.adbWireless
it's free in the market and once you download it set up is easy. i've used it through my mac terminal as well as through ubuntu. like the posters above i had the hardest time getting adb to work via usb.
chemical1der said:
https://market.android.com/details?id=siir.es.adbWireless
it's free in the market and once you download it set up is easy. i've used it through my mac terminal as well as through ubuntu. like the posters above i had the hardest time getting adb to work via usb.
Click to expand...
Click to collapse
is there any tutorials on how to use it and what commands i need to install apps?
beezy69 said:
is there any tutorials on how to use it and what commands i need to install apps?
Click to expand...
Click to collapse
once you've installed adb on your computer type "adb" at your terminal prompt and you should list of commands there.
here's the link to Android Developer's ADB website (this also lists commands):
http://developer.android.com/guide/developing/tools/adb.html
files and installation directions can be found here:
http://developer.android.com/sdk/index.html
Good luck!
Ok so me being my dumb self forgot to install the adb drivers for the nook....... im dumb haha, but i cant get them to install, every time i uninstall the mass storage driver so i can install the proper driver it automatically re-installs it....... HELPPPPPPP
Is there any way to download this to the SD and install it from there? I've upgraded to a version of froyo, which doesn't have the market, and my command line won't work after swapping nooks.
I can't seem to get mine to work with either adbwireless or via usb.
Using USB I get this:
C:\android-sdk-windows\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\android-sdk-windows\platform-tools>
Here is what I get if I try to connect using adbwireless:
C:\android-sdk-windows\platform-tools>adb connect 192.168.2.4:5555
already connected to 192.168.2.4:5555
C:\android-sdk-windows\platform-tools>adb devices
List of devices attached
192.168.2.4:5555 device
C:\android-sdk-windows\platform-tools>
But it doesn't show a serial number like all the HowTo's says it should. What am I missing?
EDIT: HALLELUJAH!!
I fixed it. Actually I didn't fix it, I just followed some instructions from another user that was having the same problem and finally figured out the very weird thing that installing the drivers did. Anyway, here is the solution from hacku:
Originally Posted by hacku View Post
Thanks for this...
EDIT 1:
I followed your instructions to a T and I still can't get ADB to see my NC. After uninstalling all instances of Nook in my device manager, unplugging it and plugging it back in, it adds all the same devices:
Under Disk Drives it lists B&N Ebook Disk USB Device (twice)
Under Portable Devices it lists MyNookColor
Under USB Controllers it lists USB Mass Storage Device
My PC is Windows 7 Ultimate 64bit. Running Nook Color 1.1.0 rooted and overclocked to 1.1Ghz. Any help will be greatly appreciated.
EDIT 2:
So I decided to pull the MicroSD card to simplify things. Uninstalled all instances of Nook from Device Manager and scanned for new hardware. This time I noticed that Windows detected it as a Nook, but then would install the drivers and it would show the same USB Mass Storage Device and the two instances of B&N Disk USB Device. I also noticed that by uninstalling the driver of the USB Mass Storage Device automatically deleted the other two instances under Disk Drives. So I updated the USB Mass Storage Device driver and this time I was able to install the drivers provided, but now it only shows up as an Android Phone > Android ADB Interface (not Composite), but I'm still not able to see it under adb devices.
Help?
EDIT 3:
GOT IT WORKING!!!
For those of you having this same problem this is what I did:
1. Right Click Android ADB Interface (it won't say Composite)
2. Select Update Update Driver Software
3. Click on Browse My Computer For Driver Software
4. Click on Let me pick from a list of device drivers on my computer
5. In the box that pops up click on USB Composite Device
6. Click Next
It now installed the USB Composite Device driver and changes your Android Phone to Android Composite ADB Device.
Open up Command Prompt and type adb kill-server then adb devices and your Nook Color will now show up.
Hope this helps some of you out.
This thing really needs to be pinned somewhere, preferably with IOMonster's first post. There's so many of us starting on this from scratch not able to get adb to see the device. har02's crosspost of hacku's post is what finally got it to work for me. there's a ton of junk out there that just doesn't make sense, and the installing the second driver on the "android interface" is a step that is completely missing from just about every post on this topic.
Aside from that, this forum is what got me buying a nook and happily learning all sorts of cool new things!
THANK you so much har02052, this marks the end of a 6 hour nook-fixing marathong....ahhhhh
so, stupid question time.
i've used ADB in the past and its worked great so not sure whats going on this time around.
I get the following errors when trying to start adb:
"daemon still not runningerror: cannot connect to daemon"
I have installed moto drivers for droid 3 (32bit), im on win7 32bit. I have my phone on dev mode, and charge only. I have run CMD with admin rights. and still ADB wont turn on.
I have also tried using the new one click method:
http://rootzwiki.com/showthread.php?t=3714&p=75934
anyone have some direction? I did kill adb from my running processes (all instances) and tried all over, no go, same error.
help?
Did you put the phone is PC Mode as opposed to USB Mass Storage?
its supposed to be done in Charing only mode, the issue isn't on my phone setup, it got to do with my darn computer, I can even do an adb devices command... may have to remove the sdk completely and start over.
Put in charge only, use one click method
Sent from my DROID3 using xda premium
did you change directory in cmd to the folder that adb is in?
...I had to change to the folder like this cd\program files (x86)\android\android-sdk\platform-tools
The one-click root method is bundled with adb.exe. Except for the driver and a USB cable, it contains everything needed to root.
Try to root my LG Optimus 4X HD and the cmd window say:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: more than one device and emulator
Well.. Thats scared me. Now, my phone is soooo slow, I could uninstall the System Backup Test, but, my phone still very VERY slow.
Please, help me :crying:
TomCarter21 said:
Try to root my LG Optimus 4X HD and the cmd window say:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: more than one device and emulator
Well.. Thats scared me. Now, my phone is soooo slow, I could uninstall the System Backup Test, but, my phone still very VERY slow.
Please, help me :crying:
Click to expand...
Click to collapse
Do the "factory reset". Erasing all data of course...
To try factory reset from recovery menu
1. turn off the phone
2. press vol down + power
3. waiting vibrate 2 times and release button
4. choose wipe data/factory reset
after that re-root again
don't forget setting debugging mode
before root.
Sent from my LG-P880 using xda app-developers app
First step would be to disconnect any other Android device.
Second one, put the phone to Airplane mode, you can do with some patience even with the SystemBackup.apk installed. Switch USB mode to "charging only".
If that doesn't help, you can still do a reset.
Do you have the Android SDK installed and are you running the root.bat as an Administrator?
XperiaPlayer said:
Do you have the Android SDK installed and are you running the root.bat as an Administrator?
Click to expand...
Click to collapse
Sorry @XperiaPlayer but, I don't have the Android SDK installed, and my root goes perfect...
You're sure that matters?
Regards
Shift + right click the folder where the root.bat is located and type adb devices (or adb.exe devices) and paste the output here.
Hi,
I just got my ZUK Z2 Pro 6/128GB.
first I had the Problem that the OTA to 2.0.048 was not working. I got the notification but when i tried to download it, it was saying "no Internet Connection". Internet is working with browser or any other app.
After that I downloaded the 2.0.048 directly and installed it via SD Update which worked out fine.
But I still get the notification that there is an OTA update.
My Major Problem is, I tried to switch the Google-Play-Store to German according this How-To
can not post URL... it is the italian How to
Everything worked out fine until I get to this part to “Grant permission” with ADB (run.bat)
I am not able to see my phone in ADB whatever I do.
Had the Standard Drivers installed, used the "Adb Driver installer" and also deinstalled the Driver manually and used this How-To
can not post Url.... it is the way with PdaNet Installation which changed the drivers
Still no phone in ADB.
Do you have any idea how to solve this?
I tried this on 3 different Pc's (2 x WIN 10 + Win 7) in several different USB ports
I've got the same problem.
Any ideas?
I even tried it yesterday on a Win XP machine... no success.
USB Debugging is on of course.
Check post 13 in the thread... it worked for me...
http://zukfans.eu/community/threads/how-to-install-google-play.32/
Funky-Fab-4Strings said:
Check post 13 in the thread... it worked for me...
http://zukfans.eu/community/threads/how-to-install-google-play.32/
Click to expand...
Click to collapse
I tried this method but I still get adb server is out of date. killing... adb server didn't ack * failed to start daemon * error. If I wait long enough I get "list of devices attached" but it's blank. This seems hopeless
Swarai said:
I tried this method but I still get adb server is out of date. killing... adb server didn't ack * failed to start daemon * error. If I wait long enough I get "list of devices attached" but it's blank. This seems hopeless
Click to expand...
Click to collapse
I've executed "ADB DEVICES" for my OP3 and it was listed, but the Z2 pro cannot be seen. Is there a driver that I'm not seeing?
Swarai said:
I've executed "ADB DEVICES" for my OP3 and it was listed, but the Z2 pro cannot be seen. Is there a driver that I'm not seeing?
Click to expand...
Click to collapse
I had the same Problem until i installed the android sdk as descripted in my previous post... Debugging and USB 2.0 is activated in the phone?
Funky-Fab-4Strings said:
I had the same Problem until i installed the android sdk as descripted in my previous post... Debugging and USB 2.0 is activated in the phone?
Click to expand...
Click to collapse
Yes, debugging USB 2.0 are activated. I've set up adb using the android sdk at least twice. When I type "ADB DEVICES" my Oneplus 3 is listed. I do not get the same result for the Zuk z2 pro? I don't know why?
So I've solved my problem. I'll try to explain it the best way I can. Apparently I had 2 sets of ADB in 2 different locations on my computer. I plugged in my other phone and typed "ADB DEVICES" in folder got the same "ADB didn't ACK" result. I tried again in a different folder but it worked. By this time I already updated my Zuk Z2 pro to 2.0.048 ST. Hope this can help. thanks
The problems with adb can have something to do with your time and timezone (check if these are correct)
That is also an issue with contacting the google servers.
To download an OTA you need to have a vpn to a chinese server. It is geo-locked. -> after vpn connection is made, stop update service + clear cache. Then check again, it should work according to some.
Hello everyone, I thought I was having the same problem, so I tried to solve with the methods posted here, but after some research, I found out that the "ADB interface" is not showing in Windows device manager
I tried to install it manually, but can't find a way to get it working, and while it seems my phone just bricked after a failed flash, the USB debugging was set on, so can't figure out what could be happening...
Any idea about how to get it working back?
Thank you in advance.
Just to say that I have tried multiple combinations while plugging the device to the PC, and didn't worked...
I mean, the PC seems to react, but always with the same end, only shows the Qualcomm port 9008, nothing about the adb...
Getting out of ideas, anyone more has some?
Anyone managed to find a solution for this issue?
Thanks!
Update to last adb drivers. It worked for me.