Hey everyone, sorry if this has been asked before but at the moment my phone is completely stuck and I'm on the edge of sending it into HTC, just wanted to know if there's anything I've missed
For the past few weeks I've been running ARHD 30.0 perfectly fine until Saturday. I suddenly got lots of pop up errors like "the process com.android.media has stopped" and other similar errors for other apps. The phone would then crash and reboot, getting stuck at the "HTC One X" splash screen. I had Clockworkmod recovery and tried a nandroid backup and everything was fine for a bit but then the errors happened again and then bootloop. Same happened when I reflashed the boot.img and the ROM: fine for a day or so, then errors then bootloop.
I finally resorted to flashing the RUU. The process went fine and then suddenly the same thing started to happen: pop up errors and then stuck in bootloop. I'm able to get into fastboot but I don't know if it can be a software problem if it's doing the same thing even after flashing the RUU. Part of me is thinking it's a hardware issue: I remember some error warnings when I had clockworkmod recovery saying "E: is a read only system" or something similar, so I wonder if I need to send it in.
I'll be back in in a couple of hours and can get it and get more information, but off the top of my head S-ON was on before and after the situation. Thanks in advance.
Related
Had a friend bring over an Evo 4g with the infamous bootloop of death.
Specs:
Revolutionary
S-Off
HW: 003
Radio: 2.15.0808
HBoot 6.16
*Aftermarket Extended Battery*
First attempt at booting the phone, it would hit the lockscreen and reset. Then it stopped on the boot animation, and then it hit the splash screen after that reboot and it gave up. Trying to get to recovery at that stage resulted in freezing on the splash screen as well. Flashed the Amon-Ra recovery successfully and it would SOMETIMES go to it and then sometimes it would just freeze on the splash screen. Hmm... Tried CWM recovery with similar results. When I was in recovery, I did factory data and cache wipes as well, just to be on the safe side. No luck. Alright, so I figured let's reset everything and start over, maybe there was a bad flash of a rom or kernel. Flashed the hex-edited HBoot 6.17 and then the stock P36IMG.zip for the 4.54 version. Everything went smooth, no error messages, all OK. Now the phone is listed as S-On with the appropriate HBoot and Radio versions. Good deal...and bootloop issue continues. Argh! Figured, I should try running the RUU from the PC just for heck of it. I tried both the 4.54 and 4.67 versions and both provided Error 120 saying the battery was not 30% or more. Odd, since the battery was charged fully according to the charging light, and from the brief times it did hit the lockscreen the battery looked fine. So I took a break from it. I came back to it the next day and thought I would try and, it booted to the lockscreen, and bootloop. Hmm. Seems it only likes to boot when cool or not having messed with it for awhile. Interesting. Let it set for a bit then put it on a fan and tried to boot to recovery...and it was the first time it had went to recovery in awhile. Hmmm. Took the phone and put it in a tupperware and put it in the freezer for like 10-15 minutes and tried to boot again. Booted all the way just like normal! Weird. Running like a champ. Played around with it for a few minutes, then just let it sit for awhile. No reboots at all. Rebooted the phone manually, but there comes the bootloop. So, threw it back in the freezer and tried it again after a bit and now the phone has been on for over 5 hours. Haven't played with it much, but before it just wouldn't even load, but now, obviously the temp has risen to normal levels and no restarts. I'm completely baffled. Would this be an issue with the battery since it is an aftermarket one (don't have a stock one to test unfortunately) since I know it can cause random issues and RUU didn't like it or...some strange hardware malfunction? Previously thought it might be an issue with the NV partition from the MetroPCS flash but since it is up and running OK now, I would think that would not be the case. Any thoughts?
Friends evo just started doing this today - he didn't make any changes or do anything to the phone to cause this. It just keeps cycling through the sprint splash screen/start up sound over and over.
its not rooted/unlocked - it's stock from sprint
If i try going into recovery, i get the black and white htc evo screen. And then I get an icon of a green arrow with green arrows circling around it and after a few seconds i get a red triangle with an exclamation mark in it, which i assume is a bad thing.
Is there anything I can do to try and fix this?
and again - stock, not rooted/not unlocked - running whatever rom is current with sprint.
thanks
Same here except sometimes times it loads up into android but after a few minutes it starts rebooting again. I rooted the phone to see if that would fix it but still stuck in boot loop with it occassionaly loading into android.
cellington77 said:
Same here except sometimes times it loads up into android but after a few minutes it starts rebooting again. I rooted the phone to see if that would fix it but still stuck in boot loop with it occassionaly loading into android.
Click to expand...
Click to collapse
I just fixed my friends phone by doing the following:
downloaded this RUU RUU_SuperSonic_GB_Sprint_WWE_4.67.651.3_Radio_2.15.00.12.19_NV_2.33_release_234563_signed.exe
download htc sync
installed htc sync
uninstalled htc sync (keep the drivers).
press the power btn and the volume down button until you get into hboot - wait a few seconds for it to fully boot. Select fastboot. Plug your phone into your pc. Run the RUU - wait a few minutes for it to do it's thing and phone is working now.
not sure how this will work for you if your phone is rooted, as this was done on an unrooted phone.
Infinite boot loop
Stock Evo Infinite Boot Loop
I have been trying to fix my daughter's evo 4g from Sprint. Its at least 2 years old. She no longer uses it because it went into infinite boot loop. Itws not hooked up and is in no warranty.
I have done the hard factory reset. There is no issue with saqving anything on the phone. I have tried everything I could find so far in the forums. I may have missed some things. idk.
Ive wiped cache.
This is what I got in the info on the phone.
supersonic EVT2 Ship s-on
H-2.16.0001
MICROP 841F
TOUCHPANEL-ATMEL224_16ab
RADIO-2.15.00.05.02
MAR 82011.17.02:15
I tried using the ruu..
RUU_SuperSonic_GB_Sprint_WWE_4.67.651.3_Radio_2.15 .00.12.19_NV_2.33_release_234563_signed.exe
MD5 Sum: 045e93a459183b144d29f18fc2a332fa
Still stuck in boot loop. But now it says in pink above supersonic...Locked..oow
Before when I was using recovery I got these messages..
CANT OPEN CACHE/RECOVER/COMMAND
WIPING DATE
CANT OPEN /DATA/CWPHG.ZIP
CANT OPEN /DATA/CWPROP
CANT OPEN CACHE//CWPKG
CANT OPEN cache/cw.prop
formatting cache
data wipe complete
This is completely stock. Never been rooted or changed in any way.
This is my daughter's exact message about problems she was having:
"it seems to me that it gets overheated sometimes. like it seems the battery is getting too hot. i dunno john had the problem with his evo one time but he took it and had sprint reset it which is pretty much the same thing you do yourself i think. his was fixed but mine wasnt.i didnt get sprint to reset it for me. i never dropped it or anything i dont know. i hope you can get it fixed though. i liked the phone when it was working good. it seems like it can go for awhile sometimes without rebooting and i could talk on it but as soon as i would hang up it would go into loop again.it was hot.i even tried making the screen darker so maybe it wouldnt get so hot."
Sorry not to be briefer. Please..anyone with suggestions?
Thanks
Possibly use odin to flash the stock image?
redheadstranger said:
Stock Evo Infinite Boot Loop
I have been trying to fix my daughter's evo 4g from Sprint. Its at least 2 years old. She no longer uses it because it went into infinite boot loop. Itws not hooked up and is in no warranty.
I have done the hard factory reset. There is no issue with saqving anything on the phone. I have tried everything I could find so far in the forums. I may have missed some things. idk.
Ive wiped cache.
This is what I got in the info on the phone.
supersonic EVT2 Ship s-on
H-2.16.0001
MICROP 841F
TOUCHPANEL-ATMEL224_16ab
RADIO-2.15.00.05.02
MAR 82011.17.02:15
I tried using the ruu..
RUU_SuperSonic_GB_Sprint_WWE_4.67.651.3_Radio_2.15 .00.12.19_NV_2.33_release_234563_signed.exe
MD5 Sum: 045e93a459183b144d29f18fc2a332fa
Still stuck in boot loop. But now it says in pink above supersonic...Locked..oow
Before when I was using recovery I got these messages..
CANT OPEN CACHE/RECOVER/COMMAND
WIPING DATE
CANT OPEN /DATA/CWPHG.ZIP
CANT OPEN /DATA/CWPROP
CANT OPEN CACHE//CWPKG
CANT OPEN cache/cw.prop
formatting cache
data wipe complete
This is completely stock. Never been rooted or changed in any way.
This is my daughter's exact message about problems she was having:
"it seems to me that it gets overheated sometimes. like it seems the battery is getting too hot. i dunno john had the problem with his evo one time but he took it and had sprint reset it which is pretty much the same thing you do yourself i think. his was fixed but mine wasnt.i didnt get sprint to reset it for me. i never dropped it or anything i dont know. i hope you can get it fixed though. i liked the phone when it was working good. it seems like it can go for awhile sometimes without rebooting and i could talk on it but as soon as i would hang up it would go into loop again.it was hot.i even tried making the screen darker so maybe it wouldnt get so hot."
Sorry not to be briefer. Please..anyone with suggestions?
Thanks
Click to expand...
Click to collapse
Been awhile since i did this. But search "revolutionary s-off". Do this to gain s-off. Download and flash "smelkus recovery" (find directions in post, search xda). Then try wiping everything and installing a room.
Might work, might not... but if not, that's a stylish paper weight
Riding the Uni on the GSIII
Good evening everyone,
I've been scanning the forums and everyone's problems seems a little different. First of all, i was running CM10 and missed some of the sense features, so i jumped to ViperX.
1. Everything seemed fine on first run, got the snakey tail, but then i noticed it was hanging just after this with the "Htc quietly brilliant" screen and snakey long gone!
2. So i reboot my phone, this time, it just hung on the first start screen and never so much as flinched.
3. I booted into recovery (CWM) and couldn't even get there, it was like a blink of the recovery screen and then it vanished and rebooted, I wiped everything clean by doing a factory reset and tried to reboot again. Same result.
4, Flashed TWRP and managed to get into recovery mode and install ViperX again but on reboot I'm stick at that same ol' "quietly brilliant" screen, this time with no snakey.
I can get into hboot to use fastboot and into recovery in TWRP but cannot get into the OS. I'm not clear as to whether this is a problem with hboot or the way the rom is installed but any suggestions or such about how i've gone about things and how to go about getting around this problem would be great! Gracias! :good:
Did you flash the correct boot.img?
BenPope said:
Did you flash the correct boot.img?
Click to expand...
Click to collapse
Strangely, and by the luck of trial and error, I tried 2 boot images. The first was for CM10 (again, this was trial and error) and now i've just rebooted from the ViperX one and managed to get back in. Back up in progress! Phewww!!!!
You get my thanks for replying anyhow!
My HTC One X was fine, running BladeX ROM for about a month, when it suddenly started telling me that some processes had unexpectedly stopped. "android.process.acore" and "com.process.htcdialer" are what was popping up the most however you could not run any app without it crashing.
I tried to fix this by flashing the latest version of BladeX, I did a full wipe as well as erasing the cache\dalvic multiple times. This did not fix the problem and now the phone would sometimes refuse to boot, sometimes it would get stuck at the HTC boot screen, sometimes it would boot but was unusable due to the errors i mentioned earlier and sometimes it would just switch between the HTC boot screen and the BladeX boot screen. I thought that this could have been a problem with the battery being too low so I booted into recovery and then rebooted back into recovery from the power menu, this seemed to allow the phone to charge.
Now when the phone would boot into the Rom the battery was at 87% but the errors were still there. Now when i tried to flash a different boot.img ( for IceColdJelly) it failed giving the error code 0x30000 and when i tried to erase the cache it gave the error code 0x1900008.
I have no idea what to do now so any help would be greatly appreciated
Thanks in advance
1) I think was better ask in Blade rom for the problem.
2) You have to flash the boot.img of Blade rom or a repacked kernel for this rom, it's normal that your device won't boot.
3) Fastboot recognizes your hox?
Hi everyone,
Being the more adventurous kind of person I am, and also rather sick of LG's android overlay, I decided to finally try rooting and installing a custom ROM, as my previous device was the Nexus 5, and I longed to return to the stock android world. It is a first for me to try this, so I read a few forum posts about it, and finally I rooted my G3 (D855 model), which went flawlessly. I then installed cyanogenmod 12 (I cannot remember which version, it was the most recent at the time) and I was finally satisfied by the software, which was as smooth as butter, unlike LGs skin. After a few months, I made the terrible mistake of installing one of the updates that where suggested, and then the problems began. While the phone was performing the update, it froze on the "optimizing apps" screen, and stayed so for several hours, until I decided to pull the plug on it, and it slowly died of a flat battery. I then tried to reboot the device, which stayed on the LG logo screen for a long time, until I again had to leave it to die. I then rebooted into TWRP recovery, which was the recovery I had installed and used to install CM12, and I tried to recover from the last backup I had performed a week prior about, and it failed with "error executing binary in script". After some googling, I found a forum where someone recommended to wipe the cache, data, system, and dalvik partitions. Having done this , the backup was successful and the phone was up again. A few days later I saw that CM13 with android M was released for the G3, and I decided to try it. I downloaded the rom, backed up my old version again and flashed it with TWRP. It worked, and the device booted into CM13, but I was greeted with a "process has crashed" message. I dismissed it, and the OS seemed to work, but then I realised it failed to recognize my SD card, and the phone internal memory (I own the 32GB model) was listed at a mighty 2gb. I decided to return to CM12 for the moment, so I rebooted into recovery, flashed the backup and got the same "error executing binary in script". I then wiped the cache, data, system, and dalvik partitions, and flashed my backup with no error. The phone reeboted, showed the LG screen, and then went black, then the LG screen, then black, etc... I quickly discovered this to be a boot loop. After some attempts to fix this, the phone booted to the LG screen, then the Cm logo pulsing, and then the "optimising apps". At the end of the process, the lock screen appeared, and after unlocking the device, I discovered it was back in CM13. This was suprising, and the errors I previously had were still here, so I returned to TWRP and tried to flash the original CM12 file I had, and this showed no error. After booting the device, CM13 greeted me again. I decided the device was seemingly possessed, and made the decision to unroot and reinstall into factory settings. But the first step of this process was out of reach, as the phone goes no further then the "download mode" screen with the small blue dots in the middle when I hold the volume down and plug it into the PC. After an hour on said screen, I pulled the plug and tried to reboot again. CM13 appeared once again, as if it was haunting my dreams, and I also found out that TWRP is no longer accessible, as the device stays on the blue loading screen of TWRP.
I have searched and not found anything saying how to get any further then this. I know that as I am not very experienced with this, it was rather foolish to act as I did, so spare me the lectures about that. But I didn't learn to ride a bike without falling off it, so it's kind of the same isn't it? Anyhow, is there someone out there who may assist me?
Many thanks to anyone who has any advice, I'm sick of my backup samsung S3 D:
Ed