Sony Fastboot Drivers
Beatrix Gerke
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.
I'm helping out a friend with rooting Xperia play, I spent 5 hours trying to root it yesterday with him and we couldn't. We tried gingerbreak and z4mod but they did not work, so we tried the fastboot way and I can't seem to get the drivers installed properly.
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.
Xperia Manufacturer offers Emma to flash a device.
Emma dosn't use fastboot mode, flashmode is used instead.
Emma does use a Gordons Gate driver ggsomc.sys, signed by 'Sony Mobile Communications AB'.
-devices/get-started/flash-tool/download-flash-tool/
It looks like clearing old entries in Device Manager that was setup by INF file that came with those drivers from Windows Update, deleting said drivers, setting up fastboot device entry using device update wizard and picking built-in ADB Device helped with the issue of the said device entry for fastboot mode being reset under certain circumstances.
Now one could argue I should not have accessed the testing menu in the first place, but the phone was getting a bit warm at the back and I wanted to check the temperature. I had forgotten where to look exactly so I looked around a bit and once I saw "radio band" I was curious which options would appear.
After selecting "radio band" only one choice popped up "USA band". Now had I not been still a bit stressed from a phone call and been a bit too tired, I might have figured out that I should have pressed anywhere outside the button, but, PLEASE, if there is only one option, how can it be a wrong one way street?
I had to backup the phone, factory reset it, restore the data and recreate all my settings and app icon arrangements. I couldn't choose the firmware I had been happy with but had to jump to 157 (with unknown consequences). I had issues with some applications which updated to newer versions without my approval so some saved game states won't load back anymore. Luckily, I could revert to an older version of Chrome which does not ignore bookmarks placed on the homescreen (why do bugs like that not get fixed? But I digress). I had to find a workaround for my phone being unable to pair with my PC anymore and luckily I found an answer on this forum.
Fortunately, I anticipated that my app icons won't reappear at their previous positions despite the fact that I tried the phone back up and a PC companion backup, and had taken pictures of my home screens before the factory reset.
I appreciate that a testing or a service menu must be approached with caution, but even experienced technicians make mistakes from time to time. AFAIC, there should be no way (I'm sparing you the expletives here) to essentially render your phone useless with one touch of a button
2. Extract the rom file and identify the modem file namely NON-HLOS.bin (in the unlikely event of having a different filename, figure out what the .bin files contain using google search and copy and use the file that has the modem band information instead of the mentioned file)
@siddharth I just signed up to this Sony forum for only one reason. To thank you Your solution (the first one) worked even though my mobile make is different (Swipe Elite Plus).
Guys,
Follow Siddharth's guideline and you should be able to save yourself from ending up with a brick phone or having to explain to that mobile service person why we selected the USA band in the first place!
just make sure to do the following before you input those commands in the command window:
1) Make sure to install " Android ADB Interface" Driver for your mobile.
2) Make sure to install "Android Bootloader Interface" Driver (also called "Fastboot driver") for your mobile.
The "fastboot erase" commands will NOT work if you do not install the fastboot driver. In other words, if this driver is not present, the "fastboot erase modemst1/st2" commands will just keep waiting in an infinite loop. It will just say and will not proceed with deleting the modemst1 or modemst2 folders in our phone that were created when we stupidly selected the USA band
So make sure you do that. Below is a tutorial I stumbled upon, that would help you install the above 2 drivers. The tutorial is pretty long, overdrawn and the suggested software occupies a lot of space. But we can always uninstall these unwanted software (JDK and Android Studio) once we have executed the commands outlined by Siddharth and as soon our phones are back to normal.
Tutorial --> How to Set Up ADB and Fastboot with Android SDK on Windows 7 & Windows 8
-to-set-up-adb-fastboot-with-android-sdk/
Note: During the fastboot driver installation process (page 3 of the tutorial), if you are unable to get into your phone's "fastboot mode" even after pressing and holding down combinations of volume and power buttons, just make sure you have the "ADB interface driver" mentioned above all set and that the command prompt command "adb services" correctly returns your device number as described in that tutorial. Then, just key in the first command alone, which is:
adb reboot bootloader
This command sends instructions to your phone that puts it in "fastboot mode" or "bootloader mode", which is essential for:
1) Installing the fastboot driver
2) Executing the "fastboot erase modemst1/st2" commands in the command prompt window.
I'm in the same situation after my nephew wanted to show a trick (the testing menu), and pressed United States by accident as well. I only found out the issue hours later when i became unreachable and couldn't call myself as well.
2) Instead of trying out the commands in the Minimal ADB and Fastboot folder (by launching the Minimal ADB and Fastboot tool), please make sure you are trying them out in the platform_tools folder instead, and without launching the Minimal ADB and Fastboot tool. Just do a "shift key+mouse right click" from inside of the platform_tools folder and select "open command window here".
c80f0f1006