When I use the Superoneclick to root my dell streak 2.2, there have some problem cant complete.
Here is the superoneclick command list:
SuperOneClick v1.7.0.0
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing psneuter...
2816 KB/s (585731 bytes in 0.203s)
OK
chmod psneuter...
OK
Running psneuter...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Killing ADB Server...
* server not running *
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running psneuter...
FAILED
Anyone can tell me how can fix it to root?!
Many Thanks
same issue here...
Try rageaginstthecage instead of psneuter
I have the same problem with the later version of superclick too...but got it to root with the older version...I believe is ver 1.5..
I can share my experience with you while my dell now is Death because I do something wrong, it wont boot up anymore.
With 31800 version,
1- Download SOC 1.6.5.
2- Stop YOUR ANTIVIRUS before extract the file of SOC (Your antivirus may delete 1 file necessary for root process).
3- Before you start check if a file name "rageaginstthecage" is in the folder, antivirus may delete it.
4- Start SOC and choose "rageaginstthecage" option.
5- If the file I mention in step 3 is exist and you choose the right option as in step 4, it will go smooth.
3GBeyotch said:
Try rageaginstthecage instead of psneuter
Click to expand...
Click to collapse
+1................
SuperOneClick v1.7 works on my dell streak official froyo build number 12903
1-unmount sd card
2-turn on usb debug mode
3-do shell root before actually rooting
4-use the "rageagainstthecage" exploit,not psnueter..
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.
I have looked everywhere, spent countless hours and days trying to find a PERMANENT solution for this. Only solution i could find was to use TaskManager and kill adb process. Not a permanent solution. As the same error will come back.
This is the error. Nothing causes it, just happens randomly with any device im using.
Code:
* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
Thanks guys. A permanent solution would be awesome. I'm tired of this..
elesbb said:
This is the error. Nothing causes it, just happens randomly with any device im using.
Code:
* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
A permanent solution would be awesome. I'm tired of this..
Click to expand...
Click to collapse
First, the obvious: have you tried different USB cables and different USB ports on your machine? (I'll assume the answer is "yes").
Now, the more likely: get a copy of USBDeview and use it to remove all copies of your ADB USB drivers. In case you're not familiar with it, this util will list every USB driver installed on your machine and (among other things) will let you delete the ones you don't want. If you've been using your current setup for a while, you'll be appalled at the cruft that's built up. Be aware that there are separate 32 and 64-bit versions, so get the one appropriate for your system.
The ADB driver(s) may be identified as "Android ADB Interface" or any of several other names. You'll see entries for various USB Vendor and Product IDs, with at least one entry for each Android device you've connected. The one thing all of the relevant entries will have in common are the values in the columns labeled USB Class, USB Subclass, and USB Protocol. Those values are ff, 42, and 01, respectively.
Sort the list by Class to group them, then uninstall all of them. When you're done, reboot. You may want to reopen the util to confirm they're really gone. Finally, attach each device in turn and let the New Hardware Wizard walk you through reinstalling the driver (which means, of course, that you'll want to have your driver packages ready before you go deleting anything).
Note: there's really only one driver (i.e. binary) for all devices. The difference in the packages is their .INF files, each of which usually only identifies Vendor and Product IDs for a single manufacturer. If you know those values for each device, you can edit the .INF file for one and add all your devices to make a one-size-fits all package (be sure to add each entry under both the 32-bit and 64-bit headings in the file). You'll still have to reinstall for each device but you won't need multiple packages to do it.
adb kill-server
adb start-server
Should get you back on track.
es0tericcha0s said:
adb kill-server
adb start-server
Should get you back on track.
Click to expand...
Click to collapse
No.. you're wrong.
dolorespark said:
First, the obvious: have you tried different USB cables and different USB ports on your machine? (I'll assume the answer is "yes").
Now, the more likely: get a copy of USBDeview and use it to remove all copies of your ADB USB drivers. In case you're not familiar with it, this util will list every USB driver installed on your machine and (among other things) will let you delete the ones you don't want. If you've been using your current setup for a while, you'll be appalled at the cruft that's built up. Be aware that there are separate 32 and 64-bit versions, so get the one appropriate for your system.
The ADB driver(s) may be identified as "Android ADB Interface" or any of several other names. You'll see entries for various USB Vendor and Product IDs, with at least one entry for each Android device you've connected. The one thing all of the relevant entries will have in common are the values in the columns labeled USB Class, USB Subclass, and USB Protocol. Those values are ff, 42, and 01, respectively.
Sort the list by Class to group them, then uninstall all of them. When you're done, reboot. You may want to reopen the util to confirm they're really gone. Finally, attach each device in turn and let the New Hardware Wizard walk you through reinstalling the driver (which means, of course, that you'll want to have your driver packages ready before you go deleting anything).
Note: there's really only one driver (i.e. binary) for all devices. The difference in the packages is their .INF files, each of which usually only identifies Vendor and Product IDs for a single manufacturer. If you know those values for each device, you can edit the .INF file for one and add all your devices to make a one-size-fits all package (be sure to add each entry under both the 32-bit and 64-bit headings in the file). You'll still have to reinstall for each device but you won't need multiple packages to do it.
Click to expand...
Click to collapse
I thank you a million! This looks promising! I did notice like 20 different adb devices installed. So far it's been good hopefully it stays that way!
Sent from my SGH-M919 using Tapatalk
Yea, sorry, that is the temp solution, not a permanent one.
es0tericcha0s said:
Yea, sorry, that is the temp solution, not a permanent one.
Click to expand...
Click to collapse
Not only that, but it's not even a temp solution. How can I or anyone kill a server you can't connect to?
Sent from my SGH-M919 using Tapatalk
elesbb said:
Not only that, but it's not even a temp solution. How can I or anyone kill a server you can't connect to?
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Oh. I see you don't understand the commands. You said that you had to continue to go to the Task Manager to kill the process and then you would restart it. That's what those commands do, without taking that step. I've solved this issue before with doing that, though it's never been an ongoing thing, so haven't had to deal with making it permanent. Guess we have a different idea of what wrong is...
es0tericcha0s said:
Oh. I see you don't understand the commands. You said that you had to continue to go to the Task Manager to kill the process and then you would restart it. That's what those commands do, without taking that step. I've solved this issue before with doing that, though it's never been an ongoing thing, so haven't had to deal with making it permanent. Guess we have a different idea of what wrong is...
Click to expand...
Click to collapse
What I'm saying is, running adb kill server wouldn't do anything because it can't connect to the adb server daemon due to that error I was receiving. After running adb kill server then running adb start server I would still get that same exact error. Which makes sense because it can't connect to the server so therefore is unable to kill it making task manager the only way of killing the server.
Sent from my SGH-M919 using Tapatalk
elesbb said:
What I'm saying is, running adb kill server wouldn't do anything because it can't connect to the adb server daemon due to that error I was receiving. After running adb kill server then running adb start server I would still get that same exact error. Which makes sense because it can't connect to the server so therefore is unable to kill it making task manager the only way of killing the server.
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
What I'm saying is that command is specifically for that issue, because the adb server is not starting correctly because it's kind of stuck. If the server wasn't on at all, it wouldn't be listed in the Task Manager, right? I've had this issue multiple times before on various devices, and that's what got it to come back on and connect again. I literally do this stuff for a living and have modded 100s of devices. Weird things pop up like this all the time and it's not always the same solution for everyone or every device.
start-server Checks whether the adb server process is running and starts it, if not.
kill-server Terminates the adb server process (which the Task Manager also does, but this is the command for it)
So yea, my solution didn't work for you, but it is a solution for this issue. Been there. Done that. Probably will have to do it again some day.
es0tericcha0s said:
What I'm saying is that command is specifically for that issue, because the adb server is not starting correctly because it's kind of stuck. If the server wasn't on at all, it wouldn't be listed in the Task Manager, right? I've had this issue multiple times before on various devices, and that's what got it to come back on and connect again. I literally do this stuff for a living and have modded 100s of devices. Weird things pop up like this all the time and it's not always the same solution for everyone or every device.
start-server Checks whether the adb server process is running and starts it, if not.
kill-server Terminates the adb server process (which the Task Manager also does, but this is the command for it)
So yea, my solution didn't work for you, but it is a solution for this issue. Been there. Done that. Probably will have to do it again some day.
Click to expand...
Click to collapse
I understand that this solution may work for a temporary issue. I myself us it all the time when I can't see a device or something. But what im trying to say is the error says "server didn't ACK" in my searching of this error, ACK means acknowledge. Therefore communication with the server fails. So sending the server a kill command fails as well. See what i mean?
Lets just hope the other guys method works. Was surprised to see about 12 or so ADB devices when i only have 3
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.