Leaderboard

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

Helga is still here, but a whole lot more gray, just like me. 11 years old now...

Necromancing this thread with a dog I got yesterday...

Try this. The download links seem to work (I am not knowledgable on any of this)... https://web.archive.org/web/20200406195436/http://files.nwwn.com/android/pro1/factory.html

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

Sorry for the late reply but I do have a copy if your still interested. This is the qfpkg_linux.zip, not sure if there were any others. qfpkg_linux.zip

Hello, Soo today i have tested today touch fix on new display from ali. Method with goodix app does not work on los22...all was fine...selinux set, read data from display was working too, but after flashing new firmware phone makes reboot and nothing - still same. But method - flashing stock rom without wipe, wait for boot and then flash back los22 works fine 🙂 ...only reinstal magisk was needed

Lineage 23.0 (Android 16) has been released for the Pro1X. I haven't yet had time to install it bbut will either tonight or tomorrow morning, if you want to let me be the guinea Pig. 😉 https://download.lineageos.org/devices/pro1x/builds https://wiki.lineageos.org/devices/pro1x/upgrade/ https://wiki.lineageos.org/gapps/

Finally I can add something of value to this forum :-) This is Harry, he is a rescue and living with us since a good year now.

Here is it for you 🙂 https://drive.google.com/file/d/1HxTmm2_oW65ijT2Ewf7pCh4qjF_JKHkK/view?usp=sharing

I never read your post, just your PM 🤪

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

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

I may try it one of these days

F(x)tec never had all the driver sources. And even if they did, they would not have been allowed to publish them. A prominent exception is the keyboard, which is the one hardware component they developed themselves. The rest of the hard- and software came from a Chinese OEM. The idea that f(x)tec ever wanted to make the Pro1/Pro1X "open" phones is a misconception introduced by some media and bloggers. F(x)tec never publicly corrected that misunderstanding, presumably as they hoped to profit from all that "Linux-phone" hype. In reality, the Pro1 was designed as a pretty standard, proprieta

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

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

Lineage-23.0-20251013-NIGHTLY-pro1x with October 1st security patch installed smoothly using the Lineage upgrade procedure linked in the OP. It was installed with MindtheGapps 16 and Magisk 29 installed as a zip for SU only. all data was preserved in the upgrade. I did have to open the Magisk app to let it run an update, but root was established. All went according to plan and everything seems to be working so far.

Lineage-22.2-20251006-NIGHTLY-pro1x with September 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.

Lineage-22.2-20250929-NIGHTLY-pro1x with September 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.

New build of LineageOS 16.0 for qx1000 (OG Pro1) available at https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1. Go for the ROM dated "20250926". Changes since last upload: Backported ASB security fixes up to September 2025. Have fun!

Lineage-22.2-20250922-NIGHTLY-pro1x with September 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.

Lineage-22.2-20250915-NIGHTLY-pro1x with Aug 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.

Lineage-22.2-20250908-NIGHTLY-pro1x with Aug 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.

Lineage-22.2-20250825-NIGHTLY-pro1x with Aug 1st (Finally!) security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.

Lineage-22.2-20250728-NIGHTLY-pro1x with July 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.

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

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

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

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

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

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

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

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.

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.

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-20260119-NIGHTLY-pro1x with January 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.

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

...change display and reflash is not too hard. If you want then you can write me PM and i will help you 🙂

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.

I think that for an OS like Lineage, which is supposed to be just Android-without-the-Google-bits, upgrading the major Kernel version will be next to impossible. The proprietary vendor blobs compiled for 4.4. will not load with 4.14 or later. That's just not how Linux works. Yes, there may be some other ms8998 devices out there using later Android kernels. So it may boot somehow. But what's the good of that if your LTE-modem, camera, and touchscreen no longer work?

Hello all, As @elvissteinjr correctly stated, Pro1 needs a kernel patch to be supported in LOS 23. in the concrete case that the ebpf backport will not be available for the kernel 4.4, I googled for msm8998 devices and there are one or two shipped or updated with kernel 4.14. maybe trying to update the kernel to that version is the way to. Also thinking that some hardware is shared with pro1x that is shipped with 4.19 will make easier the compilation. Do we have the kernel sources for pro1?

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

Ah thanks for the info! I optimistically tried 22.2 again (20251011), still not working VoLTE not supported, 😠 (expecting the 23 I thought this might be the last 22.2, so wanted to test before 23) So going back on 22.1 (20250405)- where VoLTE works ☺️

I would try to flash only the (unpatched) boot.img with fastboot: fastboot flash boot boot.img The original boot.img can be extracted from an ota.zip, either manually or by using free tools like these. While this should preserve your data, it's obviously recommended to backup your stuff first. Applies to any kind of flashing job, actually.

Lineage-22.2-20250811-NIGHTLY-pro1x with July 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained. I want to note that even though my Pro1x has working phone stuff, it has never demonstrated the battery drain problem on 22.2.

Due to the changes @Hook reported here, I tried upgrading to 22.2 (again). Will edit this post in some hours with the result.... ADD: And it is completely USELESS!!! Went from 97% to 47% in short of 8 hours. (Idle overnight, as much as possible uninstalled/disabled,,,,) Will go back to 22.1, or maybe stock and just forget about LineageOS, that (like the AICP project) seems to have F.. itself up to a useless state... Went back to 22.1, though over four months old still much newer than Android 9 in stock....,

I don't have any objective way of testing this, but I noticed that the change log for the last update and this one included references to carrier stuff. It seems to me that my phone call clarity has improved. The phone stuff actually worked pretty good for me from the get go. It wasn't perfect but far better than many people were reporting. But it seems, though anecdotal, that it has improved. Unfortunately, I don't really use this phone as a phone, as ironic as that it is for one that mostly works. So I haven't tried in a very long time, which makes this anecdotal report even more suspici