[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] Pastahl:
Hello,

It seems that I've managed to screw up my SM-P600 (32g/wifi) filesystem (lost NAND - device?). Is there anything that can be done to fix this? When trying to boot in OS the tablet freeze, but I can still boot to recovery and download modes. Flashing stock rom seems to go trough with Odin, but results the same freezing boot.

Here's a brief index from my last attempt to figure out the problem. Below are numbered results/errors etc gathered when I tried to figure out the problem.

1. CAUSE: Tried to Flash Hyperdrive ROM with TWRP. It seemed to go well, but first boot resulted freezing after Hyperdrives, “BIOS-bootupanimation”.

2. ATTEMPT TO FIX: Trying to flash back to Stock ROM. Flash seems to go through, but still freezes at startup.

3. Boot tablet to Stock recovery. shows Errors (check below for details) but the recovery is functional.

4. Flashing CWM to tablet in order to get better info about what's happening. Flashing goes Ok.

5. Boot to CWM-recovery, Boots to recovery with errors (details below)

6. Trying to run Data wipe / Factory reset -> results in Errors. (details below)

7. Checking log file from CWM advanced-menu shows errors

8. Trying to format /data "manually" from CWM (goes through, but doesn't actually seem to work)

9. Trying to figure it out with ADB Shell. Checking ls results in root directory (check below for results)

10. ADB cat /proc/mounts. Results with errors=panic lines (details below)

11. ADB cat /proc/partitions

12. ADB cat /proc/devices.

I compared the results in this article: www-imajeenyus-com/computer/20130301_android_tablet/android/partitions-html (URL-posting was forbidden, so pleace replace "-" with "." to get the link working)

It seems to me that I'm missing the NAND-device and it's partitions?

This is of course just my mundane attempt to figure this out. I'd really appreciate any experienced feedback if I'm on the right track here, and if I am, is there any hope for me to get my Tablet running again?

Any help is would be much appreciated.

***************************************** DETAILED RESULTS **************************************************

1. Tried to Flash Hyperdrive ROM with TWRP. It seemed to go well, but first boot resulted freezing after Hyperdrives, “BIOS-bootupanimation”.

I tried to wipe everything again with TWRP, and flash again from external SD, but with same results (doesn't boot).

2. Trying to flash Stock ROM

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> P600XXUCND3_P600OXACND3_HOME.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/005> Added!!

<ID:0/005> Odin v.3 engine (ID:5)..

<ID:0/005> File analysis..

<ID:0/005> SetupConnection..

<ID:0/005> Initialzation..

<ID:0/005> Get PIT for mapping..

<ID:0/005> Firmware update start..

<ID:0/005> SingleDownload.

<ID:0/005> sboot.bin

<ID:0/005> NAND Write Start!!

<ID:0/005> boot.img

<ID:0/005> recovery.img

<ID:0/005> system.img

<ID:0/005> cache.img

<ID:0/005> hidden.img

<ID:0/005> RQT_CLOSE !!

<ID:0/005> RES OK !!

<ID:0/005> Removed!!

<ID:0/005> Remain Port .... 0

<OSM> All threads completed. (succeed 1 / failed 0)

Result: tablet boots, shows the blue spinning animation and then with freezes with SAMSUNG-logo on screen.

3. Boot tablet to Stock recovery. It shows errors.

E:failed to mount /data (Invalid argument)

can't mount '/data'(Invalid argument)

E:failed to mount /data (Invalid argument)

can't mount '/data/log/recovery_log.txt'(Invalid argument)

4. Flashing CWM to tablet with Odin.

<ID:0/004> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> philz_touch_6.25.7-lt03wifi.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/004> Odin v.3 engine (ID:4)..

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

<ID:0/004> Get PIT for mapping..

<ID:0/004> Firmware update start..

<ID:0/004> SingleDownload.

<ID:0/004> recovery.img

<ID:0/004> NAND Write Start!!

<ID:0/004> RQT_CLOSE !!

<ID:0/004> RES OK !!

<ID:0/004> Removed!!

<ID:0/004> Remain Port .... 0

<OSM> All threads completed. (succeed 1 / failed 0)

5. Booting to CWM-recovery shows error:

E:could not mount /data to setup /data/media path!

6. Trying to run Data wipe (previously I formatted system, dalvik, cache)

-- Wiping data...

Formatting /data...

Error mounting /data!

Skipping format...

Formatting /cache

Formatting /sd-ext

E:unknown volume for path [/sd-ext]

Formatting /sdcard/.android_secure!

Error mounting /sdcard/.android_secure!

Skipping Format...

Formatting /storage/sdcard1/.androidsecure...

Data wipe complete

-- Wiping system

Formatting /system

Now flash new ROM!

7. Checking log file from CWM advanced-menu shows errors

mount: mounting /dev/block/mmcblk0p21 on /data failed /Invalid agrument)

W:failed to mount /dev/block/mmcblk0p21 on /data (File exists)

8. Trying to format /data "manually" from CWM

Under Mounts and Storage Menu

- format /data and /data/media (/sdcard)

outputs:

Formatting data (takes about 3 mins)

Done.

Result: still getting the same errors shown above

9. Trying to figure it out with ADB Shell ls

~ # ls

ls

boot init sd-ext

cache init.rc sdcard

data internal_sd seapp_contexts

datadata lpm.rc sepolicy

default.prop mnt storage

dev proc sys

emmc property_contexts system

etc recovery tmp

external_sd res ueventd.rc

file_contexts root ueventd.universal5420.rc

fstab.universal5420 sbin

~ # cd data

cd data

/data # ls

ls

media

/data #

10. ADB cat /proc/mounts

~ # cat /proc/mounts

cat /proc/mounts

rootfs / rootfs rw 0 0

tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0

devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0

proc /proc proc rw,relatime 0 0

sysfs /sys sysfs rw,seclabel,relatime 0 0

selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0

tmpfs /tmp tmpfs rw,seclabel,relatime 0 0

tmpfs /storage tmpfs rw,seclabel,relatime,mode=050,gid=1028 0 0

tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0

tmpfs /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,gid=1000 0 0

/dev/block/mmcblk0p21 /data ext4 rw,seclabel,relatime,discard,journal_checksum,j

ournal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0

/dev/block/mmcblk0p19 /cache ext4 rw,seclabel,relatime,discard,journal_checksum,

journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0

~ #

11. ADB cat /proc/partitions

~ # cat /proc/partitions

cat /proc/partitions

major minor #blocks name

179 0 30535680 mmcblk0

179 1 4096 mmcblk0p1

179 2 4096 mmcblk0p2

179 3 20480 mmcblk0p3

179 4 4096 mmcblk0p4

179 5 4096 mmcblk0p5

179 6 4096 mmcblk0p6

179 7 4096 mmcblk0p7

259 0 8192 mmcblk0p8

259 1 8192 mmcblk0p9

259 2 8192 mmcblk0p10

259 3 8192 mmcblk0p11

259 4 4096 mmcblk0p12

259 5 20480 mmcblk0p13

259 6 4096 mmcblk0p14

259 7 4096 mmcblk0p15

259 8 20480 mmcblk0p16

259 9 12288 mmcblk0p17

259 10 4096 mmcblk0p18

259 11 204800 mmcblk0p19

259 12 2465792 mmcblk0p20

259 13 27709440 mmcblk0p21

179 24 512 mmcblk0rpmb

179 16 4096 mmcblk0boot1

179 8 4096 mmcblk0boot0

179 32 30948352 mmcblk1

179 33 30944256 mmcblk1p1

~ #

12. ADB cat /proc/devices

Block devices:

1 ramdisk

259 blkext

7 loop

8 sd

65 sd

66 sd

67 sd

68 sd

69 sd

70 sd

71 sd

128 sd

129 sd

130 sd

131 sd

132 sd

133 sd

134 sd

135 sd

179 mmc

254 device-mapper

~ #