yashsingh1/xdaforums huggingface dataset:
[BLU R1 HD Guides, News, & Discussion] Fullmetal99012:
It would be nice to bring a plethora of options to this device, however I feel like getting CM running would be a good start. maybe CM/AOSP.

Hopefully I'll get some free time in between work to look at setting up the device tree/getting the kernel to compile.
[BLU R1 HD Guides, News, & Discussion] N00b-un-2:
Just wanted to say... I just bought the $49.99 version of this phone specifically to try and port TWRP and AOSP to it. should be arriving tomorrow. I'm downloading the source code and will set up an android build VM tonight.

In case anyone is wondering, I do have a bit of experience porting recoveries and ROMs to devices and am looking forward to developing for this device.
[BLU R1 HD Guides, News, & Discussion] onlykhaz:
I'm very happy we got a new dev here :good:

Dude why don't you put another 10$ for the 2gb ram version :confused: if you can return it for the other one it would be better for all of us and for you.
[BLU R1 HD Guides, News, & Discussion] Oscar_david:
I have the same question, especially because most of us have the $60 version, and of course I wonder whether ROM development would be different for each version.
[BLU R1 HD Guides, News, & Discussion] _AI_:
You are an amazing human being. We thank you, our children thank you and Android thanks YOU :good::good::good::good:
[BLU R1 HD Guides, News, & Discussion] Fullmetal99012:
Just got my Dev laptop working again. Just need to download Linux and set up a development VM.
[BLU R1 HD Guides, News, & Discussion] N00b-un-2:
To address everyone -- no, there doesn't seem to really be any difference between the the 8GB and 16GB variants. Aside from RAM and storage, the two are otherwise identical. I spent last night unlocking the bootloader, flashing TWRP (I was totally prepared to start working on porting, but someone saved me the trouble), rooting and removing all of the Amazon nonsense.

It took HOURS to pull down the AOSP source because Nougat source code was just released and everyone has been just hammering the google servers. That being said, I have my dev box built and my environment is in place. I'm looking at the Mediatek source code right now and trying to figure out where everything goes and what everything is called. I'm hoping to be able to successfully compile the kernel source in the next week or so.

please be patient with me. bear in mind that a kernel that compiles is not necessarily one that boots. And it certainly doesn't mean Im going to have a working port of CM13 (or 14) any time soon. Also, I have a real job outside of android dev work and thats what pays the bills.

Are there any other devs working on this right now? Has anyone else figured out if mediatek does anything non-standard with their toolchain?
[BLU R1 HD Guides, News, & Discussion] AtomicFizzle:
I'm not really a developer, but I like messing with stuff. Got it to compile I think!

unzip -o ../Downloads/kernel-source.zip
gedit kernel-3.18/drivers/mmc/core/mmc.c
took out @xuchunsheng code blocks
mkdir tools/tools

export PATH=/home/adam/android-ndk-r12b/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64/bin:$PATH&&export CROSS_COMPILE=arm-linux-androideabi-&&export ARCH=arm

drvs=~/build/kernel-3.18/drivers
miscmtk=$drvs/misc/mediatek
export CPATH=$miscmtk/base/power/mt6735/:$miscmtk/btcvsd/:$miscmtk/cmdq/v2/mt6735/:$miscmtk/ext_disp/mt6735/:$miscmtk/fingerprint/gfx1xm/:$miscmtk/gpio/mt6735/:$miscmtk/i2c/mt6735/:$miscmtk/m4u/mt6735/mt6753/:$miscmtk/power/mt6735/:$miscmtk/uart/mt6735/:$miscmtk/video/mt6735/dispsys:$miscmtk/video/mt6735/videox/:$drvs/mmc/host/mediatek/mt6735/:$drvs/pinctrl/mediatek/:$drvs/spi/mediatek/mt6735/:$drvs/watchdog/mediatek/wdt/mt6735/

make p6601_defconfig
make -j4 zImage

CPATH thing seems a little weird, but I guess it gets through those troublesome includes. Maybe there's something supposed to be in the build.ini that they didn't give us.

OBJCOPY arch/arm/boot/Image
Kernel: arch/arm/boot/Image is ready
LDS arch/arm/boot/compressed/vmlinux.lds
AS arch/arm/boot/compressed/head.o
GZIP arch/arm/boot/compressed/piggy.gzip
CC arch/arm/boot/compressed/misc.o
CC arch/arm/boot/compressed/decompress.o
CC arch/arm/boot/compressed/string.o
SHIPPED arch/arm/boot/compressed/hyp-stub.S
SHIPPED arch/arm/boot/compressed/lib1funcs.S
SHIPPED arch/arm/boot/compressed/ashldi3.S
SHIPPED arch/arm/boot/compressed/bswapsdi2.S
AS arch/arm/boot/compressed/hyp-stub.o
AS arch/arm/boot/compressed/lib1funcs.o
AS arch/arm/boot/compressed/ashldi3.o
AS arch/arm/boot/compressed/bswapsdi2.o
AS arch/arm/boot/compressed/piggy.gzip.o
LD arch/arm/boot/compressed/vmlinux
OBJCOPY arch/arm/boot/zImage
Kernel: arch/arm/boot/zImage is ready
[BLU R1 HD Guides, News, & Discussion] Nonta72:
I got a question, Are the ROMs in all versions (OEM and Amazon) actually 32-bit or 64-bit ?

Thanks!
[BLU R1 HD Guides, News, & Discussion] N00b-un-2:
ARCH=arm

they are 32 bit.
[BLU R1 HD Guides, News, & Discussion] Nonta72:
This is bad for performance (somehow).

But increases apps compatibility.
[BLU R1 HD Guides, News, & Discussion] N00b-un-2:
not necessarily. 32 is actually far more efficient, especially for devices with less RAM, eg; the 1GB version.
[BLU R1 HD Guides, News, & Discussion] N00b-un-2:
[IMG="compiling..."]http://dl-1.va.us.xda-developers.com/3/8/5/6/8/5/5/Screen_Shot_2016-08-27_at_9.16.40_PM.png?key=yAi-SMLyXEngaxXWIk4Vfg&ts=1472357947[/IMG]

compiling now...
[BLU R1 HD Guides, News, & Discussion] Nonta72:
True, but I'd preferred a 64-bit OS.

I renounced to mine because of that.

Had enough 32-bit OSes :D

Keep up the development ...

Good luck!
[BLU R1 HD Guides, News, & Discussion] N00b-un-2:
So... I've gotten about as far as you have, but after I run make zImage, it fails on

No rule to make target 'net/netfilter/xt_HL.o

What is your dev box like? what OS, where did you download the toolchain from, etc.

---------- Post added at 04:29 PM ---------- Previous post was at 04:16 PM ----------

FYI...

http://www.arm.com/products/processors/cortex-a/cortex-a53-processor.php

the CPU does support 64 bit architecture. Looks like, if we can get an arm64 kernel to cross compile, we could build out 64 bit AOSP source against that. Technically 64 bit is totally possible on this device. as for now, I'm more concerned about successfully compiling the kernel itself though.

Once I do that, my first goal is to bake in double tap to wake.
[BLU R1 HD Guides, News, & Discussion] jrk190:
And memory management. Jesus. This phone is great but the moment I try to open an app everything hits the fan.
[BLU R1 HD Guides, News, & Discussion] N00b-un-2:
hmmm... despite the unlocked bootloader, looks like this phone is still FAR from a Nexus. I just tried to fastboot flash zimage zImage my freshly baked kernel and... bootloops. tried to restore using SPFT... still bootlooping. Might be bricked, can't get into recovery anymore.
[BLU R1 HD Guides, News, & Discussion] kal250:
Well that sux.... I really want some sign of hope :crying:
[BLU R1 HD Guides, News, & Discussion] N00b-un-2:
not to worry. All that means is that the zImage needs to be packed in the boot.img and can't be flashed with fastboot. The safer thing to do definitely would have been to unpack the boot.img from the stock rom and replace the zImage on it and then fastboot boot boot.img. No risk of bricking there... That being said, my phone is in fact hard bricked now and needs to be replaced. Oh well. Can't make an omelette without breaking a few eggs.
[BLU R1 HD Guides, News, & Discussion] kal250:
You still within your return period with Amazon?? Easier than a warranty claim :rolleyes: I wonder how that works with Prime pricing???
[BLU R1 HD Guides, News, & Discussion] N00b-un-2:
yeah, just got the phone a couple days ago. wasted no time trying to break it ;)
[BLU R1 HD Guides, News, & Discussion] kal250:
Yeah, we appreciate the effort!! I wish I had more time on my hands to learn the ins and outs of this stuff. I can spin my way around Windows and PC hardware, but I am a Linux and Android Idiot :eek:
[BLU R1 HD Guides, News, & Discussion] AtomicFizzle:
Well shoot. That was what I was gonna try (just replace the kernel in the stock boot.img), but hadn't had the time yet. Did you try flashing your backed up boot image from the SP flash tool? I thought that tool worked before everything else, you know... when it's off even. I screwed up something a couple of weeks ago and it wouldn't boot at all, and was able to get it back working again.

