Jump to content

agent008

Members
 View Profile  See their activity

  • Content Count

    240

  • Joined

  • Last visited

  • Days Won

    5

 Content Type 

Posts posted by agent008

    Pro1-X: Flashing Stock Android with QDL (for those with linux)

    in How Tos

    Posted · Edited by agent008

    I have flashed the Stock, with GMS, file several times and it worked successfully every time. This is a great tool and guide.

    However, Stock with GMS only leaves 8GB free storage in Android. Some of which is occupied by the GMS apps. I was surprised to see the "low storage" warning after a few hours of use and few apps installed!

    I am not sure about the non-GMS Stock, I did flash it but did not take note of storage space. If I'm not mistaken it's a reduced storage as well.

    Flashing LineageOS exposes 240GB of free storage. What gives? Has anybody faced this same issue?

    Pro¹ X - backup, restore and repair device specific partitions

    in How Tos

    Posted · Edited by agent008

    Yesterday when I wanted to switch from LineageOS 22.2 to 22.1, I foolishly performed a factory reset/data wipe on LineageOS22.2 Recovery before removing the Google account I had logged on to on 22.2 with MindTheGapps.

    Now, if I flash MindTheGapps, I cannot login to my google account on the phone -- it fails. I can use the phone if I flash an OS without GMS. But then I cannot st the PIN/screen-lock.

    I suppose something is amiss on the persist partition? I do have the backup which I took before logging in to Google.

    Is there still no trustworthy method for flashing the persist backup?

    Thanks

     

    EDIT: solved this by installing the factory, GMS backup via qdl (as in here, can also be done via QFIL); signing on to Google on the stock firmware; removing the Google account from the phone on Stock; then, flashing LineageOS.

    • Like 1

    LineageOS 22.x Official Release for Pro1-X (QX1050)

    in General Discussion

    Posted · Edited by agent008

    I have managed to find a recovery for the "microG" flavour of LineageOS 22.1 and that has allowed me to flash 22.1.

    For future reference if anyone needs, I downloaded it here from microG's website.

    The archived image from timschumi as pointed out by @TeZtdevice worked perfectly. I have just booted into 22.1 and will check battery life and usability in the next couple of days.

    Thanks for all the help!

     

    EDIT: Daaaargh! I forgot to remove my google account from the phone when I was on 22.2. Now I can't re-login on the phone on 22.1! Had to reflash LOS without MindTheGapps to be able to use the phone, and even so I am not being able to set the screen lock PIN. Now for another odissey -- getting Gapps to work on the phone given that I forgot to remove the Google account before I wiped data. 🤦‍♂️

    • Like 1

    LineageOS 22.x Official Release for Pro1-X (QX1050)

    in General Discussion

    Posted

    17 minutes ago, TeZtdevice said:

    Perhaps.... here: https://b4.timschumi.net/lineage-archive/lineage-22.1-20250407-nightly-pro1x-signed.zip
    (not the last, but one of the 22.1 versions)
    That´s the  main page of this archive: https://lineage-archive.timschumi.net/#pro1x

    Thanks! That is fantastic.

    Now, I downloaded that image and tried sideloading it but the 22.2 Recovery refuses to install it with error: "Current SPL: 2025-06-01 Target SPL: 2025-03-01 this is considered a downgrade. Denying OTA because it's SPL downgrade".

    Is there no other way than me reflashing the phone to stock prior to installing 22.1? Since I don't have the 22.1 recovery, do you guys believe 22.2 Recovery will do?

    Pro¹ X - backup, restore and repair device specific partitions

    in How Tos

    Posted · Edited by agent008

    I have just pulled the backups now.

    Here's what I did.

    1)  Unlocked bootloader following this guide --> (ATTENTION, at the end of step 3, after enabling USB Debugging, find another option on the same screen called "OEM unlocking". Enable that option too, else you cannot unlock the bootloader. Then, proceed with the remaining steps on the guide)

    2) Installed Magisk and rooted phone following this guide --> 

    3) Downloaded LineageOS 22.2 recovery.img only at this point. Booted to the bootloader, by issuing the command below: 

    adb reboot bootloader

    Then flashed the LineageOS Recovery with the command below: 

    fastboot flash recovery recovery.img

    After flashing was finished, I selected "boot to recovery" on the bootloader.

    4) Once on the Lineage Recovery, I selected "enable ADB" and followed Eske's guide found here --> https://eskerahn.dk/?p=4633

    One adjustment to Eske's instructions is that I replaced his ls command with: 

    adb ls -lah /dev/block/by-name

    And, from that list, I could find the device names for the partitions that are recommended that we back up. This is what they were linked to in my particular phone: 

    lrwxrwxrwx 1 root root   15 1970-01-01 00:47 fsc -> /dev/block/sdf5
