Screwed Up Need Help URGENT

Mr Hofs said:

No you need to PM the guy with the mkfs file and fix that first.

Click to expand...

Click to collapse

Gawsh i'm lost, i've done everything right but when it comes to the mount /data the console says

mount: mounting /dev/block/platform/msm_sdcc.1/by-name/userdata on /data failed:
Invalid argument
On an external website it says;

How Do I Recognise The Problem?

When trying to mount the DATA partition from inside the custom recovery using the mount /data command you will most likely see this output: mount: mounting /dev/block/mmcblk0p37 on /data failed: Invalid argument

To be 100% sure you can check filesystem structure with the following command: /sbin/e2fsck -n -f /dev/block/mmcblk0p37

When I type /sbin/e2fsck -n -f /dev/block/mmcblk0p37 it comes up with;

~ # /sbin/e2fsck -n -f /dev/block/mmcblk0p37
/sbin/e2fsck -n -f /dev/block/mmcblk0p37
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p37: 11/6400 files (9.1% non-contiguous), 1233/6400 blocks

Does this make any sense?

:victory: FINALLY Fixed my phone (took me long enough), but to no avail I downloaded the latest snapshot of cm11 which i think ill change to viperone (soz cm11). Many thanks to those who helped me and a BIG thank you to Mr Hofs for being there in times of agony and pain. I'm soon going to post a thread to how to solve fixing your m8 after wiping the system :silly:. This Thread Is Now Closed! :highfive: