Related
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:
[email protected]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]
=================================================
Visionary disabled at boot or uninstalled completely
Android Terminal Emulator app
ADB
vision-combined-root.zip (Attached to this post, OR these two files: )
G2TempRoot.zip (http://forum.xda-developers.com/showthread.php?t=797042) NOTE: only download the files! Don't follow these instructions yet
vision-perm-root.zip (http://forum.xda-developers.com/showthread.php?t=833965) NOTE: again, just download the files from the thread.
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:
Launch Terminal Emulator
/data/local/tmp/rage
Wait for the message: "Forked #### childs."
Menu > Reset Term - Terminal Emulator will exit.
Launch Terminal Emulator, it Force Closes. Launch a second time, and you'll have a root shell
**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!
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.
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
*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.
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.
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.
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!
Great guide. I liked it a lot more than Unforgivens just because it doesn't rely on VisionARY which might mess things up.
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!
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
RaffieKol said:
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 ????
Click to expand...
Click to collapse
You got it!
RaffieKol said:
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
Click to expand...
Click to collapse
Custome ROMs, custom Recovery...the whole 9 yards
Thanks for posting this, it was so easy!
Thank you so very much it was a success
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.
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.
i actually changed my mind... im going to wait for a one click untended root i guess.... to scary...
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.
juanshop said:
i actually changed my mind... im going to wait for a one click untended root i guess.... to scary...
Click to expand...
Click to collapse
Not gonna happen.
then i guess.... im going to jump in it.... wish me luck...
In the process of following the rooting wiki, had hella problems getting adb working. Got adb connected finally, got the money sign, tried first instruction, got adbermission denied. What could be the problem? Did a google search as well. I have the contents of adb tools, in the same place as g free, as it is completely impossible to start up adb shell, and then navigate to a completely different folder. Also, before moving adb tools, tried long addresses of the gfree stuff, same deal.
Did you do "adb shell" and then you tried more adb commands and got "permission denied" ?
If so, then that's because "adb shell" starts a command prompt session on your phone, and the adb commands need to be run on your PC, not your phone. So don't do the "adb shell" first.
So wait a second, you're saying that the wonderful wiki, either is in the wrong order, or requires me to follow the pc, and phone steps simultaneously? Because im running them from my pc. Which would be implied by my saying im following the wiki. Fyi, i meant the one on the g2, involving rooting the g2, on the xda-dev site. I've done this before, i know how to use adb. this is the first time i have rooted a g2. Don't mean to sound like a ****, but you basically didnt read anything i wrote.
The Wiki isn't in the wrong order. But IMHO it's very confusing that it shows a $ prompt when it shows "adb push" etc, because that makes it looks like it is run on the phone. But it's assuming you're running from Linux/Mac. On a PC the prompt for your adb commands would be C:\ or similar.
The Wiki doesn't tell you to run "adb shell"
So the answer to my question was yes, it works, but i had to wait 5 minutes to post this. I dont understand why there cant be a note that, unless you put adb into your path, cmd isnt going to recognize it unless its in the folder you're using. I feel no need to put a tool that i will use maybe once a year at most into path. also, when i just checked the wiki now, i noticed how the dollar signs had changed to c:/ ha ha. and sorry about the rudeness, at first it just seemed like you were making fun of me.
jenlow said:
Okay, so before i opened the adb shell from cmd, when i would type adb push, i would get adb is not recognized as an internal or external command. so, my solution of putting the adb tools into gfree, should work now once i cd to the gfree folder?
Click to expand...
Click to collapse
That's an issue with your path not being setup properly on your PC. You can adb adb's folder to the path to mean you can run it from anywhere. Otherwise you need to put the gfree tools etc in the same folder as adb, then cd to there and run the commands.
Or if the path is setup properly, cd to where the gfree tools are and start doing your "adb push" etc from there.
I have just edited the Wiki to show a "C:\" prompt for the stuff that's run on the PC, to try and avoid this confusion.
Did it work ?
jenlow said:
In the process of following the rooting wiki, had hella problems getting adb working. Got adb connected finally, got the money sign, tried first instruction, got adbermission denied. What could be the problem? Did a google search as well. I have the contents of adb tools, in the same place as g free, as it is completely impossible to start up adb shell, and then navigate to a completely different folder. Also, before moving adb tools, tried long addresses of the gfree stuff, same deal.
Click to expand...
Click to collapse
the "permission denied" thing... from the phone? Or from the computer? You know you need to be root in order to access the hardware, or at least set the permissions on the hardware to be accessible to your user account....???
And... you DID enable adb on the phone side, didn't you?
I used the Wiki and am now perm rooted. A few tips that may help you since they helped me to get it done. I opened a command prompt and noted the default path that opened. For me it was C:\Users\Ed . I used windows explorer to navigate there and open up the Ed folder and created a new folder in Ed that I named pr. This is where I unzipped both of the gfree zip files...into that same folder. When temp rooting and perm rooting, I simply opened up the command prompt, it opened to C:\Users\Ed and then I typed cd pr then I hit enter. That set me up to input the commands in the right place both times and it worked out just fine.
Another thing that I noticed. After temp rooting, I had to ctrl alt del to open up task manager and close down adb.exe (as noted in the instructions that appeared in terminal emulator). I couldn't load adb again until I closed it down and let it restart itself. When I entered the first command in the perm root process adb started up again by itself and all went well.
Good Luck! It is well worth it. I now have Cyanogen's latest stable build loaded along with the Google apps package that I found online.
Ed
OH! yeah, it did work. i thought i said that somewhere ha. I am currently running CM 6.1.1 now. I've decided that since the adb file, and necessary files are tiny i can just move them around to whatever i need to use adb for. Path editing should only be done by hand in linux And jesus CM has improved since i had it on my cliq. I'm like 90% sure i'm going to make a donation out of the school funds.
Root my phone!!! HELP
Hi Guys
I've tried root and my cell phone, but it is not. I've tried almost everything I have .. First I tried to root using the terminal emulator''''by typing different commands ..
Also, I tried the program''Visionary''but when I pressed the application so that it was held to root, but then the screen goes black, and I had to press the home button to get out of the situation ..
Also tried I saw another app called ''Universal androot'' and when I pressed root, then came the''Failed! No ~~~~~~~~~ Fu goo ..'' I also tried''app ''superoneclick I pressed the root, also came the''error: protocol fault (no status)''
What should i suppose to do, to fix this problem.. please reply
Thaaaanks!!!
mannær said:
Hi Guys
I've tried root and my cell phone, but it is not. I've tried almost everything I have .. First I tried to root using the terminal emulator''''by typing different commands ..
Also, I tried the program''Visionary''but when I pressed the application so that it was held to root, but then the screen goes black, and I had to press the home button to get out of the situation ..
Also tried I saw another app called ''Universal androot'' and when I pressed root, then came the''Failed! No ~~~~~~~~~ Fu goo ..'' I also tried''app ''superoneclick I pressed the root, also came the''error: protocol fault (no status)''
What should i suppose to do, to fix this problem.. please reply
Thaaaanks!!!
Click to expand...
Click to collapse
None of those apps work with the G2 to perm root without extra steps. And in that case only Visionary. You need to check out the vision wiki page.
Ed thoroughly described how to make it work. I did the exact same thing he did and got it last night.
jenlow said:
OH! yeah, it did work. i thought i said that somewhere ha. I am currently running CM 6.1.1 now. I've decided that since the adb file, and necessary files are tiny i can just move them around to whatever i need to use adb for. Path editing should only be done by hand in linux And jesus CM has improved since i had it on my cliq. I'm like 90% sure i'm going to make a donation out of the school funds.
Click to expand...
Click to collapse
What method did you use to root your cliq, and did you still have 3G? I have stock motoblur 2.1 on it now, I have it for a backup phone (got a G2), but I would like to root it.
I already posted this question in another thread but I figured this is the appropriate place for this question:
I'm a bit of a newb when it comes to rooting, but I ran into some trouble while I was perm rooting my g2 and I haven't been able to find a solution. I was following the temp to perm root method that g2hacks.com broke down simple, (g2hacks(dot)com/g2-hacks/how-to-root-g2-phone. While watching thier youtube video, I made it all the way to step 18 typing "/data/local/tmp/root" into terminal emulator. But right after I hit enter, a bunch of lines of errors popped up saying ""killall: can't kill pid 7891: No such process" all the way up to pid 7926. I continued anyway with #sync, and after I rebooted my phone I tried to use superuser but when I type "su" into terminal emulator it says permission denied. It looks like the phone is rooted cause now instead of the "#" prompt in terminal emulator it first starts with "$ $ " then goes to "$" after I try to do something. What went wrong, and how do I get it to work? Am I able to do everthing over again, or should I try again from a later step? Please help! Even if someone can tell me it won't hurt to do it all over again, that would be great. Thanks
If you don't have SU permissions, you aren't rooted.
I would guess you need to start over, but I'm not familiar with the procedure on the webpage you posted. I would recommend using the rage/gfree method. I think many/most on here agree its the safest and most up-to-date method:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
I am attempted to root my phone as the new guide on the wiki.
Once I get to this secion:
In this shell:
Remark: When you run su for the first time in the adb shell make sure the the screen of the phone is unlocked. Because when you enter the command the Superuser app will show up and ask you if you want to grant superuser access to app Unknown (2000).
Check the Remember check box and click allow.
$ su
# cd /data/local/tmp
# stop ril-daemon
# ./gfree_verify
I am unable to get SU to enable, it'll immidetly say permision denied and does not prompt anything on my phone and does not allow me to gain access so I am unable to verify Gfree
Thanks in advance for the help
What's the exact commands you're typing in the command prompt?
I have shell, so I type
$ su *$ is not typed, already shows in the command prompt*
but I think I know what I di dwrong and I am trying it again
Did you manage to get the root access?
Care to tell how it's done for you? Because I am having the same problem
I pretty much just followed the steps as stated in the wiki.
Just make sure you do all the steps required and more importantly that you type properly, thats what messed me up, I went like most of the way in to find out I forgot to do something properly @ the start.
You can also copy and paste the commands into your command line window which I did the second time round and that pretty much solved all problems for me , its fairly simple to be honest
Everything was going fine. I had gotten to the step 13:
Step 13. Wait for message: “Forked ???? childs.”, it should take like 5 seconds.
Hit Menu->Reset Term and Terminal Emulator should exit. Then launch the Terminal Emulator, it should force close.
Step 14. Open up Terminal Emulator again, you should see “#” prompt, it means you have temporary root. Next we need to make root permanent.
I mistakenly closed the command prompt that I had used to push the files to the phone. Now when I go to the next step (terminal emulator on the phone) I see the # promtp showing temp root, but when I type the next command, it says adb: not found.
Should I just reboot and start all over?
Nevermind, i got it working. I couldn't find how to delete this post though.