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.
Related
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.
I have tried EVERYTHING I could find on this but still no solution.
I have a Samsung s6 edge Plus 32 GB. I am trying to deploy an app on Android Studio but it always shows the device as offline. What I have tried
Unplugging and plugging back
Restarting device
Enabling debugging on device
Shuffled and tried different transfer protocols
Installing and Uninstalling Samsung drivers
Checking 'Enable ADB integration' under Tools -- Android
Checking android studio & driver updates
Any help will be greatly appreciated
This happens sometime, even when USB Debugging is on. Try this:
Go to Settings->Developer Options
Search for Revoke USB Debugging Devices
Revoke all existing devices
Disable USB Debugging and enable it
Now connect your phone to system with USB cable
Wait, and a dialog will appear on your phone, for permission to allow for USB Debugging. Click on checkbox and press Allow.
Now the device should appear online in Android Studio.
If problem still persists, then problem is with your phone drivers installed on system.
This happens to me regularly (I use multiple devices) and one of these two things always fixes it:
Make sure your device has "only charge" selected in the dropdown menu entry that appears when you connect your phone. Instead select "transfer files".
Disable and enable usb debugging.
Change your device cable or change your connection USB port on PC. I think this problem is hardware problem. Try other hardware problem possibilities.
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.
I can't seem to connect my Samsung Galaxy Note II (N7100) to my Windows 8 Machine (aiming to use the phone for debugging - but current can't even connect the device as mass storage). No USB notification is shown when connecting the mobile by cable.
Things I have checked thus far:
USB Cable (works on different machine and with HTC phone)
USB Ports (tried different ports, 2.0 and 3.0, all working)
PC USB Drivers
Phone (connects to my Win 7 machine)
Samsung Kies (and Samsung driver) and Google USB Driver both installed
PS. The reason Im asking this here is because I'm aiming to use the phone for development and I'm hoping to get some answers that aren't "have you double checked the cable?" like on every Google search I have performed so far. Hopefully another developer recognises this issue.
OK. so You've obviously done the basics and made sure all the cabling is functional.
it sounds like the Volume is not mounting in windows 8
if it's not detected in Windows Device Manager, and More importantly, if it's not visible in Disk Management, then the volume simply is not Mounting.
I would suggest
Try connecting to a Windows 7 Machine and see if it works, if it does, Then Most likely you need Windows 8 Drivers
I would be contacting Samsung Engineers for support on the Issue
What version of Kies are you using
i found this that might be useful for you
Ultimately, as you know the volume is not mounting due to Driver issues, and this needs to be resolved if you are to have a solution
You could always Try setting up XP Mode in Windows 8 and see if it recognizes that way.
Granted this is a bit of a workaround and a bit stuffy, but. Hey, it's another option.
let me know how you go
Go to dial pad & type *#0808#
It displays USB settings
Select MTP+ADB option
Press OK button
Connect to USB cable to PC
It shows Connected as a media device."
I've tried everything, when I run 'adb devices' on my new HP Envy Windows 8 laptop I get a blank 'list of devices attached'. I've reinstalled the USB driver for the phone (Samsung Galaxy s3), I've set it to developer settings. The only clue as to what is wrong is when I performed troubleshooting on the hardware and devices control panel it said I have USB 3.0 ports and a USB 2.0 device. Though I read that the ports would be backwards compatible. Any ideas?
2014-April: I agree this is an issue with Windows 8 / 8.1 and this approach was only successful by happenstance.
On my Win8.1 system, even with Samsung's official driver installed (see link below), my SGH-I727 Galaxy SII Skyrocket would not connect over USB - neither with MTP nor PTP enabled on the device under Settings > Storage > [press menu] > USB Computer Connection.
I ended up doing the following, while the phone was untethered, and after installing the Samsung driver:
Open an elevated CMD prompt, if logged in as a non-admin
Type: set devmgr_show_nonpresent_devices=yes [press enter]
Launch DEVMGMT.MSC
Clicked VIEW > enabled SHOW HIDDEN DEVICES
Expand Universal Serial Bus controllers
Right-click uninstall all entities that appeared in gray [gray = not present]
Expand System Devices and repeat removal of non-present devices.
[NO REBOOT WAS REQUIRED at this point]
Plugged the phone into a standard USB port - still unresolved
Plugged the phone into a USB 3.0 port - device was recognized and installed itself
There is now an entry under Universal Serial Bus controllers named "SAMSUNG Mobile USB Composite Device". The driver tab for that entity is dated 02-Jan-2014 with version 2.11.7.0 from "SAMSUNG Electronics Co., Ltd." Note this version is different than the one downloaded directly from Samsung (see link below) which is 1.5.14.0.
There are now also two new entries under Portable Devices: "MTP USB Device" which is presently gray despite the device being currently connected, and "SAMSUNG-SGH-I727".
Windows Explorer now shows a device named "SAMSUNG-SGH-I727" and, when opened, shows both "Internal Storage" as well as "SD Card" directories.
ALSO NOTE that the phone has to REMAIN UNLOCKED, in order for Windows Explorer to provide access to the aforementioned directories. Most smartphones will block access to these directories, when the phone's interface is locked due to your security preferences. In other words, ensure you swipe or enter your passcode and remain seeing your phone's main screen, while trying to view its directories via tether.
Samsung Driver [version 1.5.14.0]:
www.samsung.com/us/support/owners/product/SGH-I727MSAATT
Are you mounting the device as a camera?
In other words, head over to Settings > Storage > "Usb computer connection" (via the ActionBar) > Camera (PTP).
Make sure the Samsung drivers are installed. Power off your phone. Power on the phone in Download mode. (Volume Down + Home + Power) Press Volume Up to continue. Once it's in Download mode, plug it into your computer. Windows should now discover it and load the driver. Once this is complete, unplug the phone from the computer, and pull the battery out of the phone to get out of Download mode. Replace the battery, and power on the phone like normal. It should connect to the computer properly.
this from this thread
http://forums.androidcentral.com/verizon-galaxy-s-iii/286104-s3-wont-connect-via-usb-my-computer.html
the problems will be related to the driver i face problems like this with my android device connecting to my pc
I had a similar problem (samsung note 3, hp win 8.1). When plugged in, the phone would constantly connect and disconnect. I tried 3 things - delete the whole driver from device manager (did nothing), swap from USB 2.0 port to usb 3.0 port (may have been part of getting it working) and changing one drive settings.
One drive has a setting to sync data across all devices. It appears that windows trying to grab sensitive data from the phone was causing it to reset the connection. When I turned that off I got a stable basic connection.
I may be the only one, but I am creeped out that MS takes every opportunity to behave as spyware.
Good luck, I hope that helps