Related
Ok, I've just upgraded to windows 7. I was pretty psyched about the whole thing, and my computer seems like a whole new machine, coming from XP 32 bit.
So one thing I'm attempting to get adb to work with my phone. Heres my first problem - right off the bat, my computer doesnt recognize my phone as anything but an unknown device. YES I'VE TRIED DEBUGGING, DISK DRIVE, ETC., but nothing works.
I go to device manager, all I see is unknown device. Ok fine. I download the adb files that allow you to download the Android 2.1 thing and usb drivers. Still nothing works. I go to device manager, try to update the drivers for said "unkown device" and i get a message "the drivers are the newest up to date" or something. I try downloading the 64-bit HTC Hero drivers, same thing. I download and install HTC Sync, same thing.
I get this message when I plug the phone in...
"USB Device not recognized
One of the usb devices attached to this computer has malfunctioned, and Windows does not recognize it. For assistance in solving this problem, click this message"
So my question is, how do i get my computer to recognize my phone, even as storage device??
jasongthang said:
Ok, I've just upgraded to windows 7. I was pretty psyched about the whole thing, and my computer seems like a whole new machine, coming from XP 32 bit.
So one thing I'm attempting to get adb to work with my phone. Heres my first problem - right off the bat, my computer doesnt recognize my phone as anything but an unknown device. YES I'VE TRIED DEBUGGING, DISK DRIVE, ETC., but nothing works.
I go to device manager, all I see is unknown device. Ok fine. I download the adb files that allow you to download the Android 2.1 thing and usb drivers. Still nothing works. I go to device manager, try to update the drivers for said "unkown device" and i get a message "the drivers are the newest up to date" or something. I try downloading the 64-bit HTC Hero drivers, same thing. I download and install HTC Sync, same thing.
I get this message when I plug the phone in...
"USB Device not recognized
One of the usb devices attached to this computer has malfunctioned, and Windows does not recognize it. For assistance in solving this problem, click this message"
So my question is, how do i get my computer to recognize my phone, even as storage device??
Click to expand...
Click to collapse
try uninstalling htc sync and using a different usb port. does that work?
And to address how to get it to recognize as a drive, when you plug it in you should be presented with options where you can make it a disk drive. Or pull down your notification bar and change the type.
elegantai said:
And to address how to get it to recognize as a drive, when you plug it in you should be presented with options where you can make it a disk drive. Or pull down your notification bar and change the type.
Click to expand...
Click to collapse
On the phone yes, I can select a different type. On my computer, I just get that unknown device message.
And out of the blue I just tried a different USB port, and now it works as a storage device.
Did you restart the computer after installing the drivers? Sometimes mine gets a little goofy like that.
jasongthang said:
On the phone yes, I can select a different type. On my computer, I just get that unknown device message.
And out of the blue I just tried a different USB port, and now it works as a storage device.
Click to expand...
Click to collapse
i had that issue with one of my usb ports too. i think sometimes a bank of usb ports are used as basically a usb hub, and the evo doesn't like that, from what i understand.
Reboot comp, reboot EVO. Connect 'em, and then go into Device Manager, uninstall the "unknown device" (EVO), and then have it scan for new devices. Now, when it says scanning for drivers (or something to that effect) look for an advanced or "skip checking Windows Update for drivers" option. Then navigate to the ADB drivers in the Android SDK and tell it to use those. Make sure you have USB Debugging turned on, and EVO's set for "Charging Only".
If that still doesn't work, then there's an incompatibility with your computer's USB controller and Win7.
drmacinyasha said:
Reboot comp, reboot EVO. Connect 'em, and then go into Device Manager, uninstall the "unknown device" (EVO), and then have it scan for new devices. Now, when it says scanning for drivers (or something to that effect) look for an advanced or "skip checking Windows Update for drivers" option. Then navigate to the ADB drivers in the Android SDK and tell it to use those. Make sure you have USB Debugging turned on, and EVO's set for "Charging Only".
If that still doesn't work, then there's an incompatibility with your computer's USB controller and Win7.
Click to expand...
Click to collapse
lol, I did all that a few times, but im sure its not an incompatibility issue. probably just a skipped step somewhere.
jasongthang said:
lol, I did all that a few times, but im sure its not an incompatibility issue. probably just a skipped step somewhere.
Click to expand...
Click to collapse
If your computer is old enough, incompatibility is a possibility. See if there's other ports you can use, like on a different side of the case. Also, what brand computer?
--Swyped from my EVO using XDA App.
drmacinyasha said:
If your computer is old enough, incompatibility is a possibility. See if there's other ports you can use, like on a different side of the case. Also, what brand computer?
--Swyped from my EVO using XDA App.
Click to expand...
Click to collapse
stop! lol its fine. it works. i guess i should have stated that i've been on these forums for quite a while, and have flashed and rooted a few different phones using this computer, but with xp.
i just switched to windows 7, and of course lost all my drivers, and everything I had saved would have to be switched to 64-bit. I just couldnt get anything to work, but it seems to work now.
and I dont know what brand necessarily this computer is. i built it. I do have a dell keyboard though.
Good day,
I'm having problem with my DHD unable to be recognized in my Win 7 PC. I have already install HTC Sync and also tick on "Ask Me" for Connect To PC setting. I'm running on stock 3.13.707.4 ROM with S-ON and unrooted. Even restart to Fastboot my PC still unable to recognized my DHD.
From Googling it shows many Desire having USB-Brick problem, does this problem also applied to DHD? Is it my phone is hit by USB-Brick? Any guide to solve this problem? I've tried flashing older ROM via Bootloader and PD98IMG.zip but it won't allow saying something like the ROM is older version.
I just bought this used phone for about a week so I'm still not sure on how to solved this problem. any helps is much appreciated.
are you using the original cord that came with the phone? just any old usb cable won't work
also you can't flash a new rom without rooting and gaining S-OFF, you're unrooted and S-ON, that's why you get the "version is older" message
maatsby said:
are you using the original cord that came with the phone? just any old usb cable won't work
also you can't flash a new rom without rooting and gaining S-OFF, you're unrooted and S-ON, that's why you get the "version is older" message
Click to expand...
Click to collapse
I bought the phone and it came with 1 cord (with HTC label) that can be connected to the charger, I guess there are only 1 cord for charging and connect to PC? This is the cord that I use. In addition to that I have also tried Motorola, Sony Ericsson (both also for Android phone) and Nokia cord but all can't.
The ROM is actually older version stock ROM from RUU.exe. I saw from few Desire thread they were using this method to restore the ROM to before the USB Brick condition so I thought to try it.
BUMP!
Anyone know what should I do to resolve this problem?
Are you running the very latest HTC Sync on your PC? I'm using 3.0.5606. You can get it here: http://www.htc.com/www/help/
Also, connect your phone and go into Device Manager on your PC. Check to see if you have an entry for Android USB Devices and that the phone shows up. See attached screenshot for how mine looks. This is the best place to check to see if your PC has installed the drivers correctly.
In answer to your question about the cable, yes it's the same cable that attaches to the PC or to the mains charger. I've sometimes had connection problems caused by a dodgy cable, but I've used others apart from the HTC one without issues.
Edit: Also, when you install HTC Sync it should warn you to disable Antivirus software during the installation. This can be really important! I ignored it the first time around, thinking it was just a silly precaution, and had loads of problems with the phone not being recognised. Had to uninstall, temporarily disable AV, and re-install HTC Sync. Once it has finished installing, you can turn your AV back on.
Thank you for your reply preacher6.
Yes, I'm using the latest HTC Sync, v3.0.5606, just downloaded yesterday and reinstall everything.
When my phone connected to the PC it didn't appear as Android USB Device on my Device Manager, it only appear as Unknown Device in USB Controller:
So I guess I can rule out the cable as I have tried about 4 cables already.
For the installation part, I have disable the anti virus and also running the setup program as administrator. When installing there is no problem whatsoever that crop out.
Another point is, even on Fastboot it appear as Unknown Device in the PC.
I would try to update the driver manually - right click on the Unknown device, go to "install driver" or "update driver", then browse to the "Program Files\HTC\HTC Driver" folder. See if it picks up and installs the correct driver.
I've tried manually update the driver as per your advise but it says there is no compatible driver in that folder even though androidusb.inf is in that folder.
I'm running Win 7 64bit. does the driver also work for 64bit OS?
Should do, yes, I'm on Win7 64 bit myself. There is this folder on my PC:
C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64
Is the unknown device present when the phone isn't connected? Just to make sure that is actually the phone - if it's still there when the phone isn't connected, it's some other device.
Otherwise try uninstalling the unknown device and then rebooting the PC, then forcing the installation of the drivers again.
The folder is same as yours.
The unknown device does not present when my DHD is not connected, so I'm certain it is the phone that appear as unknown device.
I have tried uninstalling the unknown device > reboot PC > installing the driver but it still won't install.
Another thing is, I check on the Device Manager > Unknown Device properties > Details" for it's Hardware Ids and it shows as USB\UNKNOWN. I think it should show a strings of the device id? Correct me if I'm wrong.
Yep, there should be a proper device ID string, on charge mode mine shows a hardware ID of USB\VID_0BB4&PID_0CA2&REV_0226&MI_01.
At this point the best thing I can suggest is to try on another PC. If it works, your drivers are screwed up and you'll need to strip them and reinstall. But if it doesn't work on another PC, it's possible you have a hardware problem with the phone.
xb360 said:
Good day,
I'm having problem with my DHD unable to be recognized in my Win 7 PC. I have already install HTC Sync and also tick on "Ask Me" for Connect To PC setting. I'm running on stock 3.13.707.4 ROM with S-ON and unrooted. Even restart to Fastboot my PC still unable to recognized my DHD.
From Googling it shows many Desire having USB-Brick problem, does this problem also applied to DHD? Is it my phone is hit by USB-Brick? Any guide to solve this problem? I've tried flashing older ROM via Bootloader and PD98IMG.zip but it won't allow saying something like the ROM is older version.
I just bought this used phone for about a week so I'm still not sure on how to solved this problem. any helps is much appreciated.
Click to expand...
Click to collapse
Hi. This thread is pretty old but I'm wondering if you ever resolved the issue? I'm having exactly the same problem with my HTC One s and I can't seem to find a solution anywhere.
THanks
dmastman83 said:
Hi. This thread is pretty old but I'm wondering if you ever resolved the issue? I'm having exactly the same problem with my HTC One s and I can't seem to find a solution anywhere.
THanks
Click to expand...
Click to collapse
Yes. Holla if you still need help
marknoll said:
Yes. Holla if you still need help
Click to expand...
Click to collapse
I need help too (HTC Desire Z device)
Is it hardware problem? (I already purchased new system board).
For me it looks like hardware problem, because device does not accept bus address, do not show USB strings/VID/PID (Tried different cables/PCs/OSes (I have OpenSUSE linux, but phone does not connect to usb on any PC, Windows PCs even do not understand that something plugged in)).
No problems with USB-connector (checked resistance), but I do not see pull-down resistance with my tester.
But all other functions work well.
UPD. Tried to connect from FASBOOT/HBOOT/Android - the same result, device does not accept bus adress. Additionally it charges without problems, but when I connect phone to USB no pop-up/information at top bar appears.
FossaFX said:
I need help too (HTC Desire Z device)
Is it hardware problem? (I already purchased new system board).
For me it looks like hardware problem, because device does not accept bus address, do not show USB strings/VID/PID (Tried different cables/PCs/OSes (I have OpenSUSE linux, but phone does not connect to usb on any PC, Windows PCs even do not understand that something plugged in)).
No problems with USB-connector (checked resistance), but I do not see pull-down resistance with my tester.
But all other functions work well.
UPD. Tried to connect from FASBOOT/HBOOT/Android - the same result, device does not accept bus adress. Additionally it charges without problems, but when I connect phone to USB no pop-up/information at top bar appears.
Click to expand...
Click to collapse
I am trying to understand what exactly are you asking me . are you asking me if the PC can recognize your device ?
marknoll said:
I am trying to understand what exactly are you asking me . are you asking me if the PC can recognize your device ?
Click to expand...
Click to collapse
Sorry, it looks like I explained my question wrong (I'm Russian, and English do not native to me). Let me try reformulate:
You said "Yes. Holla if you still need help" so I believe that you were able to fix "Device not recognized" problem. So I'm asking - how did you do it? Did problem was hardware or software?
For me (look at symptoms at my previous message) it looks like dead USB controller in phone. But maybe it very strange software problem (USB-controller firmware damaged)?
Did I explain it clear now?
Install the SDK on PC and update all android versions.
Well guys it was just my PC, i made a system backup for four days and that was all the problem(the USB port of my PC)
FossaFX said:
Sorry, it looks like I explained my question wrong (I'm Russian, and English do not native to me). Let me try reformulate:
You said "Yes. Holla if you still need help" so I believe that you were able to fix "Device not recognized" problem. So I'm asking - how did you do it? Did problem was hardware or software?
For me (look at symptoms at my previous message) it looks like dead USB controller in phone. But maybe it very strange software problem (USB-controller firmware damaged)?
Did I explain it clear now?
Click to expand...
Click to collapse
After installing and updating SDK...go into platform folder and open it. Hold mouse in field and hold shift and right click mouse. Chose "open cmd here"..that will open a cmd prompt window. In regular mode on phone,type "adb devices" should return numbers (ex: hta3829g)..if in bootloader mode,type "fastboot devices" should return numbers.
This SDK helps PC see your phone when its plugged in. Especially handy when a PC won't install drivers for your phone
Sent from my ATRIX HD
Are you also stating that your device will no longer charge when plugged in?
Sent from my ATRIX HD
I've read some people are having trouble with GN2 when connecting it to a PC via a USB cable. I've been having that problem as well.
I've found some suggested solutions, but none worked for me:
Code 10 error device manager
Missing Hardward ID fix
I found a partial solution. It's limited in what is solves. This is good for a user who is looking just to be able the phone USB storage so you can transfer files and what not. This does not give access for ADB. This will get rid of the need to plug and unplug the usb cord, or enable or disable USB debugging or whatever else people need to a bunch of times for the phone to finally be recognized by their machines. This works in Windows 7 64bit; I assume 32 bit. Don't know about Windows 8 (if there is the problem)
Basically, uninstall the Samsung USB drivers. Then just reconnect the GN2 to your PC. Let Windows install it's drivers. You'll see failures for Ssmsung and ADB, but still have access. You'll get the same access with and with USB debugging. Below are pics showing the results of driver installation by Windows, and hardware device properties. If you click the picture, you get see a large image of the screen shot.
Without USB debugging
WIth USB debuggind turned on:
Maybe someone with more knowledge can figure out the rest to complete fix the issue. But I assume for most, this should be sufficient.
lovekeiiy said:
I've read some people are having trouble with GN2 when connecting it to a PC via a USB cable. I've been having that problem as well.
I've found some suggested solutions, but none worked for me:
Code 10 error device manager
Missing Hardward ID fix
I found a partial solution. It's limited in what is solves. This is good for a user who is looking just to be able the phone USB storage so you can transfer files and what not. This does not give access for ADB. This will get rid of the need to plug and unplug the usb cord, or enable or disable USB debugging or whatever else people need to a bunch of times for the phone to finally be recognized by their machines. This works in Windows 7 64bit; I assume 32 bit. Don't know about Windows 8 (if there is the problem)
Basically, uninstall the Samsung USB drivers. Then just reconnect the GN2 to your PC. Let Windows install it's drivers. You'll see failures for Ssmsung and ADB, but still have access. You'll get the same access with and with USB debugging. Below are pics showing the results of driver installation by Windows, and hardware device properties. If you click the picture, you get see a large image of the screen shot.
Without USB debugging
WIth USB debuggind turned on:
Maybe someone with more knowledge can figure out the rest to complete fix the issue. But I assume for most, this should be sufficient.
Click to expand...
Click to collapse
Hey....Thanks so much!! It's a good start.
With all of the brilliant developer on these boards, I'm surprised no one has come up with a fix yet. In good time!!!!
I figured most users on here aren't needing to use ADB after rooting, but want to access storage. I tried accessing using ADB, which I have installed on my PC but never use, and it wasn't connecting. I had to look up how to use it. When I asked for listed devices, nothing came up.
If you look at the threads listed, it appears it's a driver issue with Samsungs USB drivers. I figure at some point either Samsung or Microsoft will fix it, more than the developers here. Although, I think they'll probably find a solution faster.
HA! I'm glad I'm not the only one. I've been rebooting my PC to solve the issue. It only happens once in a while. I'll be watching this thread. Thanks
I know this isn't exactly on topic but I've seen this discussed here and other forums as far as "properly" ejecting the Note 2/GS3 from your PC. Some say you just pull the USB, it will not corrupt etc. I just wanted to share that you can eject(windows). Just go to Devices and Printers, you will see SPH-L900 in your list. Right-click and eject. Probably means nothing but figured I'd share for those that feel iffy about just pulling the plug
I just pull my USB. I don't do the whole eject thing. The "having" to do the eject thing basically went out when Windows 7 arrived. I've been doing this method for couple years with Windows 7 for various devices. Never an issue.
And even faster than when you mention, if on WIndows 7, you go to the task bar to the right, there is a triangle that shows all your running background apps. Click that, right click the USB icon. It should be listed. If not, there is a "open devices and printers" which takes to the same place.
I have no idea what I do wrong, but this is what I tried:
I enabled adb mode on my Chinese watch
The watch is in fastboot mode
I installed all drivers, pdanet didn't work (no usb connected)
Once I put my cable in my laptop and it said: USB error, try again later or something like that?
no adb response in the commands. just blank... in the devices list, there is no sign of my watch...
It charges normally. I could really use your help
Somehow I found the chinese wear OS so I can use it. at least that is something. Is there any way to get in in English or Dutch without adb?
My other laptop seems to see a 'unknown usb device'. no adb device found...
I have no idea... maybe it's due to the unofficial cable?
I bought an expensive cable, the original, but no laptop can see the watch (windows 10 and windows 7)
The old cable is some sort of ok with the windows 7. I get an error 43 in devicemanagement.
Please help... I have no idea what I can do now...
https://forum.xda-developers.com/showpost.php?p=73472794&postcount=15
I've posted this many times in the various Huawei forums and it has worked for everyone so far.
First, remove all other drivers using USBDeview.
http://www.nirsoft.net/utils/usb_devices_view.html
Then use this tutorial to manually install the Google USB driver.
http://visualgdb.com/KB/usbdebug-manual/
Good luck!
edit - here is a fool proof method.
https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=71653349&postcount=12
I've posted this many times in the various Huawei forums and it has worked for everyone so far.
First, remove all other drivers using USBDeview.
http://www.nirsoft.net/utils/usb_devices_view.html
Then use this tutorial to manually install the Google USB driver.
http://visualgdb.com/KB/usbdebug-manual/
Click to expand...
Click to collapse
i am also bugged with this.
the win7-pc says unknown usb device detected. i turned dev mode and adb on.
then i tried to manually install the driver from the android sdk. when i try to select the driver windows says there were no driver found (but the driver is there) and i should make sure that the driver is written for x64-systems. WTF?
and even the watch does not charge wenn via usb 2.0 or 3.0 connected - but its connected cause of the message from the pc.
in the device manager the watch is listed as unknown device.
that's exactly my problem...
I have done everything. I'll try to connect it to my linux pc, I got an old laptop with ubuntu or something like that (haven't used it in ages)
maybe that will do the trick. I installed everything manually. my win10 can see an unknown device as well... but that's about it...
maybe dev mode is not working on some watches even when its enabled. or it has something to do with the 2.0 Version auf AW and it affects not every watch.
Its funny. I've been trying to get my HW1 watch to connect to my PC for a year now. Have tried numerous different cables and the original that came with my watch didn't work. Different PCs haven't worked either. Unless I'm that unlucky with all these OEM cables or the ADB debugging toggle really doesn't work for USB connections. It works just fine for bluetooth and wifi, neither of which allow you to unlock the bootloader. Guess I've got to wait for the next update manually and try again.
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.