USB Tethering - Desire Q&A, Help & Troubleshooting

Currently using RCMixHD and tethering doesn't work for me. It used to work. This is on Windows 7 32bit. It works fine on Ubuntu but my main rig is windows.
Do I need some drivers or what im lost?
Eph.

ephumuris said:
Currently using RCMixHD and tethering doesn't work for me. It used to work. This is on Windows 7 32bit. It works fine on Ubuntu but my main rig is windows.
Do I need some drivers or what im lost?
Eph.
Click to expand...
Click to collapse
you will prob need some kind of usb modem driver installed, have you tried installing htc sync, maybe the default modem drivers will work

I used to use usb tether though and it worked. I guess I could try installing newest htc sync.
Eph.

yep, thats what used to happen to me! had a format recently (win7 32 bit ultimate) and couldnt tether at all! just Install and should work fine

Related

Htc in Ubuntu

hi..
i recentely booted Ubuntu in my PC... Now the Problem Is tht i cannot connect my phone with it since the exe, files doesnot work on Ubuntu i cannot instal activesycn. is there any way i can connect to ubuntu.. n i also want to use internet thru internet sharing option on the phone.. help
i dont know about activesync, but i am able to use internet sharing and it works fine for me. my htc excalibur is running evo windows mobile 6.5 and my laptop runs linux mint 9. maybe you need to upgrade the rom on your phone?
youngdaddytc said:
i dont know about activesync, but i am able to use internet sharing and it works fine for me. my htc excalibur is running evo windows mobile 6.5 and my laptop runs linux mint 9. maybe you need to upgrade the rom on your phone?
Click to expand...
Click to collapse
thanks.... i'll give it a try....
Switch to USB mod using WM5torage will help u access the SD.
If u want to sync, try installing SynCE from synaptic.
TMinh said:
Switch to USB mod using WM5torage will help u access the SD.
If u want to sync, try installing SynCE from synaptic.
Click to expand...
Click to collapse
i couldnt figure out wht to do with SynCE...

[Q] Rooting Epic on a 64bit system need help

Alright everyone I'm a EVO User but My friend is trying to root his Epic and is haveing problems we tried z4root and then tried to flash clockwork through rom manager with out a PC. When trying a PC it won't recognize the phone he is running a 64bit system and was going to try the one-click root that flashes Clockwork as well but since his PC won't recognize the phone he can't we have tried the 64bit drivers as well and nothing any help is greatly appreciated thank you
You need to try different USB cables and different USB ports on your PC. Usually on a desktop the USB port in the back is the best. Try to uninstall the epic drivers and then reinstall.them. this has worked.for.me before. And like you found out you can't use Tom manager to flash cwm on the stock kernel. Rom manager says it flashed it but it doesn't. Just try the tips I gave you and see if.it works. Good.luck
Sent from my Evo Killer!!!
your just better off get the one click clockwork mod and reinstalling your drivers. the samsung driver are a pain to get working
system155 said:
your just better off get the one click clockwork mod and reinstalling your drivers. the samsung driver are a pain to get working
Click to expand...
Click to collapse
I have windows 7 64 and have never had problems with the samsung usb drivers or one click root/cwm. When the first attempt fails, chances are you need to retrace your steps and redo them. Use the rear usb port and be sure to reboot after installing drivers. That always helps me.
sent from my brain telepathically :-D
Is usb debugging on?
Also when you plug it in just leave it alone
Then run the one click
Sent from my SPH-D700 using XDA App
A_Flying_Fox said:
Is usb debugging on?
Also when you plug it in just leave it alone
Then run the one click
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Yes it is and tried that when we run the exploit it just closes out a second later
Jbcarrera said:
Yes it is and tried that when we run the exploit it just closes out a second later
Click to expand...
Click to collapse
If you are having a driver issue (still) try installing PDAnet. I have Win7 Ultimate 64 bit and couldn't get any of the linked samsung drivers to install and correctly recognize my phone. I installed PDAnet, selected Samsung and viola... worky.
If that still doesn't work for you, try a different USB cable.
Once you get the drivers working properly, and have a good cable, the one click root/clockwork mod installer will work like a champ.
These steps should work for you.

64 bit USB driver won't recognize my phone

