Jump to content

Recommended Posts

Posted

any idea how to get it going on xp? my pulse connects ok but the zte can't be installed properly (usb mass storage works but not adb).

Posted
here you go....

Thats great,thanks.

I must be doing something wrong,as no matter how i go about it,windows keeps telling me it cannot find the driver.(win7 64).

Guest Modmedia
Posted

Tried going into device manager and all that jazz. Can't get these to work :lol:

Guest fluxcapacitor
Posted

Not working here on Win 7 64bit, says windows could not find driver software for your device when you point it to the usb drivers folder

Guest Modmedia
Posted
Not working here on Win 7 64bit, says windows could not find driver software for your device when you point it to the usb drivers folder

Exactly what I get, how are Paul et al doing all these wonderful things with theirs? Maybe they don't run Windows?

Posted

It works ok for 32 bit win7

I don't have 64 bit so i cant help on that side.....

Guest Modmedia
Posted

Awww maybe that's why. I'm just waiting on delivery of my MacBook air I've been without my MPB for 3 days and I'm already hating windows lol.

Posted

Got a bit further, the following will get fastboot working in vol+ mode and also adb working in normal with usb debugging on

[Google.NTx86]

; ZTE Blade

;fastboot

%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D00D

;adb normal mode

%CompositeAdbInterface% = USB_Install, USB\VID_19D2&PID_1354&MI_02

this still leaves a bunch of interfaces not implemented and fastboot doesn't work in usb debugging mode

any idea what %SingleBootLoaderInterface% enables??

Guest scoobdriver
Posted

I changed the Vendor ID for the generic Android x64 drivers and it seems to work fine

Posted
I changed the Vendor ID for the generic Android x64 drivers and it seems to work fine

could you upload them please?

Guest stuartmc
Posted

I am running win 7 Pro 64-Bit and the ADB drivers downloaded from Windows Update without any problems and have run the rooting and Paul's custom ROM so not sure why others are having such a hard time with drivers.

Posted

Below are my experience with connecting the SF with WXp SP3.

1.Unzip the attached 'SF-WinXP-SP3_USB_Drivers.zip' somewhere on your C: drive.

2.Power on your SF and wait until your HomeScreen appears.

3.Go into 'Settings--USB Settings--USB Mass Storage and select 'Auto mount'.

4. Connect (using supplied USB cable) to PC USB port.

5. Windows will detect the new hardware start looking for it;if Windows automatically finds the required drivers then you are all set and don't have to read anymore, if not.....

Direct it to select from the location where you unzipped the above files.

This will give you two entries in Device Manager (see attached Android-DM.jpg).

Once this is complete you will see a new Removable Disk appear in 'My Computer' which corresponds to your SD Card. You can now read/write/browse entries there.

This was all well and good until I tried to root my device.

Following Paul's excellent instructions I got some strange things.

Firstly while at the Android logo (little green chap) and connecting my device to the USB, Device Manager would find a new Android Phone but this time directing it to the unzipped files above did not find the right drivres, so:

6. Unzip the attacheed FastBoot-XP-DriversSF.zip to the same location where you put the unzipped files above; this will extract 3 new files, androidusb.sys, android_USB.inf and WdfCoInstaller01005.dll.

7. Point the 'Found New Hardware' to this location which will install yet another entries in Device Manger, called 'Android Sooner Single ADB Interface' (see attached fatboot-sf.jpg).

This will enable you to now execute the root commands as directed in Paul's thread http://android.modaco.com/content/zte-blad...emo-now-online/

Note: even this still didn't enable me to talk to the device via adb, as in Paul's video. However, once rooted you can simply copy the mcri-system.tar.gz file to the root of the SD card, via a card reader or by connected normally and copying to the removable drive and restart the device to execute the ROM update and remove the Orange stuff.

Observations:

1. I think many who did not have an issue with connecting the SF to XP is because they had the Andoir SDK already installed on their computer which installs all the necessary drivers etc..

2. HomeSelector, which was an Orange ROM add-on, will disappear once this modified ROM is installed.

3. Digital Clock has also gone, so has the 'additional' analog clock, don't know if you can download again any of these since I am new to android myself.

Hope this helps someone out with connectivity.

post-204583-1285804666_thumb.jpg

post-204583-1285804675_thumb.jpg

fastboot.zip

SF_WinXP_SP3_USB_Drivers.zip

Guest mitrepooc
Posted
This might be a complete long shot but I've edited the T-Mobile Pulse 32bit and 64bit drivers with the IDs for the ZTE Blade. If anybody wants to try them then download and report back please. I'm interested to know if they work with 64bit.

http://flibblesan.co.uk/android/zte_driver.zip

Cheers Matey worked like a charm, vista 32 drivers for my xp pro sp3 machine :lol:

  • 4 weeks later...
Guest nas7000
Posted
This might be a complete long shot but I've edited the T-Mobile Pulse 32bit and 64bit drivers with the IDs for the ZTE Blade. If anybody wants to try them then download and report back please. I'm interested to know if they work with 64bit.

http://flibblesan.co.uk/android/zte_driver.zip

w

Worked Like a charm..

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.