So I rooted my EVO 3D using the HTC method. Then I installed CWR and SU. Installed Titanium backup and took a couple of backups. Everything was fine. Then I had this bright idea of installing ROM Manager. I run ROM Manager and I see this option for backing up existing ROM. I click on it and it asks me to install a boot loader or something. I install it. Then click backup again. BAM ! Phone reboots and goes blank. Now the red LED is consistently blinking every short while and the phone wont start.
Tried removing the battery and holding power to drain the cap. Then tried holding power. No dice. Tried holding power + Volume - no dice. The phone simply wont boot.
How do I fix it ? Is it bricked for good ? Anyone else have this problem ?
Try unplugging and then turning it on. Shouldn't be bricked either way. Hope this helps.
Try running the HTC method again
Sent from my PG86100 using xda premium
If the suggestions already given do not work try hooking it up to your
PC and seeing if adb works? Them try to boot into fastboot, then fastboot recovery.
If not, try hooking into sync and seeing if you can initiate an Ruu. The Ruu will more than likely not be successful because you are unlocked and would need to lock first, but some communication between your phone and pc is a great sign.
also there is a thread here (I think sticky) that says "think you broke your phone, look here". Check that thread out to see if any suggestions.
Edit: added link
http://forum.xda-developers.com/showthread.php?t=1281729
Sent from my PG86100 using XDA App
To try all of that it needs to power on and the screen needs to show something. It simplywont power on. Red led keeps blinking. Tried charging it, connecting it to my Mac. A DB reboot. A DB reboot recovery. Says device not cnected.
nimkar said:
To try all of that it needs to power on and the screen needs to show something. It simplywont power on. Red led keeps blinking. Tried charging it, connecting it to my Mac. A DB reboot. A DB reboot recovery. Says device not cnected.
Click to expand...
Click to collapse
Well if the red light is blinking I highly doubt it is bricked.
If Adb doesn't work, try running an Ruu through sync. Even if it says there is no device connected to sync, run the Ruu anyhow. I can tell you that I had an issue Once where I hooked it up to sync and it said there was no device connected. I tried to run Ruu anyhow and it initiated. It didn't complete because I was still locked, but at least it was a sign of life. And after it did it's partial run, I was able to but back into hboot.
Try it. You've got nothing to lose. Me though....I'm losing sleep and have to get up early tomorrow so I'm going to bed. I'll subscribe to this thread to try to keep up with it in the morning to see where you are at. Good luck.
oh. And sleep on it too if you find yourself getting frustrated. Sometimes I find that a night to sleep on it really clears my head to and let's me look at it with a fresh perspective the next morning.
Sent from my PG86100 using XDA App
All suggested up is what I'd recommend. I wish you best of luck.
remove power from the thing for 10 minutes - this means take the battery out, do not have it plugged in... then try again... sometimes they freak the f out over nothing...
Wife's stock EVO has done that when an app tried to reboot the thing.
Try typing fastboot oem boot in terminal with your phone connected obvs
Sounds like a dead battery. Try leaving it plugged in overnight or switch out the battery with a good one.
wrong section btw
Sent from my Touchpad using xda premium
thanx all for your responses. I appreciate them all. The only thing I haven't tried from suggestions above is keeping the battery out for extended period of time. Trying that now. Also since I am a complete noob what is ruu and is I avaliabe or Mac.
I had this issue with the 1.0.x versions on twrp
charge the battery externally if you can. then put it back in and try to turn it back on
do you have insurance? if nothing works take it to sprint service and act all dumb
mildlydisturbed said:
remove power from the thing for 10 minutes - this means take the battery out, do not have it plugged in... then try again... sometimes they freak the f out over nothing...
Wife's stock EVO has done that when an app tried to reboot the thing.
Click to expand...
Click to collapse
This was the fix that worked. Removed the battery for 2 hrs. Phone was fine after that. Posting from phone !
I had a the exact same thing happend to mine.
Repeated battery pulls did not help and it would just blink.
Took it to a sprint keosk at a mall and they just pulled the batter and replaced it with another battery and it booted fine, and then they put my battery back in and it was fine after that, although the battery needed to be charged.
Yeah that happened to my og evo I was all flippin out over a dead battery hahaha
Yep, dead battery. Freaked me out the first time this happened also.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
This is not a dead battery issue but more accurately a "You phone thinks the battery is dead when its actually not" issue. I charged the battery for a long time using usb cable and my Mac and then using the stock charger and even that did not help. Repeated battery pulls also did not help. Only when the battery was taken out and left for a extended period was it fixed.
Here is my theory. All EVOs have a powerful capacitor inside them somewhere where they store the "Battery is almost dead" info and this capacitor takes some time to discharge. Every time you pull the battery and put it back in again the capacitor is not fully discharged and retains the "battery is almost dead" flag and never updates it even after repeated charging. The only solution is to pull the battery and leave it out for some time ( I left it out for 2 hours, someone here suggested 15+ minutes is good enough) and let the capacitor fully discharge at which point it will loose its "Battery is almost dead" flag. Then plug in the battery and everything is fine.
This explanation is a complete assumption but it is based on my observations and expriments. I have seen a lot of people post the same problem however no clear solution and tried solution as the one above so I hope this post helps others like me.
nimkar said:
This is not a dead battery issue but more accurately a "You phone thinks the battery is dead when its actually not" issue. I charged the battery for a long time using usb cable and my Mac and then using the stock charger and even that did not help. Repeated battery pulls also did not help. Only when the battery was taken out and left for a extended period was it fixed.
Here is my theory. All EVOs have a powerful capacitor inside them somewhere where they store the "Battery is almost dead" info and this capacitor takes some time to discharge. Every time you pull the battery and put it back in again the capacitor is not fully discharged and retains the "battery is almost dead" flag and never updates it even after repeated charging. The only solution is to pull the battery and leave it out for some time ( I left it out for 2 hours, someone here suggested 15+ minutes is good enough) and let the capacitor fully discharge at which point it will loose its "Battery is almost dead" flag. Then plug in the battery and everything is fine.
This explanation is a complete assumption but it is based on my observations and expriments. I have seen a lot of people post the same problem however no clear solution and tried solution as the one above so I hope this post helps others like me.
Click to expand...
Click to collapse
Glad you got it working.
Sent from my PG86100 using XDA App
Related
Hey there,
I have my Vibrant for a good year now since it came out pretty much. Last week it just stopped charging out the blue. The battery is completely empty and shows a thermometer with a warning sign and stops charging seconds after its plugged in. So I assumed it might be a battery malfunction and I got my spare battery in as soon as I came home and tried charging - same problem. I think it is highly unlikely that both batteries fail at the same time. Therefore, I assume there is something wrong with the temp sensor in the phone. I saw a few people have a similar problem with the epic 4G, but the discussion got really side tracked by other issues. My phone is rooted, but I was running stock froyo, so that shouldn't be the problem or should it?
I just wanna know if anybody had the same problems and if there is a quick solution, I google and forum searched a while but as soon as you throw in the term battery it gets spammed with battery life discussions.I just checked my files I have on the phone, apparently I have the premium insurance - does that mean I just can go to the next Tmo store and get a replacement? Any feedback is greatly appreciated.
Phill
Well for your problem, i suggest you try a different rom and see if the problem persists... maybe its a bug
And as for insurance, you mail the phone in and pay a deductible, which should be like 135$ or so. They send you a refurb.. or if you say it wus lost, you dont have to mail in phone
Sent from a cell tower to the XDA server to you.
thanks for the quick reply. Is there a way to reflash without a battery?
I don't see it as a bad thing. If your phone gets too hot and keeps charging that's going to burn something inside. When my phone won't charge I know I have let it down. So it can cool down. But to fix your problem reboot the phone. You can keep charging it after it boots up
Sent from my SGH-T959 using Tapatalk
pro1st said:
thanks for the quick reply. Is there a way to reflash without a battery?
Click to expand...
Click to collapse
As long as your phone can run successfully for a couple minutes, i dont see why not
Sent from a cell tower to the XDA server to you.
Mine did something similar. I picked it up after putting it on the charger. It was hot and would not come on. I unplugged it and let it cool off for a while and it cleared up.
I got that message once...
Vibrant was in a car dock, with power.
It was *HOT* out and sun was hitting the back of the unit. (A/C on of course)
Google Navigation was running (display brightness max)
Google Listen was running
Bluetooth was passing music to a speakerphone
When I run the phone with that setup, the charger can't even keep up with the phone power needs. The battery level slowly drops. No question the phone is working hard.
This was a true heat issue... I removed the charger and turned off the display to let it cool off a bit. (I was almost home).
So the question again, is your phone hot or is it a false reading?
Robert
Hey,
I am sorry I didn't clarify the actual battery temp. It is normal - so its neither in the sun or in a too cold spot when I try charging it. The phone probably runs for one for a few seconds before turning off so there is no chance of the battery stats wipe. I think I will try to find an external charger and try to charge the batteries this way to have enough juice for flashing a new rom. Thanks for all the replies!
Does it charge the battery with the phone off? If not, I don't think a new ROM will help.
Hey there! Wondering if you got around to solving this. I've got a Vibrant doing the same exact thing. Battery being cool it sais that is overheating. Did changing the ROM solved it or not?
c0olcast said:
Hey there! Wondering if you got around to solving this. I've got a Vibrant doing the same exact thing. Battery being cool it sais that is overheating. Did changing the ROM solved it or not?
Click to expand...
Click to collapse
Sorry for resurrecting an old thread, but a resolution never seemed to be made here. Has anybody found a fix to this?
As of yesterday, my wife is having the same issue with my old Vibrant phone which she now uses. It's flashed with Bionix V 1.3.1 and Tigerblood overclock to 1.2ghz. This could be the issue, the Tiger Blood overclock, but I'm not sure. I'm out of the country for three weeks and currently she's left with a dud of a phone that keeps giving her the temperature warning in the triangle when plugged in while the phone is powered off followed by it stop charging. When she turns it on, she gets to the SD card check and then the phone completely freezes. Once in a while it's able to stay on for a minute or so before freezing, but more often than not the phone does not fully turn on and just goes frozen after a few seconds, sometimes at the Tigerblood logon screen before making it to the desktop. Me being 4000 miles away doesn't make it easier to help her but I've recommended she leave the phone unplugged, battery out for the night to see what happens. I also told her to take off her silicon case thinking maybe that has something to do with the overheating. Well after 7 hours of her letting it sit to cool off like that, with the case off, she plugged it back in and is having the same issues as yesterday. Absolutely no progress made. One of her colleagues said she should try leaving the phone in rice confused:) so she's giving that a go and another guy in a phone shop who she went to for advice after work said that the motherboard might need replacing. I'm convinced all it needs is to have the Tigerblood removed or reflash a rom onto it but there's really no knowing unless I have it in my hand.
Is there any quick fix to this problem without having to do all that? Surely there must be a way to charge the phone without it heating up and freezing up. She's tried plugging it into different rooms, on her laptop, etc, none seem to get rid of the temperature problem. I've had the phone since August 2010 and never had any issues with it. I also never once saw that temperature error message so was taken aback when she showed me it over skype. I just upgraded to the S3 and gave her the phone 2 weeks ago, but surely it shouldn't just die out just like that? Thought the Vibrants were made tougher than that?
Any help would be greatly appreciated. Much thanks in advance
Its most probably a kernel issue or a bug in the rom; so the only way to find out is to flash another kernel/rom..
P.s Vibrants are rock solid
Sent from my SGH-T959 using xda app-developers app
Update- Phone doesn't even turn on anymore, no signs of life
danny_extremex said:
Its most probably a kernel issue or a bug in the rom; so the only way to find out is to flash another kernel/rom..
P.s Vibrants are rock solid
Sent from my SGH-T959 using xda app-developers app
Click to expand...
Click to collapse
Will be looking into reflashing another kernel/rom when I get home in a few weeks time, but it must be noted that the phone has been showing no signs of life for the last few days now. After letting it sit out for 7 hours on the first night, battery out and everything, she went to plug it in the following morning and this time absolutely no notification came up. Not even a lighting up of the phone or anything. No signs of life at all. Every time she hit the power button nothing occurred. The phone still heats up and after a few minutes while plugged in and gets very hot to the touch again but no matter how many times she attempts to turn it on, nothing happens.. She's tried plugging it into her computer via usb, into electric sockets in other rooms, even in the bathroom in one of the 115 volt electric shaver outlets in the bathroom (we live in the UK currently), and none of these ideas worked. Still no signs of life. It has been this way for three days now and is frustrating as I can offer no advice to her to get the phone to turn on anymore.
What on earth can be the problem? Has this happened to anyone before? And is there a fix to this or can we consider the phone to be a paperweight at this point?
polosprt009 said:
Will be looking into reflashing another kernel/rom when I get home in a few weeks time, but it must be noted that the phone has been showing no signs of life for the last few days now. After letting it sit out for 7 hours on the first night, battery out and everything, she went to plug it in the following morning and this time absolutely no notification came up. Not even a lighting up of the phone or anything. No signs of life at all. Every time she hit the power button nothing occurred. The phone still heats up and after a few minutes while plugged in and gets very hot to the touch again but no matter how many times she attempts to turn it on, nothing happens.. She's tried plugging it into her computer via usb, into electric sockets in other rooms, even in the bathroom in one of the 115 volt electric shaver outlets in the bathroom (we live in the UK currently), and none of these ideas worked. Still no signs of life. It has been this way for three days now and is frustrating as I can offer no advice to her to get the phone to turn on anymore.
What on earth can be the problem? Has this happened to anyone before? And is there a fix to this or can we consider the phone to be a paperweight at this point?
Click to expand...
Click to collapse
Some kernels require a certain amount of power to fully boot the phone up and will not charge until it has 5% battery or so. I personally think her battery may be unable to hold a charge or like I said before it doesn't have enough juice to boot the phone because of the kernel. There is a way to charge the battery with the phone off. You can use ANY kind of usb cord, I used an old printer usb cable when I had to do this. All you do is cut off the side that is not usb and strip the positive and negative wires(red and black), then place the stripped wires on the positive and negative connectors on the back of the phone and insert the battery (make sure it's a snug fit). Plug the usb end into your pc and charge the battery that way, DO NOT let charge for over 2 minutes at a time. Wait five minutes and do it again if you have to. If she gets it to boot up, I would definitely flash a new kernel first to see if thats how the problem originated.
Sent from my SGH-T959 using xda premium
So the past two nights iv let my rezound battery go dead. The problem is it wont charge a dead battery. It charges if there is some battery and its on but when it is dead it is dead. The fix was I had to put the rezound battery in my tbolt to get a little bit of juice.
Any ideas or similar problems? I am unlocked with the htc unlock tool and running nils business sense?
Could it be a rom bug?
Don't let your battery die. It's bad for it anyway.
Sent from the Rez Beast
Once the battery is dead what does the LED on the phone do? If it blinks for a while it is either too hot or too dead to turn on, but it can still charge eventually. If the LED is not coming on at all I would pull the battery out and connect the charger with no battery and see if the LED comes on. If still no luck, get a new charger.
Blinks then Charges
I had the battery die on me once (on a prior battery and prior rezound). The phone will blink orange for a WHILE (I tried 3 different chargers not knowing what it was), but eventually started to charging. I think patience is needed. If, after 15 minutes, you still aren't charging, then that's something (but longer if the phone was also hot).
If I hit he power button with or without the battery in the led will light for a short time. I had it plugged in all night and no charge. I used two different plugs.
As for not letting it die. I know its not ideal but I couldn't help it.
jdmba said:
I had the battery die on me once (on a prior battery and prior rezound). The phone will blink orange for a WHILE (I tried 3 different chargers not knowing what it was), but eventually started to charging. I think patience is needed. If, after 15 minutes, you still aren't charging, then that's something (but longer if the phone was also hot).
Click to expand...
Click to collapse
+1. Same thing here.
KORM via the beast known as the Rezound.
I let my phone die completely once. I freaked out that my phone wasn't charging. I went onto HTC's site and it said that it could take 20 or more for the led to turn on while charging if the phone was completely dead. Just plug it in and be patient. It will charge and the led will eventually turn on.
Sent from my Vigor using xda premium
I had this problem too, and am a little concerned I have a defective phone
So I had this issue happen this weekend. My daughter was using the phone when it died. Couldn't get it restarted. (I am unlocked via HTC, stock ROM with bloat removed. Phone is a week old.)
After messing with it using the factory charger/cable and other chargers/cable combinations I got nothing. Light would only intermittently come on for a second or two then go back off.
I charged it over night with the factory charger/cable. Didn't work the next day. Charged it all day and night with my old charger/cable that I know works. Didn't work.
Tried multiple variations of taking out the Battery/Sim/SD card and using the plug-in chargers & CPU USB variations with no success.
Luckily, I had ordered a new spare battery and it came in the mail before I returned the phone. Plugged it and it started up fine.
But my concern is that my phone is not properly charging. I have also had other similar charging/battery life issues that raise concern.
As far as not letting it die, **** happens and phones die, if this is a reoccurring problem, that in my mind is pretty unacceptable. A phone should charge when its plugged in no matter what. I may end up returning it to see If just got a defective phone/battery.
My phone will turn on then off and im starting to think it has something to do with the battery. But when it started it was in tue yelllow on the status bar, now i have it charging without being turned on and the indicator light is on but hopping mine will fire up soon. This all just happened to me within the last two hours lol, already called verizon to get a replacement but still going down there tomorrow.
Sent from my SCH-I800 using xda premium
DLink888 said:
So I had this issue happen this weekend. My daughter was using the phone when it died. Couldn't get it restarted. (I am unlocked via HTC, stock ROM with bloat removed. Phone is a week old.)
After messing with it using the factory charger/cable and other chargers/cable combinations I got nothing. Light would only intermittently come on for a second or two then go back off.
I charged it over night with the factory charger/cable. Didn't work the next day. Charged it all day and night with my old charger/cable that I know works. Didn't work.
Tried multiple variations of taking out the Battery/Sim/SD card and using the plug-in chargers & CPU USB variations with no success.
Luckily, I had ordered a new spare battery and it came in the mail before I returned the phone. Plugged it and it started up fine.
But my concern is that my phone is not properly charging. I have also had other similar charging/battery life issues that raise concern.
As far as not letting it die, **** happens and phones die, if this is a reoccurring problem, that in my mind is pretty unacceptable. A phone should charge when its plugged in no matter what. I may end up returning it to see If just got a defective phone/battery.
Click to expand...
Click to collapse
As far as not letting it die, **** happens and phones die.
--I agree, but once it gets down to 5%, why not just turn it off knowing the problems people are having so wide spread now.
Under the exact same conditions I have had the same problem with a warm battery reboot. It seems to occur when you are talking on the phone and let it die. Once it dies the phone will not reboot. My wife has the exact same phone. When I put her battery in my phone the phone works fine. My wife’s phone dies every night and she simply plugs it in the wall and it charges no problem. Again the conditions seem to be related to the battery dying while it is hot. If the battery dies while the phone is cool and not used then it seems to reboot no problem. I will go to Verizon tomorrow to look for a fix. I will let you know what happens.
I'm also having this problem but i can return my phone because i unlock it or can i return it ?
Check and see if your battery is 3.7 or 3.8v . I wonder if it is related to the charging issue with the 3.8v battery some people seem to be having.
mjh68 said:
Check and see if your battery is 3.7 or 3.8v . I wonder if it is related to the charging issue with the 3.8v battery some people seem to be having.
Click to expand...
Click to collapse
it's a 3.8v what do you recommend i do ?
I had this happen, and here is what worked:
Unplug charger
remove battery
plug charger in
insert battery (while charger is plugged in)
I got an immediate orange LED and after a little while I was able to run the phone back on.
gsgleason said:
I had this happen, and here is what worked:
Unplug charger
remove battery
plug charger in
insert battery (while charger is plugged in)
I got an immediate orange LED and after a little while I was able to run the phone back on.
Click to expand...
Click to collapse
I had the same issue with my OG Droid. Would kill the battery and it would stay dead, even after a whole night of charging. The above method seemed to work for me.
I make 100% sure mine never goes totally dead after an experience I had with my Droid Charge.
I accidentally let it die completely (I fell asleep when it was almost dead & it ran all night). The next morning it was off, I put in a fully charged battery & it fired right up but started FCing like crazy. Every single thing I clicked on force closed immediately, I had never seen anything like it.
I was running a custom ROM & kernel & had done a nandroid BU the day before. I restored the BU & the phone ran perfectly again, but that scared me enough that I made darn sure it never happened again LOL........
gsgleason said:
I had this happen, and here is what worked:
Unplug charger
remove battery
plug charger in
insert battery (while charger is plugged in)
I got an immediate orange LED and after a little while I was able to run the phone back on.
Click to expand...
Click to collapse
That didn't work for me i just won't let it run down i guess.
Holy ****!!! I think I may have found the fix! I have had the same exact problem as everyone in here. It seems to happen once I root. My Rezound would die completely, then after plugging it in, the light would come on for 5 seconds or less then shut off. I plugged it into my computer and Windows makes the USB Connected sound, so I figured something is happening.
I went into my command prompt and *adb devices*. It showed my device, but says in recovery mode. I then *adb reboot bootloader* and the bastard rebooted into bootloader! From there, I chose "REBOOT" and it fired right back up! Anyone who is having this problem, please try this and let me know if it works for you!
***UPDATE***
It appears when the battery dies all the way and then doesn't charge, the phone is automatically going into recovery mode even though nothing shows on the screen. I had my SIM card out when I tried this the first time, then when putting my SIM back in, it started doing the same thing. But again, it was going directly into recovery mode. This time, I tried a simple *adb reboot* and BAM! I'm back up and running! Again, let me know if this works for you, or if you need help doing this, let me know.
thehomebiscuit said:
Holy ****!!! I think I may have found the fix! I have had the same exact problem as everyone in here. It seems to happen once I root. My Rezound would die completely, then after plugging it in, the light would come on for 5 seconds or less then shut off. I plugged it into my computer and Windows makes the USB Connected sound, so I figured something is happening.
I went into my command prompt and *adb devices*. It showed my device, but says in recovery mode. I then *adb reboot bootloader* and the bastard rebooted into bootloader! From there, I chose "REBOOT" and it fired right back up! Anyone who is having this problem, please try this and let me know if it works for you!
***UPDATE***
It appears when the battery dies all the way and then doesn't charge, the phone is automatically going into recovery mode even though nothing shows on the screen. I had my SIM card out when I tried this the first time, then when putting my SIM back in, it started doing the same thing. But again, it was going directly into recovery mode. This time, I tried a simple *adb reboot* and BAM! I'm back up and running! Again, let me know if this works for you, or if you need help doing this, let me know.
Click to expand...
Click to collapse
Yes... HTC phones never charge "powered off" When you turn it off and then put it on the charger, it is actually entering/booting a special screen off recovery mode during charging.
CWM recovery on the rezound has trouble charging a completely dead battery.
Use Amon RA recovery.
As per feralicious' suggestion I've created a poll to collect data. Information on the issue below. Sorry about the long poll.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
So I'm on Rezound #2 right now. Both of the phones had the same exact problem when the battery died ie. they simply wouldn't charge. Now I thought the problem was hardware (which is why i got the replacement), but after being able to boot up my replacement phone with my girlfriend's battery, I relocked and RUU'd back to stock. I then threw in my dead battery and VOILA it began charging. I let the battery die again just to see if i can recreate the problem, and havent had the issue since.
Now i really want to unlock my phone again but my girlfriend isn't here all the time for me to test out if this was an issue with either the unlocked bootloader, a kernel issue, ROM issue, or if I'm actually having hardware issues. I'm hoping someone here with an extra battery or external charger here can recreate the problem and hopefully we can pinpoint this. Just for reference the ROM I was using was CleanROM GBE 1.6.5 *SP1* - Base: OTA 2.01.605.11 and whatever kernel that came with it. If this is a ROM and/or Kernel issue, we need to get a hold of scrosler and let him know.
Any help would be much appreciated guys thanks!
EDIT: Just to let you guys know. I did do all the OTA updates prior to unlocking the bootloader in the first place.
UPDATE: So I've been sitting with my phone literally all day trying to pinpoint what could be the cause of this. Clockworkmod seems to be the culprit. I'm going to be testing more right now so I'll keep you guys updated.
UPDATE #2: Success! The battery not charging while dead and powered off issue was resolved on my end. ClockworkMod definitely was to blame. I noticed it stopped charging while powered off/dead as soon as I flashed ClockwordMod and shut down my phone while it was connected to my PC (This was after my 5th go around with the bootloader unlock). I then flashed over Amon Ra to see if it really was ClockworkMod or if it was the recovery in general, and what do you know Amon Ra allows me to charge while powered down and dead. If you guys are having this very problem with your phone and you're running any version of ClockworkMod I suggest you try flashing Amon Ra 3.13 and posting your results so we can see if this is universal.
Instructions to flash recovery with adb and fastboot for Windows below:
Note you only need to do this if for some reason you can't boot into the bootloader using Vol. Down + Power. I am not responsible for bricked phones.
Prerequisites:
1. ADB & Fastboot (found with the Android SDK)
2. Amon Ra IMG (Use ver. 3.15 if you've flashed ICS RUU)
3. Battery with a charge.
Instructions:
1. Pull out battery, and unplug from charger/computer
2. Reinsert battery
3. Plug in your USB cable to computer and phone (your charge indicator light should go on for 1-3 seconds and shut off, then your drivers should load afterwards.)
4. Place the Amon Ra img file in the folder where ADB and Fastboot reside.
5. Once drivers have loaded open up Command Prompt, and find your way to where you set up ADB and Fastboot. Type cd <folder path>
6. Now type the command adb reboot bootloader (Note: if you get some sort of error try again a few more times. if it keeps giving you error try redoing steps 1-3 before doing 5 again)
7. Your phone should have now loaded directly into Fastboot. When in Fastboot go back to the command prompt and type in fastboot flash recovery <amon_ra_file.img>
8. When the process is done shutdown your phone and test the charging.
**ADDED** If you can run ADB commands while the phone is off, dead, and not charging, type adb reboot. The OS should boot up and begin charging. I would say let it charge till 40% before you flash an alternate recovery. If you're unsuccessful in rebooting with adb try leaving your phone plugged into the charger for 2-5 hours (this seems to have worked for some people to get a charge). If that doesn't work I recommend you get another battery or use an external charger. (Thanks excellentnuke)
If you are coming from a dead battery the charge light indicator should turn on for a few seconds then turn off for a few seconds then begin flashing continuously. When the light becomes solid you should be able to boot. When coming from a charged battery the same thing should happen, except instead of the charge indicator flashing continuously it should come back solid.
UPDATE #3: I've also discovered this problem isn't relegated to having a dead battery. Simply disabling Fast Boot and shutting off your phone can recreate the problem with CWM.
UPDATE #4: I can say that I think I've gotten enough feedback to determine that this issue was solved by what I've written above. I would highly advise people to switch over to Amon Ra until we get a bug fix/update for CWM to address this issue.
Thanks to everyone that was involved in this thread to help determine the cause of this; I appreciate it.
You should set up a poll and change the thread title to indicate that.
I am on Ineffabilis GB and accidentally let the battery die yesterday and it charged no problem. I was ready for a problem, thankfully it went straight to charging. I had also let it die once before unlocking and no problem then either.
feralicious said:
You should set up a poll and change the thread title to indicate that.
Click to expand...
Click to collapse
Good idea. Done!
My phone shut off last night due to battery death, when I woke up I plugged it in and the charge indicator came on after about 10 minutes of charging.
I have been running different ROMs and had it die a few times...
When I plug it in the LED comes on and starts blinking, after a few minutes of the blinking, I unplug then re-plug in the phone to the charger and the light comes on and stays on. I never let it sit there long enough to stop blinking on its own. I get impatient LOL.
UgXvibe said:
My phone shut off last night due to battery death, when I woke up I plugged it in and the charge indicator came on after about 10 minutes of charging.
Click to expand...
Click to collapse
I take it you're running stock still? or a custom rom? It seems odd that the charge indicator would take that long to start. I left mine on the charger for about 30 minutes when it was unlocked without any progress.
This happened to me, I took my phone to verizon and they just gave me a new battery... it took a little while, them trying different batteries, looking for a 'test' rezound battery before pulling a packaged battery to try and finally they were satisfied then swapped it out... all my boot logos and screens were stock but my launcher was not... they never went as far as checking phone specs or asking about root/unlock... they did check the phone settings to check on charge at one point... I was just thankful it wasn't a bad micro connector because I didn't want to have to wait for a new phone
I'm having the same problem once my phone dies i can't get it to charge. it starts charging for two sec and it stop charging and i does that with both of my batteries i have a 3.8v that came with the phone and a 3.7v that verizon sent me because my phone was over heating. I'm unlock and running CleanROM GBE 1.6.5 *SP1*
Before I knew about this issue I actually had my phone die when I had my 3.8v battery, I had no issues what-so-ever plugging it in to charge. I've been afraid ever since, I also have the 3.7v battery now.
I bought my phone from a trade of my GNEX, so I do not have the 1 year manufacturer warranty, so no refurbs for me, and I had to buy the 3.7v battery
I'm getting rare blue screen flickers like the ones from ICS ROMS on GB ROMS too. no fun!
andybones said:
Before I knew about this issue I actually had my phone die when I had my 3.8v battery, I had no issues what-so-ever plugging it in to charge. I've been afraid ever since, I also have the 3.7v battery now.
I bought my phone from a trade of my GNEX, so I do not have the 1 year manufacturer warranty, so no refurbs for me, and I had to buy the 3.7v battery
I'm getting rare blue screen flickers like the ones from ICS ROMS on GB ROMS too. no fun!
Click to expand...
Click to collapse
What's interesting is that I keep reading about issues with the 3.8v battery but nobody talking about the 3.7v's. I'm on a 3.7v and this issue is occuring, but i'm beginning to think it has something to do with either an unlocked bootloader or ROM issue.
drinkhere said:
I'm having the same problem once my phone dies i can't get it to charge. it starts charging for two sec and it stop charging and i does that with both of my batteries i have a 3.8v that came with the phone and a 3.7v that verizon sent me because my phone was over heating. I'm unlock and running CleanROM GBE 1.6.5 *SP1*
Click to expand...
Click to collapse
I would highly suggest you relock and go back to stock. It seems to have made the issue subside. Since you have 2 batteries if you wanna do further testing with other roms and configs that would help out a lot. No pressure though i understand if you dont want to do it.
I've also had the problem with it not charging after it's died and thus had Verizon send me a new 3.7v battery. And now Ive had the same problem with the 3.7v.
This is how i've fix both the 3.7v and 3.8v when they wont charge.
Battery pull and replace. Then plug in. Dont hit power or touch the phone. Just leave alone. Orange light will come on for a few seconds then off. Still leave it alone. I swear it took an hour but it finally booted on it's own. Weirdly it had 40% battery when it was finally on.
I'm on stock OTA rooted and running chad's beta 4 but i've had the problem with beta 3-1 as well. I did have Force fast charge enabled in incrediControl. Most of the reason the phone died was because it bootlooped for hours(?) while i was sleeping and it wasnt plugged in.
I did have a similar problem when i first got my incredible... dunno what i was running at the time could have been stock.
What i'm guessing happens is that you drain the battery so much it takes forever for it to get a strong enough charge to boot on it's own.
I had this happen for the first time today. Phone wouldn't start,battery wouldn't charge. My fix.... Open command prompt. Plug phone in to computer. Type " adb reboot recovery" when recovery opens the battery starts charging. Push reboot and Pooooof! A charging phone!
Sent from my ADR6425LVW using xda premium
joel4832 said:
I've also had the problem with it not charging after it's died and thus had Verizon send me a new 3.7v battery. And now Ive had the same problem with the 3.7v.
This is how i've fix both the 3.7v and 3.8v when they wont charge.
Battery pull and replace. Then plug in. Dont hit power or touch the phone. Just leave alone. Orange light will come on for a few seconds then off. Still leave it alone. I swear it took an hour but it finally booted on it's own. Weirdly it had 40% battery when it was finally on.
I'm on stock OTA rooted and running chad's beta 4 but i've had the problem with beta 3-1 as well. I did have Force fast charge enabled in incrediControl. Most of the reason the phone died was because it bootlooped for hours(?) while i was sleeping and it wasnt plugged in.
I did have a similar problem when i first got my incredible... dunno what i was running at the time could have been stock.
What i'm guessing happens is that you drain the battery so much it takes forever for it to get a strong enough charge to boot on it's own.
Click to expand...
Click to collapse
Hmmm... I'm beginning to suspect its either an unlocked bootloader issue or a kernel issue and not a ROM issue.
Now thats cool that your phone was able to boot up after an hour on the charger without the charge indicator light telling you it was charging (my phone was probably doing the same thing) but it still shouldnt take that long to be able to boot up the device.
When stock my charge indicator blinks continuously until it's ready to boot up, then it becomes solid. This only takes about 4-5 minutes. When running custom ROM/Kernel it would give me the same thing it gave yours ie. charge indicator turns on for 1-3 seconds and turns off and nothing else.
afmracer6 said:
I had this happen for the first time today. Phone wouldn't start,battery wouldn't charge. My fix.... Open command prompt. Plug phone in to computer. Type " adb reboot recovery" when recovery opens the battery starts charging. Push reboot and Pooooof! A charging phone!
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
I'm definitely going to take this into account and try it when i unlock my phone again. Thanks man!
IrvChynaman said:
What's interesting is that I keep reading about issues with the 3.8v battery but nobody talking about the 3.7v's. I'm on a 3.7v and this issue is occuring, but i'm beginning to think it has something to do with either an unlocked bootloader or ROM issue.
Click to expand...
Click to collapse
Update in OP!
Im unlocked and on the senselessICS.
Ive had this issue happen to me several times. However today it was bad. I had it plugged in for 6+ hours with out it being able to turn on.
I had the 3.7v battery in the device.
i messed with it a bit with in that 6hour time frame. Pressing buttons pulling battery, etc. About 4 hours into this whole ordeal... it turned on, on its own. But stayed on the white HTC screen for about 45mins before i pulled the battery and tried to turn it on again. However, it would not turn on. Infact it never turned on....
Heres where it gets interesting. I had the 3.7v. My girlfriend comes home and has the 3.8v. I pop hers out, put it in my device. Fires right up... still sticks on the white HTC screen. While im impatiently waiting, i stick my 3.7v that my phone wouldnt boot with in her device. Fires right up.
I wasnt able to fully boot. Recovery/computer wouldnt mount my SDcard. Though... reformatting it from within recovery allowed it to be mountable again. I also had to wipe and reflash my rom in order to get the POS to boot.
edit: i would also like to note, when putting the battery [my 3.7v] into my girlfriends device. It showed about 80% battery.
krstnsn said:
Im unlocked and on the senselessICS.
Ive had this issue happen to me several times. However today it was bad. I had it plugged in for 6+ hours with out it being able to turn on.
I had the 3.7v battery in the device.
i messed with it a bit with in that 6hour time frame. Pressing buttons pulling battery, etc. About 4 hours into this whole ordeal... it turned on, on its own. But stayed on the white HTC screen for about 45mins before i pulled the battery and tried to turn it on again. However, it would not turn on. Infact it never turned on....
Heres where it gets interesting. I had the 3.7v. My girlfriend comes home and has the 3.8v. I pop hers out, put it in my device. Fires right up... still sticks on the white HTC screen. While im impatiently waiting, i stick my 3.7v that my phone wouldnt boot with in her device. Fires right up.
I wasnt able to fully boot. Recovery/computer wouldnt mount my SDcard. Though... reformatting it from within recovery allowed it to be mountable again. I also had to wipe and reflash my rom in order to get the POS to boot.
Click to expand...
Click to collapse
are you running clockworkmod recovery? Your issue sounds identical to mine and I MAY have a solution. I'm testing right now on my own phone right now.
IrvChynaman said:
are you running clockworkmod recovery?
Click to expand...
Click to collapse
yes. the touch one. However i had this issue prior with the unofficial clockwork.
krstnsn said:
yes. the touch one. However i had this issue prior with the unofficial clockwork.
Click to expand...
Click to collapse
Ok try flashing Amon Ra 3.13. Clockwork mod seems to be the culprit from my end. what was weird is when the phone was shut down I was able to run adb commands and every time i ran "adb devices" it showed my phone as recovery. It seems like clockwork mod recovery was trying to load before anything else preventing the phone from charging and booting up
so my amaze 4g has been having battery problems for a few days (this is the 2nd battery for it, first died after 13 months), and tonight i went to check a text message and i had about 45% battery left,i swipe to unlock the phone and then 1 sec later it just goes black.
i have tried everything, but the LED wont even turn on when plugged into charger/pc. in device manger i see "qhsusb_dload" , but everything Ive goggled about this issue seems to be related to modified phones, not bone stock.
any help?
haxxo said:
so my amaze 4g has been having battery problems for a few days (this is the 2nd battery for it, first died after 13 months), and tonight i went to check a text message and i had about 45% battery left,i swipe to unlock the phone and then 1 sec later it just goes black.
i have tried everything, but the LED wont even turn on when plugged into charger/pc. in device manger i see "qhsusb_dload" , but everything Ive goggled about this issue seems to be related to modified phones, not bone stock.
any help?
Click to expand...
Click to collapse
Unlucky! Your phone is dead,the only hope for you here :
http://forum.xda-developers.com/showthread.php?t=1627882
This happens when your battery is really dead. You might have to leave the charger plugged in for a few hours before the LED comes back on.
However, this is a temporary fix, and it is likely that it will happen again.
I'd recommend you to get a new battery, even if plugging it for a few hours solves your problem. HTC Amazes are notorious for killing batteries. If you look around, you'll see threads talking about horrible battery life, similar random shutdowns, and such that can only be fixed with a new battery.
SuperAfnan said:
Are you kidding me, why did you have to post this in the development section. This is for ROMs, Kernels, Mods, and development stuff only.
Please read the forum rules next time because you could get an infraction or get scolded. I am not rude so I don't do that stuff usually. Be warned!
Can someone call a moderator to move the thread, or lock it. I can't call a mod from the app.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
i thought i was posting in the Q&A section, i tried to delete the thread right after i saw my mistake, but it wont let me delete.
eadrang said:
Unlucky! Your phone is dead,the only hope for you here :
http://forum.xda-developers.com/showthread.php?t=1627882
Click to expand...
Click to collapse
wow, great quality phone HTC.
Keylogger_0 said:
This happens when your battery is really dead. You might have to leave the charger plugged in for a few hours before the LED comes back on.
However, this is a temporary fix, and it is likely that it will happen again.
I'd recommend you to get a new battery, even if plugging it for a few hours solves your problem. HTC Amazes are notorious for killing batteries. If you look around, you'll see threads talking about horrible battery life, similar random shutdowns, and such that can only be fixed with a new battery.
Click to expand...
Click to collapse
i tested my battery voltage and it was 3.850, how can it be really dead when its rated at 3.8v? i have had the battery issue before, but it never bricked my phone.
It's not bricked. (It shouldn't be)
Remove the battery, press the power button several times to dissipate any remaining charge in the phone, and then insert a fully charged battery. I'd recommend you using a different phone (if available) to charge the said battery.
After that, it should boot up normally.
And if I recall, voltage is supposed to be consistent, regardless of the charge level (unless it's totally dead, then maybe it's different, I don't know)
It's the current you want to look for.
Keylogger_0 said:
It's not bricked. (It shouldn't be)
Remove the battery, press the power button several times to dissipate any remaining charge in the phone, and then insert a fully charged battery. I'd recommend you using a different phone (if available) to charge the said battery.
After that, it should boot up normally.
And if I recall, voltage is supposed to be consistent, regardless of the charge level (unless it's totally dead, then maybe it's different, I don't know)
It's the current you want to look for.
Click to expand...
Click to collapse
thanks for the advice, i dont have any other phone to change this battery with. ill go and see if i can set up seomthing to test amperage, otherwise ill let it charge and heopfully it works.
EDIT: you sir are correct about the battery, i tested the amperage and a normal AA cell had 4.8A the phone battery had 0.002A lol.
haxxo said:
thanks for the advice, i dont have any other phone to change this battery with. ill go and see if i can set up seomthing to test amperage, otherwise ill let it charge and heopfully it works.
EDIT: you sir are correct about the battery, i tested the amperage and a normal AA cell had 4.8A the phone battery had 0.002A lol.
Click to expand...
Click to collapse
Yeah that's not normal. You could try charging it, but it's likely that the battery is fried already. You can buy a new battery on Amazon or some similar site. Many people (including me) recommend Anker batteries.
If you have no luck with the battery this HTC unbricking project for the amaze is definetly for you
Sent from my Nexus 4 using xda premium
sportsstar89 said:
If you have no luck with the battery this HTC unbricking project for the amaze is definetly for you
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
got a new anker battery from someone local, i saw the battery working on an amaze4g, doesn't work on mine. so the phone is the issue, are u sure the unbricking project is for me? it seems to be pointed to ppl who switched S-on
Well i tired to unbrick it, couldn't even get past the first step. linux detects the qualcomm device as bus 001 device 003 but brickdetect does not pick it up.
dead mobo?
I read loads of similar issues, but mine is a little different:
I heavily used my stock-rom, unrooted phone today, recorded long videos in Full HD, when I got back home, I had 18% battery, plugged it into my computer's USB to get the videos (unaware of the issue of insufficient current on USB ports) and windows did not recognize it.
I then unplugged it planning to plug it into the wall socket, and when I woke the phone, it died on my arms
A little annoyed, I plugged it into the wall socket, and got the slow, orange blinking LED, and was not able to turn the phone on. After 30 minutes, the LED stabilized and it seemed to be charging (while off), so I left it there for another 20 minutes.
When I tried to turn the phone on, it worked, normally, but showed 2% battery life remaining. I had Wi-Fi on, but normally it wouldn't be an issue, so I left it charging for another 20 minutes.
I then woke the device and it showed 1% battery left! While plugged in! I tried to wake it and it died again.
I left it there for an hour or so, turned it back on, 6% battery left, I then turned Airplane Mode on so it would charge faster. After 10 minutes in Airplane Mode, it still shows 6%. It is not charging, I'm using the original HTC charger and cable.
It seems like it is not charging at all when on, and charging VERY slowly when off.
Tried a few tricks I read online, such as holding the volume up + volume down + power button for 2 minutes, but all I got was a steady flashing recovery screen, which says my battery is too low for flashing.
So the difference between mine and other posts is that my stock phone is turning on, but not charging anymore. If I turn Airplane Mode off, it drains itself even while plugged into the charger.
I'm really looking for a solution for this, instead of simply returning it (it's more than one year old, and I bought it overseas) or buying a new phone.
EDIT: Battery Widget app showed Charging Speed: n/a. Testing says battery health: good, 3666 mv, "charging" status
EDIT II: Tried running it in Recovery Mode, got a 3d exclamation point with a phone icon. Rebooted it normally, it turns back on, still not charging. This does not look good at all.
EDIT III: Read about Mr Hofs idea, of running custom recovery via the PC, but I can't get it to connect. Have newest version of Sync Manager yet windows says the "device malfunctioned" and could not be recognized.
EDIT IV: Done factory reset, no luck. Phone is still draining while plugged in. After 8 hours of charging while off, all I got was 40/50% I'm really desperate as the phone is virtually bricked and I need it for work. Willing to tip/donate to whoever finds solution, if that is ok according to forum rules (not sure)
Are you using a stock charger... With at least 1amp output
Sent from my HTC One X+ using xda app-developers app
yokozuna82 said:
Are you using a stock charger... With at least 1amp output
Sent from my HTC One X+ using xda app-developers app
Click to expand...
Click to collapse
I am, HTC charger, 5V, 1A
Back to the blinking led
I tried plugging the phone into the computer's USB port, got the red blinking led again. Held the volume down + power button while connected to the PC and it seemed to be constantly rebooting - windows popped up "device not recognized" several times and the power led started flashing much slowlier. Sometimes the lower leds would also flash. I held it like that for 2 minutes.
After a while the lower lads and the screen backlight lit up. I then realeased the buttons and quickly plugged it into the wall socket.
Now I have the fast blinking again. Awesome. I can't tell if I'm doing it right or brutally murdering my phone
You might just factory reset once your charged as .much as you can. I believe your problem. Is having to do with using or somehow got a bad current or USB port/cord etc. Anyway its software related and a hard reset doesn't help I'd RMA ..you go flashing mods to do yourself probably won't work especially if its hardware. Hope this helps. I say this as it happened to me. I used a lower amp wire charger socket. Same thing happened. After many hours of trying stuff. Factory reset never used bad or non OEM again. But in your case it may be just some IDD quirk. It happens bro. Hope you get it up and running. ..
Sent from my Nexus 4 using XDA Premium 4 mobile app
Droid2drummer said:
You might just factory reset once your charged as .much as you can. I believe your problem. Is having to do with using or somehow got a bad current or USB port/cord etc. Anyway its software related and a hard reset doesn't help I'd RMA ..you go flashing mods to do yourself probably won't work especially if its hardware. Hope this helps. I say this as it happened to me. I used a lower amp wire charger socket. Same thing happened. After many hours of trying stuff. Factory reset never used bad or non OEM again. But in your case it may be just some IDD quirk. It happens bro. Hope you get it up and running. ..
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Left it charging while off overnight, now I have 40% (!) battery. Any time I try flashing the default recovery, it'll show a red exclamation. The PC won't recognize it at all, even with downloaded drivers. And doind all that seem to have drained it to 30%.
Will try to get my important files and then factory reset it.
yukifujita said:
Left it charging while off overnight, now I have 40% (!) battery. Any time I try flashing the default recovery, it'll show a red exclamation. The PC won't recognize it at all, even with downloaded drivers. And doind all that seem to have drained it to 30%.
Will try to get my important files and then factory reset it.
Click to expand...
Click to collapse
Done factory reset, no luck. Phone is still draining while plugged in.
So that's it? Phone is bricked then?
Charge to 100%
Try a different charger
Try flashing a different ROM/kernel
Try flashing RUU
Contact HTC
That's what I would do and the order I would do it in. Leave it alone until it is charged up to 100% before you do any of this though. Even if it takes a week. For all I know, charging to 100% will reset the charging circuit. I doubt it, but who knows.... Stranger things have happened.
ridethisbike said:
Charge to 100%
Try a different charger
Try flashing a different ROM/kernel
Try flashing RUU
Contact HTC
That's what I would do and the order I would do it in. Leave it alone until it is charged up to 100% before you do any of this though. Even if it takes a week. For all I know, charging to 100% will reset the charging circuit. I doubt it, but who knows.... Stranger things have happened.
Click to expand...
Click to collapse
Well this is awkward.
After many days, and since HTC is not present in Brazil anymore, I have no ways of contacting support, I gave up, bought an S4. After two days with my new phone, guess what? The HOX+ charged 100%, and it seems to be discharging normally. GOD DAMMIT.
So, ridethisbike, your suggestion worked, kudos for you and boo for me for not being patient and giving a shot.
Out to look for a buyer then. :silly: