I can't for the life of get adb to see my g2 on my mac. I've had adb detect other phones in the past. I have USB Debugging on. I connect the phone through 'Ethernet' It starts the daemon and then says List of devices and it's blank. It must be something so little that I'm missing. I've rooted via adb before on my mac with other phones so I'm pretty sure it works. Anybody have any suggestions?
not to sure about mac but on my pc only 2 out of 5 ports have adb. try a different port. not sure if that will work with mac
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 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.
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
I cant tell what im doing wrong, ive never had this much of a headache using ADB.
For the life of me i cannot connect to my device to run commands.
I can see the device and the serial, but its forcing me to connect over tcpip, and every time I put in the correct IP and port 5037 and it refuses to connect.
Device will authorize my PC, but that is it, and ADB will not run in USB mode and keeps asking me for the IP, which I can ping, but it wont connect.
Please help
What commands are you wanting to run?
And you are using the most recent USB drivers?
It sounds like the correct comm port is being used, as you get basic recognition, but I'd check anyway. Try a different USB port, maybe different PC.
Let us know.
Did you try adb kill-server then adb start-server?
I had an app I was trying to give privileges to, figured I couldn't but wanted to try anyway. That part kinda doesn't matter though because I cant get far enough.
I do have the latest drivers installed, tried 3 different ports but not a different pc.
I killed and restarted the server in USB mode, but then it says no devices connected and the phone disconnects and reconnects each time, and adb restarts in tcp/IP when it doesn't detect the phone
Hi all,
so i have got android installed on my switch but cannot seem to get the usb to work at all for ADB and MTP.
the switch does not show anything when it is connected by usb and it does not appear in device manager or adb on the host machine.
i have enabled developer mode and debug over USB.
i have tried to connect to ADB via the network but this lead to the authentication failing
does anyone have any ideas of what could be the issue?
I looked at lsusb on my Linux machine and it shows as a USB serial device, so I looked at the serial terminal and it doesn't print anything, so I guess you won't get USB to work, but you might be able to get WiFi adb to work but I haven't
Laurin Neff said:
I looked at lsusb on my Linux machine and it shows as a USB serial device, so I looked at the serial terminal and it doesn't print anything, so I guess you won't get USB to work, but you might be able to get WiFi adb to work but I haven't
Click to expand...
Click to collapse
Thank you that is greatly important stuff to know.
The issues I am having with ADB over network is that it requires the device to be trusted which first needs to be done over USB.
It could be done using root but I can not seem to enable root on this version of Android.
Roy8765 said:
Thank you that is greatly important stuff to know.
The issues I am having with ADB over network is that it requires the device to be trusted which first needs to be done over USB.
It could be done using root but I can not seem to enable root on this version of Android.
Click to expand...
Click to collapse
Just flash magisk, it's what I did and now I have root.