[Q] Freezing and crashing Rezound - HTC Rezound

Hope my fellow nerds can help me out..
I have been rooted unlocked and S-OFF for many months
I was running Android 4.0.1 stock I believe, not so sure now, and it ran well for several months.
About a week ago, my phone started acting up.
Symptoms:
-Freezing for ~10 seconds about every 30 seconds of use
-If I call anyone, the phone freezes but continues with the call, still able to talk and hear, screen completely non-interactive. Restarts itself in the middle of call after about 60 seconds.
-The power button turns off the screen, but not always the touch button lights. The times that lights stay on, the screen randomly comes back on, goes back off, and the button lights stay on, repeat..
-When trying to power off, the screen goes off, buttons stay lit, still receive notifications etc. for about 30 seconds then finally powers off.
-When the screen is off, it doesn't always want to come back on.
Fix attempts:
Factory Reset, wipe cache, and dalvik
flashed RUU 4.03.605.2
flashed TWRP_v2.2.2.1v4.5
flashed Nils' Business_ICS4.0.3_Sense3.6-v6.3
still had problems...
OLD:
HBOOT 2.25.000
Radio 1.22.10.0421r/1.22.10.0424r
Current:
HBOOT 2.27.000
Radio 2.22.10.0801r/2.22.10.0803r
please ask me anything that might help.

I would try amonra recovery. It is the most reliable for pretty much any phone. Nils room is rock solid stable and fast. Almost seems like hardware problem to me but not necessarily. Try amon ra, factory reset, wipe cache, dalvik, AND SYSTEM 3x each then flash Rom again. Try ineffabilis dues 1.2 as well. Then report back
Sent from my Rezound using Tapatalk 2

I agree with evocm7 but I'd run the latest ruu again.. while stock do a factory reset.. then flash amon ra. Then flash your rom again..
sent from my s-off reZound rockin' viperRez Rom on global ICS firmware

Quick update.
I reinstalled 4.03.605.2 and then performed a factory reset and the phone was working flawlessly until I made a phone call.
I played with it a good 10 min before I made the fail call.
then installed Amon Ra 3.15, Wiped EVERYTHING..
currently installing RUU 3.14.605.12 (wanted to see if I have more luck with an older version?)
Download on Ineffabilis Deus v1.2 is down I guess

forgot
One thing that I forgot to mention is that when booting up, sometimes it says "upgrading android"
I have no idea why it has been doing that, it does it with all roms but not every boot, just most.

I feel like there is part of the phones firmware is corrupt and it doesn't get changed when you factory reset or wipe or reinstall. There has to be a way to reformat the ENTIRE phone right? One of the times after wiping everything and installing a new RUU, when running it was like "Would you like to recover this email we found to be previously on the phone?"
update: currently running ViperRez 1.0.3 same problems.
RUU 3.14.605.12 didnt help
Amon Ra didnt change anything
RUU 4.03.605.2 -> then ViperRez

famouscollin said:
I agree with evocm7 but I'd run the latest ruu again.. while stock do a factory reset.. then flash amon ra. Then flash your rom again..
sent from my s-off reZound rockin' viperRez Rom on global ICS firmware
Click to expand...
Click to collapse
I see you are running ViperRez, I cannot figure out how to get rig of that ongoing notification showing wifi status. I do not have 10 posts yet so I cannot ask on ViperRez Thread

Related

[Q] Bootloop that's not fixed by CDMA/LTE Auto Setting

Hey, I hope you guys can help me out.
I have a rezound here, that is bootlooping. It will stay booted into android for maybe 15 seconds then freezes, and reboots. I searched and saw a fix that involved changing the phone setting to CDMA/LTE evda Auto, and it was already apparently on that setting.
It wasn't letting me factory reset it, even from the bootloader menu. It would look like it was factory resetting, but then still not be factory reset. The only way I could get it to factory reset was by unlocking the bootloader through HTC DEV...but that didn't fix the issue. (Warranty was already void anyway because the void screw was tampered with)
What should I try next? I've flashed a rom on an evo 3d where I had to load a custom recovery through the bootloader, so I figured there was probably something similar on the rezound...but this has S-ON and revolutionary doesn't seem to available for rezound yet...and I don't think I could flash clockwork quick enough since it freezes after like 10-15 seconds.
Any input? I'd really like to get this phone working...thanks!
Once you unlock you should install Amon Ra recovery with fastboot. The thread is http://forum.xda-developers.com/showthread.php?t=1339679
Well I flashed recovery via fastboot, and flashed CleanRom ICS (after loading the one zip file needed prior to flashing ICS Roms, and of course after backup and after wiping everything a few times) and its the same thing...gets into android and reboots after 10 seconds or so.
gdawson6 said:
Well I flashed recovery via fastboot, and flashed CleanRom ICS (after loading the one zip file needed prior to flashing ICS Roms, and of course after backup and after wiping everything a few times) and its the same thing...gets into android and reboots after 10 seconds or so.
Click to expand...
Click to collapse
Im having the same problem. I have tried several different roms at this point and my phone is still bootlooping..
Anyone got any ideas?? Im desperate to get this thing working!
Have you guys tried to manually install the kernel from fastboot?
phylo1 said:
Im having the same problem. I have tried several different roms at this point and my phone is still bootlooping..
Anyone got any ideas?? Im desperate to get this thing working!
Click to expand...
Click to collapse
Just boot to bootloader and run the ruu for 2.11 from windows or figureout how to get the ph98img.zip of gingerbread or one of the leaks onto the root of the sdcard and flash that in the bootloader. If not s-off you should still be able to lock the bootloader using adb.
The reboots should NOT be affecting the bootloader or flash a backup from recovery. Just start fresh.
Sent from my ADR6425LVW using Tapatalk 2
Run an RUU. EXE version is preferable.

