Leaderboard

I can attest that a Pi4 works flawlessly so far for flashing for me. Just had to do: sudo apt-get install -y android-tools-adb android-tools-fastboot to install the tools needed.

Believe it or not, this is how we used to create OS distributions back-in-the-day. Fattire even wrote a short poem about it: So Many Zeroes! A Children's Book By Dr. Seuss (a.k.a. fattire) Blue had his V2, all shiny and GNU, and wanted to send it, but stopped to review. "What would this ware weigh, if zipped up today? Should it not be much larger than the SDK?" And yet it was bigger (nearly one-half a gigger!), but Blue still released it with vim and with vigor. "A drive is a drive, at any old size! But a drive is alive when its zero'ed to thrive!" So Blue packered his tracks with a /

Thanks for testing the Pi4 in this respect. I do not have any of these and always worried its USB-3.0 parts might behave differently when compared to the older models' USB-2.0. Good to know this is not the case. I'm not sure which OS you use on your RPi, but since 'buster' the respective Debian packages are just called "adb" and "fastboot". I.e. in recent Raspberry Pi OS, one would rather do sudo apt install adb fastboot

I have always only used "B" models, which come with 4 USB ports and Ethernet in addition to WiFi. This of course doesn't mean that the A+ will not work for your purpose ...

I have an X250 and could never use fastboot from it (original Pro1, Linux also here). Probably ... There all kinds of tips and tricks (use external hubs, remove unnecessary devices from the bus, ...) but it all feels a bit like doing a rain-dance and tossing salt over your shoulder ... All I can say is: Since I have set up adb/fastboot on that Raspi3 (others have reported RPi4 will also work inspite of different USB HW), I have never looked back.

fastboot is way more picky about the USB connection than adb. If @Casey's suggestions do not help: Various RaspberryPi's have been 100% reliable for me when it comes to flashing Pro1(X) -- I've never again used adb/fastboot from my PCs since I found that solution.

I also couldn't get it to work and gave up. Same timeout errors as you. I just rooted the phone with Magisk and used the following command to backup all the partitions to the sdcard: mkdir /sdcard/backup cd /dev/block/platform/soc/*/by-name for filename in *; do if [ "$filename" != "userdata" ]; then echo "dd if=$filename of=/sdcard/backup/$filename.dd"; fi; done This prints lines with the dd syntax to back up all partitions. It does not execute them for you. Please check if those lines fit your expectations first and then run one or all of them. I then got the backups off the

@Noob : click sound, yes. I would say no mecanic problem here. I glue one touch with cyanocrylate a few months ago as he felt, and had no issue since. I test with three press on different touch like 'aaa eee ddd ccc sss ooo mmm....' and see what happens, then I found this : when pressing the bottom part of the keyboard the bug disappeard. As far as I understand @veRYANgry solve the problem with tightening the two bottom screws, wich could be related to my problem.

Some of the modifier keys are mapped a little differently from stock, but the driver is still the same one as F(x)tec ships. The most important differences are the 'F logo' key is mapped to META, and the SYM key is mapped to AltGr (ralt). The old behavior of the 'F logo' key (KEY_HOMEPAGE) has consequently moved to 'F logo' + ENTER, but you can now use any of the other keyboard shortcuts built into Android. This list is contextual, and 'F logo' + '/' will bring up the list of shortcuts defined by the current app. FWIW, this is the same mapping as LineageOS uses on the Pro1. Among other mi

Definitely F(x)tec is NOT scamming us. They are just struggling with this project and things have not gone as they planned (SoC change etc). Sure, F(x)tec has done mistakes during the journey but I think that they are trying very hard with limited resources. I received my Pro1 after long wait and during this week I am supposed to receive Pro1-X. Let's see how it works compared to Pro1.

Yet another way how to backup persist (or any other) partition even without PC, with rooted phone and Magisk: Install Magisk module "backup" and reboot. After that using some terminal app in phone (I use Termux), first gain root access: su and then enter backup persist it will create file persist.img in folder /backup of your phone's internal storage. The path can be changed of course. I suppose same can be achieved with dd command, but the above is easier. Instead of terminal app in the phone you can of course use adb shell from a pc.