Please Help before I Cry

[Guest TouchyAndalou]

Ok, so I've recently bought a second Monte Carlo which I unlocked successfully last night. I then went to restore my mac address and after it got to 100% it gave an error message saying that it couldn't communicate with the phone, or something like that. That's problem number one.

So figuring I'd install superboot and come back to that, I tried to run the Handset_USB_Driver I downloaded. No good there either; every time I try to run it I get a message saying that I have "installed a higher version application" and the program closes. Wonderful.

Next I installed the google drivers and, amazingly, that seemed to work. As soon as I try to install either superboot or recovery however, the phone just hangs on the green android man and says waiting for device. Nightmare.

Back to give the mac address another try and now I can't get the phone to show under an active port, despite following all the same instructions in QPST configuration that worked previously. ARRRGHHH OMFG!

I've read through loads of different threads and tried all sorts of things to get this working, but I'm not having a pinch of luck. I'm on Vista and had problems setting up my other OMC, but nothing like this where NOTHING is working..

If somebody can please help before I go completely, utterly insane, It'd be hugely appreciated. Thanks.

[Guest tillaz]

have you tried uninstalling ZTE Handset USB Driver from control panel, then reinstall them

[Guest Atomix86]

Go into "my computer" while phone is plugged in and eject the faux cd drive the skate shows, see if that helps.

Edited December 28, 2011 by Atomix86

[Guest RadioCharlie]

If it's hanging on <waiting for device> - Do you have an uknown device in your Windows Device Manager? If so, you'll want the "Have Disk" method which has been posted here. You'll want to point Windows to the INF that comes with the handset drivers in the Android SDK. That's how I got mine to take - I spent about a week trying to get the thing to root, even took it to a friend (HTC and Linux guru) but I got it by following the guide on here.

3rd paragraph down is what did it for me:

[Guest TouchyAndalou]

Thanks for your help.

I've tried removing the drivers, I even used usbdeview to uninstall everything related to the phone. Then installed the Google drivers from sdk manager thingy.

There's no device showing to eject. On device manager it's showing android ADB interface, which I think is correct. I've no idea why it's not working.

[Guest tillaz]

Thanks for your help.

I've tried removing the drivers, I even used usbdeview to uninstall everything related to the phone. Then installed the Google drivers from sdk manager thingy.

There's no device showing to eject. On device manager it's showing android ADB interface, which I think is correct. I've no idea why it's not working.

suppose if you still have no luck with this you could try doing the repartition tut http://android.modac...zte-skate-tpts/ , this will repartition the system via tpt & install clockwork mod witch then would essentially let you install a rooted rom

Edited December 28, 2011 by tillaz

[Guest TouchyAndalou]

When I get the waiting for device message and it hangs, the found new hardware wizard pops up and it tells me to install drivers. But which drivers? It won't let me install the Handset_USB_Drivers I downloaded (says I already have a higher version application installed) and I've already installed the google drivers. Any ideas on this? Thanks.

[Guest TouchyAndalou]

suppose if you still have no luck with this you could try doing the repartition tut http://android.modac...zte-skate-tpts/ , this will repartition the system via tpt & install clockwork mod witch then would essentially let you install a rooted rom

It may come to that mate, because this is seriously driving me mad. Are there any disadvantages to using the TPT method? It sounds too easy lol.

[Guest tillaz]

It may come to that mate, because this is seriously driving me mad. Are there any disadvantages to using the TPT method? It sounds too easy lol.

nope, it worked fine for me & took less than a minute to do plus your getting more internal memory.

it really is very easy and fast

EDIT: if doing so i would use the 200mb system 35mb cache version

Edited December 28, 2011 by tillaz

[Guest dadashi]

nope, it worked fine for me & took less than a minute to do plus your getting more internal memory.

it really is very easy and fast

EDIT: if doing so i would use the 200mb system 35mb cache version

will that solve his missing mac address problem....?

A little help for the windows driver install:

1- When you plug the OMC into pc usb you get a cd-drive in my computer, eject it !!! otherwise you won't get Androidphone device in device manager

2- You'll probably have to install java before you can install the sdk/google driver download tool, you'll be given the link by the sdk tool

3- When you execute SDK Manager.exe it might not start....I had to look under properties and choose win98/millemium compatibility to get it to work!

4-Even after starting SDK Manager.exe and choosing googleusbdrivers it still took four attempts before it finaly downloaded the drivers into the extra folder in the same SDK directory

5-Vista wouldn't allow to choose the *.inf data,... choose to find the driver from the list of device drivers on pc and then choose to search drives, choose your sdkmanager folder/google/extra and the *.inf data

6-Vista finds two Androidphone devices in Device manager, for the first one choose Android Bootloader interface and the second Android composite ADB interface

Edited December 29, 2011 by dadashi

[Guest TouchyAndalou]

will that solve his missing wlan address problem....?

That's really my only big problem now, as I finally managed to get root and recovery installed. The issue now is that my phone no longer shows up in QPST at all. When I went to configuration previously and tried to add a new port, two ports would show up and I could select the one with my phone. Now only "COM1 - serial" shows up, and it's not the one I need.

Anybody know anything about this? Thanks again.

[Guest tillaz]

is your other omc detected ok or not ?

[Guest jojozep]

Trying to unlock OMC and when running install-recovery-windows.bat get the green android on mobile and DOS box say waiting for device.

Have searched around it the suggestion is to install the GOOGLE drivers. Have downloaded drivers and made Windows XP .inf changes but when I try to 'Update Drivers' and point the location to the android_winusb.inf directory it says 'Cannot Install this Hardware'.

Also, when I plug in phone keep getting 'Select Language' Welcome to Handset USB Driver Setup Wizard.

Any tips on getting drivers sorted out ?

Thanks in advance.

[Guest dadashi]

have you read my instructions 3rd post above...?

[Guest jojozep]

have you read my instructions 3rd post above...?

From Device Manager I DO NOT get any ? or X showing a problem with any device.

Device Manager entries - Without Phone

Disk Drives - x4 - Generic USB + x2 - Seagate Drives

DVD/CD - x1 - Pioneer

Note that when phone is inserted (comes up with Removable Disk drive I:) and try to access drive I: a message box appears saying 'Please insert a disk in Drive I:'

Device Manager entries - With Phone shows added items.

ADB Interface / Handset ADB Interface (provider Google)

Disk Drives - Handset Mass storage USB Device (provider MS)

DVD/CD - No drives added

Modems - Handset US (provider ZTE)

Thanks

[Guest TouchyAndalou]

is your other omc detected ok or not ?

No, it will no longer detect either phone.

[Guest dadashi]

at least you know for certain its definitely your computer configuration thats playing up....and your omc is fine...

have you got another laptop, vista, xp...try with my instructions above

[Guest dadashi]

I've uploaded the correct windows sdk drivers...that'll save tonnes of mucking about...:D

http://www.megaupload.com/?d=2XUJ1EVS

I don't know why we don't have a permanent sticky link for everyone instead of making newbie users spend hours trying to download their google sdk drivers through elaborate ways.....

someone please tell a moderator to sticky this link for everybody....

Edited December 29, 2011 by dadashi

[Guest jojozep]

I've uploaded the correct windows sdk drivers...that'll save tonnes of mucking about...:D

http://www.megaupload.com/?d=2XUJ1EVS

I don't know why we don't have a permanent sticky link for everyone instead of making newbie users spend hours trying to download their google sdk drivers through elaborate ways.....

someone please tell a moderator to sticky this link for everybody....

Yes, the driver link is OK (except for XP apparently).

My question is how do you actually install them after having installed Handset USB Driver. Some posts say a Virtual CD Drive is created that needs to be Ejected - but I dont get a Virtual CD created.

I'm using XP and when I try to install them I get Device Manager message like 'Cannot Install Driver' 'Cannot Install Hardware'.

I'm having untold problems trying to get the XP PC to recognise the OMC ie. Drive I is visible but not accessible . The way I see it (at least for XP) is that when Handset USB Driver is installed its using the wrong android_winusb.inf The mystery (a starting point at least) is how to get those XP drivers recognised.

Edited December 29, 2011 by jojozep