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.
Related
Searched many places for my problem but cannot find it specifically and this forum seems to be more clued up than most so here goes.
One x screen started to occasionally freeze on unlock screen (volume buttons worked also the volume pop up came on so screen itself not frozen just couldnt touch input i presume) but would fix with either a full power down or a few presses of the top button. Over the course of a day or two this has progressed to virtually always freezing and finally to where i couldnt unfreeze it even after powering down.
Did a factory reset which did give me access to my phone again but still the problem persists.
From my research it could possibly be some sort of cache problem. Also noticed after factory reset with no apps or data installed, apart from the preinstalled ones, am using 4.7 gb of internal memory with only htc sense running. this seems excessive to me but never checked it before so not sure if this is about right. If not then the cache theory could be right.
So can anyone help me please.
bump
thebarran said:
Searched many places for my problem but cannot find it specifically and this forum seems to be more clued up than most so here goes.
One x screen started to occasionally freeze on unlock screen (volume buttons worked also the volume pop up came on so screen itself not frozen just couldnt touch input i presume) but would fix with either a full power down or a few presses of the top button. Over the course of a day or two this has progressed to virtually always freezing and finally to where i couldnt unfreeze it even after powering down.
Did a factory reset which did give me access to my phone again but still the problem persists.
From my research it could possibly be some sort of cache problem. Also noticed after factory reset with no apps or data installed, apart from the preinstalled ones, am using 4.7 gb of internal memory with only htc sense running. this seems excessive to me but never checked it before so not sure if this is about right. If not then the cache theory could be right.
So can anyone help me please.
Click to expand...
Click to collapse
Did you try RUU?
Not rooted my phone so was hoping to find a fix without rooting in case i have to send it back.
thebarran said:
Not rooted my phone so was hoping to find a fix without rooting in case i have to send it back.
Click to expand...
Click to collapse
Try following this:
http://forum.xda-developers.com/showthread.php?t=1859714
No need to root / unlock bootloader
EDIT: follow option 2
following option 2 but stuck.
Make sure that USB debugging is enabled (Settings/Developer options). In order to determine which ruu file you require, boot your device into bootloader mode (Power off and then restart device by holding Power and Volume Down button together). Connect to pc via USB and check that device shows FASTBOOT USB on screen. Enter the following command in command prompt:
fastboot getvar version-main
But when i enter that in Command prompt i get fastboot is not recognised command etc using windows 8. Any help
Note: my phone is locked
thebarran said:
following option 2 but stuck.
Make sure that USB debugging is enabled (Settings/Developer options). In order to determine which ruu file you require, boot your device into bootloader mode (Power off and then restart device by holding Power and Volume Down button together). Connect to pc via USB and check that device shows FASTBOOT USB on screen. Enter the following command in command prompt:
fastboot getvar version-main
But when i enter that in Command prompt i get fastboot is not recognised command etc using windows 8. Any help
Note: my phone is locked
Click to expand...
Click to collapse
Can you try running fastboot on a different OS? Windows XP/7, Ubuntu? Something else?
EDIT: BTW, are you sure you are running the fastboot command from the fastboot folder?
davidk-il said:
EDIT: BTW, are you sure you are running the fastboot command from the fastboot folder?
Click to expand...
Click to collapse
not doing this what do you mean?
thebarran said:
not doing this what do you mean?
Click to expand...
Click to collapse
Navigate on your PC to the fastboot folder lets say "c:\fastboot".
Shift+right click on any blank place and choose open command window here(or something like that my OS is not in english now).
Try using fastboot commands .
ah nice works, thanks. stay with me in case i get stuck again.
thebarran said:
ah nice works, thanks. stay with me in case i get stuck again.
Click to expand...
Click to collapse
Sorry,
Gotta get some sleep =)
If after running RUU nothing changes take the phone to service.
more problems
Ran and installed the ruu but got an
error[152]:image update error
The ROM update utility cannot update your android phone.
Please get the correct ROM update utility and try again
But i have the correct version already 3.14.401.31 it just wont install and now my phone is stuck on a black screen with htc in centre and nothing else.
Did you run the ruu.exe as a administrator ?
Right click the ruu exe and select that.....and put the phone in the bootloader/fastboot usb mode
Mr Hofs said:
Did you run the ruu.exe as a administrator ?
Right click the ruu exe and select that.....and put the phone in the bootloader/fastboot usb mode
Click to expand...
Click to collapse
tried it in admin mode still no good and cant get to any other screen on my phone now other than the black screen with htc in the middle
thebarran said:
tried it in admin mode still no good and cant get to any other screen on my phone now other than the black screen with htc in the middle
Click to expand...
Click to collapse
Phone for sure in fastboot usb mode?
davidk-il said:
Phone for sure in fastboot usb mode?
Click to expand...
Click to collapse
it was when i first did it biut cannot check no more
Hold the power button and the volume - button together until it reboots and boots into the bootloader, hook the usb cable and you should see "fastboot usb" in red text. At that point you run the ruu with administrator rights
Mr Hofs said:
Hold the power button and the volume - button together until it reboots and boots into the bootloader, hook the usb cable and you should see "fastboot usb" in red text. At that point you run the ruu with administrator rights
Click to expand...
Click to collapse
i cannot. all that happens now is that it powers down and comes back to the black htc screen. cannot get to boot screen anymore.
thebarran said:
i cannot. all that happens now is that it powers down and comes back to the black htc screen. cannot get to boot screen anymore.
Click to expand...
Click to collapse
Try shutting of the phone, powering on when holding power button+volume down for about 8s.
You will get a hboot, choose fastboot connect usb cable and try ruu with admin permissions
finally did get to hboot screen by letting the phone shutdown itself but couldnt ruu as battery power to low so i powered down and recharged battery but back to square one where i cannot get to boot screen just constant black htc screen and cant power down again.
So ill let my battery run down again to power off completely open boot screen then stay on that til i power up enough to try ruu again.
Il let you know what happens when this is done later.
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
Good day!
After searching everywhere in the web and using different methods, I decided to create an account and ask you guys how to solve my problem
Basically, I have a HTC Desire HD phone, this is unlocked, rooted and using cm-Jellytime_42_R11 ROM. I decided to change ROM and go back to Android Revolution. What I did first was I deleted a couple of folders in my clockwork folder, I deleted both backup to free space. Afterwards, I was trying to connect my phone to my laptop but to no avail (it only charged) then I decided to just boot into recovery. After a couple of tries trying to access and going to bootloader/recovery mode it just wont push through. So I decided to normal boot, then the phone won't boot anymore. It just hanged in the Jellytime loading screen.
Note: I removed the battery a couple of too many times since I was trying to boot into recovery.
Thanks in advance to anyone who can help me with this problem
I didn't understand very well.
Can you now go to Hboot screen volume (-) + power button?
And where you get now stucked when you just power on phone?
Gussta said:
I didn't understand very well.
Can you now go to Hboot screen volume (-) + power button?
And where you get now stucked when you just power on phone?
Click to expand...
Click to collapse
no, i couldnt go to Hboot while holding down volume - and power.
The phone gets stucked in the Jellytime loading screen. It just stops. help me please
What does it do when you try to go to hboot? Is it detected in fastboot? Is it detected in adb when you try to boot normally?
bananagranola said:
What does it do when you try to go to hboot? Is it detected in fastboot? Is it detected in adb when you try to boot normally?
Click to expand...
Click to collapse
it does nothing. It just cant go to hboot. it wont normal boot too. so stuck.
richardrip10 said:
it does nothing. It just cant go to hboot. it wont normal boot too. so stuck.
Click to expand...
Click to collapse
WHen it getts stuck in the roms boot animation, connect usb to the phone and try
Code:
adb devices
Most devices show up via adb during the boot animation.
If the device shows up there, enter
Code:
adb reboot bootloader
then go here and download 4ext recovery.
extract the .img file from the zip. Rename it to recovery.img and place it in your adb directory and enter this whiles in fastboot
Code:
fastboot devices
to make sure your device shows up
then
Code:
fastboot flash recovery recovery.img
after it has successfully flashed reboot to recovery ad try and flash the rom u want.
hope i helped. Click on the thanks buttton.
You can ask if you still have problems.
computer doesn't recognize android. laptop doesnt even make sound that a device has been connected. I checked the device manager but to no avail. but the phone is charging.
richardrip10 said:
computer doesn't recognize android. laptop doesnt even make sound that a device has been connected. I checked the device manager but to no avail. but the phone is charging.
Click to expand...
Click to collapse
What recovery were you using before this happened?
mickeyasamoah said:
What recovery were you using before this happened?
Click to expand...
Click to collapse
cwm sir.
richardrip10 said:
cwm sir.
Click to expand...
Click to collapse
I dont know if this is going to work with CWM but it works on TWRP and 4ext.
Remove the battery and re-insert it.
Now connect the usb to the device.
Dont press the power button.(leave it off)
After the the charging light comes on, the device should be discoverable by adb.
Now try
Code:
adb devices
It should be detected by adb.
mickeyasamoah said:
I dont know if this is going to work with CWM but it works on TWRP and 4ext.
Remove the battery and re-insert it.
Now connect the usb to the device.
Dont press the power button.(leave it off)
After the the charging light comes on, the device should be discoverable by adb.
Now try
Code:
adb devices
It should be detected by adb.
Click to expand...
Click to collapse
sorry, it still didn't work. Is this a bricked phone?
mickeyasamoah said:
I dont know if this is going to work with CWM but it works on TWRP and 4ext.
Remove the battery and re-insert it.
Now connect the usb to the device.
Dont press the power button.(leave it off)
After the the charging light comes on, the device should be discoverable by adb.
Now try
Code:
adb devices
It should be detected by adb.
Click to expand...
Click to collapse
btw, my computer really cant detect my phone. It doesnt make any sound when it is connected through USB. but other devices can be detected by my computer. I tried inserting the usb into a 2.0 and 3.0 usb.
mickeyasamoah said:
I dont know if this is going to work with CWM but it works on TWRP and 4ext.
Remove the battery and re-insert it.
Now connect the usb to the device.
Dont press the power button.(leave it off)
After the the charging light comes on, the device should be discoverable by adb.
Now try
Code:
adb devices
It should be detected by adb.
Click to expand...
Click to collapse
hey bro, I actually made it work. problem is when im flashing the recovery, it shows Failed<remote: not allowed>
what should I do?
mickeyasamoah said:
I dont know if this is going to work with CWM but it works on TWRP and 4ext.
Remove the battery and re-insert it.
Now connect the usb to the device.
Dont press the power button.(leave it off)
After the the charging light comes on, the device should be discoverable by adb.
Now try
Code:
adb devices
It should be detected by adb.
Click to expand...
Click to collapse
no worries now brother! was able to fix my phone now! THANK YOU SO MUCH! :good::good::good:
richardrip10 said:
no worries now brother! was able to fix my phone now! THANK YOU SO MUCH! :good::good::good:
Click to expand...
Click to collapse
Okay Brother.. Guess you should post how you fixed it in the OP so that others with the same problem can look it up.
mickeyasamoah said:
Okay Brother.. Guess you should post how you fixed it in the OP so that others with the same problem can look it up.
Click to expand...
Click to collapse
Ok, so basically, the problem why i can't do the power button + vol (-) is that my volume buttons are broken. (sad) Second, the reason why my computer wasn't detecting my phone is that my phone's charging slot is dirty and I had to clean it with a needle to remove the dust, at the same time, the cable I was using was broken. When I was able to clean the slot and change cables, I then followed the steps by mickeyasamoah (thanks bro) with the adb procedures. Although it failed when it was in the flash recovery line (dunno why), I just proceeded into flashing a new ROM and voila, it worked.
richardrip10 said:
Ok, so basically, the problem why i can't do the power button + vol (-) is that my volume buttons are broken. (sad) Second, the reason why my computer wasn't detecting my phone is that my phone's charging slot is dirty and I had to clean it with a needle to remove the dust, at the same time, the cable I was using was broken. When I was able to clean the slot and change cables, I then followed the steps by mickeyasamoah (thanks bro) with the adb procedures. Although it failed when it was in the flash recovery line (dunno why), I just proceeded into flashing a new ROM and voila, it worked.
Click to expand...
Click to collapse
I am happy i was able to help.
Instead of saying thanks only, you could actually hit the thanks button.
Have a nice day.
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.
I flashed a RUU for wildfire s, everything seems to be fine.
But after it finished and told me your phone will now restart............---------> only the screen turns on and off, on and off.
Nothing else. I cannot go into bootloader or start the phone, no htc logo... nothing =(
I pulled the battery and tried to restart the phone, restarting into bootloader, connecting to fastboot, flashing ruu again, but nothing worked.
No connection to pc at all and no signal on the phone. Only: background light turns on and off, turns on and off.
What can i do ?
Please help me.
I am happy for any replies.
I will pay 20 Euros, if someones solution works.
You might want to take a look at this.
http://forum.xda-developers.com/showthread.php?t=1622178
Hope that helps.
cortezthekiller said:
You might want to take a look at this.
http://forum.xda-developers.com/showthread.php?t=1622178
Hope that helps.
Click to expand...
Click to collapse
Thanks a lot, but i have already known this thread.
The guy, B3NJY, with same problem, could not solve it. At least he sent his phone to repair service.
Maybe someone else knows how to unbrick a softbricked wildfire s.?
I flashed a lot and know how to use fastboot etc., ....
Like i said, backlight is working but nothing else.
appyleptiker said:
I flashed a RUU for wildfire s, everything seems to be fine.
But after it finished and told me your phone will now restart............---------> only the screen turns on and off, on and off.
Nothing else. I cannot go into bootloader or start the phone, no htc logo... nothing =(
I pulled the battery and tried to restart the phone, restarting into bootloader, connecting to fastboot, flashing ruu again, but nothing worked.
No connection to pc at all and no signal on the phone. Only: background light turns on and off, turns on and off.
What can i do ?
Please help me.
I am happy for any replies.
Click to expand...
Click to collapse
I think you flash wrong RUU. Before flash RUU 100% confirm about it. Otherwise you will lost your device. Anyway let's begin...
[WARNING: PLEASE DON'T TRY THIS WITHOUT HAVING GOOD ENOUGH KNOWLEDGE !! BE SURE TO CHOOSE THE RIGHT RUU OR THIS MAY HARM/BRICK YOUR DEVICE !! I AM NOT RESPONSIBLE FOR ANYTHING !!]
Before you start, you will need to set up your computer to properly recognize the device. You probably did this when rooting originally, but just in case... Install SDK tools for Android, Java runtime, and HTC Sync (only for USB drivers). Make sure that HTC Sync is not running in the background when this process is ongoing. To kill that you can use "Task Manager in Windows"
:cyclops: Do step by step: :cyclops:
1. Download the correct RUU for your device from Here and please 100% confirm you are downloading right RUU for your device. Make sure you download a Marvel_C RUU for a CDMA device (no sim card) or a Marvel RUU for a GSM device (uses a sim card)!! Also make sure you get the correct RUU for your carrier.
2. Charge the battery above 80%. If the battery dies during the flashing process, you could hard brick the phone!
3. Run the RUU until the wizard comes up (step 1). While the RUU wizard is open, don't do anything. Just find the temporary folder it created. (Open Explorer in Windows and type %temp% in the navigation bar.) There will be two folders with long encrypted names. In one of them you will find ROM.zip. Copy that and keep it on another location. Close the RUU wizard.
Now, open ROM.zip with 7zip and extract "System, Boot and recovery img's" [.img file/s]. Put it in the location were you've installed Android SDK tools.
4. Boot the phone into bootloader (power off, hold down volume and press power) and highlight FASTBOOT using the volume rocker and pressing power. Then connect the USB cable. You should see FASTBOOT USB.
5. Open a command prompt in Windows and navigate to the folder where you installed Android SDK tools.
Flash the stock recovery, boot, system img's using the following command/s:
step by step
For recovery
Code:
fastboot flash recovery recovery.img
For boot
Code:
fastboot flash boot boot.img
For system
Code:
fastboot flash system system.img
Now go back to device recovery and DO FACTORY RESET and reboot your device.
If everything done perfectly then the phone will booted normally on STOCK ROM! Remember Now bootloader is UNLOCKED but NOT rooted. Don't worry, you can root your device and also install CWM as before.
Hope this method will solve your issue.
Thank you very much testmasterbd =) , for this excellent description.
But..... i can`t start my phone into the bootloader. The phone turns on (only seeing the backlight) and suddenly it turns off (again the backlight). It does this ever and ever again until i pull out the battery . =(
how can i get into the bootloader? volume down and power doesn`t work anymore.
Maybe i can connect the phone to the pc, not via usb but via other contacts. Or is there another way to get the phone into fastboot mode?
Try this
Remove and reinsert the battery [don't press the power button of your device, that's means device should be turned off]
Plug it into a computer via USB cable
Wait and see if the computer detects it
If it does, then - Open a command prompt in Windows and navigate to the folder where you installed Android SDK tools.
Code:
adb devices
See if it shows up or not.
I am not sure about your device get hard brick.
---------- Post added at 10:30 PM ---------- Previous post was at 10:12 PM ----------
I forgot to ask one thing :silly:
Did your device vibrate when you pressed the power button for normal boot?
testmasterbd said:
Try this
Remove and reinsert the battery [don't press the power button of your device, that's means device should be turned off]
Plug it into a computer via USB cable
Wait and see if the computer detects it
If it does, then - Open a command prompt in Windows and navigate to the folder where you installed Android SDK tools.
Code:
adb devices
See if it shows up or not.
I am not sure about your device get hard brick.
---------- Post added at 10:30 PM ---------- Previous post was at 10:12 PM ----------
I forgot to ask one thing :silly:
Did your device vibrate when you pressed the power button for normal boot?
Click to expand...
Click to collapse
You are very friendly.
But i cannot power off the phone. It turns only off if i remove battery =)
When i plug in the usb cable while the phone is off, after some seconds, it turns on - shows its backgound light - and turns off and again on, like a turn signal. no vibration at all.
When i type in windows command adb devices it shows:
C:\android>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
but no device is listed =(
so it should be hard bricked!?
Damn it.
thanks a lot for your help and wasted time.
i am sorry
have a nice day
appyleptiker said:
You are very friendly.
But i cannot power off the phone. It turns only off if i remove battery =)
When i plug in the usb cable while the phone is off, after some seconds, it turns on - shows its backgound light - and turns off and again on, like a turn signal. no vibration at all.
When i type in windows command adb devices it shows:
C:\android>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
but no device is listed =(
so it should be hard bricked!?
Damn it.
thanks a lot for your help and wasted time.
i am sorry
have a nice day
Click to expand...
Click to collapse
If it is then, you need an expert who is capable for JTAG repairs. So find someone in your place. You can get an idea from HERE.
Good luck
testmasterbd said:
If it is then, you need an expert who is capable for JTAG repairs. So find someone in your place. You can get an idea from HERE.
Good luck
Click to expand...
Click to collapse
Yeah, thanks a lot.:good: Luck is what i need. But i don`t think that it will be too easy to repair. :silly:
appyleptiker said:
Yeah, thanks a lot.:good: Luck is what i need. But i don`t think that it will be too easy to repair. :silly:
Click to expand...
Click to collapse
It is don't be frustrated