Hi,
I have a rooted Xperia Z5 and I would like to update my firmware to 32.2.A.0.305.
I used to do firmware updates many times before using flashtool on my windows 7 machine.
Recently I switched to windows 10 and now need to reinstall the fastboot driver.
I downloaded the driver from sonymobile webstie:
http://developer.sonymobile.com/downloads/drivers/fastboot-driver/
Unzipped the file, and got a directory with the "android_winusb.inf" file.
Booted the phone in "bootloader" mode via the TWRP recovery (LED on phone is blue).
The regular method of power down, volume up+connect to USB did not work. The LED was blue for a second and then turned off.
When in "bootloader/fastboot" mode, opened the windows "device manager" and found the problematic S1 device.
Right click on it, update driver, browse my computer, pointed to the directory where the ".inf" file is located.
Windows "makes sounds" as if it is installing the driver, but then gives an error:
"Windows found a driver software for your device but encountered an error while attempting to install it"
"Android ADB interface"
"The system cannot find the flie specified"
I have no idea what the problem is.
A few posts suggested that this might be a driver-signing problem with windows 10.
They suggested removing the "driver-signing" option and try. Did not work.
I also tried this with a virtual machine Windows 7 that I have installed, and got the same error, so I'm not sure it is a windows version problem.
I read in one place that this is an error with the location of the file and that it should be located under the "C:\Windows\WinSxS" directory.
Tried that as well, and no luck.
Does someone have any idea what the problem is?
Alernatively, if someone can explain or point me to a post of how to use fastboot and flashtool with linux,
that can also help.
Thank you.
Avi
driver signature verification
1. Goto START (windows icon);
2. Keep pressing SHIFT, klick POWER and RESTART
(shift is pressed all the time along);
3. Choose Troubleshoot > Advanced options > Startup Settings and click the Restart button.
When your computer restarts you'll see a list of options.
4. Press F7 on your keyboard to select Disable driver signature enforcement.
Your computer will now restart and you’ll be able to install unsigned drivers.
This is firt to do, but didnt quite get it if you tried this allready. Greetings
Have the same problem. Disabled driver signature enforcement. Did not help
Are you sure it's disabled? Some pc's don't have the option to disable the driver signature enforcement. If that's the case you need to enter the bios settings and look for the tk keys and delete them, then restart your pc and you can install the fastboot driver.
Hope this helps
Had the same issue on my new setup.
This solved all my problems: https://forum.xda-developers.com/xperia-z/help/help-findiing-installin-s1boot-fastboot-t2218143
dim4x4 said:
Have the same problem. Disabled driver signature enforcement. Did not help
Click to expand...
Click to collapse
Disable driver signature enforcment then install flashtool drivers and select your phone drivers and fastboot drivers, it will ask you are you sure to install press yes and then in folder x10flasher you have fastboot and open cmd in that folder and just use fastboot. Cheers
L33Tgod said:
Disable driver signature enforcment then install flashtool drivers and select your phone drivers and fastboot drivers, it will ask you are you sure to install press yes and then in folder x10flasher you have fastboot and open cmd in that folder and just use fastboot. Cheers
Click to expand...
Click to collapse
Nice and cool - but we still dont have a Sony Xperia Z5 Driver from it in the List
Related
Under Windows 8, you will likely run into the issue that you can get ADB to work properly, but cannot get Fastboot to work.
The reason is that ADB and Fastboot actually require/use two different drivers for each to work properly under Windows 8. But, only one of those, the driver that ADB will work under, will intall in a signed fashion that Windows 8 requires. You will need to enable Windows 8 to allow unsigned drivers to be installed, the steps are below.
You can install the normal HTC Sync, and the drivers/devices should be installed and work fine for ADB. You can test this by installing the SDK Tools for Windows and HTC Sync, then run "adb devices" from the command prompt, and it will find the device and work fine.
But...when you go into Fastboot mode, for example, to install a new custom recovery, the Fastboot.exe just flashes in the DOS window and nothing works.
Upon looking back into the Device Manager in Windows once in fastboot mode on the phone, it no longer recognizes the driver/device.
After some driver troubleshooting, I found that when the phone reboots into Fastboot mode, it needs another set of Generic Drivers, the typical ones you can find on the Web for HTC devices. The device while in Fastboot mode, under the Device Manager would show up with the Unknown icon instead of the My HTC device icons at the top of the list.
The issue is Windows 8 by default will not allow you to install unsigned drivers without jumping through some hoops.,
So here is what you do. You can download these generic drives, unzip them somewhere on the desktop, and have them ready.
http://androiddrivers.net/htc-android-drivers/download-htc-one-x-64-bit-windows-drivers/
(There are several other versions out there, just google "Windows 8 HTC One X Drivers" and you will find many to download, or the original HTC .exe. I like the zip file, easier to unzip, then update the driver.
Then, put your phone into Bootloader mode.
Go to Device Manager and notice that your phone is showing up as an Unknown Device in the list.
Now, in Windows 8:
1) Settings
2) Change PC Settings
3) Very bottom, Advanced Startup. Select this.
4) It brings you to another screen to select the options you want.
5) Troubleshoot
6) Advanced Options
7) Startup Settings, Select this option. You will see a list of options it gives you, included is "disable Driver signing"
Select this now and the computer will restart and provide another menu.
#7 is the option to boot the computer with driver signing disabled.
8) Once rebooted, your phone is still in bootloader mode, go back to device manager, right click the unknown android device, and update the driver manually, selecting the folder of the drivers you have downloaded previously.
It will then prompt about unsigned drivers, select Yes to install them anyway.
Now, your phone is detected in bootloader mode, and Fastboot will work properly to flash recovery etc.
this is pretty helpful but make sure you post in the right section
So I did what you did, and when i got to the screen to choose option 7, i tried with both F7 and hitting the number 7, then i went back into device management and tried to update the driver, but it didn't prompt me to install unsigned drivers.
Also, once you click settings, you have to click on general to find advanced options.
Any ideas?
---------- Post added at 12:53 PM ---------- Previous post was at 12:37 PM ----------
Ok, I got it workng, but theres a few more steps involved. Upon trying both drivers that you suggested downloading, when I run an adb devices command, it doesn't show anything under the devices attached listing.. Is that normal, or should I see my phone? I suspect this is why I'm having issues inside roms, since the boot.img isn't flashing correctly.
Hey guys, I'm usually ok at doing that part. But I can't seem to install drivers for fastboot. My computer identifies it as S1 fast boot (something similar).
I am on Windows 8.1 x64
Check my post in the firmware thread. You need to turn off driver verification
Brendo said:
Check my post in the firmware thread. You need to turn off driver verification
Click to expand...
Click to collapse
Sweet thanks! I'll take a look, although I have tried installing the drivers with the verification off.
You need to go to the "device manager" app in windows, then you select the S1 Fastboot thing, and then you need to right click on it and update driver but not automatically, you need to select the manual option, and then select the usb_driver folder from the Android SDK.
Hi To All Members. My HTC Explorer is unable to communicate with Windows 10 (64 Bit) in Fastboot Mode. Although i have installed the propers drivers for my Pico. In Device Manager, HTC Explorer is recognized as "ADB INTERFACE DEVICE" but whenever i connect it in FASTBOOT MODE. My PC says"Device Not Recognized" . I am using Windows 10 (Enterprise) and tried different USB CABLES. Also, whenever i connect it to install applications with APK INSTALLER. It Says "Connection Exception". .
Any help would be appreciated
help me tooo
My HTC sync is not recognising my device
Although the phone shows fastboot usb the computer doesnot recognise it
i am trying to unlock my bootloader but in cmd after the "fastboot oem get_identifier_token" command
I only see "<waiting for device>''
plZ HELP!!!!!!!:crying::crying::crying:
Hi their seems to be an error with usb registry since Windows 8 so some devices are not being recognised properly, thankfully their is a fix that works for Windows 8/8.1/10 right click on the attached Fasdtboot.txt file and "save target as" change the drop down option from "text" to "all files" then change the file extension from .txt to .reg (Fastboot.reg) so it can be added to your registry, once done simply double click on it and add it to your registry, then installed your drivers via device manager for fastboot and adb.
anonymous-user said:
Hi their seems to be an error with usb registry since Windows 8 so some devices are not being recognised properly, thankfully their is a fix that works for Windows 8/8.1/10 right click on the attached Fasdtboot.txt file and "save target as" change the drop down option from "text" to "all files" then change the file extension from .txt to .reg (Fastboot.reg) so it can be added to your registry, once done simply double click on it and add it to your registry, then installed your drivers via device manager for fastboot and adb.
Click to expand...
Click to collapse
Tried It. Same issue persists
syedbilal07 said:
Tried It. Same issue persists
Click to expand...
Click to collapse
Should work, just make sure your manually adding the drivers back in device manager one for adb and one for fastboot. (right click on unknown/malfunctioned device update driver, point to drivers)
I have manually added registry key and also installed drivers but it says, windows has determined the best driver for you and it is up to date. Feeling hated with windows 10
Try to update your windows ...
Fastboot working fine in my window 10..PC..
I am using enterprise edition.
Please can you properly guide me about every step with screenshots. I am trying to solve it since many days but now frustrated. Please, i will be thankful to you @vaibhav1
I don't know how to install it, all I see after downloading and upzipping is "MTK_Qualcomm_ADB" folder, inside are "install.vbs" file, "uninstall.vbs" file, Qualcomm and MTK folders. I I tried to click on "install.vbs" file, nothing happend, so I tried to install through Windows Device Manager, using the ".inf" file in the Qualcomm folder, but failed. I've just bought my phone for 1 week and I am new to Android, so don't curse me...
P/S: I read this instruction on reddit and got stuck in step 3.
1. Plug device into computer, wait for "normal" MTP drivers to install. You'll probably get an error about the ADB interface driver failing.
2. Open the notifications dropdown and select "Connected as a media device" (was the default for mine).
3. Select "Drivers CD-ROM" from the USB Computer Connection list.
4. Open My Computer and open new "USB Driver" drive (was E on my machine).
5. Double-click Setup.vbs, then click Install on the "Android USB Driver Manager" screen. (Click Uninstall to uninstall the driver)
chetlaxong said:
I don't know how to install it, all I see after downloading and upzipping is "MTK_Qualcomm_ADB" folder, inside are "install.vbs" file, "uninstall.vbs" file, Qualcomm and MTK folders. I I tried to click on "install.vbs" file, nothing happend, so I tried to install through Windows Device Manager, using the ".inf" file in the Qualcomm folder, but failed. I've just bought my phone for 1 week and I am new to Android, so don't curse me...
P/S: I read this instruction on reddit and got stuck in step 3.
1. Plug device into computer, wait for "normal" MTP drivers to install. You'll probably get an error about the ADB interface driver failing.
2. Open the notifications dropdown and select "Connected as a media device" (was the default for mine).
3. Select "Drivers CD-ROM" from the USB Computer Connection list.
4. Open My Computer and open new "USB Driver" drive (was E on my machine).
5. Double-click Setup.vbs, then click Install on the "Android USB Driver Manager" screen. (Click Uninstall to uninstall the driver)
Click to expand...
Click to collapse
Either 1) Plug in the device and when it prompts for a driver THEN point it to where the inf is or 2) install the driver zip mentioned here: http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
Thanks. I did it!
famewolf said:
Either 1) Plug in the device and when it prompts for a driver THEN point it to where the inf is or 2) install the driver zip mentioned here: http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
Click to expand...
Click to collapse
Hi, please help me install this driver, I can't down driver in this page, I have downloaded in this page ( http://mobiledriver.info/model/idol-3-(5.5)-143/ ) but not install,
Win10, in fastboot mode the device cannot be found, but it can be found in adb. I installed drivers from Sony's website. In fastboot mode the device manager shows under 'other', in adb it is normal and shows 'Sony sa0116 ADB interface driver'. As far as I know the driver is the same for adb and fastboot...my Pixel is recognised with no problem, only this Sony...anyone knows how to get it recognised in fastboot mode?
Sorted the driver issue... didn't install it properly...
Go to Windows device manager look for one called x-boot or android (your xperia) and open the driver details.
Klick update driver and next choose look for software on computer. Next window gives you the option to pick one of common devices. Install the sony driver for adb interface.
Could give a zip of it if needed.
After the manual driver update it should recognize your phone immediately - if you have checked the "fastboot devices" prompt before just repeat that (no reboot or reconnection necessary)
Win 10 seems to have problems. I downgraded to win 7 all sorted.
I'm having the same issue with my Xperia X compact. Windows 10 says it's installed best driver for my device but in device manager theres a warning next to the driver and device is not recognised under ADB devices. I remember it being simple the last time I did it under windows 7. Is there an alternative method for flashing Twrp recovery other than ABD?
Thanks
Dave
funkoot said:
I'm having the same issue with my Xperia X compact. Windows 10 says it's installed best driver for my device but in device manager theres a warning next to the driver and device is not recognised under ADB devices. I remember it being simple the last time I did it under windows 7. Is there an alternative method for flashing Twrp recovery other than ABD?
Thanks
Dave
Click to expand...
Click to collapse
unfortunatly, adb is the only way to install twrp.
the drivers (i attached) [from Sony by the way] need to be installed.
You need to install this driver/ file : android_winusb.inf
then boot your phone to fastboot (volume + [up] only) or with adb (adb reboot fastboot) and windows should detect "a new device" which (normaly) is called "android" with exclamation mark.
Tap "update driver"
Search on PC
select from list
ADB interface
Samsung Android ADB Interface is the driver you need to select for windows to detect the phone
And then theoretically it should work.
If that doesn't work, look if a USB port (either PC/Phone/Cable) is broken/damaged etc.