Go Back   Android Forums > Android Phones > HTC Rezound > Rezound - All Things Root

Find everything you need for the Galaxy S5 and discuss it in our S5 forum!
Have you seen that OnePlus One's awesome camera?? The forum is over here!

Like Tree32Likes

test: Reply
 
LinkBack Thread Tools
Old February 26th, 2012, 07:52 PM   #1 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,657
 
Device(s):
Carrier: Not Provided

Thanks: 7,194
Thanked 6,789 Times in 4,269 Posts
Default Scottys noob friendly root guide-start to finish

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




2)flash a recovery





3)flash superuser root files*




*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.

if you are intending to stay s-on,with htcdev,make sure you read this: s-on and want to flash roms? READ THIS

if you are planning s-off,or wonder what exactly s-off is,read this:s-off guide/info/return to stock


*hope it helps some folks


__________________________________________________ __________________________________
*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

donate to my device fund
Bmr4life likes this.

__________________
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
scotty85 is online now  
Last edited by scotty85; March 15th, 2013 at 09:10 AM.
Reply With Quote
The Following 83 Users Say Thank You to scotty85 For This Useful Post:
2old4this (June 26th, 2012), acoastal (July 5th, 2012), AcumenProbitas (August 23rd, 2012), aikiscott (February 29th, 2012), al23 (May 11th, 2012), Ashbane (August 20th, 2012), a_bug (April 5th, 2012), Bmr4life (April 9th, 2013), Bob Cat (February 26th, 2012), Bullitt3309 (September 11th, 2012), dassh (May 2nd, 2012), DaveHiro (July 1st, 2012), dezignstuff (May 19th, 2012), dldnh (August 14th, 2012), DonB (March 18th, 2012), ebrammer252 (May 10th, 2013), El Presidente (February 27th, 2012), ellis245 (February 28th, 2012), esmith818 (May 10th, 2012), feel the void (August 3rd, 2012), felopez (April 2nd, 2013), Fenotyp (June 23rd, 2012), FumanII (March 16th, 2012), gag138 (April 23rd, 2013), garyht (July 16th, 2012), goofdad (March 12th, 2012), GuitarG20 (March 2nd, 2013), guyd (April 9th, 2012), Hamster68 (April 11th, 2012), icedice34 (February 27th, 2012), jaunnyboy (September 13th, 2012), jjhsiung (April 16th, 2013), JosephCurwen (April 26th, 2012), JSmoove3g4 (April 24th, 2012), JustSomeDude (May 15th, 2012), jwells31 (June 1st, 2012), jwork69 (June 19th, 2012), Jxshua (February 4th, 2013), Katmeat (April 30th, 2012), kgirl808 (March 4th, 2012), leozevil (August 13th, 2012), Luis1968 (November 14th, 2012), MamboKing (April 7th, 2012), manbat (August 4th, 2012), matt.burns21 (May 16th, 2012), MaxxVE (April 21st, 2012), MrBojenglz (January 10th, 2013), Myco (February 29th, 2012), MYGuy (April 17th, 2012), NEXTLOVER (March 24th, 2012), obscuro (June 1st, 2012), okader (July 2nd, 2012), onefourthgreek (April 16th, 2012), pank (February 26th, 2012), phoenixgward (March 4th, 2012), puremp24 (May 11th, 2012), pwned (February 26th, 2012), Quadfather (April 5th, 2012), Racerx2oo3 (April 24th, 2012), rjprince (October 30th, 2013), SamXp (March 23rd, 2012), scary alien (March 18th, 2012), shturm (August 3rd, 2012), SinCitySRT4 (June 23rd, 2012), sirjake (March 7th, 2013), Snowe (September 16th, 2012), Spikey1109 (May 31st, 2013), TadCurious (May 18th, 2013), teerex (July 5th, 2012), theslik1 (February 10th, 2013), TheTyphoonxD (July 14th, 2013), today (May 4th, 2012), tomahan (August 15th, 2012), turkjey5 (November 26th, 2013), VadersDROID (August 14th, 2012), varaonaid (April 6th, 2012), vintagewalrus (July 9th, 2012), WA_Bob (February 27th, 2012), wcharland (May 30th, 2013), xIdkwtS (January 30th, 2013), xmr405o (March 18th, 2012), YourFriendCasp (April 22nd, 2012), zazan (March 4th, 2012)
sponsored links
Old February 26th, 2012, 07:52 PM   #2 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,657
 
