Database Info

captivate not being read at all

i have tried everything but my phone isnt being read at all. it doesnt even show up under device manager but my phone recognizes it as being connected but the computer doesnt. i have a desktop win 7 32bit and a laptop win xp sp3 32bit and both dont read it at all. has anyone ran into this problem, if so can you help im really desperate!!
i also noticed whenever i open kies the mtp app says initializing and it seems it keeps restarting

Have you downloaded the drivers from Samsung?
Sent from my SAMSUNG-SGH-I897 using XDA App

yes i have im not sure as to why my phone is doing that

I have the same problem. Tried everything in Win 7 32bit both drivers... the one in samsung page and the first one before those... CANT get the captivate recognized by my PC. I tried with at win xp and it works... ANY HELP?

It might be the USB cable. Is it connected directly or through a hub? You might also try plugging it into different port.
Sent from my SAMSUNG-SGH-I897 using XDA App

i have windows 7 64 bit and here is what i did
1. go to Settings>Application>Development and turn usb debugging on.
2. After you connect it to the comp pull down our notifications menu and select USB connected. It will ask you if you want mount select yes and then go to my computer and it should be there.

If you have kies installed you shouldn't have any driver issue since installing that software properly is best way to insure you have the proper drivers installed. Try uninstalling Kies and installing it again with just the mobile box ticked it should work. I am also running Win7 32bit and use Kies without a problem.
Sent from my SAMSUNG-SGH-I897 using XDA App

BignutSquirrel said:
It might be the USB cable. Is it connected directly or through a hub? You might also try plugging it into different port.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
it seems that that was the problem thanks

Never forget to check the simple stuff. It can save you lot of headaches.
Sent from my SAMSUNG-SGH-I897 using XDA App

USB unknown device

I've tried the drivers from Samsung, Keis, ODIN one click. None of them worked on 4 different machines, Windows 7 both x64 and x86(which was a fresh install), and two Windows XP machines. I tried it on Ubuntu(10.04 LTS) and that recognized the captivate.
Anyone know how to get one of those to correctly recognize my Captivate so I don't stuck on Samsung's/AT&T's 2.2

uninstall all of the driver that you downloaded. uninstall kies. then go to samsung.com search for the captivate, choose you phone, click the 'i own this' button. then go to get downloads, software. click on the .zip file icon next to usb drivers. if that didnt work uninstall them then download kies again. if it still doesn't install them, open kies, click menu, reinstall drivers

What is it that you're trying to do?
Sent from my SAMSUNG-SGH-I897 using XDA App

If it is coming up unknown device try another port. You may want to try another microusb cable as well.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

I've always had luck with the drivers in the captivate aio toolbox. Even on a fresh win7 64bit when I replaced my boot drive with a ssd a month ago.

Samsung really failed at the USB drivers for the Captivate. I would expect to be able to install the drivers from their website. Plug in my phone, and have it working.
trell959 said:
uninstall all of the driver that you downloaded. uninstall kies. then go to samsung.com search for the captivate, choose you phone, click the 'i own this' button. then go to get downloads, software. click on the .zip file icon next to usb drivers. if that didnt work uninstall them then download kies again. if it still doesn't install them, open kies, click menu, reinstall drivers
Click to expand...
Click to collapse
I tried that before, didn't work.
bornjamerican said:
What is it that you're trying to do?
Click to expand...
Click to collapse
I'm trying to:
1) connect as a mass storage devices. Yes I know turn on USB debugging and to mount the drive.
2) flash back to stock 2.1 or root my phone so I can install a custom ROM on it. Might go with CM7/MiUi or something from Team Phoenix. So use Odin3
shinji257 said:
If it is coming up unknown device try another port. You may want to try another microusb cable as well.
Click to expand...
Click to collapse
Tried all of the ports on the computers. I don't have another microusb cable to test to see if that's the problem, but I'll check that tomorrow.
Johnnie5000 said:
I've always had luck with the drivers in the captivate aio toolbox. Even on a fresh win7 64bit when I replaced my boot drive with a ssd a month ago.
Click to expand...
Click to collapse
I'm going to try a fresh install of windows 7 32-bit with aio toolbox see if that works.
Tried my friends brand new microUSB cable. It worked.

