Related
My Rezound is broken
I unlocked and de-sensed it, but that was when the unlock first came out and it's been working fine since, so I don't thing that's the problem.
The phone won't come on, and when I plug it in the charge light doesn't even come on. If I leave it plugged in, then take the battery out and put it back in the charge light comes on for a few seconds, then turns off.
I was at a new years party the night before and I may have laid down on top of it while it was in my pocket, but the water sensors are fine, and I don't remember it ever getting wet.
I notice there are a lot of connections between the phone and the back cover. Is it possible that something could be bent and these connections aren't being made, so the phone refuses to do anything? I tried putting wires across them where they would normally be connected, but it didn't seem to help.
So what do you guys think? Is there something else I can try? I guess if it's totally broken then they can't tell that it's unlocked, so I could try getting a replacement :/
First off, I wouldn't have put any wire across any of the antenna leads like that. Second, if the phone is not coming on with the cover off then you may have another problem. The phone should turn on without the cover. You just wouldn't have signal.
My opinion, try another batter if you know anyone who has one. Or maybe go to your VZW store and see if they will let you use one of theirs. If the battery/phone is too hot the LED will blink orange, once it is cool enough, or full enough to turn on/charge again it will become solid. The fact you get an indication when there is no battery leads me to believe there may be a problem with the battery itself.
with the phone off, pull the battery for several minutes. Then put it back in and plug it in to the charger. Do not try and turn the phone on. If the charge light comes on and stays on, just let it charge for a few hours until it turns green.
I've read of rezounds dying from the battery going completely out. Screws it up somehow. Verizon also has thunderbolt external chargers for 5 bucks. You could use that to charge the battery (it fits), then try and turn it on. If it still won't turn on after charging, put the battery in and try and boot into the bootloader menu (power on and vol down at the same time), from there you can restore your nandroid or flash another ROM if it will boot to it.
I tried leaving the battery out for a few minutes, and then for the rest of the day. No dice in either case. I'll try to get an external charger tomorrow :/
Thanks for the ideas, I'll let you know how it goes.
Mine died overnight. Same symptoms, charging light for a few seconds then nothing. I plugged it in, let it sit for a while (didn't time it, but not more than 15 minutes). Unplugged it, then: held power, volume up and volume down all at the same time. It booted up, as soon as the screen came on, I plugged it back into the charger. Running fine now. Hope this helps someone else.
Went to Verizon today. I bought another battery and ordered an external charger. Swapped in the new battery and the phone started right up
Now I just hope I didn't screw anything up messing with the antenna contacts :/
ministroni said:
Went to Verizon today. I bought another battery and ordered an external charger. Swapped in the new battery and the phone started right up
Now I just hope I didn't screw anything up messing with the antenna contacts :/
Click to expand...
Click to collapse
After getting the new battery, does the orange LED come on while charging the phone when powered off? I replaced my battery after having the same problem and now the orange light does not stay on while the phone is charging when it is powered off. I guess it's no big deal, but it bothers me.
flie4wtguy said:
After getting the new battery, does the orange LED come on while charging the phone when powered off? I replaced my battery after having the same problem and now the orange light does not stay on while the phone is charging when it is powered off. I guess it's no big deal, but it bothers me.
Click to expand...
Click to collapse
Yeah, it still works just fine. I turned it off just now and then plugged it in to check and the charging light came on immediately.
Maybe the battery is faulty or you got a thunderbolt battery by mistake and the phone is confused? Otherwise I have no clue why that would happen :/
I have them same problem. My phone is completely dead, won't turn on and a orange light comes on for 3 seconds and goes away and nothing happens. What do I need to do?
Sounds like your battery died. Pull the battery and let it sit for a few, then try to boot it back up and plug it in immediately.
I was reading a thread about this last night on RootzWiki. Dude did a lot of testing, came to find out it was ClockWorkMOD keeping a completely dead battery from charging at all. Is that the recovery you have? If so, I would put AmonRa on, try that.
Agreed, almost definitely a dead battery. You can try this:
1) Take out the battery and put it back in
2) Hold down power and volume down to enter the bootloader
3) Immediately plug the phone in and leave it there for 10 minutes or so
4) Reboot the phone now that you have enough power to make it through booting
This should work as long as your battery is completely dead.
My suggestion for the future though is to buy an external charger and a second battery. That's what I did, and now any time I accidentally let my battery die I just swap it out and I'm good to go at 100% while the other one recharges. Also an external charger is the easiest way to fix this if your battery is too dead for the above method.
ministroni said:
Went to Verizon today. I bought another battery and ordered an external charger. Swapped in the new battery and the phone started right up
Now I just hope I didn't screw anything up messing with the antenna contacts :/
Click to expand...
Click to collapse
Also, remember that if you are using Clockwork Recovery for some reason that makes the phone not charge when its powered down. I had the similar issue where i couldnt get it to charge or come on at all, i put in a battery from my TBolt and it turned right on, switched Recovery to Amon Ra (Blue one, not the Red one) and from there it charged no problem!
worked...
slim6596 said:
Mine died overnight. Same symptoms, charging light for a few seconds then nothing. I plugged it in, let it sit for a while (didn't time it, but not more than 15 minutes). Unplugged it, then: held power, volume up and volume down all at the same time. It booted up, as soon as the screen came on, I plugged it back into the charger. Running fine now. Hope this helps someone else.
Click to expand...
Click to collapse
this worked for me! thank you!! also to come to think of it, the problem happened after installing clockworkmod recovery. so there certainly seems to be a connection
slim6596 said:
Mine died overnight. Same symptoms, charging light for a few seconds then nothing. I plugged it in, let it sit for a while (didn't time it, but not more than 15 minutes). Unplugged it, then: held power, volume up and volume down all at the same time. It booted up, as soon as the screen came on, I plugged it back into the charger. Running fine now. Hope this helps someone else.
Click to expand...
Click to collapse
This absolutely helped me! I'm really liking this Rezound I picked up but the damn thing is also just very temperamental in general. Still a fantastic underrated device overall though.
My wifes d2g did that once. I ended up taking an old charger, stripping the ends off and taping it to the contacts on the battery for 30 minutes. It charged it up and after that it would charge thru the phone again. A lot cheaper than a new battery.
Sent from my ADR6425LVW using xda app-developers app
This is something odd I haven't experienced with any Android device until now.
Whenever my Rezound battery is depleted to the point where the phone shuts down, I cannot get the device to boot back up again without ADB.
While it's powered off in this state and plugged into charger, it exhibits no charge LED or any other type of activity.
After pressing the power button, it appears to do nothing whatsoever.
If plugged into my laptop USB, the OS detects the device and loads the Debug mode drivers. ADB DEVICES shows the device as being in Recovery, and the device is still completely dark, no video, no backlight, no button lights.
At this point I can ADB SHELL and issue commands, but it can take up to a dozen REBOOT commands (although sometimes on the first or second try) to get the device to do anything other than reboot directly back to dark-screen recovery. I just keep running REBOOT until finally the white/green HTC image appears and the phone boots normally as if nothing was wrong.
Once booted, it behaves perfectly for as long as the battery doesn't die. I can reboot, HBOOT, power off and on, do a Clockwork backup... But, if i let the battery die, I have to ADB REBOOT until it decides to come back to life.
What do you think. Hardware or software issue? Try RUU?
Thanks!
there's definietley a huge problem wtih this phone. i had a guy bring in a phone that died overnight and the same thing happend...he'd plug it into the wall, for 5 seconds it would show orange charging LED, then just shut off..phone wouldn't power on, either. he had it plugged in charging for 3 hours though, and the phone was still dead.
when i switched batteries, teh phone would not go past the white HTC screen. it was just dead. we had to get him a replacement. i'm seriously afraid to shut off my phone now or even let it die. sigh.
Oh yea, mine does the not booting past white HTC screen occasionally between REBOOTs as well. I am disappointed with HTC now, my original AMOLED Incredible was totally rock solid for the 2 years I carried it along 40+ airplane rides to 11 different states. This Rezound craps the bed if you give it a dirty look
Everyone should take a look at this thread in the Vivid forum. People were havin problems with their phone booting into CWM when the battery was dead, me included. Our CWM was updated to support charging and now all is fine. Might be worth looking into.
http://forum.xda-developers.com/showthread.php?t=1429250
Weird, just let my battery die before reading this thread, didn't experience this..
but def not going to let it die again!
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
Got it fixed, turns out my charging hole for the phone was loose and it couldn't charge.
Yesterday around 11pm my HTC Rezound completely ran out of battery. Then this morning I was charging it for like 7 hours, but the phone will not turn on at all, not even the orange light shows. I have tried holding VOL down and POWER but nothing happens. When I keep clicking the POWER button, the orange lights comes on for like 3 seconds, and then i goes out. Please help me fix this, thanks
MY PHONE IS ROOTED AND UNLOCKED!! JUST SAYING
izink said:
Yesterday around 11pm my HTC Rezound completely ran out of battery. Then this morning I was charging it for like 7 hours, but the phone will not turn on at all, not even the orange light shows. I have tried holding VOL down and POWER but nothing happens. When I keep clicking the POWER button, the orange lights comes on for like 3 seconds, and then i goes out. Please help me fix this, thanks
MY PHONE IS ROOTED AND UNLOCKED!! JUST SAYING
Click to expand...
Click to collapse
try a different battery. it sometimes happen the battery get way to low and it does now want to charge.
If you have CWM as your recovery, that's the problem. Get some juice in your battery some other way, and flash Amon Ra.
twolasrnames said:
If you have CWM as your recovery, that's the problem. Get some juice in your battery some other way, and flash Amon Ra.
Click to expand...
Click to collapse
I already flashed Amon Ra on my phone like 3 weeks ago. What should I do from there??
izink said:
I already flashed Amon Ra on my phone like 3 weeks ago. What should I do from there??
Click to expand...
Click to collapse
Find someone with a rezound(verizon store maybe?). Try there charged battery. Boots your good if not your phone is fubar. Work forward from there.
Sent from my ADR6425LVW using XDA
Don't know if you found a remedy yet, but the same happened to me yesterday. Ended up being the battery. I brought it to Verizon and they replaced it.
Sent from my ADR6425LVW using XDA
i had this same problem look you going to need to to on a pc and use cmd
to fix this battery death ....once you have your cmd open type in adb reboot
then wait a bit it will turn on then give it a bit for it to charge then go back to cmd and type adb reboot bootloader and let it charge then reboot you phone normaly as it should do
Thanks.
cflo360 said:
i had this same problem look you going to need to to on a pc and use cmd
to fix this battery death ....once you have your cmd open type in adb reboot
then wait a bit it will turn on then give it a bit for it to charge then go back to cmd and type adb reboot bootloader and let it charge then reboot you phone normaly as it should do
Click to expand...
Click to collapse
This actually worked. But a better look for telling people is:
I had the same problem. To fix it it:
Plug the phone into the computer, and load up command prompt.
Type in "cd [directory of adb.exe]"
Type "adb reboot"
It should say "daemon not running. Starting it on port XXXX"
Then "daemon started successfully. After less than a minute, your phone will turn on.
Leave it there to charge for a little while, then, type:
"adb reboot bootloader". From there, let it charge.
After it has charged, reboot your phone as you normally would.
The only part of these instructions I couldn't get to was getting the phone to reboot properly.
This has worked for me so far, and it was pissing me off the whole day that it wouldn't charge.
For what it's worth, I bought a bricked phone from Craigslist and just keeping the battery out of it for 48 hours fixed it. Otherwise the phone was completely dead (No nothing, no charging, LED, ADB, NOTHING)
So if you have a bricked phone, you may want to try this too.
GoghAndroid said:
For what it's worth, I bought a bricked phone from Craigslist and just keeping the battery out of it for 48 hours fixed it. Otherwise the phone was completely dead (No nothing, no charging, LED, ADB, NOTHING)
So if you have a bricked phone, you may want to try this too.
Click to expand...
Click to collapse
OMG... I left my battery out for 12 hours... now I have to do it for 48 hours??? Is that extra time going to make a difference? All the things that work for other people don't work for me and it makes me very, very sad.
My Rezound was running TWRP and CM10.1. It had an extended battery in it. I ran the battery down and it wouldn't charge, so I put the original battery back in. It was okay for a couple weeks until I let that run down and it wouldn't charge. I ordered a Kidigi dock with external battery charger and the Rezound sat in a drawer with no battery for a week while I waited for the dock to arrive from Hong Kong. The dock came in yesterday. I charged the original battery in it, then put it into the Rezound and...nothing. I can't get the LED to light or anything. I connected the Rezound to my PC and ran ADB DEVICES, but my PC finds no devices. I've got a Mugen extended battery coming in the mail. I'll give that a try, and I'll also drop into a Verizon store and see if they have a charged battery I can try in my Rezound, but I've pretty much run out of hope for this phone.
I usually let my phone all night on the charger and when I wake up check emails, news etc.
So the other day when I waked up, open wifi, check email ... phone started heating up, really heating up, almost too hot to touch and also seemed to drain the battery . So, closed the phone immediately and took the battery off. After that it would start the endless reboot cycle every time I put the battery in and plug in the charger. It won't charge at all even if I tell it to shutdown through fastboot. Bought a battery through ebay which came half charged, managed to flash a stock rom through hboot but nothing changed and the battery is drained now and can't try anything else. Also I have to mention that I couldn't access recovery as it would reboot as soon as I made that choice in the hboot menu. Current status is that as soon as I plug in the charger, red light turns on for one second and than the phone seems to try to boot and well endless cycle of that.
Phone was s-off hboot 1.49 and some recovery which I can't remember.
So... is it dead?
seem like you can boot into bootloader/fastboot. But revovery is a no go? Recovery does off mode charging, so if it's bad you won't charge. That would be a software issue, as for hardware I don't have a clue. If you can power up with cable, then I'd say maybe it's only software. I'd try an ruu, back to stock and see if that fixes.