[Miscellaneous Android Development] yuweng:
Never knew this thread got featured at the portal thanks to Samantha for doing the coverage . . . :o

No worries, i was a newbie once, still am but don't be an annoying one AKA . . . :laugh:

Why i strongly recommends BBQLinux is b'cos you don't need to setup BE its built-in while on Ubuntu & other distro you need to, that will lead to many potential failures even with a single missing dependency package, it would not build or build with ERROR 1. It tooks me almost a year to learn to build on Ubuntu no joke, all b'cos i was following the wrong BE setup guides . . . :p

Yes, if you have already got ~/cm11 synced earlier then using the PhilZ script to sync Part-Source will finish in just a few seconds. You can use any of your old cm repo in fact, just rename the folder to ~/cm11 & PhilZ script will do its job, doesn't matter if its jellybean branch, cm-10.1, cm-10.2 all can be use, thanks to my Master Shifu Carliv for his tips . . . :good: And make sure it is ~/cm11/.repo not ~/cm11/system/.repo will not work !

If you still wanna proceed with Ubuntu then . . .

With reference to OP then extract MediaTek.zip to ~/cm11/device then follow below commands . . .

cd ~/cm11
source build/envsetup.sh
lunch cm_MediaTek-eng
make unpackbootimg
build/tools/device/mkvendor.sh [COLOR="blue"]vendor_name[/COLOR] [COLOR="Red"]device_name[/COLOR] ~/boot.img
[COLOR="Blue"]OR[/COLOR]
build/tools/device/mkvendor.sh [COLOR="blue"]vendor_name[/COLOR] [COLOR="red"]device_name[/COLOR] ~/recovery.img

Or you can download unpackbootimg from here to your ~/bin thanks to kykdev . . . :good:

export PATH=~/bin:$PATH
build/tools/device/mkvendor.sh [COLOR="blue"]vendor_name[/COLOR] [COLOR="Red"]device_name[/COLOR] ~/boot.img
[COLOR="Blue"]OR[/COLOR]
build/tools/device/mkvendor.sh [COLOR="blue"]vendor_name[/COLOR] [COLOR="red"]device_name[/COLOR] ~/recovery.img

OR a more tedious method . . . :cowboy:

Add # remark to ~/cm11/bootable/recovery/boardconfig/BoardConfig.mk most bottom end

[COLOR="Red"]#[/COLOR] ifndef TARGET_SCREEN_HEIGHT
[COLOR="Red"]#[/COLOR] $(warning ************************************************************)
[COLOR="Red"]#[/COLOR] $(warning * TARGET_SCREEN_HEIGHT is NOT SET in BoardConfig.mk )
[COLOR="Red"]#[/COLOR] $(warning ************************************************************)
[COLOR="Red"]#[/COLOR] $(error stopping)
[COLOR="Red"]#[/COLOR] endif

[COLOR="Red"]#[/COLOR] ifndef TARGET_SCREEN_WIDTH
[COLOR="Red"]#[/COLOR] $(warning ************************************************************)
[COLOR="Red"]#[/COLOR] $(warning * TARGET_SCREEN_WIDTH is NOT SET in BoardConfig.mk )
[COLOR="Red"]#[/COLOR] $(warning ************************************************************)
[COLOR="Red"]#[/COLOR] $(error stopping)
[COLOR="Red"]#[/COLOR] endif

cd ~/cm11
source build/envsetup.sh
lunch <- Select [COLOR="Blue"]1. aosp_arm-eng [/COLOR]
make unpackbootimg
Copy it from [COLOR="Blue"]~/cm11/out/host/linux-x86/bin/unpackbootimg[/COLOR] to [COLOR="blue"]~/bin[/COLOR]

But then again, compiled PhilZ Touch might be oversize if your Alcatel MTK recovery partition is just 6Mb, on top of that, PhilZ Touch doesn't officially support /custpack partition, you need to mod the source code to do that, at the end of the day, all your effort would be wasted so do you still wanna continue . . . :cowboy: