i've installed multiple different adb/htc drivers.. at one point my computer could start adb and run up until the point where the rom was being transferred then it would error out after some time. NOW its not even starting daemon. How do i fix this? I want to remove all the driver clutter and start this process from scratch the **** has gotten so confusing for no reason. underneath is dost detailing where i've stalled out
HELP ME SOMEBODY PLEASSEEEEEEEEEEEEEEE!!!!!
Quote Originally Posted by benny3 View Post
adb and fastboot should be in the same folder. Are opening the command prompt from that same folder?
download this and extract it to your desktop. Put the rom.zip in it, Hold the shift key down, right click that folder and the run command from here
XXXXXX.com/u/45848000/adb.zip[/url]
dog **** still aint work. so i installed the HTC drivers from your other post (though nothing happens really when exe is clicked)
then i download this file and did as directed, cmd replied:
C:\Users\Gateway\Desktop\adb>adb devices
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
C:\Users\Gateway\Desktop\adb>adb kill-server
C:\Users\Gateway\Desktop\adb>adb usb
* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
C:\Users\Gateway\Desktop\adb>
other people are saying to copy adb files to folder on c drive and launch from there. they also say launch cmd from installed adb location...what where the first set of files you had me install? the driver in my list of devices says Google nexus ADB interface driver but i cant find its location. shouldnt i move the rom.zip there and lunch there??? why is this such a ******* struggle. thank you for helping seems the rest of the android community just reads random troubleshooting posts for no reason other than entertainment... most unhelpful forum ever.
Related
So I am starting my root process over the manual way and every time I run a command i get a couple extra lines shown below.
c:\android-sdk-windows\platform-tools>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT12SS007221 device
What is with the adb server being out of date and killing... and then the daemon?
Just wondering if this might be the reason for the botched attempt the first time around.
A DAEMON! The Phone is possessed ... run!
Actually, A daemon is a computer program that runs in the background
ADB found it was previously started and killed the process then started a new one for you. This is normal.
No worries, its working as it should
LOL sweet thanks!
I can't seem to push or pull any files. I can run adb and su, but I keep getting this when I adb push something.
** daemon still not runningerror: cannot connect to daemon **
Can someone tell me what my problem is? Thanks!
Hate to revive but I'm getting this too now.
Edit: Nevermind... don't do adb in adb shell lol
you have to run adb in the same directory as android SDK
otherwise,u will get"daemond is not running"
I followed the instructions on the HTCDev website. My phone showed the process was sucessful. I am trying to root with OneClickRoot_1.1 and it is not rooting. I am wondering it I am actually unlocked at the bootloader level?
Solved
1st mistake was did not include this file AdbWinApi.dll durring the HTC Dev unlocking process. I went through the instuctions again and still no root.
2nd mistake was that I had HTC Sync running. After I corrected mistake 1 and corrected mistake 2 I have root. The problem I have now is that bootloader will not recognize a PH98IMG.zip file on the SD card when I tried to flash a recovery.
Any ideas on how to fix this? I am going to start another thread since this problem is burried in this post.
??
Here is the screen results
Press any key to continue . . .
--- WAITING FOR DEVICE ---
adb server is out of date. killing...
* daemon started successfully *
--- Device Connected ---
Checking for previous attempts...
adb server is out of date. killing...
* daemon started successfully *
Pushing Zergrush...
adb server is out of date. killing...
* daemon started successfully *
2047 KB/s (23060 bytes in 0.011s)
Setting Permissions...
adb server is out of date. killing...
* daemon started successfully *
Gaining Perm Root (Aka running zergrush)...
error: protocol fault (no status)
--- WAITING FOR DEVICE ---
* daemon not running. starting it now *
* daemon started successfully *
--- Device Connected ---
Pushing Busybox
adb server is out of date. killing...
* daemon started successfully *
2267 KB/s (1075144 bytes in 0.463s)
Setting Permissions...
adb server is out of date. killing...
* daemon started successfully *
Remounting System...
* daemon not running. starting it now *
* daemon started successfully *
mount: permission denied (are you root?)
Coping Busybox to /system/xbin/...
adb server is out of date. killing...
* daemon started successfully *
/system/xbin/busybox: cannot open for write: Read-only file system
Installing Busybox...
adb server is out of date. killing...
* daemon started successfully *
Unable to chmod /system/xbin/busybox: No such file or directory
* daemon not running. starting it now *
* daemon started successfully *
Unable to chmod /system/xbin/busybox: No such file or directory
adb server is out of date. killing...
* daemon started successfully *
/system/xbin/busybox: not found
adb server is out of date. killing...
* daemon started successfully *
Installing Superuser...
* daemon not running. starting it now *
* daemon started successfully *
failed to copy 'tools\su' to '/system/bin/su': Read-only file system
adb server is out of date. killing...
* daemon started successfully *
Unable to chmod /system/bin/su: No such file or directory
adb server is out of date. killing...
* daemon started successfully *
Unable to chmod /system/bin/su: No such file or directory
* daemon not running. starting it now *
* daemon started successfully *
link failed Read-only file system
adb server is out of date. killing...
* daemon started successfully *
failed to copy 'tools\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
Removing tools That Was Pushed To Data...
adb server is out of date. killing...
* daemon started successfully *
Congrats You Are Now Perm Rooted...
Press any key to continue . . .
Do a battery pull and then hold volume- and power simultaneously until the phone powers on. This should bring you to the bootloader screen. Then just look and see if it says unlocked at the top of the screen.
sent from my newly unlocked Rezound
There is an app that can check your root status but I doubt you are rooted. I went through the same thing and it took me a bit to figure out what was wrong. Check that USB debugging and install apps from unknown sources are on , that may help
Sent from my ADR6425LVW using XDA App
Thanks for the suggestions.
Bootloader says unlocked.
Root Checker says not rooted.
use my root tutorial in my signature. It doesn't require finicky pc tools
solved but have another problem bc I screwed up
1st mistake was did not include this file AdbWinApi.dll durring the HTC Dev unlocking process. I went through the instuctions again and still no root.
2nd mistake was that I had HTC Sync running. After I corrected mistake 1 and corrected mistake 2 I have root. The problem I have now is that bootloader will not recognize a PH98IMG.zip file on the SD card when I tried to flash a recovery.
Any ideas on how to fix this? I am going to start another thread since this problem is burried in this post.
oneders65 said:
1st mistake was did not include this file AdbWinApi.dll durring the HTC Dev unlocking process. I went through the instuctions again and still no root.
2nd mistake was that I had HTC Sync running. After I corrected mistake 1 and corrected mistake 2 I have root. The problem I have now is that bootloader will not recognize a PH98IMG.zip file on the SD card when I tried to flash a recovery.
Any ideas on how to fix this? I am going to start another thread since this problem is burried in this post.
Click to expand...
Click to collapse
problem → adb server is out of date. killing...
i had the same problem and fixed by
uninstalling and re-installing the drivers..
go to control panel and programs then uninstall
htc bmp usb driver, htc driver installer, and htc sync
then re-install all three
i rebooted the computer after uninstalling incase
then re-installed.
then try the one click root
---------- Post added at 04:30 PM ---------- Previous post was at 04:26 PM ----------
oneders65 said:
1st mistake was did not include this file AdbWinApi.dll durring the HTC Dev unlocking process. I went through the instuctions again and still no root.
2nd mistake was that I had HTC Sync running. After I corrected mistake 1 and corrected mistake 2 I have root. The problem I have now is that bootloader will not recognize a PH98IMG.zip file on the SD card when I tried to flash a recovery.
Any ideas on how to fix this? I am going to start another thread since this problem is burried in this post.
Click to expand...
Click to collapse
driver probably will fix the problem,
but i also uninstalled and re-installed
android sdk tools and platform-tools in android sdk manager,
because at the time, i didn't know what was causing the problem
qudwis said:
problem → adb server is out of date. killing...
i had the same problem and fixed by
uninstalling and re-installing the drivers..
go to control panel and programs then uninstall
htc bmp usb driver, htc driver installer, and htc sync
then re-install all three
i rebooted the computer after uninstalling incase
then re-installed.
then try the one click root
Click to expand...
Click to collapse
I have installed apks using adb and gotten that message and was wondering what it was. the apps installed fine but that was on my list of questions I wanted answered before I feel comfortable enough to root. Thanks!
Either avast or comodo sandboxed HTC sync so every time I rebooted my laptop it told me there was an update even though I installed it every time. I've since added it to the white list but I don't think I've had to use it since then. I think I'll do a fresh install regardless.
Sent from my ADR6425LVW using Tapatalk
feralicious said:
I have installed apks using adb and gotten that message and was wondering what it was. the apps installed fine but that was on my list of questions I wanted answered before I feel comfortable enough to root. Thanks!
Either avast or comodo sandboxed HTC sync so every time I rebooted my laptop it told me there was an update even though I installed it every time. I've since added it to the white list but I don't think I've had to use it since then. I think I'll do a fresh install regardless.
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
I was getting that adb server out of date thing, too. Mine was because I had another adb running on the computer.
Try exiting the anti-virus on your computer. Zergrush shows up as a malicious program since it wants to access root files. Even Microsoft Essentials stops it before it completes.
saw the thread over here: http://forum.xda-developers.com/showthread.php?t=2292791
tried all of the same steps (and more) listed in that thread numerous times.
SDK is the latest zip file dated "20130522"
phone DOES have developer mode enabled.
Samsung Kies connects and works fine (using driver bundled in Kies installer)
Windows Explorer maps the device and it can be browsed
Device Manager lists device by name under Portable Devices as well lists "SAMSUNG Mobile USB Composite Device" (driver 2.9.510 date 2013.05.23) under USB controllers
using Koushik Dutta's Universal ADB Driver did not help at all, device then becomes an android device in device manager and neither Kies or adb can connect to it...
Code:
C:\Android_SDK_Windows\sdk\platform-tools>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Android_SDK_Windows\sdk\platform-tools>adb devices
List of devices attached
C:\Android_SDK_Windows\sdk\platform-tools>
ideas?
EDIT: SOLVED, mis-tapped in dev options menu (stupid small text made BIG now)... checkmarked 'include bug reports...' instead of 'usb debugging'. off to hang my head in shame
Anyone managed to find working USB drivers and get their Mate 20 Pro showing up in ADB? If so could you share the drivers as I can't find any.
Edit: for some reason USB debugging turned itself off. It's showing up now.
@Kipp162 did you finally manage to run adb with the HUAWEI Mate 20 Pro? I was not able to do so. All other devices have been no problem but it seems that the HUAWEI Mate 20 Pro needs an extra trick?!
The thing that finally worked for me was installing HiSuite.
cant see device
saturnspike said:
The thing that finally worked for me was installing HiSuite.
Click to expand...
Click to collapse
Hi, how exactly ? I have installed HiSuite, but anyway "adb devices" cant see any device.
(have mate20pro with latest os and emui)
[email protected]:/home/mato# adb kill-server
[email protected]:/home/mato# adb devices -l
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/home/mato# adb devices -l
List of devices attached
[email protected]:/home/mato#
matolog said:
Hi, how exactly ? I have installed HiSuite, but anyway "adb devices" cant see any device.
(have mate20pro with latest os and emui)
[email protected]:/home/mato# adb kill-server
[email protected]:/home/mato# adb devices -l
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/home/mato# adb devices -l
List of devices attached
[email protected]:/home/mato#
Click to expand...
Click to collapse
I have to make sure usb debugging is enabled and when you plug phone up to computer, make sure you select file transfer.
dwojr said:
I have to make sure usb debugging is enabled and when you plug phone up to computer, make sure you select file transfer.
Click to expand...
Click to collapse
yes, debugging was enabled.
well after many attempts I was able to connect. (the connection was problem, must tried many times restart server, after connection adb shell, connection with phone was stable)