Develop Bugs

[Q] Stuck on HTC Logo, can't get into bootloader after root attempt

Hi, I know there are a lot of other similar threads but none of them have solved my problem.
I ingeniously decided to try upgrading an old Desire HD to Jelly Bean to use while I'm waiting for a new phone that I actually want to be released. I followed the instructions here: http://forum.xda-developers.com/showthread.php?t=2221039 successfully until this part:
7.If this is all fine boot into bootloader again.
From bootloader go to fastboot.
Go back to the cmd window on your PC from earlier, type in:
•Fastboot oem lock
Then type:
•fastboot oem rebootRUU
•fastboot flash zip firmware.zip
•fastboot reboot-bootloader
unlock the bootloader again using the Unlock_code.bin you got from HTC:
•fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
After I ran "fastboot flash unlocktoken Unlock_code.bin" my phone restarted and now it's stuck on the htc logo. I'm unable to get into the the bootloader by holding volume down while powering the device (though I was having this problem before starting the root process, instead I was using "adb reboot-bootloader" to get into it). I've also tried to leave the battery out for a while. It's not being detected by HTCSync or "adb devices" either.
Anyone have any solutions to this problem? I'm a complete Android noob so please keep it simple (though I have experience with UNIX and the command-line).

konungr said:
Hi, I know there are a lot of other similar threads but none of them have solved my problem.
I ingeniously decided to try upgrading an old Desire HD to Jelly Bean to use while I'm waiting for a new phone that I actually want to be released. I followed the instructions here: http://forum.xda-developers.com/showthread.php?t=2221039 successfully until this part:
After I ran "fastboot flash unlocktoken Unlock_code.bin" my phone restarted and now it's stuck on the htc logo. I'm unable to get into the the bootloader by holding volume down while powering the device (though I was having this problem before starting the root process, instead I was using "adb reboot-bootloader" to get into it). I've also tried to leave the battery out for a while. It's not being detected by HTCSync or "adb devices" either.
Anyone have any solutions to this problem? I'm a complete Android noob so please keep it simple (though I have experience with UNIX and the command-line).
Click to expand...
Click to collapse
stuck in the same place... before unlocking bootloader pc would recognise the phone. now it doesn't... i think were stuck unless a developer helps us

Hmm, remove and reinsert the battery, and plug it into a computer, don't power the phone on, wait and see if the computer detects it, if it does, try "adb devices" to see if it shows up.
Sent from my Desire HD using Tapatalk 4 Beta

humzaahmed155 said:
Hmm, remove and reinsert the battery, and plug it into a computer, don't power the phone on, wait and see if the computer detects it, if it does, try "adb devices" to see if it shows up.
Sent from my Desire HD using Tapatalk 4 Beta
Click to expand...
Click to collapse
Windows detects an "Android Phone" in Devices but "adb devices" is still empty.

konungr said:
Hi, I know there are a lot of other similar threads but none of them have solved my problem.
I ingeniously decided to try upgrading an old Desire HD to Jelly Bean to use while I'm waiting for a new phone that I actually want to be released. I followed the instructions here: http://forum.xda-developers.com/showthread.php?t=2221039 successfully until this part:
After I ran "fastboot flash unlocktoken Unlock_code.bin" my phone restarted and now it's stuck on the htc logo. I'm unable to get into the the bootloader by holding volume down while powering the device (though I was having this problem before starting the root process, instead I was using "adb reboot-bootloader" to get into it). I've also tried to leave the battery out for a while. It's not being detected by HTCSync or "adb devices" either.
Anyone have any solutions to this problem? I'm a complete Android noob so please keep it simple (though I have experience with UNIX and the command-line).
Click to expand...
Click to collapse
i had the same problem but fixed now. The way i did this was to actually take out the hardware for the volume rocker and check if the contacts are all in place. i then booted into bootloader by connecting my phone to a power source (computer or ac) and pressed the volume down button so that it registered. For some reason it seems to register you clicking the button better when its out of the key. Sorry if you don't understand this, I really don't know how to explain the rocker and the keys separately 0_o

Some times guys the firmware.zip file once flash does get stuck on the HTC White screen during the exploit just run ADB and continue with the unlocking of your radio. Its safe.

IBeKay said:
i had the same problem but fixed now. The way i did this was to actually take out the hardware for the volume rocker and check if the contacts are all in place. i then booted into bootloader by connecting my phone to a power source (computer or ac) and pressed the volume down button so that it registered. For some reason it seems to register you clicking the button better when its out of the key. Sorry if you don't understand this, I really don't know how to explain the rocker and the keys separately 0_o
Click to expand...
Click to collapse
Wooh!!! It worked !!! Thank you very much!!!
For future reference, this is how what I did to complete the root process:
1. Pull off the battery cover, take out the battery.
2. Rip off the label with IMEI and S/N and then use a toothpick or plastic tweezers to pull out the ribbon cable from the volume rocker (see video here: youtube[dotcom]/watch?v=JfatoeWbMRk&feature=player_detailpage&t=143)
3. Press the volume down button on the cable a few times to make sure it clicks then clean the inside of the volume rocker a bit, put the cable back in, and press volume down a few times to test it.
4. Put the battery back in, connect the USB to your computer, hold volume down and press the power button so that it goes into the bootloader.
5. Go into fastboot and continue the rest of the steps from the guide.
Note: if adb doesn't detect your phone then reboot it and enable USB debugging again in Settings > Applications > Development and then reboot into the bootloader.
Thanks to everyone that helped ! :good:

