Hey Folks,
I'm out of ideas / options and sort of beginning to think something hardware wise went on the device but figured I would give the crowd a shot and see if I'm missing something.
moonshine s-off
monarudo pvt ship s-off
hboot-1.33.4444
radio-1.01.04.0308
opendsp-v6.120.274.0114
emmc-boot
jan 15 2013
clockworkmod v6.0.4.5
8/31 I installed NuSenseSIX MAX Rc3.02_052014, the phone ran solid since then up until last night. No issues or anything major.
Last night, I put the phone on the end table to go to bed, battery over 90%, not on charger and it reboots. Thought it was odd so once it started I checked the alarms and junk, and it reboots again. The phone ends up rebooting after it has been fully booted into the OS after about 2 minutes, and it apparently did this all night because it was dead in the morning.
I tried to do a factor/reset restore within CWM but the phone just reboots. I wipe davlik, cache, system all process OK. Go to wipe /data, phone reboots. I tried to re-install the rom file, it goes through but does the reset after a couple of minutes. I figured I would try a different rom, did the wipe steps with the same results and attempted to install a new rom(liquid sense) that I downloaded, it boots but part of the old os are there, and it continues the restart loop regardless. I go through the wipe process once more and I try to sideload a stock rom, it doesn't even get to the OS and reboots on the loading screen. Tried a stock ASOP with a sideload, same results. manually wiping before each, never got to the OS, just reset on the loading screen. I went back to the original NuSense rom and it installed, but still resets randomly after a few minutes.
Anyone have an ideas? At this point I sort of feel as if something went hardware related, but not entirely sure. No water damage no major drops or anything. Phone just fritz-ed out.
I manually removed photos and junk with adb pull before this process just to get my data, so nothing on device is of any importance anymore.
Thanks again if anyone has any other ideas. PC = Windows 8.1
tep616 said:
Hey Folks,
I'm out of ideas / options and sort of beginning to think something hardware wise went on the device but figured I would give the crowd a shot and see if I'm missing something.
moonshine s-off
monarudo pvt ship s-off
hboot-1.33.4444
radio-1.01.04.0308
opendsp-v6.120.274.0114
emmc-boot
jan 15 2013
clockworkmod v6.0.4.5
8/31 I installed NuSenseSIX MAX Rc3.02_052014, the phone ran solid since then up until last night. No issues or anything major.
Last night, I put the phone on the end table to go to bed, battery over 90%, not on charger and it reboots. Thought it was odd so once it started I checked the alarms and junk, and it reboots again. The phone ends up rebooting after it has been fully booted into the OS after about 2 minutes, and it apparently did this all night because it was dead in the morning.
I tried to do a factor/reset restore within CWM but the phone just reboots. I wipe davlik, cache, system all process OK. Go to wipe /data, phone reboots. I tried to re-install the rom file, it goes through but does the reset after a couple of minutes. I figured I would try a different rom, did the wipe steps with the same results and attempted to install a new rom(liquid sense) that I downloaded, it boots but part of the old os are there, and it continues the restart loop regardless. I go through the wipe process once more and I try to sideload a stock rom, it doesn't even get to the OS and reboots on the loading screen. Tried a stock ASOP with a sideload, same results. manually wiping before each, never got to the OS, just reset on the loading screen. I went back to the original NuSense rom and it installed, but still resets randomly after a few minutes.
Anyone have an ideas? At this point I sort of feel as if something went hardware related, but not entirely sure. No water damage no major drops or anything. Phone just fritz-ed out.
I manually removed photos and junk with adb pull before this process just to get my data, so nothing on device is of any importance anymore.
Thanks again if anyone has any other ideas. PC = Windows 8.1
Click to expand...
Click to collapse
You can try the repair feature in twrp for /data. Go to wipe. Select advanced. Then put a check Mark in /data. Click repair repair filesystem near the bottom. Curious if your reported size is zero here ...
Change to to ext2. Repeat process and change back to ext4.
dottat said:
You can try the repair feature in twrp for /data. Go to wipe. Select advanced. Then put a check Mark in /data. Click repair repair filesystem near the bottom. Curious if your reported size is zero here ...
Change to to ext2. Repeat process and change back to ext4.
Click to expand...
Click to collapse
Thanks for the reply. In a last ditch effort, I reverted the phone back to full stock, no-root, s-on through one of the methods mentioned on xda. And it worked.
My best guess is that there some something corrupted within /data that was causing a bunch of crap to happen with the device.
Thanks again!
Related
I've been trying to root my wife's HTC Rhyme and in my efforts, something hosed the WiFi. All I get is "ERROR" under WiFi in the wireless network settings menu. This happened to me once or twice on my incredible and a kernel re-flash fixed it. I really want to root it so that she can have the benefit of being able to completely backup everything. I've tried ZergRush, TocoRoot, SuperTool, OneClick, SuperOneClick... none of it worked. The only thing that I've been able to do successfully is unlock/re-lock the bootloader.
Is it possible to extract the ROM and/or all critical system files from a stock rooted phone and use them to restore another phone that is malfunctioning? I was thinking that if I found someone with a rooted HTC Rhyme who would be willing, they could send me whatever files I would need to completely restore the phone, WiFi and all.
Any help with at least the WiFi issue wold be appreciated. Rooting would be nice too but I don't want to be greedy.
Thanks.
I was able to install an RUU which fixed the WiFi issue, but now the phone is stuck in a boot-loop. I've flashed it three times (doing it twice each attempt) but its the same result every time. The phone boots normally the first time, then goes into loop on the next restart. Could be the wrong RUU, could be corrupted or maybe I'm doing it wrong. I don't know.
Please... Any suggestions would be most appreciated.
I fixed it.
RuLEoF2 said:
I fixed it.
Click to expand...
Click to collapse
So have you finally rooted your Rhyme successfully? Which tool did you use? Thanks!
itandy said:
So have you finally rooted your Rhyme successfully? Which tool did you use? Thanks![/QUOTE No root, but it's working and back to No root, but it's working and back to factory condition. factory condition.
I used CWM recovery to format all partitions I used CWM recovery to format all partitions (data, system, cache, devlog, etc.) as well as (data, system, cache, devlog, etc.) as well as the sdcard. the sdcard. Once that was done, I relocked the Once that was done, I relocked the bootloader and ran the RUU. bootloader and ran the RUU. This time I went This time I went through the entire setup process for the phone through the entire setup process for the phone (activation, market account, WiFi and so on) (activation, market account, WiFi and so on) without rebooting first. without rebooting first. After the setup, I After the setup, I rebooted and I started normally. rebooted and I started normally. About 20 About 20 minutes later, I got an android OTA update of minutes later, I got an android OTA update of some kind and now its fine. some kind and now its fine.
Not sure why setting up the phone would make Not sure why setting up the phone would make a difference, but formatting the partitions and a difference, but formatting the partitions and going completely clean-slate is probably what going completely clean-slate is probably what did the trick. did the trick. Something must have been stuck Something must have been stuck in memory from the first failed attempt and it in memory from the first failed attempt and it was corrupting the following attempts in some was corrupting the following attempts in some way. way.
I'd still like to root it, but anyway... it's fixed and I'd still like to root it, but anyway... it's fixed and my wife's is glad to get her phone back. my wife's is glad to get her phone back. Happy Happy ending. ending.
Thanks to all for your assistance.
Click to expand...
Click to collapse
RuLEoF2 said:
itandy said:
So have you finally rooted your Rhyme successfully? Which tool did you use? Thanks![/QUOTE No root, but it's working and back to No root, but it's working and back to factory condition. factory condition.
I used CWM recovery to format all partitions I used CWM recovery to format all partitions (data, system, cache, devlog, etc.) as well as (data, system, cache, devlog, etc.) as well as the sdcard. the sdcard. Once that was done, I relocked the Once that was done, I relocked the bootloader and ran the RUU. bootloader and ran the RUU. This time I went This time I went through the entire setup process for the phone through the entire setup process for the phone (activation, market account, WiFi and so on) (activation, market account, WiFi and so on) without rebooting first. without rebooting first. After the setup, I After the setup, I rebooted and I started normally. rebooted and I started normally. About 20 About 20 minutes later, I got an android OTA update of minutes later, I got an android OTA update of some kind and now its fine. some kind and now its fine.
Not sure why setting up the phone would make Not sure why setting up the phone would make a difference, but formatting the partitions and a difference, but formatting the partitions and going completely clean-slate is probably what going completely clean-slate is probably what did the trick. did the trick. Something must have been stuck Something must have been stuck in memory from the first failed attempt and it in memory from the first failed attempt and it was corrupting the following attempts in some was corrupting the following attempts in some way. way.
I'd still like to root it, but anyway... it's fixed and I'd still like to root it, but anyway... it's fixed and my wife's is glad to get her phone back. my wife's is glad to get her phone back. Happy Happy ending. ending.
Thanks to all for your assistance.
Click to expand...
Click to collapse
How did you get the ruu to run i keep getting a error 140 wrong bootloader version i tried ruu 1.26.605.11 and 1.26.605.6 i attempted to flash a ics rom and the phone got stuck on the splash screen so then i used my backup i made before i flash the ics rom and wouldnt boot so i extracted the boot.img from the ruu and flashed it to get the phone back up and running the phone is still rooted but i have no wifi no bluetooth no cam i been searching everywhere for a rhyme kernel bt no luck if anyone could help that would great
Click to expand...
Click to collapse
Trying to install MeanBean...I updated the Firmware to the latest, have the phone unlocked and rooted (it says TAMPERED and UNLOCKED in the recovery screen) and did a factory reset. I have TWRP installed and can still get to the TEAMWIN RECOVERY project interface...
I was installing MeanBean and it just stuck on about 75% and stayed there. I waited for about ten minutes and figured something must have gone wrong so I didn't really have a choice but to shut it down. After starting back up when I tried to install again it said "FAILED" in red letters. I decided to re-download the ROM but now when I mount the SD CARD from within the recovery menu (to transfer the new file) my computer says that I must format the drive before I can use it and won't let me see the contents of the sd-card. I didn't want to do that for fear of bricking...so I don't really know what to do from here. I should add that I don't have a backup made in TWRP (I got the phone yesterday and hadn't installed or done anything to the OS)
Anyone know what should be done at this point?
thx
I'm updating this for anyone else who runs into issues like this: I went ahead and formatted the SD card from within windows, then relocked the phone, reinstalled the RUU and I'm back in a workable mode
itsmattgw said:
Trying to install MeanBean...I updated the Firmware to the latest, have the phone unlocked and rooted (it says TAMPERED and UNLOCKED in the recovery screen) and did a factory reset. I have TWRP installed and can still get to the TEAMWIN RECOVERY project interface...
I was installing MeanBean and it just stuck on about 75% and stayed there. I waited for about ten minutes and figured something must have gone wrong so I didn't really have a choice but to shut it down. After starting back up when I tried to install again it said "FAILED" in red letters. I decided to re-download the ROM but now when I mount the SD CARD from within the recovery menu (to transfer the new file) my computer says that I must format the drive before I can use it and won't let me see the contents of the sd-card. I didn't want to do that for fear of bricking...so I don't really know what to do from here. I should add that I don't have a backup made in TWRP (I got the phone yesterday and hadn't installed or done anything to the OS)
Anyone know what should be done at this point?
thx
Click to expand...
Click to collapse
I had the exact same problem. I just reformatted the internal storage and that fixed a lot of my issues. I can't however get the RUU to work. Can't seem to find my phone, neither can HTC Sync. Is this just a problem caused by MeanBean? I use to run MeanBean but then switched to CM10 for a few months and was going to switch back. Never had an issue like this before.
I could use some advice on any options I have for trying to salvage this Rezound. Here is what I know:
The Symptoms:
-Was completely stock and actively used phone
-Charging port began misbehaving. I believe it may be loose/damaged. It will only charge reliably on one particular USB cable (an Amazon Basics, but only one of my dozen or so of those)
-Started randomly rebooting
-Did a factory reset, seemed to help for a while, then it started rebooting again
-It started getting stuck in a bootloop. HTC screen up ~2s -> black ~0.2s -> HTC screen up ~28s -> black ~5s -> repeat. Does this for a variable amount of time, sometimes minutes, sometimes hours before it will actually boot all the way into the OS
-If it does boot, it usually does not last long before it reboots and will typically get stuck again
The Facts:
-I can into bootloader with no issues
-Because I can get into bootloader, I went ahead and unlocked and flashed TWRP 2.6.3.0
-I can get into TWRP and use all of it's functions reliably
-I decided to try wiping data and cache then system several times, flashing a custom ROM (Global_OTA_RED_DESENSED-v1.0) in TWRP and then flashed boot.img with fastboot, but the new ROM has the same issue. In fact I've yet to boot all the way into the ROM
-Does the same thing with the SD card and SIM card removed
My Guesses:
Based on the fact that it is rock solid in the bootloader and in recovery, I thought that it was possibly corruption on system or boot, which is why I tried to install a custom ROM. Now I'm leaning towards bad memory, either where system or boot reside, possibly data or even RAM, perhaps caused by electrical damage from the charge port issues. I just don't understand why I've not seen any sort of read/write errors while doing anything with fastboot or recovery.
At this point I don't know what to do beyond throwing it out. If anyone has any fresh ideas for salvaging this thing, I'd appreciate it.
If not, any ideas for replacing are also appreciated. A new phone isn't really in the budget at the moment, particularly because I desperately want to get away from Verizon (most likely will lose unlimited data if we I start swapping and don't really have $600-$700 to throw around at the moment. I have 4 lines to move and the Rezound line is on contract, so I'm sort of feeling the rock one side and a hard place on the other.
Thanks in advance, folks!
Because you are staying in ICS at the moment and not playing with JB/KK, try booting up Amon Ra recovery, it has an option to wipe/format the /boot partition (TWRP does not) so wipe that and everything else (except external SD) at lease twice... then, assuming you are on HBoot 2.28 and 0123/0124 radios, flash this and the boot image: http://forum.xda-developers.com/showthread.php?t=2260154 it is a completely stock build with full bloat, only root is added, and see if it comes up. This ROM is my go to ROM for issues when an RUU is not possible.
acejavelin said:
Because you are staying in ICS at the moment and not playing with JB/KK, try booting up Amon Ra recovery, it has an option to wipe/format the /boot partition (TWRP does not) so wipe that and everything else (except external SD) at lease twice... then, assuming you are on HBoot 2.28 and 0123/0124 radios, flash this and the boot image: http://forum.xda-developers.com/showthread.php?t=2260154 it is a completely stock build with full bloat, only root is added, and see if it comes up. This ROM is my go to ROM for issues when an RUU is not possible.
Click to expand...
Click to collapse
Thanks for the suggestion. I had let the phone sit turned off all afternoon to charge and tried this after work. I grabbed Amon Ra from http://forum.xda-developers.com/showthread.php?p=37362226, made sure to wipe boot in excess and installed the ROM you linked. It booted up on the first try unlike the last ROM, and I've been able to load some things on it and delete some bloat for a bit with no reboots. I've even powered off and went back into recovery to do a backup, and had a successful reboot afterwards. I don't know if it was wiping boot that did it, but I hope it holds. I'll keep you posted, and either way, thanks again.
Still going. Getting a random reboot here and there, but I've yet to have it get stuck while booting. Now I'm trying to decide if I want to take my chances and try to get S-off.
"Haus" said:
Still going. Getting a random reboot here and there, but I've yet to have it get stuck while booting. Now I'm trying to decide if I want to take my chances and try to get S-off.
Click to expand...
Click to collapse
Are you still on the stock ROM from above? You will need to unlock with Linux if you are, otherwise you will need a custom ROM (actually, an unsecure kernel) to use rumrunner for Windows.
acejavelin said:
Are you still on the stock ROM from above? You will need to unlock with Linux if you are, otherwise you will need a custom ROM (actually, an unsecure kernel) to use rumrunner for Windows.
Click to expand...
Click to collapse
I'm still on the stock ROM. Unfortunately it quit booting again.
"Haus" said:
I'm still on the stock ROM. Unfortunately it quit booting again.
Click to expand...
Click to collapse
Hmm... Honestly looking like a hardware issue... Sorry bro
Sent from my Nexus 4 using Tapatalk
I recently had an issue with my Note 2 when I went to flash (yet another) ROM. I tried to run the "Wipe Data/Factory reset" from within CWMR (Touch), and it would lock up/freeze during the format /data portion of the wipe. It would eventually just reboot itself back into recovery mode.
I eventually got to a point where I tried flashing a TW4.3 (rooted) stock ROM, but it was flaking out because obviously the data partition never did get properly wiped (lots of FC's, etc after it finished booting). I tried to do a factory wipe from WITHIN the booted OS. This took me a the android with the spinning blue "heart" and pseudo-progress bar. It then just stayed on this screen for 3-5 minutes and then rebooted back to the screen over and over.
I eventually gave up and ODIN'ed it back to the a stock, unrooted state (but I chose NOT to go to the latest 4.3 release so I could still possibly unlock again).
For some reason, the stock recovery doesn't have any issues formatting the /data partition now. I actually went back to stock thinking I might have to file a warranty claim on the phone (and I could right now, since it appears to be fully stock in all the various places you might look for tampering).
I am still concerned, however, that there is a corruption present in the /data partition and I would like to know if there is a way to test for it. Do I need to re-root just to test it?
spiff72 said:
I recently had an issue with my Note 2 when I went to flash (yet another) ROM. I tried to run the "Wipe Data/Factory reset" from within CWMR (Touch), and it would lock up/freeze during the format /data portion of the wipe. It would eventually just reboot itself back into recovery mode.
I eventually got to a point where I tried flashing a TW4.3 (rooted) stock ROM, but it was flaking out because obviously the data partition never did get properly wiped (lots of FC's, etc after it finished booting). I tried to do a factory wipe from WITHIN the booted OS. This took me a the android with the spinning blue "heart" and pseudo-progress bar. It then just stayed on this screen for 3-5 minutes and then rebooted back to the screen over and over.
I eventually gave up and ODIN'ed it back to the a stock, unrooted state (but I chose NOT to go to the latest 4.3 release so I could still possibly unlock again).
For some reason, the stock recovery doesn't have any issues formatting the /data partition now. I actually went back to stock thinking I might have to file a warranty claim on the phone (and I could right now, since it appears to be fully stock in all the various places you might look for tampering).
I am still concerned, however, that there is a corruption present in the /data partition and I would like to know if there is a way to test for it. Do I need to re-root just to test it?
Click to expand...
Click to collapse
I had this issue as well at one point, my phone actually soft bricked. What you need to do is use the pit file thru odin, flash any firmware in odin EXCEPT THE NEW OTA. Then you need to unlock again using the proper version of CASUAL for the base in which you relocked.
Sent from my Galaxy Note II
icedventimocha said:
I had this issue as well at one point, my phone actually soft bricked. What you need to do is use the pit file thru odin, flash any firmware in odin EXCEPT THE NEW OTA. Then you need to unlock again using the proper version of CASUAL for the base in which you relocked.
Sent from my Galaxy Note II
Click to expand...
Click to collapse
Thanks...
I actually went through the whole revert to stock with ODIN (but I used the PDA button/file). Was this the wrong approach? It sounds like I ended up at the same point as you...
And of course I couldn't leave it alone last night and unlocked and rooted with Casual last night. So far no issues with recovery data wipes.
I would like to understand what the problem was! Is it hardware, or a flash gone wrong?
Ok, I have 2 Rezounds. Rooted mine, went s-off and loaded Liquidsmooth and Gaaps. Everything works fine after 1 week.
Went and did second phone (wife's) and everything seemed to go well, but I had 1 thing occur in this phone that did not happen in my phone. When in HBoot, it would constantly update and then force a restart. I couldn't get into Recovery, and my phone would not be recognized as an ADB device. Googled around and think it was something related to the PH98IMG file, so I deleted that off of my SD Card and bingo it worked.
So I flashed AICP KitKat and its Gaaps. I thought all was well until my wife tried to call someone and the screen blacked out (call was being made) and then the camera launched. We could not unfreeze the screen, even holding Pwr button - had to pull the battery.
I assumed it was the ROM, so I loaded CarbonROM - same thing.
I reset to factory, wiped everything and retried, same thing.
I restored my factory backup latest OTA (ICS), and it worked fine. I reinstalled my Amon recovery file. Rest phone again, and reloaded. Same problem - my phone screen locks up on outgoing calls.
Help..........
One thing, I assume you can flash the ROM and Gaaps back to back with no reboot. I did this, but also wiped all data and reinstalled them separately with a reboot between. Same results.
one additional item
Not sure why, but no matter how I reset or wipe, my contacts always reload. I am not selecting Google backup when going through setup screen. I have reset and wiped all cache, dalvik cache, and all other.
briggss3 said:
Not sure why, but no matter how I reset or wipe, my contacts always reload. I am not selecting Google backup when going through setup screen. I have reset and wiped all cache, dalvik cache, and all other.
Click to expand...
Click to collapse
Google will always restore your contacts, even if you uncheck the backup/restore options, they are part of your Google account.
As far as your other issues, it kind of sounds like a proximity sensor issue, try installing https://play.google.com/store/apps/details?id=com.incredicontrol.ProxSensorCalibrator&hl=en and see if you can calibrate it... although this doesn't explain the camera issue, it does explain why the screen goes blank during a call and will not come back on.
I wonder also if my HBoot was corrupted. I don't know why, but when I booted into Bootloader, it would go through the motions of updating and then prompting me to restart (no other option). I read that this was because my Bootloader was finding a PH98IMG file on the SD card - is this an update exe? So I deleted it and Bootloader worked.
Also, both phones hung up (dots) on Rumrunner "Pouring 2" phase, and I had to break the connection during this step. Rebooting showed s-off, but I reran the exe file and it went through and completed "successfully."
Is there any need to update my recovery file, currently Amon RA which i did from Scotty's Newbie Guides? I downloaded 7.2.2.2 TWRP and tried to flash it in recovery, but it says fail. I can not find instructions on doing this for newbies - only the one that references s-on users, but it just glosses over.
I'll do the Play store download and see if that works.
Thanks for your help. I am totally a novice, although I have learned alot after going through this. I read alot on the Android Forums and XDA before I post.
AmonRa could be your whole problem actually... Get TWRP 2.7.1.1 and either flash it via Fastboot, use the PH98IMG way, or try Flashify as a last resort.
The chances that your Hboot is corrupted is slim, but you can download the firmware zip from 4.5.605.14 and reflash with no issues, it will not change S-Off or unlock state.
Updated TWRP and tried the resound calibrator, still same bad result. Phone will work on the OTA recovery file (ICS), but will not work on any kitkat ROM installs. When making calls, I can not power off or anything, total loss of phone while call is active (unless I pull battery). Once call is hung up, then I get control back of the screen.
I can't seem to find anything, should I go s-on then relock and unlock it again maybe? If you think that's a good idea worth trying, let me know and I'll search for instructions on how to do that.
More I think about it, its proximity sensor issues. I replaced the glass just before rooting. I downloaded the calibration app, but can't find instructions. I will play around with that a bit and see what happens. I'll post back if I can't get that to work, I may have replaced the adhesive too close to (or touching) the sensor in the ear piece.
briggss3 said:
More I think about it, its proximity sensor issues. I replaced the glass just before rooting. I downloaded the calibration app, but can't find instructions. I will play around with that a bit and see what happens. I'll post back if I can't get that to work, I may have replaced the adhesive too close to (or touching) the sensor in the ear piece.
Click to expand...
Click to collapse
You can find more info here: http://forum.xda-developers.com/showthread.php?t=1904974