Jump to content

agent008

Members
 View Profile  See their activity

  • Content Count

    233

  • Joined

  • Last visited

  • Days Won

    4

 Content Type 

Posts posted by agent008

    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.

    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.

     

     

    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.

    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.

    Pro¹ X – state of production and delivery

    in Pro1 - Thoughts & questions

    Posted · Edited by agent008
    spelling error

    8 hours ago, Noob said:

    Side note from a couple of updates ago; did anyone else who's replaced their Pro1 screen see the picture of all those black stickers and wish they could get a few spares? 

    I wish. I wonder what the black backing stickers do? Are they related to touch detection on the screen? Last year when I replaced my screen for the first time I didn't reuse the old black sticker from the original screen, and it worked fine.

    Display units with large tap-insensitive margin

    in General Discussion

    Posted

    On 5/16/2022 at 4:57 AM, EskeRahn said:

    The "gt1x" could well indicate x is to be replaces with some digits,
    According to this, at the least a gt1151 exists, so that might be a relevant guess?

    Have we got any good images of the print that might help?
    We expect a minor square chip like on this image.

    ADD a little more googling indicates that a gt1143 and gt1152 also exists
     

    I've taken a photo of the chipset inside my first replacement screen which worked fine for a year until I broke its glass.

    image.png.c940ee4a2cdab923b1714bdc73f87714.png

     

    It's not very legible on the photo but it's a GT9286.

     

     

    • Thanks 1

    LineageOS 19.1 Official Release for Pro1

    in Pro1 - Thoughts & questions

    Posted

    On 5/21/2022 at 2:55 AM, Kaali said:

    There is an APK to flash the screen firmware but it only works on Android 10 or lower (basically stock or LoS16 or 17)

    Hi! At this point I would be willing to try this. Since not even my old screen (glass broken, touch perfect) worked with touch anymore, I'm not very hopeful it might fix but, why not try? I would flash an older LineageOS and try to run this APK.

    At the moment the only way I can interact with my Pro1 is by connecting a USB-C hub to it with a mouse and keyboard plugged in. Or with a  bluetooth keyboard but in order to pair the phone and the keyboard I still had to plug a mouse into the phone. No phone keyboard and no touchscreen for me. Pretty bummed and had to resort back to a Moto Z2 Play I had in storage. Which had its screen die yesterday....

×
×
  • Create New...

Important Information

Terms

  I accept