I've got an Xperia U (st25i) unbranded firmware 6.0.B.3.184, but my Windows 7 x64 doesn't show adb device at all, I have a working mtp device (that looks like it cannot be disabled). Same device works fine in adb on linux, even passing the usb device to a vmware machine with linux.
I've tried with Xperia_P_Xperia_U_Xperia_sola_drivers.zip and install PC Companion, but the adb devices still does not show, if I force add the adb interface from inf, windows 7 says it cannot start, there is same problem on windows 7 x86. Windows xp x86 instead automatically installs mtd devices but prompts for the adb device drivers, so I can give him the drivers. Any clue?
Make sure PC is connected to internet then connect the device in fastboot mode. Win7 downloads and installs drivers automatically.
Sent from my Blade using Tapatalk 2
Had the Same issue. Just Google for win7 64bit and xda. Sorry i have no Link. But Problem solved easy
Rapier07 said:
Make sure PC is connected to internet then connect the device in fastboot mode. Win7 downloads and installs drivers automatically.
Sent from my Blade using Tapatalk 2
Click to expand...
Click to collapse
I don't need fastboot drivers, just adb to develop, I'm always connected, but adb interface does not show at all in device manager, I don't have unknown/failed devices in device manager
sherpya said:
I don't need fastboot drivers, just adb to develop, I'm always connected, but adb interface does not show at all in device manager, I don't have unknown/failed devices in device manager
Click to expand...
Click to collapse
You have the "wrong" drivers installed. Use the drivers provided with c:\flashtool\drivers
-> then turn off internet on pc before connecting phone. <- prevents windoze from auto install via update
xperia mt27i
gazhead said:
You have the "wrong" drivers installed. Use the drivers provided with c:\flashtool\drivers
-> then turn off internet on pc before connecting phone. <- prevents windoze from auto install via update
xperia mt27i
Click to expand...
Click to collapse
The only driver windows automatically install is the mtd (that doesn't need internet because is in win), I don't have the device VID_0FCE&PID_5171&MI_01 but only VID_0FCE&PID_5171
It's a bit strange a common developer should download a non sony tool to develop with a sony phone
I had a similar problem with my XS, I get around it by enabling 'install PC companion' in connectivity settings under 'xperia'. Then when you plug the phone in, on your phone select install. It should then appear both as an MTP device the PCC installation, just cancel that latter.
I've used the wrong thread title, it should be x64 not x86, I've just verified that windows 7 32bit downloads and installs the adb driver, I had similar problem with gt7500 on windows xp 64bit, http://forum.xda-developers.com/showthread.php?t=1434319
I've solved modifying the inf file, I think I cannot change inf on windows 7 x64 because the driver becomes unsigned. Perhaps gt7500 works fine on windows 7
Heh... You stiill refuse to listen.
Install drivers provided with flashtool. Just doit and report back
mt27i
tested with internet disconnected and drivers pack in flashtool-0.9.1.0-windows.exe, same thing, windows shows only mtp device
check this out:
http://forum.xda-developers.com/showthread.php?t=1554632
more drivers:
http://www.mediafire.com/?2fxtdec2fxacux1
sherpya said:
It's a bit strange a common developer should download a non sony tool to develop with a sony phone
Click to expand...
Click to collapse
eeh.. its GOOGLE Android default tools. adb fastboot etc its all Android getit?
Request
thebrainkafka said:
Had the Same issue. Just Google for win7 64bit and xda. Sorry i have no Link. But Problem solved easy
Click to expand...
Click to collapse
Tell Me how Please....:crying:
I just solved this issue for my Xperia S.
Here are the steps:
1. Install driver on flashtool (I also install the pc companion)
1. On device manager, open the MTP device, and select reinstall device driver
2. Choose install the driver manually and list the compatible driver
3. It would only show one "USB Composite Device" for this device and install it
4. After the driver installed, the adb device just shows up!
Related
I'd like to simply connect the USB cable and connect to the device via ADB from my win7 x64 pc..
I've installed the latest set of USB drivers from the android SDK but am failing to update the driver since it says its not compatible with a windows x64 based system.
Anyone have any luck?
germanh said:
I'd like to simply connect the USB cable and connect to the device via ADB from my win7 x64 pc..
I've installed the latest set of USB drivers from the android SDK but am failing to update the driver since it says its not compatible with a windows x64 based system.
Anyone have any luck?
Click to expand...
Click to collapse
You need to install the Motorola drivers...that's the same for every phone. You need the drivers for the model phone you're trying to connect to.
hotleadsingerguy said:
You need to install the Motorola drivers...that's the same for every phone. You need the drivers for the model phone you're trying to connect to.
Click to expand...
Click to collapse
Ok thanks - was thinking i could use the generic one from the SDK but guess i can't. Thanks.
EDIT: confirmed that using the Motorola ones do the trick - and i can connect to the device using ADB without going into Media sync or Phone portal mode.
if you want to be even more fancy, install adbwireless on the phone, and you can do all the adb stuff over wifi.
Unfortunately doesn't work in the workplace for me
Hi there,
I got a really nasty problem here: when I connect my Sony Xperia T to my home computer, the ADB driver will be installed properly. When I connect the same phone to my work computer, Windows just doesn't want to accept the drivers. The following things are equal:
- USB debugging is always on on the phone
- Both computer are running Windows 7 64bit
- On both computers I am pointing the Windows driver installation at the same folder with drivers downloaded from Sony.
The thing that is different is the device ID that Windows reports in the Details dialogue from Device manager:
On the home PC it is:
USB\VID_0FCE&PID_5182&REV_0228&MI_01
USB\VID_0FCE&PID_5182&MI_01
On the other PC where things go wrong it is:
USB\VID_0FCE&PID_5182&REV_0228
USB\VID_0FCE&PID_5182
So it seems Windows is not recognizing the phone as a composite device (MI is it multiplexing identifier?). I double checked that USB debugging is always on and also rebooted Windows.
What could could be causing this strange problem?
Android version is 4.1.2 (original Sony firmware).
Thanks
Tom
You could search for the adb drivers for your phone on Sony's website, maybe they are available there
Sent from my Nexus 4 running Android 4.2.2
mihahn said:
You could search for the adb drivers for your phone on Sony's website, maybe they are available there
Sent from my Nexus 4 running Android 4.2.2
Click to expand...
Click to collapse
This is exactly what I did! Downloaded the adb driver from Sony's website. Installed them on one computer - works. Transferred exactly this driver package to the second computer with a USB Stick.
On the second computer, Windows does not find a matching driver for the same phone in the same driver package.
The reason apparently is that the phone reports a slightly different USB id when connected to the second computer (missing the MI at the end of the ID, see my original post).
today i reflashed my phone with stock 4.0.4 french ftf and it is working fine with usb debugging off but with debugging on, my computer doesnt see the phone! what should i do?
i have reflashed it but still usb debugging mode is not working! help! please what can the problem be?
plz help !
im stuck on stock! no root! nothing good!
First: Don't Panic.
Second: Check your drivers. If not properly installed, try one from sony (just google your device together with "adb driver").
Third: after a complete flash it's like you've never touched your device, means you have to re-root your device normally.
i hope this helps.
murderered said:
First: Don't Panic.
Second: Check your drivers. If not properly installed, try one from sony (just google your device together with "adb driver").
Third: after a complete flash it's like you've never touched your device, means you have to re-root your device normally.
i hope this helps.
Click to expand...
Click to collapse
no its not working!
ive installed a new windows on virtualbox but there also no usb debugging is working!
and how do you install the adb drivers in the zip?
even though it is in debugging mode..when i try to root, it says please connect your phone in debugging mode
Can't say if it generally works with virtualbox. try to get drivers for your native system.
So the question is now: What's your host system?
If it's Windows, get Flashtool and install included driver (found in <FlashtoolInstallDir>\driver) just for rooting the device.
If you're using linux you can look if your device was recognized properly with lsusb it should be listed there.
You can try it too in virtualbox, but i don't trust the USB-driver (i would not flash or so through it) and do not recommend it.
murderered said:
Can't say if it generally works with virtualbox. try to get drivers for your native system.
So the question is now: What's your host system?
If it's Windows, get Flashtool and install included driver (found in <FlashtoolInstallDir>\driver) just for rooting the device.
If you're using linux you can look if your device was recognized properly with lsusb it should be listed there.
You can try it too in virtualbox, but i don't trust the USB-driver (i would not flash or so through it) and do not recommend it.
Click to expand...
Click to collapse
i am using windows 7 32 bit
ive already have flashtool and have tried to install the drivers but nothing works!
Ok, you've installed (i assume) the right adb drivers for your device through the installer located in <FlashtoolsInstallDir>\driver.
So is there any Android/Sony (Ericsson) named device in your device manager? What does Flashtools write if you connect? If your device is listed in device manager, does it show an error, if yes which error?
murderered said:
Ok, you've installed (i assume) the right adb drivers for your device through the installer located in <FlashtoolsInstallDir>\driver.
So is there any Android/Sony (Ericsson) named device in your device manager? What does Flashtools write if you connect? If your device is listed in device manager, does it show an error, if yes which error?
Click to expand...
Click to collapse
in flashtool it shows the same thing in on and off
the 2nd one is debugging on and 3rd with off
Please post output of "adb devices" (if not recognizing, try again after "adb usb"). If no serial number/device is shown then do following:
There is a newer version of Flashtool available, update to 0.9.11, http://androxyde.github.io/
check after reinstallation (of drivers, too)
Maybe you have to try sonys driver from the zip. So extract them (all files).
right click at your device in the device manager
click to "update driversoftware" (or something like that, i don't have english windows)
click "search on my computer for new drivers"
choose from list
display all devices
click the button below the list (i have no idea what there could be written, it's not "windows update")
search for the inf-file extracted and choose the "sa<somenumbers>adb.inf"
if not already installing, choose "Sony Ericsson saXXXX ADB Interface Driver"
reboot (pc)
check again
I recently acquired an SGP312 from ebay and the seller upgraded it to 5.0.2 without anyone asking for it (it was supposed to be NIB now who knows).
I have not unlocked the bootloader but I did confirm it is locked and can be unlocked.
I'm trying to connect it to my PC so I can get it rooted but I'm running into issues with the device being recognized.
I installed the Android SDK USB drivers & copied over android_winusb.inf and fastboot appears to be working fine. Windowns (7) Device Manager, Flashtool, and the Sony flash tool (Emma) all see the tab.
However, none of the other connection modes appear to work.
Flash mode will initially connect with Flashtool but the the device disconnects:
31/037/2015 23:37:03 - INFO - Device connected in flash mode
31/038/2015 23:38:04 - INFO - Device disconnected
31/038/2015 23:38:21 - ERROR - Drivers need to be installed for connected device.
31/038/2015 23:38:21 - ERROR - You can find them in the drivers folder of Flashtool.
Device Manager shows an Other Devices with SGP312. I tried doing the Update Driver Software option with the drivers from the Sony developer site or the Android SDK drivers but no go.
I then boot up normally and connect either with or without ADB turned on and get the same Device Manager and driver results and PC Companion won't see the phone, either.
kadiir said:
31/038/2015 23:38:21 - ERROR - Drivers need to be installed for connected device.
31/038/2015 23:38:21 - ERROR - You can find them in the drivers folder of Flashtool.
Click to expand...
Click to collapse
Download this package of drivers and install properly (Tick Flashmode, Fastboot, Common Drivers Lagan, Xperia Tablet Z drivers).
Sorry, I forgot to mention I ran the flash tool driver utility in the flashtool\drivers directory and chose the first 2 options and the XTZ-specific option but I'll give that a shot and report back.
While I did see a driver I missed I have little change in results other than MTP in non-USB debugging mode attempted to install a driver and failed:
Windows encountered a problem installing the driver software for your device
Windows found driver software for your device but encountered an error while attempting to install it.
MTP USB Device
The system cannot find the file specified.
That reminds me that when I try to manually install the driver while in usb debugging mode it has the same message but with USB Composite Device where it says MTP USB Device.
I think I'll try this on my laptop as this PC had issues earlier this year with corruption that I thought I had fixed and I'm wondering if the corruption was more widespread than I thought.
kadiir said:
I think I'll try this on my laptop as this PC had issues earlier this year with corruption that I thought I had fixed and I'm wondering if the corruption was more widespread than I thought.
Click to expand...
Click to collapse
Seems to be this is an issue, because flashtool driver packages installed fine for me on WinXP/7/8.
Also pc-companion usually installs everything that is necessary for its fuctional, so must be OS problem.
Yep, that was it. Man, I should've checked that first. Sorry for the waste of time.
Quick question - do you know which ADB Interface I install from the SDK drivers? Is it ADB Interface or ADB Composite Interface? Or do I do 2 passes and install both?
Never mind - did some googling and got my answer. Thanks!
Hello when i put my Sony Xperia XZ1 in flash mode does not appear in my pc in the devices administration appears android and i ve installed all the drivers but dont work
Drivers installed:
Google USB Drivers
Android ADB Interface
Android bootloader interface
Sony sa0116 adb interface
android composite adb interface
Gordons Gate(i dont install because appears that the driver is not avaliable for x64 bits... and in the driver folder i have a dir named x64)
Help me please
Spaint3r said:
Hello when i put my Sony Xperia XZ1 in flash mode does not appear in my pc in the devices administration appears android and i ve installed all the drivers but dont work
Drivers installed:
Google USB Drivers
Android ADB Interface
Android bootloader interface
Sony sa0116 adb interface
android composite adb interface
Gordons Gate(i dont install because appears that the driver is not avaliable for x64 bits... and in the driver folder i have a dir named x64)
Help me please
Click to expand...
Click to collapse
If your os is windows 10 did you disabled the driver signature verification?
lilbrat said:
If your os is windows 10 did you disabled the driver signature verification?
Click to expand...
Click to collapse
yes :crying: