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.
Related
I am working at an android studio project and I always work with my own physical device SAMSUNG S7. It always worked (for a few weeks now) but today suddenly from one moment to the other my device cant be recognized by android studio anymore. I didnt change any settings! I just changed a line in the code (like a hundred times before) and after it my device is not shown in the list of devices. There is only the virtual device which is useless for me because it never displays the app correctly. Just my physical device shows the app correctly so now I need help. Otherwise I cannot continue programming.
I tried to reopen android studio and restart my phone but it didnt help.
Changing the cable plug mode (credits to Hack06)
Just swipe down the OS status bar, and tap on the device, then choose another connection mode.
Installing Samsung's development drivers
When this doesn't work, try installing the drivers provided by Samsung to improve developments. These can be found here.
USB Debugging
USB debugging may have failed. Or all of the developer settings have been reset. Try that
Reboot your phone into ODIN mode
Caution:
ODIN mode is in charge for flashing your Android phone, and if you’re not careful, you can cause permanent damage to your phone.
This solution applies only to Samsung’s devices, since they are the only devices with access to ODIN mode.
A guide how to access ODIN mode for your phone can be found here.
Install KIES software
If nothing worked till here you might want to download KIES software.
KIES software only works for Samsung’s devices.
Samsung KIES is part of Samsung Smart Switch.
Download here.
Google - Android USB Driver
My last suggestion would be to install Google's Android USB drivers. An official guide can be found here.
This may sound obvious..
but sometimes it could be a cable issue
even if it's charging it could not transfer data
try a new cable
I am trying to create a React-Native app and I need to connect my device to troubleshoot some issues that only occur on the physical device and not the simulator. For some reason I have never been able to connect my Pixel 2 XL to my PC. I am running Windows 10 and I have tried all of the following.
Enabling developer mode and USB Debugging on my device.
Uplugging and replugging my device 20+ times in a row.
Changing the USB port I am using.
Changing the USB connectivity settings in Developer Options > Default USB Configuration. (Options are: File Transfer, USB tethering, MIDI, PTP, No data transfer) I've tried them all.
Restarting my device while it's plugged in
Downloading the Google USB Driver (in Android Studio).
Restarting my PC when the device is plugged in.
Updating my PC, and updating my device.
Checking Device Manager and trying to update the driver. (So the device used to show up with the yellow warning triangle next to it and trying to update the driver never worked. But now, the device doesn't even show up in Device Manager anymore)
Factory Reset my phone.
Downloaded Media Feature Pack for N and KN versions of Windows 10 (Suggested by the google tech support)(I called them)
I feel like I've tried everything previously addressed in every Stack Overflow question on this issue.
Finally solved the issue. The data cable was the problem. If you have tried all the steps above, and nothing is working, buy a new cable. This one works great and seems very durable for my Pixel 2 X: https://www.amazon.com/gp/product/B01N4OKUB8/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1
I had this issue too - my Google Pixel 2 XL is about 9 months old. Was developing an app, so using USB debugging to debug the app as I built it. One day it mysteriously stopped working, though no issues with charging. I tried everything, including using all the different USB ports on my laptop, with no luck.
I eventually gave up and started using the emulator on Android Studio, and since I didn't need data transfer for anything else, I didn't send my phone for repair or anything.
A few weeks later it just started working again, all by itself...
I don't think I did anything to fix it - the moral of the story is, if you don't need it urgently, there's a chance it might just decide to work again!
I've done a lot of research about rooting a device but I can not even come up to this point because my phone is not recognized by windows 8.1 at all.
My intention is to establish a usb-connection between an android-device(Samsung GT-I9506) and a pc in order to use it for phonegap. Some other devices properly work collaboratively with phonegap but this one seems to refuse all attempts.
Important points:
1. The device is charged up when connected to a pc.
2. Use-Debugging is enabled
3. All drivers are installed, furthermore it's a Samsung PC and Phone
A related topic is this one: USB connection issues
But unlike the problem in the topic above my phone does not appear in the adb-list when entering:
adb devices
I plugged my phone into another pc(Windows 8.1) as well where it was not recognized either.
Thanks in advance.
If your system installed Android ADB Interface Driver then only you can see your Device in IDE.
You can check that
Go to Control Panel
Go to Device Manager
And find Android Phone like
It turned out that the usb cable was the reason for broken communication between pc and phone.
Strange enough that this faulty cable was able to load the phone but unable to establish a communication channel to other devices.
And the moral of this story is a usb cable of a smarthphone might be faulty even if other electrial supplies are still intact.
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."
After a) growing tired of the slowness of the emulator and b) nearing the end of the development of my first android app, I decided to connect my old and forgotten Toshiba Folio 100 android 2.2 tablet to my Windows 7 development PC, in order to deploy my android app. The PC and tablet 'see' each other, that is, the PC sees the tablet as a disk drive. In the android settings I switched on the developer mode. I read through the many advice threads of this site concerning deploying the app to a real device. To start with, in windows explorer, computer, right click, manage, does not result in recognition of the tablet, except for Toshiba storage USB device.
In Eclipse I went to Run configurations, target tab,tried all the different radio buttons settings, to no avail. The devices view, same story. Eclipse does not see the tablet. I also tried some old Archos 48 mini tablet, again nothing.
What can I do?
Thanks in advance.
do you see it as an android device? open a command prompt and type "adb devices" make sure your tablet is listed there, otherwise you need to find some adb drivers for it, you may want to try the generic adb usb driver.
If you're seeing the device in explorer listed as a disk drive it probably means you have the wrong USB mode on the device. It's called different things on different devices, but on many devices it's referred to as "Charge Only" mode (or not mass storage mode). Also make sure USB debugging is enabled on the device.