konungr said:
Wooh!!! It worked !!! Thank you very much!!!
For future reference, this is how what I did to complete the root process:
1. Pull off the battery cover, take out the battery.
2. Rip off the label with IMEI and S/N and then use a toothpick or plastic tweezers to pull out the ribbon cable from the volume rocker (see video here: youtube[dotcom]/watch?v=JfatoeWbMRk&feature=player_detailpage&t=143)
3. Press the volume down button on the cable a few times to make sure it clicks then clean the inside of the volume rocker a bit, put the cable back in, and press volume down a few times to test it.
4. Put the battery back in, connect the USB to your computer, hold volume down and press the power button so that it goes into the bootloader.
5. Go into fastboot and continue the rest of the steps from the guide.
Note: if adb doesn't detect your phone then reboot it and enable USB debugging again in Settings > Applications > Development and then reboot into the bootloader.
Thanks to everyone that helped ! :good:
Click to expand...
Click to collapse
glad I helped

konungr said:
Hi, I know there are a lot of other similar threads but none of them have solved my problem.
I ingeniously decided to try upgrading an old Desire HD to Jelly Bean to use while I'm waiting for a new phone that I actually want to be released. I followed the instructions here: http://forum.xda-developers.com/showthread.php?t=2221039 successfully until this part:
After I ran "fastboot flash unlocktoken Unlock_code.bin" my phone restarted and now it's stuck on the htc logo. I'm unable to get into the the bootloader by holding volume down while powering the device (though I was having this problem before starting the root process, instead I was using "adb reboot-bootloader" to get into it). I've also tried to leave the battery out for a while. It's not being detected by HTCSync or "adb devices" either.
Anyone have any solutions to this problem? I'm a complete Android noob so please keep it simple (though I have experience with UNIX and the command-line).
Click to expand...
Click to collapse
Hi
I have followed your all steps perfectly... after done i have reboot my desire hd it shows htc screen and goes to qualcom mode...plz tell what should i've to do now

[Q] Nexus 7v 2 Bootloader cannot be unlocked

