LineageOS 23.x Official Release for Pro1-X (QX1050)

[Hook 3,297]

5 hours ago, Name_not_avail said:

Interesting. I just did this update on one of my Pro 1x phones, and it worked fine.

I did it the usual way that I do to avoid losing root, ie. wait for the update process to require reboot, then open Magisk, select install to vacant slot, then reboot. 

All working tickety boo now, version 23.2-20260209-NIGHTLY-pro1x

Of course LTE reception remains unusably bad, but that kinda goes without saying now.

I guess I should wait for the next update for my other 1x.

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, 

[Name_not_avail 72]

OTA, because I am too lazy for sideload unless absolutely necessary.

Start the OTA, let it grind on ad nauseam, wait for the message to reboot, stop there and open Magisk app, select install to vacant slot, Magisk runs its little script, then swap back to the OTA and touch reboot.

Done it a couple of dozen times like that, it always works.

I recall that you and I installed Magisk in different ways, and had words here about it. I can't recall exactly what the difference was now, but you could parse our old comments here to check it. I think you claimed you didn't need to do this shuffle with the Magisk app when using the OTA, but I found that I would lose root if I did not do that. I think it had to do with the different approach we each took to the original root.

I would suggest trying the OTA again, stop at the "reboot now" toast, open Magisk and select install to vacant slot, and THEN reboot. Can't be worse than where you are now, and it may well work.

I should say this particular updated 1x has Gapps installed, and I can't recall now specifically how I did that. My other 1x is Google free, so I may try to update that one soon for pure devilment, and see what happens. Both of them were originally rooted the same way at the same time, and both of them are regularly updated through OTA by means of the above described method to preserve root.

[Hook 3,297]

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 is not. I may try following the upgrade instructions and see if that works.

[Hook 3,297]

10 hours ago, Name_not_avail said:

I would suggest trying the OTA again, stop at the "reboot now" toast, open Magisk and select install to vacant slot, and THEN reboot. Can't be worse than where you are now, and it may well work.

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.

 

[Name_not_avail 72]

According to the principle of, "Never ask someone to do something that you wouldn't do yourself", by which I lead my life, I just updated my second 1x, the one without any Gapps.

It worked flawlessly.

Don't know what to tell you Hook, but this is definitely not a universal problem for the 1x.

[Hook 3,297]

12 hours ago, Name_not_avail said:

According to the principle of, "Never ask someone to do something that you wouldn't do yourself", by which I lead my life, I just updated my second 1x, the one without any Gapps.

It worked flawlessly.

Don't know what to tell you Hook, but this is definitely not a universal problem for the 1x.

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 do a whole install from scratch. Have no idea what could be creating this problem, but it isn't my rooting method.  😉

So, upshot, People may do fine with this update. I have no clue why I am getting this. Maybe my Pro1x is mad at me for paying so much attention to Writer Decks.

[Hook 3,297]

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.  

[Hook 3,297]

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 update to the Feb 16th update with the February security patch OTA.

So what was the problem? Don't really know for sure. My best guess is that, given @Name_not_avail's success, is that LOS 23.2 no longer tolerates the way I used to install Magisk, even though it worked flawlessly up through 23.0. It was, I knew, a no longer fully supported and depreciated install method.  For now I'll rebuild the device and worry about root when I'm done.  I will probably have to, for now, install it from the app and try Name's method to preserve root after that.  A shame.  The old method was so simple. We will see how it all goes next Monday.  🙂 

Whatever the case, I consider the problem solved for now.

[Name_not_avail 72]

I will do my usual OTA method next week and report back.

Glad you have your 1x up and running now Hook.