Galaxy tab S T705 not turning on without charger - Galaxy Tab S Q&A, Help & Troubleshooting

hi guys,
sorry if i had to ask this i think i'm out of options that i'm aware of.
i have a tab s t705 which has been on stock firmware for the longest time(5.02, country PH) and a week ago it just died.
the tablet charges but does not turn on. i can get to odin and recovery modes but it does not boot to system. also it does not turn on when i unplug the charger.
what i've done so far:
. pressed the power button for more than 30seconds, unplugged - nothing
. pressed the power, home, and -vol buttons for about the same time, unplugged - nothing
. pressed the power button for the same amount of time, plugged - only charging icon with batt level, nothing else
. pressed the power, home, nd -vol buttons for a few seconds while plugged, gets into pdin mode but restarting it just goes back to charging icon
. pressed power, home, and +vol for a few seconds while plugged, gets into recovery mode and after trying factory wipe and wipe cache, still goes back to charging icon when rebooted
. followed a guide to remove the back cover and disconnected battery for more than five minutes and did the same steps - same results
. tried plugging in to computer where it was installed before - not detected, not even odin(3.05 - 3.11 versions) does not detect it
this tablet is absolutely out of warranty already and i sort of like this tablet. any chance i can still revive this, or were there some steps that i have missed?
seriously, thanks in advance for any help

If you have an DMM check the voltage of the battery it should be 4.35v fully charged battery, If the battery is faulty maybe that is what is stopping the tablet fully booting, maybe somebody else knows.
John.

unfortunately i dot have acces to such tool but i really am hoping that this could be just a dead battery.
i'll see if replacing the batt would fix this and reply back for the results. thanks!

Related

Device Won't Turn On

Screen went black during phone call, audio still present. Then the phone shut off and refuses to turn on, no charging led when connected to power supply. Battery still had 75% charge during call
Have you tried holding the power button down for 10 seconds?
John.
Tinderbox (UK) said:
Have you tried holding the power button down for 10 seconds?
John.
Click to expand...
Click to collapse
Thanks. This has also happened on my girlfriends device numerous times.
Similar thing happened to me, i was charging my One X while it was off (the battery completely depleted).
The notification LED was on (red) indicating it was charging, the LED turned off after about an hour of charging, i tried to turn it on and nothing, absolutely no reaction.
I've tried holding the power button for 10 seconds, also tried a vast combination of buttons;
Volume up + power.
All three buttons at once.
Any suggestions before i take it to the shop?
UPDATE:
5 minutes after posting this the LED light turned on, i tried to turn the device on and it did, so everything seems to be fine now, i just don't get how after an hour on the charger, when i turned it on just now my HTC One X battery was at 2%
In any case I won't be letting the battery deplete to 0% anymore
@dusan do you have CWM as recovery? It is known that battery-charge is broken, even when the device is off, when cwm is flashed.
Try to get into fastboot after some while, flash the stock recovery as fast as possible and turn the device off again for charging.
That would explain it, I do have CWM, I don't know how but I guess it charged just enough juice for me to turn the device on.
If I flash stock recovery will I be able to recharge the phone with the device off ?
Also would I lose root in that case?

Phone not bricked, but usually won't boot in any way

Hello everyone, thank you for your time.
TL;DR: Phone boots into download mode up until "Downloading...", recovery mode until "RECOVERY BOOTING," and can only boot right when I put the battery in. The battery is fully charged, and I can boot up until my home screen only once so far. Will a jig fix the issue, or should I try to get the phone replaced by TMobile warranty as I have before?
I have a Galaxy S3 from TMobile, and have been running CyanogenMod for about a year now. 2 days ago I flashed a nightly release, which I assume was unstable. Yesterday, my screen was on and then my phone turned off (low battery, but 99% sure it was a crash rather than a power off), and did not boot up again. After attempting to pull the battery out, charge for hours, turn on and plug in (in different combinations), the furthest I could get was a couple of seconds of the CyanogenMod Galaxy S3 logo initial boot screen (not the rotating splash screen).
I took my phone to TMobile today and was about to get it replaced until I realized I didn't mask the flashes.
The last time I was in an exact same situation with the same phone model, and my flash counter was still showing custom firmware, yet I did manage to get it replaced effortlessly, but I didn't want to risk what was a possible fluke again.
I get home, and here's my current situation.
The only way the phone boots up in any manner is when I take the battery out and the charger is not plugged in. Here are the scenarios I run into:
1. Boots into download mode, can press VOL + to get to the "Downloading..." screen, then shuts off 2 seconds after.
2. Boots into recovery mode, only up until "RECOVERY BOOTING", then shuts off.
3. Boot by pressing power button, plug charger in, shows grey battery icon.
3. Boots into download mode, can press VOL -, either shuts off, OR
3b) Only after tons of tries, it booted up all the way up until my actual home screen, then shut off.
I can't have the charger plugged in while booting (pc or wall), and I can only boot right after I put the battery in.
Are there any suggestions as to what I should do? I was thinking of buying a jig from Amazon, but I don't know if it is hard bricked or not. Should I just attempt to get it replaced under warranty once again, even though it shows the flash count?
Thank you very much!
FIX: STUCK POWER BUTTON PROBLEM
So, one thing I didn't check. Take the battery out of the phone, wait about a minute. If it buzzes as if its powering on, that means that your power button (either the actual button itself or the switch on the mainboard) is stuck.
Solution: Smack the power button with your battery until your battery has a (small) dent. If it doesn't work, smack it a couple more times. Took me 2 tries, second try, phone didn't buzz when I put battery in. I press the power button, works like new. Absolutely....ridiculous

