official 2.1 adb fail - Hero, G2 Touch General

i have updated to the latest rooted official 2.1 rom, but adb isnt working, ive downloaded the new drivers from this forum, but when i try to update the drivers to the new ones, it says, windows has determined that the blah blah blah, see atached screenshot, how can i update to the latest drivers, i've tried uninstalling the drivers, then they just reintall in a blink of an eye
running windows 7 home premium x64

I think you may just be missing some steps,... let me get my lappy on to find my bookmarks,........
-------------------------------------
Sent via the XDA Tapatalk App

OK,.. Use this guide .... BTDAG's [Guide] How to Setup Correct Hero Drivers (for x86 & x64 users) ..... with drivers from here ... Pulser's ADB Drivers (Updated for new 2.1 ROM) ....
..... pay special attention to the guide here .....
6. Right click on that and choose "Update Driver Software"
7. Select "Browse my computer..." > "Let me pick from..." > "Next" > "Have Disk..." > "Browse"
Click to expand...
Click to collapse
I kept missing the "HAVE DISK" bit and it kept just skipping through. Hope that helps.

Related

steps to upgrade using vista

hi
here i m writing the steps necessory to run upgrade utility on vista. You need to do this only once.
1. install some zipping utility like WINRAR.
2. Right click on the setup file of activesync 4.5.
3. Extract activesync 4.5 on any location.
4. Run Windows Mobile Device Center and click on Connection Settings.
5. Uncheck the Allow USB Connections and click OK.
6. Run task manager and go to services tab and check the services 'Windows
Mobile-based connectivity' and Windows Mobile 2003-based connectivity'
are started. If not, click the services button at bottom and go to next pop
up page.
7. Click the service name and press the 'play' button on the top bar.
8. Start Device Manager.Expand the 'Mobile devices' section and click
the 'HTC USB Sync.
9. Right Click and Update Driver Software.
10. Click 'Browse my computer for driver software on pop up screen.
11. Click Let me pick from a list of device drivers on my computer.
12. Click Have Disk.
13. Click 'Browse', and browse to the location where you extracted the
activesync 4.5 in 3rd step.
14. Double click wceusbsh.inf.
15. Select HTC USB Sync from the list and click Next.
16. Finish the installation process.
17. Run Task Manager Then find the WMDC.EXE and click End Process.
18. Now run the update utility and done ur update.
19. when you want to start syncing normally again run Windows Mobile
Device Center enable the allow USB connection as you disabled in step 5.
It's not correct! ...if i Uncheck the Allow USB Connections the device is not present in the list ...
The drivers not recognized by Vista....
Have you a solution?
NikitaSor said:
It's not correct! ...if i Uncheck the Allow USB Connections the device is not present in the list ...
The drivers not recognized by Vista....
Have you a solution?
Click to expand...
Click to collapse
put ur phone in bootloader and cradel it u will see vista will detect it.
There are simple instructions here:
http://forum.xda-developers.com/showthread.php?t=291723&highlight=vista
Have you ever heard about the wiki?
Vista must die today!!!!
If only new users spend some time reading wiki, everything is there... When I had to upgrade using windows vista, it worked the first time... I just read and follow the step by step instruction from wiki...
Thanks, it's work!!!
Dangit, I can get these upgrades to work when I'm at work on an XP machine, but I can't for the life of me get it to work on my home Vista 64bit machines. And yes, I HAVE read the wiki, and this post, and that post and many other posts that all give the same directions.
Disabling driver signature enforcement on the 64bit driver doesn't do any good either. It gives an error trying to install the driver.
You just gotta love computers. A ton of people can get something to work, and then a person that programs for a living will come along and can't get it to work. Makes you feel like a total goober. *sigh*
Maybe I have an old XP machine gathering dust in storage somewhere. *grumble*

SGS i9000 CM7 win7 x64 drivers not working

Hi! I recently upgraded my SGS i9000 to CM7 but can't get drivers to work for adb. Everything worked fine on 2.3.3 stock rom. I tried installing every possible driver, even did `Reinstall drivers` option in Kies, also tried manual driver update, without success. Device manager just shows up yellow triangle.
Yes, USB Debugging enabled. File transfer mode works fine, only debugging isn't working.
Using:
- Windows7 x64
- Samsung Galaxy S i9000
- CM7-10112011-nightly on 2.3.5 firmware
Device manager - img542.imageshack.us/img542/4683/nodrivr.png
About phone - img683.imageshack.us/img683/8615/aboutfc.png
I have same problem. CM7 stable, win7 64bit, tested samsung drivers, android sdk drivers, nothing works.
I had the same problem, but this was the fix for me. You need googles USB driver, not Samsungs if you have CM7 installed. Open up your Device manager and find eighter an unknown device or Android Composite ADB device, chose "update driver software" and "browse my computer...". The driver is located in the adb\google\usb_driver\ folder.
Could be a good idea to chose uninstall and "delete driver software" to get rid of the samsung driver first.
Thank you so much!!! It worked lika a charm
Ah alright yeah i was havin the same problem too will try this method..im on stable cm7.1 and got a x64 windows ultimate and no drivers found for samsung galaxy s
Sent from my GT-I9000 using XDA App
hencke said:
I had the same problem, but this was the fix for me. You need googles USB driver, not Samsungs if you have CM7 installed. Open up your Device manager and find eighter an unknown device or Android Composite ADB device, chose "update driver software" and "browse my computer...". The driver is located in the adb\google\usb_driver\ folder.
Could be a good idea to chose uninstall and "delete driver software" to get rid of the samsung driver first.
Click to expand...
Click to collapse
Tried this before but no luck.
edit: I don't have that folder: adb\google\usb_driver\, but i have C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver, and when i choose that folder, windows says that device driver (unknown device) is allready up to date.
You might need to open up the SDK Manager in the adb folder and install Google USB Driver package. Not sure if it is included by default in the installed version of android sdk.
hencke said:
You might need to open up the SDK Manager in the adb folder and install Google USB Driver package. Not sure if it is included by default in the installed version of android sdk.
Click to expand...
Click to collapse
I don't have folder called "adb", SDK Manager.exe is in "C:\Program Files (x86)\Android\android-sdk".
I opened sdk manager and installed "google usb driver package rev 4", then in device manager -> unknown device i tried to update device driver and choosed dir called "C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver" but windows says that driver is allready up to date and it's still named unknown device.
In "C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver" i have these files and folders:
amd64
-NOTICE
-WdfCoInstaller01009.dll
-winusbcoinstaller2.dll
-WUDFUpdate_01009.dll
i386
-NOTICE
-WdfCoInstaller01009.dll
-winusbcoinstaller2.dll
-WUDFUpdate_01009.dll
android_winusb.inf
androidwinusb86.cat
androidwinusba64.cat
source.properties
In the update driver software dialog, where you set the folder, make sure Include subfolders is ticked. You can also try "Let me pick from a list...". Hopefully it will show Android Composite ADB interface. Else, untick "Show compatible hardware" and chose Android composite adb interface if possible.
THANKS

Can't install Windows Driver

I can't seem to get the Windows driver installed for the Evo Shift. I uninstalled the USB Mass Storage drivers for the Android phone and the phone shows up in Device Manager with the Yellow triangle, but whenever I try and update its driver and point it to the USB Driver folder from the Android SDK it says that Windows could not find driver software for the device.
Any ideas here? I did try using ADB to check for devices and nothing shows up in the list.
Thanks for the help.
ks-man said:
I can't seem to get the Windows driver installed for the Evo Shift. I uninstalled the USB Mass Storage drivers for the Android phone and the phone shows up in Device Manager with the Yellow triangle, but whenever I try and update its driver and point it to the USB Driver folder from the Android SDK it says that Windows could not find driver software for the device.
Any ideas here? I did try using ADB to check for devices and nothing shows up in the list.
Thanks for the help.
Click to expand...
Click to collapse
Did you download the right drivers from HTC?
Sent from my PG06100 using Xparent Blue Tapatalk
YoungCorruptionV2.0 said:
Did you download the right drivers from HTC?
Sent from my PG06100 using Xparent Blue Tapatalk
Click to expand...
Click to collapse
No, I've been trying to point it to the USB Drivers folder from the Android SDK. I can't seem to find the driver from HTC (or know which is the right one).
I didn't think it was HTC Sync but maybe it is...
If I remember correctly what I did (it was so long ago on windows lol), after you download the sdk from google you have to run the sdk/tools/android program to update and download the windows drivers. After that I went to device manager where the yellow triangle is and then right-click on it and select install manually instead of search online for drivers. Then click the browse button and find where in your sdk folder it downloaded the drivers to (can't remember where they are since so long ago). Select the correct drivers, there's probably more then one so you might have to mess around with trying different drivers out to get it working. Hope that helps and good luck. Or you can try the above method and try out the HTC drivers but I never used those so I can't say how to install them exactly.
Ok, I think I got it working, I guess I did need to install HTC Sync to get the driver.
I now have a device number in ADB. My phone said Couldn't find HTC Sync on the computer but I don't think that matters if the device number was in ADB, correct?
Thanks for the help.
sparksco said:
If I remember correctly what I did (it was so long ago on windows lol), after you download the sdk from google you have to run the sdk/tools/android program to update and download the windows drivers. After that I went to device manager where the yellow triangle is and then right-click on it and select install manually instead of search online for drivers. Then click the browse button and find where in your sdk folder it downloaded the drivers to (can't remember where they are since so long ago). Select the correct drivers, there's probably more then one so you might have to mess around with trying different drivers out to get it working. Hope that helps and good luck. Or you can try the above method and try out the HTC drivers but I never used those so I can't say how to install them exactly.
Click to expand...
Click to collapse
That makes sense, I never ran the program, just had it search the folder. I think I got it working though as mentioned in my post right above this one. Thanks.
You need HTC Sync and you need admin rights to install drivers on windows.
ks-man said:
Ok, I think I got it working, I guess I did need to install HTC Sync to get the driver.
I now have a device number in ADB. My phone said Couldn't find HTC Sync on the computer but I don't think that matters if the device number was in ADB, correct?
Thanks for the help.
Click to expand...
Click to collapse
Yeah your all good man, when you do adb devices and get your serial # back all is well, I had sync on my Vista pc and it wouldn't let me use HTC sync, it would just say not found, but I always just used the unrevoked EVO drivers and they hold true to this day, I've done G2s inspire and MT4GS all without new drivers
Sent from my Bulletproof_Doubleshot using Tapatalk

[USB Drivers] Galaxy S GT-I9000 (Working on ICS)

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.

Windows 10 and fastboot

So I reserved my free upgrade to Windows 10 from Windows 7. I don't know if I'll go through with the update though, since I don't know if I'll be able to install the fastboot and flashboot drivers on it. Is anyone already using the preview with the drivers installed? Not that I flash very often anymore, but it's always a good idea to have the drivers ready in case something goes wrong. Any leads/ helps?
I've been running windows 10 since a couple months and flashtool works fine. Including fastboot. No issues whatsoever.
I can vouch for that too both flashtool and fastboot function perfectly on windows 10.
Techpenguin5 said:
I can vouch for that too both flashtool and fastboot function perfectly on windows 10.
Click to expand...
Click to collapse
perfect, I have some peace of mind now Is the driver install easy enough? What were the steps?
AnrgKrshn said:
perfect, I have some peace of mind now Is the driver install easy enough? What were the steps?
Click to expand...
Click to collapse
Exactly the same as windows 8, disable driver signature enforcement and install the drivers from the flashtoll drivers file and provided you have the rest of the files not fastboot and flashtool will now function fine
how do we do this? where's the link to do this ?
matalic said:
how do we do this? where's the link to do this ?
Click to expand...
Click to collapse
just google fastboot drivers for windows 8?
Hm, if you are able to install the technical or insider preview of win10, shouldn't you be able to install fastboot doing a headstand ? Just imho
jamespmi said:
Hm, if you are able to install the technical or insider preview of win10, shouldn't you be able to install fastboot doing a headstand ? Just imho
Click to expand...
Click to collapse
I wasn't running the technical preview, was just waiting on the upgrade. I got the drivers installed on my old laptop which I had upgraded to windows 10, but now that I've bought a new laptop, I can't seem to find the driver package that just easily installed all the drivers for me. Need to find it now '
Windows 10 preview or even the official Windows 10 release, its the same process of installing the drivers. Disable signature verification.
To disable driver signature on Win10 machine:
1. Open Start > Settings
2. Go to Update & Security > Recovery
3. Under Advanced Startup select Restart Now
4. Once your computer has rebooted go to Troubleshoot > Advanced Options > Startup Settings
5. Click Restart. Finally, you will be given a list of startup settings that you can change. The one we are looking for is “7) Disable driver signature enforcement”. To choose the setting, you will need to press the F7 key.
Then PC will restart and you can install unsigned drivers without any problems.

Categories

Resources