Develop Bugs

[Q] my laptop doesn't recognize my phone (flash mode & fastboot mode)

my laptop does not recognize my phone in either flashmode or fastboot mode, i tried sing pc companion and flashtool drivers but it does not fix the problem. maybe im doing something wrong, can you guys help me in step by step?
Phone: Xperia Arc S
Version: 4.0.4
Build: 4.1.B.0.587
Computer
OS: Windows 8 (64bit)

http://forum.xda-developers.com/showthread.php?t=2044804

still not working for me

Do you see any error, installing the drivers? What was the the status in the flashtool?

Cibhin said:
Do you see any error, installing the drivers? What was the the status in the flashtool?
Click to expand...
Click to collapse
there's no error in installing the drivers, the status is "device not found"

Phone [Q] my laptop doesn't recognize my phone (flash mode & fastboot mode)
Try this:
(1) Go to device manager
(2) Plug phone in and look for any changes in your list of devices (maybe under other devices) should have a yellow box with exclamation mark
(3) Once found right click then click browse my computer for driver software (point to the folder where drivers are)
(4) Install from there make sure driver signature is off like instructions above :good:

Use this ( View attachment driver_androidusb.zip )... It will work for Arc S and Other
click Thanks if I Help

still not working...
here is the device status...
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed.

try to uninstall any Android Emulator programs you have

Check also if both ends of the usb cable are properly connected and intact to phone and laptop.

Install Android SDK, open it, install all drivers with it. That should do the thing, if I remember correctly.
Sent from LT18i with custom firmware by myself.

Someguyfromhell said:
Install Android SDK, open it, install all drivers with it. That should do the thing, if I remember correctly.
Sent from LT18i with custom firmware by myself.
Click to expand...
Click to collapse
how do you install the drivers using android sdk?

If it's possible for you and not too painstaking, try and format your system, and then do a fresh install. Worked for me when I had a similar problem in the past.

MarcSinger said:
If it's possible for you and not too painstaking, try and format your system, and then do a fresh install. Worked for me when I had a similar problem in the past.
Click to expand...
Click to collapse
i think ill do that, i have tried almost everything but nothing works

so what now? working?
My laptop will not recognize flash mode.
Its not driver problem its keep usb not recognizing.

[Q] Unrecognized Device only in hboot/fastboot

Let me say beforehand that I am a lifetime lurker. I would not be posting here if I hadn't already spent at least two days scouring the web for an answer.
My HTC Desire HD cannot connect to HTC Sync, but it can connect as a storage device, and can be seen by adb. Whenever it connects while in hboot/fastboot, it will flicker "USB" a few times before Windows tell me it's not recognized (Device failed enumeration code 43). This includes using the RUU wizard from HTC. That will just make it stick on "RUU" in the bootloader.
I have tried every driver download suggested on this site. I have switched USB cables three times (all htc cables). I have used two seperate computers (Windows 8 and Windows 8.1).
I'll admit I'm a nooby specifically to Androids. All I want to do is flash new ROMs/root my device. As far as I know this is step one, and I can't go any further until I've unlocked my bootloader.
EDIT: SOLVED
HTC Desire HD drivers really hates Windows 8 and 8.1. Installed Windows 7 32-bit and it worked just fine.

