• Samsung Galaxy Tab Pro 8.4 Wi-Fi (SM-T320 or mondrianwifiue)
  • Rooted with cf auto root using superSu v2.82
  • custom recovery TWRP 3.1.1-0
  • Android version stock 4.4.2
  • Kernel version 3.4.0-4441590

Within android OS the tablet randomly crashes and then bootloops when disconnected from the charger. Intrestingly though during the bootloop sometimes the screen flickers before shutting down and rebooting.

The bootloop stops after being shutdown for a while or if the charger get's plugged into the tablet.

Oddly however, when booted into the custom recovery TWRP there is no issue. Even if entering TWRP during the bootloop. The bootloop stop until trying to boot back into the system.

I recorded a logcat of an initial crash. As far as kernel logs here is the Dmesg after the bootloop. The last_kmsg was blank.

I suspect the battery connection is the culprit but I do not know why there is no issues within TWRP.

Does this look like a software issue or a hardware issue?

Thank you

1 Answer 1


You are right about the battery connection; try this trick: 1. Hold down power button for 10-15 sec while keeping it plugged in 2. When the tablet powers down and shows charging indicator, remove the cable and it should simulate removing the battery.

There was a constant error with sec_fuelgauge which is a process that regulates battery on hardware level. Check to see error at line 955 and so on later.

  • That trick for simulating the battery pull trick did not work but thank you for your response. What make you think it is a battery connection issue? Was it from the logs or my explanation?
    – Bo Lawson
    Aug 24, 2017 at 19:25
  • 1
    The logs. There was a constant error with sec_fuelgauge which is a process that regulates battery on hardware level. Aug 24, 2017 at 19:28
  • Great and thanks, it has been a bit since I have read kernel logs. I slightly remember that error -110 ment a lack of power for usb but I was not totally sure. You should put the part about the logs in your answer.
    – Bo Lawson
    Aug 24, 2017 at 19:53
  • Edited the answer. Maybe backup your data and factory reset? It works wonders for most problems which you can fix. If it is a hardware problem, you might be out of luck (I really don't think it is) Aug 24, 2017 at 20:18

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .