I installed xdandroid 2.2.1 and everything works fine (except camera i saw that this is fixed with karnel update but I don't know how to do that) and i can't connect usb to PC.
I try install driver with Android SDK but it can't install CDC Abstract Control Model and CDC ACM Data drivers. On notification bar say that USB is connected and USB debugging is connected .Also I install HTC Sync it install all drivers except CDC Abstract Control Model and CDC ACM Data.
I also done this :
adb and usb debugging
To ensure that you are able to use adb and usb debugging you will need to plug in your usb cable to your computer and in winmo select activesync. Now launch haret and once Android is loaded you'll see a notification that will notify you have usb-debugging control and able to use adb.
Click to expand...
Click to collapse
But can't fix the problem
How to fix this problem.Can someone help me.
Sry for my bad English
edit:
I found this Guide http://forum.xda-developers.com/showthread.php?t=502010 I registered on the side but still can't see the links Can someone post quide here?
Hi i've got CM7 installed and android v 2.3.5
I try to plug it in to USB on ubuntu 10.10
It is not detected so i can't mount it .
Also i don't have the option to change usb settings on my device because this option doesn't exist. Putting on usb debugging mode doesn't help also.
Thanks.
Hi all,
i'm trying to thether my phone with windows xp but windows requires the following driver
"LGE Android Phone"
i've tried:
LG USB Modem Driver
LG United Mobile Drivers
LG Bluetooth Drivers
LG Android Driver
SDK Drivers
but nothing is working.
do i need a special driver? i'm running the nighlty 177
I had just the same problems when using the CM7 mod for the first time... I also searched for driver and installed many things without knowing if it will work... then just tried to connect the device with usb-debugging mode and windows (7) suddenly installed some drivers and my phone got connected to my pc...
You need an extra driver for XP
For XP an extra driver (Remote_NDIS_based_Internet_Sharing_Device) needs to be installed for tethering
See this thread for the driver:
http://forum.xda-developers.com/showthread.php?t=445436
nosmirc said:
For XP an extra driver (Remote_NDIS_based_Internet_Sharing_Device) needs to be installed for tethering
See this thread for the driver:
http://forum.xda-developers.com/showthread.php?t=445436
Click to expand...
Click to collapse
Thanks... It is working fine!
I installed android studio on ubuntu 16.04. also modified 51-android.rules but android studio doesn't show connected deveces while running. I also enabled developers and usb debugging option in phone settings.
what is the error message?
PriyankaM said:
I installed android studio on ubuntu 16.04. also modified 51-android.rules but android studio doesn't show connected deveces while running. I also enabled developers and usb debugging option in phone settings.
Click to expand...
Click to collapse
hi folks!
I recently bought a sm-t713 and i can't get my pc to recognize it in linux or windows.. i want to root and unlock the bootloader but odin cant even see it.. and its not an issue with not having debugging on. thats all turned on. Please advise. thanks!
Nobody knows why? I have oem unlock "on"
debugging "on"
But I cant get my comp to see the device..Have Samsung drivers installed. Still no luck.
How can I fix this? all it does is charge when I hook it to pc but can't transfer files.
sorry double post
Same issue here. I've had no luck sorting it out.
Gutterball said:
hi folks!
I recently bought a sm-t713 and i can't get my pc to recognize it in linux or windows.. i want to root and unlock the bootloader but odin cant even see it.. and its not an issue with not having debugging on. thats all turned on. Please advise. thanks!
Click to expand...
Click to collapse
USB Debugging and MTP use different drivers and are different protocols.
Open a command prompt in windows then type:
adb devices
You should get a response with a serial number if USB debugging is working.
If so then it's likely an MTP driver problem or MTP isn't enabled.
In developer options under USB configuration, ensure MTP is enabled.
If so check the device is detected as an MTP device in windows device manager.
ashyx said:
USB Debugging and MTP use different drivers and are different protocols.
Open a command prompt in windows then type:
adb devices
You should get a response with a serial number if USB debugging is working.
If so then it's likely an MTP driver problem or MTP isn't enabled.
In developer options under USB configuration, ensure MTP is enabled.
If so check the device is detected as an MTP device in windows device manager.
Click to expand...
Click to collapse
What the USB configuration is set to is actually moot. When the device is plugged in to a PC the tablet will bring up a notification stating what mode the USB port is in and also provide the option to change that to MTP mode (Transfer files), provided the drivers are correctly installed and all is in working order. By changing USB configuration to MTP the tablet shows up immediately on the PC but you still have to switch to "Transfer file" mode before you can move files between devices. Either way the results are the same and it takes the same number of steps. I always leave my USB configuration in "System Default" and I have never had any issues.
ashyx said:
USB Debugging and MTP use different drivers and are different protocols.
Open a command prompt in windows then type:
adb devices
You should get a response with a serial number if USB debugging is working.
If so then it's likely an MTP driver problem or MTP isn't enabled.
In developer options under USB configuration, ensure MTP is enabled.
If so check the device is detected as an MTP device in windows device manager.
Click to expand...
Click to collapse
Thanks for helping! under device manager the tablet is showing as a mass storage controller not an mtp device. Even though in the tablet itself I have it set to mtp under developer options.
When I do the command "adb devices" I get this message
C:\Users\Brian\Downloads\platform-tools_r28.0.0-windows\platform-tools>adb devices
List of devices attached
nothings there
Also I was reading this is happening because of the newest stock update from Samsung.. is that true?
Gutterball said:
Thanks for helping! under device manager the tablet is showing as a mass storage controller not an mtp device. Even though in the tablet itself I have it set to mtp under developer options.
When I do the command "adb devices" I get this message
C:\Users\Brian\Downloads\platform-tools_r28.0.0-windows\platform-tools>adb devices
List of devices attached
nothings there
Also I was reading this is happening because of the newest stock update from Samsung.. is that true?
Click to expand...
Click to collapse
No response from the adb command suggests you don't have the correct adb drivers installed or the device isn't being detected at all.
Have you installed the ADB drivers?
I would try a different cable first. Is Windows device manager detecting the device if it's plugged in/unplugged?
ashyx said:
No response from the adb command suggests you don't have the correct adb drivers installed or the device isn't being detected at all.
Have you installed the ADB drivers?
I would try a different cable first. Is Windows device manager detecting the device if it's plugged in/unplugged?
Click to expand...
Click to collapse
Still having trouble here, too.
After flashing a ROM and attempting to install what was probably the wrong Gapps version, I'm now getting a boot loop into TWRP, and the device is still not recognized. I can boot into 'Download Mode', but the device is still not being seen by my PC. I have tried multiple times to install the USB drivers, but Odin 3.12.3 is still not seeing the tablet.
Much as I hate installing hokey, bloated software, would KIES be helpful here?
So, all is not lost (yet) - I can still access TWRP, but I'm not sure where to go from here.
Thanks in advance for any ideas you have.
I
BillTheCat said:
Still having trouble here, too.
After flashing a ROM and attempting to install what was probably the wrong Gapps version, I'm now getting a boot loop into TWRP, and the device is still not recognized. I can boot into 'Download Mode', but the device is still not being seen by my PC. I have tried multiple times to install the USB drivers, but Odin 3.12.3 is still not seeing the tablet.
Much as I hate installing hokey, bloated software, would KIES be helpful here?
So, all is not lost (yet) - I can still access TWRP, but I'm not sure where to go from here.
Thanks in advance for any ideas you have.
Click to expand...
Click to collapse
Considering download mode is totally OS independent and neither uses adb nor mtp drivers it seems the issue is either incorrectly installed usb drivers or faulty cable, device or port issues.
Boot to Download mode, open device manager then plug in the usb cable.
Windows should detect the device as a USB composite device.
If there is no detection then there is a communication issue between device and PC which could be any one of the afore mentioned reasons.
No matter what windows should show some sort of detection as soon as the device is plugged in.
No detection means no matter what drivers are installed its not going to work.
It's probably worth uninstalling the usb ports then rebooting.
Then trying again.
ashyx said:
I
Considering download mode is totally OS independent and neither uses adb nor mtp drivers it seems the issue is either incorrectly installed usb drivers or faulty cable, device or port issues.
Boot to Download mode, open device manager then plug in the usb cable.
Windows should detect the device as a USB composite device.
If there is no detection then there is a communication issue between device and PC which could be any one of the afore mentioned reasons.
No matter what windows should show some sort of detection as soon as the device is plugged in.
No detection means no matter what drivers are installed its not going to work.
It's probably worth uninstalling the usb ports then rebooting.
Then trying again.
Click to expand...
Click to collapse
Well, I'll be dipped in $hit.
What's the probability that one guy could have three dodgy USB cables? Used one, wiggled it around and the PC recognized the device. Looks like I'm in for a quick trip to WallyWorld. Thanks!
ashyx said:
No response from the adb command suggests you don't have the correct adb drivers installed or the device isn't being detected at all.
Have you installed the ADB drivers?
I would try a different cable first. Is Windows device manager detecting the device if it's plugged in/unplugged?
Click to expand...
Click to collapse
yeah, windows device manager detects it as a mass storage controller. I installed the driver from samsung site. Cant be the cord cause it works with the phone. Even linux mint wont pick it up either. Any ideas? Thanks again for helping this is driving me nuts!
Gutterball said:
yeah, windows device manager detects it as a mass storage controller. I installed the driver from samsung site. Cant be the cord cause it works with the phone. Even linux mint wont pick it up either. Any ideas? Thanks again for helping this is driving me nuts!
Click to expand...
Click to collapse
Are you able to connect to the device in TWRP, either ADB or MTP?
ashyx said:
Are you able to connect to the device in TWRP, either ADB or MTP?
Click to expand...
Click to collapse
nope don't have twrp installed. and adb or mtp wont detect it. how can I install twrp? don't I need to bootloader unlock this first? And I cant do it if its not recognized by the comp right?
Gutterball said:
nope don't have twrp installed. and adb or mtp wont detect it. how can I install twrp? don't I need to bootloader unlock this first? And I cant do it if its not recognized by the comp right?
Click to expand...
Click to collapse
Are you certain this is a genuine Samsung and not a copy?
Can you post the build details from the app Phone Info.
ashyx said:
Are you certain this is a genuine Samsung and not a copy?
Can you post the build details from the app Phone Info.
Click to expand...
Click to collapse
screenshot is in the attachment.