HTC Droid DNA Bootloader Unlock App Method (Difficulties) - Upgrading, Modifying and Unlocking

I have been trying to do this new method to unlock my DNA but im having difficulties getting my computer to recognize my phone. I installed the app and followed directions perfectly. But when i enter fastboot and enter the "fastboot oem readcid" command in the command prompt window it says "waiting for device". I have my phone connected via USB and i followed all directions, i want to unlock and get rooted. Anyone who could help or just tell me what i am doing wrong i would appreciate it very much Thank You.

did yaa enable enable usb debugging?
also what do you get when you do
Code:
fastboot devices

munchy_cool said:
did yaa enable enable usb debugging?
also what do you get when you do
Code:
fastboot devices
Click to expand...
Click to collapse
Yes i enable debugging, and when i get to the fastboot screen and enter the command "fastboot oem readcid" in the prompt window it excepts the command and says "waiting for device" like the PC is not recognizing my phone.

Guessphx said:
Yes i enable debugging, and when i get to the fastboot screen and enter the command "fastboot oem readcid" in the prompt window it excepts the command and says "waiting for device" like the PC is not recognizing my phone.
Click to expand...
Click to collapse
that's why i asked you to do a fastboot devices when in fastboot mode as that would list the devices attached, also are you on mac or windows and if windows which windows version, also please PM a mod and ask him to move this to the DNA q&a section, you'll get more help there.

As soon as I get back to the house in going to do that. But I have a PC with windows xp that I'm using.
Sent from my HTC6435LVW using xda app-developers app

Related

Stuck at: Waiting for device

