there is a strange issue my laptop not recognizing my captivate in download mode. this is not os specific as since this issue began, ive installed 3 dists' of ubuntu, windows, and currently deb wheezy, with same results. lsusb shows no device during dl mode. recently, another issue occured while installing the sdk also. the adb server will not start, with a "failed to ACK" response. this was never an issue before with the sdk. anyhow, installing adb-tools via repository, i am able to access the device without issue.
on my desktop, my captivate is found during dl mode also heimdall w/o issue. my nexus however, is found by heimdall on my laptop and in dl mode/lsusb. i have installed multiple versions of heimdall/frontend and attempted running the one clicks'. i have one usb port on my dell c610 latitude and multiple usb/data cords. any suggestions?
brandonabandon said:
there is a strange issue my laptop not recognizing my captivate in download mode. this is not os specific as since this issue began, ive installed 3 dists' of ubuntu, windows, and currently deb wheezy, with same results. lsusb shows no device during dl mode. recently, another issue occured while installing the sdk also. the adb server will not start, with a "failed to ACK" response. this was never an issue before with the sdk. anyhow, installing adb-tools via repository, i am able to access the device without issue.
on my desktop, my captivate is found during dl mode also heimdall w/o issue. my nexus however, is found by heimdall on my laptop and in dl mode/lsusb. i have installed multiple versions of heimdall/frontend and attempted running the one clicks'. i have one usb port on my dell c610 latitude and multiple usb/data cords. any suggestions?
Click to expand...
Click to collapse
The only thing I can think of is drivers issue. Is it connecting fine outta dl mode?
I wouldn't have thought it would be a driver issue with the Ubuntu releases. The android devices are built into the kernel. I haven't used any 'buntu releases to connect to my Captivate, but I have been connecting to it with Linux Mint since I bought the Captivate. I tend to use the LTS releases based on Ubuntu's LTS releases. I have used the versions corresponding to Ubuntu 10.04, 12.04, and 14.04 without ever installing a driver. The same holds true to when I was using LMDE based on Debian Squeeze while it was still the testing release. It seems to be true for you that it is not a driver issue since you connected with adb-tools (was that while on Linux?).
I was going to ask if you had the Captivate set to either Mass Storage or Media Device (MTP), depending on your ROM version. But, thinking about it this should not apply to your question, since you are talking about download mode. I have further suggestions if you were talking about transferring files over a USB cable while the phone is booted for use; having mtp-tools (older Ubuntu versions) or libmtp packages (came as part of base install on latest LTS for me).
Even regarding download mode, I doubt it is a driver issue while you are using Linux. The reason I believe so is that I have read of connecting Android phones to laptops while running both Ubuntu and LinuxMint as a LiveUSB installs. In such a situation you don't install anything that is not part of the basic .iso file.
This brings you back to a connection issue that happens with the one laptop but not with the desktop. It happens from Linux OSes and Windows. If it were only Windows I would think a driver issue. You have ruled out your USB cable because you have tried several. I'm not sure if calling this an intermittent problem is the correct description. I guess there is still a possibilty it could be a hardware issue with either the one USB port on your laptop or the microUSB port on your phone.
By any chance were you running Linux as a virtual machine under Windows? Maybe that would bring it back to a drivers issue, a Windows driver issue. That would be a better problem to be working on than a faulty port.
i edited the heimdall permissions, android-adb permissions, added new permissions. nada. if i flash stock, and still no detection, yet detection on my pc, i can then verify my laptop as the culprit, which ive had problems with since i bought it. i actually took it apart and to placehold my usb port, jammed a penny in it. which has worked fine for years. the entire unit is sketchy. random reboots, broken back, trackball poultergeist. mostly i just want a backup hdd in the event this handmedown pc fails. so its a latitude c610 running 32 bit debian wheezy 3.2 pae kernel. once i researched/learned i could develop on 32 bit machines, i decided to dust it off. if i can get to the bottom of this issue, i would then buy some parts to make it decent. no heimdall/no way. im full throttle for my cappy atm.
im running natty on my pc because i was having dependancy issues compiling with precise. but heimdall was never an issue. i have a feeling the sdk issue and the heimdall issue are related. i started a thread http://ubuntuforums.org/showthread.php?t=2268539 regarding the sdk issue, but i marked it as solved as the reason was simply installing adb.
dawgdoc said:
. It seems to be true for you that it is not a driver issue since you connected with adb-tools (was that while on Linux?).
By any chance were you running Linux as a virtual machine under Windows? Maybe that would bring it back to a drivers issue, a Windows driver issue. That would be a better problem to be working on than a faulty port.
Click to expand...
Click to collapse
yes and no. i think its either dl mode being finnicky or a little elf living in my laptop keeps unplugging the usb when i heimdall.
edit. interesting how i tested stock dl mode on my laptop, which failed. however, i connected to dl mode via my laptop (device not detected)(lsusb + heimdall)) i then checked for connectivity on my pc which failed also. i rebooted dl mode from my pc and then my pc connected fine. this method unfortunatly is not backwards compatible.
UNSOLVED
since, ive tried dl mode with xp and 7. im filing it to the "aint tryin' to happen" category. i need to buy a new laptop anyhow. thanks
Related
Hello all.
First of all, before people shooting at me and saying "please search", I come from many Google and xda search with "MacOs, download mode, failure vm, virtual machine, odin , kies" in every combination you can imagine and no result.
So, the problem is the following one:
I remarked, with some friends from a french forum that we all succeed to use KIES in a virtual machine and connect the phone:
Click for full size - Uploaded with Skitch
That work like a charm.
Then w wanted to flash, then reboot the phone in Download mode ( yellow android at work ) and then there is a big crash telling us that the device is not recognized:
"unable to connect USB device to virtual machine"
Click for full size - Uploaded with Skitch
I would really be pleased to have more info on this issue and if we are only a little group to have this issue.
For info, I am using MacOS Snow Leopard and the trial of parallels desktops 6.
It doesn't work with VMware Fusion either. Must be something to do with the USB interface on Samsung.. I've heard some people have it going on Virtualbox running on Linux - but not Mac.
Works fine on VirtualBox on Ubuntu.
Why don't you give Heimdall a go? Haven't tried it personally, but OS X is in the list of supported OSes
Maybe I found the explanation , thanks to ed link:
Although Heimdall runs on OS X all Galaxy S phones tested thus far contain a bug in the secondary boot loader that prevents the phone registering itself with OS X. This may change if Samsung release an updated secondary boot loader.
Click to expand...
Click to collapse
Maybe there is the same problem.
Does the secondary boot loader has a link with download mode? If yes, that might be the problem!
profete162 said:
Maybe I found the explanation , thanks to ed link:
Maybe there is the same problem.
Does the secondary boot loader has a link with download mode? If yes, that might be the problem!
Click to expand...
Click to collapse
Saw that today too.. .pretty sure its the issue since it affects all parallels, fusion and virtualbox on Mac OSX.
profete162 said:
Maybe I found the explanation , thanks to ed link:
Maybe there is the same problem.
Does the secondary boot loader has a link with download mode? If yes, that might be the problem!
Click to expand...
Click to collapse
Yes, download mode functionality is provided by the secondary boot loader. If you really desperately want to get it working with OS X then you would need to download the source for, modify and install a custom IOUSBFamily.kext that contains a work-around specifically for the Galaxy S.
The only options for we Mac users right now are to find a Windows machine, install boot camp on your Mac (then point your vmware machine to it to save duplicate Windows wasted space), or possibly find a way to boot from an external drive with Windows (like a thumbdrive or livecd if possible).
distortedloop said:
The only options for we Mac users right now are to find a Windows machine, install boot camp on your Mac (then point your vmware machine to it to save duplicate Windows wasted space)
Click to expand...
Click to collapse
Exactly what i have done. And I HATE it :|
I had this same problem, and I just saw this thread after spending hours last night trying to figure out why XP in Parallels stopped recognizing the phone as soon as it went into download mode. So irritating!
it works for me on VMware 7 + WinXP SP3
because my Win7 64bit PC is crazy it won't recognize the phone randomly, twice it bricked my phone doing the Flash on the Host PC
so after setting up my ROM FLASH VMware machine, now i no longer have problem
stupid windows, no time to mess with the system registry to figure out what is the madness with the USB detection
i'm pretty sure you should have no problem as well if you use VMware 6.5
I posted this in the Heimdall thread but thought I should let followers of this thread know also.
I sent Samsung the OS X USB failure log and since then Samsung have informed me that the Froyo update (specifically the Nordic version released October 15) includes a fixed bootloader which should allow the phone to be recognised in OS X. I'm yet to verify this but hopefully this is the case!
I rooted and installed Cognition 2.1.6 on my phone a few weeks ago and want to change to Cognition 3.04. When attempting to flash back to stock via Odin, my computer will not recognize the phone in download mode. (I'm using AIO Toolbox and running the debug check.) The PC fully recognizes the phone until I'm in download mode. I get an error "The device has malfunctioned" and the device manager shows an unknown device. I uninstalled and reinstalled the 32-bit drivers and the same issue occurred. I've tried both Odin 1 click and Odin 3 click and neither recognizes my phone, although I doubt it matters which version of Odin I'm trying. I've searched all over the forums and the closest thing I've found is pointing the device manager to the driver, but the Samsung USB driver directory has numerous .inf files and I have no idea which one to choose. Any help?
Other relevant info: Win XP SP3 32-bit, Captivate Build 1012...
havent heard good things about xp and aio toolbox... dev doesnt own xp, but does have vista and win7,
when pointing to a driver select the whole samsung folder and check the box that says "also search sub-folders" .... or wait not sure if xp has that option, its been 6 years... hope it does.
but if your drivers installed by the program, you shouldnt need to manual install.
try different usb cable (you didnt do that fast charge tinfoil thing did you?)
try different usb port,
try different operating system (torrent win7)
Trusselo said:
havent heard good things about xp and aio toolbox... dev doesnt own xp, but does have vista and win7,
when pointing to a driver select the whole samsung folder and check the box that says "also search sub-folders" .... or wait not sure if xp has that option, its been 6 years... hope it does.
but if your drivers installed by the program, you shouldnt need to manual install.
try different usb cable (you didnt do that fast charge tinfoil thing did you?)
try different usb port,
try different operating system (torrent win7)
Click to expand...
Click to collapse
Hmm... The only issues with XP seemed to come with flashing a custom ROM step not the drivers. It seems like there is an issue with the drivers and/or usb ports. Have you tried connecting it to the USB ports near the back of the computer?
bay_wolf said:
Hmm... The only issues with XP seemed to come with flashing a custom ROM step not the drivers. It seems like there is an issue with the drivers and/or usb ports. Have you tried connecting it to the USB ports near the back of the computer?
Click to expand...
Click to collapse
right, thats what i remembered.. are the drivers for all versions of windows? many users had drivers installed before the toolbox.
bay_wolf said:
Hmm... The only issues with XP seemed to come with flashing a custom ROM step not the drivers. It seems like there is an issue with the drivers and/or usb ports. Have you tried connecting it to the USB ports near the back of the computer?
Click to expand...
Click to collapse
I had this problem when I tried last weekend without using AOI, so I doubt it's an issue with Toolbox. (I just pointed out that I used Toolbox to note that I definitely had debugging on. I tried to include as much relevant info as possible in the OP to avoid a lot of "have you tried this [basic function]" replies.) I tried multiple ports, too. I'll give it a go in the morning and see if Trusselo's "search folder" suggestion is a possibility...
I had this same problem and i searched for a fix for the three button method
hi ive searched for a few hours and tried so many different sequences her eon the forums and for some reason i cant get odin3 1.78 to recognize my captivate... otherwise i would have an awesome Cyanogenmod 7 on it.
i rooted it and installed clockwork from the thread "how to install roms" under the dev threads (the big sticky) then attempted to install a custom rom through clockwork and it failed. now my original rom is messed up. i can load into it but android.phone continuously closes...i cant get odin to see my phone thus i cant reflash the original firmware....
yes i have drivers installed.
yes i have the AIO toolbox.
now for some reason i cannot get Odin to recognize my phone AT ALL (download/recovery/loaded). ive literally tried everything i can think of and to be honest i hope someone here can make me look stupid and help me fix it . ive flashed roms before back in the day with my tilt and cliq. but ive been out of the game for a very long time and lemme tell you im completely lost feeling.
im on windows 7 ultimate x86 fully updated.
ill be glad to donate a little bit for some success on just getting odin to recognize because i have everything. its just that stopping me..
in the meantime my phone is just useless
It might be problems with usb port. Try different ports and/or a totally different computer. Make sure you have drivers according to your computer (32-bit /64). I don't really know why it isn't working.
im sure if he got cwm copied to the phone the USB works...
i have never heard of odin3 1.78
only 1.0 1.3 1.5 1.7 1.81 and 1.82
and some odins only work with some phones..
did this odin ever work for you? or never?
try this one...
no i used my laptop MicroSD then transfered into my root folder of my phone.
ive tried it on 4 computers in my house so far all windows 7 32 bit.
installed the drivers from the AIO and even KIE after seeing no results. ive tried different ports as well and thats the exact odin im using ;(
i also attempted XP compatability mode seeing on another thread windows XP worked for another user in a somewhat situation so im debating whether or not to dual boot XP just to fix my phone lol
so your computer doesnt even see it when you mount usb to copy files? not just odin? did it ever work?
i run windows 7 64 bit no probs.
EDIT... i just re-read your first post....
ODIN ONLY sees the phone in download mode. ONLY
no it doesnt see it at all i think im goin to uninstall drivers and reboot.
now it makes the sound that windows found it but i cant access it or visually see it as a mass storage device even when i specify the settings (disabling debug/enabling mass storage) and under download mode it just doesnt see it at all.
i think im going to get organized and correclty reinstall anything i might think may be an issue
also installing xp on a virtual box on my linux machine to my right
virtual machines and odin dont mix well
with linux use heimdall instead of odin. but the machine still needs to see the device.
and try the drivers from samsung.
USE THE ORIGINAL SAMSUNG CABLE!!!!!!!
some cheap cables, like the one for my bluetooth headset are power only usb cables. the other 2 data pins dont connect end to end!!!!!!!!
ahh maybe thats the problem, i happened to pick up my captivate from someone on criraglist just yesterday and it was just phone and charger. how can i tell if i have an original or not? and yea i tried the drivers from samsung for the galaxy S as well. i was so irritated earlier lol i took a break and came back to it
if windows doesnt beep when pluggin in, then the cable is probably no good...
or try the cable with another phone/ usb hard drive / some data device that takes that input....? or go to radio hack and pick up a new cable. if that doesnt work return it to the hack for your$$ back.. if it does work its worth the 15-20$...
or maybe the phone has a dead usb port... that has happened to some people
okay i found a cord that gives me "usb device not recognized" when im loaded into my phone fully and select mass storage. this is after i installed the samsung driver exe 32 bit for my 32 bit windows 7.
looks like windows 7 attempts to install drivers for "mass storage device" and it fails.
my windows will fail on phone boot a few times because the phone cycles thru different modes.. adb and download mode work on different drivers...
remember to mount to see sd card on pc...
but at least you are getting something now... maybe now is the time to try other pcs..
just throwing out some ideas its getting late.... lol
lol yea thanks man ill reinstall android sdk and java se and see if i can get the adb to be seen and try different drivers for now. thanks for helping me ill donate to you in the end even if we cant get it but man my phone is wacked, all the services are force cosing on it. its so useless right now
ConnectionStatus: FailedEnumeration
Current Config Value: 0x00 -> Device Bus Speed: Low
Device Address: 0x00
Open Pipes: 0
*!*ERROR: No open pipes!
===>Device Descriptor<===
*!*ERROR: bLength of 0 incorrect, should be 18
bLength: 0x00
bDescriptorType: 0x00
bcdUSB: 0x0000
bDeviceClass: 0x00
*!*ERROR: Device enumeration failure
thats what im getting in every port on my laptop.
okay man i got it.. i rebooted my pc after uninstalling EVERYTHING (java sdk,eclipse, android sdk, AIO Captivate toolbox, all drivers known to man that dealt with the phone) then logged back in, i downloaded and loaded up UVCView.x86 and tried my phone on every single usb port on my laptop while disconnecting ANY other device thats including my mouse and for some reason my captivate only worked on 1 usb port that was on the side of my laptop (left side) and would only make a (ding dong) sound if my external was detached from my laptop (weird) but wouldnt install drivers still. reinstalled the set of drivers needed and installed AIO captivate toolbox, nothing happened. so i put my phone in download mode and i went into the Compatibility options for the AIO toolbox and set to run as windows xp SP3 + checkboxed run in 256 color, Disable visual themes, Disable desktop composition, Disable scaling on high DPI settings and run as Administrator Then doubled clicked/loaded it up. sure looked like utter crap but my phone was seen by windows and sure enough it had 2 drivers it installed. i went into flash to stock and COM 3 came right up i cried with happiness and i flashed faster than my eyes blink while on a cup of sugar. then i went ahead and tested the com 3 detectability under Odin (i set odin with the EXACT same compatibility mode settings as the AIO - i used odin by itself just for testing) and COM 3 was instantly seen. after flashing to stock and making sure eveyrthing was okay, i went ahead and installed the speedmod kernel and yet again windows 7 x86 recgonized the device and it installed about 7 different drivers! i should be okay from here im not totally noobed feeling now.
Thanks for stickin by my side for the information and support TRusselo ill donate to you for that.
PS : i think im going to research for a week or two on getting what i ned for my linux box in the near future lol
congrats!!!!
yep yep, got cyanogenmod 7 running great, sure is a battery killer though, seriously im afraid of leaving the house with this lmao. my next paycheck be sure to see a donate from dahrat
I used to be able to put my Captivate in USB debugging mode and enable usb storage and move files perfectly. Now that I think about it the last time I did this was before I upgraded the Captivate to Android 2.2. So, I think something happened after upgrading now when I plug my Captivate I get a driver error and it says Code 43. I tried uninstalling and reinstalling drivers, but don't think it helped I even tried installing from Kies Mini. I am not really sure what to do here. Any help would be greatly appreciated because I really need to transfer some files from Captivate to PC and vice versa asap.
Thanks,
Mo
You should be able to transfer files without drivers installed.
Sent from my GT-I9000 using XDA Premium App
When I plug it in it says Driver Device Software was not successfully installed. and Windows has stopped this device because it has reported problems. (Code 43)
then USB Device not recognized pops up.
When I go to my computer there is nothing showing my device so how would I begin to transfer files via USB??
Sorry but am still somewhat new to driver issues and android
Not sure, sounds like your computer. Updating the rom won't cause usb errors.
Do you have wireless connection? If so, download FileZilla or some other ftp client to your computer. Then go to the market and download OnAir or some file server. Then you can use the wireless to ftp files back and forth.
That is until you figure out you computer usb troubles.
Yea I'm in the processs of transferring the files via bluetooth, but any advice or at least a place to start for fixing the usb problems. I honestly have had no problems since updating to 2.2 and cannot think of any changes I have made to the computer either
bump can anyone help?
I wish someone would step in here as I am having the exact problem - Win 7 - 64 Pro. All of a sudden the desktop PC has stopped recognizing the Samsung Captivate. It wasn't always this way and I cannot figure what may have changed on the desktop to cause this (except for MSFT updates of course).
win7
BUMP. I just used my home computer (windows xp) and reset my captivate, then rooted and flashed Andromeda. this is the first time i flashed a rom and everything, but everything went smoothly and I would like to try out other roms, but I am only home for 4 months out of the year
I USUALLY have my 64 bit Win 7 laptop, but it is still not recognizing my Captivate. I still cannot even mount it. If anyone can help it'd be greatly appreciated. I tried reinstalling captivate x64 drivers and tried samsung kies mini but no luck. can someone troubleshoot me or send me a step by step walkthrough. I am getting the same errors I have had earlier and like BillMc it wasn't always this way.
BUMP. I got the same issue and it is driving me nuts. Any help will be greatly appreciated.
Open Device Manager, plug in your phone, and see what new devices pop up when you plug it in. Then uninstall all "devices" related to the Captivate.
Then unplug your phone and reinstall the captivate drivers pack. Then plug your phone back in and see if your computer sorts out the drivers correctly.
This fixed my issues. Try it.
Sent from my SAMSUNG-SGH-I897 using XDA App
Hello everybody, I have a problem with my i9000 and my laptop, I today i dicided to format my laptop and install win 7, it's not the first time I've done it, but this time I haven't been able to successfully install the drivers to connect the laptop and the phone.
I believe that I try it all, download keys, download samsung driver for mobile phones x86, x64, windows update, tried to find the driver using the system32 folder from another pc where the i9000 is properly detected, and noting seems to work.
The only thing i haven't tried is to change the rom, but if the phone was correctly recognised by the laptop yesterday, this shouldn't be the problem, but currently i'm using SuperNexus 2.0 rom.
If any one have any ideia of what to do next i'm willing to try it out.
Best regards to everyone
Solved, i don't know why, but when i enable the usb tethering, it instaled all the drivers correctly.