Search This thread

bouss

Senior Member
Jun 19, 2010
195
40
Thessaloniki
Απ: HTC Desire Rebooting on its own

I thought this problem was figured long ago. Got it 3 times and 3 times htc fixed it by replacing the motherboard (as long as the warranty was active). Last time they gave me an updated version of the software. Told me it was a software glitch that destroyed the motherboard and it was fixed by the updated software. Must take their word since the problem never occurred again.
 

ashlykapoor

Member
Feb 3, 2013
5
1
HTC Desire rebooting on its own

Well I went through the entire post, but couldn't figure out a exact solution. I have a desire which is 3 years old, but i love it to the core...though my phone is rooted, but I had the official gingerbread 2.3.3 on it till last december. I then installed a custom rom and it worked fine for a few days, post which I installed another custom rom in Feb first week (miui jellybeans by vijender) and since then the phone starting rebooting endlessly. I tried re installing stock rom/other custom roms by cygenmod and aokp, but nothing seem to work. I have tried endless things but nothing seems to fix my desire :( Ofcourse the phone is out of warranty so have to bear the expense of replacing the motherboard.

P.S: I follow the exact procedure of flashing a rom as mentioned by developers...step by step...so no miss there..

If any one else figured out a solution ? Please help...I don't want to part away with my desire !!

Regards,
Ash
 
  • Like
Reactions: J.K Nilsson

Jana0503

Member
Apr 15, 2013
12
2
HTC Desire SV reboot

Although, this is the "desire General" forum, this should add some information to the existing ones, hope this is okay

I purchased the "Desire SV" about 2 months ago, which also has the similar bug/feature of rebooting on its own, which started after almost a month of purchase.
By then I had installed a lot of crap apps and uninstalled them if I didnt like. Also I have Nova launcher and customized it to my liking.
The phone is still under warranty and default ROM.

Now on the reboot disease, after going through the forums like this, here is what I did.
1> Factory reset the phone a couple of times but it didn't help.

So 2 weeks back, spoke to the customer care guy & tried safe mode but no use. So I
2> Removed some of the suspected apps -> no use
3> Installed, CPU Spy, System Monitor, Diagonsis, alogrec, alogcat to study further -> helped me :)
4> Read somewhere that the GSM/WCAMA auto mode was some kind of a problem
So changed it to only the "WCDMA" mode. -> helped me :)

And then I started the 1st test last week, for about 100 hours the phone has been running fine.
All the while, I was checking for the probable clues using the above tools, and I also did this:

-> installed back the regular apps which I use and games like temple run 2, install &
uninstall some junk/trial apps --> No reboot occured.

-> Played Temple run 2/Browsed Internet on 2G & also Internet-Pass through/ as much as 1 hr everyday at random times --> No reboot occured.

-> On the move during the day and faced no problem on the calls or Internet --> No reboot occured.

-> However, Observed that the phone got hot on the top part of the phone's backside (i.e behind the proximity sensor or left side of the camera)

-> Observed that in "Diagnosis", temperature shot up to a maximum of 41 deg Cel during playing games or browsing or on charging --> No reboot occured.

Monitored the frequency range of CPU to see the track. @92Hours: 1GHz: about 8%, 245MHz: 15%, Deep Sleep: about 70%, rest all under 5%
couldn't use alogrec or alogcat since it was too much information for me to track the bug.

However, yesterday the bug silently occured and caught me unaware. I missed switching on the alogrec at 100 hrs. Here's the sequence of events about an hour before the reboot hit...
1> Observed signal low, but still opened Maps apps and browsed - Data transfer was slow even though there was no signal bar. Maps loaded very slowly on 2G connection.

2> Used Camera to click on a few pics (used flash and normal) & tx'ed 4 pics using bluetooth - all ok

3> Pocketed the phone and a few minutes later, BBBBBangggggggggg!!! Reboot occured
(Here missed to observe the heat on the backside of the phone)

Now I am not new to Linux or embedded Linux, but am a newbie to mobile communications and I don't know Java. So no app knowledge. So there is my limitation.

Any Questions? Any Inputs? All are welcome to assist in the 2nd test. Its definitely a radio issue.

The 2nd test is in progress.
 
Last edited:

vasanthrg

Member
Nov 27, 2012
19
2
Cochin
Try a different SD card

Hey, are you using the same SD card, did you try with a different SD, the problem could be with your SD card.
Sorry I haven't gone through your early posts.:good:


Although, this is the "desire General" forum, this should add some information to the existing ones, hope this is okay

