So tonight I tried the new Cm13 that got updated, doing a full wipe. All went good after a bit of testing, finding that the camera bug I already knew about was there, but after installing a few of my apps that I had before at the same time I tried installing some unofficial ones from .apks, Google Services Framework started crashing and my launcher, Trebuchet also did, so as the settings when I tried getting into the apps screen to try wiping data and cache for the settings app. So I got stuck there. Luckily I had a backup and succesfully restored to my last ROM with most of my data back. I did try anything I could think of to stop the crashing, except flashing another Gapps package. I did try reflashing the same with no success to fix the crashes. On the thread it recommended the Nano package because that provided you with the option to hold home button to Screen Search...
Thank you for any answers. BTW I also tried wiping those apps data trough Titanium Backup with no succes, again. :crying:
How do I stop Google Framework Services and settings (when entering app management screen) from crashing?
Galaxy J500-FN Current ROM: Ressurection Remix Android 5.1.1
Hi,
A few days ago I experienced a boot loop on my Nexus 10 with Lineage OS 13, build 20170909.
I broke it down to a recent update of Nova Launcher - going back to an older version and preventing Google Play automatic updates fixed it for me.
There are a number of reports of the same symptom pointing to Nova Google Companion, TeslaUnread, IFTTT, and Action Launcher.
I don't think this is an issue in those apps, but rather caused in the OS - an App should not be able to bring down the OS to a reboot (and even worse, due to the automatic restart of the launcher, causing a reboot loop).
any ideas of a fix in the OS? something else to prevent this from happening again?
Regards
sthones
I confirm the same. Constant bootloop with Nova Launcher
I am also experiencing this on an older version of CM13. Clearing cache does not work. Any quick fix possible via recovery?
stephendt0 said:
I am also experiencing this on an older version of CM13. Clearing cache does not work. Any quick fix possible via recovery?
Click to expand...
Click to collapse
I had the same problem with a Galaxy S3 running OctOS (CM13 based Android 6.0.1). The Nova Launcher update caused my phone to crash and reboot as soon as it was unlocked.
I was able to disable Nova in recovery (TWRP) using the built-in TWRP file manager. navigate to /data/app/com.teslacoilsw.launcher/ and delete base.apk. This will keep Nova from loading on startup but will not delete your data. My phone worked fine after that, albeit without Nova.
Thanks a lot, removing base.apk stopped the reboot loop.
My device has just started a bootloop too, but I don't even have Nova installed on it (though I do on my phone), just the stock launcher in CM / LineageOS.
I reset it to factory defaults and then it boots, but when it restores my old apps it starts looping again, so one of them is the cause. I didn't learn anything from the log via adb.
Any ideas?
I discovered it was one of my apps causing this. I removed it and it boots ok. https://play.google.com/store/apps/details?id=au.com.realestate.app&hl=en
hmoffatt said:
I discovered it was one of my apps causing this. I removed it and it boots ok.
Click to expand...
Click to collapse
Thanks for the hint, it was a real estate app from germany (immoscout24) which caused the problem at my device. Deleted the base.apk and everything works fine again.
Happening to me now, ffs im on the latest nightly and thats not fixed it.
TheRealSmurf said:
Thanks for the hint, it was a real estate app from germany (immoscout24) which caused the problem at my device. Deleted the base.apk and everything works fine again.
Click to expand...
Click to collapse
Same here.
daseddy said:
Same here.
Click to expand...
Click to collapse
Mine just started boot looping yesterday, but I hadn't installed any new apps in a while, and I have automatic app updating turned off (I also don't have any real estate apps installed, German or otherwise). Any hints on how to track down the culprit? Is there a boot log to look at?
Thanks!
Folks, there is a defect open in the official lineage bug tracking system. please add your comments there - maybe this needs some more support to get looked at:
https://jira.lineageos.org/browse/BUGBASH-1075
Same here. Started happening after it updated my apps yesterday. Removed nova launcher and all other Teslacoil software, problem remains. Can only start the tablet in Safe mode.
Seeing this on my device as well, except I am not able to remove the base.apk file because the app I installed somehow corrupted my bootloader such that I cannot get into recovery mode.
The culprit app? LinkedIn. Automatic app updates were turned off, and just before the bootloop started, the last thing I did was install that app. It finished, it rebooted, and hasn't stopped rebooting since.
When I put it into bootloader mode, it stops the continual rebooting and displays the "open panel" robot and "Downloading... do not turn off target". From there, all I can do is press power to start, then it goes back into rebooting. There is no way to get into recovery mode from there.
Also, attempting to keystroke into recovery mode just restarted the lineos infinite reboot.
Can't get into recovery, can't get the bootloader out of "Downloading" mode, and lineos continually reboots... Any wise sage souls have any ideas on this one? It looks like my device is bricked
It got me too - I don't have Nova Launcher installed. A few weeks ago the device started bootlooping with a build I had installed since september. I updated to one of the latest builds and had the same issue again. At the moment i got it working most of the time, but when i start certain apps it just reboots.
Seems to be independent to build version and can occur with different apps (at least thats what I've read here...).
Is this a Lineage Os 13 only thing or can I throw the device away now?
Greetings
I started having this issue this week as well. Oddly enough, I was still on CM12.1. In the middle of watching Plex and it rebooted, and has been boot-looping since. I did a factory wipe and while installing apps, it started looping again. I then installed the latest nightly of LOS13.1 and again, once it got part-way installing apps, it started boot-looping again. So this is not just a LineageOS thing, it seems to be an app update (I do have auto-update turned on).
I´m having the same problem without ever have the Nove Launcher installed. The bootloop started on my device several weeks ago. I tried to fix it by wipe partly or total and reinstall the latest nightly of los13 (20171126) and opengapps micro 27.11.2017 (and everything else).
As soon as I reinstall my apps, los goes back to bootloop. Sometimes, when I manually install only few apps, the system seems stable, until die next updates come by the play store.
So now I went back to stock rom until I´m getting aware of the problem beeing solved.
workaround, maybe
I wouldn'n call it a bootloop but rather a startloop
Anyhow, in my case I was able to break the loop by entering android's safe mode by simultaneously pressing vol up and down keys during startup. In safe mode, I was able to delete offending apps. After reboot, system is running again. Apps identified so far to make lineageos unhappy: open camera, yalp store, YouTube(!).., oruxmaps.
Removing offending apps works
Thank you!
I did the same with your advice... removed some apps and it works. I went back to September ROM, then update to Nov ASB ROM and it works fine.
ShevT is on it, here https://jira.lineageos.org/browse/BUGBASH-1052
and here: https://review.lineageos.org/#/c/197386/
Hope it gets fixed and merged soon... as this has been a pain the neck for a while, possibly related to a similar problem earlier this year.
loveandmarriage said:
I wouldn'n call it a bootloop but rather a startloop
Anyhow, in my case I was able to break the loop by entering android's safe mode by simultaneously pressing vol up and down keys during startup. In safe mode, I was able to delete offending apps. After reboot, system is running again. Apps identified so far to make lineageos unhappy: open camera, yalp store, YouTube(!).., oruxmaps.
Click to expand...
Click to collapse
I'm running CM13 and I have the same problem. I am not tech savvy with installing ROMs but managed to get to TWRP and did a reset to factory. Got part way thru optimising apps and the problem came back. I could only turn the tablet off via TWRP!
I don't mind going back to stock rom but not sure how to do it..best I look on here and start to educate myself..I'm 73yo so might not get finished before my time is up
Hi amm my G7102 enters bootloop immediately after installing whatsapp application has been tested on lolipop CM and Recuression remix, knowing that it was working fine before that. also note I flashed many times and used stock firmware.
how to fix that issue?
same problem for me... hav u found any fix???
Yup..I was to using cm and RR...But Whatsapp issue didn't came ..But installing other apps such as magisk manager...The problems come.. there is not fix to solve the problem..But if you want to use RR only then use RR Xperia mod ROM..In tht ROM apps installed properly... Or change the rom
I also had this issue, running LineageOS 13 6.0.1 on a Redmi Note 4 SD, and the latest WhatsApp update just crashed all the background apps and after a reboot it just stuck in a bootloop. Luckily I had a somewhat recent TWRP backup, so I recovered it and just removed Whatsapp. I wonder what happened there... I DO had the beta version installed, but I've been using Whatsapp beta without problems for years. :S
Same issue w/ cm12...only after installing the wapp.
Tried recerting by manually downloading to march ver. Still the same.. The moment wapp is installed, phone goes into bootloop. No other option to factory reset..
Any possible clues.. Had someone tried a more old version 2017??
i have same problem using CM12.1. Try this :
if your phone bootloop : uninstall whatsapp from safe mode ( press vol - ) while boot.
uninstall whatsapp from play store.
download whats app apk from apkmirror.com ( i'm using whatsapp 2.18.117 (beta).
and it's work fine now.
Now using CM12.1
I ran into the same problem when I installed greenify on CM12.1. Dunno if there's a fix or not but I figured out how to get out of the bootloop. My theory was, If any app installation caused bootloops, it means the app installation was somehow interrupted and this app is now in a broken state. You just have to boot into TWRP, use TWRP's file manager or aroma file manager to delete all app related files from data/apps or other app related folders. I deleted all Greenify related files and my phone got out of bootloop and booted normally.
Thank you sir, you helped me greatly!
CM 110.0 boot looks
Updates of several apps including Whatsapp are causing my phone to go into boot loop. I had to do a factory reset and sideload of older versions of the apps (where available).
I am running Cyogenmod 11.0 Android 4.4.4 on a Oneplus One.
Does anyone have a solution for this problem? I have been using an older version of Whatsapp but support for that version is going to be cut off by Whatsapp in a few days.
Thanks for any help.
Hy everyone
After a lot of searches and flashing I have to open this thread.
No matter which oreo or nougat rom I tried I got constant app crashes and random reboots.
I have tried all oreo roms, nougat Roms and eui roms too.
Sometimes app crashes after one day or instantly after flashing.
I have tried different modems.
Tried without xposed and magisk but still apps start crashes on each rom.
I have clean flashed everytime too. But don't know why this is happening on all roms.
any one can help me out?
Thankyou
Heyyo, have you also tried doing a TWRP format data (by format data I mean format and not wipe) and then not restoring from a Google Cloud backup? There is a small chance that it could be a setting or something from your Google Cloud backup causing the instability.
Bit better
Hey, Thanks a lot for reply and I am sorry that I just read your response right now
First of all I didn't use Google cloud backup
I only restored from Tb.
I have already formatted data as you said and flashed new rom. Didn't even restore data from Tb.
As soon as I installed three to four apps from playstore phone restarted.
After installing all apps and setting up my phone.
Now app crashes are lot less then before but they still crashes like just Google stopped working until I restart phone.
Different app crashes after sometime and I have to restart phone to get them back to Work. Phone also restart sometimes.
Don't know why it's like that...
Is there any way I can check which app causing problems by myself?
Any suggestions?
Thank you
Hello XDA community,
I recently purchased the Nothing Phone 1 running on the latest version of Android 13. After rooting my phone using Magisk, I installed several Magisk modules which worked fine initially.
Here's a list of Magisk modules that I installed in chronological order:
Font Manager
NotoCJK
Fullscreen/Immersive Gesture
G-visual (later closed as I didn't see any effect)
Shamiko
DRM disabler
Revanced Youtube
Webview Manager (replaced with ungoogle chromium)
Nexus Media Before installing the 10th module, I took a full backup of my device using Titanium Backup. However, during the backup process, it got stuck while backing up a file named "Media 13-9427200." After several attempts, I had to cancel the backup for this file to complete the backup process.
Pix3lify (failed to unpack boot image and finally used slim mode)
Safetynet fix
After installing the 11th module, I went to bed and installed several applications before sleeping, such as Kiwi, Shizuku, App Ops, Buzzkill, Automate, Vmos, Brevent, and Greenify.
12.Audio Modification Library
13.Ainur Narsil
After installing the 13th module, I noticed that my phone started behaving abnormally, and it would automatically reboot. Every time I start the phone, the interface freezes after two minutes, and it restarts automatically after several seconds. This scared me, so I uninstalled all the Magisk modules and applications installed after the 11th module and disabled the two audio modules, but it didn't seem to work. So, I turned off the phone for a few hours, and it seemed to work fine after that.
When I tried to log in to my Reddit account, I found that I couldn't use "Continue with Google." When I went to the Google section in Settings, I found that I couldn't open it either.
I searched for solutions online and found that the problem might be due to the Webview. I replaced it with Ungoogle chromium and downloaded the latest version of Android Webview from the Play Store and disabled WebView Manager. But nothing worked. I tried updating the Carrier Services and clearing the Google Service's cache, but it didn't work either. (All Google apps can be opened and used normally.)
After updating the WebView, things got worse. I use a third-party launcher called Smart Launcher, and I have many customized app icons. I found that all customized app icons no longer work, only the native icons can open the app.
I am really frustrated and everything seems out of my control. I decided to restore all the data from the backup I made last night using Titanium Backup (in snap mode). Unfortunately, after the restore was complete and I restarted the phone, I found that my phone was bricked. I can see the boot animation and select the launcher, but once I choose the launcher, the screen goes black, and I cannot do anything. I am also unable to enter Safe Mode as it keeps restarting.
At the same time, I used a software control my phone. I can see NOTHING in sdcard.
What can I do? Is there any way to fix my phone and preserve my data? If not, I am willing to wipe all my data. Also, if I restore my phone to factory settings, can I still use the backup data I made with Titanium Backup?
Thank you in advance for your help.
Additionally, please find attached a screenshot of the only interface I can see on my phone after booting up.
Seems you've broken lot of system apks , clearly Nothing Launcher is first . See if you have a intact bootloader and use fastboot commands to flash the launcher but I'm quite sure there many culprits in system .
So maybe short way is to flash entirely system image shown here in one of all threads about phone unbrick
muppetz said:
Seems you've broken lot of system apks , clearly Nothing Launcher is first . See if you have a intact bootloader and use fastboot commands to flash the launcher but I'm quite sure there many culprits in system .
So maybe short way is to flash entirely system image shown here in one of all threads about phone unbrick
Click to expand...
Click to collapse
Thanks for your advice!