Noob here!
I cant find android developement driver for xperia m c1904!!
Installing the latest PC Companion doesnt help.
where can i get the drivers from??
thnx in advance!
I have here adb driver packed in, but if you are using Windows 7/8/8.1 you need first to disable Driver Signature Verification. Here is the link to show you how you do it:
http://www.howtogeek.com/167723/how-to-disable-driver-signature-verification-on-64-bit-windows-8.1-so-that-you-can-install-unsigned-drivers/
So after that, you normally install provided drivers, and I also provided a archive that contains extracted adb program, so you don't need to instal Andorid sdk.
Here is donwload link: https://www.mediafire.com/?j9xjn79lm3jkyv5
Hope I helped you
Hope hs answer helps... And just to add questions shouldn't be in the general section. We have a Q&A section for em
Sent from my C1905 using XDA Premium 4 mobile app
aleksa069 said:
I have here adb driver packed in, but if you are using Windows 7/8/8.1 you need first to disable Driver Signature Verification. Here is the link to show you how you do it:
http://www.howtogeek.com/167723/how-to-disable-driver-signature-verification-on-64-bit-windows-8.1-so-that-you-can-install-unsigned-drivers/
So after that, you normally install provided drivers, and I also provided a archive that contains extracted adb program, so you don't need to instal Andorid sdk.
Here is donwload link: https://www.mediafire.com/?j9xjn79lm3jkyv5
Hope I helped you
Click to expand...
Click to collapse
thanks, i will try too for my mikocok 8 64bit
Signed ADB drivers for Xperia M only come with very recent builds of PC Companion (even FlashTool 1.3 doesn't have this drivers currently). I managed to get only them from a local install, download the attached file and run DPInst.exe (or DPInst64.exe if running 64-bit OS). With this package you don't need to disable driver signature enforcement, they work out of box in Windows 8/8.1...
mbc07 said:
Signed ADB drivers for Xperia M only come with very recent builds of PC Companion (even FlashTool 1.3 doesn't have this drivers currently). I managed to get only them from a local install, download the attached file and run DPInst.exe (or DPInst64.exe if running 64-bit OS). With this package you don't need to disable driver signature enforcement, they work out of box in Windows 8/8.1...
Click to expand...
Click to collapse
Hello,
PC companion works well and detect my phone but does not install any adb drivers...
I can't find ADB drivers for this phone anywhere where did you found these?
thank you.
Hey, just to add to the list of answers, here is an adb drivers installer. All you have to do is open the programme, plug in your phone and press install, then you are done.
Here is the download: http://adbdriver.com/downloads/
Hedzx said:
Hello,
PC companion works well and detect my phone but does not install any adb drivers...
I can't find ADB drivers for this phone anywhere where did you found these?
thank you.
Click to expand...
Click to collapse
I got from a PC Companion update. Make sure you have the latest version of PC Companion or reinstall it to fix that...
paper13579 said:
Hey, just to add to the list of answers, here is an adb drivers installer. All you have to do is open the programme, plug in your phone and press install, then you are done.
Here is the download: http://adbdriver.com/downloads/
Click to expand...
Click to collapse
Unsigned drivers = major headaches to install in Windows 8+ since it'll accept only signed drivers unless you disable driver signature enforcement first (and M$ make that process more complicated in Windows 8+ than before)
mbc07 said:
I got from a PC Companion update. Make sure you have the latest version of PC Companion or reinstall it to fix that...
Unsigned drivers = major headaches to install in Windows 8+ since it'll accept only signed drivers unless you disable driver signature enforcement first (and M$ make that process more complicated in Windows 8+ than before)
Click to expand...
Click to collapse
Lol, what are you on about. Please explain to me, what do you mean by unsigned drivers. I used that programme on windows 7 and the drivers work perfectly for me.
paper13579 said:
Lol, what are you on about. Please explain to me, what do you mean by unsigned drivers. I used that programme on windows 7 and the drivers work perfectly for me.
Click to expand...
Click to collapse
As I assume you've already worked out drivers can come in two forms, signed and unsigned.
Signed drivers are generally ones coming from manufacturers and have a valid signature bundled in with them.
Unsigned drivers are generally ones coming from external sources (like flashtool) and do not have a valid signature bundled with them or they don't have one at all.
In Windows 7 there is slight driver enforcement, when you try to install unsigned drivers a window pops up telling that they are unsigned and that you shouldn't install them. You still have the option to install them.
In Windows 8, 8.1 and 8.1 Update 1 there is strict driver enforcement. When you try to install an unsigned driver with driver enforcement on, it will fail. When you turn the driver enforcement off (which is a pain to do) and then try to install an unsigned driver you get the pop up window telling you that the driver is unsigned and that you shouldn't install them, you still have the option to install them however.
I hope this explains it for you.
ADB driver not recognised by Flashtool
paper13579 said:
Hey, just to add to the list of answers, here is an adb drivers installer. All you have to do is open the programme, plug in your phone and press install, then you are done.
Here is the download: [not allowed to post links]
Click to expand...
Click to collapse
I'm trying to revert to 4.2.2 from 4.3 to root my Xperia M dual 2005 that I received brand new today. I have spent four hours trying to get Flashtool to recognise that the phone is in USB debugging mode. It definitely is - USB debugging (and nothing else) is checked in Developer Options, USB connectivity is set to Mass Storage (not MTP) and installing from unknown sources is enabled in Security.
When I connect the phone powered up, this is what Flashtool shows:
10/051/2014 22:51:23 - INFO - <- This level is successfully initialized
10/051/2014 22:51:23 - INFO - Flashtool Version 0.9.16.0 built on 19-04-2014 19:00:00
10/051/2014 22:51:24 - INFO - This is the first sync with devices on github. Renaming devices to devices.old
10/051/2014 22:51:24 - INFO - Cloning devices from github project
10/052/2014 22:52:06 - INFO - Devices sync finished.
10/052/2014 22:52:13 - INFO - Device connected with USB debugging off
10/052/2014 22:52:13 - INFO - For 2011 devices line, be sure you are not in MTP mode
10/052/2014 22:52:22 - INFO - List of connected devices (Device Id) :
10/052/2014 22:52:22 - INFO - - USB\VID_0FCE&PID_619B&MI_01\7&4CF9BF6&0&0001 Driver installed : true
10/052/2014 22:52:22 - INFO - - USB\VID_0FCE&PID_619B&MI_00\7&4CF9BF6&0&0000 Driver installed : true
10/052/2014 22:52:22 - INFO - - USB\VID_0FCE&PID_619B\YT910S4WK6 Driver installed : true
10/052/2014 22:52:22 - INFO - List of ADB devices :
10/052/2014 22:52:22 - INFO - - none
10/052/2014 22:52:22 - INFO - List of fastboot devices :
10/052/2014 22:52:22 - INFO - - none
But the notification area on the phone shows "USB debugging connected"!!!!!
To flash, I know I have to disconnect and turn the phone off, choose the .ftf then start the flash procedure (preparing files). Then when the animated graphic comes up, I press the volume down button and re-plug the USB cable back into the phone. Nothing happens - no lights on the phone, no flash starts, nothing. This is regardless of whether I keep the vol down button depressed for ages, or let it go after a few seconds.
I'm sure I have the ADB driver installed. I have the latest version of Sony PC Companion. I tried the ADB_Nicky method above from mbc07, using "have disk" and the driver seemed to install no problem. To double check I downloaded the file from the link given above by paper13579 and it detects the phone as a Sony Ericsson, and says the ADB drivers are already installed. I have also uninstalled the device in DM and restarted the PC and reinstalled the driver. Clip of Device Manager attached (as it appears when the powered-up phone is plugged in). Nothing appears in Device Manager when I try the flash procedure as above (phone off, vol down depressed).
I have been using Windows 7 Ultimate 32-bit, and (in desperation) XP SP3, with the same results. I've tried different USB cables (known good). I don't know what to try next.
@zumtotal, ADB drivers are different from flashmode drivers. Turn off your phone, hold Vol Down and plug USB. Go to device manager and see if you have a "SEMC Flash Device". If it show up with an exclamation mark or don't show at all, try reinstalling PC Companion or selecting "Have Disk" and then pointing to PC Companion folder in Program Files...
Please note that while in flash mode, if the phone doesn't receive any answer from the host computer within 2 minutes it'll automatically disconnect and restart the phone in normal mode, so, after plugging the phone while holding volume down you'll have approximate 2 minutes to do the driver install...
Completed
mbc07 said:
@zumtotal, ADB drivers are different from flashmode drivers. Turn off your phone, hold Vol Down and plug USB. Go to device manager and see if you have a "SEMC Flash Device". If it show up with an exclamation mark or don't show at all, try reinstalling PC Companion or selecting "Have Disk" and then pointing to PC Companion folder in Program Files...
Please note that while in flash mode, if the phone doesn't receive any answer from the host computer within 2 minutes it'll automatically disconnect and restart the phone in normal mode, so, after plugging the phone while holding volume down you'll have approximate 2 minutes to do the driver install...
Click to expand...
Click to collapse
Thanks, mbc07, your answer helped. To cut a very long story short, I made two mistakes:
1. When I first enabled USB debugging on the phone I didn't have any data connection enabled (neither wifi nor sim). So when I connected the powered-up phone to the PC the phone didn't install the USB debugging feature properly. After I got data enabled, more installation took place, and eventually Flashtool recognised my phone correctly and saw that it was in debugging mode.
2. I didn't pull out and re-insert the battery to get the phone into flash mode (that is not included in Part 1 of paper13579's instructions in the main 4.3 rooting thread). So when I connected the powered-off phone with the vol down depressed I could see that nothing changed in Device Manager. After I pulled and replaced the battery, the phone was recognised as SEMC Flash Device and the driver installed.
Simple mistakes but they cost me hours. Hope this helps someone else.
mbc07 said:
Signed ADB drivers for Xperia M only come with very recent builds of PC Companion (even FlashTool 1.3 doesn't have this drivers currently). I managed to get only them from a local install, download the attached file and run DPInst.exe (or DPInst64.exe if running 64-bit OS). With this package you don't need to disable driver signature enforcement, they work out of box in Windows 8/8.1...
Click to expand...
Click to collapse
This works
great!! I will try this in win 8.1
Hi All
I have a retarded problem with the ADB drivers for my Xperia S.
When i enable USB Debugging and i connect it Windows 7 64bit laptop i am unable to get the adb driver for my phone to work. The computer doesnt detect and install the ADB drivers for my Xperia S.
After manually installing the driver the computer keeps saying that "The Device Cannot Start (Code 10)". The drivers that i installed were from the Sony website.
But the strange problem is on another Windows 7 32bit Laptop and a Windows XP Desktop, Device Manager automatically detects and installs the ADB driver for my phone. Ive tried disabling driver signature enforcement and reinstalling the drivers but it still has the " This device cannot start problem"
Any ideas?
itsbighead said:
Hi All
I have a retarded problem with the ADB drivers for my Xperia S.
When i enable USB Debugging and i connect it Windows 7 64bit laptop i am unable to get the adb driver for my phone to work. The computer doesnt detect and install the ADB drivers for my Xperia S.
After manually installing the driver the computer keeps saying that "The Device Cannot Start (Code 10)". The drivers that i installed were from the Sony website.
But the strange problem is on another Windows 7 32bit Laptop and a Windows XP Desktop, Device Manager automatically detects and installs the ADB driver for my phone. Ive tried disabling driver signature enforcement and reinstalling the drivers but it still has the " This device cannot start problem"
Any ideas?
Click to expand...
Click to collapse
Try installing the drivers with Flashtool
Tried it. Still has the same problem
Sent from my iPad using Tapatalk
I have a Oneplus 3, and after I updated my laptop's Windows 10 to the new Anniversary Update (I'm not sure what's the reason, so I mentioned this, just in case), it fails to recognize the MTP option when I connect the phone to my laptop. Although, it is able to recognize the phone in P2P (Photo Transfer) mode and wholly recognizable on my Ubuntu on the same laptop and other Windows laptops/PCs apart from mine.
I tried updating the driver software from the Device Manager but it shows the following error:
Code:
Windows found driver software for your device but encountered an error while attempting
to install it.
[MTP Device Symbol]
A service installation section in this INF is invalid.
Thank You
When clicking on the "Driver update" find Android device, and MTP. There should be 2 options. Select an option, and if it isn't working, select the other. Hope i helped
Has anybody gotten the Sony's official usb drivers to work? Its somewhat mandatory for xperifix et all.
I tried it on 2 completely different machines.
On win7 x64 box the driver complains about Error 10 - This device cannot start.
On a win10 enterprise thinkpad the error is similar:
"This device cannot start. (Code 10)
The specified request is not a valid operation for the target device."
I am starting to suspect that the drivers are faulty. FWIW the thinkpad has NEVER seen *ANY* adb/android/sony drivers before.
This is the "Sony sa0118 ADB Interface Driver" btw. Installed as a legacy device as per Sony's instructions. Driver is already not working before a device is connected. Device is subsequently also not recognized. Device works perfectly fine in flash mode on my Linux notebook, just not both windows boxes Ive tried (sadly Windows is required for Xperifix)
You use the drivers that comes with flash tool? Those are working for me without any trouble on Win10
juandiazmora said:
You use the drivers that comes with flash tool? Those are working for me without any trouble on Win10
Click to expand...
Click to collapse
tried these and they got me a little further - but not very. On first connect of the xz2c in "blue" mode Windows said something along the lines of configuring new device: Android. So far so good. Then started xperifix, which found the device and started to get device information during which it crashed (program got stuck, no .NET exceptions or anything). Now even 2 reboots later the phone is no longer recognized, I assume xperifix somehow borked up the fastboot drivers?
PS: the constant more often than not non-working recaptchas are getting a little annoying..
The drivers have to be installed in testmode on Windows 8-10. In Windows 7 it should work "out-of-the-box". And yes, I know I'm answering to one year old question, but it could be helpfull to someone one day. Maybe.
My Oneplus 3 isn't detected on fastboot. I'm using Samsung drivers and I already tried Google Drivers.
AfonsoOnXDA said:
My Oneplus 3 isn't detected on fastboot. I'm using Samsung drivers and I already tried Google Drivers.
Click to expand...
Click to collapse
If it's an OP 3 then why are you using Samsung drivers? You need OnePlus drivers, obviously. I always followed this guide (exactly like it says) and never had an issue with my drivers so far.
This is from an OP 8 group, but the drivers should be the same:
To install the drivers, ensure that driver signature verification is disabled. Instructions:
How to Disable Driver Signature Verification on 64-Bit Windows 8 or 10 (So That You Can Install Unsigned Drivers)
64-bit versions of Windows 10 and 8 include a “driver signature enforcement” feature. They’ll only load drivers that have been signed by Microsoft. To install less-than-official drivers, old unsigned drivers, or drivers you’re developing yourself, you’ll need to disable driver signature enforcement.
www.howtogeek.com
OnePlus USB (all purpose/data transfer):
OnePlus-USB-Drivers.zip
drive.google.com
Google USB driver (for fastboot & ADB):
Extract all files to the same directory. Right click on android_winusb.inf and select install
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
Qualcomm drivers (for MSM):
Choose top option (WWAN-DHCP)
Qualcomm_Drivers_Setup.exe
drive.google.com