[Hisense Sero 7 Pro Questions & Answers] jhunjhuniya:
Re. bricked S7P, still seeking resolution

Many thanks for taking the time. I suppose this is similar

<4>[ 5.211676:0] mmc0: Invalid maximum block size, assuming 512 bytes
<6>[ 5.218167:0] mmc0: no vmmc regulator found
<6>[ 5.226852:0] mmc0: SDHCI controller on sdhci-tegra.3 [sdhci-tegra.3] using ADMA
<3>[ 5.234577:0] sdhci-tegra sdhci-tegra.0: *** sdhci_tegra_probe 1081 cd_gpio = 69, present = 0***
<3>[ 5.243707:0] Failed gpio lp0 enable for irq=293, error=-22
<3>[ 5.249569:0] sdhci-tegra sdhci-tegra.0: SD card wake-up event registrationfailed with eroor: -22
<4>[ 5.261090:0] /home/dolorespark/andy/m470/kernels/kernel/drivers/mmc/host/sdhci-tegra.c - 1191: name=sdhci-tegra.0, cd_gpio=69
<4>[ 5.277109:1] mmc1: Invalid maximum block size, assuming 512 bytes
<6>[ 5.283393:1] mmc1: no vmmc regulator found
<6>[ 5.291067:1] mmc1: SDHCI controller on sdhci-tegra.0 [sdhci-tegra.0] using ADMA
<6>[ 5.298614:1] sdhci-tegra sdhci-tegra.2: vddio_sdmmc regulator not found: -19.Assuming vddio_sdmmc is not required.
<6>[ 5.309223:1] sdhci-tegra sdhci-tegra.2: vddio_sd_slot regulator not found: -19. Assuming vddio_sd_slot is not required.
<4>[ 5.321305:1] mmc2: Invalid maximum block size, assuming 512 bytes
<6>[ 5.327671:1] mmc2: no vmmc regulator found
<6>[ 5.335163:1] mmc2: SDHCI controller on sdhci-tegra.2 [sdhci-tegra.2] using ADMA
<6>[ 5.343699:0] mmc0: new high speed DDR MMC card at address 0001
<6>[ 5.350345:0] mmcblk mmc0:0001: Card claimed for testing.
<6>[ 5.356147:1] tegra-se tegra-se: tegra_se_probe: complete
<6>[ 5.356371:0] mmcblk0: mmc0:0001 SEM08G 7.28 GiB
<6>[ 5.356622:0] mmcblk0boot0: mmc0:0001 SEM08G partition 1 2.00 MiB
<6>[ 5.356871:0] mmcblk0boot1: mmc0:0001 SEM08G partition 2 2.00 MiB
<4>[ 5.361293:2] Primary GPT is invalid, using alternate GPT.
<6>[ 5.361375:2] mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12
<6>[ 5.393138:1] usbcore: registered new interface driver usbhid
<6>[ 5.393914:2] mmcblk0boot1: unknown partition table
<6>[ 5.404103:1] usbhid: USB HID core driver
<6>[ 5.406408:2] mmcblk0boot0: unknown partition table

This seems to be the problem:

<3>[ 9.752126:3] tlv320aic325x-codec tlv320aic325x-codec: Codec Firmware failed
<6>[ 9.768452:1] fs_mgr: fs_mgr_edit_fstab - found ext4 filesystem for /dev/block/platform/sdhci-tegra.3/by-name/APP
<6>[ 9.789153:1] fs_mgr: fs_mgr_edit_fstab - found ext4 filesystem for /dev/block/platform/sdhci-tegra.3/by-name/CAC
<6>[ 9.809686:0] fs_mgr: fs_mgr_edit_fstab - found unknown filesystem for /dev/block/platform/sdhci-tegra.3/by-name/UDA
<6>[ 9.834763:2] fs_mgr: fs_mgr_edit_fstab - found ext4 filesystem for /dev/block/platform/sdhci-tegra.3/by-name/MDM
<3>[ 9.850363:1] fs_mgr: Cannot open file /etc/extra.fstab
<6>[ 9.864903:2] fs_mgr: fs_mgr_edit_fstab - found ext4 filesystem for /dev/block/platform/sdhci-tegra.3/by-name/THD
<6>[ 10.023490:2] F2FS-fs (mmcblk0p12): mounting..
<6>[ 10.028989:2] F2FS-fs (mmcblk0p12): Magic Mismatch, valid(0xf2f52010) - read(0x0)
<3>[ 10.036555:2] F2FS-fs (mmcblk0p12): Can't find a valid F2FS filesystem in first superblock
<6>[ 10.045343:2] F2FS-fs (mmcblk0p12): Magic Mismatch, valid(0xf2f52010) - read(0x0)
<3>[ 10.052999:2] F2FS-fs (mmcblk0p12): Can't find a valid F2FS filesystem in second superblock
<3>[ 10.061442:2] F2FS-fs (mmcblk0p12): mount failed
<6>[ 10.173468:2] F2FS-fs (mmcblk0p12): mounting..

and after a few lines:

<6>[ 10.583529:3] F2FS-fs (mmcblk0p12): mounting..
<6>[ 10.588715:3] F2FS-fs (mmcblk0p12): Magic Mismatch, valid(0xf2f52010) - read(0x0)
<3>[ 10.596350:3] F2FS-fs (mmcblk0p12): Can't find a valid F2FS filesystem in first superblock
<6>[ 10.605075:3] F2FS-fs (mmcblk0p12): Magic Mismatch, valid(0xf2f52010) - read(0x0)
<3>[ 10.612724:3] F2FS-fs (mmcblk0p12): Can't find a valid F2FS filesystem in second superblock
<3>[ 10.621274:3] F2FS-fs (mmcblk0p12): mount failed
<6>[ 10.743467:1] F2FS-fs (mmcblk0p12): mounting..

Then, the date had obviously reset to 2011 due to battery depletion. Now set correctly. As before,

# mkfs.f2fs /dev/block/mmcblk0p12

F2FS-tools: mkfs.f2fs Ver: 1.2.0 (2013-10-25)

Info: sector size = 512
Info: total sectors = 11665408 (in 512bytes)
Info: zone aligned segment0 blkaddr: 512
Info: format successful

# mkfs.ext2 /dev/block/platform/sdhci-tegra.3/by-name/APP
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
49152 inodes, 196608 blocks
9830 blocks (5%) reserved for the super user
First data block=0
Maximum filesystem blocks=4194304
6 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840

shows no errors, this doesn't mean anything will install. Attempt to flash anything after this still leads to "unable to mount data" in the recovery log as reason for failure and:

<2>[ 1514.079402:1] EXT4-fs error (device mmcblk0p8): ext4_lookup:1044: inode #2: comm update_binary: deleted inode referenced: 11
<3>[ 1514.090975:1] Aborting journal on device mmcblk0p8-8.
<2>[ 1514.096215:1] EXT4-fs (mmcblk0p8): Remounting filesystem read-only
<2>[ 1514.104191:1] EXT4-fs error (device mmcblk0p8): ext4_put_super:801: Couldn't clean up the journal
<3>[ 1514.170305:1] EXT4-fs (mmcblk0p12): VFS: Can't find ext4 filesystem
<6>[ 1514.179751:2] tegradc tegradc.0: Using mode 800x1280 pclk=66773000 href=0 vref=1
<6>[ 1514.228044:2] F2FS-fs (mmcblk0p12): mounting..
<6>[ 1514.233554:2] F2FS-fs (mmcblk0p12): Magic Mismatch, valid(0xf2f52010) - read(0x0)
<3>[ 1514.241189:2] F2FS-fs (mmcblk0p12): Can't find a valid F2FS filesystem in first superblock
<6>[ 1514.250267:2] F2FS-fs (mmcblk0p12): Magic Mismatch, valid(0xf2f52010) - read(0x0)
<3>[ 1514.257967:2] F2FS-fs (mmcblk0p12): Can't find a valid F2FS filesystem in second superblock
<3>[ 1514.266419:2] F2FS-fs (mmcblk0p12): mount failed

Am now trying to get back to older cwm_touch or stock recovery to see if that helps. the ext4 and f2fs format seems to be the issue, nothing clears the journal, including dd if=/dev/zero of=/dev/block/...

Any further ideas?