Leaderboard

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

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

Well, color me surprised, but after getting the phone back in an almost normal state (Android flashed back on it with the official image from Fxtec - and a 99% broken fastboot implementation in the bootloader), my phone actually has it's IMEI still intact (The one I see with *#06#*, I haven't tried to check the second one yet) and everything works as it should, so apparently it is possible to overwrite the persist partition without any issue ??? 🤔

Did the OTA update on both Gapps and non-Gapps phones as described above. Root was maintained by method described above (ie. the current Magisk recommended method). Updated Magisk app from v.30.6 to 30.7 during the process. All is well.

I whined about multiple bugs with 22.2 in the LOS thread here. The 22.1 is fine, so I would suggest to start to go for 22.1, before travelling further backwards. Last 22.1 was: lineage-22.1-20250405-nightly-pro1-signed.zip That can be found here: https://lineage-archive.timschumi.net/build/29528

I use fastboot for flashing pro1/QX1000 just fine. Why does it not work for yours? I have no idea on the edl file. Will check if I got one downloaded somewhere, but i doubt it.

Have you tried following the guide linked by my initial post pinned in here?

Yeah I got that. But, afaik, staying on 22.1 would require manual backporting of all ASB patches. The 21.0 branch still receives those from upstairs for all devices, so an ASB-updated rom of 21.0 should build out-of-the-box, with no Pro1-specific maintenance needed.

If the (qx-1000) Pro1 drops out of support at the official build farm, I suggest we find someone who is willing to make unofficial LOS 21.0 builds. That release seems to have worked better than 22.x anyway, and since it is from before the QPR mess, its Lineage code branch will receive ASB fixes for some years to come. I currently do not plan to do it, as my LOS 16 is still going strong enough for me, but feel free to try to talk me into it ... 🙂

SOLD!!! :) Many Thanks

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.

Just checked the official download page, and currently it only contains ONE build. I wonder if that is a sign that it is soon dropped completely?

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

I will do my usual OTA method next week and report back. Glad you have your 1x up and running now Hook.

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.

Yes, I already tried them but most of them are for flashing with fastboot and that's no oppurtunity for this device. The required files (firehose_progammer.edl) are missing. Maybe I could use a Firehose file from a different device which uses the same CPU (SD835)?

The only way I could ever get anything approaching reliable cell tower connection was by setting the phone to connect by WCDMA only. T-Mo has now shut that service down in the US, so that pretty much bricks the device as a phone now. Mine always had decent WiFi connection, so maybe you could get VoWiFi working when you have a hotspot, but that's probably all. If you figure this out, you'd be the first. Good luck!

Might be a long shot, especially given how long it's been since you posted this, but do you have a copy of the perist.img you flashed? I could need one to flash on mine as well, even if it means loosing my IMEI ¯\_(ツ)_/¯