Btw my build env is pretty basic. Ubuntu 16.04 with the ARM toolchain from the most recent NDK. Guess you figured out whatever was messing up your build.
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
Hey guys. Made a post about this on the general thread but figured I'd post here as well since this seems to be where the development talk is. Plus it'll help un-clutter the already over-cluttered general thread.

I'm trying to build CM13 from source, using anpage's GitHub repos for both device tree and kernel source. When I do a "lunch [device]" it tells me there are missing dependencies and that it will bail out, however it does not say what the missing dependencies are nor does it bail out. I'm not sure if this is a real issue but this could be a hint.

So far ive run into 2 errors compiling for the R1. The first one being solved by adding a line to the device_p6601.mk file. The second one is the same issue as the first one, only with a different file. I have not been able to figure out how to solve the 2nd error but the first one involved specifying in the device.mk that the screen resolution was mdpi. Here's the unsolvable error I'm getting now:

make: *** No rule to make target '/home/administrator/WORKING_DIRECTORY/out/target/product/p6601/obj/STATIC_LIBRARIES/libminui_intermediates/export_includes', needed by '/home/administrator/WORKING_DIRECTORY/out/target/product/p6601/obj/EXECUTABLES/healthd_intermediates/import_includes'. Stop.

I guess what I'm trying to say is, are we sure the device tree on GitHub is 100% complete? If so, is it 100% compatible with CM sources? I'm not sure how to check because I don't know how to make one.

I'm going to try using this tree and kernel source with compiling pure AOSP Nougat tomorrow and see if I get the same errors. Not sure if the device tree is AOSP compatible but we'll see.
[BLU R1 HD Guides, News, & Discussion] vampirefo:
zip doesn't extract cleanly some problem with arch directory, unzip works.
[BLU R1 HD Guides, News, & Discussion] AtomicFizzle:
Tried fastbooting my compiled kernel, but it didn't work. Just goes black and then reboots normally. Btw, the kernel offset is 0x40000000.

fastboot boot -b 0x40000000 ./zImage-new
creating boot image...
creating boot image - 8366080 bytes
downloading 'boot.img'...
OKAY [ 0.794s]
booting...
OKAY [ 0.052s]
finished. total time: 0.846s
[BLU R1 HD Guides, News, & Discussion] vampirefo:
Did you figure out the problem of the script that appends the DTB to end of kernel?
[BLU R1 HD Guides, News, & Discussion] ariesgodofwar:
http://xdaforums.com/jiayu-s3/development/rom-unofficial-aosp-n-jiayu-s3-plus-t3448724

[MENTION=5238428]superdragonpt[/MENTION] looks to have gotten Nougat up and running on the Jiayu S3 Plus
[BLU R1 HD Guides, News, & Discussion] kal250:
This is awesome, hopefully the devs over there can give us some pointers. I know from that thread though they are getting frustrated with all the give us a rom requests. But I think the guys working on our side are not asking for handouts just some pointers :good: hopefully this can help us tremendously!!
[BLU R1 HD Guides, News, & Discussion] ss2man44:
The trees I have on GitHub are far from complete and there might even be some problems compiling right now. I got it to build but I can't remember if I pushed those changes. What I've been doing is "make bootimage" to compile the kernel only for now. The device tree does, in fact, build TWRP if you set it up right. I'm using my own from-source recovery right now.

I don't know for sure yet, but CM solves this with the Nexus 5 by adding

BOARD_KERNEL_IMAGE_NAME := zImage-dtb

to the BoardConfig.mk

I think there's also something like

BOARD_KERNEL_APPEND_DTB := true

You could try each and see if one works.
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
I did make one slight change that fixed a linking error when building fonts, check the GitHub page (I assume you're user anpage). Sync your work up, and as I find more answers around the internet I'll add them. From what I gather, the problems I'm having so far can be fixed by adding things to various mk files. I just don't know what to add and where.
[BLU R1 HD Guides, News, & Discussion] vampirefo:
I haven't had a chance to work on it yet, I just downloaded source last night, my guess it would be.

MTK_APPENDED_DTB_SUPPORT:= yes

BOARD_KERNEL_IMAGE_NAME := zImage-dtb

*
[BLU R1 HD Guides, News, & Discussion] vampirefo:
Ok just got a chance to compile kernel, I compiled the source from mega link first.

LD arch/arm/boot/compressed/vmlinux
OBJCOPY arch/arm/boot/zImage
Kernel: arch/arm/boot/zImage is ready
CAT arch/arm/boot/zImage-dtb
Kernel: arch/arm/boot/zImage-dtb is ready
vampirefo@vampirefo-OptiPlex-760:~/Downloads/kk$

compiling the source from your github now.

LD arch/arm/boot/compressed/vmlinux
OBJCOPY arch/arm/boot/zImage
Kernel: arch/arm/boot/zImage is ready
CAT arch/arm/boot/zImage-dtb
Kernel: arch/arm/boot/zImage-dtb is ready
vampirefo@vampirefo-OptiPlex-760:~/Downloads/kk$
[BLU R1 HD Guides, News, & Discussion] N00b-un-2:
Glad to see I'm not the only one working on this. I bricked my phone flashing a bad kernel (yes, I tired SPFT to restore, it didn't work). New phone arriving tomorrow and then I'll be back at it.

On a somewhat unrelated note, I thought it would be fun to use ChromeOS as my dev box.
[BLU R1 HD Guides, News, & Discussion] vampirefo:
You would be better off, unpacking your current boot.img replace the kernel with the one you built, and boot into compiled kernel that way, assuming you have unlocked bootloader.
[BLU R1 HD Guides, News, & Discussion] N00b-un-2:
yes, you're right. In fact, I said pretty much exactly that to another member

Great minds think alike... I just figured (wrongly) that having TWRP installed, a nandroid backup, an unlocked bootloader and a copy of the stock firmware to flash with SPFT I was not at risk of bricking this phone. I had a nexus 4 a few years back and that phone was literally impossible to brick because of the unlocked bootloader. But directly flashing the zImage using

fastboot flash zimage zImage

resulted in a boot loop. tried fastboot flashing the stock boot.img, resulted in a soft brick. tried using SPFT at that point to return to stock and then the phone decided it wasn't going to turn on anymore. At which point I started an RMA with Amazon (I'd had the phone for less than two days)
[BLU R1 HD Guides, News, & Discussion] N00b-un-2:
anybody else getting this? I just synced from git and now I'm getting GPIOLIB unmet dependencies

make p6601_defconfig
warning: (ARCH_REQUIRE_GPIOLIB && PINCTRL_AT91 && PINCTRL_MTK_COMMON && PINCTRL_NOMADIK && MFD_TC6393XB && FB_VIA) selects GPIOLIB which has unmet direct dependencies (ARCH_WANT_OPTIONAL_GPIOLIB || ARCH_REQUIRE_GPIOLIB)
warning: (ARCH_REQUIRE_GPIOLIB && PINCTRL_AT91 && PINCTRL_MTK_COMMON && PINCTRL_NOMADIK && MFD_TC6393XB && FB_VIA) selects GPIOLIB which has unmet direct dependencies (ARCH_WANT_OPTIONAL_GPIOLIB || ARCH_REQUIRE_GPIOLIB)
#
# configuration written to .config
#
[BLU R1 HD Guides, News, & Discussion] AtomicFizzle:
I always got that. Couldn't figure out what exactly it was looking for, but it did build either way.

I tried the other night just fastboot boot with the kernel from a backup of my running system and that ended up rebooting too. I tried with and without the ramdisk. Maybe fastboot boot just won't work for this phone for some reason? Guess I could try flashing the boot.img I did with just the kernel replaced. Just worried because of your brick situation... ?
[BLU R1 HD Guides, News, & Discussion] KazuDante:
can someone link me to the kernel source you guys are currently working with?
[BLU R1 HD Guides, News, & Discussion] vampirefo:
First post.

---------- Post added at 02:49 PM ---------- Previous post was at 02:34 PM ----------

Have you tried fastboot boot boot.img on stock boot.img? If it boots then fast boot works, just something wrong with your custom kernel.

At least by trying stock boot.img you will know if fastboot boot works or not.

From what I have read about this phone fastboot boot does work.
[BLU R1 HD Guides, News, & Discussion] N00b-un-2:
yeah, sucks. But at the end of the day you'd only be out $50. I think that you could test whether fastboot boot boot.img works by doing it with the stock boot.img. if the phone boots, then its probably safe to say that just because the kernel compiled doesn't mean its bootable.
[BLU R1 HD Guides, News, & Discussion] AtomicFizzle:
Yeah, backed up boot.img causes a reboot for me too. Says it sends okay, but it goes black reboots after a few seconds. Just the same as fastboot boot of the extracted kernel from that boot.img. :confused:
[BLU R1 HD Guides, News, & Discussion] vampirefo:
I don't understand your problem, not being able to fastboot boot stock boot.img

Is your bootloader unlocked?

I just got phone today, rooted phone, unlocked bootloader, fastboot boot works just fine, I just booted my compiled kernel, in both boot.img and recovery.img

fastboot boot recovery.img

fastboot boot boot.img

vampirefo@vampirefo-OptiPlex-760:~/Desktop$ adb shell
shell@R1_HD:/ $ cat /proc/version
Linux version 3.18.19 (vampirefo@vampirefo-OptiPlex-760) (gcc version 4.8 (GCC) ) #2 SMP PREEMPT Tue Aug 30 22:27:26 EDT 2016
shell@R1_HD:/ $
[BLU R1 HD Guides, News, & Discussion] AtomicFizzle:
Hmmm. I guess fastboot boot using the stock unaltered boot.img maybe could have worked? Just not sure how I'd know. My boot up experience was the same as my failed attempts... the red light to goes off and the screen goes black before booting up normally. My compiled kernel's still not working for me, but i'm probably doing something wrong. Here's how I tried to replace the kernel, using the boot.img from the stock prime backup.

adam@adam-OptiPlex-780:~/build/bootimg$ abootimg -x primestockboot.img
writing boot image config in bootimg.cfg
extracting kernel in zImage
extracting ramdisk in initrd.img
adam@adam-OptiPlex-780:~/build/bootimg$ abootimg --create myboot.img -f bootimg.cfg -k ../kernel-3.18/arch/arm/boot/zImage -r initrd.img
adam@adam-OptiPlex-780:~/build/bootimg$ adb reboot-bootloader
adam@adam-OptiPlex-780:~/build/bootimg$ fastboot boot myboot.img
downloading 'boot.img'...
OKAY [ 1.581s]
booting...
OKAY [ 0.052s]
finished. total time: 1.633s
adam@adam-OptiPlex-780:~/build/bootimg$
adam@adam-OptiPlex-780:~/build/bootimg$ adb shell
shell@R1_HD:/ $ cat /proc/version
Linux version 3.18.19+ (develop@SW2-Server) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Fri Jun 17 14:58:42 CST 2016
[BLU R1 HD Guides, News, & Discussion] N00b-un-2:
Wait... so you swapped a kernel you built into the stock boot.img and were able to fastboot into the system? What hardware works? what doesnt work? that's literally the last thing that needs to happen before we can start on developing ROMs
[BLU R1 HD Guides, News, & Discussion] vampirefo:
Try mine.

https://www.androidfilehost.com/?fid=24686679545611240

fastboot boot vamp_boot.img

vampirefo@vampirefo-OptiPlex-760:~/Desktop$ adb shell
shell@R1_HD:/ $ cat /proc/version
Linux version 3.18.19 (vampirefo@vampirefo-OptiPlex-760) (gcc version 4.8 (GCC) ) #2 SMP PREEMPT Tue Aug 30 22:27:26 EDT 2016
shell@R1_HD:/ $

---------- Post added at 01:09 AM ---------- Previous post was at 01:08 AM ----------

My guess everything works as this is the source for stock kernel.
[BLU R1 HD Guides, News, & Discussion] N00b-un-2:
Thanks Vamp. can confirm your kernel does boot, which is great. but I want to make sure I can compile a bootable kernel myself. Which kernel source are you using? what are the exact commands you're using to compile? How are you packing your boot.img?

I am using the kernel source from the first post https://github.com/anpage/android_kernel_mediatek_mt6735

and I'm using pretty much the same method to build as AtomicFizzle here http://xdaforums.com/showpost.php?p=68371894&postcount=39

kernel compiles without issue. I tried the older method of split_boot and mkbootimg, as well as using abootimg. neither resulting boot.img actually boots.
[BLU R1 HD Guides, News, & Discussion] vampirefo:
I used [MENTION=4239374]ss2man44[/MENTION] kernel source same as you.

I used [MENTION=3963379]AtomicFizzle[/MENTION] exports same as you.

I used [MENTION=5186178]bluefirebird[/MENTION] CarlivImageKitchen to unpack and repack boot.img and recovery.img

I just made a script to automate it all.

SHIPPED arch/arm/boot/compressed/bswapsdi2.S
AS arch/arm/boot/compressed/hyp-stub.o
AS arch/arm/boot/compressed/lib1funcs.o
AS arch/arm/boot/compressed/ashldi3.o
AS arch/arm/boot/compressed/bswapsdi2.o
AS arch/arm/boot/compressed/piggy.gzip.o
LD arch/arm/boot/compressed/vmlinux
OBJCOPY arch/arm/boot/zImage
Kernel: arch/arm/boot/zImage is ready
CAT arch/arm/boot/zImage-dtb
Kernel: arch/arm/boot/zImage-dtb is ready

****************************************************
* *
* Carliv Image Kitchen for Android v0.5 *
* boot+recovery images copyright-2015 carliv@xda *
* including support for MTK powered phones images *
* LINUX version *
* The repacking images script *
* *
****************************************************

Processing the boot folder.

Repacking the image....

The kernel is: ./boot.img-kernel

Getting the ramdisk compression....

Compression used: gz

The ramdisk is: ./boot.img-ramdisk.gz

Getting the image repacking arguments....

Board: BLU_R0010UU_V6.

Base: 0x40000000

Pagesize: 2048

Command line: bootopt=64S3,32N2,32N2

Kernel offset: 0x00008000

Ramdisk offset: 0x04000000

Tags offset: 0x0e000000

boot_164712.img

Executing the repacking command....

Repack image utility by carliv@xda

Check and add the kernel
Check and add the ramdisk
Build the new image

'boot_164712.img' successfully repacked

Done! Your new image is packed as boot_164712.img.

vampirefo@vampirefo-OptiPlex-760:~/Downloads/kk$

Below is script I use to compile kernel and repack boot.img and recovery.img, nothing fancy just gets the job done.

#!/bin/bash
#variables
makeboot=/home/vampirefo/Desktop/R1HD/CarlivImageKitchen/bootimg
zImage=/home/vampirefo/Downloads/kk/android_kernel_mediatek_mt6735-master/arch/arm/boot/zImage-dtb
drvs=/home/vampirefo/Downloads/kk/android_kernel_mediatek_mt6735-master/drivers
miscmtk=$drvs/misc/mediatek
export PATH=/home/vampirefo/Desktop/CM12_E030U/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/bin:$PATH&&export CROSS_COMPILE=arm-eabi- &&export ARCH=arm
export CPATH=$miscmtk/base/power/mt6735/:$miscmtk/btcvsd/:$miscmtk/cmdq/v2/mt6735/:$miscmtk/ext_disp/mt6735/:$miscmtk/fingerprint/gfx1xm/:$miscmtk/gpio/mt6735/:$miscmtk/i2c/mt6735/:$miscmtk/m4u/mt6735/mt6753/:$miscmtk/power/mt6735/:$miscmtk/uart/mt6735/:$miscmtk/video/mt6735/dispsys:$miscmtk/video/mt6735/videox/:$drvs/mmc/host/mediatek/mt6735/:$drvs/pinctrl/mediatek/:$drvs/spi/mediatek/mt6735/:$drvs/watchdog/mediatek/wdt/mt6735/

#compile kernel
cd ./android_kernel_mediatek_mt6735-master
make clean
make p6601_defconfig
make -j10

#build boot.img
cd $makeboot
rm -rf $makeboot/boot/boot.img-kernel
cp $zImage $makeboot/boot/boot.img-kernel
./repack_img ./boot
[BLU R1 HD Guides, News, & Discussion] N00b-un-2:
Outstanding! the CarlivImageKitchen was the thing I was missing. Looks like abootimg is more oriented towards huawei devices, so while it does produce valid android boot.imgs, they aren't correct for MTK devices. I was wondering why your bootsize was smaller than mine. Thanks! I'll take another crack at it when I get a second.
[BLU R1 HD Guides, News, & Discussion] KazuDante:
So does the kernel boots correctly?

Also is it in a zip(twrp) format or a flash method?
[BLU R1 HD Guides, News, & Discussion] N00b-un-2:
Now i'm getting this error