Develop Bugs

[RECOVERY] TWRP 2.4.3 (downloads + DIY How-to) [for CM10/AOKP/PAC-man]

DISCLAIMER: I own Xperia X10, Xperia J, Xperia Tipo, Xperia S and Xperia V, releases of all other phones are not personally tested by me. But since the kernel is the same in FXP/KXP ROMs I presume they would not harm your device in any way
Huge props go to all TeamWIn people like Dees_Troy and bigbiff and everyone else for developing this awesome recovery and lots of thanks to FreeXperia Team (FXP, Kali-, codeworkx, bin4ry,) for maintaining device configs for Xperias
This recovery is embedded into the ramdisk of a normal AOKP 4.1.2 bootimage. The kernels are same as the latest AOKP released by KXP team. These kernels should work with FXP's CM10, and other ROM's based of it (KXP ROM, Pac-man, officialCM10 etc). These kernels will not work on stock/cm7/cm9/blah/blah/any other ROM.
INSTRUCTIONS :
1. Download the zip file for your device (twrp2.4.3-xxxxx.zip)
2. Extract the boot.img from zip on your PC, and copy the whole zip file on device's SDcard.
3. Fastboot the kernel using the terminal command
Code:
fastboot flash boot boot.img
4. To enter recovery, when LED is pink press {vol up for 2012 models} or {vol down for 2011 models}
5. Flash zip that you kept in sdcard from recovery (wifi/OTG/etc will not work without proper modules flashed).
6. Enjoy
DOWNLOADS:
Mirror1 |or| Mirror2
download according to your device name in this list
Code:
[LIST]
[*]anzu Arc/ArcS
[*]aoba ION
[*]coconut Live with WALKMAN
[*]haida Neo V
[*]hallon Neo
[*]hayabusa TX
[*]hikari Acro S
[*]jlo J
[*]iyokan Pro
[*]mango MiniPro
[*]mesona Miro
[*]mint T
[*]nozomi S/SL
[*]satsuma Active
[*]smultron Mini
[*]tapioca Tipo
[*]tsubasa V
[*]urushi Ray
[*]zeus Play
[*]zeusc Play CDMA
[/LIST]
CHANGELOG :
All official changes to TWRP is found on http://teamw.in
Code:
=============twrp 2.4.3
code updated to oficial twrp 2.4.3.0
new device J, Tipo, Miro supported
=============twrp2.4
code updated to official twrp 2.4.1.0
fixed "/boot not found" error on 2011 phones
=============twrp 2.3
official twrp 2.3 sources
first release
=======================================================================================
for advanced users/devs/modders/porters
=======================================================================================
SOURCES:
The kernels present inside the bootimages are compiled from these sources
https://github.com/KangXperiaProject/android_kernel_sony_msm7x27a (for Tipo, J, Miro)
https://github.com/KangXperiaProject/android_kernel_sony_msm8x60 (for S,Ion,AcroS, T, V, TX)
https://github.com/KangXperiaProject/android_kernel_semc_msm7x30 (for all 2011 model phones)
The device configs are found on
https://github.com/KangXperiaProject/android_device_semc_<yourdevicename> (for all 2011 model phones)
https://github.com/KangXperiaProject/android_device_sony_<yourdevicename> (for all 2012 model phones)
you can also see our merged commits to see the precise patch we applied on each repository to be able to build TWRP
http://smartdev.com.pl:8080/#/q/status:merged,n,z
BUILD FROM SOURCE
To build TWRP for your Xperia,
1. merge the patch to enable TWRP on your own device tree (for eg. http://smartdev.com.pl:8080/#/c/239/ for Xperia T)
2. replace /bootable/recovery folder with TWRP (as mentioned here http://forum.xda-developers.com/showthread.php?t=2069242)
3. If your build folder is not from CM, switch to CM's build folder (i.e the android_build repo)
4. lunch ; mka bootimage;
PORT TO STOCK/ICS/YOU-FAVOURITE-KERNEL
A boot.img consists of the kernel image and the ramdisk (additionally and optionally RPM.bin and commandline). If you want to use TWRP for some other kernel, you have to do this
1. decompile this boot.img (for 2011 models it's a true boot.img, for 2012 models, it's actually a kernel.elf file renamed to boot.img, so you have to decompile accourdingly. you can use my kernel kitchen to do the same)
2. replace the kernel zImage with the one from the kernel you want to port to
3. replace /sbin/ramdisk.cpio with the "UNCOMPRESSED" ramdisk of the kernel you want to port this to. (usually ramdisk is compressed with gzip i.e. ramdisk.cpio.gz. you need to uncompressed ramdisk image i.e. ramdisk.cpio)
4. do not touch anyother thing
5. pack it up into a boot.img (for 2011) or kernel.elf (for 2012) and fastboot it
============================================================================================
BUGS AND SUPPORT
If you have any problem with this please please please post only on this thread, not on any other thread or not on PM.
Please send me the recovery log wherever possible, and also kmsg/dmesg if you can.
If you need assistance porting TWRP to your kernel, or building from source[only for Xperia phones that I have provided builds for], then also you can post here.

i don't no way i can't download from http://uploaded.net
please upload it to other site .. Thanks any way :good:

AL PRINCE- said:
i don't no way i can't download from http://uploaded.net
please upload it to other site .. Thanks any way :good:
Click to expand...
Click to collapse
http://icxperia.com/kxp/twrp

championswimmer said:
http://icxperia.com/kxp/twrp
Click to expand...
Click to collapse
Thanks
---------- Post added at 05:35 PM ---------- Previous post was at 05:29 PM ----------
Works fine :good:

@championswimmer, thx for recovery! But in Acro S don't work usb mount in recovery. My windows see unknown device without driver and don't to want to catch already installed.
I've added this recivery to my stock kernel

Desperanto86 said:
@championswimmer, thx for recovery! But in Acro S don't work usb mount in recovery. My windows see unknown device without driver and don't to want to catch already installed.
I've added this recivery to my stock kernel
Click to expand...
Click to collapse
porting it to stock kernel worked ?
(you ported using the instructions i mentioned in OP ?? )

championswimmer said:
porting it to stock kernel worked ?
(you ported using the instructions i mentioned in OP ?? )
Click to expand...
Click to collapse
yes! all works except usb mount http://forum.xda-developers.com/showthread.php?t=2177083 ! but usb mount dont work in your original boot.img. I've downloaded twpr for hikari, unpack it and place there my zImage, rmp and ramdisk.cpio
But I have one question: why repack of TWRP don't work? I just tried unpack ramdisk-recovery.cpio and pack it again to ramdisk.cpio.gz, unpack ramdisk.cpio and reneame it to ramdisk-recovery.cpio, so I have the same file but it don't work How I should pack it?

Desperanto86 said:
yes! all works except usb mount http://forum.xda-developers.com/showthread.php?t=2177083 ! but usb mount dont work in your original boot.img. I've downloaded twpr for hikari, unpack it and place there my zImage, rmp and ramdisk.cpio
But I have one question: why repack of TWRP don't work? I just tried unpack ramdisk-recovery.cpio and pack it again to ramdisk.cpio.gz, unpack ramdisk.cpio and reneame it to ramdisk-recovery.cpio, so I have the same file but it don't work How I should pack it?
Click to expand...
Click to collapse
ramdisk.cpio and ramdisk.cpio.gz are separate things as you understand
ramdisk folder >>>>(pack using cpio)>>> ramdisk.cpio >>>>(compress by gunzip)>>> ramdisk.cpio.gz
the final ramdisk is always compressed as .gz
but it the ramdisk comtains other ramdisks inside it then those should not be compressed they should just be ramdisk.cpio
(my kitchen does not have an option of actually just making cpio. it makes cpio.gz in one step, u have to manually extract the cpio from the gz afterwards)

championswimmer said:
ramdisk.cpio and ramdisk.cpio.gz are separate things as you understand
ramdisk folder >>>>(pack using cpio)>>> ramdisk.cpio >>>>(compress by gunzip)>>> ramdisk.cpio.gz
the final ramdisk is always compressed as .gz
but it the ramdisk comtains other ramdisks inside it then those should not be compressed they should just be ramdisk.cpio
(my kitchen does not have an option of actually just making cpio. it makes cpio.gz in one step, u have to manually extract the cpio from the gz afterwards)
Click to expand...
Click to collapse
yes, I know it. I wanted to tell, that if I extract ramdisk-recovery.cpio and change, for example, logo.rle, then pack it back to .gz and extract from .gz my new ramdisk-recovery.cpio, then pack to .gz full ramdisk (sbin init logo.rle) and build kernel.elf, kernel don't work. If nothing do with ramdisk-recovery.cpio all work fine

[Tool][Kernel]Xperia_kerneltool-For all Xperia devices

******* Hi all ********​I have developed this little tool containing a few utilities for our Xperia devices​
Xperia_kerneltool​
Overview​
I created this tool to automate the process of kernel compilation for our beloved Xperia devices..In the process i have added a few more utilities like TA partiton backup.
-After completion I added a lot more features like building Cyanogenmod for any device..Kernel tools for a few more devices EFS partition backup..Git tools etc and made a multitool. If you are interested in that multitool then head over to my multitool thread
dark_multitool1.0
Features​
-Sony Kernel
Unpack Kernel Source
-Create zImage of various devices(any Xperia)
-Extract kernel.sin from ftf file
-Unpack kernel.sin(to get zImage and ramdisk)
-Make dt.img(For Xperia Z1 and Z ultra)
-Make kernel.elf or boot.img depending on device
-Download toolchains
-Unpack boot.img to get zImage and Ramdisk
-Unpack or Repack ramdisk
-Build zImage for a generic kernel(Experimental)
-Backup TA partition for Sony(By dd Method only)
How to install??
Download the tar.gz file from the link above..Place it in your home directory and run the following command in your terminal
tar -xjvf xperia_kerneltool.tar.gz
How to run it??
cd to the folder xperia_kerneltool and type ./menu in your terminal and execute
This tool is only for any linux based distro(Ubuntu,fedora etc) atm and i dont know if it will work in cygwin
You can install vitualbox and install ubuntu or any other linux based distro to use the tool if you are running windows
Credits
-xda and its wonderful devs for teaching me everything
-Doomlord for his exceptional threads and tutorials on Xperia devices
-Rickwyatt and Rekoil for Ta partition backup tutorial for Xperia
-Google.com
If i have forgotten anyone then please let me know
Donations
Running a 512 mb laptop with a semi crashed hard disk.....So any kinds of donations are welcome if you like the tool
>Just donate to my email ID : [email protected]
>I am from India..so personal payment wont work
>Select buy me goods/services and it should work
>You can donate via tool as well.....
Mods : Please Move the thread if its in the inappropriate section
Updates
-I will keep the thread updated with the latest tool and you can also update the tool through the tool itself
FAQs in the second post
Changelogs in the third post
XDA:DevDB Information
Xperia_kerneltool, a Tool/Utility for the Sony Xperia Acro S
Contributors
Dark Wraith
Version Information
Status: Alpha
Created 2013-12-10
Last Updated 2013-12-10

Reserved
FAQs
>Why is it giving errors while compiling zImage for Xperia devices????
Answer : You need to add the various makefile and defconfig fixes for the toolchain to work properly
Please refer to this excellent thread by Doomlord for various fixes
http://forum.xda-developers.com/showthread.php?t=2447310
>TA partition doesn't work properly
Answer : Please remember to specify the memory block correctly. If you still get an error then please tell me the error so that i can check if the error is from the tool's end
>How to add a toolchain????
Answer : Add it under android_toolchains folder in your home directory
Open the tool and navigate to toolchain_selector script under scripts folder
Add the toolchain name and the correct path as given there in the following format
toolchain_name[the number after the last toolchain name]=
toolchain_path[the number after the last toolchain path] =
>How to clean your kernel work directory?
Answer ; Navigate to the kernel work directory : make clean
I will incorporate this in the next release
>Download toolchains or update tool doesnt work
Answer : make sure you have the git package installed.
Bugs and Suggestions
Please let me know

Reserved

Where is the download link?

juppi said:
Where is the download link?
Click to expand...
Click to collapse
Umm..under download tab..dont download this. Download dark multitool. Its there in my signature
Sent from my Micromax A110 using xda app-developers app

Making a CM11.0 kernel for E980?

Hello fellow OGPers...
So I've been jumping from ROM to ROM for a solid few months now. Really enjoyed my time as an Android user and soaked in a lot. I've been learning (well... teaching myself) about Linux and other related things. But I've been busy with classes, a social life, and other commitments. Anyway let me cut to the chase. I really enjoyed it in 4.3 ROMs when I could use all the settings on the AOSP custom kernel for our device and among other things liked the experience of a custom kernel. It's about time we got one for 4.4.x Kitkat... right?
I am currently running Windows 7 (if specs are important I will post them) with a Linux Mint distro (both are 64-bit). I have downloaded the CM11.0 from github and a few toolchains. I haven't untared them yet or anything, but I have some. One is specialized for Cortex A-15, which I read our device's CPU is much alike to. Anyway I just wanted some help getting started with making a kernel is what it comes down to. I have basic Linux knowledge and that's about it. I just want to get a custom kernel out and then maybe in the future get a nice battery-optimized kernel out. I forgot to grab a kernel patch and I'll download it tomorrow probably. But I really don't know where to start at all. Do I need knowledge of anything or some more experience knowledge? If anybody can point me in a good direction that would be great. Everything is appreciated.
Oh and feel free to PM me answers as well if it's easier or more convenient for you.
Thanks guys!

This would be great as we need a kernel Dev ... Good luck on your journey !
2SHAYNEZ

If you only want to compile kernel,clone this repository.
git clone https://github.com/CyanogenMod/lge-kernel-gproj/tree/cm-11.0
make any change you want to do with the source.
Download android toolchain and extract it.
Compile the kernel sources with
export ARCH=arm CROSS_COMPILE=/path.to.toolchain/bin/arm-eabi- && make cyanogenmod_e980_defconfig && make -j#
(# is the number of your computer cores +1)
you will get zimage in /arch/arm/boot folder
Using boot.img(the kernel) from official CM build zip to get the ramdisk is easier
abootimg -x boot.img
you will see:
writing boot image config in bootimg.cfg
extracting kernel in zImage
extracting ramdisk in initrd.img
put the extracted initrd.img and bootimg.cfg to /arch/arm/boot(where your compiled zimage are)
run:
abootimg --create boot.img -f bootimg.cfg -k zImage -r initrd.img
You will get the boot.img!
This is the complete kernel!
Use any previous kernel zip, and replace the boot.img inside the zip with yours.
Flash it and test it.
My TWRP 2.8.0.0 or TWRP from freegee or Philz Touch will auto lokify the kernel.
Wing

Attached is the kernel.zip that i use.
Replace the your finished boot.img with it~~
Wing

BTW i am not programmer, but i am a very long time gentoo linux and archlinux user, long before android exist~

mukwing said:
If you only want to compile kernel,clone this repository.
git clone https://github.com/CyanogenMod/lge-kernel-gproj/tree/cm-11.0
make any change you want to do with the source.
Download android toolchain and extract it.
Compile the kernel sources with
export ARCH=arm CROSS_COMPILE=/path.to.toolchain/bin/arm-eabi- && make cyanogenmod_e980_defconfig && make -j#
(# is the number of your computer cores +1)
you will get zimage in /arch/arm/boot folder
Using boot.img(the kernel) from official CM build zip to get the ramdisk is easier
abootimg -x boot.img
you will see:
writing boot image config in bootimg.cfg
extracting kernel in zImage
extracting ramdisk in initrd.img
put the extracted initrd.img and bootimg.cfg to /arch/arm/boot(where your compiled zimage are)
run:
abootimg --create boot.img -f bootimg.cfg -k zImage -r initrd.img
You will get the boot.img!
This is the complete kernel!
Use any previous kernel zip, and replace the boot.img inside the zip with yours.
Flash it and test it.
My TWRP 2.8.0.0 or TWRP from freegee or Philz Touch will auto lokify the kernel.
Wing
Click to expand...
Click to collapse
Wow thank you so much... definitely going to give this a shot today! So I didn't have to download the 12 GB source... good to know.
Oh and one more thing. Is there any difference from building a CM11 kernel vs an AOSP 4.4.x kernel? I figured since most of our device's ROMs are CM based this would work fine... Thank you very much for the information at hand! Appreciated.

CM kernel is different from AOSP kernel from what i know.
CM kernel is base on CAF(which is optimized for msm chip) and AOSP kernel base on google original code.
They are a bit different so imcompatible from what i know.
Wing

When I compile there are loads of errors and eventually it stops (at different times each attempt...) anyway, the first thing I notice is this:
warning: (ARCH_MSM7X27 && ARCH_MSM8960 && ARCH_MSM8930 && ARCH_MSM8974) selects DONT_MAP_HOLE_AFTER_MEMBANK0 which has unmet direct dependencies (SPARSEMEM)
warning: (ARCH_MSM7X27 && ARCH_MSM8960 && ARCH_MSM8930 && ARCH_MSM8974) selects DONT_MAP_HOLE_AFTER_MEMBANK0 which has unmet direct dependencies (SPARSEMEM)
Is that anything I have to worry about? I can't find anything online about it. Thanks in advance.

First, is it unmodified cm kernel sources?
Make sure to use unmodified sources to test building first.
Somes errors can safely ignored.The msm8960 error can safty ignore. It has nothing to do with our device.
If it failed to build, try using option like -Xlint.
Sometimes, using older build of toolchain is easier to build, e.g.gcc4.7 or 4.8
Gcc 4.9 always failed to build e980 cm kernel.

mukwing said:
First, is it unmodified cm kernel sources?
Make sure to use unmodified sources to test building first.
Somes errors can safely ignored.The msm8960 error can safty ignore. It has nothing to do with our device.
If it failed to build, try using option like -Xlint.
Sometimes, using older build of toolchain is easier to build, e.g.gcc4.7 or 4.8
Gcc 4.9 always failed to build e980 cm kernel.
Click to expand...
Click to collapse
Ohhh okay. Yeah it's all unmodified and I've downloaded tons of "needed" packages (including most likely unnessesary ones too). I'm using a 4.9 GCC. That might be it. Okay thanks. I'll give another shot tomorrow when I have access to my VM.

Kernel has been successfully compiled. Check here for download and further discussion...
http://forum.xda-developers.com/optimus-g-pro/orig-development/kernel-e980-kernel-t2872514

Need help compiling sedikernel (or any kernel)

Hello,
In order to debug the bluetooth problem, I'm trying to compile a kernel for the Captivate Glide. I can't get it to boot properly.
@steadfasterX 's SediROM is the highest-version ROM I know of on which bluetooth works so I've got it installed (version 2.1.2) on the phone.
The steps I've taken so far:
1. I have sedikernel from https://github.com/steadfasterX/kernel_samsung_i927 at commit 088aa4109ad144c583f32da5ffba7bac200f0575
2. I copied /proc/config.gz from a running phone, which contains CONFIG_LOCALVERSION="-sediKERNEL-v1.0", ungzipped it and saved it as .config . Haven't changed anything in it yet.
3. I ran `make CROSS_COMPILE=arm-linux-gnueabihf- zImage` (also tried arm-none-eabi- (both from Debian Jessie) as well as ~/Android/Sdk/ndk-bundle/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64/bin/arm-linux-androideabi- from the NDK)
4. I also made a TWRP backup of the boot partition, and used split_bootimg.pl from William Enck to split it into a kernel and initrd
5. I then ran mkbootimg with the initrd extracted in step 4 and the kernel obtained in step 3 in arch/arm/boot/zImage
6. Finally I flashed this new boot.img onto the phone with odin (Heimdall, specifically)
I see the white "SAMSUNG" logo (which is normal when booting) with a yellow-triangle with an exclamation mark in it. No further boot stage happens (no bootanim from sediROM). If I re-pack the original kernel with bootimg and flash that via odin, then after the next boot the yellow triangle changes into a blue one and sediROM boots correctly.
I'm a bit stuck at the moment, not sure what's going wrong there. Probably the kernel panics for some reason. Is there a way to read the kernel boot messages before android starts? Any help would be greatly appreciated.
Thanks!

Successful!
Thanks to a lot of help from @steadfasterX on IRC I finally managed to compile a working kernel
Here's a list of steps I had to follow in addition to https://github.com/steadfasterX/android_device_samsung_i927/blob/sediROM_CM-ICS/README.md :
1. as discussed on IRC, `repo sync` was not finding a branch. Needed to add
Code:
revision="refs/heads/ics-release"
in .repo/manifests/default.xml in the line with
Code:
CyanogenMod/android_vendor_qcom_opensource_v8
2. I removed the spurious comma in device/samsung/i927/cm.dependencies
3. In device/samsung/i927/, I changed vendorsetup.sh to point to vendorsetup.sh.nopatching rather than .patching (none of the patches could be applied)
4. lunch target was therefore the one with -eng, not -userdebug
5. I installed java 6 manually (didn't have sudo)
6. I installed schedtool
7. I adjusted the path to Java and my toolchain in build_sediROM.sh (taken from https://github.com/steadfasterX/android_buildtools )
8. I downgraded GNU make from 4.0 to 3.81
9. I installed linux-headers and created a symlink from /usr/include/asm-generic to /usr/include/asm
10. I changed the toolchain prefixes in device/samsung/i927/BoardConfig.mk to have 4.4.3 rather than 4.7
11. I built with
Code:
BUILDID=samsung/i927 LOKIFY=0 ../android_buildtools/build_sediROM.sh bootimage
12. I used the original ramdisk I had extracted from sediROM's boot image, rather than the one that was built (we discussed this on IRC too)
This got me a working kernel, yay

uukgoblin said:
Thanks to a lot of help from @steadfasterX on IRC I finally managed to compile a working kernel
Here's a list of steps I had to follow in addition to https://github.com/steadfasterX/android_device_samsung_i927/blob/sediROM_CM-ICS/README.md :
1. as discussed on IRC, `repo sync` was not finding a branch. Needed to add
Code:
revision="refs/heads/ics-release"
in .repo/manifests/default.xml in the line with
Code:
CyanogenMod/android_vendor_qcom_opensource_v8
2. I removed the spurious comma in device/samsung/i927/cm.dependencies
3. In device/samsung/i927/, I changed vendorsetup.sh to point to vendorsetup.sh.nopatching rather than .patching (none of the patches could be applied)
4. lunch target was therefore the one with -eng, not -userdebug
5. I installed java 6 manually (didn't have sudo)
6. I installed schedtool
7. I adjusted the path to Java and my toolchain in build_sediROM.sh (taken from https://github.com/steadfasterX/android_buildtools )
8. I downgraded GNU make from 4.0 to 3.81
9. I installed linux-headers and created a symlink from /usr/include/asm-generic to /usr/include/asm
10. I changed the toolchain prefixes in device/samsung/i927/BoardConfig.mk to have 4.4.3 rather than 4.7
11. I built with
Code:
BUILDID=samsung/i927 LOKIFY=0 ../android_buildtools/build_sediROM.sh bootimage
12. I used the original ramdisk I had extracted from sediROM's boot image, rather than the one that was built (we discussed this on IRC too)
This got me a working kernel, yay
Click to expand...
Click to collapse
its really long guide. You have to replace kernel modules, wifi wouldnt work without modules.
Imho best is compile kernel, modules, replace zImage + modules in this
file and flash from recovery. You dont need to compile whole android just the kernel, you dont need java and other special things, this method is much more faster.

bubor said:
its really long guide. You have to replace kernel modules, wifi wouldnt work without modules.
Imho best is compile kernel, modules, replace zImage + modules in this
file and flash from recovery. You dont need to compile whole android just the kernel, you dont need java and other special things, this method is much more faster.
Click to expand...
Click to collapse
You are right for the kernel but we discussed on IRC to build ram disk too then you need all that stuff but most important he wants to build CM too.
However I'm always a fan of making it right so building a ram disk is the correct way of creating a bootimage. But to start its ok replacing kernel and modules first.
.
Sent from my LG-H815 using XDA Labs

steadfasterX said:
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
correct way is rebuild whole android, and reflash everything, wipe data/cache
You dont want to make new ramdisk without replace system. System and ramdisk bound together.
I hope you find something, and fix bluetooth or voip audio.
good luck

bubor said:
correct way is rebuild whole android, and reflash everything, wipe data/cache
You dont want to make new ramdisk without replace system. System and ramdisk bound together.
I hope you find something, and fix bluetooth or voip audio.
good luck
Click to expand...
Click to collapse
Well no and yes. I build kernels including ram disk without building system. This is not necessary as long both are compatible.
But you are right that booting fails when system and ram disk are not compatible so the correct way depends
However @uukgoblin I hope you get the fix you want :fingers-crossed:
Sent from my LG-H815 using XDA Labs

steadfasterX said:
Well no and yes. I build kernels including ram disk without building system. This is not necessary as long both are compatible.
But you are right that booting fails when system and ram disk are not compatible so the correct way depends
However @uukgoblin I hope you get the fix you want :fingers-crossed:
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
would you tell me an example when kernel doesnt compatible with ramdisk but kernel does compatible with system?

bubor said:
would you tell me an example when kernel doesnt compatible with ramdisk but kernel does compatible with system?
Click to expand...
Click to collapse
No no my friend that's not what I said. :cyclops:
I meant if you have CM 9 as system you can build a boot image which includes kernel and a CM9 based ram disk without building cm9 system again. :laugh:
.
Sent from my LG-H815 using XDA Labs

T2 Ultra stock 5.1.1 working kernel sources

Hope I'm not too late in posting this message to any devs or learning devs for the T2U. I've patched up my C3 stock kernel and confirmed that it's working as intended so I'm sharing my sources with you as we share the same CPU and firmware.
My original thread (do not flash this, it is built for the C3 and not T2U): https://forum.xda-developers.com/so.../kernel-manjuu-kernel-sony-xperia-c3-t3564190
My kernel source: https://github.com/AngryManjuu/19.4.A.0.182_kernel
For those learning how to compile, here's a few things you need to know:
1. I used this guide from XDA University.
2. That guide is using a very old toolchain, so I used this toolchain which is optimised for our CPU (Cortex-A7) and the latest NDK version, 13b.
3. Be sure to build your kernel using yukon_tianchi_defconfig found in /arch/arm/configs/.
4. You will get build errors, just double-check them by referring to my commits starting on 24 Feb 2017.
5. I'm not sure if dual sim is supported.
6. No I won't build for T2U, but you're welcome to use this thread if you have questions on building.
7. This tool will help you pack your zImage into a boot.img. Please use the original stock boot.img (you can use TWRP to backup and get it from there) to unpack and repack always otherwise your kernel won't boot.
8. There is no flashable zip, the boot.img is the kernel itself so just use fastboot to flash it.

I am interested, in case there is something ready about it could make available ??