[solved] cant make bootable lollipop kernel - Sony Xperia Z Ultra

hi,
im having trouble building a kernel that actually boots liquidsmooth (https://github.com/LiquidSmooth)
I tried using https://github.com/CyanogenMod/android_kernel_sony_msm8974/tree/cm-12.0 and https://github.com/Tommy-Geenexus/android_kernel_sony_msm8974.
Kernel compiles fine but when i flash the kernel the device is stuck at sony bootlogo. also i cant enter recovery. if i press volume up when the led is pink it turns yellow.
its no difference if i use cwm or twrp recovery
Also applied ramdisk size fix for twrp with no difference.
If i flash http://forum.xda-developers.com/xperia-z-ultra/development/anykernel2-zombie-t2926584 my rom (liquidsmooth lp self compiled) boots witout problem. but if i compile the same kernel its about 3mb bigger.
Im using google arm-eabi toolchain 4.8
also tried linaro and sabermod with no difference.
Anyone had the same problem?
How do i get logs at this stage?
Any suggestions?
Didnt have any problems with kitkat.
Manifest:
<project path="device/sony/togari" name="CyanogenMod/android_device_sony_togari" remote="gh" revision="cm-12.0"/>
<project path="device/sony/rhine-common" name="CyanogenMod/android_device_sony_rhine-common" remote="gh" revision="cm-12.0"/>
<project path="device/sony/msm8974-common" name="CyanogenMod/android_device_sony_msm8974-common" remote="gh" revision="cm-12.0"/>
<project path="device/sony/common" name="CyanogenMod/android_device_sony_common" remote="gh" revision="cm-12.0"/>
<project path="device/sony/qcom-common" name="CyanogenMod/android_device_sony_qcom-common" remote="gh" revision="cm-12.0"/>
<project path="device/qcom/common" name="CyanogenMod/android_device_qcom_common" remote="gh" revision="cm-12.0" />
<project path="hardware/sony/DASH" name="CyanogenMod/android_hardware_sony_DASH" remote="gh" revision="cm-12.0" />
<project path="vendor/sony" name="TheMuppets/proprietary_vendor_sony" remote="gh" revision="cm-12.0"/>
<project path="vendor/extra" name="VanirAOSP/vendor_qcom_opt" remote="gh" revision="L5" />
<project path="bootable/recovery" name="CyanogenMod/android_bootable_recovery" groups="pdk" />
<project path="kernel/sony/msm8974" name="CyanogenMod/android_kernel_sony_msm8974" remote="github" revision="cm-12.0" />
<!--project path="bootable/recovery" name="omnirom/android_bootable_recovery" remote="gh" revision="android-5.0" />
<project path="kernel/sony/msm8974" name="Tommy-Geenexus/android_kernel_sony_msm8974" remote="gh" revision="master" /-->
edit:
fixed, problem was using sabermod androideabi toolchain instead of googles.
According to Alx31TLse you cant use sabermod toolchain for xperia z line.
It seems its messing up the busybox or cpio executable for the target. I would guess the problem is with cpio because the leds for entering recovery where working which are controlled by busybox.

---

If i change https://github.com/CyanogenMod/android_device_sony_msm8974-common/blob/cm-12.0/boot/custombootimg.mk line 36 to
$(hide) $(MKBOOTIMG) --kernel $(PRODUCT_OUT)/kernel --ramdisk $(PRODUCT_OUT)/ramdisk.img --cmdline "$(BOARD_KERNEL_CMDLINE)" --base $(BOARD_KERNEL_BASE) --pagesize $(BOARD_KERNEL_PAGESIZE) --dt $(INSTALLED_DTIMAGE_TARGET) $(BOARD_MKBOOTIMG_ARGS) -o $(INSTALLED_BOOTIMAGE_TARGET)
kernel finally boots but no recovery of course.
if i look at the combinedroot folder everything looks ok.
i dont get whats going wrong. im guessing it fails at extracting the ramdisk when using the init script from combinedroot. i also tried to compress the kernel with gzip and also tried using a compressed ramdisk but that didnt change a thing.
any ideas?
@OmarEinea @Saatvik Shukla @Alx31TLse
you did compile successfully do you have any suggestions?

---

1st of all at least specify u wanna make it with twrp wich needs change to your rhine-common
u can take omni's or slim rhine-common as its already twrp-ified. or else if u take cm one, u need twrp's fstab, tagets in board config and and indeed twrp flags. to make it easier take omni's u will save time and headaches.
and main question is...why are u taking msm8974 kernel from tommy wich is for stock rom, u really like things complicated bro. if u take mine from team validus repos or Omar's one it will surely works, and on top of that, kexec patched for multi rom...
If u absolutely wanna keep working with Tommy's one, good luck but imo if u wanna make a good custom kernel change ur base and cherry-pick his stuff for gamma control and everything if its the reason why u looking for his kernel source.

---

Alx31TLse said:
1st of all at least specify u wanna make it with twrp wich needs change to your rhine-common
u can take omni's or slim rhine-common as its already twrp-ified. or else if u take cm one, u need twrp's fstab, tagets in board config and and indeed twrp flags. to make it easier take omni's u will save time and headaches.
and main question is...why are u taking msm8974 kernel from tommy wich is for stock rom, u really like things complicated bro. if u take mine from team validus repos or Omar's one it will surely works, and on top of that, kexec patched for multi rom...
If u absolutely wanna keep working with Tommy's one, good luck but imo if u wanna make a good custom kernel change ur base and cherry-pick his stuff for gamma control and everything if its the reason why u looking for his kernel source.
Click to expand...
Click to collapse
thanks for reply,
im sorry i thought i made it clear that i tried usind cwm and twrp.
already made all the changes to rhine, ramdisk and stuff... set all the flags and made changes to recovery rhine-common/rootdir/init.recovery.qcom.rc like described here:
http://forum.xda-developers.com/showthread.php?t=1943625
was never a problem with kitkat.
https://github.com/Tommy-Geenexus/android_kernel_sony_msm8974 which im using is lollipop cm kernel forked from cm. which is booting if altering "combinedroot.fs" to ramdisk.img like written in post #2 but of course without recovery!
if i dont alter "costumbootimg.mk" device is stuck at sony logo.
no difference if i change to cwm recovery either. its also the same if use cm kernel instead of tommys. i could try validus but as it is a forked cm kernel im guessing i will have the same result.
there is no kernel at github from omareinea which would be compatible with lollipop.

---

Cuz his kernel is not in his account, its in greatdevs organisation.
Well sorry but me, i don't know then...it works on my roms and cuz fota kernel is less complicated...im no more crushing my head on recoveries xD

---

update
i made a clean/fresh linux install ubuntu (14.10)
i reseted the device with flashtool to sony stockfirmware .108 and installed from fresh.
used different sources (cm, validus, greatdevs).
problem still persists. :crying:
if i check the uncompress combinedroot.cpio with cpio -tv combinedroot.cpio everything looks good.
and as stated if i use ramdisk.img instead of combinedroot.fs kernel/rom boots but no recovery... FOTAKernel is installed with twrp. If i flash a kernel i didnt build there is no problem booting recovery or rom.

---

problem was the android-eabi toolchain.
changed to default google toolchain and now its working.
i feel stupid now
before i only tried different arm-eabi toolchains.
now it all make sense.
i guess it must be problem in compiled cpio.

---

MusterMaxMueller said:
problem was the android-eabi toolchain.
changed to default google toolchain and now its working.
i feel stupid now
before i only tried different arm-eabi toolchains.
now it all make sense.
i guess it must be problem in compiled cpio.
Click to expand...
Click to collapse
don't feel stupid, cuz i did same error and took me a month to find out.