Root Overclocked at 1.0 ghz + 2.2 + watching hulu = dead droid

[AndroidPhoneHome]

UPDATE: THE DROID LIVES!!!!! Plugged it in for a last try and it turned on. PHEW

So the unimaginable just happened to my droid...

I installed 2.2, overclocked to 1.0 ghz, installed flash and watched hulu for 10 minutes.

Phone resets.

Phone never turns on again.

Sad sad day.

RIP droid, cause of death = asphyxiation caused by overheating.

 

[OMJ]

So the unimaginable just happened to my droid...

I installed 2.2, overclocked to 1.0 ghz, installed flash and watched hulu for 10 minutes.

Phone resets.

Phone never turns on again.

Sad sad day.

RIP droid, cause of death = asphyxiation caused by overheating.

I was watching hulu for like 30 minutes earlier with no ill effects. Did you have a failsafe profile set in setcpu?

 

[AndroidPhoneHome]

I was watching hulu for like 30 minutes earlier with no ill effects. Did you have a failsafe profile set in setcpu?

Wow, it's like the droid gods saw my post or something. After I posted this thread I tried my luck one last time and plugged the charger in and my phone LIVES!!!

I tried a million times last night and it just wouldn't turn on.



A failsafe profile IS a good idea, enabling it right now.

Are you OC'd as well?

 

[OMJ]

Wow, it's like the droid gods saw my post or something. After I posted this thread I tried my luck one last time and plugged the charger in and my phone LIVED!!!

I tried a million times last night and it just wouldn't turn on.



A failsafe profile IS a good idea, enabling it right now.

Are you OC'd as well?

yea I am at 1.25 but failsafe is at 45C and it throttles down to 600

 

[johnlgalt]

I have seen more than a few 'bricked' phones that will not power on nor charge that will do so after a certain time period. My supposition (since this happened to me once too) is that it tremendously overheated and the batt temp (not CPU) went past what the phone likes. So, after a cool down period (and or a battery pull - freezers are good for this) you should be back in working shape, with hopefully no permanent damage to your battery.

 

[nstallion]

UPDATE: THE DROID LIVES!!!!!

Would be nice if there was more of an explanation here.

 

[bdal1]

This has happened to me twice. It is likely a battery issue.
If the battery is stone dead it is complicated to get it to power back up just by connecting it to a power source.

The last time it happened to me was because i flashed a new rom and walked away. The phone sat in a boot loop for like an hour and killed the battery. I connected it to a non motorola wall plug and got nothing. I plugged it into my desktop pc and.....nothing
When i got home i plugged it into my motorola multimedia dock and it powered right up.

 

[johnlgalt]

When I ran my battery into the ground I connected it to my Motorola charger that came with the phone - nothing.

It took about 30 minutes of leaving it plugged in before it all of a sudden revived.