Related
I have the SDK for windows installed and have the drivers downloaded but they can not install. Even with my phone plugged in, i have tried all 3 different usb settings and currently have debugging turned on.
NOTE: The driver im trying to install is the adb driver.
Also this may be my first android phone but i do know my way inside and out on a computer
farquep,
I'm an Android newbie myself, but I don't think you need those SDK drivers. I tried installing them, and they weren't working for me, either.
I'm not sure if you're trying to root/enable sideloading on your phone, but I found that the drivers included with HTC Sync seemed to get me where I needed to be as far as THAT effort goes.
If you're just trying to hook up your phone to your PC, and expecting to be able to access it like a removable drive, I'm pretty sure you'll be unable to do that until you go through the rooting/sideload enabling process. I never had any luck with it UNTIL I rooted my phone, and I'm pretty sure that's by AT&T's design.
Regards,
Corporate Dog
You need to modify the .inf file for the driver to include your device/vendor code manually or just do what I did which is easier and install HTC sync won't hurt anything you don't have to use it. It will modify the file for you. Or you could have someone upload there modified file. At any rate the problem is the USB plug and play system that does not recognize your device. It only recognizes a handful of devices and the ARIA is not one of them. Good Luck.
I'm trying to use my new Epic to test an application I made a while ago but I can't seem to get Eclipse or the Android Eclipse plugin to recognize my phone.
The android documentation says that I need to install the USB driver package from the list of available packages in the SDK and AVD manager, but there is no USB driver package. In addition, I am unable to even mount my EPic to my computer to do simple file transfers, regardless of whether I use the drivers that Windows downloads from Windows Update or if I use the official driver package from Samsung.com. Although I will get a drive to show up when I plug my phone in, it will be a light grey and attempting to access it leads to it timing out after a few minutes.
I've attempted this on 32-bit and 64-bit editions of Windows 7, and I do have USB debugging enabled. I'm probably missing something since this is my first Android phone, but I sure can't figure it out and I consider myself pretty proficient with this type of stuff
Try one of the USB ports on the back of the CPU that are directly connected to the MB. Stupid? I thought so too until it worked for me.
Also make sure you are using the compatible version of Eclipse IDE and that you went through the steps in there to install the SDK plugin properly.
The plugin doesn't work with the newest versions of Eclipse properly. That said if you cant' mount your SD then your computer isn't recognizing it. The EPIC specific drivers were posted yesterday if you aren't using them do so and try the different USB port.
Aridon said:
Try one of the USB ports on the back of the CPU that are directly connected to the MB. Stupid? I thought so too until it worked for me.
Also make sure you are using the compatible version of Eclipse IDE and that you went through the steps in there to install the SDK plugin properly.
The plugin doesn't work with the newest versions of Eclipse properly. That said if you cant' mount your SD then your computer isn't recognizing it. The EPIC specific drivers were posted yesterday if you aren't using them do so and try the different USB port.
Click to expand...
Click to collapse
I originally tried the front USB ports, and then tried the rear ports and got the same results. I am confident that Eclipse and the SDK plugin are playing nice together because I used them extensively in developing the application a couple of months ago, including using a virtual android device for testing.
The Drivers that I downloaded from Samsung were specific to the Epic and were last revised today, so they are the most recent.
Roisen said:
I originally tried the front USB ports, and then tried the rear ports and got the same results. I am confident that Eclipse and the SDK plugin are playing nice together because I used them extensively in developing the application a couple of months ago, including using a virtual android device for testing.
The Drivers that I downloaded from Samsung were specific to the Epic and were last revised today, so they are the most recent.
Click to expand...
Click to collapse
I downloaded the drivers from Samsung website but am still unsuccessful in mounting my sd card to my Windows 7 64bit pc. Anybody has found a solution??
i had to edit 70-android.rules to include the samsung drivers code 04e8
I fiddled for a couple of hours and it just started working. No idea what I did, so sorry I can't be of more help to other people with this problem.
i'm not sure what this eclipse thing is, but i was having problems connecting my phone to my computer.
but after doing a battery pull, it all started working again. sounds noobish, but hey, it worked!
I have no idea in which section to write this, so General seams like the best choice.
I have a Galaxy Y testing device with a broken boot.img. I am trying to get Odin working in Windows 7 in order to flash a new boot.img to this device, but I can't get the Samsung USB drivers to work and my Windows knowledge is now that great as I mostly work on Linux computers, but no fastboot on Samsung devices.
There are two drivers listed in the Device Manager. The Regular Samsung USB drivers, and something called Samsung USB CDC. It's the CDC I seam to have issues with. It just shows an error message that states "The device could not start (Code: 10)". I have already talked to Samsungs online support, but there is not much support to find there. They know nothing about Windows or how to get anything working on it. And google's search engine, which usually is the best friend for something like this, did not come up with much either.
I should mention that I run Windows in VirtualBox. However, I already have HTC Sync Manager fully working with an older HTC device, so this is not a VBox issue. Also, Windows do find the device just fine, it just can't start one of the drivers.
I have tried installing Kies. I have also tried installing other separate driver versions. Nothing is working.
Search the forums for Naked Drivers, its a complete driver package for a lot of android devices.
Give em a try.
I would post a link but my post count is as such that I cannot at this time.
WooHooGuy said:
Search the forums for Naked Drivers, its a complete driver package for a lot of android devices.
Give em a try.
I would post a link but my post count is as such that I cannot at this time.
Click to expand...
Click to collapse
I love the idea of a multi driver for all devices, much like on my linux boxes, so thanks for that. However, I get the same issue and same error message. I will try to reinstall windows and see if that will work. It has been many many years since I ran windows as my daily OS, but I do remember that formatting was the best way of fixing issues with it. If this is still no go, I will try to put windows directly on my netbook to see if this could be a Virtual problem anyways, but I don't think so. USB stuff is working fine on the Virtual OSX.
Will report back later
EDIT:
Nothing is working. All I have installed, is the naked driver. When I plug-in my HTC Desire or HTC Wildfire S, the driver is working fine. But when I plug-in the Galaxy S3 or the Galaxy Y, I get the "The device cannot start (Code: 10)".
So HTC devices are working, but Samsung is not. The same problem I had with separate HTC and Samsung drivers.
try the one from my link,its latest usb driver exe from kies,worx on win8 64bit too.
http://forum.xda-developers.com/showthread.php?t=1927769
-CALIBAN666- said:
try the one from my link,its latest usb driver exe from kies,worx on win8 64bit too.
http://forum.xda-developers.com/showthread.php?t=1927769
Click to expand...
Click to collapse
Thanks, but I have tried that version, and the one newer (1.5.23). I did manage, efter some reinstalls, to get 1.5.18 (I think is was) to work on the real installation. So maybe my issue is with virtualbox, I just can't see what. I have disabled everything in linux that could block something, I have disabled firewall and such on the virtual windows, I have tried checking and changing perms on the linux device nodes, and tried running VB as root.
At least I got the Galaxy Y running again, but I don't like having unresolved issues so VB is going down
I have 2 phones, a samsung galaxy note 4 (tmobile) and a zte zinger (tmobile). One is a flagship, the other is a temporary replacement. I've attempted to get clockworkmod tethering working on both, but the tethering program wouldn't start. I'm on windows 10 as the title says, and I've done everything from uninstalling and re-installing clockworkmod tether on windows and my phone to disabling driver signature to re-install drivers for both phones, as well as replacing the ADB files from a fresh/latest install for ADB into the win32 directory to running it in compatibility mode and/or administrative mode. I verified my copy of ADB works inside C:\Program Files (x86)\ClockworkMod\Tether\win32 so I know it's not that.
Here's the only line (or 2) from the log output:
C:\Program Files (x86)\ClockworkMod\Tether
""
And then it stops.
Same here. I upgraded, and I can't uninstall OR reinstall the app either. It says I need to insert the CD-ROM for the software -.- Seems like an MS issue, but hell, who knows?
Sadly Koush hasn't made any updates to the app or PC software since February and seems to be ignoring all support requests (I've emailed, left a bug report, etc and got no response whatsoever). Windows 10 has definitely broken something with the tether, but without the dev's help I doubt it's fixable.
Just want to add that I am having the same problem. All i get is "C:\Program Files (x86)\ClockworkMod\Tether". Hopefully this gets fixed. I doubt Ill ask for a refund since Ive used the hell out of this app, but I do not want to buy another app just for Win 10.
Exactly the same here. Very frustrating.
Exactly the same here. Looks like a MS or windows 10 problem.
Hope the dev can fix it.
J
guess what.. same problem.. emailed and no response from tether anyone have a fix yet?
This really sucks. I only went to 10 on my laptop to test it out. Sadly its the only thing that uses tether. :crying:
*PDANet+ works great for USB tether. Not so much with the hot spot feature. The full version is $8 so eh... It works though! No root needed for USB tether with PDANet.
Has @Koush released the source for the PC side app?
Sent from a potato using Kung-Fu
Same problem - hello @Koush ! Any progress on this?
Thanks,
J
Looks like he took the money and ran. Very unprofessional. Everyone needs to remember if/when he releases a new app. I will be the first to say HELL NO. not getting my money.
Windows 10 android tethering apps
I'm on metropcs (t-mobile carrier) on the 'unlimited plan'. I came here seeking support for clockworkmod tether under Windows 10. I am not willing to 'downgrade' back to Windows 7 behind Clockworkmod's lack of support. I can report that the paid versions of both PDAnet and EasyTether work well enough. I would prefer Clockworkmod for the sole reason that it uses real/regular ADB as its middleware, so I can still use other apps like Vysor (to control my device) while tethered. Unlike PDAnet and EasyTether which seem to use hacked version of adb and prevent any other normal usb-pc connectivity (no regular adb apps, so no vnc/vysor). That's a big deal for me since I put my phone is an external antenna holster, because the android device is my sole source of Internet, here, and the ability access my phone via the computer screen makes my life easier. I hope CWM Tether gets fixed, but since they don't seem to care I hope someone comes along with a better product (using real ADB and more support).
Same here - doesn't work on Windows 10
@Koush - you gonna man up?
Guys, I've finally made CM Tether work on Windows 10!
Installation guide for Win10:
At first install CM Tether on your PC as usual.
Then get OpenVPN installer (you can google it)
Uncheck all checkboxes except TAP Virtual Ethernet Adapter in installator if OpenVPN isn't needed.
Install it.
Just run Tether as admin.
It worked for me, contact me if it didn't for you.
thanks
Thank you so much t1meshift! This one worked for me!
t1meshift said:
Guys, I've finally made CM Tether work on Windows 10!
Installation guide for Win10:
At first install CM Tether on your PC as usual.
Then get OpenVPN installer (you can google it)
Uncheck all checkboxes except TAP Virtual Ethernet Adapter in installator if OpenVPN isn't needed.
Install it.
Just run Tether as admin.
It worked for me, contact me if it didn't for you.
Click to expand...
Click to collapse
How did you getnit to work with antivirus and firewall
evilj said:
Same problem - hello @Koush ! Any progress on this?
Thanks,
J
Click to expand...
Click to collapse
Sent from my SM-N920T using Tapatalk
t1meshift said:
Guys, I've finally made CM Tether work on Windows 10!
Installation guide for Win10:
At first install CM Tether on your PC as usual.
Then get OpenVPN installer (you can google it)
Uncheck all checkboxes except TAP Virtual Ethernet Adapter in installator if OpenVPN isn't needed.
Install it.
Just run Tether as admin.
It worked for me, contact me if it didn't for you.
Click to expand...
Click to collapse
Good info, but rather than downloading the OpenVPN installer, get just the TAP-windows NDIS6 package instead.
filename is tap-windows-9.21.2.exe, available from same OpenVPN download page.
Then it works! Awesome.
https://forum.xda-developers.com/ge...d-tether-fix-windows-10-t3598634#post76318015
for those who still have problems with cwmtether here is my fix
I'm having an issue with file transfer where my computer can't 'see' the phone when an AOSP ROM is installed.
File transfer is fine when mounting in recovery, also when I have OOS installed, so it isn't a hardware problem.
I've gone through the forum searching for a solution, and I have:
Changed the default USB configuration (under Developer options) to MTP
Uninstalled the phone from Device Manager on my computer
Tried installing OnePlus drivers to my computer
Tried installing Qualcomm drivers to my computer
Can anyone suggest a solution? I'm desperate to get this sorted as I can't tolerate OOS any longer, I just want a cleanish build of Android with no OnePlus rubbish in it!
I join your quest man... Im looking for the solution for this problem since i have installed my first AOSP rom on OP5... Never find the solution, i'm curious for this too... Now im on PureFusion and MTP of course isnt working... so i use recovery for file transfer (which is annoying) or the WiFi server (which is slow and isnt "operations" friendly)
In the same time cant understand why my nexus 6p with PureNexus is fully working in MTP but the oneplus 5 nope
Hitman478™ said:
I join your quest man... Im looking for the solution for this problem since i have installed my first AOSP rom on OP5... Never find the solution, i'm curious for this too... Now im on PureFusion and MTP of course isnt working... so i use recovery for file transfer (which is annoying) or the WiFi server (which is slow and isnt "operations" friendly)
In the same time cant understand why my nexus 6p with PureNexus is fully working in MTP but the oneplus 5 nope
Click to expand...
Click to collapse
That's interesting. I'm transferring like 80% of my files trough MTP and it is and always was working fine, but I'm using Linux, so that might help you guys to solve it
siankatabg said:
That's interesting. I'm transferring like 80% of my files trough MTP and it is and always was working fine, but I'm using Linux, so that might help you guys to solve it
Click to expand...
Click to collapse
I know it's windows fault because when it have too many drivers to manage for the same thing it goes crazy.. but even removing every single driver (ADB and Android related) it doesn't work.. I'm looking in a solution on the Linux build called "forget windows use Linux" since I can't completely remove windows 10
I had same issue in Linux
Typically, issue is not the ROM
1) check the phone get set to "file transfer" when connected, you generally have option to chose
2) plugging to a usb in chain to other switches it was not work, connected directly to a usb MB port, worked.