I have been using Cyanogen for at least the past year. In the past I have had trouble with things like random reboots, maps crashing during navigation, etc. Because of this I switched to just running the milestone releases for the past six months or so, and that has worked reasonably well. Its still way buggier than stock, but I put up with it for all of the nice features and what not.
Lately though reboots have become more and more frequent even though I hadn't changed anything. I had been running M9 for the past month with no real problems and then last night it decided to just go into a boot loop. I tried pulling the battery, clearing the cache, clearing dalvik, nothing worked. Eventually I just let the thing boot loop all night long and when I woke up it was finally booted.
Then this afternoon it did it again for a short period of time (3 or 4 minutes). When it came out I decided to download the newest, M10. It took several tries to actually flash it because the phone would reboot iself while in the middle of the wipe, or the flash, etc. But I started the wipe/flash process from the beginning every time to make sure I had a clean flash and eventually I got all the way through. But now it is at a point where it will boot, sit there for 2 or 3 minutes (I don't even touch it), and then reboot.
I'm hoping someone can help. I'm holding onto my unlimited data for dear life... I don't want to have to get a new phone. But re-flashing doesn't fix the problem so I really don't know what to do.
I
demarcmj said:
I have been using Cyanogen for at least the past year. In the past I have had trouble with things like random reboots, maps crashing during navigation, etc. Because of this I switched to just running the milestone releases for the past six months or so, and that has worked reasonably well. Its still way buggier than stock, but I put up with it for all of the nice features and what not.
Lately though reboots have become more and more frequent even though I hadn't changed anything. I had been running M9 for the past month with no real problems and then last night it decided to just go into a boot loop. I tried pulling the battery, clearing the cache, clearing dalvik, nothing worked. Eventually I just let the thing boot loop all night long and when I woke up it was finally booted.
Then this afternoon it did it again for a short period of time (3 or 4 minutes). When it came out I decided to download the newest, M10. It took several tries to actually flash it because the phone would reboot iself while in the middle of the wipe, or the flash, etc. But I started the wipe/flash process from the beginning every time to make sure I had a clean flash and eventually I got all the way through. But now it is at a point where it will boot, sit there for 2 or 3 minutes (I don't even touch it), and then reboot.
I'm hoping someone can help. I'm holding onto my unlimited data for dear life... I don't want to have to get a new phone. But re-flashing doesn't fix the problem so I really don't know what to do.
Click to expand...
Click to collapse
I don't know why your having such an issue with cm. Which is odd because I'm running a rom that's CM based and works fine. I'd say maybe try another rom if for nothing other than to see if CM is truly the issue.
I praise you for having the unlimited data still, I wish I would be been smarter and kept mine because there are months where I'm a little too close to that sad but lack of data with 2gb
And my hometown is Syracuse NY as I see your city is there. I miss the cuse but not the loudness of the city
From my Wicked S3 on SOKP
Pull a logcat or use a tool like https://play.google.com/store/apps/details?id=com.tortel.syslog to do this for you. then after the phone reboots itself, run syslog and examine the last_kmsg and logcat to see what the obvious errors/issues are.
I too have noticed google maps crashing, camera unable to connect, random reboots, file system errors, sluggishness, etc more lately with my G3 too. Wonder if some aspects of the hardware are failing...
BSOD2600 said:
Pull a logcat or use a tool like https://play.google.com/store/apps/details?id=com.tortel.syslog to do this for you. then after the phone reboots itself, run syslog and examine the last_kmsg and logcat to see what the obvious errors/issues are.
I too have noticed google maps crashing, camera unable to connect, random reboots, file system errors, sluggishness, etc more lately with my G3 too. Wonder if some aspects of the hardware are failing...
Click to expand...
Click to collapse
I solved the problem on my S3 with the camera. Freeze the system. Default and run another app, I'm on 4.4.4
From my Wicked S3 on SOKP
ShapesBlue said:
I solved the problem on my S3 with the camera. Freeze the system. Default and run another app, I'm on 4.4.4
Click to expand...
Click to collapse
You mean freeze the stock camera and use the Google camera instead?
Yea, when the camera is broken, neither app can connect until phone rebooted. Already tried many a time.
BSOD2600 said:
You mean freeze the stock camera and use the Google camera instead?
Yea, when the camera is broken, neither app can connect until phone rebooted. Already tried many a time.
Click to expand...
Click to collapse
Yes freeze stock camera. I'm using focal and it works fine but the stock camera won't work at all
From my Wicked S3 on SOKP
demarcmj said:
I have been using Cyanogen for at least the past year. In the past I have had trouble with things like random reboots, maps crashing during navigation, etc. Because of this I switched to just running the milestone releases for the past six months or so, and that has worked reasonably well. Its still way buggier than stock, but I put up with it for all of the nice features and what not.
Lately though reboots have become more and more frequent even though I hadn't changed anything. I had been running M9 for the past month with no real problems and then last night it decided to just go into a boot loop. I tried pulling the battery, clearing the cache, clearing dalvik, nothing worked. Eventually I just let the thing boot loop all night long and when I woke up it was finally booted.
Then this afternoon it did it again for a short period of time (3 or 4 minutes). When it came out I decided to download the newest, M10. It took several tries to actually flash it because the phone would reboot iself while in the middle of the wipe, or the flash, etc. But I started the wipe/flash process from the beginning every time to make sure I had a clean flash and eventually I got all the way through. But now it is at a point where it will boot, sit there for 2 or 3 minutes (I don't even touch it), and then reboot.
I'm hoping someone can help. I'm holding onto my unlimited data for dear life... I don't want to have to get a new phone. But re-flashing doesn't fix the problem so I really don't know what to do.
Click to expand...
Click to collapse
These symptoms could indicate a sticky power button. Try knocking it lightly against the corner of a table to jar whatever is making it stick loose.
It doesn't sound software related, especially since it rebooted while in recovery. If you hold the power button down long enough in recovery it will reboot, which makes me think you just have a sticky power button. It's happened to me before.
BattsNotIncld said:
These symptoms could indicate a sticky power button. Try knocking it lightly against the corner of a table to jar whatever is making it stick loose.
It doesn't sound software related, especially since it rebooted while in recovery. If you hold the power button down long enough in recovery it will reboot, which makes me think you just have a sticky power button. It's happened to me before.
Click to expand...
Click to collapse
I think you might be right. Even when it is up and running, I have been noticing lately that I get the power menu popping up sometimes when I wasn't even touching the power button. So last night when it was in one of its constant boot loop fits I took it apart a bit (took the back off, took out the battery sim and sd, and unscrewed the shell) and blew some compressed air all around the power button. It had been rebooting for about an hour at that point and then as soon as I put it back together it came up on the first try. So far so good.
Related
I've been using my SR for a week now and initially I had QuickWiz ROM installed but after getting some SOD, I switched to TPC ROM which worked great for few days as well but lately I have started getting random reboots that I have not been able to pinpoint the cause for.
I reinstalled TPC rom and then immediately got a reboot. After restarting the phone, it worked for few mins and then rebooted again. At this point, I reinstalled QuickWiz and just within an hour, I have already gotten two reboots.
Any suggestion what might be causing it? Could it be hardware related?
You might try flashing the stock 2.3.5 or 2.3.6 ROM and KERNEL and see if random reboot problem goes away... then you'll know it's not a hardware issue. Check the Development section and read carefully... probably need to clear cache/data multiple times.
DoctorQMM said:
You might try flashing the stock 2.3.5 or 2.3.6 ROM and KERNEL and see if random reboot problem goes away... then you'll know it's not a hardware issue. Check the Development section and read carefully... probably need to clear cache/data multiple times.
Click to expand...
Click to collapse
I ODIN back to stock yesterday and everything worked for until today when I got the reboot when opening email which leads me to believe that there is a hardware problem somewhere. I have already gone through three different ROMS (including stock) and I always get random reboots sooner or later.
So do you now have 3e recovery... or is CWM Recovery still your recovery partition? From what I've read, you need to clear data and clear cache up to 3 times each from 3e recovery.
DoctorQMM said:
So do you now have 3e recovery... or is CWM Recovery still your recovery partition? From what I've read, you need to clear data and clear cache up to 3 times each from 3e recovery.
Click to expand...
Click to collapse
I gave up on this and called Amazon. They are shipping me a new SR overnight
ajamils said:
I've been using my SR for a week now and initially I had QuickWiz ROM installed but after getting some SOD, I switched to TPC ROM which worked great for few days as well but lately I have started getting random reboots that I have not been able to pinpoint the cause for.
I reinstalled TPC rom and then immediately got a reboot. After restarting the phone, it worked for few mins and then rebooted again. At this point, I reinstalled QuickWiz and just within an hour, I have already gotten two reboots.
Any suggestion what might be causing it? Could it be hardware related?
Click to expand...
Click to collapse
I had the same problem and was really confused and then I think I figured the problem out. Do you have one of those thin leather mobile phone cases that attach to your belt? I notice when I put my brand new SR in my case that I purchase that when it moves even just a little bit it will push down on my power button and shut it off and back on. Is there any chance that is happening. I know it sounds stupid but I does happen to me.
reubendevries said:
I had the same problem and was really confused and then I think I figured the problem out. Do you have one of those thin leather mobile phone cases that attach to your belt? I notice when I put my brand new SR in my case that I purchase that when it moves even just a little bit it will push down on my power button and shut it off and back on. Is there any chance that is happening. I know it sounds stupid but I does happen to me.
Click to expand...
Click to collapse
Nope, that was not the case because my phone was rebooting either when I was on call or even when it was just sitting on the table.
I had two reboots last night. Both times, I was On the phone using headphones and phone was plugged into a charger.
It seems to reboot if It's plugged in and am on the phone at the same time. It does get pretty warm.
WTF.
I have been having the same issue with my Skyrocket. I am also using TPC v3 ROM, haven't tried to put the stock rom yet, but one thing for sure that this problem is not persistent.
When this problem start, my phone keep restarting for at least 5-10 times and it doesn't allow you to do anything in between. Once it starts working you won't see the booting issue again.
Hello all, I have an HTC Arrive running LEAD's 7.8 8858 ROM. I've been running this rom since January with very little issues. However, within the last couple of weeks I have been noticing strange things going on with my phone. Some mornings I have woken up and left for work and notice my phone is almost dead, even though I remember plugging it in the night before. Also, as of this week, after a reboot of my phone, the Call button shows Home Service instead of Sprint, but eventually changes over to Sprint. At times I will go to use my phone and see it has put itself in Airplane mode or has a locked sim card logo displayed instead of signal bars. In this case I have to reconnect to the network to regain functionality.
Now as of last night my phone is constantly rebooting while charging. I plugged it in last night and kept hearing a buzz (I keep it on vibrate), looked at the phone and it would be booting up. It fully boots to the Start screen and I can go ahead and begin doing something, but no matter what I'm doing it just shuts completely off without even saying Goodbye (literally). It continues to do this until I unplug it, and it ONLY reboots when plugged in. I've tried a battery pull a couple of times but to no avail. Its getting very annoying because it takes much longer to actually charge, and I also don't imagine this is very good for the phone itself.
I was planning on flashing LEAD's latest release to see if it fixes it, but I'm not sure if the phone will react this way plugged into the PC as well. I haven't plugged in to the computer yet to find out, hopefully it won't do this, else I won't be able to flash it.
Any ideas or suggestions? Has anyone else had this issue?
well i plugged into the pc and it still reboots however, when in the tricolor bootloader it does not reboot! so with this discovery i now know that its a bug in the OS causing the reboots. also, because its not rebooting in the bootloader, i should be able to reflash without issues, correct?
as a side note, the phone got VERY hot last night while left in to charge, so i will just charge my wifes phone and swap the batteries so that i wont damage my phone.
no one else has reported this issue with this ROM as far as i can see, only random reboots.
Sorry to hear about all those problems. Have you tried the latest ROM after the 8858 release? I suspect there could be some sort of corruption in the OS. If you haven't, I recommend biting the bullet and just restoring the phone. I also recommend flashing the latest ROM, since it has the latest OS version. If the phone isn't having problem when in boot-loader mode (tri-color screen), you should be OK to flash it.
leadpoizon said:
Sorry to hear about all those problems. Have you tried the latest ROM after the 8858 release? I suspect there could be some sort of corruption in the OS. If you haven't, I recommend biting the bullet and just restoring the phone. I also recommend flashing the latest ROM, since it has the latest OS version. If the phone isn't having problem when in boot-loader mode (tri-color screen), you should be OK to flash it.
Click to expand...
Click to collapse
thanks for the reply lead! i am going to flash you latest release now. i am going to look for an alternative way to backup pictures outside of Zune and the PC, but i dont think any exist.
i will post back when its up and running.
i flashed the 8862 ROM and its been plugged in for about an hour with no reboots
plus, this ROM feels snappier than the 8858. an issue i used to have with IE, that is gone in this build is it would open Google every time i click the IE tile.
thanks for the help leadpoizon
x_orange90_x said:
i flashed the 8862 ROM and its been plugged in for about an hour with no reboots
plus, this ROM feels snappier than the 8858. an issue i used to have with IE, that is gone in this build is it would open Google every time i click the IE tile.
thanks for the help leadpoizon
Click to expand...
Click to collapse
No problem. Glad your issue is fixed now.
Ok so I am no longer having the charging or battery issues anymore, but now my Marketplace is basically broken. When I can manage to begin a download it immediately goes to Attention Required, and upon clicking i get error code 8000ffff. So no apps will install/download from Marketplace. Also, on almost every game and app, it says this app is not available for your device, even ones i used to use on 8858. Some i have even manually installed and they work fine. Also when trying to even view many of the games in the Marketplace, I get error 805a0194. So far I haven't managed to install anything from the Marketplace aside from the Bank of America app.
I have tried resyncing with Live, rebooting the phone, tried changing Marketplaces and settings with the Marketplace Config app. Nothing fixes it
Any suggestions?
No one?
I'm beginning to think 8862 is to blame. I keep getting service unavailable errors from MP, or everything is not available for my device. I don't want to hard reset, but it looks like this isn't going away on its own. :/
x_orange90_x said:
No one?
I'm beginning to think 8862 is to blame. I keep getting service unavailable errors from MP, or everything is not available for my device. I don't want to hard reset, but it looks like this isn't going away on its own. :/
Click to expand...
Click to collapse
Sorry, I've moved on from this device, so I can't test anything now. I never had any issues like this on my device and I used it extensively for a long time after flashing that ROM.
The other day, my phone died midway through a call. When I tried to turn it on, the 0% sign showed up meaning it was completely dead. I had to urgently make a call so 30 mins later, I held the power button again, turned it on, and the phone went to the white HTC screen and then turned off. I finally got home and connected to my phone to my charger after. I let it charge for a bit then turned it on. I knew something was wrong when my phone was hung on the red Verizon boot logo for a while. Minutes later, it went past the Verizon logo and a pop-up appeared that said optimizing app 1 of 44. I thought this was odd because I already got the MM update about 2 weeks ago and since it updated, I never saw that message ever until now.
Once my phone gets past that and finally boots to the homescreen, I realize that a lot of things have gone wrong. First, I got signed out out of all my accounts (Whatsapp, Spotify, Instagram, Facebook, etc). On top of that, my call history was cleared, all my text messages were cleared, and all my contacts that were saved on my phone storage were gone. In addition, I also had to re-update a lot of apps including the HTC ones that you have to upon the MM update. Finally prior to those whole thing happening I had 10.7gb of free space. After this episode, I lost exactly 1 gb of storage and only have 9.7gb free.
I don't understand what could have caused this or why I lost all this data on my phone. Moreover, it doesn't seem like anything was deleted but my phone is just not reading anything that was already there.
mine just did this exact same thing after shutting off from a drained battery. It's like the data partition or whatever got wiped. Right now trying to log back in to everything and set EVERYTHING back up again. This sucks.
baune7 said:
mine just did this exact same thing after shutting off from a drained battery. It's like the data partition or whatever got wiped. Right now trying to log back in to everything and set EVERYTHING back up again. This sucks.
Click to expand...
Click to collapse
i came here for the same thing. mine happened around the same time. only thing i can add here is that my storage is almost maxed out on the phone. makes me wonder if that had something to do with it. but then this happened to two other people around the same time. very weird.
The exact same thing happened AGAIN! I was at the gym listening to music and texting some friends while my battery was at 15%. Went from 15% to 10% in a matter of mere minutes and then from 10% just shut off. Couldn't charge it until I got home so I just kept it in my pocket. Got home about an hour later, put it to charge and then turned it on when battery hit about 10%. Same damn thing, got stuck on the Verizon boot logo and then the dreaded Optimizing Apps message showed up. Once it finished, I was logged out of all accounts, updates to system apps were gone, and widgets/BlinkFeed were gone/reset. And just like last time, suddenly 1GB of storage was gone.
Literally un-freaking-believable. I dreaded that it would happen when my phone shut off and yep, my fears were right. Going to do a factory reset once I backup everything. From there, I am debating whether to replace the battery or replace my phone. While it sucks that it happened to you guys as well, I am somewhat glad its an HTC issue and not just an issue with my personal phone.
Same thing happened to me at 40%
This was recently brought up in the viper rom thread, could be of help.
TidusWulf said:
Your battery needs to be reset. Hold down POWER + VOLUME (can't remember if it was up or down. takes about 10 seconds)and let it keep resetting and keep holding it for 3 minutes. then let go.
It'll fix your battery so that it drains to 0 instead of 13, but it doesn't fix the weird pseudo-reset problem. It's a known issue and many people are struggling with it. My advice is to set EXTREME POWER SAVER to auto-on at 10%, and if you ever see it that low, just turn it off yourself until you get a chance to charge it.
Click to expand...
Click to collapse
Same thing has been happening to me since the MM upgrade. Before that I had NO issues with my battery so I find it hard to believe that my battery is the problem.
After the third time of this happening I finally decided to to a factory reset. This did not help, phone continues to die anywhere between 15% - 30% and revert some of my settings back to stock.
This is driving me insane as I rely on this phone for personal and work use.
Decided to call HTC support today, I did not expect a solution but wanted to make sure it was reported. Of course they had no idea and claimed to have never heard of this issue.
I am guessing that since the M8 is over two years old we wont be seeing and fix pushed out for this issue. I really like my phone and dont want to upgrade at this time.
Finally somewhere where people are actually having the same issue. I've tried factory resetting the phone, doing a fresh install of the OS (with firmware recovery tool) all with no avail. I note lose all my settings and app configurations every time the phone dies, shuts down or restarts. I hope there's a fix, otherwise it looks like a custom rom is the only way.
Has anyone tried wiping the dalvic cache? I can't get into the recovery on my phone so I can't try it, but heard I it might help.
Had the same issue last week
I was at about 20%, phone shut down. I plugged it in to charge, went to boot it up, and it got stuck on the Verizon bootup screen.
I waited a while and did a hard reset, and it came back on, but was completely wiped. So I had the same problem, which is a real pain, because I use the GOOD app for work, and each time that re-installs I have to get a new PIN. And I have had to re-install the app a few times in the past month for a variety of reasons...
Teevan said:
I was at about 20%, phone shut down. I plugged it in to charge, went to boot it up, and it got stuck on the Verizon bootup screen.
I waited a while and did a hard reset, and it came back on, but was completely wiped. So I had the same problem, which is a real pain, because I use the GOOD app for work, and each time that re-installs I have to get a new PIN. And I have had to re-install the app a few times in the past month for a variety of reasons...
Click to expand...
Click to collapse
I feel your pain. I use Mobilepass for work and every time my phone resets it deletes my token and I have to request a new one.....
Here is what I did two days ago that seems so far to be working for me. I calibrated the battery. I have tried this in the past but could never get the calibration to work properly. Each time I tried I had the phone plugged into the charger. This time I didnt and the phone went through the battery calibration process like it is supposed to.
Since I have done this my phone will stay on until it gets to 8 or 9% and then shut down but when i charge and turn back on all of my setting are still in place.
To calibrate the battery I held the up volume, down volume and power button (all 3) for a full 2 minutes without the phone being plugged in. During this time the phone will start and get to the HTC splash screen then shut back off, start again to the HTC splash screen then shut off, repeat, repeat, repeat.... after 2 minutes release the buttons and let the phone boot up, plug it in and let it charge to 100%.
I hope this helps,
This happened to me today. I let the battery get a little lower than usual last night, around 13% before shutting it down and plugging it in for the night. Turned it on this morning and it booted up normally. Didn't lose any apps or data, but every time I did something on the phone it gave me those little hints like its a brand new phone. I went to settings and it says it was factory reset at 6:46 a.m. this morning (about the time I turned it on).
Parakaleo said:
This happened to me today. I let the battery get a little lower than usual last night, around 13% before shutting it down and plugging it in for the night. Turned it on this morning and it booted up normally. Didn't lose any apps or data, but every time I did something on the phone it gave me those little hints like its a brand new phone. I went to settings and it says it was factory reset at 6:46 a.m. this morning (about the time I turned it on).
Click to expand...
Click to collapse
Did it reset your ringtone and notification tone settings? Thats what it always has done to me.
I would just like to say that the same thing happens to me as well on my HTC one m8. Battery suddenly dies, now even at 25%, even after a calibration which is just a temporary solution, and when I turn the phone again, SwiftKey settings erased, everything went to stock, messages and contacts are preserved, but the apps start updating itself even though they are not allowed to and I have to manually set a lot of things. It is a total confusion and I literally can't believe HTC allows themselves to not issuing a fix for this disaster.
Was it cold?
Same issue. With mine it seems to be when it gets cold. I was skiing today in 20F but inside my pocket this really shouldn't be an issue. It has turned itself off and refused to restart several times when it has been used to take pictures in cool weather (I live in western OR, it doesn't get COLD, by cool I mean <35F but >20F, usually > 25F). This is the third time it has totally screwed up the phone when it has happened. On another occurrence it reset under normal conditions too. I'm getting pretty sick of it as it is quite a process to get all my VPN tokens reset, get all the apps back etc. Of course it waited until the warranty was out to start acting up.
This time is especially bad, the phone will not restart properly and important processes just constantly flag as stopping so that I can't even get past the initialization screen. It looks like I will have to do a full factory reset. If anyone from HTC is reading...Not acceptable and I won't be buying another phone from you.
Unfortunately I've reached the point where I wouldn't be surprised if it is a programmed planned obsolescence function, but whether or not, this is really annoying behavior.
Sorry to hash up an old thread but I put up with this crap for 5 months before I finally punched and broke the screen out of rage during an important business tech support call when I was at the clients location trying to service their security equipment, it was so embarrassing having to tell them I have to come back especially since it was a remote location.
Mine would wipe contacts, texts etc regularly. I ended up installing Super backup or something and saving my backups on google drive and just restoring everything everytime it happened.
I decided to fix up the phone and replace the battery, broken charging port and smashed screen and unlock bootloader and root but flashing superSU didnt work, got stuck in a bootloop. Anyways through all this I wiped all the caches (including Dalvik cache) flashed the correct stock rom and did the battery calibration and that seemed to have solved the random shutdown and memory leaking issue.....but I guess I wont know for a while.
I have a HTC One 610, and like every once in a while it well automatically reset it self whenever I am in the middle of a text message, on facebook, or even sending an email on phone. Its getting annoying when my cell reset its self.
what needs to be done to it? and should I do.
PRINCESS2017 said:
I have a HTC One 610, and like every once in a while it well automatically reset it self whenever I am in the middle of a text message, on facebook, or even sending an email on phone. Its getting annoying when my cell reset its self.
what needs to be done to it? and should I do.
Click to expand...
Click to collapse
try a factory reset
I know its old but people are having the same issue still so I'm gonna paste this everywhere i find this problem.
There is a Modified stock rom named "Android_Revolution_HD-One_M8_53.1" and its almost the stock M8 without bloatware and so much more stability improvements. So hear me out and flash it with a custom recovery (i did it with twrp) and it seems to be working fine so far. Give it a go before you trash your -still so good- phone to the open seas.
Well, this issue is still happening. my phone has been doing the same for about a week now. ive made several attempts to reset the battery and had to reinstall back ups every time its happened also. the only difference i think now is that its happening at 90% instead of the usual 15%. ive been following instructions to hold volume up, down, and power (with the phone off) for about 2 minutes and then letting go. i have my extreme power saver set to come on at 15% but Im not even getting that low before it shuts off and resets. i have however noticed that recently that if you plug the phone on charge after it first dies you can avoid the phone resetting.. this may be a fluke but its allowing me to deal with the battery problem now without the loss of my data, contacts, etc.
This is exactly the reason why HTC One M8 is the last HTC phone I will ever purchase. Imagine the hassle of phone factory resetting on its own. Horrible.
Out of nowhere my phone started to restart randomly to the point when it looks like a boot loop. Also I have noticed that those boot loops occurs when my battery is below 50% and when I'm charged to 100% I can boot but after 3-4 minutes it goes to restart anyway. Also when I have turned off WiFi, GPS and BT there are no more reboots so far but I'm not able to turn on back WiFi, GPS or BT unless I will pull battery out and put back and turn on them back quickly but then I'm getting back those random restarts.
I'm on a stock but rooted Lollipop with TWRP.
I saw some threads with similar issues and were related to a battery but in those cases phones stay up when were charged or a battery pack and mine has still if is connected to the wall or a battery pack.
Any clue what is going on?
Thanks
OK now I'm not able to get to the Factory Reset screen (Power + Vol Down). Any clue on that?
Also when I try to flash stock it goes for about 6% and stops saying something like can't change to download mode.
Is this phone dead?
Also when I try to flash stock it goes for about 6% and stops saying something like can't change to download mode.
Is this phone dead?
So now I have issues to get started that phone. Mostly goes into boot loop mode (LG logo, LED flashes few times and reboots). Sometimes it goes beyond LG logo - to AT&T logo and reboots there. When I pass that I have a luck and I can get phone to work but I need to disable WiFi, BT and NFC.
Also I have got into MiniOS and run that ATT testing tool which came all passed except one - OTG or something like that failed.
Any help?
I think android modification is dead man. There's a bunch of junk devs that release crap that isn't even worthy of being flushed down a toilet, then provide no help to users with problems. At best they tell you that it's your fault then ignore you.
Wish I could help. I'm having a similar problem on CM13. After a few dozen posts asking for help with 0 replies, I've decided you now modify your software entirely at your own risk and if something goes to hell you either have to install a different ROM or buy a new phone.
TheNetwork said:
I think android modification is dead man. There's a bunch of junk devs that release crap that isn't even worthy of being flushed down a toilet, then provide no help to users with problems. At best they tell you that it's your fault then ignore you.
Wish I could help. I'm having a similar problem on CM13. After a few dozen posts asking for help with 0 replies, I've decided you now modify your software entirely at your own risk and if something goes to hell you either have to install a different ROM or buy a new phone.
Click to expand...
Click to collapse
try a new battery @TheNetwork @Scyzor
I ran into those constant bootloops on every ROM I tried, including when I factory restored to KitKat unless the phone was plugged in. I got a new battery (then recently replacing that one with a newer & good 6,800mAh for under $20 because it drains way too fast) & bootloops stopped.
Sent from my LG-D850 using XDA-Developers mobile app
TheNetwork said:
I think android modification is dead man. There's a bunch of junk devs that release crap that isn't even worthy of being flushed down a toilet, then provide no help to users with problems. At best they tell you that it's your fault then ignore you.
Click to expand...
Click to collapse
I think this is sad but true :\ All PROs are gone to different phones or newest releases and only LG G3 fanboys left with bunch of "supporters" from Asia. Anyway I'm going to dump LG and will wait for new Google Nexus.
harffmut said:
try a new battery @TheNetwork @Scyzor
Click to expand...
Click to collapse
Zahr said:
I ran into those constant bootloops on every ROM I tried, including when I factory restored to KitKat unless the phone was plugged in. I got a new battery (then recently replacing that one with a newer & good 6,800mAh for under $20 because it drains way too fast) & bootloops stopped.
Sent from my LG-D850 using XDA-Developers mobile app
Click to expand...
Click to collapse
I have got two batteries week ago. One original replacement (3000 mAh) and some OEM (3500 mAh) - both were failing into boot loop until I will get to be lucky enough after full charge over the night and boot to the system and leave it as is but last Tuesday my screen started to fade away instead of turning off and after that it went again into boot loop.
But I don't have any problems booting into recovery (TWRP) or DL mode. Strange...
Scyzor said:
I think this is sad but true :\ All PROs are gone to different phones or newest releases and only LG G3 fanboys left with bunch of "supporters" from Asia. Anyway I'm going to dump LG and will wait for new Google Nexus.
Click to expand...
Click to collapse
This happens with all phones as devs are like anyone else. They upgrade their devices and focus on the new device. Some sell their old device to offset the cost of the new one. Development takes time and many of these individuals have lives outside of development. They have jobs and/or families. What they do is for the fun of it and so they can get more of what they want out of Android. If they share it, then that is up to them and does not mean they owe support to those who choose to use their ROM(s). The fact that a development site lets non developers use ROMs that are uploaded is a privilege and I'm thankful for it. I'm not a developer but have been able to use info from here to get more of whst I want from my phones.
Strange problem. Battery full, no problems there. After getting mad about sdcard not being recognized, even with cm 12.1 , I decided to install cm 6.01 rom(marshmallow) nightly. Installed, changed launcher to nova prime, right gapps, and installed kernel auditor. Downloaded xposed for marshmallow, rebooted, everything was fine(or so I thought). Two days later, coming back from store, looked at my phone and hit power, to get it out of sleep. That's when everything went wrong. It didn't come back, and no pressing of the power button did anything, I had to battery pull. I rebooted to twrp, and over the next week tried to get it right. Uninstalled cm 6.01 nightly, and put xneon rom on it. Same problem persisted, no boot to the os, or partial boot to the lockscreen. I knew the phone wasn't hard bricked, since twrp was still working, and phone wasn't shutting down to no response. Whenever I tried to boot into the os' , it would still get stuck on startup, though. I read all of the advice to return to stock, using flashtool, or lgup, going into download mode, everthing that I could read up on, and implement. I ran to best buy, and ordered a huawei 5x, and said to myself, I can't fix it. Well, today, I said why don't I short the battery pins, and repeatedly press the power buttons, at the same time( because when i put the battery in, even after 10~15 seconds, it would boot to the lg logo, then fade to non-responsive again). Viola! it booted into the os' , and didn't shut down to unresponsive condition(no power button action, and ultimately, battery pull). It seems everthing was fine, until I used the browser, then condition came back. Battery pull again, and it's working now, haven't shut it down since, so I adjusted the display off time to 30 min. , and turned off power saving modes. I don't know if it's truly fixed, but I thought my phone was going to my archives history drawer(all my other phones still work, but they're underpowered, old os' phones). It may still go there, once I pick up my huawei, but I'm glad to see it still living. Is there some type of time out I'm not aware of? or a shutdown by internal fuse, or reset that's built into the firmware? I've heard of bad screens with this, but didn't think that was the problem, since, when in twrp, it never shut down to being unresponsive, and when twrp shut off screen, it would come back, even after hrs of it on. I want to know if the bootloader has anything to do with this, and by shorting it, cleared the emmc.
I have made a video how it looks on my LG G3:
PS.
Is there flashable CWM for D850? I have heard that TWRP is creating those issues from the video.
Well, based on some articles it looks like a hardware issue mostly related to the overheating and "cold soldering joints". Based on that article most of LG phones may experience that issue:
http://www.androidauthority.com/lg-v10-bootloop-problem-711334/
Hello, everyone.
I'm using an OPO since october 2014 and I had no intention of buying a new phone in the near future. But now I'm worried about it.
Abouth three weeks ago, my phone started to freeze and reboot. At the time I was using sultan's latest ROM. I thought the problem was the latest updates and, as I wanted to test Nougat, I decided to download Lineage.
To my surprise, I kept having random freezes and reboots.
While reflashing ROMs and changing kernels, I had some reboots. Yes, self rebooting while on recovery.
So I decided to get it totally back to stock and re-start fresh.
Phone froze and restarted on COS initial config. And, after that, rebooted again when updating Gmail apps.
During these three weeks, it kept on with no reboots for, at max, around 40 hours.
Is there any way I can test my phone to determine if it's a hardware issue? It all makes me think it is. :/
Any clue is welcome.
Thanx.
Cappelletti said:
Hello, everyone.
I'm using an OPO since october 2014 and I had no intention of buying a new phone in the near future. But now I'm worried about it.
Abouth three weeks ago, my phone started to freeze and reboot. At the time I was using sultan's latest ROM. I thought the problem was the latest updates and, as I wanted to test Nougat, I decided to download Lineage.
To my surprise, I kept having random freezes and reboots.
While reflashing ROMs and changing kernels, I had some reboots. Yes, self rebooting while on recovery.
So I decided to get it totally back to stock and re-start fresh.
Phone froze and restarted on COS initial config. And, after that, rebooted again when updating Gmail apps.
During these three weeks, it kept on with no reboots for, at max, around 40 hours.
Is there any way I can test my phone to determine if it's a hardware issue? It all makes me think it is. :/
Any clue is welcome.
Thanx.
Click to expand...
Click to collapse
Get your device checked at a local shop. Looks to me like a battery or logic board issue.If it's battery then you can get a replacement but if its logic board then yes,you should consider buying new device.
Mr.Ak said:
Get your device checked at a local shop. Looks to me like a battery or logic board issue.If it's battery then you can get a replacement but if its logic board then yes,you should consider buying new device.
Click to expand...
Click to collapse
I'm fairly sure that there is no local shop that could check it.
Right now, before checking this thread, I let the battery completely drain and now it's on the wall recharging. I'll enter recovery when it's 100% charged and do a factory reset. Then install everything back and use it for a few hours.
Let's see it that helps.
Thanx for the reply.
- phone battery completely drained
- phone battery completely charged
- booted to recovery and factory reseted
- initial COS configuration done without any freeze and/or reboot
- updating Google Apps
So far, so good.
And it rebooted twice, during apps update.
Although it updated main Google apps, it was not supposed to reboot.
:/
Hmmm...if random reboot but able to boot normally afterwards then you need to tweak the kernel a little bit but if is random reboot and then stuck at 1+ logo or bootanimation then your battery is dying....
to check whether the battery is dying just wait until next reboot...if it stuck on 1+ logo or bootanimation, turn off the phone completely then plug in the charger...it it charge for 5 minutes in offline mode then turn it on while the charger still connected...if its boot normal then it is confirmed that the battery is dying...replace a new battery as quick as possible...
I've been living with random freeze+ automatic reboot since COS13 it's a PITA but doesn't cost me anything to wait 1min until full reboot, only problem are lucky patch on boot which take longer but nothing that bad. I was never able to troubleshot the issue, usually happens to me when I receive some notification I see the LED and try to unlock but the phone stays blacked out (even though it's clearly on since notifications are shown on the LED) until I force reboot.
Over the years I tried insane amount of ROMs and kernels, nothing changed, adding to that the fact that 10% of the times when i put it in charge (original charger+cable) says 7h or 6h until full charge (and I actually have to wait all that time), I just have to unplug and try again until it fixes. It's not the charger because I tried it with other phones, so I started to assume my problems are the small board with the charging board + battery. But I never had the willing to change it. I'm "fine" with how it works.
iPusak Gaoq™ said:
Hmmm...if random reboot but able to boot normally afterwards then you need to tweak the kernel a little bit but if is random reboot and then stuck at 1+ logo or bootanimation then your battery is dying....
to check whether the battery is dying just wait until next reboot...if it stuck on 1+ logo or bootanimation, turn off the phone completely then plug in the charger...it it charge for 5 minutes in offline mode then turn it on while the charger still connected...if its boot normal then it is confirmed that the battery is dying...replace a new battery as quick as possible...
Click to expand...
Click to collapse
It does not get stuck. At times, it reboots during boot. Some times (rarely) it does that for two or three times and then turns off. But most of the time it freezes, reboots and I can use it normally for hours and hours.
seanwlk said:
I've been living with random freeze+ automatic reboot since COS13 it's a PITA but doesn't cost me anything to wait 1min until full reboot, only problem are lucky patch on boot which take longer but nothing that bad. I was never able to troubleshot the issue, usually happens to me when I receive some notification I see the LED and try to unlock but the phone stays blacked out (even though it's clearly on since notifications are shown on the LED) until I force reboot.
Over the years I tried insane amount of ROMs and kernels, nothing changed, adding to that the fact that 10% of the times when i put it in charge (original charger+cable) says 7h or 6h until full charge (and I actually have to wait all that time), I just have to unplug and try again until it fixes. It's not the charger because I tried it with other phones, so I started to assume my problems are the small board with the charging board + battery. But I never had the willing to change it. I'm "fine" with how it works.
Click to expand...
Click to collapse
I'm "almost" fine with the way it works for me. As most of the time it's fully operational.
I found a OPO with damage screen for sale here. He guy didn't want too much $ for it. I bought it and will receive next week. Will try to swap logic boards.
Let's see what happens.
Was able to have logcat running when the device froze (during game) and rebooted.
Is anyone able to see any error on the log that could make the device freeze and reboot?
Got the broken screen OPO two days ago. Yesterday my phone was impossible to be used. Rebooting like hell.
I swapped logic boards and all is fine. No freezes and reboots (of course, it's pratically another phone). I kept only my screen, housing and battery.
My logic board had a 2.5 sticker on it. The one I got now has a 2.1 sticker. Does anyone know what's that about?