I have tried 4 known good cables know, 4 different computers and every USB port available on all 4 of the PCs I tried. Only once did it identify the device and install the drivers and I was able to root it but I still can't sideload because after the reboot after rooting it is back to device not recognized/unknown device. This has been a total pain. Any suggestions? I'm not with AT&T any more so I am out of luck for just bringing it into a store and asking them to take care of it.
Edit: Sorry for bumping an older post but I did it instead of starting a new thread.

rmriggin said:
I have tried 4 known good cables know, 4 different computers and every USB port available on all 4 of the PCs I tried. Only once did it identify the device and install the drivers and I was able to root it but I still can't sideload because after the reboot after rooting it is back to device not recognized/unknown device. This has been a total pain. Any suggestions? I'm not with AT&T any more so I am out of luck for just bringing it into a store and asking them to take care of it.
Edit: Sorry for bumping an older post but I did it instead of starting a new thread.
Click to expand...
Click to collapse
If you're just trying to transfer apk files to it for sideloading, you can use a wifi transfer app. I use Wifi File Explorer and it's great. You can connect to your phone via web browser and upload/download anything on the SD card.
Another option is to use an external SD card that you can remove and plug into your computer, transfer the files to it, then insert it back into the phone.
This won't work for connecting to PC apps like Odin, Heimdall, or Kies, but for simple file transfers it works like a charm.
Additionally, regarding other usb cables, you didn't mention what types of cables you used, so I'll throw in another thought. The cables that come with the Captivate don't work on some PCs (like my new iMac). Third-party, generic usb cables might not work, either (I tried some and got a whole lot of fail). The only cable that works for me is the one that came with my wife's Motorola phone. If you haven't tried one yet, I would recommend getting your hands on a Motorola cable and testing it out. You'll immediately notice the cable is much thicker. I don't know if that has anything to do with why it works when others don't, but there's something about that cable that others don't have.

Bad Phone?
Could it be the phone port is having issues?
I've had the same problem and it seems that the port on the Captivate is shot which may be your issue. it will always charge; but tends to cause a lot of profanity when trying to get a PC connection to transfer files or flash it. It will be seen, then immediately play the 'unplugged' sound from windows. I've sat there and had it play the tones of plugged in and un plugged over and over again just by tilting the phone from side to side. No matter what cables I use (tried several but they are all samsung due to the recessed port). If it establishes the connection; I have to be very still with it or it'll lose it. If it loses it; I get unknown device messages or not functioning messages on that port until I reboot the PC.
Trying to flash anything via ODIN takes a lot of patience.
Those same cables / USB ports are used on my wife's Focus without ever having a problem. I wrote it off as too much flashing / overclocking of my phone but am not sure.

hi i was having this issue as well. i solved it by:
1. download a good & stable miui rom, rename it to update.zip and place it into your sd card. i took the sd card out of the phone and used a adapter to connect the sd card to my PC since i can't access my sd card through the usb port.
2. put the sd card back into my phone, turn off my phone. press and hold volume up and down buttons, then press n hold the power button till the screen shows something.
3. select install from sd. wait until the installation finishes and select reboot the phone.
4. when you're in your new miui rom, try to connect your phone to the pc via usb port again.
this worked like charm for me.
about the miui rom, i suggest you to use the one from miuiandroid.com (the UK version)
after flashing the rom im able to connect via usb and use mass storage.
hope this helps

Also, when you uninstall drivers, don't forget to look in the program files for anything that may have been left behind and delete it.

From the description it sounds strongly like you are actually experiencing a port failure which is common on the Galaxy S devices. PM me if you need this repaired...

Only try another usb cable, i bricked my cappy with a bad contact cable on odin, unknown device too, new cable=i897 device on windows notifications
try and feedback!

strange, this only happened to my when i soft bricked my phone. try connecting it to your computer in download mode

