[GUIDE] Temp to permanent root, using rage instead of visionary

Search This thread
By:
Advanced…
T

trigeek

Member
Mar 2, 2006
17
17
There's already a guide here for obtaining permanent root using VISIONary, but some folks in #G2ROOT are having issues with the way that VISIONary modifies parititons. Using rage directly is a bit cleaner, since you know exactly what it's going to touch at each step of the way. I did NOT come up with any of this on my own, I'm building completely off of work that others have done. Speaking of which-

None of this would be possible without the tireless work that scotty2 put in. He stayed with the project for well over a month, through lots of smashed hopes and dead ends, until the solution was finally found. Were it not for his work, as well as the help of a few other key folks- we wouldn't be here. He deserves our thanks and some donations! We're talking hundreds of hours of work here, a couple bucks is not too much for that. :) His paypal is:
walker.scott@gmail.com​
Send him some love! I'm not asking for anything myself, because I spent a half hour putting this together, and that doesn't deserve any donations!


[size=+2]G2 ROOT INSTRUCTIONS[/size]
=================================================

These are modified instructions based on the ones posted at http://bit.ly/g2root that use Visionary. A number of people have run into issues with the way that Visionary juggles around temporary partitions, and using the original root exploit is a much easier, and cleaner method for achieving permanent root. This tutorial will walk you through the rooting process by first achieving temporary root, and moving on to permanent root.

[size=+1]REQUIREMENTS[/size]
=================================================

In the commands to run below, $ or # represent the prompt and should NOT be entered as part of the commands.

[size=+2]VERY IMPORTANT![/size]​
Visionary has caused filesystem corruption for some users during the rooting process. Before attempting the instructions below, make sure that you have "auto run on boot" turned OFF, and reboot your system. Since you will not need visionary anyway after this, you might as well just uninstall visionary and reboot NOW before doing anything.

[size=+1]TEMP ROOT[/size]
=================================================
ON YOUR PC:
Unzip the G2TempRoot files to a folder. From a cmd window or terminal, navigate to that folder and execute these commands:

Code: 
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*

ON YOUR PHONE:
  1. Launch Terminal Emulator
  2. /data/local/tmp/rage
  3. Wait for the message: "Forked #### childs."
  4. Menu > Reset Term - Terminal Emulator will exit.
  5. Launch Terminal Emulator, it Force Closes. Launch a second time, and you'll have a root shell
  6. **NOTE**: in the original directions from the XDA thread, you are instructed to run the /data/local/tmp/root script here. DON'T do this
    just yet. Leave the terminal window open.

[size=+1]PERM ROOT[/size]
=================================================
ON YOUR PC:
unzip the vision-perm-root.zip and navigate to that folder. There will be four files. You will need to push two of these to your phone- hboot-eng.img, and one of the wpthis-[..].ko files.

If you HAVE applied the OTA update, push wpthis-OTA.ko.
If you HAVE NOT applied the OTA update, push wpthis-pre-OTA.ko.

Code: 
$ adb push hboot-eng.img /data/local
$ adb push wpthis-OTA.ko /data/local


ON YOUR PHONE:
You should still have terminal emulator up, at a root prompt. Now run:
Code: 
# insmod /data/local/wpthis-OTA.ko
You should see:
Code: 
init_module 'wpthis-OTA.ko' failed (Function not implemented)
That means it worked. This next step is CRUCIAL. You must make sure that you are writing to the proper partition here or you could brick your phone. To be absolutely clear- the partition is mmcblk(zero)p(one)(eight)

Code: 
dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18

You should see some messages indicating that it was written. Next, run:

Code: 
# /data/local/tmp/root
This will lock in root, and give you 'su' access in the future. Next, run:
Code: 
# sync

Now wait at least a minute, just to be safe. After waiting, reboot your phone using the power button. After it finishes starting up, launch the terminal emulator, and type 'su'. You should get the prompt asking you to grant permissions. If you got the prompt, congratulations! You have permanent root!
 

