[One (M7) Q&A, Help & Troubleshooting] doomhendi:
Okay, that worked fine so far. Output:

I:\HTC One Toolkit - Squabbi - 3.1.2>adb shell

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

~ # mount

mount

rootfs on / type rootfs (rw,seclabel)

tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)

devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)

proc on /proc type proc (rw,relatime)

sysfs on /sys type sysfs (rw,seclabel,relatime)

selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)

tmpfs on /storage type tmpfs (rw,seclabel,relatime,mode=050,gid=1028)

tmpfs on /mnt/secure type tmpfs (rw,seclabel,relatime,mode=700)

tmpfs on /mnt/fuse type tmpfs (rw,seclabel,relatime,mode=775,gid=1000)

~ # chmod 777 /tmp/mkfs.ext4

chmod 777 /tmp/mkfs.ext4

~ # /tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext

ra_isize -m 0 /dev/block/mmcblk0p35

/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext

ra_isize -m 0 /dev/block/mmcblk0p35

mke2fs 1.41.12 (17-May-2010)

Filesystem label=

OS type: Linux

Block size=4096 (log=2)

Fragment size=4096 (log=2)

Stride=0 blocks, Stripe width=0 blocks

118800 inodes, 475135 blocks

0 blocks (0.00%) reserved for the super user

First data block=0

15 block groups

32768 blocks per group, 32768 fragments per group

7920 inodes per group

Superblock backups stored on blocks:

32768, 98304, 163840, 229376, 294912

Writing inode tables: done

Creating journal (8192 blocks): done

Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 20 mounts or

180 days, whichever comes first. Use tune2fs -c or -i to override.

~ # /tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext

ra_isize -m 0 /dev/block/mmcblk0p36

/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext

ra_isize -m 0 /dev/block/mmcblk0p36

mke2fs 1.41.12 (17-May-2010)

Filesystem label=

OS type: Linux

Block size=4096 (log=2)

Fragment size=4096 (log=2)

Stride=0 blocks, Stripe width=0 blocks

40960 inodes, 163839 blocks

0 blocks (0.00%) reserved for the super user

First data block=0

5 block groups

32768 blocks per group, 32768 fragments per group

8192 inodes per group

Superblock backups stored on blocks:

32768, 98304

Writing inode tables: done

Creating journal (4096 blocks): done

Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 20 mounts or

180 days, whichever comes first. Use tune2fs -c or -i to override.

~ # /tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext

ra_isize -m 0 /dev/block/mmcblk0p37

/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext

ra_isize -m 0 /dev/block/mmcblk0p37

mke2fs 1.41.12 (17-May-2010)

Filesystem label=

OS type: Linux

Block size=4096 (log=2)

Fragment size=4096 (log=2)

Stride=0 blocks, Stripe width=0 blocks

1703936 inodes, 6815744 blocks

0 blocks (0.00%) reserved for the super user

First data block=0

208 block groups

32768 blocks per group, 32768 fragments per group

8192 inodes per group

Superblock backups stored on blocks:

32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,

4096000

Writing inode tables: done

Creating journal (32768 blocks): done

Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 27 mounts or

180 days, whichever comes first. Use tune2fs -c or -i to override.

~ # mount /data

mount /data

~ # mkdir -p /data/media/0

mkdir -p /data/media/0

~ # exit

I'll now download ARHD 31.6. When I've got it, how should I install it ? Since CMW in it's current state crashes as soon as I try to select 'install zip' should I try to sideload the ROM ? Or should I restart and see if the 'install zip' function works again ? Oo

.. And if CMW works fine again, shouldn't I be able to install TWRP and install the right *selfpunch* ROM directly ? Or would you say it's safer to let the ARHD install fix structures before giving TWRP another shot ?