I had this issue once before. Here is what I did which resolved the problem. I was using a windows 7 PC
1. Download the ADB kit and extract it to C drive.
2. Connect your mobile to the PC on USB port
3. Wait for the drivers to be installed automatically (it might give you a failed to install message)
4. Never mind that message. Open Device Manager
5. In Device Manager, if you expand the "Universal Serial Bus Controllers", you'll see a device that has yellow question mark against it. This is your phone and since drivers are not installed properly, it has the question mark.
6. Right click that device, and select "Update Driver".
7. IN the window that comes up, select "I'll select a driver".
8. Browse to the folder where you have extracted the ADB kit on C drive
9. Check include subfolders and click Next.
10. The drivers should be be installed and your device should be identified by the computer.
Let me know if it works for you.

[Q] Why can I no longer mount usb

I have erased the contents of the phones internal USB storage. Now I notice that I cant mount to my PC.
Anybody know what happening or had same problem

Have you already tried formatting with CWM?
Perhaps this thread contains some useful information for you.

maksymillian said:
I have erased the contents of the phones internal USB storage. Now I notice that I cant mount to my PC.
Anybody know what happening or had same problem
Click to expand...
Click to collapse
I know this is a long shot but go to your dialer and input *#*#8778#*#* and make sure it looks like this pic. I fool with QPST and other things and sometimes forget to change the settings back to PDA and it will not mount. Long shot but what the hey...

alnova1 said:
I know this is a long shot but go to your dialer and input *#*#8778#*#* and make sure it looks like this pic. I fool with QPST and other things and sometimes forget to change the settings back to PDA and it will not mount. Long shot but what the hey...
Click to expand...
Click to collapse
Typed it in and got nothing. Using the android dialler when I pressed the last * the dialer cleared and did nothing.
Just installed the SDK so I could use (hopefully) ADB. When trying to install the Google driver rev4 windows says that rev 4 is no better than the one currently installed.
Also when I connect to the PC it says that the USB device is not recognised either.
I reckon my next thing to try flashing a new Rom via ROM manager.

well that didnt work in fact it has got considerably worse. I used ROM manager to download and install a new rom but didnt install the Gapps how daft do I feel now cos all I got is version of Blandroid running with no Android Market access to download ROM Manager.
I can access my WiFi network so I thought I would simply visit XDA via the mobile browser and download a fresh version of CM7 and then re-flash via ClockworkMod . However all I get is download fail error. I guess it doesn't know where to save the file.
So to recapp I have the following
a Nexus S (running Blandroid ROM)
a Win XP laptop that does not recognise my Nexus S (therefore cant install the Google driver to use ADB)
The Nexus S recovery is ClockworkMod and accessible.
I cannot accept that it is bricked (not just yet anyway)
I have another Laptop with Ubuntu installed. Will this help me in anyway to find a fix. I am not that experienced in Linux unfortunately.

1
i have the same problem. only thing you can try is.
pull out battery. let something metal touch the usb conecter .conecting the metal to a unload source(for static electricity.)
wait couple of hours,and try again.
if that didnt work.
2
open your nexus.
unplug all cables and screws from the main board.
again touch the usb conecter with something metal that has a ground source.
and try again.
the last step worked for me the 1st time pluging it in after i did that.
after that. usb didnt work again.
it probably has to do something with the usb phone charger and static electricity.
but i havent tested it.

will give that a try when I have a bit more time.
In the meantime I have been setting up ADB on my other laptop running Ubuntu 11.04. But unfortunately the Nexus S didnt register on the OS either. I thought you didnt need additional drivers for Linux only windows! I am really puzzled now as I thought the Linux option would have allowed me to flash a different ROM other than Blandroid (which isnt bad its just I dont have the Gapps installed)

maksymillian said:
will give that a try when I have a bit more time.
In the meantime I have been setting up ADB on my other laptop running Ubuntu 11.04. But unfortunately the Nexus S didnt register on the OS either. I thought you didnt need additional drivers for Linux only windows! I am really puzzled now as I thought the Linux option would have allowed me to flash a different ROM other than Blandroid (which isnt bad its just I dont have the Gapps installed)
Click to expand...
Click to collapse
you still have wifi/3G and CWM or bloothoot?
download the Gapps zip. put it on dropbox or any hosting site.download it trough your mobile browser and flash it trug CWM.
or use blutethoot to download it.
might be a short fix.until you get USB to work.
(this is how i do it cuz my usb doesnt work.)