Yesterday, I have tired several time, several tools to unlock my N7v2 bootloader. However, they all freezed on UNLOCK BOOTLOADER option on my device. (The process stucked after I pressed "Yes" and cannot go back to fastboot:crying. So I guess there's a problem with my bootloader, right? Please help me

Does your tablet reboot into bootloader?
If so just go in your adb directory and type
fastboot oem unlock

sfhub said:
Does your tablet reboot into bootloader?
If so just go in your adb directory and type
fastboot oem unlock
Click to expand...
Click to collapse
And do note that after pressing yes the device wipes all data and reboots itself. This can take 5-10 minutes.

sfhub said:
Does your tablet reboot into bootloader?
If so just go in your adb directory and type
fastboot oem unlock
Click to expand...
Click to collapse
I did what you said and typed fastboot oem unlock in cmd, then, the device rebooted into bootloader and unlock bootloader screen, but the failure was shown on cmd (unknown error, code error or something), then the device freezed on Yes&No in unlock bootloader. It's really strange.

Coronado is dead said:
And do note that after pressing yes the device wipes all data and reboots itself. This can take 5-10 minutes.
Click to expand...
Click to collapse
It's been stucked there more than 20mins```

jianada520 said:
I did what you said and typed fastboot oem unlock in cmd, then, the device rebooted into bootloader and unlock bootloader screen, but the failure was shown on cmd (unknown error, code error or something), then the device freezed on Yes&No in unlock bootloader. It's really strange.
Click to expand...
Click to collapse
You need to press VolUp to highlight Yes, then power to select

sfhub said:
You need to press VolUp to highlight Yes, then power to select
Click to expand...
Click to collapse
yup. I pressed VolUP to highlight Yes, power buttom to select. then it stucked T_T

Press power button for 60 seconds and try again

sfhub said:
Press power button for 60 seconds and try again
Click to expand...
Click to collapse
well...cmd shown Failed(unknown status code) after typed in fastboot oem unlock.Then, pressed Yes and freezed again omg... I have tired 3 times

jianada520 said:
well...cmd shown Failed(unknown status code) after typed in fastboot oem unlock.Then, pressed Yes and freezed again omg... I have tired 3 times
Click to expand...
Click to collapse
After it fails and you reboot, is the BL still locked at this point or is it unlocked already? Perhaps, it is already unlocked and you may just need to factory reset to get the device to fully boot up.
The little lock symbol on the boot screen will show a small break if the BL is unlocked.

jianada520 said:
well...cmd shown Failed(unknown status code) after typed in fastboot oem unlock.Then, pressed Yes and freezed again omg... I have tired 3 times
Click to expand...
Click to collapse
What the previous post said.
Also are you by chance using usb 3 port?

cowabunga said:
After it fails and you reboot, is the BL still locked at this point or is it unlocked already? Perhaps, it is already unlocked and you may just need to factory reset to get the device to fully boot up.
The little lock symbol on the boot screen will show a small break if the BL is unlocked.
Click to expand...
Click to collapse
It's still locking, and shows a locked status on the fastboot screen...I have done factory reset several times,but nothing was changed

sfhub said:
What the previous post said.
Also are you by chance using usb 3 port?
Click to expand...
Click to collapse
nope, it's all usb 2 port. All drivers are installed correctly, and it shows success after perform the Wug's NRT 1.71 full driver test .

sfhub said:
Press power button for 60 seconds and try again
Click to expand...
Click to collapse
wow, i finally unlocked it. I reinstalled bootloader interface while the device was freezing :victory:. It such a miracle. Thx for assisting me.:laugh:

jianada520 said:
wow, i finally unlocked it. I reinstalled bootloader interface while the device was freezing :victory:. It such a miracle. Thx for assisting me.:laugh:
Click to expand...
Click to collapse
What does "reinstalled bootloader interface" mean anyhow? You flash the bootloader again onto the device from the factory image? Or did you have to reinstall something on your computer (ie. drivers, etc...)?
Would be helpful to clarify for anyone who hits this thread in the future.

cowabunga said:
What does "reinstalled bootloader interface" mean anyhow? You flash the bootloader again onto the device from the factory image? Or did you have to reinstall something on your computer (ie. drivers, etc...)?
Would be helpful to clarify for anyone who hits this thread in the future.
Click to expand...
Click to collapse
It means I reinstalled bootloader interface driver on PC while the device was stucking on UNLOCK BOOTLOADER option screen.(after selected Yes). It suddenly turned into fastboot screen and continued to finish rest of processes. I hope this would be helpful for people who hits this thread. Make sure your USB drivers are installed correctly , because they seem installed correctly but actually not. If you got stuck on UNLOCK BOOTLOADER screen, try to reinstall it or install another usb driver..

Just wanted to say that this worked for me too!
I would get to the point where I would have to pick 'Yes' on the Nexus 7 screen using the volume buttons, and then when I would press the power button to confirm, it would just freeze. The volume buttons would not respond and I had to hard reboot by holding down the power button.
I just tried jianada520's method of getting to the 'freeze' point, and then I did this:
-Keep the tablet plugged in
-Open Device Manager and right click > uninstall the Android ADB interface and remove the driver
-Install the Driver (I used the Nexus Root Toolkit and installed/repaired the Universal Driver)
-Back on the Device Manager - Scan for hardware Changes
-Nexus should be detected and some kind of driver is installed
At this point the screen went back to the Bootloader menu automatically, but it now says 'LOCK STATE - unlocked', success!
Just thought I'd add my experience as this was sending me in circles for the past 2 hours of rebooting, reinstalling drivers etc.

dodgyc said:
Just wanted to say that this worked for me too!
I would get to the point where I would have to pick 'Yes' on the Nexus 7 screen using the volume buttons, and then when I would press the power button to confirm, it would just freeze. The volume buttons would not respond and I had to hard reboot by holding down the power button.
I just tried jianada520's method of getting to the 'freeze' point, and then I did this:
-Keep the tablet plugged in
-Open Device Manager and right click > uninstall the Android ADB interface and remove the driver
-Install the Driver (I used the Nexus Root Toolkit and installed/repaired the Universal Driver)
-Back on the Device Manager - Scan for hardware Changes
-Nexus should be detected and some kind of driver is installed
At this point the screen went back to the Bootloader menu automatically, but it now says 'LOCK STATE - unlocked', success!
Just thought I'd add my experience as this was sending me in circles for the past 2 hours of rebooting, reinstalling drivers etc.
Click to expand...
Click to collapse
Congratz. You explained the solution very clear.

[Q] HTC Desire won't turn on.

Hi, :cyclops:
I received a second-hand HTC Desire from a family member as my Samsung Galaxy S3 got stolen. The phone won't turn on, I don't know if it had previous problems but if someone could give me a list of things to try, and explain how to perform these things, that'd be great.
Here's some details about the problems and what I've tried:
I have plugged in the phone to a wall charger without a SD card or simcard in the phone. The LED light turns solid orange and stays on, the buttons on the phone light up and remain that way. The screen stays black and the phone makes no sound.
Sometimes if I hold down the power button, it vibrates once and nothing happens.
If I plug it into the pc, the pc registers the phone but nothing else happens.
I have tried battery pulls.
I have also held down the volume down button and power button together, I just get a continuous vibration for about 10 seconds and then nothing
I have tried holding down the power button for an extended period of time, but nothing.
Anything else I could try? Or maybe perform the tasks I have tried differently...
Any help would be appreciated I'm not fond of the alternative phone I would have to use.
Thank you

try pull the battery out for 10 seconds n put back in then press n hold back button then press n hold power button (both same time) see what happens, hopefully it will boot into fastboot. ur vol down button could be dodgy thats why wont boot into bootloader. The led comes on when plugged in and vibrates so thats a good sign. Why it only shows black screen? i dunno. Maybe u just need to flash a ruu. try the back button combo first

jmcclue said:
try pull the battery out for 10 seconds n put back in then press n hold back button then press n hold power button (both same time) see what happens, hopefully it will boot into fastboot. ur vol down button could be dodgy thats why wont boot into bootloader. The led comes on when plugged in and vibrates so thats a good sign. Why it only shows black screen? i dunno. Maybe u just need to flash a ruu. try the back button combo first
Click to expand...
Click to collapse
I tried the back button and power button combo, it vibrated once and then nothing. What next?

JeanFlea said:
I tried the back button and power button combo, it vibrated once and then nothing. What next?
Click to expand...
Click to collapse
Looks to me, like the phone is booting, but the screen isnt displaying anything. Pull the battery, then follow what jmcclue said to get into fastboot. Then setup adb, install this driver, plug the phone into your computer, and run "fastboot devices". See if your phone shows up.

Ok, So I'm downloading and installing these things on my pc and plugging the phone into the pc and doing it from there? Because nothing happens on the phone when I try the fastboot thing.. I'm not sure what these programs are or what they do.

JeanFlea said:
Ok, So I'm downloading and installing these things on my pc and plugging the phone into the pc and doing it from there? Because nothing happens on the phone when I try the fastboot thing.. I'm not sure what these programs are or what they do.
Click to expand...
Click to collapse
Yes. Adb/fastboot are executables which allow your pc to communicate with your device. You need to do this:
-setup adb
-install the driver that i linked
-follow the steps in jmcclue's post above to get your phone into fastboot mode
-plug the phone into the pc
-on the pc open up a command prompt window, and enter "fastboot devices"
-post a screenshot of the output of the command

Chromium_ said:
Yes. Adb/fastboot are executables which allow your pc to communicate with your device. You need to do this:
-setup adb
-install the driver that i linked
-follow the steps in jmcclue's post above to get your phone into fastboot mode
-plug the phone into the pc
-on the pc open up a command prompt window, and enter "fastboot devices"
-post a screenshot of the output of the command
Click to expand...
Click to collapse
The SDK Manager and the driver are both installed, however is there something else I could type in the command window? It says that "fastboot" is not a recognized command.

JeanFlea said:
The SDK Manager and the driver are both installed, however is there something else I could type in the command window? It says that "fastboot" is not a recognized command.
Click to expand...
Click to collapse
Did you completely follow the guide I linked above?

Chromium_ said:
Did you completely follow the guide I linked above?
Click to expand...
Click to collapse
Ok, I went over everything again and made sure I didn't miss anything. This was the output of the command:
HT07CPL02294 fastboot

JeanFlea said:
Ok, I went over everything again and made sure I didn't miss anything. This was the output of the command:
HT07CPL02294 fastboot
Click to expand...
Click to collapse
Aha, my prediction was correct. So the phone is actually booted into fastboot mode, but the screen is not on.
Lets get some more info out of this phone. Run this command and post the outptut "fastboot getvar all"

Chromium_ said:
Aha, my prediction was correct. So the phone is actually booted into fastboot mode, but the screen is not on.
Lets get some more info out of this phone. Run this command and post the outptut "fastboot getvar all"
Click to expand...
Click to collapse
Done.

JeanFlea said:
Done.
Click to expand...
Click to collapse
I would suggest running an RUU. Download it here: http://www.htcdev.com/process/legal_download/152
Let the phone charge for a bit though before you start.

Chromium_ said:
I would suggest running an RUU. Download it here: http://www.htcdev.com/process/legal_download/152
Let the phone charge for a bit though before you start.
Click to expand...
Click to collapse
So I let the phone charge for a while, how long would you suggest? And then I run the RUU. This should work?

JeanFlea said:
So I let the phone charge for a while, how long would you suggest? And then I run the RUU. This should work?
Click to expand...
Click to collapse
Yea let a charge for at least an hour. Then run the RUU. I cant guarantee that itll work, but if this doesnt work, I would think that there is some sort of disconnection with a screen cable. In that case, i would suggest dissembling the phone and making sure that all screen cables are connected properly. But hopefully the RUU will do the trick

Chromium_ said:
Yea let a charge for at least an hour. Then run the RUU. I cant guarantee that itll work, but if this doesnt work, I would think that there is some sort of disconnection with a screen cable. In that case, i would suggest dissembling the phone and making sure that all screen cables are connected properly. But hopefully the RUU will do the trick
Click to expand...
Click to collapse
Thank you so much for your help and patience I will try this. It's busy downloading, the LED on the phone is green so hopefully I won't have to let it charge for too long. I'll let you know if it works.

Chromium_ said:
Yea let a charge for at least an hour. Then run the RUU. I cant guarantee that itll work, but if this doesnt work, I would think that there is some sort of disconnection with a screen cable. In that case, i would suggest dissembling the phone and making sure that all screen cables are connected properly. But hopefully the RUU will do the trick
Click to expand...
Click to collapse
My guess is that who ever had the phone had it s-off and rooted then tried to run a ruu but the wrong one, thats why black screen. I seen this before (bout a year ago) Droidzone wrote a good guide explaining everything and how to fix it blind :cyclops:

My pc makes that sound when I plug in the phone but the HTC sync Manager and the pc doesn't revognize the device, nothing comes up. Will this be a problem?

JeanFlea said:
My pc makes that sound when I plug in the phone but the HTC sync Manager and the pc doesn't revognize the device, nothing comes up. Will this be a problem?
Click to expand...
Click to collapse
Make sure HTC sync isnt running in the background when you run the ruu (open task manager and kill any htc stuff before starting the ruu).
Check once more to see if "fastboot devices" recognizes the phone. If it does try the ruu. The ruu will tell you if it cant detect the phone. If that is the case, i have other solutions

Chromium_ said:
Make sure HTC sync isnt running in the background when you run the ruu (open task manager and kill any htc stuff before starting the ruu).
Check once more to see if "fastboot devices" recognizes the phone. If it does try the ruu. The ruu will tell you if it cant detect the phone. If that is the case, i have other solutions
Click to expand...
Click to collapse
It didn't detect the phone

JeanFlea said:
It didn't detect the phone
Click to expand...
Click to collapse
The ruu didnt detect it? Or fastboot devices?
Hmm, could be because its in fastboot mode. Try this:
-pull the battery then reinsert
-turn the phone on normally (hold power for a second, then release). Wait a few minutes for the phone to boot, then plug it in and try the ruu again.

Urgent - Boot and recovery problem!

Hi to all
I have a big problem. My HTC Desire HD is now "dead". So, everything is working normally, just fine, on JellyTime, but this afternoon everything get broken. Suddenly, after the boot animation is finished, nothing happens, the screen is "black". The phone works, because when I connect USB to the computer sound. I can not get into Recovery (Home + Volume Down), can not do anything. I tried to remove the battery, but it does not help. I tried with adb, but there is "error: device not found". So I installed the drivers, asking me activate USB Debugging on the phone, and I can not access the phone.
Do you have any idea how to access recovery mode and install the new ROM?
Please help!
Thanks in advance.

just turn on your device with press volume down + power to get into the bootloader..then from there you can select recovery

JJeamy said:
just turn on your device with press volume down + power to get into the bootloader..then from there you can select recovery
Click to expand...
Click to collapse
I try, but I can't. :crying:

SkipperRi said:
I try, but I can't. :crying:
Click to expand...
Click to collapse
can you explain more cleared about this..?, did you mean your volume rocker is already broken or what else..?
what is the last you know the state or your phone bootloader..?, unlocked with s-on or already s-off..?
and what about the stock RUU..did you had already tried to flashing it through the pc..?

JJeamy said:
can you explain more cleared about this..?, did you mean your volume rocker is already broken or what else..?
what is the last you know the state or your phone bootloader..?, unlocked with s-on or already s-off..?
and what about the stock RUU..did you had already tried to flashing it through the pc..?
Click to expand...
Click to collapse
I finally managed this problem. I pulled off the battery over the night, and this morning I can booted into the recovery. So, I installed new ROM, all my apps, and now I performed backup to the my PC.
Thanks for help!
Regards.

Again same problem. For few hours everything seems fine, but just now my HTC has "blank" screen... Nothing to do. Again, I can't go to Recovery, nothing... What's going on with this phone?!?!

JJeamy said:
can you explain more cleared about this..?, did you mean your volume rocker is already broken or what else..?
what is the last you know the state or your phone bootloader..?, unlocked with s-on or already s-off..?
and what about the stock RUU..did you had already tried to flashing it through the pc..?
Click to expand...
Click to collapse
How to do this? And, if I do that, will be my phone still rooted after that?

SkipperRi said:
How to do this? And, if I do that, will be my phone still rooted after that?
Click to expand...
Click to collapse
no..you will lost it
what the state of your phone bootloader..?
unlocked or locked or nothing ?
s-on or s-off ?
hboot - ???
n your phone still can't go to bootloader with press volume down + power..?, is that the new rom you've already installed earlier..already by default it had enabled usb debugging under system settings..?

JJeamy said:
no..you will lost it
what the state of your phone bootloader..?
unlocked or locked or nothing ?
s-on or s-off ?
hboot - ???
n your phone still can't go to bootloader with press volume down + power..?, is that the new rom you've already installed earlier..already by default it had enabled usb debugging under system settings..?
Click to expand...
Click to collapse
No, I can't go to bootloader with volume down+power. About state of phone... S-off, that's I know. The ROM is installed earlier, but today I perform full wipe, and then installed ROM again, not backup/recovery, but fresh install. USB debugging is, as far I know, disabled... What should I do?

SkipperRi said:
No, I can't go to bootloader with volume down+power. About state of phone... S-off, that's I know. The ROM is installed earlier, but today I perform full wipe, and then installed ROM again, not backup/recovery, but fresh install. USB debugging is, as far I know, disabled... What should I do?
Click to expand...
Click to collapse
did you already try it adb is connected or not..?, just try first with "adb devices" (while the phone is on booting and had a black screen)
anyway why your phone can't go into bootloader by pressing volume down + power..?, is that already broken with your volume rocker..?
what happen if your pull out the battery first just a few minutes..then put in back again..and try it again pressing volume down+power..

JJeamy said:
did you already try it adb is connected or not..?, just try first with "adb devices" (while the phone is on booting and had a black screen)
anyway why your phone can't go into bootloader by pressing volume down + power..?, is that already broken with your volume rocker..?
what happen if your pull out the battery first just a few minutes..then put in back again..and try it again pressing volume down+power..
Click to expand...
Click to collapse
I don't know why can't go into bootloader with volumeD+power... I pulled battery, but everything is same. Can you please explain to me how can I try with adb?
Thank you so much for help!

SkipperRi said:
I don't know why can't go into bootloader with volumeD+power... I pulled battery, but everything is same. Can you please explain to me how can I try with adb?
Thank you so much for help!
Click to expand...
Click to collapse
i assume that you already had SDK/ADT or adb.exe and fastboot.exe on your PC.. if not just downloading from here..
and already had installing the latest HTC driver on your PC..
firstly your let the phone is boot like normal..then after you see the black screen..try connecting it to your pc..
then open your SDK folder (place of adb and fastboot.exe) then run cmd and source to your adb folder.. example : if your adb folder is in "C:/android tools/" then you must change source to that folder with typing "cd C:\android tools", now you ready to used it..don't closed it..just let it open
while your phone already booting n had black screen..then already connecting it to usb on your pc..then firstly try typing "adb devices" to check that's the phone is already connected with adb..
if your phone is detected..then you had prompt after that is your phone serial number that on list of attached devices
if success connected..then you can typing "adb reboot-bootloader" or "adb reboot recovery" (all command w/o quote)

JJeamy said:
i assume that you already had SDK/ADT or adb.exe and fastboot.exe on your PC..
firstly your let the phone is boot like normal..then after you see the black screen..try connecting it to your pc..
then open your SDK folder (place of adb and fastboot.exe) then run cmd and source to your adb folder.. example : if your adb folder is in "C:/android tools/" then you must change source to that folder with typing "cd C:\android tools", now you ready to used it..don't closed it..just let it open
while your phone already booting n had black screen..then already connecting it to usb on your pc..then firstly try typing "adb devices" to check that's the phone is already connected with adb..
if your phone is detected..then you had prompt after that is your phone serial number that on list of attached devices
if success connected..then you can typing "adb reboot-bootloader" or "adb reboot recovery" (all command w/o quote)
Click to expand...
Click to collapse
Thank you so much! I'll go and try right now and let you know what's going on.

JJeamy said:
while your phone already booting n had black screen..then already connecting it to usb on your pc..then firstly try typing "adb devices" to check that's the phone is already connected with adb..
(all command w/o quote)
Click to expand...
Click to collapse
Nothing. Here is what I get in CMD:
Code:
C:\adbfastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
What now?!

SkipperRi said:
Nothing. Here is what I get in CMD:
Code:
C:\adbfastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
What now?!
Click to expand...
Click to collapse
wel on my windows 8 i also get that blank line whre the serial number from the device should be but in my case its connected 'cause i can push files and to adb commands with it.
try to do adb reboot-bootloader and see if if does that

lexuz said:
wel on my windows 8 i also get that blank line whre the serial number from the device should be but in my case its connected 'cause i can push files and to adb commands with it.
try to do adb reboot-bootloader and see if if does that
Click to expand...
Click to collapse
Hm, I'm also on Windows 8, when I try command: adb reboot recovery then I get error: device not found.
But, when I connect/disconnect phone via USB there is a sound that detect connection...

SkipperRi said:
Hm, I'm also on Windows 8, when I try command: adb reboot recovery then I get error: device not found.
But, when I connect/disconnect phone via USB there is a sound that detect connection...
Click to expand...
Click to collapse
sorry can't help you more its up to the gurus here, try the thread ace think tank here on the forum

SkipperRi said:
Nothing. Here is what I get in CMD:
Code:
C:\adbfastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
What now?!
Click to expand...
Click to collapse
you sure that your pc already had latest HTC driver right and support with your OS..?
if so..maybe that's the usb debugging is not already active on your phone indeed..
because what i know is that just had two option to access your phone again:
1. with your volume down+power to access bootloader of your phone..and you can do it everything from there..
2. with adb command on android home of your phone..
while both option that is doesn't work..i'm sorry..i don't know more how the way to access your bootloader again beside the two way above..
anyway maybe you can try it again like the first way you success go into bootloader with pull out the battery over few hours like before..
and when you've already success flashing new rom again..don't forget firstly to enable it usb debugging from system settings..and connect as charge mode only..
and don't forget to disable fast boot mode too from system settings if you using sense rom

lexuz said:
sorry can't help you more its up to the gurus here, try the thread ace think tank here on the forum
Click to expand...
Click to collapse
Thank you anyway...
JJeamy said:
you sure that your pc already had latest HTC driver right and support with your OS..?
if so..maybe that's the usb debugging is not already active on your phone indeed..
because what i know is that just had two option to access your phone again:
1. with your volume down+power to access bootloader of your phone..and you can do it everything from there..
2. with adb command on android home of your phone..
while both option that is doesn't work..i'm sorry..i don't know more how the way to access your bootloader again beside the two way above..
anyway maybe you can try it again like the first way you success go into bootloader with pull out the battery over few hours like before..
and when you've already success flashing new rom again..don't forget firstly to enable it usb debugging from system settings..and connect as charge mode only..
and don't forget to disable fast boot mode too from system settings if you using sense rom
Click to expand...
Click to collapse
Yes, I have valid drivers, because before this disaster it was possible to connect phone with PC without any problems.
Have you any idea why the phone go "dead" after few hours working just perfect? Hardware or ROM related issue, what do you think?
I pulled battery out just now, for tommorow morning I giving up, maybe I'll be lucky and again I can with volume down + power booting into Recovery Mode.
Thank you, my friend!
P.S. Do you have any suggestion for some stable and good ROM?

SkipperRi said:
Thank you anyway...
Yes, I have valid drivers, because before this disaster it was possible to connect phone with PC without any problems.
Have you any idea why the phone go "dead" after few hours working just perfect? Hardware or ROM related issue, what do you think?
I pulled battery out just now, for tommorow morning I giving up, maybe I'll be lucky and again I can with volume down + power booting into Recovery Mode.
Thank you, my friend!
P.S. Do you have any suggestion for some stable and good ROM?
Click to expand...
Click to collapse
i'm not sure about that..until now..what i see is still software related..but i don't know what software exactly had the problem is..
can be from the recovery that you had installed the rom..or else..
to make sure what exactly is.. you must return the phone to the stock..stock bootloader, stock rom and stock recovery too..all back to the stock..with flashing stock RUU while your phone back in normal condition..
you know the forum rule is doesn't give any permission to all member for compare the rom..

[Q] I can't access Bootloader or Recovery PLEASE Help!

My HTC One M8 (Verizon) is seemingly bricked. My phone is rooted, S-Off, with the stock ROM. I have been trying to update to the latest OTA update by returning to stock. I had previously modified some entries in the Build.prop and Platform.xml. I knew those had to be default in order for the OTA to work. I had copied the original files and pasted them to my SD Card so that I could simply cut the modified versions, paste them to my SD Card, and cut the originals from my SD Card and put them in their corresponding system folders.
Upon a reboot something apparently went horribly wrong because all my phone does now is boot with the white screen and green HTC Logo, then the screen goes black. I have tried the typical Power Button + Volume Down but it won't enter the boot loader. The good news is that the USB port seems to still work for my windows computer recognizes a device connecting to it but it doesn't show up as an interactive device in windows explorer..if that makes sense.
Please Help!

SF-Echo18 said:
My HTC One M8 (Verizon) is seemingly bricked. My phone is rooted, S-Off, with the stock ROM. I have been trying to update to the latest OTA update by returning to stock. I had previously modified some entries in the Build.prop and Platform.xml. I knew those had to be default in order for the OTA to work. I had copied the original files and pasted them to my SD Card so that I could simply cut the modified versions, paste them to my SD Card, and cut the originals from my SD Card and put them in their corresponding system folders.
Upon a reboot something apparently went horribly wrong because all my phone does now is boot with the white screen and green HTC Logo, then the screen goes black. I have tried the typical Power Button + Volume Down but it won't enter the boot loader. The good news is that the USB port seems to still work for my windows computer recognizes a device connecting to it but it doesn't show up as an interactive device in windows explorer..if that makes sense.
Please Help!
Click to expand...
Click to collapse
When you connect it to the PC can you pick up the device with adb? If so, have you tried to run the command from adb to boot it into bootloader? adb devices ... if found, adb reboot bootloader
:fingers-crossed:

BerndM14 said:
When you connect it to the PC can you pick up the device with adb? If so, have you tried to run the command from adb to boot it into bootloader? adb devices ... if found, adb reboot bootloader
:fingers-crossed:
Click to expand...
Click to collapse
I'm not too familiar with ADB commands but I typed in "adb reboot recovery" and it said: "error: device not found" so even if my command was wrong it's still not detecting it. I also tried: "fastboot reboot bootloader" and it just says "waiting for device"
Also I feel like it's worth mentioning the phone is automatically rebooting every two minutes or so (haven't timed it exactly but it's a while). Still showing the green HTC Logo then the screen goes dim, then the screen turns off.

SF-Echo18 said:
I'm not too familiar with ADB commands but I typed in "adb reboot recovery" and it said: "error: device not found" so even if my command was wrong it's still not detecting it. I also tried: "fastboot reboot bootloader" and it just says "waiting on device for device"
Also I feel like it's worth mentioning the phone is automatically rebooting every two minutes or so (haven't timed it exactly but it's a while). Still showing the green HTC Logo then the screen goes dim, then the screen turns off.
Click to expand...
Click to collapse
Try holding volume UP + Power button, this simulates a "battery pull", just hold it in for a while it can take a while to "pull", when it's off try again booting into bootloader, volume DOWN + Power button.

BerndM14 said:
Try holding volume UP + Power button, this simulates a "battery pull", just hold it in for a while it can take a while to "pull", when it's off try again booting into bootloader, volume DOWN + Power button.
Click to expand...
Click to collapse
I held Volume Up + Power Button and it showed the white screen with the green HTC logo. I then released all buttons. Once the screen turned off I then held Volume Down + Power Button for two minutes straight and nothing happened.
Even though we haven't found a solution yet, I am appreciative of the help.

sounds like you never installed the htc drivers for your phone, hence your pc doesn't see the phone when you are doing ADB commands.
install the drivers for it, then try the ADB commands via your pc
and dont mess with the build prop or other system files unless you have a working back up and are 101% certain about what you are doing..

Just remember to change directory in command prompt to the folder where adb.exe is located.
I don't know why the device doesn't reboot into bootloader though when you hold volume down + power button, shouldn't have to hold it for 2minutes. Holding volume up + power button to simulate a "pull" should only take up to 20 seconds or so at most and pressing volume down + power will then immediately take you into bootloader mode, or at least it's supposed to.
Did you release the volume up / power combo when the screen went dead or before? Try holding it until the phone shuts off and then right away press volume down + power.
Sorry if I'm not answering right away though, busy eating, and will be here and away for the next hour or so while I get ready for work =o( once I leave for work I'll only be able to help some more after like 2 hours or so. Hopefully we can do something before then though =o)

