Hey guys... Love you guys! I have a somewhat unique issue going on and am wondering whawt you all think is the best way to proceed. I have a D415 LG-Optimus L90 for T-Mobile. It was rooted with Towelroot (v3 I believe) and I flashed CM onto it (CM11, i believe). I had the back cover removed with battery in it BUT it was powered off and it was laying on the ground and a very shallow, light puddle of liquid seeped down the walls and eventually it puddled up and seeped under my phone so a VERY small amount, a very light layer, of liquid got onto the bottom/outside parts of my battery and the back-inside area surrounding battery. Upon reinserting the battery, it wouldn't turn on. When connected to charger, it gives me the empty battery icon with the yellow triangle (warning? sign). If i leave the phone powered off for a day or more and connect to charger/power bank (it fluctuates), it charges from 0% BUT it stays at 0%.... after about a minute of this, I can boot the phone up and it boots up to my CM initial setup/welcome screen. At this point, I can go through the setup process however no wi-fi networks show up (and i'm in a wi-fi networks zone) and after going through "Setup" steps and click "Finish" or "Go to Home Screen", it powers down and reboots and stays stuck in this bootloop. Sometimes, if i restart or power cycle my device from initial setup/welcome screen while STILL connected, it'll go back to the empty battery icon with the yellow triangle warning icon.. So i'm getting a new battery today and am wondering what I should do once I charge my new battery and am ready to fix my phone; flash stock OS onto it? Re-flash CM and Gapps? Any and all help is appreciated ; i do have internet access with sync cables, SD cards, etc so I should have all tools neessary to fix this. I've been a month without a phone and needless to say, i've suffered for it so any and all help is appreciated; any links,referalls, suggestions.... Thanks in advance!
nmoren408 said:
Hey guys... Love you guys! I have a somewhat unique issue going on and am wondering whawt you all think is the best way to proceed. I have a D415 LG-Optimus L90 for T-Mobile. It was rooted with Towelroot (v3 I believe) and I flashed CM onto it (CM11, i believe). I had the back cover removed with battery in it BUT it was powered off and it was laying on the ground and a very shallow, light puddle of liquid seeped down the walls and eventually it puddled up and seeped under my phone so a VERY small amount, a very light layer, of liquid got onto the bottom/outside parts of my battery and the back-inside area surrounding battery. Upon reinserting the battery, it wouldn't turn on. When connected to charger, it gives me the empty battery icon with the yellow triangle (warning? sign). If i leave the phone powered off for a day or more and connect to charger/power bank (it fluctuates), it charges from 0% BUT it stays at 0%.... after about a minute of this, I can boot the phone up and it boots up to my CM initial setup/welcome screen. At this point, I can go through the setup process however no wi-fi networks show up (and i'm in a wi-fi networks zone) and after going through "Setup" steps and click "Finish" or "Go to Home Screen", it powers down and reboots and stays stuck in this bootloop. Sometimes, if i restart or power cycle my device from initial setup/welcome screen while STILL connected, it'll go back to the empty battery icon with the yellow triangle warning icon.. So i'm getting a new battery today and am wondering what I should do once I charge my new battery and am ready to fix my phone; flash stock OS onto it? Re-flash CM and Gapps? Any and all help is appreciated ; i do have internet access with sync cables, SD cards, etc so I should have all tools neessary to fix this. I've been a month without a phone and needless to say, i've suffered for it so any and all help is appreciated; any links,referalls, suggestions.... Thanks in advance!
Click to expand...
Click to collapse
There should be no need to reinstall the OS, but it wouldn't hurt either. If you reinstall the stock ROM ( KDZ ), unless from backup, you'll have to go thru the rooting process again. You can also, as you mentioned, reinstall CM11 as well. Anyway, I'd try booting to recovery then wiping cache and dalvik-cache then reboot. If no luck there, then I'd reinstall an OS also wiping cache and dalvik-cache before booting to the OS.
It kinda sounds to me, from what you posted, like there is now some kind of hardware damage.
so I havent gotten the new battery yet but the old one charged up to 15% so gonna see if it'll charge up to more. And on the phone, it boots up to the setup screen and gives me a bunch of repeaged "google play has stopped running" - force close / report options dialog box for a bunch of google processes and wont boot to Home screen and I can't boot into recovery. You think there's hardware damage to the battery or other internal hardware? What, specifically, would you do? and any links to manuals, walk-thru's??
Related
I am having a problem with my phone and I'm sure there is a solution for it but I must not be using proper keywords to pull up posts. So I went through the first time flasher's guide and followed it all perfectly, got hardSPL flashed, resynced my phone then flashed the new ROM and it booted fine the first time and I was making a call then my phone turned off, rebooted once and claimed my battery was low which I know it isn't because it was a fully charged battery when I began all this, then it died again and hasn't booted since. I tried plugging it in to my computer's USB port and the charge light does not turn on. If I hold the softkeys and press the reset button or the power button (regardless of it being unplugged and running on battery) it comes up with the screen asking if I wish to restore factory defaults. When I do this it makes no difference in the device booting. When I press the power button the green light will remain solid for a short amount of time then turn off. I don't want to think this is a bad flash because it did work for a bit of time and I was going around and messing with settings and such, is there another possible reason for this and is there a way I can restore my phone to either stock FW or a different CFW?
The CFW I flashed can be found here
Thanks in Advance!
Just sounds like you have a faulty battery to me. Has it got wet somehow lately or leaked slightly?
It was a faulty battery, it had dents in it and I didn't happen to think that the cell inside the battery got damaged, got a new battery in there and its working great now.
Hey all, thanks for taking your time to read and possibly help me out with my problem. Yesterday I've tried rooting my droid in order to put cyanogen mod on it later. The reason I was interested in doing that was because I felt as droid was not working to it full potential and constantly crashing apps on me (browser, games, weather, etc). A friend of mine suggested cyanogen as he himself owns it. Being that I've did plenty of CFW on PS2, psp, xbox and mp3s/ipods, I thought there shouldn't be a hassle with this.
I followed the procedures listed on cyanogen's wiki page in order to complete the rooting process. But on the step where it asked to instal .sbf file trough RSD lite and wait till it says "pass" I've ran into trouble.
During the unpacking of that file to the phone using RSD lite the phone was undergoing several reboots, and after finally finishing the reboots on my PC screen in the RSD Lite window it showed 100% complete "please reboot the phone manually". I had no idea how to do that manually as the phone just kept going on and off by itself. (also for some reason it kept saying "error" force close/wait/send notice. But I thought it was probably just the process. After trying to reboot the phone a couple of times nothing worked. I didn't receive any "pass" signs on the droid screen.
I've got a little worried about the whole process and decided to shut the phone off and during that close the RSD Lite on my computer. Doing that made no further improvements for me. The phone just kept going on and off like crazy while in USB and not turning on at all while not plugged into either USB or AC. I've decided to go to recovery mode and just reset everything to stock as I was running out of time and had to get some sleep before work next day. After reseting the cache/data files I rebooted the phone but the same things kept happening to it. Now it was asking me to reconnect with gmail account and all that intro stuff. But the phone would always end up locking up and shutting off somewhere in the process of reconnecting the account.
Fast forward to today I've read that its possible to complete reset everything to stock version trough .sbf file once again. But now the problem consists of the phone not having enough batter life. (I'm not sure what the screen is called where the process of dumping .sbf trough RSD lite starts) but that screen keeps saying battery is too low to do anything with it. And mind me it has been charge for a very long time now in the AC adapter.
Now it also appears as the problem has worsened. The phone does not start up at all in either USB or without connection. It only starts up in AC adapter but then it shuts off in 2 minutes and back on and off , on and off. Recovery mode can't be accessed in any way, at least any way known to me. The black .sbf screen can only be accessed while the phone is not connected to anything but still keeps saying the battery is too low. And I've noticed the phone getting extremely hot during AC charge. (another small detail that sometimes when the phone does turn on and goes to home screen opening up the landscape view does not increase the length of the top (pull down) bar in horizontal view.
I've tried taking out both battery and sdcard and putting them back but no luck. I'm really lost as to what I can do next in order to fix this problem.
If you need any further information please let me know and thank you again for trying to help me!
I don't really see how you managed to get a fc with rsdlite.
Did you reboot your phone (turn off) then boot into usb recovery (power on while holding up, for the droid)?
Sent from my Droid using XDA App
I am by no means an expert and could be just wasting your time but in the absence of expert opinions something is better than nothing right? It sounds to me like maybe you have a bad battery that as luck would have it failed during the update/rewrite. Have you tried getting into recovery with the battery pulled running straight off the ac adapter? Hopefully you made a clockwork/nandroid backup before you started?
sent from a random hobo's droid on xda's app
I'm not an expert either, but having just successfully rooted my droid and installed cyanogen I feel the need to ask: did you hold up on the d-pad while RSD rebooted the phone the first time? If not then you needed to immediately restart the process.
I think you need to use a separate battery charger (meaning that charging battery without a phone) to charge the battery.
Sometimes, battery won't hold a charge when your phone is a brick.
BTW, it appears that you are having the same issue with mine.
(I can't post a URL because I am new here, but you can take a look at my article in this section, called "[S.O.S] A rare MILESTONE brick situation". )
I had the same problem (battery won't charge and phone won't start-up), I had to purchase a separate battery charger, and then flashed another SBF, to make the phone charging normal. (Although my phone is still a brick, but not a problem with battery. )
I'm getting constant times when my nook HD+ just shuts down, it first happened in cm11 the 9/11 nightly, it would shut off when I went on certain web pages and on YouTube, then it would shut off when I tried to change the wallpaper. It would then shut off at the cm boot logo after about 2 seconds,only being able to boot fully after repeating about 4 times. So I did a factory reset and reinstalled the rom, but then when I tried to install gapps the device would shut off, so I went in did factory reset again and formatted system, installed the ROM and gapps fine this time but the first time it still shut off at the cm boot logo, its now booted back into cm 11 the second time but still getting shut off's when I try to apply wallpaper etc.
I've re installed the stock ROM and I'm still getting random shut downs and its saying my battery is 1% when its fully charged
can anybody help please ?
same here
neontigers said:
I'm getting constant times when my nook HD+ just shuts down, it first happened in cm11 the 9/11 nightly, it would shut off when I went on certain web pages and on YouTube, then it would shut off when I tried to change the wallpaper. It would then shut off at the cm boot logo after about 2 seconds,only being able to boot fully after repeating about 4 times. So I did a factory reset and reinstalled the rom, but then when I tried to install gapps the device would shut off, so I went in did factory reset again and formatted system, installed the ROM and gapps fine this time but the first time it still shut off at the cm boot logo, its now booted back into cm 11 the second time but still getting shut off's when I try to apply wallpaper etc.
I've re installed the stock ROM and I'm still getting random shut downs and its saying my battery is 1% when its fully charged
can anybody help please ?
Click to expand...
Click to collapse
i have been having this issue for like two months now. it all started when my daughter ran the tablet out totaly. took a good three days of tinkering before it would actualy take a charge. now i get constant shut downs, flickering screen. will say im 100 percent charge and when take the cable out it will go down to 1% i dont think the battery is bad because sometimes it will actualy hold the charge.
Could be the power connector or at least somewhere along the power path. My old kindle had what looked like battery issues which was actually the cable itself at the port that was a bit loose and a different cable had fixed it - it even said it was fully charged but drained 4x faster (give or take). After the fix the battery life was normal again.
Its would be incredibly confusing [to me] if draining all life from the battery is the cause of your problems as I do it often with all phones/tablets (and others do it) and its never caused me a problem not even once. I do it on purpose not accidental.
More likely a coincidence and not the actual cause and the issue is that something was damaged or going bad. It doesn't sound like a software problem. And since it appears to be battery related that would likely be the battery or related path such as the power cable, port, wall plug.
Since its made by humans, I'm going to say if it turns green fully charged then its not necessarily anywhere near fully charged especially if the incoming power wasn't the proper amount, it could potentially be thrown off and confused instead of what one would expect happening that of either/or.
Wrong or right there's my best guess. Do with it what you will.
Adding if its still under warranty (I would assume), according to leapinlar, BN will give you a new power cable if that's the problem, or same with the device (as I took advantage of for hardware defect).
sandsofmyst said:
Adding if its still under warranty (I would assume), according to leapinlar, BN will give you a new power cable if that's the problem, or same with the device (as I took advantage of for hardware defect).
Click to expand...
Click to collapse
They will only give you a new cable if it is still in the warranty period AND it still is running stock. You may get by with just taking the cable in, and if they can demonstrate it is defective, get a new one. But if you bring the device in with CM on it the warranty goes bye-bye. So if you take it in, be sure stock is on it.
Sent from my BN NookHD+ using XDA Premium HD app
*gasp* the rest of it. Thanks for the correction there.
GOT IT
So i took it apart thinking i would replace the battery. Didn't end up having to. i disconnected the battery from the main board, then plugged it back in. tablet fired up and showed 100% battery. haven't had a single issue since. :good::good::good:
My phone had been working perfectly fine, as well as charging perfectly fine. Recently, I accidentally let it drop to 0%, which I don't usually do. I went to plug it into the same wall outlet as always, but instead of the usual charge process, the battery icon with the lightning bolt in the middle simply flashes on the screen and then turns off, which happens over and over again.
It should be noted as well that about 3 weeks ago my phone get fairly wet. After that incident, I turned it off till it dried, powered it up, and everything appeared to be totally ok.
Other facts:
-I can safely get into the recovery menu (power + vol down), which is stable, but any menu selections result in the Motorola splash screen for a quick second and then the phone powering down.
-The computer will recognize the connection to the phone.
Attempts to resolve:
-New cable, new usb hub, new wall outlet
-Trickle charge from the computer (same flashing)
-Phone in rice to remove moisture
-Toothbrush cleaning of Micro-usb port (suggestion from another thread)
I'm pulling my hair out, and I am considering prying off the back and replacing the battery. I have searched other threads, but have seen various solutions none of which worked for me. If anybody has any idea how I can fix this please help!!! Thanks in advance.
DroidGuy321 said:
My phone had been working perfectly fine, as well as charging perfectly fine. Recently, I accidentally let it drop to 0%, which I don't usually do. I went to plug it into the same wall outlet as always, but instead of the usual charge process, the battery icon with the lightning bolt in the middle simply flashes on the screen and then turns off, which happens over and over again.
It should be noted as well that about 3 weeks ago my phone get fairly wet. After that incident, I turned it off till it dried, powered it up, and everything appeared to be totally ok.
Other facts:
-I can safely get into the recovery menu (power + vol down), which is stable, but any menu selections result in the Motorola splash screen for a quick second and then the phone powering down.
-The computer will recognize the connection to the phone.
Attempts to resolve:
-New cable, new usb hub, new wall outlet
-Trickle charge from the computer (same flashing)
-Phone in rice to remove moisture
-Toothbrush cleaning of Micro-usb port (suggestion from another thread)
I'm pulling my hair out, and I am considering prying off the back and replacing the battery. I have searched other threads, but have seen various solutions none of which worked for me. If anybody has any idea how I can fix this please help!!! Thanks in advance.
Click to expand...
Click to collapse
Either there is something wrong with your battery, or there is something wrong with the USB port. If the USB port is the problem, you can use wireless charging instead. I'm a fan of this one, personally: https://www.amazon.com/gp/product/B00S7IBDGW/ref=oh_aui_search_detailpage?ie=UTF8&psc=1.
Also, are you unlocked? If so, what battery percentage does TWRP say?
TheSt33v said:
Either there is something wrong with your battery, or there is something wrong with the USB port. If the USB port is the problem, you can use wireless charging instead. I'm a fan of this one, personally:
Also, are you unlocked? If so, what battery percentage does TWRP say?
Click to expand...
Click to collapse
Thanks for the quick reply. It does seem like a battery problem, however it is just so coincidental that it stopped working after I let the battery drain to 0%, when only hours previously it was in use and charging without any issue at all.
Also, if there was a problem with the micro-usb port, I would think that a computer wouldnt be able to read the phone, but when I plug it in it is recognized as an ADB device.
I have another turbo with a cracked screen, I'm thinking about dissecting both and putting that battery in this phone as a replacement.
And unfortunately I am not unlocked :/.
Update
Well, after some further experimentation, I've gotten it working again. The solution was to charge it for like 5 hours, then let it sit off charge for an hour, and then it would boot... bizarre combination of actions. It has since dies twice and I've had to use this method.
It is working for now if I don't let the battery drop below like 15%. Seems more like a software or hardware issue to me, and i'm still trying to resolve it, so if anybody has any suggestions please let me know.
Also, what is the best way to re-calibrate the battery, maybe that could help?
DroidGuy321 said:
It is working for now if I don't let the battery drop below like 15%. Seems more like a software or hardware issue to me, and i'm still trying to resolve it, so if anybody has any suggestions please let me know.
Also, what is the best way to re-calibrate the battery, maybe that could help?
Click to expand...
Click to collapse
If you can't let the battery go below a certain percentage, it might be an early sign of failure. The voltage might drop suddenly and unexpectedly towards the end of discharge, prompting the phone to emergency-shutdown.
As for calibrating the battery...it depends on who you ask. I would say that running it to shutdown (even if shutdown is "15%") and then charging it to 100% should do it, since that gives the controller a full set of data with which to extrapolate a discharge curve. Clear your cache in recovery, so hopefully the OS will pick up on this to accurately track the battery's actual state.
Get Kernel Adiutor or something similar to check your battery's health, too. If there's something obviously badly wrong, it should report something other than "Good".
If you note when your battery dies abruptly and you immediately reboot the back light is very poor. Almost flickering.
I think this is a battery issue of not being able to feed enough amperage.
...however. My phone was doing this and after a full clean reflash it has stopped. I question if this is because I am running less apps now. Or if perhaps somehow the battery managed to lose its memory. (Li ion is an odd duck..)
mrkhigh said:
If you note when your battery dies abruptly and you immediately reboot the back light is very poor. Almost flickering.
I think this is a battery issue of not being able to feed enough amperage.
...however. My phone was doing this and after a full clean reflash it has stopped. I question if this is because I am running less apps now. Or if perhaps somehow the battery managed to lose its memory. (Li ion is an odd duck..)
Click to expand...
Click to collapse
Septfox said:
If you can't let the battery go below a certain percentage, it might be an early sign of failure. The voltage might drop suddenly and unexpectedly towards the end of discharge, prompting the phone to emergency-shutdown.
As for calibrating the battery...it depends on who you ask. I would say that running it to shutdown (even if shutdown is "15%") and then charging it to 100% should do it, since that gives the controller a full set of data with which to extrapolate a discharge curve. Clear your cache in recovery, so hopefully the OS will pick up on this to accurately track the battery's actual state.
Get Kernel Adiutor or something similar to check your battery's health, too. If there's something obviously badly wrong, it should report something other than "Good".
Click to expand...
Click to collapse
Thanks for the pointers. So strange, first it died at 40%, then 30% then 15%. Now, it is still dying early but I am no longer facing the issue I originally had, it will show normal charging when off, and boots up right away. Sure hope its not some ticking battery time bomb, its still a relatively new refurb.
I attempted the charge calibration so we shall see if it helps. I also did a factory reset for the hell of it, since I am on stock and can't reflash. Perhaps I'm in the clear, that would be awesome. Still no idea what the issue was in the first place though, which will annoy me to no end.
I've got an SM-T800 behaving very oddly, hope someone knows what's up!
If you attempt to boot it, it will flash up the Samsung logo, then die, and repeat in an endless boot-loop.
If you hold the power button down, oddly, it changes; instead it will proceed to the animated SAMSUNG logo which will then continue to pulse in and out indefinitely until you get bored and release the power button... at which point it instantly dies and then begins boot-looping again.
If you try to enter recovery by holding power + volume up + home, it will do so, but the moment you let go of the power button it dies.
Thinking it was down to the battery, I tried replacing it, and if anything the behaviour has been worse since!! It was at least possible previously to get the thing to sit in recovery without rebooting, but now it never does if you let go of the power button.
I've also tried reflashing the default firmware via ODIN; the one thing that always works is the download mode (power + volume down + home); I can reliably boot it into download mode and flash via ODIN, but then on reboot, it gets partway through the installation process (like a few seconds in) and then boot loops back to the samsung logo again.
Now it's difficult to get it to even charge; it will keep looping the charging symbol (battery with a lighting bolt on it) on and off the screen unless you fettle the buttons until it just sits at a black screen. I can see from the USB charger it is still drawing charge current.
Any ideas??!
It probably dead. Speaking as someone who had this issue for countless devices, I say that your battery probably can't hold enough charge anymore to completely power the device through.
It doesn't matter even if you charge it to 100%. The battery had degraded to a point where a minimal charge required to let the device pass the crazy power surge required during Android boot is just not meeting the minimum.
Hence it fizzles out. And rebooted.
I kept replacing my Galaxy S5 battery until few months ago, no battery I bought is enough to fully power it on anymore.
Thanks for the response; alas, I already tried replacing the battery; if anything it was worse! I suppose it is possible that the replacement battery was also a dud, though? Unfortunately it may be difficult to do a load test (a lot of batteries might not even provide power without specific conditions being met), perhaps I can probe the pins while it tries to boot and see if the voltage sags or something.
I have the same problem and I found this in Yoube; search for "Samsung galaxy tab s restarting issue" video from "Electronics repair school"
It shows bad contact on battery connector soldered side...
I have the same issue, I can hold down the power button and it will boot up completely. As soon as I let go, it reboots over and over again. So far I've replaced the:
USB Charger Port Connector Module Flex Cable
LCD Connector Flex Ribbon Cable
and the Battery
No change in boot up - The only option left , I think, would be to replace the main board. Any thoughts?
i got that issue too,
i did kind of a battery recalibration
meaning: i fully discharged my sm-t800 (took me some time doing reboots until the tab was totally dead)
then charged it to 100% without booting it
unplug it and reboot.
and well, now it works again
the clue here is:
the system stored wrong battery data over the time, so it randomly thinks the battery is at 0% and does an auto-shutdown. To repair this, you have to reset the system with recalibrating the battery, so the system deletes all old data and starts logging new data.
in my case this procedure worked out great
hope you guys will have the same success as i did
Hello everybody!
I thought I would let you know how I solved this issue WITHOUT having to do a full factory reset...
Or so I thought.
Turns out that it started shutting down and bootlooping after a while again.
Even after I ordered a replacement battery and charged that up. At first it looked like it would work and then it started shutting down randomly and bootlooping.
Probably will have to throw the thing out since it doesn't want to work. Makes no sense how its so uncooperative even after putting in a new good battery in the tablet but there's not nuch more that can be done.
If I just start it *sometimes* it will boot up and get to the android OS. Then work for a while before shutting down.
Sometimes it just bootloops at the Samsung Galaxy S logo over and over.
Holding the power button it does boot but if you release the button it MOST often just shuts off and bootloops.
Anyone know if there's anything to be done to fix this?
//Kindest regards XDAFan2015
xdafan2015 said:
Hello everybody!
I thought I would let you know how I solved this issue WITHOUT having to do a full factory reset...
Or so I thought.
Turns out that it started shutting down and bootlooping after a while again.
Even after I ordered a replacement battery and charged that up. At first it looked like it would work and then it started shutting down randomly and bootlooping.
Probably will have to throw the thing out since it doesn't want to work. Makes no sense how its so uncooperative even after putting in a new good battery in the tablet but there's not nuch more that can be done.
If I just start it *sometimes* it will boot up and get to the android OS. Then work for a while before shutting down.
Sometimes it just bootloops at the Samsung Galaxy S logo over and over.
Holding the power button it does boot but if you release the button it MOST often just shuts off and bootloops.
Anyone know if there's anything to be done to fix this?
//Kindest regards XDAFan2015
Click to expand...
Click to collapse
I have had the same experience with my T800. What I have been doing is to tape the power button down using scotch tape. The tablet can be waken up by pressing the home button. In my case, I need to remove the button to recharge the tablet.. So far so good.