Hook

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

Lineage-23.0-20260119-NIGHTLY-pro1x with January 1st security patch installed smoothly via OTA. MindTheGapps16, and root was maintained.

Lineage-23.0-20260112-NIGHTLY-pro1x with January 1st security patch installed smoothly via OTA. MindTheGapps16, and root was maintained.

Lineage-23.0-20260105-NIGHTLY-pro1x with December 1st security patch installed smoothly via OTA. MindTheGapps16, and root was maintained.

Lineage-23.0-20251229-NIGHTLY-pro1x with December 1st security patch installed smoothly via OTA. MindTheGapps16, and root was maintained.

Sadly, I think I'm giving up. I managed to flash back the original stock, and I think even that was a miracle. Not surprisingly, after doing 1 update, it couldn't do any of the others. So I got the 2020 version of stock, which should have the proper update, and tried to flash it. ADB worked fine, Fastboot identified the phone after reboot into bootloader, but then fastboot would just stop working. Neither the flash_all nor trying each flashboot command manually worked. The operation was just suspend. I would leave it a long while just to make sure it wasn't like when the percentage stops

Lineage-23.0-20251222-NIGHTLY-pro1x with December 1st security patch installed smoothly via OTA. MindTheGapps16, and root was maintained. Again, to be clear, when I say "root was maintained" I mean that after OTA, and without reflashinng Magisk or opening the app, I still had root on my phone.

Sorry, I haven't been to attentive lately as Mrs. Hook has been having serious medical issues, but I am in the US (Virginia), I have a Pro 1 I don't use that much and, although I have never done this, I ought to be able to figure it out, I'm assuming that if I attach the screen to the cable and reflash to stock, the dead zone will be fixed on the screen. Would having the Pro 1 on latest stock and doing a factory reset with the new screen attached work? I have several Alie Express Elephone U Pro displays, so I can test to make sure my assumptions are correct, although tips from people who

If you are updating the same major version via OTA, you should not have to reflash magisk, I never do for OTA. Now, I only use Magisk for SU, so maybe it is different if you use different modules. I only ever flash Magisk if I am doing a non-OTA major version upgrade.

Lineage-23.0-20251215-NIGHTLY-pro1x with December 1st security patch installed smoothly via OTA. MindTheGapps16, and root was maintained.

Lineage-23.0-20251208-NIGHTLY-pro1x with December 1st security patch installed smoothly via OTA. MindTheGapps16, and root was maintained.

Lineage-23.0-20251201-NIGHTLY-pro1x with November 1st security patch installed smoothly via OTA. MindTheGapps16, and root was maintained.

Lineage-23.0-20251124-NIGHTLY-pro1x with November 1st security patch installed smoothly via OTA. MindTheGapps16, and root was maintained.

Lineage-23.0-20251117-NIGHTLY-pro1x with November 1st security patch installed smoothly via OTA. MindTheGapps16, and root was maintained. Lol. Maybe I should just have one post and keep adding to the list, 😉

Lineage-23.0-20251110-NIGHTLY-pro1x with November 1st security patch installed smoothly via OTA. MindTheGapps16, and root was maintained.

Lineage-23.0-20251103-NIGHTLY-pro1x with October 1st security patch installed smoothly via OTA. MindTheGapps16, and root was maintained. A bit late this week (me, not the update) as my son is visiting from Colorado.

Lineage-23.0-20251027-NIGHTLY-pro1x with October 1st security patch installed smoothly via OTA. MindTheGapps16, and root was maintained.