My MI A2 is no longer recognised by my computer..
-
Hi @voltcab,
Well, first of all, I don't have one of the phones you used, so I can't reproduce it.
Secondly, in the normal case (when no one is fiddling with it) nothing should change on its own.After connecting the phone to the computer, you have to enter the pin/password on the phone.
So it looks like we have many many possibilities where something is working wrong.
ADB (Android Debug Bridge) is a software interface to manage Android devices from the computer. The most important thing is that there are different software and they can get in each other's way if you install both/more on the same computer. For example, the Ubuntu in-house and/or "Android SDK suite" (or others).
See also the following links:
https://manpages.ubuntu.com/manpages/jammy/man1/adb.1.html
or in German (you have to translate it yourself):
https://wiki.ubuntuusers.de/adb/And (no guarantee, because here I am not sure) the phone should be enabled as follows:
In the developer options, enable ADB debugging and OEM unlocking.In addition, forum members in possession of a phone type like you have would be more helpful, even if they only share or negate your problems.
Greetings
MarioTranslated with www.DeepL.com/Translator (free version)
-
Forgot to mention the reason I install Android Studio is I get the latest fastboot and ADB drivers that has so far covered all the devices I have put UT on.
-
@voltcab Easy, connect the phone to the usb on the back of the pc, magic...
-
@stropbu not sure that kind of answer is of any help...
-
@keneda I, if I am sure that it works, it is more, more than once I have verified it, perhaps it is the length of the internal USB cable to the front part, it reduces the voltage and response time to the round trip data, as well as the frequency, that added to the external cable of poor quality = failure. I insist, rear ports of Pc Tower, not portable PC.
-
@stropbu
So the advice would be to try a different USB port or to check the USB cable.
And also maybe they have a hardware issue with their phone...What @Keneda tried to explain is that there is already some discussion in this thread and your comment didn't add anything of value until your second, more detailed, comment.
Your first message can be understood as "duh you just have to plug it in..." also what works for you doesn't mean it will work for other, there are tons of parameters to take into account, hardware on both side, cable, power grid of the country/city, OS of the computer, ...
-
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...
-
@voltcab
It is frequently advised to use USB2 ports instead of USB3.
But your issue is very weird there is no reason it won't work anymore after some time... -
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?
-
Do you think that using the phone with the developer mode on can change the phone settings ?
-
@voltcab You can leave Dev mode on. I guess you have tried completly removeing adb and drivers and reinstalling? You might have to regrant permission for adb though. Maybe even swop update channels to see if that has an effect. Or even rerun through the installer without the wipe option.
Only other thing is the usb port on the phone clean. I once had a bit of dirt stuck in which stopped a proper conection. Tend to thing if it suddenlt stops and nothing changed start with cables and ports, then the old adb devices in a terminal. Also think you have probably done all that.
-
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 !
-
... So, it's no, nothing, nada, the phones remain invisible...
-
Hi. @voltcab,
Next, I would connect any other phone, from a friend, to your laptop to be sure about the functioning on the computer side including the cable.
Greetings
Mario -
@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... -
@voltcab. Someone had this issue a while ago. What ended up working for them was doing the following:
- Turning off developer mode in the settings.
- Revoking USB debugging authorizations in UTTT app (System -> ADB settings (under USB settings) -> Revoke USB debugging authorizations (under Debugging)
- Reboot
- Enable developer mode under settings.
- Connect device to your computer.
- Allow computer acces on device at prompt.
-
@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... -
@voltcab You mean, even if you switch off developer mode it remains selected in the settings? That is weird indeed, unless it is some quirk with this particular port.
-
@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... -
@Voltcab @arubislander I'm having the same two problems today with my Pixel 3a running the latest version of UT stable. Two Ubuntu Desktops and three USB cables cannot see my UT phone or connect via ADB.
However, I noticed I can connect via ADB in Recovery Mode only. So the USB cables, ports and ADB are fine.
I also noticed my UT is always in Developer Mode after I turn it off and reboot. I tried the instructions above regarding UT Tweaks Tool and my computers still cannot see my UT phone.
I'd really like to be able to ADB and use push/pull to run backups, but for now my hands are tied. Anyone figure out what's causing this?
