For whatever reason, when I'm trying to get my Token ID, I get as far as entering fastboot, and when trying to get the second command prompt to retrieve my token, it just gets stuck at "Waiting for Device".
I've made sure I'm using a USB 2.0 port ON THE BACKSIDE of my PC (I've tried 3.0, and front ports as well, all yield the same results)
USB debugging IS ENABLED.
I've tried with, and without fastboot disabled.
I've tried uninstalling ALL android related drivers on my PC, and re installing ONLY the HTC ones (I have a rooted nexus 7 2013 as well)
nothing seems to make a difference, everything works great right up until my device reboots into fastboot, then it becomes unrecognisable.
At the same time, windows shows a failed driver installation ONLY AFTER I unplug the device, and it shows it trying to install "HTC MTP DEVICE".
I've run out of ideas for a way to fix this by now, anyone have any other suggestions?
Try getting your token without the toolkit using fastboot. There's instructions on the HTC dev site
I attempted that as well, all it did was make me manually preform the same commands the toolkit did on it's own.
No luck with that either.
Edit: THANK GOD I FINALLY GOT IT WORKING!!!!!
When my phone boots into bootloade,r it runs on an "Android 1.0" driver. I went into my device manager, and updated that "Android 1.0 device" with the drivers located here, and everything magically connected, and I can now get my token ID!!!
suggests tractor
Also, if you have any more problems with it not showing up under devices try to unplug/plugin your USB cable. I have weird driver problems on Windows sometimes.
Related
I had my phone unlocked and working with a custom ROM in the past, but after some problems I gave up and just relocked it and went back to stock. Now I'm trying to unlock it again and I'm running into some problems. I'm unable to get the identifier token to use with htcdev because whenever I go into the bootloader my phone is not recognized by adb. fastboot oem get_identifier_token leaves me with a waiting for device message, and adb devices returns an empty list. If I turn the phone on normally the device shows up then. To the best of my knowledge, I have all the necessary drivers. I have tried multiple USB slots, multiple computers (including the one I originally did the unlock on, when it worked fine), and have searched all around the internet and various forums for an answer. I've tried manually updating the USB drivers through device manager, but that did nothing. I have HTC sync installed as well. When I plug the USB cable in I sometimes get a device cannot be identified/has malfunctioned message. Device manager also shows a yellow warning triangle on my phone when in the bootloader. I'm on windows 8 currently, but I've tried it on a windows 7 pc as well with the same results.
tldr: adb doesn't recognize my phone while in bootloader, so I can't unlock it.
Thanks in advance for any help, I've tried everything I can think of.
It sounds like the waiting for device message with fastboot it because you're in bootloader (hboot) instead of fastboot maybe. You want to uninstall the HTC sync program, it's used because it installs the drivers then you get rid of the program itself or at least make sure it's not running at startup and when you connect the device. On Windows 8 did you disable the driver signature verification yet?
Sent from my HTC6435LVW using Tapatalk 4 Beta
CharliesTheMan said:
It sounds like the waiting for device message with fastboot it because you're in bootloader (hboot) instead of fastboot maybe. You want to uninstall the HTC sync program, it's used because it installs the drivers then you get rid of the program itself or at least make sure it's not running at startup and when you connect the device. On Windows 8 did you disable the driver signature verification yet?
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
Same result in fastboot, I'll try uninstalling HTC sync and disabling driver signature verification now and see how it goes
edit: same result, adb devices comes up empty when in fastboot after disabling driver signature verification and uninstalling HTC sync
It should be "fastboot devices" as the command.
Does your computer have native USB 3?
Sent from my HTC6435LVW using Tapatalk 4 Beta
CharliesTheMan said:
It should be "fastboot devices"
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
that returns nothing it just starts a new command line.
and two of the ports are usb 3.0 one is 2.0, I've tried all three
Use the snip tool in windows to grab a screenshot of the command window stretched out to show the history, that may point me in the right direction. Do a search for Windows 8 ADB and Fastboot driver installation (i prefer Google and prefix the search with "site: www.xda-developers.com" no quotes) and you should find a thread with the steps for installing the drivers properly after signature verification is disabled in Windows 8. I used it to remotely fix a user's computer with the same issue you're having but I'm mobile at the moment. I'll help you get it straightened out though that's kind of my specialty. I'm about to go get something to eat, I'm working on a migraine and when I get back I'll check back in. Feel free to PM me if you want while waiting on input from others also.
Sent from my HTC6435LVW using Tapatalk 4 Beta
CharliesTheMan said:
Use the snip tool in windows to grab a screenshot of the command window stretched out to show the history, that may point me in the right direction. Do a search for Windows 8 ADB and Fastboot driver installation (i prefer Google and prefix the search with "site: www.xda-developers.com" no quotes) and you should find a thread with the steps for installing the drivers properly after signature verification is disabled in Windows 8. I used it to remotely fix a user's computer with the same issue you're having but I'm mobile at the moment. I'll help you get it straightened out though that's kind of my specialty. I'm about to go get something to eat, I'm working on a migraine and when I get back I'll check back in. Feel free to PM me if you want while waiting on input from others also.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thank you for the help, I hope this is all you need from the command window. I'm trying the adb and fastboot driver installation thread that you suggested now, hopefully this will have it resolved by the time you get back.
edit: unfortunately that didn't work, it said that the driver is already up to date. The phone shows up as "My HTC" under android USB devices already, even when in the bootloader/fastboot, but it shows the device status as "This device cannot start. (Code 10) A request for the USB BOS descriptor failed."
Adb devices worked, that's your serial number so it's definitely fixable. What does it tell you when you boot to hboot, select fastboot, and use the command "fastboot reboot"
Could you send me a screen shot of the folder contents for the mini-adb folder, just like you did the command window except inside the mini adb folder.
Sent from my HTC6435LVW using Tapatalk 4 Beta
CharliesTheMan said:
Adb devices worked, that's your serial number so it's definitely fixable. What does it tell you when you boot to hboot, select fastboot, and use the command "fastboot reboot"
Could you send me a screen shot of the folder contents for the mini-adb folder, just like you did the command window except inside the mini adb folder.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
I just have some extra things in the folder like some ROMs/recoveries but I don't think that would matter. I have adb.exe, fastboot.exe, and the two .dll's so I think I have everything I need.
And I tried fastboot reboot while in fastboot, I got waiting for device in command prompt. Also when I entered the command I got a "USB device not recognized" popup from the taskbar. Device manager shows the phone as My HTC with a yellow caution triangle on the icon and the device status "This device cannot start. (Code 10) A request for the USB BOS descriptor failed."
That's usually the result of using a USB 3.0 port, do you have a different set of ports you can try? Like back of the computer instead of front, side of notebook to back of notebook etc. Most motherboards have a USB 2.0 hub and USB 3.0 hub but the manufacturers don't make it obvious which is which in most cases. Also make sure antivirus and such is turned off while you're testing. Its one of those things that's just a tad bit off such as the ports or a driver.
Let me know how the above turns out and tomorrow if you want I can hop on teamviewer and we can try uninstalling what's there, starting fresh with the Google sdk and go from there.
PS- Sorry I haven't had a more direct answer I know it can be frustrating with so much trial and error and it being almost working. But I promise I'll stick with it until we get something figured out, or you get mad and remotely smack me over the head with a keyboard.
Sent from my HTC6435LVW using Tapatalk 4 Beta
CharliesTheMan said:
That's usually the result of using a USB 3.0 port, do you have a different set of ports you can try? Like back of the computer instead of front, side of notebook to back of notebook etc. Most motherboards have a USB 2.0 hub and USB 3.0 hub but the manufacturers don't make it obvious which is which in most cases. Also make sure antivirus and such is turned off while you're testing. Its one of those things that's just a tad bit off such as the ports or a driver.
Let me know how the above turns out and tomorrow if you want I can hop on teamviewer and we can try uninstalling what's there, starting fresh with the Google sdk and go from there.
PS- Sorry I haven't had a more direct answer I know it can be frustrating with so much trial and error and it being almost working. But I promise I'll stick with it until we get something figured out, or you get mad and remotely smack me over the head with a keyboard.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
I'm pretty sure I was using the 2.0 port but I could be wrong. I'll keep working on it and if I can't resolve it I'd love to try teamviewer wth you. Thank you so much for all the help so far.
Finally got it working, kept trying on my old computer that I unlocked it originally with and eventually it just decided to recognize it and worked.
Thanks so much for the help getting to this point.
kalbany said:
I'm pretty sure I was using the 2.0 port but I could be wrong. I'll keep working on it and if I can't resolve it I'd love to try teamviewer wth you. Thank you so much for all the help so far.
Click to expand...
Click to collapse
I
Is there an error information, e.g: Windows code 10.
If yes, I googled it, it shows:
The error message probably occurs when you are trying to use a particular piece of hardware, such as a USB connected device or internal DVD drive. Take note of the device you are using when the error occurs in order to update the correct drivers.
error.info/windows/driver-10.html
Cheers,
Lun:
kalbany said:
I had my phone unlocked and working with a custom ROM in the past, but after some problems I gave up and just relocked it and went back to stock. Now I'm trying to unlock it again and I'm running into some problems. I'm unable to get the identifier token to use with htcdev because whenever I go into the bootloader my phone is not recognized by adb. fastboot oem get_identifier_token leaves me with a waiting for device message, and adb devices returns an empty list. If I turn the phone on normally the device shows up then. To the best of my knowledge, I have all the necessary drivers. I have tried multiple USB slots, multiple computers (including the one I originally did the unlock on, when it worked fine), and have searched all around the internet and various forums for an answer. I've tried manually updating the USB drivers through device manager, but that did nothing. I have HTC sync installed as well. When I plug the USB cable in I sometimes get a device cannot be identified/has malfunctioned message. Device manager also shows a yellow warning triangle on my phone when in the bootloader. I'm on windows 8 currently, but I've tried it on a windows 7 pc as well with the same results.
tldr: adb doesn't recognize my phone while in bootloader, so I can't unlock it.
Thanks in advance for any help, I've tried everything I can think of.
Click to expand...
Click to collapse
I have Started a thread for HTC Droid Incredible phones in the troubleshooting area. Im having the same exact problem and im running Windows
as soon as i do the command: fastboot oem get_identifier_token, it just sits there and waits. and then i get a pop up from the system tray saying that my device has malfunctioned.
CharliesTheMan said:
Adb devices worked, that's your serial number so it's definitely fixable. What does it tell you when you boot to hboot, select fastboot, and use the command "fastboot reboot"
Could you send me a screen shot of the folder contents for the mini-adb folder, just like you did the command window except inside the mini adb folder.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
Regardless of how old this thread is I'm running into the same problems now!
My Xperia XZ1 Compact doesn't seem to be recognized when in the bootloader (indicated by a black screen and blue led).
I tried "adb reboot hboot" and it booted into a new black screen, but didn't last long before rebooting.
I tried other button combinations during the sequence and those didn't change anything.
I had my phone unlocked and working with a custom ROM in the past, but after some problems I gave up and just relocked it and went back to stock. Now I'm trying to unlock it again and I'm running into some problems. I'm unable to get the identifier token to use with htcdev because whenever I go into the bootloader my phone is not recognized by adb. fastboot oem get_identifier_token leaves me with a waiting for device message, and adb devices returns an empty list. If I turn the phone on normally the device shows up then. To the best of my knowledge, I have all the necessary drivers. I have tried multiple USB slots, multiple computers (including the one I originally did the unlock on, when it worked fine), and have searched all around the internet and various forums for an answer. I've tried manually updating the USB drivers through device manager, but that did nothing. I have HTC sync installed as well. When I plug the USB cable in I sometimes get a device cannot be identified/has malfunctioned message. Device manager also shows a yellow warning triangle on my phone when in the bootloader. I'm on windows 8 currently, but I've tried it on a windows 7 pc as well with the same results.
tldr: adb doesn't recognize my phone while in bootloader, so I can't unlock it.
Thanks in advance for any help, I've tried everything I can think of.
Hi im fairly newthis to all this so please be patient. I have Htc 4g amaze Tmous rooted s-on unlocked. I flashed a custom rom which is stock debloated. But, the wifi and bluetooth do not work. I want to revert back to stock by using the same method which is the Htc toolkit. But, when i restart in bootloader mode the phone is no longer recognized by my laptop running win 8.1. I have been searching for a week now and have tried everything from deleting drivers, reinstalling, downloading htc sync and removing the software but leaving drivers,, different USB ports 2.0 & 3.0, nothing works. When its in bootloader about 5 seconds later my computer says USB device not recognized.
Please help.
mikeny said:
Hi im fairly newthis to all this so please be patient. I have Htc 4g amaze Tmous rooted s-on unlocked. I flashed a custom rom which is stock debloated. But, the wifi and bluetooth do not work. I want to revert back to stock by using the same method which is the Htc toolkit. But, when i restart in bootloader mode the phone is no longer recognized by my laptop running win 8.1. I have been searching for a week now and have tried everything from deleting drivers, reinstalling, downloading htc sync and removing the software but leaving drivers,, different USB ports 2.0 & 3.0, nothing works. When its in bootloader about 5 seconds later my computer says USB device not recognized.
Please help.
Click to expand...
Click to collapse
You're gonna have to be a bit more specific with how you're trying to read the device:
a) When you're in bootloader, and you have the phone plugged in, does it read HBOOT USB, or FASTBOOT USB?
i) If yes: Then just run the program. It will still recognize the system even if Windows doesn't show it. Fire off a CMD command or simply click "reboot" on the toolkit and see if the phone responds.
ii) If no: Use another cable, and make sure you're securely connected. Generic micro USB cables tend to be a bit loose even when connected, so make sure the cable itself is not "ajar" in the port
Once you're in bootloader mode, post what it says here.
darkandshadow said:
You're gonna have to be a bit more specific with how you're trying to read the device:
a) When you're in bootloader, and you have the phone plugged in, does it read HBOOT USB, or FASTBOOT USB?
i) If yes: Then just run the program. It will still recognize the system even if Windows doesn't show it. Fire off a CMD command or simply click "reboot" on the toolkit and see if the phone responds.
ii) If no: Use another cable, and make sure you're securely connected. Generic micro USB cables tend to be a bit loose even when connected, so make sure the cable itself is not "ajar" in the port
Once you're in bootloader mode, post what it says here.
Click to expand...
Click to collapse
Hi and thanks for the reply. Im using the OEM htc cable and everything else reads just fine. I'm able to read the sd card and send some commands through the toolkit. For example i can click the "boot into bootloader" command and it works fine. The problem is once it is in bootloader the command prompt window just says waiting for device and the phone says fastboot. I am able to reboot the phone back into android using the vol keys and the power button. Im trying to relock the bootloader using toolkit but on the second window (first being putting it bootloader) it won't read the phone following the computers message saying usb device not recognized. Thanks again for the help.
mikeny said:
Hi and thanks for the reply. Im using the OEM htc cable and everything else reads just fine. I'm able to read the sd card and send some commands through the toolkit. For example i can click the "boot into bootloader" command and it works fine. The problem is once it is in bootloader the command prompt window just says waiting for device and the phone says fastboot. I am able to reboot the phone back into android using the vol keys and the power button. Im trying to relock the bootloader using toolkit but on the second window (first being putting it bootloader) it won't read the phone following the computers message saying usb device not recognized. Thanks again for the help.
Click to expand...
Click to collapse
You may have to try it manually. Download a fresh copy of the Android SDK tools
and put the "Platform-Tools" folder under your C:\
Fire up Command Prompt, change directory to that platform-tools folder.
Then type in "fastboot oem lock" (without the quotations).
Your phone will reboot and upon the bootloader, it should say **RELOCKED** at the top.
If you're still having issues, I would suggest loading up on another computer, or if that isn't possible, download Ubuntu and burn it as a LiveCD and see if your phone will be recognized (properly) through Linux. Sounds like the communication protocols for your phone are fuxed. As for uninstalling and reinstalling drivers like that, you may have to use regedit to completely remove trace portions of those previous installs.
It's a driver issue, uninstall and reinstall the drivers.
hi, i tried rumrunner but it keeps giving me a usb connection error when testing the adb. but when i use the adb commands in the sdk it shows up just fine and everything works. and my fastboot works as well. but on rumrunner when it runs fastboot first and then adb the adb doesnt recognize my device. ive uninstalled rebooted and reinstalled the drivers but nothings working. please help!!
this is the error message i get when running rumrunner, and i cant figure out why. on the left is my initial adb test, and then on the right is my rumrunner right afterwards
pRoDiGyXxGiRl said:
hi, i tried rumrunner but it keeps giving me a usb connection error when testing the adb. but when i use the adb commands in the sdk it shows up just fine and everything works. and my fastboot works as well. but on rumrunner when it runs fastboot first and then adb the adb doesnt recognize my device. ive uninstalled rebooted and reinstalled the drivers but nothings working. please help!!
this is the error message i get when running rumrunner, and i cant figure out why. on the left is my initial adb test, and then on the right is my rumrunner right afterwards
Click to expand...
Click to collapse
Check and make sure that when your phone reboots it connects to the computer properly, I had a similar issue when i was using moonshine to flash my phone, you should see that the phone is connected and listed in Explorer when you reboot. also make sure that you UNINSTALLED HTC Sync - if it fails to load the drivers, you may try quickly unplugging and replugging in the usb cable into your computer during the countdown, definitely do not do that after it has connected - doing so will result in a brick. follow this advice at your own risk. if you don't feel comfortable with it, don't try it, try another computer, it just so happens that i tried moonshine on 3 of my pc's before i finally got it to run with out hanging.
you can also try this tool kit to install the drivers separate from sync: http://forum.xda-developers.com/showthread.php?t=2219175
p1droidx said:
Check and make sure that when your phone reboots it connects to the computer properly, I had a similar issue when i was using moonshine to flash my phone, you should see that the phone is connected and listed in Explorer when you reboot. also make sure that you UNINSTALLED HTC Sync - if it fails to load the drivers, you may try quickly unplugging and replugging in the usb cable into your computer during the countdown, definitely do not do that after it has connected - doing so will result in a brick. follow this advice at your own risk. if you don't feel comfortable with it, don't try it, try another computer, it just so happens that i tried moonshine on 3 of my pc's before i finally got it to run with out hanging.
you can also try this tool kit to install the drivers separate from sync: http://forum.xda-developers.com/showthread.php?t=2219175
Click to expand...
Click to collapse
thanks!! i will try the toolkit. i never installed htc sync so i know its uninstalled lol. and i will also try the unplugging the cable. oh and i dont know if this matters or not, but my bootloader is still locked because it said for rumrunner i dont need to have it unlocked. is that correct?
Alright so I'm no stranger to flashing ROMS and whatnot, but today I slipped up and deleted everything on my internal storage, including my NANDROID backup. I still have access to my recovery (CWM touch v6.0.4.5). So I thought "no problem, I"ll just ADB sideload". Well here we are.
Basically I can't get my ****ing phone to communicate with my computer. I installed every damn thing I could think of to get my device to show up after typing "adb devices". I tried the universal toolkit, but as expected it didn't work very well. I tried it on my laptop and desktop, through USB 2.0 and 3.0. I installed the generic Android USB ADB driver, I installed HTC sync for DNA drivers, I installed a standalone version of the DNA driver, and no dice. Can't even get fastboot to communicate. Even though my phone says fastboot USB my computer won't recognize it.
This is seriously ****ing pissing me off, because it should be a simple fix. Anybody have words of wisdom to help me out?
Thanks in advance.
FCO2011 said:
Alright so I'm no stranger to flashing ROMS and whatnot, but today I slipped up and deleted everything on my internal storage, including my NANDROID backup. I still have access to my recovery (CWM touch v6.0.4.5). So I thought "no problem, I"ll just ADB sideload". Well here we are.
Basically I can't get my ****ing phone to communicate with my computer. I installed every damn thing I could think of to get my device to show up after typing "adb devices". I tried the universal toolkit, but as expected it didn't work very well. I tried it on my laptop and desktop, through USB 2.0 and 3.0. I installed the generic Android USB ADB driver, I installed HTC sync for DNA drivers, I installed a standalone version of the DNA driver, and no dice. Can't even get fastboot to communicate. Even though my phone says fastboot USB my computer won't recognize it.
This is seriously ****ing pissing me off, because it should be a simple fix. Anybody have words of wisdom to help me out?
Thanks in advance.
Click to expand...
Click to collapse
When your in hboot/fastboot and connected to your computer does it say fastboot usb? If it does when you type in fastboot devices is it recognizing your device at all? Should bring up serial number. Are you on Windows xp/7/8 or 8.1?
Sent from my HTC6435LVW using XDA Free mobile app
Which version of the universal ADB drivers did you use, because I just did this to my phone about a month ago and had the same issue? Once I installed the universal generic driver everything communicated and worked properly.
Try installing PDAnet it blanket installs a bunch of drivers that got me out of a similar spot!