I did try that but for some reason after stating that the download had started - Download Unsuccessful was displayed in the notification area. As useual I open a door only to find a brick wall on the other side.
In the meantime I am back with my HTC Hero.
Thanks for helping anyway!

maksymillian said:
I did try that but for some reason after stating that the download had started - Download Unsuccessful was displayed in the notification area. As useual I open a door only to find a brick wall on the other side.
In the meantime I am back with my HTC Hero.
Thanks for helping anyway!
Click to expand...
Click to collapse
try difrent download solutuins.
seeing you have HTC here.why not tranver your zip trug your hero to your Ns?(with bluethoot)

boy, i hope you haven't started tearing your phone apart yet...
since you still have access to cwm: try to format your sdcard with it. looks like you haven't done that yet.

I would try to uninstall all drivers and associated programs on your PC. Then reinstall the drivers. Windows can be very finicky as you know. Also try PDANET drivers.

ghost010 said:
try difrent download solutuins.
seeing you have HTC here.why not tranver your zip trug your hero to your Ns?(with bluethoot)
Click to expand...
Click to collapse
10 out of 10 - I just got my market back . downloading rom manager will shortly be back on CM7.
USB connection still not working yet but at least I got my account back on the NS and so the phone is usable

wild1z said:
I would try to uninstall all drivers and associated programs on your PC. Then reinstall the drivers. Windows can be very finicky as you know. Also try PDANET drivers.
Click to expand...
Click to collapse
The NS wouldn't connect to laptop with Ubuntu running. I am beginning to think that I have a faulty micro USB port.
Ill try the pdanet drivers later tonight - are they different from the google rev 4 drivers?

maksymillian said:
The NS wouldn't connect to laptop with Ubuntu running. I am beginning to think that I have a faulty micro USB port.
Ill try the pdanet drivers later tonight - are they different from the google rev 4 drivers?
Click to expand...
Click to collapse
Same PC with dual boot? Yeah, try another cord and a another PC. The fact that you plugged it in and it's recognized in some way in the tray says something is fubar. I just don't know if it is the phone though. Best of luck.

Nah, different laptop and different cable. Hope that it charges OK. Gonna have to get a WiFi file transfer app working to move files to and from.

glad to help out :3
there are allot of people that have this USB isue and its HW NS related. nothing we actually can do about it.plus it also happens after changing kernels and roms(i supose) overclocking might be 1 of the reasons thus the voltages not being original.
btw,sorry for my half assed english x3

Double check the modem/pda settings mentioned in post #3. Should be set to pda to see the files on the SD.

Moritzio said:
Double check the modem/pda settings mentioned in post #3. Should be set to pda to see the files on the SD.
Click to expand...
Click to collapse
Having the same issue. I tried that, no such luck.
My computer *did* connect at one point though... couldn't mount USB storage (wasn't prompted) but it did ask for a driver, and currently has a Samsug USB one installed. It won't accept the SDK driver (not 64-bit capable? Or NS4G? Idk...)

Moritzio said:
Double check the modem/pda settings mentioned in post #3. Should be set to pda to see the files on the SD.
Click to expand...
Click to collapse
I got nothing when I entered *#*#8778#*#*. I simply typed it in using the keypad on the dialer. Is there something else I should be doing?

Any official fix for MTP driver installation failed?

I just got a S3 yesterday but was greeted with the dreaded MTP driver installation failed message on win 7 (32 bit)
I installed the regular verizon s3 drivers from samsung's site, did the same thing, uninstalled and tried Kies and let it install the drivers, same problem
tried a different usb port, same thing
restarted the comp and computer, still no go
im getting frustrated now
it seems samsung has known about this issue for over a month now but still hasnt been able to fix it
my a500 and galaxy nexus work fine with MTP so not sure why this would mess up
ive looked at other threads but there was no clear solution on how to fix it

