Sony S1 Boot Fastboot Driver Download
Channing Rupnick
I am trying to flash Sailfish to Xperia 10 on Windows 10, bit I am not able to properly install fastboot drivers. I am using Xperia X driver as described in official manual. I even tried Xperia 10 II driver, bur without luck. I am on Windows 10 2004, as I have found it may be caused by this. Do you know how ro resolve it. Before I flashed in on Linux and it worked flawlessly. Thank you.
I have Windows 10 Pro v. 2004 and even after following the guide provided by Jolla/SailfishOS, I cannot get my PC to see my Xperia XA2 Ultra device when putting it in Fastboot mode. The guide mentions a problem with my version of Windows but if you got it working somehow using Xperia X drivers for your device, I should theoretically also be able to get my drivers installed.
Hello, guys! I am currently working hard on my Xperia S. I want to unlock my bootloader, but not ready yet because I CANNOT INSTALL S1Boot Fastboot manually for my Xperia S. I am confused why, because it should work. How can I install it then?
Are you using the amended driver found in your Fastboot folder on your C: drive under usb_driver - You need to manually point it to this folder to install the correct driver but be quick about doing it as your device manager will only show the problem driver untill it can't find the correct driver in the dfault location
Assuming you have installed Fastboot then you now need to open your device manager - There are several ways to do this but one way is to right click my computer or computer left click properties then on the left choose device manager or if using XP select the tab Hardware then device manager - Now look for a yellow sysmbol which means a missing driver this will only show up when you connect your phone in fastboot mode - When it does show up right click this then select update driver and choose the manual method which says something like let me choose the path etc - Then using the manual method direct it to that folder you downloaded, If all goes well it will begin the driver update and yellow sysbol will disapear - Fastboot mode will now be fully working
One of our developers got his development host machine updated to the 20H2 version of Windows 10, and after that happened the developer was no longer able to get step 4 above to work. Windows wasn't loading the Google USB driver when u-boot enumerated the USB gadget associated with Fastboot anymore. The obvious symptom was that Windows never "discovered" the new device when it was connected to the system.
It seems like that problem traces to the USB VID and PID that the u-boot USB gadget reports. We hadn't changed the default defconfig settings for "CONFIG_USB_GADGET_VENDOR_NUM" and "CONFIG_USB_GADGET_PRODUCT_NUM" from what they were in the distribution, and that seems to trace to a commit dating back to 2015. That commit sets the u-boot gadget VID to 0x0f25 which seems to be registered to "Netchip Technology, Inc", and PID to 0xA4A5 which would be a "Pocketbook Pro903" device.
I guess in retrospect the process outlined above did require us to manually install/update the Google USB driver the first time the Android device attached to a host. That manual installation of the driver associates the VID/PID u-boot enumerates with the Google USB driver. The problem seems to be that the new version of Windows 10 seems to no longer allow that kind of "Make this driver work with this device" kind of behavior to manually add VID/PIDs to the list that a device driver is known to support.
Our fix was to change the VID/PID to be something that is recognized by the Google USB driver. The reasoning was that once Android gets going, that USB port enumerates as a Google ADB device that is identified by Windows. So we should be OK to change u-boot so that when fastboot enumerates a device on that USB port it is the "bootloader" version of the same Google device.
The procedure described in the post mentioned below "MX8MM won't enter fastboot mode" was the way we got Fastboot to work originally, and it worked for months. Then the IT department pushed the Windows 10 20H2 update to some of our development computers. After that update on those computers, the solution described in that link doesn't work anymore. Also, we got a new guy who got a new computer with that version of Windows 10 installed on it and he couldn't follow the procedure either. So It seems like manually installing the driver doesn't work like it used to in earlier versions of Windows 10.
I'm guessing Microsoft decided that manually allowing a user to associate a driver with a device that the vendor didn't explicitly specify in the .inf file that's distributed with the driver was deemed a security issue.
I suppose one could try adding the VID/PID mentioned above to the .inf file that google distributes with the Google USB driver, to see if that allows the driver to work with a Netchips Technology Inc. (VID) Pocketbook Pro903 (PID) on Windows 10 20H2.
As a follow up to my suggestion to editing the .inf file that gets distributed with Google's Windows USB driver I'd like to say. That solution no longer works. I'm not sure how long ago I tried that trick with windows, but it must have been before Windows required all drivers be signed.
It is a known fact that updating FW using Fastboot fails in WIN10. We expect the NXP R&D team to solve this problem and provide a suitable fastboot USB driver for win10. After all, factories and ordinary people install Windows 10.
Once the file has been downloaded, install it on the device. If you are using a Windows computer, you must run the Sony Fastboot Driver to install the driver on your device. You can do this by opening the Device Manager and going to the File menu. Click on the corresponding entry for Sony drivers, and follow the directions on the window. If the process fails, restart the device and try again. You should now see the Fastboot drivers on your device.
After installing the Sony Fastboot Driver, you should install the Android SDK. This is a small debug tool that allows you to control the Sony I3113 (2019) from your computer. You can use this tool to modify your reflashing partition, update your recovery, and modify image zip files. You can also use the USB Driver to remove bloatware on your device. These tools are essential for a successful installation.
The Xperia XA2 and Xperia 10 do not have their own drivers, but there is a universal one available for most of the other devices. The Sony Fastboot driver is needed to recover your Sony mobile from the bootloader. The driver will allow you to use the ADB and USB ports of your device. Moreover, the drivers will allow you to flash stock firmware, data, and system files.
The Xperia series phones do not have dedicated drivers, but you can install the Sony drivers for all of them. Then, you can install them on all of your devices. This is an excellent way to fix a broken phone. Simply install the Sony Fastboot driver on your PC and it will be ready for you to access your device. This tool is free and works with almost all Android-powered smartphones. It is also available for all other Xperia models.
I found this, which isn't really universal since it defines a bunch of specific device IDs to identify them and is outdated anyway. There's also this pull request posted on that project's GitHub page and also another repo containing a dead link to already singed driver (or more precisely, signed INF that identifies ADB interface by the universal compatible ID).
So what are my options? Anyone found such a driver/INF that can be just installed and forgotten about or do I have to go the signing the modified android_winusb.inf with self-signed certificate route if I don't want to disable driver signature enforcement and such?
So far, my phone has used like 6 different device IDs to identify itself and under certain circumstances, I even have to re-install the official driver/INF for it to work again and confirming that I do want it installed, even if device ID doesn't match.
Thanks, I didn't look in system winusb.inf and manufacturer supplied INF must have been downloaded from Windows Update, placing the entry in Device Manager that usually appears under Universal Serial Bus devices under a different category, so I didn't realize it was already supported out-of-the-box.
I use Win10 versions 1809 and 1909 on my two machines. Depending on the software currently running on the phone, hardware ID differs, so who knows which is the "right" one. Vendor ID is always VID_0FCE, as should be.
That problem requiring re-install was actually encountered when putting the phone in fastboot mode. I suspect a conflict happened due to an old entry having a different compatible ID (adb vs fastboot and the fact that fastboot ID is missing from winusb.inf), but the same vendor and device ID. The ID when in fastboot mode is constant, but otherwise it seems to depend on the OS running, even though it should be constant as well as long as we're talking about the same phone model, in this case Xperia E3.
I did some cleaning up in Device Manager and removed two drivers that were downloaded from Windows Update for ADB, so now I have phone's entries under Universal Serial Bus devices, not under some custom categories like before. I also added USB\Class_FF&SubClass_42&Prot_01 ID to the list of Prevent installation of devices that match any of these devices ID group policy, so the OS won't try "updating" them. Manually installing ADB Device through update wizard in Device Manager while phone is in fastboot mode also works and makes it visible to fastboot utility.
The device ID when in fastboot mode is VID_0FCE&PID_0DDE, so that *.inf couldn't help the OS detect it as compatible with the driver. But you can still set it for use with fastboot mode by manually selecting it in driver update wizard.
It's good that at least for ADB mode, it works out of the box either way. Though by default settings, OS might still see fit to download "drivers" from Windows Update, even though no specialized driver is usually involved since it's all just about the .inf file identifying and setting up the device to be driven using winusb.sys.
c80f0f1006