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

I'm going to approach this thread a little differently. Rather than endless pages of new posts with each weekly update I install where everything goes smoothly, I'm going to simply update post #2 with the current week's information, Any new additional posts will now either be because I had trouble with it that week or people are discussing Lineage 24 on the Pro1x, That will mean that the thread won't show there is an unread post when I update and you will just have to check the thread if you want to know if I updated and it was successful. And, if no one has much to say, the post may

Lineage-24.0-20261026-NIGHTLY-pro1x with October 1st security patch installed smoothly via OTA. MindTheGapps17, and root was maintained. Changelog: https://download.lineageos.org/devices/pro1x/changes Updated 10/26/2026

Apologies for not checking this thread more regularly! I can still flash screens for the Pro1 X.

No - the same plug, the same voltage, similar capacity, but no way to fit it into Pro1 case

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.2-20261005-NIGHTLY-pro1x with September 1st security patch installed smoothly via OTA. MindTheGapps16, and root was maintained. Changelog: https://download.lineageos.org/devices/pro1x/changes

Hello. I’ve been using my Pro1x as my only phone for two years now, everywhere I go. Yes, I have black corners and a big black spot on the screen too, and the reception, call quality, and internet performance are mediocre. But... I own a Pro1x—something truly special. It turns heads wherever I go; no one has ever seen or used anything like it. It’s a very exclusive device, and I actually use it. I’m proud of it and have to take my hat off to FxTec for actually pulling it off. My display is broken now, but I’m sure I can sort that out, too. And I don't care that the big players like App

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

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

Great to hear you found the cause and a way to get the data out. We have in other threads looked for the battery, but AFAIK no perfect match have been found, sadly.

Update: Battery was the culprit. I have replaced the battery with Xiaomi Mi6 BM39 and my Pro1 has successfully booted to Lineage 🙂 Now I can at least transfer all my data...

Lineage-23.2-20260727-NIGHTLY-pro1x with July 1st security patch installed smoothly via OTA. MindTheGapps16, and root was maintained. Changelog: https://download.lineageos.org/devices/pro1x/changes Another pretty small update, Wonder if they are working on Android 17 or if there's not much left to do because 16 is it. 😉

Lineage-23.2-20260720-NIGHTLY-pro1x with July 1st security patch installed smoothly via OTA. MindTheGapps16, and root was maintained. Changelog: https://download.lineageos.org/devices/pro1x/changes Not a big update, but I always test them.

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

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

Phew! That was close. Didn't get a chance to update until Tuesday night and discovered my Pro1x had been knocked loose from it's magnetic charging cable. It was rebooting and came up with 7% power. Was it in a boot loop because power was so low? Did I need my rubber bands. Apparently not. Don't entirely know why it was spontaneously rebooting, but it didn't start shutting down again. I connected the charging cable and turned off the screen and a couple of hours later it was full (Have it set to not charge over 85%. I think I was lucky. Lol. All's well that ends well. 😄 Lineage-23.2

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-20260504-NIGHTLY-pro1x with April 1st security patch installed smoothly via OTA. MindTheGapps16, and root was maintained. Changelog: https://download.lineageos.org/devices/pro1x/changes

You mean GAPPS for LineageOS 21.0? Then...this one: https://github.com/MindTheGapps/14.0.0-arm64/releases/tag/MindTheGapps-14.0.0-arm64-20250203_200051

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-20260420-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

Lineage-23.2-20260330-NIGHTLY-pro1x with March 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

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-20251229-NIGHTLY-pro1x with December 1st security patch installed smoothly via OTA. MindTheGapps16, and root was maintained.

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.

...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-20251201-NIGHTLY-pro1x with November 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-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.