I purchased the "Desire SV" about 2 months ago, which also has the similar bug/feature of rebooting on its own, which started after almost a month of purchase.
By then I had installed a lot of crap apps and uninstalled them if I didnt like. Also I have Nova launcher and customized it to my liking.
The phone is still under warranty and default ROM.

Now on the reboot disease, after going through the forums like this, here is what I did.
1> Factory reset the phone a couple of times but it didn't help.

So 2 weeks back, spoke to the customer care guy & tried safe mode but no use. So I
2> Removed some of the suspected apps -> no use
3> Installed, CPU Spy, System Monitor, Diagonsis, alogrec, alogcat to study further -> helped me :)
4> Read somewhere that the GSM/WCAMA auto mode was some kind of a problem
So changed it to only the "WCDMA" mode. -> helped me :)

And then I started the 1st test last week, for about 100 hours the phone has been running fine.
All the while, I was checking for the probable clues using the above tools, and I also did this:

-> installed back the regular apps which I use and games like temple run 2, install &
uninstall some junk/trial apps --> No reboot occured.

-> Played Temple run 2/Browsed Internet on 2G & also Internet-Pass through/ as much as 1 hr everyday at random times --> No reboot occured.

-> On the move during the day and faced no problem on the calls or Internet --> No reboot occured.

-> However, Observed that the phone got hot on the top part of the phone's backside (i.e behind the proximity sensor or left side of the camera)

-> Observed that in "Diagnosis", temperature shot up to a maximum of 41 deg Cel during playing games or browsing or on charging --> No reboot occured.

Monitored the frequency range of CPU to see the track. @92Hours: 1GHz: about 8%, 245MHz: 15%, Deep Sleep: about 70%, rest all under 5%
couldn't use alogrec or alogcat since it was too much information for me to track the bug.

However, yesterday the bug silently occured and caught me unaware. I missed switching on the alogrec at 100 hrs. Here's the sequence of events about an hour before the reboot hit...
1> Observed signal low, but still opened Maps apps and browsed - Data transfer was slow even though there was no signal bar. Maps loaded very slowly on 2G connection.

2> Used Camera to click on a few pics (used flash and normal) & tx'ed 4 pics using bluetooth - all ok

3> Pocketed the phone and a few minutes later, BBBBBangggggggggg!!! Reboot occured
(Here missed to observe the heat on the backside of the phone)

Now I am not new to Linux or embedded Linux, but am a newbie to mobile communications and I don't know Java. So no app knowledge. So there is my limitation.

Any Questions? Any Inputs? All are welcome to assist in the 2nd test. Its definitely a radio issue.

The 2nd test is in progress.
 

Jana0503

Member
Apr 15, 2013
12
2
Hey, are you using the same SD card, did you try with a different SD, the problem could be with your SD card.
Sorry I haven't gone through your early posts.:good:

And updates, the 2nd reboot occurred at 65 hours (y'day). No actions done prior to reboot, it just occured. No symptoms.

I am gonna try with a different SD Card. Will keep the updates coming in...hopefully more response comes in :D :)
 

HTCisRubbish

New member
Apr 20, 2013
1
0
I was stupid enough to have 2 HTC Desire HD's. Both from new. First was an Orange upgrade. The second I was stupid enough to pay for with my own money.

Both were treated like babies. I didn't install Apps on either. They were only used for text messaging and phone. I never used any of the smart features, but kidded myself that one day I might watch a movie on a train etc. In fact, both had such easy lives that they probably only were used for about 1 hour per month.

The first started to go wrong within months, minor things, reception related, but it still worked and soldiered on for 1.5 years. Then it just went totally dead. I took it apart rather than send it back to Orange, thinking I might be able to find the problem. I gave up, and put it in the bin.

The second HTC Desire HD I bought with my birthday money this year, January. It was new but only £120 because it was now an older moiney, and I was prepared to give HTC the benefit of the doubt. I wish I had seen this forum thread and the hundreds of others like it!

This second phone, again treated with kid gloves, has gone completely belly up in less than 3 months. Constant hanging, constant rebooting, constant hanging during booting, 7 vibrations, a constant never ending vibration, and now and again I can get into the phone, but not for long.

I feel well and truly ripped off and I intend to never buy another HTC phone ever again. I also intend to spread my story far and wide and tell everyone whomever discusses phones with me about my experiences with HTC.

I have emailed HTC support but, after reading this thread and others, I am not expecting any help....

HTC have stolen from me. Stolen my money. That's how I see it. Thieves.
 

Jana0503

Member
Apr 15, 2013
12
2
I was stupid enough to have 2 HTC Desire HD's. Both from new. First was an Orange upgrade. The second I was stupid enough to pay for with my own money.

