Related
So I am on my second battery right now. The first one just decided it shouldnt turn on. I could plug the charger in and the notification light wouldnt turn on, pull the battery and it would. Well, now my second battery is doing the samething. I had left it on the charger while I was outside doing stuff, came in in the afternoon, dead phone. Pulled and replaced battery a few times, phone still wouldnt turn on. Then I plugged in the charger and no notification light would come on. So I finally pulled the battery and with the battery out I plugged in the charger and then the notification light would come on. What the hell is going on here?
Anyone else have these problems? Now I have to drive 30+ miles one way to my nearest Verizon store to replace this damn thing and I am not happy about this one bit. Anyone on here have any suggestions for me?
remmy5r said:
So I am on my second battery right now. The first one just decided it shouldnt turn on. I could plug the charger in and the notification light wouldnt turn on, pull the battery and it would. Well, now my second battery is doing the samething. I had left it on the charger while I was outside doing stuff, came in in the afternoon, dead phone. Pulled and replaced battery a few times, phone still wouldnt turn on. Then I plugged in the charger and no notification light would come on. So I finally pulled the battery and with the battery out I plugged in the charger and then the notification light would come on. What the hell is going on here?
Anyone else have these problems? Now I have to drive 30+ miles one way to my nearest Verizon store to replace this damn thing and I am not happy about this one bit. Anyone on here have any suggestions for me?
Click to expand...
Click to collapse
If you bought it from Verizon and not second hand, then you have 1 year warranty. I suggest you call Verizon's customer service and speak with them and get a replacement sent. I've done this multiple times with just about every phone I've had. 1800-922-0804 is what I dial. to get to them, press 0, then press 0 again, and it will ask for your account password, then a rep will get on the phone.
best of luck.
If the phone is older than 30 days, or maybe it's 14 now with Verizon, they give you a refurbished phone, if you are over that period and went to the store I'm pretty positives all they would do is order you the replacement refurb phone. 30+ miles each way is a hike, save the gas money
remmy5r said:
So I am on my second battery right now. The first one just decided it shouldnt turn on. I could plug the charger in and the notification light wouldnt turn on, pull the battery and it would. Well, now my second battery is doing the samething. I had left it on the charger while I was outside doing stuff, came in in the afternoon, dead phone. Pulled and replaced battery a few times, phone still wouldnt turn on. Then I plugged in the charger and no notification light would come on. So I finally pulled the battery and with the battery out I plugged in the charger and then the notification light would come on. What the hell is going on here?
Anyone else have these problems? Now I have to drive 30+ miles one way to my nearest Verizon store to replace this damn thing and I am not happy about this one bit. Anyone on here have any suggestions for me?
Click to expand...
Click to collapse
Just had my Rezound battery die last night. It was freezing outside and my battery was at 1%. The screen just went blank. When I got home, plugged in the charger. The notification led came on for 3 seconds then went back off again. Tried several chargers I had and pulling the battery and plugging it in.
Weird.
Verizon has the 14 day return/exchange policy now. I was at 12 days so I just went in and they replaced the battery with a brand new one from a Rezound box. I assume they will send that unit back RMA. My phone works now.
You're not the only person having battery death issues. Not sure why this is a problem on the Rezound. I recently purchased an extended battery ironically. It will be arriving tomorrow.
Here's to hoping that it won't die. I should buy some spares just in case. Make sure you call customer service and report the issue. It is tracked.
I was also having an issue charging from a dead battery (would charge just fine otherwise). The charging indicator would not stay lit, but after giving it 10 minutes or so, repeated attempts to power on would eventually work and then it would charge normally.
Had this happen several times and then reflashed the stock image. Seems to be working as it should now. However, when I got my phone it had a dead battery it wouldn't charge. So we'll see what happens.
Note: was running Senseless 1.0 and de-bloated. Stock rom kernel. If it matters....I probably didn't get a clean install when doing it all.
Rezound has a known issue that if the battery dies to far you'll need something else to charge the battery. Some people have used their old thunderbolts to give it a pre charge, buy the stand alone charger from Verizon. Or just don't let your phone discharge tthat far.
Sent from my ADR6425LVW using XDA App
nosympathy said:
Rezound has a known issue that if the battery dies to far you'll need something else to charge the battery. Some people have used their old thunderbolts to give it a pre charge, buy the stand alone charger from Verizon. Or just don't let your phone discharge tthat far.
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
Good to know - is that all or most Rezounds? Because I wonder if I should swap mine while I still can.
Like I said, I was having that issue and after flashing the stock RUU (updated one, .6) my phone is charging a dead battery just fine (2 for 2 so far, fingers crossed).
Actually brand new in the store mine had a dead battery and it would not charge, so they gave me a new battery. Perhaps there was a fix in that updated RUU. It's just a suggestion - after I confirm this works consistently I'll see what happens with some other roms.
Alternatively, it's also possible the stock RUU doesn't let you drain the battery as far as the roms do. I was able to power back on several times until it finally wouldn't (and no led flashing at that point), but now it charges from there.
Yea, I woke up one morning and my phone was deader than a door nail. Popped on the charger and no notification light, called Verizon to whine and prepared to stop by the store to get a replacment battery. However just for kicks I plug the phone back on the charger (ok my laptop) and after 1/2 hour the notification light popped back on and the battery started to charge. Now Prior I was having a high rate of discharged getting about 2 hours of use and 5 on standby (airplane on, WiFi and Data off) and still having the high rate of discharge. I started to investigate why the phone was getting hot and discharging so fast. Now I couldn't fine the culprit (I think WIFI was the cause) but I just did a factory reset, reloaded my rom and kernal and poof, everything return to normal including much longer discharge rates and I'm much happier now (Adult Beverages and household chemicals indigestation).
If you go to HTC's website it actually has a faq on this. Their response goes pretty much like this. If you drain your battery till the phone shuts off, plug your phone in. It will flash the notification light then there will be no charging light. The light could take 20 minutes or more to turn on. I also had this problem like you guys but just put it on charge over night and it will be fine. Just don't kill it to 0 anymore.
Found the Quote: My phone won’t power on. What can I do? close
If your phone will not power on, your battery may be drained or not seated correctly.
Tips:
If the battery is completely dead, the phone will need to charge for a few minutes and then should power on once this happens. When plugging the phone into the charging, the notification light may not light up immediately as the battery is completely dead. Let it charge for about 20 minutes before trying to power on.
Make sure you are using the AC charger that was supplied with your phone
Sent from my Rezound using xda premium
battery discharges while plugged in and using it
ok, so this happened with the stock rom, and two other roms i had.
What would happen is if you plug the phone in, and use it, you would expect it to charge while you are using it. It did on my dinc. it actually discharges while you use it and it is plugged into the supplied charger.
This is not a good thing. I am wondering if anyone else is having a similar experience.
One interesting side note.
I installed rezrom recently, and after the initial install i didn't experience this problem and got a 24 hour charge out of the battery. Now on my second charge only lasted 7 hours, and i get that drain while plugged in again.
Are you using the stock charger or a different one? You might not be charging at 1amp.
Sent from my ADR6425LVW using xda premium
I am using the stock charger. I have two actually, one from my dinc, which also supply 1 amp of power
That's really crappy and definitely an issue they need to address. My Rezound sucks on the battery like a wine-o on a Friday night, but it's never gotten to the point of blacking out.
I am just interested to know if anyone else is experiencing this issue of it being plugged in and not charging when u surf the net, but actually discharges.
The whole issue of it not powering up for 15 minutes after it dies is a bunch of crap too. my dinc does not do this, and god forbid that my phone dies in an emergency situation and i need to get a hold of someone fast!
oh i forgot to add that i called VZW and complained about this, and they going to send a new battery. Something tells me this won't resolve this issue though
I have the official HTC 2750 battery and Its been good except 2 mornings I woke up to an unresponsive phone with no charge notification after plugging it in.. Pulling the battery and reinstalling let me start the phone up. I have had this phone/battery combo for 2 weeks.. should I try to get a replacement battery or is this normal. There have been two different answers here and I want to do the right thing here...
Sent from my Xoom using xda premium
UgXvibe said:
I have the official HTC 2750 battery and Its been good except 2 mornings I woke up to an unresponsive phone with no charge notification after plugging it in.. Pulling the battery and reinstalling let me start the phone up. I have had this phone/battery combo for 2 weeks.. should I try to get a replacement battery or is this normal. There have been two different answers here and I want to do the right thing here...
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
So you are saying the phone died, then refused to charge on the extended battery?
carm01 said:
So you are saying the phone died, then refused to charge on the extended battery?
Click to expand...
Click to collapse
Yes, exactly. Not sure if it was entirely discharged. I'll leave it off the charger tonight and see if it does it again by morning. I'll let you know battery % once I get it booted.
Sent from my ADR6425LVW using xda premium
From the beginning, phone was on charger, charging then came back later (phone still on charger) no led, nothing, phone wouldnt turn on.
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 I got my Amaze on Friday, rooted and installed Energy Rom on Saturday, and phone just died on me on Sunday.
I was in the middle of playing Scramble with Friends and phone froze up on me. I had to take the batter out to reset it since the power button was not responsive. After I pulled the battery and put it back in, the phone would turn on.
So i read and read and found out people usually bought new batteries since the most likely culprit was a dead battery. I have a friend with the same phone and tried his battery. I saw the HTC Logo come on for a brief second and then that was it, nothing else. Phone died again and did not turn on (under his batter). I recharged my battery in his phone and tried that as well, but no luck.
Any ideas what went wrong and what I can do to fix this?
The phone is completely dead and not turning on. So that means I can't get into bootloader and recovery.
About Phone:
Unlocked Bootloader
TWRP recovery
Faux Kernel
ENERGY Rom
Any incite on this would be great. Thanks in advance!
Plug it in to the wall charger for 30-45min. Unplug and pull battery again. Put battery back in and you should be good...
Don't be alarmed if the orange led light flashes... It's normal when the phone dies. Be happy you're using twrp and not an old recovery that doesn't have charging while off
http://forum.xda-developers.com/showthread.php?t=1561104
Amaze Bricked
http://forum.xda-developers.com/showthread.php?t=1575191
[Q] Bricked Amaze Won't turn on
I hope that's XBoarder's TWRP 2.0.0...
Sent from my HTC_Amaze_4G using Tapatalk 2
Thanks, i actually read those threads before i posted. I think there are more threads about that but i tried all options and none seemed to work. I will try plugging it in the wall and pulling battery out but the battery is at a 100% charge right now (i can confirm from a friends phone). However, if its just a glitch, then i will try the wall charger trick.
Thanks.
ars88 said:
Thanks, i actually read those threads before i posted. I think there are more threads about that but i tried all options and none seemed to work. I will try plugging it in the wall and pulling battery out but the battery is at a 100% charge right now (i can confirm from a friends phone). However, if its just a glitch, then i will try the wall charger trick.
Thanks.
Click to expand...
Click to collapse
Once you get it booted, I recommend 4EXT recovery... But that's just my opinion
Sent from my HTC_Amaze_4G using Tapatalk 2
Thanks - tried the battery solution but unfortunately it didn't work out for me. Phone just refuses to power up.
Assuming its an official brick.
i have a similar problem, well my battery had charged and running fine for several months, so i unplugged the battery to put my sim on it, and plug it back in when it was booting up it froze on the boot logo, so i took off the battery again so i can reboot it
and ever since it wont come back on, wont either go to the bootloader, so i let it charged all night and nothing happen no led blinking or on, so got my friends amaze's battery to test and it would not do anything at either, right now i am waiting for my replacement, but i hate the fact that this had happen to me
oh wow - well i ordered a replacement as well. I really hope it doesn't come down to a software issue and they don't end up covering the device since it has been rooted.
If the phone is completely dead and non-booting, there's no way for T-Mobile to determine if it's rooted or not. Only until it gets back to HTC to be refurbished could they (HTC) find out but at that point it won't matter to anyone anyhow.
And it couldn't possibly be a software issue. There's something physically defective inside the device that caused it to die.
htc amaze 4g refuse to turn on.
hi all, i'm a newbie here, though i have always loved the XDA. I unlocked my bootloader last night, downloaded and reinstalled my fav apps since i didnt do a backup. while i was downloading the XDA app, my fone freezed and eventually went off. When i tried to get it back on, it got stuck on the white htc screen and later went off after some seconds. It has refused to come on till the time of this post. i really need urgent advice.
I was yet to install a recovery software before the tragedy occurred.
Updated "Please help: VZW S4 not charging..." (The refurb/replacement is busted)
First of all, big thanks to this whole community and the wealth of info that led me through my first time rooting and flashing ROMs. But now on to the sour part (search didn't bring up anything useful to my situation).
Short history of phone in case it helps:
I've been rooted since June (rooted on MDK). I've been on the CM 10.1 and then 10.2 nightlies ever since. I've followed all directions, and am glad to say that I had a great experience (a few hiccups from dirty flashing a few times, but nothing that couldn't get sorted). Last ROM I was on was CM 10.2 nightly from 2013-10-11.
Anyway, last night my battery gets low, but I didn't charge it right away. It got down to about 8%, and then I try to charge, but the battery icon doesn't indicate charging. Indeed after a few minutes fiddling, the % drops to 7%. Trying to charge it while powered off caused the phone to vibrate once every 5-10 seconds or so, but no LED or on-screen indication it's charging. I tried my wife's S4 charger and cable. Same result, not charging. I restored to a previous CM nightly backup I had from September. Same result, still not charging. I restored to my rooted stock ROM backup made right after I first rooted in June. Same result, not charging. Charging from the wall or PC doesn't make a difference. I ended swapping batts with my wife, using her stock never-been-rooted S4 to charge my batt, which worked just fine.
The USB port on my phone does work since I could see the device in Odin. Tried reflashing the stock kernel. Still not charging. I spent the rest of last night restoring to out-of-the-box stock. Now I'm back to a completely stock, unrooted S4 (still on MDK kernel, haven't accepted update to ME7), and it still won't charge. No notices or anything that the charger is connected. Except this morning, for no reason discernible to me, I now get the following warning message when I connect my or my wife's charger:
"The connected charger is incompatible with this phone. To prevent damage to your phone, charging has been stopped. To continue charging, use the original charger and cable that were provided with this phone."
Thoughts, please? And thanks in advance to you all.
Update 1 at 2013-10-13T17:30EDT
So I did some more digging and came across what looks like a similar problem (that's what I get for not using Google for search anymore). Sorry, can't post links yet.
forums.androidcentral.com/rogers-samsung-galaxy-s4/297925-samsung-galaxy-s4-not-charging-grey-battery.html
The biggest difference is that I don't get the grey battery symbol when plugged in while powered off, just the cyclic vibrating. And mine doesn't charge at a reduced rate at all (I lost 7% battery in 45 minutes while plugged in and powered off due to all the vibrating).
Further, my "incompatible charger" warning has ceased. I'm just back to the phone not recognizing a charger is plugged in at all. Phone still talks to my PC just fine though.
Is it likely I need to replace the USB charging port flex cable as suggested in the Android Central post? Thanks for anyone reading and pondering.
Did you try to flash back to stock?
kheltek said:
Did you try to flash back to stock?
Click to expand...
Click to collapse
Yes. I flashed via Odin back to unrooted stock (MDK kernel) and stock recovery, which is the phone's current config. I haven't yet done the ME7 update, but it auto-downloaded today, just haven't installed it.
How long have you had the phone? My suggestion would be to make another backup and put it on your computer. Then restore back to full stock, no root or anything. Take it to Verizon / Best Buy and tell them it's not charging. Hopefully it's not water damaged.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Quentin.Sheley said:
How long have you had the phone? My suggestion would be to make another backup and put it on your computer. Then restore back to full stock, no root or anything. Take it to Verizon / Best Buy and tell them it's not charging. Hopefully it's not water damaged.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've had the phone since the end of May (so I've owned it 4.5 months). Since I've already restored to full stock, I'm thinking tomorrow I'll take it to a VZW store near me to see what they say. Is Samsung's manufacturer warranty handled through VZW? Or do I deal with Samsung directly? Note, I have no extra insurance/warranty on the phone.
That should be manufacture warranty and you normally have1 year from purchase. Good luck and again just ensure you completely wipe it off all root and custom Roms. They'll try to blame it on that.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Back to VZW to replace the replacement phone
Update:
I went to my local VZW store on Monday and they tried cleaning the USB port. No luck, so they shipped me a refurb since this is still under the 1 year hardware warranty. I paid the extra for overnight shipping. My refurb phone arrived yesterday. I moved over my sim, micro SD, and battery from the old phone to the refurb/replacement phone, and plugged in the wall charger. BOOM, battery starts charging no problem :victory:. I spent last night getting my phone all set up. I also checked and this phone has the ME7 update so no more CM or any other ROM for now :crying:.
But otherwise, everything looked good with the replacement device...until this morning. I had the phone powered off all night, tried turning it on this morning and it won't turn on. Won't boot normally, won't boot into recovery, won't boot into download. Tried a battery pull...no luck. The phone had like 95% battery when I shut it off last night. Now, when I plug in the wall charger, the phone buzzes once, the grey battery icon with the circle shows up for 10-15 seconds, then the screen goes blank, then that sequence repeats.
Back to VZW today to get the replacement phone replaced .
dang...you have some bad luck. I had some similar issues and the phone seemed to fix itself?? Did not want to lose custom recovery, so actualy ordered an external charger and two batteries and of course the day the batteries came, the phone started charging normally again. Anyways...good luck...hopefully the new device wont have the newest update (which i dont think it's ota yet...just over wire). Dont let the store update anything at all or you may not even be able to root!
Hey guys,
So I've had my DNA for almost 1 1/2 years, and just recently decided to root and flash CM 11 and CWM recovery onto it. Now, everything went fine, except a month later, I was listing to music on Pandora, and my phone crashed (it has a few times before since it wasn't a stable release, but always boots back up in like 5 mins), but this time it never booted back up. I let it sit in the charger over night, but got nothing, not even an orange light. So I decided that, since it was broken anyways, to go ahead and take the entire phone apart and reassemble it. And after the second time, it turned back on (by plugging it into my computer at the same time of holing down the power button). But an hour later, the battery died, and I couldn't get to the charger in time, so it shut off. Now, I've tried everything that I have before, and also took it to a repair shop, but never got any life out of it again. Does anyone have any ideas about whats wrong? Is it fixable? I've also herd of a type of USB jig for Samsung phones that can put an unresponsive phone into 'download mode', is there some kind of equivalent of that for the DNA? Any help is appreciated!
Thanks!
Cman1468 said:
Hey guys,
So I've had my DNA for almost 1 1/2 years, and just recently decided to root and flash CM 11 and CWM recovery onto it. Now, everything went fine, except a month later, I was listing to music on Pandora, and my phone crashed (it has a few times before since it wasn't a stable release, but always boots back up in like 5 mins), but this time it never booted back up. I let it sit in the charger over night, but got nothing, not even an orange light. So I decided that, since it was broken anyways, to go ahead and take the entire phone apart and reassemble it. And after the second time, it turned back on (by plugging it into my computer at the same time of holing down the power button). But an hour later, the battery died, and I couldn't get to the charger in time, so it shut off. Now, I've tried everything that I have before, and also took it to a repair shop, but never got any life out of it again. Does anyone have any ideas about whats wrong? Is it fixable? I've also herd of a type of USB jig for Samsung phones that can put an unresponsive phone into 'download mode', is there some kind of equivalent of that for the DNA? Any help is appreciated!
Thanks!
Click to expand...
Click to collapse
It's your recovery. Try the most recent twrp instead. I've had this issue with my rezound and DNA and it's scary for sure. If you find a way to power on your device immediately change recoveries. Some are touchy on charging a dead phone.
iHateWebOS said:
It's your recovery. Try the most recent twrp instead. I've had this issue with my rezound and DNA and it's scary for sure. If you find a way to power on your device immediately change recoveries. Some are touchy on charging a dead phone.
Click to expand...
Click to collapse
Would maybe trying to charge the battery outside of the phone work? If so, how would I go about that? A friend of mine has a Lipo charger for RC cars, could I make some kind of jig to charge the DNA's battery with that?
EDIT: Found out he has a supper high end lipo charger that is programmable, so could I charge it with that if I can get the battery hooked up right?
Cman1468 said:
Would maybe trying to charge the battery outside of the phone work? If so, how would I go about that? A friend of mine has a Lipo charger for RC cars, could I make some kind of jig to charge the DNA's battery with that?
EDIT: Found out he has a supper high end lipo charger that is programmable, so could I charge it with that if I can get the battery hooked up right?
Click to expand...
Click to collapse
You could to irreversible damage to the battery if you do the settings wrong, or hook it up incorrectly. You can get a replacement battery online for pretty cheap. I suggest that than possibly having a small explosion from charging a battery in a way not suggested. After you get the phone back on, immediately fastboot flash a different recovery as @iHateWebOS said.
New batteries come half charged (40-60%) out of the box as that is the suggested storage capacity for batteries to ensure long shelf life.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Okay, just ordered a new battery, should be here between the 10th and the 20th. Hopefully this works
HOLY ****, IT WORKED!!!!!! My DNA booted!!! Thanks so much guys!!!! Which recovery would you guys recommend?
EDIT: So I flashed on twrp, and it won't charge with the original battery in it, so does that mean if the new battery dies, my phone won't boot again? If so, which recovery should I flash to prevent that?
Okay, update. So I tried updating my DNA to the latest snapshot of Cyanogen mod (was at m6, going to m11), and the recovery failed, so now I'm soft-bricked... I'm trying to flash on the old m6 snapshot I have on it, but it keeps failing. Also, the recovery won' t support external storage, so I can't flash on m11 from my flash drive... What should I do?
EDIT: Okay, just found out that I was running the 2.4 beta of twrp, so I'm trying the latest 2.8.0.2, Ima see if that does anything
EDIT: YAY, flashing the latest recovery worked!! so now everything is working properly, except the digitizer, since I ripped the ribbon cable a little, but I already ordered a new one
Okay, so I accidentally let the battery drain, and now I'm at square 1 again. Does anyone have the pin-out schematics for the battery on the DNA so I can make a jig to charge it?
Thanks!