I had the same problem in 64 bit windows. I had to do my update on an xp machine.. Long story short. All the Kyocera modem drivers worked before under 1.6 but fail now under 2.2. Even when I try to use the old drivers they still fail.
When I was running 1.6 my Kyocera Android Modem worked fine. Same with Kyocera HSUSB Device 2 each. My ADB Interface loaded OK though.
Anyone else having this issue?
Thanks,
MM
Easy Tether
I was using PDAnet on my other phones. After I got the Zio I couldn't use pdanet until I download and installed easy tether on my phone and computer. Apparently the drivers in Easy Tether installed on the computer fix the problems.
Related
Ok Ok....So for all of those people that are getting the error message or "Yellow Exclamations" in device manager. Here is a link to the drivers that you will need to use for your OS.
http://www.mediafire.com/?rwjyl0d2s2o2dr9
I "JUST" found the link from reading the Zclusive Facebook page, Thanks go to Megan for uploading the drivers, for those of us who do not have the Original Driver CD.
I would like to note, that THESE Drivers are only for those of you who have trouble getting the Drivers from the Kyocera Website, or any other post in this thread.
Worked Like A Charm
!!!! these need stickied!!!!!!
after all the troubles I had getting drivers(spent over 5 hours the day the update came out trying to find a good workaround...) and not being able to get anything to work with either the drivers on CD the drivers from the Zio webpage or the drivers that came with the update itself.... I gave up and installed through a x32 server 2008 box....
I just installed these drivers on my x64 w7 ultimate box and they all went through PERFECTLY!!!! didnt even have non signed driver issues!!!!!
I also have pulled out lots of hair trying to get the drivers to function, then I had to take a step back and realize that well...I was just trying to install drivers that were NOT for a 64bit operating system lol.
Its easy to make that mistake since everyone said that it was working.
The only thing I can think is that ...most people are actually using 32bit and not 64bit, or that they just installed the drivers from the CD, which will manually select the right driver version for you.
Either way, I'm glad that I could repost this and help out.
Lots of digging, but, it was well worth it.
thanx dude..worked great..
If you still have the zio disk that can with it there shouldn't be a problem. I'm running Win7 64bit Ultimate and got it too work!
ZIO 2.2 ROOTED
ADW Launcher EX
Gingerbread Theme
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 guys,
I have now tried for the last 8 hours to connect my phone via USB to my computer without any success.
I have read many threads concerning this problem but by now I just assume that my USB port is partly broken as I have tried all the solutions and none worked for me.
I can still charge the phone but windows isn't even showing that a device has been connected. Twice of probably thirty times windows showed me that an unknown device has been connected for a couple of seconds and then the phone isn't connected anymore.
I would like to root my phone and would like to know if there is a possible way to do it. Some say it's possible (depending on the Firmware already installed), some say it isn't.
My i9000 phone has:
Firmware 2.2
Kernel 2.6.32.9
[email protected]#1
Build Number Froyo.XWJPA
I hope you guys can help me, I am getting desperate...
Try this : http://www.unlockroot.com/
Here is the drivers : http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x64.shtml
Hey guy,
did you install Kies on your Computer? Your PC need the latest USB Samsung drivers. Note that you couldn't install Samsung drivers for newer devices like the Galaxy 9000 on Windows 2000 or older. You also have to look for the right drivers for your system. Maybe you did install x86 driver on 64 bit system or x64 drivers on 32 bit system.
Driver solution:
Go to settings, system and look for the hardware manager or simply check the "windows brenchmark settings" (included in vista and win7).
Try to follow that instruction: http://forum.xda-developers.com/showthread.php?t=1542633
Note:
If you have a working USB connection, you should search for flashing instructions because flashing is always on your own risk! It isn't hard to learn but you have to know which risks are there. Don't be scared by faults they can be undone (mostly).
Flashing:
First you should upgrade your phone to an early Gingerbread (3.2) build. Just search for "Gingerbread Stock Rom" or use "Darky's Resurrection" package. You'll find them here on XDA or in the world wide web
If you get trouble you'll get support here but first you should read about flashing and rooting.
best regards
As I told you I think that my USB port is damaged and hence I can't establish a usb connection to my phone.
I tried several drivers, Kies, different settings, simply everything which was already discussed.
My Galaxy will not even show up as an "unknown device" in my Windows 7 32bit (of course I used 32bit drivers).
Unlockroot requires me to connect the Galaxy via USB to the computer, so I can't use that.
Any other suggestions?
If your using a acer computer and you have never reinstalled window than it more than likely wont work. But you can google apps like z4root and universaland root i think thats what its called. Those apps i have rooted a few froyo devices with but z4 i have never seen work with the i9000 but try and see
Sent from my GT-I9000 using xda app-developers app
taz0697 said:
If your using a acer computer and you have never reinstalled window than it more than likely wont work. But you can google apps like z4root and universaland root i think thats what its called. Those apps i have rooted a few froyo devices with but z4 i have never seen work with the i9000 but try and see
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
Thanks z4root worked perfectly.
Hey Gang!
Ok, Here's the problem, No matter which rom I run, I cannot get the ADB Drivers to load on windows 8 PRO. Used to run just fine on Win7 SP1, matter of fact it would install itself as soon as I plugged in the phone along with all the other Samsung usb drivers, now all i get is something called "Samsung File-CD Gadget USB Device" and it doesn't even install it as a phone. Any Ideas?
There have been issues from mobile driver to odin & now up to your post on win8. Donno what's the problem but it seems that what worked on win7 flawlessly for phones doesn't seem to be working equally well on win8. I haven't been able to find the solution too. Tough luck, use win7 itself. Can't help . Hope some one does...
Sent from my GT-S5830 using xda premium
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