[Q] Having some driver issues that I need help with - Epic 4G General

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.

Related

[Q] Trouble getting "Android 1.0" driver in XP can't get fastboot to work

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

Debugging - Download mode / usb not recognized

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...

Really really bricked fascinate

windows wont recongnize my fascinate. yes it is a verizon. cant use odin as windows doesnt like my phone. and yes i did mess it up. Ive odin it a few times before with success. I have installed the samsung driver also. My question is, is it totally bricked or is there anything i can do?
Thanks.
Well what did you do prior to "bricking" it? What did you flash, etc.
Sent from my SCH-I500 using XDA App
Try a different USB port, different cable, and finally a Different computer.
Okay so what your saying is it will flash into: download mode If not and you see a black screen you could possibly try this so you will have to get an extra Mini USB to do so and a few other things: http://www.youtube.com/watch?v=Rdn5GoRjhn0&feature=youtu.be
If you are able to go into download mode ect there is no need for the above to be done. Or you might want to try looking at this: http://forum.xda-developers.com/showthread.php?t=1153310
I am not responsible for what you do with this information though read through carefully to see if you want to take these steps on your device. From what I read and see some have had problems switching back to Odin when this program took over.
What Sendan has said here would probably help us more as I just jumped right into it for you. There may or may not be a need to do these steps listed here if we have more info on what is happening with your device.
Give me a detailed description of what you did, what you used, and what happens to it now.
Sent from my GT-P7510 using xda premium
cleanerdude said:
windows wont recongnize my fascinate. yes it is a verizon. cant use odin as windows doesnt like my phone. and yes i did mess it up. Ive odin it a few times before with success. I have installed the samsung driver also. My question is, is it totally bricked or is there anything i can do?
Thanks.
Click to expand...
Click to collapse
Not sure if this will help, but I had a similar problem (PC wouldn't recognize phone in usb mode or download mode, Odin wouldn't connect, multiple cables had same result, remove/reinstall of Samsung drivers didn't help).
I ended up installing the Samsung drivers on a laptop that had never had them installed. Connection success! Was able to use Odin from that machine to flash back to stock Froyo/ED05.
After that, usb and download mode worked on the original PC. Same drivers that wouldn't work previously. Can't explain it, YMMV. It got me out of a jam.
Good luck.
maybe i freaked out. i put battery in just now and was able to boot into red recovery. yesterday i used it as an excuse to go buy a galaxy 2 on att. im trying an older backup. tried one a couple nights ago and it kept getting stuck. i have had the hardest time. started on a mac with heimdall and couldnt get it to work. went to a windows machine. couldnt get odin to work right with it. not sure now what i did to brick it. my win laptop i usually use is at my girlfriends. was just hoping to make this phone last til nexus prime.
Ok messing with it more. everytime i try something in recovery it will end up on the black screen with the phone to computer and the yellow sign between. heimdall (back on the mac) wont recognize it. not sure if i can do something in recovery
So Odin won't recognize your phone in download mode? You using the stock USB cord? Try different ports? Best thing would be to flash Stock ED05 and restart from there.
OK got it figured. Usb cord must be the problem. Now have cyanogenmod 7.1. But can't get gapps to install. Have tried rom manager and downloading it
Sent from my SAMSUNG-SGH-I777 using Tapatalk
And fixed gapps. Had to use power menu to recovery. So all fixed.
Sent from my SAMSUNG-SGH-I777 using Tapatalk

USB Drivers for Intercept

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

USB Device Not Recognized.

Hello, I was wondering if someone could help me. My computer no longer recognizes my tablet and says it is an unknown device when I connect it via USB. It won't detect it in odin either. I have the correct drivers installed and have tried reinstalling them and have tried it with different usb cords and different computers with the same result. USB debugging is enabled. I am not sure where to go from here. If someone could please point me in the right direction I would sincerely appreciate it. I would be able to restore functionality to be able to transfer files between my tablet and computer through USB once again.
ROM: BinDroid (Previous was CleanROM and had same issue)
If I download roms through tablet I can install them normally through CWM, and my tablet boots up okay so I am not really "bricked" But I am kind of bricked in the way that I can no longer use odin to flash anything..which is not very good.
bump
am i the only one with this problem.....
caaznkid said:
am i the only one with this problem.....
Click to expand...
Click to collapse
No, it is one of the big problems when loading ROMs, bootloaders, etc. Most of the time it is better to fully de-install the driver and then reinstall, as the change of the ROM also changes the perceived device-id by USB (on Windows I presume). I have even seen this happen between HC Stock and ICS Stock...
Odd but true. So, try to de-install the driver (or Kies, including driver) and reinstall (Kies, or just driver). Most of the time that should be enough, but do not hold it against me if that did not solve it.
Just_Another_N00b said:
No, it is one of the big problems when loading ROMs, bootloaders, etc. Most of the time it is better to fully de-install the driver and then reinstall, as the change of the ROM also changes the perceived device-id by USB (on Windows I presume). I have even seen this happen between HC Stock and ICS Stock...
Odd but true. So, try to de-install the driver (or Kies, including driver) and reinstall (Kies, or just driver). Most of the time that should be enough, but do not hold it against me if that did not solve it.
Click to expand...
Click to collapse
Here is a possible solution, disconnect device tab/phone, disable your firewall connect device, mine worked, disconnect again restart firewall reconnect device.
this worked for me and also with my s3.
I even tried it with a new computer that has not recognized the device before. I am afraid to use mobile odin as well and I can't backup all my stuff like my pictures and videos. I guess i could use upload to dropbox.
Sent from my GT-P7510 using xda app-developers app

Categories

Resources