1.06.00.1216 Reboot problems. Help?

So i had to take my phone in because my radio died and could not get cell reception. And of course they had to give me a hboot 1.50. So i used the downgrade trick and got it to 1.40 which of course security flagged the phone. No problem I flashed the 1.13.651.7 OTA/RUU exe and the phone booted up ran revolutionary on it and unlocked the bootloader flashed 1.04 and installed recovery. Everything was going swell. Updated the radio to 1216 and tried out a ICS ROM and phone would shut off some times when i hit the power to turn it on and it would reboot. tried a few ics roms got same results. so tried out some of the 2.08.651.2 roms and it still would reboot randomly. now im ticked. So i flash the 0.97.10.0808 no hboot it flashes more then just the radio but radio 2 and some other things and use the 2.08.651.2 steel rom and no more reboots. I was going on 8 hours with no reboots with 0808. so i figure maybe its fixed now so i put the 1216 radio back on and phones rebooting like clockwork every 20 mins or so. If i did not love this thing it would be bouncing off the walls right now. Of course ive not changed the rom back to a ICS one yet. but any ideas what the heck is going on?
Thanks in advance
Stealthee
Anybody with any idea on this ? There was one other thread started on this and no one answered or put in input on it either.
I had a similar issue with reboots after updating to that radio. I was only flashing the radio update. Freeza made a combo that updates a couple other bits and now I'm rock solid again. Here is the link to freeze'a thread:
http://forum.xda-developers.com/showthread.php?p=21374142
hope that helps if you're still having an issue.

New Global Ruu

Hi Xda people
Hey for people having troubles after running the latest global ruu.
1- Make sure to flash the ruu twice. After is done flashing and it says update complete just reboot to hboot and run the ruu again that way everything is truly wiped and everything is truly flashed/installed the way it is.
2- Make sure after you run the ruu twice make a factory reset from hboot BEFORE THE PHONE FIRST BOOT. after the 2 flashes if the phone reboots automatically just pull the battery and reboot to hboot and do a factory reset.
Doing this two steps will avoid a LOT OF TROUBLES.
Enjoy
Unfortunately I read this too late. I just did the RUU today after a borked mod on the last leaked ICS before the OTA came out. Anyway, ran the RUU and then when trying to unlock everything was fine, but after rebooting into Hboot, it still said locked, and then I had all sorts of trouble getting into the hboot itself. Trying to get amon ra on there again was a PIA. All is fine now and factory restore went ok. But man, what a PIA.

Lost Radio

