[One (M7) Q&A, Help & Troubleshooting] BlankOne:
First off I would like you to try with a different recovery. While 2.7.1.1 shod work fine in theory 2.6.3.3 has proven to be more reliable with less bugs than any other version. I recommend downloading 2.6.3.3

And flashing it with fastbootusb

fastboot flash recovery "nameofrecovery".img

Then

fastboot erase cache

Then

fastboot reboot-bootloader

Then select recovery from the bootloader menu. Once in recovery do the e2fsck in adb shell again. But I noticed first time you tried e2fsck you had a typo which would explain the no file directory error you got. See you appear to have used.

~ # e2fsck -fvy /dev/bl./ock/mmcblk0p35

You have a ./ separating the word "block"

It should read like this

~ # e2fsck -fvy /dev/block/mmcblk0p35

While your at it repeat the command on mmcblk0p36 and mmcblk0p37 then use the Format Data option in TWRPs Wipe options.

Then check the md5 for your rom if it's ok push and flash it. Hopefully that should get you up and running :fingerscrossed:[/QUOTE]

Downloaded TWRP 2.6.3.3, checked md5 and tried to flash it. Got this;

Clayton-Markels-iMac-3:android thecdmarkels$ ./fastboot flash recovery twrp.2.6.3.3.img

sending 'recovery' (9184 KB)...

OKAY [ 1.083s]

writing 'recovery'...

FAILED (remote: image update error)

finished. total time: 2.256s

Restarted, tried again, same result

When I boot 2.6.3.3 from fastboot it asks for a password in the device (which I don't have/never put one on) and won't recognize the phone in the command window on my computer.

Booted 2.7.1.0 from fastboot and ran

~ # e2fsck -fvy /dev/block/mmcblk0p35

e2fsck 1.41.14 (22-Dec-2010)

e2fsck: No such file or directory while trying to open /dev/block/mmcblk0p35

Possibly non-existent device?

~ # e2fsck -fvy /dev/block/mmcblk0p37

e2fsck 1.41.14 (22-Dec-2010)

e2fsck: No such file or directory while trying to open /dev/block/mmcblk0p37

Possibly non-existent device?

~ # e2fsck -fvy /dev/block/mmcblk0p35

e2fsck 1.41.14 (22-Dec-2010)

e2fsck: No such file or directory while trying to open /dev/block/mmcblk0p35

Possibly non-existent device?

~ # e2fsck -fvy /dev/block/mmcblk0p39

e2fsck 1.41.14 (22-Dec-2010)

e2fsck: No such file or directory while trying to open /dev/block/mmcblk0p39

Possibly non-existent device?

(and the same result for mmcblk0p36)

but for cat /proc/emms I get

~ # cat /proc/emmc

dev: size erasesize name

mmcblk0p19: 000ffa00 00000200 "misc"

mmcblk0p34: 00fffe00 00000200 "recovery"

mmcblk0p33: 01000000 00000200 "boot"

mmcblk0p35: 73fffc00 00000200 "system"

mmcblk0p26: 00140200 00000200 "local"

mmcblk0p36: 27fffe00 00000200 "cache"

mmcblk0p37: 680000000 00000200 "userdata"

mmcblk0p22: 01400000 00000200 "devlog"

mmcblk0p24: 00040000 00000200 "pdata"

mmcblk0p27: 00010000 00000200 "extra"

mmcblk0p31: 04b00200 00000200 "radio"

mmcblk0p16: 03c00400 00000200 "adsp"

mmcblk0p15: 00100000 00000200 "dsps"

mmcblk0p17: 007ffa00 00000200 "radio_config"

mmcblk0p20: 00400000 00000200 "modem_st1"

mmcblk0p21: 00400000 00000200 "modem_st2"

mmcblk0p28: 00100000 00000200 "cdma_record"

mmcblk0p18: 02000000 00000200 "reserve_1"

mmcblk0p30: 034ffa00 00000200 "reserve_2"

mmcblk0p32: 05fffc00 00000200 "reserve_3"

mmcblk0p29: 06069e00 00000200 "reserve"

Thanks for your patience and sorry for the false hope with the typo