Jump to content

agent008

Members
  • Content Count

    209
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by agent008

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

  2. 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
  3. 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
  4. @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
  5. 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!

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

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

     

  8. 1 hour ago, CornholioGSM said:

    Hmmm it sounds littlebit hard to remote help you. For me it looks like display touch problem. Because i have not hear about fully not working touch...have you visually checked display unit ?...then all flex cables and connectors?

    Here can be problems with touch ... but problems like shifted touch, no touch on edges etc.

    about keyboard it looks like hw problem too - was keyboard water spilled?...how about connector? 

    ...will be needed more informations about your phone

    Thanks for your interest in helping. I can say that the last time I changed the screen (this is the second time now) it was the same. Screen completely unresponsive, 100% not working until the update came through. The problem now is that the OTA provider for the update is not serving the updates anymore!

    Therefore -- THIS IS IMPORTANT! @EskeRahn you might want to put this info somewhere very visible. If you are considering a screen replacement right now, don't do it until a way has been figured out to update the screen without the OTA!

    I would be very thankful if someone could provide me with the file that has been used in the past to solve this manually (without OTA). My Pro1 is at this moment with the stock firmware installed (as per this post: https://community.fxtec.com/topic/2466-guide-restore-to-stock-firmware-using-fastboot-method/ ), waiting for a solution for this. Since stock is Android 9 I believe the manual update package will work.

    Thanks everyone so far for your help!

     

  9. 7 hours ago, Kaali said:

    Interesting, did you use device fingerprint from another device? That is definitely not recommended as it can lead to all kind of problems. There is a working fingerprint from the stock firmware for the pro1 in the MagiskHidePropsConfig fingerprint list which is only one that one should use with pro1.

    I did because back then (in early 2021) it was the only way that solved for me (then later on stopped working anyway). Now after I solve my screen I'll use the QX1000 fingerprint. thanks

  10. If anyone can help me with the screen update package I'll be grateful. I was foolish enough to install a new screen without visiting the forum and this thread. Turns out the stock OTA updates are not working anymore and now I have a phone with a beautiful new screen that doesn't work (no touch at all!) and I can't solve it. Besides my hardware keyboard stopped working a couple weeks ago, so the only way I can use the phone now is by plugging an external mouse and keyboard... 😪

  11. 3 minutes ago, EskeRahn said:

    Indeed. Or at the least that there were a simpler option than an entire flash to stock, package by package to both to a and b, as the guide describes...

    Eske, have you ever heard of the "58 megabyte" update that installs on top of stock that @divstar mentioned? My memory isn't very sure but I believe I also had to go through this to make the digitiser to work last year when I replaced the screen for the first time. I wonder if that update can be downloaded somewhere?

  12. An observation: it is interesting that the device fingerprint remained as "Sony Xperia" (I don't remember the model, XZ II maybe?) even after flashing stock. Also, I got the fingerprint bug, seems "persist.img" is not included in the "back to stock" package? EDIT: never mind, persist.img is also part of the package. Sorry.

  13. 10 minutes ago, EskeRahn said:

    Is this a clean install after stock? If so did you follow the guide to the letter and wiped the user partition also? If an upgrade from 18.1 your data ought to be preserved, and the setup guide thus not launched. Practically everything was preserved for me. Despite being forced to also replace OpenApps 11 with MindTheGapps 12.

    Yes, it is. Actually my saga is longer and more convoluted. I had a cracked screen. Installed a new one like I did last year. Touch wouldn't work at all (like last time). Not only the edges but no touch is registered.

    I then went back to stock to see if the touch issue would be fixed. No dice. Plugged in a keyboard and mouse and tried to set up the stock firmware because I read that an OTA update might for stock solve the touch issue -- read it here:

    However, stock would show 'no updates'. But when configuring the device I realised that Google asked me to confirm on my other devices the new "Sony Xperia" I was setting up. So I realised I reflashed my phone with an altered device signature done with MagiskHideProps module (used to make banking apps work with AICP).

    I unsuccessfully tried to install Magisk to stock. Then I had the idea of using Magisk with Lineage 19.1 to install MagiskHideProps and return the device signature to the original. That's where I got stuck. So I reflashed stock again.

    Now I'm flashing AICP 16.1 which was what I had been using until yesterday, in order to see if I can get to Magisk and return the device signature to normal. Maybe then the "screen update" will be able to be downloaded.

    Another option would be a fix "package" that someone had here (I think it was @EvilDragon ?) that I could run on stock.

    Man, that's why I hate reflashing... why couldn't our replacement Elephone screens work out of the box? 🤕

    • Sad 2
  14. I successfully installed LineageOS19.1 20220502 with MindTheGapps 12.1.0 20220416, but I can't get past the welcome screen setup part. After it asks me for the PIN or lock pattern it takes me to the fingerprint setup. As soon as I finish the fingerprint setup it enters a loop, asking me again for the PIN or pattern and taking me through the fingerprint setup all over again.

    • Sad 1
  15. 19 minutes ago, VaZso said:

    Interesting that practically I did not have such an issue under 18.1

    I had a very bad USB port which has caused a lot of issues for me, including close to keep charging or even depleting during night, so I had to reach a state where it shows "charging" instead of "slow charging" and it worked or at least worked for a short while having to reconnect agan for further charge.

    That was something like a contact issue for me.

    My current USB panel is new and I don't have any charging issues...

    How difficult was it to find a new USB port for your Pro1?

  16. On 4/6/2022 at 9:51 AM, Hook said:

    It is appreciated.  Unfortunately, my Pro1 is still in the shop so I'm out of the loop right now (not suprisingly, nor unexpected—knew it would take time when I sent it in).  I'm always happy to see it is still going.
     

    Looking forward to getting back and hoping, maybe, there might be an AICP for the Pro1x eventually.

    I agree. I follow this sparsely but do not post much here anymore (lack of time).

    Just last night I have replaced the screen for the second time, and am now in the process of going back to stock, then reinstalling AICP yet again. Also my keyboard is inoperative (maybe a hardware issue, let's see after the reflash). I took the opportunity to open the back of the phone while changing the screen, I disconnected and reconnected the keyboard flat cable (it didn't solve the issue) but did not feel like tearing the whole thing apart before trying the reflash, which I need anyway because the touchscreen doesn't work.

    Wouldn't be a bad idea to find a way to do the screen firmware update without reverting to stock...

  17. 10 minutes ago, Hook said:

    Google Maps does fine with my location, but I had to agree to allow it to use location services or whatever they call it.  It was a pop-up that showed up when I hit the locate icon.  I'm using  Open Gapps, but I wouldn't expect that to make a difference.

    Thanks. Yes, I also agreed to location services. But my phone often loses GPS fix and is usually clueless about where it is (maybe it's a good thing so nobody's tracking me? 😁)

    I had OpenGapps on the Q Beta, and also tried OpenGapps with this fresh AICP R install. Didn't make a difference, couldn't make SafetyNet nor GPS work with either of them.

    I'm now suspicious of the issue discussed here: 

    But, I don't know how to change this file on my phone. Having Magisk installed, it seems I do not have a straightforward /system mountpoint? 🧐

  18. Hey guys, I'm having an issue with location. I already had the same problem on AICP Q beta. (Beta also had an issue with notifications. Most apps' notifications never played a sound or vibrated, this is now working on AICP R).

    I can't reliably get my location on Google Maps and other apps that depend on Google's location services infrastructure. I've already gone through all of the location settings and permissions to no avail.

    It seems that apps that communicate directly with the GPS work OK.

    Does anybody have any suggestions? Is AICP's standard behaviour to not allow location to work?

    My setup:

    * AICP 16.1 - 20211110 build
    * MindTheGappas 20210920 build
    * Magisk 23.0 with Props Config, Riru and safetynetfix
    * Props set up to simulate a Google Pixel 5 with Android 11

    Help needed... Thanks in advance!

×
×
  • Create New...

Important Information

Terms