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.

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!

From OOS 10.0.1 trying to install LOS 16.0 as a beginner and failing completely

I'm trying to install LOS 16.0 but it just won't work. I've tried using the TWRP 3.3.1-16 Q Unofficial by mauronofrio and it works that I can get into TWRP and can flash the rom and GApps, but then after that process once I try to boot into the OS it is just forever stuck in either fastboot or stuck on the bootloader unlocked warning screen. I did realize that I had to use fastboot flash boot twrp*.img because they disabled fastboot boot twrp*.img in the Android 10 update, but then am I supposed to reflash something on that boot partition now? The whole process is very confusing and the instructions from the LineageOS seem to not work at all. Is there anything I can do right now or is it just not possible to install this until TWRP, or OOS, or something I'm not knowledgeable enough to know about updates?

It's because you are using OOS 10.1 as a base (android 10) and you are trying to install Lineage OS 16 (android 9), so it's quite obvious why it isn't working. Try lineage OS 17 instead.

TheSproker said:
It's because you are using OOS 10.1 as a base (android 10) and you are trying to install Lineage OS 16 (android 9), so it's quite obvious why it isn't working. Try lineage OS 17 instead.
Click to expand...
Click to collapse
Lineage OS 17 won't work either. The developer intentionally used OOS 9 as base since fastboot boot command doesn't work yet on OOS 10. OP needs to downgrade to OOS 9 first, whichever of the two Lineage OS versions they wish to use.

remewer said:
Lineage OS 17 won't work either. The developer intentionally used OOS 9 as base since fastboot boot command doesn't work yet on OOS 10. OP needs to downgrade to OOS 9 first, whichever of the two Lineage OS versions they wish to use.
Click to expand...
Click to collapse
I tried this. I downgraded to 9.0.9 and still the fastboot boot command is not working. Apparently this has something to do with the bootloader image itself not being downgraded?

I give up now, my temp phone I was using for holding backups for chat data just randomly wiped itself on havocOS and I've just lost years of chats and stuff and it's got me really down right now. They did fix the fastboot boot issue with today's 10.3.0 update but still nothing is working from any tutorial to get this thing to work on lineage, it just won't boot to it and twrp keeps having errors during flashing. This used to be so much easier on my older phones and I've installed this OS on about 5 phones now but OnePlus 6 just doesn't seem to work no matter what. I'm just going to go back to OOS and hope LineageOS 17.0 will get these issues ironed out by the time it releases. Severely disappointing and a waste of 3 days now but oh well

In my opinion, this is the easiest way to downgrade everything to OOS 9, including bootloader https://forum.xda-developers.com/oneplus-6/how-to/op6-collection-unbrick-tools-t3914109
After that, just unlock the bootloader again like usual and follow the LOS16/17 page's install instructions and you should be good to go.

I tried to install Havoc 3.5 while i was on 10 Ob2, unlocked bootloader and installed patched twrp, then rom. Got stuck in fastboot mode. **** hell i messed everything, later i found fastboot recovery rom from xda, flashed it, thank god it saved me. For me, msm tool was not getting connected, got an error like sahara xyz something... Then after refering to multiple xda threads came to know that most of the present 10 custom roms are based on oos android 9. Then again i used downgrade package from community, reverted back to ob 25 oos (pie), then as usual installation process. So if you are interested in custom roms, downgrade to pie. And again i wanted to go back to complete stock from havoc but unfortunately msm was not responding and fastboot roms wont support upgradation (im not sure), i went to twrp and installed stable 9.0.9 to both partitions + twrp installer. Then 10 oos stable to both partitions + twrp. Then booted up and installed Ob2 again from system updater, lost twrp on that process, then locked bootloader, so mow completely stock ? lot of work for nothing ? oos is better for me.. infact i got used to that. maybe i should purchase another phone to continue the momentum of getting latest updates. crazy oos influence ?

[solved] Reboot to twrp when installing latest lineage16

Hello
Strange think for me, maybe not for you
I switch from carbon 8 and came back to lineage 16.
I'm not able to achieved installation with latest lineage 16, lineage microG or lineage17. Flashing the new rom works well, but after lineage home screen, the phone reboot to recovery.
With an lineage16 old version from 03/2019,install is ok and phone boot well.
I've suspected an old twrp version, but I'm on 3.3.1.0.
Any idea ?
thank you

it's the same with an old twrp version 3.2.

Ok, solved. You shouldn't install twrp as an app before rebooting to new os version.

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...