[Hisense Sero 7 Pro Questions & Answers] jhunjhuniya:
Bricked S7Pro after e2fsck errors

Somewhat adb/fastboot literate user who used DoPa versions for a while. Tablet was on most of the time. Then disk errors (I guess). A couple of times, booting into (PhilZ 6.58, CWM 6.0.5.1, dopa 2.61) and running e2fsck -y on /system and /data partitions would clear errors.

So I got tired and tried sero7pro-aosp500 beta2 and associated gapps and nexus 7 spoof for a change. It installed fine, and booted, but froze soon after.

Rebooting to recovery (after a battery rundown or two, taking the back cover off, finding out that you must get into fastboot mode and keep tab on for it to recharge and not power off) still works, and fastboot still works. Adb is still available.

But flashing anything makes no difference. e2fsck -y runs into endless errors and does not recreate ext3 journal, so /data or /system will not mount. Here is the output of /proc/partitions

179 0 7634944 mmcblk0

179 1 2048 mmcblk0p1

179 2 34816 mmcblk0p2

179 3 32768 mmcblk0p3

179 4 65536 mmcblk0p4

179 5 8192 mmcblk0p5

179 6 8192 mmcblk0p6

179 7 786432 mmcblk0p7

179 8 524288 mmcblk0p8

179 9 2048 mmcblk0p9

179 10 32768 mmcblk0p10

179 11 262144 mmcblk0p11

179 12 5832704 mmcblk0p12

179 32 2048 mmcblk0boot1

179 16 2048 mmcblk0boot0

This still looks ok.

-------------

~ # parted /dev/block/mmcblk0

GNU Parted 1.8.8.1.179-aef3

Using /dev/block/mmcblk0

Welcome to GNU Parted! Type 'help' to view a list of commands.

(parted) print

print

Error: /dev/block/mmcblk0: unrecognised disk label

(parted)

----------------

This one I am not sure is right anymore. Finally,

~ # fdisk /dev/block/mmcblk0

Device contains neither a valid DOS partition table, nor Sun, SGI, OSF or GPT disklabel

Building a new DOS disklabel. Changes will remain in memory only,

until you decide to write them. After that the previous content

won't be recoverable.

The number of cylinders for this disk is set to 238592.

There is nothing wrong with that, but this is larger than 1024,

and could in certain setups cause problems with:

1) software that runs at boot time (e.g., old versions of LILO)

2) booting and partitioning software from other OSs

(e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): p

Disk /dev/block/mmcblk0: 7818 MB, 7818182656 bytes

4 heads, 16 sectors/track, 238592 cylinders

Units = cylinders of 64 * 512 = 32768 bytes

Device Boot Start End Blocks Id System

Command (m for help):

-----------------

is empty.

Can not flash another recovery, no other ROM, boot, system, nothing changes the existing philZ recovery.

fastboot says transfer is ok for flashes, but nothing changes.

Can run mkfs.ext2 /dev/block/mmcblk0p5 and

mkfs.f2fs /dev/block/mmcblk0p12 without errors,

but they will still not mount after reformatting.

Recovery will not format /system or /data. f2fs or ext4 change has no impact.

Here is a typical recovery log, washed out on reboot:

mount: mounting /dev/block/platform/sdhci-tegra.3/by-name/UDA on /data failed: Invalid argument

W:failed to mount /dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 (File exists)

mount: mounting /dev/block/platform/sdhci-tegra.3/by-name/UDA on /data failed: Invalid argument

W:failed to mount /dev/block/platform/sdhci-tegra.3/by-name/UDA /data f2fs (File exists)

mount: mounting /dev/block/platform/sdhci-tegra.3/by-name/UDA on /data failed: Invalid argument

W:failed to mount /dev/block/platform/sdhci-tegra.3/by-name/UDA /data f2fs (File exists)

I:Cannot open /data/philz-touch/philz-touch_6.ini

I:use_qcom_time_offset set to default (0)

Command: "/sbin/recovery"

ro.sf.lcd_density=213

ro.com.android.dateformat=MM-dd-yyyy

ro.boot.selinux=permissive

ro.boot.serialno=015d4a826d541c09

ro.boot.commchip_id=2

ro.wifi.channels=

ro.allow.mock.location=0

ro.audio.monitorOrientation=true

ro.board.platform=tegra

ro.build.id=KTU84Q

ro.build.date=Mon Nov 10 17:49:00 EST 2014

ro.build.date.utc=1415659740

ro.build.host=fong

ro.build.tags=test-keys

