![](https://community.fxtec.com/uploads/set_resources_1/84c1e40ea0e759e3f1505eb1788ddf3c_pattern.png)
phukfxtec
Members-
Content Count
35 -
Joined
-
Last visited
Everything posted by phukfxtec
-
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); | ^~~~~~~~~~~~~~~~~~
-
Pro¹ X – state of production and delivery
phukfxtec replied to Rob. S.'s topic in Pro1 - Thoughts & questions
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: -
Pro¹ X – state of production and delivery
phukfxtec replied to Rob. S.'s topic in Pro1 - Thoughts & questions
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... -
Pro¹ X – state of production and delivery
phukfxtec replied to Rob. S.'s topic in Pro1 - Thoughts & questions
It's been a month now since their 3/4 claim. Has anyone got their email for confirming address? -
Pro¹ X – state of production and delivery
phukfxtec replied to Rob. S.'s topic in Pro1 - Thoughts & questions
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. -
Pro¹ X – state of production and delivery
phukfxtec replied to Rob. S.'s topic in Pro1 - Thoughts & questions
The fact that they wont even put out a simple statement saying "hey we're confirming addresses" on their page or they cant even do the bare minimum of log in to respond to this forum. Like is there anyone even working there anymore? -
Pro¹ X – state of production and delivery
phukfxtec replied to Rob. S.'s topic in Pro1 - Thoughts & questions
The next two weeks huh, yet not a single device has shipped since because now your "waiting for 50%"... well which is it liars? -
Pro¹ X – state of production and delivery
phukfxtec replied to Rob. S.'s topic in Pro1 - Thoughts & questions
How can this be this true? They've done nothing for 5 months and just waiting for 50%? endless lies... this is truly absurd at this point. Just start shipping what you can, my address has not changed, this is bs. JUST SHIP MY FUCKING PHONE ALREADY. -
Pro¹ X – state of production and delivery
phukfxtec replied to Rob. S.'s topic in Pro1 - Thoughts & questions
well thats sad.... It is only because of XDA that I felt comfortable backing in the first place. fxtrash still list the SD835 on their sales page, despite being called out multiple times by multiple people. literally false advertising -> illegal -
Pro¹ X – state of production and delivery
phukfxtec replied to Rob. S.'s topic in Pro1 - Thoughts & questions
wut... you want to give the scammers more money? 5 months now since their last update. they don't even respond to this forum anymore. Casey is absent for like 6 months. It's clearly not a shipping issue at this point... I truly don't understand how some people are still defending fxtrash after years of bs. I wouldn't be surprised if this forum silently disappears one night to save on server costs. This forum is basically nothing but bad PR filled with complaints. Even if this it shows up it will maybe barely work for a couple years. There's no way this will h -
Pro¹ X – state of production and delivery
phukfxtec replied to Rob. S.'s topic in Pro1 - Thoughts & questions
+1 for k9 mail and f-droid! thunderbird for email if on desktop. LibreWolf or Mulvad over stock Firefox as FF has too much telemetry and crap (Pocket) and relies on google. Brave or ungoogled-chromium if you prefer chrome. but never stock chrome. -
Pro¹ X – state of production and delivery
phukfxtec replied to Rob. S.'s topic in Pro1 - Thoughts & questions
Since fxtec has decided to no longer provide updates, I took the liberty of producing an update on their behalf: Disclaimer: this is a joke for those those who can't read in comic sans... -
Pro¹ X – state of production and delivery
phukfxtec replied to Rob. S.'s topic in Pro1 - Thoughts & questions
From the Sept update: "We would like to begin by apologising for not providing an update for July and August." So your way of apologizing is to not provide a monthly update again?