phukfxtec

the context is irrelevant, I would feel the same if this were the only issue. to you its minor. to me its severe. now we enter subjectivity, so it's a fruitless debate. if this major cosmetic blemish was on a TV, it would be returned immediately.

This is irrelevant and absurd to suggest people just make their own phone. Imagine hiring someone to do a job and they do it poorly, then when you question them on it they turn around a suggest you do a better job? That's not how it works. Actually I do have an idea for how it should be done, but I haven't the resources. Again, irrelevant. What is optimal is not even the issue. Having defects in an $800 device is the issue. Once again, this defect would not be acceptable on any display, from any manufacturer. I don't care how small or big the company is. They can

So because of the other issues this is "appropriate"? No. This defect is inappropriate on an $800+ device. I would still want a replacement even it this was the only issue. Maybe you understand that the screen is the thing you focus on while using the device. So yeah... I am focused on it, in addition to the countless other issues... That would be even worse as the rounds are already cutting off text in the terminal, and also cuts part of the AM/PM in the status bar time. Rounded corners are bad design in the first place, the solution is not to cut off even more pixels and

@claude0001 thanks. I eventually ended up compiling from source then manually flashing via fastboot. Finally in Ubuntu! The documentation / process needs updating. Newer builds. Better device detection. This is not user a friendly process for those unfamilar with the command line.

No, it absolutely is a defect. You can try to diminish it by calling it a "minor cosmetic blemish", but this type of issue would not be acceptable on any screen from any manufacturer. If you bought a new monitor or tv with dead pixels would you not return it/warranty it? If this defect was found on an iPhone, people would riot. Obviously fx is not apple, but that does not give them a pass on an $800+ device.

already tried installer. does not work:

which to download? i dont see artifacts. where is ota 5 build?

ubports installer stuck at "Fastboot is scanning for devices" device does show in > fastboot devices

glad you were able to recover your device. do you select manual? ubports says "QX1050 is not recognized" for me

where is this OTA 5 build? I see it listed on this page but no download: https://devices.ubuntu-touch.io/device/pro1x/ 20.04 - focal stable OTA-5 7/25/2024 Stability over newer features (recommended) is it in here? i dont see it: https://gitlab.com/ubports/porting/community-ports/android11/fxtec-pro1x/fxtec-pro1x/-/jobs

UBPorts Intaller tool says: "The device QX1050 is not supported" will try with fastboot method instead...

is the fastboot method still the recommeded way? because the https://devices.ubuntu-touch.io/device/pro1x/ page suggests using UBports installer.

never. we all start somewhere. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ I can't provide much better steps than what is already in the OP. I guess start here: backup persist. try adb method first. requires unlocked and a recovery boot if above doesn't work, install EDL (see readme and OP) edl r persist persist_backup.img edl r modemst2 modemst2_backup.img edl r modemst1 modemst1_backup.img edl r fsc fsc_backup.img edl r fsg fsg_backup.img flash your OS of choice:

try here:

new question: if flash linux, how to go back to android if can't restore backup? op make this note that there is no way to restore?

linux host and linux livedvd vm continue to give issue... unknown root cause. tried edl on different machine with windows. hit issue: "NotImplementedError: Operation not supported or unimplemented on this platform"....solution was to reinstall WinUSB driver in Zadig: https://github.com/bkerler/edl/issues/349#issuecomment-2060152724 backup successful.

That is where I started. It led me here. Where edl is failing to backup the persist partition.

one user suggests button combo instead of adb to get into edl: what is this "full" mode vs not full mode? I tried with buttons to no difference, still times out. are these guide's / tooling up to date? the information seems a little scattered between threads. is there any official documentation or official tooling from fx for flashing process and proper backing up procedure? please advise as I do not wish to brick my device. it appears it is easy to do so: https://community.fxtec.com/topic/4022-pro1x-is-bricked-is-there-any-way-to-save-it/?do=findComment&comment=6

found --debugmode flag. appears to be timing out: user@livedvd:/opt/edl$ python edl r persist persist_back.img --debugmode Qualcomm Sahara / Firehose Client V3.60 (c) B.Kerler 2018-2022. loader_utils loader_utils - [LIB]: 'str' object has no attribute 'append' loader_utils loader_utils - [LIB]: 'str' object has no attribute 'append' loader_utils loader_utils - [LIB]: invalid literal for int() with base 16: 'prog' loader_utils loader_utils - [LIB]: 'str' object has no attribute 'append' loader_utils loader_utils - [LIB]: invalid literal for int() with base 16: 'prog' loader_utils loader_uti

attempt #2: re_livedvdV4.iso load .iso into vm boot into edl on device. edl is freeze after Device detected? edl r persist persist_backup.img Qualcomm Sahara / Firehose Client V3.60 (c) B.Kerler 2018-2022. main - Trying with no loader given ... main - Waiting for the device main - Device detected :) then wait forever. I tried to look with printgpt: edl printgpt Qualcomm Sahara / Firehose Client V3.60 (c) B.Kerler 2018-2022. main - Trying with no loader given ... main - Waiting for the device main - Device detected :) It also freeze forever.

the setup.py step of installing edl: sudo python setup.py install fails with: src/pylzma/pylzma.c: In function ‘PyInit_pylzma’: src/pylzma/pylzma.c:296:5: warning: ‘PyEval_InitThreads’ is deprecated [-Wdeprecated-declarations] 296 | PyEval_InitThreads(); | ^~~~~~~~~~~~~~~~~~ In file included from /usr/include/python3.12/Python.h:95, from src/pylzma/pylzma.c:26: /usr/include/python3.12/ceval.h:132:37: note: declared here 132 | Py_DEPRECATED(3.9) PyAPI_FUNC(void) PyEval_InitThreads(void); | ^~~~~~~~~~~~~~~~~~

update: rubber band worked. ordered lineage, but it came with regular android. that is a non-issue as I prefer to wipe and flash myself. I have artifacts in screen corners:

i did not expect it to show up. somehow, it did... box open as expected, battery dead as expected. rubber band is currently rubber banding. will report back when I know it actually turns on...

It's been a month now since their 3/4 claim. Has anyone got their email for confirming address?

Well it's more profitable to sell them behind our backs instead of deliver them of course... Where was this 'pre-order bonus' mentioned? I don't want/need them, but I want to verify these were promised at some point in the campaign.