I've searched everywhere for a solution (XDA and elsewhere) but all solutions seem to not work with my device.
I don't get the RSA dialog to popup when I connect my phone to a PC anymore, and I can't work with ADB without this.
The device is shown as 'unauthorized' in ADB
"OFFLINE" in Android Studio
I tried different ADB versions.
I tried restarting ADB server, device and PC.
I tried using different PC's, with different OS's.
I tried different USB drivers.
I tried multiple USB Ports and Multiple USB cables
I tried deleting the ADB key from the PC.
I tried factory reset of phone
Absolutely nothing works. Other phones get connected to my PC just fine(Tried 3 other phones), so the problem is with the Phone.
It's like my device lost it's ability to be recognized.
Can someone help me out?
Related
Every time i connect my wizard to my machine using the USB cable, i get the following message in baloon.
"One of the USB Devices attached to this computer has malfunctioned, and windows does not recognize it."
It appears as "Unknonw Device" on windows device manager.
This started happening when i changed my ROM to AMP.v2.Vanilla. Prior to that my wizard was connecting fine. I have been trying to resolve this for days now but no luck.
Following are the things i have tried.
1. Un-installed Activesync & re-installed.
2. Soft & Hard Reset the device.
3. Tried going in bootloader so that i can install my preivous rom, but the machine still doesnt recognize the device and gives the same message as mentioned above.
4. Removed all the USB controllers and re-installed in the machine.
5. Tried on different machines but same results, so its not machine specific.
6. Tried with a new cable to so its not the cable, it has to be the device.
Anyone who can help with this. I am sure i am not the only one having this trouble.
Any kind of help is appreciated. Just need to connect and go back to my preivous rom.
Thanks in advance.
Nick.
Please don't cross post. Pick a flavour and run with it.
V
My apologies mate. Its just that i am little desperate now to make this thing work.
nvm ive been an idiot,
AdbWinUsbApi.dll was not present, this makes sense as this would probably describe the USB interface...
And when phone is booted up, with usb debugging connected, adb devices doesnt show anything either, and the task manager is saying that the adb interface is connected...
Update #2:
My locked and unrooted nexus 7 is also not showing up, but the drivers are said to be installed and the device is said to be connected...? Im now wondering if this is a problem with my PC?
Try different usb ports, mainly the ones in the back of your pc. Sometimes the ones on the front cause issues. Also try other usb cables.
Also if your environment variables aren't set up correctly you'll need to CD to the directory in which adb and fastboot are located.
I have searched extensively to no end. When I ./adb devices in terminal, it lists my phone but says 'unauthorized.'
I do not get a prompt on my phone to authorize its connection to osx.
I have rest phone to factory spec. Still nothing.
Thoughts?
lablunk said:
I have searched extensively to no end. When I ./adb devices in terminal, it lists my phone but says 'unauthorized.'
I do not get a prompt on my phone to authorize its connection to osx.
I have rest phone to factory spec. Still nothing.
Thoughts?
Click to expand...
Click to collapse
I had this issue on a stock rom with ADB in Windows and in Linux. This apparently is a known "issue" with the stock rom when the USB mode is set to MTP.
The "fix" is to make sure you are in Network mode (either Internet or Modem is fine). You might have to disconnect and re-connect the USB cable a couple times (and re-select the Nework mode) before it will actually connect with ADB. If it pops up with the ADB Verify Server Fingerprint window on the phone, you have sucessfully made an ADB connection.
Not sure If I missed it with searching or if anyone has made a post about this, sorry for repeating.
I just recently bought the Essential phone and for some reason had issues getting the USB debugging authorization to show up. Nothing seemed to fix it, tried numerous cables, usb ports, removed and reinstalled drivers, still nothing.
I realized that there is a file located in C:\Users\Current User Name(whatever the current user is)\.android called adb_usb.ini. It list device IDs of other android devices and for some reason my phone wasn't listed. After adding my device ID (the file just opens in notepad) and saving, I went back to terminal and sure enough my phone got the allow usb debugging rsa key prompt and my phone finally showed up when typing ADB devices.
The device ID is 0x2e17
Also, even though I downloaded the lasted platform tools from google, in order to issue commands in fastboot I need to type fastboot -i 0x2e17
So for example in order to unlock the bootloader I needed to type fastboot -i 0x2e17 flashing unlock. I modified Essentials flashall.sh file and added the device id to all commands in order to get DP4 installed.
Didn't work for me...however windows just gives me an error when i even connect my phone to the PC.
Update: switching usb-c cables DEFINITELY works.
Try another computer will sure fix this, or just install another system like windows 10 or Ubuntu something like that.
I was having problems when i connected my essential phone to the pc and nothing was showing up. After a lot of frustration i decided to plug my usb cable to a usb 2 port instead of a usb 3.0 and that made everything work.
So if you're having problems connecting to the pc try using a regular usb port and not a 3.0 port.
I had previously connected my Asus X00TD to my laptop for transferring files. The phone doesn't connect to PC from yesterday. Only charging happens after connection, and device doesn't show up on the device manager(no change on list of devices after connection), and no notification sound of device being connected either. There is no notification in my phone as well. Here are the following workarounds I have tried, but failed:
Changing USB cable
Changing PC/laptop
Installing ADB and Qualcomm drivers and again uninstalling them(error code 10 on ADB Driver)
enabling and disabling USB debugging
changing connection mode(nothing works)
Going into safe mode
restarting and connecting multiple times
Kindly help me if possible, and your help will be kindly appreciated
I had a similar problem recently. What ended up working for me was to install some generic Android driver published by Google. I already had the ADB package installed, but without the generic Android driver published by Google, my phone could charge and transfer files, but I could not issue ADB commands through the Windows command prompt.
The package I needed was called "usb_driver_r13-windows.zip"