128 replies to this topic

[Nozz]

xiaoyaoswim, on 07 December 2011 - 01:47 PM, said:

When the Found New Hardware Wizard appeared, you should install the driver manually, or perhaps through Windows Updates.

Now you need to run install-recovery-windows.bat again. As soon as you get stuck in ""waiting for device" find a unknown device in device manager(if you cannot find it, try to Scan for New Hardware), and then follow the instruction in the frist post to install the Google SDK driver. Remember to download the android_winusb.inf in attachment and overwrite the original one since you are using Windows XP.

Thank you so much. Looks to have worked perfectly with XP. Now let's get a ROM added and see how that looks!

[Coffer52]

Hi guys, I've just moved from OSF this device and like many others I have lost hours trying to connect to the phone. I'm getting the same problem as most failed to find device waiting for device and the green andriod screen. Never had these problems with the OSF!!!

[Skate Away]

Coffer52, on 20 December 2011 - 07:31 PM, said:

Hi guys, I've just moved from OSF this device and like many others I have lost hours trying to connect to the phone. I'm getting the same problem as most failed to find device waiting for device and the green andriod screen. Never had these problems with the OSF!!!

I bet it won't take you as many hours as it took me.....

[Coffer52]

Skate Away, on 20 December 2011 - 07:32 PM, said:

I bet it won't take you as many hours as it took me.....

Today is a new day, so onto another PC, download all the files again, start it all again. This was so easy on the OSF, I've been 30 years in IT and its making me feel very humble at the moment! Still I wont be beaten, here goes again!

[Wacky.ddw]

Coffer52, on 21 December 2011 - 10:34 AM, said:

Today is a new day, so onto another PC, download all the files again, start it all again. This was so easy on the OSF, I've been 30 years in IT and its making me feel very humble at the moment! Still I wont be beaten, here goes again!

Ive noticed it has problems with vista, if your using that?

[Skate Away]

Coffer52, on 21 December 2011 - 10:34 AM, said:

Today is a new day, so onto another PC, download all the files again, start it all again. This was so easy on the OSF, I've been 30 years in IT and its making me feel very humble at the moment! Still I wont be beaten, here goes again!

Ah, pride before a fall...

You probably won't be beaten, but I bet you get to the point where you would be very happy to throw the phone at a wall before you do win....

[Coffer52]

xiaoyaoswim, on 16 November 2011 - 01:11 PM, said:

I keep seeing people struggle with problems when connecting their handset to a Windows PC by USB cable. So here I am trying to give some more explanation about the Windows drivers stuff on OMC/ZTE Skate. Hope it will help you sort out the driver issue especially the annoying "waiting for device" message.




Basically there are two kinds of Windows drivers for Skate. One is an executable file from ZTE, named Handset_USB_Driver.exe. This file will appear in a virtual CDROM which is automatically mounted the first time you connect your phone to a PC (as long as your phone still got the stock firmware on).  I also uploaded the driver to http://www.multiupload.com/BQ7VQOQA4L . Since it’s an exe file, you just need to run it and the driver will be automatically installed. Once you installed it, your phone should be able to work in normal mode and FTM mode.




On the other hand, when you are trying to flash the superboot or recovery (clockworkmod or stock one) by the ADB tool you need another driver from Google. I ripped it from Google Android SDK and uploaded it to http://www.multiupload.com/71A1OXUPYI  . Unfortunately this one is not an exe file, which means you need to install the driver manually. And to make things worse, you will have to select which driver to install as Windows will not do it for you.   If you are stuck in bootloader mode, where you only have the green Android logo on the phone screen and "waiting for device" message on Windows Command Prompt, I will take Win7 as an example to show you how to manually install the driver.  Open device manager and find the unrecognised device called Android Phone ---> in its driver tab click update driver---> choose to browse my computer for driver ---> choose to pick from a list of device drivers and then select all device  --->click have disk --->browse  to the folder where you extracted Google driver to --->Select "Android Bootloader Interface" and then click next. Now the driver for bootloader mode should be successfully installed.




Note: The windows driver is for both 32 bit and 64 bit OS. The manual installation process for  Vista could be slightly different but very similar.

UPDATE
If you are installing Google SDK driver in Windows XP, you need to add following section into android_winusb.inf ( Many Thanks to dadcore)

;ZTE Skate
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D00D
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D00D&MI_01

OR you can just download & overwrite the original android_winusb.inf with the one in attachment. android_winusb_Skate_WinXP.zip

Hi I'm following method 2 here and have downloaded the google drivers as I want to install clockworkmod but when I want to update the driver windows 7 tells me the current driver is the best and refuses to replace it!! FFS can someone help me with this crap!

[Coffer52]

Wacky.ddw, on 21 December 2011 - 10:45 AM, said:

Ive noticed it has problems with vista, if your using that?

No mate this is Win 7 and Ive tried another PC and still no joy!! It will not let me update the google USB drivers just keeps telling me the installed drivers are the best and closes the window!

[Coffer52]

OK now I've removed the windows installed driver and have an android phone with a question mark in other devices in device manager. I right click, update driver, and go to the driver files downloaded  from the first post and all the f**king Android SDK environment USB  drivers and it responds with cannot find driver FFS, I give up!

[Coffer52]

Skate Away, on 21 December 2011 - 11:39 AM, said:

Ah, pride before a fall...

You probably won't be beaten, but I bet you get to the point where you would be very happy to throw the phone at a wall before you do win....

Your right I'm there, wasted too must time on this crap!

[dibbles]

double post

Edited by dibbles, 21 December 2011 - 02:07 PM.

[dibbles]

Coffer52, on 21 December 2011 - 01:29 PM, said:

Your right I'm there, wasted too must time on this crap!

This is what you should see...



could you please post a screen shot showing what yours looks like and expand the tree to show the driver etc for the relevant components to do with the phone. The phone must be connected with debugging on but do not mount the SD card.

Edited by dibbles, 21 December 2011 - 02:09 PM.

[Coffer52]

dibbles, on 21 December 2011 - 02:07 PM, said:

double post

Thanks for your response no I'm not getting the ZTE ADB interface I have the Handset ADB interface under ADB. What is the best tool for attaching a screen shot? Thanks again, I'm going staircrazy here!!

[dibbles]

Taking a screenshot of your device manager under Windows....

Open DM with the relevant tree expanded. Click on DM to ensure it is "selected". Press and hold the ALT key and the Print-screen Key. Open up Paint and paste from the clipboard. Adjust as required and save to desktop. Post here with the full editor and in the left bottom corner attach the file, in this case your saved screenshot.

But does it state Composite ADB Interface under the device, ignore the ZTE prefix on mine for now.

Edited by dibbles, 21 December 2011 - 02:20 PM.

[Skate Away]

Coffer52, on 21 December 2011 - 01:29 PM, said:

Your right I'm there, wasted too must time on this crap!

Yeppers, bet you haven't wasted as much time as I did....or got quite as close to throwing it against a wall...

I did try all the guides on here, several times, but none of them worked (for me).


I don't normally have any problems with PC troubleshooting - this one is an exception.

I think I put in more than 24 hours of very frustrating effort and lots of missed sleep...

Eventually, it just worked, for no obvious reason and with no identifiable series of steps.

Here's how I did it, this might work for you, but I wouldn't put money on it....

1) remove anything related to the phone with USBdeview (it was difficult to tell what was related so I sorted them by date and removed everything recent)

1a) uninstall all drivers

2) reboot

3) plug phone in, when the virtual CD appears in 'my computer' open it and copy the supplied driver to the desktop

4) close everything apart from one window showing 'my computer'

5) install the driver

6) right click and eject the virtual CD

7) wait

At this point nothing spectacular happened - there wasn't a phone symbol in 'my computer' and there wasn't anything much different in device manager.

In fact, I couldn't see any way of telling it had actually connected - other than in a DOS window.

I suspect I may well have had it connected earlier, possibly several times.

AFAIK, listing devices in DOS is the ONLY way of knowing if it has actually connected - though I stand to be corrected....

btw, how are you checking to see if the phone has connected ?

Edited by Skate Away, 21 December 2011 - 03:38 PM.

[Coffer52]

OK guys, heres the current DM config:
 DM.jpg   113.35K   30 downloads

I'm hoping I dont have to remove everything but you may be right Skate Away!!

[dibbles]

@Coffer52 - do this...

With the phone plugged in, only with debugging mode on, open a command window and at the DOS prompt type in...

adb devices and then note what is listed. If your device is thee you should be fine if not, and I doubt it will, then double click on that ADB Interface driver and browse and pick your own to change it to the Composite ADB Interface as shown in mine.

You MUST have installed the Handset_USB_Driver before you do any of the above.

Then repeat with the same DOS Window when the driver reflects the Composite one. Run the command adb devices and the phone (ID) should be there.

I'm in a rush to go out and so have had to skimp through the above, I will be back soon to see how things have gone on for you.

[Coffer52]

dibbles, on 21 December 2011 - 03:10 PM, said:

@Coffer52 - do this...

With the phone plugged in, only with debugging mode on, open a command window and at the DOS prompt type in...

adb devices and then note what is listed. If your device is thee you should be fine if not, and I doubt it will, then double click on that ADB Interface driver and browse and pick your own to change it to the Composite ADB Interface as shown in mine.

You MUST have installed the Handset_USB_Driver before you do any of the above.

Then repeat with the same DOS Window when the driver reflects the Composite one. Run the command adb devices and the phone (ID) should be there.

I'm in a rush to go out and so have had to skimp through the above, I will be back soon to see how things have gone on for you.

OK ran the commend it says P743T_OUK

[Coffer52]

OK now inexplicably it has connected and allowed me to install CMR, I give up!

[Coffer52]

Moving onto the unlocking thread and guess what, having rebooted the phone, the ADB no longer sees it, WTF!!