Anyone help solve my driver issues.

[Guest cmberry20]

Firstly, I think i've got the drivers sorted when the phone is switched on.

Using Win7 64bit I get this when the phone is on:

However, when the phone is switched off, all i get is an 'Unknown Device' in my USB list in Device Manager.

No matter what driver i try i cant get it to install.

I get this:

Does anyone know how to fix this or is this normal? I thought the phone needed to be off in order to flash a custom ROM on to it but cant while the drivers are working!

Cheers

[Guest rjm2k]

Firstly, I think i've got the drivers sorted when the phone is switched on.

Using Win7 64bit I get this when the phone is on:

However, when the phone is switched off, all i get is an 'Unknown Device' in my USB list in Device Manager.

No matter what driver i try i cant get it to install.

I get this:

Does anyone know how to fix this or is this normal? I thought the phone needed to be off in order to flash a custom ROM on to it but cant while the drivers are working!

Cheers

What do you mean the phone is off?

If you want to use fastboot to flash then the official zte driver doesn't include the required setup so either download one of the other drivers or try the following, replace c:\system\inf\oem44.inf with the attached file then windows should recognise it, if not then use device manager to change the driver to zte single adb interface.

There is a very brief device not recognised when rebooting, but I don't know what that is, maybe kernel boot debugging?

;/*++

;

;Abstract:

; Installation inf for the Android USB Bulk device

;

;--*/

[Version]

Signature="$WINDOWS NT$"

Class=USB

ClassGuid={F72FE0D4-CBCB-407d-8814-9ED673D0DD6B}

Provider=%GOOG%

DriverVer=06/25/2009,1.0.0010.00001

CatalogFile.NTx86=androidusb86.cat

CatalogFile.NTamd64=androidusb64.cat

; ================= Class section =====================

[ClassInstall32]

Addreg=AndroidUsbClassReg

[AndroidUsbClassReg]

HKR,,,0,%ClassName%

HKR,,Icon,,-5

[DestinationDirs]

DefaultDestDir = 12

; ================= Device section =====================

[Manufacturer]

%MfgName%=Google,NTx86,NTamd64

[Google]

%USB\VID_18D1&PID_D00D.DeviceDescRelease%=androidusb.Dev, USB\VID_18D1&PID_D00D

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

%USB\VID_19D2&PID_1351&MI_01.DeviceDescRelease%=androidusb.Dev, USB\VID_19D2&PID_1351&MI_01

%USB\VID_19D2&PID_1352.DeviceDescRelease%=androidusb.Dev, USB\VID_19D2&PID_1352

%USB\VID_19D2&PID_1354&MI_02.DeviceDescRelease%=androidusb.Dev, USB\VID_19D2&PID_1354&MI_02

[Google.NTx86]

%USB\VID_18D1&PID_D00D.DeviceDescRelease%=androidusb.Dev, USB\VID_18D1&PID_D00D

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

%USB\VID_19D2&PID_1351&MI_01.DeviceDescRelease%=androidusb.Dev, USB\VID_19D2&PID_1351&MI_01

%USB\VID_19D2&PID_1352.DeviceDescRelease%=androidusb.Dev, USB\VID_19D2&PID_1352

%USB\VID_19D2&PID_1354&MI_02.DeviceDescRelease%=androidusb.Dev, USB\VID_19D2&PID_1354&MI_02

[Google.NTamd64]

%USB\VID_18D1&PID_D00D.DeviceDescRelease%=androidusb.Dev, USB\VID_18D1&PID_D00D

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

%USB\VID_19D2&PID_1351&MI_01.DeviceDescRelease%=androidusb.Dev, USB\VID_19D2&PID_1351&MI_01

%USB\VID_19D2&PID_1352.DeviceDescRelease%=androidusb.Dev, USB\VID_19D2&PID_1352

%USB\VID_19D2&PID_1354&MI_02.DeviceDescRelease%=androidusb.Dev, USB\VID_19D2&PID_1354&MI_02

[androidusb.Dev.NT]

CopyFiles=androidusb.Files.Ext

[androidusb.Dev.NT.Services]

Addservice = androidusb, 0x00000002, androidusb.AddService

[androidusb.AddService]

DisplayName = %androidusb.SvcDesc%

ServiceType = 1 ; SERVICE_KERNEL_DRIVER

StartType = 3 ; SERVICE_DEMAND_START

ErrorControl = 1 ; SERVICE_ERROR_NORMAL

ServiceBinary = %10%\System32\Drivers\androidusb.sys

AddReg = androidusb.AddReg

LoadOrderGroup = Base

[androidusb.AddReg]

HKR,"Parameters","MaximumTransferSize",0x10001,4096

HKR,"Parameters","DebugLevel",0x10001,2

HKR, Parameters\Wdf, VerboseOn, 0x00010001, 1

HKR, Parameters\Wdf, VerifierOn, 0x00010001, 1

HKR, Parameters\Wdf, DbgBreakOnError, 0x00010001, 1

[androidusb.Files.Ext]

androidusb.sys

[sourceDisksNames]

1=%Disk_Description%,,,

[sourceDisksFiles]

androidusb.sys = 1

;-------------- WDF Coinstaller installation

[DestinationDirs]

CoInstaller_CopyFiles = 11

[androidusb.Dev.NT.CoInstallers]

AddReg=CoInstaller_AddReg

CopyFiles=CoInstaller_CopyFiles

[CoInstaller_CopyFiles]

wdfcoinstaller01005.dll

[sourceDisksFiles]

wdfcoinstaller01005.dll=1 ; make sure the number matches with SourceDisksNames

[CoInstaller_AddReg]

HKR,,CoInstallers32,0x00010000, "wdfcoinstaller01005.dll,WdfCoInstaller"

[androidusb.Dev.NT.Wdf]

KmdfService = androidusb, androidusb_wdfsect

[androidusb_wdfsect]

KmdfLibraryVersion = 1.5

;---------------------------------------------------------------;

[strings]

GOOG = "Google, Inc"

MfgName = "Google, Inc"

Disk_Description= "ADB Interface Installation Disk"

androidusb.SvcDesc = "ADB Interface Driver"

ClassName = "ADB Interface"

USB\VID_19D2&PID_1350&MI_04.DeviceDescRelease = "ZTE Kernel Debug Interface"

USB\VID_19D2&PID_1351&MI_01.DeviceDescRelease = "ZTE Composite ADB Interface"

USB\VID_19D2&PID_1352.DeviceDescRelease = "ZTE Single ADB Interface"

USB\VID_19D2&PID_1354&MI_02.DeviceDescRelease = "ZTE Composite ADB Interface"

USB\VID_18D1&PID_D00D.DeviceDescRelease = "ZTE Single ADB Interface"

Edited November 16, 2010 by rjm2k

[Guest cmberry20]

^^ :rolleyes:

Lost me at 'Replace with attached file'

& the rest of of the post might as well have been written in Latin!!!

When I mean 'Off' I mean the phoned switched off - ie. Not switched on! When i plug the phone into the PC via USB I get 'Unknown Device' - is this normal??

If its not, how do i fix it. A noobs guide please!!

Edited November 16, 2010 by cmberry20

[Guest Flumpster]

Edit.. misread question sorry

Edited November 16, 2010 by Flumpster

[Guest cmberry20]

Anyone??

Is this normal or does it need sorting in order to flash a custom ROM?

I'm dying to try out the lastest Froyo build - please help!!!

[Guest goatee]

Anyone??

Is this normal or does it need sorting in order to flash a custom ROM?

I'm dying to try out the lastest Froyo build - please help!!!

Ok, have you rooted your phone and installed Clockworkmod? When I did my phone, I ignored what devices Windows saw - all I cared about was that adb works - and it should on yours. If your phone isn't rooted and doesn't have Clockworkmod installed, then try the steps listed in the posts, and if that doesn't work, come back with the errors :rolleyes:.

[Guest cobalt01]

Have you tried this thread? worked for me when i had problems on Win 7 x64. Just remember to uninstall drivers that are currently there first.