[Nexus 7 Q&A, Help & Troubleshooting] samw52000:
Man I truly appreciate the help!!!

Ok so this is what I've done:

>adb shell umount /cache

>adb shell umount /system

umount: can't umount /system: Invalid argument

>adb shell umount /data

>adb shell e2fsck -f -n /dev/block/mmcblk0p3

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/mmcblk0p3: 1309/41664 files (2.1% non-contiguous), 158713/166400 blocks

>adb shell e2fsck -f -n /dev/block/mmcblk0p4

e2fsck 1.41.14 (22-Dec-2010)

Warning: skipping journal recovery because doing a read-only filesystem check.

Pass 1: Checking inodes, blocks, and sizes

Deleted inode 16 has zero dtime. Fix? no

Pass 2: Checking directory structure

Pass 3: Checking directory connectivity

Pass 4: Checking reference counts

Pass 5: Checking group summary information

Inode bitmap differences: -16

Fix? no

Free inodes count wrong (28336, counted=28335).

Fix? no

/dev/block/mmcblk0p4: ********** WARNING: Filesystem still has errors **********

/dev/block/mmcblk0p4: 16/28352 files (0.0% non-contiguous), 3666/113408 blocks

>adb shell e2fsck -f -n /dev/block/mmcblk0p9

e2fsck 1.41.14 (22-Dec-2010)

e2fsck: Device or resource busy while trying to open /dev/block/mmcblk0p9

Filesystem mounted or opened exclusively by another program?

>fastboot erase cache

******** Did you mean to fastboot format this partition?

erasing 'cache'...

OKAY [ 0.016s]

finished. total time: 0.016s

>fastboot erase system

******** Did you mean to fastboot format this partition?

erasing 'system'...

OKAY [ 0.016s]

finished. total time: 0.016s

>fastboot erase userdata

******** Did you mean to fastboot format this partition?

erasing 'userdata'...

OKAY [ 0.031s]

finished. total time: 0.031s

>fastboot format cache

erasing 'cache'...

OKAY [ 0.031s]

formatting 'cache' partition...

Creating filesystem with parameters:

Size: 464519168

Block size: 4096

Blocks per group: 32768

Inodes per group: 7088

Inode size: 256

Journal blocks: 1772

Label:

Blocks: 113408

Block groups: 4

Reserved block group size: 31

Created filesystem with 11/28352 inodes and 3654/113408 blocks

sending 'cache' (9052 KB)...

writing 'cache'...

OKAY [ 1.625s]

finished. total time: 1.657s

>fastboot format system

erasing 'system'...

OKAY [ 0.031s]

formatting 'system' partition...

Creating filesystem with parameters:

Size: 681574400

Block size: 4096

Blocks per group: 32768

Inodes per group: 6944

Inode size: 256

Journal blocks: 2600

Label:

Blocks: 166400

Block groups: 6

Reserved block group size: 47

Created filesystem with 11/41664 inodes and 5415/166400 blocks

sending 'system' (12416 KB)...

writing 'system'...

OKAY [ 2.173s]

finished. total time: 2.204s

>fastboot format userdata

erasing 'userdata'...

OKAY [ 0.031s]

formatting 'userdata' partition...

Creating filesystem with parameters:

Size: 14442037248

Block size: 4096

Blocks per group: 32768

Inodes per group: 8176

Inode size: 256

Journal blocks: 32768

Label:

Blocks: 3525888

Block groups: 108

Reserved block group size: 863

Created filesystem with 11/883008 inodes and 96825/3525888 blocks

sending 'userdata' (137526 KB)...

writing 'userdata'...

OKAY [ 26.130s]

finished. total time: 26.161s

Then I ran this again:

>adb shell umount /cache

>adb shell umount /system

umount: can't umount /system: Invalid argument

>adb shell umount /data

>adb shell e2fsck -f -n /dev/block/mmcblk0p3

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/mmcblk0p3: 1309/41664 files (2.1% non-contiguous), 158713/166400 bloc

ks

>adb shell e2fsck -f -n /dev/block/mmcblk0p4

e2fsck 1.41.14 (22-Dec-2010)

Warning: skipping journal recovery because doing a read-only filesystem check.

Pass 1: Checking inodes, blocks, and sizes

Deleted inode 16 has zero dtime. Fix? no

Pass 2: Checking directory structure

Pass 3: Checking directory connectivity

Pass 4: Checking reference counts

Pass 5: Checking group summary information

Inode bitmap differences: -16

Fix? no

Free inodes count wrong (28336, counted=28335).

Fix? no

/dev/block/mmcblk0p4: ********** WARNING: Filesystem still has errors **********

/dev/block/mmcblk0p4: 16/28352 files (0.0% non-contiguous), 3666/113408 blocks

>adb shell e2fsck -f -n /dev/block/mmcblk0p9

e2fsck 1.41.14 (22-Dec-2010)

e2fsck: Device or resource busy while trying to open /dev/block/mmcblk0p9

Filesystem mounted or opened exclusively by another program?

>fastboot flash system "c:\users\...\data\Factory_Images\nakasi-kot49h-factory-5e9db5e1\image-nakasi-kot49h\system.img"

erasing 'system'...

OKAY [ 0.016s]

sending 'system' (625382 KB)...

OKAY [ 75.438s]

writing 'system'...

OKAY [ 27.602s]

finished. total time: 103.055s

>fastboot boot "c:\users\...\data\Factory_Images\nakasi-kot49h-factory-5e9db5e1\image-nakasi-kot49h\boot.img"

downloading 'boot.img'...

OKAY [ 0.609s]

booting...

OKAY [ 0.031s]

finished. total time: 0.641s

Device automatically restarted here - same thing happened, my wallpaper was still up as if nothing had happened.

C:\Users\Sam Wagner\Desktop\Nexus 7 Toolkit\data>adb shell umount /system

umount: can't umount /system: Invalid argument

>adb shell e2fsck -f -n /dev/block/mmcblk0p3

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/mmcblk0p3: 1309/41664 files (2.1% non-contiguous), 158713/166400 blocks

Now the tablet will still boot to the lock screen and shows the wallpaper that's been set before... Sticks there for a few seconds then restarts.

I'm just not understanding why it would tell me that it's deleted stuff but isn't doing any of it.

Also like I mentioned before the stock recovery shows "no command" every time I tried to load into it - I've managed to get past this to the second where you can select the full factory wipe but as everything else it didn't wipe anything.