Attachments

  • vision-combined-root.zip
    1.3 MB · Views: 7,126
Last edited:
  • Like
Reactions: marcimix, potatotree, agentmantis and 10 others
fattire

fattire

Inactive Recognized Developer
Oct 11, 2010
2,281
6,473
www.eff.org
I used these instructions and they worked brilliantly.

Sounds like it's a little safer than using VISIONary, which some people in the thread are reporting can get confused and not let you root because it thinks you already have root, etc.
 
F

fetusbeats

Member
Mar 27, 2010
21
0
I love it when a plan comes together. Perma-root. thanks man, i never had much luck getting visonary to work so this was spot on. worked like a charm
 
S

sinistersai4d4d

Senior Member
Oct 21, 2009
512
2
*not smart enough*

*leaves thread*

I really try to leave ADB out of the equation since I'm not comfortable navigating it.... I suppose I could dedicate my time to learning it, but it's not worth it since I would only use it once every two years to root my phone. In 16 hours I'm sure there will probably be a one click perm root method out anyway.
 
tazz9690

tazz9690

Senior Member
May 9, 2009
690
11
South Windsor
It worked flawlessly!

I always get so stressed when I root my phones, especially without tutorial vids.

I first did my G1 and that worked perfectly fine.
My second attempt at rooting was with my MT3G and that resulted in a bricked device because one of the lines of code was incorrect in the thread.
This, however, was clearly and plainly spelled out exactly to what happened to my phone.

I give you my thanks.
 
T

trigeek

Member
Mar 2, 2006
17
17
Awesome- glad to hear it's working well for people. If anybody sees areas that I could improve in the description just let me know.

sinistersai4d4d said:
I really try to leave ADB out of the equation since I'm not comfortable navigating it....
Click to expand...
Click to collapse

ADB is worth it IMHO because it makes moving files around easy, whether you're rooted or not. You don't have to turn on SD card storage, you can just do adb pull/push etc to grab or put files when you need them. Worth the effort. The one click root should be out within the next couple days though, you are right about that one.
 
Radioactive Death

Radioactive Death

Senior Member
Oct 14, 2010
78
2
Bristow, VA
trigeek,

I already perm rooted earlier, but just wanted to say you gave a very nicely detailed explanation that anyone should be able to follow. Well done!
 
R

ramainli

Member
Oct 5, 2010
26
0
Great guide. I liked it a lot more than Unforgivens just because it doesn't rely on VisionARY which might mess things up.
 
T

tornado9015

Member
Oct 29, 2010
24
1
Guide worked absolutely great, no problems. I did not try the visionary method first, but for some reason I just felt safer doing it in adb.

Thank you!
 
RaffieKol

RaffieKol

Senior Member
Feb 23, 2008
270
3
Los Angeles, CA
Sorry for the noob question...? but does this mean we have fully rooted to G2 and now we can load ROMS on it when they come out ????

Edit: Nevermind I didnt see the sticky
 
Last edited:
juanshop

juanshop

Senior Member
May 3, 2010
667
45
this is my first rooting on an android device... im freaking out... but here i go.... if something happens i will just report my phone lost and get a new one i guess ahahah still... im scared.
 
J

joackie27

Senior Member
May 25, 2010
567
59
Los Angeles, CA
Issues

I was temp rooted before using rage and then thru Visionary. But I decided to go back to stock till we have permanent root. I perm rooted today using this method. But I'm having the following issues:

1) adb remount
- remount failed: Operation not permitted

2) when using Root Explorer in /system, toggling Mount R/W does not work
- the only way to mount it R/O is thru terminal/adb shell. Once mounted R/O, the only way to mount R/W again is thru a reboot. Issuing mount -o remount ro /system either in terminal or adb shell does not work.
 
Last edited:
juanshop

juanshop

Senior Member
May 3, 2010
667
45
i actually changed my mind... im going to wait for a one click untended root i guess.... to scary...
 
H

hiddengopher

