Rooting for Eclair and leaked Froyo DK28

Backing your system up with Clockwork is the first thing you should do before flashing any ROMs or kernels. If you ever mess up and need to revert, Clockwork can save your butt.
 
then you press any key to continue haha

and then itll do its thing then fellow the directions here

i'm not COMPLETELY ******ed... i pressed and nothing happened. i dont' want to close the window cause i dont'; knwo if its in the middle of something or not

ok restarted it.. looks like i got it workign now

spoke too soon... got to the adb connection will be reset line.. closed all instances of the proccess in task manager.. but it seemed to restart itself. now it says "wait for phone to reconnect..." and is hung there
 
Last edited:
i closed the command prompt, and then clicked run again. unplugged and plugged in my phone and everything started to run... but now i'm stuck again

phone is frozen.. don't knwo what i should do


Exploit made by joeykrim and one click installer made by noobnl and firon
busybox by skeeterslint
Press any key to continue . . .
Phone is not connected.
Press any key to continue . . .
Copy and run the exploit (may take up to two minutes). Ignore messages about re-
logging in.
If more than five minutes pass, reboot the phone and try again.
Starting adb server...
* server not running *
* daemon not running. starting it now *
* daemon started successfully *
219 KB/s (5392 bytes in 0.024s)
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C

[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3712, 3712}
[*] Searching for adb ...
[+] Found adb as PID 29652
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] 7-4-3-C@web.de so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
Wait for phone to reconnect...
 
ugh i have no idea what's going on. someting different happens every time i try this

Exploit made by joeykrim and one click installer made by noobnl and firon
busybox by skeeterslint
Press any key to continue . . .
Phone is not connected.
Press any key to continue . . .
Copy and run the exploit (may take up to two minutes). Ignore messages about re-
logging in.
If more than five minutes pass, reboot the phone and try again.
Starting adb server...
* daemon not running. starting it now *
* daemon started successfully *
292 KB/s (5392 bytes in 0.018s)
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C

[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3712, 3712}
[*] Searching for adb ...
[+] Found adb as PID 6757
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] 7-4-3-C@web.de so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
Wait for phone to reconnect...
Mount system as r/w, cleanup old files, do some basic configuration
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
Copying files onto phone...
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
Setting permissions...
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
Installing busybox...
error: device not found
Press any key to reboot the phone
Press any key to continue . . .
 
Unfortunately that's how rooting goes - it's really a trial and error process. Just keep trying different things in different combinations per the guide.

That last line that you copied and pasted, "restart adb server on desktop and re-login. Wait for phone to reconnect..." - did you restart adb?
 
i dont' even know what i'm looking for at the end =| was i supposed to get all those errors?
 
nope. i'm giving up. tried it about ten times and keep getting different situations. seems like the program refuses to copy anything to the phone though
 
Well your attempts were not in vain - I added a little paragraph to the guide warning users about the unpredictability of rooting.
 
Well your attempts were not in vain - I added a little paragraph to the guide warning users about the unpredictability of rooting.

i ended the process and it automatically restarted itself again. the problem seems to be that when i turn on debugging my computer can no longer see the phone as a drive so it won't copy anything to it
 
i have to run it twice?

ok here's what happens... i run "run" and it hangs.. every time. i close the window and run "run" again and it tells me it can't see the phone. i unplug the phone and plug it back in and the process starts. when it says to i open taks manager and close one of the 2 instances of adb that's running in processes. it closes both and then restarts adb on its own, and the process continues. but it always tells me it can't copy the files. then it says to press to reboot and i do and the phone restarts. no root though
 
Last edited:
so the phone automatically restarts? how are you checking if you have root - Titanium Backup?
 
Exploit made by joeykrim and one click installer made by noobnl and firon
busybox by skeeterslint
Press any key to continue . . .
Phone is not connected.
Press any key to continue . . .
Copy and run the exploit (may take up to two minutes). Ignore messages about re-
logging in.
If more than five minutes pass, reboot the phone and try again.
Starting adb server...
* daemon not running. starting it now *
* daemon started successfully *
135 KB/s (5392 bytes in 0.039s)
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C

[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3712, 3712}
[*] Searching for adb ...
[+] Found adb as PID 3869
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] 7-4-3-C@web.de so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
Wait for phone to reconnect...
Mount system as r/w, cleanup old files, do some basic configuration
* daemon not running. starting it now *
* daemon started successfully *
mount: Operation not permitted
failed to copy 'rootsetup' to '/system/xbin/rootsetup': Permission denied
Unable to chmod /system/xbin/rootsetup: No such file or directory
/system/xbin/rootsetup: not found
rm failed for /system/xbin/rootsetup, No such file or directory
Copying files onto phone...
failed to copy 'su' to '/system/xbin/su': Permission denied
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Permission denied

failed to copy 'playlogo' to '/system/bin/playlogo': Permission denied
failed to copy 'busybox' to '/system/xbin/busybox': Permission denied
failed to copy 'remount' to '/system/xbin/remount': Permission denied
Setting permissions...
Unable to chmod /system/bin/playlogo: Operation not permitted
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/remount: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
link failed Permission denied
Installing busybox...
/system/xbin/busybox: not found
Press any key to reboot the phone
Press any key to continue . . .



the whole problem seems to be the line "mount.. operation not permitted"
 

Trending Posts

Forum statistics

Threads
957,050
Messages
6,971,214
Members
3,163,693
Latest member
Ap2300