Posts made by Voltcab

@arubislander
Yes, I switch off (grey button) but when the phone restarts, it automatically switches to Developer Mode... If one or more owners of MI A2 could make a return on this problem...

@arubislander
Hi,
Thank you, maybe the problem is not far away... it doesn't work for me but following your procedure, I have a difference with your result... When I restart, the phone automatically switches back to developer mode (In fact, it always remains in developer mode), maybe there is something to look for on that side? This evening, I will test with the other phone to see if the result is the same...

@mario-ch
Hello ! I'm using a connected android tablet, it's directly recognized. The problem of the cable should be eliminated... For the UT version, the phone is in stable channel OTA 23. We never know, if anyone has heard of a problem with this channel or this version...

... So, it's no, nothing, nada, the phones remain invisible...

Ok, I'm dropping the developer mode story... I found a laptop with USB2 plugs, contact cleaner and new cables... All I have to do is update it and... I cross the fingers !

Do you think that using the phone with the developer mode on can change the phone settings ?

Given the number of tests on different computers I think I tested USB2 ports but I'll check anyway... I'm going back to the fact that I had the same problem with an Opo and that adding the hardware ID to the ADB commands seems to have unblocked the situation... Do you know where I can find the MI A2 ID?

Hi! Thanks for the leads but unfortunately I still don't have a positive result... I'm using a laptop at the moment, I'll test the connection directly on a tower card but on a laptop I think the connection is direct too... One detail, I had left the developer mode open, I don't know if this can have an impact on the phone settings when using it...

@mario-ch
Hi,
I will try to be as precise as possible...
I have several phones under UT, two MI A2 and a Oneplus one, on these devices, I encounter the same problem of recognition. At the beginning everything is ok they work normally and after a few months they don't connect to the PC anymore... I tried on several computers under Ubuntu 22.04 and windows 10 with several cables including new ones but without success. While searching on the internet I came across this topic (https://docs.ubports.com/en/latest/userguide/advanceduse/adb.html) which used the Oneplus One as an example and the Opo was finally recognized by the PC running Ubuntu 22.04, so I was able to save my files. For the Mi A2 I did not find the ID as indicated in the topic Shell access via ADB, so I can not test this solution. Maybe there are other ways? Thanks for your feedbacks...

@keneda
It no longer goes up on the desktop and is no longer recognised at all...

@keneda
Hello and thank you for your answer, yes, I have tested many cables and pc's under linux and w10 but they don't recognize the phone... I had the same problem with an Opo and with this method (https://docs.ubports.com/fr/latest/userguide/advanceduse/adb.html) my pc managed to display it and I was able to recover my files... I would like to try the same process with an MI A2 but I don't know where to find its identifier. I will have to find out why all my UT phones have the same problem...

Hello, my MI A2 no longer goes up on my computer desktop, it is no longer recognised, could someone give me the identifier of the MI A2 in order to force its identification by the ADB commands?