Thinks its time for a new evo... issues...

**intheb0x** · 10-28-2010, 12:08 AM

Well lately, i been swearing its been the kernels i been using that been making my phone reboot, well its gotten so bad, that i cant even install stock kernels and such without the phone rebooting on home screen, its just a endless cycle, even if i do a nandroid restore to a older date, it will do the same thing..

should i just throw on the newest stock 3.30 rooted and go to a sprint store? is there a way to remove the super user icon so they wouldnt know?

or do u guys recommend me just doing the 3.30 ruu STOCK without root?

**Kevin O'Quinn** · 10-28-2010, 12:17 AM

Since 3.3 hasn't been officially pushed out you would need to RUU the 3.29.

Have you done crazy OCing that woulda maybe fried your CPU? Like pushing the limits or letting your phone get REALLY hot?

You could also try unrooting and returning to stock and go for a while and see if it does the same thing. Just follow the sticky.

**intheb0x** · 10-28-2010, 12:33 AM

no, im not really into OCing, im just running the kernels the way they are, if anything im underclocking..

i could care less about quadrant and such, i just want my phone to run smooth...

it all started about a week ago, and its been getting worse ever since, i been thinking it was a problem with kernels undervolting, but then when i load the stock kernels, the same thing happens...

finally got her back up and running, im afraid to restart lol...

i flashed amon instead of cw, to wipe to make sure something wasnt getting left behind with CW, ill flash the 3.30 and see if it holds i think...

**Kevin O'Quinn** · 10-28-2010, 12:35 AM

did you install any particular apps right before it started? BTW I'm pretty sure the newest stock kernels undervolt (that's what HAVS is).

**intheb0x** · 10-28-2010, 12:41 AM

Originally Posted by iamlilysdad

did you install any particular apps right before it started? BTW I'm pretty sure the newest stock kernels undervolt (that's what HAVS is).

angry birds, my phone will reboot while playing, its just a matter of when, today i got reboots while texting, while texting in gtalk, while surfing the net, and so on...

i got juice defender on from a few days ago, ill take that off and see if that does something.

**intheb0x** · 10-28-2010, 12:42 AM

its like ill have bouts with my phone on the reboots, it will happen non stop and then just be normal, this has happened before, just not as bad.

**Kevin O'Quinn** · 10-28-2010, 12:44 AM

I've had that happen before with kernels. but never with the stock kernel.

I'm thinking this thread needs to be in the hacks section. It's not really gonna get the attention it needs from the right people that could help you morel.

**intheb0x** · 10-28-2010, 12:45 AM

yea, i was debating doing that originally... but figured id get more views here quicker..

maybe mods could move it?

**intheb0x** · 10-28-2010, 12:47 AM

its happening now and its on the fresh 3.30 with NO apps installed...
i can predict when its going to happen as well.

its telling me there is a voice mail update, when i click update, it will start to install, then in the middle or so it shuts off, like the cpu is messing up or something.

only seems to happen under load.

**beezy** · 10-28-2010, 01:00 AM

Im going to side with iamlilysdad.I would say that best and easy way to figure out would be to unroot and root again.Then flash a rom with a stock kernel run it for awhile without any tweaks.Then slowly start to work in setcpu or anything like that.If it still happens after that i would return to fully stock,figure out away to reproduce the problem.Then take to sprint and show them what is going on.If it doesn't happen then its probably doing it cause things aren't getting completely wioed out like they should when wiping.

**intheb0x** · 10-28-2010, 01:07 AM

can u point me in the right direction to RUU SuperSonic EvO 3.29.651.5 OTA ??

thats the one i need right?

also i cant flash back to clockwork anymore if i wanted to try go back to nandoid, when i do it in rom manager it says error flashing recovery?

**Kevin O'Quinn** · 10-28-2010, 01:15 AM

just follow the sticky on how to unroot.

http://forum.androidcentral.com/htc-...urn-stock.html

**beezy** · 10-28-2010, 01:17 AM

Originally Posted by intheb0x

can u point me in the right direction to RUU SuperSonic EvO 3.29.651.5 OTA ??

thats the one i need right?

also i cant flash back to clockwork anymore if i wanted to try go back to nandoid, when i do it in rom manager it says error flashing recovery?

Im not a big rom manager user so not sure about that one.
As for the RUU.Here's a link i know it's 4shared but it;ll only make you wait 90seconds. http://forum.androidcentral.com/htc-...tml#post407509

or do like he^ said.

**intheb0x** · 10-28-2010, 01:19 AM

Originally Posted by beezy420

Im not a big rom manager user so not sure about that one.
As for the RUU.Here's a link i know it's 4shared but it;ll only make you wait 90seconds. http://forum.androidcentral.com/htc-...tml#post407509

or do like he^ said.

are u sure its that link for 3.29.651?

it says

RUU_SuperSonic_S_Sprint_WWE_3.26.651.6_Radio_2.15. 00.07.28_NV_1.40_release_140444_signed.exe - 4shared.com - online file sharing and storage - download

**beezy** · 10-28-2010, 01:23 AM

Originally Posted by intheb0x

are u sure its that link for 3.29.651?

it says

RUU_SuperSonic_S_Sprint_WWE_3.26.651.6_Radio_2.15. 00.07.28_NV_1.40_release_140444_signed.exe - 4shared.com - online file sharing and storage - download

I must of made a mistake.I would just go with what iamlilysdad said grab the RUU from Lj's sticky and run it.You will be back to stock and be able to see if the problem still happens.

**intheb0x** · 10-28-2010, 01:37 AM

Just a heads up, if anyone else asks about the issue with rom manager, just connect to wifi and u will be able to go back to clockwork.

im going to call sprint tomorrow and see if they got any warranty replacement evos in stock, last time i had a issue with it freezing up before i was rooted, and they swapped it out no questions asked, they didnt even look at it lol.

hoping the same will happen this time, because i think im pretty sure its a issue with the hardware or something.

**Kevin O'Quinn** · 10-28-2010, 01:39 AM

sounds like maybe you had a connection problem then. i've flashed clockwork using ROM Manager over 3G many times without a problem.

EDIT: If you're doing the RUU and returning to stock the recovery image won't matter. It'll get overwritten anyway.

**intheb0x** · 10-28-2010, 01:44 AM

Originally Posted by iamlilysdad

sounds like maybe you had a connection problem then. i've flashed clockwork using ROM Manager over 3G many times without a problem.

EDIT: If you're doing the RUU and returning to stock the recovery image won't matter. It'll get overwritten anyway.

i did a quick google search, and alot of ppl just said to enable wifi and then try to reflash CW through rom manager.

i just wanna go back to a previous nandroid before i finally take the step towards unrooting, i download the RUU, so im ready, just wanna see if i can keep the phone the way i had it for a little longer if it lets me.

**intheb0x** · 10-28-2010, 02:21 PM

I think I figured out what's been happening, here's my idea on what it is, I think my phone is overheating.

That's why when playing angry birds the phone is being tested and the cpu is being well used. That's the reason why my phone will shut off during heavy loads.

And then it will not start it will keep rebooting after going to the home screen.

I tested it today after the phone overheated shut off, I tried to restart it and it would be rebooting, so then I took the back cover off, and then put the phone with out the battery or back cover on my air conditioner vent on my car, I left it on there for 5 minutes and the phone with cold , I then proceeded to reboot the phone and everything is working fine , but once I start playing that game and overheat my phone it would do the same thing until it cools down...

What should I do from this point forward?

**Kevin O'Quinn** · 10-28-2010, 03:03 PM

Get your phone exchanged because it sounds like something you did fried the CPU, or something else on the board. Normal use wouldn't do this so it's likely that the cause is something else. I say that because I've played Angry Birds for very long periods of time with my phone on and off the charger and have had zero problems.

**Kevin O'Quinn** · 10-28-2010, 03:03 PM

Of course you could just try returning to stock like we already suggested and see if it does the same thing.

**intheb0x** · 10-28-2010, 03:25 PM

I'm going to return it to stock tonite and then download angry birds, play it and see if the same happens, if so, I'm going to sprint tonite.

Will keep you all posted, thanks for the help.

**intheb0x** · 10-31-2010, 11:25 AM

Well now after un rooting, i cannot get the phone to reboot...

ive done like 15 quadrants, and ive run angry birds...

im un sure what to do at this point, im pretty sure sprint isnt going to give me a new phone if i cant replicate the re boots

**intheb0x** · 10-31-2010, 11:50 AM

well i got it to reboot once during a quadrant.

**YeOj** · 10-31-2010, 11:20 PM

I would call Sprint and tell them that your phone is rebooting and it's been happening for awhile now. Tell them you have factory reset the phone and it's still occurring. Ask them to do an Advanced Exchange. They will ship you a refurb phone to your house and you can just ship your bad one back.

My wife's EVO had the same problem. It would reboot at random times of the day. At first it was only happening every now and then. The problem finally progressed to the point where the reboots were happening every day. Once the phone rebooted, it would get stuck in an endless reboot loop. My wife would have to pull the battery and let it sit without the battery in for at least an hour before it would boot back up again and be stable.

I did some research on the reboot loop issue online and most people who have had the problem had to get a new phone in order to resolve the issue. Hope this helps you and good luck! Her new phone has been rock solid, so it was definitely a hardware issue.