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.

Two Pro1-X issues, possibly related. First, the built-in microphone gain is extremely low. it makes my spouse completely inaudible during calls and only barely audible using a sound recording app. When we attach a wired headset, the microphone gain is fine. Second, and this one is really weird, when we're making a call using the build-in mic and earpiece, we can hear the other party just fine _until_ we try to say anything, at which point the incoming sound cuts out completely for anywhere from a fraction of a second to multiple seconds. I assume this is some kind of feedback avoidan

I found a way to backup partitions that also works for windows, with just the usual ADB on the PC. HOWEVER this ONLY works for an unlocked device. ADD: The below only works on Linieage/AICP not stock android, see also this If not unlocked - unlock wiping data, or look for another method.... Make sure that your phone is in developer mode [*], and allows adb to connect as root (the phone does NOT need to be rooted) Connect cable and run (first time you must accept the connection from the pc) adb root adb shell find /dev/block/platform -name "by-name" -exec ls -al {}

We're experiencing this too! For what it's worth, Firefox is not affected. Does anyone know why this happens? We don't particularly want to disable the fingerprint sensor.

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)

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

I usually say that it is a bit like riding a bike. Hard to explain, hard to do at first, and when your body learned it, you can not understand how it was hard in the first place. But a simple way to open is to lift the back edge of the display, rather than pushing the front edge 'downish'. With a little exercise , this can be combined with touhching the fingerprint reader, thus doing all in one motion.

There were interviews. I also remember finding a court case online with f(x)tec as the plaintiff with some company as the defender. I tried to find it again since you asked but the link I had no longer works and I wasn't smart enough to keep the Chinese pdf document. I can only tell that there was (dunno if it wasn't erased) a court procedure and... That's it for outside f(x)tec control.

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.

Now let us get things straight.... Those that pre-ordered from FxTec could cancel until the unit was actually sent. (and in some countries even have the rights to regret and send it back within some timeframe typically a fortnight) If they cho(o)se not, it was/is their own choice!!! Those of us that took the risk of crowdfunding taking a Perk on IGG for one should (as @Hook pointed out above) actually fell lucky that they just did not fold, and told us our money were lost, but are sending something pretty close to what we hoped for hardware wise. Remember that the alternative is no

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.

Sucks 😞 I made a backup of my persist partition and I notice they're just ext4 partitions. I guess copying the right files from one to the other would resolve it. I wonder what happens when you flash the same keys to multiple devices? 🤔

I installed Key Attestation and it shows "Security level: TrustedEnvironment"

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

@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

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

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.

From what others wrote, out-of-the-box, the Pro1X is not configured for charging in powered-off state (was the same for the Pro1). So keeping it connected to the charger will not fix anything if the battery is completely depleted. The phone should ship with a half-charged battery and ready for action. I think you should contact support.

I received an email in advance notifying me that FedEx had paid the custom charge to avoid any delay and I simply paid online.

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.

I don't, and at the moment I'm playing around with Sailfish, so I can't go looking. It should certainly light up, even in default configuration, when you plug in a USB cable to charge.

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.

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

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.

I tried to make some four times slo-motion videos a while ago. of two different ways to open by pushing They are far from perfect, but perhaps you can see what is going on better slowed down. First the classic push slightly down, where the back lifts as you push a bit downwards (that is what you see above in full speed) Note the important detail that my thumb is NOT continuously pushing in the same direction, but follow the screen edge down and then up. YouCut_20191223_174454298.mp4