Database Users

[Q] root problem "device not found"

Hello ..
Sits and try to root my legend, but can not really get it to succeed. Coming to Step 2
What it says
* Error device not find *
* Error device not find *
And so it will not rise further
Someone who knows how I fixer this problem?
/ Ns_

Seems like you don't have an ADB-Driver for your Legend.
do you have HTC Sync installed? The ADB-Driver is contained in that Utility

just tryed with Htc sync installed, and i says the same!

Legend Root Step 2
Pushing required files to device...
* server not running *
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found
Pushing update file to device sdcard - this may take a few minutes...
error: device not found
error: device not found
Now wipe and apply rootedupdate.zip from the recovery image menu.
error: device not found

just tryed to downgrade it... That also fails.
when i Run the RUU it says Waiting for bootloader, and times out. :S

grrr

I rooted my phone previously and then saw that DL09 was available, so i decided to upgrade. once i upgraded i had to root the phone again and havent been able to since..the phone goes through all the steps in the one click root process and once it restarts after about 2 seconds i unlock it on the lock screen and it freezes up and the root fails..here is what it says when i try to root.
******************************************************************************
* *
* Dirrk's EZ Root v0.2 (Sebastien Krahmers Exploit) *
* *
******************************************************************************
*
* Testing if your device is connected
*
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
I5003ec0df8a device
*
* If you are NOT connected please follow these directions
* Install the correct drivers
* Turn On Debugging
* Check usb port, cable and phone
* Then rerun this application
*
Press any key to continue . . .
*
* Pushing the files to your phone
* rage.bin, busybox, Superuser.apk, su, com.sh
376 KB/s (1867568 bytes in 4.838s)
88 KB/s (26264 bytes in 0.291s)
225 KB/s (196521 bytes in 0.852s)
17 KB/s (5392 bytes in 0.294s)
3 KB/s (281 bytes in 0.069s)
* Restarting your phone to ensure the exploit will work
* When your phone comes back on please unlock it if it is locked and then
* wait
* About to exploit your device
* This will take about 3 minutes
*
* If it doesn't respond after waiting 5 minutes then it probably failed,
* so you should close this and run again
*
* Start Time: 21:29:09.77
*
*
** Successfully exploited, installing permanent root files and deleting temp fil
es
*
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
*
* Restarting your phone now.
*
error: device not found
* Complete
*
******************************************************************************
Press any key to continue . . .

There has GOT to be an easier way to root than this batch file...Im gonna look into it, in the morning. No promises, of course.

http://forum.xda-developers.com/showthread.php?t=833953
Does this works ?

hetaldp said:
http://forum.xda-developers.com/showthread.php?t=833953
Does this works ?
Click to expand...
Click to collapse
I've heard it doesn't on stock DL09, rage.bin is all we have as of now
until adrynalyne saves the day again

I had a pretty easy time rooting my phone using the terminal on my Mac. No drivers to worry about that way. Pretty much uses adb. Maybe try installing cygwin on your pc, and find the mac/linux rooting procedure. If I were a PC user, I think that would be the route I would take.

Just posted on another report of this. The one clickroot worked for my phone after updating to DL09.
I had the same exact error message you have. I let it sit for almost ten minutes and it did complete. I was getting frustrated as well because it was not working and i was at work when i was trying to do this.

If you were already rooted, why on earth did you go for the OTA instead of flashing one of the DL09 packages?
There's no magic in downloading from Verizon, you know. Same software.

i didnt do the ota update i flashed it..i havent had a chance to try and root again but for some reason now im not able to send or receive sms.

I was able to edit the START_ROOT.bat file so the it would pause for 120 seconds instead of 60 seconds after the first phone reboot. Then, after the reboot, unplug the USB from the phone and reconnect it. I'm not sure if this will work for everyone, but it worked for me.
Sent from my SCH-I500 using XDA App

Worked for me. Must unplug after first reboot.

Your sms problem may be solved by flashing the DL09 modem if you haven't already.
Sent from my SCH-I500 using XDA App

http://forum.xda-developers.com/showthread.php?t=803682
check it out.....it does work

