All Activity

I just dealt with this issue on a new Windows 11 PC, mentioned in the LOS 23 thread. Same symptoms as the OP here, trying to use fastboot. If you look at the devices attached to the PC once the phone is connected to it in fastboot mode, I expect you would see a driver error on the PC. The solution for me was to install a dedicated Andriod phone fastboot interface driver in the PC operating system. I can't advise how to do that with Linux, but I'm sure the OP can figure it out.

I went ahead and did this, too. No issues as yet. The one hiccup was that I had recently "upgraded" the OS on my PC to Windows 11, and it didn't have a fastboot driver for an Android device, to use with installing the Magisk img file. The phone shows as an unknown device on the PC when the phone was rebooted into fastboot mode, and when trying to update the driver manually, the default driver list does not show Android Phone. The default driver list did show "Samsung Android Bootloader Interface" though, and I installed driver version 2.21.0.0 of that. It worked just fine f

Lineage 23.0 (Android 16) is out for the Pro1x. This conversation continues here:

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

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!

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.

It will wipe it, sorry.

I have had Magisk on my Pro1X since I got it (as well as my Pro1 before that). Sometime in the last year, while trying to get ChatGPT to like my phone, I tried several modules in Magisk and also tried hiding it. When I hid it, it created a shortcut on the home screen. Recently, I realized that shortcut was gone and I can no longer get into the Magisk app GUI. The phone still appears to be rooted, but all attempts to reinstall Magisk and run it have failed. I've also tried removing all the Magisk modules through ADB and re-installing Magisk, but still no luck. I'm hoping that I ca

Strange as it may sound, the connection of fastboot is more picky than adb. Usually an older pc, a usb hub or a Linux OS seems to fix it. I primarily see the issues with Windows pc with an USB3 port. I got the issue on mine too, but even a USB3 port on a thunderbolt docking works. As an old tech guy it oozes of handshaking issues, that is a bug in the driver for Windows means it can not correctly handle if things goes too fast, and an usb2 port or a hub is enough overhead for handshaking to work...

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

I got a problem with fastboot. From my PC with adb no problem, but after I did the command : adb reboot fastboot (or adb reboot bootlaoder), the phone reboot in fastboot mode but second after, got a logo screen and it says Press any key to shudown. The command fastboot devices return nothing. I tried many different USB cables, different port on my PC, but nothing works. I'm running Linux (Ubuntu 24.04), so what can I do now that I'm not tried before ? Thanks.

I previously tried to report a bug - and frankly I do not want to to try that again. With neither calls on 4G nor multilingual keyboard working, and combined with ridiculous stamina, It is unusable as a daily driver for me anyway. for 22.1 it is only the keyboard that is messed up. And has been since perhaps 20.1 or even older. So more reporting the state here so others do not waste their time with it, than actually expecting anyone that can fix it to read it here,

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

I mean that it is for nothing to crying here 😞 Only way is write to lineage gitlab and wait for result 🙂

is needed to replace micro switch on flex cable or whole flex cable with switches.

Hi all, My power button sunk in. Are there any spare-parts and fix guides around? Thanks!

I optimistically tried 22.2 again (20250913), still not working VoLTE not supported, 😠 So back on 22.1 - where VoLTE works ☺️

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

Lineage-22.2-20250901-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.

I wish I had an answer for you for what is going on. I have no idea on how the legal construction/status is, and if any assets are left at all. The fxtec site has for long just redirected to some 'placeholder'-page, but some deep links (including this community) is still kept alive (AFAIK). I have no idea who is paying for them staying alive. I'm not sure if it was this thread or another, but a year or two back, some dug up info on the company from some official British site, and the company was still alive back then.

Thank you. Since this post and today, the fxtec.com site no longer allows me access to my order at all! This is a real shame because I cannot use a phone touch screen and really need a real QWERTY keyboard! I do not see how they can just ignore liabilities of unfulfilled orders. I plan to report to my state Attorney General's Office (when I get time!) just to document their malfeasance. They should declare bankruptcy, or have to community file a class-action lawsuit. OK my $900 is gone, but . . .