Random reboots - One (M7) Q&A, Help & Troubleshooting

So a friend of mine gave me a htc one which works perfectly fine unless you keep wifi on while the screen is off.
It'll reboot within a minute after you turned the screen off. Did some googling, but couldn't find anything about it.
Tried different roms and kernels, but nothing fixed it so far. Currently I'm running santods gpe lollipop on kk sense firmware.
Maybe upgrading to latest sense firmware would help (which I currently can't do as I have no access to a computer)? Or do you guys think it's a hardware issue?

If it was a software issue, I think more people would have this problem. So...
Try going back to stock.

Already flashed back to stock, didn't help.
And yeah, I knew it's most likely a hardware issue, but I thought I tried asking anyway.

Related

[Q] Galaxy S screen keeps blinking?

Hi, my SGS is working fine all the while. But sometimes after i unplug the power adapter upon fully charge, the screen keeps blinking in the way like loading home(loading icons)->black screen->loading honme-> black screen->.....
it repeats for very a long time, even if i manually screen off then unlock the screen, the blinking problem still repeating. Until i reboot the device, it works fine again... Happened once in the middle of playing game, it suddenly 'jump' to home screen and the blinking problem begin
Wonder if this related to system crash and cause home screen keeps loading on and off or hardware problem... did anyone experience this?
I've never heard of this before. To diagnose whether it's a hardware problem, your only bet would probably be to flash a clean firmware. Maybe someone will have heard of this though.
upichie said:
I've never heard of this before. To diagnose whether it's a hardware problem, your only bet would probably be to flash a clean firmware. Maybe someone will have heard of this though.
Click to expand...
Click to collapse
thx mate for suggestion seems like its only me having this problem, so far has been flashed 2 custom roms, and problem persists, i think need to flash it back to old GB stock rom to compare it.. sadly warranty period has expired, hope its not related anything with hardware issue..
davidncs11 said:
thx mate for suggestion seems like its only me having this problem, so far has been flashed 2 custom roms, and problem persists, i think need to flash it back to old GB stock rom to compare it.. sadly warranty period has expired, hope its not related anything with hardware issue..
Click to expand...
Click to collapse
Try a stock firmware, that should tell you whether or not it's a hardware issue. If it isn't, it's probably kernel related. Hopefully you can figure it out!
i have got the same problem too.. =(( how to fixed it.. the screen keep blinking...
Flash stock firmware . Then if its fixed pls report here.
BHuvan goyal said:
Flash stock firmware . Then if its fixed pls report here.
Click to expand...
Click to collapse
I've flashed from 2.1 to 2.3.6 and still it's blinking
Does anyone know how to fix it?
same issue
hi,
i have the same issue as well with 2.3.6, BaseBand version I9000XXJVU.
It is not a stock rom and it started appearing just a few days ago. It happens when i plug to charge it and after unplugging it. I have not noticed when it stops.
A friend of mine has the same issue, but with 2.3.4 stock firmware, so i think it is not firmware related.
Any new info on this? what could i provide for further troubleshooting
Main issue is of course that it drains the battery quite much and also allows you to mistakenly unlock the phone when the screen is on, so i was forced to put patter or PIN lock.
Cheers...
avatarz_bg said:
hi,
i have the same issue as well with 2.3.6, BaseBand version I9000XXJVU.
It is not a stock rom and it started appearing just a few days ago. It happens when i plug to charge it and after unplugging it. I have not noticed when it stops.
A friend of mine has the same issue, but with 2.3.4 stock firmware, so i think it is not firmware related.
Any new info on this? what could i provide for further troubleshooting
Main issue is of course that it drains the battery quite much and also allows you to mistakenly unlock the phone when the screen is on, so i was forced to put patter or PIN lock.
Cheers...
Click to expand...
Click to collapse
If you have ChatOn app try to uninstall it. Did work for me. (I my case the issue appeared when the internet was accessed via any browser. Same blinking pattern though)

Do any ROMs fix the shutdown problem?

I tried to search but alas Tapatalk isn't very good at that.
I bought a Captivate via eBay. Before I press to return it, is there a fix or ROM that fixes the dreaded random shutoffs? I tried resets and the GB Serenity ROM but alas I'm still encountering it...rather frequently. Every hour or less it'll shut off. So, other than the battery draining Captivate Keep Alive app...is there a real solution?
barring anything physical with your phone .. I have not had any sleep deaths or random reboots since switching to Fusion-CM-ICS-beta. It used to be a chronic issue with my phone.
Thanks for the fast reply Garyth. I'll give it a go.
I've heard the aosp roms seem to help the problem (this includes the ICS roms). They use different drivers than Samsung roms.
So far, so good. Data is consistently faster as well. Thanks again!
Hmm. Still getting random yet pervasive shut downs.
I believe this was a known hardware issue as well. There is a thread around somewhere will effected build numbers.
I saw that thread and don't believe mine is in the range. I'll be calling the seller tomorrow anyway.
Not sure if you are in the same boat as me, since the IMEI of my phone does fall into that catergory of the "recalled" phones, but since it was out of warranty by the time I saw that post, they wouldn't exchange it at the store.
At any rate, here's what I've gone thru:
Back in the Froyo times, I "think" CM7 fixed the issue, but I was too fidgety at the time so I was always trying new roms so I don't remember 100% if that was true or not.
I read somewhere that this could be caused by the battery shifting around due to temp changes as it charge/discharges, and that you should put some electrical tape or whatever to make sure your batt. made good contact. Didn't work for me at all.
So finally what fixed the problem was Captivate Keep Alive app, it's in the market.
First I tried it with two ICS roms: ICSSGS and Fusion, with Platypus and IcyGlitch kernels. The app work fine with a setting of 85%, but I was getting "charge death" as well, which I've never had before.
So now I've rolled back to KK4 (Serenity ROM) with the latest Corn kernel, and for some reason I have to set the app to 80% charge but works.
There'll be definitely an increase in battery drain, but for me it hasn't been that bad.
I used to have that problem when I first got my cappy, had froyo KB1 on it, and it would randomly shut down. Eventually when I got into hacking the android, when I finally updated to newer bootloaders, the problem went away. Though I can't recommend flashing bootloaders, since you can hard brick your phone if unsuccessful. Just saying that's what seemed to solve the problem for me.
mrhaley30705 said:
I've heard the aosp roms seem to help the problem (this includes the ICS roms). They use different drivers than Samsung roms.
Click to expand...
Click to collapse
Can anyone confirm this?
crt60 said:
I used to have that problem when I first got my cappy, had froyo KB1 on it, and it would randomly shut down. Eventually when I got into hacking the android, when I finally updated to newer bootloaders, the problem went away. Though I can't recommend flashing bootloaders, since you can hard brick your phone if unsuccessful. Just saying that's what seemed to solve the problem for me.
Click to expand...
Click to collapse
But what bootloader fix that to you?
Mine only rebooted randomly once when on eclair. Haven't had a problem in gb or ics.
Posted from my ICS'd Captivate
That would help if eclair wasn't completely useless.
Sent from my Samsung Captivate running Team ICSSGS 4.0.3
I tried Captivate Keep Alive. Even it didn't work. A replacement phone is on its way. The IMEI was actually affected, but I didn't realize at first because I only looked at the last digits. Apparently was a really early build. The seller photographed the new IMEI before shipping it out so I could verify.
I have Dark Knight's 4.0.4 ROM since 2 weeks ago.
At the moment, and I hope it remains 0 reboots.
Just wanna share with you, is up to you to try it....
http://forum.xda-developers.com/showthread.php?t=1501615
By the way, with this ROM also I got the best Quandrant Benchamark score (2400) without overcloking...
I'll keep that in mind but I got a replacement that works really well. I ended up getting it from another seller though.

Audio completely nonfunctional.. Should I return?

I just got my One a week ago today, and rooted it the first day as well. From last Wednesday to earlier today, I've had no issues at all with it; suddenly, audio is not working at all, either through the headphone jack or speakers. I thought it might be a ROM issue, so I reflashed the ROM clean (PACMan 4.2.2), and it still didn't work. I flashed 2 other ROMs, SlimBean and a Sense 4.2.2 based one, and the audio still doesn't work at all. I've done nothing that could've damaged it; I don't overclock, it's never gotten wet, nothing. Has anyone else had this issue, and know a fix, or do I have to return it to stock and turn it back into Sprint?
Also, another note- earlier today it was getting really hot for no reason- I wasn't running anything that would do that, no OC like I said. I Googled, and many people said it was a common occurrence due to the aluminum body dispelling heat from the internals. It went away after 20 minutes or so, so I figured it wasn't an issue. Could that have done some damage? Thank you for any help in this, I'm really worried since I just got the phone and it's already having issues. I've loved it otherwise so far, and owned 3 other HTC phones, and nothing like this has happened before, so I hope it's just a one time thing.
I don't have the audio issue with any rom I flashed, maybe your device is damaged. You can return it for a new one.
I also have the heat problem...
sent from my m7spr using tapatalk 4
I've been backing up my stuff to get it ready to take back. I hear the blue model's coming to Sprint on the 10th, maybe I can hold out a few more days and pick up one of those
Update- I've been trying all morning to restore to stock, and I'm getting worried now.
I went by this thread http://forum.xda-developers.com/showthread.php?t=2250904 to use that RUU to return to stock. I am trying to relock my bootloader in fastboot, and I get the error "[Err] Command Error!" each time I try. To use the RUU, I need to have a locked bootloader, but I can't get a locked bootloader because of that error. What might be wrong here? I am using the stock USB cable with a USB 2.0 port, Windows 7 32 bit.
Alright, it turns out that was due to a stupid error on my part. I have got my bootloader relocked, but now when I try to flash the RUU, I get the 171 USB Connection error. It'll get stuck on the black HTC screen at that point. What could possibly be wrong now?!?! If anyone has any tips, I can provide as much further information as you may need.

No network and "com.htc.htcdialer is not responding."

Hello!
I had purple tint on my old HTC One, so I sent it for repairs under warranty and I got a completely new unit. It was working for a day, but today it couldn't connect to the network. At first I thought it was a HW issue, but I realized that Dialer was crashing with a message: "com.htc.htcdialer is not responding.". That made me think it was a software problem, so I tried doing a factory reset in HBOOT, but now htcdialer is still crashing, and I can't even go through initial setup, it just keeps rebooting when I try to unlock it for the first time. Is there any other way to flash a ROM, without being able to boot the phone?
Everything is completely stock, bootloader is locked and phone is not rooted. I updated it to the latest available version, 4.4.2 with Sense 5.5, I'm unsure what version it exactly is. I would like to keep it stock for at least a couple of days in case there is a hardware failure and I have to send it back to service, but I can do anything if it's necessary.
Thank you very much.
HBOOT image, if it is of any help: http://i.imgur.com/3XKC6Br.jpg?1
Since its completely stock and you just got the phone, I wouldnt bother going through and installing a custom rom, its too much of a hassle and if it ends up being a hardware problem its an even bigger issue.
I'd contact HTC again and see if they can do anything about it, or just send it back again under warranty. Flashing a custom rom in your situation isnt worth it imo.
Bhavpreet said:
Since its completely stock and you just got the phone, I wouldnt bother going through and installing a custom rom, its too much of a hassle and if it ends up being a hardware problem its an even bigger issue.
I'd contact HTC again and see if they can do anything about it, or just send it back again under warranty. Flashing a custom rom in your situation isnt worth it imo.
Click to expand...
Click to collapse
That's exactly what I've been thinking.
I was actually able to get it to go through initial setup between reboots and I was able to install a RUU, a the same thing is happening again, so I'm pretty sure it's HW related. And it still isn't getting any signal. It's a bit of a problem because I have to bring it to a store 150km away, but I'll have to do it :crying:
[email protected] said:
That's exactly what I've been thinking.
I was actually able to get it to go through initial setup between reboots and I was able to install a RUU, a the same thing is happening again, so I'm pretty sure it's HW related. It's a bit of a problem because I have to bring it to a store 150km away, but I'll have to do it :crying:
Click to expand...
Click to collapse
Ahh that sucks. Call them and make some excuse about how you cant come to the store and see if you can ship it to them.

Wifi stuck trying to turn on.

Has anyone ever encountered this problem? I tried restarting the tablet and powering off completely. Nothing has worked. The last time it happened i deleted some random 3rd party apps and it magically switched on. But i havent downloaded anything new and my tablet is very close to original. It is the 9.7 inch us cellular version. I want to check for an update but without wifi, i cant do much. Thanks in advance for any pointers.
Had this problem with the 8 inch version. Shutting off the Samsung power saving app resolved ot for me. Look at my post history, it should be a recent thread that I started where I documented what to turn off. YMMV.
Thanks for the suggestion. The wifi magically was on again today. The only thing i had done was took the sim card out, rebooted and left it sit. Wifi did not come on initially so i dont know how long it took but hopefully it keeps working
Well it quit working again after rooting and flashing a custom rom. Ive read the wifi chip could have a bad solder. Anyone else have any input?
bowhunt2005 said:
Well it quit working again after rooting and flashing a custom rom. Ive read the wifi chip could have a bad solder. Anyone else have any input?
Click to expand...
Click to collapse
I would flash back to complete stock before making any assumptions.
WiFi is highly dependent on the device firmware.
ashyx said:
I would flash back to complete stock before making any assumptions.
WiFi is highly dependent on the device firmware.
Click to expand...
Click to collapse
Ive actually flashed back to stock and same thing. Thanks for the suggestion.

Categories

Resources