Jump to content

agent008

Members
  • Content Count

    221
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by agent008

  1. 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
  2. 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
  3. 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.

  4. 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.

  5. 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
  6. 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....

  7. 2 hours ago, VaZso said:

    When has your keyboard stopped working anyway?

    About a couple weeks ago. It didn't work, I rebooted, it started working again. Then later on the same day it died permanently.

    I hadn't been using it during the last couple months prior to the first symptom a couple weeks ago.

    2 hours ago, VaZso said:

    Anyway, have you used a metal tool to disconnect connectors?

    Always my fingernails or a plastic cellphone pry tool.

    2 hours ago, VaZso said:

    My suspect is somehow you made a short-circuit and now power of these devices are missing, so it would be good to check that somehow and find a way to power them... but that is not something an ordinary user can do.

    I can try looking at the whole motherboard assembly and the screen connectors with a magnifying glass. But only will be able to do so during the weekend. But this wouldn't explain the keyboard failing by itself prior to the screen replacement.

  8. 14 hours ago, CornholioGSM said:

    anyone can help me how ti install magisk ? i have installed magiskapp 24.3, and then i have tried to install  magisk.zip in recovery...but i stuck on could not find meta-inf/com/google/android/update-binary

     

    ***SOLVED***

     

    It worked out of the box for me. Boot to Lineage or AICP recovery, choos apply update via ADB, then on the host PC: 'adb sideload Magisk-v24.3.apk'

    Good to know it worked for you. One important comment is that if you are coming from a fresh ROM install, you should flash your ROM via sideload, then flash MindtheGapps or OpenGapps, then reboot to system. After you get to the Android screen, reboot to recovery again and then sideload Magisk.

    I'm not sure if the reboot to full Android screen is needed, or just a reboot back to recovery is enough. So I always reboot to system first.

    • Like 1
    • Thanks 1
  9. 11 hours ago, VaZso said:

    Do all your sensors / interfaces work on your phone?

    The fingerprint sensor works. I have been using the phone with a USB -C hub with a mouse connected to it, that is how I can navigate the system and how I was able to install Termux and run i2cdetect.

    Every time after flashing I use the mouse to pair a bluetooth keyboard+touchpad, it's fun to use an Android device without touch, haha. 😪

    Apart from the fingerprint, I have devices 0x08 (microphone?) and 0x09 (unknown device?) on bus 7, and on bus 6 I have 0x28 (NFC).

    I spent 2½ days troubleshooting this and now don't have much time to look further into it until the weekend. If I have some time today I will connect the broken screen (which had a broken glass but was working, both screen and touch) and see if it still works. If it works, then I have 2 problems: new screen's touch digitiser is dead, and the keyboard isn't working. If the old screen doesn't work anymore, then I suspect one problem is the cause of both malfunctions and that might be something on the i2c bus (maybe solvable only by changing the motherboard 😪)

    • Like 1
  10. @VaZso : bingo! I don't have any drivers using address 0x14 (just "--" instead of "UU" on row 0x10, column 4). So I'm now suspecting a hardware issue, either flat cable misconnected or something else. Did I understand this right? Any other testes I could carry out to confirm there is nothing at address 0x14? Thanks

    • Like 1
  11. 29 minutes ago, Rob. S. said:

    But just to be sure, did you actually boot the 2020825 stock ROM after flashing it? It needs to start up once to do the touch margin adjustment trick.

    Thanks. Yes, I did. In fact the phone is on right now in hopes the OTA might come yet. haha

    If I remember correctly, last time it took an OTA to solve the screen too.

    However, I will reopen the phone this evening and recheck all connections. Maybe something is not right in there. I also can try the old screen and a third new one I have still on the box.

    Thanks for everyone's inputs!

  12. 14 minutes ago, EskeRahn said:

    But there have not been an update to 20200825, so even if OTA was up, that would not offer anything newer.

    I see. I might try an older stock then, if OTA is still up i might be lucky. I only found older stock firmware at @tdms link but they are EDL files and his Linux tool didn't work for me. I'll try the windows tool. EDIT: or if anybody has the older fastboot image I'll be thankful if you share it with me. Fastboot works well with my Linux box.

  13. 34 minutes ago, EskeRahn said:

    I'm a little confused here. Why do you need the OTA update? Isn't the issue fixed with flashing newest stock directly? Do it need to be flashing an older version with successive OTA update to be fixed?

    I flashed the 20200825 fastboot firmware from the Back to Stock guide thread: https://community.fxtec.com/topic/2466-guide-restore-to-stock-firmware-using-fastboot-method/?do=findComment&comment=33838

     

×
×
  • Create New...

Important Information

Terms