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
Related
After hours of headache I am still unable to test my app on the nexus one device... mainly because my 64 bit Vista cannot find a device driver for the usb.
1. I have gone tried the developer.android instruction, which ofcourse does not work.
2.I have also gone tried the idea posted in a thread in this forum <mods wont allow me to post link> without success mainly because the cmd says "boot configuration data store cannot be opened. access is denied."
3. I went over Install and run USBDeview<mods wont allow me to post link> , but it wont work either, USBDView cannot uninstall in step 5 of the blog.
Any help would be greatly appreciated. Please if someone has installed the USB Driver for nexus one in a Windows Vista x64 help me out.. i have so many apps on the emulator which I want to try on the new device !!
Is their any other way I can port my app from the emulator and try it on the device? Thanks in advance
Please do not post non-dev related threads in the dev section... yeah, i think u thot this was a dev question since u are talking abt porting an app, but the question is really not dev related... this shud go in Q&A... mods please move!!
In any case, I've installed the N1 driver in Windows 7 x64 without any problem, and since the driver is the same for Vista & 7 x64, I don't think it shud be a problem...
I simply downloaded the drivers via the SDK setup... plugged in the phone and manually installed the driver via device manager... worked like a charm!!
+1 for the section and also for it working on Win 7 pro x64 for me.
+1 on posting in the proper section. I also have it working on win 7 x64.
As a side note, people who think the word 'should' is spelled 'shud' should not be correcting people.
TwilightArchon said:
After hours of headache I am still unable to test my app on the nexus one device... mainly because my 64 bit Vista cannot find a device driver for the usb.
Click to expand...
Click to collapse
Try turning on USB debugging! Worked for me on Win7 when having similar difficulties
TwilightArchon said:
After hours of headache I am still unable to test my app on the nexus one device... mainly because my 64 bit Vista cannot find a device driver for the usb.
1. I have gone tried the developer.android instruction, which ofcourse does not work.
2.I have also gone tried the idea posted in a thread in this forum <mods wont allow me to post link> without success mainly because the cmd says "boot configuration data store cannot be opened. access is denied."
3. I went over Install and run USBDeview<mods wont allow me to post link> , but it wont work either, USBDView cannot uninstall in step 5 of the blog.
Any help would be greatly appreciated. Please if someone has installed the USB Driver for nexus one in a Windows Vista x64 help me out.. i have so many apps on the emulator which I want to try on the new device !!
Is their any other way I can port my app from the emulator and try it on the device? Thanks in advance
Click to expand...
Click to collapse
Here you go - USB Driver that worked fine with Vista 64 bit - found on this very site. Install the driver and just enable USB debugging.
krohnjw said:
Here you go - USB Driver that worked fine with Vista 64 bit - found on this very site. Install the driver and just enable USB debugging.
Click to expand...
Click to collapse
Thanks a lot.. this zip file worked like a charm unlike the last ones I downloaded from what seems to be everywhere ( even the google repository) !
Hi all,
I am unable to get Kies to recognise my galaxy s (when in Kies mode) or windows for that matter. I've tried installing the samsung usb drivers etc using the latest version of kies, still doesn't work.
What options do I have now in terms of firmware flashing? (I'm not installing 32bit xp just to flash my phone)
Cheers
if you search the forums you will find your answer, which will be along the line sof using Odin, very easy to use, so good luck and enjoy.
win7-64bit and kies connection semi-working method
I've tried almost all methods mentioned on different forums...but since i'm unwilling to mess to much around i've opted for this way:
using latest kies 1.5.3. 80something... on win7 64 bit..
remove the lockpattern from the phone if yo uhave it enabled
install kies...remove the kies autostart option and the kies trayagent
do the repair drivers and reboot
ones the bios screen is done..have the phone unlocked and connect to pc/laptop
wait and wait some more after login to windows..
one most occasions windows will finally tell you it have a new device ready for you...then open kies and life is good.. at least until like in my case the laptop goes into powersave mode and the connections are broken and I have to do the reboot step again
the firmware update from jf__ something to jm__ something was a hassle...but after a few attempts to run it the darn thing finally worked..
hope this helps
thanks for the help b, tried it but didn't work
I think the official word from samsung is that kies does not support windows 7 64.
Seriously regret ever getting this phone.
ardll said:
thanks for the help b, tried it but didn't work
I think the official word from samsung is that kies does not support windows 7 64.
Seriously regret ever getting this phone.
Click to expand...
Click to collapse
i am with win7 x64, fine here
using odin to flash rom is dam easy job.
Kies updated to _82 today.
the _82 update fixed closing the firmware updater for me that was in the last 2 builds on win7 x64 , it promptly closes having not used up more than 33mb ram when I click cancel or close after checking for new firmware, previously it billowed up to over 1300mb use and really flawed my system until it, kies and the connection manager were terminated fully.
http://www.samsung.de/de/support/detail.aspx?aguid=47e29085-4dff-4b5c-b8ab-dd9b9c8b70f8&dl=software
try the new PC Studio software for SGS
download link and detailed info on SGS wiki, click my link
What are the tips/tricks to get KIES to work ?
I am running eclair. Windows 7 64 bit. I installed the 64 bit drivers etc. Im using TouchWiz. It just says connecting device in Kies but it never does.
On the phone, it just keeps looping ....
Anyone help me out? I will donate to your paypal if you can get Kies working for me.
Funkadelick said:
What are the tips/tricks to get KIES to work ?
I am running eclair. Windows 7 64 bit. I installed the 64 bit drivers etc. Im using TouchWiz. It just says connecting device in Kies but it never does.
On the phone, it just keeps looping ....
Anyone help me out? I will donate to your paypal if you can get Kies working for me.
Click to expand...
Click to collapse
There is no official support of KIES for Win7 64 bit. It works for some, for less fortunate ones, it doesn't. You can try installing these http://graveyard.hu/SAMSUNG_USB_Driver_for_Mobile_Phones_x86.zip
OR
You can try Samsung PC Studio http://in.samsungmobile.com/support/softwaremanuals/softwareNpsUpdate.do?phone_model=GT-I9000
OR
Weird still, there have been solutions to this where you can update your windows media player 10/11.
OR
if you are adventurous enough, give a try with ODIN and flash any firmware/ROM you wish.
Good luck.
rajuki said:
There is no official support of KIES for Win7 64 bit. It works for some, for less fortunate ones, it doesn't. You can try installing these http://graveyard.hu/SAMSUNG_USB_Driver_for_Mobile_Phones_x86.zip
OR
You can try Samsung PC Studio http://in.samsungmobile.com/support/softwaremanuals/softwareNpsUpdate.do?phone_model=GT-I9000
OR
Weird still, there have been solutions to this where you can update your windows media player 10/11.
OR
if you are adventurous enough, give a try with ODIN and flash any firmware/ROM you wish.
Good luck.
Click to expand...
Click to collapse
That's the thing, i don't want to be adventurous. I bought this phone straight up and paid over $500 for it and yet I can't update it ? Is this a joke ?
Probably the worst phone / software / customer service ever created. There isn't a phone in history with as much problems as this piece of sh!t.
NO SUPPORT FOR WINDOWS 7 ???????????????
What the FCK is wrong with these people? They thing we are all running windows 98 or something? Stupid fcks.
Funkadelick said:
What are the tips/tricks to get KIES to work ?
I am running eclair. Windows 7 64 bit. I installed the 64 bit drivers etc. Im using TouchWiz. It just says connecting device in Kies but it never does.
On the phone, it just keeps looping ....
Anyone help me out? I will donate to your paypal if you can get Kies working for me.
Click to expand...
Click to collapse
It works for me and i have done it a couple of times.
First you need to install it with administrator rights.
Put the phone so it go into kies mod automatic.
Use the latest kies.
Reinstall the driver if windows don't se it. You have the options in kies.
If it still don't work download android sdk and follow all info there. There is also drivers you can install with it.
I don't remember but i think it 32-bits. But that's okay.
If you can get adb to work( adb shell) then kies should see it.
Sometime you need to install drivers that windows installs.
Just go to device manager and put your usb cabel in the phone and watch when you see the phone shows up in device manager.
Install the drivers then pull out the cabel. Then install the drivers with kies. Then put the cabel in with kies open.
It should work.......
**Using my own JPU kernel, z4mod, 339MB Ram and ext2 filesystem**
I had the same issue. Samsung advised that you re-update the drivers (double click the exe file in usb drivers within program files - kies), and this did the trick. Although i have to do this everytime i want to use kies but seeing as i only need it when the updates come i have no issue.
Stupid samsung and their unkown reason for not taking OTA updates.
DamianGto said:
It works for me and i have done it a couple of times.
First you need to install it with administrator rights.
Put the phone so it go into kies mod automatic.
Use the latest kies.
Reinstall the driver if windows don't se it. You have the options in kies.
If it still don't work download android sdk and follow all info there. There is also drivers you can install with it.
I don't remember but i think it 32-bits. But that's okay.
If you can get adb to work( adb shell) then kies should see it.
Sometime you need to install drivers that windows installs.
Just go to device manager and put your usb cabel in the phone and watch when you see the phone shows up in device manager.
Install the drivers then pull out the cabel. Then install the drivers with kies. Then put the cabel in with kies open.
It should work.......
**Using my own JPU kernel, z4mod, 339MB Ram and ext2 filesystem**
Click to expand...
Click to collapse
silly question - how do you install with admin rights ?
silly question - how do you install with admin rights ?
Right click Run as admin.
jje
Hello all, first time poster, but I have been lurking for a few days absorbing what I can. I just recently got my first Android phone, the Droid Turbo. So far I love it. I am trying to use the awesome Debloater tool I found elsewhere, but I have a problem. When ever I connect my Droid Turbo to a computer in my house (desktop or laptop), I get an error in device manager. Neither the standard Google ADB driver, or the Universal ADB drivers seem to be working. I am not stupid when it comes to computers, but am I missing something? I have uninstalled, restarted and reinstalled both drivers a few times, I even tried using the SDK to install Google's drivers as well. USB debugging is turned on. I can't seem to find any USB drivers for the Droid Turbo at the Motorola site listed with Google. The phone is new, running 4.4.4 KitKat. I am running Windows 7 x64 on my PC, a fairly fresh install. I'm really at a loss to figure out what is going on, any help or a point in the right direction would be greatly appreciated . I have already searched most of the relevant information and videos on this sight, but perhaps I missed something.
Please keep up the good work! My phone is just begging for a root/unlocked bootloader with a clean Android install, But I will settle for no bloatware for now.
I was going to include a screenshot of what I see with my phone plugged in, but I don't have enough posts yet. None of the options of "Update Driver" result in it working, its as if it sees my Droid Turbo there, but I just don't have correct the drivers for it, and I cant find the right ones.
Install drivers from motorola and select driver manualy, dont work with Windows XP
matheus_sc said:
Install drivers from motorola and select driver manualy, dont work with Windows XP
Click to expand...
Click to collapse
at this link:
Motorola Device Manger/USB drivers.
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Awesome!
Awesome! That link is what I was missing. Thanks a lot to both of you!
Hello, I just received my Nexus 6 but I have a problem which also was also a problem on my old note 2. It won't recognize the drivers or install them. I did some test, it connected and instantly updated the drivers on another machine, so it's not the cable or the phone(A windows 7 machine), and it also works with my windows 10 tablet.
I also removed digital signature requirement for installing them, doesn't seem to work. I literally have no clue and did my research for about 1 hour to no avail. I must have done something way long in the past on windows 8.1 to flash my note and that ****ed up somewhere in windows, but I have absolutely no clue here.
Worst comes to worst, I'll just reformat, as this was an "upgrade" from windows 8.1.
Couldn't this be linked to motherboard drivers possibly?
Edit : http://puu.sh/jVpz1/38c5e640f8.jpg I tried manually to uninstall/reinstall, to no avail.
Lyper said:
Hello, I just received my Nexus 6 but I have a problem which also was also a problem on my old note 2. It won't recognize the drivers or install them. I did some test, it connected and instantly updated the drivers on another machine, so it's not the cable or the phone(A windows 7 machine), and it also works with my windows 10 tablet.
I also removed digital signature requirement for installing them, doesn't seem to work. I literally have no clue and did my research for about 1 hour to no avail. I must have done something way long in the past on windows 8.1 to flash my note and that ****ed up somewhere in windows, but I have absolutely no clue here.
Worst comes to worst, I'll just reformat, as this was an "upgrade" from windows 8.1.
Couldn't this be linked to motherboard drivers possibly?
Edit : http://puu.sh/jVpz1/38c5e640f8.jpg I tried manually to uninstall/reinstall, to no avail.
Click to expand...
Click to collapse
Delete all your android drivers, and try this:
http://forum.xda-developers.com/showthread.php?t=2588979
I removed 4 adb drivers and many samsung ones, installed with administrator settings the linked content, then it tried to install the nexus 6 via the default windows updated. Seemed to work, get the sound for connection, but no option to transfer my stuff. I tried uninstalling the drivers and re-installing, still nothing.
http://puu.sh/jVt0q/57fb6bf8d3.png
No more ideas?
Lyper said:
No more ideas?
Click to expand...
Click to collapse
Been a long time since I did it. Have to download the google driver. Then go to device manager where you delete the Android driver. Right click and will ask for where to get the driver. Pick local to search PC for driver and install from there. That the best I remember off top of my head. On mine is Asus driver. I deleted it and then searched PC for the Google driver.
prdog1 said:
Been a long time since I did it. Have to download the google driver. Then go to device manager where you delete the Android driver. Right click and will ask for where to get the driver. Pick local to search PC for driver and install from there. That the best I remember off top of my head. On mine is Asus driver. I deleted it and then searched PC for the Google driver.
Click to expand...
Click to collapse
Yeah well I did that multiple times, which didn't work. I really don't feel like reformatting, ho boy, but I really gotta get this going. Thanks for the suggestion!
Try switching ports.
Sent from my Nexus 6 using Tapatalk
I tried switching ports.
Ok so the list of things I tried : Manually removing any drivers that had to do with android/usb phone, I reinstalled the drivers for my motherboard, I fixed every system inconsistency with ccleaner, removed android studio. I had also manually removed any prior detection fo the nexus 6 in the device manager. It will once again pop up the "driver install" from windows, complete, but be impossible to manually update via device manager as it doesn't recognize my device.
I'm also using the default cable from my nexus 6, and tried others. Is there anything else to do? Otherwise reformatting tonight. Thanks everyone for the support.
Hello, sorry to keep bumping this thread. I just reformat... and the problem still persists. I have no clue what to do anymore, I literally tried everything I could possibly think of.
Anyone got any ideas? To state again, I'm running windows 10 x64.
http://puu.sh/k0qiv/a4802d7e43.png
I just found that when I used the "reset pc" function of Windows, I still have remnants of adb. What am I supposed to do here? Any ideas how to remove them fully? Could that be the problem?
Nevermind, I did a total complete reformat now, still doesn't work. I'm literally out of ideas now.
Should I contact my motherboard manufacturer (MSI) ?
not sure what to tell you, but definitely samsung drivers and motorola drivers do not play well together very often
Lyper said:
http://puu.sh/k0qiv/a4802d7e43.png
I just found that when I used the "reset pc" function of Windows, I still have remnants of adb. What am I supposed to do here? Any ideas how to remove them fully? Could that be the problem?
Click to expand...
Click to collapse
Not sure what you lost. I did an upgrade from 8.1 to 10. All my SDK, Java, adb/fastboot, Path Variables, ect remained intact. Depending on Make and Model of PC there have been a lot of drivers missing or needing updates. The PC should see the phone regardless of adb/fastboot status. It has to be a driver on PC side. The OS supports it. It should show as an Android device even if it doesn't say Nexus 6. Nexus 6 shows the Google Driver is good.
prdog1 said:
Not sure what you lost. I did an upgrade from 8.1 to 10. All my SDK, Java, adb/fastboot, Path Variables, ect remained intact. Depending on Make and Model of PC there have been a lot of drivers missing or needing updates. The PC should see the phone regardless of adb/fastboot status. It has to be a driver on PC side. The OS supports it. It should show as an Android device even if it doesn't say Nexus 6. Nexus 6 shows the Google Driver is good.
Click to expand...
Click to collapse
Can this be the problem?
http://www.msi.com/support/mb/P67AC43_B3.html#down-driver&Win10 64
There doesn't seem to be any drivers for windows 10, I tried installing the windows 8 ones, but that didn't work.
Lyper said:
Can this be the problem?
http://www.msi.com/support/mb/P67AC43_B3.html#down-driver&Win10 64
There doesn't seem to be any drivers for windows 10, I tried installing the windows 8 ones, but that didn't work.
Click to expand...
Click to collapse
Have you tried a Windows update since the original boot. On my son's AZUS the touchpad driver was bad. It had changed driver to a Generic. Deleted that driver and ran Windows update and it found the new driver. Worth a shot. Hard to tell what to do. I couldn't see any differences after the Win 10 upgrade. Didn't even effect my dual boot Linux. My friend just lost lost the drive sync to his Linux setup.
---------- Post added at 11:40 AM ---------- Previous post was at 11:38 AM ----------
Just an update, I cannot believe I found the problem while I kept digging.
Get this.
It was because I had Windows 10 N version. I am not ****ing kidding. Somehow the windows bloatware makes it so I'm unable to install phone drivers. It seems to be a recurrent problem because my friend has another phone and it did the same to him. How the **** is this a thing? Like, how could microsoft let such a **** up go by and there hasn't been a big controversy? Am I missing something?
I feel like the cheaper version of an OS gimping the user by removing such basic function as installing phone drivers is insane. But then you can fix it by installing the media pack for your respective OS, but you have to know that.
I'll leave this up if anyone ever searches for these terms.
Lyper said:
Just an update, I cannot believe I found the problem while I kept digging.
Get this.
It was because I had Windows 10 N version. I am not ****ing kidding. Somehow the windows bloatware makes it so I'm unable to install phone drivers. It seems to be a recurrent problem because my friend has another phone and it did the same to him. How the **** is this a thing? Like, how could microsoft let such a **** up go by and there hasn't been a big controversy? Am I missing something?
I feel like the cheaper version of an OS gimping the user by removing such basic function as installing phone drivers is insane. But then you can fix it by installing the media pack for your respective OS, but you have to know that.
I'll leave this up if anyone ever searches for these terms.
Click to expand...
Click to collapse
Can you tell where can I find the media pack for windows 10?
Thanks.