Let me share one solution that I developed recently.
At some point, after numerous reinstallation of Android, my HD2 become undiscoverable for MAGLDR as well as for Android flasher via USB Flasher. I wasn't able to flash anything. "Waiting for USB connection" was displayed until timed out. I did reset phone, removed battery, rebooted PC - nothing happened. I started to think about replacing USB cable.
Here is what helped at the end:
- Disconnect phone from PC
- Open Command Prompt
- Type "set devmgr_show_nonpresent_devices=1", Enter.
- Type "start Devmgmt.msc", Enter.
- Two commands above should be entered in the same command prompt window or it won't have an effect.
- When Device Manager opens select View->Show Hidden Devices
- Expand all nodes and remove all inactive devices - and icon of such device is grayed out
Here is an article about it http://support.microsoft.com/kb/241257
After that when I connected phone with USB cable system reinstalled drivers from scratch and I was able to flash.
:::Edited:::
Try killing any adb running in the background first
I'm not sure it is somehow connected with Android or ADB since when HD2 is in flasher mode it is not runnung Android. The device is detected like HTC Usb Sync or something like this.
Another option is to use updated flasher attached. I found it on russian forum.
hlvl said:
I'm not sure it is somehow connected with Android or ADB since when HD2 is in flasher mode it is not runnung Android. The device is detected like HTC Usb Sync or something like this.
Click to expand...
Click to collapse
Meh... I can't read. For some reason I read that you were talking about connecting your phone to the PC, i.e. within android, for USB mass storage etc....
Even the topic of the thread says otherwise. I'll go get my eyes tested...
Sometimes it's because ADB still in your PC memery, just force close it and everything will be fine.
As I said I tried to reboot PC but it didn't help. I doubt ADB start with Windows but rather only when you start using it.
hlvl said:
Another option is to use updated flasher attached. I found it on russian forum.
Click to expand...
Click to collapse
Do you mean that this is MAGLDR 1.13!?!?
hlvl said:
Let me share one solution that I developed recently.
At some point, after numerous reinstallation of Android, my HD2 become undiscoverable for MAGLDR as well as for Android flasher via USB Flasher. I wasn't able to flash anything. "Waiting for USB connection" was displayed until timed out. I did reset phone, removed battery, rebooted PC - nothing happened. I started to think about replacing USB cable.
Here is what helped at the end:
- Disconnect phone from PC
- Open Command Prompt
- Type "set devmgr_show_nonpresent_devices=1", Enter.
- Type "start Devmgmt.msc", Enter.
- Two commands above should be entered in the same command prompt window or it won't have an effect.
- When Device Manager opens select View->Show Hidden Devices
- Expand all nodes and remove all inactive devices - and icon of such device is grayed out
Here is an article about it http://support.microsoft.com/kb/241257
After that when I connected phone with USB cable system reinstalled drivers from scratch and I was able to flash.
Click to expand...
Click to collapse
Thanks man. I was already freaking out because of this.
I'm going to try this on my desktop, that's why I stopped using it lol
Sent from my HD2 using xda premium
Thanks! It worked very well!!
PG
Really thank you, you saved my phone
Mine has always done that. I just have to wait until the flasher program gets to the Looking for USB step and disconnect/reconnect the USB cable.
Or get a new cable. I had the same issue but even this guide didnt work. My cable needed replacing, luckily I had a spare in my closet. Tried it and bingo all the drivers installed. If it just wont find it, get a new USB cable.
I have the same problem but in bootloader my usb connection works...when i try to flash recovery with usb flasher mode in magdlr doesnt.
Wait for usb............and is stuck like that.So its not the cable..i tried to install new driver..i tried with command prompt....im freaking out!!
Installing WMDC 6.1 worked for me
hlvl said:
Let me share one solution that I developed recently.
At some point, after numerous reinstallation of Android, my HD2 become undiscoverable for MAGLDR as well as for Android flasher via USB Flasher. I wasn't able to flash anything. "Waiting for USB connection" was displayed until timed out. I did reset phone, removed battery, rebooted PC - nothing happened. I started to think about replacing USB cable.
Here is what helped at the end:
- Disconnect phone from PC
- Open Command Prompt
- Type "set devmgr_show_nonpresent_devices=1", Enter.
- Type "start Devmgmt.msc", Enter.
- Two commands above should be entered in the same command prompt window or it won't have an effect.
- When Device Manager opens select View->Show Hidden Devices
- Expand all nodes and remove all inactive devices - and icon of such device is grayed out
Here is an article about it http://support.microsoft.com/kb/241257
After that when I connected phone with USB cable system reinstalled drivers from scratch and I was able to flash.
Click to expand...
Click to collapse
Had same problem getting PC to recognize HD2 in order to Task29, etc...
I downloaded/installed WMDC 6.1 (for Vista, but works with W7) and walla... fixed! Link HERE.
Related
OK using a windows 8.1 Pro laptop, ADB installed properly with HTC Sync Manager, both Windows, HTC Sync Manager and the Device Manager in the Control Panel can see my phone. I tick on USB debugging and then press revoke USB debugging authorizations. Unplug my phone and plug it back in. I'm using the original USB cable from HTC. Everything pops up and shows like it's connected, except when I type in
Code:
adb devices
in the command prompt, then it just comes up blank. I've attached screen shots so you guys can see what I am talking about. If you have any ideas it would be much appreciated. I've attached some photos just to show that I've dotted all my i's and crossed all my t's as far as I can see. I also want to point out this is the second computer I've tried this on.
reubendevries said:
OK using a windows 8.1 Pro laptop, ADB installed properly with HTC Sync Manager, both Windows, HTC Sync Manager and the Device Manager in the Control Panel can see my phone. I tick on USB debugging and then press revoke USB debugging authorizations. Unplug my phone and plug it back in. I'm using the original USB cable from HTC. Everything pops up and shows like it's connected, except when I type in
Code:
adb devices
in the command prompt, then it just comes up blank. I've attached screen shots so you guys can see what I am talking about. If you have any ideas it would be much appreciated. I've attached some photos just to show that I've dotted all my i's and crossed all my t's as far as I can see. I also want to point out this is the second computer I've tried this on.
Click to expand...
Click to collapse
Might be a driver issues... Try those: https://www.dropbox.com/s/nr91z4bveeugaow/googleUSBdrivers.zip?dl=0
Sent from here
1) Unplug the phone from your computer
2) Uninstall anything related to HTC (drivers, sync managers..)
3) Reboot the computer
4) Install the latest (direct URL) HTC Sync Manager
5) I tend to uninstall the manager right afterwards (optional)
6) Reboot the computer & plug in your device
7) Report back
abyssis said:
1) Unplug the phone from your computer
2) Uninstall anything related to HTC (drivers, sync managers..)
3) Reboot the computer
4) Install the latest (direct URL) HTC Sync Manager
5) I tend to uninstall the manager right afterwards (optional)
6) Reboot the computer & plug in your device
7) Report back
Click to expand...
Click to collapse
Yeah that didn't work unfortunately
lukes91 said:
Might be a driver issues... Try those: https://www.dropbox.com/s/nr91z4bveeugaow/googleUSBdrivers.zip?dl=0
Sent from here
Click to expand...
Click to collapse
Yeah that didn't work, I even tried installing the USB Driver manually and that didn't work either. Still comes up as not connected, it's super frustrating.
Not sure if this helps but for some reason my Android Phone isn't showing up under Android phone in my Device Manager, it's showing up as Portable Devices. I don't know if this is an issue or not, anyone care to give an opinion?
reubendevries said:
OK using a windows 8.1 Pro laptop, ADB installed properly with HTC Sync Manager, both Windows, HTC Sync Manager and the Device Manager in the Control Panel can see my phone. I tick on USB debugging and then press revoke USB debugging authorizations. Unplug my phone and plug it back in. I'm using the original USB cable from HTC. Everything pops up and shows like it's connected, except when I type in
Code:
adb devices
in the command prompt, then it just comes up blank. I've attached screen shots so you guys can see what I am talking about. If you have any ideas it would be much appreciated. I've attached some photos just to show that I've dotted all my i's and crossed all my t's as far as I can see. I also want to point out this is the second computer I've tried this on.
Click to expand...
Click to collapse
check and unchecked camera under USB settings when its plugged in
reubendevries said:
Not sure if this helps but for some reason my Android Phone isn't showing up under Android phone in my Device Manager, it's showing up as Portable Devices. I don't know if this is an issue or not, anyone care to give an opinion?
Click to expand...
Click to collapse
That's normal as the phone is using MTP, the Android Phone entry only appears once the drivers are installed. It's definitely a driver issue but as to what I can't say as I have no issues on my 8.1 Pro laptop
I think I figured something out, just flash CM 12 - (God it's amazing. ) and now I can see my phone on ADB, so whatever ****ery was going on I am blaming it on HTC stock rom.
reubendevries said:
I think I figured something out, just flash CM 12 - (God it's amazing. ) and now I can see my phone on ADB, so whatever ****ery was going on I am blaming it on HTC stock rom.
Click to expand...
Click to collapse
is cm12 worth the hassle?
Sorry for the necrobump, but I ran across this thread while researching the same issue on my M8 and wanted to save anyone else the trouble if they also stumbled across this same issue.
Though the solution discussed would likely work, if you don't want to hassle with a new ROM, it is possible to fix it on your existing ROM provided you have root.
[SOLVED] ADB 'unauthorized', no RSA prompt, and no 'Revoke USB debugging' option
NFSP G35 said:
Sorry for the necrobump, but I ran across this thread while researching the same issue on my M8 and wanted to save anyone else the trouble if they also stumbled across this same issue.
Though the solution discussed would likely work, if you don't want to hassle with a new ROM, it is possible to fix it on your existing ROM provided you have root.
[SOLVED] ADB 'unauthorized', no RSA prompt, and no 'Revoke USB debugging' option
Click to expand...
Click to collapse
Thanks for this guide you put up. Interesting that there was no option for you to revoke USB authorization. My device is S-ON and have been using Viper for a while with the option available. Same for HTC stock. Good for you getting that fixed. Had a similar issue on a different device months ago.
So I updated my phone to fix "critical bugs". The phone turned off went into TWRP, restarted and I was met with "no command". Oh great I forgot I was rooted again. So I open up TWRP, connect to my computer and try adb, oh it didn't work. I played with the drivers for literally forever installing the google driver, and various third party ones, reading every online tutorial. No work. I purchased a new high quality cord with charging+sync. It still did not work, at this point I decided that I would use ubuntu instead of windows, I have more experience doing this stuff in ubuntu anyways. Well it still did not work, the same error. No Device Found. I went through a few tutorials on some other troubleshooting, I used nirsofts usbinfo tool and I also used lsusb in ubuntu, and I could not find my phone connected. I could plug it in and out and the lsusb would look the same either way. Though my phone was still charging. I then tried on another computer with ubuntu as well and the same problem then too. Any ideas?? I am kinda on vacation and it was my source of data+contacting people. Also somewhat concerned about the new system where they check your electronic devices at border security, when it doesn't work they definitely will think its a bomb.
Le bump??
Bump, does anyone have any ideas???
My Nexus 5x randomly stopped working on ADB saying devices not found earlier this year. That device bootlooped and received my replace a couple weeks ago and decided to finally setup and not sell it. The same thing was happening to my replacement device so I knew it was the drivers on the computer since my Sony Xperia X was able to ADB and all that. I finally setup my phone today and updated the firmware and found the issue. This is what ended up working.
Steps:
1) Uninstall old drivers by going to Windows key + R key together. Type devmgmt.msc and hit enter to open Device Manager.
2) Click on Android device or Portable Device and find your device, right click and uninstall driver.
3) Download/Update Google USB driver through SDK manager and install.
4) Connect your phone with the cord and it should install its own drivers.
5) Windows key + R key again, devmgmt.msc to go to Device Manager.
6) Go to Android Device or Other and right click on your phone and update driver software.
7) Click on Browse my computer from driver software.
8) Click on Let me pick from a list of device drivers on my computer.
9) There should be 1 or 2 lists under Model. Double click on the first one and it will update it. After that finishes, go back to step 6 and until you get to step 9 to double click and update the other item on the list to update.
10) Reboot computer and connect your device and it should work.
If you don't see Android Device > ADB interface in Device manager when you update the Google USB drivers, click on Portable > Nexus 5x and update drivers and just follow steps 6-9, then update the Android Device under Device Manager.
Once thats all done ADB should work, for me it did today but the android with no command showed up. For that when your at that screen, Hold power button + tap volume UP once (don't hold it, just tap and let go) and it should bring you to recovery screen with the choices.
Riverdales27 said:
My Nexus 5x randomly stopped working on ADB saying devices not found earlier this year. That device bootlooped and received my replace a couple weeks ago and decided to finally setup and not sell it. The same thing was happening to my replacement device so I knew it was the drivers on the computer since my Sony Xperia X was able to ADB and all that. I finally setup my phone today and updated the firmware and found the issue. This is what ended up working.
Steps:
1) Uninstall old drivers by going to Windows key + R key together. Type devmgmt.msc and hit enter to open Device Manager.
2) Click on Android device or Portable Device and find your device, right click and uninstall driver.
3) Download/Update Google USB driver through SDK manager and install.
4) Connect your phone with the cord and it should install its own drivers.
5) Windows key + R key again, devmgmt.msc to go to Device Manager.
6) Go to Android Device or Other and right click on your phone and update driver software.
7) Click on Browse my computer from driver software.
8) Click on Let me pick from a list of device drivers on my computer.
9) There should be 1 or 2 lists under Model. Double click on the first one and it will update it. After that finishes, go back to step 6 and until you get to step 9 to double click and update the other item on the list to update.
10) Reboot computer and connect your device and it should work.
If you don't see Android Device > ADB interface in Device manager when you update the Google USB drivers, click on Portable > Nexus 5x and update drivers and just follow steps 6-9, then update the Android Device under Device Manager.
Once thats all done ADB should work, for me it did today but the android with no command showed up. For that when your at that screen, Hold power button + tap volume UP once (don't hold it, just tap and let go) and it should bring you to recovery screen with the choices.
Click to expand...
Click to collapse
There is no android device or portable device, I have used many oem cables too.... Using usb diagnostic tools it doesn't even show it as plugged in, though it still is getting a charge. The positive and negative wires still are supplying electricity but the sync wires are not working, though it doesn't seem to matter what cable I use. With the second part, do you mean with using the SDK tool? I was just installing the google drivers from the standalone installer.
I don't know then. You have usb debugging enabled on developers option.
Do you have the "Qualcomm HS-USB QDLoader 9008" ? In the com ports? If so jump to this thread nexus-5x/help/finding-solution-qualcomm-hs-usb-t364828
Hello, my Oneplus 3 finally met its maker when it slid off my knee as I was doing a poo. This phone had served me well for a long time and was used for the last year without a functioning power button.
Today I was trying to extract my data from the phone using adb. However, I have a few issues.
The screen is fully black and shattered and digitizer appears to also be broken.
I can use the fingerprint sensor, but not much else. If I try to apply pressure to the screen, the device disconnects from the computer then reconnects.
My phone will not show in 'My PC' and just shows as 'android' under 'USB devices' in Device Manager, I try to update the driver through this and I am just assigning it to be an 'ADB device' or 'Oneplus Android ADB Interface' which does not help.
I have downloaded the Oneplus USB drivers and installed them which did not help or allow me to select those as driver updates in 'device manager'. Even after turning off signed driver checks in boot options.
I believe I have USB debugging on, as I turned it on not long ago due to the power button failing. But when I attempt to use ADB I either get 'unauthorised' or 'offline' beside my devices serial number.
I have tried unlocking my device with my fingerprint and it has the response vibration but does not allow me to access it.
Ideally I would like it to work with '[email protected]' and 'android control' but I would settle for just being able to pull everything off the device. I have been reading threads and trying fixes all day to no avail. Please help me.
Desktop Info that may have an effect
Windows 10 version 1803
USB 3.0 ports
Related programs installed
ADB Minimal and Fastboot
Android Studio (not sure how to use)
[email protected]
Android Control
Thankyou
FinnSanity7 said:
Hello, my Oneplus 3 finally met its maker when it slid off my knee as I was doing a poo. This phone had served me well for a long time and was used for the last year without a functioning power button.
Today I was trying to extract my data from the phone using adb. However, I have a few issues.
The screen is fully black and shattered and digitizer appears to also be broken.
I can use the fingerprint sensor, but not much else. If I try to apply pressure to the screen, the device disconnects from the computer then reconnects.
My phone will not show in 'My PC' and just shows as 'android' under 'USB devices' in Device Manager, I try to update the driver through this and I am just assigning it to be an 'ADB device' or 'Oneplus Android ADB Interface' which does not help.
I have downloaded the Oneplus USB drivers and installed them which did not help or allow me to select those as driver updates in 'device manager'. Even after turning off signed driver checks in boot options.
I believe I have USB debugging on, as I turned it on not long ago due to the power button failing. But when I attempt to use ADB I either get 'unauthorised' or 'offline' beside my devices serial number.
I have tried unlocking my device with my fingerprint and it has the response vibration but does not allow me to access it.
Ideally I would like it to work with '[email protected]' and 'android control' but I would settle for just being able to pull everything off the device. I have been reading threads and trying fixes all day to no avail. Please help me.
Desktop Info that may have an effect
Windows 10 version 1803
USB 3.0 ports
Related programs installed
ADB Minimal and Fastboot
Android Studio (not sure how to use)
[email protected]
Android Control
Thankyou
Click to expand...
Click to collapse
If you had used adb before and the phone was recognised earlier, then there shouldn't be an issue. If not, then when issuing adb commands, there will be a popup on the phone asking you to enable authorisation and to make it permanent. In your current scenario, you will not be able to grant authorisation. Your drivers might be installed properly but because of this "authorisation" issue, the phone might not be recognised properly.
Search for methods to pull data from the phone. I had read about a couple of methods where you can mirror your screen on the PC which will solve the problem for you. Unfortunately I am not able to recollect where I read that.
EDIT: Enter fastboot mode on your phone and connect it to the PC. Then using 'fastboot boot twrp.img' you can boot into TWRP on the phone and access the files and copy them using adb commands. This requires the TWRP in the same folder as your adb tools or vice versa and renaming the file as TWRP. I don't know whether this also requires 'authorisation' but try it any way.
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.
So my buddy gave me this Nexus S 4G, since I like to collect phones. Unfortunately, it appears to be stuck on 4.0 ICS. I tried to check for an update to 4.1 ICS, but for some reason, it reports that my phone is up to date??? Wtf. So I tried doing it manually, I can't flash this random OTA which may or may not (probably is) Jelly Bean in stock recovery, but it fails. I tried doing it even more manually using fastboot, but for some reason, I can't get the USB drivers to work. My next step is to use a Macintosh, as they seem to work better with Android, but I don't have access to it yet. In the mean time, is there any other way to get this phone updated or, at the very least, rooted and ROM'd?
@Dr. Hax
I'm assuming you are using windows? If so burn a Linux iso, Mint or Ubuntu are both great. You can make a bootable iso using a thumb drive or CD. Then set up your pc for dual boot. You'll never have a driver issue on Linux.
I'm sure you probably know this but how I have gotten windows to work and see my device is install the fastboot and adb 15 second installer from here: https://forum.xda-developers.com/showthread.php?t=2588979
Then reboot of course. And when I plug my device in have developer options enabled and usb debugging enabled and be watching phone for the little box pop up that you just checkmark really quick so your pc can communicate with the device... Also if you scroll down on the phone in developer options to "default usb configuration" and change that to "file transfer", that will usually bring the little box up on my devices to check mark so they can communicate..It only shows for a second then it's gone. But if it hasn't popped up yet then open terminal and type sudo adb devices (hit enter) and again be watching your phone because that little box should then come up that you must quickly check mark on phone so pc and phone can communicate.
I always uninstall and reinstall drivers on windows and reboot afterwards. Also make sure check device manager and see what's there. But that 15 second fastboot adb installer for windows is a life saver and makes it all super easy!! On Linux none of this happens. Ever! ? You just plug in your phone and the model of your device shows up on the computer screen. IDK if this makes sense much but I tried to word it where it did best I could. Hopefully this helps or you already got it going.