lrwxrwxrwx 1 root root   15 1970-01-01 00:47 fsg -> /dev/block/sdf4
lrwxrwxrwx 1 root root   15 1970-01-01 00:47 modemst1 -> /dev/block/sdf2
lrwxrwxrwx 1 root root   15 1970-01-01 00:47 modemst2 -> /dev/block/sdf3
lrwxrwxrwx 1 root root   15 1970-01-01 00:47 persist -> /dev/block/sda2

    So, I just ran the "adb push <source> <destination_backup.img>" command for each of the above.

    These are the sizes for each of the images: 

    -rw-r--r-- 1 localuser domain users   131072 jun 30 17:11 fsc_backup.img
-rw-r--r-- 1 localuser domain users  2097152 jun 30 17:11 fsg_backup.img
-rw-r--r-- 1 localuser domain users  2097152 jun 30 17:10 modemst1_backup.img
-rw-r--r-- 1 localuser domain users  2097152 jun 30 17:10 modemst2_backup.img
-rw-r--r-- 1 localuser domain users 33554432 jun 30 17:09 persist_backup.img


    Hopefully my backups are correct? 32M for persist, 2M for modemst1, modemst2 and fsg; and 128K for fsc.

     

    EDIT: As I now think further about it, step 2) above (rooting with Magisk) is probably not necessary. I had done it believing I could use adb on a rooted system with the phone booted to Android. It didn't work as the adb pull command would always run internally on the phone as an unprivileged user and didn't have access to the /dev/block devices.

    I believe it's likely that performing steps 1), 3) and 4) above is sufficient.

    Pro1X - Lock Bootloader, but now, cannot Unlock it anymore

    in General Discussion

    Posted

    On 6/29/2025 at 1:00 PM, mangled said:

    try restoring back to stock android and repeat the process? 

    I was on full stock. Still couldn't make it work. After bashing my head a lot, I found the answer. Here's what I had missed:

    On 6/25/2025 at 11:46 AM, agent008 said:

    UPDATE: Yes, I was missing something. Before booting into recovery and issuing the fastboot flashing unlock command, one needs to boot into Android, go to Developer Settings, and Turn on the option called "OEM unlocking". Who knew? Official instructions by F(x)tec here are unclear, and the only mention to it I found was a nonspecific one on the LineageOS flash guide.

     

     

    • Thanks 1

    Pro¹ X – state of production and delivery

    in Pro1 - Thoughts & questions

    Posted · Edited by agent008

    On 6/25/2025 at 11:46 AM, agent008 said:

    I have finally taken possession of my ordered Pro1X.

    I am from Brazil but had it delivered to a friend in the US to avoid tariffs. This was last August 2024 so none of the new US tariffs were in force.

    I finally came to his house yesterday and opened the box ( he wouldn't dare opening it before despite all my insistence ). I am disappointed to say I received a used phone with a fading label on the back, scratch marks on the aluminium frame, with what looks like a brand new screen and a used cable. It's evident to me it was a return or, worse, a service phone delivered to the wrong person.

    It didn't boot, all I got was the bootloader. Fastboot flashing unlock did not work either.

    I then flashed the non-GMS EDL file using the Linux qdl tool as described here, and got the phone to boot.

    Now I'm trying to install LineageOS but am stuck at the first step -- unlocking the bootloader. 

    
fastboot flashing unlock

    just returns an error every time: 

    
FAILED (remote: 'Flashing Unlock is not allowed
')

    Perhaps I'm missing something in the process. Hope somebody can point me to the right instructions?

    Oh, I forgot to add. I'm an IndieGoGo contributor, not a website customer.

    I've never heard(read) of anyone who ordered from the website actually getting a phone.

    Pro1X - Lock Bootloader, but now, cannot Unlock it anymore

    in General Discussion

    Posted

    Hey Forum,

    I'm going to repeat what I posted on the "state of production and delivery" thread here, because I believe it's more on-topic. Has anybody experienced the same? I can't unlock the bootloader on my recently received Pro1X so that I can install a better camera app and take full advantage of LineageOS. Any help appreciated!

    Quote

     

    "I have finally taken possession of my ordered Pro1X.

    I am from Brazil but had it delivered to a friend in the US to avoid tariffs. This was last August 2024 so none of the new US tariffs were in force.

    I finally came to his house yesterday and opened the box ( he wouldn't dare opening it before despite all my insistence ). I am disappointed to say I received a used phone with a fading label on the back, scratch marks on the aluminium frame, with what looks like a brand new screen and a used cable. It's evident to me it was a return or, worse, a service phone delivered to the wrong person.

    It didn't boot, all I got was the bootloader. Fastboot flashing unlock did not work either.

    I then flashed the non-GMS EDL file using the Linux qdl tool as described here, and got the phone to boot.

    Now I'm trying to install LineageOS but am stuck at the first step -- unlocking the bootloader. 

    
fastboot flashing unlock

    just returns an error every time: 

    
FAILED (remote: 'Flashing Unlock is not allowed
')

    Perhaps I'm missing something in the process. Hope somebody can point me to the right instructions?"

     

     

    Pro¹ X – state of production and delivery

    in Pro1 - Thoughts & questions

    Posted · Edited by agent008

    I have finally taken possession of my ordered Pro1X.

    I am from Brazil but had it delivered to a friend in the US to avoid tariffs. This was last August 2024 so none of the new US tariffs were in force.

    I finally came to his house yesterday and opened the box ( he wouldn't dare opening it before despite all my insistence ). I am disappointed to say I received a used phone with a fading label on the back, scratch marks on the aluminium frame, with what looks like a brand new screen and a used cable. It's evident to me it was a return or, worse, a service phone delivered to the wrong person.

    It didn't boot, all I got was the bootloader. Fastboot flashing unlock did not work either.

    I then flashed the non-GMS EDL file using the Linux qdl tool as described here, and got the phone to boot.

    Now I'm trying to install LineageOS but am stuck at the first step -- unlocking the bootloader. 

    fastboot flashing unlock

    just returns an error every time: 

    FAILED (remote: 'Flashing Unlock is not allowed
')

    Perhaps I'm missing something in the process. Hope somebody can point me to the right instructions?

    UPDATE: Yes, I was missing something. Before booting into recovery and issuing the fastboot flashing unlock command, one needs to boot into Android, go to Developer Settings, and Turn on the option called "OEM unlocking". Who knew? Official instructions by F(x)tec here are unclear, and the only mention to it I found was a nonspecific one on the LineageOS flash guide.

    Pro1-X: Flashing Stock Android with QDL (for those with linux)

    in How Tos

    Posted

    Thank you, this was very helpful, with qdl I was able to successfully flash my Pro1X with the factory "Non-GMS" image, version 2.1.5.

    I had to edit some of the .c files to add <stdlib.h> as a header include, but after that it compiled successfully.

    I'd like to install LineageOS but am having a hard time unlocking the bootloader.

    Pro¹ X – state of production and delivery

    in Pro1 - Thoughts & questions

    Posted

    37 minutes ago, claude0001 said:

    Rather, they realised the radio problems, discovered when the first devices went into the wild, cannot be resolved by firmware updates after all. So they hold back all devices not yet shipped to apply hardware fixes.

    Well, of all 3 scenarios you put forth this would be the best one. Meaning we might get a fixed version. Oh man. Everyone has limits. I am pushing mine further away in hopes that the outcome will be a good one.

    • Like 3

    Pro¹ X – state of production and delivery

    in Pro1 - Thoughts & questions

    Posted

    Oh my... December? It's quite a change in tune from "it will ship next week".

    I hope people at FxTec are getting better at estimates, rather than spitballing the December 2022 date which then might turn into March 2023.

    I've been supportive of FxTec's struggles and endeavour to make a grat phone but with my Pro1 turned into a paper weight (for now at least) and my replacement phone showing signs it might soon give up the ghost... I'm utterly disapointed.

    I'm trying to find solace in the reasoning that since they changed the estimates from "next week" to December, they might have understood the idea that it's better to put out realistic estimates rather than just keep the cliffhanger announcements. Time will tell if this hope of mine is founded or unfounded...

    • Like 3

    Pro¹ X – state of production and delivery

    in Pro1 - Thoughts & questions

    Posted

    34 minutes ago, Rob. S. said:

    The operation is definitely much more active than it was until recently. In response to my recent support request, I got a reply today that the USB module and display unit were available (£30 + £149 + shipping), and our dialogue went on to determine the shipping cost via FedEx, and the package is already 'in transit'!

    I guess I'll wait for the Pro1X to arrive, though, before I undertake the adventure of dismantling the old Pro1...

    I second that, I've been corresponding with tech support in order to see if my Pro1's no-keyboard and no-touch issue can be solved, and the rep at support has been quick to reply and also stated they have the USB board and display on stock.

    • Like 2
    • Thanks 3

    Pro¹ X – state of production and delivery

    in Pro1 - Thoughts & questions

    Posted

    8 minutes ago, SnydeyMan said:

    I got the email that they were about to start shipping and then 5 minutes later I got a text from FedEx saying I have a package on the way. When I clicked on the tracking number it said the package was coming from China. 

    Whoa, then it has finally started! Around what number is your contribution? Mine is in the 2100's.

    • Like 1

    Display units with large tap-insensitive margin

    in General Discussion

    Posted

    Hi, how can I help with this? Even though I believe my case is different (no touch at all, touch driver absent from i2c bus, whereas the problem here is insensitive touch margins).

    Last thing I attempted was flashing an older Lineage version (17.1) and running the display firmware upload APK. The apk never was able to update the display always complaining that firmware update wasn't supported.

×
×
  • Create New...

Important Information

Terms

  I accept