I've followed your guide, flashed the recovery, try to boot into recover, and it just boots normally. I've tried ten different ways from Sunday and cannot root this device. Rooted my Tbolt, Bionic, Razr, and Galaxy with ease, but this Rezound POS is pathetic. I'm about to sell this thing unless you can offer some advice on why I can't boot into recovery? I've tried ARa3.14 3.15 and two others, still can't get the thing to recovery. I've turned off fastboot, turned it on, this that, unlocked the device through the long process of getting the code and sending it to htc. I'm so frustrated I'm about to ___@#$^%!#
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root Scottys noob friendly root guide-start to finish
- Thread starter scotty85
- Start date
-
- Tags
- htc rezound
manbat
Newbie
My phone is a Rezound....S-off....used instructions here to root after upgrading to the Global update. Went smoothly. Recovery AmonRa 3.15 booted fine. AmonRa 3.15 was on computer and Superuser zip on SD Card. Flashed from there. Kept stock recovery on phone. What Hboot do you have? Stock Hhoot may keep you for booting AmonRa remotely....Are you S-off?
scotty85
Extreme Android User
take some deep breaths.
1)what directions did you follow to flash recovery?
2)how are you trying to boot to recovery?
3)what is happening when you boot to recovery?
4)you are unlocked correct?
I followed your exact instructions, got the code, processed the unlock. It does say "tampered" then "unlocked" then some coding and so forth when booting volume down and pwr. Then it goes thru the PH**** check, and I select "Recovery" and it shows a white screen for about 30 seconds, then screen goes blank, shows white screen again, flashes off, then back on, then dims and loads like normal.
manbat
Newbie
Have you tried...Unpluging USB, Pulling Battery, Replace battery, Hold volume and power. This will take you to Hboot Screen. Then scroll to and select recovery. If your flash worked you should be in AmonRA...
Your screenshot showns that you Flashed recovery not booted to recovery.
Your screenshot showns that you Flashed recovery not booted to recovery.
Yep tried all that. It's like the recovery isn't taking, and I've tried at least four different recoveries at this point.
manbat
Newbie
I always work from a folder directly on my C drive.....Looks like you are working from a desktop folder and directing to a recovery image that is in a folder in that folder. Try shortening the command line by working right from C Drive. I originally Rooted mine when there was a working(Gingerbread) ONE-Click-Root. I S-Offed with the original JBear Beta.
scotty85
Extreme Android User
sounds to me like you have flashed something to the recovery partition,that is not a recovery.
if you had simply not flashed a custom recovery,then selecting recovery would take you to the stock recovery(red triangle and !)you are going to have to quit being so vauge in your explantions. if you had followed the directions exactly,you would be getting to recovery
there is something youre overlooking. i can help you fix it,but i need more than "i followed directions exactly" and "some coding and so forth".lets start over,from square one. youre unlocked,so going back to step 2:
-download amon recovery from the link in the OP.
-repeat the steps in step 2 "flash a recovery". make sure you are flasing an .img file,not a .zip file.
-if the process fails this time,copy everything in your cmd window,and paste it here. to copy in cmd,right click,click mark,highlight everything in white. hit enter.
scotty85
Extreme Android User
I flash the recovery and it states successfully, and then try to load recovery and the phone merely reboots like normal after a couple white screen HTC flashes.
im not exactly sure what youre doing here. fastboot reboot is the command that tells the phone to reboot normally,so its not surprising thats what its doing.
after the phone has rebooted,have you tried adb reboot recovery ??
or entering thru hboot as manbat suggested?
I even made a video of the entire process located here:
Rezound Recovery Will Not Start - YouTube
Rezound Recovery Will Not Start - YouTube
Code:
C:\Users\Anthony\Desktop\adbmini>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT1BMS206963 device
C:\Users\Anthony\Desktop\adbmini>adb reboot bootloader
C:\Users\Anthony\Desktop\adbmini>fastboot devices
HT1BMS206963 fastboot
C:\Users\Anthony\Desktop\adbmini>fastboot flash recovery recovery-ra-vigor-3.15-
gnm.img
sending 'recovery' (7078 KB)... OKAY [ 1.670s]
writing 'recovery'... OKAY [ 2.269s]
finished. total time: 3.939s
C:\Users\Anthony\Desktop\adbmini>scotty85
Extreme Android User
i watched the video as well. it certainly appears that everything is correct. only things coming to mind at the moment,are:
1)the image has become corrupt
2)you may have a bad usb cable.
3)something is running on the PC and interfering with the flash(therefore corrupting the recovery partition). make sure you do NOT have htc sync,pda net,easy tether,or any other programs cable of comunicating with the phone running.
try different ports on the PC,and different cables.
what is the md5 sum if the exact image that you flashed?
you could try installing the recovery as a PH98IMG in hboot(leaving usb cables out of the equation) but hboot flashing with s-on is a PITA. youll need to make sure the main version number on the android info document is the same or higher,as your current main version.
you can try fastboot booting the recovery,but with a bad image,or a bad usb cable,the phone will prolly hang at the htc screen
i have seen a couple cases like this where everything seems 100% correct,and the only solution was for the user to use a different PC.
1)the image has become corrupt
2)you may have a bad usb cable.
3)something is running on the PC and interfering with the flash(therefore corrupting the recovery partition). make sure you do NOT have htc sync,pda net,easy tether,or any other programs cable of comunicating with the phone running.
try different ports on the PC,and different cables.
what is the md5 sum if the exact image that you flashed?
you could try installing the recovery as a PH98IMG in hboot(leaving usb cables out of the equation) but hboot flashing with s-on is a PITA. youll need to make sure the main version number on the android info document is the same or higher,as your current main version.
you can try fastboot booting the recovery,but with a bad image,or a bad usb cable,the phone will prolly hang at the htc screen
i have seen a couple cases like this where everything seems 100% correct,and the only solution was for the user to use a different PC.
manbat
Newbie
Are you using the EXTUSB cable that comes with the Rezound?...I have had trouble with regular micro usb cables when trying to do some things before. I had to remove HTC Sync completely to get constant results.....with the HTC Sync installed things worked sometimes and sometimes Not..
wayrad
Android Expert
I'm wondering if anyone can help me - something has gone rather badly amiss. Last Saturday I followed the instructions in this thread to unlock the bootloader, temporarily install a recovery, and root my Rezound (wow, it's a lot different from doing it on my late lamented DInc). I did mess up at one point - got the latest Amon-Ra 3.15 and checked the md5, then found fastboot boot didn't do anything. Realized that the file I had downloaded was zipped and the instructions seemed to have been written for the older non-zipped version. Unzipped with 7-zip and tried the fastboot boot command again. Still in Hboot. Found out that unzipping had changed the md5 somehow. Went back and got the nonzipped Amon-Ra 3.14, checked md5, tried again. It appeared to work then. After that I flashed the superuser files and things seemed OK.
I did have a strange episode the next day where it kept saying "unfortunately, the wallpaper application has stopped" and showing me a black screen with just the notification bar. I had been disabling bloatware and figured I'd accidentally disabled something I shouldn't. Did a factory reset and things went back to normal for almost a week. I've been running root-only apps with no problem.
Anyway, last night I was transferring ebook files to my card from my Calibre library, which has never caused any trouble before, but the phone crashed when I tried to take it out of disk drive mode. Now it's in a boot loop - mostly it goes back and forth between the boot animation and the splash screen, but sometimes it says "Updating Android application, Optimizing file X of xx" and continues like that for a while with the file number changing before going back into the boot loop. A couple of times it made it to the lockscreen or the language selection screen, but no further.
I can pull the battery and get into hboot with the hard keys, but when hboot is loading I get a series of brief messages - they go by quickly but I think it says the image is missing. Saw something about PBIMG? - so I think the stock recovery image is corrupted maybe. When it does get into hboot there is a "Tampered" message at the top of the screen.
I tried connecting to my desktop with the cable, but adb devices is not doing anything (same computer I used before, the mini-adb_vigor folder is intact).
Can anyone offer any advice? Have I bricked it? At this point I'm about ready to start scouring craigslist for a Nexus.
I did have a strange episode the next day where it kept saying "unfortunately, the wallpaper application has stopped" and showing me a black screen with just the notification bar. I had been disabling bloatware and figured I'd accidentally disabled something I shouldn't. Did a factory reset and things went back to normal for almost a week. I've been running root-only apps with no problem.
Anyway, last night I was transferring ebook files to my card from my Calibre library, which has never caused any trouble before, but the phone crashed when I tried to take it out of disk drive mode. Now it's in a boot loop - mostly it goes back and forth between the boot animation and the splash screen, but sometimes it says "Updating Android application, Optimizing file X of xx" and continues like that for a while with the file number changing before going back into the boot loop. A couple of times it made it to the lockscreen or the language selection screen, but no further.
I can pull the battery and get into hboot with the hard keys, but when hboot is loading I get a series of brief messages - they go by quickly but I think it says the image is missing. Saw something about PBIMG? - so I think the stock recovery image is corrupted maybe. When it does get into hboot there is a "Tampered" message at the top of the screen.
I tried connecting to my desktop with the cable, but adb devices is not doing anything (same computer I used before, the mini-adb_vigor folder is intact).
Can anyone offer any advice? Have I bricked it? At this point I'm about ready to start scouring craigslist for a Nexus.
wayrad
Android Expert
Thanks for the reply Scotty! That is somewhat reassuring, but how do I do any of that when I can't communicate with the device via adb? A couple of times I got it to return the serial number when I caught it in the exact right place while it was starting up from a battery pull/factory reset via hard buttons, but it didn't stay connected long enough to type the next command. I couldn't even get "adb devices" to work twice in a row.
scotty85
Extreme Android User
Thanks for the reply Scotty! That is somewhat reassuring, but how do I do any of that when I can't communicate with the device via adb? A couple of times I got it to return the serial number when I caught it in the exact right place while it was starting up from a battery pull/factory reset via hard buttons, but it didn't stay connected long enough to type the next command. I couldn't even get "adb devices" to work twice in a row.
adb will never work with the phone in fastboot,adb is for use within the booted operating system.
all you need to do is power on into hboot,wait for the green writing to flash and then disapear(wich is perfectly normal,your phone isnt missing anything) and then select fastboot with the vol rocker and power button. this will put you into fastboot,wich is the same mode the phone is in after typing adb reboot bootloader.
open a cmd window,then plug the phone in,with it in fastboot,and type fastboot devices wich should return your serial number.
then launch recovery,just like you did in step 2 of the root guide:
fastboot boot recoveryname.img
this will start your recovery,and you can restore a backup,or flash a rom of choice.
if youre on gingerbread firmware,youll have to flash this old firmware patch if you want to flash an ICS rom.
the best thing would be to restore a know working backup,so that you know the phone is fine,and dont have to search for a good rom in a state of panic
once your phone works again,you can take time to properly research what rom you want to try.also in the future b careful what you delete with titanium,as this was almost certainly what caused your situation,even tho it may have taken some time to surface. just make backups so that youve always got a working one to restore.
if it comes down to running an ruu,well need to know your current software build to find it. if you dont have that information,the info in your hboot screen should give us a clue.
sorry for my short answer earlier,i was at work
wayrad
Android Expert
Thanks Scotty! I'll try that after a night's sleep when my brain is fresher. Probably tomorrow afternoon (tied up in the AM). I did try "adb devices" unsuccessfully when it was in fastboot, but not "fastboot devices". This is pretty new to me and it's hard to get a firm grasp of the whole business just from reading. Thanks for the help.
I didn't delete anything with Titanium, just used the ICS Settings/Apps to disable them. The factory reset I did subsequently should have fixed that, right?
Anyway, I did make a nandroid when your instructions said to. Hopefully I can restore it. I think I might eventually want to permanently install a custom recovery to avoid this sort of situation in future. Now that I've got the ICS update and no more seem likely to come out any time soon, that doesn't seem like as much of a factor as when you wrote your guide. And I do want to be able to flash ROMs easily - I've really missed that since getting the Rezound.
Probably tomorrow afternoon (tied up in the AM). I did try "adb devices" unsuccessfully when it was in fastboot, but not "fastboot devices". This is pretty new to me and it's hard to get a firm grasp of the whole business just from reading. Thanks for the help.I didn't delete anything with Titanium, just used the ICS Settings/Apps to disable them. The factory reset I did subsequently should have fixed that, right?
Anyway, I did make a nandroid when your instructions said to. Hopefully I can restore it. I think I might eventually want to permanently install a custom recovery to avoid this sort of situation in future. Now that I've got the ICS update and no more seem likely to come out any time soon, that doesn't seem like as much of a factor as when you wrote your guide. And I do want to be able to flash ROMs easily - I've really missed that since getting the Rezound.
scotty85
Extreme Android User
you can permantly install a recovery if you wish,but keep in mind it may actually make things more difficult for you. s-on phones are not able to flash the kernel from recovery,so youll be stuck at the splash screen with kernel incompatibilities if you try and restore a backup or flash a rom with a differrent kernel from a permanent recovery.
if you want to stay s-on,get into the habit of launching your recovery with fastboot boot even if you wish to permantly install one.
more info: http://androidforums.com/rezound-all-things-root/587430-s-want-flash-roms-read.html
wayrad
Android Expert
Woohoo! I'm back in business - just had to reflash the superuser files since my nandroid was made before I did it last time. And it looks like my Titanium backup is gone with the wind - I really hate the Rezound's habit of putting backups in internal memory.
This is all a lot less scary the second time around.
I really appreciate your help!One more quick question - is it normal for the Settings/Software Update/Status page to say:
Source: Verizon Wireless
Name:
Status:
Code: 0
Date:
Time:
Description:
Looks odd, but I really have no idea what it was like before. And is the "Tampered" flag on the bootloader screen normal now?
scotty85
Extreme Android User
yup,and yup.
the tampered is from launching recovery and flashing superuser,its a new watermark with ICS.
and i believe that the OTA bit is what it always looks like when there are no updates. you should be good to go