Related
Strange problem I am having.
I am running Eclipse 3.0 on my Galaxy S4 (4.3) on SafeStrap 3.71 in ROM-Slot 1. I purchased Nova Prime - and tried uninstalling the launcher to install the prime, was unsuccessful and every time I attempted installation of it, the phone would reboot. I have referenced several threads and nothing allows me to uninstall the launcher. I thought this was a problem just with Nova, until...
I tried installing my paid version of Titanium Backup (cause that was a suggestion to use to uninstall the launcher) and even after uninstalling the free version, I went to install paid version, restart occurs without the installation.
Also, just tried to install my purchased version of XDA Developers, same thing. The download completes, but in the middle of installing, it reboots.
What could this be? Let me know what other information you need.
(NOTE - I just switched from my droid bionic to this S4 that I purchased from someone)
I am running 3.0 when there is a 5.1 available. Oh dear. Will flash the updated ROM and let you know.
Update: Unable to get that ROM up and running. WIFI would not turn on and network wasn't showing. Looks like I am having to learn from scratch this phone I have. Nothing going to be easy... yet...
must install module for paid apps
Brad003 said:
Strange problem I am having.
I am running Eclipse 3.0 on my Galaxy S4 (4.3) on SafeStrap 3.71 in ROM-Slot 1. I purchased Nova Prime - and tried uninstalling the launcher to install the prime, was unsuccessful and every time I attempted installation of it, the phone would reboot. I have referenced several threads and nothing allows me to uninstall the launcher. I thought this was a problem just with Nova, until...
I tried installing my paid version of Titanium Backup (cause that was a suggestion to use to uninstall the launcher) and even after uninstalling the free version, I went to install paid version, restart occurs without the installation.
Also, just tried to install my purchased version of XDA Developers, same thing. The download completes, but in the middle of installing, it reboots.
What could this be? Let me know what other information you need.
(NOTE - I just switched from my droid bionic to this S4 that I purchased from someone)
Click to expand...
Click to collapse
In order for phone not to reboot you must install xposed and the module play store disable encryption on order to stop the reboot when installing paid apps this is a issue with the ROM on GS4
Known Bugs
Safestrap users will need to use Modaco's paid app encryption module for now
follow this link
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
Hi. I have a Xiaomi MiA1, Lineage 16.0 (I try to update it two or three times per week). It is rooted. I use openGapps.
I have a problem since yesterday: suddenly, my phone got a lot of lag that makes impossible the use. KLWP got closed (it stopped being the default background), Nova Launcher was lagging and restarting several times. Openning any app was impossible, including the settings and system, it freezes and closes, returning to the launcher home screen... I tried to stop, clean data and delete klwp, nova, but i got the same result. The minutes passed and it got worse. Finally, the phone freezed, the clock wasn't working, so the only solution was doing a manual soft reset.
So, yesterday I did a dirty flash, because I didn't have a recent backup. I used SDMaid database feature in the morning so I tought maybe it was bad executed and was the origin of the issue. I tried to rescue some information (to backup some app data) with oandbackups. I cleaned caché and did a Factory reset. It seem to work. and do a clean installation. at first, it seem like it worked. I installed the apps I had by my Google account, and went to sleep. Today, it was ready, I turned it off and charged it, and in the morning: again the crash. So I did a clean installation. Again, it seemed to work. It installed all my apps and... crash again. I fear it could be some launcher issue? any prob with lineage? Any app? How can I know whats happening?
Sorry for my bad english. Any help would be apreciated.
vainille said:
Hi. I have a Xiaomi MiA1, Lineage 16.0 (I try to update it two or three times per week). It is rooted. I use openGapps.
I have a problem since yesterday: suddenly, my phone got a lot of lag that makes impossible the use. KLWP got closed (it stopped being the default background), Nova Launcher was lagging and restarting several times. Openning any app was impossible, including the settings and system, it freezes and closes, returning to the launcher home screen... I tried to stop, clean data and delete klwp, nova, but i got the same result. The minutes passed and it got worse. Finally, the phone freezed, the clock wasn't working, so the only solution was doing a manual soft reset.
So, yesterday I did a dirty flash, because I didn't have a recent backup. I used SDMaid database feature in the morning so I tought maybe it was bad executed and was the origin of the issue. I tried to rescue some information (to backup some app data) with oandbackups. I cleaned caché and did a Factory reset. It seem to work. and do a clean installation. at first, it seem like it worked. I installed the apps I had by my Google account, and went to sleep. Today, it was ready, I turned it off and charged it, and in the morning: again the crash. So I did a clean installation. Again, it seemed to work. It installed all my apps and... crash again. I fear it could be some launcher issue? any prob with lineage? Any app? How can I know whats happening?
Sorry for my bad english. Any help would be apreciated.
Click to expand...
Click to collapse
Keeping in mind the kind of apps you mentioned, I'd go with an app+data backup of those apps you installed and uninstall them completely, check if problem is still there.
I suspect you're facing a compatibility or configuration issue, since both apps are related to home screen.
If problem is solved, first read if those apps are actually compatible with ROM and OS version, then you could try to install just one app, without data, and check if things go well (give it a day), same with the rest until you can confirm OS is working well with apps just installed, no changes made in them yet... In other words, were trying to confirm that problem comes from apps and/or their configurations, so you could somehow report those issues to apps developers. You can use Catalog or other apps to record System logs until app crashes.
On the other hand, if problem is still there, even before you started to reinstall apps, then Dirty flashing isn't a good choice in that case, since it preserves System configurations, no mention your device is rooted, were user changes are present... you are opened to different problems, worse if you use an old Magisk version, or installed modules there, or apps that force your OS to do things it doesn't do in it's original state.
So, as you were so dare to go with a dirty flash, you could better go with a clean flash instead.
Erase any system lock protection (fingerprint, pattern, etc), do a ROM Backup from TWRP, flash latest firmware and make a clean install of the latest version of the ROM of your choice, keeping in mind their own flashing procedure.
As with above reply, if a completely clean install doesnt work, consider going back to a previous lineage release. If it still doesnt work, consider a full EDL stock rom reflash using MiFlash -- then flash your custom rom.
KaaMyA said:
Keeping in mind the kind of apps you mentioned, I'd go with an app+data backup of those apps you installed and uninstall them completely, check if problem is still there.
I suspect you're facing a compatibility or configuration issue, since both apps are related to home screen.
If problem is solved, first read if those apps are actually compatible with ROM and OS version, then you could try to install just one app, without data, and check if things go well (give it a day), same with the rest until you can confirm OS is working well with apps just installed, no changes made in them yet... In other words, were trying to confirm that problem comes from apps and/or their configurations, so you could somehow report those issues to apps developers. You can use Catalog or other apps to record System logs until app crashes.
On the other hand, if problem is still there, even before you started to reinstall apps, then Dirty flashing isn't a good choice in that case, since it preserves System configurations, no mention your device is rooted, were user changes are present... you are opened to different problems, worse if you use an old Magisk version, or installed modules there, or apps that force your OS to do things it doesn't do in it's original state.
So, as you were so dare to go with a dirty flash, you could better go with a clean flash instead.
Erase any system lock protection (fingerprint, pattern, etc), do a ROM Backup from TWRP, flash latest firmware and make a clean install of the latest version of the ROM of your choice, keeping in mind their own flashing procedure.
Click to expand...
Click to collapse
I made a clean flash in the morning, with the same results, so there's when I thought it could be an app the main problem. It worked with Nova a few hours.
I just followed your instructions, I installed the last firmware (the jan one) and the last rom of lineage. I didn't installed the apps in my google backup so I can install them and check how is the behaviour. I will install CatLog so I can check the logs too! I really hope installing the firmware was enough. Thank you very much!
ayunatsume said:
As with above reply, if a completely clean install doesnt work, consider going back to a previous lineage release. If it still doesnt work, consider a full EDL stock rom reflash using MiFlash -- then flash your custom rom.
Click to expand...
Click to collapse
I was planning to reflash the custom ROM but I couln't find the latest one that's compatible with MiFlash. I really hope the clean install is enought... thank you
I was planning to reflash the custom ROM but I couln't find the latest one that's compatible with MiFlash. I really hope the clean install is enought... thank you[/QUOTE]What our partner said was flashing stock (original) ROM.
In any case, if you went with a clean flash, try to leave your system free of user installed apps for a few and check how it goes.