[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] fc_android:
Hi folks,

I'm sorry for posting this but I need some of expertise here, because I managed to brick my Samsung Galaxy Tab 10.1 (IO Edition) and I've tried what I know and what I can find from searching here and on other boards.

The basic problem I believe is that I think the /data partition is trashed. I can't mount it from clocksworksmod, or from a recovery adb shell, and it seems like my internal storage is no longer visible.

1. If I'm booted into clockworksmod, and am in an adb shell, doing

"mount /data" results in error:

mount: mounting /dev/block/mmcblk0p8 on /data failed: Invalid argument

2. I can't see my internal storage anymore... Error:

"Unable to open ums lunfile" No such file or directory".

3. I've tried to wipe the data partition, but it no longer wipes. And I'm unable to do any recovery from clockworksmod.

4. I've tried to manually fastboot flash the boot/system/data from the 3.1 OTA image from droidbasement, but that didn't boot at all (stuck at the Samsung Galaxy Tab 10.1 splash screen)

http://droidbasement.com/db-blog/?p=2035

5. I've followed the direction to using Odin 3 to reflash my tablet from the suggestion of this thread

http://xdaforums.com/showpost.php?p=14011086&postcount=26

When I did this, it boots up, but it's stuck in a "enter a password screen". I never locked this tablet, and I still can't mount the data partition and the internal storage is still not visible.

Does anyone have any suggestions on how to fix this? Some background information about what I did to get to this nightmare state.

*I was running clockworksmod 3.1.0.1 as the recovery image

*I successfully updated my tablet to HC 3.1 with the OTA update, and it booted and ran fine.

*After my HC 3.1 update, I rebooted into recovery because I wanted to take a backup of my system using clockworksmod. (Go figure that my decision to do a backup backup would end up causing this)

*For whatever reasons, I stupidly entered "reboot recover" from a adb root shell, and the device went into a hung state.

*I powered down/and powered back up by holding the power button for a few seconds....The tablet ended up going into a reboot loop.

*From the adb logcat, it appears that the /data partition was being mounted in read-only mode

--------- beginning of /dev/log/main

I/DEBUG ( 90): debuggerd: May 5 2011 01:05:44

I/Netd ( 89): Netd 1.0 starting

I/ ( 96): ServiceManager: 0x13858

E/DataRouter( 102): Main entered

E/DataRouter( 102): Data Router: INIT+

E/DataRouter( 102): dr_pcsync_init

E/DataRouter( 102): dr_init_pcsync_ipc

--------- beginning of /dev/log/system

I/Vold ( 88): Vold 2.1 (the revenge) firing up

D/Vold ( 88): USB mass storage support is not enabled in the kernel

W/Vold ( 88): dev_media add: /mnt/sdcard/usbStorage/->/devices/platform/tegra-ehci.0

D/Vold ( 88): void VolumeManager::handleBlockEvent(NetlinkEvent*)++ /devices/virtual/block/loop0

W/Vold ( 88): Can't handled block event for '/devices/virtual/block/loop0'

D/Vold ( 88): void VolumeManager::handleBlockEvent(NetlinkEvent*)++ /devices/virtual/block/loop1

W/Vold ( 88): Can't handled block event for '/devices/virtual/block/loop1'

D/Vold ( 88): void VolumeManager::handleBlockEvent(NetlinkEvent*)++ /devices/virtual/block/loop2

W/Vold ( 88): Can't handled block event for '/devices/virtual/block/loop2'

D/Vold ( 88): void VolumeManager::handleBlockEvent(NetlinkEvent*)++ /devices/virtual/block/loop3

...

...

..

W/UsageStats( 209): Error : java.io.IOException: Read-only file system reading data from file:/data/system/usagestats/usage-20110612

D/dalvikvm( 209): GC_CONCURRENT freed 139K, 4% free 6628K/6855K, paused 2ms+2ms

W/BatteryStats( 209): Error writing battery statistics

W/BatteryStats( 209): java.io.FileNotFoundException: /data/system/batterystats.bin.tmp (Read-only file system)

(more errors about read-only)....

*I rebooted into clocksworkmod recovery. And from a console shell on my laptop, did "adb shell"

*I did a mount "/data" from the adb shell, and tried to run e2fsck on the partition. e2fsck reported that my /data partition contained errors, and when I tried to run repair on it manually, it failed. When I did an "ls" on /data, I got a an IO error log/ directory.... I couldn't delete the log directory... At this point my internal storage was still available.

*I tried to do a wipe data/factory reset from clockworksmod recovery image...It failed.

*I then updated recovery to 3.2.0.1... And rebooted back into recovery.

*I then attempted to wipe the user data from clockworksmod recovery... This time it successfully wiped my user data... But it my internal storage (/sdcard) also disappeared and was gone.

* Tried to mount /data, and it failed....

mount: mounting /dev/block/mmcblk0p8 on /data failed: Invalid argument

*Tried to flash boot/system/data from the 3.1 HC zip file from droidbasement

http://droidbasement.com/db-blog/?p=2035

Flash seemed to complete, but can't boot at all

*Used Odin v3 and flashed the boot/system/recovery from bonzai3558

http://xdaforums.com/showpost.php?p=14011086&postcount=26

but while it booted, it was stuck at a password screen and neither the /data nor the /sdcard is pointing to a valid file system.

Really could appreciate anyone's suggestion. Is there a way to explicitly recreate the /data partition and what do I do about the internal storage not showing up?