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.
Related
Hi all,
i've got a normal nexus s, not rooted or anything, its running 2.3.2 as i haven't had the OTA yet. However strange things have started happening this week with regards to my battery.
I can no longer shutdown the phone whilst its plugged in, it goes through the motions, vibrates and then just hangs on the dimmed screen with shutdown on it. when i unplug the cable, it switches off. However, when i then plug the cable in, it starts up the phone, instead of just charging when switched off with that white battery meter.
It has also stopped recognising that it has been plugged in on the battery use info screen, so it is saying that i have been on battery power for almost 6 days now.
Its not a dealbreaker for me, but i haven't tinkered with anything, and its just plain annoying. I'm starting to think its just shizzle samsung hardware. Anyone any ideas? Or same thing happened? Cheers.
Yea, the most dreaded acronym. Black screen of death. I was in a phone call, got off and the phone just shut off and now it wont come back on or take a charge, screen just black. Cant enter bootloader or recovery. When I connect it to my laptop it makes the connection sound on my laptop as if it has detected it but still black screen and doesn't show up in my list of connected devices. I'm fully stock btw just unlocked bootloader.
Hmm, sounds like it might be gone for good. Have you tried a battery pull, or leaving it on charge for a few hours?
Could be a faulty battery too. Try opening the phone, disconnecting the battery, wait a few seconds, reconnect battery, connect phone to a power source and see if anything happens.
Battery dead, not charging, stuck on "low battery screen", bootloops with forceboot
Hello people, this is my very first post on xda, even though I've been lurking around for about a year. The community has helped me a lot, I'd like to thank you all for that.
Back on topic though! My error seems to be very similar to the one here.
I was watching some YouTube, battery sitting on a respectable 85%, when it suddenly shut off. Not the usual "shutting down for low battery" kind of shutting down, it was istantaneous, more like the battery was unplugged from the phone. Which is clearly impossible. I tried to boot it using the power button to no avail. I connected it to the charger, and the "the battery is too low" screen popped up. I left it at that for about 45 minutes, then unplugged from the charger and tried to boot. No success. The battery didn't even charge; the charger should be is fully working.
So I tried leaving it plugged to the charger and force boot the phone via volume down and power button; it attempted to boot, but stopped midway through, bootlooping until I unplug it, at that point it shuts off again.
The loop goes like this: OnePlus white logo (normal when you boot), radioactive kernel loading, reboot and repeat. That happens, again, until I unplug it from the charger. Then it shuts off.
EDIT: If I try to get into bootloader instead (volume up + power), after about 8 seconds of me pressing the buttons the screen just shuts off and doesn't react to any more presses (even while plugged). If I unplug and replug it to the charger, I'm back to square one (low battery, please charge).
PC doesn't recognize it. It makes the "the battery is low" screen pop up, but nothing else.
Here's some phone information in case you need them.
Phone info:
Rom: NucleaRom 1.3 (+ Radioactive kernel which comes with it) got it from here
Xposed modules: Youtube Background Playback, AdAway
Root: Yes
Thanks in advance everyone.
I doubt it would be software related if it does it even when in bootloader. It could be the problem I had with my nexus 7 a few times. I needed to charge it like all day for it to even turn on. Either that or faulty phone/bad battery. I hope it's just dead
NUNsLAUGHTER92 said:
I doubt it would be software related if it does it even when in bootloader. It could be the problem I had with my nexus 7 a few times. I needed to charge it like all day for it to even turn on. Either that or faulty phone/bad battery. I hope it's just dead
Click to expand...
Click to collapse
Hello there, thanks for taking the time to reply. Yesterday I worked all day to try and make sense of the problem. I could have just bought another phone but I'm fairly attached to this one so I went deep.
I was fairly sure (like you) that it couldn't be a software problem, so I looked at the logic board of the phone; turns out (correct my poor technical wording) the bracket (connector?) for the battery on the logic board was coming off from the motherboard itself (the battery was indeed attached to the bracket, the bracket was just coming off of the board). What I did was just reposition the bracket and pushed it down with a bit of force on the board, then replugged the battery in the newly restored battery plug, and tried my luck. It booted! Back at its original 75%-ish.
My only guess would be that due to a fall the bracket got misplaced, but stayed close enough for it to still make contact and never actually shut down, until yesterday. That was... Quite an interesting ride.
Thanks for replying, it was indeed a "faulty phone", but I just couldn't leave it at that without trying
I'm glad it worked out for ya
Not work at all ...
My phone its show the logo on charging or low charge but its stuck for this for while full battary is empty... When I plagued in charger the same show charging logo with indicator but not charging its suck on that logo to .......then I charged the battary externally then put the battary try to open its show only a (powered by android log ) stuck on this ......I cant go any recovery modes ..fast boot mods... Only show this one or charging logo if battary low that logo to ... I try to get adb driver on my computer its also not show because of not get recovery modes ........
Any other idea to solve this
Hey there.
I'm in trouble with my old Nexus 5. As the battery was becoming less and less powerful, I decided to change it ; and so I did ! Get a new one on Amazon, and installed it.
But now, my Nexus 5 refuse to boot. Even when I put the old battery back. I didn't damage anything, all the connexions seem fine, but the N5 refuse to boot (even Recovery Mode). I also try to keep the Power Button on for 30 seconds, or even bang it, but nothing. With the 2 batteries, same result.
When I put the battery off and charge the N5, the screen does turn on ! The battery logo with the lightning sign appears for a few seconds, then it turns off. And on again, and off.
If in this situation (N5 plugged and battery off) I connect the battery (just a simple connector), I have the charging screen (battery icon fulfilling). But then when I tried to boot it, nothing. The screen just turns off and nothing happens. Even the first screen does'nt show up again.
I am really stuck with this issue as I don't know what to do ! Both batteries give me the same result. The old one is supposed to be charged (at least 50%) but nothing happens..
Could the new battery have damaged the phone ?
If you can help me on this one, I would really appreciate it..
Cheers !
When you connect the phone to a computer, is it detected at all? Maybe it is semi-bricked?
New battery could be doa, happened to me before. Also always fully charge new batteries first or you risk making them unable to charge fully or at all.
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.