Okay so, a few questions.
Do I need to update drivers for ADB coming from 1.5 to 1.6?
If so, were can I get a working 64bit driver?
I've tried pulling it from the SDK and it won't install, complains about no 64bit related driver of something of the sort.
Thanks for the help,
Wise
No, see sig for download link.
Related
Is anyone else having an issue with drivers running a 64 bit system, I cannot do anything from cmd line on my 64 bit desktop but from girls laptop i can root and use all the commands wtf
i have windows 7 32bit and mine is working good here is the driver i used for adb
BrianDigital said:
Is anyone else having an issue with drivers running a 64 bit system, I cannot do anything from cmd line on my 64 bit desktop but from girls laptop i can root and use all the commands wtf
Click to expand...
Click to collapse
It's probably your environment settings. Download the sdk and make sure your PATH has the extracted sdk folder location in it. I'm using windows 7 64-but ultimate, and did have a few problems at first, but everything is great now.
Also, I installed the Java Runtime Environment on my machine because I was developing an android app and I need it to run files within the SDK (like to make an emulated sdcard). You may want to install the JRE and add that to your PATH as well.
Google HTC sync x64 drivers. I installed a few weeks ago and had no issues with adb today.
oh sorry i thought thats what you meant
installed the HTC 64 bit drivers and still no go I cannot even use htc sync
I had a problem getting the device to work in cmd with xp64. I had to make sure I had a working ADB driver. One blog by a guy named Chris Bunney said to use PDAnet's driver. Basically install the 64 bit version of PDAnet in order to get the driver and then uninstall if you're not going to use it (but make sure you have the driver set up first). If you've already got a driver installed, go to the driver and manually pick "HTC Dream Composite ADB Interface" as the working driver for the device. Again, this is how I got it working on xp64 not sure how it'll go for windows 7 64 bit.
BrianDigital said:
installed the HTC 64 bit drivers and still no go I cannot even use htc sync
Click to expand...
Click to collapse
Did you use the updated driver from THIS link? Beyond that I have no other idea what to tell you beyond putting the android sdk in the root of your c: drive.
I just tried this on my girlfriends laptop with 7 x64 pro (completely fresh), and had no issues.
I had the same problem, this guide and some googling got me up and running quickly.
http://gadgets.softpedia.com/news/How-To-Solve-HTC-Hero-Sync-Problem-in-Windows-7-4442-01.html
Hello All.
I've had my UK, T-Mobile G1 for quite a while now. I have rooted it and it is running the latest CyanogenMod recovery image and ROM. I also have Apps2SD set up on my 8GB SD card, on a 512MB ext partition. This was all working fine until the problems below occurred...
I'm having some problems with several apps and ADB.
My PC runs Windows 7, 64 bit, and I can't seem to find a driver for the G1's ADB. I'm probably being incredibly stupid, but I just can't find one. I have used one before on Vista, where I had to set some boot options, but I'm not too sure / happy about doing that on my nicely functioning Windows 7. And as my friend once said; "You mess around with windows, then windows will mess around with you"...
But, anyway, I can't seem to get ADB working, if someone could either send me a link to the drivers or guide me through it, I'd be grateful...
Also, it may be due to me running CyanogenMod, but if I try to update the Facebook app, it downloads the app, and then when it tries to install, gives me the error "Installation Unsuccessful - Incompatible Update".
And with the Google Maps app, it says "Installation unsuccessful - Package file was not signed correctly". This may be due to me trying to get the hacked version of the app to get the Google Maps Navigation working in the UK, but I couldn't get that to work, so I uninstalled it and Nav Launcher, and now when I try to update from the Market it gives me that error.
I've seen a guide online with ADB commands, but as I have no access to ADB, I'm a tad screwed. I've tried runnign the commands in the Terminal Emulator in the phone, which does approximately nothing whatsoever.
So, can anyone give me any guidance on any of my Android problems?
Thanks in advance - Ethan
To the best of my knowledge no one has successfully used ADB with Windows 7/64bit
jamesrdorn said:
To the best of my knowledge no one has successfully used ADB with Windows 7/64bit
Click to expand...
Click to collapse
Ah. Looks like I'll be reinstalling Ubuntu then for the ADB. Thank you for such a fast response.
- Ethan
jamesrdorn said:
To the best of my knowledge no one has successfully used ADB with Windows 7/64bit
Click to expand...
Click to collapse
Lies, I'm running windows 7 64bit and ADB works fine.
chris4500uk said:
Lies, I'm running windows 7 64bit and ADB works fine.
Click to expand...
Click to collapse
In that case, do you remember where you obtained the driver from? I would love a link, or a zip file or something...
I'm on Vista x64 SP2 and I can use ADB just fine. You just need to download the SDK and then get the USB driver through there. It used to come included, but now you need to use the ADV and SDK manager and download the drivers as an SDK Component through there.
After that, make sure your phone is set to USB Debugging mode and plug it in then point windows to the new drivers. If it doesn't want to install the new drivers, you might need to remove the old ones first. I had to use USB Deview (DL link at bottom of page) and removed all installed HTC drivers. After that I plugged my G1 back in, pointed it at the newly downloaded drivers and all was well.
I'm running adb/fastboot/android sdk on win7 64b ultimate. The drivers are included in the sdk download. Once you download the sdk, make sure you have java installed. (I had to install JRE and JDK to get it to work properly, not sure if this was needed) Anyhow, when you have the sdk downloaded, run the sdk setup program. Go to settings and check the box for force update (unsure of the exact terminology used there) then go to available updates and your drivers are the last option on the list.
I have a folder for android stuff like fastboot and adb that I keep for fixing my phone. I keep the minimum files required for fastboot to work... adb.exe, adbwinapi.dll, fastboot.exe and the 64bit usb drivers.
I used to be able to use fastboot even after formatting my computer (and reinstalling the drivers), but it's been a long time and when I tried to do the same again, it no longer works.
Windows says the driver is not compatible with the device. I download Android SDK Tools to download the usb drivers there. They install, but fastboot still doesn't detect the phone.
I tried following tutorials out there to get fastboot to work, but I tried on 2 HTC Dreams and they don't get detected. What am I missing?
Only thing I remember being different is that I'm using Windows 7 x64 SP1 now and before I was using plain Windows 7 x64.
You need to use the usb driver removal tool and install the usb driver from SDK.
yes you've got my same trouble.
this is my thread.. http://forum.xda-developers.com/showthread.php?t=1032249
i solved with backtrack 3.. don't ask me why because i don't know.. i just have a try with bt3 because i use bring it with me on my pendrive (it can ever be useful )
BeenAndroidized said:
You need to use the usb driver removal tool and install the usb driver from SDK.
Click to expand...
Click to collapse
The old drivers I had were never installed. For some reason, Windows did not recognize a compatible driver. I did download a fresh set of drivers from SDK and windows did install them, but fastboot devices is not listing anything.
P4p3r1n0 said:
yes you've got my same trouble.
this is my thread.. http://forum.xda-developers.com/showthread.php?t=1032249
i solved with backtrack 3.. don't ask me why because i don't know.. i just have a try with bt3 because i use bring it with me on my pendrive (it can ever be useful )
Click to expand...
Click to collapse
I see no reason why I can't use fastboot on Windows if it worked before. Perhaps if there is no other way, I'll try Linux distros.
It sound like there is no compatible driver for Windows 7 x64 SP1. Check google to see may be they might have an updates.
BeenAndroidized said:
It sound like there is no compatible driver for Windows 7 x64 SP1. Check google to see may be they might have an updates.
Click to expand...
Click to collapse
So there is an actual difference between win7 and sp1 in regards to the drivers and not that I set it up wrong?
From my experience on working with Windows. Every version always different. As far as how much different, I can't tell.
If you had it working with W7 before SP1, then there is a change in driver that causing it not to work correctly. Do you required to upgrade to W7 SP1? Or is that your preference?
BeenAndroidized said:
From my experience on working with Windows. Every version always different. As far as how much different, I can't tell.
If you had it working with W7 before SP1, then there is a change in driver that causing it not to work correctly. Do you required to upgrade to W7 SP1? Or is that your preference?
Click to expand...
Click to collapse
Well that's all I can think of. Just wanted to know if anyone else had problems with sp1. I think faastboot should work with my winxp vms.. gonna try that next time I try to use fastboot..
Need some help with setting up ADB.
Ive installed both 32bit and 64bit drivers, nothing works.
In device manager it just comes up Galaxy S, If I try and update drivers from device manager it just says no drivers can be found (Whilst pointing at the 32bit and 64bit drivers.) Ive restarted the phone and PC loads of times.
Im using Windows 7 32Bit.
Any help is appreciated.
Thanks
Is Kies running?
Tried with it running and without
Still cant get it working, Are there any other drivers available? Ive searched and couldnt find any.
dpgc213 said:
Still cant get it working, Are there any other drivers available? Ive searched and couldnt find any.
Click to expand...
Click to collapse
Get and Installl Java SDK and JDK
Once done make sure your environment variable "PATH" is referring your tools folder.
C:\XXX\android-sdk-windows\tools
Google driver could be found on android-sdk-windows\extras\google\usb_driver
Hope this helps
Ive already done that, I've got quite a few HTC phones that work perfectly with ADB. Its just the SGS.
So, I've been trying to install the drivers for a generic rk29 rockship tablet. I had to go to adbdriver installer as a last resort. Yet, not even this helps. It says that it's incompatible with my x64 windows 8. picture attached. Any help is appreciated.
You can try running the installer in Compatibility Mode (right-click the file, go to Properties, set Compatibility Mode for Win7). That might work. Or it might not. Or it might bluescreen. But there's at least a chance it would work.
A bit misleading that it says xp/vista/7/8 x86 and x64 and then errors on x64.
I would try what gooddaytodie suggested and then contact the manufacturer to complain.
Or get virtualbox, install Linux within and use adb through that but that is an absolute faff to go through for 1 driver. You don't tend to need device specific adb drivers under Linux, just the adb itself.
I am install manually with disable signature process and its working on my Windows 8.1
Ah, completely unsigned driver. Good times... (not). Hope you trust the source.
I used the HTC drivers. I just extracted the files from the installer and installed the driver manually through device manager.
GoodDayToDie said:
Ah, completely unsigned driver. Good times... (not). Hope you trust the source.
Click to expand...
Click to collapse
Oh so fun....
Needed to disable the driver enforcement to install my stellaris launchpad on windows 8 which is entirely contrary to texas instruments installation instructions but I do not appear to be the only one that had to do that.
Can someone please send me a Google Drive link to the drivers they downloaded. My archives are claiming they're corrupted.