ok,i keep seeing the same questions being asked over and over,so i decided to go ahead and make up my own guide. i maintain alot of stuff in the TB and inc forum still,so i was originally leery of adding to my list of threads to support,but hopefully i can spell it out a lil clearer than some of the current guides. i know reading thru htcdevs directions,and looking thru some posts here it can seem overwhelming,but when y ou break each step down its all really easy.
the basic steps will be:
1)unlock with htcdev
2)temporarily or permanently flash a recovery
3)flash root files
before you start,go ahead and download these files:
-mini-adb.zip: mini-adb.zip
-the latest amon ra recovery image: [Recovery] Amon Ra style vigor - xda-developers
-superuser files: forGB or ICS,use the latest superSU from this thread on xda(the download link you want is labled CWM-SuperSU-v0.96.zip. do NOT attempt to install it from the market-it wont work)
-go to HTCdev - Unlock Bootloader and register an account
*i highly reccomend to donate to drellisdee for bringing us amon recovery. at the very least,make sure to click the thanks button on his post on xda
1)unlock with htcdev
sorry,there are no exploits for temp root at this time.
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
most guides simply say "follow the directions to unlock with htcdev" but im gonna go thru it with ya the mini-adb.zip file is all the files that htcdev is telling you to download and put into a folder,so allready this should be a lil easier
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
your command promt should change to "c:\mini-adb_vigor>" provided you: 1)unzipped the miniadb zip 2)put the folder on your c drive 3)renamed the folder "mini-adb_vigor"
-now make sure usb debugging is checked in settings/apps/development,and plug your phone into your PC with a usb cable
-make sure your phone is being recognized- type:
adb devices
if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
2)unlock using htcdev
-go to HTCdev - Unlock Bootloader and sign in to your account. chose "rezound" from the "select your device bar" and click the green "begin unlock bootloader" button underneath.
-click yes to procede,then read the warnings before checking the boxes and clicking yes to continue,as they are basically explaining that your warranty is now void,and any repairs that your phone needs that may have been a result of unlocking your bootloader and messing with your phones operating system may no longer be covered under mfgr warranty
-steps 1-4 are describing how to get your phone into bootloader mode and connect it to your PC,wich we have done above. ignore these steps and simply type in your cmd window:
adb reboot bootloader
it may take several seconds,but this command should boot your phone into the "fastboot" screen wich is white with a bunch of colored writing. once this happens,make sure your phone is still being seen in fastboot. type:
fastboot devices
again,this should return your phones serial number.
-click the green procede to step 5 bubble.
-steps 5-7 are telling you how to find the files and utilities inside your mini-adb folder. you have them,so ignore steps 5-7.
-click the green procede to step 8 bubble.
-heres where steps are important,steps 8-10 are telling you how to get your unlock token,and send it to htc. its phone specific(so they prolly know your serial number,meid,etc) so no,you cant use your buddys unlock token and not have htc know that youve unlocked your bootloader. copy this line either from below,or from step 8,and paste it into the prompt in your cmd window. you have to right click to paste in cmd,you cannot control/v :
fastboot oem get_identifier_token
-after yuo hit enter,you will get a bunch of letters that are your identifier token. not much i can say,other than follow the directions in steps 9 and 10 to copy and submit your identifier token to HTC. make sure you get the characters as shown in the pic,with no extra lines or letters. note that you can also hit the "enter" key on your PC to copy,as well as right clicking.
-click the green submit button. wait patiently for an email containing your unlock code. (dont worry,it should come pretty fast )
-save the unlock_code.bin that htc sends you directly to your mini-adb_vigor folder(if your PC automatically downloads somewhere else,no biggie. just move the unlock code to mini-adb_vigor)
-click the link in your email to get the rest of the unlock instructions
-step 12 is where them magic happens copy from below,or from htc dev:
fastboot flash unlocktoken Unlock_code.bin
-youll see the purdy screen pictured in step 13. use the vol rocker to chose "yes unlock bootloader" and select it with the power button. your phone will reboot,performaing a factory data reset in the process. your data is gone,sorry this boot may take a bit longer than they normally do,dont freak out this is normal
as you can see,once the adb files are put in one place to download,its not hard to use,and the commands are pretty simple. below is what you will see in your command window,the red are my inputs.
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>cd c:\mini-adb_vigor
c:\mini-adb_vigor>adb devices
List of devices attached
HTxxxxxxxxxx device
c:\mini-adb_vigor>adb reboot bootloader
c:\mini-adb_vigor>fastboot devices
HTxxxxxxxxxx fastboot
c:\mini-adb_vigor>fastboot oem get_identifier_token
... INFO
INFO< Please cut following message >
INFO<<<< Identifier Token Start >>>>
INFO2ADC7C0C0F1BAF92074BAE9B0035CB6A
INFO021839BFA7465CD0788664688DCCFDEA
INFO33A2FD2C96C7308DD3C57A517DBA8E14
INFO8048F98A9FEA06B8F2AD05D4D3497CFE
INFO6FCCC1DC4E31E0C6F54CEA18D9A80C82
INFO27C33E209D472E6C11753E9D7BCBCE6D
INFO90D9F226E827B6C26165A029B6F7DFF2
INFO63E382B4C82F9F6D866C01B9823ED1BC
INFO0EEFA859327E6B5AC4C24533C9DFA7AF
INFODBD70D55E4666B4B41828B76FFBD010C
INFO1B916E350EFF199EA5B096FF3337FE19
INFO40E6CA9E7F1DD5B33D8D4780DD775289
INFO953404686AEC4C3CB6F1BBB9DC69BA13
INFO8738C00DAFF280ECF02D0C7A66E13855
INFO1D756616732FF47915EAD551A6933E08
INFO10C541C7RD02C14991E83CC49FCA4B92
INFO<<<<< Identifier Token End >>>>>
OKAY [ 0.069s]
finished. total time: 0.070s
c:\mini-adb_vigor>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.143s]
writing 'unlocktoken'... INFOunlock token check successfully
OKAY [ 0.011s]
finished. total time: 0.156s
c:\mini-adb_vigor>
2)flash a recovery
if you want to run stock,do not permanently install your recovery. keeping the stock recovery on the phone will ensure that you recieve OTAs without a hitch,wich i know is important to alot of users. YES,the OTA will break root. its no big deal. one good thing about htcdev is that you will always be able to reroot after,simply by following steps 2 and 3 again to launch recovery,flash superser.
once youve either skipped past all the setup,or have re-set up and are ready to root,chose ONE of these 2 options:
1)temporary recovery:
-move the image file you downloaded above for amon RA and place it into the mini-adb_vigor folder.
-put the superuser zip file onto your phones sd card
-enable usb debugging once again,as above. open a cmd window,if its not still open from unlocking.
-if you had to re-open a cmd window,dont forget to change back to your mini-adb_vigor directory:
cd c:\mini-adb_vigor
-make sure youre connected by typing:
adb devices
-should return serial number
-check the md5 of your recovery image:
md5sums<recoveryname>.img
**make sure the resulting md5 matches the one that drellisdee lists for the image that you downloaded. **
-boot to bootloader:
adb reboot bootloader
-check for connectivity:
fastboot devices
-should return serial number
-temporarily launch your recovery to phone memory:
fastboot boot <recoveryname>.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.
in your command window you will see(red are my inputs):
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>cd c:\mini-adb_vigor
c:\mini-adb_vigor>adb devices
List of devices attached
HTxxxxxxxxxx device
c:\mini-adb_vigor>md5sums recovery-ra-vigor-3.14-gnm.img
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[c:\mini-adb_vigor\]
recovery-ra-vigor-3.14-gnm.img 915d5e3cb662076f36f3d6e54759e951
c:\mini-adb_vigor>adb reboot bootloader
c:\mini-adb_vigor>fastboot devices
HTxxxxxxxxxx fastboot
c:\mini-adb_vigor>fastboot boot recovery-ra-vigor-3.14-gnm.img
downloading 'boot.img'... OKAY [ 1.518s]
booting... OKAY [ 0.005s]
finished. total time: 1.523s
2)permanently install your recovery
-move the image file you downloaded above for amon RA and place it into the mini-adb_vigor folder.
-enable usb debugging once again,as above. open a cmd window,if its not still open from unlocking.
-if you had to re-open a cmd window,dont forget to change back to your mini-adb_vigor directory:
cd c:\mini-adb_vigor
-make sure youre connected by typing:
adb devices
-should return serial number
-check the md5 of your recovery image:
md5sums<recoveryname>.img
**make sure the resulting md5 matches the one that drellisdee lists for the image that you downloaded. **
-boot to bootloader:
adb reboot bootloader
-check for connectivity:
fastboot devices
-should return serial number
-permanently flash your recovery to phones recovery partition:
fastboot flash recovery <recoveryname>.img
-youll see a (really fast) green status bar on the top right as your PC sends the recovery to your phone,then a (really,really fast) red bar as it flashes it. amon ra is now permanently on your phone when you need it. be aware that you can no longer accept OTAs,unless you reinstall the stock recovery at some point before the next OTAs are pushed.
-to get to recovery,push the power button to select hboot. once in hboot wait for the green writing to flash and disapear,then select recovery.
*note that you can still launch recovery by using the command from scenario 1 above. i reccomend doing it this way. without complex explanations,its better
-youll then see the HTC splash screen,then your recovery.
and the code(again,red my inputs):
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>cd c:\mini-adb_vigor
c:\mini-adb_vigor>adb devices
List of devices attached
HTxxxxxxxxxx device
c:\mini-adb_vigor>md5sums recovery-ra-vigor-3.14-gnm.img
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[c:\mini-adb_vigor\]
recovery-ra-vigor-3.14-gnm.img 915d5e3cb662076f36f3d6e54759e951
c:\mini-adb_vigor>adb reboot bootloader
c:\mini-adb_vigor>fastboot devices
HTxxxxxxxxxx fastboot
c:\mini-adb_vigor>fastboot flash recovery recovery-ra-vigor-3.14-gnm.img
sending 'recovery' (7074 KB)... OKAY [ 1.659s]
writing 'recovery'... OKAY [ 5.179s]
finished. total time: 6.840s
3)flash superuser root files*
there is not much to explain with this one. if booted to recovery from above,use the recovery menu on your phone to:
-make a backup of your stock,unrooted rom. completely optional,but a very good idea,IMO.
-wipe cache
-wipe dalvik cache
-install zip from sd card(chose your superuser file)
-reboot
*congratulations,youre rooted
*note that you do not neccessarily need to flash superuser. if you want to flash a custom rom,you can go ahead and do that now,no need to root your stock rom first.
__________________________________________________ __________________________________ *stock recoveries
for 2.01.605.11: PH98IMG-2.01.605.11-vigor-recovery.zip
for 3.14.605.12: PH98IMG-recovery_stock_3.14.605.12.zip
simply download,pull out the image,place in mini-adb_vigor folder,and fastboot flash usaing the the directions for permanent recovery in step 2
__________________
The Delivery Guy
If someone has helped you,please click the THANKS button on that post.
Please post questions so others can benefit from the answers. donate to my device fund
Last edited by scotty85; March 15th, 2013 at 09:10 AM.
The Following 80 Users Say Thank You to scotty85 For This Useful Post:
-make a backup using your phones on screen amon ra menu options. this is optional,but a good idea,if you have a a good workling setup and think you might want to get back to this point later.
-using the phones amon ra menu options,flash "SetMainVersionLOW.zip" just like you would any other rom. no need to wipe anything,just flash it.
-boot back into bootloader adb reboot bootloader
-check main version fastboot getvar all
-if your main version is now 1.00.000.0 then procede:
-relock bootloader fastboot oem lock
*you may get a security warning after it locks. dont panic,this is normal when relocking with custom software
-run the .exe file on your PC with our phone still in fastboot. follow the onscreen directions. it will reboot when finished
**work in progress** more later...
Last edited by scotty85; December 19th, 2012 at 07:53 PM.
The Following 15 Users Say Thank You to scotty85 For This Useful Post:
the main version is simply the software build version. it is checked by the s-on hboot to make sure that we do not roll back our firmware to what HTC considers inferior and obsolete(and in some cases,exploitable ) older software/firmware.
the first place it is checked is the "android info" text document. this is simply a small text file that is packaged inside of hboot flashable PH98IMG files. if the file fails this check,and finds the "main version" in the text document to be lower than the software on the phone,it will either return siliently to the hboot screen without explanation,or it will spit out a "main version older!" error.
here is a very basic android info text document i always use in making up PH98IMG files:
you will sometimes see different "hboot preupdate" numbers,and different things inside. i havent messed with them enuff to know(or care ) what it all means.
*you can use the directions at the end of the post to find out what your main version info is,if you need to(or maybe i should move those directions up here? hmm).
if you find yourself with a main version error you will need to do ONE of the following 2 things:
1)edit the android info text document
to alot of folks this is the easier thing to do. just like it sounds,you need to edit the main version number of the text file to be equal to or greater than your softwares main version.
i.e.,if you are on 1.02.605.6,your main version could be 1.02.605.6, 2.01.605.11, or 3.xx.xxx.x
-take the .zip file you want to flash,and unzip it. you can unzip many files without anything special in windows 7. if youre on xp,or for signed files that you cant simply right click,then "extract" you may need a utility such as 7-zip.
-open the unzipped folder and click on the android info text document to open with your favorite text editor.
-change the main version number to be = or > than yours.
Code:
modelid: PH9810000
cidnum: VZW__001
mainver: 2.01.605.11 <- edit this number
hbootpreupdate:12
-save the text document. close it. open it again for peace of mind that it changed
-rezip your file. in windows 7 this is as easy a highlighting the android info document,and any images. right click,click "send to" then "compressed(zipped) folder". older versions of windows may need a seperate utility.
your file *should* flash now.
*or
2)edit the main version on your phone
a)old school method
download this modified misc image from this threadon xda. make sure to click the "thanks" button for mrbracht.
-place the modified misc image onto your SD card,and make sure it is named " miscnew "
*next you must be booted into a rooted operating system.
-put the phone in charge only mode,plug it in if its not.
-open a cmd window as described in post 1
-change to your mini-adb_vigor directory cd c:\mini-adb_vigor
-make sure youre connected adb devices
-open a root shell. have your phone awake and unlocked before doing this,as sometimes you will have to allow a supeuser pop up if youre running a stock rom.
adb shell (prompt should change to a # .if your prompt only changes to a $,then type su )
-write the new misc image: dd if=/sdcard2/miscnew.img of=/dev/block/mmcblk0p24
-exit out of your adb shell exit (may have to type this a second time)
-reboot adb reboot
your main version should now be set to 1.00.000.0. you should now be able to flash literally anything without altering stupid text documents
heres what it will look like(red are my inputs):
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>cd c:\mini-adb_vigor
c:\mini-adb_vigor>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HTxxxxxxxxxx device
c:\mini-adb_vigor>adb shell
root@android:/ # dd if=/sdcard2/miscnew.img of=/dev/block/mmcblk0p24
dd if=/sdcard2/miscnew.img of=/dev/block/mmcblk0p24
32763+0 records in
32763+0 records out
16774656 bytes transferred in 4.858 secs (3452996 bytes/sec)
root@android:/ # exit
exit
c:\mini-adb_vigor>adb reboot
b) flash "main version low zip" method
credits: drellisdee for coming up with this main version tool con247 for using it to create a flashable zip to change main version to a generic 1.00.000.0 in this post
*assumtions:
-that you rooted with the guide in this first post,and thus have adb/fastboot set up in the "mini-adb_vigor" file on the root of your C drive.
-that you are using amon ra recovery image
Thanks this is great! I finally feel comfortable going through the root process! I think this should get sticky as this is very noob friendly! Now how about an unroot and relock guide. I know you said in another forum my bootloader will say "relocked", but for warranty Verizon probably wont look at that...
The Following User Says Thank You to icedice34 For This Useful Post:
Thanks this is great! I finally feel comfortable going through the root process! I think this should get sticky as this is very noob friendly! Now how about an unroot and relock guide. I know you said in another forum my bootloader will say "relocked", but for warranty Verizon probably wont look at that...
It is stickied in the All Things Root guide.
Also a Super Noob Unroot and Relock would round it off wouldn't it. We all have to give a lot of credit to Scotty for all these write up's he does.
Last edited by Bob Cat; February 27th, 2012 at 08:37 AM.
The Following User Says Thank You to Bob Cat For This Useful Post:
Thanks this is great! I finally feel comfortable going through the root process! I think this should get sticky as this is very noob friendly! Now how about an unroot and relock guide. I know you said in another forum my bootloader will say "relocked", but for warranty Verizon probably wont look at that...
Back to stock and others coming soon
The Following 4 Users Say Thank You to scotty85 For This Useful Post:
I got through unlocking the bootloader without a problem, however having issues flashing recovery. At the step where you enter fastboot boot <recoveryname>.img after I do that this is what I get.... (note I renamed the recovery file to just "recovery" but its the same recommended in the instructions).
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
Thanks, tired eyes...missed that. However just tried it with the missing command "boot" to temporarily flash and received message saying "cannot load 'recovery.img'
I checked the mini-adb_vigor folder on the c: to confirm it was there and named correctly and it is. Tried placing it there again and flashing recovery with same result. Frustrated that I'm so close but stalled, any help is appreciated.
Last edited by ellis245; February 28th, 2012 at 10:05 PM.
are you wanting to temporarily or permanently flash your recovery?
you are missing a vital word in your command:
to temporarily flash recovery(using your image name "recovery": fastboot [COLOR="Red"]boot[/COLOR] recovery.img
to permanently flash it: fastboot [COLOR="red"]flash[/COLOR] recovery recovery.img
Is it truly permanent? Or is there an way to flash the stock recovery if I decided to. Sounds to me like with permanent it would be easier to flash the super user back on after an OTA? or am I missing something?
Is it truly permanent? Or is there an way to flash the stock recovery if I decided to. Sounds to me like with permanent it would be easier to flash the super user back on after an OTA? or am I missing something?
it is permanent in the sense that it stays until you flash something else. so yes,you can flash the stock recovery back if you want to. IMO there is not a whole lot of point to permanently flashing a recovery,since you cant really do anything without being connected to a PC anyway you need a PC to flash the kernels,and restore backups.
a permanent recovery will NOT make it easier to restore superuser. it will,in fact,prevent you from recieving the OTA,making it neccessary to relock,and run an RUU in order to get the updates,thus making what is normally a seamless process un-neccessarily complex.
only the STOCK recovery can apply vzw's OTA updates,so its best to just leave it on the phone if you want to run stock and recieve the OTAs.
hope that clears it up
The Following 2 Users Say Thank You to scotty85 For This Useful Post:
Device(s): Samsung Galaxy S3 16GB, Stock ROM (VRBMA2), KT747 kernel o/c'ed to 2.1Ghz, Go Launcher EX, TWRP2 rec
Carrier: Verizon
Thanks: 78
Thanked 94 Times in 83 Posts
Quote:
Originally Posted by scotty85
a permanent recovery will NOT make it easier to restore superuser. it will,in fact,prevent you from recieving the OTA,making it neccessary to relock,and run an RUU in order to get the updates,thus making what is normally a seamless process un-neccessarily complex.
Wow. That's a very compelling reason not to flash a permanent recovery. You may have just convinced me although it's too late for me. Looks like I have to run the RUU .exe before I can receive the next OTA. Bummer.
it is permanent in the sense that it stays until you flash something else. so yes,you can flash the stock recovery back if you want to. IMO there is not a whole lot of point to permanently flashing a recovery,since you cant really do anything without being connected to a PC anyway you need a PC to flash the kernels,and restore backups.
a permanent recovery will NOT make it easier to restore superuser. it will,in fact,prevent you from recieving the OTA,making it neccessary to relock,and run an RUU in order to get the updates,thus making what is normally a seamless process un-neccessarily complex.
only the STOCK recovery can apply vzw's OTA updates,so its best to just leave it on the phone if you want to run stock and recieve the OTAs.
hope that clears it up
I think its finally clear. As long as I just boot, and don't flash amon ra I can receive the next OTA like normal then boot amon again and install super user? Will the process still work the same with each OTA?
I think its finally clear. As long as I just boot, and don't flash amon ra I can receive the next OTA like normal then boot amon again and install super user?
correct
Quote:
Originally Posted by icedice34
Will the process still work the same with each OTA?
yup! sure will
The Following 2 Users Say Thank You to scotty85 For This Useful Post:
Wow. That's a very compelling reason not to flash a permanent recovery. You may have just convinced me although it's too late for me. Looks like I have to run the RUU .exe before I can receive the next OTA. Bummer.
you dont really need to run the RUU. you can just flash the stock recovery back,just like you flashed amon
I went through all of the steps and everything seemed to work perfectly. However, when I flashed super user it went for a bit then said "install aborted". I rebooted the phone anyway and I have a super user app, but no apps can gain root access. I tried TiBu and rootchecker basic.
Did I do something wrong? I downloaded all the files exactly as you said. I don't see what happened?
I get stuck "waiting for device" when trying to get the identifier. I used adb to get to fastboot successfully, but it can't find the device once it's in bootloader. Thanks
Device(s): ASUS Transformer Prime, HTC Rezound, Classic nook.
Carrier: Not Provided
Thanks: 3
Thanked 3 Times in 3 Posts
Thanks for the detailed instructions. I rooted my Incredible a year ago so I'm not completely new to rooting but I'm rusty. This process for rooting the Rezound seems different from what I can remember when I did my Dinc. I have a question that I believe I know the answer to but I just want to be 100% certain. Is the difference between permanent root and temporary root that with temporary root you can not install a custom ROM? If not then what is the advantage of permanent root? Thank you very much.
Thanks for the detailed instructions. I rooted my Incredible a year ago so I'm not completely new to rooting but I'm rusty. This process for rooting the Rezound seems different from what I can remember when I did my Dinc. I have a question that I believe I know the answer to but I just want to be 100% certain. Is the difference between permanent root and temporary root that with temporary root you can not install a custom ROM? If not then what is the advantage of permanent root? Thank you very much.
actually,the main difference between temp and permanent root is just that- temp root is only temporaty and generally is undone each time the phone is rebooted a custom recovery could possibly installed,but would disapear as soon as you boot the phone.
there is no more temporary root. the most recent OTA fixed the exploit that had been being used,so until someone comes up with something else,permanent root via htcdev is the only option.
the only thing temporary in this guide is the possible temporary installation of recovery. dont let that confuse you-just because you temporarily install recovery to root,it does NOT mean that you are temp rooted with htcdev,the old days of having to fight to keep your root access are gone. you can always re-root after OTAs,so temporarily installing your custom recovery makes your life significantly easier if you wish to stay stock rooted,as your stock recovery can and will install OTAs for you as they happen.
Quote:
Originally Posted by Aremihc
I get stuck "waiting for device" when trying to get the identifier. I used adb to get to fastboot successfully, but it can't find the device once it's in bootloader. Thanks
"waiting for device" in fastboot means either a prollem with the fastboot utility or one of its supporting files(missing?) or a prollem with drivers.
try rebooting the phone,reboot the PC. try different usb ports. make sure you are in fastboot,and not in hboot.(if you pushed the power button after "adb reboot bootloader" took you to fastboot,you are not in hboot)
-make sure you followed the above directions carefully. use the "mini-adb" download,rename the unzipped folder to "mini-adb_vigor" so you can directly copy/paste commands without having to remember to change the name.
-what did you do for drivers? the ones i linked for revolutionary are a .exe file that you can run as administrator after downloading,and it should install drivers for you.
-temporarily uninstall htc sync
if youre using my mini-adb file,and are still having prollems after reboots and rerunning the driver .exe file,etc.,youy might try manually updating the drivers by locating the phone(plugged in and in fastboot mode) in device manager.manually update the drivers,pointing them toward the extracted HTCDriver3.0.0.007 file,or htc sync drivers.
very often,a copy of your cmd window is quite helpful. if you continue having prollems,then copy and paste your session by:
-right click in the command window,click mark.
-highlight everything in white. hit enter.
-then,in your "reply to thread" box here,click the "#" up top
-right click and "paste" everything between the [code] tags.
Last edited by scotty85; March 3rd, 2012 at 09:12 PM.
The Following User Says Thank You to scotty85 For This Useful Post:
Device(s): ASUS Transformer Prime, HTC Rezound, Classic nook.
Carrier: Not Provided
Thanks: 3
Thanked 3 Times in 3 Posts
Quote:
Originally Posted by scotty85
actually,the main difference between temp and permanent root is just that- temp root is only temporaty and generally is undone each time the phone is rebooted a custom recovery could possibly installed,but would disapear as soon as you boot the phone.
there is no more temporary root. the most recent OTA fixed the exploit that had been being used,so until someone comes up with something else,permanent root via htcdev is the only option.
Thanks a million. I understand now. I was confusing temporary root with temporary recovery. I also found a reply you made to someone else in regards that you can install custom ROMS on a temporary recovery. One other question please. After an OTA update removes the root can I use Titanium Backup to restore my apps and settings after rooting again?
Device(s): Samsung Galaxy S3 16GB, Stock ROM (VRBMA2), KT747 kernel o/c'ed to 2.1Ghz, Go Launcher EX, TWRP2 rec
Carrier: Verizon
Thanks: 78
Thanked 94 Times in 83 Posts
Quote:
Originally Posted by EddieE
After an OTA update removes the root can I use Titanium Backup to restore my apps and settings after rooting again?
Not all system settings are restored and not all user app settings are restored. Be prepared to go through the settings you've changed to restore them.
Device(s): ASUS Transformer Prime, HTC Rezound, Classic nook.
Carrier: Not Provided
Thanks: 3
Thanked 3 Times in 3 Posts
Quote:
Originally Posted by thornev
Not all system settings are restored and not all user app settings are restored. Be prepared to go through the settings you've changed to restore them.
It appears it's not necessary but thank you for the reply anyway.
Device(s): ASUS Transformer Prime, HTC Rezound, Classic nook.
Carrier: Not Provided
Thanks: 3
Thanked 3 Times in 3 Posts
Quote:
Originally Posted by scotty85
thats the beauty of accepting OTAs. your personal data is not lost or damaged. you wont need to restore anything- just:
1)relaunch recovery
2)reflash superuser
you do NOT need to relock to accept an OTA,therefore,you will NOT need to re-unlock(wiping your data)
That is great. It's a pain installing and reconfiguring everything. BTW, I just followed your instructions and rooted using temporary recovery. Everything worked smoothly except one small issue at the end. When I first flashed superuser the process was aborted and there was a message about a problem with the zip file. I just flashed it again and the second time it worked just fine. Thanks again for making this so easy.
The Following User Says Thank You to EddieE For This Useful Post:
Thanks for an extremely easy to follow root guide. I have never rooted a phone before so I was a bit wary of doing so, however the last OTA on the Rezound has absolutely killed my battery life. I went from lasting a full day with moderate/heavy use to lasting max of 6 hours with hardly any use at all. From what I found on Google, a lot of people said it had to do with the Verizon Location Agent running constantly and never letting the phone sleep and the only way to kill it is to root. I rooted my phone in one try with no problems by following your guide and after setting back up my phone I found that the MyBackup Pro app I had had a root access tool that allowed me to freeze the Location Agent and a few other bloatware apps. My battery life has greatly improved but still isn't back to what it was before. My fiancee has the Rezound too and even with moderate to heavy use her battery lasts much longer than mine, still being green around 11pm-midnight when mine has died a few hours before. Do you know of anything else I can do to get my battery life back up? Also, if you don't mind the questions, is Titanium Backup really as good as everyone makes it out to be? Again, thanks so much for an easy guide helping this noob root his phone without screwing up!
Edit: I used your guide and rooted my phone on Thursday 3/1, so am basing the new battery life off the last 2 days, it's lasting about 11 hours with very light use before dying, whereas my previous battery life and my fiancee's battery life will be at between 45-60% after 12+ hours of moderate use.
Last edited by phoenixgward; March 4th, 2012 at 02:01 PM.
Reason: Add info
The Following User Says Thank You to phoenixgward For This Useful Post:
Scotty, thanks so much for the guide. The process couldn't have been any easier or more straightforward, thanks to you! I bought my Rezound after lunch today, and was rooted before dinner.
I did have to try twice to get my Rezound to install SU, but this thread told me that such things aren't uncommon, and told me just to back out, get back into recovery, and try again.
The only thing that threw me off (for about 2 seconds) was that after step 1, you have to go back into settings and re-enable USB debugging.
All in all, my first time rooting took about 30 minutes, because I was being very methodical (i.e. slow).
I've got a nandroid backup, installed Titanium Backup and frozen bloat, and am ready for more ideas on how to take advantage of root and my shiny new Rez.
Thanks again! You rock!
The Following User Says Thank You to aikiscott For This Useful Post:
as for battery life, run a kernel thats slightly undervolted,maybe even underclock it when youre not using it heavy,and definately lower the min and max speeds when the screen is off. minimize the amount of syncs that are being done by various apps and widgets,keep an eye on runing services to see whats always on sucking down the juice.
for what its worth,my battery life is pretty on par with yours. im pretty hard on my phone,i talk via bluetooth 2-3 hours a day,and am constantly waking my phone up for to text,check email,phandroid,etc. i also use it frequently to find things and navigate to them.
only way i could get anywhere near 12 hours would be to put my phone down and not touch it your fiancee seems to be getting better batterly life than most. id try to set your phone up EXACTLY like she does,and try and mess with it similarly over a day when youre together. see if yours is more on par then.
i couldnt get along without titanium backup with the prokey.ive never used my backup pro,so i really couldnt say for sure that one is better than the other.i just happened to get titanium first and theres not much reason to purchase another paid backup app when the one i have does what i need it to. as long as my backup pro will let you do batch backup and restore of your apps,and let you uninstall,freeze,and melt user or system apps, it would prolly suit me fine as well.
as for what else to do with root,you can check out root only apps,and you can modify system files. some folks like to tweek different things like screen density. personally,i like to flash different roms,but what you do with your root access is entirely up to you
The Following User Says Thank You to scotty85 For This Useful Post:
Mmmm, no, that didn't work for the .11 OTA. I had to relock and run the RUU .exe file to bring my phone back to stock .6 before the .11 OTA would install.
Last edited by thornev; March 4th, 2012 at 10:35 PM.
Mmmm, no, that didn't work for the .11 OTA. I had to relock and run the RUU .exe file to bring my phone back to stock .6 before the .11 OTA would install.
thats becasue you waited until the OTA tried to install. if you install it now,and have the stock recovery in place when the next OTA hits,it will work.
if you want some peace of mind that installing only the recovery isnt leaving out some piece of the puzzle,your other option is this:
1)make a backup
2)relock
3)run full RUU
4)re-unlock
5)launch temp recoveruy with fastboot.
6)restore backup
a couple ways to skin the cat, but if you want to seemlessly OTA without losing data,the important thing is to do one or the other prior to the next OTA downloading and trying to install.
Last edited by scotty85; March 5th, 2012 at 07:34 AM.
The Following User Says Thank You to scotty85 For This Useful Post:
Quick question. Which recovery method are you using? At the moment I'm using amon ra as my permanent recovery but using the other method would seem more like having s-off. At least you could restore a nandroid and not have to then flash the boot.img separately. Thoughts?
Quick question. Which recovery method are you using? At the moment I'm using amon ra as my permanent recovery but using the other method would seem more like having s-off. At least you could restore a nandroid and not have to then flash the boot.img separately. Thoughts?
that is correct. if you launch the recovery from fastboot(fastboot boot recoveryname.img) then you can simply wipe and restore without having to flash the boot image seperately.
there is no harm of keeping your recovery permanently installed,as you *could* flash new roms and restore backups that use the same kernal without a PC present,but if you want to want to restore without a seperate kernel flash,then always fastboot boot the recovery into memory rather than booting to your installed recovery.
if rom developers would put kernel updater scripts into their roms,then you would be able to simply FLASH new roms in recovery in the conventional manner,without a seperate kernel flash there either
Last edited by scotty85; March 5th, 2012 at 08:02 AM.
Device(s): Samsung Galaxy S3 16GB, Stock ROM (VRBMA2), KT747 kernel o/c'ed to 2.1Ghz, Go Launcher EX, TWRP2 rec
Carrier: Verizon
Thanks: 78
Thanked 94 Times in 83 Posts
Quote:
Originally Posted by scotty85
thats becasue you waited until the OTA tried to install. if you install it now,and have the stock recovery in place when the next OTA hits,it will work.
Well, OK then. I've become a Scotty85 Disciple. I'm sticking with stock recovery on the phone, flashing a temp recovery when I do ROM/kernel installs, and thus I expect a clean and green OTA whenever it comes. =:-) Life is good.
The Following User Says Thank You to thornev For This Useful Post:
Am i the only one having trouble with this??? This is what i get when trying to flash a recovery. Any suggestions? I'm almost positive i have all the drivers and files i need.
c:\mini-adb_vigor>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
<My serial number> offline
c:\mini-adb_vigor>md5sumsrecovery-ra-vigor-3.14-gnm.img
'md5sumsrecovery-ra-vigor-3.14-gnm.img' is not recognized as an internal or exte
rnal command,
operable program or batch file.
Device(s): Samsung Galaxy S3 16GB, Stock ROM (VRBMA2), KT747 kernel o/c'ed to 2.1Ghz, Go Launcher EX, TWRP2 rec
Carrier: Verizon
Thanks: 78
Thanked 94 Times in 83 Posts
Quote:
Originally Posted by tCizzler
Am i the only one having trouble with this??? This is what i get when trying to flash a recovery. Any suggestions? I'm almost positive i have all the drivers and files i need.
c:\mini-adb_vigor>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
<My serial number> offline
c:\mini-adb_vigor>md5sumsrecovery-ra-vigor-3.14-gnm.img
'md5sumsrecovery-ra-vigor-3.14-gnm.img' is not recognized as an internal or exte
rnal command,
operable program or batch file.
c:\mini-adb_vigor>
Your 2nd command is missing a blank between "md5" and "recovery..."
The problem with your 1st command has happened to several people. Search the forum on something like "server out of date" and you may find the solution.
The Following User Says Thank You to thornev For This Useful Post:
Well, OK then. I've become a Scotty85 Disciple. I'm sticking with stock recovery on the phone, flashing a temp recovery when I do ROM/kernel installs, and thus I expect a clean and green OTA whenever it comes. =:-) Life is good.
a couple other things to keep in mind about OTAs:
-most custom roms will have the updater scripts removed,so even being on the correct firmware version the phone will not OTA.
-updter scripts generally only look for official fimrware release versions,not leaks. so if you happened to be on a leak GB rom(for example we get a leak that is version number 2.01.605.13),even tho the OTA version number may be greater(for example 2.01.605.20) the phone will not OTA,as the updater scripts are looking for the last official software 2.01.605.11.
-phone must be on the correct radio to OTA(tho this does not affect us in fake s-off,"unlocked s-on" land,as we cannot change our radio other than an OTA
so if youre on anything other than the current stock software when you get wind of an upcoming OTA,you will want to restore a (mostly)unmolested stock backup
Quote:
Originally Posted by tCizzler
Am i the only one having trouble with this??? This is what i get when trying to flash a recovery. Any suggestions? I'm almost positive i have all the drivers and files i need.
c:\mini-adb_vigor>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
<My serial number> offline
the out of date error is not a big deal and not responsible for the offline status. it is usually fixed as simply as unplugging the phone for a few seconds and then plugging into a different usb port. sometimes a reboot of the phone and/or PC may be needed as well.
Last edited by scotty85; March 6th, 2012 at 04:38 AM.
The Following User Says Thank You to scotty85 For This Useful Post:
Thanks... I think i got it fixed somewhat. I did google "adb server is out of date.... killing" and came up with it being an incompatibility with HTC sync. So i uninstalled HTC Sync and tried again and it worked. I was able to flash a recovery, but now my problem is that when i try to flash my (Superuser-3.0.7-efgh-signed.zip) from my sd-card, i get an installation aborted prompt. And the reason being is something related to a bad file. Any suggestions on that part?
The Following User Says Thank You to tCizzler For This Useful Post:
OK so the weird part is that even after i got the installation aborted prompt, i rebooted and seem to have root. I have the SU app and all of my apps that use root are currently working. So my question is, should i leave it alone? or try steps 21-26 to see if i can get it to run through correctly?
31Likes
Scottys noob friendly root guide-start to finish
)
copy from below,or from htc dev:
this boot may take a bit longer than they normally do,dont freak out this is normal 
you need a PC to flash the kernels,and restore backups.
