Related
I recently broke my HOX+ and got a GNex for my replacement. Whenever I try to connect it, using another cable (Nexus 7) because its stock cable did not come with the phone (used) I get that pop up which says "Unable to recognize device" or sometimes an error. Though on all events, I get something called Error 43.
Anyone know how to fix this? Ive tried fixing to usb port. It is all stock. I just want to connect so I can root this thing.
Mikeonic said:
I recently broke my HOX+ and got a GNex for my replacement. Whenever I try to connect it, using another cable (Nexus 7) because its stock cable did not come with the phone (used) I get that pop up which says "Unable to recognize device" or sometimes an error. Though on all events, I get something called Error 43.
Anyone know how to fix this? Ive tried fixing to usb port. It is all stock. I just want to connect so I can root this thing.
Click to expand...
Click to collapse
Try installing samsung mtp drivers..
Sent from my Galaxy Nexus
Ive tried
mixtapes08 said:
Try installing samsung mtp drivers..
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I have tried installing drivers...still nothing..
I do assume you're using windows?
And my apologies, are you getting this error message when you try to root?
Were these the MTP drivers you installed?
http://www.samsung.com/us/support/owners/product/SCH-I515MSAVZW
iLeopard said:
I do assume you're using windows?
And my apologies, are you getting this error message when you try to root?
Were these the MTP drivers you installed?
http://www.samsung.com/us/support/owners/product/SCH-I515MSAVZW
Click to expand...
Click to collapse
Yes, Windows 7. Those were the ones and I want to root, but I can't even connect my phone. I'll plug in my GNex and it will charge through the computer though it will not be recognized nor connected for storage purposes.
Mikeonic said:
Yes, Windows 7. Those were the ones and I want to root, but I can't even connect my phone. I'll plug in my GNex and it will charge through the computer though it will not be recognized nor connected for storage purposes.
Click to expand...
Click to collapse
One thing you may want to try if you havent yet:
My Computer -> Right Click -> Properties -> Device Manager (On Sidebar) -> Find the GNex Drivers currently installed and remove them and reinstall (Re-plug) your phone so that the drivers can re-install.
Is this a used or new replacement?
iLeopard said:
One thing you may want to try if you havent yet:
My Computer -> Right Click -> Properties -> Device Manager (On Sidebar) -> Find the GNex Drivers currently installed and remove them and reinstall (Re-plug) your phone so that the drivers can re-install.
Is this a used or new replacement?
Click to expand...
Click to collapse
Unfortunately, the device appears as Unknown Device. It was my Uncles and it was able to work for him. So it bothers me how its not for me. At times even, when I connect the USB to the Device, it causes my Computer to Shut Down abnormally. So, either something is wrong and I need to fix it...or this phone is haunted,
Mikeonic said:
Unfortunately, the device appears as Unknown Device. It was my Uncles and it was able to work for him. So it bothers me how its not for me. At times even, when I connect the USB to the Device, it causes my Computer to Shut Down abnormally. So, either something is wrong and I need to fix it...or this phone is haunted,
Click to expand...
Click to collapse
Even after deleting it?
Did he by chance have it rooted prior to the ownership change?
Is the result replicated in other computers? If you haven't tried, do so. That way you can eliminate either your PC or the GNex as the culprit.
iLeopard said:
Even after deleting it?
Did he by chance have it rooted prior to the ownership change?
Is the result replicated in other computers? If you haven't tried, do so. That way you can eliminate either your PC or the GNex as the culprit.
Click to expand...
Click to collapse
He was stock at all times. Though when I got it, it seemed to be freshly restored...but 5 minutes into using the phone, it froze and gave a fixed screen of something being flashed...though even after I factory restored it again...It wont connect to my All in One PC, Desktop or Laptop, every other device I own connects properly .
Mikeonic said:
He was stock at all times. Though when I got it, it seemed to be freshly restored...but 5 minutes into using the phone, it froze and gave a fixed screen of something being flashed...though even after I factory restored it again...It wont connect to my All in One PC, Desktop or Laptop, every other device I own connects properly .
Click to expand...
Click to collapse
Wierd. Did you try a reset through the stock recovery or just defaults from the security menu?
Here's what I've done. I've pulled my drivers and compressed them. Update the "Unknown Device" from the Device Manager by pointing it to the extracted DLL's and see if that will work.
Drivers
iLeopard said:
Wierd. Did you try a reset through the stock recovery or just defaults from the security menu?
Here's what I've done. I've pulled my drivers and compressed them. Update the "Unknown Device" from the Device Manager by pointing it to the extracted DLL's and see if that will work.
Drivers
Click to expand...
Click to collapse
Been trying and it wont let me push those files and when I do, I get Code Error 10
Mikeonic said:
Been trying and it wont let me push those files and when I do, I get Code Error 10
Click to expand...
Click to collapse
Pushing them? Sorry for my poor explanation. Those files you downloaded are my working drivers that I managed to pull from:
C:\Windows\system32\DRIVERS\UMDF
C:\Windows\system32\DRIVERS\
C:\Windows\system32\
All you have to do is press START -> Type "Device Manager" -> Select the "Unknown Device" -> Press "Update Driver" -> "Browse my computer for driver software" -> Hit "Browse" and point to the folder were the DLL's are located in your computer (Once you have decompressed the archive of course)
iLeopard said:
Pushing them? Sorry for my poor explanation. Those files you downloaded are my working drivers that I managed to pull from:
C:\Windows\system32\DRIVERS\UMDF
C:\Windows\system32\DRIVERS\
C:\Windows\system32\
All you have to do is press START -> Type "Device Manager" -> Select the "Unknown Device" -> Press "Update Driver" -> "Browse my computer for driver software" -> Hit "Browse" and point to the folder were the DLL's are located in your computer (Once you have decompressed the archive of course)
Click to expand...
Click to collapse
It says there are no files in the folder...
UPDATE
It says it FOUND Drivers though cannot execute actions due to error 43
Mikeonic said:
UPDATE
It says it FOUND Drivers though cannot execute actions due to error 43
Click to expand...
Click to collapse
Honestly, I'm stumped. The drivers should have installed correctly regardless. This leads me to believe that its the GN acting up. Again, when you did a reset on it; Did you do it from the Security Submenu or from the Stock Recovery?
Is the device recognized under fastboot? ADB usually works fine there.
iLeopard said:
Honestly, I'm stumped. The drivers should have installed correctly regardless. This leads me to believe that its the GN acting up. Again, when you did a reset on it; Did you do it from the Security Submenu or from the Stock Recovery?
Is the device recognized under fastboot? ADB usually works fine there.
Click to expand...
Click to collapse
It was through the Settings SubMenu, I'll try a Fast boot
Mikeonic said:
It was through the Settings SubMenu, I'll try a Fast boot
Click to expand...
Click to collapse
Also try a factory reset via Stock Recovery. You should find it under the Fastboot menu
iLeopard said:
Also try a factory reset via Stock Recovery. You should find it under the Fastboot menu
Click to expand...
Click to collapse
Still nothing....this is hopeless
Mikeonic said:
Still nothing....this is hopeless
Click to expand...
Click to collapse
Wow, I'm truly amazed how nothing seemed to work. I don't think 1-Click Temp-Root Methods work on the GN, in which case you would use the terminal to Perm-Root it.
This happens on all computers?
Tried Different USB ports?
Rebooting PC?
iLeopard said:
Wow, I'm truly amazed how nothing seemed to work. I don't think 1-Click Temp-Root Methods work on the GN, in which case you would use the terminal to Perm-Root it.
This happens on all computers?
Tried Different USB ports?
Rebooting PC?
Click to expand...
Click to collapse
I will try getting a new USB, maybe a stock if I can find and see if that works. Wish I could root without a USB...Thank You for your help. I will update if anything.
When I connect Nexus 5X to a Windows 10 PC, I can't see it in File Explorer.
Many people said that one should change the option from charging only to MTP in the USB connection notification, appeared when plugged in. But I don't even have that notification, and cannot find the option anywhere else.
In Devices and Printers, there's a Nexus 5X under Unspecified; and in Device Manager, I can see a "ACER ADB Interface" there which I assume is for Nexus 5X. I tried to download Nexus driver from Google buy it seems is the same with the ACER ADB thing and is not helping.
Any tips or solutions? Thanks in advance!
PS. First xda thread started by me, yay!
UPDATE: After awhile, maybe it's because I slid the screen while connected, the notification did pop up. But EVEN after I chose MTP, there's still nothing in my File Explorer...
Hiya,
I had the same thing happen on my 5X. I was only able to get to the "Use USB for Charge / MTP" dialog by enabling Developer Mode.
To do that: Go to Settings / About Phone, and scroll all the way to the bottom.
Tap "Build number" seven times. On the sixth tap, you should see a message that says "one more tap will unlock Developer mode" or something to that effect.
Back-arrow to the Settings main menu.
Click on Developer options
Look for Networking / Select USB Configuration.
Choose the mode you want.
The notification should appear when you plug in the USB cable to your computer.
elzapato said:
Hiya,
I had the same thing happen on my 5X. I was only able to get to the "Use USB for Charge / MTP" dialog by enabling Developer Mode.
To do that: Go to Settings / About Phone, and scroll all the way to the bottom.
Tap "Build number" seven times. On the sixth tap, you should see a message that says "one more tap will unlock Developer mode" or something to that effect.
Back-arrow to the Settings main menu.
Click on Developer options
Look for Networking / Select USB Configuration.
Choose the mode you want.
The notification should appear when you plug in the USB cable to your computer.
Click to expand...
Click to collapse
Thanks for this info! I'll keep that in mind, but now I still have problem after chose the transfer mode. Maybe it's because I slid the screen while connected, the notification do pop up. But EVEN after I chose MTP, there's still nothing in my File Explorer...
could be a driver issue?
download and install latest usb drivers.
Go to My Computer> Properties>Device Manager> Find the android device>Right Click update driver software>Browse My Computer>set to folder where you have usb driver saved and go from there?
You can also try to let me pick (instead of browse local folders) and pick the google ADB interface from there.
I have also had success in the past using other software (PdaNet) to manage the whole installataion of drivers; but this adds software to both phone and computer ... may or may not be useful.
After re-reading your first post its definately driver related. It shouldnt say Acer just ADB Interface or google adb interface.
alienboytw said:
When I connect Nexus 5X to a Windows 10 PC, I can't see it in File Explorer.
Many people said that one should change the option from charging only to MTP in the USB connection notification, appeared when plugged in. But I don't even have that notification, and cannot find the option anywhere else.
In Devices and Printers, there's a Nexus 5X under Unspecified; and in Device Manager, I can see a "ACER ADB Interface" there which I assume is for Nexus 5X. I tried to download Nexus driver from Google buy it seems is the same with the ACER ADB thing and is not helping.
Any tips or solutions? Thanks in advance!
PS. First xda thread started by me, yay!
UPDATE: After awhile, maybe it's because I slid the screen while connected, the notification did pop up. But EVEN after I chose MTP, there's still nothing in my File Explorer...
Click to expand...
Click to collapse
Check Device Manager, is it listed as ACER Device? It probably is. It happened to me. Select the device, mouse right, update driver, choose "let me pick a driver" or something simmilar. Then you should get a list of compatible drivers and 2 entries, the current ACER driver and some generic USB driver. Choose the generic USB driver. That did the trick for me.
This i got from reddit . I had the same problem today this link helped me .. hope it helps you too
arpan_pratik said:
Check Device Manager, is it listed as ACER Device? It probably is. It happened to me. Select the device, mouse right, update driver, choose "let me pick a driver" or something simmilar. Then you should get a list of compatible drivers and 2 entries, the current ACER driver and some generic USB driver. Choose the generic USB driver. That did the trick for me.
This i got from reddit . I had the same problem today this link helped me .. hope it helps you too
Click to expand...
Click to collapse
@arpan_pratik, Thank you! You are the best! This is exactly what my problem is and I solved it using your suggestion!
Although I didn't yet find any useful information from reddit regarding my issue, you must used some magic keywords
@The_Automator, thank you, too! It indeed is a driver issue. I tried many times to update the driver or uninstall the ACER ADB driver, but none of them worked. Didn't realize that it is Windows chose the wrong default driver. Don't know why, maybe it's because I installed adb before?
So, for the record, here are some key points to solve the problem:
The wrong driver for my Nexus 5X showed in Device Manager is ACER Device\ACER ADB Interface
No use to install Nexus driver from Google, even use "Browse my computer for driver software" and search the extracted Google driver folder. Windows will say the driver is up to date.
So I have to do this: In Device Manager -> RMB on ACER Device\ACER ADB Driver -> Properties -> Update Driver -> Browse my computer for driver software -> Let me pick from a list of device drivers on my computer -> check "Show compatible hardware" -> choose "MTP USB Driver" (this is a Microsoft driver under "standard MTP Device" category) -> Problem solved!
Then I can find my Nexus 5X in Device Manager here: Portable Devices\Nexus 5X
After the right driver installed, if I try again to update the driver using ""Search automatically for updated driver software", Windows 10 will actually install the wrong driver (ACER ADB) back!
Thank you all in this thread to help me exclude other possibilities, lock down the culprit and finally solve the issue!
Just got a Nexus 5X, and I'm having the same problem under Windows 10. I don't see an Acer device in Device Manager though, I see a "Nexus 5X" under "Other devices" with a yellow triangle exclamation mark.
When I tried following the steps, I don't have "Show compatible hardware" nor "MTP USB Driver". When I tried installing "MTP Device", I get an error "The install class is not present or is invalid."
cigar3tte said:
Just got a Nexus 5X, and I'm having the same problem under Windows 10. I don't see an Acer device in Device Manager though, I see a "Nexus 5X" under "Other devices" with a yellow triangle exclamation mark.
When I tried following the steps, I don't have "Show compatible hardware" nor "MTP USB Driver". When I tried installing "MTP Device", I get an error "The install class is not present or is invalid."
Click to expand...
Click to collapse
Were you ever able to get this working on your PC?
azsl1326 said:
Were you ever able to get this working on your PC?
Click to expand...
Click to collapse
Yeah, and it's been a while so I don't remember exactly, but I think it was a different cable that made it work.
I've switched to a Droid Turbo 2. The 5X didn't have enough battery life for my usage.
thanks
i fuking love u
SadsArches said:
i fuking love u
Click to expand...
Click to collapse
Huh? LOL
Sent from my Nexus 5X using Tapatalk
Brilliant! Solved and excellently described. Many thanks.
Bruce
cigar3tte said:
Just got a Nexus 5X, and I'm having the same problem under Windows 10. I don't see an Acer device in Device Manager though, I see a "Nexus 5X" under "Other devices" with a yellow triangle exclamation mark.
When I tried following the steps, I don't have "Show compatible hardware" nor "MTP USB Driver". When I tried installing "MTP Device", I get an error "The install class is not present or is invalid."
Click to expand...
Click to collapse
If you have other android devices that is working on your PC, you'll notice that the driver used is the "wpdmtp.inf" you can get it on your 64-bit Windows on this location:
"C:\Windows\WinSxS\amd64_wpdmtp.inf_31bf3856ad364e35_10.0.16299.15_none_42867195f7d5106b\wpdmtp.inf"
Locate this file via device manager and choose "MTP USB Device"
And viola! You can now transfer files again in your Nexus 5x!
I am in the same boat but my PC stopped recognizing my phone at all. PC will see all my other devices including my pixel 2xl. But every since that Nov update I believe my PC's and diffet cables does not show up at all. Have read all the threads and so far nothing has worked for me.
Travisdroidx2 said:
I am in the same boat but my PC stopped recognizing my phone at all. PC will see all my other devices including my pixel 2xl. But every since that Nov update I believe my PC's and diffet cables does not show up at all. Have read all the threads and so far nothing has worked for me.
Click to expand...
Click to collapse
Did you get it working again? I have 2 other phones working fine but the nexus5x disappeared and cant get it back. Even deleted the cache and the data for the System apps named "External Storage and Media Storage" as some suggested. Shows up as unknown device now.
AlienTeck said:
Did you get it working again? I have 2 other phones working fine but the nexus5x disappeared and cant get it back. Even deleted the cache and the data for the System apps named "External Storage and Media Storage" as some suggested. Shows up as unknown device now.
Click to expand...
Click to collapse
Nope, was never able to find a fix. If you do please let me know.
Yes I got it working. Since longer USB cables only shows unknown device I installed android development system and it made no difference.. But I had a 6inch charging cable that came with my power brick and I tried that and viola the Nexus showed up.. Not as a nexus 5x like before but as something like romaster composite ADB interface or something and I was able to flash TWRP recovery so now I can at least get access to it. Backed up the memory to a flash drive.. Have not flashed SU or anything yet but that should not be a problem with TWRP installed.. And like usual it takes a few flashes and rebooting into TWRP for it to stick other wise the recovery goes away.. Still dont know why the longer USB cables make any difference.. I even tried it out on a USB extension socket which is a 20 foot long USB extender and that also works.. So it must be something else like when I had the MB changed the adapter I was using did not work for data transfer.. Might be using some wire that is missing in the longer cable..
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 !!!
I got my OP3 today and am trying to unlock the bootloader. I've tried every tutorial and toolkit out there but they all get stuck at the same point in adb, "waiting for device". The "adb devices" command works fine but anything else gets stuck on "waiting for any device". I've tried googling the issue but none of the suggestions have worked so far. Any input would be great.
did you enable oem unlocking from developer options?
bro you may be running win 10 and to connect fastboot on that u need adb driver which u will find on windows update all u have to do is just connect your phone with data transfer mode and update the window 10 . ull find something name qalllcom its adb drive or i dont but after that it will like charm.
I have all the necessary developer options checked. After futzing with it for hours, I tried a different computer (also Windows 10) and it worked right away. I'm going to see what the driver issue is this evening because I still would like to use the original computer I was using. Thanks for the replies!
What does "adb devices" return?
aadityarulez said:
What does "adb devices" return?
Click to expand...
Click to collapse
Screenshot:
for bl unlock, you need to be at fastboot mode, and installed right driver, for me working any of stock Google USB package fastboot bootloader driver.
Go to fastboot mode and do "fastboot devices", then try unlocking bl.
You can install the driver after disabling the driver enforcement..
Sent from my Xiaomi Mi 5 using XDA Labs
harish15 said:
You can install the driver after disabling the driver enforcement..
Sent from my Xiaomi Mi 5 using XDA Labs
Click to expand...
Click to collapse
I've tried everything including disabling driver enforcement on Win 10 but I still have the same issue. I have the wrong drivers installed. I've tried uninstalling and reinstalling the drivers but when I plugin the phone, the wrong drivers get installed. I got it to work on another Windows 10 computer and below are device manager screenshots of the working (with right drivers) and not working (with wrong drivers) computers. I have no idea how to get the right drivers installed on the computer where its not working and unfortunately, its the primary computer I use.
shobuddy said:
I've tried everything including disabling driver enforcement on Win 10 but I still have the same issue. I have the wrong drivers installed. I've tried uninstalling and reinstalling the drivers but when I plugin the phone, the wrong drivers get installed. I got it to work on another Windows 10 computer and below are device manager screenshots of the working (with right drivers) and not working (with wrong drivers) computers. I have no idea how to get the right drivers installed on the computer where its not working and unfortunately, its the primary computer I use.
Click to expand...
Click to collapse
Right click, uninstall the wrong drivers.. Tick delete button too in the dialog prompt. Try installing now.
Sent from my Xiaomi Mi 5 using XDA Labs
harish15 said:
Right click, uninstall the wrong drivers.. Tick delete button too in the dialog prompt. Try installing now.
Sent from my Xiaomi Mi 5 using XDA Labs
Click to expand...
Click to collapse
I've tried this several times over. I do not get the tick option to delete.
shobuddy said:
I've tried this several times over. I do not get the tick option to delete.
Click to expand...
Click to collapse
Pm me, if case, you need some guidance.
Sent from my Xiaomi Mi 5 using XDA Labs
Same here. When I reboot in fastboot mode, the driver adb interface disappears and I get the Android Bootloader Interface (Kedacom USB Driver).
"waiting for any device" each time.
Thx for help
shobuddy said:
I've tried this several times over. I do not get the tick option to delete.
Click to expand...
Click to collapse
Try this:
Connect the op3 to usb port - don't bother changing from "charging"
Right click on "ADB Interface" in dev man and disable it.
Without unplugging the op3 use the buttons to reboot into bootloader.
Hopefully W10 will now detect your op3 and either load the correct "oneplus" driver or create a new entry in dev man of Other Devices > Android Composite ADB Interface. Right click on this and then Update driver software > Browse my computer.... > Let me pick... > and if you're lucky One plus will show up in the manufacturer column and allow you to select the composite interface
peterk-1 said:
Try this:
Connect the op3 to usb port - don't bother changing from "charging"
Right click on "ADB Interface" in dev man and disable it.
Without unplugging the op3 use the buttons to reboot into bootloader.
Hopefully W10 will now detect your op3 and either load the correct "oneplus" driver or create a new entry in dev man of Other Devices > Android Composite ADB Interface. Right click on this and then Update driver software > Browse my computer.... > Let me pick... > and if you're lucky One plus will show up in the manufacturer column and allow you to select the composite interface
Click to expand...
Click to collapse
I tried this but didn't see any new/different entry in DM when I rebooted into bootloader. Didn't see OnePlus under manufacturers either.
cyspak said:
Same here. When I reboot in fastboot mode, the driver adb interface disappears and I get the Android Bootloader Interface (Kedacom USB Driver).
"waiting for any device" each time.
Thx for help
Click to expand...
Click to collapse
Okay so this is the problem. I figured it out 2 days ago.
check the bootloader driver when you're in fastboot. Right click it and update driver, it should be the Android Bootloader 9.00, and not Bootloader 11.00
it's a silly weird fix, but it should be under Android and not Kedacom
I was using the Android SDK Studio Platform Tools and Google Drivers provided from SDK Studio
deleted
Similiar to the previous users post I'll try and be a bit more clear.
unplug your device if plugged in.
boot in to fastboot mode on your device.
Go to your PC and access device manager
plug your device in and you should see
"kedacom" instead of android interface
now inside you wanna click update driver
browse my compute for driver software > let me pick from a list of driver software > "Android adb sooner interface"
if its not that exact one check for the one that does say adb interface.
https://www.youtube.com/watch?v=Gdl6P2akRK0
I created a bootable USB drive with Linux Mint to solve my problem. It was Windows 10 that would recognize my OnePlus 3 in "Fastboot Mode" with Kedacom drivers.
After upgrading to Android Q suddenly my pc can't recognize my pixel as a android device also i can't connect any wired things such as dongle jack or USB Transfer (USB charging options disappeared).
Planning to downgrade to Pie but the problem is my device can't be detected on my pc. Any solutions? Thanks
If you're using a Microsoft Windows machine, I would suggest uninstalling any "Android" drivers from the Device Manager. Then restart the PC, then turn off "USB debugging" and back on for the Pixel, and even "Revoke authorizations" in hopes that it will re-alert & request another authorization and, therefore, verify it being connected and detected on the PC....
After all that -- or if you can only enter in Bootloader Mode -- type the command "fastboot devices" and say here what it outputs. If anything, while in Bootloader Mode, do what I previously said, but look for anything "Android" and "Bootloader" and uninstall those device drivers...
Good luck and hope this helps!
simplepinoi177 said:
If you're using a Microsoft Windows machine, I would suggest uninstalling any "Android" drivers from the Device Manager. Then restart the PC, then turn off "USB debugging" and back on for the Pixel, and even "Revoke authorizations" in hopes that it will re-alert & request another authorization and, therefore, verify it being connected and detected on the PC....
After all that -- or if you can only enter in Bootloader Mode -- type the command "fastboot devices" and say here what it outputs. If anything, while in Bootloader Mode, do what I previously said, but look for anything "Android" and "Bootloader" and uninstall those device drivers...
Good luck and hope this helps!
Click to expand...
Click to collapse
Thanks for replying, i already tried to uninstall android driver, but when i try to reconnect, my pc recognize my device as "unknown device"
blancheSX said:
Thanks for replying, i already tried to uninstall android driver, but when i try to reconnect, my pc recognize my device as "unknown device"
Click to expand...
Click to collapse
what about the other things I suggested?
Or, so it can be clearer, are you in the System/OS when plugging/reconnecting or in Bootloader Mode?
I ran across the same issue..I followed this video to get rid of the old USB drivers and updated to the new Android driver.. Now my window 10 recognize my pixel 2xl storage completely.
https://youtu.be/Zc_dhxc8iJU
I have this issue before, and after all i got my phone detected. But when i flash it, it say unbootable slot in fastboot screen. After couple onf time, it cant be flashed again and die.... My phone cant turn on in fastboot mode again, it bricked
I had to use the USB dongle to connect a flashdrive to my phone, wait for it to recognize the drive, then unplug the drive and dongle... Then connect phone to PC... Profit!
If anyone is still having the issue of PC not recognizing device in fastboot, please be sure you have UNinstalled the older version(s) of SDK Tools from yhour PC and make sure to INSTALL the latest versions.
You can find the latest version linked in the 9x guide in my signature.
Also, make sure you have both older and newer USB cables handy. The Pixel has a nasty reputation for being finicky with USB cables, try diff cables and different USB ports on your PC.
There is also a basic troubleshooting guide in the same link in my sig.
Best regards!
simplepinoi177 said:
what about the other things I suggested?
Or, so it can be clearer, are you in the System/OS when plugging/reconnecting or in Bootloader Mode?
Click to expand...
Click to collapse
i did in 2 conditions, first one is my device turned On (adb is not detected) also 2nd one is my device in bootloader mode (fastboot devices is not detected too)
been trying to update my driver but i always got (error code : 10, device cannot started) i dunno what to do right now
dallas90733 said:
I ran across the same issue..I followed this video to get rid of the old USB drivers and updated to the new Android driver.. Now my window 10 recognize my pixel 2xl storage completely.
https://youtu.be/Zc_dhxc8iJU
Click to expand...
Click to collapse
i tried those tuturial and ended in error code : 10, device cannot started.
SageWilliams said:
I had to use the USB dongle to connect a flashdrive to my phone, wait for it to recognize the drive, then unplug the drive and dongle... Then connect phone to PC... Profit!
Click to expand...
Click to collapse
whenever i try to connect a flashdrive with my dongle, there is no option or something, it's just usb charging option appeared.
blancheSX said:
i did in 2 conditions, first one is my device turned On (adb is not detected) also 2nd one is my device in bootloader mode (fastboot devices is not detected too)
been trying to update my driver but i always got (error code : 10, device cannot started) i dunno what to do right now
Click to expand...
Click to collapse
blancheSX said:
whenever i try to connect a flashdrive with my dongle, there is no option or something, it's just usb charging option appeared.
Click to expand...
Click to collapse
So…without you being too definitive…it seems that you’re able to get into your OS…
What I’d like you to do is uninstall and remove Google usb drivers on your computer. Then, download it again HERE: https://dl-ssl.google.com/android/repository/latest_usb_driver_windows.zip . And, in case things don’t work out this time around, if you can please save the (.zip) file on your Desktop or root folder (usually the C: drive). I might have you direct the device detected to the files in this .zip directly.
Then, after installing the USB drivers, I’d like you to uninstall and remove any/all things that are named “platform-tools” (so there will only be ONE "platform-tools" after you re-download it in this step) on the whole device. After, I’d like you to download the latest Windows version HERE: https://developer.android.com/studio/releases/platform-tools . Again, to simplify things, if you can extract it either in your Desktop or root folder (C: drive).
Again, like I mentioned before, I would like for your device to request authorization for your computer again, so if you can please go to the Developers option, and select “Revoke USB debugging authorizations” as well as double-checking you have "USB debugging" enabled…
Only THEN, once these two things are extracted and installed (as is the case in the first step) and you revoked the authorizations, can you plug in your device and USB cord. Watch your phone/device, as it will ask for authorization to connect to your computer, and you’ll have to make sure the box is checked that says “don’t ask this every time” or “remember this device” – I can’t recall off-hand – and then make sure to “Allow” it. By doing this, you can be sure that your computer and device are talking correctly.
*One suggestion that isn’t mandatory is that you select where it says “USB charging” and change it to “MTP” or “file-sharing” (sorry, again, I can’t recall specifically off the top of my head…)
If all things are working well, if you can open up a command prompt (a.k.a. “cmd”, and also make sure you are running it “As an administrator”) and direct it to the platform-tools directory (hopefully you followed my suggestion and kept it simple so it will either be at the root “C:\” or on your Desktop “C:\Users\[username]\Desktop” so it won't be too difficult directing it there...), and run the commands
Code:
adb devices
and
Code:
fastboot --version
.
Hopefully, if you do all of these things, it might get things reset and working from a stable established set up.
If it somewhat works, but the device in your "Device Manager" is showing up something "funky", then it'll take a rather nuanced Windows troubleshooting technique to resolve where I would have you correct the wrong entry/driver in the "Device Manager" and have it specifically point to one of the contents of the .zip files; shown prior.... We'll tackle that if need be and if all this initial beginning troubleshooting doesn't pan out...
Let me/us know how it works out, good luck, and hope this all ends up being helpful…
simplepinoi177 said:
So…without you being too definitive…it seems that you’re able to get into your OS…
What I’d like you to do is uninstall and remove Google usb drivers on your computer. Then, download it again HERE: https://dl-ssl.google.com/android/repository/latest_usb_driver_windows.zip . And, in case things don’t work out this time around, if you can please save the (.zip) file on your Desktop or root folder (usually the C: drive). I might have you direct the device detected to the files in this .zip directly.
Then, after installing the USB drivers, I’d like you to uninstall and remove any/all things that are named “platform-tools” (so there will only be ONE "platform-tools" after you re-download it in this step) on the whole device. After, I’d like you to download the latest Windows version HERE: https://developer.android.com/studio/releases/platform-tools . Again, to simplify things, if you can extract it either in your Desktop or root folder (C: drive).
Again, like I mentioned before, I would like for your device to request authorization for your computer again, so if you can please go to the Developers option, and select “Revoke USB debugging authorizations” as well as double-checking you have "USB debugging" enabled…
Click to expand...
Click to collapse
thanks for ur explanation, and i'm sure i already did this 100% as you mentioned before. looking for solution and i found this at pixel community thread : https://support.google.com/pixelphone/thread/14477635?hl=en
and btw when i try to disable and back to enable (again) USB debugging, there's no pop up or something like that, just nothing appear. so i just realized why i got error code : 10 is just because my phone still not detected by PC also i tried in other computer (with windows 8.1 installed) my device is got detected but as "device descriptor request failed" not as an android device. Hopefully next update google will fix this "bug". Once again thank you very much
blancheSX said:
thanks for ur explanation, and i'm sure i already did this 100% as you mentioned before. looking for solution and i found this at pixel community thread : https://support.google.com/pixelphone/thread/14477635?hl=en
and btw when i try to disable and back to enable (again) USB debugging, there's no pop up or something like that, just nothing appear. so i just realized why i got error code : 10 is just because my phone still not detected by PC also i tried in other computer (with windows 8.1 installed) my device is got detected but as "device descriptor request failed" not as an android device. Hopefully next update google will fix this "bug". Once again thank you very much
Click to expand...
Click to collapse
Yeah...I figured as much...I was just making sure to lay down the "ground work" before proceeding...
If you're still willing....what I had planned next was to walk you through manually updating/"editing" the driver (on the PC) to directly look at the Google usb drivers specifically to try and get around the whole "device descriptor" and other (detection) error codes.......
Might want to try uninstall the SDK toolkit, reboot PC, then install the latest SDK toolskit.
Also having both USB 2.0 and 3.0 cables saved me more than once, and is a known thing on the 2XL.