Haven't used my tab for some time and now I cannot start it.
When starting tab stucks on samsung logo.
When charging tab shows battery with "wait" sign without progress animation.
Holding power makes no effect.
Cannot enter recovery but can enter download (odin) mode. Flashing other roms makes no effect.
What sort of problem can it be? Dead battery? Hardware problems?
Probably a *severely* drained battery. Connect it to the charger (not the computer) and let it charge for 24 hours. Hopefully, it can be revived.
Might try flashing stock through Odin but only after letting it charge.
So my phone was working with no issues since I first bought it at launch. Today, after being on in the morning. It shuts down by itself, goes into boot animation but never gets back into the main screen. Tried to charge it for a few hours to see if the battery was the issue, but the "charging battery icon" does not even pop up when I plug in the charger.
I tried to get into the bootloader/recovery. At random times, I might be able to get in to the "start" screen, choose boot into recovery mode but it turns off as soon as I choose it.
So not sure if the battery is the issue?
Phone is rooted and using a custom ROM.
Thanks for any help before I go and replace the battery.
Hey guys, so I have a small problem. I used a Mi Bank (5200mAh) power bank to charge my OPO yesterday. It worked the day before. When I plugged it in yesterday, it charged for like 5 seconds and then wouldn't charge. So I tried a variety of other cables and chargers but none of them worked.
I turned the phone off and plugged it to charge, the charging battery icon would appear, disappear and then the phone would reboot to the charging screen and the cycle continued.
I then let the battery die and did a few power cycles and plugged the phone to charge while it was off. It started to charge and then fully charged. I used the phone till today and wanted to plug it in again. I charged it for around 20 minutes and it worked.
Now, I'm facing the same issue as yesterday.
Phone won't charge
Does not get detected in MTP or ADB mode, but DOES get detected in Fastboot mode.
Ampere shows the voltage as 3.7v, I recall the voltage being around 3.9-4.1v)
OTG also works. I connected a flash drive and it detected the source and I even watched a movie.
When I boot into recovery (TWRP 3.0.2.0) with the battery dead, and connected to the charger, the phone stays ON. I did a full Nandroid backup and a wipe and flashed another ROM as well and the phone stayed on, but as soon as the phone rebooted into the ROM and got to the boot animation, the phone shut down saying "battery low"
Not sure if it was a placebo effect or not, so I wrapped the phone in a dry towel and left it under my pillow for like 30 minutes and then plugged it to charge. It began to charge and after a full charge, I could use the phone without an issue so I proceeded to backup my data to the PC just in case I needed to perform a full wipe. About halfway through the copy process, the indicator light went off and the copy process got cancelled and the phone wouldn't show up in the PC again.
My question is, What is the culprit here?
Do I have to replace the entire motherboard?
Is it just a battery issue?
Is it a USB connector issue?
Any help with regard to this would be much appreciated
My Verizon S6 64GB is about 2yrs old. And it tries to do a system update (Not software update) as soon as it's turned on. It freezes a few second upon starting. I either have to let the battery drain out or disconnect the battery from the logic board every time.
I tried getting into recovery to wipe cache but it freezes on that screen as well. Button are unresponsive. Again have to disconnect the battery from inside.
While the phone is completely off it turns on to the Samsung logo screen when I plug in the charger and freezes there too. Weird--it does the same when I connect it to the charger and the battery isn't even connected. Doesn't seem to be charging properly either. It holds a little bit of a charge after being plugged in for hours. Dies in like 5 min.
Now it boots up to the recovery mode with the blue screen, yellow exclamation over slanted droid and the words....No Command. It freezes there.
Does anyone know what could be wrong and whether or not I can retrieve my pictures from it? Thanks.
I've had this phone 3 years and it worked well. It's an unlocked ATT phone so no OTA updates other than the standard app updates. It's on Lollipop 5.1. Been working perfectly fine until yesterday, I was watching the CBS app, when the phone rebooted. Now it's stuck on a boot loop and initally went to optimizing apps which it rarely finishes but the times it does, the phone just powers off. It then got into another loop later last night where it'd get to the Kyocera logo then reboot over and over. I let it do that until the battery died 2.5 hours later. Then I kept attempting to boot until the batter was entirely drained to the point it wouldn't attempt to power up any more.(battery is not removable on this model). I've now charged it up, trying to enter recovery mode with power+volume down. That doesn't seem to register. Tried volume up+volume down+power with no effect. Now after charging, it will do the reboot loop mentioned earlier to the Kyocera logo. If I plug it into a charger, it will go to the optimizing apps portion and repeat the above. At the optimizing apps screen, if I unplug the charger, the phone powers off immediately. It appears to be holding a charge according to the charge indicator and the fact that I can try to boot over and over unplugged. Any suggestions? Phone wasn't dropped or damaged in anyway. Very weird what could have happened.
An update: Phone finally got past the "optimizing app" phase last night sitting on the charger. Out of no where the phone booted completely. However, it only works while plugged in. If I remove the charging cord, the phone shuts down after about 2 seconds. Booting without charging cord results in the same boot loop. I've considered the battery has failed however when plugging in the charger, battery shows 100% and it will decrease appropriately over time. I'm thinking there must be a hardware issues at this point. Somewhwere in the charging/power circuit. Any other suggestions?
Last update I guess. I was able to keep the phone up and booted as long as it was plugged into a wall charger. PC USB was not enough. I managed to grab my photos etc. thankfully. Factory reset the phone from the settings menu. Unplugged from charger, ran for about 2 minutes. Still said 99% charged, then went into boot loop again. Phone still shows near full charge if you let it run for awhile and decrements the charge state appropriately as time goes on. However, i guess this 3 year old phone is toast. No known reason for it to fail unfortunately. Thought I'd share the experience if anyone else has this issue.
djhurt1 said:
Last update I guess. I was able to keep the phone up and booted as long as it was plugged into a wall charger. PC USB was not enough. I managed to grab my photos etc. thankfully. Factory reset the phone from the settings menu. Unplugged from charger, ran for about 2 minutes. Still said 99% charged, then went into boot loop again. Phone still shows near full charge if you let it run for awhile and decrements the charge state appropriately as time goes on. However, i guess this 3 year old phone is toast. No known reason for it to fail unfortunately. Thought I'd share the experience if anyone else has this issue.
Click to expand...
Click to collapse
I have the same exact problem. It started the crazy booting process in my pocket, and I did all the same things you did. Factory reset didn't correct the problem, so I'm think the battery has had a stroke. Sine your problem and my problem are very close to the same time frame, our phones are also probably about the same age, and its a quality control issue. Not bad quality control, just that these batteries were designed to last X number of months or cycles, and probably they died. Too bad, because my E6560 is the very best cell phone I have ever owned. Built like a tank and thank God for that.