jsreed5

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

An update to this. My replacement Elephone U Pro screen arrived yesterday, but I didn't have a chance to install it until today. The screen is clearly secondhand; there was exposed, dirty adhesive on the back, and the plastic scratch protector on the front is also scuffed. The screen itself is largely undamaged. It came with several tools to help with replacement, including spudgers, adhesive strips, and two small screwdrivers (one Phillips and one flat). The display frame was very easy to remove per F(x)tec's instructional video. It was a little more difficult to remove the screen from t

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

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

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.

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?

Thank you, this is exactly what I needed! I didn't realize I had to tap into the "English (US)" option to get different keyboard layouts.

I have updated my Pro1 X to official LineageOS 21 with root. My only problem with the update is that my keyboard mapping seems to have changed slightly. On LOS 20, my key mappings matched what was printed on the physical keys. Now they more closely match a standard en-US keyboard: I get a semicolon (;) where the key says question mark (?), I get a question mark where the key says pipe (|), and I cannot get a pipe at all. This severely limits the functionality of terminal emulators such as Termux, which I use regularly. Does anyone know of a fix for this issue?

My Pro1 X just arrived about half an hour ago. Luckily, my device doesn't have a depleted battery, but it came out of the box at around 10 to 15 percent. I'm guessing some units were close to dying when F(x)tec checked them, and they fully ran out during transit.

It's finally happening! Just got a notification from IGG that my perk has shipped, with a USPS tracking number (I'm in the United States).

I've moved to a new address between the last update and now. When I saw the most recent update, I sent a e-mail to F(x)tec asking if I could have my shipping address changed. Interestingly, they responded and changed the address very quickly, and I even got a message from Indiegogo that the shipping address on my order was updated. I mention this because I've heard people on IGG claim that they couldn't change their shipping addresses with F(x)tec. The fact that I could do it quickly feels like an indication--albeit a small one--that they genuinely are hopeful things will work out this time.

That's good news for me; it's the exact model I ordered. The bad news? My ID is 1874. No dice on this allotment. It does make me wonder, though: might I (and others who ordered that version) be prioritized in the next contributor batch as well?

I ordered via the IGG campaign (#1874) and purchased the pre-early bird 256 GB perk, with a QWERTY keyboard, no engraving, and switched from LineageOS to Android. I am located in the US. It appears some orders from batch 1 are arriving in the US now. I haven't inquired as to what batch my order is in, but I have not yet received a shipping notification, so I assume mine is not in batch 1. That being said, the number of confirmed orders I'm seeing is rather small for a 707-unit batch. It's possible that my order is indeed in batch 1 and it's simply shipping slowly. If that's the case,

I believe there was a thread at one point where people would post their order number for the original Pro1, the country their order was shipping to, and when they got a shipping notification for the device. This allowed people to infer information about the order of shipping. Does that thread still exist? If so, we might start using it once we get notifications, or start posting such information here.