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?
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 everyone, I was going to post this in dsb's kernel thread but I'm not allowed since I have less than 10 posts.
My problem is that I tried flashing dsb's cubed kernal (2.4.1) using the All In One Toolkit and I must have done something wrong because I am stuck in a bootloop.
I'm able to access the bootloader and enable Fastboot (computer recognizes the connection), but when I manually go to cmd window and type "adb devices" there are no devices listed.
When I enter device manager through Windows, I can see the computer recognizes the devices as "Android USB Devices". Is there a way to associate the adb drivers to this?
Thanks for the responses!
Edit: Well I realized part of my error was not copying the modules.zip to SDcard, assumed the Toolkit did this...teaches me to assume
I guess the question now is how to get the modules.zip to the SDcard if adb doesn't recognize it? Thanks!
It appears to be a driver issue. Try installing HTC Sync and then uninstalling it. I've read that it should keep the drivers.
Don't do adv devices, do fastboot devices.
Sent from my HTC6435LVW using xda app-developers app
Thanks for the input guys. I ended up just doing a factory reset and used titantium backup to restore everything. (whew!) Definitely was a driver problem and is working now.
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
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
im guessing i wont be the only one with this problem so im gonna make a post my phone reads in command prompt under adb devices however when i enter fastboot it wont show also i realized i cant restart my phone by holding power when in bootloader
Wrong section, chief...
You need to install fastboot drivers. They're different from the adb drivers. Keep your phone in fastboot mode and then install drivers on your computer.
Sent from my LG-H901 using Tapatalk
4lph4num3r1c said:
You need to install fastboot drivers. They're different from the adb drivers. Keep your phone in fastboot mode and then install drivers on your computer.
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
i must have done that somehow i also installed some **** from the sdk manager and then it worked so im happy sorry i dont really undrstand what goes where yet just started using xda and not very good at navigating it usta use it alot threw google search
Ask a mod to move this thread because it's def in the wrong section...
BeameD From My LG V10... The one with the ALWAYS ON SCREEN... Watching me.. ?
Thread moved to Q&A.
I am having the same problem, but I have the phone drivers, AND the adb drivers, AND the fastboot drivers installed. It still will not see the phone in fastboot mode. No matter what. Is there any other method to lock bootloader so I can get this phone back to a state where I can exchange it? It has tons of problems that I cannot tolerate any longer.