So what's the difference between the 2?

@advocatux The Matrix room doesn't exist

I just finished school, so now I have time to tackle this again.

I'm now getting this error after I ran mka mkbootimg

frameworks/av/camera/cameraserver/Android.mk:18: Target has integrated cameraserver into mediaserver. This is weakening security measures introduced in 7.0
halium/hybris-boot/Android.mk:69: ********************* /boot appears to live on /dev/block/platform/msm_sdcc.1/by-name/boot /dev/mmcblk0p20
halium/hybris-boot/Android.mk:70: ********************* /data appears to live on /dev/block/platform/msm_sdcc.1/by-name/userdata /dev/mmcblk0p29
halium/hybris-boot/Android.mk:73: *** There should be a one and only one device entry for HYBRIS_BOOT_PART and HYBRIS_DATA_PART.  Stop.

@suoko nope sorry

So I got it to build, but now I'm wondering about changing userdata or data to ext4. In fstab.qcom, there are 2 /data mountpoints, one with f2fs and the other with ext4. Do I just delete the f2fs entry?

/dev/block/platform/msm_sdcc.1/by-name/userdata  /data          f2fs    nosuid,nodev,noatime,rw,inline_xattr                                                          wait,check,formattable,encryptable=footer
/dev/block/platform/msm_sdcc.1/by-name/userdata  /data          ext4    nosuid,nodev,noatime,noauto_da_alloc,journal_async_commit,errors=panic                        wait,check,formattable,encryptable=footer

So I'm running into issues building Halium for jfltexx.

When I ran mka mkbootimg, here's what I got:

halium/hybris-boot/Android.mk:69: ********************* /boot appears to live on /dev/block/platform/msm_sdcc.1/by-name/boot
halium/hybris-boot/Android.mk:70: ********************* /data appears to live on /dev/block/platform/msm_sdcc.1/by-name/userdata

Here are the list of commands I ran (pretty much followed the steps), and their output. Hope you can help me.