WinXP/7 ZTE Blade drivers and ADB
#21
Posted 12 October 2010 - 03:19 PM
#22
Posted 17 October 2010 - 01:43 PM
flibblesan, on Oct 11 2010, 16:30, said:
You will probably need to install the drivers manually from the device manager. Ignore any warnings about them being unsigned.
First post - having picked up a SF yesterday, I'm having a play
Anyhow: Flibblesan's driver pack didn't work under 32-bit Vista, sadly - the modem driver is installed, but Vista then can't find the driver for "ZTE HSUSB". JSPlace's driver pack did the job, but I had to download it from Matty P's link, as the free hosting thing completely failed to work...
Edited by j00ce, 17 October 2010 - 01:44 PM.
#23
Posted 19 October 2010 - 10:38 AM
jsplace, on Oct 2 2010, 10:51, said:
The .rar contains the r3 android driver, latest adb from the SDK and a modified .inf file to allow the Blade to be recognised by Windows in both ADB and bootloader modes.
I have had sucess with this both in WinXP and Win7 using exactly the same files.
Enjoy and please let me know if it works for you
http://www.easy-shar.../usb_driver.zip
~6.5Mb
EDIT: Sorry for the REALLY crapps hosting, if someone could please upload to somewhere sensible it would be appreciated!
EDIT2: Quick HowTo. (How I did it)
1. Download the file above and extract to a folder of your choice.
2. With your phone ON and fully booted, connect to PC with USB cable.
New Hardware wizard should start. (See below if it doesn't)
3. When asked to search select no and browse to the folder where you extracted the files.
Click next and the wizard should install 2 devices. (SingleAdbInterface and CompositeAdbInterface)
4. Unplug the phone from the pc and restart phone in bootloader mode (Power on with Volume up key pressed)
Phone should stay on Green Android screen.
5. Plug in phone again and wizard should detect new hardware. Again point wizard to folder where you extracted files and SingleBootloader device should be installed.
6. Job done
IF NEW HARDWARE WIZARD DOES NOT START.
1. Open device manager and right click on The exclamation (Think it says HSUSB?)
2. Select Update driver
3. When asked to search select no and browse to the folder where you extracted the files. Select next and driver will be installed.
4. Repeat step 3 for the other HSUSB device with exclamation.
5. Reboot into bootloader, rinse and repeat.
Hope this helps
Big thanks to Matty P for hosting this on his site too
Here is his link (Fixed)
http://www.matthewpi.../usb_driver.zip
Rapidshare etc just wont work for me for some reason....
#24
Posted 19 October 2010 - 10:41 AM
rgunning, on Oct 19 2010, 11:38, said:
Open a command prompt in the folder where you have fastboot/adb (and the drivers) just type "fastboot reboot"
Phone should restart, pulling battery at this point tho is safe, you are not flashing anything
Edited by jsplace, 19 October 2010 - 10:45 AM.
#25
Posted 19 October 2010 - 10:48 AM
#26
Posted 19 October 2010 - 11:13 AM
jsplace, on Oct 2 2010, 11:51, said:
The .rar contains the r3 android driver, latest adb from the SDK and a modified .inf file to allow the Blade to be recognised by Windows in both ADB and bootloader modes.
I have had sucess with this both in WinXP and Win7 using exactly the same files.
Enjoy and please let me know if it works for you
http://www.easy-shar.../usb_driver.zip
~6.5Mb
EDIT: Sorry for the REALLY crapps hosting, if someone could please upload to somewhere sensible it would be appreciated!
EDIT2: Quick HowTo. (How I did it)
1. Download the file above and extract to a folder of your choice.
2. With your phone ON and fully booted, connect to PC with USB cable.
New Hardware wizard should start. (See below if it doesn't)
3. When asked to search select no and browse to the folder where you extracted the files.
Click next and the wizard should install 2 devices. (SingleAdbInterface and CompositeAdbInterface)
4. Unplug the phone from the pc and restart phone in bootloader mode (Power on with Volume up key pressed)
Phone should stay on Green Android screen.
5. Plug in phone again and wizard should detect new hardware. Again point wizard to folder where you extracted files and SingleBootloader device should be installed.
6. Job done
IF NEW HARDWARE WIZARD DOES NOT START.
1. Open device manager and right click on The exclamation (Think it says HSUSB?)
2. Select Update driver
3. When asked to search select no and browse to the folder where you extracted the files. Select next and driver will be installed.
4. Repeat step 3 for the other HSUSB device with exclamation.
5. Reboot into bootloader, rinse and repeat.
Hope this helps
Big thanks to Matty P for hosting this on his site too
Here is his link (Fixed)
http://www.matthewpi.../usb_driver.zip
Rapidshare etc just wont work for me for some reason....
firstly thanks for the guide but i'm stuck on step 5. i can istall the SingleAdbInterface and CompositeAdbInterface and i can see in my device manager when i connect the phone.however when i disconnect it and out the battery out etc and then reconnect, the wizards comes up and starts to copy but then it says it needs a particular file that i can't find.
i would be very grateful for any ideas
#27
Posted 19 October 2010 - 11:20 AM
lllacey25, on Oct 19 2010, 12:13, said:
firstly thanks for the guide but i'm stuck on step 5. i can istall the SingleAdbInterface and CompositeAdbInterface and i can see in my device manager when i connect the phone.however when i disconnect it and out the battery out etc and then reconnect, the wizards comes up and starts to copy but then it says it needs a particular file that i can't find.
i would be very grateful for any ideas
Point the wizard to the folder where you extracted the files to, all the files should be there.
If not then you could try the manual install instruction further down the post.
#28
Posted 19 October 2010 - 05:45 PM
#29
Posted 19 October 2010 - 07:44 PM
Mangemongen, on Oct 19 2010, 18:45, said:
Both my main PC and my sons run win7 64 bit and I have had no problems.
What file is it looking for?
#30
Posted 19 October 2010 - 08:24 PM
#31
Posted 24 October 2010 - 11:22 AM
jsplace, on Oct 19 2010, 10:41, said:
Phone should restart, pulling battery at this point tho is safe, you are not flashing anything
#32
Posted 28 October 2010 - 10:00 PM
I have tried the ones linked here but I believe I have a different USB ID. It ends in 5 and not 4 ?!
Edit: I'm not exactly sure whats going on, but after I cleared the cache partition, I'm seeing the proper 0x1354 usb product id instead of 0x1355.
For the first time since I unboxed the phone its now installing the drivers?! Problem is solved but I'm not sure what was happening before...
Edited by bunnygirl222, 28 October 2010 - 11:18 PM.
#33
Posted 31 October 2010 - 12:07 PM
First time posting here, but done a lot of reading over the last 2 weeks.
Got a problem that i can't seem to resolve with my San Fran. I've tried this on 2 seperate W7 machines.
I've loaded the Android drivers (after removing the Google drivers that automatically installed), without any problems. However, when i boot the phone up (volume up and stopping on the green android symbol) i don't see any removable devices appearing on my laptop, after connecting using the USB. I do here the confirmation tone that a USB device has been plugged in, plus i can see an Android USB device that is ejectable.
Any clues as to where i'm going wrong? I already managed to successfully root this phone 2 weeks ago, but now can't "see" it anymore.
Thanks!
#34
Posted 31 October 2010 - 12:44 PM
Monkey Butler, on Oct 31 2010, 13:07, said:
First time posting here, but done a lot of reading over the last 2 weeks.
Got a problem that i can't seem to resolve with my San Fran. I've tried this on 2 seperate W7 machines.
I've loaded the Android drivers (after removing the Google drivers that automatically installed), without any problems. However, when i boot the phone up (volume up and stopping on the green android symbol) i don't see any removable devices appearing on my laptop, after connecting using the USB. I do here the confirmation tone that a USB device has been plugged in, plus i can see an Android USB device that is ejectable.
Any clues as to where i'm going wrong? I already managed to successfully root this phone 2 weeks ago, but now can't "see" it anymore.
Thanks!
Have you mounted the SD card on the phone? Tap the notification after dragging the bar down.
#35
Posted 02 November 2010 - 10:24 AM
adb devices
adb server is out of date. killing.....
*daemon started succesfully*
List of devices attached
it then returns to the c:\folder>
where i have gone wrong i can adb into my own hero but no luck with the san francisco i am using the correct folder for the SF
#36
Posted 02 November 2010 - 10:36 AM
mifran, on Nov 2 2010, 11:24, said:
adb devices
adb server is out of date. killing.....
*daemon started succesfully*
List of devices attached
it then returns to the c:\folder>
where i have gone wrong i can adb into my own hero but no luck with the san francisco i am using the correct folder for the SF
Are you running 1.0.26 ?
type.....`adb version`
#37
Posted 03 November 2010 - 08:31 AM
#38
Posted 03 November 2010 - 09:53 AM
#39
Posted 03 November 2010 - 02:35 PM
jsplace, on Nov 3 2010, 09:53, said:
ok thanks i have downloaded it should it also work with a hero
Microsoft Windows [Version 6.1.7600]
Copyright © 2009 Microsoft Corporation. All rights reserved.
C:\Users\****>cd c:/san
c:\san>adb
Android Debug Bridge version 1.0.26
EDIT i have reinstalled all the drivers .and also ADB into a new folder and now i can adb into both the hero and the san francisco thanks for the new drivers and adb how often do we have to update adb
mifran
Edited by mifran, 03 November 2010 - 03:03 PM.
#40
Posted 21 November 2010 - 10:20 PM
Edited by Fishk, 21 November 2010 - 10:59 PM.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users







Sign In
Create Account


Back to top









