Leaderboard

It is highly advised to take a backup of your device specific partitions right after you receive the device. Update 20220829: tl:dr: Community has not found a safe way to restore backups as of yet. Making below described backups is still highly advised for a future where some wizard found a reliable way to restore those backups. For now, if you have broken sensors from flashing another OS, the restorecon method described in the "Repair sensors/ folder..." section does 100% work to fix those while retaining your attestation keys. While restoring any backup has a high chance to make the keys

Okay, I've successfully backed up my persist partition using the linked tool. The edl tool produced a number of error-looking things on its output, but they seem to be non-fatal, and I eventually got... Reading from physical partition 0, sector 8, sectors 8192 Progress: |██████████████████████████████████████████████████| 100.0% Read (Sector 0x2000 of 0x2000, ) 33.83 MB/s Dumped sector 8 with sector count 8192 as persist_backup.img. ...which produced a 32 MB file containing an ext4 filesystem, the contents of which do appear to be the correct things. A tip for anyone who has alrea

Okay! Got Debian Sid up and running in lxc, by fumbling my way through @matf's guide. It works! 😄

I think the point was that, given the delay (which wouldn't have been free even without the SoC/etc. changes, and I'm sure it wasn't through choice), if money had been invested in developing the software then there's a significant risk they'd of ended up with somewhat incomplete software for somewhat incomplete hardware - ie. nothing deliverable to anyone. They've decided to prioritise the hardware. At least people are getting something for their money, even if at the moment it might not be exactly what we were expecting/lacking in some regards. If you don't like what you've got (r

Sure there is. Money. As @EskeRahn pointed out, what is said on the Indegogo pages should be changed. But all of this goes back to what keeps being referred to, appropriately, as "the swindle." The Pro1x was created to be a limited edition Pro1 with a blue case and an option for more memory. Lineage was already available and UT was close. They had secured and paid for the SD835 SOCs they were going to need. Then, they were informed that the supplier, who had been paid, was not going to give them the chips and, as an older chip, they couldn't find another supplier. So now, along with

I can not guarantee that above is already final since i feel a bit like a lonely tester on this. It worked for me. But no one is around me to save me from jumping to wrong conclusions and build on them 😅

I am writing instructions for a complete backup thread just now. Copying the data folder from the backup to the stock persist did not work. What worked for me however is to copy the sensors folder from the stock partition to the backup persist. EDIT:

Are you asking why they do not pay for being swindled? What we paid for for was supposed to be hardware usable with the software for the Pro1. Perhaps with minor improvements. As hook already explained they were swindled and did not get the chips they paid for, and could not get them anywhere else. So was thus unable to deliver anything compatible with that software. So you then see it as their responsibility to develop software for a different chipset? I repeat my self: Pre-orders could get refunds if they wanted. Crowdfunded IGG Perks were lucky we got anything at all !!! SURE I t

It's actually 32 MB. But it does compress very well, since it's mostly empty space, down to 177 kB with gzip. 🙂

As other have already said, The pro1X was INTENDED to be a Pro1 with very minor adjustments, and additional roms available in collaboration with XDA. And yes it would have caused less confusion if they after they were swindled had also decided to call it e.g. Pro2. And I agree that the text ought to be changed, e.g. With the Pro1 X you have the flexibility with the unlocked bootloader enabling you to loadother popular OS’s such as Lineage and Ubuntu Touch. to With the Pro1 X you have the flexibility with the unlocked bootloader enabling you to loadother popular OS’s such

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

Excellent. Thanks. Windows? What's that? 😂

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.

boot_a vs boot_b is the easy part. The hard part is creating two separate userdatas, and is alas somewhat more complicated than a mere "set_active". I'm looking forward to multiboot as well. I'd like to use Sailfish as my almost-fulltime OS, with the ability to boot into Android for occasional must-have Android-only apps (e.g. banking).

Unfortunately, they had no option but to build a new phone (basically mainboard then related things) from scratch or manufacture no phone at all. I don't know what they did but I think alternative OSes will come up, especially if F(x)tec may continue to supply Pro1-X for a while. As of Pro1, it took for a while for these OS supports come up but finally they became available, Pro1-X is still young in this relation.

Problem is, the Pro¹X they wanted to build actually was a Pro¹ — just with more flash storage (optionally), a blue casing and some of the already existing alternative ROMs preloaded, possibly after helping to make them more stable in case of Sailfish and Ubuntu Touch. But then they didn't get the SoCs anymore, even though, as I understand, the SoCs were paid for and promised. And as that SoC was already out of production at that point, they couldn't get it anywhere else, either. So they made a complete redesign for a current SoC. Which, unfortunately, loses compatibility with existing RO

@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

Hi community, Does anyone know if the ew Pro1X's Screen and Body Parts compatible with the old Pro1? Parts are scarce these days.

For what it's worth, Key Attestation" on my Pro1 with Lineage and Magisk shows "Not supported by this device." Not a big surprise. It has had Lineage or AICP on it since early 2020 and I've never gone back to Stock, so of course I've never noticed. It will likely be the same with my Pro1x. I will probably keep it on stock until Lineage is available. I plan on using my Pro1 as my experimental device (read that learning device). If I find a setup I really like and is stable on the Pro1, then I will try to bring it to the Pro1x. I will see if I can backup the persist partition when I get

Thank you for this thread (i added a link here)

Guys, this is all incredibly hard to follow. I don't plan to flash custom ROMs until F(x)tec says that they're ready, so I hope that they release good instructions by that point. But in the meantime, do the backup instructions outlined above have anything to do with the backup instructions found here? And what is the difference between Google Mobile Services and Google Play Services, anyway? I know about the limitations of using a device without the latter, but not the former.

I'm going to try that later as well. Thanks for the tip.

Interesting... Even without seeing the videos I just do it easily... I do either the lift behind then push open or push slightly down and slide to get it open. (I'm still eager to get a propr OS in this thing and start playing with it!!!)

That is fantastic news that I must have missed. Thank you for pointing that out. Really, that is all I was asking for. That fxtec didn't expect other unaffiliated developers to work for free to fulfil a company's promises.

Good news. It has been done. I am not at a computer currently but essentially what people in the Pro¹ Telegram group did is to copy the whole Data folder from the persist backup to the stock persist image. Will be able to test later today.

For me it started working again after I did "fastboot flash persist persist.img" (using the persist.img from the Archive posted above) (Edit: Don't try at home, it might do more harm than good. See the thread about landscape mode). I've read that does not restore all functionality, but on my Pro1X everything seems to work fine for now (i.e. Screen rotation, keyboard backlight etc. are back).

Oh alright my bad then 😅 Haven't played with Android in a while

I'm not arguing against your position that you didn't get what you paid for. You do have a valid complaint, and as someone who wants to see solid non-Android options on the Pro1-X, I do hope the situation gets resolved. I just think that if the hardware is ready, but the alternative software is not, then it's better to get the hardware in the hands of the users, rather than shelve it all and make everybody wait.

So now at least three of us have this issue . . . I had to look up clipping. How could that be the cause if it sometimes works more or less OK with the volume up? I wish that there was a way to just disable the bottom speaker. I've been getting by just fine without stereo on my KEY².

So, I'm in the same boat. I've flashed a recent UT build, didn't work. Then I reset by following these instructions to restore to a booting phone, and to try out SailfishOS instead. On Sailfish, everything seemed to work, apart from the lock screen rotation when flipping out the keyboard bit. Normal rotation worked fine based on the gyroscope, so I didn't really think much of it other than "early community build". After deciding the software ecosystem on SFOS is a bit spartan, I decided to hold out for a more mature, working Ubuntu Touch build for the phone, but go back to Android in

Thanks for the tip! Is this the keyboard that you're talking about? https://anysoftkeyboard.github.io/ I haven't tried mobile data yet. Given all the other problems, I wasn't about to pop my SIM card over.

Yup - recognised on Linux after udev rules amended. Leaving this thread...

Indeed. I struggled with the Pro1 initially, especially holding it in portrait in the left hand (for operating with the right), But as I almost immediately started using shells, and then flip-cases, the problem disappeared. But without a case it is as aPple would put it: "You are holding it wrong" *LOL* It will simply take a while to getting used to a grip avoiding inadvertently touching the fingerprint-reader. I'm pretty sure that if you delete all you fingerprints (Setting►Security►Fingerprint) it will effectively be disabled. The slick design where the fingerprint-reader is almo

You have to try pretty hard to significant scratch Gorilla Glass. I've not used any kind of screen protector on the previous few Samsung Galaxy models I've owned and after several years of use, there's nothing more than surface scratches. I'm of the opinion that screen protectors do little more than reduce the sensitive and usability of the touch screen.

Looks good to me, from what I understand on the subject.

See this post, unfortunately probably too late. Hopefully someone else knows how to fix that problem without a persist backup.

And you still have that option. I also want something other than "full Google" on my device, but I do understand the decision to go ahead and ship rather than shelve their own completed hardware and wait for the software to catch up. I do agree with you that they should update the website so that it isn't promising unavailable software. The headline video on the website in fact is chock-a-block with praise about how great the LineageOS experience will be. Someday! 🙃

No - it makes weird popping noises, and when I set the audio really loud (like a YT video, put the volume to the max) it works, pretty much. It's weird. I've managed to power off and power on my phone (not restart) and the effect was gone - ONCE. Worked for a while, then after some time (I can't tell what have I been doing exactly) it started behaving like this again.

Mine arrived today (Australia). The blue colour looks pretty nice to me. 👍

I will highly recommend NOT omitting this tiny step. Remember that an OTA update swaps what is active between A/B so could easily become a mess Alternatively flash the boot image to booth boot_a and boot_b, so it is in whatever is active.

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.

But is it blue? 😁 By "notification diode", do you mean the general notification LED on the front of the device? There is one, RGB, upper right corner.

Received today. No duty/tax payable (Australia). We must have a free trade agreement.

I hear what you're saying, but I think that most users buy a phone as a means to communicate with others while on the go. A physical keyboard makes it easier for me to write paragraphs just as I like them. And it's not like you can't write sequences with normal smartphone physical keyboard behavior. It's not too hard to just rapidly tap a key. That even gives you more control over exactly how many <'s you need. You can also make good use of copy and paste.

That seems to have been the problem, then. It's odd that it would enable caps with two presses of the [Shift] key seconds apart. Still, it's much worse to not have sticky shift at all!

Ah, that makes sense. The last paragraph on my previous post suggests that you need to hold three keys down simultaneously, but you don't actually have to hold down a yellow [↗] key. Still, the fact that the [Alt] key isn't sticky either makes typing accents and the like a pain. This especially true in Spanish, which uses tons of acute accents. The [Alt] key and the [E] key are right on top of each other on the left side of the keyboard, so holding them down at the same time isn't easy and certainly wasn't designed for thumb typing. And there isn't a Spanish keyboard on that website for a work

This is intended as a central entry point with links to known ROMs for the PRO1/PRO1X. You will need android adb / fastboot tools that officially can be found here (Windows / Linux / mAc) Important step BEFORE changing from Android initially!! If you want to ever be able to change the phone back to the state it had when you received it with stock Android, there is an important step that is needed before flashing any non android-based ROM, That is to backup the persist partition. If the device is unlocked and a recovery boot is present a fairly simple partition backup method (fo

Screen is disconnecting from its connector. Which one? I don't know. Unplug, brush both plugs and sockets very gently with fiberglass brush, reassemble. Pins just oxidized, had the same issue and also very bad LTE signal, brushing connectors helped a lot.

The real challenge is to open it silently i.e. in bed room while your partner sleeps ☺️

And here one where I on the contrary LIFTS the front, by rolling in the finger YouCut_20191223_192100210.mp4 And as a third method you can of course just lift the back edge up. Or you can also do a combo lifting the back while pushing the front. I most often lift with the right index after triggering the fingerprint scanner, while pushing with the left thumb.