Database Users

Nexus 10 (manta), Lineage OS 13, bootloop with Nova Launcher

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

My OP2 keeps optimizing an app every reboot

Every time I reboot my OnePlus 2 keeps optimizing a certain app
I don't know which one but I deleted a lot of downloaded apps and it still didn't help
I thought it could be the SuperSU app so I ran the UnSU script and flashed Magisk
It still keeps optimizing that app
Factory reset would probably solve this issue but I'd prefer not to do that
Thanks

do you have some "optimizing" apps or mods installed? like Lspeed, or hebf or something like that?

IvanMuse said:
Every time I reboot my OnePlus 2 keeps optimizing a certain app
I don't know which one but I deleted a lot of downloaded apps and it still didn't help
I thought it could be the SuperSU app so I ran the UnSU script and flashed Magisk
It still keeps optimizing that app
Factory reset would probably solve this issue but I'd prefer not to do that
Thanks
Click to expand...
Click to collapse
I have a similar problem. Optimising 2 apps while booting. This takes a lot of time, I guess about 5-8 minutes for each app. Initially I thought I was stuck with a boot loop or something, but later figured out that after insanely waiting, the phone actually boots up after optimising.
So I uninstalled many apps from my phone and now optimising is reduced to 1 app. I cannot pinpoint on which app is being optimised so i can get rid of that app.
I am running on unrooted oxygen 3.6.1 with no fancy stuff installed, to the best of my knowledge.
Any help to understand how to get rid of this optimisation will be appreciated.

JohnJacobT said:
I have a similar problem. Optimising 2 apps while booting. This takes a lot of time, I guess about 5-8 minutes for each app. Initially I thought I was stuck with a boot loop or something, but later figured out that after insanely waiting, the phone actually boots up after optimising.
So I uninstalled many apps from my phone and now optimising is reduced to 1 app. I cannot pinpoint on which app is being optimised so i can get rid of that app.
I am running on unrooted oxygen 3.6.1 with no fancy stuff installed, to the best of my knowledge.
Any help to understand how to get rid of this optimisation will be appreciated.
Click to expand...
Click to collapse
i flashed 8.1.0 lineageos and it solved the problem but i guess that just a factory reset would do the job
let me know if you fixed it

Have you got bit torrent installed?? Bit torrent updated, I restarted, optimising bit torrent for hours

Solution:-
Boot into recovery mode(TWRP recommended) and delete the true caller folder from data and the system.

I had the same problem.
It was utorrent.
Sent from my ONE A2003 using Tapatalk

OnePlus 5 corrupted and cannot be trusted

So recently, I had to unroot my phone because I need snapchat working. I was using Magisk with the newest update and EdXposed. Everything was fine until I got struck by a suprise 12 hour ban, yeah no big deal, I wasn't even using root for much else but changing the boot animation at the time.
This is where it gets interesting, after multiple restarts disabling modules and then finally uninstalling Magisk, I get struck by a mesagge that the phone is corrupted and can't be trusted. I got a mini heartattack from this but after starting my phone, nothing is weird or out of place, bootloader is still unlocked and updating the phone works.
My question is, what will this affect that I haven't realised yet and is there any way to prevent that message from appearing?

I think Magisk Hide can do something. Just turn on Magisk Hide and in its section turn on Snapchat.

Luckypatcher Android 11 BOOTLOOP WARNING

I recently moved to OOS11 and had trouble rooting. Now that I have my phone rooted I can no longer restart it or it will bootloop. Does anyone have any idea why that would be?
This will be the 3rd time I have MSMed my phone in the last 3 days.
As many problems as I'm having I'm thinking of just going back to Android 10.
Thanks in advance.

night hawk said:
I recently moved to OOS11 and had trouble rooting. Now that I have my phone rooted I can no longer restart it or it will bootloop. Does anyone have any idea why that would be?
This will be the 3rd time I have MSMed my phone in the last 3 days.
As many problems as I'm having I'm thinking of just going back to Android 10.
Thanks in advance.
Click to expand...
Click to collapse
Can you provide a bit more background, do you have any Magisk modules installed, does your phone boot at all? Did you patch your own boot.img just so that we can help you out better

Shredz98 said:
Can you provide a bit more background, do you have any Magisk modules installed, does your phone boot at all? Did you patch your own boot.img just so that we can help you out better
Click to expand...
Click to collapse
I'm patching my own boot.img and I only have skyvalex call recorder installed as a module. When it happens I just get stuck in an infinite boot animation with the two dots circling continuously.
I think I may have narrowed down the problem by going through the steps that I normally go through after MSMing my phone (I've done it 4 times now lol) and rebooting after each step to see what triggers it. Here are the steps in order.
1. MSM the phone and do bare minimum to get to home screen so I can enable OEM ulocking and usb debugging. (rebooted just fine)
2. Unlock bootloader with adb. (rebooted just fine)
3. Install magisk manager, switch to beta update channel, patch boot.img, flash patched boot.img (rebooted just fine)
4. Setup up phone with google account, set up fingerprint, etc (rebooted just fine)
5. Enable magisk hide and systemless hosts (rebooted just fine)
6. Restore a backup using oneplus switch from before this all started happening. (rebooted just fine)
7. Use luckypatcher to remove ads from a few games (BOOTLOOP)
Well it would appear that luckypatcher is the problem. I'm wondering if the new "use magisk module" mode in the newest version is causing the problem. Maybe if I installed EdXposed and used that like I used to maybe it would remedy the problem. Or maybe I should just use an adblock magisk module. However its far passed my bedtime so I will confirm this tomorrow if possible.

Disable the modules you have installed.
Reboot, does it loop?
If no then it's a module
If it does then it's your boot img
I'd recommend booting your patched boot img then directly installing via magisk (do not reboot until you have)
Hope this helps

night hawk said:
I'm patching my own boot.img and I only have skyvalex call recorder installed as a module. When it happens I just get stuck in an infinite boot animation with the two dots circling continuously.
I think I may have narrowed down the problem by going through the steps that I normally go through after MSMing my phone (I've done it 4 times now lol) and rebooting after each step to see what triggers it. Here are the steps in order.
1. MSM the phone and do bare minimum to get to home screen so I can enable OEM ulocking and usb debugging. (rebooted just fine)
2. Unlock bootloader with adb. (rebooted just fine)
3. Install magisk manager, switch to beta update channel, patch boot.img, flash patched boot.img (rebooted just fine)
4. Setup up phone with google account, set up fingerprint, etc (rebooted just fine)
5. Enable magisk hide and systemless hosts (rebooted just fine)
6. Restore a backup using oneplus switch from before this all started happening. (rebooted just fine)
7. Use luckypatcher to remove ads from a few games (BOOTLOOP)
Well it would appear that luckypatcher is the problem. I'm wondering if the new "use magisk module" mode in the newest version is causing the problem. Maybe if I installed EdXposed and used that like I used to maybe it would remedy the problem. Or maybe I should just use an adblock magisk module. However its far passed my bedtime so I will confirm this tomorrow if possible.
Click to expand...
Click to collapse
The issue is definitely lucky patcher, I had the same problem and my phone was useless until I got rid of it. So it seems it's not playing well with A11 or OOS11 in any case do not use it or you'll end up in a boot loop.
Cheers!

Ah lucky patcher..oh dear, can't help you with that crap.
Best advice, get rid

Bummer about Lucky Patcher....

In b4 the lock.

I can confirm the same findings, lucky patcher seems to break reboots later.
Hopefully a new version will find and resolve the issue, but until then not much we can do but to wait.

Unfortunately doesn't appear to be any way to get around this or recover from the bootloops without a wipe/reimage. Can't get access for adb during bootanimation, cant boot from a boot img, just basically stuck.
@OP, perhaps you can put a message in your thread's title just warning against LP on A11 for the time being.

uaktags said:
Unfortunately doesn't appear to be any way to get around this or recover from the bootloops without a wipe/reimage. Can't get access for adb during bootanimation, cant boot from a boot img, just basically stuck.
@OP, perhaps you can put a message in your thread's title just warning against LP on A11 for the time being.
Click to expand...
Click to collapse
I changed the title. Do we know if LP can be used with xposed on Android 11 with success still?

night hawk said:
I changed the title. Do we know if LP can be used with xposed on Android 11 with success still?
Click to expand...
Click to collapse
Did xposed work on 11?

night hawk said:
...
7. Use luckypatcher to remove ads from a few games (BOOTLOOP)
Well it would appear that luckypatcher is the problem. ...
Click to expand...
Click to collapse
@night hawk
Hi!
You better read the XDA Forum Rules and refrain from such topics. We don't accept discussions about issues with warez!
6. Do not post or request warez.
If a piece of software requires you to pay to use it, then pay for it. We do not accept warez nor do we permit members to request, post, promote or describe ways in which warez, cracks, serial codes or other means of avoiding payment, can be obtained or used. This is a site of developers, i.e. the sort of people who create such software. When you cheat a software developer, you cheat us as a community.
Click to expand...
Click to collapse
THREAD CLOSED!

After restart, some apps stuck

Hello, I have a strange problem, after every reboot of the phone, some apps are not working anymore, they either stuck at the loading screen or force close. For example, Genshin Impact (game) gets stuck, Faceapp force closes, other apps like a banking app and a local provider app are also affected. Clearing cache/data does't help, only reinstalling fixes this.
Open bootloader, rooted, stock rom 11.0.2.2IN11BA, stock kernel, no magisk modules, upgrade from 11.0.1.1 didn't fixed it. Model IN2023, when I got the phone it had the global rom and I installed the eu after rooting. Any ideas what the problem could be?

Perpatoura said:
Hello, I have a strange problem, after every reboot of the phone, some apps are not working anymore, they either stuck at the loading screen or force close. For example, Genshin Impact (game) gets stuck, Faceapp force closes, other apps like a banking app and a local provider app are also affected. Clearing cache/data does't help, only reinstalling fixes this.
Open bootloader, rooted, stock rom 11.0.2.2IN11BA, stock kernel, no magisk modules, upgrade from 11.0.1.1 didn't fixed it. Model IN2023, when I got the phone it had the global rom and I installed the eu after rooting. Any ideas what the problem could be?
Click to expand...
Click to collapse
Are you indeed still rooted? I get this issue if I turn on systemless and then don't reboot.
Or if I lose root if I haven't actually installed the patched image after booting the patched image.
Check to see if you're actually still rooted.
If you are then turn on systemless.

dladz said:
Are you indeed still rooted? I get this issue if I turn on systemless and then don't reboot.
Or if I lose root if I haven't actually installed the patched image after booting the patched image.
Check to see if you're actually still rooted.
If you are then turn on systemless.
Click to expand...
Click to collapse
Hello, thank you for your answer, I still have root, just checked. What do I have to do to turn on systemless? Just press on "systemless hosts" in magisk settings?