Device(s):
Carrier: Not Provided

Thanks: 7,194
Thanked 6,789 Times in 4,269 Posts
Default how to unroot

"full ruu" method to unroot
-download the an ruu for the current firmware ( http://shipped-roms.com/index.php?category=android&model=Vigor )
-download main version tool
-open a cmd window,as described in post 1
-change to mini-adb directory:
cd c:\mini-adb_vigor

-check connectivity
adb devices

-boot to bootloader
adb reboot bootloader

-launch recovery
fastboot boot recovery-ra-vigor-3.14-gnm.img

-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...
scotty85 is online now  
Last edited by scotty85; December 19th, 2012 at 07:53 PM.
Reply With Quote
The Following 15 Users Say Thank You to scotty85 For This Useful Post:
acoastal (June 4th, 2012), al23 (May 11th, 2012), chknhwk (April 24th, 2012), DonB (March 18th, 2012), Fenotyp (June 23rd, 2012), guyd (April 22nd, 2012), Hamster68 (April 11th, 2012), icedice34 (April 14th, 2012), Jon22 (August 3rd, 2012), jwork69 (February 25th, 2013), kool kat2 (March 26th, 2012), manbat (August 4th, 2012), nali66 (August 28th, 2012), scary alien (March 18th, 2012), shturm (August 3rd, 2012)
Old February 26th, 2012, 07:53 PM   #3 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,657
 
Device(s):
Carrier: Not Provided

Thanks: 7,194
Thanked 6,789 Times in 4,269 Posts
Default dealing with "main version" errors

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:
Code:
modelid: PH9810000
cidnum: VZW__001
mainver: 2.01.605.11 
hbootpreupdate:12
heres the one that comes inside the 2.11.605.01 RUU:

Code:
modelid: PH9810000
cidnum: VZW__001
mainver: 2.01.605.11
hbootpreupdate:12
DelCache:1
DelFat:1
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

1)download this file:
- main version tool

2)change main version:

-place "SetMainVersionLOW.zip" on the root of your phones SD card

-open a cmd window as described in post 1

-change to mini-adb directory:
cd c:\mini-adb_vigor

-check connectivity
adb devices

-boot to bootloader
adb reboot bootloader

-launch recovery
fastboot boot recovery-ra-vigor-3.14-gnm.img

-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 with whatever you needed to change the main version for




*how to check your main version
-open a cmd window as described in post 1
-change to mini-adb directory:
cd c:\mini-adb_vigor

-check connection
adb devices

-boot to fastboot
adb reboot bootloader

-enter:
fastboot getvar all

-check your mainver number

heres what it will look like(red are my inputs,blue are simply additional comments):
Code:
c:\mini-adb_vigor>adb devices
List of devices attached
HTxxxxxxxxxx    device


c:\mini-adb_vigor>adb reboot bootloader

c:\mini-adb_vigor>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 2.11.0000
INFOversion-baseband: N/A
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.00.000.0 <-this is the number you want to check
INFOserialno: HT19WS213284
INFOimei: 990000336304110
INFOproduct: vigor
INFOplatform: HBOOT-8260
INFOmodelid: PH9810000
INFOcidnum: VZW__001
INFObattery-status: good
INFObattery-voltage: 4061mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-bc948b45
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.534s

c:\mini-adb_vigor>fastboot reboot
scotty85 is online now  
Last edited by scotty85; April 22nd, 2012 at 07:51 AM.
Reply With Quote
The Following 7 Users Say Thank You to scotty85 For This Useful Post:
chknhwk (April 24th, 2012), DonB (March 18th, 2012), guyd (April 22nd, 2012), jwork69 (February 25th, 2013), manbat (August 6th, 2012), onefourthgreek (April 16th, 2012), scary alien (March 18th, 2012)
Old February 26th, 2012, 07:53 PM   #4 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,657
 
Device(s):
Carrier: Not Provided

Thanks: 7,194
Thanked 6,789 Times in 4,269 Posts
Default

this one too:
scotty85 is online now  
Last edited by scotty85; September 2nd, 2012 at 03:23 PM.
Reply With Quote
The Following 2 Users Say Thank You to scotty85 For This Useful Post:
jlb0305 (March 15th, 2012), manbat (August 6th, 2012)
Old February 26th, 2012, 11:58 PM   #5 (permalink)
Careful, They're sharp!!
 
