68 replies to this topic

[FrankE]

jsplace, on Oct 19 2010, 10:41, 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

Hi I am totally new to Android phones and I know nowt about programming etc., so please have patience with me! After I downloaded the SF USB drivers and following the instructions I too am stuck with the green symbol, I don't know how to reboot the phone nor do I know how to open a command promt etc :-? I could do with an idiots guide on how to reboot the phone. Can someone please help?

Cheers FrankE

[FrankE]

FrankE, on Nov 24 2010, 22:46, said:

Hi I am totally new to Android phones and I know nowt about programming etc., so please have patience with me! After I downloaded the SF USB drivers and following the instructions I too am stuck with the green symbol, I don't know how to reboot the phone nor do I know how to open a command promt etc :-? I could do with an idiots guide on how to reboot the phone. Can someone please help?

Cheers FrankE

Hi again, I managed to download power toys and opened a command prompt in the folder where I had fastboot/adb (and the drivers) and typed "fastboot reboot" and hit the return key, now my phone just keeps going through a start up (reboot?) cycle, also I get messages stating USB device not recognised.  Any ideas?

Cheers FrankE

[FrankE]

FrankE, on Nov 25 2010, 10:33, said:

Hi again, I managed to download power toys and opened a command prompt in the folder where I had fastboot/adb (and the drivers) and typed "fastboot reboot" and hit the return key, now my phone just keeps going through a start up (reboot?) cycle, also I get messages stating USB device not recognised.  Any ideas?

Cheers FrankE

Think I have sorted it, took battery out, replaced it, done!

FrankE  

[xrelishx]

Hello Ive bought my San Francisco last Friday. Ive already installed the device drivers and windows is already recognizing my San Francisco when I connect the USB, and my San Francisco is already saying that is connected through USB to a computer.

But I cant see any folder on my computer referring to the San Francisco memory nor the SD card. Using this device driver the San Francisco memory shouldnt be mounted into a device in windows?

[Polythene]

Hello,

Upon booting the phone iwth teh Volume key up and pressing the power buttun, Windows installer found drivers and installed correctly without me having to point the installer to the driver files. Is this normal or has something gone wrong?

[malgiff10]

flibblesan, on Oct 11 2010, 16:30, said:

I've updated my modified drivers to fully support 32bit and 64bit Windows Vista & Windows 7 as well as 32bit XP and Windows 2000. http://flibblesan.co.../zte_driver.zip

You will probably need to install the drivers manually from the device manager. Ignore any warnings about them being unsigned.

Downloaded the Android SDK, tried an adb-> devices and my SF doesn't display. Tried installing fibblesan's drivers. But no luck, it installs some sort of 3G modem...i'm on Windows 7 64-bit.

Any help?

Edited by malgiff10, 29 November 2010 - 11:10 PM.

[CharlesBrown]

Seem to have tried every possible solution for this but still my laptop wouldn't recognise the San Fran - it will see the card but not the phone.

I've tried all sorts of drivers and solutions - the drivers here/Fibblesans Android forum - becoming frustrated that I seem to have tried everything and still Windows XP fails to see the phone.

I want to get rid of the orange junk and try a couple of custom ROMs - any help would be greatly appreciated.

[midwinter]

After a lot of messing around trying to get my SF detected you method just... worked! Fantastic. Many thanks...

Now off to play with AppInventor...

[getk]

Not able to install the drivers after cooking with alpha3?
guys any idea on this?

[Phoenix Silver]

CharlesBrown, on Dec 7 2010, 22:24, said:

Seem to have tried every possible solution for this but still my laptop wouldn't recognise the San Fran - it will see the card but not the phone.

I've tried all sorts of drivers and solutions - the drivers here/Fibblesans Android forum - becoming frustrated that I seem to have tried everything and still Windows XP fails to see the phone.

I want to get rid of the orange junk and try a couple of custom ROMs - any help would be greatly appreciated.

try ubuntu live cd
download iso here :

Ubuntu live cd

burn it
boot with the cd and enjoy
(live cd doesn't change anything in your system unless you install it)
terminal for adb is in applications / accessories / terminal

[majnu]

thanks cinfirmed working in win 7

[90180360]

flibblesan, on Oct 11 2010, 17:30, said:

I've updated my modified drivers to fully support 32bit and 64bit Windows Vista & Windows 7 as well as 32bit XP and Windows 2000. http://flibblesan.co.../zte_driver.zip

You will probably need to install the drivers manually from the device manager. Ignore any warnings about them being unsigned.

Did anyone have any luck with those drivers?

[skoo]

Can't get this to work now :/

I did it successfully a couple of days ago when I for the first time installed a custom rom on my Blade. Everything went well and I managed to get Paul's r3 and everything is fine except that I can't get the drivers to work so I can't install a new version of Clockworks Mod.

When i connect my phone with USB now there shows up 4 (instead of 2 as previously) ZTE HSUSB devices and windows just won't find the drivers when I point them to the folder with the drivers (which worked just fine previously). I've tried with Fibblesans drivers too but no luck there either.

Any suggestions? Otherwise I guess I'll just install Linux and do it from there or does it work from an virtual enviroment of Linux?

Edited by skoo, 03 January 2011 - 12:09 AM.

[tanivula]

skoo, on Jan 3 2011, 13:08, said:

Can't get this to work now :/

I did it successfully a couple of days ago when I for the first time installed a custom rom on my Blade. Everything went well and I managed to get Paul's r3 and everything is fine except that I can't get the drivers to work so I can't install a new version of Clockworks Mod.

When i connect my phone with USB now there shows up 4 (instead of 2 as previously) ZTE HSUSB devices and windows just won't find the drivers when I point them to the folder with the drivers (which worked just fine previously). I've tried with Fibblesans drivers too but no luck there either.

Any suggestions? Otherwise I guess I'll just install Linux and do it from there or does it work from an virtual enviroment of Linux?

I think its a case of the phone changing it's device ID now that 2.2 has been installed.  I think the drivers might need a tweak to add the new ID in?

[_kD]

Just installed another ROM - Flibblesan's Froyo R5a, and now I just cannot get the phone hooked up to my PC! I've tried everything, and downloaded every single driver I can find, but nothing works.. I put it into bootmode, and it installed all the hardware without hesitation, but when I hook it up when the phone is fully booted it just wont install.

I've tried turning off USB Debug, but still with no results - What is up? Anyone got any ideas? I'm pretty annoyed right now. The last time when I reinstalled the stock ROM, the phone wouldn't install either, but then I came back on the next day and it worked..

If I turn on USB Storage, then I can access the SD card - but ZTE HSUSB still comes up as new hardware and wont install.

[90180360]

skoo, on Jan 3 2011, 02:08, said:

does it work from an virtual enviroment of Linux?

Yes it does!

[90180360]

_kD, on Jan 4 2011, 21:31, said:

Anyone got any ideas?

Try removing all drivers, then installing "Correct ZTE USB driver for Blade" from the sticky topic.

[matjc82]

skoo, on Jan 3 2011, 00:08, said:

Can't get this to work now :/

I did it successfully a couple of days ago when I for the first time installed a custom rom on my Blade. Everything went well and I managed to get Paul's r3 and everything is fine except that I can't get the drivers to work so I can't install a new version of Clockworks Mod.

When i connect my phone with USB now there shows up 4 (instead of 2 as previously) ZTE HSUSB devices and windows just won't find the drivers when I point them to the folder with the drivers (which worked just fine previously). I've tried with Fibblesans drivers too but no luck there either.

Any suggestions? Otherwise I guess I'll just install Linux and do it from there or does it work from an virtual enviroment of Linux?

I've had exactly the same problem.  Jdspace's drivers worked well for the initial installation of the custom rom but once I installed froyo 2.2 the drivers were no longer recognized.  However, the below drivers now do work for me! Using Vista 64bit

http://android.modac...amp;mode=linear

[mecha_matt]

Hi Everyone!

I hope this doesn't sound stupid - I am no phone expert but competant with computers, and after 3 days of tearing my hair out with my SF I am ready to give up!

I was a victim of the dreaded (negligent?) launcherpro cancellation and I am trying to use your steps/drivers to be able to either install the update, access my laptop's internet on my phone, or just reset the phone and start again. Anyway, I am following your steps and when I plug in the phone I only get one HSUSB driver in my device menu, and I am only currently able to install the ADB Composite driver and not the Single one.

Is this something to do with the launcher not being active, or am I missing something? I have only ever seen one HSUSB when accessing my device manager in this way. In ADB, I currently get my device detected (adb devices) but it just says 'device offline' and I can't use any other commands.

As I said, I am reasonably computer literate though the phone stuff is new to me. The instructions here seem relatively straightforward, which makes my failure to implement them all the more maddening! I am really ready to give up so any assistance would be truly great. I am running win7 32.  


Thanks in advance for your time

Matt

[eLJay]

Hmm so I update the 2.2 Froyo build and have to reinstall the xp driver...

Slightly annoying but ho hum here we go.

LJ