I've been using Lineageos 14.1 (and Xposed) on my Nexus 5 for yesrs and am happy with it. But in the last week I've been having crashes, usually when waking the phone from sleep. When that happens I can sometimes just reboot but other times I was faced with repeated bootloops and I've had to go into twrp recovery and "reboot system" to get back to a working phone.
To resolve the crashes and boot loops the first few times this happened, I deleted the Davlic cache and cache. The problem persists.
I updated lineageos to the latest Jan 3, 2019 even though I don't think this has anything to do with linesgeos which has worked for years, but the crashes continue.
I just don't know "how" to troubleshoot this problem beyond what I tried. What should I do to find out what is causing the phone to crash?
Any troubleshooting suggestions appreciated.
To determine if it a software issue, I suggest flashing the latest stock Google ROM. If the crashes stop, you'll know it is a custom ROM issue.
audit13 said:
To determine if it a software issue, I suggest flashing the latest stock Google ROM. If the crashes stop, you'll know it is a custom ROM issue.
Click to expand...
Click to collapse
Thank you for replying . I'll try that although the problems started without my having upgraded from the same rom I've used for a long time.
Would some kind of log help?
Thanks again.
A log would certainly help the developer.
Have you posted your query in the ROM thread?
Yes and got no reply so far.
Related
Hi,
I'm having trouble with my OpO since I rootet it. Here is the history:
-Day One: Just stock 25R, installed all Apps via google play, no problems whatsoever.
-Update 30O still no problems.
-Then I rootet the phone and flashed TWRP recovery to install the Titanium Backups of my old Nexus 4. Thats when I had the first random reboots. Some while Browsing in Chrome, Some on Youtube, Some while listening Music on Hedphones.
Since I have no Sim-Pincode activated a reboot just means, that I'm Offline for about 20 seconds but having that about 5 times a day just isn't acceptable.
-Then I got the 33R OTA update, which made my root and TWRP recovery disappear because I forgot to make a check in the developper settings, but that did not make the reboots disappear
-Today I flashed the 25R stock Image of the Firmware via Fastboot to set my One to real Factory status. I only installed apps via google play and recovered the app data of 2-3 apps via helium backup without root. I got the two OTA updates, and another reboot.
-Then I rootet the thing again, to use a logcat app, and now I have two logcats ending with a reboot.
I really hope that you can help me since I allready sold my old phone and expect that it will take really long until I get a new OpO here in Germany.
The next thing I will do is flash the 25R Image again and install the apps without using helium at all and leave out the goolors icon pack that I used before. But after that I'm absolutely out of ideas.
UPDATE: Yeah so it's definitely a HW defekt or something I cannot solve. I just wiped everything via TWRP, then flashed the factory image 25R without root and just installed some apps via google play. But after one hour I read an email and it rebooted....
Unfortunately I cant post the links to the logcats due to my low post count.
Logcats don't help you when it comes to finding out what is causing your phone to reboot. It is last_kmsg that is responsible for debugging reboots.
A hardware defect would not be causing your phone to reboot, its something to do with the way your phone is configured / set up.
I would highly recommend you to start from scratch completely and do the following,
- Flash XNPH33R http://dist01.slc.cyngn.com/factory/bacon/cm-11.0-XNPH33R-bacon-signed-fastboot.zip from scratch. Make sure you do wipe.
(OR.. flash a custom ROM after wiping)
- List all of the apps that you currently have installed.
- Are you using Xposed?
- Whats your set up? ROM/Kernel/Gapps/etc.
I am not using any custom Rom, root, custom kernel or xposed module.
I just wiped everything in TWRP and flashed the 25R factory image. After about one hour of installing apps in Google play and loging into account i got the first reboot.
I can try flashing the image that you postet tomorrow but thats the same Rom that Im using now
Ord3r66 said:
I am not using any custom Rom, root, custom kernel or xposed module.
I just wiped everything in TWRP and flashed the 25R factory image. After about one hour of installing apps in Google play and loging into account i got the first reboot.
I can try flashing the image that you postet tomorrow but thats the same Rom that Im using now
Click to expand...
Click to collapse
I meant, you can try a custom ROM and see if you can reproduce the problem. Custom ROMs are running on code that is much newer than CM11S.
Ensure you're on XNPH33R when it comes to OTAs.
I just wanted to add my frightful experience. I've had the OPO for two weeks now without problems and no random reboots. Had my first reboot today and just now my phone powered off and wouldn't turn back on. I plugged it back into the wall charger and it turned itself back on but was stuck on the boot logo. I tried holding down the power button to turn it off but nothing. Pressing the power button only turned the display on and off but still stuck on boot logo. Eventually I held down the power button and volume down and the phone buzzed and went to recovery. I'm on stock 33R and Franco's kernel. Haven't tweaked anything. Now I'm afraid my phone is going to brick itself.
Sent from my A0001
Yeah so this is definitely getting worse. At first I had 1-2 reboots a day but today after unplugging I already had 3 reboots in one hour.
I think I am definitely going to send it back when I'm back home next Week.
I already flashed stock Firmware 3 times and did what feels like 10 full wipes in one Week.
This cant be normal. Apps that I installed that arent in the top 50 in the play store are: Dailyme, yatse for xbmc, line, Wolfram aplha and ogyoutube.
That really sucks. I already sold my nexus 4 and have no other phone left
Btw: I'm on 33R for the third time this Werk. Everytime via OTA
Try a different Rom like crDroid + AK Kernel. Running this 2 things since 2 weeks and i only got one reboot just because my camera stopped working because in undervolted my phone ^^
THX but I just want a functioning phone. And since I have errors that nobody else has I think that it is a Hardware issue. At the Moment I am waiting for a answer from one plus so i can send it back
Ord3r66 said:
THX but I just want a functioning phone. And since I have errors that nobody else has I think that it is a Hardware issue. At the Moment I am waiting for a answer from one plus so i can send it back
Click to expand...
Click to collapse
ok I understand your frustration but to fully test your phone you will need to run stock and stock only with no outside apps loaded. Try and do this for a day or half a day or so and see what your results may be. Its your phone and of course do what you like but testing your phone and doing the same thing every time as in reloading your apps is not a good way of fully testing.
also did you do a last_kmsg report as recommended.
Okay will do that. Is there a tutorial to do a last_kmsg report? Do i need root?
Ord3r66 said:
Okay will do that. Is there a tutorial to do a last_kmsg report? Do i need root?
Click to expand...
Click to collapse
Yes you need root. After a reboot just pull the last_kmsg file from /proc/ using adb, file Explorer of your choice, etc.
Sent from my One A0001 using Tapatalk
Ord3r66 said:
Okay will do that. Is there a tutorial to do a last_kmsg report? Do i need root?
Click to expand...
Click to collapse
of course there is a tutorial there is a tutorial for everything.... Got to utilize google my friend.
OKay it's me again. Meanwhile the Oneplus support answered my mails and told me to flash custom Kernels to resolve the issue.
Since Yesterday I tried three Kernels (Franco, Heeroluca and AK) and nothing changed, so now I start to gather some Last_kmsg files name it after the APP where the reboot occured and upload it here. Ofcourse I'm also sending those files to the Oneplus Support
Here is the first one:
https://dl.dropboxusercontent.com/u/43103242/1_Line_Messenger_last_kmsg
https://dl.dropboxusercontent.com/u/43103242/2_standby_screenoff_last_kmsg
Have the same problem. Using wi-fi -> reboot. Don't know how to fix this defect. I hope a solution will be found
Had a random reboot while browsing chrome. I was scrolling down the page and received a text at the same time when my screen froze. After freezing for a few seconds, it rebooted itself. I tried getting the last_kmsg but it tells me that it isn't found. The code I used was: "su" followed with "cat /proc/last_kmsg > /sdcard/last_kmsg.txt" in terminal emulator. Let me know if there is anything else I can do. Thanks!
I have also problems with chome beta browser. I get freezes. Is this issus only with chrome or with all browers?
Gesendet von meinem A0001 mit Tapatalk
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Jst flash a newer modem in recovery
mugoftee said:
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
Click to expand...
Click to collapse
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
PivotMasterNM said:
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Click to expand...
Click to collapse
That won't help, flashing an older build than what was previously installed without wiping properly will cause problems.
KURDKiNG said:
Jst flash a newer modem in recovery
Click to expand...
Click to collapse
Modem has nothing to do with this.
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
KURDKiNG said:
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
Click to expand...
Click to collapse
Most likely pure coincidence.
Thanks your reply!
Heisenberg said:
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
Click to expand...
Click to collapse
Actually this is what I did in the very first beginning but I encountered the same rebooting symptoms like after the OTA update. Since it didn't seem to change anything I didn't mention it. I used cm-12.1-YOG4PAS1N0-bacon-signed.
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
mugoftee said:
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
Click to expand...
Click to collapse
I don't think you have any other option unfortunately.
I have an occasional problem where my tablet will be loading an app (different apps) and it just freezes and then reboots.
Its running different apps so hard to pin down. Ive flashed the latest rom build (12.1-20160119-2048-UNOFFICIAL-P5110 at the moment) several times and its been the same through them all. Its also occured on previous roms.
What is the easiest way to diagnose the problem as I believe logcat resets after the forced reboot so I havent a clue how to diagnose it.
Could it be the Recovery or the Kernel that need updating?
I have the same problem with craching and rebooting on both Tab2`s in the house.
One completly stock and one with CM11.
Mabye an faulty app ?
Steveh8204 said:
I have an occasional problem where my tablet will be loading an app (different apps) and it just freezes and then reboots.
Its running different apps so hard to pin down. Ive flashed the latest rom build (12.1-20160119-2048-UNOFFICIAL-P5110 at the moment) several times and its been the same through them all. Its also occured on previous roms.
What is the easiest way to diagnose the problem as I believe logcat resets after the forced reboot so I havent a clue how to diagnose it.
Could it be the Recovery or the Kernel that need updating?
Click to expand...
Click to collapse
Well, it is happening with everyone, the apps have become memory hungry and our devices lack RAM, andoid L, and our device kernel is full of bloatwares, our devs are trying very hard to overcome this, and we hope they will succeed in this too.
many people are of the view that android M has better management of ram, and I have seen in other devices that have confirmed they are experiencing better stability than lollipop. well on our device it's still in alpha stage, so wait and watch. till then keep your tab less burdened.
Steveh8204 said:
I have an occasional problem where my tablet will be loading an app (different apps) and it just freezes and then reboots.
Its running different apps so hard to pin down. Ive flashed the latest rom build (12.1-20160119-2048-UNOFFICIAL-P5110 at the moment) several times and its been the same through them all. Its also occured on previous roms.
What is the easiest way to diagnose the problem as I believe logcat resets after the forced reboot so I havent a clue how to diagnose it.
Could it be the Recovery or the Kernel that need updating?
Click to expand...
Click to collapse
Try changing SElinux to enforcing.
It helped me in my P3110.
HIT THE THANKS BUTTON IF I HELPED YOU
Zte blade l said:
Try changing SElinux to enforcing.
It helped me in my P3110.
HIT THE THANKS BUTTON IF I HELPED YOU
Click to expand...
Click to collapse
Hi, thanks for the reply but how the hell do you do that lol
Sent from my GT-P5110 using Tapatalk
Steveh8204 said:
Hi, thanks for the reply but how the hell do you do that lol
Sent from my GT-P5110 using Tapatalk
Click to expand...
Click to collapse
No need for that, just follow the original thread, bugs have been squashed. There are no more random reboots on latest builds.
Good day everyone. So I recently started to experience weird freezes and crashes of most of the apps. Like facebook, instagram, some games. Not all of the apps do this. It all started about a month ago. I tryed using multiple diffrent ROM's. Although that ROM did work correctly for another month before these errors came up. Now I am using Global Elite rom: https://forum.xda-developers.com/galaxy-s6/development/sm-g920f-sm-g925f-griffin-t3435461
I always do a clean flash. Rooted with magisk, even though I was using SuperSU for other roms. Any help will be aprecieted. I am suspecting hardware failure (anyway to test that?). Thanks in advance.
Bumping this thread. Things getting worse... Please anyone. I am desperate...
Why don't you revert to your initial ROM, the one that never caused any issues?
RossTeagan said:
Why don't you revert to your initial ROM, the one that never caused any issues?
Click to expand...
Click to collapse
Problem is that every rom I've tried do same things. What is left to try is stock official firmware. But I will have to try it later as I am currently on the go.
Try to do a factory reset and see if the problem persists.
Hi,
Has anyone experienced random reboots or similar issues after upgrading to Android 10? I'm on retla and, since receiving the new version a couple of days ago, my phone has been rebooting randomly. Sometimes it's 5 times in a row, others only once. I know a factory reset might help, but I was hoping not to get to that instance. While on Android 9, I never experienced similar issues with this phone, and no new apps have been installed recently.
Thanks.
Hi. No reboot for me. I recommend reset.
No reboot for me x2
Thank you all for confirming this. I'll be performing a factory reset then.
my phone has been rebooting randomly too.Hard reset and factory default did not help.I wait fix from moto
My phone also reboots by itself mostly at night:crying:
For me works stable
It looks like a factory reset resolved the issue for me. It's been 2 days without reboots...
joseph_1802 said:
It looks like a factory reset resolved the issue for me. It's been 2 days without reboots...
Click to expand...
Click to collapse
Not for me (((
Also happening to me. Happened in android 9 and solved on their last update before android 10. Now it's happening again, hopefully it will be solved on Motorola's next upgrade patch