jojodablow said:
Worked for me. Must unplug after first reboot.
Click to expand...
Click to collapse
I did the same thing and it worked for me as well. I was running DJ05 previously and after upgrading to DL09 I had to update the Samsung Drivers on my PC. I was prompted to install the new drivers after connecting my fascinate to my and selecting the option to copy files to my PC. After updating the drivers I was successfully able to root my phone using "Dirrk's EZ Root v0.2 (Sebastien Krahmers Exploit)" and disconnecting/reconnecting the USB cable after the first reboot.

[Q] Help with sdk

First off i apologise for any newbie questions. I have just acquired an xperia play (first smartphone ) and i have been trying to use sdk to setInstallLocation 2. I have installed sdk the .zip version (unziped to desktop) and installed the sdk platform tools revision 3 plus enabled the google usb driver package. I conect my phone to the pc (in debugging mode) and mount my sd card (so pc companion sees my phone) (also tried unmounted)
My problem is when i try to adb devices in cmd (as admin) the following error appers
* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
so i have followed a few tips i have seen when googling the error. So i start the task manager and end the adb.exe process and then when i try again with adb devices now it says
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
but when i installed sdk platform tools revision 3 i noticed when it asked to restart adb that deamon tools was loaded in sdk successfully. Any ideas/help would be greatly appreciated?
Moz

Could you post a screenshot of cmd?

Yeah i tried removing http:// and put spaces every where but it stil realised it was an outside link lol. Anyways i can post it now. So here it is.
After the first fail. I did as i said before ended the task in the task manager and then tried again but got the second error. Even if i run cmd not as admin its still the same

You could post only part of the URL, if you leave out the beginning with "http://www." you should be able to post it. And your next post will be number 8 so you can always edit the post afterwards.

