[One (M7) General] free_refil:
Really having a hard time with firewater this go 'round, and can't seem to find my answers via search (I'm VERY sorry if I over-looked them!). I recently sent my M7 in for repair for purple camera and a busted rear case, and it came back wipe clean and fresh. I was able to root and install TWRP 2.6.3.3 recover and then ARHD 81.1 (4.4.3 Sense). I couldn't get firewater to run with this config. I tried installed ElementalX 17 kernel, still a no go. This is what my command prompt looks like when running firewater. I never receive any prompts on the device at all.

"

C:\Android-adb>adb devices

List of devices attached

HT34Y***** device

C:\Android-adb>adb reboot

C:\Android-adb>adb wait-for-device push firewater /data/local/tmp

5856 KB/s (4519496 bytes in 0.753s)

C:\Android-adb>adb shell

root@m7:/ # su

su

root@m7:/ # chmod 755 /data/local/tmp/firewater

chmod 755 /data/local/tmp/firewater

root@m7:/ # /data/local/tmp/firewater

/data/local/tmp/firewater

root@m7:/ #

"

Here is my "fastboot getvar all"

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.57.0000

(bootloader) version-baseband: 4M.27.3218.14

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 5.12.502.2

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) serialno: HT34*

(bootloader) imei: *

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0712000

(bootloader) cidnum: CWS__001

(bootloader) battery-status: good

(bootloader) battery-voltage: 4184mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-1f512bb6

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

finished. total time: 0.051s

What is my issue? I read another member here (@balag59) had sort of the same issue, but on 4.4.2 ARHD 71.1, and was suggested by (@Danny201281) to run some commands e2sfck commands, as he suspected corrupt partitions, and here is the output of those commands for me:

C:\Android-adb>adb shell

~ # ←[6ne2fsck -fvy dev/block/mmcblk0p35

e2fsck -fvy dev/block/mmcblk0p35

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

2471 inodes used (2.15%)

30 non-contiguous files (1.2%)

1 non-contiguous directory (0.0%)

# of inodes with ind/dind/tind blocks: 0/0/0

Extent depth histogram: 2167/1

364955 blocks used (79.55%)

0 bad blocks

0 large files

2087 regular files

80 directories

0 character device files

0 block device files

0 fifos

0 links

295 symbolic links (295 fast symbolic links)

0 sockets

--------

2462 files

~ # ←[6ne2fsck -fvy dev/block/mmcblk0p36

e2fsck -fvy dev/block/mmcblk0p36

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

19 inodes used (0.05%)

0 non-contiguous files (0.0%)

0 non-contiguous directories (0.0%)

# of inodes with ind/dind/tind blocks: 0/0/0

Extent depth histogram: 11

5271 blocks used (3.22%)

0 bad blocks

0 large files

6 regular files

4 directories

0 character device files

0 block device files

0 fifos

0 links

0 symbolic links (0 fast symbolic links)

0 sockets

--------

10 files

~ # ←[6ne2fsck -fvy dev/block/mmcblk0p37

e2fsck -fvy 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

14033 inodes used (0.82%)

816 non-contiguous files (5.8%)

18 non-contiguous directories (0.1%)

# of inodes with ind/dind/tind blocks: 0/0/0

Extent depth histogram: 13580/108

3421503 blocks used (50.20%)

0 bad blocks

1 large file

11865 regular files

1822 directories

0 character device files

0 block device files

0 fifos

0 links

328 symbolic links (328 fast symbolic links)

9 sockets

--------

14024 files

~ # ←[6nexit

exit

"

Any idea what I'm doing wrong? Do I need to go to a 4.4.2 Sense ROM? Or is it because I'm on HBOOT 1.57, and Firewater isn't compatible with it, and I should go and use Sunshine? If so, I'll drop the $25 no problem! Just want to ensure I've used all my free routes before dropping the dough.

Also, should I even worry about S-OFF? I think I'm on the latest firmware for my carrier right now, so I'm not sure this is even necessary at this point really, but I hate not having the freedom to do as a like and not having Super-CID.