I have a new HTC Evo LTE and HBOOT 1.15.000 Radio 1.05.11.0606and do not have S-OFF.
I installed Fresh 5.2.1 and had problems, when back and did a wipe including system and installed 5.2.1 again and it didn't work. After doing that I went back, wiped system again, and then restored the backup I previously made. Now the backup sometimes loads, sometimes doesn't, but even when it does I have no radio. I am going to try to install a stock rom through recovery or fresh 5.1.1 and HOPE I get radio back.
Any other suggestions of what I could do?
jeggen said:
I have a new HTC Evo LTE and HBOOT 1.15.000 Radio 1.05.11.0606and do not have S-OFF.
I installed Fresh 5.2.1 and had problems, when back and did a wipe including system and installed 5.2.1 again and it didn't work. After doing that I went back, wiped system again, and then restored the backup I previously made. Now the backup sometimes loads, sometimes doesn't, but even when it does I have no radio. I am going to try to install a stock rom through recovery or fresh 5.1.1 and HOPE I get radio back.
Any other suggestions of what I could do?
Click to expand...
Click to collapse
So now I'm just in a boot loop. I relocked, installed stock recovery and ran RUU. When I did that I booted just long enough that I could almost slide the ring to unlock before I rebooted. Then the device just constantly reboots.
I unlocked again, installed TWRP 2.2.2.0 in case there was a bug causing flashing issues. Recovery boots just fine now. I flashed Stock Rooted DeOdexed 1.22.651.3 from here since that was the version I had before this whole fiasco. I'm going to try to restore backup again but don't know how to get out of this horrible mess. Worse part about it is that it's my wife's phone! Help please!
You might need to run a different RUU. I'm not too experienced with that kind of issue though.
"We're coming from a pure power source"
metalfan78 said:
You might need to run a different RUU. I'm not too experienced with that kind of issue though.
"We're coming from a pure power source"
Click to expand...
Click to collapse
I reflashed stock recovery, relocked bootloader (fastboot oem lock), ran RUU (RUU_JEWEL_CL_ICS_40_Sprint_WWE_1.22.651.3_Radio_1. 05.11.0606_NV_SPCS_2.45_003_release_268323_signed. exe), and still had the boot loop problem. RUU said it completed but the bootloader still said "relocked". Isn't RUU supposed to totally wipe and restore the entire device?
I recall on my old EVO there was a zip you could place in the SDcard that the bootloader automatically looked for and would use to reflash to factory everything. Is there a way to do this with the EVO 4g LTE?
Is it possible that radios/firmware somehow got borked even though I am on S-ON? Is there a way to reflash them from bootloader?
Just thinking through ideas I'd try next and something that could possibly help recover or at least put me in a position to go back to Sprint for help.
Could have been a bad download. I think there is info on re locking in the development sticky section. It might give you some more information on what to do next.
"We're coming from a pure power source"
Just an update. Flashed again a stock ROM and installed the boot.img from stock using fastboot to be sure it was in place. (fastboot flash boot boot.img). That didn't work, still had boot loop where the phone loads enough to show the background and then restarts.
Used the PJ75IMG.zip file and attempted to install automatically in bootloader (from here) <-- Didn't install says "Main Version is older! Update Fail!
I then installed stock recovery and locked bootloader. Bootloader now shows "*** TAMPERED*** and *** RELOCKED***.
Ran RUU <-- Have a hard time doing anything since it doesn't boot up long enough to connect. Eventually RUU will fail with a connection error. I haven't been able to run RUU from HBOOT either and without the device stable long enough I'm not sure how to get RUU to run on the phone.
Still only boot far enough to see the background screen (wallpaper) and then reboot.
I'll gladly give $20 to anyone who offers a workable solution, paid either to you, or dev/charity of your choice if you don't want it.
This all started when I installed Fresh 5.2.1. Not sure if it was the fresh install or using TWRP to wipe data/cache and I also wiped system. Was that a mistake?
I just don't understand why I can't flash back even to stock. Since I'm relocked and never had S-OFF I don't understand how I was able to do something that can't be undone by flashing. I've flashed phones dozens of times so am comfortable with the process and just can't understand what went wrong and how to recover.
Is there an updated version of the PJ75IMG.zip file I could use?
Would it work to flash CM10 & the boot.img using fastboot?
jeggen said:
Just an update. Flashed again a stock ROM and installed the boot.img from stock using fastboot to be sure it was in place. (fastboot flash boot boot.img). That didn't work, still had boot loop where the phone loads enough to show the background and then restarts.
Used the PJ75IMG.zip file and attempted to install automatically in bootloader (from here) <-- Didn't install says "Main Version is older! Update Fail!
I then installed stock recovery and locked bootloader. Bootloader now shows "*** TAMPERED*** and *** RELOCKED***.
Ran RUU <-- Have a hard time doing anything since it doesn't boot up long enough to connect. Eventually RUU will fail with a connection error. I haven't been able to run RUU from HBOOT either and without the device stable long enough I'm not sure how to get RUU to run on the phone.
Still only boot far enough to see the background screen (wallpaper) and then reboot.
I'll gladly give $20 to anyone who offers a workable solution, paid either to you, or dev/charity of your choice if you don't want it.
This all started when I installed Fresh 5.2.1. Not sure if it was the fresh install or using TWRP to wipe data/cache and I also wiped system. Was that a mistake?
I just don't understand why I can't flash back even to stock. Since I'm relocked and never had S-OFF I don't understand how I was able to do something that can't be undone by flashing. I've flashed phones dozens of times so am comfortable with the process and just can't understand what went wrong and how to recover.
Is there an updated version of the PJ75IMG.zip file I could use?
Would it work to flash CM10 & the boot.img using fastboot?
Click to expand...
Click to collapse
I sent you a PM
Sent from my EVO using xda premium
I'm back up and running. With a kind and helpful tech we ran RUU again (twice) and still had boot loop. I was going to give up on it but we went into the default recover and cleared data and factory reset and it seems to be back to normal again and working fine.
Sent from my MB855 using Tapatalk 2
jeggen said:
I'm back up and running. With a kind and helpful tech we ran RUU again (twice) and still had boot loop. I was going to give up on it but we went into the default recover and cleared data and factory reset and it seems to be back to normal again and working fine.
Sent from my MB855 using Tapatalk 2
Click to expand...
Click to collapse
Awesome glad you got it fixed.
Sent from my EVO using xda premium