Both were treated like babies. I didn't install Apps on either. They were only used for text messaging and phone. I never used any of the smart features, but kidded myself that one day I might watch a movie on a train etc. In fact, both had such easy lives that they probably only were used for about 1 hour per month.

The first started to go wrong within months, minor things, reception related, but it still worked and soldiered on for 1.5 years. Then it just went totally dead. I took it apart rather than send it back to Orange, thinking I might be able to find the problem. I gave up, and put it in the bin.

The second HTC Desire HD I bought with my birthday money this year, January. It was new but only £120 because it was now an older moiney, and I was prepared to give HTC the benefit of the doubt. I wish I had seen this forum thread and the hundreds of others like it!

This second phone, again treated with kid gloves, has gone completely belly up in less than 3 months. Constant hanging, constant rebooting, constant hanging during booting, 7 vibrations, a constant never ending vibration, and now and again I can get into the phone, but not for long.

I feel well and truly ripped off and I intend to never buy another HTC phone ever again. I also intend to spread my story far and wide and tell everyone whomever discusses phones with me about my experiences with HTC.

I have emailed HTC support but, after reading this thread and others, I am not expecting any help....

HTC have stolen from me. Stolen my money. That's how I see it. Thieves.

You have warranty to use or the "Consumer Court" in your country :) Use them.
 

Jana0503

Member
Apr 15, 2013
12
2
#3 test Updates

And updates, the 2nd reboot occurred at 65 hours (y'day). No actions done prior to reboot, it just occured. No symptoms.

I am gonna try with a different SD Card. Will keep the updates coming in...hopefully more response comes in :D :)

And further updates on week #3: The 3rd test is running for the last 121 hours --> "No reboots so far"

@121hrs:
- 1GHz, 600MHz, 480Mhz, 320MHz < 7%
- 245MHz: 37%, Deepsleep: 48%

Now I have been using "alogrec" to record to a log file. Hence the reason for 245MHz activity, which otherwise is usually less than 20%.

Couple of changes:
1. formatted SD card using SDFormatter and reused.
2. Not used the GSM mode as didn't move into a low signal area. So always in WCDMA(UMTS) mode.

Others:
1. Activity usual: browsing on 2G, games, calls, camera, videos --> No change in this.

My Questions:
1> Any effect of the "alogrec" continuous recording(many writes in chunks) on the flash memory area, since the log file is stored on the internal SD card.
 
Last edited:

pcny

New member
Jun 4, 2013
2
0
Hamburg
Hey guys,

after reading in this forum for a while now, this is my first post. The search showed no results on my issues, so ...

The Problem:
Desire reboots after searching/finding a carrier signal and sometimes randomly.

The Story:
I first experienced this after using my first ROM vijendrahs CM 10.1 for a few days (flashed with CWM). Because it seemed obvious to me that it couldn't be an overheating-issue (the motherboard was changed in the last days of guarantee some weeks before), I flashed the newest Radio ROM (5.17.05.23). That did it, at least when I was staying in the same city. My beloved Desire couldn't stand longer travels by train including exhausting signal-searches and rebooted/shut down immediately after booting up.

But things got even worse. Since my Desire fell from my desk some features didn't work at all (such as flashlight, camera, headphone-jack, LEDs). Crafty as I am :silly: I tried to fix it myself. After watching a disassembly-video on youtube and opening the phone I really found a loose contact between mainboard and upper-board. So I reassembled it and everything worked just fine.

A few days later the reboots started again. Now, the phone reboots immediately though I have a strong carrier signal. And sometimes it even reboots when no SIM card is inserted.