Unplugged phone from computer charging and it stuck on charge screen. Won't boot.

I was charging my phone connected to my laptop, the phone was powered off. I unplugged it and it just stuck like it was still plugged in charging. The charging light is on but trying to rest or boot does nothing. Just makes the charging light turn off for a second then back on.
Is it bricked? What should I do?
UPDATE
I let the battery drain out overnight and plugged it into the wall socket this morning. Now the charge light blinks but no charge icon pops up and it still doesn't power on. When trying to boot it into recovery, the icon pops up again. When I unplug it from charging, the charge light still blinks and the icon stays still. I think it is going to have to be a paperweight.
Anyone ever had this happen?
mkbeyer said:
I let the battery drain out overnight and plugged it into the wall socket this morning. Now the charge light blinks but no charge icon pops up and it still doesn't power on. When trying to boot it into recovery, the icon pops up again.
Click to expand...
Click to collapse
First, let the phone charge on wall socket for several hours. This is sometimes needed if the battery is allowed to drain to shutoff, and there is unsufficient battery voltage to boot/power-on the phone.
There is no button combo to directly access recovery on this phone, so I think you mean you tried to boot to bootloader (power+vol down). In some conditions like this (battery drained, stuck on boot screen, etc.), you will need to hold button combos for a minute or more before it will reboot. So try to just hold the buttons longer. Also try to do this (hold for a minute+) for power+vol up (this button combo forces a reboot in most situations) or simply just the power button ("regular" power-on).
Power + vol up would have been the best way to force a reboot (works in virtually every condition short of a true brick), rather then let the battery drain to shut-off. Letting the battery drain to shutoff is never a great idea, if it can be avoided, for the reason already mentioned.
redpoint73 said:
First, let the phone charge on wall socket for several hours. This is sometimes needed if the battery is allowed to drain to shutoff, and there is unsufficient battery voltage to boot/power-on the phone.
There is no button combo to directly access recovery on this phone, so I think you mean you tried to boot to bootloader (power+vol down). In some conditions like this (battery drained, stuck on boot screen, etc.), you will need to hold button combos for a minute or more before it will reboot. So try to just hold the buttons longer. Also try to do this (hold for a minute+) for power+vol up (this button combo forces a reboot in most situations) or simply just the power button ("regular" power-on).
Power + vol up would have been the best way to force a reboot (works in virtually every condition short of a true brick), rather then let the battery drain to shut-off. Letting the battery drain to shutoff is never a great idea, if it can be avoided, for the reason already mentioned.
Click to expand...
Click to collapse
Oh man! I was freaking for a while. I tried like everything except holding the buttons down so long. That reset it. It booted. When it booted up I tried to update the with the OTA in settings and it locked again on bootscreen. I did the hard reset again. It didn't update. I want to update it to Android 6.0, but it keeps running into problems some error "unexpected contents on partition - installation aborted." Something like that.
Thinking of trying to flash the OTA or RUU. Do you think that is a good idea?
mkbeyer said:
Oh man! I was freaking for a while. I tried like everything except holding the buttons down so long. That reset it. It booted.
Click to expand...
Click to collapse
I did the same a while back. Found my M8 had powered off overnight. Tried the button combos, which didn't seem to work, and thought it was spontaneously bricked. Finally just tried holding power (or maybe power+vol up, don't remember exactly) for a long time, and it finally booted, leading to much relief.
mkbeyer said:
Thinking of trying to flash the OTA or RUU. Do you think that is a good idea?
Click to expand...
Click to collapse
Flash the OTA how?
RUU should be fine, if you version has an RUU.

