Hi,
I have the SM-T310 Galaxy Tab 3 8.0 variant with stock android 4.4.2 and was rooted with Xposed Framework installed. I need some help and advice on how to fix it, if possible, or whether it's beyond fixing.
A few days ago my tablet was working fine and there was no indication of anything wrong. I put it on charge as the battery was getting low from watching YouTube. I came back to it a couple of hours later to find it stuck on the Samsung boot screen, but was able to get into Odin mode after some time (I tried to get into recovery but it wouldn't work). It had some trouble being recognised in the computer at first. I tried flashing the stock ROM again several times, but it failed each time with no useful error code.
I then tried rebooting which came up with a firmware upgrade error and asked me to recover it with Kies. I tried that to no avail. Firstly tried with Kies 3 which said the device wasn't compatible, even though I have plugged it into Kies before and it has been recognised and worked fine. I then tried the older Kies which wouldn't work either. Then, I opened Odin again and found it was being seen even with this error screen instead of Odin mode. I tried flashing again but still didn't work and had a COM port error instead. I did make sure that Kies was completely shut before attempting to flash. I even attempted to perform a proper Nand erase and repartition but that also didn't work and failed.
I couldn't do anymore after that due to it being so late at night, and had no choice but to let the battery drain. It now won't power on at all, nor does it appear to be charging, although there is something under a metal plate (not entirely sure what it is but possibly the memory or CPU chip), that gets warm when plugged in and slightly warmer when trying to power it on.
I did try a different computer, different cables and different operating systems to ensure none of those were contributing.
I have also tried to use ADB to get the device to be 'seen' but that didn't work either (used 'adb devices' command), but I'm new to ADB so don't understand it too well yet.
I appreciate any help given and hope I've given enough detail. Thank-you for your time,
Jed.
I have the SM-T310 Galaxy Tab 3 8.0 variant with stock android 4.4.2 and was rooted with Xposed Framework installed. I need some help and advice on how to fix it, if possible, or whether it's beyond fixing.
A few days ago my tablet was working fine and there was no indication of anything wrong. I put it on charge as the battery was getting low from watching YouTube. I came back to it a couple of hours later to find it stuck on the Samsung boot screen, but was able to get into Odin mode after some time (I tried to get into recovery but it wouldn't work). It had some trouble being recognised in the computer at first. I tried flashing the stock ROM again several times, but it failed each time with no useful error code.
I then tried rebooting which came up with a firmware upgrade error and asked me to recover it with Kies. I tried that to no avail. Firstly tried with Kies 3 which said the device wasn't compatible, even though I have plugged it into Kies before and it has been recognised and worked fine. I then tried the older Kies which wouldn't work either. Then, I opened Odin again and found it was being seen even with this error screen instead of Odin mode. I tried flashing again but still didn't work and had a COM port error instead. I did make sure that Kies was completely shut before attempting to flash. I even attempted to perform a proper Nand erase and repartition but that also didn't work and failed.
I couldn't do anymore after that due to it being so late at night, and had no choice but to let the battery drain. It now won't power on at all, nor does it appear to be charging, although there is something under a metal plate (not entirely sure what it is but possibly the memory or CPU chip), that gets warm when plugged in and slightly warmer when trying to power it on.
I did try a different computer, different cables and different operating systems to ensure none of those were contributing.
I have also tried to use ADB to get the device to be 'seen' but that didn't work either (used 'adb devices' command), but I'm new to ADB so don't understand it too well yet.
I appreciate any help given and hope I've given enough detail. Thank-you for your time,
Jed.
from xda-developers http://ift.tt/28W9DOY
via IFTTT
No comments:
Post a Comment