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.
Related
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 am in dire need of assistance.
My hero is running 1.1 fresh and trying to use prekitchen 0.2 after prekitchen 0.1 and 0.1b failed yesterday. My phone won't give me the option to MOUNT SD when I connect to my pc, though it does have option for HTC Sync.
Now my device wizard is showing problem for the "android device" and when I open it, it tells me it's missing the adb driver!?!?!
WTF? I have had zero problems until yesterday. I also tried to DL the update driver from http://developer.android.com/sdk/index.html but after extraction windows says there is no driver in the folder.
AHHH. I think I might break my Hero in half, or worse, my computer.
please help, anyone, please.
try re-downloading the SDK and running/installing it. That's where the drivers come from
Please try to not post the same thing in multiple places.
You are running windows 7. Download the driver from here and install it.
flipzmode said:
Please try to not post the same thing in multiple places.
You are running windows 7. Download the driver from here and install it.
Click to expand...
Click to collapse
It worked!! Thanks so Much Flipz, wish I could figure out how this stuff got removed to begin with since your pre-kitchen worked successfully once.
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..
Hello.
And bacon and spam:
I've recently upgraded my SGS to ICS (ICSSGS ROM) and started to develop a simple application.
So, now i've got to the point that the emulator starts to show its limitations, so i need to debug directly on the real device.
Well, i've been trying to make ADB recognize my phone, tried several usb drivers from several sites, none of them worked.
After several hours spanking windows, it's finally working (yes! almost 6 AM in the morning!).
What matters:
So, to anybody who have the same problem as i had, do the following:
0. Uninstall any drivers that you've tried before.
1. Extract the zip file that i've uploaded to anywhere you like.
2. Enable debugging on your phone and connect it to PC throught the USB cable
(Just connect it, don't mount)
3. On your computer, click Start -> Right click on "Computer" -> Manage
This will open the "Computer Management" window (it might take some seconds to load).
4. Click "Device Manager". Now you should find your device in the list. It must be really easy to find. It's called something like "GT-I9000" or "GalaxyS" and it has a yellow warning sign next to it.
5. Right click on it and choose "Update Driver Software". In the window that appears, choose "Browse my computer for driver software". It then asks you where is the driver.
6. Click the "Browse" button and choose the folder you extracted from my zip file.
(If you didn't change it, it must be called "Android Composite ADB Interface")
7. Click "Next" and cross your fingers. If you're lucky, it may work for you.
Final notes:
1. I'm not responsible for ANYTHING. Whatever you do, it's your own choise to do it. I guarantee absolutely nothing.
2. This is was tested on Windows 7 - 64 bits with Team ICSSGS RC4.2 ROM and Semaphore ICS 0.9.1 Kernel.
3. Have fun.
4. If you try this, please answer the topic and tell everybody if it's working for you (mentioning your Windows version and what ROM you use).
Driver file:
-> http://www.mediafire.com/?t8ekrd9ly3mwwbk
Missing file when installing driver on windows 7 x64
Hi,
I have recently installed the most recent Dark Knight ICS 4.0.4 build to my Samsung Galaxy S. The ROM seems very good but I'm an android app developer and need to be able to debug my applications on the device via USB.
I have tried the driver provided in the thread which won't install due to a missing file according to the Windows 7 x64 driver install wizard. The exact message is displayed after step 7 and says:
"Windows found driver software for your device but encountered an error while attempting to install it."
"Android Composite ADB interface"
"The system cannot find the file specified".
Is there a file missing in the package? Has anybody managed to get this driver working?
Cheers,
Ben
Does it say that it doesn't find a controller or that is there a missing file?
Anyway, please try this installer and let me know if it works for you:
http://www.mediafire.com/?v70501cxbzzdvc2
What's wrong with the Nexus S drivers available with Android SDK?
Google USB driver, R4 developer.android.com/sdk/win-usb.html
The SGS will present it self like that when it is running ICS/CM7/CM9.
Sent from my GT-I9000
METEMEDO said:
Does it say that it doesn't find a controller or that is there a missing file?
Anyway, please try this installer and let me know if it works for you:
http://www.mediafire.com/?v70501cxbzzdvc2
Click to expand...
Click to collapse
Dont work for me.
System: Windows 7 x64
Android 4.04 Dark Knight
Nevertheless thanks for your approach. I'll test if it works with the SDK Updater.
I'm going to test in my desktop this weekend to check if it works with it.
I have the same problem, but with WIndows 7 32 bit. Drivers from discusion doesn't work. Don't you have some for 32 bit?
I found SDK Components on developer.android.com, where is Android driver which suppose to work, but unfortunately ODIN still do not see phone.
I also have the same problem but mine is worse because my phone is completely down after I tried to restore from a GB ndriod backup failure , phone won't boot , cannot boot into recovery only in download mode but no way my 4 x computers would detect the phone now ....tried using heimdall in linux as well as sdb, no go....so sad...help...
Sent from my Dell Streak using XDA
Using Google USB drivers finally worked for me. They can be optionally installed with Android SDK using SDK manager (extras). After installation drivers can be found in <sdk>\extras\google\usb_driver.
Just follow the instructions in the first post to find your device from device manager with exclamation mark. Need at least one reboot to work and I also redirected the driver installation process to Google usb driver directory but now ADB finally recognizes my SGS (MyICS, Android 4.0.3).
Edit: Operating system Vista 64-bit
[Currently stuck in "error: device not found" while trying adb push -command. I will update if I find a workaround. Probably something to do with inf-file.]
For alternate .inf -file (optional):
Google "usb-drivers-not-working-after-flash-latest-rom-ota" and see post #12 to see alternative inf-file. Some have managed to make adb recognize the device with that file, but I have at least this far been unsuccessful.
Edit: Problem above was caused by me being stupid and trying to use push in shell, which caused phone unable to locate host system folders. I don't know if that inf file has anything to do with drivers working now, but go ahead and try it if doesn't work with the original .inf
I got my i9000 recognized using the latest drives from the Google sdk
That‘s great
http://ics.samsung-updates.com/addons/usb_driver.zip
oxidising said:
I got my i9000 recognized using the latest drives from the Google sdk
Click to expand...
Click to collapse
I tried last night didn't work for me.... (r18)
Sent from my Dell Streak using XDA
oxidising said:
I got my i9000 recognized using the latest drives from the Google sdk
Click to expand...
Click to collapse
Daha açık anlatabilir misiniz?
IWillExplain said:
http://ics.samsung-updates.com/addons/usb_driver.zip
Click to expand...
Click to collapse
... this driver actually worked for me...!
(Tiramisu ICS)
USB option has been lost in my galaxy s
RazorNova said:
Using Google USB drivers finally worked for me. They can be optionally installed with Android SDK using SDK manager (extras). After installation drivers can be found in <sdk>\extras\google\usb_driver.
Just follow the instructions in the first post to find your device from device manager with exclamation mark. Need at least one reboot to work and I also redirected the driver installation process to Google usb driver directory but now ADB finally recognizes my SGS (MyICS, Android 4.0.3).
Edit: Operating system Vista 64-bit
[Currently stuck in "error: device not found" while trying adb push -command. I will update if I find a workaround. Probably something to do with inf-file.]
For alternate .inf -file (optional):
Google "usb-drivers-not-working-after-flash-latest-rom-ota" and see post #12 to see alternative inf-file. Some have managed to make adb recognize the device with that file, but I have at least this far been unsuccessful.
Edit: Problem above was caused by me being stupid and trying to use push in shell, which caused phone unable to locate host system folders. I don't know if that inf file has anything to do with drivers working now, but go ahead and try it if doesn't work with the original .inf
Click to expand...
Click to collapse
What should i do after instaling SDK
IWillExplain said:
http://ics.samsung-updates.com/addons/usb_driver.zip
Click to expand...
Click to collapse
This worked for me
The very important thing is that newest Google USB driver is in
Code:
[B]<android-sdk>/extras/google/usb_driver/[/B]
location, not in
Code:
<android-sdk>/usb_driver
It really makes the difference !
these drivers only worked once...
all the other times killing and starting over adb i was getting error messages like "device not found" and "protocol fault" even though adb devices was listing the device online.
apparently i connected the phone to another USB3 port on my pc (front panel) and that was it!! it now works every time i type adb shell or adb devices.i no longer get any error messages.rather weird
anyway..i also wanted to be up to date with everything so i uninstalled all related software like the older java 6 jdk, Android SDK and the drivers mentioned above.
i followed the procedure below and installed all the latest packages:
latest java 7u5 JDK, the latest Android SDK (nstaller_r20.0.1-windows.exe) then ran sdk-manager and loaded http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver google USB drivers rev 6. then installed these drives so i got the ADB composite interface on my device manager and it all works fine now.
I recenelty installed latest ICS , and SDK recognizes my phone as ACER ADB , when I'm pretty sure its a Samsung I9000 . I tried uninstalling the ACER ADB and install the one that the guy posted in the first post , and it didn't work , it said this driver is not compatible , oddly it reinstalled ACER ADB though. I can't even uninstall it at all , I removed all my Samsung drivers , and everything else I installed for Samsung , and its still there , I even tried removing the GOOGLE USB drivers , still there.
Neendless to say that the phone doesnt connect to the PC at all even though it says everything is alright. For example i got ths gPAD app , which uses the USB with Debugging to turn the phone into a mouse , but it says its not connected even though it is.
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.