Anyonge successfully installed ADB/Fastboot drivers for their experias on Win 8 x64 RTM/Trial?
Because I tried:
- disabling driver integrity checks/ driver signing verifications
- installing xperia drivers from sony dev blog site
- installing drivers provided with latest flashtool
All failed - when connected my device is not recognized (even tho it shows ADB Android device in device manager with warning sign). Win7 works flawlessly.
Any advice/ideas?
Maybe there are. Use win7.
Cant u update drivers automatically using internet bro?
Sent from my X8 using Tapatalk 2
After few hours of struggle i managed to weed out the cause:
USB 3.0 and driver signature enforcement.
So I went into advanced boot option, disabled driver signature enforcement, plugged my phone to USB 2.0 port and VOILA, it works flawlessly
Related
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!
I was installing my Titan2 device on my Windows7 x64 desktop when downlaoding a podcast. It is a AMD system.
When I plugged in the Titan2, the installer started by now I keep gettings an error (!) givign a code 10 driver installation error.
Driver Error for Windows Phone 7 driver (under portable devices in device manager)
"This device cannot start. (Code 10)"
Every time I plug in my titan2 cable onto the PC, the driver attempts to install but always returns with this error. So basically Zune doesn't see my PC. The error (according to MS) seems to be a driver version issue. I can uninstall the device through the USB (connected devices) Eject Windows 7. It seems it doesn't recognize this is a Titan2. Any suggestions
ms driver
For Windows driver issues no matter which version of Windows or type of connected device, I would normally suggest uninstalling the driver through device manager if you have the original driver or can download it through Windows update, rebooting to be sure all the driver hooks are removed, then plugging your device back in and letting the driver be downloaded and installed fresh.
Good Luck!
mf2112
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).
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!
Please Help me to Solve This problem
My device is detecting in adb but not in fastboot mode This problem is there since I formatted the phone. My all drivers are updated. My oneplus nord 2 is Detecting in fastboot mode but Oneplus 9r Is not detecting
sorry to say that there is no fastboot and recovery mode on 9R... its broken
manualy install usb driver for unknown devices
I also had the same problem on 8T. It used to have no problem with the "Oneplus USB driver" on Windows10, I had it installed and it works great, but I upgraded to Windows 11 and got a driver problem. And it turns out my windows 11 said the driver from the Oneplus USB driver is unsigned, so disabling driver signature enforcement is necessary.
I really have no idea why it works on Windows 10 if it's unsigned, I didn't disable driver signature enforcement but it worked simply after installing the driver via the installer.
Anyway, disabling driver signature enforcement and manually selecting Oneplus_android_winusb.inf fixes the issue.
I followed this guide and solved my problem: https://www.droidwin.com/fix-android-device-not-showing-in-fastboot-mode/