• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root The Official One-Click Rooting Solution for Droid Thread!!! :D :D LATEST: V2.0.4

Failed on 1.2 as well.. same error I reported above.

I can see that you added in all that text after the failed mount error that says "it should be done now.... if there was an error a couple of lines up thats normal dont worry"

well, after we get that we just unplug the phone, reboot it, as your app does not reboot it, and go into ROM Manager and still have no root access

BTW, we also tried that new "have you been rooted before option" and selected "yes" and it ran a command line window, closed window, then told us "only press OK AFTER the Droid has fully restarted" which implies your app should restart the phone, but the thing is, your app did not restart the the Droid? after we rebooted we hit "ok" and it ran the root app and again, we got that mount error and no root was obtained.
 
Upvote 0
Failed on 1.2 as well.. same error I reported above.

I can see that you added in all that text after the failed mount error that says "it should be done now.... if there was an error a couple of lines up thats normal dont worry"

well, after we get that we just unplug the phone, reboot it, as your app does not reboot it, and go into ROM Manager and still have no root access

BTW, we also tried that new "have you been rooted before option" and selected "yes" and it ran a command line window, closed window, then told us "only press OK AFTER the Droid has fully restarted" which implies your app should restart the phone, but the thing is, your app did not restart the the Droid? after we rebooted we hit "ok" and it ran the root app and again, we got that mount error and no root was obtained.

same here
 
Upvote 0
That's the weirdest thing. Okay guys, give me these details:

Phone Make/Model:
Firmware Version:
ROM Version (ex. FRG22D):
Windows Version:
Do you have admin privileges?
Is your phone on USB Debugging?
Have you turned on USB Storage (that's a no no)?
What cable are you using?
What port on your computer is it?


That "the error above should be fine blah blah" is only intended for the final command: adb shell rm /data/local/tmp/rageagainstthecage-arm5.bin
 
Upvote 0
Phone Make/Model: Moto Droid
Firmware Version: 2.2
ROM Version (ex. FRG22D): FRG22D
Windows Version: XP
Do you have admin privileges? Yes
Is your phone on USB Debugging? Yes
Have you turned on USB Storage (that's a no no)? No
What cable are you using? USB that came with it
What port on your computer is it? O
 
Upvote 0
yes I did, but not sure of your point?

(1) I didn't dog the OP - I appreciate it and said as much and think he is on the right track, but not there yet
(2) it isn't really a 1 click tool at this time
(3) though the old school method surely works, I think it archaic and dated and a true 1 click - like Easy Root - is the way rooting should go. so the end goal of the OP and my points are on the same page.
(4) people are already trying this and coming back with follow up questions.. which just means, as of this time, it is not a 1 click root tool as a 1 click root tool is just that with no process questions and clarifications needed. point and click.
(5) I do my darnedess to now help others based on that experience I had, but 1 hope is the creation of another truly 1 click root tool to make it easy on everyone

:thinking:

I'm just saying that RSD Lite is already as easy as it needs to be. People fear it and think it's such a complicated process, and I don't get why. Flashing an SBF is much more robust.
 
Upvote 0
watched the video and noticed that i dont get the same error as you. my error is as follows: mount: operation not permitted
failed to copy 'C:\Program Files\souproot\droidroot\Superuser.apk' to '/system/app/superuser.apk' : Read-only file system
reboot: Operation not permitted. so yeah need to make the phone a read and write file system but how is the question?
 
Upvote 0
with 1.6 I click on run and it brings up the command prompt box and this is what it does.

---------------------------------------------------------------------
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
0403889808010008 device

337 KB/s (0 bytes in 5392.000s)
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C

[*] checking NPROC limit ...
[+] RLIMIT_NPROC={1803, 1803}
[*] Searching for adb ...
[+] Found adb as PID 1912
[*] 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.
List of devices attached
0403889808010008 device

mount: Operation not permitted
failed to copy 'C:\Program Files\souproot\droidroot\Superuser.apk' to '/system/a
pp/Superuser.apk': Read-only file system
reboot: Operation not permitted
It should be done now. Enjoy!! :D


If there was an error a couple lines up,
that's normal so don't worry!
Press any key to continue . . .
--------------------------------------------------------------------

phone never does anything during the process.
phone isn't rooted.
phone never reboots automatically.

for people having problems, is this the same for you?
 
Upvote 0
watched the video and noticed that i dont get the same error as you. my error is as follows: mount: operation not permitted
failed to copy 'C:\Program Files\souproot\droidroot\Superuser.apk' to '/system/app/superuser.apk' : Read-only file system
reboot: Operation not permitted. so yeah need to make the phone a read and write file system but how is the question?

mine says the same thing
 
Upvote 0
No prob guys, I noticed the trend (just got home from class) and I'm analyzing the code. For some reason my computer (I'm guessing because I don't do a complete un-root on droid before testing) doesn't have that problem so skipping the step I still have su permissions or something.

Anyway, long story short don't download until my next release. I may have to revamp the code completely from scratch (again).

Sorry about all the problems and thanks for your patience!!
 
Upvote 0
with 1.6 I click on run and it brings up the command prompt box and this is what it does.

---------------------------------------------------------------------
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
0403889808010008 device

337 KB/s (0 bytes in 5392.000s)
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={1803, 1803}
[*] Searching for adb ...
[+] Found adb as PID 1912
[*] 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.
List of devices attached
0403889808010008 device

mount: Operation not permitted
failed to copy 'C:\Program Files\souproot\droidroot\Superuser.apk' to '/system/a
pp/Superuser.apk': Read-only file system
reboot: Operation not permitted
It should be done now. Enjoy!! :D


If there was an error a couple lines up,
that's normal so don't worry!
Press any key to continue . . .
--------------------------------------------------------------------

phone never does anything during the process.
phone isn't rooted.
phone never reboots automatically.

for people having problems, is this the same for you?


im getting just about the same thing, tried it a few times and rebooted after each time. and still no dice
 
Upvote 0
No prob guys, I noticed the trend (just got home from class) and I'm analyzing the code. For some reason my computer (I'm guessing because I don't do a complete un-root on droid before testing) doesn't have that problem so skipping the step I still have su permissions or something.

Anyway, long story short don't download until my next release. I may have to revamp the code completely from scratch (again).

Sorry about all the problems and thanks for your patience!!

cool ill keep my eyes out for the next update
 
Upvote 0
I found the problem, but now I have to figure out the answer. I'll most likely have to program in a different language (yay...) because of some silly little technical reasons. As for now, v0.8 (I think it was?) works because it requires the window to be on top while it manually types in commands for you. It's the only for-sure way of rooting as I now know the problem and hope my fellow coders get back to me soon with the alternative language to use.
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones