Database Develop

Incredible adb recovery device ids

So far, I've been able to get adb in recovery 1 time, but didn't get superuser apk installed correctly, and cannot duplicate that one success to fix it.
I have the PNY 2gb microsd
Win 7 32bit
I have the first OTA update - current ver. is 1.22.605.2
I'm convinced that at least part of my problem is that I have a driver issue.
Here are the additions to android_winusb.inf that I've collected from various posts. These are also the changes that I added to the usb driver inf that I had installed when I went into recovery that 1 time:
;
;HTC Incredible
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0C94
;
;HTC Incredible
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0FF9
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0FF9&REV_0100
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0FF9
;
Here are my device ids when booting into various modes:
HTC Incredible in normal boot mode
USB\VID_0BB4&PID_0C9E&REV_0100&MI_01
USB\VID_0BB4&PID_0C9E&MI_01
HTC Incredible in normal boot mode USB COMPOSITE DEVICE
USB\VID_0C45&PID_6282&REV_0100
USB\VID_0C45&PID_6282
HTC Incredible in normal boot mode USB COMPOSITE DEVICE
USB\VID_0BB4&PID_0C9E&REV_0100
USB\VID_0BB4&PID_0C9E
HTC Incredible in normal boot mode MASS STORAGE
USB\VID_0BB4&PID_0C9E&REV_0100&MI_00
USB\VID_0BB4&PID_0C9E&MI_00
HTC Incredible in optical mouse/power bootloader mode
USB\VID_0BB4&PID_0FFF&REV_0100
USB\VID_0BB4&PID_0FFF
HTC Incredible in vol dwn/power bootloader mode
USB\VID_0BB4&PID_0C94&REV_0100
USB\VID_0BB4&PID_0C94
HTC Incredible in recovery mode
USB\VID_0BB4&PID_0FF9&REV_0100
USB\VID_0BB4&PID_0FF9
To view the device ids, boot your phone into whatever mode, plug the phone into usb, and view Device Manager. It doesn't matter if you have a driver installed or not. Right click the device (or installed driver), choose Properties, Details tab, and select Hardware IDs from the drop down. If you can't figure out if the device id is for the Android phone, choose Parent, Children, or Siblings. You'll see that some of them say AndroidPhone, while others such as USB\VID_0BB4&PID_0C9E have a string that corresponds to your individual device.
If I do not remove the following 2 files, the phone always shows up in Device Manager under Disk Drives as 2 drives, and in Universal Serial Bus Controllers as USB Mass Storage Device:
C:\Windows\inf\usbstor.inf
C:\Windows\inf\usbstor.PNF
I don't know if removing this file does anything or not:
C:\Windows\System32\drivers\USBSTOR.SYS
It seems like I need to have the correct driver installed for the correct device id, but I'm still experimenting.
I should mention that if I use:
;
;HTC Incredible
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0C94
then I cannot install any driver for adb in recovery. Device Manager always says driver not found when browsing to the edited usb driver inf.
My question is:
Are some people able to install the drivers just fine using the following inf file settings and then get adb in recovery using these hardware ids:
;
;HTC Incredible
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0C94
And are others having issues because when they are in recovery, their hardware id is:
;
;HTC Incredible
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0FF9
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0FF9&REV_0100
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0FF9
Just to reiterate: I have to install drivers using %CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0FF9&REV_0100
The other 'normal' inf settings (%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E&MI_01) that are on many, many posts will not allow me to install the usb driver.

jerrberr said:
If I do not remove the following 2 files, the phone always shows up in Device Manager under Disk Drives as 2 drives, and in Universal Serial Bus Controllers as USB Mass Storage Device:
C:\Windows\inf\usbstor.inf
C:\Windows\inf\usbstor.PNF
I don't know if removing this file does anything or not:
C:\Windows\System32\drivers\USBSTOR.SYS
I have to reboot now, so I'm gonna post this.
Click to expand...
Click to collapse
I wouldn't do this, I don't think it's your issue. You might screw more then fix with this... Guarantee you your issue is timing. ESPECIALLY if you've already got the error once.

