***Please Help*** Urgent! May have bricked

[Wanda]

Try this.

rezound_ics_androidpolice_3.11.605.22 - Minus

Remember, to flash the RUU as a .zip your bootloader has to be locked and the RUU needs to be reanamed PH98IMG.zip I've heard of people trying to rename it and for whatever reason Windows renames it PH98IMG.zip.zip

You may need to consider running the RUU as a .exe. You'll need pizzadude or Mr. Smith's help for that as I've never done it that way.

Edit: I see you're looking for the Stock RUU...the link above is to an ICS leaked RUU so you may want to just Google the stock one and find it that way. Once you move up to ICS it's hard to go back to GB...hardware limitation, not because it's so much better.

 

[anon(94115)]

to run as an exe, just make sure the drivers are installed, hook the phone up (be sure it is connected) and click the exe. It will run you through the rest step by step.

I only add this so that if you need it, it is there. Otherwise follow those smarter than I. I am having a HUGE off day with the rezound, but I know what I said above is right....

 

[-Droid-]

Try this.

rezound_ics_androidpolice_3.11.605.22 - Minus

Remember, to flash the RUU as a .zip your bootloader has to be locked and the RUU needs to be reanamed PH98IMG.zip I've heard of people trying to rename it and for whatever reason Windows renames it PH98IMG.zip.zip

You may need to consider running the RUU as a .exe. You'll need pizzadude or Mr. Smith's help for that as I've never done it that way.

Edit: I see you're looking for the Stock RUU...the link above is to an ICS leaked RUU so you may want to just Google the stock one and find it that way. Once you move up to ICS it's hard to go back to GB...hardware limitation, not because it's so much better.

Just tried this way also. Downloaded the file, locked the bootloader, renamed the file and put it on the root of the sd card but I get error main version older.

 

[-Droid-]

to run as an exe, just make sure the drivers are installed, hook the phone up (be sure it is connected) and click the exe. It will run you through the rest step by step.

I only add this so that if you need it, it is there. Otherwise follow those smarter than I. I am having a HUGE off day with the rezound, but I know what I said above is right....

Like I said before I get error 140 although i just looked and I don't know if I have the htc drivers or not. Maybe if you could please post a link to the drivers I'll try it again. I did a google search but couldn't find any links

 

[-Droid-]

Also do you think Verizon would check that it's relocked or could I take it under warranty? And if so could they fine me $650 for the refurbished one that they send me if they see it's relocked?

 

[MrSmith317]

Also do you think Verizon would check that it's relocked or could I take it under warranty? And if so could they fine me $650 for the refurbished one that they send me if they see it's relocked?

Don't worry about that. You really shouldn't need to go that far either. Try to follow my how-to on flashing an ruu. If you continue to get the mainver error there's a fix for that on xda. It sets your mainver back to 1.0. When I get to a PC I'll update this post with links.

Sent from my Paranoid Android Galaxy Nexus

 

[-Droid-]

Finally fixed it by resetting the mainver to 1.XXX in the 4th post of this link HTC Misctool [Tool to read/write main version] - xda-developers
The used the application that wanda and pizzadude showed me to get back to 2.XXX.
After that it no longer recognized the sim card so I went into Verizon, got a new one, and I'm good to go now.
Anyway, just wanted to help anyone else that may have this problem. Once again thanks to all of you, I got my phone working again, but I think I'll just wait until the OTA ICS comes out now!!!

 

[Wanda]

Finally fixed it by resetting the mainver to 1.XXX in the 4th post of this link HTC Misctool [Tool to read/write main version] - xda-developers
The used the application that wanda and pizzadude showed me to get back to 2.XXX.
After that it no longer recognized the sim card so I went into Verizon, got a new one, and I'm good to go now.
Anyway, just wanted to help anyone else that may have this problem. Once again thanks to all of you, I got my phone working again, but I think I'll just wait until the OTA ICS comes out now!!!

I completely understand your reservations about rooting and ROMing considering you're experience. I would point out though that some good reading and homework could have prevented much of your troubles and when done in the proper order rooting and installing ROM's is very easy and painless (minus setting up your phone again).

If you get the itch to get your ICS on give us a shout and we'll be here if you need help.

If you're going to wait for the OTA...well, get comfortable...it could be a while

 

[JTAC]

Ok...I am in the same boat. However my problem is this...I have no custom recovery, when I hit recovery it just goes to a black screen and then nothing happens. Second problem is this....if I try doing adb commands, it says device not found.

 

[MrSmith317]

Ok...I am in the same boat. However my problem is this...I have no custom recovery, when I hit recovery it just goes to a black screen and then nothing happens. Second problem is this....if I try doing adb commands, it says device not found.

If you're in HBOOT, ADB doesn't work, fastboot does. If you're in the normal phone mode, make sure USB debugging is enabled. Take a look at my guide for unlocking and loading a custom recovery.

 

[JTAC]

If you're in HBOOT, ADB doesn't work, fastboot does. If you're in the normal phone mode, make sure USB debugging is enabled. Take a look at my guide for unlocking and loading a custom recovery.

That's the thing I had USB Debugging enabled. I cannot get into normal phone mode at all. Stuck at HBOOT or a black screen.

 

[MrSmith317]

That's the thing I had USB Debugging enabled. I cannot get into normal phone mode at all. Stuck at HBOOT or a black screen.

In HBOOT, you can use fastboot commands, not ADB commands. Fastboot commands are more limited but if you have the AmonRa .img file you can flash it there. "fastboot flash recovery <insert amon ra img file here>"

 

[JTAC]

Smith...thanks for helping me out....but anytime I do a fastboot command it hangs on waiting for device. Any tips? So used to being spoiled with easy root like Droid and Nexus.

 

[MrSmith317]

Smith...thanks for helping me out....but anytime I do a fastboot command it hangs on waiting for device. Any tips? So used to being spoiled with easy root like Droid and Nexus.

You should be sitting in HBOOT with the message "Fastboot USB" staring at you. That's the one and only time that fastboot will work.

 

[JTAC]

Then just put the recovery img in the folder on desktop? Correct? Rather ask 5 times and do it once.

 

[MrSmith317]

Then just put the recovery img in the folder on desktop? Correct? Rather ask 5 times and do it once.

Copy it to wherever you like, but the same directory as fastboot is the easiest. I'll show you why.

If I used c:\androidsdk(and copied the img there) , here's the command I'd use:
"cd \androidsdk"
"fastboot flash recovery recovery.img"

If I did the same but copied the img to desktop:
"cd \androidsdk"
"fastboot flash recovery c:\users\myusername\desktop\recovery.img"

So it's up to you. Hopefully you see the potential pitfall.

 

[JTAC]

New error message. Cannot load the recovery image.

 

[MrSmith317]

You are unlocked right? As long as you're unlocked you may just have a bad download.

 

[JTAC]

Ok. Here is what I did with success. Downloaded Amon Ra 3.14. Changed the name to recovery.img. Put that in C:\Program Files\Android\android-sdk\platform tools. Then once the prompt was changed to the above...type, fastboot flash recovery recovery.img

All I got to do now is finish rooting.

 

[JTAC]

Ok. This phone is killing me. Flashed the recovery.img and then went to recovery, developer menu and installed super user. Rebooted device after that completed, it powered on, saw HTC screen and now is stuck on a black screen.