Has anyone else had issues trying to use an actual type c port on their motherboard? I have one on my Gigabyte GA-Z170N-Gaming 5 and when I'm using the type c port in Windows 10 with the supplied type c cable I always seem to have issues flashing images. If I switch to a type A (standard) usb 2 or 3 port and use a standard micro USB cable with a type C adapter everything works fine!
I'm using a USB C pci card with W10 Pro with no issues so far. What USB drivers are being used? I cannot get Google's driver to "install" for the Pixel C. Plugging N10, N9, N7 & N5 into any USB port gives me the device under Portable Devices in Dev Mgr and with ADB "on" a corresponding entry under "Android Devices" but the Pixel C only ever shows in Portable Devices and with USB C as "ADB Interface" under "Universal Serial Bus devices".
I'm using the Microsoft drivers. I just got a new Pixel, and I unlocked it using the Type C cable and no issues so far, lets see how everything else goes.
Edit: That lasted a whole minute hahah I just tried to flash TWRP and it failed due to an "unknown error". I plugged in a standard Type A to MicroUSB with a Type C adapter and it flashed perfectly. I'm going to change drivers and see if that fixes it.
Edit 2: Gigabyte doesn't seem to provide a USB 3.1 driver....
Related
I can't transfer files/push stuff to the phone though adb when the phone is plugged into the front USB. I find this strange as the front USB ports on my PC are USB 3.0. It's charging the phone but not allowing me to transfer files, which is extremely annoying. All of my other devices work in the front USB ports (USB flash drives, other Android phones via USB).
Windows 7 is basically not recognising it. Is this a driver issue?
Did you in stall drivers for your Nexus? Does adb devices return anything when the phone is plugged in? Drivers
I've now resolved it using those drivers, thank you!
Hello all, I'm having what I would like to call one of the weirdest cases of USB troubles.
For some reason unknown to me, my Galaxy Nexus will simply not connect to my computer's front USB 2.0 and USB 3.0 ports whatsoever. It will simply throw the "USB device not found" message and if I'm blessed with a unicorn's presence, it will connect and show my Galaxy Nexus's file system and disconnect whenever it wants, specifically when transferring a file to the phone. Awkwardly enough, this only occurs on OEM Samsung cables, both on the original cable that came with the phone and a new one that I just purchased off eBay a couple of days ago. I have used the cable that came with my ASUS Nexus 7 (first gen) and it connects perfectly. The driver will install successfully and hold a connection until I physically disconnect it. I even gave the cable that came with my HTC G2 a try and the same thing. However, I decided to test this on two other computers, a school computer and a Dell machine I have at home and both of those machines will hold a perfect connection with the Samsung cables. Although I haven't tested it yet, I'm sure it will connect just fine to my laptop and to the USB ports located in the back of the computer (directly to motherboard)
If it helps any, the computer that is having troubles is encased in a Fractal Design Define R4. I'm thinking it could be a faulty USB header but other devices such as my Nexus 7 and various USB flash drives have connected without any issues. I have used USBDeview to uninstall the Galaxy Nexus driver and I have unchecked USB debugging to "ensure" a clean installation. At this point, I'm lost between re-installing Win7 or calling Fractal for what could be a very specific issue against my Galaxy Nexus.
Anybody have an idea on how to solve this? Much thanks in advance!
leikamkei said:
Hello all, I'm having what I would like to call one of the weirdest cases of USB troubles.
For some reason unknown to me, my Galaxy Nexus will simply not connect to my computer's front USB 2.0 and USB 3.0 ports whatsoever. It will simply throw the "USB device not found" message and if I'm blessed with a unicorn's presence, it will connect and show my Galaxy Nexus's file system and disconnect whenever it wants, specifically when transferring a file to the phone. Awkwardly enough, this only occurs on OEM Samsung cables, both on the original cable that came with the phone and a new one that I just purchased off eBay a couple of days ago. I have used the cable that came with my ASUS Nexus 7 (first gen) and it connects perfectly. The driver will install successfully and hold a connection until I physically disconnect it. I even gave the cable that came with my HTC G2 a try and the same thing. However, I decided to test this on two other computers, a school computer and a Dell machine I have at home and both of those machines will hold a perfect connection with the Samsung cables. Although I haven't tested it yet, I'm sure it will connect just fine to my laptop and to the USB ports located in the back of the computer (directly to motherboard)
If it helps any, the computer that is having troubles is encased in a Fractal Design Define R4. I'm thinking it could be a faulty USB header but other devices such as my Nexus 7 and various USB flash drives have connected without any issues. I have used USBDeview to uninstall the Galaxy Nexus driver and I have unchecked USB debugging to "ensure" a clean installation. At this point, I'm lost between re-installing Win7 or calling Fractal for what could be a very specific issue against my Galaxy Nexus.
Anybody have an idea on how to solve this? Much thanks in advance!
Click to expand...
Click to collapse
Yeah it sounds like a faulty usb cable. I have cables too that just won't hold a connection. Make sure you have "usb debugging" checked though when you want to use adb.
What I almost always use these days is wireless adb connection.
Go to settings >> developer options and check "ADB over network". Then in a terminal on your computer, "cd" to the directory you keep adb or adb.exe and type "adb connect 192.168.0.3" (or whatever ip is listed in settings >> developer options).
7175 said:
Yeah it sounds like a faulty usb cable. I have cables too that just won't hold a connection. Make sure you have "usb debugging" checked though when you want to use adb.
What I almost always use these days is wireless adb connection.
Go to settings >> developer options and check "ADB over network". Then in a terminal on your computer, "cd" to the directory you keep adb or adb.exe and type "adb connect 192.168.0.3" (or whatever ip is listed in settings >> developer options).
Click to expand...
Click to collapse
Thanks for the steps in regards to wireless ADB connection. As much I really want to say it's a faulty cable, I can confirm that the cable will provide a stable connection to the Dell machine I have sitting around and on the school computers as mentioned in the OP. I even got 2 new OEM Samsung cables and neither of them work on the computer that gives me that message with the Samsung cables. It's so frustrating
Hi,
I got the USB type C to USB type A cable from Google.
My Pixel C charges fine over that, but I don't see the tablet on my Windows 10 computer.
Do I need to do something in the settiings for this to work. MTP?
Michael
drmichael said:
Hi,
I got the USB type C to USB type A cable from Google.
My Pixel C charges fine over that, but I don't see the tablet on my Windows 10 computer.
Do I need to do something in the settiings for this to work. MTP?
Michael
Click to expand...
Click to collapse
When connected to your PC, you should see an icon in the notification bar of your Pixel C titled "USB for charging." Click on this and change from "Charging" to "File Transfer."
rjmillenbaugh said:
When connected to your PC, you should see an icon in the notification bar of your Pixel C titled "USB for charging." Click on this and change from "Charging" to "File Transfer."
Click to expand...
Click to collapse
It was not there. After a reboot it was then there. All fine. Thanks.
Michael
Hello everyone,
I am fairly new to the USB-C world and was wondering why does my Samsung Galaxy S9 only charge when I plug it into my Windows 10 PC using a double sided USB-C (10Gbs) cable.
The phone does not give me an option to change the mode to data transfer.
PS:
The cable being used "USB C Cable, QacQoc USB C to USB C 3.1 Gen 2 Cable supporting 100W Power Delivery, 10Gbps Data Transfer, [email protected] Video Output Thunderbolt 3 Compatible for USB Type-C Devices, 1.2m"
Thanks in advance
enable Developer Mode (go to settings, about phone, then Software Information, then Build Number around 7-10 times (it'll say "X more clicks to enable Developer Mode" (or something like that)). Once Dev Mode is on, you can select "DEveloper Options" in Settings, then Default USB Configuration, and choose "Transferring Files"
Hello,
my new S22 is not visible in device manager so there's no way to enable file transferring, only charging works when connected to my Windows 10/11 PC.
Also the "USB for file transfer" notification below is not visible at all for me:
https://imgur.com/rr13tI9
I have tried with 2 different cables and 2 different PC (Windows 10 & 11).
File transferring works fine with S21.
I have tried enabling USB debugging, and installing the latest Samsung USB Drivers from https://developer.samsung.com/android-usb-driver
I have checked the "default USB configuration" is set to "Tranferring files" and *#08080# is set to "MTP + ADB".
Only "Link to Windows" (the problem with this is you can see only 2000 latest photos) and Samsung Dex works.
Is my brand-new phone defective ?
Daimie said:
Hello,
my new S22 not visible in device manager so there's no way to enable file transferring, only charging works when connected to my Windows 10/11 PC.
Also the "USB for file transfer" notification below is not visible at all for me:
https://imgur.com/rr13tI9
I have tried with 2 different cables and 2 different PC (Windows 10 & 11).
File transferring works fine with S21.
I have tried enabling USB debugging, and installing the latest Samsung USB Drivers from https://developer.samsung.com/android-usb-driver
I have checked the "default USB configuration" is set to "Tranferring files" and *#08080# is set to "MTP + ADB".
Only "Link to Windows" (the problem with this is you can see only 2000 latest photos) and Samsung Dex works.
Is my brand-new phone defective ?
Click to expand...
Click to collapse
This may sound stupid, but flip the cable over and plug it in. Yes, I know, it doesn't (or shouldn't) matter which way you plug in a USB-C cable. Not all USB-C cables are created equal.
I've had this happen to me. It wouldn't recognize my phone, but when I flipped it over and plugged it in, it worked.
I had to go through all of my cables to check for this. I tossed the ones that caused this phenomenon. It seemed to be all of my older cables I had purchased when I had a Note 8.
Use adb push and pull
gernerttl said:
This may sound stupid, but flip the cable over and plug it in. Yes, I know, it doesn't (or shouldn't) matter which way you plug in a USB-C cable. Not all USB-C cables are created equal.
I've had this happen to me. It wouldn't recognize my phone, but when I flipped it over and plugged it in, it worked.
I had to go through all of my cables to check for this. I tossed the ones that caused this phenomenon. It seemed to be all of my older cables I had purchased when I had a Note 8.
Click to expand...
Click to collapse
This didn't work. Tried flipping the original USB-cable.
mr.herbert said:
Use adb push and pull
Click to expand...
Click to collapse
The command "adb devices" returns 0 devices.
Daimie said:
The command "adb devices" returns 0 devices.
Click to expand...
Click to collapse
Is USB debugging on?
If so did you grant the computer authorization?
My USB-C -> USB-C stopped being recognized, hade to go with USB-C -> USB for computer to recognize it again. Device is S22 Plus.
Solved! I tried a 3rd cable and it started working.
So my original S22 USB-C cable is faulty, as only the charging works.
Yes, my S22 also works with only few cables (I have tried like 10pcs including completely new ones and like 1/3 is working). Samsung is restricting from using other cables for other purposes then charging. Its not the cable fault. They are working with other phones and charging S22 properly. Its just something between heaven and hell why Samsung is trying to f*ck us and make our daily lives more complicated...
Daimie said:
Solved! I tried a 3rd cable and it started working.
So my original S22 USB-C cable is faulty, as only the charging works.
Click to expand...
Click to collapse
Do you know what brand and model cable you got working?
What specs the proper cable should have? Having the same issue.
Having the same issue. And adb connect <ip>:5555 also refused for my case