Guest
joackie27 said:
I was temp rooted before using rage and then thru Visionary. But I decided to go back to stock till we have permanent root. I perm rooted today using this method. But I'm having the following issues:

1) adb remount
- remount failed: Operation not permitted

2) when using Root Explorer in /system, toggling Mount R/W does not work
- the only way to mount it R/O is thru terminal/adb shell. Once mounted R/O, the only way to mount R/W again is thru a reboot. Issuing mount -o remount ro /system either in terminal or adb shell does not work.
Click to expand...
Click to collapse

make sure you have debugging enabled.
 
You must log in or register to reply here.

Similar threads

unforgiven512
  • Locked
[GUIDE] Perma-root and S-OFF!! (Both manually or if you used VISONary r12)
Replies
795
Views
419K
broncogr
broncogr
paulobrien
[GUIDE][ROOT][19/Nov] r14: VISIONary + one click root
Replies
743
Views
272K
demkantor
demkantor
Mikey
[ROM][NIGHTLY] CyanogenMod 7 for vendor Vision (HTC Vision)
Replies
12K
Views
2M
Y
yogi2010
I
[GUIDE] Permanent Root with Visionary/gfree (No ADB Required)
Replies
391
Views
174K
kbeezie
kbeezie
rmk40
[ROM][07/18/11] Virtuous Sense v2.0.0 :: Enhanced & Optimized Stock ROM (2.42.405.2)
Replies
7K
Views
1M
K
Kéno40

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 13
    T
    trigeek
    There's already a guide here for obtaining permanent root using VISIONary, but some folks in #G2ROOT are having issues with the way that VISIONary modifies parititons. Using rage directly is a bit cleaner, since you know exactly what it's going to touch at each step of the way. I did NOT come up with any of this on my own, I'm building completely off of work that others have done. Speaking of which-

    None of this would be possible without the tireless work that scotty2 put in. He stayed with the project for well over a month, through lots of smashed hopes and dead ends, until the solution was finally found. Were it not for his work, as well as the help of a few other key folks- we wouldn't be here. He deserves our thanks and some donations! We're talking hundreds of hours of work here, a couple bucks is not too much for that. :) His paypal is:
    walker.scott@gmail.com​
    Send him some love! I'm not asking for anything myself, because I spent a half hour putting this together, and that doesn't deserve any donations!


    [size=+2]G2 ROOT INSTRUCTIONS[/size]
    =================================================

    These are modified instructions based on the ones posted at http://bit.ly/g2root that use Visionary. A number of people have run into issues with the way that Visionary juggles around temporary partitions, and using the original root exploit is a much easier, and cleaner method for achieving permanent root. This tutorial will walk you through the rooting process by first achieving temporary root, and moving on to permanent root.

    [size=+1]REQUIREMENTS[/size]
    =================================================

    In the commands to run below, $ or # represent the prompt and should NOT be entered as part of the commands.

    [size=+2]VERY IMPORTANT![/size]​
    Visionary has caused filesystem corruption for some users during the rooting process. Before attempting the instructions below, make sure that you have "auto run on boot" turned OFF, and reboot your system. Since you will not need visionary anyway after this, you might as well just uninstall visionary and reboot NOW before doing anything.

    [size=+1]TEMP ROOT[/size]
    =================================================
    ON YOUR PC:
    Unzip the G2TempRoot files to a folder. From a cmd window or terminal, navigate to that folder and execute these commands:

    Code: 
    $ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*

    ON YOUR PHONE:
    1. Launch Terminal Emulator
    2. /data/local/tmp/rage
    3. Wait for the message: "Forked #### childs."
    4. Menu > Reset Term - Terminal Emulator will exit.
    5. Launch Terminal Emulator, it Force Closes. Launch a second time, and you'll have a root shell
    6. **NOTE**: in the original directions from the XDA thread, you are instructed to run the /data/local/tmp/root script here. DON'T do this
      just yet. Leave the terminal window open.

    [size=+1]PERM ROOT[/size]
    =================================================
    ON YOUR PC:
    unzip the vision-perm-root.zip and navigate to that folder. There will be four files. You will need to push two of these to your phone- hboot-eng.img, and one of the wpthis-[..].ko files.

    If you HAVE applied the OTA update, push wpthis-OTA.ko.
    If you HAVE NOT applied the OTA update, push wpthis-pre-OTA.ko.

    Code: 
    $ adb push hboot-eng.img /data/local
