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

Root Scottys noob friendly root guide-start to finish

I am a bit late to the Rezound crowd but recently, my aunt switched her phone to the HTC Rezound and I'm trying to root it for her. I cannot unlock the bootloader because when I enter the command "fastboot oem get_identifier_token.", it gets stuck at waiting for device. Sorry if this has been answered before but any help? :confused:
 
I am a bit late to the Rezound crowd but recently, my aunt switched her phone to the HTC Rezound and I'm trying to root it for her. I cannot unlock the bootloader because when I enter the command "fastboot oem get_identifier_token.", it gets stuck at waiting for device. Sorry if this has been answered before but any help? :confused:

sounds like either a driver issue,or a "something running on the PC" issue

did you get a response from the previous command( fastboot devices )?

here are some basic trouble shooting steps for non-connectivity:
troubleshooting connectivity issues:
-try a reboot of the PC
-try different usb cables and ports
-dont use a usb hub
-dont use usb 3.0
-make sure nothing capable of comunicating with the phone is enabled and running. htc sync,pdanet,easy tether,and even itunes have all been known to cause issues.
-windows 8 has been known to have issues. try a windows 7 or older machine

failing the above,
-i use these drivers for fastboot and adb(donwload and run as admin): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe

failing that,try manually updating the drivers in the following manner:
-put the phone in fastboot mode(select fastboot from the hboot menu)
-open device manager on the PC
-plug in phone,watch for it to pop up in device manager.
-update drivers with device manager,pointing the wizard to the extracted
driver download folder from above

note that you can check the connectivity of the phone,and make sure drivers are working by in the following manner:
-open cmd window. change to directory containing adb/fastboot utilities

-adb with the phone in the booted OS,usb debug enabled,enter:
adb devices in a cmd window

-fastboot with phone in fastboot,enter:
fastboot devices in cmd window

in either case,a properly connected phone with working drivers installed should report back the phones serial number.
 
sounds like either a driver issue,or a "something running on the PC" issue

did you get a response from the previous command( fastboot devices )?

here are some basic trouble shooting steps for non-connectivity:

Thanks, I'll try this out when I get back home
 
So from what I've read, I should turn off s-on into s-off so that I can flash ROMs easily? S-off seems to be a risky and dangerous thing and I don't want to risk hardbricking the phone so if I turn off s-on, flash CM10 in recovery and reboot, the phone will work?
 
I'm not exactly sure what you're asking. If you'd like to stay s on and flash roms,read this: s-on and want to flash roms? READ THIS - Android Forums

Alright from that post, should I go to this link: http://androidforums.com/rezound-all-things-root/499172-how-manually-flash-roms.html#post3933400 and follow the instructions there? I tried flashing CM10 last night and it would get stuck at the HTC boot screen and never pass that so I figured I was doing something wrong and that seems to be that the kernel wasn't flashed due to S-On. Sorry if I'm not making myself clear.
 
Alright from that post, should I go to this link: http://androidforums.com/rezound-all-things-root/499172-how-manually-flash-roms.html#post3933400 and follow the instructions there? I tried flashing CM10 last night and it would get stuck at the HTC boot screen and never pass that so I figured I was doing something wrong and that seems to be that the kernel wasn't flashed due to S-On. Sorry if I'm not making myself clear.

appears as tho youve somewhat missed the point of the post. your permantly installed recovery is unable to install the boot image,wich is why cm10 would not boot. AOSP and sense kernels are not compatible(your stock sense kernel is still on the phone)

manually flashing the boot image via the linked thread is one way to skin cat. however,id go the other route: launch recovery into phone memory. that way,recovery can install the boot image,and all youll need to do is flash the rom.
more specifically,the directions youll need to follow are these:
some more detailed instructions

if you rooted with my guide,then you have seen this before. its basically the directions to "temporarily flash recovery"

for those that have rooted via other means,you can modify these directions to fit whatever folder you have adb/fastboot in,or you just use these directions:

download these files:
-mini-adb.zip: mini-adb.zip
-the latest amon ra recovery image: [Recovery] Amon Ra style vigor - xda-developers

first thing you need is drivers for adb to see your phone. if you have htc sync installed,you should allready have drivers. if not,you can install htc sync,or install these modified htc drivers from revolutionary (i recomand revolutionary drivers)

1)prepair ADB
-unzip your mini-adb.zip file. this is native funtionality in windows 7. you otherwise may need a utility such as "7-zip" to extract,or unzip it. place the unzipped folder onto the root of your C\ drive on your PC(sorry, you mac guys will need to develop this for yourself,i dont have a mac). root means the top level,not inside any folders. so just copy and paste,or drag and drop the folder onto C with everything else that is there. rename it to "mini-adb_vigor" since youll be putting some vigor(rezound) specific files in here. you actually can call it whatver you want,but directions from here forward will assume this folder to be named "mini-adb_vigor"
-open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
-change to your mini-adb_vigor directory. type the following at the prompt in your cmd window:

cd c:\mini-adb_vigor


2)launch a temporary recovery:
-move the image file you downloaded above for amon RA and place it into the mini-adb_vigor folder.

-type in your cmd window,or copy/paste the commands that are in bold

-check the md5 of your recovery image:

md5sums <recoveryname>.img

i.e.,if youre using an image named recovery-ra-vigor-3.15-gnm,then your command will be:
md5sums recovery-ra-vigor-3.15-gnm.img

**make sure the resulting md5 matches the one that drellisdee lists for the image that you downloaded. **
(if you use 3.15,then the md5 should match: 9d127cde10b68de5e424aaea2d4a4357)

-enable usb debugging on your phone and plug it in,charge only mode.

-check for connectivity:

adb devices

-it should reply with your serial number. if so,then:

adb reboot bootloader

-this will boot your phone into "fastboot" wich is a white screen with coloered letters.

-check for connectivity:

fastboot devices

-should return serial number

-temporarily launch your recovery to phone memory:

fastboot boot <recoveryname>.img

again,if youre using amon:
fastboot boot recovery-ra-vigor-3.15-gnm.img

-youll see a (really fast) green status bar on the top right as your PC sends the recovery to your phone. youll then see the HTC splash screen,then your recovery.

now that youre recovery is running,you have lots of options. you can mount usb storage to move things on and off the sd card if you need to. you can also flash the main version tool if you need to: main version tool.

note that once recovery is running,you can unplug from the PC if you want to flash your rom from the couch,ktichen table,or wherever :)

you can now restore a backup,or flash a rom. be aware that if you are still on gingerbread firmware(hboot 2.09.0000, 2.10.000, 2.11.0000) and are flashing an ICS rom,you will need to flash a special patch for the rom to work,AFTER flashing the rom: old firmware patch

last and not least,a couple notes:
-to paste into the cmd window,you must right click/paste. you cannot control/v
-to copy from the cmd window,right click. click mark. highlight everything to copy in white. now hit enter,or right click again.

holler if you have more questions :)

*there will be some refinements to this in a bit,ive got to step out for a bit...
 
Sorry for being such a bother lol, I'm just very confused as I've never messed with an HTC Device. As of now, I have no idea what to do to flash CM10. I see I have to flash a different kernel since the stock kernel isn't compatible with CM10. I read the instructions and I think I should 'launch a temporary recovery' and then flash from there after using a firmware patch? Is this correct?
 
Sorry for being such a bother lol, I'm just very confused as I've never messed with an HTC Device. As of now, I have no idea what to do to flash CM10. I see I have to flash a different kernel since the stock kernel isn't compatible with CM10. I read the instructions and I think I should 'launch a temporary recovery' and then flash from there after using a firmware patch? Is this correct?

almost ;)

no need for a firmware patch. just download cm10 and gapps,place them on your sd card. follow the directions above or in the root guide to launch a temporary recovery(you can do this even if youve allready installed permant recovery) then flash the rom normally.

-make a backup of stock
-wipe data/cache/dalvik cache
-flash rom
-flash gapps
-reboot :)

when a temporary recovery is launched,the phone behaves as if it were s off,and will flash the kernel for you- no need to do it seperately.

hope that helps,and you are not being a bother... it can be pretty confusing when you first get into it :)

not sure wich cm 10 rom youre looking at,but im about to try this one: http://forum.xda-developers.com/showthread.php?t=2113140 as it supposedly has working BT and the buglist is down to "camcorder only records in landscape" wich i can live with :D
 
Thank you very much! I finally got it to boot with your help! That is the CM10 I was looking at and now I'll see how it runs.
 
I've added my thanks to the list for this easy-to-understand guide. I'm late to the Rezound myself and heard it was hard to root, but your guide made it painless (even easier than my original DINC).

My only other comment is that I didn't use the 3.16 recovery because I could never get the md5sum to match regardless of how I downloaded or extracted it, so I used version 3.15 which went without a hitch. :)
 
Hi Scotty,
You have been so helpful to so many users, I was wondering if I could solicit some assistance. I rooted my rezound when ICS came around as an OTA on verizon, and have just been running stock, S-ON. Then Verizon comes up with this most recent OTA. At first I declined it, then later it snuck up on me and loaded on my phone automatically. The update installed successfully it appears, but my root is now gone. I can't get super user access or wifi tether etc. I also can't get into my recovery. I'm currently on build number 3.14.605.13 710RD. Do you know where I need to go from here? Thanks in advance for any help you can offer.
 
