first i wanna thank you guys for this awesome forum
i have an AT&T aria phone that randomly reboots
LIBERTY PVT SHIP S-OFF
HBOOT-1.02.0000
MICROP-831b
TOUCH panel-stn21_03
radio-7.16.35.11
Nov 4 2010
the phone is rooted with CWM v2.5.0.1 istalled.
i flashed the original ATT rom 2.2 from HTC website and it didnt fix it
i flashed shipped att rom and it didnt fix.. also flashed rooted rom yet no luck
1-i tried to unlock the bootloader with HTCDEV.COM but it gives me error message
fastboot oem get_identifier_token
...INFO[err] command error
2-i tried to use the revolutianary website and no luck either
3-i tried to put the original img on the sd card LIBEIMG.zip and booted into bootloader but the phone didnt recognize the file at all.
i am a newbie in the android word but i can swear i did every thing by the book in these last 3 steps** at least as i could understand**
p.s: i dont know wut or who did this to this phone
This is sort of a long shot, but did you happen to install a 32GB SD card around the time the problem started happening?
If not, did you change ANYTHING else? new SIM card? new charger? etc.
nope i did not install 32 GB card..
i dont know exactly what happened to this phone.. i took it AS IS..
when i first got the phone it had the original at&t 2.2 stock S-off ... i was lucky to flash CWM using fastboot..
i think if i can install HBOOT again and turn S on this might solve the problem... or may be i need to do something to the partitions but as i told u im a newbie in here
i am sure it is a software problem due to the error message i get when i try to unlock the bootloader...
I tried everything: stock AT&T Froyo rom, returned to S-on, new sd card, new sim card. Also returned to HTC for "repair," but it still rebooted so I returned to HTC for another try.
BTW, I used the Unrevoked method to root/S-off the phone, and the S-on method listed in the development forum to take the phone back to stock. Both with no problem (several times). The S-on was a little trickie, had to load stock AT&T rom, then follow the S-on instructions, which includes loading the stock AT&T Froyo rom again.
I'll report the results of my 2nd HTC repair on the 2 Arias reboot problem thread.
Sent from my MB860 using XDA
i am trying to install HBOOT 1.03 but no luck.. i think if there is a way to reflash the hboot this would solve the problem
gdjy said:
i am trying to install HBOOT 1.03 but no luck.. i think if there is a way to reflash the hboot this would solve the problem
Click to expand...
Click to collapse
Don't try to do that. HBOOT 1.03 will not fix your problem, it'll only make it worse (not being able to easily S-OFF). You should avoid HTC's official bootloader unlocking method -- it's worse than Revolutionary.
thank u drumist...
i tried already but no luck.. it says device ID error..
i am so desperate in here.. is there anyway i can fix this aria??
To my surprise I had called HTC and found out that my phone was still under warranty. As I said above, the phone is now back at HTC for a 2nd try. I will let you know what they found as soon as I get the phone back -- it took about a week last time.
Drumist was very supportive in my effort to find the problem, and against his advice and out of desperation, I did restore the HBOOT, and, as he said above, it did not solve the problem. The phone was back to being completely stock -- ATT Froyo 2.2 and S-ON -- and it sill had random reboots --taking anywhere from 1 minute to almost an hour before rebooting. Which is really annoying when trying to troubleshoot. I even re-rooted and S-Off'd the phone using Revolutionary, and still had the problem. I then returned the phone to stock again prior to sending it to HTC for repair. Checked one more time... still random rebooting. As I am now using another phone -- Atrix 4G -- solving this has become more of a challenge.
The other thing that's amazing is that I have 2 ATT Arias with exactly the same problem!
I wonder if it is a location thing. You don't happen to reside in SE Pennsylvania do you?
the same thing has been happening to me. it just started happening recently.
about 10-20 times a day the phone just buzzes and goes straight to the white HTC turning on background.
it's very annoying.
charbo187 said:
the same thing has been happening to me. it just started happening recently.
about 10-20 times a day the phone just buzzes and goes straight to the white HTC turning on background.
it's very annoying.
Click to expand...
Click to collapse
I have to agree with you, it is really annoying. Luckily I dont use my phone very often. I dont think it is location based, as I'm in eastern Iowa.
Ok. Just got my Aria back from HTC after their 2nd attempt at at fixing the random reboot problem. It rebooted within 5 minutes of turning it on! And twice after that.
The only thing I did was put in the battery. No SD or SIM card, and I did not plug in a battery charger. I didn't even have a chance to connect to my wifi.
I will call HTC tomorrow and anticipate sending it back to HTC for a 3rd try.
I really thought they would send me a new phone after the 2nd attempt at fixing it. Although now I'm really curious about what could be causing this.
It's interesting that that there are more reports about this problem. I had rooted and installed multiple roms before restoring it to stock AT&T Froyo prior to returning it to HTC for repair. Has anyone had this random reboot problem on a phone that was never rooted?
Oh well. I will probably be sending it back to HTC tomorrow, and will keep you posted about the results.
Sent from my MB860 using XDA
I am having the same issues...luckily I now have the HTC One X, however I do still use the Aria as a dedicated GPS, which is frustrating having CONSTANT reboots.
This also only happened recently...I wonder what the issue could be...
Reboot saga
Just spoke to HTC about their failed 2nd attempt to repair my phone. They told me the repair records state that they replaced the "main board," which I assume is like the mother board.
If that is true, I would assume that would be like getting a new phone. If that doesn't fix it, I am truly baffled. The ONLY thing I did was put the old fully charged battery in the phone to test it -- without a SIM or SD card . Could the problem be related to the battery? Since I have another Aria (with its own battery) with the same problem, I doubt it.
Regardless, HTC is having me send it back for a 3rd try to fix it, and they sent me a prepaid shipping label this time.
They said if the 3rd repair attempt doesn't fix it, they would send it to a higher level repair facility for a 4th try! I can't complain about HTC's commitment to trying to repair my phone.
From the responses on this thread, this has become a recent problem. Mine started about a month ago. Any theories out there?
Thanks for sharing your experiences yar, however I'll be dealing with the reboots cause I cant go that long without my phone.
Another thought I had while driving yesterday, Do your guy's that reboots, happen usually after you press the lock button? I've noticed after I send a text message and I hit the lock button is mostly when it will restart. Anyone think it would be that button causing the problem or maybe the HTC Sense Lockscreen?
While I'm waiting for HTC to return my phone after their 3rd attempt to fix this problem I have been experimenting with my other Aria.
I booted into CWM and left it there for over an hour and the phone did not reboot. Does this helps isolate the problem?
Also, has anyone managed to stop a random reboot problem?
Sent from my MB860 using XDA
Just got my Aria back from HTC after their 3rd attempt, and it rebooted within 10 minutes. I even used a new battery, thinking that somehow that was causing the problem. No sim or sd card, and I did not even log onto wifi. They claim they replaced the "main board." Its hard to believe they actually tested it.
Probably beating a dead horse, but I will take HTC up on their offer to send it to the next level of service for a 4th try at fixing the problem. Can't believe it wouldn't be more cost effective to just send me a new phone at this point... but then there might not be any new Arias available.
Sent from my MB860 using XDA
try setting the Aria data comm to Edge only
I've been following this thread with interest since I have an Aria with AT&T "service" and have been experiencing the random reset problems described here. I have not rooted the phone and have the stock 2.2.2 release side loaded through HTC Sync. After several attempts to isolate the problem, I think I may have stumbled across something that works (so far, no reboots in the last 11 hours, but, that is not conclusive evidence yet). Try using the "hidden test feature" by entering *#*#4636#*#* on the dialer keypad. Then under the "Phone information" section select "GSM only". I understand that this forces the phone to use only the Edge data format.
I think there may be a problem with the Aria's firmware that communicates with the 3G network. I was able to use 3G successfully in the past year, but, something must have changed recently in the way AT&T configured this network or at least I suspect that a recent network change has caused these problems with our phones. You would think that AT&T and HTC would be aware of such a problem by now since I imagine many of us are affected. I'm leaving my phone on Edge until I see evidence that the problem has been resolved.
RWB Jr said:
I've been following this thread with interest since I have an Aria with AT&T "service" and have been experiencing the random reset problems described here. I have not rooted the phone and have the stock 2.2.2 release side loaded through HTC Sync. After several attempts to isolate the problem, I think I may have stumbled across something that works (so far, no reboots in the last 11 hours, but, that is not conclusive evidence yet). Try using the "hidden test feature" by entering *#*#4636#*#* on the dialer keypad. Then under the "Phone information" section select "GSM only". I understand that this forces the phone to use only the Edge data format.
I think there may be a problem with the Aria's firmware that communicates with the 3G network. I was able to use 3G successfully in the past year, but, something must have changed recently in the way AT&T configured this network or at least I suspect that a recent network change has caused these problems with our phones. You would think that AT&T and HTC would be aware of such a problem by now since I imagine many of us are affected. I'm leaving my phone on Edge until I see evidence that the problem has been resolved.
Click to expand...
Click to collapse
I will have to give this a try, as for HTC and ATT knowing, they probably don't care and I dont really blame them this is a 2 year old phone.
Related
Every time I reset or turn on my fone after shutting down, it will stuck at the logo boot up. It wasn't like that when I first bought the fone. Now it's getting worse and worse since the issue happens so frequently.
I have to take out the battery and put it back, then wait for about 3 to 5 mn before I turn the phone on.Then it would boot up as usual.
Is there anyone facing the same issue as I am? Any suggestion guys?
Are you experiencing excessive heat when this occurs? Also, can you give more info such as: does this happen only after recent charging or does it ever happen when the phone has been turned off for a long time? Was there any recent apps you installed or ROM changes when this started happening? Was there any potential damage done to the phone -dropped it, got it wet, or microwaved
When you say frequently, does that mean every time you restart? every other time? every five times?
Lastly, do you have any other issues/symptoms other than freezing at startup? Does the phone ever freeze during normal use?
i'd suggest you do a hard reset of your phone (hold down both vol up and vol down keys while powering on/resetting). that should fix the problem. if the problem still persists, it's probably some hardware faults.
Me too
My HD2 just started doing this too. It was fine for 7 weeks I have owned it. However, as described in this by OP, when doing soft reset would it would also get stuck on bootup logo. I'd have to remove the battery for a few minutes before it would bootup.
However, my HD2 also crashes and upon reboot then get stuck on bootup logo. It appears to crashes randomly eg not with any particular program or action.
I figured it was software issue so did hard reset. This worked fine. After hard reset the only software I loaded were Total Commander and Cookie Editor.
After Cookie Editor install I did soft reset and it got stuck on bootup logo. : (
So I did another hard reset but it hung up again upon reboot on bootup logo.
This appears to be a hardware issue. But has anyone else had same issue?
T-Mobile HD2
Stock ROM
Purchased July 6 2010 from Expansys
yes i am experiencing the same problem and i have uploded a video on youtube showing this! Yes my phone heats up when this happens..
Hi. I got this problem for quite sometime and am so used to taking out and putting back and taking out and putting back the batt.
But now I have another prob: my ringtone suddenly went soft and I now have to keep myself alert all the time to see if there's any incoming call or SMS.
I would like to do a hard reset but the question is: will it set my phone back to the stock ROM or still retain the updated version - 1.66.707.1?
Thanks in advance.
Stormrider75 said:
Hi. I got this problem for quite sometime and am so used to taking out and putting back and taking out and putting back the batt.
But now I have another prob: my ringtone suddenly went soft and I now have to keep myself alert all the time to see if there's any incoming call or SMS.
I would like to do a hard reset but the question is: will it set my phone back to the stock ROM or still retain the updated version - 1.66.707.1?
Thanks in advance.
Click to expand...
Click to collapse
It will retain whatever rom you are using
Htc Hd2 vodafone UK
HD2 issue
After some more searching it appears this is not uncommon for HD2. Its not clear to me if it is specific to T-Mobile HD2 or HD2 in general.
It appears to be a hardware issue. Although that is not 100% clear either. I find it hard to distinguish what some people report as 'freezing' which i believe is different to the issue described in this post which is 'hanging up' or 'getting stuck' on boot up screen - in my case it is the T-Mobile 'stick together' pink and white screen/logo.
(The 'freezing' issue that i believe is different to this 'getting stuck on bootup logo' issue appeared to have been resolved iwth new T-Mobile ROM - and I never experienced it on my HD2).
The resolution for getting stuck on bootup screen issue described here appears to have been to exchange HD2 (although some people exchanged up to 6 times and keep getting same issue!)
I think it is important to note that my HD2 performed fine for 7 weeks with lots of soft resets, hard resets, and lots of software installs (though no ROM reflashing) but within last week or so, start crashing randomly, then upon reboot get stuck on bootup screen/logo. This also became more frequent as time progressed. After doing hard reboot, the issue is now acute, eg it gets stuck on every reboot, and crashes more often.
This leads me to think some hardware has failed or degraded and is getting worse, maybe a connection/soldering etc?
However, is there any possibility that a ROM could 'degrade'? Can a ROM have a setting that is modifiable? (I know it is 'read only memory' but is it really?)
Anyways, love to hear from others on this issue.
Same problem here. Bought my HD2 in june. Cooked my own rom with Chucky's kitchen. Flashed different radios, hard resets, task 29 etc. Absolutely no problem. Worked fine for several weeks. But sometime it begun to freeze, auto resets, stuck at boot logo. It was getting worse. Even flashing stock rom it hungs at boot logo.
Now my HD2 is out for repair. Now waiting for returning. Hope they will change the motherboard.
several people have had their motherboards replaced and that has seemed to fix it for them. You'll probably have to fight with htc or your carrier, but should be able to get it replaced.
Hi guys. Another question:
I'm considering doing a hard reset. How do I store my messages before doing it? I can't seem to locate the folder that keeps all my messages.
TIA.
HD2 is an odd one
Thanks for replies. I really don't want to send it in .. but it will probably be the only way to resolve the issue. It will cost me courier there and back, and $20 'triage' fee .. total cost to me will be ~$100 just to have them look at it. Price of doing business I guess.
Anyways, I realized that one of my issues was that it was crashing when syncing. A little digging reveals that HTC Sense does something to all contacts when syncing first time putting a bit of html in contact notes field (weird but it is true .. its their way of reminding you bought an HTC phone?) So once I got it up and running, I disabled Sense and syncing went fine, no crashing.
(Btw, Sense also appears to do something with SMS msgs too so if you have lots it crashes on due to this reason too).
However, even with plain Jane MS today screen (eg not using Sense) it still crashed once on sync and again when listening to radio. Both times had to remove battery for few minutes before it would reboot without getting stuck at bootup logo.
But so far it seemed to be working 'better' without using Sense.
So, I re-enabled Sense to see what would happen and over a day it has crashed twice. I am going to see how it behaves for few days before sending it in as RMA repair.
Still, important point is that it was ok for 7 weeks, and then started crashing, more and more, even after hard reset, though some of issues may have been due to Sense (which is reported by many users).
It is still not a 'normal' thing for a $700 consumer device to have such erratic behaviour. So, given others have exchanged crashing handsets for new handset that has no issues points to underlying hardware issues as suggested above eg motherboard.
As comparison I also have HTC Diamond 2 which has been rock solid for 2 years of continuous use even with lots of software install, tweaking, reg hacks, etc.
Stormrider75 said:
Hi guys. Another question:
I'm considering doing a hard reset. How do I store my messages before doing it? I can't seem to locate the folder that keeps all my messages.
TIA.
Click to expand...
Click to collapse
I don't text a lot so i just hard reset without saving .. but do a quick search on on XDA for SMS backup or PIM backup .. during my searches I am sure i have seen a couple of utilities that do what you want.
genoki said:
I don't text a lot so i just hard reset without saving .. but do a quick search on on XDA for SMS backup or PIM backup .. during my searches I am sure i have seen a couple of utilities that do what you want.
Click to expand...
Click to collapse
Thanks. Btw I read before we can actually 'disable' Sense.
How do we do that?
Sense - go to Today
Go to Start - Settings
- iI you see the black HTC Settings (has 'Personalize' on top of items) then go to Menu and select 'All Settings' (this will show Windows Mobile's Settings. HTC Sense 'Settings' doesn't everything Windows Mobile Settings has or shows it differently)
- Select 'Today'
- Select the 'Items' tab in Today
- Check 'Windows Default' and click OK in top right.
This will 'swap' out HTC Sense 'today' with Windows Mobile standard Today screen and voila you will have 'disabled' HTC Sense and you are back to using Microsoft's Windows Mobile 6.5 version of Sense (not anywhere near as useful or neat-o to look at but hey they are pretty happy with it )
genoki said:
However, even with plain Jane MS today screen (eg not using Sense) it still crashed once on sync and again when listening to radio. Both times had to remove battery for few minutes before it would reboot without getting stuck at bootup logo.
But so far it seemed to be working 'better' without using Sense.
So, I re-enabled Sense to see what would happen and over a day it has crashed twice. I am going to see how it behaves for few days before sending it in as RMA repair.
Click to expand...
Click to collapse
Just by disabling Sense is not going to make it work. I had this problem with my HD2 also and without using Sense it seemed to be working (there were fewer crashes), but only for few days. My HD2 was getting worse day by day - it was not crashing only if it was not touched (it was crashing just cycling between Sense tabs or by initiating a call).
At repair center they told me (after three weeks of waiting) that the motherboard must to be changed.
Is it possible to damage it by flashing custom ROMs?
For me, this problem appeared after just one month of usage. I was flashed some custom ROMs.
Now, I have a new HD2 but I'm affraid to flash a custom ROM (at least in the near future).
I have my HD2 back. Took me 2 weeks, the repair center changed the motherboard and got an new IMEI.
Now all is working, no more stuck at bootlogo.
But i'm on stock rom (1.66) with 2.07 radio. No way to run Android with this radio. Hmm...
axman79 said:
Is it possible to damage it by flashing custom ROMs?
For me, this problem appeared after just one month of usage. I was flashed some custom ROMs.
Now, I have a new HD2 but I'm affraid to flash a custom ROM (at least in the near future).
Click to expand...
Click to collapse
I'm afraid as well to flash any custom rom now. For Android i need to HSPL and flash a 2.08 radio or greater to use it. But i'm stick on stock rom for sure.
I want to know as well if it possible to damage it by flashing customs roms ?
As i stated earlier, i flashed plenty of roms, doing task 29 etc., in the end stuck on bootlogo.
Thanks for the feedback on your repairs axman79 and Kalip. Btw, aside from courier cost there and back, did you have to pay the $30 'triage' fee or whatever they call it? Also, did they challenge your observations at all or did they just replace motherboard without question?
Yah, disabling Sense hasn't stopped my HD2 from crashing eith. Without using Sense it crashed several times while using Opera and more than a few times while syncing over the past three days. Also, it still gets stuck on reboot often, requiring battery to be removed for few minutes before rebooting.
So, guess I will send my HD2 in for RMA repair too (and wait for up to 3 weeks) and hope I get a functioning device in return.
Interesting though I didn't flash my HD2 but it went from 'good' to 'bad' in similar way that your two HD2's. From reading other posts around here on XDA and elsewhere it appears that HD2 motherboards fail with surprising frequency and for variety of reasons.
Would be nice to know if HD2 motherboards are unusually delicate and something physically breaks, or if there is some electrical operation, eg charging it on USB or unusual combination of button pushes that shorts something out?
The fact that battery has to be removed for few minutes in order to get thing to reboot hints that something requires charge to dissipate eg a component somehow 'locks up' which causes crash, and needs to be discharged by removing battery?
genoki said:
Thanks for the feedback on your repairs axman79 and Kalip. Btw, aside from courier cost there and back, did you have to pay the $30 'triage' fee or whatever they call it? Also, did they challenge your observations at all or did they just replace motherboard without question?
Click to expand...
Click to collapse
Was flashing stock rom with stock SPL, was at the shop where i bought it and they send it. I told them it stucks at bootlogo. Repair center changed motherboard without any question. Cost me nothing.
genoki said:
Also, it still gets stuck on reboot often, requiring battery to be removed for few minutes before rebooting.
Click to expand...
Click to collapse
Ja ja, same here.
genoki said:
So, guess I will send my HD2 in for RMA repair too (and wait for up to 3 weeks) and hope I get a functioning device in return.
Click to expand...
Click to collapse
Yes you will, but dont forget to flash back stock rom regarding SPL !
genoki said:
Interesting though I didn't flash my HD2 but it went from 'good' to 'bad' in similar way that your two HD2's. From reading other posts around here on XDA and elsewhere it appears that HD2 motherboards fail with surprising frequency and for variety of reasons.
Would be nice to know if HD2 motherboards are unusually delicate and something physically breaks, or if there is some electrical operation, eg charging it on USB or unusual combination of button pushes that shorts something out?
The fact that battery has to be removed for few minutes in order to get thing to reboot hints that something requires charge to dissipate eg a component somehow 'locks up' which causes crash, and needs to be discharged by removing battery?
Click to expand...
Click to collapse
I want to know as well !
hey guys. I am so glad I found this post! I have exact same issues ith my HD2, it's driving me nuts.
I kept sort of log and described my problems in this post: http://forum.xda-developers.com/showthread.php?t=712729
I think I have to send my HD2 for replacement or repair.
Can you please tell me how can I get my phone fixed/replaced?
I got the US T-Mobile version, but I don't have account in T-Mobile. Can I deal directly with HTC? Where do I have to call to get RMA number etc.
I would greatly appreciate your help!
KML
I know this is a common problem as I've seen it in other threads on other sites, but I haven't been able to find a cause/solution. My Evo 3D randomly reboots, frequently. It has happened with every firmware version since I got the phone, and with every rom/kernel I have installed. It doesn't seem to be an overheating issue. I've tried uninstalling a few apps to see if they might be the cause. Basically I'm ready to call it a hardware defect. Does anyone have any idea what causes this or how to fix it? I bought my phone unsubsidized online so it isn't easy to return, but I may have to try anyways. My 3D is useless as it is right now.
Return it.....
Sent from my EVO3D
I bought it from eBay so that's not an easy return. HTC wants me to pay to ship it to them and they want my credit card number, then if they decide it's not an issue covered by warranty then they will charge me both for looking at it and also to send it back. Basically they will hold my phone hostage if they decide they want money from me. I have filed a complaint against HTC with the Better Business Bureau over their warranty policy.
If on stock ROM, return it. Sometimes on custom roms it reboots like crazy for me when using browser.
It reboots on stock and custom roms.
Return it...
I've talked to three people at Sprint and they won't accept it as a return. They say I have to take it back to the store it was purchased at, and though I've talked to the person I bought it from, he's in another state, so Sprint says I'm SOL.
SeeNev said:
I've talked to three people at Sprint and they won't accept it as a return. They say I have to take it back to the store it was purchased at, and though I've talked to the person I bought it from, he's in another state, so Sprint says I'm SOL.
Click to expand...
Click to collapse
Try different Roms. My buddies had the same problem. Flashed supra and flashed silver needle kernel. Flashing a custom kernel can easily fix it. The stock kernel argues with the stock OS and the phone is tricked into thinking there is harm. Therefore reboots to try and save your phone from any damage. For sure switch the rom and kernel.
Sent from my PG86100 using Tapatalk
I reboot alot also and its been on all my roms and stock but better now on synergy rom
Sent from my PG86100 using XDA App
tnh196 said:
I reboot alot also and its been on all my roms and stock but better now on synergy rom
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Most reboots are due to using unstable software or user error, if these aren't in question then your phone is a bad apple
Sent from my PG86100 using Tapatalk
Have a look at the battery contacts. I have read of some people solving reboots by wedging in a piece of thin cardboard on the opposite end of the battery to give it more solid contact.
SeeNev said:
I know this is a common problem as I've seen it in other threads on other sites, but I haven't been able to find a cause/solution. My Evo 3D randomly reboots, frequently. It has happened with every firmware version since I got the phone, and with every rom/kernel I have installed. It doesn't seem to be an overheating issue. I've tried uninstalling a few apps to see if they might be the cause. Basically I'm ready to call it a hardware defect. Does anyone have any idea what causes this or how to fix it? I bought my phone unsubsidized online so it isn't easy to return, but I may have to try anyways. My 3D is useless as it is right now.
Click to expand...
Click to collapse
replace your sd card.
*EDIT.... just for the sake of being a little more informational and contributing.... a bad sd card will cause this. your phone, like a computer, can detect a bad disk and will reboot itself to check it.
i had the same problem when i first got my phone... i had my old sd card in there... random reboots. replaced the sd card, problem went away immediately.
i KNEW it was the sd card, though, as soon as i powered up the phone with the new sd card installed because on my old phone whenever i would transfer apps to sd i would get this error pretty often "failed to move application" and i would do it again and it would work.
so after i put the old one in my new 3d i would get that same error... along with the reboots, and thats how i figured it was the card.
so when i powered the phone up with the new card, i went to move my apps from the internal disk to the card and EVERY single one of them moved over the first try. and the phone has not rebooted itself once since then.
also, i heard somewhere that HTC sent some phones out with bad sd cards.... so if you are using the one that came with the phone, that could still be your issue. replace the card.
I had a horrible time with my 3vo rebooting, then got a replacement through Sprint TEP (a new one, thank goodness; ##786# tells you refurbished status) but I had the new one do the same.
Once either of mine had a single reboot, it would then continue to a complete load (booting properly) but would then reboot again after 1-5 minutes. After pulling/reconnecting the battery, it is fine for a day.
The old one had the initial reboot WAY more often than the replacement (the old one had several in a day, this one has had only one per day for the past 2 days).
How to fix: You cannot fix it. You can, however, get a good day before it begins its rebooting sequence. To so this, you have to pull the battery. I have waited until it has rebooted, then I hit shutdown and disconnect-reconnect the battery before restarting.
I hope the issue is taken care of and the initial reboot is gotten rid of.
This has happened on bare stock unrooted and rooted cleanrom 2.1 and 2.2. Also, with 2 different SD cards and 2 different batteries and 2 different 3vos. I have HTC's fastboot off.
Cause: My best guess is that HTC fastboot is not completely off even when unchecked--something differentiates what is loaded during a random reboot from what is loaded after a battery pull, but I don't know what. That, or something differentiates a shutdown and the reboot that the phone does when it reboots randomly. I could be wrong. My sample size is only 2 corrections, but it literally rebooted 12 times then stopped completely after the battery pull and the same thing happened one additional time.
I appreciate the insights you guys have given. I have pulled the battery several times and I don't believe it has done any good, though I will test that further. I am using a 32gb sd card that I purchased when I had my evo 4g and it always worked before, but I will try using the 8gb that came with the phone. The battery is snug and I even 2 two spare battery that also don't fix the problem when being used. I had a lucky 2 days without any reboots, then back to about a dozen reboots a day. So far it's happened with every rom I've tried.
I have noticed that the problem seems to get worse in areas where there is no reception. I took it into the hoover dam and it rebooted like 20 times. Also at Disneyland in different ride buildings where there's no reception it would often reboot.
Yes, marginal reception areas are usually, but not exclusively, where mine starts its reboot routine. The other is during the airvana handoff.
Neither the battery or SD card made any difference. It seems to be getting worse now. All I have to do is run an application and half the time it will reboot. I've tried wiping the system and cache and reinstalling roms. Nothing works.
I was wrong before. It is the shutdown that makes the difference. Difference got home and it began to reset itself every 5 minutes or so. I pulled tjw battery during startup and it did not break the rebooting.
After it finished reboting, I selected shutdown then poweres it back on. After it came back up, it stayed up and has been stable since.
It looks like this might be something I have to get used to. If it begins to reboot, I have to give it a clean shutdown to relieve the issue (well, for 20 hours or so, at least). Again, HTC fastboot is always off.
Hi, I've scoured the forums here looking to see if anyone else had this problem. I found an old thread started back in May, but I am concerned with firmware 2.13.651.1 (the latest OTA). Since installing this update my phone now restarts 3-4 times per day, usually while idle sitting untouched on my desk. I hear a "buzz", look over and my phone is on the HTC startup screen. No rhyme or reason, just a completely random restart.
A little history, I had this problem OOB with version 1.13.651.1, it went away with OTA #1 - 1.22.651.3 (which had it's own problems, including lockup/overheating 3-4 times a day) and it returned with OTA #2 - 2.13.651.1. I am HTC Unlocked and have SuperSU/BusyBox installed, however I doubt those are my issue. Obviously I am running stock ROMs.
I've tested by doing a complete factory reset and letting the phone sit there idle on the startup wizard. Within hours it had restarted itself despite being untouched. I don't see a huge number of folks complaining about this issue here, so it must be hardware, yes? Do you think I got a bum unit?
I had this happen once today.. this is my second day on the new kernel.do not know if it was a fluke or related to your issue
Sent from my EVO using xda app-developers app
That is definitely not normal. You may want to relock and take it into Sprint. I have never experienced a reboot and I've had my phone since launch week. Or try a custom roms like MeanRom and see if you have better luck. You're already upgraded to the new base so you can just download and flash it.
Sent from my A500 using Tapatalk
Yep. I'm on EVO LTE #5. Strange part 2 and 4 did not have reboots. 1,3 and 5 do. Drives me nuts and sprint techs are clueless. With the lastest update it gives you a log of exactly why it had the errors. Yesterday I brought the log to the sprint repair and he said it was meant for HTC, not them.
I'm otherwords, he had no clue on how to read the log.
I'm hoping they fix this crap soon..they will not replace the phone anymore yet they can't fix it. I hate Sprint
Edit. Mine is stock, have not had one working good, long enough to root
Sent from my EVO using Tapatalk 2
Well, I took it into Sprint and yes they were clueless. Best they could offer me was to flash me back one version to the one the had blank notifications and overheated. I declined and went to HTC. They immediately issued an RMA. While I am not excited to get a refurb unit, I certainly am fed up with the constant reboots. Good thing I kept my old EVO 3D just in case.
FYI, I sent it back to HTC unlocked (but not S-OFF). I like to live dangerously.
So I was looking to leave my Sprint contract (long story) and decided to sell my Evo 4g LTE to help pay off the massive contract-breaking bill. I'd had my phone rooted and running CM10 nightlies for quite a while without any sort of trouble.
So right before I put the phone on the market, I took out the SD card, and wiped everything using TWRP recovery. This included Cache/Dalvik/System/Factory reset and the only thing I did different, which was to wipe Internal and External storage.
After that, I flashed the latest CM10 nightly at the time (which was cm-10-20121008 at the time) and called it a day as I didn't want to put any of my info on the phone before I sold it.
Flash forward a couple of days, I sell the phone and almost immediately get a call back saying it has no sound at all.
The guy I sold it to tells me he even tried unrooting and flashing the stock ROM to no avail. I bought the phone back from him, and am trying to figure out what exactly is wrong with it.
Since then, I've discovered that not only is there no sound, although occasionally I will hear the buttons click, so I know the speaker hardware itself is fine, There is also no video playback at all, which makes me think this is some sort of software or firmware problem, though I can't tell where the problem lies.
I've tried installing different ROM's and the best I could get out of video was the Youtube app showing still images every couple of seconds, without any sound at all. I tried loading videos to the SD cards only to get a message saying "This video cannot be played" without any further reason.
I'm currently downloading the latest OTA stock ROM to see if I can restore it to Factory settings, but I'm lost as to what could possibly cause this strange behaviour.
Anybody ever encounter something similar? Any ideas what I could try next?
Alternatively, does anyone want a (mostly) working phone at a steep discount?
Have you ran an RUU yet?
How much do you want for it as is?
jayjam99 said:
Have you ran an RUU yet?
How much do you want for it as is?
Click to expand...
Click to collapse
I tried running the RUU, still won't work.
If you want it, an even $100 will do.
i have the exact same problem ive ran ruu and relocked and locked bootloader i have unrooted ive done everything and the problem still is there please someone help me
As the title suggests, suddenly I started getting force closes with com.android.phone when I'd receive a call. I immediately tried to call out, same story. I've been troubleshooting for the past few hours, and had no luck finding anything relevant on XDA or any other site.
Firstly I switched kernels, since I'd updated to DSB's latest, though I'd had no issues with it until then. That failed, so I reverted to Viper's stock build.prop, undoing some changed I'd been running for a while (and hadn't modified at all today).
With no luck there, I backed up my sdcard and did a full factory reset and formatted the sdcard in twrp and then in cwm, followed by a reinstall of the latest Viper ROM. Even that didn't work, so I relocked and RUU'd back. Twice. Same exact issue. I can text anyone just fine, data over LTE goes on as normal, but anytime I try to make a call, be it with the stock dialer or through a diff one from the play store (for kicks, last resort). I reseated the SIM card a multitude of times, to no avail. I get full functionality with my SIM in my other phone, so I'm sure it must be the hardware itself on the phone. Every time com.android.phone stops, the SIM initialization happens like when you physically re-seat the SIM.
The troubling thing is that I haven't done anything, save for a simple kernel and recovery update, which would've been negated by two RUU runs to stock. I haven't touched the SIM card or anything, at least until that started happening. Furthermore confusing is how all other functionality can remain except for actually making phone calls.
Removing the SIM entirely and dialing a number does the exact same thing, just as an FYI.
Has anyone seen this? Any ideas?
As I've unlocked my phone, my last resort is to go into a VZW store and act like an idiot so they don't check to see if i unlocked it. Further complicating that is the fact that the DNA was actually purchased on my own account, which I closed, and brought to an unlimited data line that was preexisting. I'm half tempted to wait for the official OTA and see if that will remedy the issue, but my fear is this may be a physical issue beyond the remedy of a firmware update.
http://forum.xda-developers.com/showthread.php?t=2126386
Check this thread, me and another member faced the same problem. I can get 3g/2g data, sms and all other functions just right. Just no phonecalls, every time i make a call i get a crash of the app.
So, i am pretty sure this is a software bug. For god's sake, what a strange problem!Did your phone used to work right?
I bought my phone from ebay, did not check if phonecalls are working(i couldn't imagine such a bug) and went straight away to rooting/other kernels/roms etc. But can't find a solution too,tried everything as you, and the worst, i am overseas!!!
Is the update coming soon?
edit1: i have seen lots of threads about sim errors,a very common issue of DNA, i am believing that these two bugs have something in common. No hardware defect, just software bugs.
ergotelis said:
http://forum.xda-developers.com/showthread.php?t=2126386
Check this thread, me and another member faced the same problem. I can get 3g/2g data, sms and all other functions just right. Just no phonecalls, every time i make a call i get a crash of the app.
So, i am pretty sure this is a software bug. For god's sake, what a strange problem!Did your phone used to work right?
I bought my phone from ebay, did not check if phonecalls are working(i couldn't imagine such a bug) and went straight away to rooting/other kernels/roms etc. But can't find a solution too,tried everything as you, and the worst, i am overseas!!!
Is the update coming soon?
edit1: i have seen lots of threads about sim errors,a very common issue of DNA, i am believing that these two bugs have something in common. No hardware defect, just software bugs.
Click to expand...
Click to collapse
thanks for the thread, for the life of me i couldn't find anything exactly relating to what i described. that is spot on though, and def makes me feel a bit more at ease that maybe it can be resolved with an update to the firmware that's due soon.
yea, the funny thing is that it worked flawlessly, i never even got the SIM error message, i'd been texting my gf, a few friends, and my parents and then my pops called in the evening and it immediately closed out the call before it really even rang. i called him right back and that's when the force closes started happening, calls never working agian thereafter. however, i was able to still text everyone i was before and data was working flawlessly as always, just no calls, not even after all the crap i did to troubleshoot.
the update is hopefully going to be out soon. the support documents came out a few days ago. i def can't survive on this galaxy nexus after having used my DNA since launch!
I will wait for the update too, hopefully it will be uploaded today or tomorrow i think. But just because i can't get on the air update, i need to download from a server the update and install it on my own.
If anyone finds a solution or have an idea of what to look/do, please post here. I am pretty sure it is a software bug, something is stucking the application from working properly. The other solution is RMA, but it is a very difficult to send it back and get it back again.
ergotelis said:
I will wait for the update too, hopefully it will be uploaded today or tomorrow i think. But just because i can't get on the air update, i need to download from a server the update and install it on my own.
If anyone finds a solution or have an idea of what to look/do, please post here. I am pretty sure it is a software bug, something is stucking the application from working properly. The other solution is RMA, but it is a very difficult to send it back and get it back again.
Click to expand...
Click to collapse
The update is out now, can someone send it to me too? I am overseas, trying to find a way to download it.
OP, can you test this one to see if you get a fix?Thanks!!!
Ok, I had the same exact issue. I was stock then went to viper Dna then tried going to hatka and soft bricked my phone. I went back to stock using the RUU. That's when I got the com. Android. Phone crash message. So I had to re unlock reboot and then flash viper Dna again. Everything works as it should now.
After saying all that I just got the new update from Verizon. I assume I shouldn't flash this since I'm on a custom rom.
Sent from my Nexus 7 using xda premium
Thanks for the input, really interesting!Will try it right away! Hope you won't have any problems with the update now!
msturner79 said:
Ok, I had the same exact issue. I was stock then went to viper Dna then tried going to hatka and soft bricked my phone. I went back to stock using the RUU. That's when I got the com. Android. Phone crash message. So I had to re unlock reboot and then flash viper Dna again. Everything works as it should now.
Click to expand...
Click to collapse
THIS IS THE SOLUTION!Now working! A HUGE HUGE HUGE THANKS TO YOU!!!! :victory:
ergotelis said:
THIS IS THE SOLUTION!Now working! A HUGE HUGE HUGE THANKS TO YOU!!!! :victory:
Click to expand...
Click to collapse
Hi guys i got a similar problem. My DNA was perfect since yesterday but now i can use data connection for internet. All the other stuff is working fine....SMS,call, wifi, the only thing that is not working is the 3g data. All of this problem came when i flashed the viper DNA, so i flashed the supercharged hoping it was an issue of the rom. Olso with the supercharged the problem was always here.... So i decide to came back to stock and i re-lock my bootloader and flasched stock RUU. But data connection is still not working :crying:
can anyone please tell me what can i do?
Did you install patches 1.1.1& 1.1.2 from viper?They fix some gsm problems.
As I've unlocked my phone
ergotelis said:
Did you install patches 1.1.1& 1.1.2 from viper?They fix some gsm problems.
Click to expand...
Click to collapse
yes but notthing changed.... :'(
Now i'm compleatly stock and the problem is still here.
flash again the viper rom, do the whole procedure again, at least this is what i did and fixed the problem!(stock->viper->stock-> viper and then OK)
ergotelis said:
flash again the viper rom, do the whole procedure again, at least this is what i did and fixed the problem!(stock->viper->stock-> viper and then OK)
Click to expand...
Click to collapse
Which version of viper worked for you?
hard problem
Has any one figured out this problem? I have not been able to received any phone calls since I did s-off. I have tried everything that has been wrote so with no luck. I have relocked my phone and flashed stock RUU no change. Unlocked and tried several roms still no calls. formatted everything under CWM not change. Fixed permissions. Went back and re-locked and reflashed stock RUU. I know that some of the things above have fixed others phones and some still have problems. I also found a script someone wrote lock my phone which now it says locked and flashed stock rom after that still have problem. Does anyone here here a idea that I have not already mentione above? I like my droid dna but if I can't get it to make and take calls it is a paperweight.:crying:
jimmydee62 said:
Has any one figured out this problem? I have not been able to received any phone calls since I did s-off. I have tried everything that has been wrote so with no luck. I have relocked my phone and flashed stock RUU no change. Unlocked and tried several roms still no calls. formatted everything under CWM not change. Fixed permissions. Went back and re-locked and reflashed stock RUU. I know that some of the things above have fixed others phones and some still have problems. I also found a script someone wrote lock my phone which now it says locked and flashed stock rom after that still have problem. Does anyone here here a idea that I have not already mentione above? I like my droid dna but if I can't get it to make and take calls it is a paperweight.:crying:
Click to expand...
Click to collapse
Still broke?
Sent from my HTC6435LVW using xda app-developers app
kaliblazin707 said:
Still broke?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Yes it is still broke I just don't know what to do at this point paper weight right now.