Database Info

[SOLVED] Bootloop when trying to downgrade from Android 8.1 (LineageOS 15.1) to 7.1.

I have the following installed:
[url]https://forum.xda-developers.com/oneplus-one/development/8-0-0r3-lineageos-15-0-t3670670[/URL]
Android: LineageOS 15.1 (8.1.0_r4) with latest magisk installed (15.3) with unofficial opengapps 8.1 mini package
When I try to downgrade to either Lineage 14.1 official or carbonrom 5.1 I am getting a boot loop at the oneplus logo. Restoring from backup to 8.1 resolves the issue.
1. factory reset
2. wipe system
3. Install Lineage 14.1 or carbonrom 5.1
4. Install recent opengapps mini package for 7.1.2
4. Reboot
The phone boot loops at the oneplus logo and I end up restoring from backup.
I have looked online and was struggling to find anything relevant. Some people report a new battery solved the issue but since It works when I restore from the backup It doesn't seem to be that. I do have a new battery on hand that I am eventually going to install though so I can do that.
Apologies if I am missing something obvious.

-Snowrider- said:
I have the following installed:
https://forum.xda-developers.com/oneplus-one/development/8-0-0r3-lineageos-15-0-t3670670
Android: LineageOS 15.1 (8.1.0_r4) with latest magisk installed (15.3) with unofficial opengapps 8.1 mini package
When I try to downgrade to either Lineage 14.1 official or carbonrom 5.1 I am getting a boot loop at the oneplus logo. Restoring from backup to 8.1 resolves the issue.
1. factory reset
2. wipe system
3. Install Lineage 14.1 or carbonrom 5.1
4. Install recent opengapps mini package for 7.1.2
4. Reboot
The phone boot loops at the oneplus logo and I end up restoring from backup.
I have looked online and was struggling to find anything relevant. Some people report a new battery solved the issue but since It works when I restore from the backup It doesn't seem to be that. I do have a new battery on hand that I am eventually going to install though so I can do that.
Apologies if I am missing something obvious.
Click to expand...
Click to collapse
Try the following :
-uninstall magisk using uninstaller(available in magisk forum)
-clear system,data,cache,dalvik
-install only the rom with out gapps
if it boots properly then you can install the gapps later or else if u find flashing gapps is causing the bootloop then use an older version and double check the compatibility.
if still not just try out another nougat rom

Thanks for the suggestion.
I tried your steps with the latest stable slimrom 7.1.2, lineage 14.1 and carbonrom 5.1 and I am still seeing the same issue. I was able to clean install the lineage 15.1 beta I linked to though in addition to restoring my backup as I have done before. I might try to clean install a different 8.1 (AOSP for example) and see if that one works. This will help narrow down if the issue is caused by 8.1 in general or specifically something that the lineage 15.1 beta has done.

I had a similar problem when I flashed Sultan's LOS14.1. I fixed it by flashing down to stock using wugfresh's bacon root toolkit. Keep in mind though that this will wipe EVERYTHING on your phone. Hope it doesn't come to that. Best of luck!

CedArctic said:
I had a similar problem when I flashed Sultan's LOS14.1. I fixed it by flashing down to stock using wugfresh's bacon root toolkit. Keep in mind though that this will wipe EVERYTHING on your phone. Hope it doesn't come to that. Best of luck!
Click to expand...
Click to collapse
This is what I ended up doing and it did the trick. Thank you for the suggestion.

Constant Reboot

I had the official Lineage 15.1 installed with gapps pico, it was upgraded from 14.1 lineage with gapps pico + magisk 16 . Today I wanted to downgrade back to 14.1 so I flashed the latest 14.1 lineage with gapps 7.1
After booting it shows com.android.phone has stopped working and it restarts again to show the same thing.
I am able to get into TWRP recovery , can anyone please suggest me what should I do?
I dont have previous backup

Mmodi said:
I had the official Lineage 15.1 installed with gapps pico, it was upgraded from 14.1 lineage with gapps pico + magisk 16 . Today I wanted to downgrade back to 14.1 so I flashed the latest 14.1 lineage with gapps 7.1
After booting it shows com.android.phone has stopped working and it restarts again to show the same thing.
I am able to get into TWRP recovery , can anyone please suggest me what should I do?
I dont have previous backup
Click to expand...
Click to collapse
I did a factory reset using TWRP . Lost all the data but the phone started, able to use it now

Mmodi said:
I did a factory reset using TWRP . Lost all the data but the phone started, able to use it now
Click to expand...
Click to collapse
Always do a clean wipe (wipe everything except internal/external storage). Always back up your previous system just in case. Sometimes it is better to flash Gapps right after flashing the ROM, sometimes it's better to flash the ROM, boot and then flash the Gapps.

[Q] LineageOS Nightly Dirty Flashing

I hope someone can help me here. I recently moved from CyanogenMod 13.1 to LineageOS 14.1 (fully wiping my phone). I haven't had any issues with LineageOS until I try to dirty flash a nightly build. I never had issues dirty flashing with CM, so I'm not sure what's going on. I just tried flashing the 7/25 build from the 7/18 build and the latest gapps. Upon rebooting, my D850 just sits at the boot screen (13 minutes now). When I restore from my TWRP backup, my phone will boot back up after about 3 minutes (for the first boot). Am I missing a step when flashing nightlies?

OFFICIAL LINEAGE OS 16 was released but was taken down?

They made a wiki on Beryllium (https://wiki.lineageos.org/devices/beryllium) and some other links to the official build (https://download.lineageos.org/beryllium) but they removed it.
I don't know what was the reason.
They rolling out the Lineage 16 PIE on couple devices like Oneplus 5/5T, Huawei P20 Pro, Xiaomi Mi Note 3, etc. (https://www.androidpolice.com/2019/...1-oneplus-phones-galaxy-s5-and-other-devices/)

wasn't released it failed but it is expected to succeed soon.

bower1994 said:
wasn't released it failed but it is expected to succeed soon.
Click to expand...
Click to collapse
Thank you for the response, out of curiosity, what was failed in the latest official build?

https://gitlab.com/LineageOS/builder/android/pipelines/49950700/builds
Yesterday all builds failed on that user/server

#### build completed successfully (01:34:25 (hh:mm:ss)) #### Guess we can expect a build in a few hours?

The nightly is available now

The inital nightly build seems to be broken, at least for me. Can't boot into system.

Same here, installed via adb sideload. system displays the boot animation for a while, then I end up in recovery every time.

tiantnait said:
Same here, installed via adb sideload. system displays the boot animation for a while, then I end up in recovery every time.
Click to expand...
Click to collapse
I tried again, this time flashing the 9.2.25 vendor firmware instead of 9.3.1, LOS flash also via sideload. It's working now!

no problems here.. clean flash, flashed firmware 9.2.25, los official nightly, pico gapps and magisk 18.2, wipe cache/dalvik and reboot. it runs awesome

Strel0ka said:
I tried again, this time flashing the 9.2.25 vendor firmware instead of 9.3.1, LOS flash also via sideload. It's working now!
Click to expand...
Click to collapse
No luck here. I also tried flashing 9.2.25 first (had 9.2.21 before). Still same boot loop. Must be something else.
(magisk, no google services, encrypted fs, not a clean install [update from UNOFFICAL 20190220])
going back to UNOFFICAL build works fine for now...

tiantnait said:
No luck here. I also tried flashing 9.2.25 first (had 9.2.21 before). Still same boot loop. Must be something else.
(magisk, no google services, encrypted fs, not a clean install [update from UNOFFICAL 20190220])
going back to UNOFFICAL build works fine for now...
Click to expand...
Click to collapse
So you performed a dirty flash of official LOS over unofficial LOS? That's like dirty flashing NOS over LOS. If you want to switch over to the official branch, I highly recommend starting from scratch.
My current setup is official LOS with microg + magisk and Encryption, no issues so far.

Yep.. Official build is on!

Lineage OS 17.1 won't boot after update notification on Redmi 2 prime

I was running Lineage OS 17.1 without problems in a Redmi 2 prime. Today I got a notification update from July 24th and then proceded to download update, then I clicked on install, then the phone booted again to TWRP and it won't boot into OS again, what should I do?
Thanks a lot.

You should reflash lineage os.
(You need lineage recovery to update lineage os)

Drobly said:
You should reflash lineage os.
(You need lineage recovery to update lineage os)
Click to expand...
Click to collapse
So if a recovery wasn't installed that's why is not booting to OS? if I reflash lineage os my information will be deleted?
Any other way to make it boot to lineage, I'm confused...