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?
Related
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.
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/
Hi everyone, i know the title seems like it's just a trival matter, but trust me it's not.
The phone was bought new in August of last year (2015).
The story so far: I've been using sultanxda ROM for over 6 months without any issues, but i decided to test a different ROM, so i downloaded Darkobas rom and GAPPS, the ROM and Gapps installed fine but when i started the device and i was doing the initial configuration the phone rebooted by itself. It happened about 3/4 times and after that the phone had entered a bootloop. I tried to reflash the ROM and gapps, but the phone was restarting during the flash in TWRP. I decided to go stock Cyanogen OS, so i did a clean fastboot install of cyanogen OS. Everything went well the phone was working fine, but a few hours after installation the phone was randomly rebooting again, i decided i'll live with it and wait and see if it goes away by itself.
The phone was rebooting 2/3 times a day, during different acitivities so it was hard to pinpoint what might the issue be (even when locked in my pocket with all apps killed). After a few days of usage it just went straight to bootloop, after that i had issues to even install a rom (even via fastboot), because it would install everything fine and then it wouldn't start properly and would be in a bootloop (straight after installation).
I also tried the Bacon Root Toolkit installation as well as formatting everything and wiping everything. But even with the usage of Bacon Root Toolkit the random reboots happened.
So i installed an older TWRP recovery, i wiped everything re-formatted the phone to F2FS (was EXT 4 b4) and installed a F2FS compatible ROM (can't remember which one), after that installation everything seemed to work fine, but after a day or so the random reboots came back to haunt me again. So i reformatted the phone to EXT-4 again, installed stock cyanogenmod via fastboot (the 4.4.2 version), and updated it to 6.0.1 via OTA (during the course of a day or so, but even when the phone was on 4.4.2 i had a random reboot once), and the reboots returned ( i tried many different solutions, even the command line in TWRP "make_ext4fs /dev/block/mmcblk0p15"). I had NO IDEA what might be causing them but i thought that maybe the processor is ****ed and it's overheating, i returned to sultanxda rom (with the underclock to 1957 mHz).
After returning the phone booted correctly after a clean install via TWRP, but now it's rebooting again, and sometimes it happens 4/5 times in a ROW, sometimes it doesnt even reboot, but goes to black screen and I have to push the power button for 6 + seconds for it to reboot.
I've tried the stability test, or running antutu a few times in a row to verify if maybe it's the processor's/RAM's fault, but the phone didn't care, it rebooted randomly (sometimes 6/7 antutu runs in a row and nothing happened, sometimes rebooting in my pocket with all apps shut down). I've tried different launchers/messing with WiFi options/turning off the proximity check/turning off the trust agents nothing seems to make a difference. At this point I'm at a loss of what to do so i came here to ask for any advice. Is there any way to check if the phones internal memory is corrupted in some way ? I've tried searching for some apps but nothing turned out.
oski131 said:
Hi everyone, i know the title seems like it's just a trival matter, but trust me it's not.
The phone was bought new in August of last year (2015).
Click to expand...
Click to collapse
flash this solved my problem http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
Flashed the persist.img the problem still occurs. 15 minutes after the flash the phone shutdown, black screen.
Your phone battery is dying...replace your phone battery and all the problem will go away....random reboot a couple of times and then goes straight to bootloop is a sign of a dying battery....trust me i know this cause it happen to me before and i'm sure you have the same problems....
this problems will get worst when you can only boot into your rom while your phone is connected to the charger and goes straight to bootloop when you disconnect the charger....
iPusak Gaoq� said:
Your phone battery is dying...replace your phone battery and all the problem will go away....random reboot a couple of times and then goes straight to bootloop is a sign of a dying battery....trust me i know this cause it happen to me before and i'm sure you have the same problems....
this problems will get worst when you can only boot into your rom while your phone is connected to the charger and goes straight to bootloop when you disconnect the charger....
Click to expand...
Click to collapse
Shouldn't the battery meter go crazy after reboots or something ? Well i guess i'll try this, the battery is not a costly component. Are there perhaps any bigger batteries than the original one with bigger backs ?
oski131 said:
Shouldn't the battery meter go crazy after reboots or something ? Well i guess i'll try this, the battery is not a costly component. Are there perhaps any bigger batteries than the original one with bigger backs ?
Click to expand...
Click to collapse
Nope...the battery remains like normal but random reboot will happen more regularly until bootloop....
Not sure if there is a bigger battery but there is one thread here that show one battery with 3600mAh and don't buy OP2 battery as it is not compatible with OPO...
Sent from my A0001 using Tapatalk
Ok thanks for the help, will report back with new battery.
Switched the battery, the random reboots still happen, decided to do a clean flash, after wiping the phone in TWRP during the flash of GAPPS the phone rebooted itself and is in a boot loop currently.
Ok so the reboots stopped, it was a battery issue, but now i have a problem with battery indicator it's stuck at 50 % all the time and the phone does not show when it's charging (no information, no LED color), but the battery is being charged because when i shut it down and connect the charge and battery level (which shows when the phone is off) increases.
I've tried to use it untill it shuts down then i charged it while it was off for 6 hours, but after turning it on it still showed 50 %. I've also deleted the batterystats.bin using TWRP but it still did not help. Any ideas how to make it show the correct % ?
oski131 said:
Ok so the reboots stopped, it was a battery issue, but now i have a problem with battery indicator it's stuck at 50 % all the time and the phone does not show when it's charging (no information, no LED color), but the battery is being charged because when i shut it down and connect the charge and battery level (which shows when the phone is off) increases.
I've tried to use it untill it shuts down then i charged it while it was off for 6 hours, but after turning it on it still showed 50 %. I've also deleted the batterystats.bin using TWRP but it still did not help. Any ideas how to make it show the correct % ?
Click to expand...
Click to collapse
told you it was a battery issues but look like you have another battery issues here...try disconnect the battery from the motherboard for 1 minutes before connect it again and do offline charge for atleast 30 minutes....after 30 minutes reboot the phone and look at the battery percentages...if its goes above 50% then you have solved your problems....if it doesn't then you might bought a bad battery....you need to contact the seller that sell you the battery and asked for replacement....
Well unfortunately after changing the battery for a second one (the random reboots started again on the new one) the issue still prevails, so i'm currently writing a ticket to oneplus in hopes of some help.
Thank you iPusak Gaoq™
iPusak Gaoq™ said:
Your phone battery is dying...replace your phone battery and all the problem will go away....random reboot a couple of times and then goes straight to bootloop is a sign of a dying battery....trust me i know this cause it happen to me before and i'm sure you have the same problems....
this problems will get worst when you can only boot into your rom while your phone is connected to the charger and goes straight to bootloop when you disconnect the charger....
Click to expand...
Click to collapse
You Sir iPusak Gaoq™ are amazing. I 've searched for 2 whole weeks and no one was able to zero in on the issue.
After reading your post, I changed my battery. 3 days back. Till now my phone is as good as new.
I cannot thank you enough. I tried everything from recovery to rom to stock.
Thank you Thank you thank you.
What peace of mind now !!!!!!!
You can try this it solved my problem without changing battery :-
https://forum.xda-developers.com/k5-plus/how-to/solving-random-reboots-problem-t3682037
Hey there,
i got a used OPO from a friend, and no matter what i try, it always does the same thing:
After about two weeks of working flawlessly it reboots randomly and gets stuck at the boot logo (says "Cyanogen" or shows the animated "bow" in case of Lineage).
I have tried the stock CM11 & 13 roms, i also tried Lineage for some time, every time with a clean flash. Still the same issue comes back after two weeks.
Sure - after a factory reset the phone boots normal again, but i know it wont last long...
Do you guys have any idea what could cause this? Maybe a hardware fault?
eraser87 said:
Hey there,
i got a used OPO from a friend, and no matter what i try, it always does the same thing:
After about two weeks of working flawlessly it reboots randomly and gets stuck at the boot logo (says "Cyanogen" or shows the animated "bow" in case of Lineage).
I have tried the stock CM11 & 13 roms, i also tried Lineage for some time, every time with a clean flash. Still the same issue comes back after two weeks.
Sure - after a factory reset the phone boots normal again, but i know it wont last long...
Do you guys have any idea what could cause this? Maybe a hardware fault?
Click to expand...
Click to collapse
Battery fault.What's the health of battery like?
Thanks for your input Mr.AK!
The battery seems fine, the phone can go fo multiple days if i dont use it much.
Also (according to the description of others) the phone should be "boot looping" and also boot when connected to a charger. Mine does neither :/
eraser87 said:
Thanks for your input Mr.AK!
The battery seems fine, the phone can go fo multiple days if i dont use it much.
Also (according to the description of others) the phone should be "boot looping" and also boot when connected to a charger. Mine does neither :/
Click to expand...
Click to collapse
You should get your device checked from a professional repair shop then.
Maybe try an Oreo Rom. If problem persist, I would say it's the battery
eraser87 said:
Thanks for your input Mr.AK!
The battery seems fine, the phone can go fo multiple days if i dont use it much.
Also (according to the description of others) the phone should be "boot looping" and also boot when connected to a charger. Mine does neither :/
Click to expand...
Click to collapse
When you need charger connected to boot your phone that means that the battery is at it worse state so you phone battery might not be at those point yet but it doesn't mean that its not a battery problem...easiest way to figure out that the battery is not good is looking at the battery percentage after reboot or after you have solved the bootloop...if the battery percentage drop drastically (even 5% drop) after reboot then your battery is at bad state and will become worse eventually...