wase4711 said:
sounds like you never installed the htc drivers for your phone, hence your pc doesn't see the phone when you are doing ADB commands.
install the drivers for it, then try the ADB commands via your pc
and dont mess with the build prop or other system files unless you have a working back up and are 101% certain about what you are doing..
Click to expand...
Click to collapse
You're right, I didn't install the drivers. I did so and ADB was able to recognize it and I was able to access the bootloader. Thank you everyone for your help. I won't be making the mistake again.

SF-Echo18 said:
You're right, I didn't install the drivers. I did so and ADB was able to recognize it and I was able to access the bootloader. Thank you everyone for your help. I won't be making the mistake again.
Click to expand...
Click to collapse
So you'll be able to fix it from here on then? I was just about to link this thread to you as well should you have gotten adb to work again, it's for the RUU for Verizon seeing as you said you're on Verizon.
But going by your response up there you might already know how to fix this issue further :good:

BerndM14 said:
So you'll be able to fix it from here on then? I was just about to link this thread to you as well should you have gotten adb to work again, it's for the RUU for Verizon seeing as you said you're on Verizon.
But going by your response up there you might already know how to fix this issue further :good:
Click to expand...
Click to collapse
Indeed I appreciate it, but I just finished installing the RUU ha. Hopefully this thread will be of use to someone in a similar circumstance in the future.

Share another method of getting into recovery mode on non-responsive blank screen
Hi,
I just want to share how I accessed recovery mode with the same build.prop issue but with S-ON (might work with S-Off too).
I found the solution from here:
http://forum.xda-developers.com/htc...ter-download-mode-t2853100/page2#post62490577
To get into recovery mode on a non-responsive blank screen, hold the power button and volume up button at the same time and then approximately after 10 seconds, switch from pressing the volume up to volume down button before the HTC logo white screen shows while still holding down the power button. After, a white boot screen will give an option to go into recovery mode.