Related
I think I just figured out how to fix it!!!!!!! I was tinkering around and got my red light brick to turn on!!!! I'm not sure exactly what fixed it so here's everything I did-
1. Removed the storage & sim cards.
2. Took off the backplate.
3. Removed the battery.
4. Bent these 2 pins up a little bit:
5. Put the battery in at an angle, so that the power leads were connected, but the metal shielding plate on the back of the battery was not touching:
6. Hit the power button (with the battery still "halfway" installed) Bam, green light of life.
Somebody please confirm this. Meanwhile I'll be copywriting this process so anyone who performs it owes me 10 bucks
So my replacement Tilt isn't working either, so they're overnighting me a third one. In the meantime, I haven't sent back my original (RLoDed) Tilt, so I thought I'd play around with some of your theories.
skuzz said:
Another thought I had. After the tilt goes into red brick death mode, has anyone tried plugging it into power, battery installed, and then holding down power+camera(all the way) and then pushing in the reset button on the bottom? This may trigger it to go into flash mode - although I kinda doubt it'll work. Worth a shot! Might be able to reflash it back to life! Holding down power and camera while it boots is how you manually force it to get in the Red/Green/Blue firmware flash mode. If it let us do that much when the device bricked we might have a snowball's chance in hell of getting them working. I didn't think of trying it before I returned mine tho. D'oh!
Click to expand...
Click to collapse
I didn't know what to try besides installing the battery and SIM card and trying to push down the power, camera, and stylus buttons (I knew I was doing it correctly, because I had to use this to return my second Tilt to factory specs). No response whatsoever! This thing is deader than a doornail. Except for the red LED, of course... that works REALLY well whenever it's plugged in.
sWuRv said:
I think I just figured out how to fix it!!!!!!! I was tinkering around and got my red light brick to turn on!!!! I'm not sure exactly what fixed it so here's everything I did-
1. Removed the storage & sim cards.
2. Took off the backplate.
3. Removed the battery.
4. Bent these 2 pins up a little bit:
5. Put the battery in at an angle, so that the power leads were connected, but the metal shielding plate on the back of the battery was not touching:
6. Hit the power button (with the battery still "halfway" installed) Bam, green light of life.
Somebody please confirm this. Meanwhile I'll be copywriting this process so anyone who performs it owes me 10 bucks
Click to expand...
Click to collapse
I appreciate your enthusiasm, but the only thing I can confirm is that this did NOT work on my RLoDed Tilt. Tried it several times in various ways. I think you just seriously lucked out!
As such, I'd also have to vote against stickying this... for now.
Best of luck, all... if not actually in fixing your RLoDed Tilts, then definitely in avoiding the $500 service fee if AT&T discovers we voided our warranties.
alright i will confirm this too....my phone was truely RLOD..... i did the same thing that these guys did just jammin the battery in and out and it "jump started the phone"
exact process used
Moto Razr charger
hold down power button
"bounce" battery on and off the contacts for the battery a good 100 times or so
green light apeared after the red light started to flicker a little bit..... tis as if you were giving the phone CPR or something
im not going to call this a fix all i know is that the phone was RLOD and now it is working....battery is at 54% right now and i will post back in a bit to see if it has risen at all....
no smell arising from device
running origional rom but have had other roms on there (alex's)
hard SPL still installed on device
SPB phone suite is the last software that was installed on the device
reg tweaks installed as well, the usual ones no sms, hsdpa enabled blah blah blah
that is about all i can provide....the unit was on the computer overnight charging....when i woke up it was RLOD....and i was sad....i did have the ATT store replace the battery for me as well dunno if that had anything to do with the issue...
in the time that it has taken me to write this the battery is now at 55% so it is charging.....on wall charger with MOTO razr charger
ok lets take a little closer look at what happened within the past little bit....
after gettin the device all up and running it was behaving very oddly.... it would go through multiple attempts to connect to the data network for various reasons....after showing that it was at 55% on the charger it went back down to 54%... i pulled it off the charger and took it into the other room to do something......within 10 min it was down to 46%....now having a data connection my blackberry connect should have a valid network connection....but it did not... not sure why...
the best that i can conclude is that it was trying to connect to so many things all at the same time that it exhausted its self that fast....
so the question is how many people out there that have RLOD are running the BB connect software on there devices and have made REG edits to the data connection time outs and the HSDPA mod availability
editing those settings together may confuse the device and make it think that it has to connect to too many things at one time....
just another thought process that i thought that i would throw out there...
here are some things on the my device that would use the DATA connection and automatically initiate the connection on the device rather than you opening a program forcing it to connect such as Internet explorer
GPS update
HTC home weather tab
SPB weather tab
Blackberry connect
SPB insight....RSS Reader
text messages going in and out....my phone sees quite a few of those
Edit/Delete Message
There have been a few other people who have now fixed their RLOD's. Confirmed it was done by messing about with the battery. If you have revived yours, please post your method in here so we can compare them and eventually pinpoint the fix. Thanks.
i had the same prob..took out the batterly wiped the four contact points on the phone (might of pushed them down or up) and put battery back in and worked..
I believe sWuRv was onto something. My Tilt had the RLOD today. I tried everything, even what he suggested above to no avail. So I called warranty and got my replacement on it's way, express shipping waved and all. So I decided to everything I could think of to try and get the thing back on so I might be able to back up my data again.
I started fooling with the battery, like sWuRv suggested but I moved it all around at 45 degrees or so pushing the power on button. I noticed while it was plugged to the USB with red light on that every now and then the red light would flash when I moved the battery so the contacts moved (while holding the battery at that 45 degrees). I started getting the light to go yellow but it would not stay. So I unplugged from the USB and kept trying it while pushing the power button. It eventually started and I was able to back up to my SD card. One thing I can tell you is that this process caused the phone to get hot and smell like electronics burning a little. There is definitely a power problem inside.
I have no idea how or why this worked but it did. I think I will still take the replacement even though I have to figure out how to swap my fancy invisible armor clear protector skin.
I'll try and update on whether this phone dies again or what until I get the new one.
rlod
I tried messing with the battery in a variety of ways for 30 minutes with no sucess. RLOD stayed solid.
RLOD
Holy shoot............After bouncing my battery up and down about 40 times my phone came to life!!!!!!!!!!!!!!!
Reseating the battery and/or sim/storage cards is hardly a revolutionary procedure. Its Cellphone 101.
you guys are LIFE SAVERS. I have been on this forum for about a month now and I finally found a reason to post. I haven't posted because I always find my answers. I just wanted to thank everyone, as I have been on the phone with Amazon.com (where i got my tilt), went into an AT&T store and was on the phone with HTC tech support ALL day trying to resolve my red light issue. Unbelievable that all I needed to do was give it some "battery CPR":
UGHHHH. Well i found reason to make post #2. The fix lasted less than 5 minutes.
this did not work for me
These stories remind me off all the bad batteries/no powerup of my Motorola Q and those of others. My mother is on her 4th Q and I know its the battery, but the store just swaps out the whole phone. I've seen batteries last as little at 2 weeks, especially if let run down to empty at any point.
My questions are, is this just a bad battery problem? Does anyone with RLoD have a spare battery to try? If these batteries fail in the shorted condition, will they over draw power from the phone and mess up the charging circuit?
Roto
"Not the Mama", OR, NOT THE BATTERY
rotohammer said:
These stories remind me off all the bad batteries/no powerup of my Motorola Q and those of others. My mother is on her 4th Q and I know its the battery, but the store just swaps out the whole phone. I've seen batteries last as little at 2 weeks, especially if let run down to empty at any point.
My questions are, is this just a bad battery problem? Does anyone with RLoD have a spare battery to try? If these batteries fail in the shorted condition, will they over draw power from the phone and mess up the charging circuit?
Roto
Click to expand...
Click to collapse
I certainly don't believe it's a bad battery problem. I had 2 spare batteries, fully charged with separate docking charger - none of the 3 batteries made any difference once I got the RLOD.
cushcalc said:
I certainly don't believe it's a bad battery problem. I had 2 spare batteries, fully charged with separate docking charger - none of the 3 batteries made any difference once I got the RLOD.
Click to expand...
Click to collapse
Very good, thanks for the insight!
I finished a call yesterday and then dropped my phone on to the pavement cos I was a bit drunk... Anyway this caused my phone to go from working fine (all be it with pants battery life) to just flashing the red light. Fixed it today. I tried the methods prescribed in this thread without success although I did not persevere for very long. I then put a spare battery in to the phonea and bingo the orange light comes on, phone boots up and it's now happilly charging. Note that I charged the old battery for several hours before trying the fix. Pity nobody seems to know what the problem actually is. I wish HTC would let us know....
sWuRv said:
There have been a few other people who have now fixed their RLOD's. Confirmed it was done by messing about with the battery. If you have revived yours, please post your method in here so we can compare them and eventually pinpoint the fix. Thanks.
Click to expand...
Click to collapse
I had a similar problem with my old iPAQ hw6515, and a Motorola V3. The contacts on the battery don't spring forward as well on an older phone as they do when it was new. I shimmed the battery. I did this by taking a business card and holding it against the opposite side of the battery from the contacts I traced the battery's profile and cut it out. I scotch taped my new shim to that side of the battery, then re-inserted it. This forces the battery up against the contacts better and in many times resolves inoperable phones, failure to charge, and spontaneous rebooting issues.
-Jay
My replacement tilt (first one had a bad USB connector) died Sunday.
Had it on the charger, looked down, red LED. Back of phone was pretty
warm. Pulled the battery, SIM, memory card, slammed the battery onto the
battery contacts rapidly 5-6 times, put the SIM, memory, battery back into
it, and it charged up. Did a hard reset. Battery was 100% charged, I turned
it completely OFF when I went to bed. Got up, battery was 0% drained!
Red LED again. Did the rapid thingy with the battery again, orange charge
light came on.
Called at&t warranty replacement. When I told her I had a red LED, she didn't
even ask me to do anything else. She just asked for the IMIE number and shipped me another one.
Maybe the 3rd one will be the charm LOL.......
I'm beginning to think that HTC doesn't stand for "high tech computes" but
"high tech CRAP"....
Maybe you guys got the margin of error productions? I know its really unlikely that you could get them again after a replacement but it is possible, and it maybe your computer. What do you think could be making this things go crazy? Overly protective anti-virus, I know, I know but it could do things secretly and screw around like mine does and wont let me into sites I have been on before on the same app no changes . . . Well I hope you luck.
ok I just tried everything you guys said, but it didn't work for me
so as some of you have stated it must be the battery, so what I did is put it between my hands for about 1 minute and put it in and it worked again!
really weird... must be the heat?
well hope that helps the research
Cheers
Jay
Right off the bat, my Revo is non-responsive, no buttons will light, backlight, vibration, sound, and of course no splash screen since the screen isn't lighting. The only sense that it is partly there is after a time connected to USB/wall charger the battery warms as if it is charging. Yet, there is no indication during charge on the screen, it stays totally black as described above.
I have been poring over forum posts, CWR threads, and the like, but have come up short on a method of reviving this puppy. thecubed had posted something that seemed promising but doesn't work for me here. At all steps, the phone remains non-responsive and connecting it to the PC yields no mass storage connection. The only step I have abbreviated is letting it charge for an hour since the phone had charged about four hours since it shut down.
Two evenings ago, I flashed from Revolt ROM 1.0 to 1.1. It was successful but since I had just gone through battery calibration and running my battery down until the phone shut down the day before when I flashed it to 1.0, I was hoping (naive?) that I wouldn't have to do it this time (yes, naive!). So, I left the phone on all night, on the wall charger.
I was using it the next day and at one point, while using it in a low reception area, browsing the web, it rebooted on me. No biggie, had that happen in the past. After reboot however, the battery level seemed different so I wanted to get it topped off then calibrate. 1-2 hours later I noticed that the calibration app was showing the mV lower and capacity was at 70%. The battery felt unusually hot. I shut it down, removed the battery and cooled both battery and phone in a small fridge to accelerate the process (was near time to leave work).
Next boot was I recall having an extra FC, one beside the CarHome normal FC with Revolt ROM 1.1. This boot the battery showed maybe 20% capacity so I said "screw it" and deleted battery.bin with the battery calibration app (I recall the mV was low, in the 3600 range). I discharged it on the way home and left the display on to run the last couple percent down. It appeared to try and shutdown but ended abruptly. That was the last time I saw any life from my Revo.
The day after its first and only ever root, I did have an odd occurrence which I posted.
Boot Trouble - Rooted After Phone Downloaded OTA, Not Installed
That time, I had not installed a ROM yet but the phone got itself into a boot up funk. Removing the battery, connecting to wall charger, watching buttons flash ~5 times, disconnecting (which stopped the flashing lights), then battery in, power on... success! I was hoping that would happen this time around but I haven't been able to.
Full history, being my first root, I used S1C successfully, installed Titanium Backup (ran system and app backup), and RevoToolkit. The phone did download the OTA but I never let it install, instead selecting to delay it by 24hrs when it asked to install. Fearing that deadline and getting one more warning that it wanted to reboot and install the OTA, I went ahead and installed the Revolt ROM 1.0. All went fine, no drama. The next afternoon I thought going to 1.1 was going well too, until this brick hit me.
My hope of hopes is it's just a bad battery and the phone won't respond because the mV is too low. Reading thecubed's comment in his first link (above) how recoverable this phone is lends me hope.
It sounds like a bad battery. I would take it to a verizon store and see if you can try a different battery. If it still will not boot then they should warranty it out for you.
Sent from my VS910 4G using XDA Premium App
P.s. I never do anything for my battery. I charge until full then use until empty. Yesterday with moderate tI heavy use I made it from 6am until 8:30 pm
Sent from my VS910 4G using XDA Premium App
Thanks for the responses. I will be going to VZW shortly to figure this out. This phone is maybe two months old so hopefully the battery is the answer *fingers crossed*
Impressive battery life! At my office, I'm in a bit of a metal cubicle area and a bit low on signal strength. My phones will sometimes use up the battery trying to keep connected, it seems, so I am usually plugged in most of the time.
While I have your ear, thanks for the great work on Revolt ROM. I am very happy with it and look forward to its future development
Good news and bad.
The good news was they swapped in a new battery and the phone worked. Having the warranty, it didn't cost anything.
The bad news is that it looks like there may be another problem. On the way out of the store the battery was indicating 1% so I quickly got it on the charger in the car. Driving home, about 10 minutes later, I got a warning for battery temperature. Thinking the low battery may just be taking a charge and getting hot from that, I turned the car A/C on full, took the back cover off, and kept the phone in the cold air.
In about two minutes, just feet from home, I noticed the display was off. Faintly I could see the battery charge symbol that shows when the phone is powered down and charging, but the backlight was off and I couldn't see if there was any color or animation to it.
As soon as I shut the car off and the power quit, that faint display disappeared, full black, dead. Now it seems it is behaving exactly the same. I haven't fiddled with it much, holding out hope of hopes it can be started and maybe recovered.
Could calibrating the battery at the wrong time have caused something like this? Do batteries have a safety lockout if they overheat? To be fair, I was running an intensive app at the time, Waze GPS. Maybe the battery didn't keep up and the phone decided it was too low and shut off. I will post back after letting it sit, cool, hopefully charge, and see what comes of it.
My phone is behaving exactly the way you describe too. A couple of days with Revolt 1.1, and this is the only problem. I had my phone hooked to a lithium ion usb battery pack all day, and it showed "100%" while hooked up, but as soon as I disconnected the battery pack, the battery icon changed to red, then it refused to boot like the situation described in the Revolt 1.1 thread in Development. It also would not go into charge mode on the battery pack, but when I came home and hooked it to a genuine AC adapter and it went into power-off charge display. I'm going to give it a few hours on the charger before I attempt to boot it again, and I'll report back.
Still no luck. I haven't charged it too much yet for fear that it isn't charging properly. Seeing the new battery work for about 20 minutes yesterday lent me hope that if I figure out how to get a fresh battery in or just shell out for another new one, I can have a window of opportunity to change ROMs and see if that has anything to do with it.
This morning I got out my digital multimeter to measure the battery pos to neg and am getting nothing (unless you consider 0.01v something). I tested my old LG clamshell's bulging, old, and damaged 1000mAh battery and it reads 3.99v but couldn't keep my old phone up (lacks oomph now).
Comparing that battery to the Revo's, they have the same four contact pattern but different connection scheme which just stops contact when test fitting. After shaving down its casing on the bottom a little bit, it was just enough to make contact. Using four hands (yes, I am very talented ) to hold the phone, hold the test battery properly, and hold the power button, I was able to get the power-up vibration and the first LG splash screen. We lost it after that but that's likely due to the very weak test battery and/or losing contact while holding it in the Revo.
Since the spankin' brand-new battery is now reading zero, I'm left second guessing my decision of not shutting the phone down when I got the temperature warning. Maybe these batteries do have an internal protection to prevent runaway failure and it too is trash. I have no experience with this otherwise so this is just guesswork.
I'm contemplating rigging the new battery into my old LG phone to see if it can tell it "all clear" and charge it up. I'll post anything I find out here. Any other suggestions are highly welcome. Still, last ditch, I'm pretty certain I can set up another ROM to flash on the SD ahead of time, get another battery, and Clockwork to test another ROM if it's the phone or ROM. I may have had 20 minutes of uptime on the last battery.
I think I've gotten to the bottom of my problem. It's a syndrome of things that I have hopefully untangled.
First off, I had been messing with Power Manager, and wanted the phone to not sleep or timeout the display when plugged into both AC and USB. I figured that would help when I'm plugged into the computer, but it was probably a bad choice.
Yesterday I was out on a boat, which probably put me into a weak signal area, causing the phone to expend extra energy staying locked on a tower. In addition, I had plugged it into the external USB power pack, and thrown them in a bag together. This did two very bad things: 1) It allowed heat to build up from both the charging and 2) it invoked the "USB powered" Power Manager profile which kept the display active which created both additional heat AND crazy battery drain.
Here's what I think happened:
1. The battery overheated
2. The USB battery pack couldn't charge as fast as the display and radio could suck it out -- so five hours in that mode BOTH drained the internal battery AND tapped into about 30% of the external battery pack.
3. The USB battery pack will not provide enough initial juice to restart a flat-dead, overheated phone, or the firmware "knows" it is hooked to USB and refuses to start the phone -- for some bizarre reason.
So, I think my phone demonstrated normal behavior for a flat-dead, overheated phone, and hooking it up to AC brought it right back to life -- after about 5 hours of continuous charging. The battery also got very warm during charging -- more than I recall feeling ever in the past.
I'm hoping there is nothing that software power management could have done to physically damage the battery, but I assume Verizon would claim it could -- as part of the reason they forbid system modifications, and therefore withdraw their warranty if you modify.
At this point I think I have dodge a bullet, and my phone is fine -- other than a few of the quirks others are seeing in Revolt 1.1 (Phone occasionally FC, etc.)
Good to hear your phone is fine. Seems like mine is too as posted above but time will tell. I got the Revo battery set up and charging on my old phone. It seems to be connected well enough. The phone complained the first try that there was no battery but my second try has it displaying that it is charging. The battery isn't warm at all but maybe that's due to a different charging rate for the old phone's 1000mAh battery vs. the Revo's 1500mAh. Or, it really isn't connected perfectly. We shall see.
Success. The surrogate charge setup got the Revo battery up to 4.11v and indicated charge complete. The Revo completed a full boot on the battery and appeared normal.
Not normal was quick heating (still unsure of the cause). Going straight to Battery Calibrator, it indicated 68% and around 3.7v and falling. Not wanting to push my luck, I shut it down. Battery now read 3.9v. Not bad but it sure seems to be getting drained quickly which would explain all the heat. Going to set up later and see if I can get it back to stock and see if the behavior persists.
I don't know how to fix any of your issues but I would like to say thanks for giving such a detailed display of what you've been doing to fix this problem should anyone else run into this issue. Also, That picture in you one post: That is the most jerry rigged set-up to charge a phone I have ever seen in my life and I love it. Good luck getting your phone working I hope everything turns out for the best.
You're welcome. It was a bit of impromptu brainstorming with some fellow tinkerers that helped come up with a way to test charge the battery. Having it come back to life
I've come to a conclusion. Somehow, I think when the battery overheats, it must internally soft protect itself. Charging it on the old phone reset it and then it worked again on the Revo. Why the old phone works and not the Revo, unsure. That would at least explain why the battery tested at zero volts before the charging rig.
After many starts and stops on my Revo now, I have found that what was heating up first was the casing of the phone. I'm guessing heat conduction of heat from the processor as it wasn't the display which was set to minimum brightness (those are the main heat sources, right?). Looking into Settings > About > Battery Stats, it only showed Android System at 98%. It seems like the processor got locked into some some high power continuous use situation which survived reboots.
The battery gets hot later due to the high consumption and proximity to the hot casing (processor), especially with the back on. Withing 1-2 minutes from start, the sides of the phone would be quite warm and after 5 minutes becomes concerning. It seems that's why the battery was never able to get to 100%, but instead its percentage was always falling, phone over consuming greater than charge rate.
With the processor going full tilt, battery cover on, protective case on phone, sitting in a warm car without A/C, that got the battery too hot within 20 minutes. It was a similar situation with the prior battery when the problem cropped up.
I don't know what the cause of this predicament was in the first place however. The phone was plain stock, then rooted, later flashed Revolt 1.0, then Revolt 1.1. Between Titanium Backup, RevoToolkit for CWM, basically nothing unusual, I have no idea how it happened. Maybe I should have done Decrap first since I've read others doing such. Thinking back to my first post/thread, I had a boot issue and only had rooted, Titanium, and RevoToolkit, no ROMs yet.
And, don't get me wrong. I'm not placing blame anywhere, just documenting my "progress." There was a time I was on Revolt where it wasn't behaving this way. I am left without a solid conclusion as to the cause.
How to avoid the battery drain?
I had a similar situation, downgraded and then installed Revolt 1.3. Can't say what did it, but the battery got hot and drained so far it would even start charging.
I got the battery charged on the old phone, and the new one, with Revolt 1.3 is working. But I'm not sure how to make sure the overheating/draining problem doesn't occur again. After 10 minutes the phone is starting to get hot again, battery is down to 57%. With the phone on or off, it does not charge the battery, even with an AC wall charger. With the phone on, it indicates 57% charge, with the phone off, the battery icon just sits at red, no charging is happening. I erased the battery stats in ClockworkMod, but is there anything else to do? Any other ideas?
It sounds like Haxid had it happen and he got back to LG stock and unrooted, all good.
http://forum.xda-developers.com/showthread.php?t=1233668
Mine happened again this time totally dead battery. Trying to get some charge in it now to boot and remove cwm so I can take it to verizon.
Decrap 1.0 rom this time w/ CWM
I do not believe it is the rom. It has to be an app or hardware.
Were you having spontaneous reboots? That's when it happened to me, after a spontaneous reboot.
Good luck. Hope it all works out.
Bait-Fish said:
Were you having spontaneous reboots? That's when it happened to me, after a spontaneous reboot.
Good luck. Hope it all works out.
Click to expand...
Click to collapse
No my phone is actually super stable it just is sucking battery like its candy. Been off charger only 1 hour right now and its down to 83%. It has to be an app doing it but I have no idea which one. The phone shows 64% battery usage by android system.
When mine was hogging battery, same here. All I saw was Android process.
just to add my 2 cents here. I noticed my phone draining like crazy, I tried everything, then I changed the battery. boom. everything is now stable. I'm going to try to exchange that battery I think its my drain and reboot culprit.
Ok, so I have had no issues at all since buying this phone at launch, and this randomly happened yesterday.
I was on my phone and checked the battery info as I do a few times a day, just to see what's using my battery the most, SoT, etc. I was at 87%, which was about right as it has been off the charger a few hours with some light use. A few hours later I noticed my actual battery icon was exactly the same, no drainage at all. I viewed my battery info, and the line was flat for a few hours and still said 87%, which is very inaccurate as I've been using it during those few hours. If I had to guess, I was realistically around 60-70%. Then, while looking at my battery info, it said 'battery critically low' and shut off. I plugged in the charger and the animation when the phone is off said 0%. I left it plugged in for like an hour, and turned it on and it still said 0%. I unplugged the charger and it immediately died. I was on pop rocks ROM when this happened. I then plugged it back in, because the phone would function as normal as long as the charger was plugged in. I booted into recovery and restored an old stock backup, even after that I'm having the same issue. I downloaded a stock ROM from here, wiped everything like normal, same issue. Here's the frustrating part -- I chalked it up to this battery being bad. But I have two batteries, and the other one I hardly ever use, but I've used it before and it was fine and normal. I put that battery in, I'm having the same stupid issue! I don't understand, no matter what ROM or batter I use, this is happening. This is so frustrating, I don't know what to do or why this is happening. The phone will not charge at all. Please, anyone I would greatly appreciate help. I searched for issues like this on Google and here but it's usually chalked up to a bad battery, but I know that's not the case here. I couldn't find the option in TWRP, so I downloaded 'battery calibrator' app and wiped my battery stats, still didn't help. Below is a link to picture of what it looks like when I charge it, it just stays like this. I've done it with fast charging on, off, and with the phone completely off, same result.
http://imgur.com/6375t5i [1]
Edit- One thing that was weird that also happened, was after I restored stock and then rebooted, I unplugged the charger and during the whole 'android is upgrading' thing where it shows the number of apps and such, the charger was unplugged and the phone stayed on for that entire duration. Then once it finished the upgrading thing, it immediately died. That is incredibly strange. Also someone mentioned maybe it's the charger plug in area not working properly, but that doesn't explain a battery going from ~70% to 0 instantly, and the phone not recognizing a charged battery and showing 0% even unplugged.
Also, in addition to everything above, even though I'm certain it's not a battery issue, I bought another official Samsung battery just because I really don't want an 800 dollar paper weight, and I know the battery was somewhat charged when I got it, and I put it in and have the exact same issue. I also just flashed stock firmware via Odin, same issue. I was able to do all of that with my USB plugged in -- but as soon as I unplugged it the phone turned off. This is so frustrating, I can't explain how much I would appreciate help, and maybe even send some money via Paypal for an answer to a fix.
Does anyone have any idea? Please, any suggestions would be greatly appreciated. I have heard maybe it's the charging port on another site, but that would only explain it not charging, not the sudden and instant drainage of two batteries that were both over 60%. I would really appreciate any suggestions.
It could just be something wrong with the phone itself. Bring it to a tmobile store.
Hi guys,
My phone turns off automatically. It actually has happened 4 -5 times in 3 days. Let me explain; Once my phone was just on my table and I picked up but it was off and nothing was happening. I just plugged in my wall charger (Turbo Power), it turned on and the charging showed 53℅ so it came back to life. Today, my phone was on charge and it was almost 70℅ andI had to remove the charger but as soon as I removed it, screen turned off and then I had to put the wall charger again to make it alive.
What could be the issue? I am confused.
Thanks!
Attached is an image of my battery stats for reference. Thanks!
82% wifi battery drain? Do you still have this problem if you keep wifi off? I would perform a factory reset if I were you.
TheSt33v said:
82% wifi battery drain? Do you still have this problem if you keep wifi off? I would perform a factory reset if I were you.
Click to expand...
Click to collapse
Yes, the issue is still there when I keep my WiFi off. Also, i noticed that my phone used to get charge from 5℅ to around 40℅ within 15 or 20 minutes. I did put my phone on charge few hours ago but in one hour it was only 53℅.
I use Turbo Power wall charger and I purchased this phone 2 weeks ago. I'm not sure if doing factory reset would work or not but first I want to make sure there is nothing else wrong with this.
Any thoughts?
sh_obaid said:
Yes, the issue is still there when I keep my WiFi off. Also, i noticed that my phone used to get charge from 5℅ to around 40℅ within 15 or 20 minutes. I did put my phone on charge few hours ago but in one hour it was only 53℅.
I use Turbo Power wall charger and I purchased this phone 2 weeks ago. I'm not sure if doing factory reset would work or not but first I want to make sure there is nothing else wrong with this.
Any thoughts?
Click to expand...
Click to collapse
If a factory reset doesn't fix it, my only other guess is that there is something wrong with the battery. If you purchased it new, it's very easy to get a warranty replacement through Motorola if you live in the USA, but I'm not sure how it would work outside of it.
I just posted in the "Weird Battery" thread. But you need to do a Battery Re-calibration by holding the power button to turn the phone and KEEP holding button until the phone re-boots itself. Ignore the "Power Off" dialog. Then plug in the stock turbo charger overnight. I had this problem a lot while using a wireless charger.
radon222 said:
I just posted in the "Weird Battery" thread. But you need to do a Battery Re-calibration by holding the power button to turn the phone and KEEP holding button until the phone re-boots itself. Ignore the "Power Off" dialog. Then plug in the stock turbo charger overnight. I had this problem a lot while using a wireless charger.
Click to expand...
Click to collapse
Thanks for the response and I will definitely try this. However, there is something I noticed: Today I plugged in my Turbo Charger and the phone started charging from 4%. After 45 minutes, it was 22%. I think that means it wasn't turbo charging and as soon as I plugged out the cable from my phone, it turned off and again I had to plug the cable in and it turned on and started charging. I then turned on my phone and the battery was at 22% (charging). After next 30 minutes it was at around 70% and then I tried to pull out the charging cable to see if it turns off again but it didn't.
I am not sure if it's right but I feel like when it doesn't get a turbo charge, it gets turned off when I remove the charging cable from it. But when it actually gets turbo charge, it doesn't turn off and act normally.
This is really confusing, isn't it?
No one?
The most likely problem is that your battery is failing due to age.
Although it appears to maintain a usable voltage, reflected in the battery % displayed, it can no longer provide the current needed to run the phone under high-load conditions. In those cases the voltage drops momentarily below the 0% level, triggering an immediate shutdown.
Try taking the back cover off the phone and seeing if the battery is significantly swollen or bloated. If so, it's time for a replacement. There are good video guides on YouTube detailing the process.
Your device is two years old, and all batteries wear out with enough charge/discharge cycles. If the phone is exposed to high temperatures (such as during turbo charging), the batteries will wear out faster.
Spott07 said:
The most likely problem is that your battery is failing due to age.
Although it appears to maintain a usable voltage, reflected in the battery % displayed, it can no longer provide the current needed to run the phone under high-load conditions. In those cases the voltage drops momentarily below the 0% level, triggering an immediate shutdown.
Try taking the back cover off the phone and seeing if the battery is significantly swollen or bloated. If so, it's time for a replacement. There are good video guides on YouTube detailing the process.
Your device is two years old, and all batteries wear out with enough charge/discharge cycles. If the phone is exposed to high temperatures (such as during turbo charging), the batteries will wear out faster.
Click to expand...
Click to collapse
Are you sure it can be a problem of battery? I purchased this phone in start of February and it's new. Also, if it's a battery problem then why does it happen just sometimes? Why not every time i plug in the charger? Also, my battery after full charge give me a handsome backup of 1 and a half day easily even after 81% use of a WiFi.
sh_obaid said:
Are you sure it can be a problem of battery? I purchased this phone in start of February and it's new. Also, if it's a battery problem then why does it happen just sometimes? Why not every time i plug in the charger? Also, my battery after full charge give me a handsome backup of 1 and a half day easily even after 81% use of a WiFi.
Click to expand...
Click to collapse
A weak battery is one possibility, but if you're getting a day and a half of usage from a full battery, then it's probably a different problem.
My next guess would be a bad charging cable or damaged USB port. Or possibly a poorly written app that's running in the background and causing memory problems somehow.
What Android version or ROM is on your phone, what background apps are running, and do you have any root programs or system modifications?
Spott07 said:
A weak battery is one possibility, but if you're getting a day and a half of usage from a full battery, then it's probably a different problem.
My next guess would be a bad charging cable or damaged USB port. Or possibly a poorly written app that's running in the background and causing memory problems somehow.
What Android version or ROM is on your phone, what background apps are running, and do you have any root programs or system modifications?
Click to expand...
Click to collapse
Thanks for the response. My Android version is 6.0.1 and in background I am not sure where to look at but the usual stuff I use are Facebook, Watsapp, MyCafe game (I have already tried uninstalling it to see if it's causing the problem). My device is not rooted and there are no modification. I am using this phone as I got it new. Thanks!
For few days it was working fine. Now, I was facing the same issue again so I tried to do a factory reset. Now when I tried to boot it up for the first time, I was setting up the Google Account, I didn't remember my password so I first changed it using my PC and then tried to sign in on my phone but now it's always saying "please sign in using one of the owners accounts for this device". I tried to google it but all of it ended up giving me a solution that I have to wait 72 hours because there has been some Google Security or something? I don't understand. Please help!
sounds to me like the battery is dying/dead. i would certainly open up an inquiry to motorola to see if they can get you a new battery. doesn't hurt to ask.
jco23 said:
sounds to me like the battery is dying/dead. i would certainly open up an inquiry to motorola to see if they can get you a new battery. doesn't hurt to ask.
Click to expand...
Click to collapse
I had to encrypt the device and it's back to life now. But still, the issue is still there. The phone still shuts down automatically as soon as I take off the charger. It's weird that when I don't face this problem, I get day and a half battery backup which is totally normal to me. Do you think it still can be a bad battery problem?
No one?
Are you using custom rom or stock one?
mubaidr said:
Are you using custom rom or stock one?
Click to expand...
Click to collapse
I am on Stock ROM.
It's never too late
sh_obaid said:
I am on Stock ROM.
Click to expand...
Click to collapse
Hi Sh-Obaid!
Although this is a pretty old post, but I have just faced the same problem with my droid turbo as you were facing exactly a year ago. I am pretty sure that you must have ditched the droid turbo by now, but still I am curious to know if you finally found out the actual problem or some solution. Please share your experience as it can help me to fix my paperweight (almost dyeing turbo).
It keeps turning off during boot-up or android running mode within a few minutes after the charger is removed. But, it can stay 'on' for several hours in recovery mode (due to which I doubt that battery is dyeing) and also shows Good Battery status in the boot-loader mode. I have done factory reset and even re-installation of the stock rom but neither worked for me.
Any input from you would be highly appreciated - Thanks!
This One M7 had been my spare for close to a year. I replaced the screen, camera, and back cover to make it whole again, and everything worked great for a couple months. Unfortunately, it completely died one day while I was using it and the device has shown no signs of life since... until now.
Actually, it still doesn't really show any signs of life. No amount of button holding has been able to elicit any response whatsoever. No charging indicator light either. I've tried leaving it sitting for several months, but this too has not changed anything. I finally opened it up today to check on the battery connection and reseated it. Still nothing.
The one and only response that I do get is recognition on my computer when plugging it in, where it shows up as an "MTP USB Device." Nothing shows up in Windows Explorer though except an empty CD drive.
Any ideas?
Bill720 said:
This One M7 had been my spare for close to a year. I replaced the screen, camera, and back cover to make it whole again, and everything worked great for a couple months. Unfortunately, it completely died one day while I was using it and the device has shown no signs of life since... until now.
Actually, it still doesn't really show any signs of life. No amount of button holding has been able to elicit any response whatsoever. No charging indicator light either. I've tried leaving it sitting for several months, but this too has not changed anything. I finally opened it up today to check on the battery connection and reseated it. Still nothing.
The one and only response that I do get is recognition on my computer when plugging it in, where it shows up as an "MTP USB Device." Nothing shows up in Windows Explorer though except an empty CD drive.
Any ideas?
Click to expand...
Click to collapse
you bricked it, maybe flashing RUU can help. if it will not help you can then use JTAG, it can help to flash firmware on dead boards. you can find JTAG on eBay.
Request for clarification
itwasmistake said:
you bricked it, maybe flashing RUU can help. if it will not help you can then use JTAG, it can help to flash firmware on dead boards. you can find JTAG on eBay.
Click to expand...
Click to collapse
How could I have "bricked" it without flashing anything? The device literally died while I was using it.
Bill720 said:
How could I have "bricked" it without flashing anything? The device literally died while I was using it.
Click to expand...
Click to collapse
Do you have multimeter to check voltage on battery? it could be battery problem, or maybe connector on motherboard is damaged? check for scratches on board (on traces).
It shall be tried
itwasmistake said:
Do you have multimeter to check voltage on battery? it could be battery problem, or maybe connector on motherboard is damaged? check for scratches on board (on traces).
Click to expand...
Click to collapse
I'll try to measure the battery voltage this weekend. Aren't the pins a little small to test with standard multimeter leads though?
0volt multimeter test
I finally got around to trying to measure the voltage of the current battery with a standard multimeter. I got absolutely nothing, which means that I'm either measuring it wrong, the leads are not sharp enough, or the battery is dead. Has anyone else ever had any luck testing this battery with a multimeter?
Going for it!
I tested another, similar, battery by multimeter successfully, so I suspect that it might just be a case of bad battery (at least). With that and the fact that I had a Galaxy Note 2 battery fail earlier in the year, I'm going to jump in and buy new batteries.
Rather than just trying to go cold turkey and install the replacement, I'll test it with the multimeter and then hook it up pre-install. If the phone powers up, then (and only then) will I go through the massive hassle of replacing it. We'll know one way or another next week when it comes in.
Humongous Tinfoil Catamaran!
Just to follow up, I did end up buying that battery. Definitely not "new," but as long as it's in decent shape, it should do the job. While the multimeter test revealed practically nothing, (same as before) the phone did spring to life with the charging indicator as soon as I plugged it in to power. With that, I've charged it up and will be fully testing the phone next weekend. If everything checks out, I'll start the long & annoying process of replacing the battery and hopefully have a fully-working One once again.
Here's to Change!
FIXED!
Just to provide some closure, I can say that the battery replacement was a success! The vibration motor is totally dead (despite being plugged in adequately and not seized) and the casing took a beating from the repeated re-entry attempts, but the phone is now working once again. I suppose I could buy another replacement back cover to really finish the job, but will probably just leave it as-is for right now.