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

Root Trying to fix the Rezound from something...

M

Member 45863

Guest
On Thursday afternoon I noticed my Rezound screen wasn't shutting off after I checked a txt msg. Nothing major it had been a day or two since I did a reboot so I rebooted it and it only comes up to the HTC screen and stops. I have let it sit there for about 5 min.

When I bought the phone I bought it used and I was told it was rooted. Clockwork Recovery is on it and it says "unlocked" across the top.

When I try to select recovery it takes me to the ClockworkMod Recovery v5.8.1.4 screen and on the very bottom of the screen it has a bunch of errors about not being able to mount command, and log and last_log.

When I attempt to do anything from this screen it just shows a picture of the ClockworkMod logo in the middle of the screen and does nothing....

I never did anything "rooted" with it, was just a good deal so I am thinking if there is a way to reset this to stock it might fix it...?

Someone said Thursday an OAU went out for the Rezound so maybe something with that jacked it up...

Can anyone help me out here.... PLEASE!

Viro

P.S.

If it matters this is on the Verizon Network....
 
clockwork is not good for the rezound,and may have screwed up your phnes filesystem.

you will need to run a few adb and fastboot commands in a cmd window on your PC to relock the bootloader,and youll need to flash a file in recovery to ensure that the "main version" in your phone is low enuff for the ruu to flash.

my recomendations would be to read thru the OP here: http://androidforums.com/rezound-al...ys-noob-friendly-root-guide-start-finish.html

you dont obviously need to register at htcdev or run the commands to unlock,but follow the directions to download "mini-adb",get it extracted and seeing your phone,and then follow the directions to install amon recovery in place of clockwork.

once youve done that,you can jump to post 2,and follow the directions under this heading: 2)"full ruu" method to unroot
they will tell you how to run the main version fix file,then relock the bootloader,and run the .exe file to get you back to stock gingerbread.

after that,if you leave the phone stock,with the stock recovery,any OTAs that come along will install naturally and without issue.

sorry to direct you to another thread,but all the info and directions are there,and its alot to retype over here ;)

ill watch this thread so you can post whatever questions you have along the way either here or the end of the other thread and we will get you thru installing a stock RUU,wich hopefully will fix your issue.
 
Very cool, have to wrap up a few things and will start on it in about 2 hours. Will post any issues/questions as I have them.

Really REALLY appreciate you helping point me in the right direction!

Viro
 
Ok I think I have a problem, I know the "debugging" was selected prior to this issue but I can't boot the phone up, only to the (pwr/vol dwn) screen so when I run the adb devices I assume it has to have the phone on to see the device..?

ATM it will not see the phone at this state when typing adb devices.

When I connect the phone via usb it says HTC drivers were successfully installed.

Thoughts?

Viro
 