[Root Locked Bloader]Nexus One Easy Rooting Toolkit (DoomLord's via Zergrush Exploit)

Just a heads up (I nearly missed it),
After rooting my Galaxy S2 with Doomlord's Rooting Toolkit I pulled out my N1 to see if it would work and it did! Within 30secs I was fully rooted.
My N1 was running 2.3.6 stock till now and I didn't want to wipe to be able to root and this is the way.
I know I had been waiting a long time for this so maybe it'll be useful to others.
Doomlord's Rooting Toolkit: http://forum.xda-developers.com/showthread.php?t=1319653
Zergrush Exploit: http://forum.xda-developers.com/showthread.php?t=1296916
Update: Note that several manufacturers have patched their firmware to make this exploit fail. I don't know if this still works for the N1 though I believe it should considering I haven't seen an update come out for it (could've missed it) So if it fails for you and you got a very recent firmware could be google fixed it.

Could you give a little more detailed instruction how to do it?

Instructions are in the first link.
The gist of it is
1. You need to have your phone's drivers installed for adb to work
2. set to usb debugging
3. connect usb cable
4. run the bat file
5. press space to start the process
6 30secs later (for me) it rebooted and I was rooted.

So to confirm, this I's a working Gingerbread 2.3.4 / 2.3.6 Root exploit without unlocking the bootloader?
Oh man, my Nexus is just begging to be reunited with CyanogenMod!
Sent from my Nexus One using XDA App

Airbag888 said:
Instructions are in the first link.
The gist of it is
1. You need to have your phone's drivers installed for adb to work
2. set to usb debugging
3. connect usb cable
4. run the bat file
5. press space to start the process
6 30secs later (for me) it rebooted and I was rooted.
Click to expand...
Click to collapse
Oh okay, I thought you have to do something special as you provided two links.
I just did those steps and it worked flawless.
Thanks!

@CPM
Yes it roots your phone without unlocking the Bootloader even on 2.3.6 (as is my case)
@DarsVaeda
Sorry for the confusion I was just trying to provide references and credits where due.

Works great! Thanks.
last exploit here: http://cloud.github.com/downloads/revolutionary/zergRush/zergRush.zip
Step by step:
empty /data/local/tmp/
C:\adb pust zergRush /data/loca/tmp
adb chmod 755 /data/local/tmp/zergRush
wait...
C:\adb remount
adb push su /system/bin
adb push su /system/xbin
adb push Superuser.apk /system/app
adb chmod 4755 /system/bin/su
adb chmod 4755 /system/xbin/su
reboot phone
You can su
Try: Install connectbot (or any Terminal) from Google Market connect local, type su, allow. Done.
Now remote bloatware: facebook, Amazone, twitter )

Cheers Airbag888 for bringing this exploit to our attention (and of course everyone else involved in finding the exploit and scripting it)
Works like a charm. I couldn't revert back to the older 2.3.3 Gingerbread after HTC fixed my power button. Suffered the "Main version is older" error downgrading and nothing else worked.
My Nexus is now safely reunited with CyanogenMod and I'm mighty happy
Sent from my Nexus One using XDA App

I'm new to this so I have a question!
If I root my phone using this method will i then be able to use rom manager to install cyanogen rom or do I have to do anything extra?

adamspir said:
I'm new to this so I have a dummy question!
If I root my phone using this method will i then be able to use rom manager to install cyanogen rom or do I have to do anything extra?
Click to expand...
Click to collapse
If you root via any method (this one included)
you can install a custom recovery of any kind (including clockwork which comes with Rom Manager)
you can install compatible Roms via Rom manager as well.
It should not void your warranty either since you're not unlocking your bootloader.
However make sure to do a backup before you install a new ROM and also to wipe your data/cache via recovery when you install another ROM

Thanks!

Hi !
Assuming that an unlocked bootloader wouldn't be a problem, I just tried your method, alas to no avail. Here is the output I got :
Code:
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Pressione qualquer tecla para continuar. . .
--- STARTING ----
--- WAITING FOR DEVICE
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- cleaning
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- pushing zergRush"
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- correcting permissions
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- executing zergRush
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- pushing busybox
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- correcting permissions
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- remounting /system
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- copying busybox to /system/xbin/
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- correcting ownership
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- correcting permissions
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- installing busybox
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- pushing SU binary
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- correcting ownership
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- correcting permissions
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- correcting symlinks
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- pushing Superuser app
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- cleaning
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- rebooting
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
ALL DONE!!!
Pressione qualquer tecla para continuar. . .
I just loved the "ALL DONE!!!" message in spite of every single step having failed
My config looks like this...
Nexus One
Bought directy from Google
running 2.3.6, build GRK39F
bootloader unlocked for the first time through the SDK afew moment before trying to root
MacBook pro running Windows XP
Also tried Bexton's scripts, unsuccessfully.
Out of the blue, I would blame faulty ADB drivers, but since they worked for unlocking my bootloader, I guess they're ok. I'm a bit at loss there, what do you think I did wrong?
Edit: I'm now the first result for "nexus one"+"cannot connect to daemon" on google.fr. Yay me!

I'm not an expert, merely a messenger. But it appears adb isn't starting for you somehow.
I'd look into that.
Try launching it manually and trying to get a list of connected devices. (should give one named HTC#########)
Also if you have unlocked your bootloader then there are other methods to try.

Thanks Airbag888!
For future fellow rooters in need, here is what I did :
Tried to run a sample adb command from the command line, got the dreaded "ADB server didn't ACK"
Opened the Task Manager, noticed two instances of adb running, killed them both
Ran adb devices once again, and TADAA! it worked!
Mad with hope, launched DooMLoRD's script, and so far, it's running. Right now, I've reached the "executing zergRush" stage.
It's been running for a few minutes with no error message so far... Murphy's Law dictates that the process surely is frozen
Edit:
It has indeed frozen (or silently crashed) at "executing zergRush". Killed the adb process again, started the script again. But we're making progresses, I'm now stuck at
Code:
...
[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root... enjoy!
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND

Ad3lphi said:
Hi !
Assuming that an unlocked bootloader wouldn't be a problem, I just tried your method, alas to no avail.
Click to expand...
Click to collapse
If your bootloader is unlocked, why are you even bothering with this. Just start up your phone in fastboot mode, connect to your computer, and flash a custom recovery (i.e., fastboot flash recovery <NameOfYourRecoveryHere.img>, then boot into your custom, and flash ChainsDD's superuser zip. Done.
If your bootloader is unlocked, you never have to worry about root, because you can root at any time...

efrant said:
If your bootloader is unlocked, why are you even bothering with this.
Click to expand...
Click to collapse
Because I feel like keeping the stock ROM until the first ICS-based custom ROMS are out. I just want root access to get the hang of tinkering with my N1 and trashing some bloatware apps.

Ad3lphi said:
Because I feel like keeping the stock ROM until the first ICS-based custom ROMS are out. I just want root access to get the hang of tinkering with my N1 and trashing some bloatware apps.
Click to expand...
Click to collapse
What does that have to do with anything? Did you read the rest of my post? What I gave you was the way to root if your bootloader is unlocked. I never mentioned anything about switching ROMS...
efrant said:
Just start up your phone in fastboot mode, connect to your computer, and flash a custom recovery (i.e., fastboot flash recovery <NameOfYourRecoveryHere.img>, then boot into your custom recovery, and flash ChainsDD's superuser zip. Done.
Click to expand...
Click to collapse
Much simpler. No change to your stock ROM at all.

Finally a exploit that doesnt involve formatting my phone
Now, I am planning to run this exploit when I get home tonight
My phone at the moment is 2.3.4 and I would guess this exploit would work for it?
And I also guess you can't install clockworkmod without unlocking your bootloader?

Warmo161 said:
Finally a exploit that doesnt involve formatting my phone
Now, I am planning to run this exploit when I get home tonight
My phone at the moment is 2.3.4 and I would guess this exploit would work for it?
And I also guess you can't install clockworkmod without unlocking your bootloader?
Click to expand...
Click to collapse
I successfully rooted 2.3.4 using the exploit. Then installed RA Amon recovery rather than ClockworkMod (personal choice). Then onto CyanogenMod 7.1 and S2E for loading my apps onto SD Card. All worked perfectly fine too.
Sent from my Nexus One using XDA App

Warmo161 said:
Finally a exploit that doesnt involve formatting my phone
Now, I am planning to run this exploit when I get home tonight
My phone at the moment is 2.3.4 and I would guess this exploit would work for it?
And I also guess you can't install clockworkmod without unlocking your bootloader?
Click to expand...
Click to collapse
You don't need to unlock the bootloader to install recovery or any different rom or run nandroid backup etc

Problem with root D802

Hello and sorry for my very bad english ... and thank you Google translation
I 've had a week a problem with my G2, it is impossible for me to root
Sunday I installed the rom CloudyPro 2 I had before due to a back in stock and I flash the Kernel Dorimanx .
Problem, since the flash kernel , the G2 is no longer root ...
Since Monday , it is impossible for me to root with ioroot25 , I all the time the same error message and adb is not recognized on my phone , the PC can not access it.
Here is the message:
* Daemon not running . starting it now on port 5037 *
* Daemon started successfully *
** Daemon still not runningerror :
*
Determining device model ...
Did ADB server ACK
* Failed to start daemon *
error: can not connect to daemon
With adb shell , this is what I get:
C: \ adb > adb shell
* Daemon not running . starting it now on port 5037 *
* Daemon started successfully *
** Daemon still not running
error: can not connect to daemon
*
C: \ adb >
I have been back to 4.2.2 with the TOT file, but the problem is always the same.
If anyone here had a solution , it is with pleasure that I take .
Importantly, I root.bat restart several times , each time I killed adb.exe in task manager.
Thank you for your help

What antivirus do you use ? Try this

I use Avast free antivirus

fabin0u77 said:
I use Avast free antivirus
Click to expand...
Click to collapse
Always same problem after try your method

A strange thing is that when I root my G2 the first time, I never had this problem.
It is only since I put the kernel Dorimanx last Sunday I noticed that the phone was no root and it was impossible for me root my G2

The upper problem would appear regardless you connect the g2 or don't. It's computer issue. Try disabling AV.

Sorry, I don't understand your answer...

I'm of the opinion that the error has nothing to do with your phone. It's computer / software issue.

On this point I agree with you, I think the same thing, but I do not see how to solve the problem of sudden ...
What did you mean by disable AV

fabin0u77 said:
On this point I agree with you, I think the same thing, but I do not see how to solve the problem of sudden ...
What did you mean by disable AV
Click to expand...
Click to collapse
disable antivirus......

I try to disable the antivirus and re-handling, but I still have the same concern ..
I think I'm going to format and reinstall all my PC hoping that the problem will be solved in this case.
Point still weird, I just flash by LG Support Tools and the 80220D when flash Unrooted became ROOTED gold I do not have superuser installed with root checker and I'm not root

Hi, problem finally solved.
Ultimately the concern came well my pc, he could not have contact with my adb as ...
Suddenly full format and installation and attempt to root this time has functioned well.
Thank you for your help

:good: good thing it works now