I have an old Galaxy Tab A. I don't recall the exact model and I'm too afraid to turn it on to check, which I'll explain below.
In the last few months my device has been burning through chargers. I get it a new one and it works for a while, only for the brick or the cable stop working on it or any device.
It also occasionally gets the problem of turning off at %15 or so percent before hitting 0, but that changes from charger to charger.
The most recent incident is the worst. I plugged it in and it immediately booted to the homescreen, which was odd but I thought nothing of it and I turned it off.
Then it booted up again and again and again, no matter how many times I turned it off it would boot up again.
I unplugged my device and it finally stopped booting up. I don't want to turn it on for fear of it losing all power and never turning on again. Any ideas to what might be causing this and how to fix it?
Related
Twice yesterday my GT screen went blank. The tablet isn't dead because I can see the backlight on at about 10% brightness. Gives off an eerie gray tone to the screen.
The screen and volume controls do nothing to revive it. However, holding down the power button for about 20 seconds turns the unit off. From there I can reboot.
One of the times happened during the night while I was recharging the unit. It locks the unit up so tight that the charger stops charging. When I unplugged it from the charger and rebooted it in the morning it only had a 42% charge.
Any idea why this is happening? Since it affects charging it appears to be hardware related. Can a software hiccup cause the charger to stop charging?
If it keeps up I may do a factory reset to see if that solves it.
Anyone else having this issue?
Sorry but I haven't had anything like that happen...but I wouldn't tolerate it for more than a couple days.
out of juice ?
Are you using USB charging or the wall charging plug ?
There's a BIG difference in charge .. USB trickles and once the screen is on or you're downloading .. it discharges ..
This has happened to me a few times too. I figured it was just some odd bug.
I haven't experienced this on either of our tabs (both are 16GB (retail) a white and a gray both rooted nothing custom as of yet/ both have locked bootloaders)
Probably not relevant, but I see 2 people have posted this experience. So I ask are either of you rooted or using custom kernel/rom, 16GB/32GB?
This happended to me a couple of times:/ actually happened 2 hours ago. I realized within an hour so only lost 30 percent. I hope there will be a fix with touchwiz ux, even though i don't want to update it to touchwiz, I might have to
This has happened to me, and I am not rooted.
Sent from my GT-P7510 using Tapatalk
Not rooted and I only charge with wall charger.
Someone asked if I was rooted, I am. Was running stock kernel and rom the first few times this happened though. Only charge with oem charger, although I've only seen it happen once while on charger.
Sounds like it's shutting down but not completing the power-off.
When you power off the tablet - you'll see it do the same thing - it's the backlight that's still on.
If you have access to the android dev tools/adb - use: adb logcat and see if there's any useful output about what's happening.
Omnia 7 with Mango RTM officially installed, working perfectly was recently let to sit idle while I was using my Focus, and the battery drained over time.
Today, I wanted to charge it, but plugging in the USB did not power the phone on. I even changed cables, and also used my PC to charge it - but for the life of me, it wouldn't turn on. I even let it sit with the charging cable in it for a while.
I also took the battery out and only plugged the cable, still nothing.
Is the phone dead? Can anything be done to revive it - it was a flawless phone and there were no issues as such. I would appreciate any help.
Update: I plugged in the USB jig which powered the phone on, but now it's in the download mode. Powering it down and and trying to restart it again I am hitting a dead end. It's not powering on. Anyway to restart the phone without removing battery?
Update 2: I remembered from the past trying to update the ROM, that it fails and restarts the phone. So, while in the download mode, I started the ROM updater from Samsung and ran through the normal update process. It failed and restarted the phone - now I see a big white battery charging icon on the front screen. So hopefully this will be ok - and I will update the progress.
But this is quite disturbing as to what steps I had to take to power it on. Imagine if I didn't have the USB jig.
Update 3: After showing the battery icon for about 5-10 minutes, the phone restarted itself and booted normally. It's now charging and hopefully all will be ok. I'll make sure I don't let the battery die again.
--- This may belong in the Xposed forum, I am uncertain. ---
Hello. Please forgive my ignorance regarding the technical aspects of methods discussed on these forums.
I have a Samsung Galaxy S4 GT-I9505 supplied by Vodafone Australia. This was received today as a replacement for a screen issue I had with my previous S4. On the previous S4, I had rooted using a Saferoot method as read about on this forum. Later I had installed Xposed to use Keepchat and everything was fine. Today I have rooted this replacement phone successfully using the same method, and then moved to install Xposed. The Xposed application required an update, the very first option in the app was red and suggested an update or a reboot, and the reboot did nothing, so I pressed update. The phone turned off but didn't restart. I tried the usual button presses and battery pulls and finally a simple power up using the standard power button started the phone up. It got as far as the lock screen I believe, before shutting down again. It is now unresponsive. It wont turn on, enter the boot menu (multi button holding method) or charge. I believe the battery is quite low at this point, and unable to charge, causing me some consternation. It has now been over 30 minutes with no response.
If anyone could provide a resolution to this issue, I would be extremely thankful.
Regards,
CaleS
Try and ask in this forum my friend good luck
http://forum.xda-developers.com/showthread.php?t=2265477
Hello again.
I have an update on my situation.
I left the phone on charge and it eventually turned on by itself. I played around with it for a while and it seemed OK. Eventually it turned off again. I had to pull the battery to get it to turn back on. After starting up again, getting to the lockscreen, it turned off again. This process repeated many times, until I got frustrated.
The next day I thought I'd try a factory reset via volume up + power, and the device managed to stay on long enough for this to complete. After the phone reset, I used it for a while and again it turned off. The same cycle continued.
Perhaps the phone is naturally faulty, despite my rooting attempt, as it was a refurbished model. I am quite happy to return it for another replacement under warranty, however I may not be able to do it as the device is rooted. I would gladly remove the root using stock firmware and Odin, however the phone resets after a few seconds of entering download mode.
Any advice?
Thanks.
Sounds to me you have a faulty power button. It's somehow stuck that's why it even reboots in download mode. It's a common problem for the S4. Try to wedge it or replace it.
if it is refurbished model it might as well be dead battery.
battery sensor detects "low battery" state and shutdown phone saying battery 0% - to protect battery against fully depleted state (damaging to max capacity or even impossible to charge at some point)
if you power it on again it will boot and say it has like 1% left and you will be able to use it for few more moments, but doing so will degrade your battery.
powering it on, going to lock screen for it to shutdown on its own again sounds like weak power source
imagine above scenario happening several times (previous owner of the phone kept "reviving" it after shutdown due to battery 0%)
that would resulted in battery able to hold only fraction of its standard power - allowing you to just boot your phone before it shuts down.
I had similar situation with my laptop battery (this one was on AC all the time) - battery was so damaged that laptop was shutting down at windows login screen - if booted on battery alone.
When booted on AC and unplugged it said 100% battery, that went down to 0% in a matter of around 2 minutes, when laptop shuts down.
So, I have a Samsung SM-T230NU. When I tried to power it on, it flashed for a split second the Samsung Galaxy Tab 4 logo and then went blank. I figured it was out of juice, so I plugged it in and let it charge for an hour or so.
When I came back, it was flashing and going dark.
I tried a different cable. As soon as power was applied, it flashed and went dark again.
Now, the boot logo is showing for an even briefer amount of time.
I am suspecting the battery or USB port. I don't have parts readily available to swap, however.
It may be worth adding, when I plug in the device, without touching any buttons, the screen starts flashing the Samsung Galaxy Tab 4 boot logo. I would guess a stuck power button, but the power button travels freely. When I unplug the tablet from the computer, the flashing stops.
Trying to boot it with power + volume up garners no response from the device.
Any ideas?
Having same issue here
Tried hard reset, no dice.
Tried opening the back to see if I can identify some loose connection, didn't see anything funny. I am not an electrician.
My sister's having the same issue with her T230NU. It still boots (it'll boot to the Samsung splash, but then it flashes off the screen in half a second; this repeats every 7 seconds), but only if it's plugged directly to the wall charger. She let it sit overnight to charge, and it's still got this issue. I'm pretty sure her battery was drained when the issue started occurring last night, but it doesn't look like the battery has charged much (if at all) since then.
So someone called me about 3 hours ago, and my phone just outright died. Couldn't turn it on - no signs of life, even though I had received a call just fine this morning, 2-3 hours before the random crash. Now I couldn't turn it on, and my first guess was that the battery was the culprit, though it was on charge through out the whole night.
So I pugged it into my powerbank, the phone turned on, but kept kinda bootlooping - where the "relock your bootloader pls" message would come up for half a second, followed by the phone restarting again to continue the cycle. This was without the battery charging animation - straight into booting.
After 20 or so tries to turn on it actually did, and I was able to discharge it past the point at which it crashed - most likely excluding the battery as the issue for now.
What could this be? Could it be a chip that's on its way out (as in about to brick my phone)? Anyone have any ideas as to why this is happening? Or maybe an app to check system stability / hardware test?
Edit: thanks to firefox, for saving the progress of this write up as my phone did the exact same thing after I locked it. My pebble watch vibrated to indicate that the connection is lost and I wasnt able to turn the screen on.
Had to plug the my 6P into my power bank again for it to turn on. Though it didn't do the glitchy bootloop this time.