if you want Android 11 / lineage-18.0 :highfive:
https://forum.xda-developers.com/pi...om-lineage-18-0-pixel-3-xl-blueline-t4185847/
https://forum.xda-developers.com/pi...om-lineage-18-0-pixel-3-xl-blueline-t4185847/
Is anybody having update problems with the latest nightly? I have a pixel 3 (blueline) that is successfully running the September 15 nightly. Today, I updated to the October 27th nightly. The phone never successfully boots up. I see nothing but the lineage boot animation. Finally, after about 10 or 15 minutes, it reboots a few times, and finally finishes booting -- and I'm taken back to the September 15 image. Obviously, the A/B partition stuff is working well, thankfully -- as I'm back on a working image. But I'm not sure what is going on that is preventing me from updating to a newer version. I might try the previous week's October 20th nightly, but I guess I'm hoping to hear some reports from others before I keep working on it.
Just reflash magisk to inactive slot before you reboot - works for meUpdates have been perfect, only issue is after every OTA I loose root, just gonna make do without it though.
Just reflash magisk to inactive slot before you reboot - works for me
How do you flash the inactive slot?Just reflash magisk to inactive slot before you reboot - works for me
I wonder if it has something to do with how you install it. Did you sideload magisk or patch the boot image (I sideloaded). Also, I'm on the latest canary, I'm not sure when this started working.I installed the new magisk but after updating it has been erased as usual![]()
I don't think that would matter. It gets overwritten anyway. I noticed there's a 99-magisk.sh in my /system/addon.d. Do you have that? I wonder if that doesn't get installed if you patch the boot image yourself.
By the way, I just took another OTA and magisk is still there after it completed.
adb shell pm disable-user --user 0 com.google.android.euicc
adb shell pm disable-user --user 0 com.google.android.ims