Hey guys,
I followed this thread to unlock boot loader (http://forum.xda-developers.com/showthread.php?t=2694600), used the automated way to install adb drivers and did everything like the post says, but when I boot into bootloader and connect to my pc, when I type an adb command to get the code, it just stays at waiting for device for ages...
What I'm doing wrong? I even updated to the last api of adb, which are on the automated post (http://forum.xda-developers.com/showthread.php?t=2588979), posted by an user.
Can anyone help me please?
Thanks in advance!
You don't use ADB at the bootloader, you use fastboot. ADB is only when Android is running
Hgneto said:
Hey guys,
I followed this thread to unlock boot loader (http://forum.xda-developers.com/showthread.php?t=2694600), used the automated way to install adb drivers and did everything like the post says, but when I boot into bootloader and connect to my pc, when I type an adb command to get the code, it just stays at waiting for device for ages...
What I'm doing wrong? I even updated to the last api of adb, which are on the automated post (http://forum.xda-developers.com/showthread.php?t=2588979), posted by an user.
Can anyone help me please?
Thanks in advance!
Click to expand...
Click to collapse
This method does not require you to boot into bootloader. It does require S-off, however. Notice the instructions only tell you to boot into bootloader as the last step, simply to verify the unlock was successful.
Confused...
What? I don't know what to next then... I installed the automated way drivers, installed HTC connect program and allowed the connection via usb in developer options... What shall I do next to unlock boot loader?
For what I see on the VomerGuide it says after:
"Enter Fastboot (bootloader) Mode" ... now you are telling me that I do not need to...
When I enter in this Fastboot Mode, I connect the device to pc and then say the command to get the code, but it says waiting for device for ages and doesn't give me the code... Can you explain me what I'm doing wrong/what shall I do next?
Thanks in advance!
Hgneto said:
What? I don't know what to next then... I installed the automated way drivers, installed HTC connect program and allowed the connection via usb in developer options... What shall I do next to unlock boot loader?
For what I see on the VomerGuide it says after:
"Enter Fastboot (bootloader) Mode" ... now you are telling me that I do not need to...
When I enter in this Fastboot Mode, I connect the device to pc and then say the command to get the code, but it says waiting for device for ages and doesn't give me the code... Can you explain me what I'm doing wrong/what shall I do next?
Thanks in advance!
Click to expand...
Click to collapse
Make sure "usb debugging is enabled" on your phone, then cmd "adb devices" on PC and it should return your phonr serial number.
Will try that.
BTW, shall I enter in bootloader and then connect to PC, or do the other way around?
Thanks!
Sent from my G3
Hgneto said:
What? I don't know what to next then... I installed the automated way drivers, installed HTC connect program and allowed the connection via usb in developer options... What shall I do next to unlock boot loader?
For what I see on the VomerGuide it says after:
"Enter Fastboot (bootloader) Mode" ... now you are telling me that I do not need to...
When I enter in this Fastboot Mode, I connect the device to pc and then say the command to get the code, but it says waiting for device for ages and doesn't give me the code... Can you explain me what I'm doing wrong/what shall I do next?
Thanks in advance!
Click to expand...
Click to collapse
My apologies. I was looking under a different page from the link you provided. If you are following VomerGide, yes you do start in fastboot.
Try this first, though. Make sure USB debugging is enabled, leave phone on (not fastboot), plug it into your computer, and cmd "adb devices". If a message comes up on phone screen to allow computer connection, choose to always allow. Once you have gotten adb to recognize device, you can cmd "adb reboot bootloader" and phone should reboot into bootloader. In bootloader screen on phone, you might have to select fastboot mode. Then try to cmd "fastboot devices" and see if it brings up you device info. If so, you are good to go!

ADB won't work in fastboot

When I type ADB devices in fastboot it won't list my phone, however when I do it in ROM it my phone shows up. Anyone know how to fix this?
Nothing to fix, that's the way it is.
In fastboot mode, you use fastboot command
In ROM, you use adb command
meant fastboot devices, sorry I was a bit distracted when typing lol.
Do you see "fastboot usb" on the bootloader when connected to PC ?
Assuming it is a Windows .. is HTC drivers properly installed ?
ckpv5 said:
Do you see "fastboot usb" on the bootloader when connected to PC ?
Assuming it is a Windows .. is HTC drivers properly installed ?
Click to expand...
Click to collapse
Got it sorted, turns out the USB driver didn't install properly. Chalking it up to windows 10 silliness. :good:

Problem with fastboot flashing

I have somehow installed the fastboot drivers for my Pixel C (although ADB still doesn't work), and have successfully (?) unlocked the bootloader.
If I try to flash either the newest bootloader in order to install the N Developer Preview or a TWRP image, I get the following message:
FAILED (command write failed (No such device or address))
Click to expand...
Click to collapse
I tried different USB ports but the result was the same. I found somewhere about fwtool, but in order to use that I have to be rooted (if I understood correctly).
Any other ideas?
_Raziel666 said:
I have somehow installed the fastboot drivers for my Pixel C (although ADB still doesn't work), and have successfully (?) unlocked the bootloader.
If I try to flash either the newest bootloader in order to install the N Developer Preview or a TWRP image, I get the following message:
I tried different USB ports but the result was the same. I found somewhere about fwtool, but in order to use that I have to be rooted (if I understood correctly).
Any other ideas?
Click to expand...
Click to collapse
I'm assuming that since you were able to "successfully" unlock the bootloader that you can do this to check and see if your PC still recognizes your device. So, while you have you're Pixel C in fastboot and have it connected to your PC, open a command prompt and type the words fastboot devices and see if it returns your device serial number. Normally the command prompt will show that message when your device is not properly connected with the correct drivers installed. Also, if you have the correct drivers installed your ADB should work if you have enabled USB Debugging in developer options.
Sent from my Nexus 6 using XDA-Developers mobile app
Well, fastboot devices (and all fastboot commands) works. As for ADB it shows my device, but says unauthorized and never asks for my authorization.
But the thing is that I cannot flash anything.
_Raziel666 said:
Well, fastboot devices (and all fastboot commands) works. As for ADB it shows my device, but says unauthorized and never asks for my authorization.
But the thing is that I cannot flash anything.
Click to expand...
Click to collapse
Okay. If it will recognize fastboot commands let's start over from the beginning. Go to developer options and verify OEM Unlocking is checked and USB Debugging is checked. If you have the correct ADB drivers installed you will receive a pop-up message that says "This computers RSA key fingerprint is xxxxxxxxx. Check the box to always allow. Next, boot to the bootloader and type fastboot devices in a command prompt window. If it returns your device serial number then we are good to go.
Next, open a command prompt window and type fastboot flashing unlock. (may have to use fastboot OEM unlock) I've seen both work for some reason. If you are successful your Pixel will give you a message saying the bootloader is unlocked and OS verification is off. Once it's complete it will boot into the bootloader again. Once this happens, boot normally and hurry through the setup wizard so you can enable developer options and enable USB Debugging.
Now, once this is done boot to the bootloader and open another command prompt window and type fastboot devices to verify you are connected. If you are connected then you can fastboot flash the Android"N" bootloader and install the developer preview. Lemme know how you make out.
If you want to chat over Hangouts my email is [email protected].
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
Okay. If it will recognize fastboot commands let's start over from the beginning. Go to developer options and verify OEM Unlocking is checked and USB Debugging is checked. If you have the correct ADB drivers installed you will receive a pop-up message that says "This computers RSA key fingerprint is xxxxxxxxx. Check the box to always allow. Next, boot to the bootloader and type fastboot devices in a command prompt window. If it returns your device serial number then we are good to go.
Next, open a command prompt window and type fastboot flashing unlock. (may have to use fastboot OEM unlock) I've seen both work for some reason. If you are successful your Pixel will give you a message saying the bootloader is unlocked and OS verification is off. Once it's complete it will boot into the bootloader again. Once this happens, boot normally and hurry through the setup wizard so you can enable developer options and enable USB Debugging.
Now, once this is done boot to the bootloader and open another command prompt window and type fastboot devices to verify you are connected. If you are connected then you can fastboot flash the Android"N" bootloader and install the developer preview. Lemme know how you make out.
If you want to chat over Hangouts my email is [email protected].
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks for the very descriptive post. The thing is that I have already done all that, with the exception of using ADB, the pop-up never appeared and my Pixel C appears as unauthorized in adb devices.
I know for a fact that the bootloader is unlocked, because everything got wiped afterwards, and I also get the message saying that the bootloader is unlocked in every boot.
The thing is I cannot flash neither the developer preview nor the TWRP image. I read somewhere about a similar thing some users had on Pixel C, but the solution was to either do something via TWRP or use fwtool that needs root. And I can do neither.
So that's why I started this topic to see if anyone can think of anything else.
Sent from my A0001 using Tapatalk
On thing to try is to go into the settings Developer Options and "revoke USB debugging authorization". Connect to PC and you should then be asked to allow the "fingerprint". Hopefully that will fix it. I assume you've tried changing the connection type - charging, File transfer etc. If you are using W10 Pro then you may have driver issues. There are many posts on the net about that os and Google's driver but I've yet to find a definitive answer, I now use a USB C card see http://forum.xda-developers.com/pixel-c/help/windows-10-pixel-c-type-c-ports-t3414423

Fasboot unlocking hangs - can't detect phone when it's in bootloader mode?

Hi.
Trying to flash a ROM to a Nexus 5X.
I have enabled OEM unlocking and USB debugging.
When I enter the command 'fastboot flashing unlock', I get '< waiting for device >' and it just stays there for ever and ever and ever.
I think this is happening because the computer isn't detecting the phone in bootloader mode. When the phone is on, in the normal Android state, my computer lists it when I type 'adb devices'. But when I put the phone in bootloader mode and type 'adb devices', nothing comes up.
Do I need to install different drivers?
Thanks.
Hiltil said:
Hi.
Trying to flash a ROM to a Nexus 5X.
I have enabled OEM unlocking and USB debugging.
When I enter the command 'fastboot flashing unlock', I get '< waiting for device >' and it just stays there for ever and ever and ever.
I think this is happening because the computer isn't detecting the phone in bootloader mode. When the phone is on, in the normal Android state, my computer lists it when I type 'adb devices'. But when I put the phone in bootloader mode and type 'adb devices', nothing comes up.
Do I need to install different drivers?
Thanks.
Click to expand...
Click to collapse
Replying to my own thread to say I figured it out
Although 'adb devices' didn't show the phone, 'fastboot devices' did
The problem wasn't that the computer wasn't seeing the phone; it was that I'd been using the wrong command. 'fastboot flashing unlock' didn't work, but 'fastboot oem unlock' did
You must reinstall fastboot drivers on computer.

[HELP] MI a2 lite Fastboot Exits aAutomatically

I have a mi a2 lite and i want to unlock its bootloader, i have alrready enabled oem unlocking on developer options, when i boot my device in fastboot and connect to computer, command window says waiting for device and after 15-20 seconds of connecting my device to my pc, fastboot mode automatically exits and shows charging animation. Please anyone can help?
My device is in andoid pie (stable).
Check if you have installed drivers and run "fastboot devices" to see if device is recognised.
Agree something with your PC.
Phone will automatically exit fastboot if no connection in timely manner.
Check drivers are installed, reboot your PC.
Also be sure USB debugging is on in Dev option and trust PC.
For me, I generally boot Android normal. Then plug into PC and from command line, "adb reboot bootloader". That should verify adb, If that doesn't work, your PC not talking to device.
hossman said:
Agree something with your PC.
Phone will automatically exit fastboot if no connection in timely manner.
Check drivers are installed, reboot your PC.
Also be sure USB debugging is on in Dev option and trust PC.
For me, I generally boot Android normal. Then plug into PC and from command line, "adb reboot bootloader". That should verify adb, If that doesn't work, your PC not talking to device.
Click to expand...
Click to collapse
I reinstalled the drivers and the command "adb reboot bootloader" works for me that means it boots to fastboot mode but when in fastboot mode, when i enter a command "fastboot devices" it does nothing and when i enter command "fastboot oem unlock" it again says waiting for any device.
i have attached a screenshot of it.
I've tried restarting my pc as well as my phone and after 5-6 attempts it is now unlocked.
Thanks guys for supporting and giving response to my post
Love ya'll
CherryFarmer8 said:
I reinstalled the drivers and the command "adb reboot bootloader" works for me that means it boots to fastboot mode but when in fastboot mode, when i enter a command "fastboot devices" it does nothing and when i enter command "fastboot oem unlock" it again says waiting for any device.
i have attached a screenshot of it.
Click to expand...
Click to collapse
same problem boss, did you already solved this? please help me out
Andrew.kathy said:
same problem boss, did you already solved this? please help me out
Click to expand...
Click to collapse
The solution for fastboot disconnecting after a few seconds are the windows drivers. There are different drivers for our phone, normal, bootloader and fastboot. Windows loads these drivers depending in which state the phone is.
If you still didn't find the correct drivers, you should try installing MiFlash, as it contains all the needed drivers for our phone
If you like to try the Linux way, there's a distro called FWUL linux here on XDA
capajga said:
The solution for fastboot disconnecting after a few seconds are the windows drivers. There are different drivers for our phone, normal, bootloader and fastboot. Windows loads these drivers depending in which state the phone is.
If you still didn't find the correct drivers, you should try installing MiFlash, as it contains all the needed drivers for our phone
If you like to try the Linux way, there's a distro called FWUL linux here on XDA
Click to expand...
Click to collapse
Yeah, just go to windows drivers, click update device driver, browse my computer, let me pick, choose android > next > and choose another version or try whatever you feel is appropriate
CherryFarmer8 said:
Yeah, just go to windows drivers, click update device driver, browse my computer, let me pick, choose android > next > and choose another version or try whatever you feel is appropriate
Click to expand...
Click to collapse
I also have this problem drivers are installed and fine but when I go to fastboot within like 15 sec it automatically turns off.
I fixed it with this https://forum.xda-developers.com/attachments/howto_driver-zip.2480396/

Categories

Resources