Hi all ... I am trying to load DoomLord's boot IMG (ready to load a new ROM) and for some reason when I plug into USB (with UP volume) my computer can't recognise the Sony ADB Interface. It recognises the "Sony ADB Interface" as "Found New Hardware" then when I try to select the Sony drivers it says it can't match it and fails when you finish.
I have installed Flashtool and all the drivers, in addition to downloading the latest from the Sony website. I even right click on the .inf files and install them direct but still Windows doesn't want to recognise my phone!
The ADB command prompt waits for a device to be connected, I assume because Windows has not recognised the Sony ADB Interface.
Any ideas? It has all worked previously, when I first rooted the device.
(note, running Windows XP)
Related
hello guys, just bought that amazing watch today i have an issue. How can i connect it to my pc ? I plug in the usb, while sm3 is off. Win7 start to install and at the end it fails because of the drivers. So my pc doesn't recognise it. I can only see the "empty" E:/ Disk. Any suggestion ?
edit: unistalled the "watch" and then plugged in again and drivers get istalled. Now i have a "sony file-cd usb gadget" . help me pls
edit: wrong section :/ sorry
I have exactly the same problem.
i installed the Google USB Driver from theAndroid SDK Manager and also installed the Sony PC Companion. But the Smartwatch 3 still shows in the device manager under "other devices" without installed driver.
The only way i could connect to it is using ADB over Bluetooth which is really slow.
Anyone any idea?
i used these adb drivers http://download.clockworkmod.com/test/UniversalAdbDriverSetup6.msi
after installation, i went to device manager, update drivers, search pc for drivers, choose from a list of...., and then i selscted adb testing interface version 3.12.0.0
i had to skip the warnin popup, but adb is working fine
Thank you a lot.
i could not find any "adb testing interface" so i installed "Google Nexus 7 ADB Interface" from the list and so far it seems to work with that too.
Not sure why you have such a testing interface driver.
Did this HERE and no driver problem for me.
Drivers can be found in this folder : Program Files (x86)/Sony/Sony PC Companion/Drivers/
The Driver used in the bootloader is a different one. I have no issue there.
But it seems there is no actual ADB Driver used when the device is in normal operation mode for debugging apps or pushing apps directly over ADB on to the device.
Pixel XL (Verizon) Not Being Recognized via "ADB Devices" command on Windows 7.
So I got my 128gb pixel xl from Verizon today. It's still 7.1.0 (Build NDE63P) so I want to unlock the bootloader asap. I was able to get the phone booted up and mostly set up without taking the OTA update (I pulled sim card before booting the phone for the first time, and I skipped the wifi setup).
I intended to follow the instructions here to use dePixel8 to unlock the bootloader. I got USB debugging enabled on my phone, and ABD/Fastboot installed on my computer (Windows 7 laptop). The problem is the phone doesn't come up in the list when I use the "adb devices" command from the command prompt within the SDK folder. Looking at the device manager, it appears my laptop is automatically installing the "Google Nexus ADB Interface" driver for the phone, is this not the correct driver? I downloaded the USB drivers from here and tried pointing the Device Manager at them to force a driver update, but the device manager tells me the drivers are already up to date.
Can someone please explain to me how to get my computer (Windows 7) to recognize my phone via ADB so I can push dePixel8 and unlock the bootloader? I feel like I'm so close to being able to unlock the bootloader, but my phone not being recognized via ADB is driving me freaking crazy.
Thanks!
EDITED TO ADD: If I turn off USB debugging, and just put the phone in File Transfer mode when connecting via USB, it never shows up in Windows Explorer as any kind of storage device, which would make me think its a problem with the driver, right?
That link has the wrong Fastboot ADB version. Use this one
https://developer.android.com/studio/releases/platform-tools.html
TonikJDK said:
That link has the wrong Fastboot ADB version. Use this one
https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
Thanks for the prompt reply. I'm currently uninstalling Android Studio and SDK I downloaded, and will install the one you linked.
I think this is still a problem related to the driver Windows 7 is automatically installing for my phone. If I turn off USB debugging, and just put the phone in File Transfer mode when connecting via USB, it never shows up in Windows Explorer as any kind of storage device, which would make me think its a problem with the driver, right?
Yesterday i got my zuk z2 plus 64gb. I installed adb driver on pc & enable usb debugging from zuk z2 plus. I connect my phone to pc, Grant the usb debugging permission, extract the adb setup, shift button & write click. Now the cmd is open. When i enter "adb devices", my device is not showing.
I always use something called 15 Second ADB Installer when setting up ADB and Fastboot on a new computer. It installs all the correct drivers as well, so maybe that would solve your issue. Also, be sure to check Device Manager in Windows and see whether there are any devices showing with yellow caution symbols besides them.
If you find your phone displaying like this; right-click and choose 'Update driver', then 'Browse my computer for driver software' and 'Let me pick from a list of available devices on my computer'. Find Google Inc. and choose the one which says 'Android ADB Interface'. You have to do this AFTER running the 15 Second ADB Installer otherwise it won't work.
Definitely driver related, remove and reinstall etc but don't give up haha sometimes its a PITA to install the correct drivers...
satya365 said:
Yesterday i got my zuk z2 plus 64gb. I installed adb driver on pc & enable usb debugging from zuk z2 plus. I connect my phone to pc, Grant the usb debugging permission, extract the adb setup, shift button & write click. Now the cmd is open. When i enter "adb devices", my device is not showing.
Click to expand...
Click to collapse
Download MIFLASH TOOL, it installs all the drivers needed for Z2
Hi
I want to flash a system through Flashtool to my Xperia Z1 Compact. I've installed the drivers and connected the phone in flash mode. But Windows says that "USB device is not recognized". In devices manager the Xperia is showed as "Unknown USB Device (Device Descriptor Request Failed)". I tried to connect to another usb ports or with other usb cables. I also tried to update drivers of USB Hubs (by clicking on them and selecting Update driver). I also tried to install the drivers straight from Sony Developer Site. I also installed Xperia Companion. Nothing helps.
Repairing software via Xperia Companion is impossible because of that.
I tried to install drivers again for at least 5 times. After that installer says this:
Sony (WinUSB) sa0109AdbDeviceClass 05/13/2013 2.0.0010.30018 - Ready to use
Sony Net (5/13/2013 6.0.6000.16501 - Not need (no devices to update)
Google, Inc. (WinUSB) AndroidUSBDeviceClass (12/06/2010 4.0.0000.00000 - Ready to use
Sony Mobile Communications (ggsomc) USB (11/10/2014 3.1.0.0) - Ready to use
It's weird because my other Xperia (Xperia L) is recognized without any problems.
Is there any solution to that problem other than installing a clean copy of Windows?
Computer Specification (maybe useful):
Windows 10 Home 1803 64-bit
AMD Ryzen 5 2600
GeForce 1060 Ti
AsRock B450 Fatl1ty Gaming K4
8 GB RAM
I installed drivers on Windows 10 as well. When I connected the device and entered in the power shell
Code:
./adb.exe devices
it answered: "List of devices attached", "daemon started successfully" and showed my device.
With
Code:
./adb.exe reboot bootloader
I put it in fastbood modus and the problems began.
If I understand correctly, that's the same state, you were in.
My solution was that the driver for fastboot was wrong. I downloaded an updated version for fastboot from Sony Website.
The driver was unsigned, therefor I had to go into Windows UEFI (new Bios) to enable installation of unsigned drivers... (at own risk)
When I installed this second driver, the device was recognised in power shell, when I typed in commands with:
Code:
./fastboot.exe
and also with flashtool.
Hey there, same problem with my Ryzen system as well. Something with the motherboard drivers or the USB drivers that are not updated to work with these new boards.
As you explained, adb and fastboot works, but flashmode detection is broken.
Flashmode still gets detected on my Surface Pro 4 and ThinkPad T450s.
Hello,
I am trying to unlock my bootloader but I my computer (Windows 10) does not recognize fastboot.
When I connect to fastboot (holding volume up button + connecting my phone by USB when it's off, or using the adb reboot fastboot command), the computer does not recognize the phone. I then tried installing drivers (both from Google and Sony) by going into device manager but Windows just doesn't install the drivers.
I then saw this on Sony's website:
Fastboot driver - Sony Developer World
developer.sony.com
So I download the file and pasted it instead of the same file (android_winusb.inf) in the Google driver folder, and it somewhat worked, but Windows said something like unable to find drivers for ADB.
I also tried to install in Windows test mode but to no avail.
No matter what I tried, entering the command fastboot devices in fastboot mode does not give me any output (not even "waiting for device").
What am I doing wrong?
Thank you!
TheeWolf said:
Hello,
I am trying to unlock my bootloader but I my computer (Windows 10) does not recognize fastboot.
When I connect to fastboot (holding volume up button + connecting my phone by USB when it's off, or using the adb reboot fastboot command), the computer does not recognize the phone. I then tried installing drivers (both from Google and Sony) by going into device manager but Windows just doesn't install the drivers.
I then saw this on Sony's website:
Fastboot driver - Sony Developer World
developer.sony.com
So I download the file and pasted it instead of the same file (android_winusb.inf) in the Google driver folder, and it somewhat worked, but Windows said something like unable to find drivers for ADB.
I also tried to install in Windows test mode but to no avail.
No matter what I tried, entering the command fastboot devices in fastboot mode does not give me any output (not even "waiting for device").
What am I doing wrong?
Thank you!
Click to expand...
Click to collapse
Did you already disable driver signing? Pretty sure you have to do that with Win 10. I would disable driver signing, and then use " 15 second adb installer" from XDA. Always has worked for me...