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.
Related
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 can't access my N7 with adb (when booted) or fastboot (while in the bootloader). It's connected via a USB cable. This is both with a Mac and WUGS. Commands like fastboot devices or adb devices return nothing as the device isn't seen. I can connect my N4 and use those commands without problem. I just tried doing the same with my 2013 N7 and it's not being seen, either. Strange. I don't think I've had this problem before on the Mac. I have on Windows, which I can sometimes resolve by installing and reinstalling drivers until something works.
I'd wanted to update the 2012 N7 to Lollipop.
Thoughts, anyone?
maigre said:
I can't access my N7 with adb (when booted) or fastboot (while in the bootloader). It's connected via a USB cable. This is both with a Mac and WUGS. Commands like fastboot devices or adb devices return nothing as the device isn't seen. I can connect my N4 and use those commands without problem. I just tried doing the same with my 2013 N7 and it's not being seen, either. Strange. I don't think I've had this problem before on the Mac. I have on Windows, which I can sometimes resolve by installing and reinstalling drivers until something works.
I'd wanted to update the 2012 N7 to Lollipop.
Thoughts, anyone?
Click to expand...
Click to collapse
Crazy as it sounds, try another USB cable. Reboot everything, plug in fresh, and try again. Failing that, use WUGS to reinstall all your USB drivers. Use the stock Google.
The cable was the culprit. I tried another and it worked. Thanks so much!
I'm having a similar problem that's driving me insane.
Nexus 7 wi-fi version
I've loaded every driver on the planet and in recovery mode it simply will not show up. And I'm not talking won't show up using ADB, I get absolutely nothing in device manager. So before anyone tells me to point to the device and manually change the driver, there is no device to try and point a driver to.
In "normal" mode, it shows up perfectly fine in Device Manager as Android ADB Composite Device. ADB will list it in devices with no problem. It will accept the "adv reboot recovery" command perfectly and reboot the tablet into stock recovery. The minute it does that, the device disappears from the Device Manager list and nothing takes it's place. I've tried to have it search for new hardware, I've tried the Google USB drivers kit, I've used Koush's Universal Driver install. I've used 3 different cables on 2 different USB ports.
This is a completely stock N7 running 4.4.4 plugged into a Windows 8.1 64 bit PC.
The last thing I'm wondering is do I have to unlock the bootloader at all? I don't want to because it'll wipe the tablet. If so I guess I'll just wait out the actual OTA rather than try to sideload it.
Any suggestions would be appreciated.
Yaz75 said:
Any suggestions would be appreciated.
Click to expand...
Click to collapse
Any suggestions at all?
Ummm... does the Stock Recovery actually run "adbd" by default? If it doesn't (or it doesn't start adbd until you execute the sideload menu item), then you wouldn't normally see anything on the other side of the cable with a stock Recovery. (I don't have my tablet with me to check)
Here's an extra "any suggestion at all":
Get rid of Windows and use Linux; there are no drivers to screw with in the latter case.
No, seriously. But probably not what you are thinking.
If you can get a "live CD" to boot** on your PC, you can (as root) run the "lsusb" command to see what devices are enumerated on the USB bus, port by port.
In conjuction with the decoder ring at the end of this post, you can determine from inspection of the USB VID/PID identifiers whether or not all the hardware is behaving, and whether or not the tablet is in the mode you think it is supposed to be in.
The reason this is valuable is that it allows you to take drivers completely off the table; if everything is as it should be, then you know that all the hardware and cabling are functioning correctly, the tablet is behaving correctly, your PC hardware is behaving correctly, and that 100% of the problem is Windows driver issues.
If you want to go the extra 1/4 mile, you can put a copy of (Linux) fastboot & adb plus your flashables on a USB key, and run adb or fastboot from the Live CD boot. It won't matter that the live CD doesn't have them preinstalled, they will be on your USB key. It will be easier on you if you can find statically-linked fastboot and adb binaries; if not you will have to copy one or two supporting shared libs (.so files) along with the binaries, and find out what LD_LIBRARY_PATH is all about.
suppose the USB key mounts at /media/usb1; then
$ sudo /bin/bash
# mkdir /tmp/tools
# cp /media/usb1/fastboot /media/usb1/adb /media/usb1/*.so /tmp/tools/
# chmod 755 /tmp/tools/*
# export LD_LIBRARY_PATH='/lib:/usr/lib:/tmp/tools:.'
# cd /tmp/tools
# ./fastboot devices
OR
# ./adb devices
Good luck; as you are using Windows you are going to need it. Hahaha LOL
**depending on whether your BIOS on your win 8.x PC can be toggled between UEFI and Legacy modes or not, this can be either trivial (Legacy boot mode) or complicated (UEFI) requiring a "Trusted Computing" crypto boot shim from MisterSoftie.
Ok this works for me
Use USBDeview (http://www.nirsoft.net/utils/usb_devices_view.html)
delete all the associated drivers like Google, Samsung, etc for ADB, etc
Restart Computer
Reconnect N7 without MTP and USB debugging
Wait for PC to recognise device and install driver
*If you see something like PC unable to recognise device, go into device and Update Driver and choose "Automatic....."
Disconnect and Reconnect with MTP and USB Debugging
Wait for PC to recognise device and install driver
Restart N7 in bootloader
Wait for PC to recognise device and install driver
Profit
* My PC OS is Win 8.1 Pro 64bit
make sure mtp is switched off, i couldnt get adb or fastboot on my nexus just now . switched off mtp and works fine
Hi guys...
Yesterday my new PH-1 arrived and today I wanted to use ADB with the app "custom navigation bar". My problem is: i can`t get it to work... I´ve used adb several times with different phones, but with the PH-1 it can´t connect with my Windows 10 computer. Is it possible that I can´t get it to work because Ì´m using a different USB-C cable (took 3 different from Xiaomi another manufacturer)?
How do get it to work? Everytime I connect the phone with the computer, I get the message USB debugging is on and I use MTP to work, but the phone doesn`t show the RSA key fingerprint. Any suggestions?
masterchief_2001 said:
Hi guys...
Yesterday my new PH-1 arrived and today I wanted to use ADB with the app "custom navigation bar". My problem is: i can`t get it to work... I´ve used adb several times with different phones, but with the PH-1 it can´t connect with my Windows 10 computer. Is it possible that I can´t get it to work because Ì´m using a different USB-C cable (took 3 different from Xiaomi another manufacturer)?
How do get it to work? Everytime I connect the phone with the computer, I get the message USB debugging is on and I use MTP to work, but the phone doesn`t show the RSA key fingerprint. Any suggestions?
Click to expand...
Click to collapse
Mines wouldn't connect using the usbc cable it came with I had to use a regular usb to usbc cable for it to work
See your device manager. To see if you are seeing "Mata". You have to download the google usb driver and update it from there
I have S8 from my previous computer but i need to re install the driver again
https://www.youtube.com/watch?v=LbAq6d2Du0U
You can also try this tuturial hope that it is working for you.
Try this > Download and install the essential usb driver > go to device manager and update the driver. Choose the option where you can change the source and select the driver in the list > go to the Essential Folder in Program Files and choose the file named "essentialadb.inf" for your pc. That should work
It's and old thread but if there is someone new to this...
My essential wouldnt work with the previous ADB i had installed that had worked fine with all my other devices.
I installed https://forum.xda-developers.com/showthread.php?t=2317790 and worked just fine. Make sure your device isnt connected as anything other than charging. The previous ADB i was using didnt acknowledge my device but on first try with Minimal i was prompted on my phone right away
I had the same problem when attempting to flash my ph-1, when trying to use the cable that came with the device. I used a standard USB-A to USB-C cable and everything worked just fine. I noticed on the 8.1 update notes for side loading that the team indicates that the cable that comes with the phone is "Primarily" designed for charging and not data transfer. So I'm guessing that it is of lower quality and doesn't handle the transfer speeds.
blackbms said:
I had the same problem when attempting to flash my ph-1, when trying to use the cable that came with the device. I used a standard USB-A to USB-C cable and everything worked just fine. I noticed on the 8.1 update notes for side loading that the team indicates that the cable that comes with the phone is "Primarily" designed for charging and not data transfer. So I'm guessing that it is of lower quality and doesn't handle the transfer speeds.
Click to expand...
Click to collapse
Hold either volume button while connecting cable from phone to pc, it will detect automatically. It may work.
Hi guys. Everything was fine yesterday. Ran Windows disc cleaner today and now when I plug in my phone into PC, the charging starts but Windows does not detect it/nor there is menu "file transfer/etc" popping on the phone.
- tried different cables (charges starts on all of them)
- Enabled USB debugging in Dev settings
- reinstalled ADB adb-setup-1.4.3.exe - and chose "Yes" on the prompt to install drivers. Install was successful, but no changes.
- Phone is not detected in Fastboot either.
Adb devices - device is not listed.
EDIT:
It just came back and working normally for now, without me doing anything else, just another re plug. Worrisome...
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"