Related
Well, I spent the last week or so having all sorts of creative fun with my new Captivate. Unfortunately, I was having the random shutdown issue, so I decided to remove SRE, SU, etc, using ODIN to restore my phone back to stock and get it exchanged for a new one.
I came home with my new phone today and proceeded to start the customization process all over. Before I did anything serious, I connected my new Captivate to my desktop, to both charge the battery and to sync with outlook using Kies.
With a full battery and my contacts loaded, I moved on the rooting and installing SRE. I then installed a bunch of apps, including ADW, ShopSavvy, and a bunch of games.
I then tried to get on the Market to download a few more apps. I forgot to 'emulate' T-Mobile to get around the AT&T censorship, so I fired up MarketAccess. I got an error message saying that MarketAccess couldn't get SU privs. That made no sense, since the phone was rooted, and SRE installed SuperUser. I downloaded the latest copy of Superuser and installed that. The SU problem was now fixed. (Turns out there was a glitch in the SRE I used. Designgears quickly fixed the zip file, but I was already using the glitchy one.)
Anyway, after loading a slew of apps/games, I plugged the phone back into the desktop to charge the battery some more. I got two error messages, one on the phone, and one on the desktop.
The phone complained that it was not on an 'idle' screen, since ADW was running. Since I had set ADW to be the default launcher, I used TitaniumBackup to temporarily uninstall ADW. (I couldn't figure out how to stop ADW and set TW back to the default.)
The desktop is more or a serious problem. I am now getting an info bubble saying that the USB DEVICE IS NOT RECOGNIZED.
The correct USB drivers are installed. I've used them to ODIN my previous phone back to stock. And they were working fine before I added SRE, ADW, etc.
I've uninstalled and reinstalled the drivers. Didn't help.
I tried USB Debugging, on and off. Didn't help.
I tried the age-old trick of unplugging the desktop and leaving it unplugged for 30 minutes. Didn't help.
So, here are my questions:
1) Does anyone know how to correct the DEVICE NOT RECOGNIZED error?
2) If not, is there anyway for me to restore the phone to stock without USB connectivity?
The phone still functions fine, just no USB. I was able to download the new SRE (with SuperUser fixed) using Dolphin browser. I then used My Files to rename and move the zip file to the root directory, and was able to install it fine. Is this same approach possible to restore to stock?
Thanks in advance...
Uninstall the usb drivers. Not sure what there called when kies installs it
fivebraids said:
Well, I spent the last week or so having all sorts of creative fun with my new Captivate. Unfortunately, I was having the random shutdown issue, so I decided to remove SRE, SU, etc, using ODIN to restore my phone back to stock and get it exchanged for a new one.
I came home with my new phone today and proceeded to start the customization process all over. Before I did anything serious, I connected my new Captivate to my desktop, to both charge the battery and to sync with outlook using Kies.
With a full battery and my contacts loaded, I moved on the rooting and installing SRE. I then installed a bunch of apps, including ADW, ShopSavvy, and a bunch of games.
I then tried to get on the Market to download a few more apps. I forgot to 'emulate' T-Mobile to get around the AT&T censorship, so I fired up MarketAccess. I got an error message saying that MarketAccess couldn't get SU privs. That made no sense, since the phone was rooted, and SRE installed SuperUser. I downloaded the latest copy of Superuser and installed that. The SU problem was now fixed. (Turns out there was a glitch in the SRE I used. Designgears quickly fixed the zip file, but I was already using the glitchy one.)
Anyway, after loading a slew of apps/games, I plugged the phone back into the desktop to charge the battery some more. I got two error messages, one on the phone, and one on the desktop.
The phone complained that it was not on an 'idle' screen, since ADW was running. Since I had set ADW to be the default launcher, I used TitaniumBackup to temporarily uninstall ADW. (I couldn't figure out how to stop ADW and set TW back to the default.)
The desktop is more or a serious problem. I am now getting an info bubble saying that the USB DEVICE IS NOT RECOGNIZED.
The correct USB drivers are installed. I've used them to ODIN my previous phone back to stock. And they were working fine before I added SRE, ADW, etc.
I've uninstalled and reinstalled the drivers. Didn't help.
I tried USB Debugging, on and off. Didn't help.
I tried the age-old trick of unplugging the desktop and leaving it unplugged for 30 minutes. Didn't help.
So, here are my questions:
1) Does anyone know how to correct the DEVICE NOT RECOGNIZED error?
2) If not, is there anyway for me to restore the phone to stock without USB connectivity?
The phone still functions fine, just no USB. I was able to download the new SRE (with SuperUser fixed) using Dolphin browser. I then used My Files to rename and move the zip file to the root directory, and was able to install it fine. Is this same approach possible to restore to stock?
Thanks in advance...
Click to expand...
Click to collapse
I had a similar problem and it turn out that Kies hosed up all my drivers...The only way I got it fix was by totally removing any trace of Kies and then uninstalled all my samsung drivers and usb drivers and then rebooted my pc. Then I reinstalled the samsung drivers and win 7 did the rest...
Well, I haven't uninstalled Kies yet. Although I have uninstalled and reinstalled the drivers from the ODIN thread. No difference.
I even uninstalled the ODIN referred drivers and tried the drivers directly from the Samsung site. Still no difference.
I'll go ahead and try uninstalling Kies and then the ODIN drivers, reinstall the ODIN drivers and see if that helps.
I've also ordered a new cable, since I've read a few threads on other forums where the problem was bad cables. I was going to go to AT&T and get a new cable, but they want $24.99. I just ordered a pair from Amazon at $3.99 each, with free shipping!!
Thanks...off to try ridding myself of Kies...
Well, deleting Kies (and associated drivers) didn't help!
After deleting Kies, I tried both the ODIN referenced drivers, as well as those from the Samsung site. Still not working!
I guess I'll wait on a new cable and see if that helps...
Okay, I think I'm in BIG TROUBLE here!!!
New cables arrived today, but they made no difference at all! Still getting the USB Device Not Recognized message. Doesn't matter if I plug the cable in while the phone is on and select any of the connection options (Kies, Mass Storage, etc.). It gives me the same message when I have Odin running and plug the phone in while holding the volume keys.
To further add to the problem, I tried installing the Odin referenced USB drivers on my wife's laptop which has never seen this phone or Kies. SAME PROBLEM!
I'm thinking there might actually be something wrong with the physical port on the phone. But this highlights my actual problem...
How can I return the phone (for the second time) when this phone has been rooted and is running SRE 1.2.1a ?!?!?
Apparently, there's no way for me to restore this thing to stock without USB.
Any ideas/suggestions?
Relax dude--I just got a captivate a few weeks ago, and have it working on tmobile.
For the drivers, when you plug your phone in, you're getting some errors. I know you uninstalled the drivers, but to double-check, open up device manager and see if there are any ! marks for the phone. Right-click and uninstall the entries. Also, you might try using a different USB port. I can only get my phone to connect using one of the 6 usb ports i've tried. Finally, and I don't know if these are the drivers for Odin, but I downloaded these drivers: SGH-i897_Captivate_USB_Drivers_5_02_0_2
When the phone connects, you might want to go to device manager, find the device(s), righ-click and and select 'update driver'. then, in the driver update window, pick 'manual' or 'let me specify location' and navigate to the unzipped SGH-i897_Captivate_USB_Drivers_5_02_0_2 file. Then, it should work.
Like I said, I have no idea if those are the drivers for odin...but I'm about to find out
I'd like to relax, but I think I'm dealing with a phone with a bad usb port...and since I've rooted, SRE'ed, etc., I won't be able to return it.
Anyway...
The driver you're using is the 'direct from Samsung' version, not the one for Odin.
Regardless, I've been through the exercise you propose...both with the Samsung and Odin drivers. When you attempt to manually install drivers, you need to point the installer to the ".inf" setup information file to use. The Samsung driver has three: SSADADB2.inf, SSADBUS.inf, and SSADMDM2.inf.
I get the following message when trying to use any of these three setup files:
The specified location does not contain information about your hardware.
Oh, and I've tried several different USB ports on the computer...both on my external hub and directly into the back of the machine.
Thanks for the suggestions, but still not working...
I'm really thinking I have a bad port on the phone...especially since trying the connection on my wife's laptop produces the exact same error.
Dam...
Still trying to find a way to restore the phone to stock without a USB connection...
i also have this "DEVICE NOT RECOGNIZED" on my sony x1.
Drivers
I was having trouble using the USB drivers from Samsung the one's you were using SGH-i897_Captivate_USB_Drivers_5_02_0_2. The computer didn't recognize the phone. If you havn't tryed these already give these a try. Well since I am new I can't post the url. Put these words together (forum.xda-developers com archive index.php t-730638)
superdog404 said:
I was having trouble using the USB drivers from Samsung the one's you were using SGH-i897_Captivate_USB_Drivers_5_02_0_2. The computer didn't recognize the phone. If you havn't tryed these already give these a try. Well since I am new I can't post the url. Put these words together (forum.xda-developers com archive index.php t-730638)
Click to expand...
Click to collapse
Not sure different USB drivers would help, but I went to the thread you show and tried to download the 32bit drivers. This is what I get:
{"error": "Invalid access attempt for this token"}
Oh well, thanks anyway.
I'm still thinking that the problem is hardware on the phone. I've tried four different cables, and three different computers. All show same problem of DEVICE NOT RECOGNIZED.
Still trying to figure out how to restore to stock without USB connection for ODIN so I can exchange for a new phone...
What are your USB settings on the device? Do you have debug mode enabled or maybe you've set the device to connect to kies right away which is producing errors on your PC. What versions of windows have you been trying to connect to? This sounds like a windows problem more than anything else.
No modifications, same error
I didn't make any modifications to my new AT&T Captivate, and I too am getting USB Device not recognized under any of the following conditions:
- drivers installed, no Kies
- drivers installed after Kies
- Kies installed after drivers
No response to any USB connection mode (Kies, mass storage, media player, PC INternet).
Only way to exchange files is to physically remove the SD card and plug it into my PC. Windows XP Professional.
By the way, which of the three drivers is the correct one: ssadadb2.inf, ssadbus.inf, or ssadmdm2.inf? Pardon my ignorance as to how this is supposed to work.
mukherji said:
I didn't make any modifications to my new AT&T Captivate, and I too am getting USB Device not recognized under any of the following conditions:
- drivers installed, no Kies
- drivers installed after Kies
- Kies installed after drivers
No response to any USB connection mode (Kies, mass storage, media player, PC INternet).
Only way to exchange files is to physically remove the SD card and plug it into my PC. Windows XP Professional.
By the way, which of the three drivers is the correct one: ssadadb2.inf, ssadbus.inf, or ssadmdm2.inf? Pardon my ignorance as to how this is supposed to work.
Click to expand...
Click to collapse
You should return your phone if it's new if you can't get your computer to recognize it when you have the correct settings and drivers.
Choose, mass storage. I use the drivers from ODIN, I also have to ones from Samsung's site but they are for Windows 7 64bit. Before you plug any Captivate into a PC for the first time you need to first change the settings to USB Mass storage or Kies will attemp to download drivers. Once you get your phone to mass storage windows should find the drivers. I am not sure, I am running Windows 7, I have an old desktop that runs XP, I could plug my phone in and check for you.
FiveBraids
Settings--developement-- check debugging mode, this will allow you to open a command shell. Using SDK and ADB commands.
Download SDK online.
http://developer.android.com/sdk/index.html
Follow the installation instructions. This will allow you to use the command ADB download to get your phone into download mode. Kies screws my drivers so I don't use it.
Rhiannon224 said:
You should return your phone if it's new if you can't get your computer to recognize it when you have the correct settings and drivers.
Choose, mass storage. I use the drivers from ODIN, I also have to ones from Samsung's site but they are for Windows 7 64bit. Before you plug any Captivate into a PC for the first time you need to first change the settings to USB Mass storage or Kies will attemp to download drivers. Once you get your phone to mass storage windows should find the drivers. I am not sure, I am running Windows 7, I have an old desktop that runs XP, I could plug my phone in and check for you.
FiveBraids
Settings--developement-- check debugging mode, this will allow you to open a command shell. Using SDK and ADB commands.
Download SDK online.
http://developer.android.com/sdk/index.html
Follow the installation instructions. This will allow you to use the command ADB download to get your phone into download mode. Kies screws my drivers so I don't use it.
Click to expand...
Click to collapse
The 2 folders I found that have the drivers are /program files/android/, .... and /program files/samsung. Delete these subfolders that have drivers in them.
Download this : http://www.megaupload.com/?d=N4GC49JL and unzip. In the folders inside (i386 and amd) there are uninstallers. Run whichever version is appropriate for you. If you have no drivers or it doesn't say to reboot, the main folder has a setup program. Run that to install the proper drivers. When you plug in to usb, it will now find these drivers.
Also, for me, ONLY the REAR usb ports work properly with this. Top, front, and ext hub ALL give issues.....
JayPhill89 said:
What are your USB settings on the device? Do you have debug mode enabled or maybe you've set the device to connect to kies right away which is producing errors on your PC. What versions of windows have you been trying to connect to? This sounds like a windows problem more than anything else.
Click to expand...
Click to collapse
USB is set to Ask on connection
Debug off or on makes no difference
All tests have been done on XP machines (3 different ones)
I'm all but positive this is hardware...
Thanks for trying to help!
Rhiannon224 said:
<snip>
FiveBraids
Settings--developement-- check debugging mode, this will allow you to open a command shell. Using SDK and ADB commands.
Download SDK online.
http://developer.android.com/sdk/index.html
Follow the installation instructions. This will allow you to use the command ADB download to get your phone into download mode. Kies screws my drivers so I don't use it.
Click to expand...
Click to collapse
I haven't tried ADB, but I'm not understanding how ADB would be able to connect when the connection to the computer is failing at the driver level. I guess I can give it a try tomorrow.
Thanks for trying to help!
What would REALLY help me is for someone to post a backup taken of a completely stock (ODIN'ed) phone using ROM manager. I'm thinking I could load that on the phone and then be able to return it for a new phone!
Any volunteers...please?
techmik67 said:
The 2 folders I found that have the drivers are /program files/android/, .... and /program files/samsung. Delete these subfolders that have drivers in them.
Download this : http://www.megaupload.com/?d=N4GC49JL and unzip. In the folders inside (i386 and amd) there are uninstallers. Run whichever version is appropriate for you. If you have no drivers or it doesn't say to reboot, the main folder has a setup program. Run that to install the proper drivers. When you plug in to usb, it will now find these drivers.
Also, for me, ONLY the REAR usb ports work properly with this. Top, front, and ext hub ALL give issues.....
Click to expand...
Click to collapse
Big thanks!
Just got my first Android device a couple hours ago (went from ATT Bold to Captivate), and could not get the phone to mount to my PC.... followed your instructions here and BAM! Perfect-o! I have now rooted....
OK, not sure where to go next... was thinking about just getting a new ROM flashed since I am totally stock at this point.... the fun begins!!!
jaxf250 said:
Big thanks!
Just got my first Android device a couple hours ago (went from ATT Bold to Captivate), and could not get the phone to mount to my PC.... followed your instructions here and BAM! Perfect-o! I have now rooted....
OK, not sure where to go next... was thinking about just getting a new ROM flashed since I am totally stock at this point.... the fun begins!!!
Click to expand...
Click to collapse
Great!! Glad it all worked for you. My next advice is, before adding anything READ A LOT!!! =) Decide what you want from the descriptions and issues you will see in the threads....
Happy modding!!
I didn't see, I just skimmed through bit did you try to put the phone in download mode and see if windows sees that (different drivers come in to play in download mode and none of the touch wiz stuff is running)? it would test the idea of a bad port.
then you can still always install linux and use adw from there, linux and macs don't need drivers. if that doesn't work, put insurance on the phone if you haven't already then drop it in the sink and get another one.
also I think although I don't know but I think adw may have something to do with it. and incorrectly uninstalling it. first put the phone in download mode then you can work from there on ways to fix that.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Ok, I've given up trying to get this to work. I'm 100% convinced this is a hardware problem with the phone!
I had another thread going, looking for a way to restore this phone (remove SRE, SU, etc.) without usb/ODIN so I could return it to AT&T. I've figured out how to restore it to stock and will be heading to AT&T in the morning.
Thanks to everyone for their patience and assistance!
Hi,
I had earlier opened a thread regarding this issue. But that was having more than one query and was misleading.
I need to install Froyo JP6 (the official one - no custom ROMs). Currently I'm having JF3.
Kies is not working for me (The MTP application in the mobile opens up, but gets restarted while getting connected to kies, so kies is not recognizing my mobile).
How shall I install JP6 without Kies?
Is it possible to install from mobile itself? (like installing apk file?)
nandihno had told me to install using odin. But i couldn't find it in dev section. Can anybody provide me the link for odin foryo JP6?
Thanks in advance!
Install latest version of Kies - 1.5.3.10093_82.
You can go in setting and Upgrage..
Once the latest version is installed, go into Program Files - Samsung
Delete USD Drivers directory here.
Now go in Program Files - Samsung - Kies - USB Driver
Install the drivers from here.
Once the installation is complete, go to settings in SGS (Galaxy) and unmount Internal SD card.
Connect SGS using USB Key and wait till system detects your SGS.
Once it is done you can use Kies to upgrade to Froyo... However as of today Froyo is not out for India... though there are work around to fool Kies and still download, though I will suggest to wait...
thanks I will try this as well. Well this also work with my issue? I tried to upgrade my firmware using kies, but it failed because of some file missing. I installed kites again, and now it detects my phone when I connect it, but it never seems to make the connection
It just says that it is trying to connect and this goes on forever.
So now I cannot repair my firmware using kies. Can this solution help with that as well?
Shurdus said:
thanks I will try this as well. Well this also work with my issue? I tried to upgrade my firmware using kies, but it failed because of some file missing. I installed kites again, and now it detects my phone when I connect it, but it never seems to make the connection
It just says that it is trying to connect and this goes on forever.
So now I cannot repair my firmware using kies. Can this solution help with that as well?
Click to expand...
Click to collapse
Same problem here. It detects my phone. But freezes in "connecting your device".
@shurdus - when this is happening (connecting ur device), did you notice your phone restarting the MTP application.
I mean, the MTP application will be displaying "installing kies" but after some time, it disappears and appears again in a fraction of a second..
I have to try the solution said by satyawali.
Another doubt - unmounting internal SD card will affect the data?
emmarbee said:
@shurdus - when this is happening (connecting ur device), did you notice your phone restarting the MTP application.
I mean, the MTP application will be displaying "installing kies" but after some time, it disappears and appears again in a fraction of a second..
Click to expand...
Click to collapse
I have a similar problem. I just downloaded the newest version of Kies, but can't get Windows/Kies to recognize my phone. I unchecked "Automatically start monitoring for device..." and "Start Kies automatically..." in the Settings box, and I did the Driver Recovery and rebooted, all recommended in another thread. Still nothing. All I get is some very quick flashing of MTP Application and my home screen opening and closing. Then Windows (Win 7, 32 bit) tells me it couldn't do something and to contact the device manufacturer.
Have you found a solution?
Sent from my GT-I9000 using XDA App
SlowRain said:
I have a similar problem. I just downloaded the newest version of Kies, but can't get Windows/Kies to recognize my phone. I unchecked "Automatically start monitoring for device..." and "Start Kies automatically..." in the Settings box, and I did the Driver Recovery and rebooted, all recommended in another thread. Still nothing. All I get is some very quick flashing of MTP Application and my home screen opening and closing. Then Windows (Win 7, 32 bit) tells me it couldn't do something and to contact the device manufacturer.
Have you found a solution?
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I haven't found the solution yet.
I guess the only solution is to format the SD card and then try. But I'm not willing to do that So no froyo for me... If only there was an OTA or froyo installer it'd be great
1. Uninstall KIES
2. Uninstall "SAMSUNG USB Driver For Mobile Phones".
3. Reboot your PC
4. Brows to "Program Files" (windows 32bit) or "Program Files (x86)"(windows 64bit) and remove the folder "Samsung".
5. Run "regedit" from Command Prompt and look in HKEY_CURRENT_USER\Software and delete the "Samsung" folder.
6. Right click your C-drive and choose "Properties", click "Disk Cleanup" and check "Temporary Files" and hit "OK".
7. Install KIES and reboot your PC.
8. When booted, don't start KIES yet, just connect the phone and let windows install the drivers for it, unplug the device when done, start KIES and connect the phone.
That should work out for you..
^ thanks. gonna try it now. Will let u know
@[Ramad] - even this didn't work.
The problem is in the phone - i can clearly see it. I guess, a factory reset will do it. Is there any backup software that can backup including the application data/caches ?
isn't there a download link for the new and original Froyo? there are too many pages and it's quite hard to find what you want (I've found Froyo but not the original one, I think, and I've found plenty of advices for kies but I don't want to do all that unistall-delete traces-install again, when there's a simpler way with odin)
Kies problem is related to the ammound of MP3's on your SGS!
Because MTP is a MP3 player connection protocol it's using some MTP Windows media player driver to connect. If you have all MP3 on an external SD card, just remove it and Kies will work fine. Otherwise remove or rename your MP3s to make it work.
Seriously this worked for me, credits to a user of some forum (can't find the post).
Force close all d launchers before connecting d phone to kies its very necessary step hope it will work
It's unbelievable... the best Android phone has the crappiest PC companion. Seems everyone has exactly the same problem with kies.
As far as I've read it's related to files with longer names stored inside the internal memory. Come on! The old Palm Hotsync didn't suffer from such stupid things!
I think we should start a global petition for Samsung to fix that. My wife has a 10 bucks nokia that has a far leaner/better/functional PC companion.
@nagash1979 - by saying remove it - u mean "all mp3/flac and media" in the external card?
@ srajoria - did that. In fact. uninstalled laucnher pro and then tried. no use.
@c3p9 - i don't think its a deal breaker for this phone. As there are alternatives for kies (like es file explorer for wireless transmission of files). But if only there was an OTA update, then no need of kies at all
@nagash1979 - i couldn't find any windows media player application running in the background. thanks anyway....
Finally I got the solution for the KIES problem.
I had recently downloaded winamp beta from android market. And when connected the phone in usb storage mode when winamp was open in PC and phone, my phone was detected as mass storage. And when I opened Kies, it also detected my phone (finally!), but asked me to connect to kies mode. I removed the cable and connected again in kies mode. And it worked like a charm! WOW!
But it's not working everytime!
Edit: The Mass Storage worked 4/10 times. Kies worked only once out of 10 tries. Everytime a alert message to turn off the SD card is popping up which is very irritating. Dunno how to fix that....
Atleast I was able to connect my phone with the PC using USB Mass Storage mode after a very long time - took the backup of all camera files
If you have latest version of Kies installed and drivers working and experiancing MTP crashing issue on phone then it is long file name issue.
To solve this, connect your phone in media mode and mount the card on system. Use attached utility and search long file names on phone and delete them.
Now connect Kies you should not get MTP issues.....
However this does mean this crappy software (Kies) will still detect your phone...
Try to use Antroid Manager will be satiafied. I have uaed it works fine over Wifi.
Sent from my GT-I9000 using XDA App
Ok, been trying this now for 2 hours and getting ready to throw my nook though the monitor.
I've followed the instructions for setting up ADB to work with the NC on nookDevs and it's still not working.
Ok, I'm running windows XP x64 edition. Was a pain just getting ADB installed, but I digress. When I plug in the NC, I don't see it listed under "Other Devices" in the device manager, but rather as 2 disk drives (Barnes & Noble Ereader) and a USB MAss storage device. I update the driver for the Mass Storage device and then it shows up as an Android Phone, but ADB doesn't recognise it.
Help please, I only bought this thing to turn into a tablet, and I'm quickly failing at that.
I couldn't get my windows to recognize the device either so i just use adbwireless.
The easiest way to root your nook is get the monster pack with cwr, its a bootable image that you will need to burn onto your sdcard. And if your nc is already 1.1 then grab a 1.0.1 zip to flash within cwr before rooting it.
sent from my nookcolor
Which version are u using? There is a thread for ADB driver:
http://forum.xda-developers.com/showthread.php?t=882751
This should work on 1.0.1, however, I also have problem with prerooted 1.1 as usb debugging keeps turning itself off when connected to PC and I now use ADB over wifi instead.
arda99 said:
Which version are u using? There is a thread for ADB driver:
http://forum.xda-developers.com/showthread.php?t=882751
This should work on 1.0.1, however, I also have problem with prerooted 1.1 as usb debugging keeps turning itself off when connected to PC and I now use ADB over wifi instead.
Click to expand...
Click to collapse
did that, no dice.
I have 1.0.1. Anyhoo, thank god for bootable images, otherwise it looks like I'd be stuck stock
Used the Monster Root to root, install CWM, etc. so at least that part's done. Still no ADB love.
Hi everyone,
I have an AT&T Captivate SGH-i897 (2nd hand) and i can't mount the phone to my laptop (winXP 32bit). When i plug in the cable to the phone and then the PC i get the "device not recognized".I've donwloaded the Samsung drivers from the xda wiki page and extracted them and tried to update the driveres via Device Mng ,but didn't work.Also dl'ed the Samsung drivers 5.0.x instaled ,and still nothing.USB Debugging is on...
So to recap,my top can't recognize the phone('s internal sd card) so plz help ???????
Try this, go into usb settings and choose "mass storage"
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
install kies
I would also recommend trying to fully uninstall all the drivers that associated on your pc with your phone (samsung or otherwise), and then reinstall the drivers before you plug in your phone. Then try to reconnect.
Just covering the basics. Assuming your phone is working correctly.
You have tried multiple USB ports on your computer, particularly those on the back if it's a desktop.
You have installed correct drivers (x86 or x64)
" for the correct operating system.
You have uninstalled the drivers before trying to reinstall.
You've tried to get Windows/ Mac to find them online (assuming you're using versions of OS that support doing that)
You've first tried Kies mini before full version, uninstalling in between. (Kies full version isn't supported for US, there are workarounds, but that's a different discussion)
On the phone you tell the phone to connect 'USB storage' (from the pull down menu after connected or in the settings)
I too am having problems with USB connectivity on a notebook with Win7/64. The usual failure mode is Windows not recognizing the USB device. I have followed ZBigT's basics, step by step and still cannot connect.
FWIW, my registry is awash with Samsung entries, some of which cannot be deleted.
I've even tried the AIO Toolbox application (to install the 64 bit drivers) to no avail.
Any other tips?
Is usb debugging turned off?
o hey guys sry for keeping u waiting,
i menaged to install ginger ,
the problem was my lap....rusty old bucket!!!!
had my friend come over with his lap and it worked like a charm ,
the problem is now i need a new one ;(,
damn
mrhaley30705 said:
Is usb debugging turned off?
Click to expand...
Click to collapse
Yes. Still no love. Have tried:
usb_drivers_GalaxyS_x64
SGH-i897_Captivate_USB_Drivers_5_02_0_2
mini-KIES
Kies
AIO
uninstalling reinstalling each time
When I plug in the Captivate, any of 3 USB ports on the laptop, Windows gives the "Unrecognized Device..." message.
Go to settings/about phone. Look at the very bottom to see what rom you are running.
mrhaley30705 said:
Go to settings/about phone. Look at the very bottom to see what rom you are running.
Click to expand...
Click to collapse
Paragon RC6.0
FWIW, I also have a Win7/64 desktop with the usb_drivers_GalaxyS_x64 installed and that works fine; can connect see "drives", use ODIN, adb commands etc.
It just the notebook, which I would like to be able to use to connect, especially when I travel, which has issues.
mabovalu said:
Paragon RC6.0
FWIW, I also have a Win7/64 desktop with the usb_drivers_GalaxyS_x64 installed and that works fine; can connect see "drives", use ODIN, adb commands etc.
It just the notebook, which I would like to be able to use to connect, especially when I travel, which has issues.
Click to expand...
Click to collapse
Check in program files for a Samsung folder. There may be remnants from old drivers that need to be manually deleted.
mrhaley30705 said:
Check in program files for a Samsung folder. There may be remnants from old drivers that need to be manually deleted.
Click to expand...
Click to collapse
Thanks for sticking with this. I was able to connect. I as focused on the Registry remnants, but your advice to clear out the Samsung folder in Programs worked. Thank you.
Additional comments: I am now running the Dlev ROM, it's OK, but when I plugged in the USB cable, just to the phone, it launched the Alarm Clock app! So I deleted that.
Then on the first of my four USB ports I got a USB driver failure to install, then the Windows Unrecognized USB device on ports 2 & 3. On port 4 it worked. (This is a Lennovo/Thinkpad notebook.)
I used the usb_drivers_GalaxyS_x64 package as that also worked on my desktop.
Thank you very much.
Hi everybody,
I have a 64-bit PC with Windows 7 Ultimate Service Pack 1 and a Samsung Galaxy S Advance GT-I9070 with Android 4.1.2.
I can't install a driver in order to make Windows recognize correctly the phone when I connect it via USB cable.
I've installed and uninstalled Samsung Kies many times with no results. I've also tried some Samsung driver from Windows Update with no success...
When I connect the phone, it is recognized as a MTP Device and the driver installation starts, but always ends with an error, as shown in the attached screen-shot image.
What can I do?
Thank you very very much.
Note: in another PC with WinXP I have no problems.
Firstly make sure phone can run MTP (make sure if you delete MTP releated stuff in system you won't able connect it. Re-flash with Odin) Now if you don't have problem with phone then uninstall drivers & KIES from Windows. Don't just do a uninstall clear temp files, dll files, registry entries (you can use CCleaner) then install THIS DRIVERS.
explanation
King ov Hell said:
Firstly make sure phone can run MTP (make sure if you delete MTP releated stuff in system you won't able connect it. Re-flash with Odin) Now if you don't have problem with phone then uninstall drivers & KIES from Windows. Don't just do a uninstall clear temp files, dll files, registry entries (you can use CCleaner) then install THIS DRIVERS.
Click to expand...
Click to collapse
Hello, thank you for your answer.
How can I make sure my phone can run MTP?
For the complete uninstall, is it enough to run CCleaner, uninstall Kies and then perform the Registry Cleaner in CCleaner?
Thank you
ZioAlfredo said:
Hello, thank you for your answer.
How can I make sure my phone can run MTP?
For the complete uninstall, is it enough to run CCleaner, uninstall Kies and then perform the Registry Cleaner in CCleaner?
Thank you
Click to expand...
Click to collapse
Did you root phone ? or installed a ROM or you just using it stock ?
I noticed something too; if you any have PIN or Password you have to unlock phone otherwise MTP not works. Unlock it and try too.
CCleaner will *probably* be enough but if you want to make sure go to regedit.exe and go to;
Code:
HKEY_CURRENT_USER/Software/
Then delete KIES & USB Driver stuff (don't delete system USB configs & drivers just Samsung's softwares )
EDIT: In start menu click to RUN (or whatever I don't now it's name in English, you're entering a text) Then write
Code:
%AppData%
Then delete KIES & Samsung folders and files.
I've just Updated the phone firmware from Android 2.3.6 to 4.1.2 with Samsung Kies on my WinXP PC.
I've deleted all Samsung Kies registry entries.
Now I'm going to install the driver you suggested...
Let me see results...
King ov Hell said:
Let me see results...
Click to expand...
Click to collapse
Failure... The same as always
ZioAlfredo said:
Failure... The same as always
Click to expand...
Click to collapse
...
I've also installed Windows MTP Porting Kit, but it still fails...
Any idea?..
I think it is the configuration of this PC, because in another brand new PC with Windows 7 I've installed Kies and it all went right.
ZioAlfredo said:
I've also installed Windows MTP Porting Kit, but it still fails...
Any idea?..
I think it is the configuration of this PC, because in another brand new PC with Windows 7 I've installed Kies and it all went right.
Click to expand...
Click to collapse
Have you tried to reboot phone? I lost mtp after charging phone over wall charger. Everytime I need to reboot after charging to get it connected to pc.
Sent from my GT-I9070 using Tapatalk
This may be a bit silly but is important to ask.
Was your PC connected connected to the internet while installing the drivers??
Did you unplug your phone while the drivers were being installed??
anantttt said:
This may be a bit silly but is important to ask.
Was your PC connected connected to the internet while installing the drivers??
Did you unplug your phone while the drivers were being installed??
Click to expand...
Click to collapse
Yes to all.
shut_down said:
Have you tried to reboot phone? I lost mtp after charging phone over wall charger. Everytime I need to reboot after charging to get it connected to pc.
Sent from my GT-I9070 using Tapatalk
Click to expand...
Click to collapse
I've just tried to reboot the phone before connecting it to the PC, but I get the same error (see attachments).
Last year I managed to connect the phone to this PC, but, in any case the connection got interrupted after a while (see this thread).
I don't know what to do...
I had the same problem when i formatted my PC 2 days ago. I did some trial and error and it worked.
1. Dont use any USB Hub if you are using.
2. Remove the Pattern lock or any password security etc. Go to lock screen and select 'None'. (I dont know why but windows doesn't recognise if the device is locked)
3. Have Kies installed. Even new version worked for me. I used 2.5.13043_14
4.Connect your device with the USB cable (Should have MTP option selected which is by default)
5. Windows automatically recognises now and installs the necessary files.
P.S:- Remove the security pattern, etc. It really works.
If worked then pls reply.
Hello,
I've disable any screen lock on my phone and I've connected the USB cable to another USB port (a 3.0 USB port) and Windows magically recognized correctly the device! (no Kies installed, only drivers)
Anyway, after some minutes of usage (cut-paste of files). Windows stopped recognizing the device...
If I disconnect the phone and then connect it back, Windows still recognizes it, but I have few minutes until the device stops being recognized and no file on it can be read...
See attached pictures
ZioAlfredo said:
Hello,
I've disable any screen lock on my phone and I've connected the USB cable to another USB port (a 3.0 USB port) and Windows magically recognized correctly the device! (no Kies installed, only drivers)
Anyway, after some minutes of usage (cut-paste of files). Windows stopped recognizing the device...
If I disconnect the phone and then connect it back, Windows still recognizes it, but I have few minutes until the device stops being recognized and no file on it can be read...
See attached pictures
Click to expand...
Click to collapse
Did you download newest version of drivers? I see in your screenshot it says 2012, on mine it is 2014.
Did you set Windows to gather drivers automaticaly from the internet?
shut_down said:
Did you download newest version of drivers? I see in your screenshot it says 2012, on mine it is 2014.
Did you set Windows to gather drivers automaticaly from the internet?
Click to expand...
Click to collapse
This is how my PC recognizes my phone. The driver seems to be old, but I've configured Windows for downloading drivers automatically and that is all it can do.
Today, th PC did not recognized the phone at once. Then I unmounted and mounted back the MicroSD card and the PC recognized it.
But, after few seconds of folder browsing, the PC lost the connection. I'm thinking that the problem is the SD card.
Solved!
Solved!
It was the USB cable.
I replaced it with an original one and now it works.
Thank you everybody for your effort!