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

Root LTEVO ROOTING FOR DUMMIES {The Complete Guide}

Question. I don't have Windows 7 and need to root with the HTCDev. I read about the technical disadvantages, but I'm not sure what it means exactly. I looked at the ROMs and want to put Viper4G on. Will I need to do anything besides root with HTCDev and load the ROM?

Thanks for the help!

Cheers!
Doug

Sent from my EVO using Tapatalk 2 Beta-5
 
Question. I don't have Windows 7 and need to root with the HTCDev. I read about the technical disadvantages, but I'm not sure what it means exactly. I looked at the ROMs and want to put Viper4G on. Will I need to do anything besides root with HTCDev and load the ROM?

Thanks for the help!

Cheers!
Doug

Sent from my EVO using Tapatalk 2 Beta-5

what is your hboot? did you take the latest ota? you will not need to do anything special per se. just unlock via the HTCdev site and then get a custom recovery and then flash viper. make sure that you make a nandroid backup once you get a recovery insatlled and before you flash viper.
 
HBoot is 2.09

Yep, latest version of Android.

Thanks!

Doug

Sent from my EVO using Tapatalk 2 Beta-5

ok you are current with your radios then as well.......so you should be fine. nothing special you will need to do.

i believe that viper has the latest kernel installer and since you will be on stock sense rom then you should be ok. just keep in mind that with unlocked s-on the boot.img (where the kernel is located) will not get flashed when flashing roms. this can become an issues depending on what rom you are on now and what rom you plan on flashing. just make sure that you read the op for each rom you flash and you should be fine.
 
ok you are current with your radios then as well.......so you should be fine. nothing special you will need to do.

i believe that viper has the latest kernel installer and since you will be on stock sense rom then you should be ok. just keep in mind that with unlocked s-on the boot.img (where the kernel is located) will not get flashed when flashing roms. this can become an issues depending on what rom you are on now and what rom you plan on flashing. just make sure that you read the op for each rom you flash and you should be fine.

Thanks ocnbrze! I appreciate it!

Sent from my EVO using Tapatalk 2 Beta-5
 
Hey guys, I have a kind dumb question. Sorry if I missed an answer already posted - I did try to search for it.

I am still on hboot 1.15, on a Win7 64 bit machine, have my linux live cd (ver 12.10, 36 bit version) up and running, know what to do in terminal, and am ready to follow the dirty racun instructions. But: I am confused about what I am supposed to do with the actual phone.

1. I think I can have it plugged in from the beginning, on charge only with USB debugging on?
2. Should I put go into fastboot on the actual phone before I do step #5 (chmod 755 RabiesShot adb fastboot)?

Thanks much in advance.
 
Hey guys, I have a kind dumb question. Sorry if I missed an answer already posted - I did try to search for it.

I am still on hboot 1.15, on a Win7 64 bit machine, have my linux live cd (ver 12.10, 36 bit version) up and running, know what to do in terminal, and am ready to follow the dirty racun instructions. But: I am confused about what I am supposed to do with the actual phone.

1. I think I can have it plugged in from the beginning, on charge only with USB debugging on?
2. Should I put go into fastboot on the actual phone before I do step #5 (chmod 755 RabiesShot adb fastboot)?

Thanks much in advance.


1. Yes, you can just leave your phone plugged in at first. Make sure you have a good charge going in. :)

2. Yes, power the phone down and boot into the bootloader, with volume down and power, then select fastboot. It'll be highlighted in red. Follow the instructions from there. :)

Good idea to go to the section of the Unlimited website for RacunHunter at the bottom and download that file as well before you begin. This file is for recovering from Qualcom download mode in the unlikely event that it happens.

Make sure you're using a USB 2.0 jack, not a 3.0, and you're good to go!! :D

Let us know if you're successful / have any issues. Thats why we're here. :)
 
Hey guys, I have a kind dumb question. Sorry if I missed an answer already posted - I did try to search for it.

I am still on hboot 1.15, on a Win7 64 bit machine, have my linux live cd (ver 12.10, 36 bit version) up and running, know what to do in terminal, and am ready to follow the dirty racun instructions. But: I am confused about what I am supposed to do with the actual phone.

1. I think I can have it plugged in from the beginning, on charge only with USB debugging on?
2. Should I put go into fastboot on the actual phone before I do step #5 (chmod 755 RabiesShot adb fastboot)?

