Hi,
I'm using this CM 11 http://forum.xda-developers.com/showthread.php?t=2922500 but I have strange problem with my laptop. It periodically looses driver information for my device. I don't know how but when I re-installed my OS Windows 7 (32bit) it found the proper driver. Later I've got a message that my USB device is not recognized and can't connect to my device. Does anyone else have the same problem and do you know a fix? I've tried a lot and different driver versions but without success. Logcat doesn't show anything last time but I will try later or when I loose drivers again (it seems I cannot use USB again).
BTW I don't have this problem with my desktop PC which has always connected USB cable to it. Also everything works fine with CM 10.1, MIUI or Sense ROMs but they are based on lower Android versions.
P.S. I was trying to connect with another USB cable. I've found my cable that I used to install drivers and USB is working again. This is really strange behaviour
Logcat from device terminal
Logcat when plug in or out my USB connector is attached.
Use this tool
http://forum.xda-developers.com/showthread.php?t=2588979
Related
Hi, just received my Surface Pro yesterday and its amazing Anyways, I've been installing all my normal desktop applications as I would do with any other new PC. Today, I tried to install drivers for fastboot so I can flash custom kernels on my Xperia S. I managed to get the fastboot and ADB drivers installed correctly by disabling driver enforcement, but every time I connect my phone in fastboot mode to my Surface, Windows says the last USB device connected has malfunctioned.
I've read that other people are having problems with Windows 8 64bit and installing drivers, but I've managed to do that without problems
I've also read that you should plug your phone into a USB 2.0 port because it won't work with USB 3.0 ports yet but since the Surface Pro has only one USB 3.0 port, I haven't had the chance to try that.
I wonder if there is an adapter that changes USB 3 to USB 2? Maybe this could solve the problem?
Has anyone managed to get fastboot for any android phone working successfully on their Surface Pro?
Thanks in advance.
You could possibly try a USB 2.0 hub to degrade the USB 3 port to a USB 2 port.
netham45 said:
You could possibly try a USB 2.0 hub to degrade the USB 3 port to a USB 2 port.
Click to expand...
Click to collapse
Thanks for the reply, I've actually already tried that. It seems to me that Google need to update their SDK for USB 3.
ttiimm said:
Thanks for the reply, I've actually already tried that. It seems to me that Google need to update their SDK for USB 3.
Click to expand...
Click to collapse
I doubt that it is a USB 3.0 problem as I have USB 3.0 ports only on my laptop and have had fastboot working no problem, as well as adb for my nexus.
It sounds more like you are having driver problems and not usb port problems. I have not tried using fastboot yet on my win8 asus tablet but I should try that today.
goofball2k said:
I doubt that it is a USB 3.0 problem as I have USB 3.0 ports only on my laptop and have had fastboot working no problem, as well as adb for my nexus.
It sounds more like you are having driver problems and not usb port problems. I have not tried using fastboot yet on my win8 asus tablet but I should try that today.
Click to expand...
Click to collapse
Same thing on my Surface Pro. The problem lays in BOTH: the USB 3.0 driver and the Windows 8. There are tons of posts regarding not working many devices on USB 3.0 and Win8 (I'm not sure if it's only in x64 or x86 as well).
Anyway, I'm also stuck with not working fastboot (ADB works good). There is a tutorial how to install unsigned Intel driver but Microsoft's engineers geniuses didn't enabled USB keyboard in Startup Settings so I can't navigate and disable that specific option (I'm using 3rd party keyboard so I guess those morons punish me for that ).
I'm loading a ROM on this Nexus S i9020A. I have unlocked the bootloader and flashed CM 5.0.2.0.
When I boot into recovery, the Windows 7 host reports "This Device Can Perform Faster" and recommends moving the phone to a different port. However all ports on the computer are USB 2 or USB 3. I have tried other ports just in case and I get the same warning.
When I try to download files with ADB PUSH, it takes forever (5-10 minutes), indicating that it is probably running at USB 1 speeds.
Windows Device Manager reports that it is using the "Android Composite ADB Interface" as the USB driver for the phone.
I have performed a ROM update using the same procedure on another Nexus S on the same computer with the same drivers, and I did not have this issue.
Why does this happen, and how can I solve it? Is there something wrong with the phone or its USB port?
As a workaround, it seems to be possible to unplug the USB cable and plug it back into the same port. In the few times I tried it, it would correctly connect at full speed. There must be some timing issue when the USB port is initialized in CM Recovery that causes the problem with Windows.
I have an SCH-i535 running CM-11, M3-SNAPSHOT. My desktop is running Linux Mint 16 in one partition and Win 7 in another.
I cannot get the phone to show up when plugged into a USB hub. It isn't simply that MTP is not working, but that the USB connection doesn't even show up in dmesg. I have android debugging turned on and have tried to connect via adb in recovery also. In no situation have I been able to establish any sort of USB connection since changing to M3. Setting/toggling MTP under settings>>storage>>menu>>USB computer connection also fails.
I have also tried to connect from my Win 7 partition and nothing shows up at all.
Does anyone have any suggestions other than going back to 10.2?
polymath257 said:
I have an SCH-i535 running CM-11, M3-SNAPSHOT. My desktop is running Linux Mint 16 in one partition and Win 7 in another.
I cannot get the phone to show up when plugged into a USB hub. It isn't simply that MTP is not working, but that the USB connection doesn't even show up in dmesg. I have android debugging turned on and have tried to connect via adb in recovery also. In no situation have I been able to establish any sort of USB connection since changing to M3. Setting/toggling MTP under settings>>storage>>menu>>USB computer connection also fails.
I have also tried to connect from my Win 7 partition and nothing shows up at all.
Does anyone have any suggestions other than going back to 10.2?
Click to expand...
Click to collapse
I was having a similar issue, I followed the instructions in this post and it fixed the issue:
http://forum.xda-developers.com/showpost.php?p=47140274&postcount=11732
yoda2nd said:
I was having a similar issue, I followed the instructions in this post and it fixed the issue:
http://forum.xda-developers.com/showpost.php?p=47140274&postcount=11732
Click to expand...
Click to collapse
I did not have an issue with the M7 snapshot. I have not yet tried for the M8.
Afternoon all,
Have been out of the rom'ing scene for a while...
I have a number of devices (Galaxy Tab 2 10.1 and Nexus 7 2012, to be exact), that I want to flash a new ROM onto (the Tab's stuck in a boot loop, the N7's due for Dirty Unicorns Nougat Rom).
All pretty straight forward - I've done it in the past - BUT...
Can I get Windows 10 to even *see* new hardware's been connected, let alone recognize it?
Can I fook
To confirm, I plug the USB between the PC and the device, and all that shows this is connected is that the device realises it's being charged, no "ding ding" from Windows, no USB confirmation from the device...
Both devices have USB Debugging enabled.
Have tried different USB cables
Have tried different USB ports
Have tried - many! - different USB drivers, including that from both Asus and Google's own dev kit.
Have ADB installed, "adb devices" shows no devices (blank).
The thing that's really pi**ing me off is that this is such a basic thing to be stuck by, I really cant figure out what I'm missing!
Any help appreciated gents...
cy80rg said:
Afternoon all,
Have been out of the rom'ing scene for a while...
I have a number of devices (Galaxy Tab 2 10.1 and Nexus 7 2012, to be exact), that I want to flash a new ROM onto (the Tab's stuck in a boot loop, the N7's due for Dirty Unicorns Nougat Rom).
All pretty straight forward - I've done it in the past - BUT...
Can I get Windows 10 to even *see* new hardware's been connected, let alone recognize it?
Can I fook
To confirm, I plug the USB between the PC and the device, and all that shows this is connected is that the device realises it's being charged, no "ding ding" from Windows, no USB confirmation from the device...
Both devices have USB Debugging enabled.
Have tried different USB cables
Have tried different USB ports
Have tried - many! - different USB drivers, including that from both Asus and Google's own dev kit.
Have ADB installed, "adb devices" shows no devices (blank).
The thing that's really pi**ing me off is that this is such a basic thing to be stuck by, I really cant figure out what I'm missing!
Any help appreciated gents...
Click to expand...
Click to collapse
Windows 10 is very buggy. Download lobit Drive Booster to see if you are missing any driver for your pc. Your pc is probably missing some drivers for the motherborad or outdated. If this does not work, clean install windows 10. Let windows 10 install all the drivers for you while it is installing. Best method. Good internet connection required.
its damn easy,the problem lies in Windows,just boot into repairmodus/system recovery its the blue menu for troubleshooting,there u choose Startup Setting and there u choose number 7,thats for disabling the digital driver signature checking,after the reboot all is fine,boot note u must do it everytime new after reboot.
please next ask and post in right section,thanx.
Nvidia USB driver (ADB and Fastboot) is the only one that works for me
https://developer.nvidia.com/shield-open-source
Anyone else having trouble connecting your phone with your pc?
I've tried different computers with win 10 and one Ubuntu Linux pc with no luck.
The phone starts loading but I get no other options. I've tried different usb ports and different chords.
The computer sees the phone in device manager as "Unknown device".
I have had no luck finding drivers?
When i had this kind of issues tho with another Xiaomi phone mi pc suite did the thing. Hope itll help
Installing this suite triggers the usb driver install, or at least you can install them within it´s menu
I will try, but latest update was 2015