I bought a new laptop and it's 64 bit running Windows 7. I'm trying to install the 64 bit USB driver & get it to recognize my phone but it simply won't work.
The following two things keep running and running with the words "installing driver software" after them:
CDC Abstract Control Model (ACM)
S3C6410 Android ADB
I have no idea how to get this to work so any advice is greatly appreciated!
ps - USB debugging is checked in my application settings.
There are lots of people having problems with 64 bit windows nit recognizing the epic. My suggestion is to try.another USB cable. I use my wife's evo cable and it works fine for me. Good luck man just keep trying. Try different ports, cables and also check.to.make sure the USB slot is clear from any obstructions.
Sent From My Evo Killer!
musclehead84 said:
There are lots of people having problems with 64 bit windows nit recognizing the epic. My suggestion is to try.another USB cable. I use my wife's evo cable and it works fine for me. Good luck man just keep trying. Try different ports, cables and also check.to.make sure the USB slot is clear from any obstructions.
Sent From My Evo Killer!
Click to expand...
Click to collapse
I've done all those things.
Install the 32-bit drivers even if you're on a 64 bit computer
iSaint said:
Install the 32-bit drivers even if you're on a 64 bit computer
Click to expand...
Click to collapse
I was going to try that but didn't want to screw anything up...so that should work then?
droid newb said:
I was going to try that but didn't want to screw anything up...so that should work then?
Click to expand...
Click to collapse
Yes, I have 64bit computer and mine works with 32bit drivers.
Doing the same thing with 32 bit that it does with 64 bit.
droid newb said:
Doing the same thing with 32 bit that it does with 64 bit.
Click to expand...
Click to collapse
Here is a link to the drivers I installed on my Win 7 Ultimate 64bit machine. (i put them on my google documents site)
https://docs.google.com/leaf?id=0B8DFupwiCOXyMGViMDJmY2MtMGU4YS00MGY5LWFkOGItNjkyMDY3MjkyNjgx&hl=en
I have had no issues using odin or mass storage.
Hope this helps, good luck
jdelano said:
Here is a link to the drivers I installed on my Win 7 Ultimate 64bit machine. (i put them on my google documents site)
https://docs.google.com/leaf?id=0B8DFupwiCOXyMGViMDJmY2MtMGU4YS00MGY5LWFkOGItNjkyMDY3MjkyNjgx&hl=en
I have had no issues using odin or mass storage.
Hope this helps, good luck
Click to expand...
Click to collapse
That's the same one I've been trying all this time. I just don't understand why this won't work.
The ACS Module has never installed for me but my device works fine
watermoore said:
The ACS Module has never installed for me but my device works fine
Click to expand...
Click to collapse
So would you be able to Odin back to stock if you needed to?
droid newb said:
That's the same one I've been trying all this time. I just don't understand why this won't work.
Click to expand...
Click to collapse
When you ran the setup for the driver, did you run it as administrator?
Right click on setup.exe and select that option from the menu.
Sorry you're having such a bad time, that has got to be mega-frustrating.
I've read also, that some people run the 32 bit drivers on win 7 64bit and they report that they work for them just fine.
hey man i feel your pain. I have been having the same exact problems as you. I also have tried the 64 bit/32bit drivers, uninstalling/reinstalling them, everything i can think of or have been told to do to no avail. It use to work fine until i got the first froyo update eb13 and ever since its been like this. My laptop keeps telling me to replace my device.
I did get on a computer at work with win XP and i plugged my phone into it and the device installed but im not sure about the drivers. Im limited to what i can do at work. So maybe it has something to do with windows 7 cause my laptop is brand new as most people having this problem are to.
Did the drivers change after the EC05 update. Neither of my computers will recognize my phone now after I updated the modem. I even tried reinstalling the links you have in this post and updating drivers and still a no go.
I just had this problem recently. It wasn't the drivers - instead, it was the USB port I was using. If you're on a desktop, try a usb port on the back of the pc. If you're on a laptop, give all the usb ports a go.
Sent from my SPH-D700 using XDA Premium App
I am on a laptop and i have repeatedly try all usb ports and still a no go. It really seems like something changed after EB13 cause i never had a problem before.
dazednconfused1144 said:
Did the drivers change after the EC05 update. Neither of my computers will recognize my phone now after I updated the modem. I even tried reinstalling the links you have in this post and updating drivers and still a no go.
Click to expand...
Click to collapse
Nope; I have a win7 ultimate 32 laptop and a win 7 ultimate 64 desktop. Both see my phone just fine. Same drivers from when I first rooted after xmas to DK28 from 2.1.
I have heard of people having an issue with something bent on the phone's usb connector, it stops from getting full connection.
I'm having the same issue, but I can connect when I uncheck USB debugging. With it checked, it won't connect. I'm trying to root with 2.5.5...
jerbeck24 said:
I'm having the same issue, but I can connect when I uncheck USB debugging. With it checked, it won't connect. I'm trying to root with 2.5.5...
Click to expand...
Click to collapse
That worked!!!!!!!!!!!
Wooooooooooooooooooo!!!!!!!!!!!!!!!!!!!
droid newb said:
That worked!!!!!!!!!!!
Wooooooooooooooooooo!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
No problem...problem for me is, it needs to be checked in order to root...
I'm just going to odin back to EB13 and CWM3 and restore my latest back up of ACS 1.0.2

[Q] there is a disturbance in the force...

Hi
recently, i decided it was time to wipe my computer clean and do a fresh install (you know, its like flashing roms, sometimes fresh is better) so i reinstall win 7 ultimate x64 and for the life of me, i cannot get adb to recognize my g2 with cm7 rc1... ive searched through several threads on installing the proper drivers, installed the most recent version of htc sync, latest android sdk, and nothing... its not such a big deal, but i would like to flash to the final of cm 7, but i dont like a lot of the fluff in cm7 (adw, etc) and find it easier to remove and change things around through adb.
thanks in advance
Did you use the installer to install the android sdk? I had issues as well with that one. Removed it and just extracted the .zip package, after that it worked fine.
This REALLY is a tricky one. In the past I've had luck installing both the HTC sync software, and PDANet. Between those two all the drivers seem to work for me in Win 7 64bit.
Why not just use a file manager like 7zip to remove/add the things you want prior to flashing. Or do you just like doing things the hard way?
kamontryst said:
Hi
recently, i decided it was time to wipe my computer clean and do a fresh install (you know, its like flashing roms, sometimes fresh is better) so i reinstall win 7 ultimate x64 and for the life of me, i cannot get adb to recognize my g2 with cm7 rc1... ive searched through several threads on installing the proper drivers, installed the most recent version of htc sync, latest android sdk, and nothing... its not such a big deal, but i would like to flash to the final of cm 7, but i dont like a lot of the fluff in cm7 (adw, etc) and find it easier to remove and change things around through adb.
thanks in advance
Click to expand...
Click to collapse
See bold. Therein lies your problem.
dhkr234 said:
See bold. Therein lies your problem.
Click to expand...
Click to collapse
Unless it's specifically a problem with Ultimate, there's no reason it won't work. I run Win 7 Home Premium x64 at home and the steps I said work for me.
I run 7 ultimate 64bit and adb works fine for me.
I used the pdanet drivers.
Flash with rom manager and then install zip from card..the adwmod zip that is..take it out for you
Sent from my Vision using XDA Premium App
dhkr234 said:
See bold. Therein lies your problem.
Click to expand...
Click to collapse
I have to agree with everyone else on this. I'm running Windoze 7 X64 and adb works just fine. I also have Ubuntu 10.10 64bit and Sabayon 64bit on my HDD (yay multiboot!) and neither of them have issues either.
dhkr234 said:
See bold. Therein lies your problem.
Click to expand...
Click to collapse
i was using win 7 ultimate 64 before, and it worked just fine, im staring to think that its my actual hardware usb port on the tower, my wifes phone (mytouch slide) isnt recognized either, and i have gotten my younger sisters pc to recognize my phone no problem (except the pc is slow as dirt...
KCRic said:
Why not just use a file manager like 7zip to remove/add the things you want prior to flashing. Or do you just like doing things the hard way?
Click to expand...
Click to collapse
i use winrar to change files around before i flash it, but lately ive been having problems with the edited rom (i.e. install fails, boot looping even after a data/cache wipe, etc) i just wanted to try a different route this go around
You could try another usb cord, and make sure everything is installed under admin,and the way I got my drivers I edit the driver file and added the info for G2 (saw it in tmobile forum) and also I have no problem with win 7 x64 aswell... and I agree I don't like all the extra puff and bluff oin cm7
well, i havent been able to get a wired adb to connect, but i have gotten it to work with wirelessadb and i am now rockin a modified cm 7 final

Nexus 7 wont connect to computer via MTP

When I connect my Nexus 7 to my windows 7 computer it is not recognized in MTP, but is when I change it to PTP. When I connect my 1st gen Nexus 7 to the same computer it is recognized fine and I am able to transfer files. I have all the drivers installed and adb works when I am in PTP I just cant transfer any files. Has anyone else experienced this problem or is there maybe something wrong with my Nexus?
Check out this thread. I was experiencing similar issues although I didn't test out PTP .
Sent from my Galaxy Nexus using xda app-developers app
Disregard. I figured it out. It was a driver issue after all.
How did you fix it? I have the same problem. Is root needed to view transfer files via USB?
My N7 2013 won't connect with my Macbook Pro. I already have the Android File Transfer app, which works fine with my Nexus 4, but it won't recognize the Nexus 7 2013. It charges, but no connection. Anyone have any ideas?
lucastmw said:
My N7 2013 won't connect with my Macbook Pro. I already have the Android File Transfer app, which works fine with my Nexus 4, but it won't recognize the Nexus 7 2013. It charges, but no connection. Anyone have any ideas?
Click to expand...
Click to collapse
Might be a silly question but did you enable USB debugging in developer tools.
Sent from my Galaxy Nexus using xda premium
jmileti said:
Might be a silly question but did you enable USB debugging in developer tools.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yes, I tried it with debugging on and off.
thaliagoo said:
How did you fix it? I have the same problem. Is root needed to view transfer files via USB?
Click to expand...
Click to collapse
Root is not needed to transfer files via USB. I just uninstalled the previous driver and updated to the latest and that worked for me.
No matter what, I always keep getting error code 10, device cannot be started when I install the new nexus 7 drivers Android ADB device (from the previous posts- Nexus 7 root). I'm not even trying to root, just trying to install drivers correctly.
thaliagoo said:
No matter what, I always keep getting error code 10, device cannot be started when I install the new nexus 7 drivers Android ADB device (from the previous posts- Nexus 7 root). I'm not even trying to root, just trying to install drivers correctly.
Click to expand...
Click to collapse
These are the drivers I used... http://developer.android.com/sdk/win-usb.html
fixed mine by just forcing it to reinstall the drivers.
fstbusa said:
fixed mine by just forcing it to reinstall the drivers.
Click to expand...
Click to collapse
How did you force it do that? I've actually never ran into this problem. Windows 8 is what I'm running.
dirtyfingers said:
These are the drivers I used... http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
It is definitely a driver issue. I had to uninstall my drivers and then manually install others, because I had a Nexus 7 2012. Those drivers were showing up as *up to date* according to windows, but the device was not working. Total clean install worked to correct it.
Xirix12 said:
How did you force it do that? I've actually never ran into this problem. Windows 8 is what I'm running.
Click to expand...
Click to collapse
In device manager, go to the properties of each android device. I had one near the top of the list and one lower under portable devices. Click update driver and navigate to your updated drivers folder.
It should update them. The device listed under portable devices had mtp as part of the title so I figured that one was the problem.
Sent from my Nexus 7 using xda app-developers app
To anybody who comes to this thread looking for help.
Go to device manager, and under devices remove the Google ADB Driver. This drove me nuts. All of my nexus devices wouldn't connect because they lacked an external SD.
Sent from my Nexus 7 using XDA Premium HD app
I've tried every suggestion in all of these threads so far & nothing worked. Even after I deleted the ADB drivers, windows 7 would automatically reinstall them. When I tried to update the drivers, win7 said they already had the best drivers (ADB).
Here's what worked for me:
I had to turn off USB debugging, delete the ADB drivers in Device Manager, then reboot the device while it's still plugged in. Windows recognized the device as an MTP device & installed the drivers before it even fully booted.
i installed the drivers from the link in this thread and still no luck, i am running the latest paranoid android rom, and tried it on 8 different computers with 23 different cables and no luck - would it help if i flashed a stock rom ? otherwise i dont know what to do - any help would be appreciated, thanks, chris
edit flashed a stock rom and now it is working again - came right up on my pc, i am selling it today to buy the 32gb and just wanted to get me twrp backups off it
golfinggino said:
i installed the drivers from the link in this thread and still no luck, i am running the latest paranoid android rom, and tried it on 8 different computers with 23 different cables and no luck - would it help if i flashed a stock rom ? otherwise i dont know what to do - any help would be appreciated, thanks, chris
edit flashed a stock rom and now it is working again - came right up on my pc, i am selling it today to buy the 32gb and just wanted to get me twrp backups off it
Click to expand...
Click to collapse
I have the same problem. When I was using stock ROM I could connect fine to my PC. When I installed CM10.2 I can not longer connect. i have no problem when I try it with my phone though.
huizingajm said:
I have the same problem. When I was using stock ROM I could connect fine to my PC. When I installed CM10.2 I can not longer connect. i have no problem when I try it with my phone though.
Click to expand...
Click to collapse
After helping someone with Paranoid ROM, I think the problem you are experiencing may be on the ROM/kernel side. Part of the problem is the custom ROM was sending out different USB IDs from stock. I was able to help them force the recognition of the MTP device from a driver standpoint on windows, but the MTP device wouldn't start up when windows tried to initialize it.
sfhub said:
After helping someone with Paranoid ROM, I think the problem you are experiencing may be on the ROM/kernel side. Part of the problem is the custom ROM was sending out different USB IDs from stock. I was able to help them force the recognition of the MTP device from a driver standpoint on windows, but the MTP device wouldn't start up when windows tried to initialize it.
Click to expand...
Click to collapse
I switched kernels to stock to jassy to tiny. None of them work so it has to be the ROM. I am just going to use WiFi transfer of files. Nothing major right now while everything is still new to 4.3.

Categories

Resources