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!
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Might also verify the Md5 of your superuser download:
Superuser-3.0.7-efgh-signed.zip md5:[COLOR="Red"]a5d14dc42323a61caf71549a885af8c3[/COLOR]
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.
a custom recovery could possibly installed,but would disapear as soon as you boot the phone.
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."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.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
tags.
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 rebooteda 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.
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.After an OTA update removes the root can I use Titanium Backup to restore my apps and settings after rooting again?
. 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.
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)![]()

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

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. =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.
Life is good.Your 2nd command is missing a blank between "md5" and "recovery..."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>
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.


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
