Leaderboard
Popular Content
Showing content with the highest reputation since 08/08/2025 in Posts
-
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 i5 points
-
Helga is still here, but a whole lot more gray, just like me. 11 years old now...4 points
-
4 points
-
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.html4 points
-
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 firmw4 points
-
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.zip4 points
-
No - the same plug, the same voltage, similar capacity, but no way to fit it into Pro1 case3 points
-
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/3 points
-
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.3 points
-
Here is it for you ð https://drive.google.com/file/d/1HxTmm2_oW65ijT2Ewf7pCh4qjF_JKHkK/view?usp=sharing3 points
-
3 points
-
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 up3 points
-
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 tri3 points
-
3 points
-
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, proprieta3 points
-
Lineage-23.0-20251027-NIGHTLY-pro1x with October 1st security patch installed smoothly via OTA. MindTheGapps16, and root was maintained.3 points
-
Lineage-23.0-20251020-NIGHTLY-pro1x with October 1st security patch installed smoothly via OTA. MindTheGapps16, and root was maintained.3 points
-
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.3 points
-
Lineage-22.2-20251006-NIGHTLY-pro1x with September 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.3 points
-
Lineage-22.2-20250929-NIGHTLY-pro1x with September 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.3 points
-
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!3 points
-
Lineage-22.2-20250922-NIGHTLY-pro1x with September 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.3 points
-
Lineage-22.2-20250915-NIGHTLY-pro1x with Aug 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.3 points
-
Lineage-22.2-20250908-NIGHTLY-pro1x with Aug 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.3 points
-
Lineage-22.2-20250825-NIGHTLY-pro1x with Aug 1st (Finally!) security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.3 points
-
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/changes2 points
-
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/changes2 points
-
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/changes2 points
-
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_2000512 points
-
Yes, I have some boot.img. One moment... Link: https://limewire.com/d/12R72#U1UK7JaNiG2 points
-
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/changes2 points
-
Lineage-23.2-20260323-NIGHTLY-pro1x with March 1st security patch installed smoothly via OTA. MindTheGapps16, and root was maintained. Changelog: https://download.lineageos.org/devices/pro1x/changes2 points
-
Lineage-23.2-20260316-NIGHTLY-pro1x with March 1st security patch installed smoothly via OTA. MindTheGapps16, and root was maintained. Changelog: https://download.lineageos.org/devices/pro1x/changes2 points
-
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/changes2 points
-
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 ??? ðĪ2 points
-
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.2 points
-
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/295282 points
-
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.2 points
-
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/changes2 points
-
Lineage-23.0-20260119-NIGHTLY-pro1x with January 1st security patch installed smoothly via OTA. MindTheGapps16, and root was maintained.2 points
-
Lineage-23.0-20260112-NIGHTLY-pro1x with January 1st security patch installed smoothly via OTA. MindTheGapps16, and root was maintained.2 points
-
Thank you very much for all of your effort. I'd be interested in giving it a try myself. I'll send a DM.2 points
-
...change display and reflash is not too hard. If you want then you can write me PM and i will help you ð2 points
-
Hi Everybody, I am sorry for the late response. I was to busy for almost 2 month and forgot to answer here. Today I updated to lineage-22.2-20251022-microG-NO-PI-PATCH, and that did remind me that I have an open promise here. On my Pro1 the new SIM card almost solved the battery drainage problem. The phone is still consuming a little bit more battery than it did before the update to LOS 22. That time I had to charge it every second day only. Now with the new SIM card the battery works for a full day again. That makes the Pro1 use-able for me.2 points
-
Not using it myself on the Pro1X. But most SFOS users (well, still quite few actually) are on discord. I send you an invite link via pm. Be reminded that whatever technically did not work on Android/Lineage with your Pro1X will also not work in SFOS. Under the hood, it is the same core OS, after all. There will be additional technical limitations with respect to Android, because not every function is available from SFOS userspace. E.g., as far as I know, VoLTE does not work with SFOS on Pro1/X, while it does in Lineage.2 points
-
Very optimistic. Android 16 comes with additional eBPF feature requirements to the kernel, which the 4.4 version the Pro1 is stuck on doesn't fulfill, but the Pro1X's 4.19 kernel version does. Or rather, those have been backported down to that version, but nobody has done this for 4.4 yet. See the LineageOS announcement for some details: https://lineageos.org/Changelog-30/ It may happen, but not within a few days if it does.2 points
-
Lineage 23.0 (Android 16) is out for the Pro1x. This conversation continues here:2 points
-
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.2 points
-
Lineage-22.2-20250818-NIGHTLY-pro1x with July 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained. A little slow on getting the Aug security patch.2 points
-
...i have i mean 2 flex spare cables and 2 small pcbs from top part - pcb between flex and display/camera/earpiece. I have repaired some fx and mainly not working display was not problem by flex but by pcb on top. Was needed to resolder flex connectors.2 points
