So i've been trying to get back to my stock settings on my DNA and i've hit a myriad of problems. Right now, I can get my phone to communicate when it's just plugged in. But whenever i boot into bootloader and plug it in, it tries to install the "Android 1.0 driver" but to no avail. The phone will then not be recognized by the computer and I can't do the "fastboot oem lock" command. Is there a download or something that i can grab that will solve this?
HosstaLaVista said:
So i've been trying to get back to my stock settings on my DNA and i've hit a myriad of problems. Right now, I can get my phone to communicate when it's just plugged in. But whenever i boot into bootloader and plug it in, it tries to install the "Android 1.0 driver" but to no avail. The phone will then not be recognized by the computer and I can't do the "fastboot oem lock" command. Is there a download or something that i can grab that will solve this?
Click to expand...
Click to collapse
Do you have the latest SDK version installed, sounds a bit like the drivers are outdated. Might be worth downloading the latest version and installing it...
Try the drivers in this zip file and see if this helps.. these are drivers I am using and have never had an issue
http://db.tt/kr11CT4d
Sent from my HTC6435LVW using xda app-developers app
lazarus2297 said:
Try the drivers in this zip file and see if this helps.. these are drivers I am using and have never had an issue
http://db.tt/kr11CT4d
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Okay, i downloaded that zip and attempted to relock the bootloader. When i type in "fastboot oem lock", the command prompt just shows <waiting for device>
HosstaLaVista said:
Okay, i downloaded that zip and attempted to relock the bootloader. When i type in "fastboot oem lock", the command prompt just shows <waiting for device>
Click to expand...
Click to collapse
Do you have debug turned on in developer options? Of so might try toggling on and off
Sent from my HTC6435LVW using xda premium
HosstaLaVista said:
Okay, i downloaded that zip and attempted to relock the bootloader. When i type in "fastboot oem lock", the command prompt just shows <waiting for device>
Click to expand...
Click to collapse
Are you in bootloader mode when you try this? You have to put phone in bootloader mode either thru adb command or manually. If communication is occuring, you will see fastboot usb in a red box, Then if your adb is working correctly it should go.
we need more info.. first did you uninstall the old drivers first.. then after installing the zip did you confirm that the drivers are the ones that were installed.. and also like someone mentioned is your phone in bootloader/fastboot mode and showing fastboot usb in red on the screen
Sent from my HTC6435LVW using XDA Premium HD app
Also make sure it's not a USB 3.0 spot, you need to use a 2.0. Windows 8 or 7? 8 has been causing issues connecting in fastboot for some.
madzozs said:
Also make sure it's not a USB 3.0 spot, you need to use a 2.0. Windows 8 or 7? 8 has been causing issues connecting in fastboot for some.
Click to expand...
Click to collapse
On my machine (win7) I can use either port usb 2.0 and 3.0..
Sent from my HTC6435LVW using XDA Premium HD app
lazarus2297 said:
On my machine (win7) I can use either port usb 2.0 and 3.0..
Sent from my HTC6435LVW using XDA Premium HD app
Click to expand...
Click to collapse
Win 8 has been having issues with 3.0 for some people.
Reply
HosstaLaVista said:
Okay, i downloaded that zip and attempted to relock the bootloader. When i type in "fastboot oem lock", the command prompt just shows <waiting for device>
Click to expand...
Click to collapse
Have you tried launching command prompt as an administrator?
I ran as root in Ubuntu to get it to re-lock.
Sounds like drivers to me. After you boot into the bootloader are you going into device manager selecting the android whatever and changing the driver to bootloader. Sorry not at a pc so don't know exactly what it says but that sounds like the case.
Sent from my HTC6435LVW using xda premium
One thing that worked for me was installing pdanet, for some reason it installed the correct drivers for HTC. Once I did that it saw my phone in adb, and I could get the device waiting prompt to go away and it would show my model and serial number...hope it helps. Just Google pdanet...and install it.
Sent from my HTC6435LVW using xda app-developers app
Related
OK so I've searched all over the forums and couldn't find a solution for this.
Most people seem to have the problem where ad works but not fastboot. For me though running "adb devices" and "fastboot devices" both work (I.e. showing a list of connected devices) but the phone stays in " starting fastboot protocol support" and doesn't change to "fastboot reboot" when connected.
If it helps I'm running Ubuntu 10.04 and my phone is on Jokers cm9 2.0 beta.
Sent from my Atrix 4g using xda app
Phone wont change to 'fastboot reboot'. That's a command entered from cmd prompt on your computer. Its normal for phone to stay at 'starting fastboot protocol support'.
Sent from my MB860 using xda premium
+1
"fastboot reboot" is a command as @CaelanT states. Try typing in "fastboot devices" while the phone says "Starting fastboot protocol" to see if it shows the serial number.
CaelanT said:
Phone wont change to 'fastboot reboot'. That's a command entered from cmd prompt on your computer. Its normal for phone to stay at 'starting fastboot protocol support'.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Davidrd91 said:
OK so I've searched all over the forums and couldn't find a solution for this.
Most people seem to have the problem where ad works but not fastboot. For me though running "adb devices" and "fastboot devices" both work (I.e. showing a list of connected devices) but the phone stays in " starting fastboot protocol support" and doesn't change to "fastboot reboot" when connected.
If it helps I'm running Ubuntu 10.04 and my phone is on Jokers cm9 2.0 beta.
Sent from my Atrix 4g using xda app
Click to expand...
Click to collapse
A serial number does show up when I type fastboot devices. But the phone still does not recognize that fastboot has started on the computer. Like if the USB wasn't connected.
Edit: also I'm sorry I didn't mean to say fastboot reboot. I know its a command. What the text doesn't change to is "fastboot USB". Or whatever its supposed to say when connected.
The Atrix usually doesn't say anything about a computer recognizing that it's there. If the serial shows up under devices command, then you're good to go!
At least you should be. It says fastboot next to the serial, right?
Yes it does, just none of the commands will work.
Edit: Turns out it will register the commands if connected to a specific USB port. Is this normal? Either way at least it works .
Sent from my MB860
Sometimes the USB port you use makes a difference. Most of the time on a PC you use the rear ports, but I myself have not found any problems using any ports on my PC or laptop.
Also remember that depending on if you have fastboot or moto-fastboot your commands will differ, e.g. "fastboot erase webtop" vs "moto-fastboot erase webtop".
The reason for the difference in which USB ports work is the way they are connected on the motherboard. The OS will only be able to send certain USB commands to the devices if that device is on a port connected directly to the chip set, from what I understand. My guess is that fastboot relies on some of those commands. This is true for me when I am doing Arduino development and want to use USB reset after flashing a new program.
Thanks guys. I got it working . Back to trying to compile a ROM now. This is taking me forever to get down right xD lol
Sent from my MB860
Davidrd91 said:
Thanks guys. I got it working . Back to trying to compile a ROM now. This is taking me forever to get down right xD lol
Sent from my MB860
Click to expand...
Click to collapse
I'm just curious on how you got it working. Some may want to know, if they are having the same problem.
I didn't pay attention that you were using Ubuntu. Don't you have to point fastboot to the device node using some Linux distros?
Edit: oh, missed your post saying how you fixed it. NVM. lol.
Hey guys, need a little help. I've been trying to unlock a friends DNA using jcases method and I'm having some issues. I've made it through his process, but when I go to get the token, for HTC, I can't see the phone in adb, while its in fastboot mode. I can see it, using adb devices, when the phone is booted normally, just not in fastboot. Any ideas?
Sent from my HTC6435LVW using xda app-developers app
in my experience, when im in bootloader > fastboot, and as long as i see the 'fastboot' header change to 'fastboot usb' ; i can run fastboot.exe commands.
*this post is not counsel and i'm not responsible for any action taken and/or damage to your device.
Ok, ill give it a shot. Earlier I tried and it just said "waiting on device", but I didn't notice if it had changed to fastboot usb.
Sent from my HTC6435LVW using xda app-developers app
jslcpd157 said:
Ok, ill give it a shot. Earlier I tried and it just said "waiting on device", but I didn't notice if it had changed to fastboot usb.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Push the power button with bootloader is highlighted and it will switch to fastboot usb.
sent from time out
If you are running windows, install HTC Sync and then uninstall it. That should install the fastboot drivers for you.
Have you tried opening command prompt as Administrator?
When I run fastboot in Ubuntu I have to run as superuser otherwise I just get the "waiting for device" message.
thread moved to q&a due to it not being development and it actually being a question
Make sure you're not using a USB3.0 port. That was my problem. As soon as I plugged into a USB2.0 port instead, it worked perfectly.
BotsOne said:
If you are running windows, install HTC Sync and then uninstall it. That should install the fastboot drivers for you.
Click to expand...
Click to collapse
Was having the same issue myself and this turned out to be my problem. Thanks. Now I got it rooted.
I have same issue on ubuntu, any help?
Have firmware 2.xxxx and have my phone recognized through adb devices on my command prompt and it now says S-OFF but when I check under command for "fastboot devices" I dont seem to have the correct drivers installed. Can anyone help?
Secondlook said:
Have firmware 2.xxxx and have my phone recognized through adb devices on my command prompt and it now says S-OFF but when I check under command for "fastboot devices" I dont seem to have the correct drivers installed. Can anyone help?
Click to expand...
Click to collapse
What OS are you running on the computer? When you use the fastboot command, is your phone in fastboot mode?
Sent from my HTC6435LVW using xda app-developers app
danjull said:
What OS are you running on the computer? When you use the fastboot command, is your phone in fastboot mode?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Windows 8 and no, I am either in standard mode on the phone or in bootloader
Make sure you're not plugged into a usb 3.0 port
Sent from my HTC6435LVW using xda premium
Secondlook said:
Windows 8 and no, I am either in standard mode on the phone or in bootloader
Click to expand...
Click to collapse
Go in bootloader, then fastboot, then run the fastboot command. Should pop up then.
in normal mode do adb devices, if it shows up drivers are fine
Secondlook said:
Have firmware 2.xxxx and have my phone recognized through adb devices on my command prompt and it now says S-OFF but when I check under command for "fastboot devices" I dont seem to have the correct drivers installed. Can anyone help?
Click to expand...
Click to collapse
I'm on windows 8, used the 3.0 port, uninstalled and deleted all HTC drivers, installed PDAnet exe
The title pretty much says it all. I have tried every single method on this site to get my computer to recognize my phone while in fastboot mode with no luck. It works in adb mode just fine I can even reboot to boot loader but once it gets there I get "device enumeration failure" or "device not recognized" when I was on the 1.57 hboot it worked just fine so it has to be something with the 1.39 eng hboot but what I'm not sure. If anyone could help or if anyone else has this problem maybe we could help each other in fixing this cause my only other option is downgrading to win7 which I'm not sure I'll be able to do.
eriknors said:
The title pretty much says it all. I have tried every single method on this site to get my computer to recognize my phone while in fastboot mode with no luck. It works in adb mode just fine I can even reboot to boot loader but once it gets there I get "device enumeration failure" or "device not recognized" when I was on the 1.57 hboot it worked just fine so it has to be something with the 1.39 eng hboot but what I'm not sure. If anyone could help or if anyone else has this problem maybe we could help each other in fixing this cause my only other option is downgrading to win7 which I'm not sure I'll be able to do.
Click to expand...
Click to collapse
Check to make sure that Windows installed the correct driver in device manager. Also, in bootloader adb doesn't work. Only fastboot and only on the fastboot USB side of bootloader.
dottat said:
Check to make sure that Windows installed the correct driver in device manager. Also, in bootloader adb doesn't work. Only fastboot and only on the fastboot USB side of bootloader.
Click to expand...
Click to collapse
Windows installed the correct drivers or I should say I installed the correct drivers. Depending on if I plug into a USB 3.0 or a USB 2.0 port is when my computer tells me whether or not I have "device enumeration failure".
Plugged into USB 3.0 in device manager shows "HTC MTP device" but with a yellow triangle on it obviously meaning the driver needs to be updated or is incorrect, but when trying to update it I'm given "windows has installed the correct drivers already" which in fact by checking it manually it has. HTC driver 2.07xx
Plugged into USB 2.0 gives me "device enumeration failure" and doesn't find any HTC MTP device.
Mind u this is while in fastboot mode not in ADB mode. I'm well aware of the difference between the 2. And fwiw ADB mode works flawlessly while fully booted and in recovery. It's only fastboot mode my computer will not recognize.
eriknors said:
Windows installed the correct drivers or I should say I installed the correct drivers. Depending on if I plug into a USB 3.0 or a USB 2.0 port is when my computer tells me whether or not I have "device enumeration failure".
Plugged into USB 3.0 in device manager shows "HTC MTP device" but with a yellow triangle on it obviously meaning the driver needs to be updated or is incorrect, but when trying to update it I'm given "windows has installed the correct drivers already" which in fact by checking it manually it has. HTC driver 2.07xx
Plugged into USB 2.0 gives me "device enumeration failure" and doesn't find any HTC MTP device.
Mind u this is while in fastboot mode not in ADB mode. I'm well aware of the difference between the 2. And fwiw ADB mode works flawlessly while fully booted and in recovery. It's only fastboot mode my computer will not recognize.
Click to expand...
Click to collapse
Unzip and try this fastboot/adb.
https://www.androidfilehost.com/?fid=95784891001612150
dottat said:
Unzip and try this fastboot/adb.
https://www.androidfilehost.com/?fid=95784891001612150
Click to expand...
Click to collapse
As soon as I get home I will. Quick question where should I install it? Meaning should I install it directly to the C:/ drive? or should I make a sub folder? Or does it matter?
eriknors said:
As soon as I get home I will. Quick question where should I install it? Meaning should I install it directly to the C:/ drive? or should I make a sub folder? Or does it matter?
Click to expand...
Click to collapse
Not an install. Unzip and run cmd prompt from there. Note that your fastboot commands will start HTC_fastboot
Ok sorry if I sound lame but I want to make sure I get this right. So unzip the file, open a cmd prompt window from where I unzipped the file correct (eg: C:/downloads/HTC_fastboot/ ) then from there see type in fastboot devices?
eriknors said:
Ok sorry if I sound lame but I want to make sure I get this right. So unzip the file, open a cmd prompt window from where I unzipped the file correct (eg: C:/downloads/HTC_fastboot/ ) then from there see type in fastboot devices?
Click to expand...
Click to collapse
Once you extract it simply browse to the new folder, hold shift key and right click. Select open cmd prompt here.
Got it
dottat said:
Once you extract it simply browse to the new folder, hold shift key and right click. Select open cmd prompt here.
Click to expand...
Click to collapse
No dice. ADB worked just fine but still no fastboot
eriknors said:
No dice. ADB worked just fine but still no fastboot
Click to expand...
Click to collapse
Are you typing in "fastboot" or "HTC_fastboot"?
Sent from my HTC6500LVW using XDA Free mobile app
Are you trying on usb 2.o or 3.o? Last I read, 3.o didnt have support for fastboot yet. But I could be wrong.
Uzephi said:
Are you typing in "fastboot" or "HTC_fastboot"?
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
I don't follow. Do u mean the command?
Eg: (HTC_fastboot devices) or (fastboot devices)
I'm just typing fastboot (cmd)
Acoustichayes said:
Are you trying on usb 2.o or 3.o? Last I read, 3.o didnt have support for fastboot yet. But I could be wrong.
Click to expand...
Click to collapse
Well tbh I've been trying on both just to see if anything works.
eriknors said:
I don't follow. Do u mean the command?
Eg: (HTC_fastboot devices) or (fastboot devices)
I'm just typing fastboot (cmd)
Click to expand...
Click to collapse
He asked that because if you use mine you need to use htc_fastboot devices
Otherwise you will be using the fastboot from sdk install.
eriknors said:
No dice. ADB worked just fine but still no fastboot
Click to expand...
Click to collapse
Had the same issue tried every thing, but eventually end up installing uBuntu that solved every thing.
http://blogs.msdn.com/b/usbcoreblog...8-0-but-fail-on-windows-8-1-with-code-43.aspx
Its due to the missing device descriptor.
Royal PITA, I have yet to get it working. I just keep a win7 laptop around.
The only way this could be "fixed", would be if we had a newer eng-hboot that had the descriptors set.
Hi all,
I'm here because i don't know where else to look..
I've got a nexus 9 tablet running 5.1.1, its rooted with an unlocked bootloader, running twrp custom recovery, i was trying to flash a new rom, now all i get is a constant google logo upon bootup, I can enter recovery and fastboot and all of that, but none of my computers can see the tablet in adb or fastboot when I plug it in via usb, so Im not able to flash anything from my computer, does anyone have any ideas? or have I totally ****ed my nexus 9?
I have 2 laptops running Ubuntu, and my desktop is Windows 7 with all the necessary drivers, I've never had issues connecting my devices in the past, so I'm kinda at a loss.
have you flash all the .img file manually..if yes then try to factory reset first and see what happen..if no then you need to flash stock recovery and then factory reset..hopefully it help
Sent from my Nexus 9 using Tapatalk
Check your drivers in windows again.
Nexus Root Toolkit has a driver guide if needed.
Hope your not trying "adb devices" while in fastboot mode? Try "fastboot devices" while in that mode.
kacang87 said:
have you flash all the .img file manually..if yes then try to factory reset first and see what happen..if no then you need to flash stock recovery and then factory reset..hopefully it help
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
I have tried to do that, factory reset just resulted in no change to the tablet
corkiejp said:
Check your drivers in windows again.
Nexus Root Toolkit has a driver guide if needed.
Hope your not trying "adb devices" while in fastboot mode? Try "fastboot devices" while in that mode.
Click to expand...
Click to collapse
no, no, I know not to use adb devices while in fastboot, but I can put my tablet in fastboot, but any time I try to give it a command via my laptop, it just says "waiting on device", its like the computer doesn't recognize that the tablet has been connected...
Baskinmfr said:
no, no, I know not to use adb devices while in fastboot, but I can put my tablet in fastboot, but any time I try to give it a command via my laptop, it just says "waiting on device", its like the computer doesn't recognize that the tablet has been connected...
Click to expand...
Click to collapse
change your cable connect to computer..some cable cannot sent data..happen to me
Sent from my Nexus 9 using Tapatalk
Can you enter recovery? If you can then use your computer to copy the zip file of a rom and install it. Otherwise check your cable, I had problems with the one htc gave me.