1. Download our Official Android App: Forums for Android!

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

Discussion in 'Android Devices' started by AndroidPhoneHome, Jun 6, 2010.

  1. AndroidPhoneHome

    Thread Starter
    Rank:
    None
    Points:
    5
    Posts:
    2
    Joined:
    Apr 8, 2010

    Apr 8, 2010
    2
    0
    5
    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. :(
     

    Advertisement

  2. OMJ

    OMJ Bazinga
    Rank:
    None
    Points:
    213
    Posts:
    3,290
    Joined:
    Nov 27, 2009

    Nov 27, 2009
    3,290
    825
    213
    Finance
    Pennsylvania

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

    Thread Starter
    Rank:
    None
    Points:
    5
    Posts:
    2
    Joined:
    Apr 8, 2010

    Apr 8, 2010
    2
    0
    5
    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.

    :D

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

    Are you OC'd as well?
     
  4. OMJ

    OMJ Bazinga
    Rank:
    None
    Points:
    213
    Posts:
    3,290
    Joined:
    Nov 27, 2009

    Nov 27, 2009
    3,290
    825
    213
    Finance
    Pennsylvania
    yea I am at 1.25 but failsafe is at 45C and it throttles down to 600
     
  5. johnlgalt

    johnlgalt Antidisestablishmentarian
    Rank:
    None
    Points:
    453
    Posts:
    9,415
    Joined:
    Oct 28, 2009

    Oct 28, 2009
    9,415
    1,924
    453
    Male
    Graduate Research Assitant | That part time IT guy
    3rd Rock
    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.
     
  6. nstallion

    nstallion Android Expert
    Rank:
    None
    Points:
    143
    Posts:
    1,152
    Joined:
    Nov 13, 2009

    Nov 13, 2009
    1,152
    136
    143
    San Diego, CA
    Would be nice if there was more of an explanation here.
     
  7. bdal1

    bdal1 Well-Known Member
    Rank:
    None
    Points:
    36
    Posts:
    246
    Joined:
    Nov 13, 2009

    Nov 13, 2009
    246
    9
    36
    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.
     
  8. johnlgalt

    johnlgalt Antidisestablishmentarian
    Rank:
    None
    Points:
    453
    Posts:
    9,415
    Joined:
    Oct 28, 2009

    Oct 28, 2009
    9,415
    1,924
    453
    Male
    Graduate Research Assitant | That part time IT guy
    3rd Rock
    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.
     

Share This Page

Loading...