The last couple of weeks I have been having problems with the phone randomly shutting off and power cycling. I had been using CM6 for a long time with no apparent problem till this started happening. So I unrooted and flashed back to stock and dl'ed current updates OTA...To no avail it was still happening....I brought it into Sprint and the tech determined that it is a safety feature cause the phone was overheating...And that it is a known issue that has to do with the last current update... I also use the silicone case so I know that is keeping it warmer than normal. I usually have these random resets when using apps for along time...They said HTC knows about it and trying to come up with a different update to fix it. I had asked the tech about rooting which he said corporate frowns on but would be nice to have it unrooted when you bring it in...I am just curious if anyone else is having this problem...The tech also suggested to flash a different kernel and that should take care it or wait for the OTA. Anyone have a suggestion for a good kernel?...And now i have to root again dammit...ughh..
Related
Hey all.
Been having problems with a Nexus One that crashes at seemingly random times.
I have been unable to pin it on anything, and am asking your help.
It appears to be independent of the Rom installed, whether there is an SD card present, or whether its connected to a USB cable or phone charger.
Any help would be greatly appreciated.
Phone Info:
Nexus One (AT&T model)
Radio: 4.06.00.12_7
Current Rom: Enomther's TheOfficial Nexus1 - v2.12.2
Provider: Rogers (BC, Canada)
Logcat output attached as screen capture image.
This has been reported by a few users. I sent mine in for repair and got it back not repaired - they couldn't replicate the problem.
My case has been escalated which means a HTC guy called and asked me a few questions and then told me to wait for an email (a few days ago).
I believe my problem started when I seriously overheated it ... driving with navigation on, 3g downloading maps and traffic data, car charger plugged in all on a very hot day on a very hot dashboard. This was the first reboot and they got more and more often after that. Now I can't run anything for more than 5 minutes if 3G or wireless is on (in 'Airplane' mode I can run for quite a while without a reboot).
mine was doing the same thing.
getting progressively worse until the phone was basically unusable earlier this week.
I was running CM6 at first when it started happening.
installed the newest nightly and it worked better for a bit then got even worse.
uninstalled the stand alone version of gmail from the market and it worked for a couple hours and then kept rebooting on me.
finally i did a factory data/cache wipe and installed a rooted stock rom and things have been working PERFECT for over half a week.
I had the same issue. first reboot happen when i had nav running plunged in then after a few months utube , browser etc would restart my phone. it didn't matter which rom i used or stock. I sent it in and they fixed it. i had issues with htc but it got fixed.
Yup, same here, strange thing is it isn't a complete reboot. Hard to explain but what happens is i'll touch the phone and then it will immediatly go to the CM6 boot logo, then immediatly to the lock screen, (which I have disabled) then to my normal desktop. Total time elapsed maybe 5/6 seconds, wierd.
A normal reboot usually takes about say a minute or so. just started happening 3/4 days ago, and happens maybe twice a day at most, some days not at all. Probably wait until Cyanogen includes 2.2.1 into 6.0.0 stable then reflash.
Ive been having the same problem for about a week now, but I'm still using stock, not rooted. Its weird, because its a really fast reboot. It goes to the Booting X, for about 6 seconds, then it boot up just fine. I cant understand it.
this really sucks
I am keeping my ATT nexus one around for gingerbread but these random reboots are really killing me....I use the phone for five minutes and it just reboots by itself....The phone runs really well for those five minutes...Ive done five factory resets but it is still just doing these phantom reboots.... Anybody find out anything more about this...or know a fix....the phone is not rooted and it is clean stock froyo...so please help or keep talking about it so htc will address this issue lol which i doubt since this phone is starting to become ancient....(cant wait till nexus S) =P
With regards to the original problem posted, I believe I've managed to diagnose it correctly.
The problem lies with faulty heat distribution. The phone would crash and reboot more often in times of great stress:
charging the phone (heats up the battery)
running many applications at once (heavy system load)
navigation (heavy dataand gps traffic, image processing)
This coupled with the fact that changing the OS did nothing to remedy the problem solidified the notion that the problem was hardware based.
Given this, I contacted HTC Nexus One support and had the phone repaired.
Note: HTC will honor the warranty and fix hardware issues for an unlocked Nexus One. With software issues, you're on your own (for obvious reasons).
This is exactly what my phone is off to warranty for. I experienced this with every rom tried. I wipe my phone completely and put stock froyo on only to see the exact same behaviour...so at least I'm not crazy
The tech told me it was a hardware problem so that is a bit of a mind ease.
It seems Nexus One and Desire are really similar: HTC Desire rebooting on its own.
P.S. It's a problem with faulty motherboard, if you're within warranty, it should be replaced.
I also have been pleasantly experiencing this issue with the nexus one, so i sent it for repair at HTC and they have said it is an issue with the motherboard and it has been replaced, it is now in the post so I will update this post when I receive it to whether the problem is resolved. Hope so was driving me crazy!
The log did not capture the error. In most cases its a software issue, not hardware. (has happened to me too, not recently though)
Well an update as promised.
I received my N1 back after UPS had finished not dispatching it due to "Adverse weather conditions" and the issue is GONE!!! I know a week isn't really a long time to trial the device but this was happening several times a day.
HTC replaced the motherboard.
My advice to anyone having this problem, is to send it to HTC for repair (dont be worried about it being rooted/custom ROM etc mine was and because its a known hardware issue they really aren't bothered about it.)
It took two trips to HTC for them to finally address the issue. They did fix something (they didn't say what) and the problem is gone.
I believe it was the motherboard because Swype Beta decided that it was a new phone and not the one I registered (so it would not install).
Anyone having a issue with the screen not coming back on and staying blank? I get this happening from time to time and the only way to fix it is to do a battery pull or do volume up + camera + power button to reboot. When it happens I can hit the power button to wake up the screen but it stays blank and just the keys on the bottom light up and respond to be touched but don't do anything.
Rooted with stock EB13, it did this on rooted DI18 also.
I've done a lot of reading on the Epic forums (General and Development) and I haven't heard of this issue before. What method did you use to update to EB13? If you didn't already do it, you might want to consider a full wipe/reflash of EB13 using Odin/Heimdall/Samsung installer. I'm not guaranteeing anything, but to me it sounds kinda like you have a bad upgrade/flash.
If wiping your caches and doing a full reflash doesn't fix it then it's probably a hardware issue.
DISCLAIMER: I'm nowhere near as experienced as some of these dudes on XDA. If anyone else thinks I'm wrong, please say so and explain why so that I don't give any more bad info! However, I try not to talk out of my ass, so I feel fairly confident in what I've said.
AmericanJedi001 said:
I've done a lot of reading on the Epic forums (General and Development) and I haven't heard of this issue before. What method did you use to update to EB13? If you didn't already do it, you might want to consider a full wipe/reflash of EB13 using Odin/Heimdall/Samsung installer. I'm not guaranteeing anything, but to me it sounds kinda like you have a bad upgrade/flash.
If wiping your caches and doing a full reflash doesn't fix it then it's probably a hardware issue.
DISCLAIMER: I'm nowhere near as experienced as some of these dudes on XDA. If anyone else thinks I'm wrong, please say so and explain why so that I don't give any more bad info! However, I try not to talk out of my ass, so I feel fairly confident in what I've said.
Click to expand...
Click to collapse
I used the Samsung installer.
Same thing has happened to me thrice today (since the upgrade last night, which came from ODINed DI18 usind update.zip).
And that's with no apps installed/running.
I've had this coming up couple times a week on DK28 ROMs, sometimes it's able to recover (like some sort of soft-reboot), most times I need to pull the battery.
I need to replace my Epic badly.. if the replacement behaves the same way, it will join a pile of junk WM6 phones in my basement.
No one else has had this?
Yes. It happened to me twice earlier today. Disturbing. I can't think of anything specific when it happened...once on Dolphin and once after using the camera i think. Have used those a lot since, and it hasn't happened again.
Stock, not rooted. I manually updated via placing the install.zip file on my SD card.
I can confirm this behavior.
Sent from my SPH-D700 using XDA App
Ok I fear I have a very isolated problem since I have not found any other posts over multiple sites on the same issue.
I bought my VM optimus V 3 days ago and wanted to root it. I had used gingerbreak to root my optimus M just 1-2 weeks ago without problem. Well unfortunately I did not see that it basically doesnt work anymore (I did PLENTY of research but you guys have the only post), and installed and attempted a root.
It failed after a few restarts and tries, so I moved on, but soon I noticed 3G and GPS (I guess data as a whole) was not working.
Since then (2 days) I have rooted using <yuck> windows-superoneclick and flashed multiple ROMS including stock with success. BUT no matter what I do the data is still not working.
VM couldnt figure anything out, and has escalated the issue internally, and I could go down to BEST BUY and exchange it as broken, but I'd rather figure it out, and I hope its something stupid easy.
Can any serious developers, or even funny ones help me out here? Thanks in advance!
Update
Wow, no one up for a challenge?
Latest: Its been escalated again to like lvl3 VM support now, since 3G shows up and up and down arrows flash but it doesnt actually work. Also the virgin activate app completes but identified my phone as a Nexus S!!???
Any takers?
Same thing happened to me I freaked out.
I saw this thread and used Gingerbreak to unroot my phone in hopes the problem would go away. It didn't seem to. Then I tried to turn on some sync things like gmail and google reader. Googled for a bit and the 3g came back on I received the email notice for signing up to xda and just thought I would let you know it wasn't permanent. If you backed up your original rom with the gingerbreak try flashing to it and unrooting. Then wait a while for the 3g to come back.
Hi
I'm on my 2nd N4 after the first one developed a case fault. I had no problems with that one when using Minco or PA.
However this one seems to have a habbit of becoming completely unresponsive at least once every couple of days. The only way to bring it back on is to hold the power button in for a few seconds and then reboot it.
I will be putting it back to stock tonight and giving it more of a chance. But I thought i'd ask and see if anyone else has experienced this type of issue or knows if it's a sign of a more serious problem such as the red light of death.
Thanks
Phils7 said:
Hi
I'm on my 2nd N4 after the first one developed a case fault. I had no problems with that one when using Minco or PA.
However this one seems to have a habbit of becoming completely unresponsive at least once every couple of days. The only way to bring it back on is to hold the power button in for a few seconds and then reboot it.
I will be putting it back to stock tonight and giving it more of a chance. But I thought i'd ask and see if anyone else has experienced this type of issue or knows if it's a sign of a more serious problem such as the red light of death.
Thanks
Click to expand...
Click to collapse
I did actually experience this when I'm on stock 4.2.1 out of the box state, rooted and custom recovery.
transfered to PA for a couple of days and reflashed stock images from google site. after going back from PA to Stock I haven't experienced the lock up/screen unresponsive yet. hopefully it flashing back from PA to stock fixed this.
I've been using my phone for a month with rooted stock rom, custom kernel, unlocked bootloader, custom recovery, busybox and there's no single lag or lockups. Maybe you got a bad phone. I hope it can be fixed though.
I have a rooted stock ROM, unlocked bootloader, I don't have busybox permanently installed because I use apps that require a 'unrooted' phone but I have Stephen Stericson busybox installer at the ready.
I've not had a single lockup since I bought this phone.
I need your help guys. Been on here for years, rooted every phone I have ever owned (multiple carriers). Self taught through trial and error and reading threads on here. But I have now ran into an issue that I have never seen or heard of and cant seem to find something on here to help. A friend of mine has Verizon Galaxy S5 and recently had to replace it through the insurance plan he had on it from Verizon. He had been complaining for a while and has finally agreed to let me take a look and see if I can fix it. I HAVE TRIED EVERYTHING!!! (that I can think of). This is extremely frustrating. Below ill list the issues and things Ive tried.
Issues:
Operating system crashes
Rebooting on its own
Wont load up when turned on
Apps crashing
Battery wont last long
and general "Jankyness" haha (seriously though)
These issues are constant issues meaning all happen constantly throughout the day and night.
I have tried multiple factory resets through the settings and through stock recovery
Just tried using Odin to fix this aaaannndddd NNOOO GO!!! 8-O
i have used Odin many times, never seen it not work like this. If anyone has an explanation for this and a recommended solution that would be great!! Thanks all for reading this and hopefully I can help my friend.
pockermj said:
I need your help guys. Been on here for years, rooted every phone I have ever owned (multiple carriers). Self taught through trial and error and reading threads on here. But I have now ran into an issue that I have never seen or heard of and cant seem to find something on here to help. A friend of mine has Verizon Galaxy S5 and recently had to replace it through the insurance plan he had on it from Verizon. He had been complaining for a while and has finally agreed to let me take a look and see if I can fix it. I HAVE TRIED EVERYTHING!!! (that I can think of). This is extremely frustrating. Below ill list the issues and things Ive tried.
Issues:
Operating system crashes
Rebooting on its own
Wont load up when turned on
Apps crashing
Battery wont last long
and general "Jankyness" haha (seriously though)
These issues are constant issues meaning all happen constantly throughout the day and night.
I have tried multiple factory resets through the settings and through stock recovery
Just tried using Odin to fix this aaaannndddd NNOOO GO!!! 8-O
i have used Odin many times, never seen it not work like this. If anyone has an explanation for this and a recommended solution that would be great!! Thanks all for reading this and hopefully I can help my friend.
Click to expand...
Click to collapse
if your friend's S5 is running OE1, you're out of luck:
http://forum.xda-developers.com/verizon-galaxy-s5/help/downgrade-oe1-t3149085/post61730480
if this replacement phone has been malfunctioning since he got it, I'd raise a ruckus with Verizon.