$ adb push wpthis-OTA.ko /data/local


    ON YOUR PHONE:
    You should still have terminal emulator up, at a root prompt. Now run:
    Code: 
    # insmod /data/local/wpthis-OTA.ko
    You should see:
    Code: 
    init_module 'wpthis-OTA.ko' failed (Function not implemented)
    That means it worked. This next step is CRUCIAL. You must make sure that you are writing to the proper partition here or you could brick your phone. To be absolutely clear- the partition is mmcblk(zero)p(one)(eight)

    Code: 
    dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18

    You should see some messages indicating that it was written. Next, run:

    Code: 
    # /data/local/tmp/root
    This will lock in root, and give you 'su' access in the future. Next, run:
    Code: 
    # sync

    Now wait at least a minute, just to be safe. After waiting, reboot your phone using the power button. After it finishes starting up, launch the terminal emulator, and type 'su'. You should get the prompt asking you to grant permissions. If you got the prompt, congratulations! You have permanent root!
    View
    1
    F
    fastludeh22
    backache said:
    I have the same issue. I have S-off but can't run /data/local/tmp/root without a lot of input/output errors.
    Click to expand...
    Click to collapse

    scoreo99 said:
    Join the club :(
    Click to expand...
    Click to collapse

    Guys if your s-off you've already won the battle. All you need to do is go the the clockwork mod recovery thread. Grab the recovery that says for manually flashing from fastboot. Put that img on the root of your computers c drive named recovery.img. then download rom of your choice, I suggest starting with my stock w/root rom, and put it on the root of your sdcard.

    *you will have to have adb/fastboot installed and working for this next step:

    boot the phone into fastboot. And on the computer type "fastboot flash recovery c:\recovery.img" when its done you will have cwm recovery. Select recovery from the menu on the phone. BACKUP first. Then wipe data and wipe cache. Then go down to flash zip from sd, select zip from sd, then select the rom u downloaded.(be sure to follow the instructions on flashing that rom in whatever rom u choose to uses thread). Once that's done, your done. Reboot and enjoy!
    View
    1
    steviewevie
    steviewevie
    hightechlive said:
    i get al the way to the end and there seems to be a problem with
    adb shell chmod 0755 /data/local/tmp/*
    because it says error cant find chmod
    Click to expand...
    Click to collapse

    The "chmod" command is built into Android, so that should work. Are you copying and pasting in that command like that ? You're not accidentally doing "adb *push* chmod", are you ?
    View
    1
    ddgarcia05
    ddgarcia05
    steviewevie said:
    The "chmod" command is built into Android, so that should work. Are you copying and pasting in that command like that ? You're not accidentally doing "adb *push* chmod", are you ?
    Click to expand...
    Click to collapse

    He I'm helping him root the phone. We just copy pasting the code. I believe he used visionary prior to using rage but was unsuccessful. We're now stuck with s-off but no root. I'll be using the hex editor shortly to restore stock and s-on then attempt to root with rage again. What do you think?
    View
    1
    steviewevie
    steviewevie
    okidongkii said:
    I tried to root my Desire Z, and for some reason maybe i missed the steps or something stupid,
    and now my phone is stuck on the HTC screen

    I removed the battery, put it back and tried to switch it on, nothing happened.
    I did the factory settings back from the recovery boot, and it still stuck.

    Is there anyway I can get my phone back?
    Click to expand...
    Click to collapse

    Did you try using Visionary before you used the "rage" method ?

    Can you get it into the bootloader (hboot), if you power off the phone, then hold Volume Down and then press the Power key till it turns on ? If so, what does it say at the top of the screen ?
    View

New posts