[Acer Iconia A500] ser.:
Hi guys, I'm a new poster but long time reader of these boards, which helped me a lot since I got my A500 and an Android phone years ago. So far I've always found a ready solution for my 'droid needs and wants here but this time I think I've hit a bricked (tablet) wall! :laugh::crying:

My A500 has Skrilax_CZ's bootloader v9 with CWM v6.0.4.5 on the secondary partition and for more than a year has been running HenrikE's Android 4.4.4 (OmniROM unofficial) from this thread: http://xdaforums.com/showthread.php?t=2705989 The ROM has been going fine apart from a few random freezes but overall I like it.

Yesterday I was using the tablet to read a book and it started running Play store auto updates, I went to look at the store app to check which apps etc, then switched back to my book and the tablet froze. Normally I'd just long press the power button and then press it again to turn it on, so I did, only this time the ROM would not boot anymore and the tablet got stuck at the bootloader screen. I went into recovery and wiped cache and dalvik, no change. I went back to recovery and then I realized the partitions aren't mounting nor can be formatted! /system, /data, /cache, nothing:

E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p3

Without much hope I reinstalled the ROM with a data/factory reset and that of course didn't fix it. Tried to erase userdata and cache with fastboot, no change. It looks like either my internal SD card is broken/not found or my partitions are horribly corrupted? mmcblk0 isn't showing on /dev, see below from adb shell:

/dev/block # ls

loop0 loop2 loop4 loop6 mmcblk0p5 zram0

loop1 loop3 loop5 loop7 vold

/dev/block # fdisk /dev/block/mmcblk0

fdisk: can't open '/dev/block/mmcblk0'

/dev/block # parted

Error: No device found

Retry/Cancel? c

c

/dev/block #

/etc # cat fstab

/dev/block/mmcblk0p4 /cache ext4 rw

/dev/block/mmcblk0p8 /data ext4 rw

/dev/block/mmcblk0p3 /system ext4 rw

/etc # mount -t ext4 /dev/block/mmcblk0p8 /data

mount: mounting /dev/block/mmcblk0p8 on /data failed: No such file or directory

/etc #

Looking at other threads I guess the next step would be to try an APX reinstall however I use Linux and don't have a Windows machine around. While I can certainly spend my Easter break setting up a Windows Virtualbox :eek::crying: do you guys think this is a hardware fault or something that can be fixed? Many thanks for any input. Oh and yeah I do have the tablet's SBK number.

Edit:

I forgot to paste this:

/etc # cat recovery.fstab

# Android fstab file.

#<src> <mnt_point> <type> <mnt_flags> <fs_mgr_flags>

# The filesystem that contains the filesystem checker binary (typically /system) cannot

# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK

/dev/block/mmcblk0p3 /system ext4 ro,noatime wait

/dev/block/mmcblk0p4 /cache ext4 noatime,nosuid,nodev,errors=panic wait,check

/dev/block/mmcblk0p8 /data ext4 noatime,nosuid,nodev,errors=panic,discard,noauto_da_alloc wait,check

/dev/block/mmcblk0p2 /boot emmc defaults recoveryonly

/dev/block/mmcblk0p1 /recovery emmc defaults recoveryonly

/dev/block/mmcblk0p5 /misc emmc defaults recoveryonly

/dev/block/mmcblk0p3 /system ext4 defaults recoveryonly

/dev/block/mmcblk0p4 /cache ext4 defaults recoveryonly

/dev/block/mmcblk0p6 /flexrom ext4 defaults recoveryonly

/dev/block/mmcblk0p8 /data auto defaults recoveryonly

/dev/block/mmcblk1p1 /mnt/sdcard vfat defaults recoveryonly

# vold-managed volumes ("block device" is actually a sysfs devpath)

/devices/platform/sdhci-tegra.2/mmc_host/mmc1 /storage/sdcard1 auto defaults voldmanaged=sdcard:auto

/devices/platform/tegra-ehci.2 /storage/usbdisk0 auto defaults voldmanaged=sda:auto

/etc #