Do we have one that supports it?
I take it that is a no
Sent from my Galaxy Nexus using XDA App
GN still new, give it couple more months and there will be more infor about it.
I have tethered via USB wire on mine with stock ROM. It's ITL41F with 3.0.1 kernel. You need the RNDIS driver on your computer.
I have wired and wireless tethering working. Using Gummynex 0.3.0 with Lean kernel 1.1. I do have SDK installed on my machine and when rooting I did install Samsung drivers from 2 different locations. When I turned on wired tether in Settings my Win7 pc said "installing new hardware" and then it installed successfully. Don't know if it installed successfully because I had all that crap installed prior or if the OS and phone already had the drivers built in. None the less, it works with that ROM.
Related
I recently rooted my Incredible and put the most recent stable version of Cyanogen mod on it. I've been trying to get my wireless tethering to work on my desktop PC but haven't been able too. I'm not sure what settings I am messing up and on which end.
I am currently running an intel PC with Windows 7 64-bit. I went into my device manager and enabled ad-hoc connections on my wireless adapter but still no luck.
Any ideas?
Android Version: 2.2
Kernel Version: 2.6.32-ga81a44f
Mod Version CyanogenMod-6.0.2
I use the wifi tether from here: code[dot]google[dot]com/p/android-wifi-tether/
It says it's for 2.1 but it works fine in 2.2. FWIW, I'm running stock 2.2 rooted with unrevoked3.
It also creates an infrastructure network rather than an ad-hoc network, so you can connect with more devices, such as other android phones.
Howdy folks. So I had a hardware 0003 Evo prior to my current 0004 due to an insurance claim. I was running the latest stable CM7 and could tether it to my XP laptop without problems. However...
Now, with my new device Windows will not recognize the device at all as a RNDIS network adapter. I have tried the tetherxp.inf that worked fine, tried HTC Sync, and neither have compatible drivers that will work. The device shows up but after the drivers are installed Windows says the device cannot start. I have plenty of OS experience and have worked with drivers in the past...but for whatever reason it just wont work. The wired tether app has the same problem. I won't use PDAnet.
I've read several forum topics pertaining to this issue and none of the suggestions seem to do the trick. Even modifying the tetherxp.inf doesn't produce.
Does anyone know of a way to get this sucker to fire? I'm on CM7 N214 with Tiamat 4.0.8 kernel and Amon_RA's recovery...if it matters. No roms I've tried thus far make a difference. Thanks in advance!
Sent from my PC36100 using XDA App
Hello all, sorry if this is a repeat and all but I'm new to this and just came from an iPhone. After I rooted and flashed CM9 my USB tether does not work from the stock from or with pdanet. Its my only source of internet. Please help. Is there just a driver missing now?
Sent from my SPH-D710 using xda premium
USB Conx Issues After CM9 Flash
I am also having problems: I finally got my E4GT to take a custom rom (Thanks mobile ODIN!), but ever since the flash, my computers will not connect with the phone. It recognizes it as a SPD D710, but will not allow transfers. Kies says USB debugging needs to be turned off, but it is.
So I restored to my nandroid I made prior to the flash, but it did not fix the issue. I have tried re-flashing, and no luck.
TIA
Hey guys,
Updated KIES yesterday (Version 2.3.2.10454_19), and I'm now not able to connect my Galaxy S2.
I'm using the Mr. X Telus Mobility ROM, which as I understand is still the stock ROM.
Is anyone else having the same problem?
Windows 7 Enterprise x64, and, yes, I have rebooted
A lot of times Kies won't recognize a rooted phone.
Sent from my SGH-T989 using xda premium
When I had a Galaxy Fascinate (Telus) I had to unroot my phone, after re-installing a base Telus Rom, in order to get Kies to work. I think Kies is just very sensitive..... now I don't even bother with Kies.... so many other ways to communicate with the phone.
It took me a few tries to get a connection, The trick I found was to run Kies as admin, and it worked for me
Try restarting your computer if you just updated kies
Sent from my SGH-T989 using XDA
I had this issue before and I had to uninstall Kies, reboot then put it back.
Also make sure you're using a good cable.
VacTacks11 said:
Hey guys,
Updated KIES yesterday (Version 2.3.2.10454_19), and I'm now not able to connect my Galaxy S2.
I'm using the Mr. X Telus Mobility ROM, which as I understand is still the stock ROM.
Is anyone else having the same problem?
Windows 7 Enterprise x64, and, yes, I have rebooted
Click to expand...
Click to collapse
I have the same problem.
I plugged in my Telus S 2X.
Kies recognized, said there was firmware upgrade for the phone (ICS I expect), but instructed that I had to update Kies on my Win 7 computer (Win 7 Pro 64 bit) in order to update the phone.
I updated to the latest Kies (June 12 update). It no longer would connect to the phone. I ran the connection troubleshooter. No change. I uninstalled & reinstalled Kies & drivers on the computer. Rebooted several times. No change. I ran as an admin. No change. I made sure debug on the phone was off & tried a number of cables & USB ports.No difference - still no connection.
The prompt says: "cannot start service on the device"
BTW, my Telus Galaxy Note is recognized by the new Kies.
The s2 x works on Kies air as well - just not on Kies USB, which is required for the firmware update.
EDIT: After multiple tries, it just kicked in - didn't do anything other than what I specified above (??!!)
Same here. Kies will not pick up my phone :-(
Sent from my SGH-T989D
About KIES
KIES is help to use back up you entire media library . so you can update the mobile .KIES content air applications.
Only if you're running stock remember ....I think.
Sent from my SGH-T989 using Tapatalk
Got a GS3 a little over a month ago in exchange for an Evo LTE that was having serious text message issues. As soon as I got it, I was experiencing absolutely horrible battery life, so I immediately rooted and installed Blazer rom on stock kernel. I did this through Odin, so I had to plug my phone into the computer, which recognized it as a USB storage device so I could access files and whatnot.
Fast forward to now and I"m still having seriously battery life concerns. Today, I ran the one-click unroot/return to 100% stock zip from this link. I tried to plug my phone into my pc to load the file, but though it will charge, the PC won't recognize the phone. I ended up downloading the file to the phone and resetting to stock (thinking I was taking it to Sprint tonight). I made sure the most up-to-date Samsung drivers were installed. I updated my chipset drivers. My USB 3.0 drivers. I even updated the BIOS. Tried three different USB cords and all 14 USB ports (2.0 and 3.0). No luck. Windows keeps saying "One of the USB devices attached to this computer has malfunction and WIndows does not recognize it." I have XP, 7, and 8 all installed on this box and none would properly recognize my phone.
My question is whether this is a computer problem or a phone problem. Given my semi-advanced knowledge of computer hardware, I'm inclined to believe this is actually a problem with the phone, but don't want to go waste an hour or two at Sprint trying to get it fixed. Any insight is greatly appreciated. Picture of actual error included.
Wish I could help. I had a few issues connecting my S3 to my work computer, but downloading the Samsung drivers for the Sprint Galaxy S3 L710 from the Samsung web-site solved that problem. I'm using XP at work. On my home computer and my laptop, which are both using Windows 7 Ultimate, I haven't had an issue though.
Maybe try using the driver from the Samsung web-site or trying to install Samsung Kies and then connecting your phone.
davelikestacos said:
Maybe try using the driver from the Samsung web-site or trying to install Samsung Kies and then connecting your phone.
Click to expand...
Click to collapse
I tried Kies. I installed, uninstalled, and reinstalled the drivers twice, with a restart inbetween each step to be safe. No luck.
Stopped by the Sprint store today. They couldn't get it to work either so as it turns out it was actually the USB port on the phone.