[Q] Cannot relock bootloader - HTC Droid DNA

I'm trying to relock my bootloader and unroot because I cracked my screen and wish to use my insurance to get a new DNA. My computer recognizes my phone when the phone is on, but when i boot into bootloader, the computer does the two beeps like a connection has been found but then is followed by 3 low pitched beeps like it failed. I'm S-ON. I can't do any work on my phone when in bootloader. When I try to enter the command "fastboot oem lock," it just says <waiting for device> I've installed the latest version of HTC Sync Manager so i'm sure the drivers are up to date.

HosstaLaVista said:
I'm trying to relock my bootloader and unroot because I cracked my screen and wish to use my insurance to get a new DNA. My computer recognizes my phone when the phone is on, but when i boot into bootloader, the computer does the two beeps like a connection has been found but then is followed by 3 low pitched beeps like it failed. I'm S-ON. I can't do any work on my phone when in bootloader. When I try to enter the command "fastboot oem lock," it just says <waiting for device> I've installed the latest version of HTC Sync Manager so i'm sure the drivers are up to date.
Click to expand...
Click to collapse
Try a different usb port. Uninstall HTC Sync, as I have seen sync cause problems before. Also try using a different cable if you have one. I have an old T-Bolt cable that will let you charge and transfer, but will not recognize phone in bootloader.

when in bootloader make sure that you are in fastboot and it says "fastboot usb"

Related

[Q] Problems unlocking bootloader

I've been trying to unlock the bootloader on my Legend using the HTCDev unlock guide, however I can't get past the initial update. It says "wait for bootloader..." before giving error 170 or 171 (USB connection) yet the cable is still connected. I have USB debugging on, and "adb devices" shows the phone connected and not offline, however "fastboot devices" lists nothing when in the fastboot screen on the bootloader. I can't see where I've gone wrong here as I have all the requirements listed by HTCDev, I have the correct ROM (3.14.161.1) and HBOOT v1.00, and I've checked again and again that I have downloaded the correct RUU.
What can I do?
Edit: Never mind, I was being stupid and didn't try other USB ports.

[Q] Relocking Droid DNA Bootloader Roadblock

Okay, so i'm using this guide to relock my bootloader and i've gotten to the part where I must enter in the command "fastboot oem lock." My phone just sits at "waiting for device." I read somewhere that the USB connection might not be 100% in the phone, so when I adjusted the plug, the computer unrecognized the device and I cannot do anything. The connection comes and goes as it pleases.

[Q] T-mobile HTC one Brick

I've had this phone for about a good 4 months now, was getting bored so i decide to unlock the bootloader, root, and install a new rom. Then i heard youwer able to activate the HTC logo button to wake and sleep your device with using a different kernel. tbaldens kernel v3.6. I have TWRP recovery installed with trickdroid as my rom.After i ran threw all the procedures to flash in Aroma installer. My phone won't turn on, when i connect it to my computer it shows up as a MTP device. When I do get it to power on its stuck at the "quietly brilliant" screen. cant get into recovery to restore from back up. PLEASE HELP! SOLDIER DEPLOYED!!!!!!!! dont have the means of sending it in. Any suggestion. Mac is my primary means of rooting. windows 8 drivers are kinda funky:crying::crying::crying::crying::crying::crying::crying:
If you have access to a Windows 7 PC, then download the RUU for your device. Next, relock your bootloader (fastboot oem lock) Next step, if you have bootloader access to your device, then you can go into fastboot (make sure it says fastboot USB). Open a command prompt, and type in fastboot oem rebootRUU. You're in RUU mode, where you can run the RUU and reset everything back to stock.
crashfocus said:
If you have access to a Windows 7 PC, then download the RUU for your device. Next, relock your bootloader (fastboot oem lock) Next step, if you have bootloader access to your device, then you can go into fastboot (make sure it says fastboot USB). Open a command prompt, and type in fastboot oem rebootRUU. You're in RUU mode, where you can run the RUU and reset everything back to stock.
Click to expand...
Click to collapse
can i do this from a mac? and i can't get into fastboot because it wont go past the htc logo screen. it is identified as a MTP device in windows
Ahhhh thankfully i was able to get into my bootloader and flash my recovery! but thanks for the reply bro

[Q] Can't fastboot boot.img

