Xperia Flash Tool Driver
Etienne Levic
hello.
I have a question about Emma. in the website, sailfish talks about downloading Emma if we want to go back to androidOS , but when downloading Emma, Sony doesnt allowed you to use it if you are not a professional??? so how we should do it then?
For completeness on the issue of flashing, I guess we should note that there are flash tools other than Emma which can be used, e.g. Xperifirm/Flashtool (could provide links but would prefer the more experienced to do this if demanded.)
Be aware that for Emma, it is the DOWN Vol. button , not the UP one, like when you flash SF.
The light should be green.
When you plug the phone like this, does Windows signal something? It should beep or display a message that the phone is found.
Im not sure but gonna try it anyway. If it doesnt work with seller I will try to sell that phone anyway so flashing to android is necessary? Or maybe someone want to buy it? Is there an official WTS WTB sailfish forum section?
When I connect my XA2 to the computer via Volume Down nothing sounds and the device is not displayed via USB either. Only in the device manager it says SOMC Flash Device. Then I install Emma and Emma recognizes my XA2 directly. It offers me the option for a firmware update and software update content erase for Android versions 8 and 9 respectively.
After the update to marshmallow i am facing problems with wifi and mobile network signals. I have to stand near the router to use the internet and another problem is that xperia is not detected by pc companion. I tried 3 usb cable and it only charges, i have tried enable usb debugging option and updated drivers. Everything was fine in lollipop. This is update is buggy and i have seen others facing wifi issues as well. Please fix these issues soon.
As you said that using pc companion would fix this issue,but it didn't. I powered off my phone and pressed volume down button then connected the cable the light went from red to green. I have another xperia that too worked fine last week. Its on lollipop and even my other xperia m4 doesnt connects to pc excepts it only shows charging. I tried enabling debugging mode as well. I tried 3 usb cables and xperia only charges. Maybe its a software issue. Its not allowing the connection between the pc and phone. Still i am facing problem in wifi,its having the range problem. Is there a fix?
I downloaded the xperia flashtool and downloaded all drivers including sony pc companion, nothing worked. I have two m4 aqua one is updated to 6.0 and has the issues stated above and other one is on lollipop. Last week i was tranferring my files and mtp was working in windows 10 and pc companion detected my phone, i did receive windows update in between but i don't know if it has anything to do with this, now the lollipop version and marshmallow version are not being detected at all. I am not sure if its the device or my laptop problems i tried all ports and tried 3 different cables and today i tried it on my other pc having windows 8.1. Is there still a way to fix it or should i take it to repair center because i am facing a lot of problem due to less wifi and mobile signals.
i turned on the enable usb debugging mode but still no response. There is an option in developer mode called select usb configuration. Whatever i select i comes back to charging only,sometime it shows media tansfer protocol but the pc never detects any of my devices, what should i do?
I installed adb drivers again by disabling driver verification, re installed flashtool, pc companion and other drivers, still no response. I tried safe mode as well in xperia and nothing worked. The last time i repaired my other xperia using pc companion was connecting fine until this week when i re connected to check for problems. I believe there is a software problem because the device and pc don't communicate at all. I have attached a screenshot, whenever i connect to my pc using usb it shows ac charging.
Recently, well actually two days back when I installed Flashtool on my Windows 8 Laptop in order to flash my cutie pie, Xperia Ray phone ? I ran into a massive issue. After successfully installing Flashtool setup I headed up to installing flashtool drivers. I selected the needed drivers from the list and executed with the process, but then suddenly the driver installation results had failed at the end. I tried running as Admin, restarting the Lap and I even downloaded the whole set up once again, which was pretty much retarded until i realized the issue and reinstalled the whole thingy. But still NO ! -_-
To install all the drivers for the Windows operating system, you download the software Easy Driver Pack for Win8 x64 at download here (Chinese version), after downloading, run the .exe file. For other Windows versions, you accessed at and search by keyword Easy Driver Pack
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.
I experienced the same problem a couple of days ago and managed to solve it. Just make sure you chose the two Xperia Z2 drivers, Flashmode and fastboot drivers, and the "Common drivers Shinano board" when installing flashtool drivers. If the problem persists, just install all the drivers.
It is that time of the year again, where we have a major Android release and people want to update as soon as possible. We have received numerous requests from Xperia Z3+ and Z5 owners asking how they can manually update to Android 6.0 Marshmallow, using third-party utilities Flashtool and XperiFirm.
Disclaimer: Please read the following instructions thoroughly before attempting to flash your phone. Xperia Blog absolves itself from any responsibility should something go wrong. Please proceed with caution and at your own risk.
Note: You will not void the warranty of your Sony Xperia device by flashing new firmware using this guide. In addition, you do NOT need to unlock your bootloader nor do you need root to flash your handset.
It is recommended that you create a backup of your existing regional/carrier firmware just in case you need to send your device back for repair. The instructions below can be used to create any firmware file, so use these to create a backup with the relevant firmware build.
One of the primary reasons people encounter problems in flashing their device is due to not installing the correct drivers on their computer. Please ensure that drivers for your Sony Xperia device and Flashtool software are correctly installed on your PC before attempting to install new software.
c80f0f1006