Help Finding kernel partition...

[hyperspherical]

I have an htc one m7 at&t version, and I am installing a new cyanogenmod .zip

I have to modify updater-script because it uses /dev/block/platform/msm_sdcc.1/by-name, which for some reason is missing on my phone.

I pointed everything to the right partitions but I am stuck on the last line: package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");

I have no idea where my boot partition is. Is there I way I can know for sure what partition it boot is? I want the kernel partition, not block 0.

CWM seems to find it ok, so there must be a way to know.


/proc/self/mountinfo
ID PARENT BLOCK ROOT MOUNTPOINT OPTIONS TYPE SOURCE SUPEROPTS
1 1 0:1 / / ro,relatime shared:1 - rootfs rootfs ro,seclabel
11 1 0:11 / /dev rw,nosuid,relatime shared:2 - tmpfs tmpfs rw,seclabel,mode=755
12 11 0:9 / /dev/pts rw,relatime shared:3 - devpts devpts rw,seclabel,mode=600
13 1 0:3 / /proc rw,relatime shared:5 - proc proc rw
14 1 0:12 / /sys rw,relatime shared:6 - sysfs sysfs rw,seclabel
15 14 0:10 / /sys/fs/selinux rw,relatime shared:7 - selinuxfs selinuxfs rw
16 1 0:13 / /acct rw,relatime shared:8 - cgroup none rw,cpuacct
17 1 0:14 / /mnt/secure rw,relatime - tmpfs tmpfs rw,seclabel,mode=700
18 1 0:15 / /mnt/asec rw,relatime shared:10 - tmpfs tmpfs rw,seclabel,mode=755,gid=1000
19 1 0:16 / /mnt/obb rw,relatime shared:11 - tmpfs tmpfs rw,seclabel,mode=755,gid=1000
20 1 0:17 / /mnt/fuse rw,relatime shared:12 - tmpfs tmpfs rw,seclabel,mode=775,gid=1000
21 11 0:18 / /dev/cpuctl rw,relatime shared:4 - cgroup none rw,cpu
22 1 179:35 / /system ro,noatime shared:13 - ext4 /dev/block/mmcblk0p35 ro,seclabel,nobarrier,data=ordered
23 1 179:36 / /cache rw,nosuid,nodev,noatime shared:14 ext4 /dev/block/mmcblk0p36 rw,seclabel,nobarrier,data=ordered
24 1 179:37 / /data rw,nosuid,nodev,noatime shared:15 - ext4 /dev/block/mmcblk0p37 rw,seclabel,nobarrier,noauto_da_alloc,data=ordered

25 1 179:31 / /firmware/mdm ro,relatime shared:16 - vfat /dev/block/mmcblk0p31 ro,context=ubject_r:radio_efs_file:s0,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro

26 1 179:16 / /firmware/q6 ro,relatime shared:17 - vfat /dev/block/mmcblk0p16 ro,context=ubject_r:radio_efs_file:s0,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro27 10:19 / /mnt/qcks rw,relatime shared:18 - tmpfs tmpfs rw,seclabel,size=20480k,mode=750,gid=1000

28 1 0:20 / /mnt/efs rw,relatime shared:19 - tmpfs tmpfs rw,seclabel,size=20480k,mode=750,gid=1000
29 1 0:21 / /mnt/secdata rw,relatime shared:20 - tmpfs tmpfs rw,seclabel,mode=755,gid=1000
30 14 0:5 / /sys/kernel/debug rw,relatime shared:9 - debugfs /sys/kernel/debug rw
31 1 0:22 / /mnt/shell/emulated rw,nosuid,nodev,relatime shared:21 - fuse /dev/fuse rw,user_id=1023,group_id=1023,default_permissions,allow_other


/proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 130671 mmcblk0p3
179 4 1 mmcblk0p4
179 5 16 mmcblk0p5
179 6 256 mmcblk0p6
179 7 15577 mmcblk0p7
179 8 256 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 256 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 2080 mmcblk0p12
179 13 5120 mmcblk0p13
179 14 1024 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 61441 mmcblk0p16
179 17 8190 mmcblk0p17
179 18 32768 mmcblk0p18
179 19 1022 mmcblk0p19
179 20 4096 mmcblk0p20
179 21 4096 mmcblk0p21
179 22 20480 mmcblk0p22
179 23 4 mmcblk0p23
179 24 256 mmcblk0p24
179 25 16 mmcblk0p25
179 26 1280 mmcblk0p26
179 27 64 mmcblk0p27
179 28 1024 mmcblk0p28
179 29 98727 mmcblk0p29
179 30 54270 mmcblk0p30
179 31 76800 mmcblk0p31
179 32 98303 mmcblk0p32
179 33 16384 mmcblk0p33
179 34 16383 mmcblk0p34
179 35 1900543 mmcblk0p35
179 36 655359 mmcblk0p36
179 37 27262976 mmcblk0p37
179 38 25600 mmcblk0p38

 

[scary alien]

Review the various log files in your /cache/recovery folder--either the stock or custom recoveries should be reporting it in a file (last_log, etc.).

Welcome to our AndroidForums, by the way .