Bob Cat's Avatar
 
Join Date: Nov 2010
Location: Midland's, South Carolina
Posts: 6,870
 
Device(s): Samsung Galaxy Note 2
Carrier: Big Red

Thanks: 2,402
Thanked 3,873 Times in 1,850 Posts
Default

Um not used to standing in line for second, third or fourth spots but this was well worth it. Great write up.
Bob Cat is offline  
Reply With Quote
The Following User Says Thank You to Bob Cat For This Useful Post:
scotty85 (February 27th, 2012)
Old February 27th, 2012, 05:20 AM   #6 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,657
 
Device(s):
Carrier: Not Provided

Thanks: 7,194
Thanked 6,789 Times in 4,269 Posts
Default

thanx BC. i kept finding myself running out of room in my TB posts,so i figured what the heck- first 4 are mine!
scotty85 is online now  
Reply With Quote
The Following 2 Users Say Thank You to scotty85 For This Useful Post:
chknhwk (April 24th, 2012), manbat (August 6th, 2012)
Old February 27th, 2012, 08:05 AM   #7 (permalink)
Member
 
Join Date: Feb 2012
Posts: 148
 
Device(s):
Carrier: Not Provided

Thanks: 32
Thanked 41 Times in 33 Posts
Default

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...
icedice34 is offline  
Reply With Quote
The Following User Says Thank You to icedice34 For This Useful Post:
scotty85 (February 27th, 2012)
Old February 27th, 2012, 08:30 AM   #8 (permalink)
Careful, They're sharp!!
 
Bob Cat's Avatar
 
Join Date: Nov 2010
Location: Midland's, South Carolina
Posts: 6,870
 
Device(s): Samsung Galaxy Note 2
Carrier: Big Red

Thanks: 2,402
Thanked 3,873 Times in 1,850 Posts
Default

Quote:
Originally Posted by icedice34 View 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.
Bob Cat is offline  
Last edited by Bob Cat; February 27th, 2012 at 08:37 AM.
Reply With Quote
The Following User Says Thank You to Bob Cat For This Useful Post:
scotty85 (February 27th, 2012)
Old February 27th, 2012, 08:43 AM   #9 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,657
 
Device(s):
Carrier: Not Provided

Thanks: 7,194
Thanked 6,789 Times in 4,269 Posts
Default

Quote:
Originally Posted by icedice34 View 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
scotty85 is online now  
Reply With Quote
The Following 4 Users Say Thank You to scotty85 For This Useful Post:
Bob Cat (February 27th, 2012), chknhwk (April 24th, 2012), icedice34 (February 27th, 2012), manbat (August 6th, 2012)
Old February 27th, 2012, 04:05 PM   #10 (permalink)
Beware The Milky Pirate!
 
El Presidente's Avatar
 
Join Date: Jan 2011
Location: Scotland
Posts: 26,672
 
Device(s): Xperia Z1, Nexus 7 3G, HTC One X, SGS3 Mini
Carrier: EE

Thanks: 14,058
Thanked 15,874 Times in 8,527 Posts
Default

Awesome work Scotty!
__________________
Site Rules & Guidelines / Staff List / Ask the Staff
Want to bring naughty posts to our attention? Use:
Be respectful to each other - That's what we're all about.
El Presidente is online now  
Reply With Quote
The Following 2 Users Say Thank You to El Presidente For This Useful Post:
jose1020 (August 7th, 2012), scotty85 (February 27th, 2012)
sponsored links
Old February 28th, 2012, 07:05 PM   #11 (permalink)
New Member
 
Join Date: Feb 2012
Posts: 2
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 0 Times in 0 Posts
Default Issue flashing recovery

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).


c:\mini-adb_vigor>fastboot devices
HT19SS201341 fastboot

c:\mini-adb_vigor>fastboot recovery.img
usage: fastboot [ <option> ] <command>

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

Anyone have an idea where I went wrong?
ellis245 is offline  
Reply With Quote
Old February 28th, 2012, 07:32 PM   #12 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,657
 
Device(s):
Carrier: Not Provided

Thanks: 7,194
Thanked 6,789 Times in 4,269 Posts
Default

Quote:
Originally Posted by ellis245 View Post
Code:
c:\mini-adb_vigor>fastboot devices
HT19SS201341    fastboot