This was after a 1/2 root where I could install root apps like lamppu and wifitether, and they worked, but others - titanium backup - could not escalate su to root privs. superuser.apk never prompted me for allowing root.
I could run adb shell after a normal boot and run as su - of course everything was locked down. unrEVOked2 flash recovery used to say device not found.
So I reloaded the androidusb drivers using both sets of inf settings collected above, I put the c:\windows\inf files that I had removed back in place. Basically got the phone back to where all of the drivers were recognized in all of the modes, including the Mass Storage, so that the phone shows as 2 disk drives.
I reformatted my pny 2gb micro to fat32 512kb blocks in the phone, deleted all the stuff that was loaded into it (4 folders) then I did the following and got it first try:
1) unplug usb unplug battery. leave sd card in. Start up a loop.bat (look at other methods)
2) put the battery back in, hold down vol- and power together. let go once it gets into hboot. let it attempt and fail at loading the img files, then use vol- to go down to boot recovery but don't let go of vol-
3) continue to hold vol- and then press power to select reboot recovery. (begin counting, use a second hand on a pc to aide) (also, I kept holding power and vol- until done with step 4)
4) wait for the scan line flicker that happens around 7-8 seconds after pressing power (on the HTC screen, you cannot miss it). Insert the USB cord just after the scan line flicker but just before the black screen.
results:
So everything except titanium backup is working. I still have my root apps and other apps as well. Now when I run titanium backup and d/l busybox, I was prompted by superuser to allow su privs, but when I run connectbot, su, whoami gives whoami: not found
I did have to reinstall wifitether to get it back up and running.
I think that now I'll try the unrEVOked2 flash recovery tool. - installed and working as well.
Any linux people know how to install/link whoami?

jerrberr said:
So I reloaded the androidusb drivers using both sets of inf settings collected above, I put the c:\windows\inf files that I had removed back in place. Basically got the phone back to where all of the drivers were recognized in all of the modes, including the Mass Storage, so that the phone shows as 2 disk drives.
I reformatted my pny 2gb micro to fat32 512kb blocks in the phone, deleted all the stuff that was loaded into it (4 folders) then I did the following and got it first try:
1) unplug usb unplug battery. leave sd card in. Start up a loop.bat (look at other methods)
2) put the battery back in, hold down vol- and power together. let go once it gets into hboot. let it attempt and fail at loading the img files, then use vol- to go down to boot recovery but don't let go of vol-
3) continue to hold vol- and then press power to select reboot recovery. (begin counting, use a second hand on a pc to aide) (also, I kept holding power and vol- until done with step 4)
4) wait for the scan line flicker that happens around 7-8 seconds after pressing power (on the HTC screen, you cannot miss it). Insert the USB cord just after the scan line flicker but just before the black screen.
results:
This was after a 1/2 root where I could install root apps like lamppu and wifitether, and they worked, but others - titanium backup - could not escalate su to root privs. superuser.apk never prompted me for allowing root.
So everything worked. I still have my root apps and other apps as well, but now when I run titanium backup and d/l busybox, I was prompted by superuser to allow su privs. unrEVOked2 flash recovery tool said device not found.
I did have to reinstall wifitether to get it back up and running.
I think that now I'll try the unrEVOked2 flash recovery tool.
Click to expand...
Click to collapse
Dude this finally did it for me. I was losing my mind trying to do this, but these exact instructions with the 2GB PNY worked perfectly. God bless you!
I think the problem you're having may be with the HBOOT drivers. I got Clockwork installed with no problem.

i too tried about 9 million times different ways and was convinced it wouldnt work. I did get into adb recovery once and messed up, and then on the next boot it didnt work i tried hours that nite to figure it out. i havent tested this solution with others but here is what i found worked the first time i got it and once i replicated it, then it worked on the first try again.
my drivers were messed up on my machine also. i used a sony laptop. win7 64 bit and pny 4gb class 4
here is how i got it to work.
1 download ubuntu desktop remix from ubuntu.com
2 use a usb flash drive, i used 1gb
3 use the usb format tool that is on the ubuntu.com walkthrough
4 this tool will place the image on the usb and check the format button to format it, this will take 15 mins or so
5 then do the exact same to your sd card.
6 basically you should have your usb flash drive and sd card configured the same
7 plug the flash drive in and boot to that
8 when it boots it will ask you if you want to live boot, do that
9 then download the sdk and adb and such
10 then use the tail method with the log messages
11 basically from here you follow the linux boot method on the forum, you dont need look
12 i had the sd card clicked out all the way into hboot
13 when you hit recovery watch the logs as soon as it disconnects then click in the sd card
14 watch the logs and once it says its connected to android phone then try the shell (again using linux method) sudo ./adb shell in terminal
15. follow unrevoked rooting process
again as i said if it doesnt work the first time, i would try the whole process over again. once i got in and then rebooted to recovery it wouldnt do it again. only seemed to work if the sd card was freshly formatted as ubuntu desktop remix. once in ubuntu you want to familarize your self with the log messages by unplugging your phone and plugging back in to see the messages its gives.

Cannot install USB ADB driver on PC for streak.

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

[Q] Android SDK tools error: device not found

I’ve got driver problem with my Incredible S. When I have the phone on normally and connect it with a USB cable it shows:
Android USB Devices / Android Composite ADB Interface
in device manager. However, when I go into fastboot USB mode it just shows
Android USB Devices / My HTC
and it won’t recognize the device with Android SDK tools.
I can run fastboot commands using the cmd prompt but when I run ADB commands I get device not found or similar messages.
I have a HTC One S phone and in fastboot mode it shows correctly
Android USB Devices / Android Composite ADB Interface and it works with no problem.
I have tried uninstalling / reinstalling both Android SDK tools v 21.1 using SDK manager and HTC Sync. I have uninstalled / re-installed the Google USB driver.
Tried entering this in android_winusb.inf file at the end of the [Google.NTamd64] section.
;HTC Incredible S
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0FF0
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0FF0&REV_0100
with no luck.
Also HTC Sync doesn’t seem to recognize the device either. I am running Windows 7 64 bit.
Does anyone know of a fix?

Quills88 said:
I’ve got driver problem with my Incredible S. When I have the phone on normally and connect it with a USB cable it shows:
Android USB Devices / Android Composite ADB Interface
in device manager. However, when I go into fastboot USB mode it just shows
Android USB Devices / My HTC
and it won’t recognize the device with Android SDK tools.
I can run fastboot commands using the cmd prompt but when I run ADB commands I get device not found or similar messages.
I have a HTC One S phone and in fastboot mode it shows correctly
Android USB Devices / Android Composite ADB Interface and it works with no problem.
I have tried uninstalling / reinstalling both Android SDK tools v 21.1 using SDK manager and HTC Sync. I have uninstalled / re-installed the Google USB driver.
Tried entering this in android_winusb.inf file at the end of the [Google.NTamd64] section.
;HTC Incredible S
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0FF0
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0FF0&REV_0100
with no luck.
Also HTC Sync doesn’t seem to recognize the device either. I am running Windows 7 64 bit.
Does anyone know of a fix?
Click to expand...
Click to collapse
Try installing the latest version of HTC Sync. It will install the most up to date drivers which are compatible with Windows 7 X64

Drivers
I've done that a few times. Perhaps because I have an AMD 64 bit the drivers don't work. It does seem like it a driver problem.

Nexus 6 not detected during recovery/sideloading? Try this

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.

[Q] Installation driver Moverio BT 200 Windows 7

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 ?