Win10, in fastboot mode the device cannot be found, but it can be found in adb. I installed drivers from Sony's website. In fastboot mode the device manager shows under 'other', in adb it is normal and shows 'Sony sa0116 ADB interface driver'. As far as I know the driver is the same for adb and fastboot...my Pixel is recognised with no problem, only this Sony...anyone knows how to get it recognised in fastboot mode?
Sorted the driver issue... didn't install it properly...
Go to Windows device manager look for one called x-boot or android (your xperia) and open the driver details.
Klick update driver and next choose look for software on computer. Next window gives you the option to pick one of common devices. Install the sony driver for adb interface.
Could give a zip of it if needed.
After the manual driver update it should recognize your phone immediately - if you have checked the "fastboot devices" prompt before just repeat that (no reboot or reconnection necessary)
Win 10 seems to have problems. I downgraded to win 7 all sorted.
I'm having the same issue with my Xperia X compact. Windows 10 says it's installed best driver for my device but in device manager theres a warning next to the driver and device is not recognised under ADB devices. I remember it being simple the last time I did it under windows 7. Is there an alternative method for flashing Twrp recovery other than ABD?
Thanks
Dave
funkoot said:
I'm having the same issue with my Xperia X compact. Windows 10 says it's installed best driver for my device but in device manager theres a warning next to the driver and device is not recognised under ADB devices. I remember it being simple the last time I did it under windows 7. Is there an alternative method for flashing Twrp recovery other than ABD?
Thanks
Dave
Click to expand...
Click to collapse
unfortunatly, adb is the only way to install twrp.
the drivers (i attached) [from Sony by the way] need to be installed.
You need to install this driver/ file : android_winusb.inf
then boot your phone to fastboot (volume + [up] only) or with adb (adb reboot fastboot) and windows should detect "a new device" which (normaly) is called "android" with exclamation mark.
Tap "update driver"
Search on PC
select from list
ADB interface
Samsung Android ADB Interface is the driver you need to select for windows to detect the phone
And then theoretically it should work.
If that doesn't work, look if a USB port (either PC/Phone/Cable) is broken/damaged etc.
Related
Hi all,
I was having a strange problem with my USB dropping out when using the NEWER recovery (TWRP and Philz). Which meant I couldn't push files via ADB or Sideload. Here is my solution....
Before starting
I am using Windows 7
Download Google USB driver
Make sure you have TWRP 2.7.1.1 loaded as your recovery
You may have slightly different devices show up maybe, but this is what mine showed...
Open device manager
Plug phone in and power up to bootloader
Device manager should show 'Android Device' or similar
Open recovery
**This is where my USB was dropping out**
Make sure TWRP 2.7.1.1 loads
Look at device manager and should show 'One Mini' with a yellow exclamation mark
I tried updating the drivers automatically and browsing to the Google USB folder that we downloaded above but just kept saying 'device driver loading failed'.
The only way I found worked was
Right click 'One Mini' and update driver
Browse my computer for driver software
Let me pick from a list of device drivers
If you have Android device listed click that, if not choose Portable device.
Click 'Have disk' and locate the Google USB Driver folder and should be able to load the .inf file.
Click from the list ADB USB device and click ok.
This should load your device and install properly.
You shoud now be able to use ADB and Sideload in Recovery now.
Let me know if this works or not as there are a couple of bits that I can't replicate as the driver is already there!
I've been at this the entire evening, but can't seem to get it to work.
I installed the latest driver package (https://github.com/koush/UniversalAdbDriver) which should make W7x64 accept my NexS in fastboot mode. But it doesn't. All other modes are recognized, but in fastboot it keeps saying "Android 1.0" with that yellow exclamation mark on it.
I also tried the "have disk..." option and fed it the "android_winusb.inf", but it said this wasn't compatible with x64. What else can I try?
How to Install ADB and Fastboot: Method 1
To quickly and easily install ADB and Fastboot on your Windows XP, Vista, 7, and 8/8.1 computer (32-bit and 64-bit), do the followingownload the latest*ADB Installer file*(adb-setup-1.4.2.exe).Right-click the file*adb-setup-1.3.exe*and choose “Run as Administrator“.Type “Y” and press Enter to install ADB and Fastboot, and set the environment variables. Enter “N” if you don’t want to do the same and want to just install the drivers.In the next step, enter “Y” to install the drivers for your device. Enter “N” to skip this step.Wait till the driver installation finishes up. That would take only some seconds.To verify that you have successfully setup ADB and fastboot, open up a command prompt (press*Windows key + R*-> type in*cmd*->*OK) and enter “adb version” (without quotes). If it returns something like “Android Debug Bridge version x.x.xx“, then your ADB and Fastboot are all-ready.Congrats! You are ready to rock!Read more at http://dottech.org/21534/how-to-ins...m8Vo3.99QUOTE=Lex_Michdeandroid;56140163]I've been at this the entire evening, but can't seem to get it to work.
I installed the latest driver package (https://github.com/koush/UniversalAdbDriver) which should make W7x64 accept my NexS in fastboot mode. But it doesn't. All other modes are recognized, but in fastboot it keeps saying "Android 1.0" with that yellow exclamation mark on it.
I also tried the "have disk..." option and fed it the "android_winusb.inf", but it said this wasn't compatible with x64. What else can I try?[/QUOTE]
Hi There.
I've been trying for the past couple of days to root my Oneplus One. I started with this tutorial: (http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471) which is featured in the FAQ (which I've read through) and I've gotten stuck at one location.
You can test fastboot by connecting your device to your PC while booted into fastboot mode (power + volume up) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
Click to expand...
Click to collapse
The ADB command appears to be working, but when I boot into fastboot mode (and when I'm not in it as well), the PC does not detect the phone. I've tried connecting it to multiple USB ports, and I'm using the official Oneplus One cable, so I'm at a bit of a loss of what to do.
However, I feel like I've identified where the source of the error is. If you see here: (http://i.imgur.com/IE1Bxjs.png), you can see that the phone is being detected under Portable Devices. In all of the tutorials I've looked through so far, it's been detected under something like "Android Phone" or "ADB Interface". I've tried various things to fix this, the most common of which is installing drivers onto/for the phone. I've tried the one here: (http://forum.xda-developers.com/showthread.php?t=1413293), which I know is for Archos phones, but should work similarly, as I tried both the Universal ADB driver and the Google one, from the SDK Manager. I kept getting an error telling me that: "the folder you specified doesn't contain a compatible software driver for your device."
I've also tried the one here: (http://www.makeuseof.com/tag/android-wont-connect-windows-adb-fix-it-three-steps/) (let me know if external links aren't allowed and I'll remove it.) This doesn't seem to work either, as I get this error (http://i.imgur.com/CLATXsl.png) when it tells me to:
If you cannot get any driver to work, you will need to force installation. Instead of choosing “Let me pick from a list of device drivers on my computer” in the previous step, you will choose “Browse for driver software on your computer” and manually find the directory where you installed Koush’s drivers.
The location on your hard drive looks something like this:
C:\Program Files (x86)\ClockworkMod\Universal Adb Drivers\
Windows will then install the drivers. From now on, whenever you connect the Android device with debugging enabled, Koush’s drivers will load in place of the ones that failed to work.
Click to expand...
Click to collapse
And now I'm posting here, praying that someone will have some sort of idea what to do. Any help at all would be greatly appreciated,
Fappled
EDIT: Managed to get it working, messing around with the drivers in device manager while in Fastboot mode seemed to work.
Fappled said:
The ADB command appears to be working
Click to expand...
Click to collapse
Feel your pain, I've been thru some pain myself with some weird issue, posted here yesterday. Though, my issue is different from yours, I have some ideas for you.
You say that adb works, so I assume your usb cable & PC are OK here.
I aslo assume that your Device Manager screenshots taken when connected to your phone in device mode (rom running). Don't worry about what you see in Device Manager just yet. Your goal is to make fastboot work, right. Note: Adb works in recovery mode and device mode, but not in fastboot mode. Fastboot works only in fastboot mode.
You could try this, put your phone in fastboot mode, then connect to your PC. Now, see what in your Device Manager. In my case, the phone is under Android Device>Android Bootloader Interface and I use Google driver. Then, try "fastboot devices" to see if your phone is detected.
If not, play with the driver in Device Manager (uninstall, rescan, install another). No need to unplug the phone. After the driver changed, see your Device Manager changed, and then try "fastboot devices".
I played with the driver changing a few time and got fastboot to work. I hope you get it to work too.
Sony instructions are awful, I downloaded both the Studio and the SDK tools and things are just... "off" ( f.ex., android_winusb.inf doesn't even exist anywhere in either Studio or SDK tools to be replaced with ).
So I downloaded minimal ADB and fastboot, and I'm having trouble getting the device to be recognized while in fastboot - in device manager, "S1 boot" is unrecognized - I've tried using the drivers I've downloaded from Sony to no avail. Downloaded Xperia software and flashtool, installed drivers from flashtool ( XZ wasn't included in the ****ing thing, of ****ing course it wasn't... ), same thing.
"fastboot devices" simply isn't procuring an answer, and trying to jump ahead and do the unlock, it says that it's pending for devices to show up ( obviously ).
Some help?
Try this guide: https://forum.xda-developers.com/xperia-xz/how-to/how-to-unlock-bl-kernel-twrp-root-t3541648
btw. Sony use custom adb/fastboot driver (link in guide). If I remember correctly, this driver works, however you have to manually point it in device manager (ignore prompt about being incompatible).
You could also try drivers available in Flashtool - in Devices -> Check Driver menu.
http://imgur.com/a/DYGuG
can't get Android WinUSB driver to install. Any help?
edit
when connected while on, it displays this in flashtool : http://imgur.com/a/SqzuB
bump
Did you try to manually select driver for fastboot device? You have to choose from all drivers, not using automated search. Windows will complain it's incompatible, but it should work.
As the title says.
I'm trying to unlock the bootloader on my XZs so I can root it.
My device is listed normally when turned on w/ the command window, but in fastboot mode it disappears and when I try a command, an error comes up saying ""error: no device/emulator found". (see attached image)
As far as I'm concerned, I have all the necessary drivers, I've tried on another PC, the result is always the same.
And when I try to change the drivers (Via Device Manager>Update Driver>Browse My Computer...>Let me pick...>Have Disk...)
I get yet another error saying "The folder you specified doesn't contain a compatible software driver for your device..."
Can someone please give me a solution. This has been asked before on XDA by someone else (that thread has no replies). It seems it's always us little guys with actual problems which need solving who get little to no help at all here.
Reinstall driver again.
It doesn't work. The problem is I want to install the Google USB drivers for my Xperia phone but Windows 10 will not let me and driver signing seems to be impossible to disable (currently typing this on my laptop while it's in test mode).
1. Turn off your phone. Boot in to fastboot mode and plug the cable. After your heard the sound from the computer for new device found. Go to device manager look to usb S1 device. Reinstall driver by manual choose (do not search) from the menu with the name is Android Google. When prompt for install. Choose install anyway. After successful install driver, please check status from flashtool to make sure your device show connected in fastboot.
2. Change the usb port. Sometimes you get problem with usb port 2.0 and 3.0
Hope you can fix it asap.
Nothing by the name of 'Android Google' appears in the menu when selecting new drivers.
I clicked on 'S1boot Fastboot' under 'other devices' in Device Manager and clicked on update driver
>Browse Computer
>Let me pick
- and then there's something similar called 'Android Device' but no 'Android Google' so I click on that
- then I get three options:
Android ADB Interface Version 11.0.0.0
Android Bootloader Interface Version 11.0.0.0
Android Composite ADB Interface Version 11.0.0.0
None of them worked when I tried.
I think the solution is to have the phone on, with USB debugging enabled, connect via USB to PC, test your adb devices again, if all good, go ahead and
Rich (BB code):
adb reboot fastboot
This is because some phones use Fastbootd (notice the d..).