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

Root .ru file question

Steven58

Former Heavyweight Champion of AF-Early Bird Club
Moderator
Feb 19, 2010
34,780
28,715
USA
I went to check if I could get 2.2 last night, after midnight. I could but didn't select it as I wanted to keep superuser access. Well, all of a sudden it's updating on its own! Too late!

It updated fine, but I lost super user access. So, here's my question:

1) I found the .su file in the bin directory. If I move it to Xbin will I get root back or have I blown it?

2) I tried moving it with astro file mgr, unsuccessfully. Is it not possible to do so or am I misusing astro?

TIA.

Steven
 
Upvote 0
One more question: Someone (elsewhere) said I will have no trouble getting root with the D2 method unless I had previously used 1 click root, which I did. Am I out of luck? I can live w/o root, but I love it so much and have paid for root apps, already.

TIA
 
Upvote 0
One more question: Someone (elsewhere) said I will have no trouble getting root with the D2 method unless I had previously used 1 click root, which I did. Am I out of luck? I can live w/o root, but I love it so much and have paid for root apps, already.

TIA

previously using 1 click root isnt going to effect using the D2 method. Rageagainstthecage (D@ exploit) is totally different than exploid(1 Click exploit) and will still work even if you have used a 1 click method. At least on the D1 it still did. I cant think of any reason that wouldnt also be true on the DX
 
Upvote 0
previously using 1 click root isnt going to effect using the D2 method. Rageagainstthecage (D@ exploit) is totally different than exploid(1 Click exploit) and will still work even if you have used a 1 click method. At least on the D1 it still did. I cant think of any reason that wouldnt also be true on the DX

Thank you! I'll try it tomorrow morning! (Thank you even if you take no responsibility! ;))

The bloatware is starting to really annoy me. And to tell the truth the screen moving all the time is starting to make me dizzy!
 
Upvote 0
Yaaaaay! I like "good to go!!!!!"

Can't wait to dump the bloat and regain the "power". I didn't remove bloat in anticipation of 2.2, because I didn't wanna deal with putting it back. Now, IDC. I won't hold my breath for Ginger.

I managed the bloat fine with autokiller root...very smooth. Now the bloat is making me lag a bit, but I'll fix it tonight!
 
Upvote 0
It didn't work. I used the one step process. I'm going to go through it a fourth time. sigh.

Here's the dos text:

Welcome to DarkOnion Root

Presented by: darkonion and facelessuser

Special thanks to: Sebastian Krahmer at C skills

If the following command takes too long to connect, close your terminal.
Disconnect your phone and make sure debugging is enabled, and you are set to PC mode

Checking for devices...
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.

Transfering payload.
-->Superuser.apk
'adb' is not recognized as an internal or external command,
operable program or batch file.
-->su
'adb' is not recognized as an internal or external command,
operable program or batch file.
-->busybox
'adb' is not recognized as an internal or external command,
operable program or batch file.
-->rageagainstthecage-arm5.bin
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.

We will begin to apply the tears of 1000 unicorns to root your phone.
This could take as long as 5 minutes. Please be patient...
10 seconds.
5 seconds.
4
3
2
1
'adb' is not recognized as an internal or external command,
operable program or batch file.
Reconnecting in 20 sec...
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.
Checking for device...
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.

Remounting system as RW
'adb' is not recognized as an internal or external command,
operable program or batch file.

Copying files to system
-->Superuser.apk
'adb' is not recognized as an internal or external command,
operable program or batch file.
-->su
'adb' is not recognized as an internal or external command,
operable program or batch file.
-->busybox
'adb' is not recognized as an internal or external command,
operable program or batch file.

Setting permissions
-->su
'adb' is not recognized as an internal or external command,
operable program or batch file.
-->busybox
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.

Clean up: deleting temp files
-->su
'adb' is not recognized as an internal or external command,
operable program or batch file.
-->busybox
'adb' is not recognized as an internal or external command,
operable program or batch file.
-->Superuser.apk
'adb' is not recognized as an internal or external command,
operable program or batch file.
-->rageagainstthecage-arm5.bin
'adb' is not recognized as an internal or external command,
operable program or batch file.

Congralations, you should now be rooted.
No Errors

Enter exit once to exit terminal.
Press any key to continue . . .
 
Upvote 0
Tried it again after uninstalling and reinstalling everything:

This is what I get:


Welcome to DarkOnion Root

Presented by: darkonion and facelessuser

Special thanks to: Sebastian Krahmer at C skills

If the following command takes too long to connect, close your terminal.
Disconnect your phone and make sure debugging is enabled, and you are set to PC mode

Checking for devices...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
015A97091101D00B device


Transfering payload.
-->Superuser.apk
192 KB/s (27688 bytes in 0.140s)
-->su
547 KB/s (26248 bytes in 0.046s)
-->busybox
1297 KB/s (1926944 bytes in 1.450s)
-->rageagainstthecage-arm5.bin
5 KB/s (5392 bytes in 1.000s)

We will begin to apply the tears of 1000 unicorns to root your phone.
This could take as long as 5 minutes. Please be patient...
10 seconds.
5 seconds.
4
3
2
1
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C

[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3815, 3815}
[*] Searching for adb ...
[+] Found adb as PID 1116
[*] 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.


Frustrating. Anyone can help?
 
Upvote 0
Thanks for your post. I noticed that some of my old programs seemed to be working a bit, but it was stalling as you said, so I just unplugged it. Then it said to reconnect and it would wait. Who am I to argue with a DOS dialog box, right? I did and then it seemed to finish.

Thanks for your help, I'm going to test it now.

Edit: Rooted baby!! w00t!

Steven does the happy dance!
snoopy_dance.jpg







Welcome to DarkOnion Root

Presented by: darkonion and facelessuser

Special thanks to: Sebastian Krahmer at C skills

If the following command takes too long to connect, close your terminal.
Disconnect your phone and make sure debugging is enabled, and you are set to PC mode

Checking for devices...
List of devices attached
015A97091101D00B device


Transfering payload.
-->Superuser.apk
1287 KB/s (27688 bytes in 0.021s)
-->su
1281 KB/s (26248 bytes in 0.020s)
-->busybox
1533 KB/s (1926944 bytes in 1.227s)
-->rageagainstthecage-arm5.bin
752 KB/s (5392 bytes in 0.007s)

We will begin to apply the tears of 1000 unicorns to root your phone.
This could take as long as 5 minutes. Please be patient...
10 seconds.
5 seconds.
4
3
2
1
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C

[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3815, 3815}
[*] Searching for adb ...
[+] Found adb as PID 9329
[*] 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.
Reconnecting in 20 sec...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Checking for device...
List of devices attached
015A97091101D00B device


Remounting system as RW

Copying files to system
-->Superuser.apk
-->su
-->busybox

Setting permissions
-->su
-->busybox

Clean up: deleting temp files
-->su
-->busybox
-->Superuser.apk
-->rageagainstthecage-arm5.bin

Congralations, you should now be rooted.
No Errors

Enter exit once to exit terminal.
Press any key to continue . . .
 
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