My DX (running Liberty) won't go past the reboot screen, it has been sitting there for at least 15 min. Any ideas on what to do?
NVM...just re-flashed the ROM and got it running again
What have you done to the phone? Rooted, Stock, Roms etc etc, also define reboot screen. Is it the boot animation, or just the M. We will gladly help you out, but you need to be more specific with your problems
Well, glad to hear you got it working again!
Sorry for the vagueness. The screen I was referring to was the screen it goes to right after you reboot out of clockwork; all it said was "Liberty," (so yes, I'm rooted). But yeah, it's running fine now; I tried to download a theme off of a forum and I think it messed with my phone.
Alright, this issue has seriously driven me insane over the last few days, and today it's gotten to the point where I'm going to do something I'll regret if somebody can't help me out. As you can tell, I'm pretty desperate.
Using Fresh 3.5.0.1, I've encountered more reboots than I can count. Whether it's checking an email or playing Asphalt, the phone frequently decides it doesn't want to cooperate and restarts itself. I decided to try to get rid of the reboots for good today with a complete wipe and new rom.
First, I made a nandroid backup, followed by a data/system wipe and cache/dalvik cache wipe. Afterward, I flashed the ZenDroid 1.1.0 kernel in case that was the issue. I then proceeded to flash CyanogenMod 7 RC1 with gapps.
That worked for all of three minutes, and then it got even worse. The phone started restarted itself when I wasn't even doing anything, up to the point where it would restart on the CM7 boot animation. I took my rage out on a nearby pillow and decided to try something else.
I downloaded the final release MIUI rom and used Calkulin's format all to wipe my phone as instructed. This time around I flashed Savage-Kernel 1.6 along with MIUI. Lo and behold, after rebooting I was finally able to swipe through the home screens again.
And then I wasn't. It started rebooting on the boot animation again. At the moment it's even worse, rebooting three seconds into the damned splash screen. I've tried keeping the battery pulled for half an hour with the HTC battery and two after market batteries. I wiped the ext partition on the micro sd card. I even physically removed the card itself. This effing phone is still rebooting on the splash screen.
I'm at the end of my wits. All I want is for my Evo to WORK, without any constant reboots or force closes that make it utterly unusable outside. If anyone could help me out with this issue, I'd be extraordinarily grateful.
Mecha2142 said:
Alright, this issue has seriously driven me insane over the last few days, and today it's gotten to the point where I'm going to do something I'll regret if somebody can't help me out. As you can tell, I'm pretty desperate.
Using Fresh 3.5.0.1, I've encountered more reboots than I can count. Whether it's checking an email or playing Asphalt, the phone frequently decides it doesn't want to cooperate and restarts itself. I decided to try to get rid of the reboots for good today with a complete wipe and new rom.
First, I made a nandroid backup, followed by a data/system wipe and cache/dalvik cache wipe. Afterward, I flashed the ZenDroid 1.1.0 kernel in case that was the issue. I then proceeded to flash CyanogenMod 7 RC1 with gapps.
That worked for all of three minutes, and then it got even worse. The phone started restarted itself when I wasn't even doing anything, up to the point where it would restart on the CM7 boot animation. I took my rage out on a nearby pillow and decided to try something else.
I downloaded the final release MIUI rom and used Calkulin's format all to wipe my phone as instructed. This time around I flashed Savage-Kernel 1.6 along with MIUI. Lo and behold, after rebooting I was finally able to swipe through the home screens again.
And then I wasn't. It started rebooting on the boot animation again. At the moment it's even worse, rebooting three seconds into the damned splash screen. I've tried keeping the battery pulled for half an hour with the HTC battery and two after market batteries. I wiped the ext partition on the micro sd card. I even physically removed the card itself. This effing phone is still rebooting on the splash screen.
I'm at the end of my wits. All I want is for my Evo to WORK, without any constant reboots or force closes that make it utterly unusable outside. If anyone could help me out with this issue, I'd be extraordinarily grateful.
Click to expand...
Click to collapse
hmm...
i don't know what kernel fresh comes with, but both of the other kernels are more aggressive ones, and i would guess your phone doesn't like them. i would try this:
Wipe twice using calk, wipe again using recovery, flash mikfroyo or stock rooted (stock kernel). If you still get reboots... unroot and take your phone back in because its a hardware problem.
I had this problem. Drove me insane. Ultimately just unrooted and got a new one from sprint. Not one reboot since I got the new one.
Sent from my PC36100 using XDA App
Well I'm still super new to the whole flashing of the ROM's. But from what you have explained the only thing I can think of is that you missed a step when you rooted your phone. Because of this that is why your phone keeps brick. You should go and check out HTC EVO Hacks (go Google it) and the guy who runs the site made a sweet video & write-up on how to root your phone. Just re-do everything and follow directions, then when your done just flash Kings Unleashed. And when you check out the HTC EVO hacks root page look for the link to the XDA root forum which has more info on how to root your HTC the proper way.
Sent from my PC36100 using XDA App
aimbdd said:
hmm...
Wipe twice using calk, wipe again using recovery, flash mikfroyo or stock rooted (stock kernel). If you still get reboots... unroot and take your phone back in because its a hardware problem.
Click to expand...
Click to collapse
Yeah, I guess I should try the stock rooted rom. If I'm only able to use that instead of any other custom rom, though, I'm going to lose it. There's something inherently frustrating about a device refusing to work for no apparent reason.
chickut123 said:
I had this problem. Drove me insane. Ultimately just unrooted and got a new one from sprint. Not one reboot since I got the new one.
Click to expand...
Click to collapse
I'm sort of hoping I won't have to do that, considering I'll likely get a refurbished unit.
Fredrow425 said:
But from what you have explained the only thing I can think of is that you missed a step when you rooted your phone. Because of this that is why your phone keeps brick. You should go and check out HTC EVO Hacks (go Google it) and the guy who runs the site made a sweet video & write-up on how to root your phone. Just re-do everything and follow directions, then when your done just flash Kings Unleashed. And when you check out the HTC EVO hacks root page look for the link to the XDA root forum which has more info on how to root your HTC the proper way.
Click to expand...
Click to collapse
I'm pretty sure that isn't the case at all. If there was an issue with the way I rooted my phone, it would have been present eight months ago when I bought it. This rebooting issue is relatively new, and it isn't bricked. I appreciate the advice, though.
It could be just a defective phone - memory isn't immortal or impervious to defects.
I'd downgrade to a Sprint ROM, and keep it stock and see how that works. You have to rule out bad hardware first, and that's the only way to do it.
I agree on all of your guys suggestions but one thing i noticed was that he said he wiped data then dalvic cache then he said he flashed the kernel then the rom. Maybe he should try and rewipe everything with calk format all then flash the rom and reboot. Then go back into recovery and flash your new kernel then reboot again and see whats up from there.
Have you tried repartitioning your SD card and formatting? I was getting random reboots on every single rom I tried, and every single kernel. Turns out my partitions somehow got messed up on my SD card and that was causing it randomly. Now I have no reboots.
akrod2as said:
Have you tried repartitioning your SD card and formatting? I was getting random reboots on every single rom I tried, and every single kernel. Turns out my partitions somehow got messed up on my SD card and that was causing it randomly. Now I have no reboots.
Click to expand...
Click to collapse
Yes, I first formatted the sd card in Windows and then partitioning it on the phone's recovery. Still no luck.
Yeah... Sprint rom or if you go through with the unrooting process (I forgot how...) then you can figure out if it is hardware.
But yeah, endless reboots are frustrating.
If Sprint rom is giving you troubles, then just return it and get a new one. It's gotta be hardware then.
Also you could try running stock rooted without any downloaded market apps. Just run what came with the phone.
You can also try stock rooted eclair 2.1
Mine started the reboot bs after the december update. Mine seems to reboot when I use it heavily even though I'm not overclocked (heats up). Before the 2.2 update, it was very fussy being outside during the summer. I would like to exchange mine for another, even though I don't use it anymore. It would be nice to have a fully functioning backup. My gf's daughter wants the evo very much. Even if I would do that, which I wouldn't, I wouldn't let someone use a possibly unstable phone. If an emergency happened, and the phone started it's rebooting bs, it would be very bad to not be able to use the phone when you need it the most.
I am guessing I would have to reactivate the evo, run it for a month or so, unroot and lock it, then take it to a service center and see if I can make it start rebooting like crazy. Maybe I will get lucky and they would give me another one. I don't care too much if it is a refurb as long as it is in good shape and works good.
Try removing the SD card and booting.
Sent from my PC36100 using XDA App
rebooting
I had this same problem with my evo. Sometimes it would be ok, but then others it wouldnt stop doing it, didnt matter what I did. It could be sitting by itself and I would hear it rebooting. Drove me mad!!!
My first evo was awesome, it was a hardware ver 3. My camera lens cracked and the gave me a refurb, hardware version 2. This is when my reboots started happening.
After 3 batteries from Sprint and two more refurbs I finally blew in front of a store full of customers telling them that either give me a NEW evo, hardware version 3 like I originally had with no problems or it was going against their wall.
I havent had one problem since.
I wasnt rooted yet so cant comment along those lines but if you take it back to stock and it still does it I recommend throwing it at one of Sprints walls. No need to do any drywall patching at your place LOL.
I hope you get it resolved as I can feel your pain!
It may not be hardware. Did you restore any apps using any back up app (Titanium Backup) after flashing the AOSP roms? If so, make sure you did NOT restore any system apps or data. This is especially important when you go from Sense to AOSP.
The test is what everyone is suggesting. Flash back to Sprint rom and see what happens.
Also, you need to flash the kernel after flashing the rom, otherwise you'll just get the kernel packaged with the rom. I usually reboot and art least try the default kernel unless I know that my phone hates it.
bigmoogle said:
It may not be hardware. Did you restore any apps using any back up app (Titanium Backup) after flashing the AOSP roms? If so, make sure you did NOT restore any system apps or data. This is especially important when you go from Sense to AOSP.
The test is what everyone is suggesting. Flash back to Sprint rom and see what happens.
Also, you need to flash the kernel after flashing the rom, otherwise you'll just get the kernel packaged with the rom. I usually reboot and art least try the default kernel unless I know that my phone hates it.
Click to expand...
Click to collapse
No, I haven't even been able to get to the stage of installing any apps before the rebooting cycle starts again. I tried installing the stock Sprint rom this morning with the stock radios and kernel and it was stable for about five minutes. It's back to rebooting again, though.
Do you guys think it's time to unroot and go to the Sprint store for an exchange?
Mecha2142 said:
No, I haven't even been able to get to the stage of installing any apps before the rebooting cycle starts again. I tried installing the stock Sprint rom this morning with the stock radios and kernel and it was stable for about five minutes. It's back to rebooting again, though.
Do you guys think it's time to unroot and go to the Sprint store for an exchange?
Click to expand...
Click to collapse
If it was me, I would take it back. I just downloaded the newest ruu and will flash it later tonight. The only thing I'm worrying about is they won't be able to reproduce the problem. I really have to be multitasking a lot and pushing the phone hard. Actually the last time it had rebooting fits was with wireless tether running. The back of the phone was warm. I put it in front of the ac vent in the car for a minute or two and that seemed to help it stop rebooting.
herbthehammer said:
If it was me, I would take it back. I just downloaded the newest ruu and will flash it later tonight. The only thing I'm worrying about is they won't be able to reproduce the problem. I really have to be multitasking a lot and pushing the phone hard. Actually the last time it had rebooting fits was with wireless tether running. The back of the phone was warm. I put it in front of the ac vent in the car for a minute or two and that seemed to help it stop rebooting.
Click to expand...
Click to collapse
Well, it looks like I'll be taking it to the store after all. I just finished unrooting my phone with the RUU, so it's as if I had never touched the software. Lo and behold, the damned thing still rebooted a minute into using the phone.
I guess that in some sick way, I can consider myself more 'fortunate' than you, seeing as how my phone doesn't even need to be used in order to begin rebooting. It's ridiculous that I have to part with my Evo because of this bs.
Mecha2142 said:
Well, it looks like I'll be taking it to the store after all. I just finished unrooting my phone with the RUU, so it's as if I had never touched the software. Lo and behold, the damned thing still rebooted a minute into using the phone.
I guess that in some sick way, I can consider myself more 'fortunate' than you, seeing as how my phone doesn't even need to be used in order to begin rebooting. It's ridiculous that I have to part with my Evo because of this bs.
Click to expand...
Click to collapse
Did you even try removing the sd card and booting the phone?
Same thing happend with my old evo it started after i install one of the first cm safe roms not nightlies not saying tyat was the cause, i tried evverything wiping unrooting botting without sd, ive been on android sice g1 and i tried everything nothing worked, ended up going to sprint and getting another refurnished it was prolly hardware issue maybe cpu overheating or something, anyways not sure why ppl are so scared of refurnished phones i believe they do a lot more tests on those phone than retail ones lol
akrod2as said:
Did you even try removing the sd card and booting the phone?
Click to expand...
Click to collapse
Yes. I've already said I tried booting the phone without the sd card several times now without success.
Hopefully this is the right place. Ive searched and not quite found exactly my situation, so if there are similar threads, I apologize..
So I have CyanogenMod 6.1.2 on my Evo, with MattedBlues skinned over it.
Last night it rebooted randomly in the middle of me writing a text and went into bootlooping from the HTC EVO 4G splash. I cannot get into recovery and Ive tried running the stock RUU .exe (as I did last time I bricked my phone) and I get error 170 over and over (from HBOOT USB and FastBOOT USB menus).
What can I do? I dont have the cash right now to pay the deductible for a new phone and I *must* have a phone.
I rooted using Unrevoked 3, but I believe my recovery image is damaged, and my HBoot is 0.97.00 when Ive read I need 0.76.
How can I fix my phone?
If I can get adb to recognize my phone, can I just push/flash a new recovery using adb since I cant get into recovery through the phone?
Shaihalud9 said:
Hopefully this is the right place. Ive searched and not quite found exactly my situation, so if there are similar threads, I apologize..
So I have CyanogenMod 6.1.2 on my Evo, with MattedBlues skinned over it.
Last night it rebooted randomly in the middle of me writing a text and went into bootlooping from the HTC EVO 4G splash. I cannot get into recovery and Ive tried running the stock RUU .exe (as I did last time I bricked my phone) and I get error 170 over and over (from HBOOT USB and FastBOOT USB menus).
What can I do? I dont have the cash right now to pay the deductible for a new phone and I *must* have a phone.
I rooted using Unrevoked 3, but I believe my recovery image is damaged, and my HBoot is 0.97.00 when Ive read I need 0.76.
How can I fix my phone?
If I can get adb to recognize my phone, can I just push/flash a new recovery using adb since I cant get into recovery through the phone?
Click to expand...
Click to collapse
Should have posted this in the q&a but try THIS post and we'll go from there.
I should have, but thanks, I will try that.
Shaihalud9 said:
I should have, but thanks, I will try that.
Click to expand...
Click to collapse
If your having issues running the ruu and the error your not completely out of luck. I have unrooted several times that way. I would recommend try rebooting your computer first off. After that before you run the ruin reboot the bootloader a couple Times, in fastboot you'll see the reboot option. This has always solved the issue for me, may take a few times but its still worth a shot.
Sent from my PC36100 using XDA App
Yellowcard8992 said:
If your having issues running the ruu and the error your not completely out of luck. I have unrooted several times that way. I would recommend try rebooting your computer first off. After that before you run the ruin reboot the bootloader a couple Times, in fastboot you'll see the reboot option. This has always solved the issue for me, may take a few times but its still worth a shot.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Rebooting the bootloader doesnt help, still getting Error 170, so hopefully flashing a new recovery from HBoot will.
Okay so copying the PC36IMG to my SDcard, the bootloader recognizes it, and reads it, and I get a progress bar on the right.... but no option to flash the image, and booting into recovery does nothing.
Im going to try an HBoot run of the PCIMG36 RUUs I found on another page... I dont mind going back to stock, I just want the damn phone to work.
Double post.
So I used the latest PC36IMG Signed zip from here: http://forum.xda-developers.com/showthread.php?t=884060&highlight=hboot-0.97+ruu&page=7, and it went through, did all the updates, but when asked to reboot, which I did, I get a blinking yellow LED that goes solid, boots up, get the EVO 4G white splah for a few moments... then nothing.
Im hoping its just a dead battery. =\ Gonna try it again in a bit.
Nope. Still getting bootloops, even with the new PCIMG flashed. What the f*cking hell.
OK heres the deal. I have done tons of searching and it looks like I SHOULD be able to get out of this, but I cant figure it out and I may have gone to far(by unrooting with 4.24 and bootloader 2.16).
So long story short, my launch day evo got lost about a month after I got it. Got a replacement from Sprint(or whoever their insurance is), my original Evo got found about a month or so after that. It has not been powered on since then(a year realistically) with no battery or SD card in it. I got bored and decided to power it up and update everything(because I cant do **** with my new Evo3d, yet since im on a Mac and have no access to a PC). Here are where things went bad.
Phone was rooted with the very original Toast method including S-off with the .76 Eng boot loader. I was running some form of CM6 on it when I lost it.
-Went to power it up and it boot looped at the white Evo4g screen.
-Went into bootloader and tried to get into recovery(had Amon RA 1.7 I think). No go.
-Flashed the new TWRP recovery and got into recovery just fine.
-Flashed the CM7.1.0-RC1
-reboot into a boot loop
-battery pull and a reboot and it loaded, but after about 30 seconds, reboot into a boot loop.
-Thought maybe TWRP didnt like the phone so I flashed Amon RA 2.3
-went into recovery just fine. Did complete wipes of everything using Calkulin Wipe all.zip
-re-flashed CM7.1.0 RC1
-boot loop
-flashed latest radios
-rebooted back into recovery
-reflashed cm7.1.0 rc1
-boot loop
During all of the reboots I would occasionally get the CM7 splash screen and then a reboot into boot loops. I THINK everything was flashing ok.
At this point I was frustrated and was thinking it was something I was doing that was jacked up so I decided to unroot and I flashed the newest RUU(which obviously removes root, S-off, .76 boot loader, etc...) so I did it. Figured I was just trying to get the phone running to sell anyway. Flashed was successful, chose to reboot and guess what. Boot loop. I pulled the battery out for about 10 minutes and it boots into the rom, runs for about 10-15 seconds in the rom and then reboots, back into the rom at least, but only about 10-15 seconds later, another reboot.
Every thread I read on these infinite boot loops were guys saying they couldnt even get into recovery or flash anything, which I had no problem doing(obviously cant really do that anymore with losing root and s-off). So I am stuck.
So current state of the phone is boot loader 2.16 S-on with 4.24.651.1 with all current radios, etc... flashed(as far as I can tell) from the RUU posted on Goo-inside.me.
Does anybody have any ideas for me to try? It seems like I am so close to getting it running because it will run for about 60 seconds but then reboot. I am guessing a hardware issue, but I honestly at this point have no clue.
Sounds like a hardware issue to me.
Sent from my PC36100 using XDA Premium App
Rem3Dy said:
Sounds like a hardware issue to me.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Thats what I am leaning towards, but why, if a hardware issue, will the phone run in the boot loader or recovery for basically forever without rebooting? It will also successfully(or did) flash everything I asked it to. I would think it would always reboot around that 60 second time frame if it was a hardware issue.
damn, too bad you ran RUU & lost s-off. now you couldn't do anything to test/troubleshoot even if you wanted to.
drdrewdown said:
damn, too bad you ran RUU & lost s-off. now you couldn't do anything to test/troubleshoot even if you wanted to.
Click to expand...
Click to collapse
I know. I probably should have posted up and waited, but I got impatient and thought that was a last ditch effort anyway since I tried everything else I knew to try.
rjacobs said:
but why, if a hardware issue, will the phone run in the boot loader or recovery for basically forever without rebooting? It will also successfully(or did) flash everything I asked it to. I would think it would always reboot around that 60 second time frame if it was a hardware issue.
Click to expand...
Click to collapse
because in the boot loader and recovery menu I'm sure the phone is not accessing radios, audio components, gps, and all manner of other hardware components that get activated once the phone tries to boot up for real.
It sounds like according to this thread: http://forum.xda-developers.com/showthread.php?t=805612&page=4
That my NV is FUBAR, but since I ran RUU and lost S-off, I cant do the fix. Oh well, I am sure eventually somebody will crack the boot loader and then I can fix it. Otherwise I have to send it off to HTC and I am sure pay them to fix it.
Just to clarify. The thread you linked to is for people who wrote nv items to their device.
What I'm afraid you are experiencing is the bootloop commonly complained about by those running CM roms.
I have yet to find a solution to the CM bootloop and all signs point to hardware failure.
Sent from my Evo using XDA Premium App