Related
I've installed 2nd bootloader + TWRP + cyanogenmod for my kindle fire 8.9 hd, but now the device isn't showing up on my computer (windows 7 64bit.) It starts to install drivers but says "unidentified device" and fails. I looked around in settings on the actual tablet and couldnt find anything relevant. Is it possible I need to turn on adb debugging on the tablet again, and if so, where is it located in CM10.1?
I've tried rebooting and reinstalling adb drivers on my computer, but no dice.
It detects as a PTP device, but doesn't show up when I change it to MTP. adb devices doesn't list anything.
Any help would be greatly appreciated.
konasus said:
I've installed 2nd bootloader + TWRP + cyanogenmod for my kindle fire 8.9 hd, but now the device isn't showing up on my computer (windows 7 64bit.) It starts to install drivers but says "unidentified device" and fails. I looked around in settings on the actual tablet and couldnt find anything relevant. Is it possible I need to turn on adb debugging on the tablet again, and if so, where is it located in CM10.1?
I've tried rebooting and reinstalling adb drivers on my computer, but no dice.
It detects as a PTP device, but doesn't show up when I change it to MTP. adb devices doesn't list anything.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Yeah I had that problem just a few days ago. Turns out you just go to the setting and about section and tap the build number a few times to enable the developers options in setting. Then you will be able to select adb debugging.
AlexAquarium said:
Yeah I had that problem just a few days ago. Turns out you just go to the setting and about section and tap the build number a few times to enable the developers options in setting. Then you will be able to select adb debugging.
Click to expand...
Click to collapse
Sweet, that was really helpful. Now the device shows up in adb devices, but not in windows. I can't send or receive files.
This is really frustrating. You'd something something as simple as "how to connect cm10.1 kindle to computer" would be documented somewhere, but I cant seem to find it.
konasus said:
Sweet, that was really helpful. Now the device shows up in adb devices, but not in windows. I can't send or receive files.
Click to expand...
Click to collapse
Never had an issue not showing up in windows especially if the "adb devices" cmd now works in your windows. That seems odd. Maybe you should connect your kindle to pc and enter windows device manager under portable drivers and uninstall the kindle driver. Window will reinstall the driver once you disconnect and reconnect the kindle.
I have the exact same problem with my KFHD8.9 since I rooted and installed CM10 two days ago.
I also have Win 7 64, and I also can use it as PTP but not as an MTP (USB debugging is on).
I've tried installing and re-installing both ADB drivers provided here. Countless times I've tried to: reboot Kindle, restart my PC, removing unrecognized drivers in device manager and then reinstalling them when the Kidnle connects via USB.
I've even tried installing the Android SDK files with no success.
So far, I've spent more than 7 hours trying to fix this.
The closest I've gotton, was to manually direct the broken Kindle Fire HD driver in device manager to update via the ADB driver located in Program files (x86) folder- then it showed the kindle as being connected under the "safely remove hardware" icon in the notification area and showed as a working driver in device manager, but even then, the MTP won't work and won't show the Kidnle in my computer.
One of the most frustrating things about it is that I connected the Kindle to a 7 year old laptop we have and it was
recognized immediately in "my computer". So I know this means something is wrong with my laptop that
prevents it from being recognized.
Anyone have a suggestions? A solution?
After more than 7 hours trying to figure this out, I would really appreciate your help!
did you solve this?
I just flashed CM10.1 and have the same problem
Try this:
Disconnect kindle
Go to device manager
look for kindle
uninstall
connect kindle
I see that a1745 has tried something like this, but these USB drivers are really flaky. Worth a try.
You can also try toggling MTP mode.
Settings -> storage -> the 3 cube icon on the upper right -> USB computer connection -> and try toggling MTP.
Cronoss said:
Try this:
Disconnect kindle
Go to device manager
look for kindle
uninstall
connect kindle
I see that a1745 has tried something like this, but these USB drivers are really flaky. Worth a try.
You can also try toggling MTP mode.
Settings -> storage -> the 3 cube icon on the upper right -> USB computer connection -> and try toggling MTP.
Click to expand...
Click to collapse
thanks, it works now
I've never had a problem with android file transfer up till I rooted today. My wife has a stock Nexus 7 and I can plug her Nexus into my computer and the file transfer app will start. I have usb debugging turned on and the usb connection on my tablet is set to Media device.
Now as I'm typing this my Nexus has been connect to my mac for about an hour. I just went to the USB settings to make sure I had Media device selected and the file transfer window popped up out of nowhere. I killed it and tried again and it won't come up. Maybe in an hour or so if it does the same thing.
Any ideas as to what's going on? Very strange behavior.
Disable USB debugging.
Unplug/plug in your nexus.
The USB IDs change for some reason when you have USB debugging turned on and the MTP device isn't recognized as such. PTP (camera) mode continues to work for both cases though.
Thanks for the suggestion but It still fails. I disabled debugging and still can't connect. Switching USB modes didn't help either.
If that doesn't work uninstall the adb driver & then plug your tablet back in so it will reinstall
My next suggestion would to reboot the tablet with USB debugging turned off.
If that doesn't work, my next suggestion would be to delete the existing drivers and force reinstall.
All with USB debugging turned off.
johnnyninja said:
I've never had a problem with android file transfer up till I rooted today. My wife has a stock Nexus 7 and I can plug her Nexus into my computer and the file transfer app will start. I have usb debugging turned on and the usb connection on my tablet is set to Media device.
Now as I'm typing this my Nexus has been connect to my mac for about an hour. I just went to the USB settings to make sure I had Media device selected and the file transfer window popped up out of nowhere. I killed it and tried again and it won't come up. Maybe in an hour or so if it does the same thing.
Any ideas as to what's going on? Very strange behavior.
Click to expand...
Click to collapse
Make sure after you plug in your device you're looking at your tab and click OK on the pop up........
Sent from my Nexus 7
Thanks for all the suggestions. It's working now. I was just about ready to delete the driver and the tablet started to be recognized consistently. I was in the settings screen and toggled debugging on and off while plugging in the tablet. I noticed the info bar at the top alternating between showing "debugging" and "media device" and I selected each one a couple of times when they came up. I think that it finally worked through the ID confusion that was mentions. I'll follow the the rest of the instructions if the problem comes back.
Thanks again.
It's acting up again so I'm going to try deleting the drivers. I thought I knew what to do but I can't find any information. What's the procedure to delete the driver? I'm running os x lion
I've tried every suggestion in all of these threads so far & nothing worked. Even after I deleted the ADB drivers, windows 7 would automatically reinstall them. When I tried to update the drivers, win7 said they already had the best drivers (ADB).
Here's what worked for me:
I had to turn off USB debugging, delete the ADB drivers in Device Manager, then reboot the device while it's still plugged in. Windows recognized the device as an MTP device & installed the drivers before it even fully booted.
I'm not sure how I finally resolved the problem on my mac. I toggled debugging on and off and rebooted a couple of times. That may have done it. I also ran the adb script in the SDK platform-tools folder. I don't know what that script does exactly but possibly it reinitialized the driver and ID.
Anyway, hopefully these workflows will work for others.
johnnyninja said:
I'm not sure how I finally resolved the problem on my mac. I toggled debugging on and off and rebooted a couple of times. That may have done it. I also ran the adb script in the SDK platform-tools folder. I don't know what that script does exactly but possibly it reinitialized the driver and ID.
Anyway, hopefully these workflows will work for others.
Click to expand...
Click to collapse
Rooted my nexus 7 (2012) last night and struggling with my laptop not recognizing it. This thread solved it!
Delete the ADB on my window, toggle off debugging and restart the nexus 7 with usb connected to laptop. works like a charm.
Thank you!
Guys, my N4 got this problem too.. until just a few minute ago
I read somewhere ini goge groups (i think N5 group), and found explanation that we can change ADB or MTP "mode" on device manager. On "Androoid ADB Device" right click and select "Update Driver Software". Click "Browse My Computer for Driver Software" and then "Let me pick from blablabla...." And then select MTP USB Device, "next" and my N4 detected on Windows Explorer.
Hope it will be usefull for you guys.
Im new nexus 7 user, just OTA update to 4.4.2 and rooted using wugfresh..
But afterward when i connect to computer, my nexus didnt detected n i cannot assess my sdcard for file transfer.. Anyone can help?
Sent from my GT-I9070 using xda app-developers app
slaughterer0206 said:
Im new nexus 7 user, just OTA update to 4.4.2 and rooted using wugfresh..
But afterward when i connect to computer, my nexus didnt detected n i cannot assess my sdcard for file transfer.. Anyone can help?
Click to expand...
Click to collapse
Its a good chance that its a cable problem. Also got in Settings>Storage>[Menu]>Make sure 'MTP' is selected. You can try PTP as well I guess.
If you need to transfer file for emergency purposes use 'Airdroid' for the moment. I think you can use 'ES file explorer' but that would be a little more complicated.
cable work fine... i think some setting im missing or driver in my computer...
slaughterer0206 said:
cable work fine... i think some setting im missing or driver in my computer...
Click to expand...
Click to collapse
Download the WugFresh Nexus Toolkit. It has a setup for drivers, maybe that would help. You can also try adb push/pull commands to transfer files via usb.
Go to : settings >> Storage >> USB computer connection , then check the option you want ( MTP or PTP )
in some roms i was not able to connect my device till i uncheck USB debugging form Developer options menu
[ my english is not well ]
Archinux said:
Go to : settings >> Storage >> USB computer connection , then check the option you want ( MTP or PTP )
in some roms i was not able to connect my device till i uncheck USB debugging form Developer options menu
[ my english is not well ]
Click to expand...
Click to collapse
i done it... before i root, its work fine.... i able to transfer my file through usb,,,
just after rooting it doesn't appear in my computer
resolved my problem after founded this post
http://forum.xda-developers.com/showpost.php?p=47310943&postcount=338
uninstalled and removed the driver,
then reboot my tab with MTP on, debug mode off...
and it installed the driver for MTP which was missed before...
hehee...
:fingers-crossed:
I gave up getting my XP machine to see the Nexus (Windows 7 laptop is OK).
I now use AirDroid instead, so much quicker and without the hassle of cables, drivers etc.
m+a+r+k said:
I gave up getting my XP machine to see the Nexus (Windows 7 laptop is OK).
I now use AirDroid instead, so much quicker and without the hassle of cables, drivers etc.
Click to expand...
Click to collapse
I had connected n7 to winxp at my work computer without installing latest wmp-****. I do remember unpacking wmp-installer then manually installing some libs from it's dirs, but I do not remember if I had to add n7 vid&pid to some inf file. I will try and write some guide
MTP wintout installing WMP11
Hi,
This is just another guide how to install driver and access nexus 7 2013 in windows XP...
Get a WMP install for winXP
Extract it by using command:
Code:
wmp11-windowsxp-x86-xx-xx.exe /C /T:[full-path-to-dest-dir]
eg.
Code:
E:\_TEMP\8\>wmp11-windowsxp-x86-xx-xx.exe /C /T:e:\_temp\8\wmp11\
Go into extracted directory, we are interested in files: wmfdist11.exe and umdf.exe
Install them, one is User Mode Driver Framework and other one is "media framework"
Go to
Code:
%windir%\inf
( eg.:
Code:
C:\WINDOWS\inf
)
Make a copy of file wpdmtphw.inf and open original one in notepad.
Find section [VendorModels.NTx86] (or [VendorModels.NTamd64] if you have winxp 64bit)
At end of section add line:
Code:
; Nexus 7 2013 LTE
%GenericMTP.DeviceDesc%=MTP, USB\VID_18D1&PID_4EE2&REV_0228&MI_00
Reboot your computer. Unplug also your Nexus, also switch off USB Debugging because of that you will see two MTP devices and you might try install MTP drivers for debug (which fail, or windows will yell with code 10...)
Hook up Nexus and when windows popup about installing drivers, choose that you have driver and the location point to search set to
Code:
c:\windows\inf
, click next, windows might complain that this driver is not intended to use with this device, so give win a slap and wait patiently until windows install driver
Windows might install drivers twice, just remember to point to windows/inf directory or directory with google usb driver http://developer.android.com/sdk/win-usb.html
---------------
After almost a year I noticed I made a hell of mistake , There should be MI_00 (MI stands for Media Interface 0) not MI_01 (MI 01 is for ADB ). And There is no need for 1st line ( USB\VID_18D1&PID_4EE2&MI_00 ).
I am terribly sorry for committing such basic error.
I already fixed those error in this my "guide"...
Hello,
I cannot get the bootloader unlock working on my Win 8.1 laptop by any means. If I try through hasoon2000's toolkit, I get the error that the ADB server did not ACK (whatever that means). If I try using the command line and HTC's official method of getting the TokenID, I get a message that a certain ADB-related dll is not installed. I have installed the USB drivers that come with hasoon2000's toolkit about 4 times now. I installed the Android SDK and even Samsung USB drivers. I'm going to uninstall everything, can someone walk me through the step-by-step to get things working? I've read that USB 3.0 is the problem, but I only have USB 3.0 ports on my laptop.
killfire72 said:
Hello,
I cannot get the bootloader unlock working on my Win 8.1 laptop by any means. If I try through hasoon2000's toolkit, I get the error that the ADB server did not ACK (whatever that means). If I try using the command line and HTC's official method of getting the TokenID, I get a message that a certain ADB-related dll is not installed. I have installed the USB drivers that come with hasoon2000's toolkit about 4 times now. I installed the Android SDK and even Samsung USB drivers. I'm going to uninstall everything, can someone walk me through the step-by-step to get things working? I've read that USB 3.0 is the problem, but I only have USB 3.0 ports on my laptop.
Click to expand...
Click to collapse
Use another computer if you can.
I had similar problems until I used this version of adb
http://www.mediafire.com/download/e5mieo2vxjd71ws/android-tools.zip
Run everything from the downloaded folder.
First of all ensure you have USB DEBUGGING enabled in DEVELOPER OPTIONS in the phone settings.
Open the downloaded folder then right click inside the folder while holding shift then choose 'Open command Windows here'
Plug in the phone using the original HTC usb cable then in the command window type ADB DEVICES. The response should be a device comprised of letters and numbers.
If you don't see any device attached try swapping the cable to another usb port. If you see your device attached then follow the unlock instructions at HTCDEV as its the most reliable way.
If still no device then it could be a usb driver problem. You should here a ding when you plug your phone in.
Make sure the Unlock_code.bin is in the above folder when unlocking.
ashyx said:
Run everything from the downloaded folder.
First of all ensure you have USB DEBUGGING enabled in DEVELOPER OPTIONS in the phone settings.
Open the downloaded folder then right click inside the folder while holding shift then choose 'Open command Windows here'
Plug in the phone using the original HTC usb cable then in the command window type ADB DEVICES. The response should be a device comprised of letters and numbers.
If you don't see any device attached try swapping the cable to another usb port. If you see your device attached then follow the unlock instructions at HTCDEV as its the most reliable way.
If still no device then it could be a usb driver problem. You should here a ding when you plug your phone in.
Make sure the Unlock_code.bin is in the above folder when unlocking.
Click to expand...
Click to collapse
That version of ADB didn't work for me either. Anyway I was able to get fastboot to work but not ADB so I was able to unlock and root and everything through a strange method using only fastboot.
Second question, if I am switching between AOSP roms, say for example CM to PA, can I dirty flash or do I have to reset?
ADB does not work with USB 3.0 ports yet on Windows 8 or 8.1. You have to use it on a USB 2.0 port. I have had best results with Windows 7. Fastboot, however, works just fine on 8.1 and 8
xeron72548 said:
ADB does not work with USB 3.0 ports yet on Windows 8 or 8.1. You have to use it on a USB 2.0 port. I have had best results with Windows 7. Fastboot, however, works just fine on 8.1 and 8
Click to expand...
Click to collapse
Not so, I and others have ADB working fine on USB 3.0 ports.
The problem is Windows 8 driver signing enforcement blocking the install of drivers. You need to go to advanced startup options to disable it.
Download these drivers first and extract: http://www.mediafire.com/download/i3lcm7dwl581518/ADB_Fastboot_Drivers_Win81.zip
Follow these instructions to disable driver signing enforcement: http://www.isunshare.com/windows-8/...gnature-enforcement-in-windows-8-and-8.1.html
Once fully booted go into device manager and you should see a device called 'Android 1.0' with an exclamation mark.
Right click 'Android 1.0' then 'update driver software' then 'Browse my computer for driver software'
Click the 'Browse' button and then browse to the driver folder 'ADB_Fastboot_Drivers_Win81' extracted earlier then click next to install the driver.
You will get a warning about unsigned drivers, just ignore and continue.
The drivers should install and you should see a new entry in device manager called 'Android phone' which means the ADB driver is installed.
ADB should now be working.
Thank you so much for this. Have been wondering for a very long time
Sent from my HTC One_M8 using XDA Free mobile app
It sounds like you've got plenty of technical help already, but I will say that I use ADB perfectly fine on my desktop with Win 8.1 so it's possible. I also use hassoon's toolkit occasionally with no issue.
Before I could get the desktop to recognize the M8 I had to completely uninstall all drivers related to my previous galaxy nexus as well as remove any mention of the device in Window's USBdeview. After a reboot, I just plugged in the M8 and windows automatically installed the necessary M8 drivers. I can then run fastboot and adb from the toolkit.
I ended up uninstalling the MSFT USB 3.0 drivers and use the Intel USB 3.0 drivers instead on my Win8.1 laptop that has only USB 3.0 ports. Works great.
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.