Related
hello all,
I have a rooted OP3 running the latest TWRP recovery. Using these instructions I am trying to upgrade to 3.2.8 from 3.2.7. There are no errors displayed during OOS or SuperSU install steps.
But when the phone reboots - it stays stuck at the boot animation. This happens across several attempts. I do not have xposed installed, if it helps. Repeating the above steps with a 3.2.7 image works without issues.
Is there any way I can figure out where the 3.2.8 reboot is getting stuck at? I *do not* want to do a fresh install.
Any thoughts/ Suggestions? I have already posted at the above thread and thought I'd try my luck here too.
EDIT: Can a MOD please move this to Q&A forum. Just realized I posted to Guides, News & Discussion.
backup all your data and install 3.2.8 with the official procedure
Sacob said:
backup all your data and install 3.2.8 with the official procedure
Click to expand...
Click to collapse
That's my last option. But that's as good as starting from scratch. In which case, I might as well postpone until Nougat arrives on the OP3
tropicanapure said:
That's my last option. But that's as good as starting from scratch. In which case, I might as well postpone until Nougat arrives on the OP3
Click to expand...
Click to collapse
and wait without a phone?
Flash the new Beta 10. i'm currently using it with root and it works great
Not sure what you mean - without a phone. I was able to roll back to 3.2.7 with zero issues
I was mulling over installing the Beta - but I understand Nougat is due in Jan? Also, is there a process to move to b10 without losing data?
Sacob said:
and wait without a phone?
Flash the new Beta 10. i'm currently using it with root and it works great
Click to expand...
Click to collapse
tropicanapure said:
Not sure what you mean - without a phone. I was able to roll back to 3.2.7 with zero issues
I was mulling over installing the Beta - but I understand Nougat is due in Jan? Also, is there a process to move to b10 without losing data?
Click to expand...
Click to collapse
i got the impression that your phone wasn't booting xD
well, every time i flash those betas (9 and 10) TWRP asks me for a PIN that doesn't exists and to solve that i need wipe everything... so i wouldn't count on that
tropicanapure said:
hello all,
I have a rooted OP3 running the latest TWRP recovery. Using these instructions I am trying to upgrade to 3.2.8 from 3.2.7. There are no errors displayed during OOS or SuperSU install steps.
But when the phone reboots - it stays stuck at the boot animation. This happens across several attempts. I do not have xposed installed, if it helps. Repeating the above steps with a 3.2.7 image works without issues.
Is there any way I can figure out where the 3.2.8 reboot is getting stuck at? I *do not* want to do a fresh install.
Any thoughts/ Suggestions? I have already posted at the above thread and thought I'd try my luck here too.
EDIT: Can a MOD please move this to Q&A forum. Just realized I posted to Guides, News & Discussion.
Click to expand...
Click to collapse
Did you download the full 3.2.8 zip from http://downloads.oneplus.net? I did. And to my surprise, it erases the whole userdata partition, including TWRP backups and downloaded files (including SuperSU zip). So big warning if you try with that zip. I assume that this zip is intended for those reverting from Nougat Beta, to go back from F2FS to EXT4.
My solution was to restore an old TWRP backup that was saved on my PC and then reflash a modified full 3.2.8 zip where the last line in the update script was removed: the one that erases userdata partition. So before flashing full 3.2.8 zip from http://downloads.oneplus.net I recommend you to remove the last line in the update script.
No, I downloaded the Full ZIP from this official thread on the OP3 forums. I was aware of that line though. And from previous experience - the first thing I do when I make a TWRP backup is to move it off the phone. That and I purchased Titanium Backup long time ago. I use it to back up stuff surgically and sync it up to Dropbox every night. The app also seems to have the ability to make a recovery-flashable "update.zip" - something I have yet to try.
Appreciate the heads-up though.
ptblad said:
Did you download the full 3.2.8 zip from http://downloads.oneplus.net? I did. And to my surprise, it erases the whole userdata partition, including TWRP backups and downloaded files (including SuperSU zip). So big warning if you try with that zip. I assume that this zip is intended for those reverting from Nougat Beta, to go back from F2FS to EXT4.
My solution was to restore an old TWRP backup that was saved on my PC and then reflash a modified full 3.2.8 zip where the last line in the update script was removed: the one that erases userdata partition. So before flashing full 3.2.8 zip from http://downloads.oneplus.net I recommend you to remove the last line in the update script.
Click to expand...
Click to collapse
tropicanapure said:
No, I downloaded the Full ZIP from this official thread on the OP3 forums. I was aware of that line though. And from previous experience - the first thing I do when I make a TWRP backup is to move it off the phone. That and I purchased Titanium Backup long time ago. I use it to back up stuff surgically and sync it up to Dropbox every night. The app also seems to have the ability to make a recovery-flashable "update.zip" - something I have yet to try.
Appreciate the heads-up though.
Click to expand...
Click to collapse
OK. I also use TB, and from now on I use cloud storage :laugh:
After the full modified 3.2.8 zip I successfully flashed official SuperSU 2.79, Xposed v87 and Bluspark r25 kernel. I use F2FS on data partition. It boots and runs fine!
The only thing I'm a bit concerned about is that it stays on the bootlogo (OnePlus logo, Powered by Android) for about 25 secs before the bootanimation begins when booting to system. Much faster before. When booting to recovery (TWRP 28, Bluspark) the time on bootlogo is normal (short). Any thoughts on that?
I wish I had, man. You went a number of steps ahead when your phone went past the boot animation
As a afterthought - try looking through your logs.
ptblad said:
OK. I also use TB, and from now on I use cloud storage :laugh:
After the full modified 3.2.8 zip I successfully flashed official SuperSU 2.79, Xposed v87 and Bluspark r25 kernel. I use F2FS on data partition. It boots and runs fine!
The only thing I'm a bit concerned about is that it stays on the bootlogo (OnePlus logo, Powered by Android) for about 25 secs before the bootanimation begins when booting to system. Much faster before. When booting to recovery (TWRP 28, Bluspark) the time on bootlogo is normal (short). Any thoughts on that?
Click to expand...
Click to collapse
I just installed the 4.0.2 update, got this new Android 7.
However, upon booting somehow my device cannot detect any sim card. I went to settings, then selected SIM&Network and suddenly settings crashed. I tried selecting Data Usage / More options which also makes settings crash, while other options work fine.
Along with network related settings crashing, some of the system apps, like the new oneplus community thingy and file manager also crashes upon launching the app.
Also, whenever I boot my phone I get this 'dm-verity not started in enforcing mode' screen.
Anyone have a solution? I am seriously confused right now.
Like any Android version change, you should do a clean install. If you do a factory reset your phone should be fine.
jenil1428569 said:
I just installed the 4.0.2 update, got this new Android 7.
However, upon booting somehow my device cannot detect any sim card. I went to settings, then selected SIM&Network and suddenly settings crashed. I tried selecting Data Usage / More options which also makes settings crash, while other options work fine.
Along with network related settings crashing, some of the system apps, like the new oneplus community thingy and file manager also crashes upon launching the app.
Also, whenever I boot my phone I get this 'dm-verity not started in enforcing mode' screen.
Anyone have a solution? I am seriously confused right now.
Click to expand...
Click to collapse
Check this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757/
dbabaev21 said:
Check this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757/
Click to expand...
Click to collapse
I did the hard reset thingy and factory reset whatsoever, and some system apps not launching have been dealt with. However, my sim card is still not being detected and thos horrendous lag is still present.
jenil1428569 said:
I did the hard reset thingy and factory reset whatsoever, and some system apps not launching have been dealt with. However, my sim card is still not being detected and thos horrendous lag is still present.
Click to expand...
Click to collapse
Ok, good.
Now sideload the OOS v4.0.2. So, everything will go back to normal.
How did you upgrade to OOS 4.0.2 ? from OOS 4.0.1 ? Or OOS 3.5.4 ? So did you upgrade from stock recovery or TWRP ?
Kris Chen said:
How did you upgrade to OOS 4.0.2 ? from OOS 4.0.1 ? Or OOS 3.5.4 ? So did you upgrade from stock recovery or TWRP ?
Click to expand...
Click to collapse
I upgraded it from OOS 3.2.8 through TWRP.
OK, May I ask you which one of TWRP version do you use ?
jenil1428569 said:
I upgraded it from OOS 3.2.8 through TWRP.
Click to expand...
Click to collapse
Kris Chen said:
OK, May I ask you which one of TWRP version do you use ?
Click to expand...
Click to collapse
3.0.3_0
The dm-verity problem usually comes if you flash the update and don't flash SuperSU without rebooting, and with the problem with your sim, I would try to insert a different sim and see if the problem persist.
Un saludo.
Thanks!
Let me summarize how to flash OOS 4.0.2: You use TWRP 3.0.3-0 to upgrade your OP3 from OOS 3.5.2 to OOS 4.0.2
Well, I would recommend you do so:
(1)Please use Titanium to backup all your files and then copy to your computer.
(2)Upgrade your TWRP 3.0.3-0 to TWRP 3.0.3-1. TWRP 3.0.3-1 can be downloaded from TWRP official site.
(3)Then download complete OOS 4.0.2 to your computer HDD.
(4)Wipe all partition
(5)Copy OOS 4.0.2 to your phone, including of your Titanium App backup files.
(6)Flashing OOS 4.0.2. Then SuperSU 2.79 and google play store.
(7)Reboot to system and complete all necessary settings.
(8)After that, going to google play store and install Taitanium backup. Then restore all your backup files.
(9)Reboot again. Done
God bless !
jenil1428569 said:
3.0.3_0
Click to expand...
Click to collapse
Kris Chen said:
Thanks!
Let me summarize how to flash OOS 4.0.2: You use TWRP 3.0.3-0 to upgrade your OP3 from OOS 3.5.2 to OOS 4.0.2
Well, I would recommend you do so:
(1)Please use Titanium to backup all your files and then copy to your computer.
(2)Upgrade your TWRP 3.0.3-0 to TWRP 3.0.3-1. TWRP 3.0.3-1 can be downloaded from TWRP official site.
(3)Then download complete OOS 4.0.2 to your computer HDD.
(4)Wipe all partition
(5)Copy OOS 4.0.2 to your phone, including of your Titanium App backup files.
(6)Flashing OOS 4.0.2. Then SuperSU 2.79 and google play store.
(7)Reboot to system and complete all necessary settings.
(8)After that, going to google play store and install Taitanium backup. Then restore all your backup files.
(9)Reboot again. Done
God bless !
Click to expand...
Click to collapse
Can I ask why you recommend flashing google play store, when it's included in the complete OOS 4.0.2 ? Seems redundant...
https://download.lineageos.org/crackling
The First One!
Do we need su for arm or su for arm64?
Obscurax said:
Do we need su for arm or su for arm64?
Click to expand...
Click to collapse
Arm64
What's the build name of the Swift 2X?
Sent from my Moto G4 using XDA Labs
kartotar said:
What's the build name of the Swift 2X?
Click to expand...
Click to collapse
marmite
M.A.K said:
marmite
Click to expand...
Click to collapse
Thanks. Do you have any idea if LineageOS will be supported on Marmite?
Sent from my Moto G4 using XDA Labs
AFAIK, Swift 2 ks not officially supported by Lineage OS, so no. You may be able to find an unofficial version though.
Cannot dirty flash
I currently have thomson.aa's unofficial lineage os build installed. This update shows up in the updater app, but after I download it, it says the zip is corrupt or unsigned and it does not let me install it. If I manually download it and try to install via TWRP, it fails saying "can't install this package on top of incompatible data. Please try another package or run a factory reset". I would hate to have to reinstall all my stuff, though. Is there some way around this? Or is there something wrong with the update?
Got no problems installing it via TWRP. Works great, stable so far.
crdroid was fine too, lots of special settings (little too much for me), but I prefer a ROM with regular OTA updates. Thank you beroid anyway.
P.S. My grammar help changes "beroid" to "heroic"
Can this be installed over the top of cm13.0 nightly?
Mithodin said:
I currently have thomson.aa's unofficial lineage os build installed. This update shows up in the updater app, but after I download it, it says the zip is corrupt or unsigned and it does not let me install it. If I manually download it and try to install via TWRP, it fails saying "can't install this package on top of incompatible data. Please try another package or run a factory reset". I would hate to have to reinstall all my stuff, though. Is there some way around this? Or is there something wrong with the update?
Click to expand...
Click to collapse
You basically asked the same question in 2 threads??? So as this isn't really thomson.aa's problem, I'll answer you here.
I dirty flashed from stock -> cm13 -> crDroid -> thomson.aa's LOS14 without issue. I tried with the official release and got the same as you. So after editing the installer script to force it to install, it did. But once it booted, everything kept force closing. It just wasn't happening.
So I wiped data and chose to restore my backup from google. I just installs most of your apps but it saves a bit of time. Still need to set things up properly though.
M.A.K said:
You basically asked the same question in 2 threads??? So as this isn't really thomson.aa's problem, I'll answer you here.
Click to expand...
Click to collapse
I figured this might be due to either
- Something being wrong with the currently installed build
- Something being wrong with the one I'm trying to install
That's why I posted in both places. Sorry if that is not the thing to do.
Thanks for your reply. I guess I'll have to do another reinstall then.
Wifi
Installed tonite smoothly however no wifi - anyone else with this?
Same here, just reported a bug to the bugtracker.
Make a clean install three days ago, all works fine
pahesis said:
Same here, just reported a bug to the bugtracker.
Click to expand...
Click to collapse
I have no wifi, too (after trying a dirty install over an old CM13 that resulted in an error). Here's the issue in their bugtracker, I think, in case anyone else experiences this.
Got the same issue when trying to go back to CM13 now -___-
Seems strange that I've had no wifi issues. I've tried turning it on and off with no problems.
A few (maybe patronising) thoughts:
Did you guys check the md5 hash?
Which recovery did you use? I used TWRP 3.0.2.5
Were you previously on COS13.1.2? I was.
I downloaded fresh open-gapps for the install - ARM64, 7.1, nano.
I wiped system, dalvik, cache. Installed LOS14.1, su, gapps in that order.
The dirty boot left me with lots of force closures so I wiped data, dalvik and cache, completed the wizard after booting and all was fine.
M.A.K said:
Did you guys check the md5 hash?
Click to expand...
Click to collapse
Yes
M.A.K said:
Which recovery did you use?
Click to expand...
Click to collapse
TWRP-3.0.3-0
M.A.K said:
Were you previously on COS13.1.2?
Click to expand...
Click to collapse
I was on the latest CyanogenMod snapshot.
I wiped data, dalik and cache, then installed lineage, gapps and su. Restoring a nandroid backup of CM13 did bring the wifi back again.
I then wanted to restore my backup of lineage, because I already transferred most apps and settings and don’t care to much for the wifi (hoping it will be solved in not too far future), but TWRP failed to recover, getting stuck while restoring data, only restoring the system partition. Strangely, after this, the wifi worked, however I experienced many FCs. After wiping data again, the wifi was broken again, the MAC adress showing as 02:00:00:00:00:00.
Wiping system, I tried to reinstall lineage without any extras, but TWRP just got stuck again with no progress being made after detection of the partitions. Strangely, restoration of the lineage backup worked now, including data The original problem persists, of course.
I mentioned COS13.1.2 specifically because it flashes partitions other than system that may affect your situation. CM doesn't. If you've had COS13.1.2 installed previously then these other partitions should be up to date.
If you're having inconsistent results using TWRP3.0.3 it may be worth trying 3.0.2.5.
ES File Explorer
Hello guys! I have a small problem. I installed the LOS 14.1 and now I have error in ES File Explorer, "Sorry test failed. This feature cannot run on your phone".
The su binary I already threw, and all files bin already threw. Help solve the problem!
p.s. sorry for my English
So, I unlocked my bootloader and wanted to flash Lineage OS, but my phone had a different opinion.
I went into TWRP and tried to format data, but I'm getting
Code:
Formatting Data using mkfs.f2fs...
mkfs.f2fs -t 0 -r 16384 /dev/block/mmcblk0p56
process ended with ERROR: 1
Unable to wipe Data.
Unable to format to remove encryption.
I've tried repairing the data partition, changing the filesystem, nothing works...
Any ideas as to what might be wrong, or how to fix it?
Thanks
todorare said:
So, I unlocked my bootloader and wanted to flash Lineage OS, but my phone had a different opinion.
I went into TWRP and tried to format data, but I'm getting
I've tried repairing the data partition, changing the filesystem, nothing works...
Any ideas as to what might be wrong, or how to fix it?
Thanks
Click to expand...
Click to collapse
Which recovery are u using ?
Armaty said:
Which recovery are u using ?
Click to expand...
Click to collapse
I was using TWRP, but I somehow managed to fix it using Redwolf. Have no idea what happened, but it's ok now.
Hello, I encountered the exact same issue with same origin...
Do you remember what you did to sort this out ?
thanks
(I posted in another thread, before finding yours)
You should check the f2fs kernel workaround guide .
Your problem is due to using incompatible twrp .
Read the guide you'll get around the problem .
0101chaitanya said:
You should check the f2fs kernel workaround guide .
Your problem is due to using incompatible twrp .
Read the guide you'll get around the problem .
Click to expand...
Click to collapse
Thanks... well that's weird, because I downloaded the TWRP recovery linked in LineageOs kuntao install page and I'm coming from stock...
Anyway I just solved my issue by installing Redwolf recovery :
There I could format /data.
I installed crdroid + gapps, but got a "Encryption Unsuccessful" on reboot.
I changed /data from f2fs to ext4 and could reboot properly.
Phone is working good. (I can't get fingerprint reader to unlock my crdroid rom but that's another story and maybe normal limitation, I'll check).
eljuggy said:
Thanks... well that's weird, because I downloaded the TWRP recovery linked in LineageOs kuntao install page and I'm coming from stock...
Anyway I just solved my issue by installing Redwolf recovery :
There I could format /data.
I installed crdroid + gapps, but got a "Encryption Unsuccessful" on reboot.
I changed /data from f2fs to ext4 and could reboot properly.
Phone is working good. (I can't get fingerprint reader to unlock my crdroid rom but that's another story and maybe normal limitation, I'll check).
Click to expand...
Click to collapse
If you ever need to format data just use official build from twrp.me. The one from Lineage wiki has some problems for now. Redwolf is probably based on official one, that's why you succeded.
The thing is that you need to use it ONLY to format /data partition and then switch back to Lineage one before flashing system zip. Known problem, wiki is just a little misguiding here.
Hello. Same problem here, not solved with RedWolf, neither official TWRP.
I've just followed the guide about lineage 15.1 and I really don't know how/if proceed.
Any help would be really appreciated
trespass23 said:
Hello. Same problem here, not solved with RedWolf, neither official TWRP.
I've just followed the guide about lineage 15.1 and I really don't know how/if proceed.
Any help would be really appreciated
Click to expand...
Click to collapse
Update: after closing and run again RedWolf, tap to Format data, magically it worked. I don't know why but thats'it.
Thanks.
this issue seems to pop-up now and then.
just to make it easier for future users coming across this issue. I had explained the issue here in the following post and how to fix it.
just scroll down till it says: "so for those that would like to switch to f2fs but for some reason end up in "black screen with blue led and the phone vibrates".
it applys to the same /data issue.
page 25 off official lineageos 8.1 thread:
https://forum.xda-developers.com/lenovo-p2/development/rom-lineageos-15-1-p2-t3814361/page25
I have a blank App in my app drawer since I flashed my custom ROM and now they're 3 of them. When I tap on the app info it says I need a broader app to view it. I included a screenshot. Anyone know what these are?
Also, my phone keeps randomly rebooting.
@newbrooster89
Looks like apps left from maybe a backup of whatever launcher you were using on your previous setup. Shows the partial icons but not the whole app because they are not installed now. That's what it appears to be. I use nova prime and, I can hold down (long press) an icon and it gives me options and one is playstore and you can select that and it takes you to play store to the app. See if you can long press and maybe select "search" or something that will take you to the app. If not just swipe em off your screen. Its nothing to be worried about. Just something from a past launcher backup/restore.
Edit/added:
Explain how you installed? What rom, what gapps package... What did you wipe in twrp recovery?
I always wipe data and system and cache unless whoever made the rom states not to in their op. (original post) Ex: Lineage 17 The dev says to only wipe data in twrp so that's what I do... otherwise I wipe data, system, cache flash rom, flash twrp installer zip reboot system. Then I boot back into twrp and install gapps and magisk zip for root and reboot system. That's my usual method for installing a rom.
I recommend a factory reset either through your phones settings or fastboot or twrp. See if that stops your reboots ..
NewbRooter89 said:
I have a blank App in my app drawer since I flashed my custom ROM and now they're 3 of them. When I tap on the app info it says I need a broader app to view it. I included a screenshot. Anyone know what these are?
Also, my phone keeps randomly rebooting.
Click to expand...
Click to collapse
if you flashed anything other than lineage you deserve what you are getting
flash713 said:
@newbrooster89
Looks like apps left from maybe a backup of whatever launcher you were using on your previous setup. Shows the partial icons but not the whole app because they are not installed now. That's what it appears to be. I use nova prime and, I can hold down (long press) an icon and it gives me options and one is playstore and you can select that and it takes you to play store to the app. See if you can long press and maybe select "search" or something that will take you to the app. If not just swipe em off your screen. Its nothing to be worried about. Just something from a past launcher backup/restore.
Edit/added:
Explain how you installed? What rom, what gapps package... What did you wipe in twrp recovery?
I always wipe data and system and cache unless whoever made the rom states not to in their op. (original post) Ex: Lineage 17 The dev says to only wipe data in twrp so that's what I do... otherwise I wipe data, system, cache flash rom, flash twrp installer zip reboot system. Then I boot back into twrp and install gapps and magisk zip for root and reboot system. That's my usual method for installing a rom.
I recommend a factory reset either through your phones settings or fastboot or twrp. See if that stops your reboots ..
Click to expand...
Click to collapse
I just ended up deleting everything and flashing a whole new ROM. I was on Lineage 17 but kept having so many bugs that I decided to try a different one. Thanks for the advice though.
sudoxd said:
if you flashed anything other than lineage you deserve what you are getting
Click to expand...
Click to collapse
That's what I was using and I had so many bugs and issues with it.
NewbRooter89 said:
That's what I was using and I had so many bugs and issues with it.
Click to expand...
Click to collapse
Then something was wrong on your end because lineage 17 is very close to being flawless. I've used it several times and always worked great for me.
Flash latest factory image & let it wipe (fastboot -w) at the end don't remove the fastboot -w in the script, if you did. I know many people do that ...
Boot twrp and Wipe data, flash lineage 17 w/gapps
Flash twrp installer (I use 3313) reboot system ...
Boot twrp, flash magisk root zip reboot system.
That's how I've always installed lineage and works great. Sounds like you had something interfering with it. Maybe residue from a past install or something but it was most definitely user error. Reflash factory image and wipe data and install it and it will be close to flawless. If not get logs and post them on lineage thread and someone there can tell you exactly what's going on. 11/30 build is not buggy.
flash713 said:
Then something was wrong on your end because lineage 17 is very close to being flawless. I've used it several times and always worked great for me.
Flash latest factory image & let it wipe (fastboot -w) at the end don't remove the fastboot -w in the script, if you did. I know many people do that ...
Boot twrp and Wipe data, flash lineage 17 w/gapps
Flash twrp installer (I use 3313) reboot system ...
Boot twrp, flash magisk root zip reboot system.
That's how I've always installed lineage and works great. Sounds like you had something interfering with it. Maybe residue from a past install or something but it was most definitely user error. Reflash factory image and wipe data and install it and it will be close to flawless. If not get logs and post them on lineage thread and someone there can tell you exactly what's going on. 11/30 build is not buggy.
Click to expand...
Click to collapse
you dont even need to flash the factory image, will work fine flashing from whatever they have now
sudoxd said:
you dont even need to flash the factory image, will work fine flashing from whatever they have now
Click to expand...
Click to collapse
That's correct you don't have to flash factory image but that's what I would do. There's always more than one way to do something.
flash713 said:
That's correct you don't have to flash factory image but that's what I would do. There's always more than one way to do something.
Click to expand...
Click to collapse
yes but why? just sounds like wasted time to me, our lives are short remember. that time could be spent with friends and family but no here you are flashing factory image before rom
sudoxd said:
yes but why? just sounds like wasted time to me, our lives are short remember. that time could be spent with friends and family but no here you are flashing factory image before rom
Click to expand...
Click to collapse
But I love to flash factory image. Jkjk. ?? The reason I had initially posted that on my comment was because I thought if anything wasn't right on his setup it would square it away or if something was left from another past install on sdcard it would clear it all up. Sure a format data in twrp will do same I just thought of that as an easy thing to say that had a zero % chance of being misunderstood. And what if he was on 9.0? ? That's just how I thought at that moment when I commented that. I know Lineage 17 build for Marlin is damn near flawless. I've been using it off and on since it came out. I see you are the dev who makes that kernel. Saw your link to your work. I remember you from long ago (i used to have another user name but had my account deleted a while back) on some Nexus device everyone and their mom owned. Maybe the 5 or 5x or the Gnex idk but I remember your kernel because it was bad ass.
It probably was something on my end. This is the first phone I've rooted with the A/B slots. I also did it through adb sideload because I was having issues with TWRP. I was also stuck in a bootloop when I installed it. Maybe I'll give it another shot. I did really like having Android 10 and my battery life was much better with lineage.