c:\mini-adb_vigor>fastboot recovery.img
usage: fastboot [ <option> ] <command>

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
Anyone have an idea where I went wrong?
are you wanting to temporarily or permanently flash your recovery?

you are missing a vital word in your command:
Quote:
Originally Posted by ellis245 View Post
c:\mini-adb_vigor>fastboot action recovery.img
to temporarily flash recovery(using your image name "recovery"):
fastboot boot recovery.img

to permanently flash it:
fastboot flash recovery recovery.img
scotty85 is online now  
Reply With Quote
The Following 2 Users Say Thank You to scotty85 For This Useful Post:
chknhwk (April 24th, 2012), manbat (August 6th, 2012)
Old February 28th, 2012, 09:53 PM   #13 (permalink)
New Member
 
Join Date: Feb 2012
Posts: 2
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 0 Times in 0 Posts
Default Temporary

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.
ellis245 is offline  
Last edited by ellis245; February 28th, 2012 at 10:05 PM.
Reply With Quote
Old February 28th, 2012, 10:04 PM   #14 (permalink)
Member
 
Join Date: Feb 2012
Posts: 148
 
Device(s):
Carrier: Not Provided

Thanks: 32
Thanked 41 Times in 33 Posts
Default

Quote:
Originally Posted by scotty85 View Post
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&quot:
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?
icedice34 is offline  
Reply With Quote
Old February 29th, 2012, 06:50 AM   #15 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,657
 
Device(s):
Carrier: Not Provided

Thanks: 7,194
Thanked 6,789 Times in 4,269 Posts
Default

Quote:
Originally Posted by icedice34 View Post
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
scotty85 is online now  
Reply With Quote
The Following 2 Users Say Thank You to scotty85 For This Useful Post:
chknhwk (April 24th, 2012), manbat (August 6th, 2012)
Old February 29th, 2012, 07:31 AM   #16 (permalink)
Member
 
thornev's Avatar
 
Join Date: Nov 2011
Location: Hudson Valley, NY
Posts: 309
 
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 95 Times in 84 Posts
Default

Quote:
Originally Posted by scotty85 View Post
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.
thornev is offline  
Reply With Quote
Old February 29th, 2012, 07:40 AM   #17 (permalink)
Member
 
Join Date: Feb 2012
Posts: 148
 
Device(s):
Carrier: Not Provided

Thanks: 32
Thanked 41 Times in 33 Posts
Default

Quote:
Originally Posted by scotty85 View Post
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?
icedice34 is offline  
Reply With Quote
Old February 29th, 2012, 07:58 AM   #18 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,657
 
Device(s):
Carrier: Not Provided

Thanks: 7,194
Thanked 6,789 Times in 4,269 Posts
Default

Quote:
Originally Posted by icedice34 View Post
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 View Post
Will the process still work the same with each OTA?
yup! sure will
scotty85 is online now  
Reply With Quote
The Following 2 Users Say Thank You to scotty85 For This Useful Post:
chknhwk (April 24th, 2012), manbat (August 6th, 2012)
Old February 29th, 2012, 08:16 AM   #19 (permalink)
Member
 
Join Date: Feb 2012
Posts: 148
 
Device(s):
Carrier: Not Provided

Thanks: 32
Thanked 41 Times in 33 Posts
Default

Quote:
Originally Posted by scotty85 View Post
correct


yup! sure will
That is great news!
icedice34 is offline  
Reply With Quote
Old February 29th, 2012, 07:57 PM   #20 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,657
 
Device(s):
Carrier: Not Provided

Thanks: 7,194
Thanked 6,789 Times in 4,269 Posts
Default

Quote:
Originally Posted by thornev View 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

PH98IMG-2.01.605.11-vigor-recovery.zip
PH98IMG-2.01.605.11-vigor-recovery.zip 5e2f77d90d4cdfc0a221113ba52435a7
scotty85 is online now  
Reply With Quote
The Following User Says Thank You to scotty85 For This Useful Post:
chknhwk (April 24th, 2012)
sponsored links
Old March 2nd, 2012, 12:47 PM   #21 (permalink)
Member
 
Join Date: Feb 2012
Posts: 148
 
Device(s):
Carrier: Not Provided

Thanks: 32
Thanked 41 Times in 33 Posts
Default no root?

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?
icedice34 is offline  
Reply With Quote
Old March 2nd, 2012, 01:05 PM   #22 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,657
 
Device(s):
Carrier: Not Provided

Thanks: 7,194
Thanked 6,789 Times in 4,269 Posts
Default

Sometimes you'll get that... Just launch the recovery again,and wipe cache and dalvik cache. Then flash superuser again
scotty85 is online now  
Reply With Quote
Old March 2nd, 2012, 01:13 PM   #23 (permalink)
Member
 
Join Date: Feb 2012
Posts: 148
 
Device(s):
Carrier: Not Provided

Thanks: 32
Thanked 41 Times in 33 Posts
Default

Quote:
Originally Posted by scotty85 View Post
Sometimes you'll get that... Just launch the recovery again,and wipe cache and dalvik cache. Then flash superuser again
I tried installing twice and had problems. Basically you are saying I need to reboot and then wipe and reinstall?
icedice34 is offline  
Reply With Quote
Old March 2nd, 2012, 02:27 PM   #24 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,657
 
Device(s):
Carrier: Not Provided

Thanks: 7,194
Thanked 6,789 Times in 4,269 Posts
Default

Yup.
scotty85 is online now  
Reply With Quote
Old March 2nd, 2012, 02:42 PM   #25 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,657
 
Device(s):
Carrier: Not Provided

Thanks: 7,194
Thanked 6,789 Times in 4,269 Posts
Default

Might also verify the Md5 of your superuser download:

Superuser-3.0.7-efgh-signed.zip md5:a5d14dc42323a61caf71549a885af8c3
scotty85 is online now  
Last edited by scotty85; March 2nd, 2012 at 03:41 PM.
Reply With Quote
Old March 2nd, 2012, 04:50 PM   #26 (permalink)
Member
 
Join Date: Feb 2012
Posts: 148
 
Device(s):
Carrier: Not Provided

Thanks: 32
Thanked 41 Times in 33 Posts
Default

Quote:
Originally Posted by scotty85 View Post
Might also verify the Md5 of your superuser download:

Superuser-3.0.7-efgh-signed.zip md5:[COLOR="Red"]a5d14dc42323a61caf71549a885af8c3[/COLOR]

the reboot and reinstall worked. I have root access now. thanks for all your help!
icedice34 is offline  
Reply With Quote
The Following User Says Thank You to icedice34 For This Useful Post:
scotty85 (March 2nd, 2012)
Old March 3rd, 2012, 11:52 AM   #27 (permalink)
Junior Member
 
Join Date: Jun 2010
Posts: 72
 
Device(s):
Carrier: Not Provided

Thanks: 7
Thanked 17 Times in 7 Posts
Default

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
Aremihc is offline  
Reply With Quote
Old March 3rd, 2012, 07:49 PM   #28 (permalink)
New Member
 
Join Date: Dec 2011
Location: Galloway, NJ
Posts: 13
 
Device(s): ASUS Transformer Prime, HTC Rezound, Classic nook.
Carrier: Not Provided

Thanks: 4
Thanked 3 Times in 3 Posts
Default

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.
EddieE is offline  
Reply With Quote
Old March 3rd, 2012, 09:04 PM   #29 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,657
 
Device(s):
Carrier: Not Provided

Thanks: 7,194
Thanked 6,789 Times in 4,269 Posts
Default

Quote:
Originally Posted by EddieE View Post
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 View Post
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.
scotty85 is online now  
Last edited by scotty85; March 3rd, 2012 at 09:12 PM.
Reply With Quote
The Following User Says Thank You to scotty85 For This Useful Post:
manbat (August 6th, 2012)
Old March 3rd, 2012, 10:58 PM   #30 (permalink)
New Member
 
Join Date: Dec 2011
Location: Galloway, NJ
Posts: 13
 
Device(s): ASUS Transformer Prime, HTC Rezound, Classic nook.
Carrier: Not Provided

Thanks: 4
Thanked 3 Times in 3 Posts
Default

Quote:
Originally Posted by scotty85 View Post
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?
EddieE is offline  
Reply With Quote
sponsored links
Old March 4th, 2012, 12:39 AM   #31 (permalink)
Member
 
thornev's Avatar
 
Join Date: Nov 2011
Location: Hudson Valley, NY
Posts: 309
 
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 95 Times in 84 Posts
Default

Quote:
Originally Posted by EddieE View Post
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.
thornev is offline  
Reply With Quote
Old March 4th, 2012, 07:05 AM   #32 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,657
 
Device(s):
Carrier: Not Provided

Thanks: 7,194
Thanked 6,789 Times in 4,269 Posts
Default

Quote:
Originally Posted by EddieE View Post
. After an OTA update removes the root can I use Titanium Backup to restore my apps and settings after rooting again?
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)
scotty85 is online now  
Reply With Quote
The Following 3 Users Say Thank You to scotty85 For This Useful Post:
acoastal (July 5th, 2012), EddieE (March 4th, 2012), manbat (August 6th, 2012)
Old March 4th, 2012, 07:56 AM   #33 (permalink)
New Member
 
Join Date: Dec 2011
Location: Galloway, NJ
Posts: 13
 
Device(s): ASUS Transformer Prime, HTC Rezound, Classic nook.
Carrier: Not Provided

Thanks: 4
Thanked 3 Times in 3 Posts
Default

Quote:
Originally Posted by thornev View Post
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.
EddieE is offline  
Reply With Quote
Old March 4th, 2012, 08:12 AM   #34 (permalink)
New Member
 
Join Date: Dec 2011
Location: Galloway, NJ
Posts: 13
 
Device(s): ASUS Transformer Prime, HTC Rezound, Classic nook.
Carrier: Not Provided

Thanks: 4
Thanked 3 Times in 3 Posts
Default

Quote:
Originally Posted by scotty85 View Post
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.
EddieE is offline  
Reply With Quote
The Following User Says Thank You to EddieE For This Useful Post:
scotty85 (March 4th, 2012)
Old March 4th, 2012, 08:34 AM   #35 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,657
 
Device(s):
Carrier: Not Provided

Thanks: 7,194
Thanked 6,789 Times in 4,269 Posts
Default

Awesome. Glad it was helpful. Holler if you have other questions
scotty85 is online now  
Reply With Quote
Old March 4th, 2012, 01:53 PM   #36 (permalink)
New Member
 
Join Date: Mar 2012
Posts: 3
 
Device(s):
Carrier: Not Provided

Thanks: 3
Thanked 2 Times in 2 Posts
Default

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.
phoenixgward is offline  
Last edited by phoenixgward; March 4th, 2012 at 02:01 PM. Reason: Add info
Reply With Quote
The Following User Says Thank You to phoenixgward For This Useful Post:
scotty85 (March 4th, 2012)
Old March 4th, 2012, 05:43 PM   #37 (permalink)
Junior Member
 
Join Date: May 2010
Posts: 18
 
Device(s):
Carrier: Not Provided

Thanks: 14
Thanked 3 Times in 3 Posts
Default

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!
aikiscott is offline  
Reply With Quote
The Following User Says Thank You to aikiscott For This Useful Post:
scotty85 (March 4th, 2012)
Old March 4th, 2012, 06:10 PM   #38 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,657
 
Device(s):
Carrier: Not Provided

Thanks: 7,194
Thanked 6,789 Times in 4,269 Posts
Default

awsome! im glad it was helpful to both of ya

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
scotty85 is online now  
Reply With Quote
The Following User Says Thank You to scotty85 For This Useful Post:
aikiscott (March 4th, 2012)
Old March 4th, 2012, 06:55 PM   #39 (permalink)
Senior Member
 
Mr. Boom's Avatar
 
Join Date: Jul 2010
Location: Nevada
Posts: 678
 
Device(s): HTC Rezound, Droid Incredible, Droid Incredible 4G
Carrier: Not Provided

Thanks: 117
Thanked 82 Times in 76 Posts
Default

I have used nothing but Mybackup Pro. Saves all app data and market links, and can freeze apps like TB. I like the interface much better than TB.
Mr. Boom is offline  
Reply With Quote
Old March 4th, 2012, 10:33 PM   #40 (permalink)
Member
 
thornev's Avatar
 
Join Date: Nov 2011
Location: Hudson Valley, NY
Posts: 309
 
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 95 Times in 84 Posts
Default

Quote:
Originally Posted by scotty85 View Post
you dont really need to run the RUU. you can just flash the stock recovery back,just like you flashed amon

PH98IMG-2.01.605.11-vigor-recovery.zip
PH98IMG-2.01.605.11-vigor-recovery.zip 5e2f77d90d4cdfc0a221113ba52435a7
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.
thornev is offline  
Last edited by thornev; March 4th, 2012 at 10:35 PM.
Reply With Quote
sponsored links
Old March 5th, 2012, 07:22 AM   #41 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,657
 
Device(s):
Carrier: Not Provided

Thanks: 7,194
Thanked 6,789 Times in 4,269 Posts
Default

Quote:
Originally Posted by thornev View 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.
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.
scotty85 is online now  
Last edited by scotty85; March 5th, 2012 at 07:34 AM.
Reply With Quote
The Following User Says Thank You to scotty85 For This Useful Post:
thornev (March 5th, 2012)
Old March 5th, 2012, 07:40 AM   #42 (permalink)
Junior Member
 
Join Date: May 2011
Posts: 75
 
Device(s): HTC Droid Incredible, Cyanogenmod 7.0.3, latest incredikernel
Carrier: Not Provided

Thanks: 10
Thanked 30 Times in 23 Posts
Default

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?
pwned is offline  
Reply With Quote
Old March 5th, 2012, 07:56 AM   #43 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,657
 
Device(s):
Carrier: Not Provided

Thanks: 7,194
Thanked 6,789 Times in 4,269 Posts
Default

Quote:
Originally Posted by pwned View 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?
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
scotty85 is online now  
Last edited by scotty85; March 5th, 2012 at 08:02 AM.
Reply With Quote
Old March 5th, 2012, 08:56 PM   #44 (permalink)
Member
 
thornev's Avatar
 
Join Date: Nov 2011
Location: Hudson Valley, NY
Posts: 309
 
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 95 Times in 84 Posts
Default

Quote:
Originally Posted by scotty85 View Post
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.
thornev is offline  
Reply With Quote
The Following User Says Thank You to thornev For This Useful Post:
scotty85 (March 6th, 2012)
Old March 5th, 2012, 11:01 PM   #45 (permalink)
Junior Member
 
Join Date: Jan 2011
Location: America
Posts: 71
 
Device(s): Samsung Infuse 4G
Carrier: Not Provided

Thanks: 2
Thanked 11 Times in 10 Posts
Default

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>
tCizzler is offline  
Reply With Quote
Old March 5th, 2012, 11:28 PM   #46 (permalink)
Member
 
thornev's Avatar
 
Join Date: Nov 2011
Location: Hudson Valley, NY
Posts: 309
 
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 95 Times in 84 Posts
Default

Quote:
Originally Posted by tCizzler View 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.

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.
thornev is offline  
Reply With Quote
The Following User Says Thank You to thornev For This Useful Post:
scotty85 (March 6th, 2012)
Old March 6th, 2012, 04:35 AM   #47 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,657
 
Device(s):
Carrier: Not Provided

Thanks: 7,194
Thanked 6,789 Times in 4,269 Posts
Default

Quote:
Originally Posted by thornev View 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 View 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
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.
scotty85 is online now  
Last edited by scotty85; March 6th, 2012 at 04:38 AM.
Reply With Quote
The Following User Says Thank You to scotty85 For This Useful Post:
Drivembig (March 22nd, 2012)
Old March 6th, 2012, 05:44 AM   #48 (permalink)
Junior Member
 
Join Date: Jan 2011
Location: America
Posts: 71
 
Device(s): Samsung Infuse 4G
Carrier: Not Provided

Thanks: 2
Thanked 11 Times in 10 Posts
Default

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?
tCizzler is offline  
Reply With Quote
The Following User Says Thank You to tCizzler For This Useful Post:
scotty85 (March 6th, 2012)
Old March 6th, 2012, 06:11 AM   #49 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,657
 
Device(s):
Carrier: Not Provided

Thanks: 7,194
Thanked 6,789 Times in 4,269 Posts
Default

check out posts 21-26,see if that helps
scotty85 is online now  
Reply With Quote
The Following User Says Thank You to scotty85 For This Useful Post:
Drivembig (March 22nd, 2012)
Old March 6th, 2012, 06:58 AM   #50 (permalink)
Junior Member
 
Join Date: Jan 2011
Location: America
Posts: 71
 
Device(s): Samsung Infuse 4G
Carrier: Not Provided

Thanks: 2
Thanked 11 Times in 10 Posts
Default

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?

Thanks
tCizzler is offline  
Reply With Quote
Reply


Go Back   Android Forums > Android Phones > HTC Rezound > Rezound - All Things Root
Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT -5. The time now is 04:01 PM.
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.