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.
Related
I tried installing the latest builds of Haykuro into my G1, they install fine however I lose adb I keep getting "error: device not found" when I revert to the latest JesusFreak build it starts working again just fine, any ideas why? Thank you in advance.
Sometimes adb.exe stay open in windows process close it reboot your phone and plug it again all is good.
did this fix it?
If not i updated to the new spl and got the new drivers and now adb works fine.
I am using Windows 7 64bit... I could get ADB working one time, and two mins later not at all.
I found this "tip" in a prior thread and I cannot remember who to credit (sorry).... but this worked for me last night without a problem....
When you reboot... hit F8, and scroll all the way down and disable Digital Driver Signing.
After I booted ADB was working great.
Thank you all
Thank you for all your responses I will try them tonight =]
Do0zman said:
did this fix it?
If not i updated to the new spl and got the new drivers and now adb works fine.
Click to expand...
Click to collapse
quick question can u point me in da right direction for the new adb driver....ive searched cant find it
im still getting the problem ive tryed disable driver signing uninstalling reinstall drivers reboot after reboot process kills. And stil cant mount adb. Vista Ultamite 32 bit with update drivers from haykuro
jmotyka said:
im still getting the problem ive tryed disable driver signing uninstalling reinstall drivers reboot after reboot process kills. And stil cant mount adb. Vista Ultamite 32 bit with update drivers from haykuro
Click to expand...
Click to collapse
I'm trying to get this to work also. I have Vista Ultimate 32 bit, where is this new driver that i've read about?
I7oobie said:
I'm trying to get this to work also. I have Vista Ultimate 32 bit, where is this new driver that i've read about?
Click to expand...
Click to collapse
Its in the driver package, just unzip it to C:\ then plug in your phone, go to device manager and look for Android Device, then install the driver from that folder on C:\
works for me and im on XP Laptop and an Vista Ultimate X64 Machine
Dantehman said:
Its in the driver package, just unzip it to C:\ then plug in your phone, go to device manager and look for Android Device, then install the driver from that folder on C:\
works for me and im on XP Laptop and an Vista Ultimate X64 Machine
Click to expand...
Click to collapse
Thanks for the response. I could've swore I've done that, but maybe I'll try it again.
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 just got my Gtab today and can already find things I just cant live with so im trying to prep for a new ROM when there are some stable ones out there.
I have downloaded everything from the CWM recovery and root threads but i cant seem to get a driver to work... I have tried section #2 multiple times over on both XP pro x86 & Win7 pro x64 but i end up with the same 3 unknown devices on both *neither have SDK*. When i try to install the unknown USB device with the drivers supplied in nvflash it cant find anything suitable *even pointing to sub-directories*. I downloaded the drivers mentioned in the rooting thread and installed those, I went back to the DM and tried every single directory in the newly unpacked location "C:\Program Files\Samsung\etc.." which had quite a few different ones but i havent gotten anywhere.
I remember this being almost identical to the problems i had trying to root my phone so I finally found linux directions and worked from my mac. Does anyone have a clue whats going on and how to get MS FAIL OS to work?
I guess im the only person having this problem... ohh joy another android that is going to be a pain in the as to root
on your computer, uninstall ALL the samsung drivers (for any previous samsung device/phone). Then connect the tab to your computer and let it search on its own. on your tab the usb debugging should be turned off.
I think the tab is designed to let windows recognize it as usb, but if you have any previous drivers they get into the way.
Hello,
Just an average XDA noob speaking here. Reason i'm creating this topic is because I'm having problems getting the ADB composite drivers right. Previously I've rooted a HTC Hero without any problems, but with my Huawei U8800 Ideos X5 I just can't fix it, I searched in all corners of the Internet. Below are my specs.
- Android 2.3.5
- Unbranded
I've also tried to root with SuperOneClick and by replacing the boot.img, but I can't get it to work because of the drivers.
When I get to recover mode (the pink/purple screen) it isn't showing me the IMAGE folder on my computer. Also tried to install new drivers for the ADB composite by using the H:/Mobile Partner disk on my phone but that isn't helping either. It says their isn't any new hardware found in the folder, but as you can see on the image, there are still exclamation marks. I Also uninstalled the drivers a few times and tried to re-install them but that isn't working neither. Firstly my phone was recognized as an Other device > Ethernet Controller in the device manager screen. But that was possible to solve by browsing to the H:\MobilePartner\Drivers folder.
By the way, when in recovery mode plugged in the computer, it shows me two drivers called "HUAWEI TECHNOLOGIES". I can't seem to find a good driver for those, they also show the !-mark.
Any help will be appreciated! :good:
The image. www(dot)dropbox(dot)com/s/tn2q2neo5362gd1/screenshot.1.png?m
maybe you can try to install this driver from huawei.. it worked for me..
https://www.box.com/s/ywqomlr1pj1ca4ls0wlm
Drivers
Get the drivers from here
http://forum.xda-developers.com/showthread.php?t=1876457
(if your problem solved click thx)
socioan said:
Get the drivers from here
http://forum.xda-developers.com/showthread.php?t=1876457
(if your problem solved click thx)
Click to expand...
Click to collapse
Sadly the password for the Quallcomm setting is not working :/ 0 and 0000 both didn't. Thanks for your help
@ first poster
Used that driver install, when the phone is connected and has USB Debug on this is the situation, screen: www(dot)dropbox(dot)com/s/y6x0ta8bwp1rqsr/screenshot.2.png
have u tried to uninstall/remove all related driver instances and try to do it afresh?
iamelton said:
have u tried to uninstall/remove all related driver instances and try to do it afresh?
Click to expand...
Click to collapse
What's the best way to do that? Just delete them from the device manager screen and letting them re-install automaticly by the phone? Or just download drivers from the internet and install it manually?
Jordy14 said:
What's the best way to do that? Just delete them from the device manager screen and letting them re-install automaticly by the phone? Or just download drivers from the internet and install it manually?
Click to expand...
Click to collapse
if u r doing manual driver installation, then its best to disallow auto-installation by windows..
delete all instances from device manager, or u may use an application called "USBDeview" to remove the usb drivers.. and i think this second way is probably doing it more cleanly..
iamelton said:
if u r doing manual driver installation, then its best to disallow auto-installation by windows..
delete all instances from device manager, or u may use an application called "USBDeview" to remove the usb drivers.. and i think this second way is probably doing it more cleanly..
Click to expand...
Click to collapse
Thanks man, gonna try that tomorrow after school.
Will keep you updated.
Sorry for the late update, forgot about the topic... I threw away all the drivers, got the pinkpurple screen and connected to my pc. It's now missing this drivers when connected, Windows can't install them itself. Check the printscreen below.
http://i50.tinypic.com/20qyzc0.png
Jordy14 said:
Sorry for the late update, forgot about the topic... I threw away all the drivers, got the pinkpurple screen and connected to my pc. It's now missing this drivers when connected, Windows can't install them itself. Check the printscreen below.
http://i50.tinypic.com/20qyzc0.png
Click to expand...
Click to collapse
this works 100%
1. Tools
a. Drivers for U800 32bit win 7 (tested and work )
http://www.2shared.com/file/fnP5fc8G/u8800Drivers.html
b. Drivers for Android 32 and 64 bit win 7 (not tested )
http://www.2shared.com/file/ZNZ4Q0lk/Attachments_2012_09_12.html
socioan said:
this works 100%
1. Tools
a. Drivers for U800 32bit win 7 (tested and work )
http://www.2shared.com/file/fnP5fc8G/u8800Drivers.html
b. Drivers for Android 32 and 64 bit win 7 (not tested )
http://www.2shared.com/file/ZNZ4Q0lk/Attachments_2012_09_12.html
Click to expand...
Click to collapse
Gonna try that out, do I need both?
The first one i have tested and it is for 32 bit win 7
The second one i havent test it it is for 32 and 64 bit win 7
Choose one acording your windows
socioan said:
The first one i have tested and it is for 32 bit win 7
The second one i havent test it it is for 32 and 64 bit win 7
Choose one acording your windows
Click to expand...
Click to collapse
Ok ty, I started over, deleted all the drivers and let Windows install the drivers themself. Still not working. I find it very strange why Android Composite ADB Interface pops up 4 times in the device manager... As you can see, he installed one by himself >> https://(w)(w)w.dropbox.com/s/lttgky3qozhraf9/kak4.png
I'll try your method.
Hey everybody,
I got my Oppo since 3 days now and I am very satified with it. But this morning I was trying to connect the device via USB to continue developing an app in Processing and the IDE didn't find my device. The IDE is waiting for the device to become available and that's it.
After this, I tried the universal adb drivers, the usb drivers of the SDK and the usb drivers of the pdanet app. Nothing worked for me so far. In the device manager the device is listed as "Android ADB Device", so it should be working, right? I am working on Windows 8 on my laptop right now and I think this is where the evil comes from
Any Processing developers here, which got Processing working with their Oppo??
Greetings
digga_mies
I use windows 8 on my PC, but OPPO is recognized when plugged in. I'm pretty sure my correct drivers were installed when I connected the phone.
sent from my Find 5 using Tapatalk 4 Beta
Coreym said:
I use windows 8 on my PC, but OPPO is recognized when plugged in. I'm pretty sure my correct drivers were installed when I connected the phone.
sent from my Find 5 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Okay, and what drivers did you use? The stock drivers of Win 8? Or do you have downloaded others?
I don't know if it helps, but I have installed the stock firmware X909EN_12.A.09_GLO_009_130514
digga_mies said:
Okay, and what drivers did you use? The stock drivers of Win 8? Or do you have downloaded others?
I don't know if it helps, but I have installed the stock firmware X909EN_12.A.09_GLO_009_130514
Click to expand...
Click to collapse
I remember having some issues trying to get Casual to work as it wasn't seeing my phone. I'm pretty sure I used this reference to get everything working correctly.. Install Drivers for any Android
Okay, tried it again with pdanet and got no success again. Even the platform tools adb.exe doesn't recognize my phone as an adb device. I'm getting a little bit frustrated right now.
By the way, I tested it on Windows 7 and it doesn't work either.
Anyone got another idea?
digga_mies said:
Okay, tried it again with pdanet and got no success again. Even the platform tools adb.exe doesn't recognize my phone as an adb device. I'm getting a little bit frustrated right now.
By the way, I tested it on Windows 7 and it doesn't work either.
Anyone got another idea?
Click to expand...
Click to collapse
Try wireless adb, and connect manually to your phone via command line (something like: adb connect YOURIP). I pretty much use only wireless adb (as I do tend to develop stuff that relies a lot on the 9 DOF sensors...) Cheers.
I got it. My device was shown in the device manager all the time as adb device, but the Processing IDE didn't found it. In the Oppo forums is the same error described with eclipse.
The solution was, to change the adb_usb.ini in "C:\Users\YOURUSER\.android". In my file wasn't any entry and I simply added "0x22D9". That's it! Worked for Windows 7 and 8.
:victory::victory:
digga_mies said:
I got it. My device was shown in the device manager all the time as adb device, but the Processing IDE didn't found it. In the Oppo forums is the same error described with eclipse.
The solution was, to change the adb_usb.ini in "C:\Users\YOURUSER\.android". In my file wasn't any entry and I simply added "0x22D9". That's it! Worked for Windows 7 and 8.
:victory::victory:
Click to expand...
Click to collapse
I dont understand what you mean adb_usb.ini
can you make a guide?
digga_mies said:
I got it. My device was shown in the device manager all the time as adb device, but the Processing IDE didn't found it. In the Oppo forums is the same error described with eclipse.
The solution was, to change the adb_usb.ini in "C:\Users\YOURUSER\.android". In my file wasn't any entry and I simply added "0x22D9". That's it! Worked for Windows 7 and 8.
:victory::victory:
Click to expand...
Click to collapse
Thanks for the device code!