Related
Hey XDA I got my DNA the day it was released and love it. I am a creature of habit though so i want to root it like my past dinc2. I am running into a problem though. the command
Code:
adb devices
doesn't return my device. when i type in
Code:
fastboot devices
my phones serial number comes up, like it should. Fastboot works but ADB doesn't. I am trying to do JCase's Bootloader Exploit. I have the drivers installed, environment variable path set to my adb/fastboot location, and java sdk and android sdk all installed. I know ADB doesnt recognize it in the fastboot menu, just the beginning menu so that's what I'm doing. How can i get ADB to recognize my device like fastboot does.
Here's what I'm getting:
Code:
C:\And-sdk\platform-tools>adb devices
List of devices attached
C:\And-sdk\platform-tools>fastboot devices
FA2BBS500706 fastboot
Any help is greatly appreciated!!
Um, do you have usb debugging enabled.
Sent from my HTC6435LVW using xda app-developers app
termin8tor22 said:
Hey XDA I got my DNA the day it was released and love it. I am a creature of habit though so i want to root it like my past dinc2. I am running into a problem though. the command
Code:
adb devices
doesn't return my device. when i type in
Code:
fastboot devices
my phones serial number comes up, like it should. Fastboot works but ADB doesn't. I am trying to do JCase's Bootloader Exploit. I have the drivers installed, environment variable path set to my adb/fastboot location, and java sdk and android sdk all installed. I know ADB doesnt recognize it in the fastboot menu, just the beginning menu so that's what I'm doing. How can i get ADB to recognize my device like fastboot does.
Here's what I'm getting:
Code:
C:\And-sdk\platform-tools>adb devices
List of devices attached
C:\And-sdk\platform-tools>fastboot devices
FA2BBS500706 fastboot
Any help is greatly appreciated!!
Click to expand...
Click to collapse
having the same issue. I can issue commands through fastboot and ADB commands when I'm in recovery but not when my phone is fully booted.
Try going into slept dev. settings turning adb debugging off then back on
Sent from my HTC6435LVW using xda premium
@Bigandrewgold:
Its really bugging me. All Google says is "ADB works, Fastboot doesn't" and that's the opposite of our problem!!!
@Chyrux:
Um, do you have usb debugging enabled.
Click to expand...
Click to collapse
yes, usb debugging is enabled, has been (I'm not that dumb haha).
@starscream86:
Try going into slept dev. settings turning adb debugging off then back on
Click to expand...
Click to collapse
Not sure what "slept dev. settings" is (typo maybe??). I have on/off'd dev settings and check/unchecked usb debugging a alot of times to no success.
Here's the cure all....I'm assuming you have the lastest SDK and have yor ADB folder set to something simple like C:\ADB and I'm also assuming you are running Windows
I had the same issue ....initially I had no issue in ADB and I was able to do the CIG change and unlock on HTC Dev..but later on I installed HTC sync drivers and from then on no matter what I did only fastboot commands worked in recovery...ADB did not in recovery or when my phone was running normal.
So...uninstall all htc SYnc and driverin programs/features on oyur laptop...reboot your laptop. on the laptop download and instal PDANet 3.50 (its free). it will prompt you to connect your phone and will install a proper driver (and also throw the pda net 3.50 program on your phone). Once you have successfully installed it, ADB should work perfectly for you.
bakemcbride21 said:
Here's the cure all....I'm assuming you have the lastest SDK and have yor ADB folder set to something simple like C:\ADB and I'm also assuming you are running Windows
I had the same issue ....initially I had no issue in ADB and I was able to do the CIG change and unlock on HTC Dev..but later on I installed HTC sync drivers and from then on no matter what I did only fastboot commands worked in recovery...ADB did not in recovery or when my phone was running normal.
So...uninstall all htc SYnc and driverin programs/features on oyur laptop...reboot your laptop. on the laptop download and instal PDANet 3.50 (its free). it will prompt you to connect your phone and will install a proper driver (and also throw the pda net 3.50 program on your phone). Once you have successfully installed it, ADB should work perfectly for you.
Click to expand...
Click to collapse
This didn't work for me... PDANet gave me error 103 when i connected my phone. I have uploaded the image.
termin8tor22 said:
This didn't work for me... PDANet gave me error 103 when i connected my phone. I have uploaded the image.
Click to expand...
Click to collapse
yeah, whatever Windows or other HTC driver you have that install for thephone is still on the laptop and that will conflict when installing.
You get PDANet to install successfully your ADB will come back.
In your programs and features make sure HTC SYnc AND HTC Drivers are unisntalled.
No idea if Windows 8 is more of a pain..I'm still on 7
before anything else, make sure your sdk is updated to an ics or later level
i just update the sdk whenever google pushes an update
I'm on 7 as well. How can I uninstall the drivers for good, like to the point where its like the first time I'm connecting my phone to pc again
Sent from my HTC6435LVW using xda app-developers app
termin8tor22 said:
I'm on 7 as well. How can I uninstall the drivers for good, like to the point where its like the first time I'm connecting my phone to pc again
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
With your phone not attached..
Control Panel- Programs Features...when I had HTC Sync installed I had to uninstall that AND the program entry for HTC Drivers as well.
You can then also use USBDeview..sort/toggle by Last Plug/Unplug and uninstall any Android drivers you see which could be conflicting.
Reboot, Install PDA Net and attach the phone when prompted. Also accept the driver even though you get the warning that it isn;t digitally signed from JuneFabrics.
This didn't work I'm still getting error 103 Android Device not found
Update:
I got Pdanet installed via putting the phone into fastboot mode and installing Pdanet on the computer.
I did notice that when im in fastboot my Android adb interface (in device manager) popped up but when I left fastboot mode and went to the bootloader my Android adb interface went away, this may be my issue with adb devices not working i think...
Sent from my HTC6435LVW using xda app-developers app
i am currently having this same issue. i did as you did and went to usbfastboot loader and tried installing pda net. i also saw the same adb device pop up but my install is stuck at installing pdanet phone and not moving. did you leave it in fastboot mode or did you reboot back?
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.
This may be an "old" issue, but i ran into a problem. I have tried every compatible driver for my phone and adb works fine. However, when i reboot into fastboot, the phone is not recognized.
I've tried changing the id of the usb drives and changing the drivers for my phone. I have a functioning adb and fastboot, but now that i've upgraded to 8.1, i can't fastboot flash anything.
Does anyone know of a solution for this on our DNA?
-DroidIsDNA- said:
This may be an "old" issue, but i ran into a problem. I have tried every compatible driver for my phone and adb works fine. However, when i reboot into fastboot, the phone is not recognized.
I've tried changing the id of the usb drives and changing the drivers for my phone. I have a functioning adb and fastboot, but now that i've upgraded to 8.1, i can't fastboot flash anything.
Does anyone know of a solution for this on our DNA?
Click to expand...
Click to collapse
Have a look at
http://forum.xda-developers.com/showthread.php?t=2521504
Are there any compatible fastboot drivers for Windows 8.1. Ever since I upgraded to 8.1 the device is not recognized in fastboot. It worked fine in Windows 8 but when I went to 8.1 it no longer would. I have tried numerous drivers to no avail. It connects fine normally to transfer files etc, just when it reboots in fastboot evice not found".
mrpickem said:
Are there any compatible fastboot drivers for Windows 8.1. Ever since I upgraded to 8.1 the device is not recognized in fastboot. It worked fine in Windows 8 but when I went to 8.1 it no longer would. I have tried numerous drivers to no avail. It connects fine normally to transfer files etc, just when it reboots in fastboot evice not found".
Click to expand...
Click to collapse
They work for me in 8.1, however, for some reason, fastboot will NOT work with any USB 3.0 port (with the blue color). Make sure you are connecting to a 2.0 port!
same issue, and i'm using usb 2.0. i'm also using original usb cable and have tried other cables as well.
i am to getting this problem is there any solution on this
I downloaded the latest HTC Sync which installed the drivers. I have no problem with Fastboot and my One. You can unintstall Sync afterwards.
RangerLG said:
I downloaded the latest HTC Sync which installed the drivers. I have no problem with Fastboot and my One. You can unintstall Sync afterwards.
Click to expand...
Click to collapse
And you're using Windows 8.1 right? I just tried that, did a system restore to before I had any drivers whatsoever installed...then installed the latest HTC Sync. The adb drivers work fine but as soon as I reboot into the bootloader I get the same USB enumeration error and fastboot doesn't work. I have no idea how to fix this, it's real frustrating.
Sorry I haven't responded sooner. Yes I am on 8.1 and have no issues.
I can confirm it was a USB 3.0 issue in my case. As soon as I found a regular USB 2.0 port all my Windows 8.1 woes went away.
i have flashed pacman in my phone and now i cant mount usb storage on my pc , i am having windows 8.1 in my pc . But when i am having stock rom i am able to mount usb , please help me . My Phone Model is HTC Desire S
Hello
i have a asus transformer book t100 with windows8.1 and i cant get fasboot to Work... Adb is working
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!