Do I need special drivers or something that I'm missing? :/
On Win 7, the way I found is to make a copy of "...\sdk\extras\google\usb_driver" on desktop or elsewhere, then edit file "android_winusb.inf" to add Gear Live description :
First open Device Manager and right click "Gear Live" in "Other devices" and choose Properties. In "Details" folder, choose "material identification numbers" and copy the second one (My os is in french, so i try to translate names correctly...). The number to copy must look like (or be): "USB\VID_18D1&PID_D002"
Then edit "android_winusb.inf" (the one in the folder previously copied, in case of...) and add under "[Google.NTx86]", at the end, these lines :
;Gear Live
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D002
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D002&MI_01
Be careful to change "USB\VID_18D1&PID_D002" with your material number if needed (but let "&MI_01" on second line.
Make the same under [Google.NTamd64].
Now you can go back to "device manager", right click on "Gear Live", choose "Update driver software" then "Browse my computer..." and choose the folder where you just edit "android_winusb.inf".
---------- Post added at 09:11 PM ---------- Previous post was at 09:11 PM ----------
Quoted from http://stackoverflow.com/questions/24583354/adb-doesnt-recognize-samsung-gear-live-or-lg-g-watch
I couldn't get this method to work on win 8.1 any other ideas i keep getting the "hash for the file is not present in the specified catalog file" error ?Thanks
Related
I am trying to fix the WiFi on my Captivate. This thread here tells how to do it. Unfortunately when I run DDMS I get the error "Failed to get the adb version: Cannot run program "adb": CreateProcess error=2, The system cannot find the file specified." I have tried installing the SDK on both a Windows 7 64-bit and XP 32-bit machine. I get the same error on both machines. I have tried both the generic Galaxy S drivers and the Captivate drivers. Any suggestions? Here are the instructions I've followed in case you don't want to read the other thread:
1. Install the SDK -> Android SDK | Android Developers
(make sure the <SDK>/tools path is added to the windows path variable. My Computer -> Properties -> Advanced -> Environment Variables -> System variable -> add the SDK path at the end of Path variable )
2. On your phone, please enable (tick mark) "USB debugging" under "Settings" -> "Applications" -> "Development"
3. Connect your phone using USB to PC/Laptop. Close phone manager application if it comes up on the PC.
4. Run "ddms.bat" from <SDK>/tools directory. The DDMS application will come up and it should readily connect to your phone. (in the main screen, under Name, you should find the phone ID and SW ver. no.)
5. Go to menu Device -> File Explorer. New window will come up.
6. Here go to data -> wifi directory. You will see a file bcm_supp.conf.
7. Though it is not possible to read this file, you should be able to delete it. (at least I could delete it). You can delete the file by selecting it and then pressing red "-" on top left of the window.
Thanks!
Post in q and a.
sent from my craaazy fast cappy running di11igaf v2.5 at 1280mhz!!!
silverslotcar said:
Post in q and a.
sent from my craaazy fast cappy running di11igaf v2.5 at 1280mhz!!!
Click to expand...
Click to collapse
Yes, Q&A would be the proper location for this thread.
Sent from my GT-I9000 using XDA App
Ok, sorry, although I just figured out the problem. The Path should have the platform-tools directory instead of the tools directory because that's where adb is located. I corrected that and it loaded right up. Unfortunately, when I click on the + sign for the Data folder it doesn't show me anything Guess I'm going to have to do a factory reset after all.
automagrt said:
I am trying to fix the WiFi on my Captivate. This thread here tells how to do it. Unfortunately when I run DDMS I get the error "Failed to get the adb version: Cannot run program "adb": CreateProcess error=2, The system cannot find the file specified." I have tried installing the SDK on both a Windows 7 64-bit and XP 32-bit machine. I get the same error on both machines. I have tried both the generic Galaxy S drivers and the Captivate drivers. Any suggestions? Here are the instructions I've followed in case you don't want to read the other thread:
1. Install the SDK -> Android SDK | Android Developers
(make sure the <SDK>/tools path is added to the windows path variable. My Computer -> Properties -> Advanced -> Environment Variables -> System variable -> add the SDK path at the end of Path variable )
2. On your phone, please enable (tick mark) "USB debugging" under "Settings" -> "Applications" -> "Development"
3. Connect your phone using USB to PC/Laptop. Close phone manager application if it comes up on the PC.
4. Run "ddms.bat" from <SDK>/tools directory. The DDMS application will come up and it should readily connect to your phone. (in the main screen, under Name, you should find the phone ID and SW ver. no.)
5. Go to menu Device -> File Explorer. New window will come up.
6. Here go to data -> wifi directory. You will see a file bcm_supp.conf.
7. Though it is not possible to read this file, you should be able to delete it. (at least I could delete it). You can delete the file by selecting it and then pressing red "-" on top left of the window.
Thanks!
Click to expand...
Click to collapse
Hi,
I am going crazy with this crap, I am not impressed how google put this **** together.
I can see you managed to fix the issue of ddms not finding adb but I didnt. Can you please explain in more details? I searched everywhere over the internet but everybody just says "add the path". Fine. Then what....?
I added a new path in the environmental system variables called "SDK" and points to:"C:\program files\Android\android-sdk-windows\platform tools\. Still no joy. What am I doing wrong?
thanks
Did you reboot after adding the path?
And I didn't realize that Google had changed the SDK path to "platform-tools" with their latest release. Just plain dumb imo as folks have been so used to it being in just the "tools" location.
How to get ADB to work with Adam by detecting in Windows properly.
Hello I wanted to document a way to get this going so hopefully this helps anyone interested in using ADB with their Adams since the original tutorial seems to lack some important "how-to" parts.
Another thing.. I am only trying to help and add to the adam experience.. I am not a teacher or anything so if you are unsure about a step STOP and go do some research.. this is for someone who already has a general knowledge and to assist those to are trying to learn this.. its not a substitute for learning it yourself.
----------
Here are the steps that you need to follow in order to enable these drivers:
You must have Android SDK installed before you can proceed!!
If you don’t have it already, proceed to download here and you can see a ADB guide found here.
Make sure you download the Google USB Driver Package as well.
Open the google-usb_driver folder that you will find inside your Android SDK folder.
Open the android_winusb.inf file in notepad or any text editor to edit it.
Add these lines under [Google.NTx86] or [Google.NTamd64] depending on whether you are using 32 bit or 64 bit Windows. If unsure, it is safe to add these under both these sections.
Code:
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
Don’t edit or replace any other text that is already there; just add these new lines and save the file. You can add them right before the
Code:
; HTC Dream
To be able to use ADB and other SDK tools with your device, you can proceed as follows:
On your tablet, go to Menu > Settings > Applications > Development and enable ‘USB Debugging’.
Connect your tablet to your PC via USB. You will get a notification that some drivers were not installed, which is OK for now.
Go to device manager and Identify your device from the list, right-click it and click ‘Update Driver Software..’.
Choose to browse your computer for driver software and then select to pick from a list device drivers on your computer.
Choose to view all devices and click ‘Have Disk…’.
Browse to the google-usb_driver folder inside your Android SDK folder and select the android_winusb.inf file.
If you get any warnings prompts telling you that the driver might not be compatible, just choose to continue installing.
Once the drivers have been installed, you should be able to use ADB with your device.
You will want to connect your device via usb and make sure usb debugging is on. (Settings, applications, development, usb debugging CHECKED!!)
To confirm that your device is recognized, launch a Command Prompt window and enter these commands:
Code:
adb kill-server
adb start-server
adb devices
If you see your device name or a few numbers as the output under the list of devices, your device is now recognized by ADB.
Happy Developing!
--------------------------------------
My Notion Ink Adam Videos
ADB / QtADB
Then there's the easy way .... http://forum.xda-developers.com/showthread.php?t=1009982
stewarta said:
Then there's the easy way .... http://forum.xda-developers.com/showthread.php?t=1009982
Click to expand...
Click to collapse
Well I took a look at your "easier way" and its exactly what I explain to do in my tutorial but maybe others will enjoy your wording better, thank you for your input and for sharing.
See title. Using Win7, 64-bit. I've tried with the most current version, as well as the revision 3. I go to device manager, choose "Dell Streak7" (under "Other Devices"), choose "Update Driver Software", point it to the correct folder, and it tells me there are no available driver files there. Streak is in debug mode, no driver is currently installed. Can't root until I can get this working, can someone please help me?
Same for me. It seems there's no way to install usb drivers. In windows xp everything's gone ok, but in windows 7 64 bit no way to install. I am win7 64 bit and i need help ((
Have the DS7 plugged in to usb. Copy the Drivers.zip from internal sd card to win 7 desktop, unzip, in desktop manager browse to ADB-V1POP25 folder. Update driver.
Yes all steps have been done...but the result is always the same: when I search the driver and I specify the folder windows doesn't find any driver to update
Ok resolved. I put the ENTIRE driver folder contained inside the dell on my desktop not only the win7 64 bit folder but the full Drivers folder. So I made the procedure fir recognize the driver and I've searched inside the entire folder and.. it works now *-*
Ahh, your win 7pc is deciding whats best for drivers. Its something that you have to disable in admin settings. Google this: "addictive tips install drivers manually windows 7" and read the instructions.
Addictive tips is the site name.
How that enlightens you.
Its okay now win7 now recognize my dell streak 7 *-*
drivers.zip
I've searched XDA for a couple hours now and my 7 is stuck in CMR. Seems I can't do a factory restore until I can round up the drivers folder. I've even searched the Internet for a system dump and can't find one that actually works.. all the links are dead. Do you have the ability to upload the drivers folder even as a zip file if necessary? I'm really hoping this 7 can come back to life. Thanks in advance!!
It's a big package that you can find on dell.com official website in the drivers section. For now i have my notebook in assistence so i write directly from my streak 7 so i can't upload the folder. Try also with the search button on these forums.
Drivers please!?!?!
My streak will not power on or anything. All it does is light up the 3 soft keys on the right so I cant get the drivers off the sd. Can someone PLEASE post up the drivers off theirs. I'm trying everything to get them to install from the dell site but im having no luck. I need to get this fixed asap
This is how i solved my issue. There might be an easier way to do it but this is what worked for me.
Install Android sdk tools( would post a link but im too new)
once installed it will ask if you want to install a bunch of packages. Click Cancel.
In the android sdk and avd manager select "available packages" on the left hand side.
then you want to download
"Android SDK Tools, revision 11"
"Android SDK Platform-tools, revision 5"
"SDK Platform Android 2.2, API 8, revision 2"
"Google USB Driver PAckage, revison 4"
After all that is installed, find the root folder for which you installed the Android SDK software. Navigate through "Android-sdk>extras>google>usb_driver" In the usb_driver folder there is a setup information file called "android_winusb" Open that up in note pad and modify it like so (make a backup of the file just incase)
Under [Google.NTx86] add the following
;Dell Streak 7
%SingleAdbInterface% = USB_Install, USB\VID_413C&PID_B104
%CompositeAdbInterface% = USB_Install, USB\VID_413C&PID_B104&MI_01
Under [Google.NTamd64] add the same
;Dell Streak 7
%SingleAdbInterface% = USB_Install, USB\VID_413C&PID_B104
%CompositeAdbInterface% = USB_Install, USB\VID_413C&PID_B104&MI_01
Click to expand...
Click to collapse
Now save the file and try to update your Streak 7 by right clicking computer and selecting "Manage" then you should see your Dell Streak 7 listed and right click that and select update drivers. Select to browse for the update on your computer then navigate back to "Android-sdk>extras>google>usb_driver" Select just the "usb_driver" folder so it goes through all the subfolders in it and bam your device drivers should be installed and updated. This worked for me. Hopefully it will work for you too.
Windows - Dell Streak Drivers
...Chill guys
DS7 Drivers
If these don't work, and as a last resort, try installing the NERO software off the dell site!
Here
If that doesn't work, I ain't got a Scooby Doo
Mirroring the Drivers.zip file because you shouldn't ever use MegaUpload.
Where do you get off making me wait 41 seconds to download a file and then popping up an adult ad. Piss off MegaUpload.
http://android.schneenet.com/downloads/streak7/Drivers.zip
So I've been figthing this battle for the last couple of days... and no matter what drivers I installed (and trust me I've installed everything from the latest google drivers to Khoush's Universal drivers) I could never for the life of me get the Nexus 6 to show up during recovery - and hence couldn't sideload the 5.1 OTA. Mind you I'm completely stock - boatloader, recovery, kernel and all....
I Knew it was a driver issue - so I went back to the drawing board. Here's what I did and you should try.
Step 1 : Assuming you have SDK installed/Minimal ADB fastboot installed , download the latest usb drivers.
Code:
https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
Unzip and remember location.
Step 2 : Unplug your phone and Use usbdeview (google USBdeview) to uninstall all existing devices that say something like
Code:
nexus 6
android
google
Step 3 : With USB debugging enabled and MTP on , plug your phone in... If it installs drivers - dont worry. Go to device manager - look for anything that says Andoid/ADB composite device or MPT/Nexus. Right click and select Uninstall. Check Delete driver software for this device and press OK. You may need a restart, if windows tells you to. Either way unplug your phone.
Step 4: Plug your phone in. Let it try to figure out devices/drivers. Then go to Device manager. The Nexus should have an exclamation on it. Right click and go to properties-->Details. Select Hardware Id's from the dropdown. There should be one or two. Either one is valid. Now open the USB drivers folder you unzipped earlier and open the android_winusb.inf file with notepad (usually double click should open it).
If you're on a 32 bit operating system - scroll the [Google.NTx86] section.
If you're on a 64bit OS (like most on Windows 7/8/8.1) scroll to the [Google.NTamd64] section.
If you don't know which OS you are on - please wait for the OTA to arrive on your phone because this guide( and other guides) maybe beyond you .
Scroll down to the Google Nexus (Generic) section for your OS type. It should say something like
Code:
;Google Nexus (generic)
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_4EE0
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE2&MI_01
....
Now from device manager copy the hardware id for your device. Say its
Code:
USB\VID_18D1&PID_4EE7&MI_01
If your Hardware Id (atleast one) isnt listed in the CompositeAdbInterface list on the driver file then insert a new line. Like below.
Code:
;Google Nexus (generic)
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_4EE0
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE2&MI_01
....
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE7&MI_01 <----New line
Save the driver file. Now open device manager again and Right Click the nexus device... Update Device Driver --> Browse my computer.. --> Specify the newly modifed USB file.--> press Next to completion. If you are prompted saying device is unsigned... ignore it.
Step 5 : Open command prompt /cmd (Start-->search for cmd). Browse to the ADB location. Then type
Code:
adb devices
It should show you the a device. (You may have to allow adb usage on your phone from that specific computer - should popup on your phone when connected). Next type
Code:
adb reboot bootloader
Your phone will automatically reboot into the bootloader.If you see a device listed under Android Bootloader Interface of If you see a new nexus device in your device manager then Uninstall the device while deleting driver. If you dont see a device - use USBdebiew to uninstall devices. Right Click on the computer name in device manager and click scan for hardware changes. You now have a device showing up with Exclamation. Now add the hardware ID for this device to the usb file. Make sure you add it under CompositeAdbInterface and not SingleBootLoaderInterface. If your device is listed under SingleBootLoaderInterface - Then use a semi-colon ( ; ) at the beggining of the line to comment it out... and then add the Hardware Id to the CompositeAdbInterface. Save and update driver.
Now choose recovery from the options. At this point unplug your phone. Now hold the Power button on your phone for about 5 seconds and then press Volume UP. It should take you to the recovery options screen. Use your volume button to move to "apply update from ADB" and press Power Button to select. It will take you to another screen saying its ready for adb sideloading.
Now Plug your phone in. If you see a new nexus device in your device manager then Uninstall the device while deleting driver. If you dont see a device - use USBdebiew to uninstall devices. You now have a device showing up with Exclamation. Now add the hardware ID for this device to the usb file. Make sure you add it under CompositeAdbInterface and not SingleBootLoaderInterface. If your device is listed under SingleBootLoaderInterface - Then use a semi-colon ( ; ) at the beginning of the line to comment it out... and then add the Hardware Id to the CompositeAdbInterface. Save and update driver.
Go to the command shell and look for adb devices again. It should now list your Device.
Sorry about providing links as code : Dont have enough post apparently to directly link stuff.
Happy sideloading!!!
i DID WHAT YOU SAID NOW DRIVER INSTALL SAYS THE HASH FOR THE FILE IS NOT PRESENT IN THE SPECIFIED CATALOG FILE
This should be stickied, I just searched google for this and found this exact post on Reddit and was just about to make a new thread on here referencing it.
Hi,
I am in internship and I develop on Android glasses : I have Epson Moverio BT 200 model. I am at windows 7
My problem is that I don't manage to install driver to connect glasses to computer.
I follow this tutorial provided by Epson (I cannot posted the link => I am a new...)
I am blocked at second last step, during driver installation. I obtain this error message :
"Windows could'nt install your embt2.
Windows has found none driver for your peripheral device. "
I have already uninstalled google's usb driver (whit sdk manager), and next reinstalled, restarted computer, glasses, witout resilt.
The path for driver that I chose is : "C:\Program Files\Android\android-sdk\extras\google\usb_driver".
Do you have a solution, please ?
P.S : sorry for the faults.
Installation of Moverio BT 200
Hey Le-E
Epson Moverio BT 200 has not been certified with Google, therefore, you can't install it as ADB Andriod interface yet or get any app for it from Google play store directly.
Cheers
Hi Farid_Ashabi,
thank you for your response.
However, I follow a document provided by Epson, if Moverio bt 200 was not certified with google, why have they done this document ?
The document : tech.moverio.epson.com/en/life/bt-200/pdf/bt200_adb1505a_en.pdf (add https:// at beginning) (It last updating is 05/21/2015).
Are you sure ?
Installation driver Moverio BT 200 Windows 7
Hey Le-E,
I have looked at the document, it looks like work around......this document tell you how to hack the INF and add Moverio's VID\PID so the device could get recognized as Andriod ADB Interface. I have worked with Vuzix M100 and they have certified Google driver and no such hassle as installing Andriod Studio.
Cheers
Farid
Hi Farid_Ashabi,
I see. I will continue to search why that doens't work.
Thank you for your time !
keep it up !
Hi,
I resolved my problem.
For others persons with the problem, it is neccessary to add next lines twice in file "android_winsub.inf" :
";WS2 - MTP
%SingleAdbInterface% = USB_Install, USB\VID_04B8&PID_0C06
%CompositeAdbInterface% = USB_Install, USB\0VID_04B8&PID_0C06&MI_01
;WS2 - PTP
%SingleAdbInterface% = USB_Install, USB\VID_04B8&PID_0C07
%CompositeAdbInterface% = USB_Install, USB\VID_04B8&PID_0C07&MI_01"
(see the tuto tech.moverio.epson.com/en/life/bt-200/pdf/bt200_adb1505a_en.pdf (add https:// at beginning)).
you had to add this lines in the sections "[Google.NTx86]" and "[Google.NTamd64]".
And it finishes.
good luck =).
Hey Le-E,
I was able to get the BT-200 to show up as ADB interface with INF changes, but when I Execute “adb devices” to confirm name of device (0123456789ABCDEF) ......no devices is listed had no luck (as documents says, I tried is multiple time, still the same).....I'm running it under Windows 7 Ult. 64 bit......can you tell me your BT-200's Andriod version as well as your OS?
Cheers,
Farid
Hi Farid_Ashabi,
I am in Windows 7 32 bits.
BT-200's Andriod version is 4.0.4.
Have you suceeded to intsall driver ?
Hi Le-E
My specs are: Anroid 4.0.4 Kernel Version 3.0.21-00003-OMAP Build number: D1.1.2
Yes, driver have been installed and my BT-200 comes in as Android ADB Interface in device manager, but when I run the "adb device" in command prompt, I should see my device listed, but I don't.............if listed, I can install few APK files manually......no luck yet
Hi Farid_Ashabi,
sorry, I was with friends this weekend.
I have exactly same version for Kernel and Build number. I do not understand why this does not work for you...
Do you have tryed with an other USB cable ?