Thanks much in advance.

first off those are not dumb questions......no such thing really except the un-asked questions.....those are dumb:D

and yes all of what granite said above this post is correct.

now go and get your root on:D
 
OK thank you thank you thank you. That goes also to everyone here...I read like 20,000 posts here and in xda before I started. You'll laugh at where I got tripped up.

I had to re-run the last part of step #9 in the racun instructions because i got the error noted, the second time around it was fine. When it came time to paste the token into the htc website...here i had some trouble because it seemed like I was not able to copy the token from the terminal without including the line header (title?) that said bootloader at the beginning of each line. It seemed to me that I needed to get rid of those line headers first (and believe me, i tried, by copying into the word processing program and removing, then re-copying, etc). Finally just did a straight copy-paste without worrying about it and that worked.

Other than that, and firefox not liking the HTCdev website security certificate, it was 100% according to plan. Added bonus is that my significant other caught a few peeks at what was going on and now thinks that I'm Lisbeth Salander. Score.

Now I'm off to TWRP and superuser. I may be back for more help.

Thanks guys.
 
PS - one other thing - I did go and download racunhunter as recommended by granite before I started. But I could not get the MD5 checksums to match. Each time I was getting the same value, but it was not matching what was printed on their website. I'm confident I was doing it right because I did make sure the RUU checksums matched when I downloaded that. Never needed it though.
 
Final notes -
I did TWRP and superuser (almost) exactly as shown in the guide in OP. I was still in Linux when I did TWRP, so I downloaded it into the same folder as where I had the racoon and ran the fastboot command from there (with sudo ./).

Next, when trying to get into TWRP, I almost forgot that the phone re-checked the fastboot option under settings, power, so that I couldn't figure out how to get into bootloader for a minute. Once I did that, the first time I tried to go into recovery, it ignored twrp and rebooted into system. Tried it again and it worked fine.

Went back to windows (feeling less awesome somehow) to download and flash su file according to instructions, all went fine.

I had fun. Thanks again! Now I'm finally ready to spend a bunch of time customizing, because I know I can back it all up. And I think i'll try viper.
 
This seems like a good place for an easy question like this.
Is there a root-friendly version of the newest update yet? (3.16.651.3 7ORD (Jan. 31))
I obviously know more than enough to not take updates. And have seen some of the issues posted that have arisen with the new update. But I haven't seen anyone post an 'all clear' or that they've been worked around with a link to a clean file. (Tried searching a little to no avail)

I'm S-OFF with Viper's stock de-odexed version of the Jelly Bean update installed - I never updated radios. I'm not a hot ROMmer yet and don't feel like going that route yet even though some of the ROMs may have the update applied already.
 
The update didn't change hboot, and HTCdev unlock would work, as will Dirty Racun for permanent s-off. So roots like regaw's or a manual method ought to work. TWRP 2.4.1.0 will be required to deal with the latest firmware evil rolled into that update, some have reported issues with that, so we're watching.

Roms never include radio/firmware updates. To get those, you have to be s-off and flash as you would a rom, see our sticky for all kernels, roms and tools for the link for that.

You can update firmware if you're s-on by the complex process of re-locking, applying an RUU, updating, then unlocking and doing all root steps over again. With the invasive changes we see in each update's firmware, I've never been one to recommend that personally, I see s-off as a far safer way to go.
 
I'm just going to add that there is a new kernel and touch panel version in the update. The touch panel has been removed from the radio update files I believe. That will allow it to work with older 3.15 based roms. To Run the new 3.16 rom and kernel you will need to also update the touch panel to get it to function properly.

I believe the screen becomes unresponsive if you don't have the correct combo. Something to watch out for when flashing.
 
I'm just going to add that there is a new kernel and touch panel version in the update. The touch panel has been removed from the radio update files I believe. That will allow it to work with older 3.15 based roms. To Run the new 3.16 rom and kernel you will need to also update the touch panel to get it to function properly.

I believe the screen becomes unresponsive if you don't have the correct combo. Something to watch out for when flashing.

I must read to get my mind wrapped around this. I don't want to advise someone and get them in deep do-do.

Also, it's good to see you around AutoDrew!! ;)
 
Back
Top Bottom