Another thing is when I click the link to download the miniRUU2.01.605.11 (in post #2 of that thread) the only thing that will download on the page that pops up is iLividSetupV1.exe which appears to be a download manager of some kind.

Viro
 
virodeath said:
Ok I think I have a problem, I know the "debugging" was selected prior to this issue but I can't boot the phone up, only to the (pwr/vol dwn) screen so when I run the adb devices I assume it has to have the phone on to see the device..?

ATM it will not see the phone at this state when typing adb devices.

When I connect the phone via usb it says HTC drivers were successfully installed.

Thoughts?

Viro
Click to expand...
you are correct... the phone must be booted to use adb. what you will do is boot to hboot,select fastboot from the hboot menu,then plug in the phone. if the drivers are working,in your cmd window,typing fastboot devices should get your serial number back.

in fastboot you can flash or launch recovery,and run the .exe file.

"fastboot" on the phone is the mode that adb reboot bootloader will take you to. so in any directions you follow,you can more or less just start at fastboot devices

virodeath said:
Another thing is when I click the link to download the miniRUU2.01.605.11 (in post #2 of that thread) the only thing that will download on the page that pops up is iLividSetupV1.exe which appears to be a download manager of some kind.

Viro
Click to expand...

hmm its now saying that you need to sign in or sign up do download it. grrr. im gradually getting everything ive uploaded to androidfilehost.com,so i can upload it there if you need it,or you can try downloading from footballs folder:
FileFactory Folder View - Vigor

edit:
uploading now,so let me know if you cant download from filefactory
 
All file slots are currently active on that download location, will keep trying though.

So I want to ensure I do this in the correct order:

1. go into Hboot and select FastBoot
2. plug in USB (FastBoot on phone becomes "FastBoot USB")
3. in CMD window go to the mini-ADB_Vigor folder (c:\mini-adb_vigor\) and type adb devices
Kicks out the following msgs: adb Server is out of date. killing...
* daemon started successfully *
List of devices attached
(nothing listed)

Possible issue ADB not up-to-date?

Viro
 
and I want to ensure I am giving all the information needed.

At the Hboot screen this is what I see:

*** Unlocked ***
Vigor PVT Ship S-ON RL
Hboot-2.10.0000
eMMC-boot
Oct 5 2011,21:18:48

the rest is standard Hboot options

Viro

P.S.

Got a slot for that file but because I am not a member will take about 4hrs to download. :(
 
virodeath said:
All file slots are currently active on that download location, will keep trying though.

So I want to ensure I do this in the correct order:

1. go into Hboot and select FastBoot
2. plug in USB (FastBoot on phone becomes "FastBoot USB")
3. in CMD window go to the mini-ADB_Vigor folder (c:\mini-adb_vigor\) and type adb devices
Kicks out the following msgs: adb Server is out of date. killing...
* daemon started successfully *
List of devices attached
(nothing listed)
Click to expand...

almost... ;)

remember adb is only used in a booted phone.

you need to type

fastboot devices

idk if youll need to wait for these to finish their upload,but the links should be:

.exe file(run as administrator on PC)
http://www.androidfilehost.com/main....1123r_3161E_9K_QMR_release_233635_signed.exe

hboot flash(rename PH98IMG,place on sd,flash in hboot)
http://www.androidfilehost.com/main....1123r_3161E_9K_QMR_release_233635_signed.zip

they are about 35% currently

id try and use the .exe file first. only if you cannot get it to run,use the .zip file in hboot
 
OMG DUH! Yes you are correct Fastboot Devices... I can't believe I was typing adb devices... Thank you for pointing out the obvious! That did the trick now it is reporting the HTC serial.

I am downloading the .exe from your link now, say 45 min.

so now that it is seeing the HTC move on to post #2 correct?

Thanks again!

Viro
 
OK... /sigh very sorry but totally confused myself here...

Post #2 step 2 reads:

2)prepair to unroot:

-place the mini ruu into your "mini-adb_vigor folder". keep it named "RUU-2.01.605.11-mini"

-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

-verify the mini ruu:
md5sums miniRUU2.01.605.11.zip (it should output 00d8fe40e9fdb943d5c77855a9324dbf)
Click to expand...

Is the .exe that you pasted the link to the equivalent of the "RUU-2.01.605.11-mini" file?

It's been so long since I have rooted, I don't recall it being this difficult on the Droid X...

Viro
 
I think I am gtg with an attempt with the exception that I am having a tad bit of trouble understanding where the md3sums come from and where exactly the ,exe file I downloaded fits into the picture.

-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. **
Click to expand...


When I try to verify the md5sums via "md5sums miniRUU2.01.605.11.zip" I receive back an error:

'md5sums' is not recognized as an internal or external command, operable program or batch file.

I am issuing that cmd from inside the mini-adb_vigor directory on the computer, since I can't access a TE on the phone I assumed it was possible to do it here but maybe not..?

Viro
 
OK... LOL this is where I am at..

I downloaded md5sums 1.2 and placed in the mini-adb_vigor directory. :)

The Hboot area now says that it is *** relocked ***, I flashed the miniRUU2.01.605.11.zip and did the fast OEM lock.

ClockworkMod seems to be gone now but I am thinking I am not quite done yet..

I am pretty sure I need to hit it with the "SetMainVersionLOW.zip", just not 100% sure how. It was on the SD card in it's root directory this entire time.

Also I am reading through the other post and it appears I "should" be able to do a "adb devices" and see the phone but I am not able to do that. I can do a fastboot devices and see the phone.

Viro
 
virodeath said:
OK... /sigh very sorry but totally confused myself here...

Post #2 step 2 reads:



