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
Related
Solution:
If you were like me, you couldn't get ADB working no matter what you did with the drivers. As it turns out, I was plugging it into a USB 3 port on my motherboard. I have the USB 3 drivers installed, but there seems to be an adb issue with USB 3 ports. be warned, my issue is now fixed (I probably don't even need them bootleg drivers either). Thank You XDA.
Alright, so I just picked up a Galaxy Nexus (coming from Thunderbolt) today only to find out that my sdk will not detect my phone in adb devices. Now, I have the Thunderbolt and Eris working fine with it, but the NExus seems a little stubborn. Here are the steps I have taken:
1. Plug in phone, wait for win7 (x64) to install all the drivers... Success
1a. MTP and PTP both installed, using MTP for the rest.
2. Turn on debugging on my phone one more driver... Success
3. Went to the GNex Samsung support page to download and install that driver... Success
4. Go into Device Manager, everything is A-OK, drivers all happy
5. Open up my sdk prompt and type adb devices and 1 device is found, offline
6. Type it in again, nothing, maybe a glitch?
So there is nothing wrong in Device Manager, no Windows Updates, SDK works fine, but no device under adb devices. This is honestly the strangest thing ever.
If you have any special instructions regarding drivers, please be specific, stating "update your driver" doesn't really help.
Oh, and this is my first post I believe.
Update your drivers :laugh:
Right Click the "Android" option and select Update Driver. Choose to "Browse My Computer" and "Let Me Pick From A List." Pick the Samsung driver with the newest date and install it.
Srsly though...
If that doesn't work...try the PDAnet option.
My sig has a link.
Install PADnet and plug your phone in.
Then check that the new driver is the one in use.
@ OP, did you restart your PC after installing the drivers? If not, that may cause an issue. As well, you could always restart the ADB daemon. Type:
adb kill-server
adb start-server
As for drivers, I personally would not recommend using any package that installs crapware other software along with the driver (such as the PDA drivers). Chance are if the package comes with an .exe extension, it contains other software. 1wayjonny has packaged the driver by itself here. Those are clean drivers with nothing extra to cause any issues. I recommend those, but (as with anything that works well) you need to manually install it, i.e., right-click on the device listed in Device Manager and select update, and browse to the location where you unzipped the driver. This needs to be done TWICE: once when your device is booted in fastboot mode, and once when booted normally.
efrant said:
@ OP, did you restart your PC after installing the drivers? If not, that may cause an issue. As well, you could always restart the ADB daemon. Type:
adb kill-server
adb start-server
As for drivers, I personally would not recommend using any package that installs crapware other software along with the driver (such as the PDA drivers). Chance are if the package comes with an .exe extension, it contains other software. 1wayjonny has packaged the driver by itself here. Those are clean drivers with nothing extra to cause any issues. I recommend those, but (as with anything that works well) you need to manually install it, i.e., right-click on the device listed in Device Manager and select update, and browse to the location where you unzipped the driver. This needs to be done TWICE: once when your device is booted in fastboot mode, and once when booted normally.
Click to expand...
Click to collapse
Noob question, but how do I install those drivers?
epicrevolt said:
Noob question, but how do I install those drivers?
Click to expand...
Click to collapse
Is that a joke?
efrant said:
[snip]
As for drivers, I personally would not recommend using any package that installs crapware other software along with the driver (such as the PDA drivers). Chance are if the package comes with an .exe extension, it contains other software. 1wayjonny has packaged the driver by itself here. Those are clean drivers with nothing extra to cause any issues. I recommend those, but (as with anything that works well) you need to manually install it, i.e., right-click on the device listed in Device Manager and select update, and browse to the location where you unzipped the driver. This needs to be done TWICE: once when your device is booted in fastboot mode, and once when booted normally.
Click to expand...
Click to collapse
Alright, so I have done the following:
Uninstalled all Samsung Drivers through Device Manager
Unplugged phone
uninstalled those official Samsung drivers for the GNex (available for download on their site)
Plug phone back in, both MTP and Nexus unknown
install the 1wayjonny driver... Success (It's now under Android Device in Device Manager)
adb still doesn't work... f*ck
reboot phone into fastboot (vol +/- & power)
install 1wayjonny driver... success
fastboot device recognized by 'fastboot devices' and commads work.
I believe the issue is with the MTP device as it is not recognized so therefore I can't access the phone storage. So far the only way I can get MTP working is by using the official Samsung driver, but that overrides the ADB driver by 1wayjonny (no way around it, even through uninstallation and choosing the 1wayjonny driver, Samsung one is more 'recent').
In the attachment you can see that the MTP device has no driver and therefore is unavailable.
Thank you so much for the help so far.
UPDATE: MTP Driver downloaded through Windows Update, divice still not showing up in adb. Actually when I first run adb devices after kill-server it finds the device as offline, but as soon as I type 'adb devices' again, it's gone. poof.
Hello,
I have searched the forums and Google, and was not able to find anyone else with this issue, so here I am.
I'm on Windows 7 x64 with a stock Canadian Galaxy Nexus 4.0.1 (yakjuux.)
I am trying to install GNex Toolkit and am unable to get past the first step. No matter what I try to do, any time I plug in the phone, it installs the default drivers.
Device installation settings are set to "never install drivers from Win Update." Phone is in development mode, I have removed Google Nexus from my devices (and checked the "delete drivers" box, though it doesn't even appear anymore), there is nothing for Samsung in Programs and Features, I have used USBDeview and there is nothing for Samsung/Nexus. I've tried using PDANet to no avail (I get error 103). I tried using "uninstall drivers" with GNTK, no dice (it seems to just remove a registry entry).
Any other ideas on how to make my PC install the drivers I want and not the default ones?
Thanks.
Read part A of this post.
efrant said:
Read part A of this post.
Click to expand...
Click to collapse
I have read that entire post and Bourne-nolonger's guide. Instead of showing up as "Android 1.0" device in Device Manager, my phone always shows up as Galaxy Nexus, with no yellow triangles or any other issues. (Yes, developer mode is enabled, and it seems to make no difference to how my computer responds.)
From Bourne-nolonger's guide:
"As soon as you enable this Windows will pick up a new device and it will attempt to install a driver - this will fail (or hopefully it will)." - mine never fails, it always installs drivers from somewhere. When I attempt to install new drivers to the Google Nexus device using UNK 0.7, Windows tells me that I already have the newest drivers.
Should I be restarting my PC after every install/uninstall of drivers? That's the only thing I can think of....
Scarf Face said:
[snip]
Should I be restarting my PC after every install/uninstall of drivers? That's the only thing I can think of....
Click to expand...
Click to collapse
Absolutely.
Here is the sequence I followed:
- phone plugged in
- USB debug mode on
- uninstall phone from Device Manager
- USB debug mode off
- uninstall phone from Device Manager
- reboot
- reconnect phone, it installs with no problems
- enable USB debug mode while plugged in
- phone installs again, exactly like the previous time, with Galaxy Nexus in Portable Devices
So it appears my computer doesn't care if it is in USB debug mode or not. It sees them as two separate devices/states of device, but installs the same drivers for both.
edit: tried doing the same in fastboot mode; the Device Manager recognized it as Fastboot mode, but did not let me install the proper drivers, saying that I already have the newest ones.
Scarf Face said:
Here is the sequence I followed:
- phone plugged in
- USB debug mode on
- uninstall phone from Device Manager
- USB debug mode off
- uninstall phone from Device Manager
- reboot
- reconnect phone, it installs with no problems
- enable USB debug mode while plugged in
- phone installs again, exactly like the previous time, with Galaxy Nexus in Portable Devices
So it appears my computer doesn't care if it is in USB debug mode or not. It sees them as two separate devices/states of device, but installs the same drivers for both.
Click to expand...
Click to collapse
This is what I would do:
1) Unplug your device from your PC.
2) Go into Device Manager and in the View menu at the top, select show hidden devices.
3) Uninstall every driver related to the GNex/Samsung/Android/etc.
4) Reboot your PC.
5) Make sure your Device Installation settings are set to never download drivers from Windows Update (as per bourne-nolonger's post).
6) Make sure USB Debugging is enabled in your GNex's settings.
7) Plug your GNex into your PC.
8) In device manager you should see Android 1.0 with a yellow "!". Right-click on that and update the driver from where you downloaded 1wayjonny's driver.
9) Reboot your device in fastboot mode.
10) In device manager you should see Android 1.0 with a yellow "!". Right-click on that and update the driver from where you downloaded 1wayjonny's driver.
efrant said:
This is what I would do:
1) Unplug your device from your PC.
2) Go into Device Manager and in the View menu at the top, select show hidden devices.
3) Uninstall every driver related to the GNex/Samsung/Android/etc.
4) Reboot your PC.
5) Make sure your Device Installation settings are set to never download drivers from Windows Update (as per bourne-nolonger's post).
6) Make sure USB Debugging is enabled in your GNex's settings.
7) Plug your GNex into your PC.
8) In device manager you should see Android 1.0 with a yellow "!". Right-click on that and update the driver from where you downloaded 1wayjonny's driver.
9) Reboot your device in fastboot mode.
10) In device manager you should see Android 1.0 with a yellow "!". Right-click on that and update the driver from where you downloaded 1wayjonny's driver.
Click to expand...
Click to collapse
Done, with no luck: instead of Android 1.0, I get a normal GNex install; with fastboot I did get it to show Android 1.0, and installed Samsung Galaxy Nexus Fastboot Interface using the downloaded drivers.
When I am uninstalling GNex from Device Manager, it never asks me to delete the driver as well; it asked me once and I can't get it to do that again. With fastboot, it did ask me, and that seems to be the only difference in the process.
Scarf Face said:
Done, with no luck: instead of Android 1.0, I get a normal GNex install; with fastboot I did get it to show Android 1.0, and installed Samsung Galaxy Nexus Fastboot Interface using the downloaded drivers.
When I am uninstalling GNex from Device Manager, it never asks me to delete the driver as well; it asked me once and I can't get it to do that again. With fastboot, it did ask me, and that seems to be the only difference in the process.
Click to expand...
Click to collapse
At least you got the fastboot driver installed properly.
I'm out of ideas for the ADB driver though.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
At least you got the fastboot driver installed properly.
I'm out of ideas for the ADB driver though.
Click to expand...
Click to collapse
Seems to be a problem with my PC, so I will try it with a different machine. Thanks for your help!
Ignore this. Wrong thread.
Hi Guys,
Any help would be great! i do have google talk if anyone is willing to help me out!
My R800i Is rooted and has a version of recovery but not sure which version, i am wanting to update my phone with a better kernel and rom since the current one i have installed is giving me issues ( not being able to receive incoming calls for example )
Another problem is i reformatted the phone since i was having issues with receiving calls but now when i connect my phone to ANY computer via the USB cable the computer trys to install MTP or MSC driver ( depends on which connection type i select ) the Installer fails and i cant even take any files off my phone.
Provided details below. i want to somehow get into the current bootloader and install the ROM thats on my SD card! i do have flashtool installed and Android tool SDK installed but still no success in phone wanting to talk to my laptop.
I am running windows 7 64 bit. i am starting to think the phone is belond repair since i cant get any software to work between the phone and computer.
does anyone know what buttons i need to push on the Xperia Play to enter into the boot loader, i have tried pressing the back button and search button on phone boot but nothing happens apart from the phone starts up normally.
would a factory reset delete the boot loader and other config-ed software off the phone is this why i cant enter the boot loader or am i not pressing the right buttons on boot.
Any help would be really appreciated!
IMEI:
357302043579712
IMEI Software Verson
49
Available Speech Codecs
HR, FR, EFR, AMR_HR, AMR_FR
Working Bands
GSM850, GSM900, GSM1800, GSM1900, UMTS_BC1, UMTS_BC8
Rooting Status Bootloader Unlocked Allowed: Yes
Phone Software Version
1245-8821_4.0.1.A.0.283
S1 Boot Version
1241-3656 R9A021
EST Software Version
1242.5099_10
Android Version
2.3.4
Baseband Version
8x55A-AAABQMAZM-203028A-49
Kernel Version
2.6.32.9-perf
Build Number
4.0.1.A.0.283
If you want to change the kernel you must unlock your bootloader. If your Xperia Play is a SIM free one, you can do it for free in this link: http://unlockbootloader.sonymobile.com
For SIM locked devices I think you must find another ways to do it. There are some online sites that unlock bootloader to SIM locked devices for a fee.
Once you have unlocked your bootloader, turn off the phone, hold on the search button, plug the USB cable in the computer, release the search button (power button LED will be blue) and install this driver: http://drivers.softpedia.com/progDownload/Google-USB-Driver-Revision4-Download-139077.html
Now you are ready to flash any kernel you want with Flashtool or any other app.
Thanks for the information, i have already done this, i payed £25 for a guy on this forum to unlock my phone to any network. i'll give this a try and get back to you, problem is the phone doesn't like to talk to my laptop via USB cable keeps on failing to install the drivers..
Thanks for quick response.
PsychoShaft said:
Thanks for the information, i have already done this, i payed £25 for a guy on this forum to unlock my phone to any network. i'll give this a try and get back to you, problem is the phone doesn't like to talk to my laptop via USB cable keeps on failing to install the drivers..
Thanks for quick response.
Click to expand...
Click to collapse
I have tried what you said but having problems with connecting my phone to my Windows 7 Laptop!
Check your device manager. The fastest way to open it is running this command: devmgmt.msc
There must be some kind of Android device while your phone is connected in fastboot mode. If you see it, update its driver with the Google USB driver v4 pointing at the folder path with the uncompressed files.
jcarbox said:
Check your device manager. The fastest way to open it is running this command: devmgmt.msc
There must be some kind of Android device while your phone is connected in fastboot mode. If you see it, update its driver with the Google USB driver v4 pointing at the folder path with the uncompressed files.
Click to expand...
Click to collapse
Hi I tried what you said, i Turned off my phone and holded the search button and turned it back on, the light went blue and the computer popped up trying to install fast boot i point to the SDK folder to update the driver but it fails.
do you have google talk might be easier on there to talk! cheers!
I'm not using gtalk atm. Sorry.
Be sure the driver you downloaded is named usb_driver_rev4.zip: http://drivers.softpedia.com/dyn-postdownload.php?p=139077&t=4&i=1
If Windows doesn't detects any driver in that uncompressed folder, you can choose to select the device from a list, point to that folder and force to install the driver. It's named something like Android ADB Interface.
jcarbox said:
I'm not using gtalk atm. Sorry.
Be sure the driver you downloaded is named usb_driver_rev4.zip: http://drivers.softpedia.com/dyn-postdownload.php?p=139077&t=4&i=1
If Windows doesn't detects any driver in that uncompressed folder, you can choose to select the device from a list, point to that folder and force to install the driver. It's named something like Android ADB Interface.
Click to expand...
Click to collapse
Thanks for the download link, i going to try this in a bit and get back to you! thanks for the support guys! :good:
Just tried, i put my phone into Media Transfer Mode.. my computer tried to install the MTP usb device and i directed the installation to the driver you linked..
Update Driver Software says: the best driver software for your device is already installed MTP USB DEVICE, there is a small yellow triangle on the icon and in MTP USB Device Properties it says: This device cannot start. (Code 10)
i need someone to Teamviewer with me, for the record i don't have the Sony Ericsson software installed on my Computer because that still wont install the drivers for my phone, i also know its not needed for installing new kernel and roms.
i tried connecting this phone to a bunch of pcs including my friends and it still fails to install any drivers!!! i think i am just going to bin this phone! i have had enough (
You must install that driver when you plug the phone in fastboot mode. It shouldn't work in any other case. In other words, when you plug your Xperia Play being powered on and Android is running it needs one driver, and when you boot it in fastboot mode you need other driver.
Please, install the driver following the steps previously posted with your phone in fastboot mode (blue LED).
Hello, i put my phone into fastboot mode, my device manager shows 1 device not installed S1Boot Fastboot, i right click go to properties and click update driver...
then i browse my computer for driver software i point the location to usb_driver_rev4\usb_driver and it says: Windows was unable to install your s1Boot fastboot!
Ok, let's see...
Try to update the driver using the "choose from a list" option to force the installation, point to the driver folder and select "Android ADB Interface" from the list. If Windows shows a warning message don't worry about it and go ahead.
i tryed this and its not wanting to work (
Sorry to hear that because I don't have any more ideas for your problem.
Maybe you may spend some minutes searching in the forum to find some detail that can help you.
i need someone with teamviewer to help me go though the setup process again, if anyone is willing to get my phone working i will happy pay them some money!
Thanks Jcarbox for all your support!
Regards
Paul
I just check the Windows device manager with my phone plugged in bootloader mode and it appears as Android Bootloader Interface, so this is the device you must choose from the list when you install the driver.
Hope this helps you.
thanks for the help, to bad my phone isnt having any of it.. just going to buy another phone (
This may work
PsychoShaft said:
thanks for the help, to bad my phone isnt having any of it.. just going to buy another phone (
Click to expand...
Click to collapse
hi PsychoShaft,
I had similar problems. I don't know how to fix it permanently. but i do this to make it work for some time.First, download flashtool and install it.Open your device manager and select view->show hidden drivers.Then, delete all your drivers related to xperia play. like the adb interface, semc flash ,etc. All of them in all categories. then reboot your computer into safe mode with administrator and connect your device with flashtool running in your windows in safe mode. then the flashtool will indicate that you don't have the drivers. then,open the drivers folder in flashtool and use the setup to install arc-play-...,flashmode drivers and fastboot mode drivers.then after the installation is over windows will ask you to reboot.now reboot with your mobile connected. after boot windows will automatically install the drivers. then unplug your phone and turn off it and connect in flash/fastboot mode.it will automatically install drivers.wait for windows to say drivers installed successfully or installation failed. don't unplug it in the middle of the process then you will have to start from first.sometimes it will not work in the first time ,then reboot into safe mode and try again installing the drivers and rebooting into safe mode itself and connecting your device.at one point of time flashtool will say your device is connected in flas/fastboot mode.then continue with flashing
Gladwin.
Thanks for the support guys i managed to solve the issue!
^^^^ Glad i could help
Sent from my GT-I9300
What type of drivers are there for the S3?
I understand that you need drivers installed on the computer for it to reecognize the S3
How many driver are there?
Are there any more aside from this?
Where can i download these drivers?
I think ADB has a driver for thisas well?
Thanks!
mikoal said:
What type of drivers are there for the S3?
I understand that you need drivers installed on the computer for it to reecognize the S3
How many driver are there?
Are there any more aside from this?
Where can i download these drivers?
I think ADB has a driver for thisas well?
Thanks!
Click to expand...
Click to collapse
Here is the link to the Driver package for i747 and i747m (AT&T/Bell/Rogers/Telus) With this, you don't need Keis...unless you want to use Keis. Also, TRY a WINDOWS UPDATE after installing this driver package.
I found their to be side issues on my Win7 and XP pc's....too long a story. If you have issues, I will send you a link.
themadproducer said:
Here is the link to the Driver package for i747 and i747m (AT&T/Bell/Rogers/Telus) With this, you don't need Keis...unless you want to use Keis. Also, TRY a WINDOWS UPDATE after installing this driver package.
I found their to be side issues on my Win7 and XP pc's....too long a story. If you have issues, I will send you a link.
Click to expand...
Click to collapse
Thanks mad producer. Is this driver package all the drivers I'll need?
I noticed these drivers are from the samsung site.
Are there any custom drivers or drivers for rooted phone, on custom roms etc?
Are there different kinds/type, I recall reading about ADB drivers or ADB connections.
Can you also send me the link to the issues with the drivers?
Thanks a bunch!
mikoal said:
Thanks mad producer. Is this driver package all the drivers I'll need?
I noticed these drivers are from the samsung site.
Are there any custom drivers or drivers for rooted phone, on custom roms etc?
Are there different kinds/type, I recall reading about ADB drivers or ADB connections.
Can you also send me the link to the issues with the drivers?
Thanks a bunch!
Click to expand...
Click to collapse
If/when you need ADB (I don't use it) then just look around for ADB. I don't have a link for that.
When I first connected my S3 to my Win7, XP, 2nd XP machine, each one had an issue with the MTP protocol. This is what's used to transfer files to and from phone internal and external storage. I did my homework and massive experimenting and solved the issues. (pretty pathetic really) I just don't have a turn key absolute solution but here are some tips. Try one or all of these till it works...and it WILL!
(Backup your PC before attempting and use at your own risk)
XP
- plug your Ss in via usb
- install the samsung drivers
- after any/each of these steps, unplug/replug usb S3 to PC
- check Device Manager in XP for any Yellow exclamation marks. If there are none, then go see if you can transfer large files (eg mp3) to your S3 and back via USB
- if you can then your done
- if not, download this and install
- if it's still not working, (which I doubt) then update windows. After the Samsung drivers are installed on some windows machines, windows updates provides a specific update that helps. I watched it happen/work on 2 machines.
- still not working, get ready....sounds crazy...but install Windows Media Player 11. It is tied into the MTP framework somehow. This is the version I used
Win7
- plug your Ss in via usb
- install the samsung drivers
- after any/each of these steps, unplug/replug usb S3 to PC
- check Device Manager in Win7 for any Yellow exclamation marks. If there are none, then go see if you can transfer large files (eg mp3) to your S3 and back via USB
- if you can then your done
- if it's still not working, (which I doubt) then update windows. (remember to unplug/replug usb after.
- install wmp11 or higher
- if it's still not working, try this file (sorry...can't elaborate on it)
- STILL NOT WORKING...doubt it...but last chance, download this file and place it into c/windows/inf directory and reboot.
Anyone got P8000 to detect correctly in Windows 10?
At first my W10 refused to install driver package cause of driver signing, which was expected,
so i restarted W10 in mode without driver signing and run through the installation without problems.
Still nothing at all happends though when i connect my P8000 via USB to computer...
* Checked USB cable and port
* Checked that USB debugging is on in Dev-options
Suggestions? Anyone else tried?
I experienced the same. It seems like the P8000 requires an additional driver when it connects in off-mode. Never found a solution for it in Win10, so I used an old computer with Win7. That worked like a charm
I got the drivers working on Windows 10. I'm not quite sure what steps are needed but these worked for me:
-Download and install the driver package. The Drivers where extracted to the specified folder, but Windows wasn't able to install them.
-Reboot the PC.
-Open the device manager and plug the P8000 in while it is off.
-Under other devices, there should be an entry called MT65xx Preloader. Click on it and select "Update drivers"
-In the following window, select "Browse for driver software" and browse to the folder where the drivers where extracted in the first step.
-Confirm the selection and the warning message.
After this, you should get a message that Preloader USB VCOM was installed and flashing should work.
P.S: Now, what would also be interesting would be flashing with linux. But I don't think this is possible yet.
restarted W10 in mode without driver signing, installed again, restarted, connected phone when it's on, connected phone when it's off... Not sure what made the difference but now it's working
sharkware said:
restarted W10 in mode without driver signing, installed again, restarted, connected phone when it's on, connected phone when it's off... Not sure what made the difference but now it's working
Click to expand...
Click to collapse
Where can I download the drivers?
dgdeivid said:
Where can I download the drivers?
Click to expand...
Click to collapse
http://en.lmgtfy.com/?q=elephone+p8000+root+tutorial
sharkware said:
I can´t quote URL
Click to expand...
Click to collapse
I downloaded P8000 drivers from many different sites but many sites are malware or are general drivers tools or drivers make error when install, Could you indicate where you downloaded the drivers to have a link here that we know it works?
dgdeivid said:
I downloaded P8000 drivers from many different sites but many sites are malware or are general drivers tools or drivers make error when install, Could you indicate where you downloaded the drivers to have a link here that we know it works?
Click to expand...
Click to collapse
Why don't you download directly from Elephone??
http://bbs.elephone.hk/forum.php?gid=269
sharkware said:
Why don't you download directly from Elephone??
Click to expand...
Click to collapse
I assume you're referring to these
"SP_Driver_v2.0.rar"
I install and get the next error:
h t t p : //s27.postimg.org/pk8ig719t/Sin_t_tulo.png
I restarted W10 in mode without driver signing, did "not" istall any drivers and flashtool was working perfect.
P8000 drivers
dgdeivid said:
Where can I download the drivers?
Click to expand...
Click to collapse
I tried many drivers but none worked, finally this driver worked for me:
h t t p : // w w w .mediafire. com/download/5ff6s5bk1couva9/Compelte+USB+Drivers%2BPDanet%2BAdb+Installer.rar
From the above rar, I installed: "Universal Android USB Driver\Universal ADB DRiver.exe" and it worked fine.