Need help getting Adb to work with jt's vgb v3 and win7 - Fascinate Q&A, Help & Troubleshooting

I'm no noob by any means, but for the life of me I can't figure out how to get ADB to recognize my SF. I had no problems doing so with winxp, but I've been shooting blanks with win7. I've tried the fascinate drivers, and I've tried the nexus drivers, both to no avail. I have a device called fascinate in my device manager, but when I try to update the driver to the samsung drivers it doesn't work. I really need help to do this so that I can reboot into recovery to fix my unresponsive touch screen. Any help would be greatly appreciated.

Also, in case you were wondering, I have tried multiple data cables, multiple usb ports, and have used uninstall software to completely uninstall the drivers to try and reinstall them. All have gotten me nowhere.

RandomGuy982 said:
Also, in case you were wondering, I have tried multiple data cables, multiple usb ports, and have used uninstall software to completely uninstall the drivers to try and reinstall them. All have gotten me nowhere.
Click to expand...
Click to collapse
How did you install the Nexus S drivers? I'm using Win7x64 and ADB can see my SF running VGB/CM7. I installed the drivers through the Android SDK..
If you don't want to install the SDK, just get the .zip version and unzip, then find the drivers at /android-sdk/extras/google/usb_driver
Use it to install under Device Manager..
Good luck!

Related

Am I really rooted? Hope you guys with Samsung Experience can explain..

There are alot of things that are different compared to htc devices so far.
Now I rooted using this method:
http://forum.xda-developers.com/showthread.php?t=1285894
Downloaded and installed kies drivers, Downloaded odin, downloaded and loaded codeworkx, used superoneclick..it all went smooth. I tried different roms through cwm. Currently I'm running cm7 as I am so used to it. But here is my question, on two different pc's when I tried to run "adb devices" it cannot find my device. I wanted to push something and couldnt find my devices. I have the Superuser icon in my apps. Also when I tried to su in terminal app it said permission denied. I'm a bit baffled lol. All my drivers seemed to have installed fine.
SysAdmNj said:
There are alot of things that are different compared to htc devices so far.
Now I rooted using this method:
http://forum.xda-developers.com/showthread.php?t=1285894
Downloaded and installed kies drivers, Downloaded odin, downloaded and loaded codeworkx, used superoneclick..it all went smooth. I tried different roms through cwm. Currently I'm running cm7 as I am so used to it. But here is my question, on two different pc's when I tried to run "adb devices" it cannot find my device. I wanted to push something and couldnt find my devices. I have the Superuser icon in my apps. Also when I tried to su in terminal app it said permission denied. I'm a bit baffled lol. All my drivers seemed to have installed fine.
Click to expand...
Click to collapse
If "adb devices" failed you either have a driver problem or USB debugging is turned off
I do recall that with recent CM7 builds on my Infuse, root didn't work on first boot. I had to open the Superuser app or reboot, not sure which one fixed the problem.
Entropy512 said:
If "adb devices" failed you either have a driver problem or USB debugging is turned off
I do recall that with recent CM7 builds on my Infuse, root didn't work on first boot. I had to open the Superuser app or reboot, not sure which one fixed the problem.
Click to expand...
Click to collapse
usb debugging has been on. This issue I mention happened when I was stock, after I tried cognition, and now using cm7. Might be a driver issue, is there any other samsung drivers I can try for my windows machines?
SysAdmNj said:
usb debugging has been on. This issue I mention happened when I was stock, after I tried cognition, and now using cm7. Might be a driver issue, is there any other samsung drivers I can try for my windows machines?
Click to expand...
Click to collapse
if you are on CM7, i think you need to install the nexus S drivers, which are included in the Android SDK. you will need to run the emulator and run the update in SDK
Since you mentioned this has happened on two different computers, I doubt my advice will help. With that said, whenever I've had issues like this, I've found that USB ports tend to be the culprit. Have you been using ports on the front of a tower? Have you tried the ones on the back as well? Again, just taking a shot at a possible fix...

[Q] Odin issue

