Database Info

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/

Random reboots.

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

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?

OPO bricking itself around every 2 weeks

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...

Serious Problems after OOS 10.3. Update/Dying battery? Please Help

Hey guys, so I recently updated my OP6 from OOS 9.0.9 with TWRP 3.2.1-0 and Magisk 20.1 to OOS 10.3 with TWRP 3.3.1-16, Magisk 20.1, and xXx NoLimits 9.4 and I'm having a bunch of really strange, some of which are scary, issues. If anyone else has been experiencing any of these, or has any sort of possible fix I can try, please let me know. The problems I've been experiencing include
- Random reboots across different apps
- On one occasion, it randomly rebooted and went into a bootloop for about 10 minutes, I had to boot into recovery and reboot into the system to fix it
- When I woke up, after charging it over night, tap to wake, the fingerprint scanner, and the power button were all unresponsive. I had to hold the power button down and reboot. I've had this problem about 3 times in the past 3-4 days.
- Battery seems to be draining faster than normal, around 5-6 hours
- On one random boot, when I check the storage tab, it said 100% used and when I clicked on storage, the settings would crash
- other miscellaneous settings tabs randomly deciding not to work
- multiple settings crashes after clicking various options in settings
And these two are what's scaring me the most because I'm afraid something is wrong with the battery
- I let the phone charge over night, but when I checked it in the morning, it said had a 67% charge. When I unplugged it from it's charger, it continued to say "Charging Rapidly" until I rebooted the device and it jumped to 99%
And
- I charged the phone over night as I usually do. My phone was at about 50% when I plugged it in, but when I woke up, the phone was dead and I had a message that said something like "Battery is too low, please charge for a few minutes before powering on", a message I've never seen, even after using the phone till it died. Once I charged it up a bit, it booted like normal, but when I checked the battery history, you can see it rise from 50% to about 70% before immediately dropping to 0% (pic attached)
Does this mean my battery is dying? Before I updated to OOS 10.3, my phone was fine and I had NEVER experienced anything even close to these. Is this a problem with my battery? A bad Android 10 install? Or are these just common problems with A10? Should I just try reinstalling A10, and if so, could someone give me the best way to do so? Any sort of help is appreciated, please let me know.

And the most standard question..
Did you do a clean install or just updated over Android 9.x?
Sent from my ONEPLUS A6003 using Tapatalk

RASTAVIPER said:
And the most standard question..
Did you do a clean install or just updated over Android 9.x?
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
I had flashed over 9.0.9, I'm assuming that was the problem. I'm still pretty new to rooting and flashing and what not so I wasn't even aware of the differences between "clean" and "dirty" flashes. After a bunch of reading, I think I figured it out. I did a full wipe and "clean" flashed it and everything seems to be ok so far. Sorry if this is a noobie post that gets questioned over and over on here, but thanks so much for the response.

Juwapa said:
I had flashed over 9.0.9, I'm assuming that was the problem. I'm still pretty new to rooting and flashing and what not so I wasn't even aware of the differences between "clean" and "dirty" flashes. After a bunch of reading, I think I figured it out. I did a full wipe and "clean" flashed it and everything seems to be ok so far. Sorry if this is a noobie post that gets questioned over and over on here, but thanks so much for the response.
Click to expand...
Click to collapse
Remove xXx and see if problems continue

I had the same problem this guy did. I removed nolimitxxx 9.5 and the phone is snappy again and no overheating