Develop Reference

How to Connect Pixel 2 to ADB

I have a Pixel 2 that is unlocked and has USB debugging enabled. Yet if I plug it into my computer, it only ever shows charging. The USB cord works to connect other devices for data transfer no problem though, so it's not the cord. I have no trouble connecting any other devices to any of my ports, even the original Pixel. I am running Windows 10 pro. The Pixel 2 connects fine to an older computer running Windows 10 pro. I have Android Studio 3 and the usb driver from Google tools. If I go into device manager and click on the Pixel 2, it says I have the most updated driver if I try to update. I have tried disabling and reenabling USB debugging, revoking permissions, etc. Nothing causes it to do anything other than charge. There is no pull-down menu either to select different options.
How can I get my Pixel 2 to be seen by my computer?

I had the same issue connecting my S7 Edge to my MacBook Pro running Android Studio. Make sure that you have the "USB Configuration" setting in the Developer Options to be set to "MTP" ("PTP" on newer phones).
One last ditch effort, a lot of the times when my phone would not show up, switching USB ports on my computer would work most the time. I am very unsure as to why it would, but it would. I thought this was just my situation, but it's worth a try on your end.

Plug cable into device by interchanging upside down. This is hilarious but it worked for me.

I had the same issue connecting my Google Pixel 2 to my Android Studio and this works for me:
Settings -> Connected devices -> USB -> Transfer files (otherwise it's only charging your phone by default)
Settings -> System -> Developer options -> USB debugging (turn this on)
A question prompts up and you need to allow your computer to see your device
lo and behold, my Android Studio can see my Google pixel 2.

My problem ended up being that my Pixel 2 wouldn't connect to my MacBook Pro when using a USB 3.0 cable. It would charge fine, but the mac wouldn't detect it (in any USB Configuration) and the trust device dialog or USB debugging notification never appeared on the device.
Using a chain of cables/adapters that included a USB 2.0 component fixed the problem, e.g. Pixel 2 -> USB-C to USB 2.0 cable -> USB to USB-C cable -> MacBook.
It doesn't appear this problem (and solution is limited to just me

I tried all of the above, several times over the last few months and the only way I am able to get it to work (temporarily) is to reboot my MacBook Pro. It will work for the rest of the day, until I sleep the MBP again.

After my Pixel 2 updated to Android 9, I had to clear the cache of the Media Storage app for my phone to be recognized by my computer / have my phone recognize it was connected to a computer.
My phone has to be plugged in at Windows 10 startup time for this to work.
I connected my phone with USB-C and restarted Windows 10.
In Android,
Search Settings for Media Storage
App info -> Storage -> Clear Cache
Phone prompts me (immediately in my case) with 2 notifications, 1 notification that USB Debugging is enabled (follow steps from this answer), and 1 notification that it is charging.
Tap the charging notification for more options. What I see by default worked for me. I see "USB controlled by: This device" and "Use USB for: No data transfer" (Selecting "File transfer" also works for me)
In Windows 10's Devices -> Bluetooth & other devices -> Other devices, I now see Pixel 2 (Or "MTP" if I had selected "Use USB for: File transfer" in step 4.
The first time you do this, Windows should have sent a notification that the device is being set up (I assume it installs the drivers).
I can now see my Pixel 2 as a connected device in ADB.
Solution based on this thread:
https://productforums.google.com/d/msg/phone-by-google/JlooQqANO2A/d_n-MGIHAgAJ

For debian/ubuntu only
If you try to use the adb in {your sdk location}/platform-tools/, you will see the message
no permissions (user XXX is not in the plugdev group); see [http://developer.android.com/tools/device.html]
Turns out, you should be using another package with some custom rules of some sort (I have no idea what plugdev group means), and basically you just have to
apt-get install android-tools-adb
and use that adb instead.

Android devices no longer recognized by PC following Windows update

Yesterday my PC (Windows 8.1) performed an automatic update and now my android devices (a Samsung s4 mini and Samsung Note 8.0 tablet) are not being recognized by Android Studio or Windows in general when plugged in via USB. I have tried the devices on other PCs as they work as normal.
When I plug the devices into the computer I see a charging icon on the phone but no notification of USB connection and no option for selecting between camera and MTP device. The devices also do not appear in Device Manager (not even as unknown devices) or as storage drives in explorer. I attempted to do a system restore but the restore point failed when I tried to launch it and then deleted itself. Re-opening the restore tool now shows that there are no restore points and that the memory allocation for restore points had suddenly been set to zero (perhaps I have a virus).
The USB ports work for other devices, such as USB drives. I have tried plugging the Android devices into a variety of ports with no success. I have also tried different cables. I use the devices for development, so USB debugging is switched on.
Is there any sort of process that is typically launched by Windows that allows an Android device to be recognized? I am trying to understand what may have happened here and how to fix it. Google searches are turning up nothing without being able to see the devices in Device Manager.
Many Thanks

Unbelievably, I tried a fourth USB cable and connectivity is back. I didn't realize there could be so much variation in a cable.

Google Pixel not found in Android Studio

Having trouble with Android Studio connecting to my Pixel phone. I'm sort of out of ideas and am looking for suggestions. I feel like I'm missing an obvious step.
Things I've done:
Made sure developer options is on with USB debugging on.
Have tried switching from MTP to PTP.
My computer recognizes the Pixel just fine under windows 8.
Made sure android studio is up to date including "Google USB Driver" installed under SDK tools.
My previous phone (Droid mini) connects just fine.
Tried different USB ports for the cable to my phone.

Encountered this problem today as I tested on other people's phones. I found 4 possibilities why a device may not be recognized:
Case #1: The USB cable supports charging but not data transfer.
Case #2: Developer options haven't been enabled on target phone (see: https://www.verizonwireless.com/support/knowledge-base-215055/)
Case#3: Developer options enabled, but USB debugging hasn't been enabled. Go to Settings > System > Developer Options > USB Debugging
Case #4: Some (but not all) phones require MTP transfer mode to be enabled. It can be enabled by sliding a finger from the top of the screen and tapping "Android system - USB charging this device" > Tap for more options > Transfer files.
Hope this helps someone ^_^
EDIT:
It's come to my attention that there's another possibility. I don't know what causes this, but if you get really stuck, sometimes you need to go into Settings > Developer Options > Debugging > Revoke USB debugging authorisations. This will reset your device USB pairing fingerprint which will often bring the phone back as a device target in Android Studio.

In Pixel devices USB debugging is enable when:
Step 1. Enable Developer Options to double tap on Build Number, you can get it by search with build in setting.
Step 2. Enable USB debugging Option, to enable this just to search usb debugging in settings.
Step 3. Pixel devices require USB tethering mode to be enabled, It can be enabled by sliding a finger from the top of the screen and tapping "Android system - USB use for " > Tap on USB tethering.
After completion of all these steps you will be able to use you pixel device as enabled for debugging in SDK.

Android Studio / SDK Manager will provide the driver but Windows might not automatically install it for your device. Try checking the device manager, unplugging and reconnecting the device or let the device manager search for new hardware.
The driver (when installed via SDK Manager) will be found by windows when provided with the SDK root directory, usually AppData/Local/Android/sdk

I have had the same trouble with my Google Pixel 2 (Android 9); I couldn't connect it to ADB in Android Studio 3.3. In my special case, AS runs on Kubuntu 18.04 in a VMware Workstation on a Windows host.
I have to do following steps every time I want to connect the phone (the phone is already in developer mode):
Plug phone via USB into the computer (and connect it to the VMware guest, if you use it)
Phone: Swipe down the notification bar, there should be a message 'Charging the device via UDB'
Tab on it and change the 'Use USB for' from 'No data transfer' to 'File trasfer'
You can activate 'USB debugging' on your phone's developer screen before or after this procedure, both works for me.

That happened to me with a generic Type C to USB Cable (White Cable in the Picture Attached). Then I bought another Cable (The Black one in the Picture Attached) and it worked perfectly. It was the Cable. Make sure to have one that says "Data & Power".
Hope it helps!

The solution to device not found when running adb devices from windows 7 standard terminal for my Pixel 4a 5g was to simply update my google USB drivers. https://developer.android.com/studio/run/win-usb

If dev options aren't available, double click the build number until a notification appears stating dev options have been enabled.

samsung android usb device disconnect reconnect constantly windows 7

When I connect samsung tab s2 to pc windows 7, initially windows does not recognize usb device, or MTU driver failed install, many error.
I uninstall all other usb driver, still has problem.
samsung android usb driver, unknow device, usb device disconnect constantly
MTU usb driver, not installed properly.
not sure what is the cause.
=============================================
Updated:
The problem solved by Buy a non-samsung, non-OEM cable.
This this so bad, that samsung OEM cable is the reason of all trouble.
I end up spend $10 buy any brand(except Samsung) cable on amazon.

samsung android usb driver, unknow device, usb device disconnect constantly
MTU usb driver, not installed properly.
Samsung OEM micro usb cable is the ultimate cause, when you move or touch the cable around, it get disconnected, device manger constantly refreshing, constantly scan for hardware change.
Replace Samsung OEM micro usb cable with any other brand will fix all problem.
==========================================================
For my HP Desktop.
1) repeat press F10 when power on, get into BIOS configure.
2) on top menu - advanced - device option - USB 3.0 support (enable it), default is disabled.
3) sometime device manager refresh scan for hardware change, then unknow device,
this is because windows install driver from windows update, should disable it, should let windows install driver from samsung driver folder only,
Disable Searching Windows Update for Device Drivers
Click Start, right-click Computer, and then click Properties.
In the Tasks list, click Advanced System Settings.
On the System Properties dialog box, click the Hardware tab, and then click Windows Update Driver Settings.
Select Never check for drivers when I connect a device.
Click OK twice, and then close the System dialog box.
I believe this is the real cause for all trouble, such as MTU usb driver not installed properly, samsung android device not recognized by PC, android usb device constantly disconnect and reconnect and failed to recognized. etc.....
if you use android simulator, must enable bios vt-x visualation technology from bios
bios - security - system security - visualation technology - enable.
Leeds VT enable.jpg
below are try may not be the cause.
=====================================================
try:
1) remove previously installed blue tooth usb device. (or SD card), they may be the problem.
2) remove google androic studio ( maybe problem )
3) unplug internet. ( I see samsung continuing removed add, remove add, not sure if computer keep removing hardware)
=========================
windows, device manager, 'scan for hardware change' constantly , android device disconnect constantly,
Scroll to the right and type 'Power Options' in the search field and click on it.
Click 'Change plan setting' on your chosen plan.
Click 'Change advanced power setting' on your chosen plan.
Find 'USB settings' and open.
Find 'USB selective suspend setting' and change it to disabled.
This fixed ALL my USB 3.0 issues. Not mentioned anywhere else!
Its a BIOS ISSUE. Hopefully your computer has this option.
Go into your BIOS and TURN OFF "Legacy USB Support".
If you want even more speed, (there is a catch), Switch from "quick remove" to Buffering. BUT YOU HAVE TO DISCONNECT THE DRIVE WITH THE REMOVE USB DEVICE OR POWER DOWN THE COMPUTER FIRST.
hey guys here is the fix if you are having trouble with your Windows 8.1 all USB devices keep disconnect / reconnect with power saving off ... this took me two days to try to figure out what the heck was going on so i luckily found the fix hope this saves you alot of time an you dont have to downgrade to windows 7 if you love windows 8.1 good because its not what virgin of windows you have it dosnt matter what OS your on its clearly your BIOS so i suppose many people having this problem has an ASUS motherboard so heres the fix
restart your computer an go into your BIOS Press F2 repeatedly or THE DEL Key for those who dont know how to go to BIOS
2.Go into Advanced mode in your BIOS by clicking F7 on keyboard
3.Go to Advanced Tab Scroll down to USB Configuration Scroll down to XHCI Mode yours Will probably be on Smart Auto or Auto so Disable it Completely an Save changes F10 an click yes an exit it will auto restart your computer an BOOM You have Fixed the Problem by simply reading this post Hope this helps guys