I can not get Odin to "See" my phone when it is in download mode!!!! I can get my phone into download mode without any issue. I can mount the phone as a mass storage drive without a problem. Any suggestions would be GREAT!!!
Which version of Odin are you using?
Do you have the drivers installed? Does it show up in device manager?
The best thing for you to do here is to download AIO Vibrant Toolbox. It comes with all of the drivers that you need and will allow you to put your Vibrant straight into download mode without the need for the button combinations. It comes with a good version of Odin and everything.
Give it a try and let me know if you have any more problems putting it into download mode.
Another problem that I ran into when putting my phone into Download Mode was the cable connections. The phone that I had second hand was a bit worn and I had to fiddle with the connector to get it all secure. Try another cable if you've got one lying around.
bluelink77 said:
Which version of Odin are you using?
Do you have the drivers installed?
Are you in download mode (yellow shovelling Android)?
The best thing for you to do here is to download AIO Vibrant Toolbox. It comes with all of the drivers that you need and will allow you to put your Vibrant straight into download mode without the need for the button combinations.
Give it a try and let me know if you have any more problems putting it into download mode.
Click to expand...
Click to collapse
Odin3 v1.81
Yes, the drivers are installed.
Yes, I can get to that screen.
I am using AIO Vibrant Toolbox. I used the drivers with that for an x64 system, did not work. I found newer versions of the drivers, still not working.
The weird part about all of this is that I had this working, on this computer, the last time I flashed ROM.
Reboot your computer. Try a different usb port. If that doesn't work try a different cable like chadhoard said. I had one that got loose and wouldn't make contact anymore.
jneal9 said:
Reboot your computer. Try a different usb port. If that doesn't work try a different cable like chadhoard said. I had one that got loose and wouldn't make contact anymore.
Click to expand...
Click to collapse
I tried those things, other then a different cable. I do not believe it is the cable, because I can mount the phone as a mass storage device without any issues.
Hm... Different computer then maybe?
jneal9 said:
Hm... Different computer then maybe?
Click to expand...
Click to collapse
I am going to try that later. Someone on another forum suggested disabling driver signature. Still fuzzy on how to do that, plus it is my work computer, so I do not want to screw anything up by doing that.
If the drivers are already installed I don't think driver signature should matter. Is that the computer you used before?
jneal9 said:
If the drivers are already installed I don't think driver signature should matter.
Click to expand...
Click to collapse
Any suggestions on how to make that I remove every last bit of the drivers off the computer?? I will just try re-installing them.
Depending on how you initially installed the drivers there should be an uninstall entry in Add/Remove Programs.
This is what I've always used to install the drivers. http://forum.xda-developers.com/showthread.php?t=728929
jneal9 said:
Depending on how you initially installed the drivers there should be an uninstall entry in Add/Remove Programs.
This is what I've always used to install the drivers. http://forum.xda-developers.com/showthread.php?t=728929
Click to expand...
Click to collapse
Would it matter that I am using Windows XP Professional x64 Edition?
jneal9 said:
Depending on how you initially installed the drivers there should be an uninstall entry in Add/Remove Programs.
This is what I've always used to install the drivers. http://forum.xda-developers.com/showthread.php?t=728929
Click to expand...
Click to collapse
Just un-installed the drivers through the control panel. Rebooted. While installing the drivers from that link, this popped up...
chadhoard said:
Just un-installed the drivers through the control panel. Rebooted. While installing the drivers from that link, this popped up...
Click to expand...
Click to collapse
Yeah just click continue. May come up once or twice more.
And no, it shouldn't matter that you're on XP. That's what I use.

[Q] Can't install S3 drivers