I don't have any issues with mine
Sent from my SCH-I535 using Xparent Blue Tapatalk 2

thats nice but it doesnt exactly do anything for my problem

Joey22688 said:
thats nice but it doesnt exactly do anything for my problem
Click to expand...
Click to collapse
Did you try a factory reset?
Sent from my SCH-I535 using xda app-developers app

This happened to me too but I was running a CM10 ROM. What are you running and have you tried a different ROM?
Unfortunately, I cannot remember exactly what I did but I recall allowing Windows (I'm on W7) to find the drivers and install for me.

I'm not having any issues either, I'm using both 32/64 versions of Win 7...
These are the drivers I'm using:
http://downloadcenter.samsung.com/content/SW/201206/20120620051748445/Verizon_Wireless_I535_GSIII_Samsung_USB_Driver_v1_4_6_0.exe
Hope this helps..

I think I found the problem (its not the phone)
its the drivers that samsung issued
I plugged the phone on my win 7 64 bit desktop (not installing any drivers beforehand) and I got a few failed messages for drivers but I was able to access the file system fine
I then installed the driver pack posted and above then got the mtp driver installation failed message and was unable to access the file system
uninstalled the driver pack and connected the phone back up and I can access the file system (with some other drivers failing to install, I think relating to usb modem stuff ect...)
so until samsung fixes the driver problem I will have to deal with a few driver installation failed message every time I hook up the phone, but at least I can access the file system
im running the phone on the stock ics btw, didnt install cm10 or anything like that, the phone is rooted though but I rooted it after I found out about the mtp driver problem so it shouldnt mean anything

I have the same problem on Windows 7 32 bit. I rooted my phone and installed samba as a temporary fix.
Plus I just bought an external 32 GB SD card and I plan on using that as my workaround and just transfering files between the two.
Sent from my SCH-I535 using Tapatalk 2

Problem for me was the root.
Could you humor me and try this:
- go into the superuser app
- Select the 'temp unroot' checkbox from the first screen.
- unplug then replug the USB cable on your phone. The drivers should install on the first try this time (they did for me) and Kies should work too.
The problem seems to be that SuperUser exploits the USB Debug internally so, even though USB Debug is unchecked, it is still detected as checked by the connection and fails the install of the driver.
Solution #2 is the amazing script that transforms your MTP connection into a UMS one (look in this thread http://forum.xda-developers.com/showthread.php?t=1785243 and thank open1your1eyes0 ). Once in UMS, you don't need the MTP driver to see your device so that's another approach.
Good luck

I bought Samsung Galaxy S3 2 weeks ago. Windows installed the drivers for it when first connected to my Windows 7 64 bit PC. It came up in the list of Devices on the Explorer. I installed "Kies_2.5.0.12094_28_8" which installed USB driver on top of the Windows driver. At the end of the installation, it gave "failure to install Samsung MTP driver".
Saw a thread on other forum where it was suggested to remove the driver from System Driver window under Control Tab/System and reboot. To be cautious, uninstalled Kies. Rebooted PC. Windows installed the driver. As soon as Kies was installed the whole issue unfolded again.
Looks like ALL Kies versions (including previous version of Kies_v2.3.3.12085_7_5) have incompatible and wrong driver which is resulting in this unresolvable situation.
I removed the MTP driver (control panel/system/device manager - MTP driver has ? mark - this is the one). Then removed the phone and rebooted PC. After reboot, connected the phone back. Windows detected the device and automatically installed the driver. The device is listed in Explorer and is fully accessible. Started Kies. It showed the device as GT-I9300. It took a while and connected to the phone. All functions became useable. Sync'ed the contacts etc.
Day2. Booted the PC. Device is still shown in Explorer. Kies shows GT-I9300 and then displays "Connecting Device" - IT FAILS TO CONNECT and on pressing "Trouble shooting" button, it re-installs its own drivers and fails to install MTP driver AGAIN" - the Kies software SUCKS

Solved! For real!
For some reason, any of those options helped me to make it work:
- Reinstall Windows Media Player
- Remove registry key
- Clean up old usb drivers
- re-install 100 times drivers from Verizon, Samsung. Even old versions.
- Install from Windows Update. I tried to do that 1000 times. Gosh!
- enable UMT access (mass storage) on the phone.
The only thing that worked was, for some reason , getting the drivers from a random computer that was the only computer that worked.
Windows 7 x64
Attached the files. Go to the devices manager and update the drivers.
Israel Leite

How I solved it
Joey22688 said:
I just got a S3 yesterday but was greeted with the dreaded MTP driver installation failed message on win 7 (32 bit)
I installed the regular verizon s3 drivers from samsung's site, did the same thing, uninstalled and tried Kies and let it install the drivers, same problem
tried a different usb port, same thing
restarted the comp and computer, still no go
im getting frustrated now
it seems samsung has known about this issue for over a month now but still hasnt been able to fix it
my a500 and galaxy nexus work fine with MTP so not sure why this would mess up
ive looked at other threads but there was no clear solution on how to fix it
Click to expand...
Click to collapse
1. Un-install Samsung Kies and USB drivers
2. Then install the Install Samsung Usb driver for mobile phones version 1.4.6.0
3. with phone un-pluged from the usbcable Go into settings/Developer Options un-check Stay Awake un-check USB debugging un-check Allow mock locations Now hit the HOME button then plug in the USB cable and your are set..
This worked perfectly painless for me :laugh:

Solution x Win XP
This solution worked for me.
Install microsoft patch for usb and reinstall MTP driver
see:
http://forum.xda-developers.com/showthread.php?t=1150211
Hope this helps

No any PC recognizes my tablet

see if you can help me,for some time now no device recognize my tablet, did not give much importance and all that happened I do sd taking the tablet and connecting it to my s3 this if I catch him, but clearly not as comfortable.
I thought it would be a thing of windows 8, but I've tried on other computers with xp, win7 and nothing.
I do not remember if it stopped working when I put cyanogenmod10. I love cyanogen by fluent but I downloaded the latest official samsung already incorporates the attractively landscaped MULTI I find on a tablet.
I installed and uninstalled samsung kies but nothing.
and clear to not hold my tablet I can not flash by odin.
I'll see if I find any official version as I downloaded but it is for recovery mode.
the model is the tab2 10.1 gt p5100
Thank´s in advance

Have you installed the drivers properly for your tablet? It took me sometime to get my tab to register on the computer too.
Sent from my GT-P3113 using Tapatalk 2

If it was when you went to Cyanogen Mod then something you could check (haven't heard of it on these tablets, but it is a known issue on another device I own) is go into the settings menu, scroll down to "Storage" and click into it, now find the menu button (not sure where it is on these) and tap it, it should not give you an option for "USB computer connection", tap that and make sure its on MTP or Mass Storage (if that is an option, depends on device and ROM), on the unofficial CM builds for my other android device you can't connect it to the computer after flashing the ROM till you go in and pick a setting there.

Install drivers by installing samsung kies

Luigi2012SM64DS said:
Install drivers by installing samsung kies
Click to expand...
Click to collapse
Kies drivers have NOTHING to do with being able to connect it to the computer to transfer files, also there is absolutely no reason to ever install Kies as you can get the Samsung drivers easily enough and that is a much smaller download. http://forum.xda-developers.com/showthread.php?t=961956

daniel644 said:
Kies drivers have NOTHING to do with being able to connect it to the computer to transfer files, also there is absolutely no reason to ever install Kies as you can get the Samsung drivers easily enough and that is a much smaller download. http://forum.xda-developers.com/showthread.php?t=961956
Click to expand...
Click to collapse
That too. But it is easier to let Kies install it for you.

I was baffled by a similar experience.
The answer for me was to go to your settings in your device > storage settings > choose either MTP or Camera (check / tick a box)
Then the mac or pc should connect or recognise your device as long as you have the latest version of kies correctly installed.
:good:

install the drivers properly
or use another usb wire