Tuesday night, I was charging my phone and I left it alone for probably 30 minutes. I checked it, pressed the power button, and it didn't turn on! Today is day 3 of my phone not working. No, it is not rooted. My screen is cracked if that matters. It used to restart it a lot.
Yes, I've tried pulling the battery multiple times. Hard reset won't work either. I've tried volume down + power button, both volume buttons + power, even the camera button + power, charging with the computer, using different USB cords, and it still won't turn on. I took the battery and SD card out, waited 30 minutes.. put it back in, no luck.
Could it be a battery problem? Will a new battery fix it? Is it a hardware problem? If I need to replace it, could the Sprint store still retrieve my text messages and contacts? I hate not having a working phone and Christmas is coming up.
vannyyyyyy said:
Tuesday night, I was charging my phone and I left it alone for probably 30 minutes. I checked it, pressed the power button, and it didn't turn on! Today is day 3 of my phone not working. No, it is not rooted. My screen is cracked if that matters. It used to restart it a lot.
Yes, I've tried pulling the battery multiple times. Hard reset won't work either. I've tried volume down + power button, both volume buttons + power, even the camera button + power, charging with the computer, using different USB cords, and it still won't turn on. I took the battery and SD card out, waited 30 minutes.. put it back in, no luck.
Could it be a battery problem? Will a new battery fix it? Is it a hardware problem? If I need to replace it, could the Sprint store still retrieve my text messages and contacts? I hate not having a working phone and Christmas is coming up.
Click to expand...
Click to collapse
Happened to me too a while back. Had to take it in to a Sprint repair center and it turned out that my phone was fried somehow minutes after I put it on the charger. As long as you had your contacts backed up with your Google account you should be fine. Not sure about your texts.
Sent from my PG86100 using XDA App
i had the same problem.
Its a bug in the Recovery
simply reboot-bootloader with ADB and it will charge
HOW TO
you need The Android SDK on your computer
1.remove the battery
2.Put the battery back in your Evo 3d
3.Connect the phone with your computer
4.Start CMD
5. type "cd C:\Program Files (x86)\Android\android-sdk\platform-tools"
6.type "adb reboot-bootloader"
7.your phone should now charge just let it charge for a couple of minutes
8.restart your phone
sorry for my bad English
it won't recognize the commands
This happened to me.
1. take out battery
2. hold down the power button for 15sec with battery out.
3. place battery back in phone and put the back on.
4. try to turn on. If it doesn't turn on try a different charger (this worked for me a few times. this worke dfor me a few times i remember back on at&t when i had the slider windows phone htc 8250 i think it needed a charger with more amperage to start the charge.)
5. If the above doesn't work maybe take it in to sprint if you have the warranty.
nastystang05 said:
This happened to me.
1. take out battery
2. hold down the power button for 15sec with battery out.
3. place battery back in phone and put the back on.
4. try to turn on. If it doesn't turn on try a different charger (this worked for me a few times. this worke dfor me a few times i remember back on at&t when i had the slider windows phone htc 8250 i think it needed a charger with more amperage to start the charge.)
5. If the above doesn't work maybe take it in to sprint if you have the warranty.
Click to expand...
Click to collapse
I only wish I had seen this post before stressing all night! This worked perfectly and EASILY on what appeared to be a bricked phone!
Thank you soooooooooo much !!
Sent from my HTC EVO 3D, with ViperRom Redline v2.1.1
your way reli help..thx so much
...next time just press n hold the camera button then the power button too - should boot then
Sent from my HTC EVO 3D X515m using xda premium
pati5313 said:
i had the same problem.
Its a bug in the Recovery
simply reboot-bootloader with ADB and it will charge
HOW TO
you need The Android SDK on your computer
1.remove the battery
2.Put the battery back in your Evo 3d
3.Connect the phone with your computer
4.Start CMD
5. type "cd C:\Program Files (x86)\Android\android-sdk\platform-tools"
6.type "adb reboot-bootloader"
7.your phone should now charge just let it charge for a couple of minutes
8.restart your phone
sorry for my bad English
Click to expand...
Click to collapse
Why doesnt the cd C:\Program Files (x86)\Android\android-sdk\platform-tools work
vannyyyyyy said:
Tuesday night, I was charging my phone and I left it alone for probably 30 minutes. I checked it, pressed the power button, and it didn't turn on! Today is day 3 of my phone not working. No, it is not rooted. My screen is cracked if that matters. It used to restart it a lot.
Yes, I've tried pulling the battery multiple times. Hard reset won't work either. I've tried volume down + power button, both volume buttons + power, even the camera button + power, charging with the computer, using different USB cords, and it still won't turn on. I took the battery and SD card out, waited 30 minutes.. put it back in, no luck.
Could it be a battery problem? Will a new battery fix it? Is it a hardware problem? If I need to replace it, could the Sprint store still retrieve my text messages and contacts? I hate not having a working phone and Christmas is coming up.
Click to expand...
Click to collapse
your battery is completely discharged. find another battery or buy a docking external charger to charge your battery bro. Been throuhg the same thing
I had the same problem, left it plugged in for awhile. Then I held the camera button like j4n87 suggested and it booted. Don't know if the 3d switch position makes a difference. Thanks for your help guys.
This method actually worked!
nastystang05 said:
This happened to me.
1. take out battery
2. hold down the power button for 15sec with battery out.
3. place battery back in phone and put the back on.
4. try to turn on. If it doesn't turn on try a different charger (this worked for me a few times. this worke dfor me a few times i remember back on at&t when i had the slider windows phone htc 8250 i think it needed a charger with more amperage to start the charge.)
5. If the above doesn't work maybe take it in to sprint if you have the warranty.
Click to expand...
Click to collapse
Thank you so much!!
So, I am in my car getting ready to drive home and my phone won't turn on or even register the car charger. I had the phone in my pocket prior to that. I tried the three button trick, but nothing worked. I drove the whole way home dreading that I had bricked my phone. But thanks to XDA and all the help that is out there, I found a way to fix my problem.
I wish I could figure out exactly what caused the problem. My battery was at about 20-25%. My phone is rooted, hboot 1.4 running Android Revolution HD 1.1.3, and TWRP 1.1.1. I haven't flashed anything in a couple days, so is there any log I could look at to help figure out this mystery? Or is this something that just happens?
Thanks everyone!
When the blue moon decides to rise It happens to me as well.
"DU4L C0R3 SH00T3R"┌П┐[◣_◢]┌П┐
http://goo.gl/v6NqW iTz_r0cky!
I had a similar problem last week & had to sent it off to HTC UK for a warranty repair - a new mainboard!
Although to be fair to HTC, they did send a courier to my remote home to collect it and it was back within 2 working days.
Sent from my HTC EVO 3D X515m using XDA App
Grevers said:
Why doesnt the cd C:\Program Files (x86)\Android\android-sdk\platform-tools work
Click to expand...
Click to collapse
You need to install OpenJDK6+, the Android SDK, and the USB drivers for your phone since you're running Windblows. Do that, then open a command prompt window (type "cmd" in the Start menu search bar if you can't find it). Now if you're running a 32 bit OS, the "(x86)" part can be omitted from the command you're trying to use. The command "cd" means change directory, you cannot go to a directory (AKA folder, path, etc) that isn't there. The directory will be created for you when you install the SDK. Google is a helpful resource if you need further instruction .
Oh yeah, and don't forget to enable USB debugging from your phone otherwise ADB will not work. (It's located in: Settings>Applications>Development).
Sent from a Shooter running Android 4.0.3 via XDA Premium.
[/COLOR]
MikeyCriggz said:
You need to install OpenJDK6+, the Android SDK, and the USB drivers for your phone since you're running Windblows. Do that, then open a command prompt window (type "cmd" in the Start menu search bar if you can't find it). Now if you're running a 32 bit OS, the "(x86)" part can be omitted from the command you're trying to use. The command "cd" means change directory, you cannot go to a directory (AKA folder, path, etc) that isn't there. The directory will be created for you when you install the SDK. Google is a helpful resource if you need further instruction .
Oh yeah, and don't forget to enable USB debugging from your phone otherwise ADB will not work. (It's located in: Settings>Applications>Development).
Sent from a Shooter running Android 4.0.3 via XDA Premium.
Click to expand...
Click to collapse
got mine with sme problem. Bsttery went to 3.5V, phone do not loads.? LED slowly blinking.
I used your method, CMD wrote Daemon successfully started, phone rebooter into recovery, i reload bootloader again from recovery, but this did not helped/ en batery voltage ups to 3,6V, phone turns on, but do not charging anyway. No other tricks not helps.
Try this...
http://forum.xda-developers.com/showthread.php?t=1408374
edit:
Sry... was too late XD
Sent from my PG8630000 using XDA App
j4n87 said:
...next time just press n hold the camera button then the power button too - should boot then
Sent from my HTC EVO 3D X515m using xda premium
Click to expand...
Click to collapse
Had the same problem, nothing worked till i found this post!
Thanks
pati5313 said:
i had the same problem.
Its a bug in the Recovery
simply reboot-bootloader with ADB and it will charge
HOW TO
you need The Android SDK on your computer
1.remove the battery
2.Put the battery back in your Evo 3d
3.Connect the phone with your computer
4.Start CMD
5. type "cd C:\Program Files (x86)\Android\android-sdk\platform-tools"
6.type "adb reboot-bootloader"
7.your phone should now charge just let it charge for a couple of minutes
8.restart your phone
sorry for my bad English
Click to expand...
Click to collapse
thank you. worked for me...
thanks!!!
Hi all,
WOOOOW this just saved my life. thanks.!!!
Related
The market was acting a little flaky on my Evo3D, so I thought I'd reboot the phone. I recently flashed ViperROM RC 1.3, so now I get the option to "Hot Restart". Sure, why not I thought. So I choose the "Hot Restart" option. And my phone never came back on.
Tried every combination I could think of, pulled the battery, held the power button down for a minute, held volume down and the power button.. Nothing happens. No flickering of the screen, no lights, nothing.
If I plug it into AC, the charge light comes on red, stays red for a few seconds, turns green, then turns off. The battery was fully charged when I tried to reboot it.
If I plug it into a PC, and issue an "adb devices", I get the following:
D:\Downloads>adb devices
List of devices attached
HT16CHX00895 recovery
Recovery?!?
I can adb shell into the phone, and it looks like I have root (I get a "/ #" prompt).
I can push/pull from the phone.
I tried all combinations of adb reboot (with and without bootloader or recovery), and while it does reboot the phone (and the screen DOES flicker at this point), it just goes dark and again and appears to shut down (but adb devices still shows it as in recovery mode).
After about a minute, the phone appears to go to full sleep mode, and adb disconnects.
I've searched google and xda-developers, and can't find ANYTHING about this.
Anyone have ANY ideas???
Getting desperate here folks!
Scott
This happened to me as well. I dont really remember how I got phone to turn on but I did. Try pulling battery for longer duration. I do know that I pulled the battery. I will try and think more of what I did when it happened to me. So you cant get into the bootloader or recovery?
Sent from my PG86100 using XDA Premium App
adb reboot usually works for me when i get stuck during hot restart... pull the battery and wait 10-15 seconds then press the power button for like 3 seconds, put the battery back in and see if that helps
thesparky007 said:
adb reboot usually works for me when i get stuck during hot restart... pull the battery and wait 10-15 seconds then press the power button for like 3 seconds, put the battery back in and see if that helps
Click to expand...
Click to collapse
Thanks for your assistance.
I pulled the battery, let it sit for about 2 minutes, held the power button down for 15 seconds, put the batter back in, hit the power button again for 5 seconds. Nothing.
Scott
Sometimes you'll need to hold the power button down for more than ten seconds, with the battery in of course.
smark72 said:
This happened to me as well. I dont really remember how I got phone to turn on but I did. Try pulling battery for longer duration. I do know that I pulled the battery. I will try and think more of what I did when it happened to me. So you cant get into the bootloader or recovery?
Click to expand...
Click to collapse
I pulled the battery, let it sit for several minutes, put the battery back in, held down the volume down and the power button. Nothing
No, I can't get anything anything on the phone. Absolutely nothing happens when I hit the power button, no led's blink, the screen doesn't flicker, nothing.
ADB does appear to work. ADB REBOOT does make the phone reboot, and it does make the screen flicker, but then it just goes dead again.
Thanks for your help!
Scott
phatmanxxl said:
Sometimes you'll need to hold the power button down for more than ten seconds, with the battery in of course.
Click to expand...
Click to collapse
I just tried holding it down for about a minute.. Nothing
Thanks for your help,
Scott
Delvorak said:
I pulled the battery, let it sit for several minutes, put the battery back in, held down the volume down and the power button. Nothing
No, I can't get anything anything on the phone. Absolutely nothing happens when I hit the power button, no led's blink, the screen doesn't flicker, nothing.
ADB does appear to work. ADB REBOOT does make the phone reboot, and it does make the screen flicker, but then it just goes dead again.
Thanks for your help!
Scott
Click to expand...
Click to collapse
Try what the other poster said. When I read it I kind of remember holding the power button in for a little once I replaced the battery after the pull. I recall holding the power button for more than 5 sec, letting go then hit power again and it finally came on. If that doesnt work maybe you can pm the dev from viperrom and ask for help.
Sent from my PG86100 using XDA Premium App
There was a thing where some people needed to pull their sdcard for some reason.... Once powered up without it you could shut down and restart and put it back and we're all good.... I needed to once, though the charge light never came on for me... Worth a shot
Sent from my PG86100 using XDA App
I have never used ADB before but could you push a PG86100 update zip if there was one on your sd card or does that have to be done through the bootloader?
Sent from my PG86100 using XDA Premium App
daneurysm said:
There was a thing where some people needed to pull their sdcard for some reason.... Once powered up without it you could shut down and restart and put it back and we're all good.... I needed to once, though the charge light never came on for me... Worth a shot
Click to expand...
Click to collapse
Progress! Removing the sd card makes the
adb reboot bootloader
command work, so I can get into the bootloader now... but , if I select reboot, it goes back to doing the same thing.... and I select bootloader, and then recovery, it does the same thing.
Trying a bunch of other stuff, nothing's panning out yet.
Any ideas now that I can get into bootloader?
Thanks!
Scott
Delvorak said:
Progress! Removing the sd card makes the
adb reboot bootloader
command work, so I can get into the bootloader now... but , if I select reboot, it goes back to doing the same thing.... and I select bootloader, and then recovery, it does the same thing.
Trying a bunch of other stuff, nothing's panning out yet.
Any ideas now that I can get into bootloader?
Thanks!
Scott
Click to expand...
Click to collapse
can you read anything on your sd card when you plug in the usb? I would guess not if you cant see the screen to choose storage instead of charge only. Sounds like somehow flashing a stock update.zip would get you going again, I just wouldnt know how to do it. Can you put your sd card in an adapter for pc to get the PG86100 image on it then place it back into your phone and run it from bootloader?
Sent from my PG86100 using XDA Premium App
do a battery pull and hold down the power for 10 seconds with the battery out, put the battery back in and hold volume up and press and hold power until it turns on
if that doesnt work, flash a new recovery through adb and see if it boots up
Delvorak said:
Progress! Removing the sd card makes the
adb reboot bootloader
command work, so I can get into the bootloader now... but , if I select reboot, it goes back to doing the same thing.... and I select bootloader, and then recovery, it does the same thing.
Trying a bunch of other stuff, nothing's panning out yet.
Any ideas now that I can get into bootloader?
Thanks!
Scott
Click to expand...
Click to collapse
So, hboot works, adb works...does fastboot work?
Either way, I'd flash a recovery and a rom....I was also thinking maybe refresh hboot, but, if you are getting to the bootloader I don't think it's corrupted, but, maybe the other parts are....
I'd start with recovery and a rom...if no luck there flash another hboot on top. I'm a big fan of the eng hboot.
Problem solved!
It was the battery, somehow. When I got home from work, I swapped out the chinese knockoff battery with the original stock battery, hit the power button, and it started right up. Swapped out for the same knockoff battery, and it won't start again. WTF?
Anyway, thanks everyone for your suggestions, I appreciate it!
Scott
Delvorak said:
Problem solved!
It was the battery, somehow. When I got home from work, I swapped out the chinese knockoff battery with the original stock battery, hit the power button, and it started right up. Swapped out for the same knockoff battery, and it won't start again. WTF?
Anyway, thanks everyone for your suggestions, I appreciate it!
Scott
Click to expand...
Click to collapse
when the battery gets depleted completely you need to charge it a while for it to be able to start up again may be thats what happened...
so i followed the instructions to unroot my evo 3d...went back to stock sprint rom and when i did the fastboot and adb i chose to reboot and now my phone won't turn on. did a search i can't find any resolve to this problem. ive tried to take the battery out...boot into recovery...even when i plug in my phone the led light doesn't come on anymore...battery is fully charged too...any ideas?? help me please
poktangju said:
so i followed the instructions to reroot my evo 3d...went back to stock sprint rom and when i did the fastboot and adb i chose to reboot and now my phone won't turn on. did a search i can't find any resolve to this problem. ive tried to take the battery out...boot into recovery...even when i plug in my phone the led light doesn't come on anymore...battery is fully charged too...any ideas?? help me please
Click to expand...
Click to collapse
Try pulling out the battery and putting it back in, then plugging the phone in and rebooting it.
tried your suggestion and still won't power on...led light doesn't even come on when plugged in to charger...
VladBelsky said:
Try pulling out the battery and putting it back in, then plugging the phone in and rebooting it.
Click to expand...
Click to collapse
See if this helps http://forum.xda-developers.com/showthread.php?t=1281729
thanks...looks like my phone is d u n...dun
VladBelsky said:
See if this helps http://forum.xda-developers.com/showthread.php?t=1281729
Click to expand...
Click to collapse
This is a complete guess/longshot but take out the battery, plug in the charger and hold down the power button. While the power button still held, unplug the power cord from the phone and insert the battery. This once worked to get my old Xperia X10 to respond. Different phone, but thought it might be worth a try.
thanks for trying to help but no dice...
spywhite said:
This is a complete guess/longshot but take out the battery, plug in the charger and hold down the power button. While the power button still held, unplug the power cord from the phone and insert the battery. This once worked to get my old Xperia X10 to respond. Different phone, but thought it might be worth a try.
Click to expand...
Click to collapse
Have you tried adb reboot recovery? If by some miracle adb sees the phone you can just flash a recovery and load up a rom. Might have to try acting like you power it on. It could be actually powered up but not screen or led responsive.
3VO Sent
I've had a problem like this with my phone before, I let my battery get to zero while in recovery mode and phone wouldnt do anything. The battery seemed like it was so low the phone didn't recognise it was there. I hooked it up to a variable dc voltage box and jumped it for a bit and it worked. U could either stop at a sprint store and see if they have a charged battery, or get one of those things that charges the battery outside of the phone, its like a universal battery charger or somethin.
Sent from my PG86100 using xda premium
sorry for my ignorance but how to i go about doing the adb reboot recovery?
ifly4vamerica said:
Have you tried adb reboot recovery? If by some miracle adb sees the phone you can just flash a recovery and load up a rom. Might have to try acting like you power it on. It could be actually powered up but not screen or led responsive.
3VO Sent
Click to expand...
Click to collapse
i do have a wall charger that charges the battery outside the phone and i was really hoping that it was due to low battery but even with a fully charged battery still won't power on. thx tho
troublein420 said:
I've had a problem like this with my phone before, I let my battery get to zero while in recovery mode and phone wouldnt do anything. The battery seemed like it was so low the phone didn't recognise it was there. I hooked it up to a variable dc voltage box and jumped it for a bit and it worked. U could either stop at a sprint store and see if they have a charged battery, or get one of those things that charges the battery outside of the phone, its like a universal battery charger or somethin.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Have you tried another battery ?
Sent from my HTC EVO 3D X515a using XDA App
Are you using an old version of twrp?
sent from my EVO 3D via XDA app
i had twrp 1.0 before the phone bricked...
z50king said:
Are you using an old version of twrp?
sent from my EVO 3D via XDA app
Click to expand...
Click to collapse
Twrp 1.xxx would think the phone was in recovery after the battery died. It made it so you needed to pull the battery for a while to let the capacitor drain and reset twrp
sent from my EVO 3D via XDA app
Download ADB from http://developer.android.com/sdk/index.html
Download the zip
unzip somewhere
Open SDK manager
Download sdk platform-tools and tools (other stuff is optional)
open cmd and use "cd <directory>" to navigate to platform-tools in the android sdk folder (e.g. "cd /android-sdk-windows/platform-tools/"
Download htc sync http://dl3.htc.com/application/HTCSyncv3.0.5579.exe
uninstall after installed
connect phone to computer
type "adb devices" in a cmd/terminal
if it recognizes your device, it's not bricked
try "adb reboot bootloader" and see if it gets into bootloader. If it does, flash TWRP 2.0 and flash a ROM. Your device should now be usable.
If that doesn't work, you could probably download the bootloader file and push it to your phone but you'll have to ask someone else about that.
What is TWRP?
Sent from my HTC EVO 3D X515m using Tapatalk
Castellano2 said:
What is TWRP?
Sent from my HTC EVO 3D X515m using Tapatalk
Click to expand...
Click to collapse
Team Win Recovery Project
http://teamw.in/project/twrp2
Got it fixed, turns out my charging hole for the phone was loose and it couldn't charge.
Yesterday around 11pm my HTC Rezound completely ran out of battery. Then this morning I was charging it for like 7 hours, but the phone will not turn on at all, not even the orange light shows. I have tried holding VOL down and POWER but nothing happens. When I keep clicking the POWER button, the orange lights comes on for like 3 seconds, and then i goes out. Please help me fix this, thanks
MY PHONE IS ROOTED AND UNLOCKED!! JUST SAYING
izink said:
Yesterday around 11pm my HTC Rezound completely ran out of battery. Then this morning I was charging it for like 7 hours, but the phone will not turn on at all, not even the orange light shows. I have tried holding VOL down and POWER but nothing happens. When I keep clicking the POWER button, the orange lights comes on for like 3 seconds, and then i goes out. Please help me fix this, thanks
MY PHONE IS ROOTED AND UNLOCKED!! JUST SAYING
Click to expand...
Click to collapse
try a different battery. it sometimes happen the battery get way to low and it does now want to charge.
If you have CWM as your recovery, that's the problem. Get some juice in your battery some other way, and flash Amon Ra.
twolasrnames said:
If you have CWM as your recovery, that's the problem. Get some juice in your battery some other way, and flash Amon Ra.
Click to expand...
Click to collapse
I already flashed Amon Ra on my phone like 3 weeks ago. What should I do from there??
izink said:
I already flashed Amon Ra on my phone like 3 weeks ago. What should I do from there??
Click to expand...
Click to collapse
Find someone with a rezound(verizon store maybe?). Try there charged battery. Boots your good if not your phone is fubar. Work forward from there.
Sent from my ADR6425LVW using XDA
Don't know if you found a remedy yet, but the same happened to me yesterday. Ended up being the battery. I brought it to Verizon and they replaced it.
Sent from my ADR6425LVW using XDA
i had this same problem look you going to need to to on a pc and use cmd
to fix this battery death ....once you have your cmd open type in adb reboot
then wait a bit it will turn on then give it a bit for it to charge then go back to cmd and type adb reboot bootloader and let it charge then reboot you phone normaly as it should do
Thanks.
cflo360 said:
i had this same problem look you going to need to to on a pc and use cmd
to fix this battery death ....once you have your cmd open type in adb reboot
then wait a bit it will turn on then give it a bit for it to charge then go back to cmd and type adb reboot bootloader and let it charge then reboot you phone normaly as it should do
Click to expand...
Click to collapse
This actually worked. But a better look for telling people is:
I had the same problem. To fix it it:
Plug the phone into the computer, and load up command prompt.
Type in "cd [directory of adb.exe]"
Type "adb reboot"
It should say "daemon not running. Starting it on port XXXX"
Then "daemon started successfully. After less than a minute, your phone will turn on.
Leave it there to charge for a little while, then, type:
"adb reboot bootloader". From there, let it charge.
After it has charged, reboot your phone as you normally would.
The only part of these instructions I couldn't get to was getting the phone to reboot properly.
This has worked for me so far, and it was pissing me off the whole day that it wouldn't charge.
For what it's worth, I bought a bricked phone from Craigslist and just keeping the battery out of it for 48 hours fixed it. Otherwise the phone was completely dead (No nothing, no charging, LED, ADB, NOTHING)
So if you have a bricked phone, you may want to try this too.
GoghAndroid said:
For what it's worth, I bought a bricked phone from Craigslist and just keeping the battery out of it for 48 hours fixed it. Otherwise the phone was completely dead (No nothing, no charging, LED, ADB, NOTHING)
So if you have a bricked phone, you may want to try this too.
Click to expand...
Click to collapse
OMG... I left my battery out for 12 hours... now I have to do it for 48 hours??? Is that extra time going to make a difference? All the things that work for other people don't work for me and it makes me very, very sad.
My Rezound was running TWRP and CM10.1. It had an extended battery in it. I ran the battery down and it wouldn't charge, so I put the original battery back in. It was okay for a couple weeks until I let that run down and it wouldn't charge. I ordered a Kidigi dock with external battery charger and the Rezound sat in a drawer with no battery for a week while I waited for the dock to arrive from Hong Kong. The dock came in yesterday. I charged the original battery in it, then put it into the Rezound and...nothing. I can't get the LED to light or anything. I connected the Rezound to my PC and ran ADB DEVICES, but my PC finds no devices. I've got a Mugen extended battery coming in the mail. I'll give that a try, and I'll also drop into a Verizon store and see if they have a charged battery I can try in my Rezound, but I've pretty much run out of hope for this phone.
After a little discussion in the Development section, we decided to offer a fix for those who continue to use ROM Manager and Clockwork Mod Recovery. Some of you started using CWM as default choice, not knowing the issues, and others of you simply prefer CWM.
Be warned! Neither I nor any others credited in this post are responsible for you breaking your phone! You do this at your own risk! This is given as a basic tutorial, but assumes some working knowledge of Windows and command line
The reason your battery does not appear to charge is that you are using CWM, which puts the Rezound in a recovery state (screen off) when the battery is run down too far. The recovery's kernel does not activate the LED while charging. CWM recovery also does not recognize use of the power button. Please see more about this below, in punman's replies to this post.
NilsP has posted a fixed recovery.img based on CWM Touch. This is essentially a kang of Koush's work, but the only change is the battery fix. Nils has tested the fix for a few months and feels confident that it works properly. Neither he nor I take any credit for this. The fix was provided punman (many thanks to you), who is willing to field support questions, as noted below in his responses, and know far more about the recovery than I do. If you use the "fixed" CWM recovery found here for download, please give him your thanks.
EDIT: The "fixed" CWM Touch works in two ways:
1. - If you replace your current battery with a charged one.
or
2. - If you leave your Rezound charging for a few minutes, then use the command "adb reboot."
The following steps should bring your rezound back and are based on djh816's guide for "Debricking your Rezound" here http://forum.xda-developers.com/showthread.php?t=1711408. Thanks to djh816 for his work on this.
What do you need?
1. A Windows 7 PC
2. Fastboot and ADB installed (you do not have to install the Android SDK, unless you want to). Links to these two programs are common in the development section and throughout xda.
3. Patience
Start up your PC and place a copy of the file I have attached into the directory where you have placed ADB and Fastboot on your PC. Rename this file "recovery." If you have deselected "Hide extensions for known file types" in your advanced folder viewing settings, confirm that the file is named "recovery.img"
Plug in your Rezound and confirm you receive a USB connection sound. If you don't get the connect sound, install HTC Sync and try connecting again. Make sure you select "Charge only" on your Rezound
With Windows 7, search in the Start menu for "cmd" and right click on the cmd program selecting "Run as administrator" - click "Yes" or enter your admin credentials in the UAC dialog box.
In the command line window, type "cd" and the path to the ADB/Fastboot directory.
ex.: "cd C:\Users\WookieFan\Desktop\ADB" (excluding quotations)
Type the following exactly (excluding quotations):
"adb devices"
If the list of devices is blank, unplug your Rezound and plug it back in to confirm you hear the USB connect sound.
If you have a device listed, type the following (as always, no quotation marks):
"adb reboot recovery"
If you have not had your phone plugged in for ten minutes or more at this point, this command may do nothing. After a few minutes, your Rezound will have trickle charged enough to reboot into CWM, so keep trying every few minutes.
Once you've successfully booted into a normal recovery state, leave the phone charging on your PC for an additional 15 minutes. There is some debate whether or not the Rezound charges in CWM recovery. It has done so for me, even though the charging indicator light does not come on.
Now type:
"adb reboot"
Your phone will now be charged around 10% and should reboot normally. You can charge it up using a regular outlet at your convenience. If you are unable to reboot your phone normally, wait a few minutes more and try again.
To avoid this problem in the future, flash Amon Ra or TWRP recoveries via Hasoon's All-In-One Toolkit v2.x found here:
http://forum.xda-developers.com/showthread.php?t=1504824
Or, if you prefer to continue using CWM, take a deep breath and try the following:
With your phone connected to your PC via USB, type the following into your command line window:
"adb devices"
and confirm your device is listed. Then type:
"adb reboot bootloader"
After a short wait, your phone will reboot to the bootloader (HBOOT) and you will see the familiar white screen with skateboarding androids. "Fastboot" should be highlit at this time.
Now type:
"fastboot flash recovery recovery.img"
You will receive a confirmation that the flash went through successfully and you will now have a fixed version of CWM Touch recovery installed. Now type:
"fasboot reboot"
This will bring you back to a normally operating Rezound. But wait! there's one more step.
Before you take this next step, I would also suggest that you go into ROM Manager settings and confirm that "Quick Backup and Restore" is checked and "Use External Storage" is checked.
Using the root explorer of your choice, navigate to the clockworkmod directory. The full path will be something like this:
/%root%/mnt/sdcard/ext_sd/clockworkmod/
Create a file in this folder named ".hideandroidprogress" - this is a hidden file, so once you've created it correctly, you may not see it in the directory.
At this point ROM manager and CWM will work primarily as you would expect. I have heard that there are issues flashing ROMs or recovering backups from internal storage, but I did not test this, since I feel it is best to keep backups on your external storage and to flash ROMs and backups from there as well.
As always, be careful, ask questions and read through the instructions. Good luck!
Thanks for the post. However, I would still recommend users stick with Amon Ra or TWRP.
I agree - Amon Ra is presented as the preferred choice. I'll provide a link to the Amon Ra and TWRP recovery pages in the OP.
Battery fix version doesn't work for me. If I plug the phone while off the led will come on like before then goes off shortly after. Then the phone won't boot without pulling the battery. I know you were just reposting the file for Nils but I thought I should let others know.
zhp pilot said:
Battery fix version doesn't work for me. If I plug the phone while off the led will come on like before then goes off shortly after. Then the phone won't boot without pulling the battery. I know you were just reposting the file for Nils but I thought I should let others know.
Click to expand...
Click to collapse
Ok, I've tested replacement of the dead battery with a charged one with no issues. Testing with charging a discharged battery later tonight, but with "regular" CWM, replacement with a charged battery didn't help.
I'll confirm results later.
Sent from my ADR6425LVW using Tapatalk 2
WookieFan said:
Ok, I've tested replacement of the dead battery with a charged one with no issues. Testing with charging a discharged battery later tonight, but with "regular" CWM, replacement with a charged battery didn't help.
I'll confirm results later.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Cool. I will try it again just in case. My battery was at like 40% or so when I powered it down. Honestly, I have so many batteries that there's always one with something on it laying around. But it would be nice to have a working version in that rare rare event it dies and I'm away from home and forgot a spare.
zhp pilot said:
Cool. I will try it again just in case. My battery was at like 40% or so when I powered it down. Honestly, I have so many batteries that there's always one with something on it laying around. But it would be nice to have a working version in that rare rare event it dies and I'm away from home and forgot a spare.
Click to expand...
Click to collapse
I can confirm - if you are using the USB cable to charge your battery inside your Rezound after a full discharge (or down to 8% or so), it appears at first that nothing has changed - you will still go into the screen-off recovery but your phone will continue to charge normally - you can either replace the discharged battery with a charged one, or wait roughly ten minutes (while charging through a power outlet, not a PC) and then remove the battery and replace it. Your Rezound should charge normally after this and you should be able to turn it on.
I will note the OP, accordingly.
zhp pilot said:
Battery fix version doesn't work for me. If I plug the phone while off the led will come on like before then goes off shortly after. Then the phone won't boot without pulling the battery. I know you were just reposting the file for Nils but I thought I should let others know.
Click to expand...
Click to collapse
Ignore the charging led, the kernel in Koush's recovery image doesn't know how to turn it on. What you're seeing is the Rezound firmware turning on the charging led while it's doing power-up stuff, but once control is transferred to the recovery kernel the light will go off, but it's still charging. CWR also doesn't know anything about the keycode for the power button in the screen-off recovery mode.
Plug your phone in for a few minutes and do an "adb reboot" instead of hitting the power button. This should get you enough charge (if you're using the image posted here) to boot into Android proper, which has all the right software.
When you plug a Rezound in with a dead battery, the phone detects USB power and no battery charge and then boots a mini-recovery image with some special flags that tell the kernel not to display anything and just charge the battery. Problem here is that Koush's CWR image isn't set up to run in this special recovery mode, but Amon Ra's is.
Even with the "fix" to get your phone to charge in recovery, the power button won't work, so when you all keep trying to "power on" your phone after unplugging it, what's really happening is that it's ignoring you completely, and very slowly draining your battery more while still running in recovery. That's why there has been some success reported with pulling the battery at this point, but if you wait too long or your battery hasn't charged enough, you still won't have enough juice to boot.
[Advanced users: you can run a dmesg in the mini-recovery and watch the BATT lines to see what level it's at before doing a reboot, 10% should be enough to get you booted.]
I'm the "anonymous" fixer, btw. Not so anonymous any more, but I figured if this is posted, I might as well chime in.
Good luck.
punman said:
Ignore the charging led, the kernel in Koush's recovery image doesn't know how to turn it on. What you're seeing is the Rezound firmware turning on the charging led while it's doing power-up stuff, but once control is transferred to the recovery kernel the light will go off, but it's still charging. CWR also doesn't know anything about the keycode for the power button in the screen-off recovery mode.
Plug your phone in for a few minutes and do an "adb reboot" instead of hitting the power button. This should get you enough charge (if you're using the image posted here) to boot into Android proper, which has all the right software.
When you plug a Rezound in with a dead battery, the phone detects USB power and no battery charge and then boots a mini-recovery image with some special flags that tell the kernel not to display anything and just charge the battery. Problem here is that Koush's CWR image isn't set up to run in this special recovery mode, but Amon Ra's is.
Even with the "fix" to get your phone to charge in recovery, the power button won't work, so when you all keep trying to "power on" your phone after unplugging it, what's really happening is that it's ignoring you completely, and very slowly draining your battery more while still running in recovery. That's why there has been some success reported with pulling the battery at this point, but if you wait too long or your battery hasn't charged enough, you still won't have enough juice to boot.
[Advanced users: you can run a dmesg in the mini-recovery and watch the BATT lines to see what level it's at before doing a reboot, 10% should be enough to get you booted.]
I'm the "anonymous" fixer, btw. Not so anonymous any more, but I figured if this is posted, I might as well chime in.
Good luck.
Click to expand...
Click to collapse
Thanks for clarifying for everyone.
punman said:
........
I'm the "anonymous" fixer, btw. Not so anonymous any more, but I figured if this is posted, I might as well chime in.
Good luck.
Click to expand...
Click to collapse
Thanks for chiming in. I didn't want to volunteer you, so we did not have to support it, but thought it was worth posting originally.
NilsP said:
Thanks for chiming in. I didn't want to volunteer you, so we did not have to support it, but thought it was worth posting originally.
Click to expand...
Click to collapse
I think if it's useful and has been stable for a few months (on my phone too) it's probably ok at this point. I'm certainly willing to try to answer questions if people are having problems.
Hey guys - made a few changes to reflect this discussion. Let me know if you feel I got it wrong, and many thanks to punman for his work and input here.
Still need help with this PLEASE!
Hey guys,
I know this thread hasn't been used in almost a year and a half, but I would love it someone could help me out with this issue!
My Rezound with CWM won't power up so I believe this thread describes my problem. I've tried the instructions given here for a few days now and I can't get it to work.
When I plug my phone into the computer I hear the "plugged in" sound. However, after typing "adb devices", no devices are listed. I've unplugged, replugged, tried reinstalling drivers, google usb drivers, htc sync drivers, and nothing seems to help my phone being recognized by adb.
Oddly, when my phone is plugged in, two drives show up in My Computer just as they had when this phone used to work. However, those two drives are greyed out and unclickable (when clicked, it says "please insert media into drive..").
Can anyone help me with getting adb to recognize the phone so I can fix it and retrieve all my data on the internal storage?!
Thank you!
Alex
puckgenius said:
Hey guys,
I know this thread hasn't been used in almost a year and a half, but I would love it someone could help me out with this issue!
My Rezound with CWM won't power up so I believe this thread describes my problem. I've tried the instructions given here for a few days now and I can't get it to work.
When I plug my phone into the computer I hear the "plugged in" sound. However, after typing "adb devices", no devices are listed. I've unplugged, replugged, tried reinstalling drivers, google usb drivers, htc sync drivers, and nothing seems to help my phone being recognized by adb.
Oddly, when my phone is plugged in, two drives show up in My Computer just as they had when this phone used to work. However, those two drives are greyed out and unclickable (when clicked, it says "please insert media into drive..").
Can anyone help me with getting adb to recognize the phone so I can fix it and retrieve all my data on the internal storage?!
Thank you!
Alex
Click to expand...
Click to collapse
Alex,
You'll have to help out by being more specific. I am sorry that I have not had a chance to respond sooner, but I was away traveling when you wrote your question.
Where do my instructions break down? You say that the drives show up in your "My Computer" directory, but you cannot open them. Do they appear to have the blue colored USB drive icons when they appear in My Computer, or are they a grey/white color? If grey/white, then they are not being recognized as drives (they are not mounting properly), which probably means you never installed the Rezound drivers from HTC.
Either way, there should be a fairly simple solution. Remove your battery and charge it with an external charger or try a new, charged battery. If the Rezound hasn't had a battery in it for more than a few hours, a charged battery should work normally.
If you don't want to go through the trouble of getting an external battery charger or extra battery, then make sure to charge the battery for about two hours on the wall charger and then try connecting the Rezound to your PC.
Make sure to install the Rezound drivers from HTC on your PC - they will be part of a HTC Sync download/installation. Uninstall HTC Sync, and the drivers will remain on your PC.
Make sure you've installed ADB & Fastboot (instructions for this found all over xda) before trying the ADB commands. If you don't have those files on your drive, my process won't work for you. Also, I would highly recommend using another recovery - Amon Ra or TWRP - whichever one is most highly recommended by the good folks here now - I have since moved on to a One X, so haven't been following the Rezound threads at all.
We can also do a G+ hangout if you like and I can walk you through some of this, but I won't be able to do that tonight.
Good luck, either way. And i hope I have helped.
WookieFan said:
Alex,
You'll have to help out by being more specific. I am sorry that I have not had a chance to respond sooner, but I was away traveling when you wrote your question.
Where do my instructions break down? You say that the drives show up in your "My Computer" directory, but you cannot open them. Do they appear to have the blue colored USB drive icons when they appear in My Computer, or are they a grey/white color? If grey/white, then they are not being recognized as drives (they are not mounting properly), which probably means you never installed the Rezound drivers from HTC.
Either way, there should be a fairly simple solution. Remove your battery and charge it with an external charger or try a new, charged battery. If the Rezound hasn't had a battery in it for more than a few hours, a charged battery should work normally.
If you don't want to go through the trouble of getting an external battery charger or extra battery, then make sure to charge the battery for about two hours on the wall charger and then try connecting the Rezound to your PC.
Make sure to install the Rezound drivers from HTC on your PC - they will be part of a HTC Sync download/installation. Uninstall HTC Sync, and the drivers will remain on your PC.
Make sure you've installed ADB & Fastboot (instructions for this found all over xda) before trying the ADB commands. If you don't have those files on your drive, my process won't work for you. Also, I would highly recommend using another recovery - Amon Ra or TWRP - whichever one is most highly recommended by the good folks here now - I have since moved on to a One X, so haven't been following the Rezound threads at all.
We can also do a G+ hangout if you like and I can walk you through some of this, but I won't be able to do that tonight.
Good luck, either way. And i hope I have helped.
Click to expand...
Click to collapse
Thank you so much for getting back to me.
I've included a screenshot of what's going on and where I'm held up.
I reinstalled HTC sync 3.3.63 and the drivers installed.
I plug the phone in, hear the plug in sound, the orange LED turns on for about 10 seconds then turns off, and then the devices listed in my device manager show up: HTC Android Phone under disk drives, Portable Devices now show E: and G:, and USB controllers now show USB Mass Storage Device. Nothing shows up anywhere about "Adb Device" or anything like that, which I'm pretty sure I've read is supposed to show up in Device Manager
My Computer then shows the two Removable Disk drives E and G, but they are greyed out.
Again, these devices only show up when I actually plug the phone in.
In the command prompt, daemon opens up but is unable to detect any devices.
I'm actually using a battery that I bought online last week. The same exact sequence of events happened when I first put the battery in several days ago.
You mentioned I need the ADB and Fastboot files on my drive. They are installed on my computer through the SDK manager, but I only did that recently ie: after my phone bricked. Was there something I had to do to my phone before it bricked for it to be recognized by the Adb software?
Thank you so much for your help!
puckgenius - I will get back to you tonight, but a quick answer to your last question is yes - ADB also has to be enabled on the phone, although many cooked ROMs have this set by default. Also, "fast boot" should be disabled in the phone. This is not the same as Fastboot which is a bootloader function. Confused yet? More to come.
Sent from my HTC One X using Tapatalk
I actually had this issue for almost a year with no idea how to fix it. So I simply took it apart and put it back together. That did the trick after praying to God. XD Haha. I immediately changed the recovery, ROM, and other things.
Josh8550 said:
I actually had this issue for almost a year with no idea how to fix it. So I simply took it apart and put it back together. That did the trick after praying to God. XD Haha. I immediately changed the recovery, ROM, and other things.
Click to expand...
Click to collapse
What do you mean you took it apart? What specifically did you take apart and then put back together?
Thank you so much for the help!
This probably isn't helpful because I'm guessing you've tried this but when I had this problem, I charged it overnight, pulled the battery, put it back in and the phone worked.
puckgenius said:
What do you mean you took it apart? What specifically did you take apart and then put back together?
Thank you so much for the help!
Click to expand...
Click to collapse
I took the whole thing apart. I just started removing whatever I could with a screwdriver, prying the back pieces off until I reached where the screen, digitizer, etc connect to the motherboard. I didn't want to mess with the hassle of fiddling with the ribbons so I stopped, put it back together, plugged it up for a while, and it booted up when I pressed the power button.
Putting the battery in an HTC Thunderbolt, another Rezound, or a charger might be necessary to charge it up enough to actually boot however. I used my sister's Thunderbolt to charge the battery.
Hello everyone, I am having a strange problem with my HTC Droid DNA. I searched around and cannot find this problem anywhere else. Last night I noticed my phone was off and figured it had lost all charge so I plugged it in to charge, left it there for a few minutes and turned it on again. When I turned it on, it displayed the white htc boot screen, then turned off again and rebooted again to the white htc screen (this goes on and on). The strange thing is that this happens only when connected to the wall power outlet. When I connect it to my PC it powers on and works fine until I disconnect it (it turns off again when I do that). The other problem I notice is that even when the phone is on and connected to the PC, it does not reproduce any sound at all (no ringtone, music, does not play videos, etc..). Also, my phone is STOCK and has never had any mods on it at all. It has android 4.1.1, software version 2.04.605.271ORD, KERNEL 3.4.10-GA02D2C6 [email protected] #1 SMP PREEMPT, BASEBAND 1.01.01.01 10
Has anyone ever had this problem or know how to fix this? I would be forever grateful if you guys could help me with this...
majincamz said:
Hello everyone, I am having a strange problem with my HTC Droid DNA. I searched around and cannot find this problem anywhere else. Last night I noticed my phone was off and figured it had lost all charge so I plugged it in to charge, left it there for a few minutes and turned it on again. When I turned it on, it displayed the white htc boot screen, then turned off again and rebooted again to the white htc screen (this goes on and on). The strange thing is that this happens only when connected to the wall power outlet. When I connect it to my PC it powers on and works fine until I disconnect it (it turns off again when I do that). The other problem I notice is that even when the phone is on and connected to the PC, it does not reproduce any sound at all (no ringtone, music, does not play videos, etc..). Also, my phone is STOCK and has never had any mods on it at all. It has android 4.1.1, software version 2.04.605.271ORD, KERNEL 3.4.10-GA02D2C6 [email protected] #1 SMP PREEMPT, BASEBAND 1.01.01.01 10
Has anyone ever had this problem or know how to fix this? I would be forever grateful if you guys could help me with this...
Click to expand...
Click to collapse
Troubleshooting the Phone : I Understand that you are not Rooted, locked, and s-on .
1- Call vzw tech support and ask for a replacement. But Do first before call VZW a Reset Phone*. ( setting>back up & Reset>reset phone )
2- are you with Verizon Wireless, if so you should be notified for a new OTA Update available (you are outdated with software 2.04 )
however it should not prevent the phone to run well.
3- Are you using the original usb cable when connect the phone to the power wall outlet ( have you check the outlet power supply if it is good)
4- are you able to charge your phone on your Computer through usb cable. (try different USB port)
majincamz said:
Hello everyone, I am having a strange problem with my HTC Droid DNA. I searched around and cannot find this problem anywhere else. Last night I noticed my phone was off and figured it had lost all charge so I plugged it in to charge, left it there for a few minutes and turned it on again. When I turned it on, it displayed the white htc boot screen, then turned off again and rebooted again to the white htc screen (this goes on and on). The strange thing is that this happens only when connected to the wall power outlet. When I connect it to my PC it powers on and works fine until I disconnect it (it turns off again when I do that). The other problem I notice is that even when the phone is on and connected to the PC, it does not reproduce any sound at all (no ringtone, music, does not play videos, etc..). Also, my phone is STOCK and has never had any mods on it at all. It has android 4.1.1, software version 2.04.605.271ORD, KERNEL 3.4.10-GA02D2C6 [email protected] #1 SMP PREEMPT, BASEBAND 1.01.01.01 10
Has anyone ever had this problem or know how to fix this? I would be forever grateful if you guys could help me with this...
Click to expand...
Click to collapse
You could always try this:
adb reboot bootloader > bootloader> factory reset
That might clear anything that messed up. seeing as youve never done anything to it, it just might work.
jake.corey.jacobs said:
You could always try this:
adb reboot bootloader > bootloader> factory reset
That might clear anything that messed up. seeing as youve never done anything to it, it just might work.
Click to expand...
Click to collapse
Yeap! but the guy is a new member, first post, he never touch, root or mod his dna so he will need likely with your suggestion the proper adb installation guidance to start using adb. so thought browser to him his phone is more appropriate and easy when the results are the same when you are DNA Stock.
= setting=back up & reset>Reset phone . profit:cyclops:
finanandroid said:
Yeap! but the guy is a new member, first post, he never touch, root or mod his dna so he will need likely with your suggestion the proper adb installation guidance to start using adb. so thought browser to him his phone is more appropriate and easy when the results are the same when you are DNA Stock.
= setting=back up & reset>Reset phone . profit:cyclops:
Click to expand...
Click to collapse
I sent him a pm with a link to the minimal adb and fastboot and told him id help him do whatever, but I don't know his knowledge level about android to begin with so.
jake.corey.jacobs said:
I sent him a pm with a link to the minimal adb and fastboot and told him id help him do whatever, but I don't know his knowledge level about android to begin with so.
Click to expand...
Click to collapse
That's so nice of you sir.:good:
finanandroid said:
Troubleshooting the Phone : I Understand that you are not Rooted, locked, and s-on .
1- Call vzw tech support and ask for a replacement. But Do first before call VZW a Reset Phone*. ( setting>back up & Reset>reset phone )
2- are you with Verizon Wireless, if so you should be notified for a new OTA Update available (you are outdated with software 2.04 )
however it should not prevent the phone to run well.
3- Are you using the original usb cable when connect the phone to the power wall outlet ( have you check the outlet power supply if it is good)
4- are you able to charge your phone on your Computer through usb cable. (try different USB port)
Click to expand...
Click to collapse
Hello and thank you for all for your help. Just so you guys know, the phone does charge when plugged in to my computer, I am using the original usb cable and power outlet, I am not with Verizon or in USA ( I bought the phone through ebay and unlocked). I tried every solution that has been posted by everyone so far and nothing. I do not have such advanced levels of adb, but I followed the guide to installing adb and reseting back to factory did not work. The phone has 100% battery level but once I remove it from the computer, the phone screen goes black, I can tell the screen is still on but everything goes black, then the htc white boot screen appears, it goes black again and it loops between the htc white boot screen and black screen on and on. Is this a software issue? Or is it possible it might be hardware (since no audio is able to be played either)?
Reset Phone
majincamz said:
Hello and thank you for all for your help. Just so you guys know, the phone does charge when plugged in to my computer, I am using the original usb cable and power outlet, I am not with Verizon or in USA ( I bought the phone through ebay and unlocked). I tried every solution that has been posted by everyone so far and nothing. I do not have such advanced levels of adb, but I followed the guide to installing adb and reseting back to factory did not work. The phone has 100% battery level but once I remove it from the computer, the phone screen goes black, I can tell the screen is still on but everything goes black, then the htc white boot screen appears, it goes black again and it loops between the htc white boot screen and black screen on and on. Is this a software issue? Or is it possible it might be hardware (since no audio is able to be played either)?
Click to expand...
Click to collapse
Could be a hardware problem, hard to tell, perform a Factory reset*
copy your media files to the computer before Reset phone
From a Home screen, select Apps ( Apps icon located at the bottom).
Select Settings.
Note If the app icon is missing, select App menu filter (located at the top) then select All apps.
Select Backup & reset.
Select Reset phone.
Note If presented, enter the current passcode or draw the unlock pattern.
Select Reset phone.
Select OK.
Note Allow up to 10 minutes for the factory data reset and reboot processes to complete.
finanandroid said:
Troubleshooting the Phone : I Understand that you are not Rooted, locked, and s-on .
1- Call vzw tech support and ask for a replacement. But Do first before call VZW a Reset Phone*. ( setting>back up & Reset>reset phone )
2- are you with Verizon Wireless, if so you should be notified for a new OTA Update available (you are outdated with software 2.04 )
however it should not prevent the phone to run well.
3- Are you using the original usb cable when connect the phone to the power wall outlet ( have you check the outlet power supply if it is good)
4- are you able to charge your phone on your Computer through usb cable. (try different USB port)
Click to expand...
Click to collapse
finanandroid said:
Could be a hardware problem, hard to tell, perform a Factory reset*
copy your media files to the computer before Reset phone
From a Home screen, select Apps ( Apps icon located at the bottom).
Select Settings.
Note If the app icon is missing, select App menu filter (located at the top) then select All apps.
Select Backup & reset.
Select Reset phone.
Note If presented, enter the current passcode or draw the unlock pattern.
Select Reset phone.
Select OK.
Note Allow up to 10 minutes for the factory data reset and reboot processes to complete.
Click to expand...
Click to collapse
Done all that and no success
I believe it's a hardware problem and the phone is probably under warranty so I would call htc tell them what's going on and see if they can help you out. It shouldn't be an issue.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Jaggar345 said:
I believe it's a hardware problem and the phone is probably under warranty so I would call htc tell them what's going on and see if they can help you out. It shouldn't be an issue.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Like I said before, I dont think I could get help if it were under warranty since i bought it used off ebay and have no receipt for it. Which part of the hardware do you think might be causing this problem? Maybe i could take a look and see the internals for my self...
..............................................
turn phone off and connect to a wall outlet then press and hold the power button while holding volume up and down and the same time for two minutes or until phone powers on htc says this can fix a magnitude of issues worth a try
I'll try that and will reply soon
thanks
it didn't work
Try this you guys. Turn off your phone completely and then just plug it into the wall charger. The orange charging led should turn on. Let it sit for about 2 hours or until it turns green. Then while keeping it connected turn on the phone.
silvania34 said:
Try this you guys. Turn off your phone completely and then just plug it into the wall charger. The orange charging led should turn on. Let it sit for about 2 hours or until it turns green. Then while keeping it connected turn on the phone.
Click to expand...
Click to collapse
I already did with no luck
how long have you had the device ? possible you bought a bad device unless over time these devices cant take the heat of the processor as this phone is beast and can easily die for heat or anything really a hard bump or fall can cause hardware issues