SM-T800 stuck on battery charging screen and wont boot - Galaxy Tab S Q&A, Help & Troubleshooting

So I was trying to install Marshmallow on my SM-T800 and got stuck on the Samsung splash screen. When trying to get back to recovery mode I accidentally booted into download mode. I exited download mode but now the tablet is stuck displaying the battery charging image, even when unplugged, and I cannot get it to boot.
Any ideas? Should I just leave it alone for a few days to let the battery drain and then try booting again?

jburdick7 said:
So I was trying to install Marshmallow on my SM-T800 and got stuck on the Samsung splash screen. When trying to get back to recovery mode I accidentally booted into download mode. I exited download mode but now the tablet is stuck displaying the battery charging image, even when unplugged, and I cannot get it to boot.
Any ideas? Should I just leave it alone for a few days to let the battery drain and then try booting again?
Click to expand...
Click to collapse
Have you tried all the key combinations?
Do you have a USB JIG?

I'm not sure how installing a rom has affected the bootloader as that's pretty much impossible.
Regardless of what's on screen now, hold POWER + HOME + VOL DOWN until download mode appears.
If still no response you may have to wait until the batter dies.

Related

[Q] Stuck in Boot Loop

Hello
Have a GS3 running Rootbox 4.2. Was running stable for probably around 6 months, no issues at all except for the occasional random reboot which seems to plague all S3s.
Felt it vibrate in my pocket, assumed I had a message. But when I looked it was restarting. It gets to the rom loading screen then abruptly restarts.
Now it even doesn't get that far. The samsung screen shows up and the phone restarts in a loop.
Cannot stay booted into recovery. CWM recovery screen shows for about 2-3 secs then phone restarts.
Download mode through odin works, but I'd like to avoid wiping everything if at all possible.
thank you for any help.
an easy try to fix is to pull battery , wait a couple minutes and then either just hold power button till vibrate or do button combo to get to recovery.
"all i can really do , is stay out of my own way and let the will of heaven be done"
Try re-flashing an updated version of CWM via Odin and see if you can remain in recovery mode.
Thanks for the replies
Tried pulling battery for few mins (actually a few days since I did not have time to mess with phone) - No good, phone gets partway through the rom load screen then reboots.
Tried the odin suggestion - home +vol. down+ power opens download mode, but download mode stays open for around 10-15 sec before the phone restarts itself.
I have tried swapping back to the oem battery since i have an extended battery and the problem still remains.
Sounds like a hardware problem to me since you can access download and recovery but it turns itself off. You've tried a couple of batteries so that kind of rules out any software issues.
Did you try booting the phone with a de-brick image from XDA?

s4 mini i9195 boot loop, no recovery, only download mode

Hey!
I was trying to find this problem all around, but no luck. So I'm setting up new thread. Hope not to get redundant
A never rooted S4 mini died for no reason. In the morning we found it powered off and it couldn't be charged, other battery didn't help, nothing.
Long story short I managed to wake it up after complete dissassemble and playing with the battery connectors.
Now it starts up, but after the Samsung Logo it reboots = boot loop.
When I try to enter recovery, it tries to enter (I can see the blue "recovery booting"), but reboots immediately again.
The only thing that works is Download Mode.
So I used Odin to flash all CWM, PhilZ and TWRP subsequently. I got a bit further: in recovery mode it says "No command", then the usual "# MANUAL MODE #" etc and after few seconds it reboots again. So I still can't use recovery.
Does this all mean that the internal SD is fried?
I just need to recover the photos, that's all...
Thanks!
Marek
personic said:
Hey!
I was trying to find this problem all around, but no luck. So I'm setting up new thread. Hope not to get redundant
A never rooted S4 mini died for no reason. In the morning we found it powered off and it couldn't be charged, other battery didn't help, nothing.
Long story short I managed to wake it up after complete dissassemble and playing with the battery connectors.
Now it starts up, but after the Samsung Logo it reboots = boot loop.
When I try to enter recovery, it tries to enter (I can see the blue "recovery booting"), but reboots immediately again.
The only thing that works is Download Mode.
So I used Odin to flash all CWM, PhilZ and TWRP subsequently. I got a bit further: in recovery mode it says "No command", then the usual "# MANUAL MODE #" etc and after few seconds it reboots again. So I still can't use recovery.
Does this all mean that the internal SD is fried?
I just need to recover the photos, that's all...
Thanks!
Marek
Click to expand...
Click to collapse
Same problem with mine I can get in to download mode but recovery mode just says recovery booting then it turns off and back on again in the same loop ie it boots samsung screen then turns off then back on again and so on, I've tried CWM and TWRP odin says everything is good, but i get the same recovery booting and the loop again!
anything else i can try?
thanks

I9195 (8Gb) on charge overnight, dead the following morning?

Hi guys,
I left my phone on charge overnight and in the morning it was off and wouldn't switch back on.
A debrick image allowed me to get the phone into ODIN download mode (i couldn't get into the recovery mode though).
I have tried several different roms and now (i think) its on a stock 4.4.2 rom.
Odin seems to flash the phone without any errors but upon reboot shows "Booting Recovery..." then gets stuck in a boot loop.
I have even tried CWM - Odin seems to flash it without a problem but when it reboots it just shows "Booting Recovery..." and gets stuck in a boot loop (I have tried the Up Volume + Home + Power with no success).
Since it was on the stock rom and has never had a custom rom on it (until lately trying to fix it) it seems likely that the flash storage is dead or has bad sectors?
Any ideas? I have never had a phone die like this before
Thanks
I have exaktly the same problem and i think we are not alone.
Have you tried all usual things e.g. battery pull?
see
http://www.smartmobilephonesolutions.com/content/android-stuck-startup-boot-loop

Need help troubleshooting this issue

Firstly thanks for taking the time to view this and helping me out.
Yesterday I was out and my Galaxy s4 mini l9190 was on and charging using a power bank, checked the battery status a couple hours after and the phone was switched off. I switched it back on and was working fine till I restarted it the phone got stuck on the boot logo (Samsung logo). I tried booting into recovery (twrp) and it got stuck on the boot logo for the recovery as well. When i reached home I tried using Odin to narrow my issues but it got stuck on initializing status.
Currently when I try to switch my phone on it vibrates and nothing shows up, same goes with trying to boot into recovery, nothing shows up just a single vibrate. Only thing works is Download Mode.
Recovery: TWRP
OS: CM 13
Things to consider:
1) Connecting a wall outlet to charge doesn't show the charging status.
2) Shows up on Odin.
3) Battery was supposed to change because I had draining issues.
I Tried:
1) Holding down power button for 30 seconds with no battery in place.
2) Charging it (no charging status showing)
Can anyone help me?

Stuck on boot screen after discharged battery

Hello everyone! My One M9 has been stuck on boot screen after it's battery drained completely. It runs AICP 8.1 and adb does work, but I get booted into system every time I try to boot or reboot into bootloader, recovery, or download mode. The htc splash screen also takes longer before trying to boot the system. I tried unplugging the battery but it didn't have any effect. Does anyone have any tips or ideas?
Faulty button?. If it bypasses download mode you might have a stuck vol- button.

Categories

Resources