Database Info

Pattern to my reboots - do yours have a pattern?

So over the last few days my phone seems to have settled into some sort of weird pattern with reboots. Although there are outliers, in general it always seems to reboot between 19-24h of uptime and nearly always at like 45 or 50 mins past the hour. It's the most bizarre thing in the world and why I think there's some funky software doing it. I don't have true random reboots, but I can't figure out what it is that is doing this. Very odd.
In all cases my phone is sitting with the screen off (I've NEVER had a reboot while using the phone/screen on) but it doesn't matter what radios are on, WiFi, BT, GPS (can be off or on).
Last time I ran "CatLog" a logging app from Market and had it write to SD logs and a reboot happened but it only by default writes every 200 lines so the last line in the file was probably not the last line in the log. I'm going to try again later and set it to write every line or few lines so I can see the last entry in the log before a reboot. Might shine some light on it.
Just find it very strange since it's a very stable and capable phone for about 18hrs and then it just craps on itself. Very strange.

finally. I too just think it is some weird software or driver bug because I was running EB 1.0.4 FINE for like 3-4 days and loving it... then it started resetting almost hourly. I didn't install any other apps past my initial normal set of apps.
Even CM7, seems like it is fine for a few days, then gets crazy. As long as I put a new nightly rom on it every day, it's good.
I didn't have any issues with stock though and didn't seem to have issues with CM7 for a while until lately.
The leaked GB rom causes lockups immediately out of the gate seemed hourly.
I use CM7 as my main daily driver now but I think you are on to something. We are talking about the Screen of Death right? I don't think mine ever reboots, but gets stuck at the lockscreen where the the display comes up, swiping to unlock vibrates then the phone but doesn't change screens to desktop. The buttons and click/drag widgets work even though you are looking the lockscreen.
I've never had my phone powered off in my pocket or noticed it "rebooting". Mine just has the SoD that seems to follow your pattern idea. They may be related. Stock roms may reset once it locks up, where CM7 just keeps running in its locked state.

I have a really strong sneaking suspicion that every G2X reboots but not everyone notices. Also if you naturually turn your phone off once a day or so you won't notice it perhaps or even a few days. The phone reboots pretty fast and the only way I've been noticing (except the times I see/hear it happen) is I have an uptime widget on my homescreen so it's obvious.
Same thing happened with my Droid Incredible btw...when it first came out there were all kind of random reboot issues. After a software update I would run that phone hard for 30-45 DAYS straight without a reboot.
It's annoying but I think it's just a matter of time before the G2X is the same.

I just hope that update gets here sooner than later.
Sent from my LG-P999 using XDA App

I dunno. The tmobile jingle is pretty loud and I never hear it. CM7 has a silent one so possibly there but I dunno.
I use my phone pretty often and never had the suspicious that it reboots. My phone stays very cool during my usage compared to my nexus and other phones
My uptime was 4 hours since I reset it last. I'll monitor it with results. It'll be hard not to flash but I'll keep track and see how far I can keep it online.

i have not had any reboots or waking up to a dead phone ....with the only fix is a battery pull.... ever since I started.
1) my over night charging / long term charging to 100%... only on the LG charger that it came with. Only short term...maybe. less than an hour and not to a 100% charge on a non LG charger (car charger etc...)
2) I restart my G2x every morning when I take it off the LG charger..(after I take it off..I did it once while on the charger and had an issue... (there is definitely an issue related to when it charges to/ around 100% charge)
Just my 2 cents.

Pattern to my reboots - do yours have a pattern?
Hold Power and volume up simultaneously for about 10 seconds.

I've had my phone since Friday, but the only time I had the rebooting problem was this past Saturday when it rebooted four times within 15 minutes or so. Before the rebooting began, the phone had slowed down to a crawl, so I went ahead and rebooted it. After that, I sat it down and watched it reboot a few times on its own. Luckily my iPhone 4 owning co-worker was completely unaware of this issue since we tease and bicker with each other every day over Android and iOS .

mobilehavoc said:
I have a really strong sneaking suspicion that every G2X reboots but not everyone notices. Also if you naturually turn your phone off once a day or so you won't notice it perhaps or even a few days. The phone reboots pretty fast and the only way I've been noticing (except the times I see/hear it happen) is I have an uptime widget on my homescreen so it's obvious.
Same thing happened with my Droid Incredible btw...when it first came out there were all kind of random reboot issues. After a software update I would run that phone hard for 30-45 DAYS straight without a reboot.
It's annoying but I think it's just a matter of time before the G2X is the same.
Click to expand...
Click to collapse
I can guarantee that mine don't reboot. I've had it up fire days, checked the up time and play with it constantly.if it rebooted in the middle of the night I would hear it or the uptime would be close to zero in the morning..
I have a way stable phone.running stock, rooted with bloat removed.. I love this damn stable phone.

smashpunks said:
I can guarantee that mine don't reboot. I've had it up fire days, checked the up time and play with it constantly.if it rebooted in the middle of the night I would hear it or the uptime would be close to zero in the morning..
I have a way stable phone.running stock, rooted with bloat removed.. I love this damn stable phone.
Click to expand...
Click to collapse
What bloat did you remove? I've removed most but not all of it. Can you list it?

mobilehavoc said:
What bloat did you remove? I've removed most but not all of it. Can you list it?
Click to expand...
Click to collapse
Everything other than smart share, tegra zone and qik. Of course have nova and need for speed also.
Oh also have car home froze..

Maybe jumping the gun here but I tried to let mine go as long as it could without resetting it. I kept tabs on it and it was running awesome the entire time (#33 CM7).
Last time I noticed my phone on was like 17:33:xx hours. I had like 44% battery left. Next thing I know the phone is off. I tried turning it on and a battery icon flashed and turned back off.
What I am thinking is that perhaps the faulty battery driver is telling the phone that the battery is dead and preventing it from booting up. We were talking in another thread and I said something that really makes sense: If the battery driver tells the OS that there is 0% battery then it will just reboot. The battery itself may have a 50% charge left. That would explain the random reboots too (the battery driver telling the phone there is 1% left and cutting power). Maybe a hard reset semi-corrects the problem but eventually resets again due to false information.
My weirdness/powered off occurred right around 18hours. The phone could have just died too.
Almost need a Voltmeter so someone can test the battery (or however it can be tested).

player911 said:
Maybe jumping the gun here but I tried to let mine go as long as it could without resetting it. I kept tabs on it and it was running awesome the entire time (#33 CM7).
Last time I noticed my phone on was like 17:33:xx hours. I had like 44% battery left. Next thing I know the phone is off. I tried turning it on and a battery icon flashed and turned back off.
What I am thinking is that perhaps the faulty battery driver is telling the phone that the battery is dead and preventing it from booting up. We were talking in another thread and I said something that really makes sense: If the battery driver tells the OS that there is 0% battery then it will just reboot. The battery itself may have a 50% charge left. That would explain the random reboots too (the battery driver telling the phone there is 1% left and cutting power). Maybe a hard reset semi-corrects the problem but eventually resets again due to false information.
My weirdness/powered off occurred right around 18hours. The phone could have just died too.
Almost need a Voltmeter so someone can test the battery (or however it can be tested).
Click to expand...
Click to collapse
Yes I know the battery driver is part of the problem as can be seen on CM7 builds but what's odd is my time varies so for a long time it would reboot every 17-20 hours, now all of a sudden it goes to 36 hours before it usually reboots. Looking at logs it doesn't appear to throw any major errors before a reboot which implies that it's a a kernel panic or low-level fault. At this point I've given up on trying to find the issue since it's been repeated over and over that T-Mo and LG are releasing an update. Might as well enjoy the phone and wait for that to come out

Amen. Just keep flashing CM nightlies and you'll never worry about it.

[Q] Damaged Captivate - Any help would be appreciated.

I've searched the forums and have not seen anything quite like my problem, so if I missed an important thread, I'm sorry.
Over the weekend, I plugged my Captivate (using a stock battery) into the official Samsung charger and overnight my roommate semi-dislodged the charger. When I woke up and grabbed my phone it only registered a few hours of charging yet still had almost full battery. Upon rebooting the phone, I was sent into a bootloop. Not at the ROM, not at the Kernel, not even at the bootloader. It goes so far as to show the white loading ring at the center of the screen which never moves. At one point, a thin pink line appears halfway through the screen as it shuts down and reboots, never making it any farther. If I plug the phone in, it will boot normally though it does not accurately report battery levels or charging.
Other oddities: after 5 minutes of a phone call, the phone hard crashes. Not FC's, but just goes black. Upon a reboot, I get stuck into the same boot loop. If I plug the phone into the wall charger without a battery, it will go into the turned-off charging animation and show a 100% charged battery. Furthermore, my other roommate has a brand new i9000 so I tried that battery (again, stock Samsung) and it continues in the same bootloop. I have tried flashing other ROMS and going back to stock, but that does not seem to help.
Other info: I was running OneCosmic's ICS 3.1 with no overclock and light undervolting at the time. It was perfectly stable for the few days until the charger dislodged. I am also out of warranty and am not eligible for a hardware upgrade so repairing my Captivate would be ideal. I also have a usb jig if that is of any use to this scenario.
Has anyone experienced anything remotely like this? If not, what debugging steps should I attempt?

What I would suggest is using one of the ODIN one clicks and flash back to stock
Sent from my SGH-I897 using xda premium

I've flashed back to Rogers 2.2 stock. Doesn't help. It actually made it harder for me to get the phone started though I have yet to make a phone call from it.

Have you had the phone for less than a year? if so call at&t(or rogers) and they'll replace it for you.
then try factory reset
then try using odin or rom manager to flash back to stock
When all else fails, flash to cm7. that will completely wipe everything and start from scratch.
if that STILL dost work.... than you can be sure that its a hardware problem :/ theres nothing you can do except replace and sell for for parts.. sorry

You may want to try clearing the battery stats. Something in there may be telling the phone that the battery is completely dead and it shuts the phone down in the middle of the boot. Just a guess, though.
It sounds to me like the phone might have gotten confused aobut how much battery life it actually has. You might also try getting it loaded up and then letting it drain the battery completely down. Reset the stats and then fully recharge the phone.

Skoffer said:
You may want to try clearing the battery stats. Something in there may be telling the phone that the battery is completely dead and it shuts the phone down in the middle of the boot. Just a guess, though.
It sounds to me like the phone might have gotten confused aobut how much battery life it actually has. You might also try getting it loaded up and then letting it drain the battery completely down. Reset the stats and then fully recharge the phone.
Click to expand...
Click to collapse
I have exactly the same problem, I did the reset of the battery stats and still not working.
Did you solve the problem?
thanks
Martin

Thanks to everyone for their suggestions, however, no amount of battery calibration could get it to work. Furthermore, a bad flash has made the situation even worse. Now Im bootlooping even when plugged in and when unplugged my jig is of no help. I have declared my Captivate dead.
Best of luck toominds, if you get it to work, let me know. I'd love to have a spare phone sitting around.

Phone shuts off all the time

Hey everyone, thanks for looking at this and hopefully helping me out. I'm new to rooting my phone and installing new roms and stuff, but I researched about as much as I could for about a week before I even rooted.
Now I've moved on and installed a new rom (CM7). Before installing I used clockwork and formated the /system, /data, /cache, and dalvik. At first everything was ok, but after about 15 minutes it turned off. I read up on battery problems, so kept my phone plugged in all weekend (got up to 4.196V-ish, with 0mA in or out) then deleted the battery file, rebooted, unplugged the phone and let it drain completely (even while it still had a charge it would turn off randomly but I figured it would be ok). After it was completely drained I completely charged it again and it still randomly turns off.
At first I thought maybe it was just the rom, but no one else seems to have the same problem as me (that I can find), so I downloaded an ICS rom to try that. Same problems. So far I have done the following to try and find out WTF is going on...
Installed Elixr to see battery drainage (sitting at main screen doing nothing its roughly -8mA, but right after boot or opening a program it jumps to -300mA to -480mA)
Done NUMEROUS battery pulls (with and without deleting the battery config file)
Switched ROMS
Any help would be amazing
PS: Before rooting or flashing a new mod my phone would shut off on its own, but only once a week, maybe. Now it turns off as soon as I unlock my sim card. However, it doesn't turn off at all if I have it plugged in.

spcclark said:
Hey everyone, thanks for looking at this and hopefully helping me out. I'm new to rooting my phone and installing new roms and stuff, but I researched about as much as I could for about a week before I even rooted.
Now I've moved on and installed a new rom (CM7). Before installing I used clockwork and formated the /system, /data, /cache, and dalvik. At first everything was ok, but after about 15 minutes it turned off. I read up on battery problems, so kept my phone plugged in all weekend (got up to 4.196V-ish, with 0mA in or out) then deleted the battery file, rebooted, unplugged the phone and let it drain completely (even while it still had a charge it would turn off randomly but I figured it would be ok). After it was completely drained I completely charged it again and it still randomly turns off.
At first I thought maybe it was just the rom, but no one else seems to have the same problem as me (that I can find), so I downloaded an ICS rom to try that. Same problems. So far I have done the following to try and find out WTF is going on...
Installed Elixr to see battery drainage (sitting at main screen doing nothing its roughly -8mA, but right after boot or opening a program it jumps to -300mA to -480mA)
Done NUMEROUS battery pulls (with and without deleting the battery config file)
Switched ROMS
Any help would be amazing
PS: Before rooting or flashing a new mod my phone would shut off on its own, but only once a week, maybe. Now it turns off as soon as I unlock my sim card. However, it doesn't turn off at all if I have it plugged in.
Click to expand...
Click to collapse
Well, if you were having this issue before the rooting took place, this very well may be hardware related. There are a few things I recommend before the dreaded unroot and send back to manufacturer route (assuming the phone is under warranty still). It's been proven or at least shown that battery calibration (the whole charge to 0Ma and then fully discharge and then recharge) is a pipe dream.
I would first say find out if the CM7 ROM you're using is OCing or UVing, while you may see some people OCing to 1.3 or higher and UVing -75, not all phones are created equal in capabilities and some phones will randomly freeze/turn off if they don't like your OC and UV settings. I would also suggest flashing a different ROM to see if this problem persists. Cleardroid is what I recommend just to get an idea if it is in fact a OC or UV problem as I believe cleardroid is set up to default stock settings.
You can also try a new battery, I have heard/read/seen that bad batteries can cause reboots. Again though if this was an issue you were sometimes experiencing before, you may have hit the tip of the iceberg on a hardware issue and its finally starting to show now. Hope this helps.

spcclark said:
Hey everyone, thanks for looking at this and hopefully helping me out. I'm new to rooting my phone and installing new roms and stuff, but I researched about as much as I could for about a week before I even rooted.
Now I've moved on and installed a new rom (CM7). Before installing I used clockwork and formated the /system, /data, /cache, and dalvik. At first everything was ok, but after about 15 minutes it turned off. I read up on battery problems, so kept my phone plugged in all weekend (got up to 4.196V-ish, with 0mA in or out) then deleted the battery file, rebooted, unplugged the phone and let it drain completely (even while it still had a charge it would turn off randomly but I figured it would be ok). After it was completely drained I completely charged it again and it still randomly turns off.
At first I thought maybe it was just the rom, but no one else seems to have the same problem as me (that I can find), so I downloaded an ICS rom to try that. Same problems. So far I have done the following to try and find out WTF is going on...
Installed Elixr to see battery drainage (sitting at main screen doing nothing its roughly -8mA, but right after boot or opening a program it jumps to -300mA to -480mA)
Done NUMEROUS battery pulls (with and without deleting the battery config file)
Switched ROMS
Any help would be amazing
PS: Before rooting or flashing a new mod my phone would shut off on its own, but only once a week, maybe. Now it turns off as soon as I unlock my sim card. However, it doesn't turn off at all if I have it plugged in.
Click to expand...
Click to collapse
I guess the issue is with the battery itself. Try getting a new battery. I heard some guys experiencing the same and sorting things out replacing the battery....

Leave the charger plugged in. If it doesn't reboot then that will let you know most likely it is the battery.

Agoattamer said:
Leave the charger plugged in. If it doesn't reboot then that will let you know most likely it is the battery.
Click to expand...
Click to collapse
That was my thoughts exactly. However, if the ROM or kernel or whatever is set to shut off the phone at a certain reading of discharge from the battery, ie -500mA, this could also be the problem.
I thought it could have been a problem with the phone as well, but before it would shut off on its own MAYBE once a month. 90% of those I attributed to overloading the phone, closing facebook, opening the internet, starting to load a webpage then open a new txt I just recieved while the phone was still vibrating type things.
Now it still feels like it's just quitting on me, it never turns off while the screen is locked or while its charging. So far after the new ROM it has shut off when I place a call, when I receive a call, clicking on a notification, opening the messaging app, clicking download in the market, and my favorite when I unlock it from sleep.
I will download a different rom right now and try it. Just to double check this is what I've been doing to install a new rom... I boot my phone into recovery (vol- and power), go to recovery from the boot screen (opens clockworkmod), scroll down to mounts and storage, have it format /system, /data and /cache, go back to wipe data/factory reset, then install zip from sdcard, select the rom and go... I know some roms require inspiremod, should I still install this if I'm USING an inspire??
Thanks for the input guys, I really appreciate it

If it does turn out to be the battery or you just decide to get a new one to test it out. I recommend these, they are awesome and the only thing anyone should try besides HTC factory replacements. Good luck and I hope this works out for you.
Anker Batteries

i only skimmed this. but cleaning battery contacts can help also check the side door, sometimes that can cause issues as well. air can out everything and clean metal contacts with rubbing (ipa) alcohol.

So I installed cleardroid. Once again everything worked fine for the first 10-15 minutes and then the shutdowns started again, always when making the phone do something (unlocking, clicking a notification, opening a program, etc) but never when the phone is charging.
I'll clean off every bronze or gold contact I can find but I think I might be fighting a lost cause lol. Three different ROMS, all with the same problem leads me to believe its a hardware issue. Since all the chips in these phones are all small and use multilayer boards I won't be able to replace anything myself so I see a new phone in my near future.
Thanks guys!

If it doesn't do it when its chargeing then it is the battery. I had bought my inspire from someone and it was having those issues ordered a new HTC stock battery from newegg for like $12 and has been working perfectly since then and honestly if you want the best battery rom absolution is the rom you should check out. It's a non sense rom but again I'd just buy a new battery. I had mine timed it'd reset at 92% 74% and 49% xD
Sent from my Inspire 4G using xda premium

spcclark said:
So I installed cleardroid. Once again everything worked fine for the first 10-15 minutes and then the shutdowns started again, always when making the phone do something (unlocking, clicking a notification, opening a program, etc) but never when the phone is charging.
I'll clean off every bronze or gold contact I can find but I think I might be fighting a lost cause lol. Three different ROMS, all with the same problem leads me to believe its a hardware issue. Since all the chips in these phones are all small and use multilayer boards I won't be able to replace anything myself so I see a new phone in my near future.
Thanks guys!
Click to expand...
Click to collapse
hmm, I would say try a new battery before getting a new phone. Worst case scenario is that you spent $15 to learn you need a new phone as opposed to spending $100+ on a new phone...this is of course assuming you want to keep the inspire and not just looking for a reason to get upgrade ahaha

I agree. It still sounds like a battery issue.

I would agree this definitely sounds like an internal short in the battery. Sounds like it's shutting off whenever it gets a significant load on it. Try a new battery first.

I had a similar issue though I was tweaking the CPU. Learned my lesson.
Sent from my Inspire 4G using XDA App

Yeah, Id bet money that its a bad battery. I had this same exact issue with my Inspire. If it shuts off more in low reception areas but it isn't shutting off when plugged in, its definitely the battery. I would try to find someone with an Inspire and try switching them batteries and see if it stops.

If I tried to use the flash with my camera, the phone would shut off. My phone would randomly reboot or turn off. ATT told me they had "some" bad batches of batteries. My phone was still under warranty so ATT sent me a new battery. All the problems went away!

The battery door on the Inspire becomes wonky the more you open it, I was having a problem like yours, new battery and new door has me going good.

Random restarts

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/

Is my OPO dying?

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?