trahe

As i installed UBTouch the first time, i think Pro1x was recognized. After some messup i needed to manual select, indeed: (QX 1050/Bengal i had shown mostly)

i still did not figure out, so i am not sure if the e.g. phone works. (e.g. IMEI is not shown) So know we know, that the root of my problems was regarding to the corrupted persist but wifi and bluetooth works just fine... So the the keypoints for the fix: having some ~working~ persist i needed to the patched boot.img, which stops early and runs the telnet server, so i was able to format userdata into ext4

so with a lot of help and custom made images from TheKit, now i got it running. Basically the persist of mine was corrupt. Some other device persist.img flashed and it worked!

right something about the partitioning is my guess as well

No unfortunately it did not help. The backups i have are doubtful i guess... But there is one noticeable difference after running the UBports installer: the recovery starts with: Can't load Android System. Your data may be corrupt. If you continue to get this message, you may need to perofrma a factory data reset and erase all user data stored on this device. Try again Factory data reset So if i choose Factory data reset i get --Wiping data... Formatting /data E:format_volume: fs_type "auto" unsupported Data wipe failed

OK sure, and thanks for helping the edl backup procedure i logged, and for further information i as well included the output of fastboot getvar all the product is *bengal* the last flash attempt has had been UBTouch i can as well have Pro1x or QX1050, depending on which ROM to flash (stock rom / Lineage21 i tried to no bootable avail) As a sidenote, i as well tried to do the : Pro1-X: Flash Stock Firmware in fastbootd Mode from the "official" Gdocs, and as well installed the newest platform-tools, but fastboot create-logical-part

Well i did not do any backup, but started the UB Installer, so it seems i lost this partition

Thanks for your reply. Yes that is for sure i good sign. Anyhow whatever and however i flash onto it, the result is still a not usable device. I did not backup the original phone, as i did not intend to use anything but UBTouch. When booting into UBTOuch, it shows the Android logo, and once i was able, to telnet 192.168.2.15 dmesg: ... [ 4.648619] initrd: Halium rootfs is /dev/mapper/system_a [ 4.649234] initrd: mounting system rootfs at /halium-system [ 4.653391] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null) [ 4.655506] initrd: WARNIN

It is: I can boot into the ub recovery

I had the same issues, and did do all the steps as explained in: https://drive.google.com/drive/folders/1h0NqcNvkcX0nV5V3VVie4-smEm5ijW36 mentioned here. The result is still the same bricked phone, even so the QFIL process went flawlessly, but the reboot still leads to the bricked phone, this time not even having the recovery partition. (the Lineage and UBTouch recovery worked fine before) Fairly to say this is the worst experience i had got with any kind of hardware i purchased. Still have some old Motorola Atrix, for which i stil can use TWRP and flash it successfully with dif