soft brick - possible corrupted internal SD

le.lucien

New member
Nov 29, 2015
1
0
0
Hello,

After a shutdown due to low battery, my tablet is soft bricked. :/ I suspect a corruption of the internal SD or the flash chip, I'm not really sure.

My tablet is unlocked, I have cwm 6.0.5.1 installed. If I remember correctly, I had some cromi-X rom.

I have access to the bootloader (11.4.1.29) and the recovery but the manipulations I'm doing aren't working.

When into recovery, I get the messages e: can't mount/open /cache/recovery/log (last_log, last_install).

I tried flashing all kind of roms, they all failed, the most successful install ended with an error creating symlinks.

Tried all the wipe/format/factory reset options in the recovery, most of the time, I get the "error mounting /data", "error mounting /sdcard/.android_secure".
I can mount /system but it doesn't work for /cache and /data.

I can fastboot boot other recoveries (other cwm, twrp) but somehow can't flash. I'm not getting any error, they're just not sticking.

I tried manually formatting with e2fsck commands but I get an error related with superblocks.

Here's my cat log /proc/partitions :
179 0 30535680 mmcblk0
179 1 8192 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 8192 mmcblk0p3
179 4 2097152 mmcblk0p4
179 5 897024 mmcblk0p5
179 6 512000 mmcblk0p6
179 7 8192 mmcblk0p7
179 8 4096 mmcblk0p8
179 9 16384 mmcblk0p9
179 10 8192 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 4096 mmcblk0p12
179 13 4096 mmcblk0p13
179 14 26916864 mmcblk0p14
179 32 4096 mmcblk0boot1
179 16 4096 mmcblk0boot0

Here's what "df" is showing :
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 960124 128 959996 0% /dev
/dev/block/platform/sdhci-tegra.3/by-name/APP
2064208 1110432 953776 54% /system

I've done so many things to try fixing this with all I could find googling, I may have done some mistakes in the process but I didn't spot any change. The only thing I haven't tried yet is to install/boot a rom from the external SD. But I'm not experienced enough for that, I prefer to keep as a last resort.

I just ran a dmesg command, there's several error messages there, maybe that'll help. As I can't post URLs yet, here's a sample :
<4>[ 12.192838] lost page write due to I/O error on mmcblk0p5
<3>[ 19.972559] mmcblk0: mmc_blk_err_check: general error sending status command, card status 0x80900
<4>[ 19.981660] mmcblk0: retrying write for general error
<4>[ 19.986857] lost page write due to I/O error on mmcblk0p14
<3>[ 20.217027] mmcblk0: packed cmd failed, nr 20, sectors 280, failure index: 0
<4>[ 20.693382] JBD2: recovery failed
<3>[ 20.696941] EXT4-fs (mmcblk0p14): error loading journal

I'm not sure how it works, maybe it's possible to manually wipe everything, keeping the bare minimum to recreate the partitions and push the files.

I may have missed something, some help would be really appreciated. ^^

Thanks in advance !
 

Redwave9

New member
Apr 13, 2016
1
0
0
Same Problem here as well!

I have the same problem. Seems like the /cache and /data partitions are corrupt.

I have full CWM and Bootloader access with ADB and fastboot. I cannot flash new recoveries. Cannot mount /data or /cache.

Repairing the partitions with e2fsck get me nowhere as well.

I can shell in and run parted on the /data (mmcblk0p14) and /cache (mmcblk0p5) blocks. I attempted to recreate the partitions using parted but keep getting input/output error during write on /dev/block/mmcblk...

Can't even delete the old partitions in /data (mmcblk0p14) and /cache (mmcblk0p5) with fdisk. get failure error.

Any ideas how to overcome the partition recreation errors? Are we screwed?
 
Last edited:

realmastah

Member
Mar 4, 2009
8
4
0
Same problem here as well.
had cromix up and running, then suddenly black screen. Recovery working good, but mount errors. Cannot restore nandroid or flash any kind of rom.
 

Jerry1996

Member
Oct 7, 2013
26
14
0
Same problem here as well.
had cromix up and running, then suddenly black screen. Recovery working good, but mount errors. Cannot restore nandroid or flash any kind of rom.
If you use TWRP, first try to wipe dalvik cache only and then try again to flash a rom or to restore a nandroid backup. This problem is TWRP related...
 
  • Like
Reactions: realmastah

tf701mega

Member
Apr 29, 2014
23
2
0
Peterborough
I had this exact issue when i was moving to lollipop. I tried to flash to zombi-x and it caused this issue. every time i turned the device on it would boot direct to recovery. I was unable to restore backups, flash new roms... nothing worked. In the end, i formatted my data partition and put blisspop on my external sd. After the format it took the new rom and has been running amazingly well since then.
 

realmastah

Member
Mar 4, 2009
8
4
0
If you use TWRP, first try to wipe dalvik cache only and then try again to flash a rom or to restore a nandroid backup. This problem is TWRP related...
thanks for the suggestion, tried it without success.
meanwhile i sent the device back as it was still under warranty, got refund.