All Activity

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

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

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,

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.

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

android auto latest version from the play store. never experienced your problem. version 16.1.660414-release com.google.android.projection.gearhead using QX1000 on lineageOS 22.1 2025 02 22 nightly build just used it today with AAWireless adapter for wireless android auto on sony XAV-100, prior to that i used to use it via cable and also did not experience what you are seeing

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

Interesting...you have classic pro1? And AAuto version? I am now on latest version and problem still - is on cable and on wireless too. Tested in toyota 2025 and vw 2017 2025-11-24-14_06_362 (1).mp4

I'm not sure if a cli version was ever released. I couldn't find any mention of it in the first few pages. If it had been released, that would have been my choice of tool.

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

using LOS 22.1 and i didn't notice any problems. my head unit is Sony XAV-AX100. i used to plug directly but i got AAWireless to do wireless android auto and everything worked fine. wired was unreliable but i suspect that was a cable issue. Last i used it was about a week ago.

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.

One more update, with apologies for the triple-post. I received a secondhand original Pro1 in the mail from the indefatigable @Hook. Using the official flashing guide from this thread, I updated the Pro1 to firmware 20200825 and re-ran the initial setup process (including a one-time factory reset). The Pro1 was confirmed to be working normally. However, when I unplugged the original Pro1 screen frame and plugged in my Pro1 X screen frame (with the replacement Elephone screen attached), the Pro1 immediately entered a boot loop. I then went back to the guide and reflashed all the firmw

An update to this. My replacement Elephone U Pro screen arrived yesterday, but I didn't have a chance to install it until today. The screen is clearly secondhand; there was exposed, dirty adhesive on the back, and the plastic scratch protector on the front is also scuffed. The screen itself is largely undamaged. It came with several tools to help with replacement, including spudgers, adhesive strips, and two small screwdrivers (one Phillips and one flat). The display frame was very easy to remove per F(x)tec's instructional video. It was a little more difficult to remove the screen from t

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

Happy New year to everyone. Lowered the price to 600€

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

I've seen a few posts raising concerns about how much longer this community forum will be available. It seems F(x)tec is still in business, working on the Clicks keyboard case and other projects, but I don't know if there's a future for the Pro1 line. I've gained a lot of useful information from here, so as a precaution, I saved an offline copy of the forum over the weekend. Specifically, the command I used to mirror the forum was: wget -E -k -m -np -p https://community.fxtec.com The archive is about 17 GB in total. Compressed as .tar.gz, it shrinks to about 2.3 GB, which I think i

Thank you very much for all of your effort. I'd be interested in giving it a try myself. I'll send a DM.

Not in a hurry to sell. It leaves space to negotiate

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.

Optimistic pricing helder_alemao, I think you would be lucky to get half that, despite it being a vintage rarity by now...