Bootlooping after going into recovery early

Edited: the phone I had was running with a non-OEM battery I switched the battery over to the extended OEM and the phone has not boot-looped since then.
I was trying to get rooted again on my rezound that is already s-off. I entered the stock recovery on accident and got the red triangle and after that my phone will boot normally and show the homescreen but it randomly restarts within 5- 10 minutes. This is before I accomplished root. I reset the phone after this and it seemed to stop the bootlooping.
Today I powered on the phone and its bootlooping all over again. This time it boots up normally but reboots anywhere from immediately to up to about 20 mins later. I didn't have any personal info or apps installed because I don't plan on using it until I install a custom rom. I went on to flash Amon-ra 3.15 with adb and installed the SuperSU.zip in AmonRA recovery. So I'm rooted right now. I had no bootlooping while in hboot or recovery. I want to backup my current setup so that I can return to a clean rooted stock if needed.
I've read that many people do a wipe with AmonRA and still have the bootlooping issue. I've been reading a ton of threads and I can't figure it out. Can anyone offer insight on what I did wrong/what happened and how I can fix it?
I'm currently S-off, rooted
Have AmonRa Recovery
SuperSU v0.96
Running software: 3.14.605.12 710RD
Kernel version: 3.0.16-gd0049f1
Baseband: 1.22.10.0421r, 1.22.10.0424r
I would just check through the basics. Did you wipe system, cache, dalvik, etc when you went from one rom to the other. I know when I don't delete the ph98img after I flash a rom and that file in bootloader I would get boot looping. Some one should chime in if this didn't help atleast it was bumped
Sent from my ADR6425LVW using xda app-developers app
queenshawtii said:
Edited: the phone I had was running with a non-OEM battery I switched the battery over to the extended OEM and the phone has not boot-looped since then.
I was trying to get rooted again on my rezound that is already s-off. I entered the stock recovery on accident and got the red triangle and after that my phone will boot normally and show the homescreen but it randomly restarts within 5- 10 minutes. This is before I accomplished root. I reset the phone after this and it seemed to stop the bootlooping.
Today I powered on the phone and its bootlooping all over again. This time it boots up normally but reboots anywhere from immediately to up to about 20 mins later. I didn't have any personal info or apps installed because I don't plan on using it until I install a custom rom. I went on to flash Amon-ra 3.15 with adb and installed the SuperSU.zip in AmonRA recovery. So I'm rooted right now. I had no bootlooping while in hboot or recovery. I want to backup my current setup so that I can return to a clean rooted stock if needed.
I've read that many people do a wipe with AmonRA and still have the bootlooping issue. I've been reading a ton of threads and I can't figure it out. Can anyone offer insight on what I did wrong/what happened and how I can fix it?
I'm currently S-off, rooted
Have AmonRa Recovery
SuperSU v0.96
Running software: 3.14.605.12 710RD
Kernel version: 3.0.16-gd0049f1
Baseband: 1.22.10.0421r, 1.22.10.0424r
Click to expand...
Click to collapse
I'd suggest running an ruu and do a full wipe while in that setup.. then try flashing to where you wanna be..
sent from my s-off reZound rockin' viperRez Rom on global ICS firmware
Thanks for the suggestions guys, I'm stock rooted right now, so i've haven't flashed a rom yet. Famouscollin, your saying that I should pretty much return to the stock ruu and re-root to see if that takes care of the problem?
Since I've changed the battery out, I've had no bootlooping.
Can you recommend a full image backup that I can use?
queenshawtii said:
Thanks for the suggestions guys, I'm stock rooted right now, so i've haven't flashed a rom yet. Famouscollin, your saying that I should pretty much return to the stock ruu and re-root to see if that takes care of the problem?
Since I've changed the battery out, I've had no bootlooping.
Can you recommend a full image backup that I can use?
Click to expand...
Click to collapse
yes that would be my first suggestion as where you could use th updated radios anyways.. itll prolly solve your issue as well..

Categories

Resources