Okay, so basically I am a HUGE idiot. My phone has been running the latest version of ParanoidAndroid and I decided that I wanted to try MIUI. I booted into TWRP v2.6.3 and wiped everything a couple of times before installing it, and I forgot to install the boot.img afterwards (it was s-on). So now everytime I turn the phone on, it is just always on the boot animation for an eternity, and my computer won't recognize my phone so I can't use fastboot or use an RUU. I am also unable to flash PH98IMG from the phone itself. Is there anything I can do to fix this? Thank you very much in advance.
trp6senile said:
Okay, so basically I am a HUGE idiot. My phone has been running the latest version of ParanoidAndroid and I decided that I wanted to try MIUI. I booted into TWRP v2.6.3 and wiped everything a couple of times before installing it, and I forgot to install the boot.img afterwards (it was s-on). So now everytime I turn the phone on, it is just always on the boot animation for an eternity, and my computer won't recognize my phone so I can't use fastboot or use an RUU. I am also unable to flash PH98IMG from the phone itself. Is there anything I can do to fix this? Thank you very much in advance.
Click to expand...
Click to collapse
Take out the battery, put it back together, power on the phone while holding down the volume down key til you get the splash screen, that'll boot you to the bootloader...
No I understand that, but there's nothing I can do from the bootloader. Once I get there, I can either go to TWRP or choose Fastboot. When I choose fastboot, it will say Fastboot USB after connecting to my PC but it will still not show up or be recognized (and I have the drivers). My only other options are Recovery (TWRP), factory reset (also TWRP), clear storage, simlock, and image crc. All I need to do is load the boot.img file, but it appears to me I have no way of doing that now.
trp6senile said:
No I understand that, but there's nothing I can do from the bootloader. Once I get there, I can either go to TWRP or choose Fastboot. When I choose fastboot, it will say Fastboot USB after connecting to my PC but it will still not show up or be recognized (and I have the drivers). My only other options are Recovery (TWRP), factory reset (also TWRP), clear storage, simlock, and image crc. All I need to do is load the boot.img file, but it appears to me I have no way of doing that now.
Click to expand...
Click to collapse
Being seen in fastboot has nothing to do with the ROM at all, you need to troubleshoot this from the PC end. When you start fastboot on the phone and connect to your PC you get nothing? Not even a connect sound?
acejavelin said:
Being seen in fastboot has nothing to do with the ROM at all, you need to troubleshoot this from the PC end. When you start fastboot on the phone and connect to your PC you get nothing? Not even a connect sound?
Click to expand...
Click to collapse
I do get the connect and disconnect sounds. Whenever it makes the connect sound, it doesn't show up under "Devices with Removable Storage." When I heard the connect sound the first time I went to the cmd prompt and typed "fastboot devices" but it showed nothing.
trp6senile said:
I do get the connect and disconnect sounds. Whenever it makes the connect sound, it doesn't show up under "Devices with Removable Storage." When I heard the connect sound the first time I went to the cmd prompt and typed "fastboot devices" but it showed nothing.
Click to expand...
Click to collapse
It won't show up as a drive at all in Fastboot mode, to see if it is connected properly go to Device Manager and look for ADB Interface -> My HTC, if it isn't there then your drivers are not installed properly. Drivers come from HTC Sync, which can be downloaded here: http://www.htc.com/us/support/content.aspx?id=6196 once installed and the connections in Fastboot and ADB verified to be working, HTC Sync can be uninstalled (the drivers will stay).
When you run "fastboot devices" you get nothing? Or do you get something like "< waiting for device >" or literally nothing?
What version of Windows are you running, you need to be on Windows 7 or older? Running under Windows 8 is not recommended.
acejavelin said:
It won't show up as a drive at all in Fastboot mode, to see if it is connected properly go to Device Manager and look for ADB Interface -> My HTC, if it isn't there then your drivers are not installed properly. Drivers come from HTC Sync, which can be downloaded here: <link> once installed and the connections in Fastboot and ADB verified to be working, HTC Sync can be uninstalled (the drivers will stay).
When you run "fastboot devices" you get nothing? Or do you get something like "< waiting for device >" or literally nothing?
What version of Windows are you running, you need to be on Windows 7 or older? Running under Windows 8 is not recommended.
Click to expand...
Click to collapse
Ah, that may be my problem then, as I am on a Windows 8 computer. I will try all of this on a friends W7 computer in the next few hours and report back with the results. And when I did fastboot devices it literally said nothing and was ready for another command. Thanks for the help!
trp6senile said:
Ah, that may be my problem then, as I am on a Windows 8 computer. I will try all of this on a friends W7 computer in the next few hours and report back with the results. And when I did fastboot devices it literally said nothing and was ready for another command. Thanks for the help!
Click to expand...
Click to collapse
You can also use a live Linux CD like Ubuntu and boot that and install the Linux version of ADB, it works fine.

Need help updating to KitKat with RUU

So I have an AT&T HTC One M7 that is S-Off, unlocked, and rooted (used revone). Needless to say it cannot receive OTA updates, they fail with a red x and for some reason it constantly checks for updates and forces an install after 3 postpones. The phone is currently on 4.1.2 (1.26.502.10) and has HBOOT 1.44.
So I'm trying to update it by using an RUU (RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2), this seems to fail at "Waiting for bootloader".
Process:
Have phone booted normally
Plug phone into computer, verify connectivity with "adb devices"
Run RUU and get to the point where it reboots the phone to the silver logo and then it stays at "Waiting for bootloader" until I reset the phone
When it's on the silver logo I tested "fastboot devices" and it does display the phone as connected
Any ideas on how to proceed?
billy_rud10 said:
So I have an AT&T HTC One M7 that is S-Off, unlocked, and rooted (used revone). Needless to say it cannot receive OTA updates, they fail with a red x and for some reason it constantly checks for updates and forces an install after 3 postpones. The phone is currently on 4.1.2 (1.26.502.10) and has HBOOT 1.44.
So I'm trying to update it by using an RUU (RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2), this seems to fail at "Waiting for bootloader".
Process:
Have phone booted normally
Plug phone into computer, verify connectivity with "adb devices"
Run RUU and get to the point where it reboots the phone to the silver logo and then it stays at "Waiting for bootloader" until I reset the phone
When it's on the silver logo I tested "fastboot devices" and it does display the phone as connected
Any ideas on how to proceed?
Click to expand...
Click to collapse
You are probably using windows 8 which is, by default, not compatible with hboot 1.44 hence why the ruu is waiting for fastboot connection forever. Use a windows 7 computer. I know there is a way to fix this issue in windows 8 but I never tried it. I think clsA could help you with this.
i'm actually on Windows 7. I was able to fix this by running the RUU for 4.3 and then doing a "fastboot flash zip" for the rom.zip from 4.4

Categories

Resources