Hook

Lineage-23.2-20260309-NIGHTLY-pro1x with February 1st security patch installed smoothly via OTA. MindTheGapps16, and root was maintained. Changelog: https://download.lineageos.org/devices/pro1x/changes

Lineage-23.2-20260302-NIGHTLY-pro1x with February 1st security patch installed smoothly via OTA. MindTheGapps16, and root was maintained. Changelog: https://download.lineageos.org/devices/pro1x/changes

That sort of happened with the Pro1x as well. When the first 23.2 build appeared, they did leave 1 23.0 build up but didn't wait for the other older builds to drop off the page as new 23.2 builds were added. They were chopped. I would guess that as long as one of the devs has a Pro 1 and Pro1x, builds will continue, but have no doubt that means support could end any time and probably be a sudden drop.

Yes, I am updated to 30.7 as well. It's easy to do (two taps and reboot) and can be done any time. It doesn't need to be done immediately during OTA to retain root. Obviously, I do need to check more often than I was before, but it's not a big deal. I am curious why I couldn't get the prescribed method to work, meaning not the OTA method @Name_not_avail describes, which is easy enough if I could get to that point, but the initial patching of the boot image to install Magisk initially. But I'm not that curious. The method I use for initial installation is so much easier and simpler and,

As predicted... OTA, root preserved, no need to do any dance with the Magisk app. Everything is as it used to be, simply taking the OTA and rebooting. Lineage-23.2-20260223-NIGHTLY-pro1x with February 1st security patch installed smoothly via OTA. MindTheGapps16, and root was maintained. Changelog: https://download.lineageos.org/devices/pro1x/changes

well, here's a new wrinkle. I had been trying all week to install Magisk the way they say to in the official instructions here: https://topjohnwu.github.io/Magisk/install.html#patching-images This was really just obsession, I don't have a huge need for root anymore. But no matter what I did, root didn't take and every time I went back to the app it didn't indicate I had root. I was honestly about to give up, but I hate to be defeated by computers. Lol. So I tried on last hail mary. I rebooted into recovery and without reinstalling anything else, I retried my old method of flashing Mag

So, I tried doing LOS 23.2 (the Feb 9th update) as if it were a new install with were a new install, doing a factory reset and all. It just made things worse,,, I got the same symptom of it only booting to bootloader, but worse because I finally could not get back to LOS 23.0 and, of course, I couldn't reinstall 23.0 because that was viewed but the system as a downgrade. So on a whim, I decided to try something. I did the whole thing over again (including factory reset-- nothing to lose at this point), but this time I didn't flash Magisk. Boom, Everything worked. I was also able to up

Well, whatever is going on (which could be something that happened at my end, though I'm baffled as to what) the new weekly update didn't fare any better. So I am forced to try a fresh install, wiping everything. I don't know how soon I'll get around to it, but I will update when I do.

Oh, I agree. I don't think it's specific to any device, and it is clearly not universal, but there have been a couple reports out there of either the same thing or something similar happening on different devices. No good clues provided by any of the reports. The ones on the bug report Gitlab are being looked into. I tried treating it as a full upgrade and that didn't work either. At least it still gave me back 23.0. Unless some information pops up about what the problem might be, I will wait until Monday and try the new update. If that doesn't work, I will have no choice but to wipe and

Sadly, it didn't work. Had to do the dance to get it to boot back to 23.0. Still have root. The result was the same as previous attempts to upgrade to 23.2. I may wait for the next update and see if things go any better. Otherwise, I will try installing it as if it were an upgrade even though it is still Android 16.

The difference was that I only flash Magisk when I sideload Lineage, which I only do when Lineage goes to a new version of Android. It's the only time I ever open the Magisk app to let it update. After that, all OTA updates leaves me with Root and always has. I will try doing what you describe and see if it works. It seems odd to me, given that my method has worked for some years now. And not clear to me why it would cause a problem with booting... I should just lose Root. I'm almost wondering if the jump from 23.0 to 23.2 isn't acting as if it is a full version update even though it

So are you talking sideload or OTA? Right now I am using OTA. I can certainly tru the update instructions that uses sideload but doen't lose data, but I had the impression that didn't change the outcome. I can give it a try,

Warning! ⚠️ Tried to update to Lineage-23.2-20260209-NIGHTLY-pro1x (notice we have jumped from 23.0 to 23.2). It reboots to the bootloader menu. It won't reboot to system and if you go to Recovery, rebooting to recovery does not change the slot. However, doing a shutdown, booting the phone (you still end up in bootloader menu), going to Recovery and doing a System reboot finally boots the older Lineage 23.0 (Future reboots are fine) with 23.2 in the updater labeleed as needing installing. This problem has been reported in the their Github for two other devices with people having tri

Lineage-23.0-20260202-NIGHTLY-pro1x with January 1st security patch installed smoothly via OTA. MindTheGapps16, and root was maintained. Changelog: https://download.lineageos.org/devices/pro1x/changes

Lineage-23.0-20260126-NIGHTLY-pro1x with January 1st security patch installed smoothly via OTA. MindTheGapps16, and root was maintained. As long as I am posting these weekly, might as well link the changelog: https://download.lineageos.org/devices/pro1x/changes