So, trying to install the driver exe file from Samsung's website and it won't work. Keeps saying that it failed to install drivers. And, if I have the phone as USB Debugging enabled, it'll pop up with 2 out of 4 that says it failed to install.
My roommate was able to install the .exe file on his Windows 8 beta laptop (I'm running Windows 7 64-bit) without a problem. And, the phone installed fine on his laptop as well. For me, no.
If USB Debugging is not enabled, then yeah, the phone is fine. But, since I want to root this thing, it won't accept the drivers. And, nowhere on Google, searching or Samsung's website provides me any answers whatsoever.
I've done:
Going through regedit and deleting all things Samsung related
Deleted every Samsung folder on my hard drive
Rebooted the computer
Uninstalled the drivers
Reinstalled multiple times
Downloading and installing Kies (did not install any drivers, still failed)
I've done everything I can possibly think of. Couldn't find any answers on here, either. And, doesn't help that the search function is broken.
So, anyone have any idea on how to fix this? And, please do not say "Reinstall Windows" because that's just ridiculous and I shouldn't have to do that for a simple phone driver install. I had my Epic 4G before and that all went smoothly.
Go do something in control panel and uninstall the samsung drivers that you already have on your comp
Then try installing
But I reccomend reinstalling windows
Sent from my SPH-D710 using xda premium
gtuansdiamm said:
Go do something in control panel and uninstall the samsung drivers that you already have on your comp
Then try installing
But I reccomend reinstalling windows
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
+1
I had the same issue with mine on xp. Uninstalled my et4g drivers and installed the gs3 drivers. After a restart, the pc finally recognized my phone as a mass storage.
gtuansdiamm said:
Go do something in control panel and uninstall the samsung drivers that you already have on your comp
Then try installing
Click to expand...
Click to collapse
I already said that I did that.
Volknochi said:
I've done:
Uninstalled the drivers
Reinstalled multiple times
Click to expand...
Click to collapse
And, I'm not reinstalling Windows all over again just for this phone, as I also said. But, it doesn't matter, I already got it rooted through the roommate's laptop.
EDIT: I managed to get it to work. My other half had similar problems with device drivers so just had to have me remove the phone from USB, uninstall driver and then plug the phone back in. And, it actually worked.

[Q] Vibrant soft bricked, can get to download mode, windows doesn't recognize device.

People!, I'm about to pull all my hair out on this one
Vibrant is soft bricked in a boot loop after a incomplete flash, I am able to get it into download mode but both my windows machines say USB device isnot recognized, and thus, I cant use ODIN to return to stock. When I try to manually point windows to the samsung drivers I get nothing…
So far I have tried drivers from:
-Bay_wolf's AIO Vibrant Toolbox 2.5
-USB drivers for vibrant from samsung support site
-Drivers from samsung keyes
Side notes that might help: I was perviously using a Hellybean Rom. My device displays "Galaxy S gt-9000" on boot... not sure when that came to be but maybe some rom changed some important recognition stuff??...
I found this thread http://forum.xda-developers.com/showthread.php?t=1008383 but no help...
Any help would be greatly appreciated!!
Try a different USB cable. This happens more than you'd think. Even cables that have worked just fine hundreds of times.
Also.... Locate the drivers in system/device manager and delete them manually and try to install them again. Unplug device and install fresh ones from either aio toolbox or Kies, then plug phone back in.
Best of luck!
Toast6977 said:
Try a different USB cable. This happens more than you'd think. Even cables that have worked just fine hundreds of times.
Also.... Locate the drivers in system/device manager and delete them manually and try to install them again. Unplug device and install fresh ones from either aio toolbox or Kies, then plug phone back in.
Best of luck!
Click to expand...
Click to collapse
Thanks a ton for reply but, sadly, no dice.
Tried connecting the phone, getting the "unrecognized device" prompt, finding "unknown device" in device manager, right clicking to uninstall. rebooting my machine, using various install methods to re-install drivers, re-connecting, and nothing.. same issue...
I lost the original cable a while back, but can't accept that NONE of the other 5 cables used are all broke... specially if the computer recognizes something going on... is it worth buying a new one?
Losing hope here, been like this for 4 days now, think it's time to go get a new phone. :crying:
Even so, it would have been nice to get what was a perfectly working phone back if only to keep it as a mp3 payer.
If anybody in New York, NY has a working odin set up that can do this for me, I have a 6 pack of your favorite beer with your name on it.
It could be a hardbrick such as bootloader getting corrupted that happened to my Sony Xperia Play (now an expensive paper weight).
I assume you boot into download mode by holding the two volume buttons, then connect the cable? Have you tried on a different PC? It can also be the weak powered USB port on the PC. Also when you uninstall the Samsung driver, check the option to also delete USB driver and uninstall any drivers. Also which version of the driver are you using, have you tried version Samsung USB Driver 1.5.3? And the drivers from here: http://www.samsung.com/us/support/owners/product/SGH-T959ZKATMB#
For what its worth, the gt i9000 screen appears after your on a custom GB boot loader and Odin back to stock (or probably Odin flashing any other ROM) you can change it by flashing the GB boot loader again. My phone says its a i9000 too, but I'm just about lazy enough to not bother changing it, lol.
So that's unrelated.
eksasol said:
It could be a hardbrick such as bootloader getting corrupted that happened to my Sony Xperia Play (now an expensive paper weight).
I assume you boot into download mode by holding the two volume buttons, then connect the cable? Have you tried on a different PC? It can also be the weak powered USB port on the PC. Also when you uninstall the Samsung driver, check the option to also delete USB driver and uninstall any drivers. Also which version of the driver are you using, have you tried version Samsung USB Driver 1.5.3? And the drivers from here: http://www.samsung.com/us/support/owners/product/SGH-T959ZKATMB#
Click to expand...
Click to collapse
Ok, faith momentarily restored. But I have questions:
-What do you mean when you say "check the option to also delete USB driver and uninstall any drivers"? I dont get such a prompt from right clicking on "unknown device" and selecting uninstall? Is there another method to uninstalling drivers?
-In the link attached, I can only find "Device(Install),USB Driver (Software) (ver.1.0)" not the 1.5.3 version mentioned. What am i doing wrong here? currently searching google for the 1.5.3 but finding nothing.
I get into download mode by holding volume- up + power. Have 2 PCs ( win xp and win 7) and a mac running mountain lion (but never ever have been able to get Heimdall to work, so devoting time to odin.)
Thank you for the time + help, guys, I really do appreciate it in the time of utter un-nerdness.
If the device is already installed it will have a check box that said "Delete the driver software for this device." If its unknown then obviously not. By "uninstall any driver", I mean uninstall any Android drivers you current have installed and reboot before you reinstall the new driver.
Although I doubt it will make a difference than the one I linked above, you can try the Samsung driver version 1.5.3: http://www.mediafire.com/?r0uc3h413qcy80z
If you did manage to get into download mode and see this: http://images.google.com/search?num=10&hl=en&site=&tbm=isch&source=hp&q=download+mode
Then it mean there is a very good chance you can restore the phone, if you can find a computer to recognize it and Odin to see a COM port.
I definitely think it would be worth the money to go buy an OEM USB cord. I can't tell you how many times I have seen this and a new USB is the fix.
sent from the depths of helly bean
OK guys...
My friend, who also owns a Vibrant, let me borrow the cable that came with the phone for the last 2 days.
Tried to make ODIN work on both PCs at home, gave Heimdall a shot on my mac, even hijacked a computer at work for the better part of the morning and freshly installed USB drivers 1.5.3 before connecting. All for nothing... “Unknown device” across the board....
At first I felt that with being able to get into download and have SOME kind of a reaction from connecting to PC had to be a good sign. Almost completely convinced that there is some unknown, unworkable hardware problem present. Definitely, officially, unremarkably out of ideas here.
Nothing is beautiful and everything hurts.
Last thoughts? Options at this point?
Also, tried One-click Unbrick tool on mac. I got a "is your phone plugged in, is it on download mode?" error, but anyone reading this down the line with a similar problem should check it out.
http://forum.xda-developers.com/showthread.php?p=15330252

Help with soft bricked vibrant

Hey everybody. I didn't get any replies in the vibrant section, and I figured it is also an over all samsung product question so here goes. I bought a very messed up samsung galaxy vibrant t959 off a friend for $20 hoping I could fix it. They had flashed a captivate rom to it but I can still manage to get it into download mode. But heres the problem. Odin wont recognize it when I plug it in it just says windows does not recognize device has malfunctioned or something along the lines of that, the bubble shows up over and over every two seconds. I got odin to recognize it once before, but my brother unplugged it XP. Now I can not get odin to recognize it again, any tips? I have a linux computer at my disposal as well if that helps. I am familiar with flashing, odin, android sdk, adb. I know I have drivers installed good because the same cable with the same port and same computer I actually modded this same device before my friend messed it up. Any help at all would be much appreciated.
blu422 said:
Hey everybody. I didn't get any replies in the vibrant section, and I figured it is also an over all samsung product question so here goes. I bought a very messed up samsung galaxy vibrant t959 off a friend for $20 hoping I could fix it. They had flashed a captivate rom to it but I can still manage to get it into download mode. But heres the problem. Odin wont recognize it when I plug it in it just says windows does not recognize device has malfunctioned or something along the lines of that, the bubble shows up over and over every two seconds. I got odin to recognize it once before, but my brother unplugged it XP. Now I can not get odin to recognize it again, any tips? I have a linux computer at my disposal as well if that helps. I am familiar with flashing, odin, android sdk, adb. I know I have drivers installed good because the same cable with the same port and same computer I actually modded this same device before my friend messed it up. Any help at all would be much appreciated.
Click to expand...
Click to collapse
I would recommend uninstalling and then re-installing your USB drivers and see if Odin will then recognize the phone. Another alternative would be to see if Heimdall recognizes the device and use that to flash the stock ROM to the device. If you are unfamiliar on how to use Heimdall I would recommend taking a look at this guide.
shimp208 said:
I would recommend uninstalling and then re-installing your USB drivers and see if Odin will then recognize the phone. Another alternative would be to see if Heimdall recognizes the device and use that to flash the stock ROM to the device. If you are unfamiliar on how to use Heimdall I would recommend taking a look at this guide.
Click to expand...
Click to collapse
Heimdall on windows also will not detect it
Would it make a difference if I tried it on linux? I'll also try reinstalling drivers
Edit: reinstalling drivers did not work
blu422 said:
Heimdall on windows also will not detect it
Would it make a difference if I tried it on linux? I'll also try reinstalling drivers
Edit: reinstalling drivers did not work
Click to expand...
Click to collapse
I believe you can download Samsung mobile phone driver on Samsung website
Sent from my SGH-T889 using xda premium
blu422 said:
Heimdall on windows also will not detect it
Would it make a difference if I tried it on linux? I'll also try reinstalling drivers
Edit: reinstalling drivers did not work
Click to expand...
Click to collapse
You can try it on Linux I can't guarantee it will make a difference but I would try it anyway. If you are going to try it on Linux make sure you configure USB access for the device correctly in order for the computer to recognize your phone.

Categories

Resources