my samsung tab s2 and tab pro 8 can't connect to pc windows 7. device manager showing unknow device, device manger constantly refreshing. I try million way, find out Samsung OEM micro usb cable is the problem, I replace it with other brand from best buy, all problem fixed.

I had exactly the same issue, and I think it is related to actual motherboard driver (Windows 8, 10). I have several android devices and all of them are connecting/disconnecting every 1-2 sec.
Things I did:
My BIOS doesn't have any configuration to switch USB 3.0 support
From Power Options USB selective suspend setting set to disabled (didn't fix the issue for me)
In Android dev options change USB configuration to MTP (also didn't fix the issue, as it was automatically switching back to Charging after ~10 attempts to connect)
Fix:
Disconnect all USB devices. (very important as disable operation might not be available)
Open System Properties -> Device Manager
Disable USB Root Hub (USB 3.0)
Disable Intel(R) USB 3.0 eXtensible Host Controller - 1.0 (Microsoft)
Connect your usb devices including android
Enable Intel(R) USB 3.0 eXtensible Host Controller - 1.0 (Microsoft)
Enable USB Root Hub (USB 3.0)
Btw it works fine on windows 7 before it makes updates to motherboard drivers, usually after first updates you can see that usb 3.0 driver support is enabled, and same issue appears.
Hope that will help someone.

Discovered a random weird solution that worked for me (Windows 8.1, Samsung Galaxy A20, Dell Lattitude laptop). The A20 uses a USB-C connector which, supposedly, is non-polarized unlike earlier versions of USB. I flipped the cable over in the phone and the problem went away. Go figure... It probably is a mix of MB hardware, drivers, and who knows what else. Users are on their own as standards evolve.

samsung mobile mtp device failed to install

I am trying to test my android application on a samsung s2 phone with android version 4.0.3, I downloaded the usb driver from the official website, but the program does not detect the phone, returning a message telling me that samsung mobile mtp device failed
any help please?

Hi I have followed the Exact steps from Link : http://androidforums.com/samsung-galaxy-s2-international/559858-samsung-mobile-mtp-device-cannot-installed.html
Here are steps : (for Windows specific instructions):
Ensure phone is not connected to PC.
Uninstall KIES from PC. Reboot your PC and Reinstall KIES after that. Just for great measure... open KIES, go to Tools | Troubleshoot connection error. Follow instructions and wait for it to finish the troubleshooting procedure.
Reboot your phone (or turn off and then on your phone again). Do not connect it to your PC just yet.
Once rebooted, go to your phone's dialer, type *#7284# - A configuration window will appear. In that window's USB section, if it's default to PDA, tap MODEM, then back to PDA, (if it is MODEM in the beginning, change it to PDA) then press the back key to exit. Most importantly, it must set as PDA when you exit.
Turn off USB debugging in your phone.
(Optional) Set your phone's screen timeout to a lengthy time. (minimum 1-2 minutes - recommended 5mins to 30mins) its found in Settings | Display. You can change this back later on.
Connect the phone to your PC with USB cable and let windows load your drivers... and wait for the drivers to get reinstalled.
Once reinstalled, disconnect the phone off USB. Switch USB debugging back on in your phone settings, and reconnect the phone back - you'll see windows load another set of drivers for your phone. Wait until it is completed. (This step is a precautionative measure to ensure your phone is identified with all the necessary drivers)
Once complete, unplug your phone, and turn off USB debugging... This is to ensure MTP will initialize. Also, press the phone's home key until your homescreen is displayed. Only after doing all that, reconnect your phone back to PC.
Test and see if MTP works using Windows Explorer. You'll see your phone's USB storage and SDCard contents if it does.
This definitely helped me after 2 days of googling..... Hope it will help others too....

I had to use a slightly different procedure with my SCH-S738C Samsung phone. Here are the steps I took to get the phone communicating with Windows XP:
Ensure phone is not connected to PC.
Uninstall KIES from PC. Reboot your PC and Reinstall KIES after that. Just for great
measure... open KIES, go to Tools | Troubleshoot connection error. Follow instructions
and wait for it to finish the troubleshooting procedure.
On your SCH-S738C Samsung phone type into google search: [root SCH-S738C]. This will
bring up the following web address:
http://forums.droidbeans.com/tutorials/(how-to)(root-micromax-qualcomm-phones-without-pc)/?action=thankyoupostlist;msg=813
then navigate to this address.
On your SCH-S738C Samsung phone select the poot.apk from the spot on the page that
reads: Download poot.apk.
Follow the rest of the instructions on the web page, which are:
1) Download and Install poot.apk
2) Now open the poot app then it will require you to install Ministro II, Simply
follow the link to Google play store.
3) Then you will be required to update ministro library, please update it.
4) Once you updated the Ministro Library then you will be faced with two options;
1. “Press here to Poot”
2. “Built in root check”
5) Click on the first option which is “Press here to Poot” and after a while,
You are going to face with three options.
1. Get Superuser
2. Get root-checker
3. In-built rootchecker
When you see these options it simply means your phone has been rooted
successfully. Then click get Superuser to complete the process..
6) And finally do a reboot to take effect :P
7) Congrats you have rooted your phone now
Ensure Samsung Kies is running on your Windows XP machine.
Connect the phone to your PC with USB cable and let windows load your drivers...
and wait for the drivers to get reinstalled.
I was now able to stop Samsung Kies and just use Windows XP File Manager to load and copy files to and from the SCH-738C Samsung phone.

I had similar problem with Samsung devices when I installed fresh Windows XP. I figured out that I cannot install "SAMSUNG Mobile MTP Device Driver" over Windows update site so I:
Download drivers from
http://catalog.update.microsoft.com/v7/site/ScopedViewRedirect.aspx?updateid=523dde6f-6efb-47ac-9aac-8f53732e45c9
Connect device to the PC
When Windows notifies about new HW I installed drivers from downloaded package (for USB, MTP etc)
adb works fine but still device was not visible over MTP so I installed Windows Media Plaery 11 over Windows Update
That solved the problem. WMP 11 is required for the MTP mode. Otherwise Samsung Kies would be helpful.

Go to Samsung Kies software, on top left of the window, click the menu > Driver recovery.
Let it reinstall drivers
After driver installation finished, go to your phone, Settings> Application > Development, tick USB debugging mode.
Under USB debugging mode connect your phone to the PC with USB.
It installs correctly!
Disconnect from PC
Untick USB debugging mode
Connect again