Is the .exe that you pasted the link to the equivalent of the "RUU-2.01.605.11-mini" file?

It's been so long since I have rooted, I don't recall it being this difficult on the Droid X...

Viro
Click to expand...
well,for starters... you are following the wrong directions. my recomendations were to follow 2)"full ruu" method to unroot so you could use the .exe file,wich may have provided some unexplainable benefits over using a mini,or full,hboot file(PH98IMG)

virodeath said:
I think I am gtg with an attempt with the exception that I am having a tad bit of trouble understanding where the md3sums come from and where exactly the ,exe file I downloaded fits into the picture.




When I try to verify the md5sums via "md5sums miniRUU2.01.605.11.zip" I receive back an error:

'md5sums' is not recognized as an internal or external command, operable program or batch file.

I am issuing that cmd from inside the mini-adb_vigor directory on the computer, since I can't access a TE on the phone I assumed it was possible to do it here but maybe not..?

Viro
Click to expand...
not sure why you were having trouble with the md5sums utility,unless you had accidentally deleted it,or you were not at the c:\mini-adb_vigor> prompt when you issued the command. also,the files you are md5sumsing need to also be in the mini-adb_vigor folder(if they were not,youd have gotten an error,but im not sure it would have been that one).

virodeath said:
OK... LOL this is where I am at..

I downloaded md5sums 1.2 and placed in the mini-adb_vigor directory. :)

The Hboot area now says that it is *** relocked ***, I flashed the miniRUU2.01.605.11.zip and did the fast OEM lock.

ClockworkMod seems to be gone now but I am thinking I am not quite done yet..

I am pretty sure I need to hit it with the "SetMainVersionLOW.zip", just not 100% sure how. It was on the SD card in it's root directory this entire time.

Also I am reading through the other post and it appears I "should" be able to do a "adb devices" and see the phone but I am not able to do that. I can do a fastboot devices and see the phone.

Viro
Click to expand...

if you are on a booted,workign phone now then you should be able to use adb devices. make sure usb debugging is enabled.

if the phone still wont boot,then adb is still off limits... you can only use fastboot commands,with the phone in fastboot.

if your phone has booted and is working,then id say you could call it done. :)

if youre still having issue,then go ahead and run the .exe. if the mini-ruu flashed,then your main version is prolly set correctly to 2.01.605.11 and the other files should flash fine :)

sorry the directions were unclear(2 methods,not 2 steps) and that i fell asleep... had to get up early this mornin.
 
Sorry I misunderstood, on the step 2, I thought you meant post #2. My bad, already the phone doesn't appear to be bricked yet. However add I sit the phone still isn't booting correctly, still hangs at the HTC screen. I will post more at lunch time I'm at work right now thank you for all the help.

Viro
 
When I flashed the miniRUU2.01.605.zip file it said it was successful when or was done. So far there hasn't Been error messages.

But like I said before, adb devices dies nor show the HTC phone like the fastboot devices does.

Viro
 
hmmm,thats not sounding like a good sign.

try running the .exe file next,then the PH98IMG if you cant get the .exe to run
 
Is there anything to running that .exe?

I mean run in admin I know but is it supposed to do something to let you know it is working? I haven't seen any popups or anything indicating it is working.

Viro
 
it should ask if you want to allow it to make changes to your pc. tell it yes,it will go thru several screens of disclaimers,plugging in the phone,verifying phone info,and "heres what will happen". it will boot the phone to ruu mode(black screen with htc in the center) and youll have a green status bar on the phone,and a status bar on the utility as it updates.

if it finds info it doesnt like,or cant communicate with the phone,it should give you errors after a couple moinutes.

did you get it working?

if not,you can use to the .zip file i uploaded. you can place it on the sd card and rename it PH98IMG,or you can flash it in hboot like you did the mini-ruu( fastboot oem reboot ruu,and flashtboot flash zip commands)

your bootloader is relocked at this time,correct?
 
The exe didn't do anything, so tonight I will flash the zip file. Yes the phone has been relocked.

Viro
 
if it just immmediately closed,it may be something on your pc interfereing... antivirus maybe seeing it as a malicious attack?

hopefully runing the .zip will fix you up :)
 
You must log in or register to reply here.
Back
Top Bottom