I have been searching and reading, but I still am unsure of which rooting method I should use. I just got my "new" EVO on Friday. Here are my specs:
HBoot 2.2
Hardware 0003
Baseband 2.15.00.09.01
Kernal [email protected]#17
Software 3.30.651.3
Any and all help would be greatly appreciated.
You have two choices:
option 1. Follow the directions and root your phone using these instructions that I copied from the thread below and use the following link to download the correct files: (http://forum.xda-developers.com/showthread.php?t=829045)
option 1 is not recommended for a noob...
option 2. Wait for unrevoked to come out with their update to unrevoked 3. If you wait, almost all of the root process will be automated. Unrevoked should be releasing this update in the next couple of weeks or so. They have been tweeting about it.
Directions from option 1 copied from thread link above:
1. Make sure that you downloaded and installed HTC Sync from HTC website.
2. Unzip hboot202-s_off-V71.zip to a folder in your C: drive. I used C:\hroot
3. This hroot folder should have a folder inside it called root. If you have a folder called hboot202-s_off-V71 then you need to move all the files from that subfolder to c:\hroot.
4. In Vista/7 slick on the start button and type in cmd. You will see in the program list the command prompt. Right click and open as Administrator.
5. In the command prompt type cd c:\hroot
6. On phone goto-> Setting>Applications>Debugging make sure usb debugging is on.
7. Connect the usb cable to your computer and phone. The phone should change it's screen to ask you what type of connection mode you want. Make sure that it is on charge only. Do not mount.
8. Type into the command prompt: adb push root/unrevoked-forever.zip /sdcard/ After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
9. Type into the command prompt: adb push root/mtd-eng.img /sdcard/ After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
10. Type into the command prompt: adb push pc36img/PC36IMG-ENG.zip /sdcard/PC36IMG.zip After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
11. Type into the command prompt: adb push pc36img/PC36IMG-MR.zip /sdcard/PC36IMG-MR.zip After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
12. Type into the command prompt: adb push root/flash_image /data/local/ After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
13. Type into the command prompt: adb push root/rageagainstthecage /data/local/tmp After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
14. Type into the command prompt:adb shell You should see a $, this means that you are "in" the phone.
15. Type into the command prompt:chmod 0755 /data/local/tmp/rageagainstthecage You should see this echoed on your screen. This is normal. You should still have $ on your cmd line.
16. Type into the command prompt: chmod 0755 /data/local/flash_image You should see this echoed on your screen. This is normal. You should still have a $ on your cmd line.
17. Type into the command prompt:./data/local/tmp/rageagainstthecage A message will pop up on the screen. It will take a few seconds, and your will be kicked "out" of the phone. The $ should now be gone.
18. Type into the command prompt: adb shell You should have a # on your command line instead of a $. # means you have temporary root in your phone. If you do not have #, then start over.
19. Type into the command prompt that has #: ./data/local/flash_image misc /sdcard/mtd-eng.img
20. Type into the command prompt that has #: sync
21. Type into the command prompt that has #: reboot bootloader
22. Your phone will be rebooting now. Eventually your phone will be at the bootloader menu. On your phone use volume up/down to highlight bootloader and press the power button once. It will start loading the PC36img.zip file.
23.After it loads, it will ask if you want to flash. Press Volume UP to say yes. It will now flash, which can take some time. You may see some red fail messages. This is normal.
24.When it is done flashing it will ask you if you want to reboot. Press Volume Down to say now to reboot.
25. Use volume up/down to highlight recovery. Press the power button once. This will try to boot into recovery mode but fail and load a screen with a red triangle. This is normal because you have not installed recovery yet.
26. Go back to your computer screen and your command prompt. You should not have a #
27. Type into the command prompt: adb push recovery /
28. Type into the command prompt: adb shell busybox --install /sbin
29. Type into the command prompt: adb shell nohup /sbin/recovery &
30. After a pause you should see a new screen on your phone. It should be green text with your recovery options.
31. Highlight backup/restore. Press the power button. Highlight backup nand and press the power button. Press the power button again to confirm the action. Your phone is now doing a nandroid backup. This will backup your wimax keys amongst other things.
32. It will take a little time to do the backup. After it is done press the power button once to return to the recovery menu.
33. Highlight enable USB-MS and press the power button.
34. On your computer, you should see a new drive in my computer or a pop up asking you for an action. Click on Explore, or open the drive in my computer, to access your phone like you would a thumb drive.
35. Rename the file named PC36IMG.zip to PC36IMG-ENG.zip and then rename PC36IMG-MR.zip to PC36IMG.zip
36. On your phone, press the power button to disable USB-MS mode. You should be back at the recovery menu.
37. Highlight the option to flash image from zip. Press the power button.
38. Highlight unrevoked-forever.zip and press the power button. Press the power button again to confirm if told to do so.
39. When it completes flashing the image, select reboot from the menu.
40. When it reboots a few things could happen. If you think your phone is frozen, you are okay because that is a normal occurrence on this step.
----->Your phone gets "stuck" on a white screen with the word HTC on it for more than a minute. You need to take the back case off your phone and pull your battery out. Put the battery back in and put the back case on again. Hold down Volume Down and press(and release) the power button while you continue to hold down the volume down button. Your phone should go into the boot loader like it did at the start of the guide.
----->You phone started up and fully booted. You need to completely power off.Hold down Volume Down and press(and release) the power button while you continue to hold down the volume down button. Your phone should go into the boot loader like it did at the start of the guide.
----->The phone returns to the boot loader.
41. No matter which of the 3 scenarios occurred to you in the last step, you are now in the boot loader. Obviously the 3rd scenario is the best, but all are OKAY.
42. The phone should find PC36img.zip. It then loads this file and asks if you want to flash. Use volume up for yes. When it asks to reboot press volume up for yes.
43. When it is done booting, return to your computer screen and type adb shell mv /sdcard/PC36IMG.zip /sdcard/PC36IMG-MR.zip into the command prompt.
44. Type into the command prompt: adb reboot recovery
45. Highlight backup/restore in recovery and then press power. Highlight backup nand and press power. Press power again to confirm. Wait for the backup to complete.
46. Press power to return to recovery menu. Highlight reboot phone and press power.
47. Your phone is now rooted, S-OFF, and booted into stock 3.30.651.2.
-------------------------------------------------------------------------
After Root:
1. Run through setup and get to the actual phone screens.
2. Try to turn on 4G/wifi/etc and see if it all works. It may not and this does not mean disaster.
For me, I had to flash Stock RUU root 3.30.651.3 to get 4G to work. Here is what I did next:
1. Download stock RUU root 3.30.651.3(I opted for Odexed version) from http://forum.xda-developers.com/showthread.php?t=836728
2. Reboot phone into recovery by completely powering off. Hold down volume down and press power. When you get into the boot loader it will try to find PC36img.zip and fail (we renamed that file remember?) and that is normal. Use volume up/down to highlight recovery and press the power button.
3. In recovery highlight USB-MS and press power to enable.
4. Your phone should be mounted as a drive in your computer again like before. Copy the whole zip file that you downloaded for RUU 3.30.651.3 rooted odexed to your phone. Wait for it to finish the transfer.
5. On your phone press power to turn off USB-MS mode.
6. On the recovery menu highlight wipe and press power.
7. Highlight the first wipe option which is something like wipe cache/factory reset. Press power. Press power again to confirm if needed.
8. Hightlight the second wipe option which is wipe cache. Press power and then press power again if needed.
9. Highlight the third wipe option which is wipe dalvik-cache. Press power and then press power again if needed.
10. Return recovery menu.
11. Hightlight flash image from zip and press power.
12. Highlight the file that you just transfered over that is for RUU 3.30.651.3 and press power. Press power again to confirm if asked. It will start flashing the image to your phone, but you will not see progress bars. It will take a few minutes.
13. When it is complete select the option to reboot the phone.
14. The phone should fully boot up into the stock rooted 3.30.651.3 rom.
15. Now try to turn 4G/wifi/etc on and make sure it works. It did for me.
16. Assuming that everything is working fine, fully power off, boot into recovery, and do another backup. This newest backup is your holy grail backup. It is stock rooted S-OFF and 4G working backup.
Note: these last 15 steps can be used to flash any custom rom too. Just make sure that you get your "holy grail" backup first before you experiment.
GOOD LUCK!
Thank you very much. I had been looking at the three different methods, I just wasn't sure which one to go with. I'm downloading the files now, but won't be able to do the thing until i get home. I had a Hero for the longest, and rooting that was pretty simple, but when I got the EVO and looked at the forum; I knew it wouldn't be quite as easy. I just wanted to be certain before I bricked my phone trying to fly blind. I'll let you know how it turns out. Thanks again, I really appreciate it.
You are welcome! I am sure you know this, but make sure you read through the thread first so you can see other hangups other people are having before you start the rooting process. If you have rooted a phone before, I am sure you can root the evo. Good luck!
Worked like a charm. 30 minutes, and I'm rooted. That went easier than I expected. Thanks again!
you are welcome...good luck with choosing a rom kernel combination. I dont flash a new rom or kernel very often (once a month) but right now i have myn 2.2 for a rom and baked battery #5 for a kernel with some setcpu profiles and it works great! I can get a full day of 10 hours of heavy usage (connected to exchange all the time) and lots of texts, web browsing etc and still have 20% battery left
I rooted my evo yesterday. I have super user and titanium backup but it still shows s-on. How do i change this. I used unrevoked.
what version is your hboot?
jay-are said:
I rooted my evo yesterday. I have super user and titanium backup but it still shows s-on. How do i change this. I used unrevoked.
Click to expand...
Click to collapse
if you still got s-on then you might need to run unrevoked forever. just go to this site.http://unrevoked.com/rootwiki/doku.php/public/forever and run the correct update.zip like you would another rom or kernel
weaselp1 said:
what version is your hboot?
Click to expand...
Click to collapse
i dunno about him. (y must i assume its a dude n not a female on these boards... tsk tsk) but i have hboot 0.97.000
I feel as if i missed my window of rooting my fone when i should of.. now theres a 1000 and 1 threads on the newer versions for newer fones.. and yes i've 'been' reading most of them.. and its all starting to stick. **and whats this i hear about the newer evo screens being more brilliant? anyways, can i follow those same directions u posted? 30 mins doesnt sound bad. even tho 30 seconds with unrevoked is pretty enticing. thanks for your time and effort. might even give u an actuall "thanks" above ur name. just seen those recently and been wanting to give em a try.
the reason i asked what version your hboot is: if you have hboot 2.02 or 2.10 you cannot use unrevoked at this current time; you must use the above method. I just wanted to make sure you had the correct hboot to use unrevoked. I have had a friend who made this mistake, and it broke his 4g and he had to get a replacement.
as far as using th above method, unless you have hboot 2.02 or 2.10, I would advise agianst it.
Sent from my PC36100 using XDA App
Some people are having trouble using unrevoked-forever on hboot 2.10 saying that their radio is not supported. Some people have not had trouble and the root worked fine. So, make sure you root before updating to the latest build.
weaselp1 said:
the reason i asked what version your hboot is: if you have hboot 2.02 or 2.10 you cannot use unrevoked at this current time; you must use the above method. I just wanted to make sure you had the correct hboot to use unrevoked. I have had a friend who made this mistake, and it broke his 4g and he had to get a replacement.
as far as using th above method, unless you have hboot 2.02 or 2.10, I would advise agianst it.
Click to expand...
Click to collapse
So with me having such an older hoot - 0.97.000, u would recommend what...?? Unrevoked? Thanks for ur time.
Yes, use the unrevoked method because of the version of hboot you have
Sent from my PC36100 using XDA App
Related
Ok so when i try to use rom manager, it says i need flash clockworkmod recovery. So i click on it n it says confirm model n i do, then it says "an error occurred while attempting to run privileged commands." Wat am i doing wrong?? Thanks.
Are you rooted? That's usually a good sign that you aren't.
Sent from my EVO from the Apple Store.
yea i went thro all the steps to root n in titanium backup it says root access is OK. so im confused now.
Make sure you have the latest version of Super User Permissions (2.2.2): http://forum.xda-developers.com/showthread.php?t=682828
When I got that error, it was because I hadn't told SUP to allow ROM Manager quick enough, and RM had timed out on the permission request.
ok so how do i get this onto my phone, i apologize, this is my first android phone.
tarheelsmj12001 said:
ok so how do i get this onto my phone, i apologize, this is my first android phone.
Click to expand...
Click to collapse
Just go ahead and download the zip file su-2.2.2-ef-signed.zip from that thread I linked to. Plug your USB cable into your phone and computer, and either go to Notifications, tap on Chareg Only, and then change it to Disk Drive and press done, then open My Computer (or if on Mac/Linux, double-click the drive on your desktop) and copy the ZIP file directly to SD card, or use ADB to push the file by first turning on USB debugging if it isn't already (Settings>Applications>Development>USB debugging) then open Command Prompt (Terminal on Mac/Linux), go to wherever you have ADB located (usually the Tools folder of the Android SDK) and use this command:
Code:
WINDOWS: adb push *path to ZIP*\su-2.2.2-ef-signed.zip /sdcard/
MAC/LINUX: ./adb puh *path to ZIP*/su-2.2.2-ef-signed.zip /sdcard/
If you used the ADB method: Go ahead and just use the command "adb reboot recovery" (or "./adb reboot recovery" if on Mac/Linux) to reboot into your Recovery. If you used USB Mass Storage, power off your phone, then hold down the Volume Down button, then continue holding Volume Down while holding the Power button. You will then see the bootloader screen (white screen with three skateboarding Androids at the bottom) and can let go of the buttons as soon as you do. Press Volume-Down to highlight "RECOVERY", and then the Power button to select it. Next you'll see the words "HTC EVO 4G" on a white screen (like a normal boot-up) followed shortly after your Recovery image.
Next, use Volume Up/Down to move your selection up/down and use the Power button to select "Install ZIP from SD Card" (or something along those lines). You should have one option for "install update.zip" and one for "Choose ZIP from SD card" (again, or something similar). Choose the latter of the two, and then use Volume Up/Down to select su-2.2.2-ef-signed.zip, and Power to select. Wait a few moments until you're told that the installation was successful, and then select to reboot the phone.
You should then be able to boot into Android, and have the Super User Permissions app installed! Whenever you try to run something which needs root, you'll get a pop-up asking for permission. Go ahead and launch ROM Manager, and you'll get the pop-up, make sure "Remember" is checked, and then press allow. If ROM Manager still complains that it didn't get permissions, re-launch it, and it should work fine.
drmacinyasha said:
Just go ahead and download the zip file su-2.2.2-ef-signed.zip from that thread I linked to. Plug your USB cable into your phone and computer, and either go to Notifications, tap on Chareg Only, and then change it to Disk Drive and press done, then open My Computer (or if on Mac/Linux, double-click the drive on your desktop) and copy the ZIP file directly to SD card, or use ADB to push the file by first turning on USB debugging if it isn't already (Settings>Applications>Development>USB debugging) then open Command Prompt (Terminal on Mac/Linux), go to wherever you have ADB located (usually the Tools folder of the Android SDK) and use this command:
Code:
WINDOWS: adb push *path to ZIP*\su-2.2.2-ef-signed.zip /sdcard/
MAC/LINUX: ./adb puh *path to ZIP*/su-2.2.2-ef-signed.zip /sdcard/
If you used the ADB method: Go ahead and just use the command "adb reboot recovery" (or "./adb reboot recovery" if on Mac/Linux) to reboot into your Recovery. If you used USB Mass Storage, power off your phone, then hold down the Volume Down button, then continue holding Volume Down while holding the Power button. You will then see the bootloader screen (white screen with three skateboarding Androids at the bottom) and can let go of the buttons as soon as you do. Press Volume-Down to highlight "RECOVERY", and then the Power button to select it. Next you'll see the words "HTC EVO 4G" on a white screen (like a normal boot-up) followed shortly after your Recovery image.
Next, use Volume Up/Down to move your selection up/down and use the Power button to select "Install ZIP from SD Card" (or something along those lines). You should have one option for "install update.zip" and one for "Choose ZIP from SD card" (again, or something similar). Choose the latter of the two, and then use Volume Up/Down to select su-2.2.2-ef-signed.zip, and Power to select. Wait a few moments until you're told that the installation was successful, and then select to reboot the phone.
You should then be able to boot into Android, and have the Super User Permissions app installed! Whenever you try to run something which needs root, you'll get a pop-up asking for permission. Go ahead and launch ROM Manager, and you'll get the pop-up, make sure "Remember" is checked, and then press allow. If ROM Manager still complains that it didn't get permissions, re-launch it, and it should work fine.
Click to expand...
Click to collapse
Damn i appreciate ur help n giving me the steps. Just one question, how do i get my command prompt to go to where my ADB is located, its stuck on C:\documents and settings. Thanks again for ur help n sorry for my stupidity.
When i go into my recovery n click on apply sdcard:update.zip, it says failed to open /sdcard/update.zip ( no such file or directory). Wat am i doin wrong??
tarheelsmj12001 said:
When i go into my recovery n click on apply sdcard:update.zip, it says failed to open /sdcard/update.zip ( no such file or directory). Wat am i doin wrong??
Click to expand...
Click to collapse
dont click that one, click the one that says install zip file or something, not update .zip
skittlesV1 said:
dont click that one, click the one that says install zip file or something, not update .zip
Click to expand...
Click to collapse
hmmm i dont have that option
skittlesV1 said:
dont click that one, click the one that says install zip file or something, not update .zip
Click to expand...
Click to collapse
Correct. There's usually two options, one of them being to choose to look for a ZIP file, and the other is sdcard:update.zip. You want to have it look for the ZIP file, and select it off of your card's root directory.
Oh, and to change what directory your command prompt is in, use "cd *path*" which is both for Windows, Mac, and Linux.
yea i dont have that option, only have the one to update.
What Recovery are you using? Perhaps your first step should be to get a better recovery image.
If u don't mind telling me how to do that then ill try n get a better one. N i have no idea which one i have.
Sent from my PC36100 using XDA App
Alright, at the top or bottom of your recovery mode's screen, it will usually tell you what recovery you have (ClockworkMod, Amon Ra, etc.).
To flash a new one, connect your computer and phone, and open up command prompt. Change to wherever you have ADB, and get ready for some fun.
First up, download recovery-RA-evo-v1.7.0.1.img (Amon_Ra's Recovery). Boot your phone into Fastboot by either using "adb reboot bootloader" or turn off you're phone, and turn it back on by holding Volume Down and Power. You'll get the white screen with the skating Androids again. Go ahead and select FASTBOOT. Now, in your command prompt/terminal, use this command:
Code:
fastboot devices
It should acknowledge that fastboot can see your phone. If not, try rebooting again. Once it sees your phone, use this command to flash the recovery:
Code:
fastboot flash recovery *path to file*\recovery-RA-evo-v1.7.0.1.img
Give it some time, and it should succeed. Then go on your phone, select bootloader, and then recovery. You should then boot into RA Recovery 1.7.0.1. Select "Flash zip from sdcard" and select the su-2.2.2-ef-signed.zip file. Give it a bit to do its thing, and then when it's all done, select "Reboot system now"
drmacinyasha said:
Alright, at the top or bottom of your recovery mode's screen, it will usually tell you what recovery you have (ClockworkMod, Amon Ra, etc.).
To flash a new one, connect your computer and phone, and open up command prompt. Change to wherever you have ADB, and get ready for some fun.
First up, download recovery-RA-evo-v1.7.0.1.img (Amon_Ra's Recovery). Boot your phone into Fastboot by either using "adb reboot bootloader" or turn off you're phone, and turn it back on by holding Volume Down and Power. You'll get the white screen with the skating Androids again. Go ahead and select FASTBOOT. Now, in your command prompt/terminal, use this command:
Code:
fastboot devices
It should acknowledge that fastboot can see your phone. If not, try rebooting again. Once it sees your phone, use this command to flash the recovery:
Code:
fastboot flash recovery *path to file*\recovery-RA-evo-v1.7.0.1.img
Give it some time, and it should succeed. Then go on your phone, select bootloader, and then recovery. You should then boot into RA Recovery 1.7.0.1. Select "Flash zip from sdcard" and select the su-2.2.2-ef-signed.zip file. Give it a bit to do its thing, and then when it's all done, select "Reboot system now"
Click to expand...
Click to collapse
Ok so i downloaded the recovery image. Where i get confused is when u say open the the command prompt and change to where i have ADB. So i go to start, run, n then type command?? N i dont understand when u said how to change what directory the command prompt is in, idk wat "cd *path*" means.
Where do you have ADB or the Android SDK?
To open command prompt, go to Start>Run and type cmd then hit enter. Then use the command cd (path to Android SDK)\tools\, so for example, I have my Android SDK in "C:\Program Files (x86)\Android SDK" so I would use cd C:\Program Files (x86)\Android SDK\tools\.
tarheelsmj12001 said:
Damn i appreciate ur help n giving me the steps. Just one question, how do i get my command prompt to go to where my ADB is located, its stuck on C:\documents and settings. Thanks again for ur help n sorry for my stupidity.
Click to expand...
Click to collapse
Dude it's not stupidity. This is the steepest part of the learning curve and there is actually not an easy answer. This drove me nuts when I first started to learn. But it's really fun once you figure it out.
First, follow the steps here: http://htcevohacks.com/htc-evo-hacks/how-to-install-android-sdk-and-adb-drivers-for-htc-evo-4g/
That will give you the SDK folder on your computer. I recommend that you extract the files directly onto the C: drive. That will give you the following path: C:\android-sdk-windows\tools (that will make more sense once you actually follow those steps.
Then, open a Command Prompt on your computer. If you use windows, it's under the Accessories folder on the Start menu. You obviously know this from your earlier post.
Then type the following:
Code:
cd C:\android-sdk-windows\tools
That should bring you to that folder. Everything you ever do that is "ADB" is done from this folder. That means that you actually need to put pertinent files into the "tools" folder there.
Once you are there type the following:
Code:
adb devices
If a long number shows up, then it sees your phone. There you go. If the above doesn't work, it might mean that you have to do another really annoying b.s. maneuver to your computer. Not worth mentioning if you don't have to do it. So just reply if this doesn't work and you can take it from there as far as troubleshooting.
Having said all that, the easiest way to install the new su zip file is to just put it on the your SD card, reboot into recovery, and choose install from SD card, and just choose it.
I would just like to thank u guys so much for ur help n def ur patience. I followed the steps u guys gave me n it worked flawlessly. Im so damn happy now lol, ive been trying to do this for sometime now. Now its time to get some ROMs on this bad boy. Once again, thank u very much guys for ur help, its nice to see ppl helping each other out on here so much.
tarheelsmj12001 said:
I would just like to thank u guys so much for ur help n def ur patience. I followed the steps u guys gave me n it worked flawlessly. Im so damn happy now lol, ive been trying to do this for sometime now. Now its time to get some ROMs on this bad boy. Once again, thank u very much guys for ur help, its nice to see ppl helping each other out on here so much.
Click to expand...
Click to collapse
You're more than welcome, just make sure to hang onto ADB and the Android SDK folders, and where they're are, as they'll be necessary for almost any ROM, upgrade, unlock, etc.!
Let me start by saying yes i'm fully rooted, ok now with that outta the way, im trying to a load new splash screen as explained here http://forum.xda-developers.com/showthread.php?t=722717, but the issue i'm having is where he say "Boot your phone into fastboot (hold vol up key while powering phone on, select fastboot)", shouldn't it be power and volume down, also when i go to cmd to type" fastboot devices" to see if the computer is recognizing my phone my first command line that comes up says C:\Documnents and Setting\Tom Harman>, i have a filling that should not be there, but either way it's not showing it's connected, should i have the phone set to charge only, or disk drive or what am i not doing right.
39 views, come one some has got to have something, searching has turned up no good results.
You check with this line.. adb devices. Will have a bunch of numbers and if it does your all good.
Sent from my PC36100 using XDA App
see i can't even get there since my first cmd line is C:\Documnents and Setting\Tom Harman>, i put in fastboot device, and it says not a internal or external command.
Boot the phone with volume up and it should bring you to a white screen with info about your phone. Select fastboot from the menu. When it talks about cmd, use windows explorer to navigate to the Android SDK folder on your computer. Find the tools folder and highlight the folder name and hold shift then right click and select open new command window here. Then type fastboot devices in the cmd window.
nukedukem said:
Boot the phone with volume up and it should bring you to a white screen with info about your phone. Select fastboot from the menu. When it talks about cmd, use windows explorer to navigate to the Android SDK folder on your computer. Find the tools folder and highlight the folder name and hold shift then right click and select open new command window here. Then type fastboot devices in the cmd window.
Click to expand...
Click to collapse
when i try this way of holding power and vol up, it buzz's 3 times and does nothing, then i have to pull battery just to start over, but if i hold power and vol down i can select fastboot, and it takes me to the red highlighted fastboot usb, but nothing about cmd.
You must navigate to the android-sdk-windows\tools folder. The path can be different for everyone. The location is where you extracted the android sdk to. Mine is at the root of the C drive.
Make sure USB debugging in Settings/Applications/Development is turned on and reboot into the bootloader (power+vol down)
Type this:
cd C:\android-sdk-windows\tools press enter
(The path you just typed should be displayed here)
Now type: fastboot devices
This should display something like HTxxxxxxxxxxxxxx
If it does, it worked. Just type your commands to flash the splash image.
Hope this helps
That's strange, did you flash an eng hboot? How did you root?
tomh1979 said:
when i try this way of holding power and vol up, it buzz's 3 times and does nothing, then i have to pull battery just to start over, but if i hold power and vol down i can select fastboot, and it takes me to the red highlighted fastboot usb, but nothing about cmd.
Click to expand...
Click to collapse
Thats referring to the command prompt terminal on your computer
dglowe343 said:
You must navigate to the android-sdk-windows\tools folder. The path can be different for everyone. The location is where you extracted the android sdk to. Mine is at the root of the C drive.
Make sure USB debugging in Settings/Applications/Development is turned on and reboot into the bootloader (power+vol down)
Type this:
cd C:\android-sdk-windows\tools press enter
(The path you just typed should be displayed here)
Now type: fastboot devices
This should display something like HTxxxxxxxxxxxxxx
If it does, it worked. Just type your commands to flash the splash image.
Hope this helps
Click to expand...
Click to collapse
that's the first time it confirmed my device, but it failed to flash, says remote not allowed.
nukedukem said:
Boot the phone with volume up and it should bring you to a white screen with info about your phone. Select fastboot from the menu. When it talks about cmd, use windows explorer to navigate to the Android SDK folder on your computer. Find the tools folder and highlight the folder name and hold shift then right click and select open new command window here. Then type fastboot devices in the cmd window.
Click to expand...
Click to collapse
i just followed what you said and held the UP VOLUME KEY and the power button at the same time, my phone vibrated 3 times, n now wont charge, or turn on, or work with volume down n power button... thanks a lot for the misleading info
nukedukem said:
That's strange, did you flash an eng hboot? How did you root?
Click to expand...
Click to collapse
the only way you could root the ota 2.2, which i have been able to do everything else from change roms, load boot animations, just can't do this, lol.
vikramjatt11 said:
i just followed what you said and held the UP VOLUME KEY and the power button at the same time, my phone vibrated 3 times, n now wont charge, or turn on, or work with volume down n power button... thanks a lot for the misleading info
Click to expand...
Click to collapse
just pull the battery, it'll be ok, i did that a few times too, lol.
If you power up the phone with the volume up held it should boot into fastboot. I was wrong about selecting fastboot earlier, I thought you had to select it, but it will boot directly into fastboot.
IDK how the 2.2 root is done, it sounds like you don't have an eng bootloader.
http://forum.xda-developers.com/showthread.php?t=752832&highlight=engineering+hboot
found the problem, it lies in the hboot, should be .76, but is .79, time to revert.
So I perm rooted and it says S-Off in fastboot and I have superuser access I believe.
I got rom manager and downloaded clockwork through rm. I try to install rom from SD card, select the baconbits rom, it asks to backup or clear, I have tried both.
The phone boots to htc screen, then shows a black screen with a phone and a red symbol over it. I waited 20 minutes on that screen and nothing happened.
I was able to push vol up and power to get a console but I can't load anything there. It will reboot just fine after that but I have no changes and still cannot overclock.
Does this have something to do with the user keys or whatever?
Thanks in advance for reading this and any help that gets offered. I hate to have my first post on a forum being a "help me" post.
Sent from my T-Mobile G2 using XDA App
Go into Rom Manager and try to flash Clockwork recovery again. This has happened to a lot of people... Flash it a second time, and it should be good.
Dan
Did you download the "g2-recovery-test-keys.img" from the 3rd post quoted below?
Place that file in the C:/android/tools or whatever your cd line is, which should in the tools folder. Now go the 6th step. FYI the sixth step I tried from fastboot and recovery, none worked until I reinstalled the drivers my computer kept prompting me for and immedatly got the OKAY's from the 7th step.
Edit: The code "fastboot flash recovery g2-recovery-test-keys.img" should be copied pasted onto your cmd.
ciwrl said:
Noob walkthrough:
1.Setup Android SDK and install drivers/udev rules as needed
2. S-Off your g2 http://goo.gl/Sc134
4. Copy vision-baconbits-0.3.zip to your sdcard, rename it update.zip (you can do this via adb using: adb push vision-baconbits-0.3.zip /sdcard/update.zip)
5. Reboot to fastboot mode (adb reboot bootloader)
6. Flash the recovery http://n0rp.chemlab.org/android/vision/g2-recovery-test-keys.img : fastboot flash recovery g2-recovery-test-keys.img (if you get 'waiting for device' your phone either isnt in fastboot mode, or you will need to fix your sdk drivers)
7. You should get two 'OKAY's once recovery flash is complete
8. Press the power button once; then the vol down button to highlight 'recovery'; then the power button again to select the 'recovery' option
9. The phone will reboot to recovery
10. Press volume up+power to show the recovery menu
11. Select the 'Apply:update.zip' option, using volume keys to navigate, and power button as [enter]
12. Once the zip applies, reboot
If you get signature verification errors on the zip, it means your fastboot flash of recovery failed to apply, redo it
Click to expand...
Click to collapse
Bingo, That worked. Glad it was that simple. I actually had to flash clockwork a third time to get it to go all the way.
Sent from my T-Mobile G2 using XDA App
Alright guys, this post is just for reference and ease. I've been using xda ever since I got my old HTC Hero a year and a half ago. Now I have the EVO and xda has been nothing but helpful to me. I've decided to make this post to try to help anyone that might not know much about android so I will make this a simple, easy to understand post tutorial.
HTC EVO 4G 2.3 Gingerbread root tutorial:
(Step 1) Power down your phone and take the battery out. Printed on the phone under the battery is a serial number. It is on the bottom line and usually starts with the letters: HT then a series of numbers and letters. Write this code down for you will need it later.
(Step 2) Download superuser from this link: http://www.mediafire.com/?q3ujsx1m4uq1662.
(Step 3) Download the HTC drivers from this link: http://api.viglink.com/api/click?for...13139469417033
(Step 4) Plug your phone to your computer and put the phone in disk drive mode. Now put the superuser .zip on the sdcard and change the mode to charge only.
(Step 5) Put the phone in usb debugging mode. Do this by: home>menu>settings>applications>development>usb debugging.
Also, enable fastboot. Do this by: home>menu>settings>applications>fastboot.
(Step 6) Got to: http://revolutionary.io/ Go down to the downloads section and select either windows or linux. (depending on your machine) Allow the file to download and proceed to the beta key generation.
(Step 7) Select your operating system (windows or linux) and your device and hboot version.
If you are unsure of your hboot version you can check by powering down your phone and holding volume down and the power button (make sure fastboot is turned off before doing this. just make sure to enable it again once you have checked and have the phone powered back up.)
Now enter your serial key (the code you got from under the battery.) select generate key and it will give you a beta key.
Make sure to keep the window open.
(Step 8) Extract the revolutionary.zip and run revolutionary. It should recognize your device and then ask for the beta key. Enter the beta key it gave you, remember it is case sensitive.
(Step 9) Revolutionary will now work its magic. Let it do its thing and DO NOT interrupt it. It may seem like it is frozen but it sometimes just takes a few minutes.
(Step10) After it gets done with all of its operations, revolutionary will ask if you want it to connect to the internet and download the recovery. type the letter "y" and hit enter. It will do it and then reboot.
(Step11) Now you need to flash the superuser .zip. Disable fastboot and and usb debugging and power down the device. Hold volume down and power at the same time until you get the hboot menu. It may check for an image and shouldn't find one. Just let it do its thing. Volume down and select recovery. It will reboot into recover. Now just volume down to install .zip then select choose .zip from sdcard and choose the su 2.3.6.3 efgh signed.zip and select yes. It will flash it. When it is done just reboot.
Congratulations. You are now rooted with superuser and s-off and have full root access.
Thank you, xda. I am grateful for this forum of great and helpful people, without you guys my android life would would be simply mediocre.
You don't need to get the s/n from behind the battery. When you run Revolutionary, it outputs the serial number immediately before the prompt requesting a beta key. Plus, the format of the s/n is a little confusing, and if you don't enter the s/n exactly as Revolutionary expects, you'll get an invalid Beta key error and have to restart Revolutionary. You can cut and paste the s/n and the key to keep things simple. Also, make sure to check if there's a market update of Superuser once you install it via the zip file. I was able to fix an issue of frequent force closes this way.
Oh yeah, and the phone should be in Charge Only mode with debugging, not disk drive.
warnning: any damage you do to your phone following these directions is your responsibility. Assume you warranty is void if your are rooted.
I used the information koush provided here and info birdman provided here and adopted it in Ubutnu Linux 11.10. I hit some bumps along the way using my Linux box so I decided to write this for those of us not using OS's made by the darkside This should also work with Ubuntu 12.04 LTS just fine.
All this should work with Linux Mint 12 also.
1- Set up Android SDK, adb, and fastboot in Ubuntu Linux using the links in my signature. I can't stress how useful and easy it is to set adb and fastboot in your "path" so you can easily use it from any prompt. The links explain it. Take your time with that and it will payoff for all your devices. Here is the guide I wrote http://forum.xda-developers.com/showpost.php?p=19446284&postcount=62
STOP NOW! EVERYTHING INCLUDING YOUR PERSONAL FILES, PICTURES, AND VIDEOS WILL BE ERASED WHEN YOU UNLOCK/ROOT THIS DEVICE. It does not have a physical SD card. Very annoying. Use Dropbox or Google+ to backup everything.
2- on your phone, go to settings/Developer Options and check the box for USB Debugging
3-connect your phone, fire up a terminal, and type:
Code:
adb devices
You should get the serial number of your device appear. If not, unplug, reboot phone, re-attach the phone to your computer and try again. If you still do not get your device's serial number, go back to step 1 and make sure everything is setup correctly.
4- Now download Clockwork Recovery from here
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.5.0.4-toro.img
(make sure it's the CDMA one (toro). The GSM one is called maguro and steps should be the same)
and su.zip from here
http://download.clockworkmod.com/test/su.zip
5-Turn the phone off, hold both Volume up and Volume Down and press the power button. You should come to a screen that has a big arrow and some writings at the bottom (fastboot). Last line should say Locked state.
6- Connect your phone to your computer, fire up a terminal and type:
Code:
fastboot devices
your phone and its serial number should appear just as it did using adb above. adb will not work here of course. If you don't see your device, go to step one. I guess you can download the fastboot for linux and cd to that directory and do it but I like to have it setup on my computer.
STOP NOW! EVERYTHING INCLUDING YOUR PERSONAL FILES, PICTURES, AND VIDEOS WILL BE ERASED WHEN YOU UNLOCK/ROOT THIS DEVICE. It does not have a physical SD card. Very annoying. Use Dropbox or Google+ to backup everything.
7- Now for the stuff that voids your warranty: Type
Code:
fastboot oem unlock
and enter. Look at your phone now, use the Volume up to choose YES and press the power button to accept. It should say that you are unlocked and fastboot is in good state.
9-use the volume up to change the value appearing in the arrow to recovery and press the power button to accept. You are taken to laying down android with a red triangle. This is the stock recovery. Now carefully press the volume up, volume down, and the power button to get to a menu. Choose wipe data and factory reset. 2 things: I had a hard time getting to the menu. Do it a few times and try pressing the power button JUST a fraction of a second earlier than the 2 volume buttons. Also wiping and resetting takes a few minutes, be patient.
10-you are now unlocked. Turn the phone off ( I pulled battery), go to fastboot screen by holding volume up, down and power button. Connect your phone to your computer and make sure it is recognized by typing:
Code:
fastboot devices
If it is, change directory to where you downloaded clockwork recovery. If you didn't change it, it should be the Download directory (remember it's case sensitive):
Code:
cd Downloads
11- Time to re-write your recovery:
Code:
fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img
Please make sure you use common sense here when it comes to file names. If the file you downloaded has a different name or version, change it in the code above. I guess you can put the fastboot file in that location also to be used if you do not have it setup as in step 1. I'm not positive how and if that would work. Downloading and installing the wrong file is a mistake that may cause harm to your phone.
12- Use the vol up/down to point the big arrow toward recovery, push the power button to get to Cloclwork Recovery. Once you confirm you have CWR, reboot the phone normally and let Android OS create all the folders it needs. Once at start up screen, pull the battery to turn phone off, and then get to bootloader by holding vol up/down and power button in. Use the vol up/down to point the big arrow on sceen toward recovery. While in recovery, make sure your terminal prompt still shows the Downloads directory (or where the su and recovery files were downloaded to). Now type: (note the space between zip and /data)
Code:
adb push su.zip /data/media
this will put the su.zip file in the root of your virtual sd card.
You are still in recovery, reboot into recovery to refresh the file list by typing this
Code:
adb reboot recovery
Now go ahead and install su.zip through clockwork recovery's menus. Pretty self explanatory (choose zip from sd card). The su.zip should be now in the root of your virtual sd card.
That's all. You are now unlocked and rooted. Reboot. Make sure you install the paid versions of rom manager, titanium backup, and update superuser app.
13- Download Rom Manager and flash the recovery again (top choice). This will erase the install-recovery.sh file and keeps your CWR at each boot. You do not have to do step 14 if you do this. I will leave step 14 here just in case someone needs it.
14-When you are back in the fastboot screen. DO NOT reboot the phone here. There maybe a file that re-writes the recovery to stock if the phone is rebooted. Your phone may or may not have this file. of the two GN I have, one did and one did not at this step(may have been erased). The file is reovery.sh and is located in /system/etc/ . You need to either rename it or delete it.
While in fastboot and after you flashed CWR, use the Volume up and Down to change the arrow's value to recovery and press the power button. You should now see the familiar Clockwork recovery. In recovery, you can use adb (you can't in fastboot of course). You need to rename that file, use these steps in terminal: (If you see no file/folder found message, you know you do not have this file)
Code:
adb shell
Code:
mount -o rw,remount /system
Code:
mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak
step 1 fires up adb, step 2 allows you to change permissions and read and write, and step 3 renames it. You can now unplug the phone.
Again, you can also get rid of this file by flashing the clcokwork recovery in Rom Manager or using the paid app root explorer to rename the file.
Once again referrence links:
http://rootzwiki.com/topic/12013-welcome-to-rootzwiki-editionstep-by-step-oem-unlock-and-root/
https://plus.google.com/103583939320326217147/posts/1Jsh9xPwnQP
thank you so much this is exactly what i was looking for. cant believe im the only one to comment on this. it is very detailed even some one new to Ubuntu could figure this out.
I've been using it too for a while but never posted so THANK YOU! Very easy to follow. Great work.
you're welcome. I find it ironic that a Linux based OS such as Android has so many HOWTOs for Windows but not enough for Linux. #powerofmonoply
I find I need to run fastboot commands with sudo or su into root before it will work. Same for you, or misconfig on my side?
Sent from my Galaxy Nexus using XDA
ual4720 said:
I find I need to run fastboot commands with sudo or su into root before it will work. Same for you, or misconfig on my side?
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
I'm not sure. How did you setup your adb and fastboot? I did not have to sudo for fastboot commands. What OS are you running?
Hey loveubuntu, I have a question.
I'm at Step 12, and I'm in recovery and when I run adb push su.zip /data/media, it isn't finding any devices. When I run adb devices, the device isn't listed.
Any advice?
AndroidSparty said:
Hey loveubuntu, I have a question.
I'm at Step 12, and I'm in recovery and when I run adb push su.zip /data/media, it isn't finding any devices. When I run adb devices, the device isn't listed.
Any advice?
Click to expand...
Click to collapse
were you able to see the device in the previous steps 3, 6 and 10 and now you don't?
Things that come to mind is:
1- Do you have the usb debugging checked?
2- unplug and replug the device and see if it works.
3- don't forget the samsung recovery file install-recovery.sh. If the phone is rebooted you may have re-written your recovery and have to start over. Then reboot the phone and go to rom manager and reflash the recovery (first option). This will take care of the install-recovery.sh file.
loveubuntu said:
were you able to see the device in the previous steps 3, 6 and 10 and now you don't?
Things that come to mind is:
1- Do you have the usb debugging checked?
2- unplug and replug the device and see if it works.
3- don't forget the samsung recovery file install-recovery.sh. If the phone is rebooted you may have re-written your recovery and have to start over. Then reboot the phone and go to rom manager and reflash the recovery (first option). This will take care of the install-recovery.sh file.
Click to expand...
Click to collapse
3, 6, & 9...check.
I rebooted my phone by pulling the battery and I still can't get adb to see the device. The install-recovery.sh? I don't remember reading anything about that.
In step 12 it says to let the phone reboot into the Android OS, but it's now back at factory reset, as that's what we did earlier in the instructions. As soon as it boots into the Android OS, adb lists the device.
At that point, since I'm in the AOS, I downloaded Astro File Manager and tried to put su.zip in the /cache folder, I think that's the folder that the clockwork recovery mod folder sees, and I don't have permission. I was hoping I could cheat and just drag & drop instead of pushing it. BUT...I did try the command adb push su.zip /media/play and I get permission denied. I'm guessing I don't have permission, even as sudo, to move the file to /data/media.
Okay I finally got it!
I didn't wait long enough for the Android OS to boot up. I finally was able to move the .zip file, but I couldn't find where /data/media was. So I let the OS boot up, removed the battery, went back into recovery, moved the zip file, and it was finally listed.
Ordered a Galaxy Nexus too, will definitely be using this guide. Windows guides are confusing.
Forceflow said:
Ordered a Galaxy Nexus too, will definitely be using this guide. Windows guides are confusing.
Click to expand...
Click to collapse
>Windows guides are confusing
>Windows guides
>Windows
Root of the issue
But agreed, this was a good supplement to follow for Ubuntu.
Sent from my Galaxy Nexus using xda app-developers app
Thank you for this guide. Some how I like the Linux method better than the Windows ones.
12- Use the vol up/down to point the big arrow toward recovery, push the power button to get to Cloclwork Recovery. Once you confirm you have CWR, reboot the phone normally and let Android OS create all the folders it needs. Once at start up screen, pull the battery to turn phone off, and then get to bootloader by holding vol up/down and power button in. Use the vol up/down to point the big arrow on sceen toward recovery. While in recovery, make sure your terminal prompt still shows the Downloads directory (or where the su and recovery files were downloaded to). Now type: (note the space between zip and /data)
Click to expand...
Click to collapse
This step is confusing. While in recovery should be replaced by "Hit Power button to enter ClockworkMod Recovery"
Otherwise people may mis-interpret by "Stay in fastboot and position the big arrow on top to Recovery Mode"
In my case (GNex GSM stock JB 4.11):
adb push su.zip /data/media
or
adb push su.zip /sdcard
did copy su.zip successfully but could not be listed by ClockworkMod Recovery menu when selecting "choose zip from sd card". I had to do this:
Code:
adb push su.zip /sdcard/Alarms
And, within the ClockWorkMod Recevery menu, select "choose zip from sd card"
Land on another screen where I could navigate to Alarms folder and see the su.zip there.
Now go ahead and install su.zip through clockwork recovery's menus. Pretty self explanatory (choose zip from sd card). The su.zip should be now in the root of your virtual sd card.
Click to expand...
Click to collapse
Sorry for being picky but personally, it is NOT self explanatory for me. I was expecting a menu item in CWM Recovery menu to say "Install su.zip". Actually you must navigate in the file system and select the su.zip yourself. Ok, may be that seems obvious now that I know what to do. But on the moment, I was worried I screwed up something because I needed to do some extra manipulations while you said that should be "self explanatory".
4- Now download Clockwork Recovery from here
Click to expand...
Click to collapse
You may want to up date the link, ClockWorkMod now has a Recovery program which is touch sensitive:
GSM: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.1.0-maguro.img
Sprint: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.1.0-toroplus.img
VRZ: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.1.0-toro.img
Step 12 finishes with
That's all. You are now unlocked and rooted. Reboot. Make sure you install the paid versions of rom manager, titanium backup, and update superuser app.
Click to expand...
Click to collapse
Therefore what is the need of doing #13 and 14?
Furthermore, Step 13 starts by
13- Download Rom Manager and flash the recovery again (top choice)
Click to expand...
Click to collapse
What is that top choice? Do you mean restart from the top at step #1? If you need to reflash again CWN, would it be simpler to restart from Step 10 instead of going back to the top?
And BTW, what is the reason to reflash the CWM Recovery again just after you have successfully flashed it at Step 12? Could that be #13 and #14 are some steps of an older guide which no longer apply now but you forgot to remove?
Sorry for the silly question but I am rather lost. After all that hardwork, when I attempt to Update SuperUser, it failed on the line "Gaining root access ..." What is the reason and how to fix that? FOUND ANSWER: the su.zip given in the post is Superuser 3.07 which is outdated, It is probably buggy. Replaced it by SuperSU 0.94 and it works perfect: http://download.chainfire.eu/204/SuperSU/
Thanks
worked like a charm.. if you have problem using fastboot, just cd to the folder with fastboot and run it like this:
Code:
sudo ./fastboot "command"
it will require your password and then work normally, seems like it need super user permissions.
Also for new user: to avoid writing a command or a folder name manually just push the TAB button, it will autocomplete the word if it's unique in that folder