Installed CyanogenMOD and it still resets, locks up and has other performance related issues.
I did an OTA update to Marshmallow originally. This corrupted my SD card and then caused about 10 resets a day, ranging from when I was using it lightly to heavily or even when it was sleeping/screen off. If I woke it up it would reset or I could feel it reset when it was in my pocket.
First thing I did was a factory reset. I tried other tricks such as swapping out the battery, SD card (or none at all), clearing cache, etc.... Nothing worked. So I tried installing CyanogenMOD, and I failed. But I got the phone back to BPA1. I updated back to marshmallow via my computer and the Verizon software updater.
About a day later the resets and lockups came back. I kept it light of apps but did slowly begin to reinstall some of my usuals (from the play store).
I had some more time so I tried installing Cyan again and was successful. It took a long time to load and optimize but it worked. I used gapps mini and the only step I did not follow in the guide was I did not install xposed.
It's been running for about 12 hours and has hanged, locked up and rebooted on me multiple times. Chrome even locks up (it will stop resounding, I'll get the message asking if I want to wait or close at the same time it starts responding again.)
When it reboots, it still takes forever and even optimizes apps (that I assume have already been optimized). I've seen two boot screens for it, one the little alien guy and the other with gears turning. It did the gears the second time I booted and then I haven't seen them again.
I'm not sure what my next step should be. Maybe I'll try reflashing Cyanogen. I have a feeling it's a hardware issue at this point, but I'm open to ideas. Are there any good diagnostic tools that could help my situation?
The phone is out of warranty and I'm sure that now that I've installed Cyanogen, the warranty was voided anyway. It's a shame because this phone was perfect up until the marshmallow update. I probably had 5 lockup/boots in the year or two I've had it.
Why are you using cyanogenmod in the first place. The support for that has ended. Go to the lineage os nougat thread and use that instead.
HORIZONx720 said:
Why are you using cyanogenmod in the first place. The support for that has ended. Go to the lineage os nougat thread and use that instead.
Click to expand...
Click to collapse
Admittedly, I did not even know about lineage until my phone was wiped with no OS. I did a quick Google search for it but could not find a Verizon note 4 mod. Now that I am not pressured to find a fix, I'll research it a bit more. Thank you.
I tried EmotionOS and NSeven, but both share the same error.
Emotion FCs random processes sporadically and then when my cell/data switches to Searching, it crashes multiple processes until the UI (trebuchet is default for Emotion?) and/or settings FCs and I have to restart. I am also stuck on 3G on that platform. I'm guessing network connectivity / switching is the root of the problems.
Nseven installed and right at the Welcome Screen where I pick my language, Google Play Services started crashing. I only had the option to click OK and then every 5 seconds after that, it kept crashing. I set up the phone, restarted and Google Play Services started crashing again. I am in the process of restoring back to Emotion, as it is the most stable platform so far.
I tried a new SIM card, hoping this was the problem but to no avail.
Does anyone have any other suggestions? I'm guessing its hardware at this point, but since it happened on an OTA Update and I can reproduce the same errors every time, I'm hoping there's still an option left for a fix.
Holy crap. As I was typing this and restoring Emotion, it fully installed and booted. I have 4G! I don't know if that will fix the FC issues, but I have regained a little hope!
I'm still getting FCs and restarts. The more I use it the more it happens, but at least with EmotionOS, It's more limited. Only about 3 or 4 a day compared to 10-20.
I'll try one more flash and I guess tough it out until my contract is up in April.
I can't help you with EmotionOS (haven't tried it yet), but if you want to stop the Google Play Services crashing in NSeven you can make your way to Settings - Applications, then select Google Play Services - Permissions and give it all permissions. It's a bit of a chore to get there when the warning pops up every five seconds, but it will stop once you do that.
So my plan is up and I'm probably switching away from Samsung after this incident. Looking into the pixel or XL. If the v20 is out for Verizon, I might get that but I'll see what looks good when I go to the store today or tomorrow.
I think I've narrowed down my issue to a heat issue. I fixed the 4g and Google play crashes but my phone still locks up or apps start a cascade of crashes. If I power down, I can't restart the phone. If I restart, it powers down but does not turn back on. I remove the battery for 10+ seconds, put it back in for 10+ seconds and it won't turn back on. I'll leave the battery out for minutes to an hour and its a crap shoot.
I can only boot normally or to download mode. TWRP no longer loads. I tried reflashing it and I get a no pit fail. I'd probably look into fixing this but at this point it's not worth it.
What I discovered works is putting the battery and phone on a cool surface, putting the battery back in and placing that on a cool surface and then try to boot up. However, neither my phone nor the battery feel warm to the touch. So that indicates to me something is either off in the sensors, preventing it from turning on or more likely it's a power issue or at least a hardware issue, preventing a constant current or something along those lines. Dips in power could explain apps crashing and the system inexplicably turning off. It would also explain why I can't turn it on easily.
It's really a shame because I liked this phone so much and if the new note was out, I might give it the benefit of the doubt. But last night my Samsung tablet decided to install the updates I've been putting off because they're the same ones that broke this phone. So timing wise, I'm done with Samsung and will try a new brand. Only issue I see with pixel is it doesn't have a removable battery so hopefully I don't run into this issue on that device!
Thanks for all the help xda. If it was a solvable problem, I'm sure I could have fixed it with your help.
Final entry.
I got the v20, and spent a day trying to get my note back to factory. I thought I was doing something wrong, but eventually flashed a kernel, recovery, bootloader and then full Rom (I think it was BPA1 but it could have been CPF3, I don't have it in front of me). I was getting error after error, no PIT partition, mmc check fail, use the Samsung Recovery Assistant, and a few others (again, it's not in front of me so I may have gotten it wrong). The big one was a write disk failure when I was trying to flash the full Rom. I fixed that by flashing kernel, bootloader, recovery, then sticking the battery and the phone on the freezer for ~5 minutes before trying to flash the full Rom.
I updated via USB after that using recovery assistant. Probably completely unnecessary, they just needed to get to the factory reset screen, but when I bought my phone, I couldn't trade in the note because i couldn't turn it on. They gave me $86 for it. Anything less and i would have considered just taking a hammer and microwave to it. Good riddance!
Still a little sad, I loved this phone right up until marshmallow dishonored and killed her.
trickyvinny said:
Final entry.
I got the v20, and spent a day trying to get my note back to factory. I thought I was doing something wrong, but eventually flashed a kernel, recovery, bootloader and then full Rom (I think it was BPA1 but it could have been CPF3, I don't have it in front of me). I was getting error after error, no PIT partition, mmc check fail, use the Samsung Recovery Assistant, and a few others (again, it's not in front of me so I may have gotten it wrong). The big one was a write disk failure when I was trying to flash the full Rom. I fixed that by flashing kernel, bootloader, recovery, then sticking the battery and the phone on the freezer for ~5 minutes before trying to flash the full Rom.
I updated via USB after that using recovery assistant. Probably completely unnecessary, they just needed to get to the factory reset screen, but when I bought my phone, I couldn't trade in the note because i couldn't turn it on. They gave me $86 for it. Anything less and i would have considered just taking a hammer and microwave to it. Good riddance!
Still a little sad, I loved this phone right up until marshmallow dishonored and killed her.
Click to expand...
Click to collapse
I know a lot of people are blaming software, but I'm fairly certain that the problems in many cases are caused by failing hardware. I went through many of the same trials and tribulations with my Note 4 (except I never rooted the phone). I finally contacted Samsung Customer Support and sent the phone in for repair. They replaced a lot of the hardware including the motherboard and returned the phone in "like new" condition. I've been using it for a few weeks now and the performance is flawless.
I was planning to get either the V20 or the G6 if I wasn't able to get the phone fixed. How do you like the V20?
I'd agree that it's most likely hardware and having to put everything in the freezer for it to when confirms it for me although I have no real expertise to say so. But I'd argue that the update created the hardware issue, it was night and day with the update. It was working 100% and then directly after the update to marshmallow, it started having catastrophic issues. Oh well, it's nice not having to pull the battery every hour or so.
V20 is pretty nice. Having used EmotionOS for a few months the switch to the Nougat was pretty smooth. The xda forums for it are a little more limited but I didn't start messing with my phone until it broke and I'm hesitant to try with a new phone given my limited knowhow.
To be honest it's not a big difference in day to day usage from the note 4. Which I like!
+ I never used the finger print scanner but really like it on the v20. I didn't bother with a screen lock before but now I'm protected and have a just as quick access.
-the grip is too slick, I feel like I will drop it. The note had that rougher back which I liked better. A case or a replacement cover should fix that though.
+ I like this top menu screen, I have quick access to a few select apps or can turn the flashlight on or whatever. I'd like it more customizable, I find I switch screens too much when trying to just pull my top menu down. If I could put everything on one tab and combine their special buttons (ie the flashlight button) with apps, it would be perfect.
-the back button and menu button are switched. I can probably customize that but I don't yet know how and by the time I figure it out, I will have relearned that habit. It actually is probably a better placement for how I hold the phone but I'm a big fan of choices.
+ upgraded camera, sound, storage. I don't notice the screen size difference, but it is a lighter phone.
-bloatware
All in all its a good shift from the note 4. I'm happy to be off of Samsung and still have the same basic user experience.
trickyvinny said:
So my plan is up and I'm probably switching away from Samsung after this incident. Looking into the pixel or XL. If the v20 is out for Verizon, I might get that but I'll see what looks good when I go to the store today or tomorrow.
I think I've narrowed down my issue to a heat issue. I fixed the 4g and Google play crashes but my phone still locks up or apps start a cascade of crashes. If I power down, I can't restart the phone. If I restart, it powers down but does not turn back on. I remove the battery for 10+ seconds, put it back in for 10+ seconds and it won't turn back on. I'll leave the battery out for minutes to an hour and its a crap shoot.
I can only boot normally or to download mode. TWRP no longer loads. I tried reflashing it and I get a no pit fail. I'd probably look into fixing this but at this point it's not worth it.
What I discovered works is putting the battery and phone on a cool surface, putting the battery back in and placing that on a cool surface and then try to boot up. However, neither my phone nor the battery feel warm to the touch. So that indicates to me something is either off in the sensors, preventing it from turning on or more likely it's a power issue or at least a hardware issue, preventing a constant current or something along those lines. Dips in power could explain apps crashing and the system inexplicably turning off. It would also explain why I can't turn it on easily.
It's really a shame because I liked this phone so much and if the new note was out, I might give it the benefit of the doubt. But last night my Samsung tablet decided to install the updates I've been putting off because they're the same ones that broke this phone. So timing wise, I'm done with Samsung and will try a new brand. Only issue I see with pixel is it doesn't have a removable battery so hopefully I don't run into this issue on that device!
Thanks for all the help xda. If it was a solvable problem, I'm sure I could have fixed it with your help.
Click to expand...
Click to collapse
I have had the exact same problem with my note 4. It wouldn't last 30 seconds at a lock screen from a cold battery before it would start boot looping, and the longer you left it in, the worse it got. Google told me I needed a new battery from several other forums and places I read. So I ordered one and replaced with a genuine Samsung one direct from them, and it didn't change anything.
I figured out it was heat related and I had it sit on an ice pack and it would run and work fine as long as the ice pack held out, about 2 hours. I've down graded, flashed, rooted the boot loader, installed a recovery console, flashed to different versions, all have the same problem. So I've kind of reserved myself to the fact it must be a hardware problem. Perhaps it was caused by the update, but nothing software change wise seems to be able to fix it. Did wake-loc fix as well. I've spent the last week with mine trying everything in the world and every evening having it on the ice pack hooked up trying whatever I could think of or read up on doing, and basically as soon as it warms up, it starts doing it again.
Heres a pic; http://imgur.com/a/5L64V
In my experience, it gets worse and worse. The day I bought my v20, I tried to trade it into Verizon but couldn't even turn it on in front of the rep. I thought I had timed the new phone perfectly but still wanted the $80! Fortunately I got it working after the weekend and just stuck everything in the freezer before I walked to Verizon.
trickyvinny said:
In my experience, it gets worse and worse. The day I bought my v20, I tried to trade it into Verizon but couldn't even turn it on in front of the rep. I thought I had timed the new phone perfectly but still wanted the $80! Fortunately I got it working after the weekend and just stuck everything in the freezer before I walked to Verizon.
Click to expand...
Click to collapse
Just out of curiosity, what phone did you wind up going to?
The LG v20 and so far so good!
Related
Within the 14 days return policy I took my Galaxy back after it bricked for no reason. I was almost stock other than unlocking it and running ADW. Too many things wrong with them so I gave it one more chance with a replacement. The new one has a working recovery/download mode so that's the biggie for me. The lag seems better and the GPS actually works. Great, I feel better. But I decided that I won't root it yet since 2.2 is coming soon. I'll let it flash as designed before digging deep.
Yeah, right. After noticing that the WiFI is still flaky at random times I turned it off again today when it wasn't passing any data. 3G still working so fine. But then the Market started to FC which I've not seen at all. I shut it down and rebooted again which is the fix for my WiFI. Well, it once again decided to brick just like the last one. I get past the logos and then just a black screen. She's bricked and I didn't even root it this time. Only thing not stock was ADW launcher instead of the Samsung thing that I don't like.
So I put her into recovery mode and did a factory reset. That fixed it and I setup all over again. Luckily with 2.1 you get a list of all your previously installed apps in Market the first time you enter so if you don't leve the app you can quickly install everything again. 20 minutes later I'm back in business except this time I'll stick with the launcher it came with, can't think of anything else that would cause this sudden bricking other than the wonder phone might be a piece of crap. I just don't know yet.
By reading the title I thought you meant that Samsungs new update to activate the 3 button combo had saved you. Having a phone with download mode enabled is quite hard to brick, you can always just put it into download mode and reflash with Odin.
That's the point, my replacement phone came with the update that Samsung is pointing people to. Labeled the same as the previous update but indeed has the button thing fixed. Until the next update comes along I'm not touching Odin or anything else, these phones have enough troubles as it is. I'm still concerned that mine bricked again simply by turning it on.
3rdcoast said:
That's the point, my replacement phone came with the update that Samsung is pointing people to. Labeled the same as the previous update but indeed has the button thing fixed. Until the next update comes along I'm not touching Odin or anything else, these phones have enough troubles as it is. I'm still concerned that mine bricked again simply by turning it on.
Click to expand...
Click to collapse
This is just my opinion but I don't think the phone would have come with the update, it would have just been an untainted unit that didn't exhibit this problem. Only a subset of new units were lacking the download and recovery modes and the fix released a couple of days ago was designed to correct that problem.
These modes are a standard feature of pretty much any Android device.
At any rate, good to hear that you have a fully functioning unit out of the box. I had to go to some length explaining and demonstrating the issue to the store from which I got my unit lacking these modes as well as my carrier until the fix came out and I fixed it myself.
I don't know either. I based my guess on the fact that Sam's fix happened to be an update that version matches what mine now shows. And my situation is a prime example why all phones need this mode. Not everyone would fix it the way I did but it only cost me 30 minutes and a few curse words because my pictures are all gone before I could get them off but I'm back up and running and that had to save somebody a few hundred dollars.
I'm still very nervous though, it did brick this morning without me doing anything. This time I don't even have NoLED or ADW but I can't leave it that way forever. My trusty Magic is way more tolerant of OS abuse.
From searching, it looks like tons of people are having random reboot issues with the HTC EVO. Let's make one thread to put everything so maybe we can figure this out.
Side note, it looks like the HTC desire has the same issue:
http://forum.xda-developers.com/showthread.php?t=676402&highlight=rebooting
So post what you've tried that hasn't worked.
If you think you have a solution, share
One thing I've noticed is it seems heat related.
I've installed temperatures monitors and it seems around 32 degrees Celcius is around when it reboots. It will reboot loop usually. This can be cured by pulling the battery and waiting for it to cool down, or just put it in the freezer for 4-5 minutes.
I've tried underclocking it with the screen dimmed way down, and running it without the back cover and it still overheats.
For me, the problem came out of nowhere. I had the device for over a month with heavy usage and no problems. My current GUESS is it must be a physical problem. Not enough thermal grease or something...
It looks like the HTC Desire users may be getting replacement motherboards to fix their issue.
Does the HTC EVO and Desire share parts?
From other threads it looks like:
Root or Stock - Doesn't matter
Radio version - Doesn't matter
Rom version - Doesn't matter
GPS Fix - Doesn't matter
GPS turned off - Doesn't matter
3G data, 4G data turned off - Doesn't matter
Hard Reset - Doesn't matter
Found this on the HTC Desire reboot thread:
Latest test list for HTC Desire RR (Random Reboot) problems:
-All phones with s/n HT03 to HT07 can get this problem (Minor problem from SH09 so far)
-Starts around 1.5 to 3 months after use
-Reboots get worse over time
-Firmware and android version doesn’t matter which you have
-Force apps2sd doesn’t matter if you use it or not
-PVT1 or PVT3 or whatever doesn’t matter
-Screen type, doesn't matter if you have AMOLED or SLCD
-There seems to be an antenna/radio/simcard issue also
-Overheating causes reboots too
-Reboot is not always temp related
-SD card size doesn’t seem to matter
-Having apps on SD or not doesn’t matter
-Size of files on SD doesn’t matter
-Rooted or not doesn’t matter
-Motherboard changed after repair doesn't always fix it
-Sim locked or not doesn't matter
-Provider doesn't matter(vodafone, kpn/hi, T-mobile etc all got it)
-Most likely hardware issue, sense flashing won’t fix it, yet changing motherboard will
-Restarting doesn't fix it
-Factory resetting doesn't fix it
-Changing/buying new battery Doesn’t fix it
-Using app killers or shutting down some services yourself doesn't help
-Leaving all settings on default doesn't fix it
-Plugged into car charger in the past doesn’t matter
-Hboot version probably doesn't matter (still not fully tested)
-Having a phone cover or not doesn’t matter
Click to expand...
Click to collapse
wifes phone has been doing it very bad...one that has never been rooted...
was going to root it and try new rom but seems to be a hardware issue.
any other comments on this subject?
My stock rooted Rom just rebooted for the first time today. I really don't rememebr what I was doing st the time....but this has never happened before. I assume there's no event log to check.
Sent from my PC36100 using XDA App
I had been facing this with increasing frequency. I got the phone on launch day, and the problem started over the last month, getting worse all the time. I agree with the OP that there does not seem to be any obvious cause -- sometimes it is heat related, sometimes not. Any time I push the phone (run psx4droid, or navigation + anything else), and sometimes even with lighter usage, like on a phone call. Unrooting did nothing to stop the problem.
After extensive searching, I found three possible causes: bad battery (I tried a new one and the problem continued, but this seems a good starting place), bad memory blocks, or bad processor.
I was unable to find any solution to this problem. I took my phone to Sprint today, and they told me that their tests didn't show a problem. Then I made it happen in front of them (launch navigation to anywhere, then a couple more apps, then boom, reboot) a couple times (really, after the first time, letting it turn back on pretty much caused it to happen again).
After that, they agreed to replace it. I do have the TEP, but they assumed that the problem was hardware related so I don't know if you have to have it for them to replace it.
Strangely, they gave me a white one as a replacement.
I haven't had any problems with the new (well, re-manufactured) one, and I hope it stays that way, but I guess only time will tell.
I'm currently experiencing the problem as well, funny thing is every time it happens, the phone is NOT in use, simply sitting on table or desktop in standby. This happens about once every two days.
Currently running rooted evio2 1.3.1
Wow, I was about to start this thread, when I saw this. I guess I was like 10 minutes late. Either way, i believe something messed with the hardware. My little bro cracked my screen badly, so I am getting a new evo anyway, but will I be able to get one free bcuz of this? This is really a terrible problem. Somebody needs to de-assemble their precious evo and see if there is an obvious problem. thanks a bunch. Subscribing.
same here.
happens mostly when on the charger and i am using it at the same time. so heat related seems likely.
can anyone get a logcat of it happening?
I called sprint support and they said it's defective to return it.
Taking it in for replacement today.
Sprint replaced mine for $35 [a refurb]. That's the end of that.
But now, I can only use the speaker to hear my callers. Gotta go back and get another!
My guess is the new update could be putting a lot of strain on the battery but who knows? I haven't experienced it but maybe its because I'm using the extended mah 3500 seido battery.
Sent from my PC36100 using Tapatalk
thlinx said:
My guess is the new update could be putting a lot of strain on the battery but who knows? I haven't experienced it but maybe its because I'm using the extended mah 3500 seido battery.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
No, I've got the 3500mAh Seido battery too.
I don't think it's strain since mine has gotten worse. AKA the amount of usage it take to make the phone reboot has gone from hours of use to minutes.
.jond said:
No, I've got the 3500mAh Seido battery too.
I don't think it's strain since mine has gotten worse. AKA the amount of usage it take to make the phone reboot has gone from hours of use to minutes.
Click to expand...
Click to collapse
Actually I just had a reboot lol.
Sent from my PC36100 using Tapatalk
Same thing here. I posted my issue in the rom threads i used, and everyone ignored the issue, lol.
For me, I noticed it about a week after using roms with the new software update (3.29). It happened with navigation, launching multiple apps, running quadrant, etc.
So yesterday I installed DC 3.5 from scratch, turned nav on and let it sit for a couple of hours. NO reboots. Before, after 10 mins of the screen and nav being on, I'd get a reboot. Has anyone else tried this (or willingly to try it)? I switched back to my nand backup, ran quadrant -> bam, reboot.
I bought my EVO on launch day (HW Version 002), and have not had any problems until around Oct 13.
I took the phone on a trip to Orlando, and as soon as I got off the plane and turned on the phone, the problems started happening. It has been happening ever since, even since I returned home.
I bought my phone at Best Buy, and have had their Geek Squad send it back to try to fix it. I also added the complaints about screen separation to the workorder so that they would be more likely to replace the device. Hopefully, this fixes the issue.
I also think it is heat related, but I don't know why it is just now becoming an issue. Just to make sure the folks at BB could see the issue happening, I put the phone in front of my car's heater for a few minutes, then started up Google Earth, and was able to make the phone start boot looping while I walked into the store.
I tried hard reset, soft reset, update prl, underclocking, GPS Reset, new battery, new SD Card, and none of those things worked. I wonder if the removal of the 30 fps limit in the last update caused some type of heat damage?
I just had a reboot last night while trying to look at a picture I'd just taken in the Camera app on CM6.0.0. Only the 2nd or 3rd time it's happened. Still annoying though. Hope it doesn't get worse.
.jond said:
I called sprint support and they said it's defective to return it.
Taking it in for replacement today.
Click to expand...
Click to collapse
How much they charged you?
Sent from my PC36100 using XDA App
MedSchool26 said:
Same thing here. I posted my issue in the rom threads i used, and everyone ignored the issue, lol.
For me, I noticed it about a week after using roms with the new software update (3.29). It happened with navigation, launching multiple apps, running quadrant, etc.
So yesterday I installed DC 3.5 from scratch, turned nav on and let it sit for a couple of hours. NO reboots. Before, after 10 mins of the screen and nav being on, I'd get a reboot. Has anyone else tried this (or willingly to try it)? I switched back to my nand backup, ran quadrant -> bam, reboot.
Click to expand...
Click to collapse
I reset mine back to stock. Unrooted it and everything.
Didn't fix the issue for me.
Now I did try erasing all the stuff that's erasable inside recovery and it seemed to go a few days without a reboot. Not sure if that was a fluke or not.
Hello dear friends!
HTC let me down Kind of stupid phones indeed at least desire...
I have my phone for quite a time now, it is rooted with unrewoked, clockwork recovery and s-on. I flashed many different roms in the past and everything was brilliant. In a pas half-a-year or so I stayed with only one ROM - MIUI-Au. I kept updating it to the newer versions and so on and on. Never had any random reboot or something. At least maybe it was because of some strange app or something else. But now it started to reboot randomly and constantly!
Phone gets hot abit and it just reboots, and never comes to android homescreen again, until I put out the battery, hold it for few minutes, pop it back and then it boots. But as soon as start to play music, or run a game the phone gets hot abit and reboots again. and so on and on. I thought maybe it was a miui issue. So I tried to flash different roms, but guess what? None of the even boot! The main screen shows and with the same second it bootloops again and forever!... (
Even from recovery it sometimes reboots randomly. So i managed somehow to flash my miui back and it at least boots. But it is very unstable now, I barely can use my phone now
PLEASE WHO CAN HELP ME????
My warranty probably out of date, and my phone is rooted, I dont think HTC would accept it...
any thoughts? friends?
What have you set the CPU max to?
Sent from my HTC Desire using xda premium
Thank you for response! Appreciate, really!! I didn't set it, I left everything by default I think! Because as i said, i even tried flashing different roms, not only miui.
What else could be? By the way, with stock froyo rom If I remember correctly, sometimes it became extremely hot, but I didnt get any reboots from that. But now, it gets just a little bit hot and it seems that this causes the reboot...
Now what I just noticed, I get reboots even when the phone is idle. And it is not even warm!
If its not getting hot then I'm confused lol. It sounds like a actual hardware fault. Sorry I can't help with this one
Sent from my HTC Desire using xda premium
cluendo said:
My warranty probably out of date, and my phone is rooted, I dont think HTC would accept it...
any thoughts? friends?
Click to expand...
Click to collapse
try and get it taken back to stock if you dare.
The phone hasn't been out 2 years yet, which is how long the warranty is.
Thank you! But is there any possibility to fix it without HTC involvement? Maybe it is not hardware issue ? Can it be because phone is rooted and I flashed many roms to it ? I didnt try AOSP roms since reboots started, I will try to pop in Cyanogenmod or other and see if I will get reboots.
Would rerooting my phone and updating my recovery fix the problem?
and Note: yesterday I tried to S-OFF my phone, but I can't even do that with my unstable MIUI. It rebooted in the middle of the process..
I had a similar problem, apparently it's not uncommon on the early revisions. I sent mine to HTC and they replaced the mainboard.
Thank you for answer! But what if my phone is bought through a contractor?
Can just call HTC and ask the for repair? Or should I contact my contractor first ?
Just give them a call and they will try to help you out. I had a very good customer service experience with them when my desire had some issues.
They will require a proof of purchase though. If you managed to get the receipt from your "contractor" (I am unsure what you mean by a contractor), then there should be no problem.
Sorry for misleading word, I meant T-Mobile. I bought my phone under contract. I think I have a receipt. I even have whole box and stuff of the phone somewhere in my drawer.(just sayin ). So how is customer service of HTC? Poor, good ? I heard you need to tell them that you did a factory reset and that didn't help. Is that true. Also if I will unroot my phone, will they know it was rooted anyhow?
Ahhh....this overheating issue seems common. How they can release faulty phones?? No clue.
thanks for answers mates!
In Singapore, HTC service is really good. Phone was still under warranty.
It took me just one (real) call to confirm a repair order. The first call I was just checking to see what options were available to me.
The second call was an actual repair request. And the third call was me pestering them for a pickup date. heehee
In Singapore, repairs were done via courier. They picked it up and 1 working day later, they sent it back.
Naturally, you will probably need to impress upon them that you tried everything to fix your phone (which I hope you did which includes proving to yourself that it's not the ROMs fault).
You will definitely need to reset everything back to zero. In my case, I downloaded an RUU to totally reset everything back to STOCK, which included removing clockworkmod recovery. You WILL need to create a goldcard for this though so bear in mind that it's not exactly a case of a simple flashing procedure. At least not if you don't already have a goldcard.
Sorry if I overread it at some point, but you speculated at the beginning there could be some faulty app causing this, but you never meantioned performing a full wipe. Have you full wiped yet? Just to make sure it is indeed no software problem.
greets
Thank you for your answers. At the moment I have SuperNova classic ROM. ( 2.3.3 + Sense 2.1) But my phone crashes again and again, it is so annoying and causes me so much trouble.
I never tried a reset or unroot and return to original rom. Im just wondering now, would this help to remove or at least remove those reboots?
Today I was in my work and i was keeping my phone in my jeans pocket. it got hot as u would expect when keeping in pocket and suddenly it rebooten, then it went into a bootloop and started to bootloop 7 times in a row quickly. then again and again. It became very hot at that time.
For the interest, what exact hardware faults causes these reboots and why phone gets even hotter if you keep it on boot loop. If I keep phone cold, the rom usualy stays normal, without reboots. but as soon as I start using my phone, texting or calling for at least 5minutes of using it just reboots.
as I said- really annoying thing :S
I remember my happy times with miui, apps and no reboots Was fun!
cheers for helping!
I would give full wipe / factory reset a chance, and maybe RUU.
At least try it before sending phone to htc.
It is hardware problem, search forum. Fresh ROM without SD card, enabled WIFI and GPS, running G navigation, back of the phone is warm - restart after few minutes.
Maybe someone know how to read info form the phone right before reset? We could understand why the phone is reseting and hopefully add some patch.
Reboot-loop experience
Hey,
i had the same problem over the last few months: In the beginning my phone restarted only when it got hot, but it got worse over the last few weeks, in the end i was not able to use two apps at the same time (music and mytracks) or even to surf the internet longer than a few minutes. The problem did noticeably decrease when the phone was cool - tested by putting it on a fan or in the fridge. Yet, Skype was regularly killing it. As i really love my phone (and especially the AMOLED-Screen!) i did not want to resign. The battery cover contains some metal which is supposed to enhance heat dissipation - so i attached a little thermal pad to the hotter bottom of the phone to improve contact with the head spreader. Unfortunately it did not entirely fix the problem. Yes, it improved the situation a little, but it got even worse after a week or two - in the end i had to turn it in.
So i decided to take it to the Telekom-Shop. They were very kind and told me they would call the other day to confirm that the replacement would have been shipped. It took a few days longer, but i got a phone with the AMOLED-Screen! The employee said it was a used mainboard in a new case, completely refurbished. They only replaced the main unit, i kept the battery, sd-card, charger and so on. Now i have a working Desire again!
Terminator
Similar?
Hi i on the other hand have similar problem, qiute anoying one, my desire, cm7 hboot, s-off, insert coin cm7 rom, have phone freezing in diferent situations, sometimes its working sometimes just freezez and i need to get battery out and turn it one and sometimes several times in row to get it working again???? RUU and go to give phone in service? plaese advice?
@cp6ija Sandisk SD card? If yes, smash it.
nvm
cant delete post so just posting gibberish
Well, I'm at wit's end. I'm usually pretty decent at borking and consequently unborking a phone. But I think I'm stumped this time; and am hoping that the community here can help me out. Though, to be fair, I suspect that rolling back to my old phone and eventually buying a new one is my only recourse.
So I imported an H815 Open EU from Handtec UK. No real issues on that front. I eventually unlocked the bootloader, flashed TWRP, and used the KDZ method to (clean) flash my way up to Europe OPEN H81510D initially, and then around two months ago, to Europe OPEN H81510E. I've been running that software without issue since that clean flash. And all this time I've been rooted through the TWRP method.
While this is (was?) my first LG phone, it isn't my first Android experience. So I've been using TiBu to back up my apps nightly, was running Kickoff's lovely hybrid theme, and had a few Xposed modules activated to tweak my experience a bit from stock behavior. I was curious about Marshmallow, but autoprime's warning that it could be non-final test software and the fact that Xposed doesn't work on it kept me from indulging that curiosity.
Everything has been going swimmingly until today. No major issues that I couldn't solve on my own. Certainly nothing that booting into recovery and clearing caches didn't fix. I was out and about engaging in a chat via Hangouts with a friend when my phone suddenly crashed and black-screened. I wasn't plugged into the wall or my PC, and I hadn't performed any kind of major update since the 10E flash a month or two ago. I had not installed any new Xposed modules or any rogue Google Play store apps. I was just using my phone normally and it crashed.
I popped out the battery and played around with it, trying to get it to boot up. I couldn't access recovery or even get beyond the LG logo. It would just hang there and after a few seconds, black-screen. Only popping the battery out and reinserting it would allow me to try again. I eventually left it alone until I got home, at which point I figured I'd try for download mode and reinstall the 10E KDZ via a CSE flash. It's always been a last resort, but a reliable one. I successfully performed the CSE flash of the 10E KDZ.
I thought it did the trick, as I got past the static LG logo for the first time and saw the LG boot animation, but it hung towards the end of the animation and black-screened again. Tried a few more reboots. Recovery mode still not accessible. Download mode was only accessible every third or fourth attempt. Finally got back into download mode and figured I'd try to roll back to 10D (I still had the KDZ I had previously used saved, just in case). Everything seemed to start going fine. Download mode's circle arrow animation on the phone was doing its thing, and then I hear the USB connection drop out. The arrow animation hangs, and the phone black screens. LG Tool 2014 spits out an error I can't read (the software is all question marks for me at this stage). Before it black-screened, it appeared that download mode hadn't progressed beyond 0%.
Now the phone is completely unresponsive. Popping out the battery and reinserting shows no signs of life. No USB sounds from my PC. No static LG logo. No recovery mode or download mode. Not even the lonely flash of an LED.
I've never had a phone hard brick, but I imagine this is what it tastes like.
So I'm probably out of luck, right?
I apologize for the long story. Thanks in advance for sticking around.
Maybe a stupid question but still deserves to be asked, what does pluging the phone in a wall socket gives you?
Sent from my HUAWEI MT7-L09 using Tapatalk
that is strange to happen randomly. The same thing happened to one of my old devices, a 1st gen moto atrix after I dropped it. I can get it to boot up but eventually it acts like the battery is pulled and just reboots. I'm convinced some wires or chip has been damaged inside even though it was only a 2 foot drop on thick carpet... not a whole lot you can do off warranty. Good luck.
Yeah, I figured the phone was toast. Of course the only time I hard brick a phone, it'd be the one time I import one from another country. Alas.
I think I'll return to my Galaxy S4 for now and pick up a Moto X Pure in a week or two, if no other ideas or opportunities present themselves.
As for having the phone plugged in, I just mentioned it in passing in order to rule out a power surge or short or whatever. Just to be completely clear about what I was doing with my phone.
There are already a few other threads on this man. Try to read first and post. Probably it's a motherboard problem. See the date of manufacturing of your device.
I read completely through the first 5 or 6 threads I saw on bricks and was overwhelmed by Marshmallow woes. Mobo, huh? That's a damn shame. Thank you.
Up until this point I hadn't messed with this phone, it was stock all the way. About a week ago it started acting funny, slow, would freeze occasionally. Figured it was time to root and throw a custom rom on. But the probably seems to just be getting worse. The phone is practically unusable.
Recovery still works fine, still pulls up into ODIN no issues and flashes.
I've tried 100% stock flashes, I've done the OTA, I've tried the awesome Note 5 port going around, even the older ones. Have tried OK1, OB7. And now I'm flashing the MM Odin File. Like I said the flashing is going through perfectly every time. But after setup yet it just keeps freezing, and then immediately goes to reboot. Sometimes it even gets stuck in bootloop, have to pull the battery. A couple times it has went directly to Download and said "Cannot do normal boot" or something like that.
Is this phone done for? Like I said, sometimes it's unusable. For instance, I just went 4-5 hours with it performing flawless, and at this exact moment; I couldn't make a phone call if my life depended on it.
Any ideas/help is greatly appreciated. Would be happy to provide any more info.
Thanks!
By any chance are you using the fingerprint scanner for your lockscreen? I had a similar problem until I turned it off in favor of a pattern lock screen. No problems at all ever since.
No, just the typical slide screen. My first thought was an app, but it is so sporadic, plus it has even locked up during the setup menu after one of the flashes. Very strange.
Mine started doing the same thing a few weeks ago. Freezing then rebooting. SystemUI.apk crashing.
Fresh ODIN to latest. Rebooted during setup. Eventually my phone wouldn't power on last Saturday.
I'd recommend backing up your phone and prepare for it suddenly dying. I found a few posts on Reddit saying others had similar issues.
I took it back to Sprint and they offered me a refurbished Note 4, so far so good!
AVAH0LIC said:
Up until this point I hadn't messed with this phone, it was stock all the way. About a week ago it started acting funny, slow, would freeze occasionally. Figured it was time to root and throw a custom rom on. But the probably seems to just be getting worse. The phone is practically unusable.
Recovery still works fine, still pulls up into ODIN no issues and flashes.
I've tried 100% stock flashes, I've done the OTA, I've tried the awesome Note 5 port going around, even the older ones. Have tried OK1, OB7. And now I'm flashing the MM Odin File. Like I said the flashing is going through perfectly every time. But after setup yet it just keeps freezing, and then immediately goes to reboot. Sometimes it even gets stuck in bootloop, have to pull the battery. A couple times it has went directly to Download and said "Cannot do normal boot" or something like that.
Is this phone done for? Like I said, sometimes it's unusable. For instance, I just went 4-5 hours with it performing flawless, and at this exact moment; I couldn't make a phone call if my life depended on it.
Any ideas/help is greatly appreciated. Would be happy to provide any more info.
Thanks!
Click to expand...
Click to collapse
I had the same issue. the phone kept rebooting in to download mode. sometimes I would have to pull the battery for a few hours to get the phone to even start. I Replaced the logic board to fix my phone.
Logic board? How hard is that to do? Where can i buy that part?
Ive had to replace the usb port, that wasnt too bad, im assuming its a similar task?
Lol the thing that makes me feel like such an idiot - I came here immediately when it started happening, and since I hadn't rooted this phone before I didn't do it 100% and cause Knox to trip.
The kicker? My 1 year warranty expired 4 days AFTER it started happening. So had I not screwed up and trippes knox, Samsung wouldve replaced.
My freind sold me his note 4 for $50. There are alot of videos on how to do it. It wasn't that hard. Some of the videos have links where to buy the different component's. https://youtu.be/OUDgGaFcCNY edit. The logic board is the motherboard
Sent from my SM-N910P using JellyBombed Tapatalk 2
This is insane.
After dealing with this issue for a while, I finally ponied up the cash and bought a Note 5 from eBay.
The phone was still acting ridiculous all day - I must have done soft resets at least 10 times between 6am-1:30. Excited to get home because the Note 5 was in the mailbox.
I get home, call Sprint, have them switch activation to the 5. They told me to turn them both off, they did their thing, and now service is on the 5. Just like normal.
The ONLY thing that has changed was the information in the phone regarding service/activation; and now the Note 4 is running FLAWLESSLY. I don't understand how that could cause the problems that I was having, but now I'm frustrated as I just dropped a good amount of money to buy a phone without a contract/upgrade, and now it's working perfectly. Does anybody have any ideas on how this could have changed anything???
Same here also...
My phone just started doing this out the blue about a week and a half ago. It will freeze, hang, get extremely sluggish, reboot randomly, power off randomly, there will be about a 5-7 second delay with touch responses, typing will be delayed, etc. I did all the things, rebooted, pulled the battery, unrooted, went stock, re-rooted and tried other ROMs, tried custom kernels; I got the same results. I have a Note 3 I'm going to reactivate over the weekend and see if my Note 4 suddenly performs flawlessly since it won't be activated.