hi, when I am trying to use putty it shows a message : network error: connection timed out. I saw my phone's ip address using adb, and it shows:
*daemon not running. starting it now on port 5037*
*daemon started successfully*
after it, my ip.
What can I do? I tried to change the port on both programs and it didn't work.
lucascastro said:
hi, when I am trying to use putty it shows a message : network error: connection timed out. I saw my phone's ip address using adb, and it shows:
*daemon not running. starting it now on port 5037*
*daemon started successfully*
after it, my ip.
What can I do? I tried to change the port on both programs and it didn't work.
Click to expand...
Click to collapse
Hi,
Did you download PuTTY.exe or PuTTYtel.exe? You need the PuTTYtel.exe file. Feel free to PM me if you need more help to get rooted.
Good luck!
lucascastro said:
hi, when I am trying to use putty it shows a message : network error: connection timed out. I saw my phone's ip address using adb, and it shows:
*daemon not running. starting it now on port 5037*
*daemon started successfully*
after it, my ip.
What can I do? I tried to change the port on both programs and it didn't work.
Click to expand...
Click to collapse
i would try googleing for the Moto X Toolkit and use that to Root your device with Rockmymoto it is about as automated as it can get.
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
Hi, does anyone know how to permanently change the MAC address on a rooted Nexus One? Thanks.
Considering the root of this file system is linux, it should be pretty similar to this: http://linuxhelp.blogspot.com/2005/09/how-to-change-mac-address-of-your.html
If at all possible. Obviously, change eth0 to whatever is appropriate. Also, you'll probably have to su to do any of the commands.
Hi, thanks for the reply. I did try that already but after the following command:
ifconfig eth0 hw ether 00:80:48:BA:d1:30
I get this error:
ifconfig: bad address 'hw'
Any ideas?
It worked for me. Before you ran that command did you switch to root user?
Also, this won't permanently change it. It'll only change it for your current boot. If you want it to be permanently done, you'll have to put the command into a init.d script.
So, I have been looking into and testing this some more and I have found something strange. It seems as though something within android keeps reverting my MAC address back to the real MAC address and I am unable to connect to the network I am trying to connect to (it has MAC address filtering). Any thoughts?
And nachod0g in response to your error, double check and make sure that when you type the command "ifconfig -a | grep HWaddr" that eth0 actually comes up. If WiFi is not enabled, this will not work.
I just bought Htc one ywsterday and i was unlocking the bootlaader today and root, and i'm trying to flash custom rom, but i can't copy anything to my storage... i did install sdk and the drivers and everything, tried lots of things, tried with adb push but it's not working, and now i'm pissing off... don't know what's the problem/.....???
p.s when i type
adb devices it says:
*daemon not running*. starting it now on port 5037 *
*daemon started succesfuly*
List of devices attached
HT35***** device
P.s.s I tried to adb sideload a rom and i get :
*daemon not running*. starting it now on port 5037 *
*daemon started succesfuly*
error: closed
Please help...
So when you plug your HTC device into the computer...go to start-computer and you dont see htc one as a media device? It should also pop up with options to open files in your device when you first plug it in
No no, the device pops out but the problem is the copyng starts and then it stucks... even for files that are 1mb
EDIT: Never mind.
sauprankul said:
EDIT: Never mind.
Click to expand...
Click to collapse
?
Sent using my HTC One from that FBI van parked down the street.
Unplug the USB and replug. Make sure the screen is unlocked. Sometimes happens.
Sent from my HTC One using xda app-developers app
also do not use a USB 3.0 port on your computer
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.
Hello everyone
I was wondering if someone can help me. I've been trying for a week to get my device recognized by the my Windows 10 PC, but it keeps coming up as unauthorized. I've seen all the posts:
https://forum.xda-developers.com/amazon-fire/help/help-thread-7th-gen-2017ask-question-t3636919
https://stackoverflow.com/questions/16256790/cannot-install-adb-for-kindle-fire-hd
https://theunlockr.com/how-to-unroot-the-amazon-kindle-fire/
https://www.howtodroid.com/2014/02/how-to-add-adb-command-prompt-windows.html
https://forum.xda-developers.com/amazon-fire/help/fire-7-2017-7th-gen-downgrade-debloat-t3699937
https://forum.xda-developers.com/showthread.php?t=1552547
Even the official Amazon website instructions
https://developer.amazon.com/docs/f...ice.html#install-the-usb-driver-windows-users
Sorry for all the links, just trying to prevent people saying i haven't tried everything. Even going to a new computer where i never plugged in the Fire 7 in said it was unauthorized. Here is the errors i get (i ran this in the folder itself using powershell and cmd as admin)
D:\Fire 7\3rd attempt\platform-tools>adb devices
List of devices attached
serial number unauthorized
D:\Fire 7\3rd attempt\platform-tools>adb kill-server
D:\Fire 7\3rd attempt\platform-tools>adb start-server
* daemon not running; starting now at tcp:5037
* daemon started successfully
D:\Fire 7\3rd attempt\platform-tools>adb devices
List of devices attached
serial number unauthorized
D:\Fire 7\3rd attempt\platform-tools>adb usb
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
I'm at a loss, i know it works sicne i've seen a bunch of people do it online, but for some reason i can't do it. Please help! Anything would be helpful! Thank you in advance!
Did you find a workarround? I'm stuck in the same place as you. Tried everything you mention and fail...
srok.desarrollos said:
Did you find a workarround? I'm stuck in the same place as you. Tried everything you mention and fail...
Click to expand...
Click to collapse
i had this on ubuntu from a command line, but abdlink said authorized (but nothing would install). I went to windows10 and i get the prompt on the tablet and no issues. I don't know if the ubuntu adb drivers don't work right or what. It seems to work fine in ADB on windows...
I have had to turn off adb usb on the fire before and remove authorizations to get it to prompt for adb.
I fixed it in Ubuntu by changing it to media device instead of charging only.
Edit - worked one time, then back to unauthorized....
next edit -
sudo adb kill-server
sudo adb devices
that prompted the authorization for me