All Activity

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

Selling my Pro 1X on vinted and Wallapop in case anyone is interested FxTec pro1 X | Vinted FxTec Pro1 X Azul em segunda mão durante 800 EUR em Queijas na WALLAPOP Also selling Gemini PDA, Cosmo Communicator and an Astro Slide 5g

Thank you so much for your responses! The replacement screen I ordered is not here yet, but once it arrives, I'll test it just to confirm that it does in fact need reflashing. @Hook If the test works with your AliExpress screens, I'll make arrangements over DM. I might even buy a second spare screen as a backup, if ou're willing to part with one. @CornholioGSM If it doesn't work, I'll reach out via DM.

Sorry, I haven't been to attentive lately as Mrs. Hook has been having serious medical issues, but I am in the US (Virginia), I have a Pro 1 I don't use that much and, although I have never done this, I ought to be able to figure it out, I'm assuming that if I attach the screen to the cable and reflash to stock, the dead zone will be fixed on the screen. Would having the Pro 1 on latest stock and doing a factory reset with the new screen attached work? I have several Alie Express Elephone U Pro displays, so I can test to make sure my assumptions are correct, although tips from people who

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

If you are updating the same major version via OTA, you should not have to reflash magisk, I never do for OTA. Now, I only use Magisk for SU, so maybe it is different if you use different modules. I only ever flash Magisk if I am doing a non-OTA major version upgrade.

Yes, after every update per OTA you have to reinstall magisk to the inactive slot before restart!

I have a black semicircular blob on the bottom corner of my Pro1 X screen due to drop damage. Fortunately, it doesn't block any important parts of the screen just yet, but it's slowly getting bigger over time. Yesterday I ordered what is apparently a replacement screen and digitizer for the Elephone U Pro from this Amazon link. Once it arrives, I'll test it with the Pro1 X directly, though I assume it'll need to be reflashed like all the others. Is anyone still offering this service? I live in the US, which might make things tough, but I'm willing to cover any shipping and import fee

I recently successfully updated my Pro1 X to LineageOS 23, starting on 2025-12-08 nightly. When I updated, I installed Magisk as a zip after flashing the image. Today I successfully updated to 2025-12-15 nightly using OTA. After installing the OTA update, I always re-install Magisk to the inactive slot before rebooting. Is that still necessary to maintain root?

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

I may try it one of these days

Sorry, I don't use / have android auto.

I think we are very few users left here, so would be pure luck if some with the same problem spotted your post...

...but question is still I am only one with this problem with Android Auto?

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

Oh - nono...it will be too much work for me 🙂 Maybe more simple way will be downgrade AA to latest working 14.x.x version.

Have you tried going back to 22.1? I would not be surprised if there are more regressions with 22.2...

Hi all 🙂 I have problem on my pro1 with Android auto and i want to know , if is it problem only with my device or on all. Display on car stereo is like pulsing and blurring. It was tested on 3 (vw and toyota)cars and on all is it same. I am now on latest LOS and android auto version 15.8.15404. Tested on wireless and cable connection.

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

My first idea was to start with pro1x kernel 4.19, maybe the compiled proprietary blobs are the same or mostly the same as pro1. But I never found a 4.19 kernel built for msm8998... Maybe one of the guru of the company can help us with the driver sources? unless @EskeRahn is correct and the sources were part of the swindle, though.

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

The base kernel source is of course available as per the GPL2. Also, e.g., the keyboard-driver source is available as part of LineageOS. However, much of the device drivers that make up basic mobile-phone functionality are not. The project of mainlining the Pro1 got stuck on such profane things like the touchscreen driver requiring some non-disclosed firmware magic to be usable in the first place. Device drivers not being open-sourced is pretty standard in the Android world, though. Nothing specific to the Pro1 here. 👎

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?