Hi Scotty,
You have been so helpful to so many users, I was wondering if I could solicit some assistance. I rooted my rezound when ICS came around as an OTA on verizon, and have just been running stock, S-ON. Then Verizon comes up with this most recent OTA. At first I declined it, then later it snuck up on me and loaded on my phone automatically. The update installed successfully it appears, but my root is now gone. I can't get super user access or wifi tether etc. I also can't get into my recovery. I'm currently on build number 3.14.605.13 710RD. Do you know where I need to go from here? Thanks in advance for any help you can offer.

you simply need to relaunch your temporary recovery,and reflash superSU :)
 
OK this is a very helpful thread and thanks so much i just need help because it gets stuck on waiting for device when i try to get the token and i tried installing your custom drivers and my windows 8 64bit said its not compatible with this operating system Can you please help me asap ive tried almost all i can think of.

PS: im new to this so can you explain it like im a kid i guess lol. Thank you alot

OH and now it sias when i type adb devices adb server is out of date then killing...
failed to start daemon can you help asap please

It doent recognize my device when i do fastboot devices but it does for adb devices please reply asap somebody
 
OK this is a very helpful thread and thanks so much i just need help because it gets stuck on waiting for device when i try to get the token and i tried installing your custom drivers and my windows 8 64bit said its not compatible with this operating system Can you please help me asap ive tried almost all i can think of.

PS: im new to this so can you explain it like im a kid i guess lol. Thank you alot

OH and now it sias when i type adb devices adb server is out of date then killing...
failed to start daemon can you help asap please

It doent recognize my device when i do fastboot devices but it does for adb devices please reply asap somebody

sorry your somewhat on your own for windows 8. ive read some stories of difficulty getting drivers and such to work.

your failed daemon may be a driver issue,or could be something running on the PC.

your fastboot device failure could be a driver issue,a something running on the PC issue,or the phone not in fastboot. when the phone is on the proper screen you should see fastboot usb on the phone screen when plugged in.

close out any programs capable of communicationg with the phone. pdanet,easy tether,htc sync,and even ituens can all cause prollems. you can also try different usb ports and cables when you dont get a serial number reply from adb/fastboot devices,and make sure youre not using usb 3.0.

you can try installing htc sync and see if it installs win 8 compatible drivers(make sure to uninstall the program itself afterward) or try a google search for "windows 8 htc adb/fastboot drivers" or something similar.

sorry i cant be of more help,but im win 7 x32,i dont have access to a 64 bit win 8 machine to try and duplicate your situations and find compatible drivers :(

might be easier on you if you borrow an older win xp/7 laptop for the purposes of rooting. you would then be on familiar ground ;)
 
ok thank you i found a video but when i install the drivers on my laptop i dont do anthing else right or how do i install them on my phone under the device manager right?


turns ot you have to disable driver signing and i did that so i just install the drivers right?
 
sorry your somewhat on your own for windows 8. ive read some stories of difficulty getting drivers and such to work.

your failed daemon may be a driver issue,or could be something running on the PC.

your fastboot device failure could be a driver issue,a something running on the PC issue,or the phone not in fastboot. when the phone is on the proper screen you should see fastboot usb on the phone screen when plugged in.

close out any programs capable of communicationg with the phone. pdanet,easy tether,htc sync,and even ituens can all cause prollems. you can also try different usb ports and cables when you dont get a serial number reply from adb/fastboot devices,and make sure youre not using usb 3.0.

you can try installing htc sync and see if it installs win 8 compatible drivers(make sure to uninstall the program itself afterward) or try a google search for "windows 8 htc adb/fastboot drivers" or something similar.

sorry i cant be of more help,but im win 7 x32,i dont have access to a 64 bit win 8 machine to try and duplicate your situations and find compatible drivers :(

might be easier on you if you borrow an older win xp/7 laptop for the purposes of rooting. you would then be on familiar ground ;)

Im afraid to do it on my neighbors computer just becuase i dont have the money to pay for a newone if i break it but do you have teamviewer so you can try to help me why it wont recognize it in fastboot everything works untill it gets to the fastbootmenu because then it never recognizes it in fastboot
 
Im afraid to do it on my neighbors computer just becuase i dont have the money to pay for a newone if i break it but do you have teamviewer so you can try to help me why it wont recognize it in fastboot everything works untill it gets to the fastbootmenu because then it never recognizes it in fastboot


Sounds like a driver issue. Sorry I don't have more info for ya :( some googling should hopefully turn up some win 8 comparible drivers. This issue actually is why i did not upgrade to win 8.
 
So I followed all the instructions in the OP at the very end when I installed SuperSU, it gave me a message that said "There is no SU binary installed, and SuperSU cannot install it. This is a problem!" What does that mean? I know I unlocked the phone because the fastboot screen said ***unlocked***
 
Sounds like you just tried to install superSU from the market,wich will not work.

You need to flash the zipfile from recovery. :)
 
Back
Top Bottom