ro.build.type=userdebug

ro.build.user=dolorespark

ro.build.display.id=dopa_m470-userdebug 4.4.4 KTU84Q eng.dolorespark.20141110.174749 test-keys

ro.build.product=m470

ro.build.version.sdk=19

ro.build.version.release=4.4.4

ro.build.version.codename=REL

ro.build.version.incremental=eng.dolorespark.20141110.174749

ro.build.description=dopa_m470-userdebug 4.4.4 KTU84Q eng.dolorespark.20141110.174749 test-keys

ro.build.fingerprint=Hisense/dopa_m470/m470:4.4.4/KTU84Q/eng.dolorespark.20141110.174749:userdebug/test-keys

ro.build.characteristics=tablet

ro.config.ringtone=Ring_Synth_04.ogg

ro.config.alarm_alert=Alarm_Classic.ogg

ro.config.notification_sound=pixiedust.ogg

ro.secure=1

ro.zygote.disable_gl_preload=true

ro.carrier=wifi-only

ro.product.cpu.abi=armeabi-v7a

ro.product.cpu.abi2=armeabi

ro.product.name=dopa_m470

ro.product.board=

ro.product.brand=Hisense

ro.product.model=Sero 7 Pro

ro.product.device=m470

ro.product.locale.region=US

ro.product.locale.language=en

ro.product.manufacturer=Hisense

ro.baseband=unknown

ro.bootmode=unknown

ro.hardware=m470

ro.opengles.version=131072

ro.revision=0

ro.serialno=xxxxx

ro.bootloader=unknown

ro.debuggable=1

ro.factorytest=0

tf.enable=y

drm.service.enabled=true

net.bt.name=Android

net.change=net.bt.name

init.svc.adbd=running

init.svc.vold=running

init.svc.healthd=running

init.svc.ueventd=running

init.svc.recovery=running

init.svc.setup_adbd=stopped

wifi.interface=wlan0

wifi.supplicant_scan_interval=15

agpsd.dev_path=/dev/ttyACM4

agpsd.lib_path=/system/lib/libagps-brcm4751.so

debug.nfc.se=false

debug.nfc.fw_download=false

dalvik.vm.heapsize=384m

dalvik.vm.lockprof.threshold=500

dalvik.vm.heapmaxfree=8m

dalvik.vm.heapminfree=512k

dalvik.vm.dexopt-flags=m=y

dalvik.vm.heapstartsize=8m

dalvik.vm.heapgrowthlimit=64m

dalvik.vm.stack-trace-file=/data/anr/traces.txt

dalvik.vm.heaptargetutilization=0.75

persist.sys.usb.config=mtp,adb

persist.sys.dalvik.vm.lib=libdvm.so

persist.tegra.nvmmlite=1

service.adb.root=1

I:Checking for extendedcommand & OpenRecoveryScript...

I:Ignoring 'extendedcommand' boot-script: file not found

I:Ignoring 'openrecoveryscript' boot-script: file not found

I:Checking for recovery lock...

W:failed to mount /dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 (Invalid argument)

mount: mounting /dev/block/platform/sdhci-tegra.3/by-name/APP on /system failed: Invalid argument

W:failed to mount /dev/block/platform/sdhci-tegra.3/by-name/APP /system f2fs (Invalid argument)

mount: mounting /dev/block/platform/sdhci-tegra.3/by-name/APP on /system failed: Invalid argument

W:failed to mount /dev/block/platform/sdhci-tegra.3/by-name/APP /system f2fs (Invalid argument)

E:Can't open /cache/recovery/log

E:Can't open /cache/recovery/last_log

E:Can't open /cache/recovery/last_install

W:Can't unlink /cache/recovery/command

---------------

/cache seems hosed. formatting cache seems ok from recovery but mounting /cache gives:

~ # mount /cache

~ # ls /

boot etc proc seapp_contexts

cache external_sd property_contexts sepolicy

charger file_contexts recovery storage

data fstab.m470 res sys

datadata init root system

default.prop init.rc sbin tmp

dev internal_sd sd-ext ueventd.m470.rc

emmc mnt sdcard ueventd.rc

~ # ls /cache

ls: /cache/lost+found: I/O error

ls: /cache/recovery: I/O error

-------------

The recovery log above shows an attempt to go back to 4.4.4 as well.

Again, sideloading fails due to /system /data errors. Script is unable to handle e2fsck, I/O errors. e2fsck -y will not finish with a clean partition on /system.

Anyone including the RoM developer got time to waste on this seemingly impossible problem?