Database Info

Fastboot will not detect my device while rooting

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.

Xperia Z5 fastboot driver not installing

Hi,
I have a rooted Xperia Z5 and I would like to update my firmware to 32.2.A.0.305.
I used to do firmware updates many times before using flashtool on my windows 7 machine.
Recently I switched to windows 10 and now need to reinstall the fastboot driver.
I downloaded the driver from sonymobile webstie:
http://developer.sonymobile.com/downloads/drivers/fastboot-driver/
Unzipped the file, and got a directory with the "android_winusb.inf" file.
Booted the phone in "bootloader" mode via the TWRP recovery (LED on phone is blue).
The regular method of power down, volume up+connect to USB did not work. The LED was blue for a second and then turned off.
When in "bootloader/fastboot" mode, opened the windows "device manager" and found the problematic S1 device.
Right click on it, update driver, browse my computer, pointed to the directory where the ".inf" file is located.
Windows "makes sounds" as if it is installing the driver, but then gives an error:
"Windows found a driver software for your device but encountered an error while attempting to install it"
"Android ADB interface"
"The system cannot find the flie specified"
I have no idea what the problem is.
A few posts suggested that this might be a driver-signing problem with windows 10.
They suggested removing the "driver-signing" option and try. Did not work.
I also tried this with a virtual machine Windows 7 that I have installed, and got the same error, so I'm not sure it is a windows version problem.
I read in one place that this is an error with the location of the file and that it should be located under the "C:\Windows\WinSxS" directory.
Tried that as well, and no luck.
Does someone have any idea what the problem is?
Alernatively, if someone can explain or point me to a post of how to use fastboot and flashtool with linux,
that can also help.
Thank you.
Avi

driver signature verification
1. Goto START (windows icon);
2. Keep pressing SHIFT, klick POWER and RESTART
(shift is pressed all the time along);
3. Choose Troubleshoot > Advanced options > Startup Settings and click the Restart button.
When your computer restarts you'll see a list of options.
4. Press F7 on your keyboard to select Disable driver signature enforcement.
Your computer will now restart and you’ll be able to install unsigned drivers.
This is firt to do, but didnt quite get it if you tried this allready. Greetings

Have the same problem. Disabled driver signature enforcement. Did not help

Are you sure it's disabled? Some pc's don't have the option to disable the driver signature enforcement. If that's the case you need to enter the bios settings and look for the tk keys and delete them, then restart your pc and you can install the fastboot driver.
Hope this helps

Had the same issue on my new setup.
This solved all my problems: https://forum.xda-developers.com/xperia-z/help/help-findiing-installin-s1boot-fastboot-t2218143

dim4x4 said:
Have the same problem. Disabled driver signature enforcement. Did not help
Click to expand...
Click to collapse
Disable driver signature enforcment then install flashtool drivers and select your phone drivers and fastboot drivers, it will ask you are you sure to install press yes and then in folder x10flasher you have fastboot and open cmd in that folder and just use fastboot. Cheers

L33Tgod said:
Disable driver signature enforcment then install flashtool drivers and select your phone drivers and fastboot drivers, it will ask you are you sure to install press yes and then in folder x10flasher you have fastboot and open cmd in that folder and just use fastboot. Cheers
Click to expand...
Click to collapse
Nice and cool - but we still dont have a Sony Xperia Z5 Driver from it in the List

Trouble unlocking bootloader

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.

Xperia J - probably hard brick - device listed as LPT

Hi!
I most probably hard bricked my Xperia J (ST26i latest stock ROM, rooted, locked bootloader) when switching and re-switching and re-reswitching... internal and external storage.
The phone is off and I can't switch it on. When I try to charge it there's no reaction (LED not turning yellow/green/anything). So, I'm quite sure that this device is gone for good, BUT:
When I plug it in to my laptop it is listed in the device manager - as COM & LPT device: "Qualcomm HS-USB QDLoader 9008. Pressing vol+, vol- or <Power> doesn't change a thing. I've had no hardware issues before but somehow Windows recognizes the phone as a ...printer? now.
Sony Companion or fastboot don't find the phone.
Can you help me to bring my phone back to life again?

in flash mode, does it working???
Here I found something.
https://forum.xda-developers.com/xperia-j-e/general/xperia-jst26i-roms-kernels-mods-how-tos-t2237164
and go to Stock ftf's section.

"Flash mode" - that's the thing I have to access by pressing vol+ or vol- when plugging the phone in, right? How do I get into flash mode?
The only thing that happens when I connect the phone with my laptop (and pressing vol+ / vol-) is that it's shown as "LPT device" in the device manager. "Adb devices" command shows nothing when the phone is connected.

Okay, so first, Remove the Drivers detected on your Xperia J. So, It will detect Unknown device.
Now, Install the proper driver(like flashmode drivers, adb drivers, and fastboot drivers) of your Xperia J. Google it to find.
Make sure the Drivers Installed properly.
Click the link that I given to you for the firmware and flashtool.
and follow the guide of the forum.
To open flashmode, press Vol-- button. This will lightup green led.
To open fastboot mode, press the Vol + button. This will lightup blue led.
Hope it helps!
Xperia J is not QPST based but the chipset is Qualcomm.
---------- Post added at 06:25 PM ---------- Previous post was at 06:18 PM ----------
My Xperia E and your Xperia J are the same but the firmware is different.

Thank you!
I'm using Win10 x64. The thing is: I removed my Xperia from the device manager as well as the drivers. Then I installed the drivers you mentioned. After plugging in the device again my Xperia is recognized as "unknown device" like you said. But after a few moments it is listed as "LPT device" again, automatically. Trying to change the driver and install the ADB driver manually doesn't work.
So, still no improvement.

Oh, the adb driver is only from Debugging or some features like Fastboot. The Flashmode driver is different of adb driver. So, I recommend to you to Install this driver to your pc.
https://dl.developer.sonymobile.com...endpoints/cloudfront/create/&nonce=bd40945b0a
When the drivers are now Installed, Do not connect your Xperia J first. Remove the Existing LPT Detected to your Xperia J.
Now on Sony Mobile flasher, or the C:\Flashtool\drivers, open the Flashtool-drivers.exe
Next, tick the Flashmode Drivers, Fastboot Drivers, and Common drivers JDM-Platform board. Install the drivers of it!
When sudden Driver Installation failures, you need to do this.
http://windowsreport.com/driver-signature-enforcement-windows-10/
Connect your Xperia J to your pc, when changes to LPT, update the driver and select the folder for Xperia J driver. (Download/Flashmode mode)
And wait until it Changes into S1 boot download. Now your'e ready to go to flash the ftf!

Thanks for your detailed instructions. Unfortunately, I'm a bit stupid.
So I downloaded the flashmode drivers you mentioned. They consist of some (packed) *.dll, *.inf and *cat files. How can I install these files without an executable or the phone being plugged in? To which folder should I copy the files?
Furthermore, the Xperia flashtool drivers setup offers many drivers like flashmode drivers and fastboot drivers (which I "ticked" both, of course) but the common drivers for Xperia J are not available. I've read that Xperia J is not supported with the Sony flashtool. Should I pick the driver of some other device? Which one?
I appreciate your help! Maybe you can continue a little further

default_user0815 said:
Thanks for your detailed instructions. Unfortunately, I'm a bit stupid.
So I downloaded the flashmode drivers you mentioned. They consist of some (packed) *.dll, *.inf and *cat files. How can I install these files without an executable or the phone being plugged in? To which folder should I copy the files?
Furthermore, the Xperia flashtool drivers setup offers many drivers like flashmode drivers and fastboot drivers (which I "ticked" both, of course) but the common drivers for Xperia J are not available. I've read that Xperia J is not supported with the Sony flashtool. Should I pick the driver of some other device? Which one?
I appreciate your help! Maybe you can continue a little further
Click to expand...
Click to collapse
No. A huge of help is on you. Here I attach some examples. Go to Start->Windows System->Control Panel
Click the View by: Category tab and click Large Icons
And select Device Manager
Connect your Xperia J in Flashmode(Vol - +connect)
When it detects, select that driver detected by your computer..
Double click that device and select Driver tab(*as I exampled the SPD U2S driver.)
Click the Update driver... And you see like popup window.
Select Browse my computer for driver software->Browse(*I extract the zip on the Desktop folder to make easier. :good: )
Locate the Xperia J driver.
Click Next
Select so0101 driver. Done! now ready to open the flashtool!
Flash the Stock ftf rom.

Allright, there was a little misunderstanding. Sorry for that. At least I understand what to do now.
I'm still stuck with installing the driver. Win10 x64 tells me that the driver is not compatible or not available with my system. Disabling the driver signature check didn't help.

default_user0815 said:
Allright, there was a little misunderstanding. Sorry for that. At least I understand what to do now.
I'm still stuck with installing the driver. Win10 x64 tells me that the driver is not compatible or not available with my system. Disabling the driver signature check didn't help.
Click to expand...
Click to collapse
Okay, It really stucks. My Xperia E is dead last week. So, I experienced your situation on your Xperia J. It really hurts. Mine is only detecting Qualcomm ><><blah blah<><>< listed in COM&Ports. Not S1_BootDownload. I replaced the unknown driver with S1_Bootdownload, It says "The detected device is stopped working. And then, BOOM!! Maybe It really needs to repartition the eMMC of my Xperia E. :crying:

Cannot recognise device in fastboot

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.