mosen

If you did not overwrite the persist partition, this could be recoverable. More competent people than me are currently looking into how to fix just the sensors in backuped persist images. You can check if your keys still exist, for instance with the "Key Attestation" app from playstore. It shows "Not supported by this device" when no keys are present. Any other view in that app is fine. And it does not really help to state, but the Hardware Key Attestation is very rarely used by any apps currently. On the Pro¹ X i lost the keys on, SafteyNet still works when locking the bootloade

@Caseyis working on QFIL instruction which will be the official way to reflash to stock. The EDL method using EDL.py from BKerler is not perfectly easy to set up but used by the testers since the testing devices went out in may. Generally, the provided EDL image contains .xml files that more exactly define what to do with the images than fastboot could do. In our case the EDL images do not wipe/overwrite the persist partition. Meaning that there is no harm for the keys. But also its not the fix for the OT problem here. I borked my keys by flashing the stock persist image which only go

Yes, its fine. The sensors getting "lost" is due to UT and sfos altering the persist partition afaiu. The keys are not touched in that process. Only when attempting to fix the sensors for stock android by flashing the wrong persist.img, the keys get lost since the stock persist image only contains the correct sensor settings. But not the keys. Flashing your own backup with keys and stock sensor config is what ultimately fixes the problem correctly. Also the EDL flash does not touch your keys (but not fix sensor too) unless you falsely use the contianed .xml.bak to flash which complete

https://github.com/bkerler/edl Its dubbed edl.py colloquial. You can also achieve the backup using the official Qualcomm QFIL software on wondows. But i have no experience with that. Looking into the adb option today.

Yeah, i am getting it hard today... I did use the edl command and just copied the fastboot command from XDA without testing... There must be a way using adb. But i am to tired to get that right now. Sorry for the confusion.

@matf Please add this warning to your first post. Users should backup their persist partition as early as possible. 1. Attestation data in persist partition is unique to the device unit, therefore backup of persist is strongly recommended to people attempting to flash a custom OS. 2. The consequences of losing this data currently don't seem too critical, as the standard attestation checks like SafetyNet are passed on such devices. But they won't pass rarely used hardware attestation checks. 3. Warning, the rawprogram0.xml.bak from the EDL package will flash your persist partition with t

Agreed, disclaimer, i was just curious and can not fully oversee the implications. Checking the device with fastboot getvar all revealed slot_a to be active "anyway". So i was curious to try what happens without the set active command. Note, the original ubuntu instructions even had a set active a before the boot image flash. Which is already omitted in the first posts instructions.

Same hw config but i got the blue IGG model. They should be 100% the same, just different casings. I flashed sfos as first action after unboxing. Maybe you changed something to the stock settings the Pro¹ X got delivered with? If you are not keen to debug the issue, i'd just reflash to the 2.1.2 build factory image using EDL/QFIL to have the device in unboxing state again. Like described in this thread:

Re: First post: I successfully flashed, omitting the set active command. All i did after receiving the Pro¹ X with Android built 2.1.2 was: 1) Download Ubuntu Touch image and extract the boot.img From this build (2830649718 artifact.zip) 2) Download the SailfishOS 4.4.0.64 devel build and extract the userdata.simg From here (2807435728 artifact.zip) 3) Execute fastboot flash commands fastboot flash boot_a boot.img fastboot flash userdata userdata.simg Happy sailing! Hope this wrap up helps someone.

F(x)tec will release flashing instruction using Qulcomms QFIL software on windows soon. The unofficial method to flash the provided EDL images that testers used on linux would be: Install EDL-Tool by bkerler https://github.com/bkerler/edl Put Pro¹ X in EDL mode using adb reboot edl when you got adb available. Else, Pro¹-X needs to be put in EDL mode manually. Hold power and vol + and vol - During boot and release all after android logo flashes up shortly and goes into a dark screen second. If it stays dark after you removed the combo, Prawn is in EDL mode.

Your optimism is inspiring! Thanks for being and staying cool 😄 Also i ordered an X as soon as it was available since i share the bad conscience OSwaldo mentioned above from being lucky and receiving the Pro¹ early. Now want to support others that did not even receive that by making sure F(x) has some cash flow. Plus the outlook to finally have a spare not-daily-driver Pro¹ to test out all those yummy OS that have been adapted in the meanwhile. Imo the March delivery commitment has some safety margin already calculate in. Last time Chinese New Year was a delay reason and it looks to me t

Sir, you asked in the discord and we created a buy+sell channel right after your request 😄 There is a never unboxed QWERTZ version up from a trusted member i personally met for 800€ if you did not see. Or did you see and what you are looking for is QWERTY version?

The work around for the fingerprint seems to be to register those parts of your palm that usually trigger the reader in error. I did the following, activate FP registration and do those task that trigger the reader. Like lay it on the table and pick it up and lay it down until this action is registered as FP1. Then move to FP2 and eg pull the pro¹ from your pocket multiple times until FP2 is registered. I did this with 5 actions and the result was the pro¹ unlocked as soon as i picked it up.

Did you not find the screen protector hidden in the manual?? It is very good quality imo.

No fear, you are even still in the given delivery timeframe of 4-6 weeks. But to already prepare you, it is not likely you will receive your Pro¹ before end of February (hopefully during march) since the devices produced pre chinese new year have been sent out and new ones are only produced starting from this week. There have been delays even in the month since you ordered sadly. And prepare for (friendly) laughter from other members triggered by your attitude. You are literally complaining amongst folk that waited for the original moto-mod since Feb 2017. Personally i was lucky and at

To give hope, we had a user on discord with a prominent pink line over the display. He got sent a new display unit with in ~2weeks. It was straight forward to change with only the screws to remove on the backside of the display.

Pro¹ is the lightest phone with hardware keyboard (German) https://benedikt.io/2020/01/fxtec-pro1-leichtestes-android-smartphone-hardware-tastatur/

Today i got the headphones accompanying my very early delivery from November. I am very satisfied with the build quality. The cables are soft but sturdy enough to not knot easily. There is no plastic smell, all components feel worthy. Compared to quiet neutral Sennheiser, the the mids and bass are nicely emphasized. No distortion in the heights even at unbearable 100%. They sit very comfy and yet tight. My expectations are met, Thank you at F(x)tec.

Yes, it is recommended to update the Pro¹ to 3.2.1.20 after flashing. Craigs commands are correct, thwy need to be executed with root permission. `devel-su` in Sailfish.

The good news from this thread seems to be the confirmation the Pro¹ being easily serviceable. Kudos to you taking the right action and let a professional solve this correctly. Was that a 3rd party repair shop not related to F(x)tec even or did they recommend to you where to go?

Just to complete with a follow up, the error was rooted in using USB 3.0 Port. As soon as @Astaoth used a USB 2.0 Port via a docking station, the flashing process worked as expected

Since Pro¹ is 73,6mm wide i can safely say i got the 62-77mm variant. Most likely mine is an old model of 511307. But since 711042 starts at min 70mm it should also fit, right.

The universal holder from Brodit does the job. Sorry, no idea about measurements and order number, it is like 6 years old. But i just needed to widen this universal holder to max after using it for XA2 which was more narrow. The thickness is exactly matching the cutout space so the pro¹ sits very tight. https://twitter.com/eLtMosen/status/1197074326245257216 Oh, and cheers form an Audi 80 [B4] owner for ~10years 😄 Now i upgraded to this nice [W639] Vito with just 260tKm.

No fear. So far community members have perfectly helped each other in configuring and afaik everyone solved eventual starting issues. I had perfectly mapped QWERTZ on Android thanks to community members explaining FinQwerty use to me. Now that i run Sailfish i try to give back and have propsed a mapping for SFOS QWERTZ. Just ask here or in the unofficial Discord for more chattier help!