It may not have bad memory, just simply corrupted. No guarantees here but it's worth trying to run WebOS doctor on it. If it fails at 12%, then it's likely corrupted from a failed Android install. There are steps in the webosnations.com forums and rootzwiki on steps to fix the issue either using tpdebrick or running command line to rebuild the partition structure. It actually takes a lot to truly kill a TP so if you have not already tried the above it's worth a shot.
+
It may not have bad memory, just simply corrupted. No guarantees here but it's worth trying to run WebOS doctor on it. If it fails at 12%, then it's likely corrupted from a failed Android install. There are steps in the webosnations.com forums and rootzwiki on steps to fix the issue either using tpdebrick or running command line to rebuild the partition structure. It actually takes a lot to truly kill a TP so if you have not already tried the above it's worth a shot.
+
+
If it's not been charged for a while and does not come up with the included barrel charger, connect it to one from a cell phone for a day or two and it will slow charge it enough for the TP charger to finish the job. There is a known issue with the charging circuit and once the battery level gets too low, this is the way to get around it.
It may not have bad memory, just simply corrupted. No guarantees here but it's worth trying to run WebOS doctor on it. If it fails at 12%, then it's likely corrupted from a failed Android install. There are steps in the webosnations.com forums and rootzwiki on steps to fix the issue either using tpdebrick or running command line to rebuild the partition structure. It actually takes a lot to truly kill a TP so if you have not already tried the above it's worth a shot.