That error can be a pain in the ass. I have it as well. I believe disabling griver signature enforcement in win8 (it's your OS, isn't it?) should allow installing adb drivers, but I was too lazy to check it. As a workaround I instead flash the boot.img in bootloader by putting it to PD98IMG.zip
I can upload you a template, leave the txt in it and replace the boot.img with your desired one, choose store (none) compression level, then put the zip directly (don't use folders) in sd card
EDIT: I didn't fully read your post before. If you don't have S-OFF most probably you can't get away without adb drivers..

Turned off device signing. No effect.

Have you tried now manually installing drivers in device manager while the phone is in unrecognized state? Does it still say the drivers are incompatible?
If your OS is 64bit, you need these http://d-h.st/23V

I have those drivers. I installed them manually. I tried the updating the drivers through device manager and pointing them directly to the drivers folder I need, and Windows is insistent that not having ANY drivers installed is the best driver to have installed for my device.
I am getting a pop up saying that the device is failing to to start. It's not like other usb devices I might have plugged in and they just sit there in at least their correct category in device manager.
The part that ticks me off most, is that this exact problem on this exact model has been solved on three different forums, and each time the OP just said "nvm I fixed it" and never even bothered to explain how for the rest of us.
It's really hard not to curse right now.

in device manager update dialog goto
browse my computer --> let me pick --> have disk --> choose the .inf from the drivers path.

Ya, I had tried that too. None of them will work. It says the file I chose doesn't have compatible software for my device.
Once again, this only happens in the hboot/fastboot/RUU. Once the phone has loaded the OS it works totally completely fine, save for HTC Sync not seeing the phone and vice versa. I don't understand why some drivers would only work sometimes unless something is wrong with my bootloader, and if so, how do i fix it?

have you tried un-installing HTC SYNC?

SuperMechaCow said:
Once again, this only happens in the hboot/fastboot/RUU. Once the phone has loaded the OS it works totally completely fine, save for HTC Sync not seeing the phone and vice versa. I don't understand why some drivers would only work sometimes unless something is wrong with my bootloader, and if so, how do i fix it?
Click to expand...
Click to collapse
Nothing is wrong with your phone, same thing happens to me, I just thought disabling driver signing should fix it, like I said I was too lazy to check it since I found workaround for my needs.

TheJokah said:
have you tried un-installing HTC SYNC?
Click to expand...
Click to collapse
It is currently uninstalled.
@smoger:
I would try your workaround, but I' m not sure where to obtain the boot image I need. Also, I thought you could only change the S-Off if your bootloader was unlocked anyways?

Power down DHD and connect it to PC. I realized, my win7 was installing drivers, while phone was off.
Sent from my HTC Desire HD using xda app-developers app

ammo12 said:
Power down DHD and connect it to PC. I realized, my win7 was installing drivers, while phone was off.
Click to expand...
Click to collapse
It appears to be the same device/drivers when powered off or when in the Android environment. While in the bootloader, it shows as an unknown device.
I also noticed that only when I am trying to update via RUU, it says instead "Device Descriptor Request Failed"

SuperMechaCow said:
@smoger:
I would try your workaround, but I' m not sure where to obtain the boot image I need.
Click to expand...
Click to collapse
The boot.img is in the ROM-zip-file packed. But I think, if its a RUU it is called PD98...img

Try this, I know its from Samsung, but this installs fastboot drivers and drivers used for ADB access
https://www.dropbox.com/s/vqfuv8fifmrkkxt/SAMSUNG_USB_Driver_for_Mobile_Phones.zip
For the set of Google Drivers, go here too http://d-h.st/23V

My drivers list does not show the Google or HTC drivers like yours does after installing all the things in your links. In fact, that's the fourth time I've downloaded those Google/HTC Win7 64x drivers from people around the web. They are not in my drivers list after installing them via the INF files. I must be doing something wrong.

SuperMechaCow said:
My drivers list does not show the Google or HTC drivers like yours does after installing all the things in your links. In fact, that's the fourth time I've downloaded those Google/HTC Win7 64x drivers from people around the web. They are not in my drivers list after installing them via the INF files. I must be doing something wrong.
Click to expand...
Click to collapse
Did you browse to the folder where the manual driver files reside?
Sent from my Desire HD using Tapatalk 4

SuperMechaCow said:
Ya, I had tried that too. None of them will work. It says the file I chose doesn't have compatible software for my device.
Click to expand...
Click to collapse
SuperMechaCow said:
I have those drivers. I installed them manually. I tried the updating the drivers through device manager and pointing them directly to the drivers folder I need, and Windows is insistent that not having ANY drivers installed is the best driver to have installed for my device.
Click to expand...
Click to collapse
To be exact I have:
Tried HTC Sync
Tried HTC Drivers Installer
Tried to Automatically search for drivers
Tried to install drivers by using the inf Install option
Tried to manually select drivers by pointing to the folder the Win7 64x drivers were placed
Tried to manually install by picking out the exact inf files
Tried to install from device drivers list, were they were not listed
Tried these steps with driver signing turned off
Tried all of these steps with another PC
I still think the issue is related to the fact that it only has problems in the bootloader menu

Ok, like u know I had this issue. Now I randomly managed to fix it when I needed adb drivers for my new toy (Sanei tablet for 40$ lol)
The mistake I was making is that I was trying to install the drivers while device was in fastboot, but apparently you can get away with casual "My HTC" drivers which can be installed when DHD is booted into Android. It looks likethe phone is not being detected from bootloader (it doesn't like any of the drivers I had tried), but I can fully use ADB while it's in recovery or starting/trying to boot OS, so it should be enough for rooting/unlocking bootloader.
I remember with HTC Wildfire I had drivers package with seperate drivers for Android and fastboot, so I had to install different driver after rebooting to fastboot, but with these new drivers and win8 it doesn't work out this way.

Solved. Used Windows 7 32-bit. Windows 8.1 was the culprit.

Similar issue
SuperMechaCow said:
Solved. Used Windows 7 32-bit. Windows 8.1 was the culprit.
Click to expand...
Click to collapse
I am facing the same problem and I too have tried different methods like you did. Am using Windows 8.
Gotta try on Windows 7. Shall update if that solves my problem too.

[Q] ADB drivers for xperia m

Noob here!
I cant find android developement driver for xperia m c1904!!
Installing the latest PC Companion doesnt help.
where can i get the drivers from??
thnx in advance!

I have here adb driver packed in, but if you are using Windows 7/8/8.1 you need first to disable Driver Signature Verification. Here is the link to show you how you do it:
http://www.howtogeek.com/167723/how-to-disable-driver-signature-verification-on-64-bit-windows-8.1-so-that-you-can-install-unsigned-drivers/
So after that, you normally install provided drivers, and I also provided a archive that contains extracted adb program, so you don't need to instal Andorid sdk.
Here is donwload link: https://www.mediafire.com/?j9xjn79lm3jkyv5
Hope I helped you

Hope hs answer helps... And just to add questions shouldn't be in the general section. We have a Q&A section for em
Sent from my C1905 using XDA Premium 4 mobile app

aleksa069 said:
I have here adb driver packed in, but if you are using Windows 7/8/8.1 you need first to disable Driver Signature Verification. Here is the link to show you how you do it:
http://www.howtogeek.com/167723/how-to-disable-driver-signature-verification-on-64-bit-windows-8.1-so-that-you-can-install-unsigned-drivers/
So after that, you normally install provided drivers, and I also provided a archive that contains extracted adb program, so you don't need to instal Andorid sdk.
Here is donwload link: https://www.mediafire.com/?j9xjn79lm3jkyv5
Hope I helped you
Click to expand...
Click to collapse
thanks, i will try too for my mikocok 8 64bit

Signed ADB drivers for Xperia M only come with very recent builds of PC Companion (even FlashTool 1.3 doesn't have this drivers currently). I managed to get only them from a local install, download the attached file and run DPInst.exe (or DPInst64.exe if running 64-bit OS). With this package you don't need to disable driver signature enforcement, they work out of box in Windows 8/8.1...

mbc07 said:
Signed ADB drivers for Xperia M only come with very recent builds of PC Companion (even FlashTool 1.3 doesn't have this drivers currently). I managed to get only them from a local install, download the attached file and run DPInst.exe (or DPInst64.exe if running 64-bit OS). With this package you don't need to disable driver signature enforcement, they work out of box in Windows 8/8.1...
Click to expand...
Click to collapse
Hello,
PC companion works well and detect my phone but does not install any adb drivers...
I can't find ADB drivers for this phone anywhere where did you found these?
thank you.

Hey, just to add to the list of answers, here is an adb drivers installer. All you have to do is open the programme, plug in your phone and press install, then you are done.
Here is the download: http://adbdriver.com/downloads/

Hedzx said:
Hello,
PC companion works well and detect my phone but does not install any adb drivers...
I can't find ADB drivers for this phone anywhere where did you found these?
thank you.
Click to expand...
Click to collapse
I got from a PC Companion update. Make sure you have the latest version of PC Companion or reinstall it to fix that...
paper13579 said:
Hey, just to add to the list of answers, here is an adb drivers installer. All you have to do is open the programme, plug in your phone and press install, then you are done.
Here is the download: http://adbdriver.com/downloads/
Click to expand...
Click to collapse
Unsigned drivers = major headaches to install in Windows 8+ since it'll accept only signed drivers unless you disable driver signature enforcement first (and M$ make that process more complicated in Windows 8+ than before)

mbc07 said:
I got from a PC Companion update. Make sure you have the latest version of PC Companion or reinstall it to fix that...
Unsigned drivers = major headaches to install in Windows 8+ since it'll accept only signed drivers unless you disable driver signature enforcement first (and M$ make that process more complicated in Windows 8+ than before)
Click to expand...
Click to collapse
Lol, what are you on about. Please explain to me, what do you mean by unsigned drivers. I used that programme on windows 7 and the drivers work perfectly for me.

paper13579 said:
Lol, what are you on about. Please explain to me, what do you mean by unsigned drivers. I used that programme on windows 7 and the drivers work perfectly for me.
Click to expand...
Click to collapse
As I assume you've already worked out drivers can come in two forms, signed and unsigned.
Signed drivers are generally ones coming from manufacturers and have a valid signature bundled in with them.
Unsigned drivers are generally ones coming from external sources (like flashtool) and do not have a valid signature bundled with them or they don't have one at all.
In Windows 7 there is slight driver enforcement, when you try to install unsigned drivers a window pops up telling that they are unsigned and that you shouldn't install them. You still have the option to install them.
In Windows 8, 8.1 and 8.1 Update 1 there is strict driver enforcement. When you try to install an unsigned driver with driver enforcement on, it will fail. When you turn the driver enforcement off (which is a pain to do) and then try to install an unsigned driver you get the pop up window telling you that the driver is unsigned and that you shouldn't install them, you still have the option to install them however.
I hope this explains it for you.

ADB driver not recognised by Flashtool
paper13579 said:
Hey, just to add to the list of answers, here is an adb drivers installer. All you have to do is open the programme, plug in your phone and press install, then you are done.
Here is the download: [not allowed to post links]
Click to expand...
Click to collapse
I'm trying to revert to 4.2.2 from 4.3 to root my Xperia M dual 2005 that I received brand new today. I have spent four hours trying to get Flashtool to recognise that the phone is in USB debugging mode. It definitely is - USB debugging (and nothing else) is checked in Developer Options, USB connectivity is set to Mass Storage (not MTP) and installing from unknown sources is enabled in Security.
When I connect the phone powered up, this is what Flashtool shows:
10/051/2014 22:51:23 - INFO - <- This level is successfully initialized
10/051/2014 22:51:23 - INFO - Flashtool Version 0.9.16.0 built on 19-04-2014 19:00:00
10/051/2014 22:51:24 - INFO - This is the first sync with devices on github. Renaming devices to devices.old
10/051/2014 22:51:24 - INFO - Cloning devices from github project
10/052/2014 22:52:06 - INFO - Devices sync finished.
10/052/2014 22:52:13 - INFO - Device connected with USB debugging off
10/052/2014 22:52:13 - INFO - For 2011 devices line, be sure you are not in MTP mode
10/052/2014 22:52:22 - INFO - List of connected devices (Device Id) :
10/052/2014 22:52:22 - INFO - - USB\VID_0FCE&PID_619B&MI_01\7&4CF9BF6&0&0001 Driver installed : true
10/052/2014 22:52:22 - INFO - - USB\VID_0FCE&PID_619B&MI_00\7&4CF9BF6&0&0000 Driver installed : true
10/052/2014 22:52:22 - INFO - - USB\VID_0FCE&PID_619B\YT910S4WK6 Driver installed : true
10/052/2014 22:52:22 - INFO - List of ADB devices :
10/052/2014 22:52:22 - INFO - - none
10/052/2014 22:52:22 - INFO - List of fastboot devices :
10/052/2014 22:52:22 - INFO - - none
But the notification area on the phone shows "USB debugging connected"!!!!!
To flash, I know I have to disconnect and turn the phone off, choose the .ftf then start the flash procedure (preparing files). Then when the animated graphic comes up, I press the volume down button and re-plug the USB cable back into the phone. Nothing happens - no lights on the phone, no flash starts, nothing. This is regardless of whether I keep the vol down button depressed for ages, or let it go after a few seconds.
I'm sure I have the ADB driver installed. I have the latest version of Sony PC Companion. I tried the ADB_Nicky method above from mbc07, using "have disk" and the driver seemed to install no problem. To double check I downloaded the file from the link given above by paper13579 and it detects the phone as a Sony Ericsson, and says the ADB drivers are already installed. I have also uninstalled the device in DM and restarted the PC and reinstalled the driver. Clip of Device Manager attached (as it appears when the powered-up phone is plugged in). Nothing appears in Device Manager when I try the flash procedure as above (phone off, vol down depressed).
I have been using Windows 7 Ultimate 32-bit, and (in desperation) XP SP3, with the same results. I've tried different USB cables (known good). I don't know what to try next.

@zumtotal, ADB drivers are different from flashmode drivers. Turn off your phone, hold Vol Down and plug USB. Go to device manager and see if you have a "SEMC Flash Device". If it show up with an exclamation mark or don't show at all, try reinstalling PC Companion or selecting "Have Disk" and then pointing to PC Companion folder in Program Files...
Please note that while in flash mode, if the phone doesn't receive any answer from the host computer within 2 minutes it'll automatically disconnect and restart the phone in normal mode, so, after plugging the phone while holding volume down you'll have approximate 2 minutes to do the driver install...

Completed
mbc07 said:
@zumtotal, ADB drivers are different from flashmode drivers. Turn off your phone, hold Vol Down and plug USB. Go to device manager and see if you have a "SEMC Flash Device". If it show up with an exclamation mark or don't show at all, try reinstalling PC Companion or selecting "Have Disk" and then pointing to PC Companion folder in Program Files...
Please note that while in flash mode, if the phone doesn't receive any answer from the host computer within 2 minutes it'll automatically disconnect and restart the phone in normal mode, so, after plugging the phone while holding volume down you'll have approximate 2 minutes to do the driver install...
Click to expand...
Click to collapse
Thanks, mbc07, your answer helped. To cut a very long story short, I made two mistakes:
1. When I first enabled USB debugging on the phone I didn't have any data connection enabled (neither wifi nor sim). So when I connected the powered-up phone to the PC the phone didn't install the USB debugging feature properly. After I got data enabled, more installation took place, and eventually Flashtool recognised my phone correctly and saw that it was in debugging mode.
2. I didn't pull out and re-insert the battery to get the phone into flash mode (that is not included in Part 1 of paper13579's instructions in the main 4.3 rooting thread). So when I connected the powered-off phone with the vol down depressed I could see that nothing changed in Device Manager. After I pulled and replaced the battery, the phone was recognised as SEMC Flash Device and the driver installed.
Simple mistakes but they cost me hours. Hope this helps someone else.

mbc07 said:
Signed ADB drivers for Xperia M only come with very recent builds of PC Companion (even FlashTool 1.3 doesn't have this drivers currently). I managed to get only them from a local install, download the attached file and run DPInst.exe (or DPInst64.exe if running 64-bit OS). With this package you don't need to disable driver signature enforcement, they work out of box in Windows 8/8.1...
Click to expand...
Click to collapse
This works

great!! I will try this in win 8.1

Can't get Fastboot to work

Ok. I can't get fastboot to work. WIndows 10 laptop. Disabled driver verification. ADB works fine and reboots into bootloader but once in bootloader no fastboot. I've got an "Unknown Device" in Other Devices in Device manager and I've tried to assign the google driver manually but it's not recognized as a driver for the device
I've removed and reinstalled drivers pre and post driver verification
I tried adding PIxel C lines to the driver INF file as instructed on stack overflow
I don't know what else to try. And i've tried on two different computers???
Help please.. thanks

I fought with this for ages today. To start with, I have the Wugfresh Nexus Root Toolkit installed. Now, when in bootloader, go to the device manager on your computer. Find the Pixel ("Unknown Device") and right click > Properties > Driver tab > Update Drivers > Browse Computer > Choose From List > WugFresh Development\Nexus Root Toolkit\data\Drivers > and pick the one that says something about the bootloader. Sorry, going off memory here. Now you should be able to get that one installed, and Fastboot will start showing up when in the bootloader.

Hakizi said:
I fought with this for ages today. To start with, I have the Wugfresh Nexus Root Toolkit installed. Now, when in bootloader, go to the device manager on your computer. Find the Pixel ("Unknown Device") and right click > Properties > Driver tab > Update Drivers > Browse Computer > Choose From List > WugFresh Development\Nexus Root Toolkit\data\Drivers > and pick the one that says something about the bootloader. Sorry, going off memory here. Now you should be able to get that one installed, and Fastboot will start showing up when in the bootloader.
Click to expand...
Click to collapse
I did the same : Choose from List >fastboot (I didn't install Wug)

jamgam said:
Ok. I can't get fastboot to work. WIndows 10 laptop. Disabled driver verification. ADB works fine and reboots into bootloader but once in bootloader no fastboot. I've got an "Unknown Device" in Other Devices in Device manager and I've tried to assign the google driver manually but it's not recognized as a driver for the device
I've removed and reinstalled drivers pre and post driver verification
I tried adding PIxel C lines to the driver INF file as instructed on stack overflow
I don't know what else to try. And i've tried on two different computers???
Help please.. thanks
Click to expand...
Click to collapse
This is what worked for me....
http://forum.xda-developers.com/showpost.php?p=64777133&postcount=96

jamgam said:
Ok. I can't get fastboot to work. WIndows 10 laptop. Disabled driver verification. ADB works fine and reboots into bootloader but once in bootloader no fastboot. I've got an "Unknown Device" in Other Devices in Device manager and I've tried to assign the google driver manually but it's not recognized as a driver for the device
I've removed and reinstalled drivers pre and post driver verification
I tried adding PIxel C lines to the driver INF file as instructed on stack overflow
I don't know what else to try. And i've tried on two different computers???
Help please.. thanks
Click to expand...
Click to collapse
I had the same problem man. This will fix it.
1. Open Device Manager and Select the Unknown Device
2. Select Update Driver
3. Select Browse My Computer
4. Select Let Me Pick From a List of Device Drivers On My Computer
5. Select Android
6. Select Android Bootloader
Done.

@Istvan_86,
We should move the discussion for your problem here.

cam30era said:
@Istvan_86,
We should move the discussion for your problem here.
Click to expand...
Click to collapse
Hello,
I don't see any link and sorry if I made too many posts.

Istvan_86 said:
Hello,
I don't see any link and sorry if I made too many posts.
Click to expand...
Click to collapse
That's OK. No problem. Did you try the steps in post #5 above?

Which operating system are you on? What worked for me on Windows 10 was to give up after several days and use a Windows 7 computer. I read everything and tried everything and I could not get Fastboot working on this device with Windows 10. I used every toolkit, every driver version, toolkits that install multiple driver versions, Minimal ADB + Fastboot, and who knows what else. If a well-documented end-to-end solution to this ever appears I'll be really grateful.

FWIW, it was my frustrations with this Windows driver nonsense, that eventually drove me to abandon Windows entirely. Been on Ubuntu for several years. No regrets.

cam30era said:
That's OK. No problem. Did you try the steps in post #5 above?
Click to expand...
Click to collapse
Thanks for point me here, yo offer me too much help.
Now I´m on Nougat working flawlessly.
CISGS said:
I had the same problem man. This will fix it.
1. Open Device Manager and Select the Unknown Device
2. Select Update Driver
3. Select Browse My Computer
4. Select Let Me Pick From a List of Device Drivers On My Computer
5. Select Android
6. Select Android Bootloader
Done.
Click to expand...
Click to collapse
Really, really, really thanks. I have the exact same issue and this solved it for me also.
Cheers!

Istvan_86 said:
Thanks for point me here, yo offer me too much help.
Now I´m on Nougat working flawlessly.
Really, really, really thanks. I have the exact same issue and this solved it for me also.
Cheers!
Click to expand...
Click to collapse
Welcome.

cam30era said:
FWIW, it was my frustrations with this Windows driver nonsense, that eventually drove me to abandon Windows entirely. Been on Ubuntu for several years. No regrets.
Click to expand...
Click to collapse
It's very annoying, there seems to be a few reasons it fails. Cable, 3.0 usb ports, windows 10 drivers. I get different results with different cables in different types of usb ports. Also switching to PTP seems to work using a usb 2.0 port with a standard usb 2.0 A to micro with a micro to c adapter. Charging and MTP fail, but at least ADB and Fastboot respond.
I am going to try to edit the win10 driver using this post as reference.
http://stackoverflow.com/questions/34775508/where-is-the-windows-adb-driver-for-the-pixel-c
---------- Post added at 11:05 PM ---------- Previous post was at 11:04 PM ----------
CISGS said:
I had the same problem man. This will fix it.
1. Open Device Manager and Select the Unknown Device
2. Select Update Driver
3. Select Browse My Computer
4. Select Let Me Pick From a List of Device Drivers On My Computer
5. Select Android
6. Select Android Bootloader
Done.
Click to expand...
Click to collapse
I came to the same conclusion, but after a reboot it was unrecognized again.

Only way I can it to stick is installing the 2nd option drivers via skipsoft toolkit. Connect pixel c via 2.0 port and cable to PC. Switch to ptp. Then manually force install driver choosing have disk using bootloader option. From then on it works using ptp.

What I am able to see using USB Device Tree Viewer, is that when I plug in my Pixel C to my ASUS Z97-A blue usb ports with USB debugging enabled, it can not identify it. Those ports use Microsoft Windows 10 drivers for the Intel USB 3.0 eXensible Host Controller - 1.0. Which is what is causing the failure, not the Pixel C drivers. When I updated my other green USB ports driver, windows used the same ones on my ASMedia USB 3.1 eXtensible Host Controller and also couldn't recognize the Pixel C any longer. I rolled back to ASMedia drivers, it worked fine. Updated using newer ASMedia drivers 4/11/2016 ver 1.16.35.1 and those work fine. Now to find working drivers for the Inter Host. Win7 drivers refuse to load.
UPDATE: If your bios allows, disable xHCI. Your USB ports will work as USB 2.0 but will detect your PIXEL C without issues.

Solution works 100%
If you've installed the SDK drivers and win10 can detect your Pixel C in every mode with usb debugging off. Use these win10 USB xHCi drivers,
http://www.win-raid.com/t834f25-USB-Drivers-original-and-modded.html

@clockcycle,
This solution works 100% too. https://www.ubuntu.com/

CISGS said:
I had the same problem man. This will fix it.
1. Open Device Manager and Select the Unknown Device
2. Select Update Driver
3. Select Browse My Computer
4. Select Let Me Pick From a List of Device Drivers On My Computer
5. Select Android
6. Select Android Bootloader
Done.
Click to expand...
Click to collapse
Been smashing my face off the wall since LAST NIGHT trying to figure this out. windows 7 machine/ windows 8/ ubuntu ! trying 100 different methods and this one FINALLY SOLVED THE ISSUE. gawd dayum thank you so much from the future !!!

Question F3 TWRP fastboot not detecting Win11

My ADB works fine but not getting a fastboot devices detect for TWRP fastboot.
I also see driver missing in device manager on Win11 but none of various versions of Google ADB, Xiaomi, etc drivers I have tried seem to match the hardware it thinks its detecting
It did work prior with stock recovery fastboot.
Prior there was some Win 11 driver signing issue for fastboot drivers.. But I have Shift rebooted and disabled driver signature enforcement, which was what worked last time, but its not helping with TWRP.
Anything obvious to suggest here ??
Poco F3 with TWRP cant detect fastboot.

windows 11 is still on its embryonic stage expect some bugs and compatibility issue, try reinstalling all drivers of your poco f3 but before that, you need to disable driver signature enforcement before reinstalling drivers search on google on how to disable this matter

I have done that though.. Rebooted with driver signature turned off (thats what worked last time) and added / removed phone.. rebooted phone.. Tried manually reinstalling same drivers, new drivers, searching for drivers, etc..
Can TWRP need any different driver pairing than the stock recovery drivers ??
Worked straight away when stock.

Phat Phreddy said:
I have done that though.. Rebooted with driver signature turned off (thats what worked last time) and added / removed phone.. rebooted phone.. Tried manually reinstalling same drivers, new drivers, searching for drivers, etc..
Can TWRP need any different driver pairing than the stock recovery drivers ??
Worked straight away when stock.
Click to expand...
Click to collapse
i am currently running on win 10, nebrassy and vasishath twrp build no issue about fastboot, maybe you should try to downgrade your pc

Phat Phreddy said:
I have done that though.. Rebooted with driver signature turned off (thats what worked last time) and added / removed phone.. rebooted phone.. Tried manually reinstalling same drivers, new drivers, searching for drivers, etc..
Can TWRP need any different driver pairing than the stock recovery drivers ??
Worked straight away when stock.
Click to expand...
Click to collapse
if it worked on stock have you maybe forgoten to enable usb debugging again? lol

Phat Phreddy said:
My ADB works fine but not getting a fastboot devices detect for TWRP fastboot.
I also see driver missing in device manager on Win11 but none of various versions of Google ADB, Xiaomi, etc drivers I have tried seem to match the hardware it thinks its detecting
It did work prior with stock recovery fastboot.
Prior there was some Win 11 driver signing issue for fastboot drivers.. But I have Shift rebooted and disabled driver signature enforcement, which was what worked last time, but its not helping with TWRP.
Anything obvious to suggest here ??
Poco F3 with TWRP cant detect fastboot.
Click to expand...
Click to collapse
Have you tried to install the drivers present on the miflash program with the Windows driver signature disabled? If that doesn't work either, I think the problem is your win 11. I tried win 11 last month and with those drivers and sdk platform tools the phone was well recognized in fastboot

mlcattini said:
if it worked on stock have you maybe forgoten to enable usb debugging again? lol
Click to expand...
Click to collapse
But I said its working on ADB..

RollDload said:
Have you tried to install the drivers present on the miflash program with the Windows driver signature disabled? If that doesn't work either, I think the problem is your win 11. I tried win 11 last month and with those drivers and sdk platform tools the phone was well recognized in fastboot
Click to expand...
Click to collapse
Will give this a go..
Can I 'update driver' and point it at the file folder or does this need re-installing the miflash app ?

Phat Phreddy said:
Will give this a go..
Can I 'update driver' and point it at the file folder or does this need re-installing the miflash app ?
Click to expand...
Click to collapse
you could try, however miflash doesn't need installation you just need to unzip it. you can also try to change USB port better if rear and 2.0

Strange I thought I replied in here this morning..
Anyway.. Got it going.. Disabled driver checking.. Then forced 'from disk' and manually pushed it to use the xiaomi drivers.. It wouldnt auto detect or even find the drivers when pointed at the disk, btu the prior install version worked and now both adb and fastboot working even when booted with driver checking on.

Phat Phreddy said:
Strange I thought I replied in here this morning..
Anyway.. Got it going.. Disabled driver checking.. Then forced 'from disk' and manually pushed it to use the xiaomi drivers.. It wouldnt auto detect or even find the drivers when pointed at the disk, btu the prior install version worked and now both adb and fastboot working even when booted with driver checking on.
Click to expand...
Click to collapse
then it was definitely a problem in the driver.