I'm having some problems following the instructions from http://ift.tt/ShTwt5 regarding setting up Android Studios and the recommended 'fastboot' drivers on Win 10. I have done some vocoder development in the past and have a background in tech development and dedicated microprocessor programming, but i'm in over my head here. I could use a little help.
This is on a Sony Xperia Z Model C6606 4.3 T-Mobile variant Build 10.4.C.0.814. Even though I checked (by *#*#7378423#*#*) and got unlock bootloader allowed: No.; T-Mobile tier 2 technical support indicated that I should try the OEM method anyway. When I checked their site, I plugged in all the info about my phone and it indicated that I could unlock the boot loader. :Big Grin:
Now to the problems. This is where you hear the *blub blub* as I wade into the deep end.
After a visit to the device manager, following numerous tips from various sources and floundering about, I looked at the two INFs and found some discrepancies. The first is the one from the Sony 'fastboot driver' link above for their version of android_winusb.inf. The error I get here is based on the fact that this download contains NO CABS and the Google USB cabs do not have the installation files the Sony INF needs. On the other hand the Google USB 'extras' loaded by Android Studio do not include specific support for the Sony Xperia Z. :forehead slap:
Short version, I can't connect to fastboot.
I have tried both INFs and in each case with USB debugging enabled on the Z, I powered it down, held the VOL up button as I plugged the cable into the USB port. In all cases I got the blue light but no windows prompt asking for a driver! Even when I open a command window in the directory where the INF resides I DO NOT get a list of adb devices. If I enter 'fastboot devices' from the command prompt, I get the stock windows error that 'fastboot' isn't a recognized command.
If I could get a little direction here as to next steps, I would really appreciate it. Thanks.
This is on a Sony Xperia Z Model C6606 4.3 T-Mobile variant Build 10.4.C.0.814. Even though I checked (by *#*#7378423#*#*) and got unlock bootloader allowed: No.; T-Mobile tier 2 technical support indicated that I should try the OEM method anyway. When I checked their site, I plugged in all the info about my phone and it indicated that I could unlock the boot loader. :Big Grin:
Now to the problems. This is where you hear the *blub blub* as I wade into the deep end.
- Their instructions read in part, "1. Download and install the Android SDK."; which I did, including loading the Google USB drivers.
- 2. If you're running Windows, you also need to download and install an updated Fastboot driver. This is the standard android_winusb.inf-file, with a few lines of code added to enable Fastboot to support Sony & Sony Ericsson devices. Replace the original android_winusb.inf-file with the downloaded file in the usb_driver folder, located in the Android SDK > extras > google folder on your computer. If you can't find the usb_driver folder, make sure you are running Google USB Driver package revision 4 or higher in your Android SDK. If not, install the Google USB Driver Packager using the Android SDK manager.
After a visit to the device manager, following numerous tips from various sources and floundering about, I looked at the two INFs and found some discrepancies. The first is the one from the Sony 'fastboot driver' link above for their version of android_winusb.inf. The error I get here is based on the fact that this download contains NO CABS and the Google USB cabs do not have the installation files the Sony INF needs. On the other hand the Google USB 'extras' loaded by Android Studio do not include specific support for the Sony Xperia Z. :forehead slap:
Short version, I can't connect to fastboot.
I have tried both INFs and in each case with USB debugging enabled on the Z, I powered it down, held the VOL up button as I plugged the cable into the USB port. In all cases I got the blue light but no windows prompt asking for a driver! Even when I open a command window in the directory where the INF resides I DO NOT get a list of adb devices. If I enter 'fastboot devices' from the command prompt, I get the stock windows error that 'fastboot' isn't a recognized command.
If I could get a little direction here as to next steps, I would really appreciate it. Thanks.
from xda-developers http://ift.tt/22Uz6wm
via IFTTT
Aucun commentaire:
Enregistrer un commentaire