Tried Win7 drivers - still can't use ADB or DDMS

[Guest blork]

I've tried the drivers in this thread and the ZTE ones in the wiki but I still can't use ADB with my phone.

It's pretty annoying because I'm an app developer and I'd like to use my San Francisco for testing, but Eclipse won't detect it at all and running adb shell just gets me "error: device not found". Doesn't work in bootloader mode either.

Any suggestions? I had a Pulse before and I remember I had a few problems setting it up to begin with but it was fine after that.

[Guest jsplace]

I've tried the drivers in this thread and the ZTE ones in the wiki but I still can't use ADB with my phone.

It's pretty annoying because I'm an app developer and I'd like to use my San Francisco for testing, but Eclipse won't detect it at all and running adb shell just gets me "error: device not found". Doesn't work in bootloader mode either.

Any suggestions? I had a Pulse before and I remember I had a few problems setting it up to begin with but it was fine after that.

Maybe a silly question so forgive me.

Do you have USB debugging enabled?

[Guest blork]

Maybe a silly question so forgive me.

Do you have USB debugging enabled?

Yep :) It's ticked in the options and I get the notification about it whenever I connect with USB.

[Guest blork]

I managed to fix it by installing "Android SDK Tools, revision 7" through Eclipse. Already had the previous version, so don't know why the San Fran needed the newer one. Only problem - screenshots are upside down!

[Guest jsplace]

I managed to fix it by installing "Android SDK Tools, revision 7" through Eclipse. Already had the previous version, so don't know why the San Fran needed the newer one. Only problem - screenshots are upside down!

Screenshots are upside down because the SF's screen is actually upside down :)

[Guest libretteer]

I managed to fix it by installing "Android SDK Tools, revision 7" through Eclipse. Already had the previous version, so don't know why the San Fran needed the newer one.

Thanks for mentioning this. I've just installed the Android SDK (although not the Eclipse plugin yet) and it now seems to work for me as well (Windows 7 64 bit). I think it's probably because this upgrades ADB: "adb version" now reports 1.0.26, when I was using 1.0.25 before.

[Guest jsplace]

Thanks for mentioning this. I've just installed the Android SDK (although not the Eclipse plugin yet) and it now seems to work for me as well (Windows 7 64 bit). I think it's probably because this upgrades ADB: "adb version" now reports 1.0.26, when I was using 1.0.25 before.

Hmm, If you used the drivers from the OP's "This thread" quote in post 1 then the version of ADB in there is 1.0.26.

However, I use the drivers in that file with both ADB 1.0.26 AND 1.0.20 with no problems, also I do NOT have the SDK installed at all on my Win7 64 installation just the bare drivers from that package. My SDK resides only on an XP VM.

Don't know what the problem was but glad its fixed.

[Guest rjm2k]

If you have wireless then use adb in wireless mode, download adbwireless from the market and on your pc use adb connect <ipaddress of phone> then adb shell

You can't fastboot using it but you can flash using adb anyway I think.

[Guest Brins0]

Got my Blade on Saturday, and used the same drivers I did for when I sorted my mum's HTC Desire out for adb.

• There are a pair of devices in the Windows 7 Device Manager you will see a pair of devices called "ZTE HSUSB Device". Select one of them, was the bottom on mine, go into the "Details" tab and look at the "Hardware Ids" property.
  
• There are two possible Hardware IDs you will see here:
  USB\VID_19D2&PID_1354&REV_0100&MI_00 -or- USB\VID_19D2&PID_1354&REV_0100&MI_02
  
• Notice the last number is different. If you have the one ending in "02", go to the "Driver" tab and select "Update Driver...".
  
• Then select "Browse my computer...", followed by "Let me pick...", click "Next" if you see a list of device types, then select the "Have Disk..." option.
  
• After browse to where you extracted the Android SDK v7 drivers to, and select "android_winusb.inf" from the "usb_drivers" folder. If it says they're not for this device, ignore it, we know they work...
  NOTE: You'll need to run the SDK_Manager.exe to install the SDK, this will download the drivers.
  
• In the next window, you'll see a trio of models, select the top one, "Android ADB Interface".
  
• Let it install the drivers, and then ADB will work perfectly over USB in both x86 and x64 environments. It'll appear as "P729B" in the ADB devices list.
  

Hope this helps you and others out with your problem :)

Edited October 11, 2010 by Brins0

[Guest =WBG=Cpt_Custard]

Got my Blade on Saturday, and used the same drivers I did for when I sorted my mum's HTC Desire out for adb.

• There are a pair of devices in the Windows 7 Device Manager you will see a pair of devices called "ZTE HSUSB Device". Select one of them, was the bottom on mine, go into the "Details" tab and look at the "Hardware Ids" property.
  
• There are two possible Hardware IDs you will see here:
  USB\VID_19D2&PID_1354&REV_0100&MI_00 -or- USB\VID_19D2&PID_1354&REV_0100&MI_02
  
• Notice the last number is different. If you have the one ending in "02", go to the "Driver" tab and select "Update Driver...".
  
• Then select "Browse my computer...", followed by "Let me pick...", click "Next" if you see a list of device types, then select the "Have Disk..." option.
  
• After browse to where you extracted the Android SDK v7 drivers to, and select "android_winusb.inf" from the "usb_drivers" folder. If it says they're not for this device, ignore it, we know they work...
  NOTE: You'll need to run the SDK_Manager.exe to install the SDK, this will download the drivers.
  
• In the next window, you'll see a trio of models, select the top one, "Android ADB Interface".
  
• Let it install the drivers, and then ADB will work perfectly over USB in both x86 and x64 environments. It'll appear as "P729B" in the ADB devices list.
  

Hope this helps you and others out with your problem :rolleyes:

Ive down loaded the file you linked to but in the rar file there is no usb_drivers folder.....have i done something wrong......yup i have lol thanks buddy all working fine now.

Edited November 17, 2010 by =WBG=Cpt_Custard

[Guest lankyfatrick]

not entirely related, but I continually am getting the message 'device not found' when i try and use adb on my san fran... really irritating me!

using a mac

Edited November 17, 2010 by lankyfatrick

[Guest Viper9lp]

Got my Blade on Saturday, and used the same drivers I did for when I sorted my mum's HTC Desire out for adb.

• There are a pair of devices in the Windows 7 Device Manager you will see a pair of devices called "ZTE HSUSB Device". Select one of them, was the bottom on mine, go into the "Details" tab and look at the "Hardware Ids" property.
  
• There are two possible Hardware IDs you will see here:
  USB\VID_19D2&PID_1354&REV_0100&MI_00 -or- USB\VID_19D2&PID_1354&REV_0100&MI_02
  
• Notice the last number is different. If you have the one ending in "02", go to the "Driver" tab and select "Update Driver...".
  
• Then select "Browse my computer...", followed by "Let me pick...", click "Next" if you see a list of device types, then select the "Have Disk..." option.
  
• After browse to where you extracted the Android SDK v7 drivers to, and select "android_winusb.inf" from the "usb_drivers" folder. If it says they're not for this device, ignore it, we know they work...
  NOTE: You'll need to run the SDK_Manager.exe to install the SDK, this will download the drivers.
  
• In the next window, you'll see a trio of models, select the top one, "Android ADB Interface".
  
• Let it install the drivers, and then ADB will work perfectly over USB in both x86 and x64 environments. It'll appear as "P729B" in the ADB devices list.
  

Hope this helps you and others out with your problem :)

you did discribed what to do, if the device is ending wiht "02", mine is ending with "00", so what can i do?

USB\VID_19D2&PID_1355&REV_0100&MI_00

USB\VID_19D2&PID_1355&MI_00

did already download all drivers frow this site:

google-usb_driver

usb_driver

zte_driver

any other ideas?

thanks

[Guest StevenHarperUK]

you did discribed what to do, if the device is ending wiht "02", mine is ending with "00", so what can i do?

did already download all drivers frow this site:

any other ideas?

thanks

Many users have driver/connection problems in windows XP / Vista / Windows 7 - all of the users that have tried the same procedure on an Ubuntu Live CD have had no problems.

I recommend you use an Ubuntu live CD

To do this:

• Download a 32bit 10.10 CD from
  http://www.ubuntu.com/desktop/get-ubuntu/download
  - it will be in
  .iso
  format
  
  
• Download ImgBurn from
  http://www.imgburn.com/index.php?act=download
  
  
• Burn the .iso file to a new blank CD
  
  
• Boot from the new CD (This will not change your current OS, Ubuntu runs from the CD) - You may need to change your bios boot order to look for the CD before your harddisk. In your computers bios you get to choose which drive the PC will boot from first : Modern machines have F12 or F10 to choose which drive to boot from as the machine boots.
  
  

[Guest Gerson2k]

I have the same issue wrt to Windows 7 drivers, as a alternative I'm using now ADBWireless, works a treat

Edited December 11, 2010 by Gerson2k

[Guest Harmin]

I had a lot of trouble installing the drivers for the ZTE HSUSB device which is required for ADB after flashing the new Japanese Jellyfish RLS1 ROM. The drivers were not recognized.

In the end I found the hardware ids for my ZTE HSUSB device were different from those in the android_winusb.inf file in usb_driver.zip.

I updated android_winusb.inf from:

[Google.NTamd64]

;Orange San Francisco

%SingleAdbInterface% = USB_Install, USB\VID_19D2&PID_1354&MI_00

%CompositeAdbInterface% = USB_Install, USB\VID_19D2&PID_1354&MI_02

to:

[Google.NTamd64]

;Orange San Francisco

%SingleAdbInterface% = USB_Install, USB\VID_19D2&PID_1351&MI_00

%CompositeAdbInterface% = USB_Install, USB\VID_19D2&PID_1351&MI_01

Which matches my hardware ids, and then I was able to install the drivers and adb now works fine.

Hope this helps anyone else with similar problems. See the post above for where to check your hardware ids.

Edited December 28, 2010 by Harmin

[Guest Phoenix Silver]

SDK should be version 8 not 7

[Guest ch0rlt0n]

I had a lot of trouble installing the drivers for the ZTE HSUSB device which is required for ADB after flashing the new Japanese Jellyfish RLS1 ROM. The drivers were not recognized.

In the end I found the hardware ids for my ZTE HSUSB device were different from those in the android_winusb.inf file in usb_driver.zip.

I updated android_winusb.inf from:

[Google.NTamd64]

;Orange San Francisco

%SingleAdbInterface% = USB_Install, USB\VID_19D2&PID_1354&MI_00

%CompositeAdbInterface% = USB_Install, USB\VID_19D2&PID_1354&MI_02

to:

[Google.NTamd64]

;Orange San Francisco

%SingleAdbInterface% = USB_Install, USB\VID_19D2&PID_1351&MI_00

%CompositeAdbInterface% = USB_Install, USB\VID_19D2&PID_1351&MI_01

Which matches my hardware ids, and then I was able to install the drivers and adb now works fine.

Hope this helps anyone else with similar problems. See the post above for where to check your hardware ids.

Similarly, the hardware IDs are different again for the MoDaCo 2.2 FroYo ROMs (1350 vs. 1354 or 1351). I finally got my device to appear in ADB with the following amendments to android_winusb.inf.

;Orange San Francisco

%SingleAdbInterface% = USB_Install, USB\VID_19D2&PID_1350&MI_00

%CompositeAdbInterface% = USB_Install, USB\VID_19D2&PID_1350&MI_04

%CompositeAdbInterface% = USB_Install, USB\VID_19D2&PID_1350&MI_02

%CompositeAdbInterface% = USB_Install, USB\VID_19D2&PID_1350&MI_01

%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_D00D

(both [Google.NTx86] and [Google.NTamd64] sections) This results in one "Android ADB Interface" and three "Android Composite ADB Interface" appearing in Device Manager. This is in XP as opposed to Win7, but I think the key point is to match the Hardware IDs to the ROM rather than the Windows version.

I think the MI_04 line was the key and is not needed/used/mentioned in reference to stock and other ROMs.

[Guest Acathla-]

Make sure you don't have an old version of adb sitting in your windows or system32 folders that you might be running instead of the one from the SDK folder.

I had problems but tied it down to an old adb.exe in my windows folder that once removed worked fine.

[Guest ololizoz]

Install the driver from here http://android.modaco.com/content/zte-blad...a-win7-x86-x64/ . If you have any exclamation marks on anything related to ZTE in Start -> Right click Computer -> Manage -> Device manager. If you have, right click it and choose update driver. Select the 2nd option. (I have windows in swedish so im just guessing). Then the 2nd option again (Let me choose from a list of drivers installed on the computer?) If you have 32 bits you should select 32-bit folder and so on. Then click "I have a disk"? . Then browse to C:\Program Files\ZTE 3GPhone USB Driver\Drivers\64bit\WIN7 or where you installed the driver.

[Guest Fabstock]

Hi all, I am a newbie but I was having problem with the drivers on both XP and Win 7 after applying the Froyo Rom and figured out how to fix it. Connect your phone to your PC, open your device manager and you should see 4 icons with errors - yellow exclamation [!]. Right click on the first one, select properties, then click details tab and the use drop down menu in property field to select Hardware Ids.

Next open the folder that your drivers for your phone is in and open the first file ending in .ini with Notepad. Modify anything relating to ZTE to what is shown in the Hardware Ids field.

E.g.1

%ZTE15010% = Modem2, USB\VID_19D2&PID_1350&MI_00

E.g 2

[Manufacturer]

%ZTE% = QcomSerialPort, NTia64, NTamd64

[sourceDisksNames]

1000 = %ZTESrcDisk%,"",,

[sourceDisksFiles]

hwusbser02.sys = 1000

[QcomSerialPort]

%HwDevice15011% = QportInstall00, USB\VID_19D2&PID_1350&MI_01

%HwDevice15014% = QportInstall00, USB\VID_19D2&PID_1354&MI_04

%HwDevice15015% = QportInstall00, USB\VID_19D2&PID_1354&MI_05

E.g. 3

; ZTE Blade 3G Phone

%USB\VID_19D2&PID_1350&MI_00.DeviceDescRelease%=androidusb.Dev, USB\VID_19D2&PID_1350&MI_00

Save them and then perform a driver update selecting 'locate and install drivers manually' then navigating to the folder with the drivers you modified. It should then install, if you get warnings, just ignore and continue.

These are the changes for my phone but yours may have different PID values. Also, there are only 3 .ini files but 4 drivers needed, 1 driver is used twice but with different settings. I am writing this from memory so not sure which, it's not too hard to work it out, I did...

I hope this helps you get your drivers working it worked for me. Please post and let me know. Good luck.

Fabs.

Edited January 27, 2011 by Fabstock

[Guest Phoenix Silver]

perhaps someone could make a .reg ?