Since then I tried several ROMs (e.g. Paranoid, CM7, MIUI 2.3.7), many Radio ROMs, went from CWM-Recovery to 4EXT, tried over- and underclocking, bought a new battery and even changed my SD-Card (okay, I have to admit I'm not using a Samsung, but a Transcend C10 32GB) - and of course tried some different sd-ext-settings too.

Does ANYONE have the same issues and/or could give me some hints on this? I really love my Desire and don't want to end our relationship just like that ... :crying:

Here some hard-facts:

S-OFF
HBOOT-6.93.1002
(actual) Radio: 5.11.05.27
sd-ext: ext4 with 2056mb

BTW: I just realised that the Desire seems to be more stable when it's charging - maybe the processor is overloaded somehow or any hardware has a malfunction and wastes too much energy?! Is there any possibility to test the hardware?

You see, I really need some help on this one!

Thank you so much!
pcny
 

fbeachler

New member
May 5, 2009
2
0
if say for example you force close the browser, it could have been linked to google maps, the news widget, friend stream etc, and once the browser is closed by the task killer, the other applications will re-open it in order to complete what they are doing, this will drain a large amount of battery.

correct me if i'm wrong :)

You stand corrected. Force closing a browser that has been launched by another activity does not cause any intents to be broadcast to the calling activity or the Android OS. Without an intent broadcast, the callers have no way of knowing that a force close occurred.

Thus, no, the Android OS will not attempt to re-open a force-closed app so that calling activities can finish what they're doing. The calling activity might have some defensive coding that can re-launch a sub-activity that was unexpectedly closed. In practice, such a level of defensive coding in Android apps is extremely rare, if present in any app including those from Google. Most Android engineers are happy enough to make sure their app doesn't crash and the user gets a readable error message.

You might be thinking of services. Android OS will manage services the way you describe - but only if the service returns a value of START_STICKY when onStart() is invoked.

None of what I describe above would explain a sudden and drastic drain on battery power - we are talking about re-launching activities which takes perhaps a few seconds and normal drain on the battery.

---------- Post added at 10:29 PM ---------- Previous post was at 09:58 PM ----------

Hey guys,
The Problem:
Desire reboots after searching/finding a carrier signal and sometimes randomly.

In my case it usually powers-down randomly, without warning. Sometimes it randomly reboots instead of powering down. Any of this in common for your device?
 
Last edited:

pcny

New member
Jun 4, 2013
2
0
Hamburg
In my case it usually powers-down randomly, without warning. Sometimes it randomly reboots instead of powering down. Any of this in common for your device?

Yep, all of them are occuring several times a day - I also discovered that shaking the phone, even during normal walking, can cause a power down. In most cases the Desire only boots completely when the battery is pushed/pressed into position. Best chances for using it I get when it's wired to the charger. For now it's more like a wired 4-inch wifi-tablet.

Nevermind ... by the end of the month a HTC One will be my new device. Meanwhile I'm using my gf's old Samsung Corby. The resistive Touchscreen really is state oft the art ... :eek: I guess the step from Corby to One might be a hell of a switch. ^^
 

Jana0503

Member
Apr 15, 2013
12
2
Updates on my desire SV reboot expts...

Its been a long time on this..... HTC desire SV reboot issue...


After my last post....had to go off on trips (work) to Europe.....and found plethora of problems....reboot would occur anytime - signal or no signal, low signal or during call, or on just a single ring when somebody calls....

got frustrated.....

I solved my problem by purchasing a Samsung GG2.

But some changes on my Desire SV has lowered the reboot problem...

1. rooted my desire SV and using only the single SIM.
2. Using Holo Laucher HD.
3. using DU battery saver.
4. Changed the mother board once from the customer service, but still the same problem...

My guess, this is a known problem of the device and is deliberately released by the company without proper testing. The hardware is faulty.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    It seems a lot of people having this problem.
    A poll to count how many?
    Mine doesn't have any problem, yet I'm worried.
    2
    HTC Desire SV reboot

    Although, this is the "desire General" forum, this should add some information to the existing ones, hope this is okay

    I purchased the "Desire SV" about 2 months ago, which also has the similar bug/feature of rebooting on its own, which started after almost a month of purchase.
    By then I had installed a lot of crap apps and uninstalled them if I didnt like. Also I have Nova launcher and customized it to my liking.
    The phone is still under warranty and default ROM.

    Now on the reboot disease, after going through the forums like this, here is what I did.
    1> Factory reset the phone a couple of times but it didn't help.

    So 2 weeks back, spoke to the customer care guy & tried safe mode but no use. So I
    2> Removed some of the suspected apps -> no use
    3> Installed, CPU Spy, System Monitor, Diagonsis, alogrec, alogcat to study further -> helped me :)
    4> Read somewhere that the GSM/WCAMA auto mode was some kind of a problem
    So changed it to only the "WCDMA" mode. -> helped me :)

    And then I started the 1st test last week, for about 100 hours the phone has been running fine.
    All the while, I was checking for the probable clues using the above tools, and I also did this:

    -> installed back the regular apps which I use and games like temple run 2, install &
    uninstall some junk/trial apps --> No reboot occured.

    -> Played Temple run 2/Browsed Internet on 2G & also Internet-Pass through/ as much as 1 hr everyday at random times --> No reboot occured.

    -> On the move during the day and faced no problem on the calls or Internet --> No reboot occured.

    -> However, Observed that the phone got hot on the top part of the phone's backside (i.e behind the proximity sensor or left side of the camera)

    -> Observed that in "Diagnosis", temperature shot up to a maximum of 41 deg Cel during playing games or browsing or on charging --> No reboot occured.

    Monitored the frequency range of CPU to see the track. @92Hours: 1GHz: about 8%, 245MHz: 15%, Deep Sleep: about 70%, rest all under 5%
    couldn't use alogrec or alogcat since it was too much information for me to track the bug.

    However, yesterday the bug silently occured and caught me unaware. I missed switching on the alogrec at 100 hrs. Here's the sequence of events about an hour before the reboot hit...
    1> Observed signal low, but still opened Maps apps and browsed - Data transfer was slow even though there was no signal bar. Maps loaded very slowly on 2G connection.

    2> Used Camera to click on a few pics (used flash and normal) & tx'ed 4 pics using bluetooth - all ok

    3> Pocketed the phone and a few minutes later, BBBBBangggggggggg!!! Reboot occured
    (Here missed to observe the heat on the backside of the phone)

    Now I am not new to Linux or embedded Linux, but am a newbie to mobile communications and I don't know Java. So no app knowledge. So there is my limitation.

    Any Questions? Any Inputs? All are welcome to assist in the 2nd test. Its definitely a radio issue.

    The 2nd test is in progress.
    1
    Right, very interesting.... Just called HTC to book phone in for repair. Spoke to the girl which explained that reboot occurs when reception is weak and app you are using at the moment requires internet access. Because of the poor reception, some of the data is missing, and CPU has to work much harder, basically, it's trying to work with information which it hasn't got. Also, i told her that it happened not only when using gnav, but when playing games too, to which she replied that games access internet too (which makes sense, adverts). I'll do a little test later on today. I'll put phone on charge and will play angry birds with wifi on, and then with 3g on (reception is not that great at my place), and see if i can force it to reboot. If it doesn't reboot when wifi is on, and will when wifi is off, it will become a valid explanation i suppose.

    Any thoughts?

    BTW Bad news guys. She said that if reception is poor again, rebooting WILL start again even with new motherboard. Basically, once it happens it gets progressively worse over the time. Hope she is wrong, but she DID sound like person who knows about these things :(
    1
    Hello guys.
    I am afraid I won't make you happy. I did have my Desire in repair 2 months ago
    due to overheating-reboot problem.
    Repair was successful. Motherboard was immediately replaced, no more reboots.
    BUT until today! All started again. So my guess is this: It is design fault. In my opinion, every Desire will have this problem - it is just a mater of time, when the heat will degrade motherboard.
    I'll send it to repair again.
    Jan.

    P.S.
    1. one more clue - the reboots are accelerating - first, it has rebooted just once, playing games on AC adapter, but then reboots became more frequent, like a short surfing on WiFi + AC adapter and at the end just a 1 minute on Google Maps with GPS and 3G, no AC adapter plugged and 5x reboot loop until phone cooles itself to boot properly. It looks like less and less tollerant to CPU usage/heat.

    2. I guess it is not definitely software based - I am using stock T-Mobile Froyo - no ROM/root modifications whatsoever.
    My first repair was on stock T-Mobile Eclaire, the second one is on stock T-Mobile Froyo. These symptoms remind me behaviour of badly cooled PCs with AMD K5/K6 CPUs. The system is less and less stable and it takes shorter and shorter to overheat - chip/chips are being degraded.
    1
    folks, the issue that i am facing is quite frustrating. when i watching flash videos on youtube or other sites, my desire reboots automatically. it does not matter which browser i use, the native one or a 3rd party one ie Dolphin HD browser. the phone keeps rebooting until i remove the battery and leave it switched off for atleast 15-20 minutes. the phone is not overheating, neither is there some unwanted app running. my phone is rooted with unrevoked and have the clockworkmod version 2.5.0.7.

    and sometimes when the phone reboots, i usually hold down the volume button to ensure it boots into HBOOT. After which if I try to goto recovery, the phone keeps rebooting again.

    under normal circumstances though, i am able to get into recovery without issues.

    i have tried factory reset/wipe 100 times already but that doesn't fix the problem. i have also reflashed a 100 times and that again, does not fix the problem.

    phone details;

    HBOOT-0.93.0001
    RADIO-5.09.05.30_2
    Android 2.2 with 2.13.720.2 CL274424 release-keys
    Kernel - 2.6.32.15-gd96f2c0

    3rd party apps installed;

    Angry birds
    Dolphin HD browser
    pFinance
    Profile Valet
    Rom Manager
    Titanium Backup
    Winamp
    Youtube ripper

    also, in the past two weeks, the phone reboots while charging too...which makes it doubly frustrating!!

    HELP PLEASE!!

    Looks like your problem is same like mine.
    Only solution is to send to HTC repair center for MB changing :)
    I did mine, after change MB now my desire is superb again!!