Hi all,
I have been strugeling for days now amd figured I will reach out. I have an intercept and over my dead body I can not get my workstation to connect to the phone. Initially my OS was Win7/64, which I saw there was no drivers for this phone. I then loaded a XP VM and it also failed trying a multitude of drivers. I dont know where to go from here.
I also tried (just a little though) on Win7/32 - no go.
Please if you have succesfully loaded the drivers for the Intercept, can you point me to where you got the drivers as well as what OS it is loaded on?
Sincerely,
J
i'm on win 7 64, and i seached around a while ago and ended up with some drivers for another samsung phone that ended up working on my system, and it only connected after i turned off usb debugging, i'll check out my computer and see what i did
It was a very furstrating experience for me. I ended up, finding a sollution over at:
http://forum.sdx-developers.com/index.php?topic=15586.msg194417#msg194417
It worked great. Thought if in future I want to drop a new ron on this baby, I am still stuck.
http://www.samsung.com/us/support/downloads/sprint/SPH-M910ZIASPR click on software do download the drivers.
Good luck with that one... those drivers got me nowhere
Did you try the Easy Tether drivers? http://easytether.blogspot.com/2010/10/easytether-drivers.html
Select Samsung
USB drivers
jluyt said:
Good luck with that one... those drivers got me nowhere
Click to expand...
Click to collapse
Not tooo sure what might have caused you an issue with the drivers from Samsung website. I have used them and never had any issues. I can tell you for fact, that Samsung, has changed their package of USB drivers for these Phones. I recently needed them for me new laptop, and i went there. When i seen the size of the package, i fired up my desktop, and compared the two. none the less i installed them ,and they worked better than the older package they had
Related
so i am new to android and i decided " hey why don't i try to root my nexus" so i tried and i cant get any father that checking if the computer can see my device which it cant for some reason. so i went online i figured out that i don't have the usb driver for android. so after that i tried to down load then and i even installed them and restarted my computer and it still wont work. so if any one can help me with my problem it would be greatly appreciated.
On Home Screen, press menu>settings>applications>development and make sure USB debugging is checked.
What OS you running?
Specs would help, where did you get your drivers? What other software have you tried?
i turned on the debugging and it still hasnt worked
i am running xp. i downloaded the android sdk from here
developer.android.com
i just want to put the modaco desire rom on my phone that my onl reason for wanting to root. i really like the sense ui
I am having a similar problem, so i might as well use this thread instead of creating a new one.
I have a dual boot computer, win7 and fedora, both have SDK. I unlocked my nexus one with windows, as i noticed the commands were considerably easier, or at least they don't work when i plug the linux ones into fedora.
Last night i was going to push the undervolt kernel so i plugged my n1 while in win7, It instantly came up complaining about drivers, which i had already installed and had previously worked, i went to re-install them, and windows says they are up to date, but still no luck recognising the device (Debugging mode is definately on)
So i switched to fedora, no driver pop ups obviously, but when i try to push the kernel through, it does not recognise the device.
In the bootloader it says "fastboot usb" while plugged in.
I can't pinpoint when it stopped working, but the last time i used fastboot was to put the RA recovery, since then i flashed CM 5.0.2, CM 5.0.3.1, the desire rom, and used a nandroid restore to get back to 5.0.3.1
Anyone got any ideas? Without fastboot i am pretty much restricted to flashing .zip files from the recovery.
yeah i cant even unlock mine its so frustrating
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...
temperbad said:
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...[/QUOTE
Yeah I know how you feel its so frustrating I tried all day yesterdAY too
Click to expand...
Click to collapse
drbrendin said:
temperbad said:
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...[/QUOTE
Yeah I know how you feel its so frustrating I tried all day yesterdAY too
Click to expand...
Click to collapse
I tried all day too like a gazillion times.... and wonder does everyone have driver issues? I tried with my XP computer and windows 7, no go, then I read posts people having the same issue, then they just post " nevermind got it" and didn't even write what they did to get it.......
Click to expand...
Click to collapse
not everyone is a dev
Ok, I have my Nexus One set up so I can use with via Windows 7 (desktop) or Ubuntu (Laptop).
The Linux part is a bit more involved, but since everyone is running Windows (unless I missed something), I will work there.
First of all, your phone needs to be in Dev mode (which was covered earlier).
With the phone UNPLUGGED from the PC, uninstall any previous SDK installs you have and be sure to remove the directory.
Then, install the SDK found here: SDK
Install this SDK and let it complete the install, which will include downloading for a bit. You need to do this since the SDK package above does NOT include the right drivers!!!
Once this has been completed, plug your phone into the computer via USB. Your computer will find a new device, however, it cannot locate the drivers for it. Browse and point the installer to:
DRIVE:\PATH_TO_android-sdk-windows\usb_driver
Don't go any further than this!!
Now, let it do it's thing and you should have a new device in the device manager called:
Android Phone
...|_Android Composite ADB Interface
Now, go to the command prompt and change to the following directory:
DRIVE:\PATH_TO_android-sdk-windows\tools
There, you will find adb.exe
Type:
adb devices
and you should see:
List of devices attached
HT019P801614 device
If not, something got screwed up and would need to dig further to help ya.
Ok ill give this a try once get home from school
nexus one root.
Ok assuming that you have the android sdk installed correctly, try rooting your phone via the superboot method. The first link below has a full detailed guide for rooting the nexus one and I believe has all of the device drivers for those who have not been able to get them running well. If you still have trouble getting the drivers working checkout the second link. Anyone who is relatively new to working with the sdk and is not familiar with working the commands check out the third link. Read the entire thread! it is very helpful.
1) http://theunlockr.com/2010/01/02/how-to-root-the-nexus-one/
2) http://forum.xda-developers.com/showthread.php?t=613217
3) http://forum.xda-developers.com/showthread.php?t=619153
If you have any questions PM me on xda. I'll try and help in anyway, it took my like two days to actually root my nexus, I wasnt familiar with using ADB and Fastboot to root.
One thing I know I was having problems with since I came from the G1 was that the new SDK has to actually be installed via an .exe now. I was used to it all being in a zip so I kept trying to load up what I thought were the right USB drivers, but they were actually the 1.6 drivers I already had. So make sure to run the .exe that comes with the SDK.
ok so while i was downloading the sdk a notification came up that said that it could not rename the directory. is this bad?
i am having an issue with installing the right driver as well. my computer keeps installing the nexus one as a "mass storage device". i have uninstalled and reinstalled a few times but no luck. i have the phone set to debug mode, using XP btw. any help would be appreciated.
ok, I'm not really a noob but I'm having a horrible time w/ drivers for my Epic.
I had almost a 3 or 4 day long project to get drivers to load and work for my samsung moment..
I have uninstalled them and am now trying to get drivers to install and work for my Epic so that I can 'one click root' and install clockwork mod recovery.
My dilemma is, the drivers that are available here for the Epic seem to install fine. After I restart the computer, I put the phone in USB debug mode, then plug it in.
The drivers attempt to install, the computer recognizes the "Samsung SPH-D700" but in the right side of the window it says "failed"...
been trying all weekend to get this working.
I'm using Win7 64bit Ultimate FWIW..
When I had this problem w/ my samsung moment, Part of the culprit was the USB cable so i ran down to radio shack and purchased a $20 cable out of necessity. I'm using that same cable as well. The one that came with the phone is at work and unavailable at this time.
Thanks for the help
http://randomtechinfo.com/epic/Samsung_Mobile_Driver_V1.3.800_For_SPH-d700_Epic_4G.zip
I had better luck with these drivers in xp than the other two that were "confirmed" working. They worked once, then I removed them and reinstalled moment flashing software, then removed that and tried reinstalling the drivers. It wasn't working. There was something on the phone the drivers wasn't recognising. I flushed them out and installed the link above and it worked like a champ. I don't know if you'll have any luck with 64bit os. It's worth a try. Also, did you try changing to a different usb port?
Yeah I tried using different USB pets and no luck.
Are you using the stock cable that came with the phone ?
I'll try the drivers from the link you posted and report back. I can always run then in compatibility mode if need be.
Thanks.
Sent from my SPH-D700 using XDA App
Ive tried the one that comes with the evo. It's flaky but sometimes works. The one that usually always works, don't know where the epuc one is, is the over prices official one at a corporate sprint store.
Problem 1: (trying to get fastboot to work)
I downloaded the latest SDk and used the drivers in there. When I goto "update" my Android ADB driver and point it to the the google usb driver, it tell me to go jump off a bridge.. Though I fail to see how that will make my driver install
Anyway that's where i'm stuck, i've tried replacing the .sys files and blew up my XP blue screen at boot which was awsome..
I'm trialing a Streak to replace my iPhone4, This seamed to be the only phone so far that really WOWed me, that was until I used it, with 1.6 it's no iPhone killer..
I am also a previous HTC Advantage user, so i like big phones...
Any Ideas? Maybe i need the old 1.6 SDK Drivers?
This is all to get FastBoot to work, so i can start installing roms.
Problem 2:
Is there anything that I need to be careful of having an ATT phone over an 02?
try dell's drivers.
I found that using XP I had to install the drivers multiple times for it to register the Android 1.0 or whatever.
I simply used the QDL Tool on my locked-to-contract AT&T Streak 1.6. Like I said, I had to install the ADB drivers multiple times (I think that is their name) for it to finally go through. And then on the 4th time or so, it all went smoothly and I'm now running the "official" 2.2
I did nothing special. Just ran the Tool, installed the drivers, if it failed, I installed the drivers again, and ran the Tool again. I think maybe 4th time of installing drivers was the trick. I don't know what I did differently on the last time, but it worked just fine.
subvecto said:
try dell's drivers.
Click to expand...
Click to collapse
Tried that as well, no dice...
stang393 said:
Tried that as well, no dice...
Click to expand...
Click to collapse
That is strange... I was able to get dell recognized by win7 only via drivers that was installed via dell PC sync software...
Sent from my Dell Streak using Tapatalk
So I want to root my phone, but I cannot get ANY computer to recognize the phone when it is in either download mode, or debug mode.
I'm running Sprints stock EB13 right now.
I've downloaded the samsung drivers and installed them.
I've tried 3 computers -- A XP 32bit, a vista 64bit, and a 7 64bit system. I've also tried 3 different cables. Nothing works.
The phone is recognized fine in mass storage mode.
Tried restarting the phone many times, removing the battery, etc.. same with the computer side of things.
I'm out of ideas to try and can't find a good post with a fix.
Thanks for any input!
syntax_erorr said:
So I want to root my phone, but I cannot get ANY computer to recognize the phone when it is in either download mode, or debug mode.
I'm running Sprints stock EB13 right now.
I've downloaded the samsung drivers and installed them.
I've tried 3 computers -- A XP 32bit, a vista 64bit, and a 7 64bit system. I've also tried 3 different cables. Nothing works.
The phone is recognized fine in mass storage mode.
Tried restarting the phone many times, removing the battery, etc.. same with the computer side of things.
I'm out of ideas to try and can't find a good post with a fix.
Thanks for any input!
Click to expand...
Click to collapse
what are you running on your PC that you want to connect to the phone with?
Odin (in download mode?)
ADB in debugging mode?
What exactly are you trying to run ??
jdelano said:
what are you running on your PC that you want to connect to the phone with?
Odin (in download mode?)
ADB in debugging mode?
What exactly are you trying to run ??
Click to expand...
Click to collapse
I wanted to use Odin to go back to DI18 at first. After that didn't work I tried ADB in debug mode, and that no longer works!
I know ADB in debug mode used to work when I was on DI18 because I used it before when I first got my phone. Now I've upgraded to EB13 from the file samsung provided on their website. I've also tried a hard re-set of the phone and that didn't help either.
I had a similar issue. I was able to resolve it by creating a fresh user in windows and then running it from there.
Sent from my SPH-D700 using XDA Premium App
iil said:
I had a similar issue. I was able to resolve it by creating a fresh user in windows and then running it from there.
Click to expand...
Click to collapse
umm..yeah three complete different computers?...I don't think thats the case.
syntax_erorr said:
So I want to root my phone, but I cannot get ANY computer to recognize the phone when it is in either download mode, or debug mode.
Click to expand...
Click to collapse
I had this exact problem with my Epic also. I tried rooting my fone too, for like 2 months straight, with no luck... Tried every technique, software, and trick in the book and nothing worked...
2 days ago though, I finally rooted it using this solution:
Forget about trying to "root" it.
Instead, flash the "Stock EB13 Deodexed EXT4 + CW 3.0.0.6" to your fone (search the forum, you'll find it and the thread that explains how to do it).
It's pre-rooted too!
It worked fabulous for me. I am now rooted and well on my way to fully customizing my fone.
Odin is finicky though... I had to switch the usb cord around to several different ports before it recognized my fone. Also, it kept locking up at a certain point in the flashing process, but after moving the image from "Phone" to "PDA" (you'll know what these are once you open up Odin), it worked brilliantly.
Try it, it works!
P.S. Just in case this helps anyone; I should note that originally I upgraded from Eclair to the official unrooted straight from Samsung (before they pulled it) stock Froyo. I loved it, but wanted it rooted.
I read somewhere that it was easier to root it if you reverted back to Eclair first. So I did (search forum for uninstalling Froyo).
And from Eclair, I flashed to the above mentioned rooted and deodexed version of Froyo (EB13).
Hope it helps!
syntax_erorr said:
I wanted to use Odin to go back to DI18 at first. After that didn't work I tried ADB in debug mode, and that no longer works!
I know ADB in debug mode used to work when I was on DI18 because I used it before when I first got my phone. Now I've upgraded to EB13 from the file samsung provided on their website. I've also tried a hard re-set of the phone and that didn't help either.
Click to expand...
Click to collapse
Might try looking at the usb on the phone to check for something preventing a good connection; I've read where people have found bent connectors and were able to fix it.
Good luck; that has to be extremely frustrating.
I tried everything like you, multiple cables, multiple computers, EVERYTHING!!!
I finally broke down and took it to sprint and they couldnt even get it to connect or fix the problem so i got a new epic. You might just want to take it back and get another one. Im on my 3rd epic now so that should tell you something about these ****TY phones...
First, I'm not a newb, but I'm at my wits end so I'm swallowing my pride and posting this here.
I recently wiped my hard drive and reinstalled Windows 10. Prior to that Windows could see my v20, I could transfer files and ADB worked fine.
I installed command line tools to install ADB/drivers and tried both LG mobile 4.20 drivers and even tried the Intel drivers. Along the way I dusted off usbdeview to clear out the drivers and start over so likely further screwed things up.
I was able to eventually get ADB functional but no matter what I did the device wouldn't show up as a portable device under My PC.
I've finally said screw it and am currently reinstalling windows 10 from scratch for a fresh start.
So, looking for input as to the best way to proceed on fresh Windows install. Is best way to install adb/adb drivers by installing command line tools rather than full android studio? Does it matter what order I install LG drivers/ADB?
I'm running the notsostock 5.5 dirtysanta rooted on a verizon v20.
Thanks.
I haven't been able to get it to show as a portable device since flashing the NotSoStock rom. I'm on Windows 7, it was visible just fine prior to flashing and I haven't done anything to the computer in the meantime.
I've been assuming it was something goofy in the rom rather than windows drivers... It just hasn't been a big enough deal for me to monkey with, I don't often need that, and adb still works fine so I just push/pull stuff if I need to move anything...
ZachJohnson said:
I haven't been able to get it to show as a portable device since flashing the NotSoStock rom. I'm on Windows 7, it was visible just fine prior to flashing and I haven't done anything to the computer in the meantime.
I've been assuming it was something goofy in the rom rather than windows drivers... It just hasn't been a big enough deal for me to monkey with, I don't often need that, and adb still works fine so I just push/pull stuff if I need to move anything...
Click to expand...
Click to collapse
I came to the same conclusion about 4 hours ago. It was the NotSoStock rom that broke it. I wiped my v20 and installed the WETA rom and everything works perfectly. The dialer lock issue I had with that rom is gone. The hotspot issue is gone, etc. I've only been on it for a few hours, but it's definitely better than what I was on before.