Is it dead? No boot or led

Hola! Last night my phone freezed for a few seconds before shutting down. I tried to reboot with no luck. No buttons combos no charghing,nothing,not even the red led that use to blink when it happened before after shutting down. The battery was low then ,about 15% and shut down but I managed to get it working . Now I had the same percentage ,around 15-30% on battery. I let it charge for about 10 mins and then tried booting again. Power+ vol up booted and showed "Download mode" . I don't know if it was me or the phone itself but it booted and Google appeared. Then Those circles appeared and after a few moments the have frozen and the phone shut down. Attempted again with no luck. I unplugged it and let the matter for today. This morning I again tried to boot up ,after a few attempts it booted but only got the Google screen before it shut down again... I let it charge for about 2 hours but still no luck with it. Connected it to the PC ,got the sound of a new device then the error sound and message of the driver. Disconnected and connected again and I got only the driver error sound without the new device sound if I don't change the port. Interesting is that if I press any button combination or just power while connected to the computer,after about 20 seconds of pressing I get the sound of disconnected and/or driver error. That gives me hope that it's not dead at all.. Might the battery be the cause? Replacing it would be a cheaper solution without losing data...Opinions? Tips? I had 3 different dreams in which I solved the problem...but the reality is a nightmare ( Heeeelp
Well it still shows signs of litttle life: If I let it without pressing anthing ,just leave it alone for a night or more and try to boot i,the red led flashes so I plug it right away get to the battery charging screen and that's i...I still hope it's because of the battery thinking hat the battery regenerates but cannot hold for too long.

Stuck in low battery boot loop

Hello, Huawei gadget friends.
My watch started to go in to a "low power boot loop" a week ago so I left it alone hoping a full drain would restore it back to working condition, but alas not.
So now this is the situation:
1) press button, nothing happens
2) connect to power shows the charging icon (white battery with power sign) and then after a few mins commences a boot loop as follows
3) from the charging icon, then gives the "Device software can't be checked for corruption..." message
4) followed by the red Huawei logo, then a single vibrate and then back to step 3 above
5) removing the watch from the charger stops the boot loop but then shows the low battery icon (white battery with one bar).
In one or two occasions, I saw it boot up to the colorful spinning 4 android wear logo, but did not complete (did not show "Android Wear" before rebooting again.
I have tried getting it to recovery mode screen or fastboot but without success -- I keep getting the second buzz without fail.
When the beta of 1.5 came out, I tried it, but since then, have wiped my mac and don't have the adb/fastboot software anymore. From reading the forums, there is now some new software called TWRP. Please advise what I can do.
Would I be right to suspect that it is some battery problem? Is it beyond help? :crying:
Thanks in advance!
MMM
Edit: I have also left it on for several hours charging (and rebooting constantly), thinking that perhaps it is just low battery -- but no success.
I'm experiencing the same problem, i turned it off yesterday at 17% and connected to the pc this morning to charge. I immediately noticed that it started looping with the white icon and it doesn't turn on, nor boots into download mode.
Have you found any way to restore it?
Mine doesn't show the red HW logo, charged for some hours and nothing.
I noticed that the pc see that there's something connected, but keeps saying "USB not recognized". I don't know what to do, i may open up and disconnect the battery
EDIT: SOLVED, it was just the cable that broke somehow. I soldered a new cable to the circular base but that didn't work, but as soon as i received this i connected to the pc and started pressing the button randomly till it showed the battery logo and started charging
I got this when I plugged it into my laptop. Plugging it into a dedicated USB charger solved my problem - I suspect the power rating on the USB socket wasn't high enough to charge effectively or that the USB socket is faulty in some other way. From what I understand, not all USB sockets are equal in that some are suitable for high-drain devices, some not so much. So trying another USB port on your computer may also help (Unfortunately at the time I was backing up to an external HDD on the other USB so that option wasn't open to me).
guyz, i have tried my method it actually worked on Xperia X Perfomance
When it goes to Bootloop for Drained battery, i just plug the cable and perform activity block method By pressing and holing power and both volume up and down and when it hits the 1st viberation i just simply release the key. (remember dont hold it too much long after 1st single viberation just release the keys ) and your phone will go to block activity mode. charging light will change it colors from red to blue.. after 2 minutes just press power button then you ll get another viberation and your phone will be seen as charged 2% and then it will be normal again...
i think it happens when battery drained and phone is unexpectedly trying to go boot in first place.
thank you

Categories

Resources