17 replies to this topic

[gujis]

Hello, I have been struggling to install Clockwork on OSF2.
Windows recognized the phone and "adb-windows.exe reboot bootloader" executed successfully
but after phone restart ADB just says "waiting for device".
I believe I have Fastboot drivers missing don't I? (there is a device in Device Manager called "Android" which is not installed properly)
Drivers from ZTE website does not seem to work either.
Any ideas?
Thanks

[ian_blade2]

hi i also have the same problem as this guy can anyone help many thanks ian.

[oldfella]

suggest you try the same drivers as recommended for the Blade

[Sebastian404]

Here is a link to the copy of PCSuite that comes with the Blade2..

http://www.multiupload.com/80M0LJQ99O

[gujis]

Thanks for reply. I get an error (pic attached) instantly after I double click SETUP.exe
I can't figure out what's wrong..

Attached Files

•  error.jpg   194.07K   58 downloads

[unrandomsam]

64 bit windows 7 ? I think I might know what the problem is.

If the usbid's are different to the ones in the signed cat file you cannot just add them doesn't work.

You have to force it to load going through update driver software -> browse my computer -> Let me pick -> have disk

Then go to the android_winusb.inf file and force it to load.

then you have to prefix all the fastboot commands with what ever is in

Details -> Hardware Ids.

To get the vendor id if its changed

i.e

fastboot -i 0x18d1 flash recovery recovery.img (or something similar).

[unrandomsam]

Think you might need to run the exe as admin.

You can run the driver installer prior to download.exe as well if you want.

[Hermione1986]

Im stuck at the same point,im using Windows Vista
ive loaded ADB and got to "adb reboot bootloader" phone goes into Green Droid mode
It then ask for drivers and ive gone to the ZTE folder but they dont load
I then tried to run the cmd line "fastboot flash recovery recovery-clockwork-4.0.1.5-blade2.img and get the message "Fastboot is not recognised as an internal or external command.
Any idea's

[Sebastian404]

Hermione1986, on 30 November 2011 - 10:29 PM, said:

Im stuck at the same point,im using Windows Vista
ive loaded ADB and got to "adb reboot bootloader" phone goes into Green Droid mode
It then ask for drivers and ive gone to the ZTE folder but they dont load
I then tried to run the cmd line "fastboot flash recovery recovery-clockwork-4.0.1.5-blade2.img and get the message "Fastboot is not recognised as an internal or external command.
Any idea's

fastboot-windows.exe ?

[gujis]

unrandomsam, on 30 November 2011 - 09:39 PM, said:

64 bit windows 7 ? I think I might know what the problem is.

If the usbid's are different to the ones in the signed cat file you cannot just add them doesn't work.

You have to force it to load going through update driver software -> browse my computer -> Let me pick -> have disk

Then go to the android_winusb.inf file and force it to load.

then you have to prefix all the fastboot commands with what ever is in

Details -> Hardware Ids.

To get the vendor id if its changed

i.e

fastboot -i 0x18d1 flash recovery recovery.img (or something similar).

Tried forcing android_winusb.inf file that I've got. Did not work, windows won't accept it and got the following error. Android_winusb.inf has been lying on my desktop for some time and I don't even know where I got it from.. Maybe it's the wrong file?
P.S. My system is x86 and not x64.

Attached Files

•  error 2.jpg   163.75K   52 downloads

Edited by gujis, 01 December 2011 - 06:32 PM.

[unrandomsam]

The pictures is not the right thing (Thats the adb one not the fastboot driver).

Try the generic google fastboot drivers.(From latest SDK).


usb_driver.zip (8.28 MB)http://www.multiupload.com/1CZD8UK88O

(Install it to the android incorrect installed device (when its in adb reboot bootloader).

[Hermione01]

Sebastian404, on 30 November 2011 - 11:06 PM, said:

fastboot-windows.exe ?

Hi ,
Ive tried that as well and still no go, ive tried it on a windows 7 laptop and it cant find the phone !

[Hermione01]

Hi Guys, need some help  here
Ive installed ADB , when i run the cmd line "Reboot bootloader "it puts the OSF2 into green droid mode, windows then as for driver details, i have browsed to the zte folder, android install folder and downloaded the drivers mentioned on this post and none load.
<BR itxtNodeId="50">I then tried to run the cmd line "fastboot flash recovery recovery-clockwork-4.0.1.5-blade2.img and get the message "Fastboot is not recognised as an internal or external command.
I tried the fastboot-windows.exe as well and get the same message.<BR itxtNodeId="49">Any idea's<BR itxtNodeId="48"><BR itxtNodeId="43"><BR itxtNodeId="42">

[gujis]

unrandomsam, on 01 December 2011 - 10:20 PM, said:

The pictures is not the right thing (Thats the adb one not the fastboot driver).

Try the generic google fastboot drivers.(From latest SDK).


usb_driver.zip (8.28 MB)http://www.multiupload.com/1CZD8UK88O

(Install it to the android incorrect installed device (when its in adb reboot bootloader).

Apparently it looks like my laptop has some USB hardware issues. I tried on other laptop and everything went silky smooth. Thanks for all the help though.

[raverrr]

anybody had any luck with the drivers on win7 x 64? if so please share (pulling my hair out)

[unrandomsam]

raverrr, on 12 December 2011 - 08:51 PM, said:

anybody had any luck with the drivers on win7 x 64? if so please share (pulling my hair out)

It will always work if you just force the stock (from the sdk) driver to install and use the right

-i option

(It is annoying though because you need to remember a string of hex).

[raverrr]

unrandomsam, on 12 December 2011 - 08:59 PM, said:

It will always work if you just force the stock (from the sdk) driver to install and use the right

-i option

(It is annoying though because you need to remember a string of hex).

ok thanks

[raverrr]

nvm

Edited by raverrr, 13 December 2011 - 07:12 PM.