yashsingh1/xdaforums huggingface dataset:
[Sony Cross-Device General] DooMLoRD:
hello folks!

i have been working on kernels for various xperia devices since the Xperia X10... i will update this thread with information on how to build kernels for various xperia devices...

Sony (Ericsson) started off helping the developer community with information on how to build kernels:

http://developer.sonymobile.com/2011/05/06/how-to-build-a-linux-kernel/

do read the above post, though its slightly old (2011), its really good! Since then Sony has released various devices which use a variety of chipsets and each chipset has different ways to build bootable kernel...

the objective of this thread is to provide brief instructions for some of these chipsets across the various device generations to build bootable kernels...

this will not cover how to build working ramdisks... you can always use the stock ramdisks from kernel.sin... here is how to get stock ramdisk out from kernel.sin...

Toolchains:

I have tested various toolchains for building kernels and very few work correctly on the kernel sources to get bootable kernel.

The toolchains which worked for me are:

arm-eabi-4.4.3 - GCC 4.4.3 toolchain from CyanogenMod repo

arm-eabi-linaro-4.6.2 - GCC Linaro 4.6.2 (2011.10) toolchain

arm-linux-androideabi-4.7 - GCC 4.7 from Google repo

all of these are posted on my git repo:

https://github.com/DooMLoRD/android_prebuilt_toolchains

sometimes the kernel sources need to be modified slightly to support compiling using these toolchains. I have mentioned the necessary patches where-ever applicable.

Instructions for various generation of devices:

Xperia 2014 (H1) - msm8974ab - Xperia Z2

Xperia 2013 (H2) - msm8974 - Xperia Z1, Z Ultra, Z Ultra GPe, Z1 Compact

Xperia 2013 (H1) - apq8064 - Xperia Z, ZL, ZR, Tablet Z

Xperia 2013 (H1) - msm8960t - Xperia SP

Xperia 2012 (H2) - msm8960 - Xperia T, TX, V

Xperia 2012 (H1) - msm8660 - Xperia S, SL, Ion, Acro S

Xperia 2011 - msm8x55/msm7x30 - Xperia Arc, Play, Neo, Ray, etc
[Sony Cross-Device General] DooMLoRD:
reserved for later
[Sony Cross-Device General] DooMLoRD:
Instructions for MSM8x55/MSM7x30

Latest sources available at:

http://developer.sonymobile.com/dow...ves/open-source-archive-for-build-4-1-b-1-13/

Recommended toolchain:

GCC 4.6 Linaro

Fix Makefile for 4.6 Toolchain:

KBUILD_CFLAGS := -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs \
-Werror \

to:

KBUILD_CFLAGS := -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs \
-Wno-unused-but-set-variable -Wno-uninitialized \

Supported boards on this platform:

zeus - Xperia Play, Xperia L

mogami - Xperia Arc, Arc S, Ray, Neo, etc

Building kernel (zImage):

for Xperia Arc (anzu):

import defconfig

ARCH=arm CROSS_COMPILE=~/android-toolchain-eabi-linaro-4.6-2011.10/bin/arm-eabi- make semc_anzu_defconfig

for Xperia Play (zeus):

import defconfig

ARCH=arm CROSS_COMPILE=~/android-toolchain-eabi-linaro-4.6-2011.10/bin/arm-eabi- make semc_zeus_defconfig

build zImage

ARCH=arm CROSS_COMPILE=~/android-toolchain-eabi-linaro-4.6-2011.10/bin/arm-eabi- make -j8

Instructions for building boot.img

first get the kernel built... once kernel is built u will get zImage and copy that zImage to the folder containing the build tools...

i have posted the build tools i use here:

https://github.com/DooMLoRD/build_tools/tree/master/msm7x30_mogami_zeus

Sony used the standard boot.img format for this chipset devices

building boot.img

use the following command:

./mkbootimg --base 0x00200000 --kernel zImage --ramdisk ramdisk.cpio.gz -o boot.img

Special notes

Sometimes the compiled kernel will just not boot, will show blank screen. Workaround is, ramdisks needs to be filled with filler so that total size is bigger.

boot.img can be hotbooted (fastboot boot boot.img)

regards,

DooMLoRD
[Sony Cross-Device General] XperianPro:
Novathor?
[Sony Cross-Device General] DooMLoRD:
Instructions for MSM8260/MSM8660

Latest sources available at:

Since I actively develop for a device of this platform (Xperia S) latest sources can found at my git repo:

https://github.com/DooMLoRD/android_kernel_sony_msm8660/tree/sony_sources

Recommended toolchain:

GCC 4.7

Fixes for 4.7 Toolchain:

Makefile fix

defconfig fix

Supported boards on this platform:

fuji- Xperia S, SL, Ion, Acro S

Building kernel (zImage):

for Xperia S (nozomi):

import defconfig

ARCH=arm CROSS_COMPILE=~/arm-linux-androideabi-4.7/bin/arm-linux-androideabi- make fuji_nozomi_defconfig

build zImage

ARCH=arm CROSS_COMPILE=~/arm-linux-androideabi-4.7/bin/arm-linux-androideabi- make -j8

Instructions for building kernel.elf

first get the kernel built... once kernel is built u will get zImage and copy that zImage to the folder containing the build tools...

i have posted the build tools i use here:

https://github.com/DooMLoRD/build_tools/tree/master/msm8660_fuji

Sony shifted to ELF format for this chipset...

They had posted instructions on there website:

http://developer.sonymobile.com/201...-archive-released-with-building-instructions/

(avoid using those files as they are for GingerBread)

building kernel.elf

use the following command (for JB):

python mkelf.py -o kernel.elf zImage@0x40208000 ramdisk.cpio.gz@0x41300000,ramdisk RPM_JB.bin@0x20000,rpm

the additional files required are posted at my build tools repo

Special notes

RPM is different for each device and also differs for OS release, so the same RPM wont work on Xperia S or Xperia Ion and GB/ICS/JB each have different RPMs

kernel.elf CANNOT be hotbooted (fastboot boot kernel.elf)

regards,

DooMLoRD
[Sony Cross-Device General] DooMLoRD:
Instructions for MSM8960

Latest sources available at:

Since I actively develop for a device of this platform (Xperia T) latest sources can found at my git repo:

https://github.com/DooMLoRD/android_kernel_sony_msm8960/tree/sony_sources

Recommended toolchain:

GCC 4.6 Linaro

Supported boards on this platform:

blue- Xperia T, TX, V

Building kernel (zImage):

for Xperia T (mint):

import defconfig

ARCH=arm CROSS_COMPILE=~/android-toolchain-eabi-linaro-4.6-2011.10/bin/arm-eabi- make blue_mint_defconfig

build zImage

ARCH=arm CROSS_COMPILE=~/android-toolchain-eabi-linaro-4.6-2011.10/bin/arm-eabi- make -j8

Instructions for building kernel.elf

first get the kernel built... once kernel is built u will get zImage and copy that zImage to the folder containing the build tools...

i have posted the build tools i use here:

https://github.com/DooMLoRD/build_tools/tree/master/msm8960_blue

Sony uses ELF format for this chipset...

building kernel.elf

use the following command (for JB):

python mkelf.py -o kernel.elf zImage@0x80208000 ramdisk.cpio.gz@0x81400000,ramdisk RPM_JB.bin@0x00020000,rpm bootcmd_JB@0x00000000,cmdline

the additional files required are posted at my build tools repo

Special notes

RPM is different for each device and also differs for OS release, so the same RPM wont work on Xperia T or Xperia V as each have different RPMs

kernel.elf CANNOT be hotbooted (fastboot boot kernel.elf)

regards,

DooMLoRD
[Sony Cross-Device General] DooMLoRD:
Instructions for MSM8960T

Latest sources available at:

Since I actively develop for a device of this platform (Xperia SP) latest sources can found at my git repo:

https://github.com/DooMLoRD/android_kernel_sony_msm8960t/tree/sony_sources

Recommended toolchain:

GCC 4.7

Fixes for 4.7 Toolchain:

Makefile fix

Supported boards on this platform:

viskan- Xperia SP

Building kernel (zImage):

for Xperia SP (huashan):

import defconfig

ARCH=arm CROSS_COMPILE=~/arm-linux-androideabi-4.7/bin/arm-linux-androideabi- make viskan_huashan_defconfig

build zImage

ARCH=arm CROSS_COMPILE=~/arm-linux-androideabi-4.7/bin/arm-linux-androideabi- make -j8

incase u get errors like:

error : /scripts/gcc-wrapper.py

just correct the permissions of that file

chmod 755 ./scripts/gcc-wrapper.py

Instructions for building kernel.elf

first get the kernel built... once kernel is built u will get zImage and copy that zImage to the folder containing the build tools...

i have posted the build tools i use here:

https://github.com/DooMLoRD/build_tools/tree/master/msm8960t_viskan

Sony uses ELF format for this chipset...

building kernel.elf

use the following command:

python mkelf.py -o kernel.elf zImage@0x80208000 ramdisk.cpio.gz@0x81600000,ramdisk RPM.bin@0x00020000,rpm bootcmd@0x00000000,cmdline

the additional files required are posted at my build tools repo

Special notes

kernel.elf CANNOT be hotbooted (fastboot boot kernel.elf)

regards,

DooMLoRD
[Sony Cross-Device General] DooMLoRD:
Instructions for APQ8064

Latest sources available at:

Since I actively develop for a device of this platform (Xperia Z) latest sources can found at my git repo:

https://github.com/DooMLoRD/android_kernel_sony_apq8064/tree/sony_sources

Recommended toolchain:

GCC 4.7

Fixes for 4.7 Toolchain:

Makefile fix

prima fix

Supported boards on this platform:

fusion3- Xperia Z, ZL, Tablet Z, ZR

Building kernel (zImage):

for Xperia Z (yuga):

import defconfig

ARCH=arm CROSS_COMPILE=~/arm-linux-androideabi-4.7/bin/arm-linux-androideabi- make fusion3_yuga_defconfig

build zImage

ARCH=arm CROSS_COMPILE=~/arm-linux-androideabi-4.7/bin/arm-linux-androideabi- make -j8

Instructions for building boot.img

first get the kernel built... once kernel is built u will get zImage and copy that zImage to the folder containing the build tools...

i have posted the build tools i use here:

https://github.com/DooMLoRD/build_tools/blob/master/apq8064_fusion3

Sony uses slightly different boot.img format for this chipset...

building boot.img

use the following command:

./mkbootimg --base 0x80200000 --kernel zImage --ramdisk_offset 0x02000000 --cmdline "androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 vmalloc=400M androidboot.emmc=true" --ramdisk ramdisk.cpio.gz -o boot.img

corrected build tools are posted at my build tools repo

Special notes

boot.img CANNOT be hotbooted (fastboot boot boot.img)

regards,

DooMLoRD
[Sony Cross-Device General] DooMLoRD:
Instructions for MSM8974

Latest sources available at:

I will soon be getting the Xperia Z1 and actively develop for it... i will keep the latest sources at my git repo:

https://github.com/DooMLoRD/android_kernel_sony_msm8974/commits/sony_sources

Recommended toolchain:

GCC 4.6

Fixes for 4.6 Toolchain:

Makefile fix 1

Makefile fix 2

Supported boards on this platform:

rhine- Xperia Z1, Z Ultra

Building kernel (zImage):

for Xperia Z1 (honami):

import defconfig

ARCH=arm CROSS_COMPILE=~/android-toolchain-eabi-linaro-4.6-2011.10/bin/arm-eabi- make rhine_honami_defconfig

build zImage

ARCH=arm CROSS_COMPILE=~/android-toolchain-eabi-linaro-4.6-2011.10/bin/arm-eabi- make -j8

Instructions for building boot.img

first get the kernel built... once kernel is built u will get zImage and copy that zImage to the folder containing the build tools...

i have posted the build tools i use here:

https://github.com/DooMLoRD/build_tools/blob/master/msm8974_rhine

Sony uses slightly different boot.img format for this chipset...

building boot.img

to get the dt.img:

# path to kernel sources
KERNEL_SRC_PATH=~/android_kernel_sony_msm8974/

echo "generating device tree..."
./dtbTool -o dt.img -s 2048 -p {KERNEL_SRC_PATH}/scripts/dtc/ {KERNEL_SRC_PATH}/arch/arm/boot/

once u have the dt.img along with the zImage and ramdisk.cpio.gz use the following command:

./mkbootimg --base 0x00000000 --kernel zImage --ramdisk_offset 0x02000000 --tags_offset 0x01E00000 --pagesize 2048 --cmdline "androidboot.hardware=qcom user_debug=31 maxcpus=2 msm_rtb.filter=0x3F ehci-hcd.park=3 msm_rtb.enable=0 lpj=192598 dwc3.maximum_speed=high dwc3_msm.prop_chg_detect=Y" --ramdisk ramdisk.cpio.gz --dt dt.img -o boot.img

corrected build tools are posted at my build tools repo

Special notes

boot.img CAN be hotbooted (fastboot boot boot.img)

regards,

DooMLoRD
[Sony Cross-Device General] DooMLoRD:
Later I will add info for them too....
[Sony Cross-Device General] siankatabg:
Hello doom,I want to ask you something.I manage to port your doomkernel v22 GB for Arc/Arc S to Neo/Neo V and I want permissions from you to share it in Neo forum.Sorry for asking here, but you don't answer me on the PM that I send you.

Sorry for my English.
[Sony Cross-Device General] RuLe89:
it is possible port the kernel of 'xperia sp on xiaomi mi2a?

the two terminals have the same hardware
[Sony Cross-Device General] DooMLoRD:
updated instructions for MSM8974 kernels
[Sony Cross-Device General] Diego910:
Please take a look at novathor devices if you have time :D
[Sony Cross-Device General] gavster26:
Hi sir can you recommend a toolchain for msm7627a (Xperia J) the ones on your github won't work.
[Sony Cross-Device General] DooMLoRD:
You need to patch Makefile somethings to disable some flags for these toolchains
[Sony Cross-Device General] lozohcum:
@OP

How can I attach my compiled zImage to CM10 build from source? I have already compiled kernel from source and now I want to use it in my CM10 build
[Sony Cross-Device General] syahazu:
Great TUT
[Sony Cross-Device General] updateing:
Great tutorial! But I came across a problem:when compiling a CM kernel for Xperia TX,I need to change the command from

python mkelf.py -o kernel.elf zImage@0x80208000 ramdisk.cpio.gz@0x81[COLOR="red"]4[/COLOR]00000,ramdisk RPM_JB.bin@0x00020000,rpm bootcmd_JB@0x00000000,cmdline

to

python mkelf.py -o kernel.elf zImage@0x80208000 ramdisk.cpio.gz@0x81[COLOR="red"]7[/COLOR]00000,ramdisk RPM_JB.bin@0x00020000,rpm bootcmd_JB@0x00000000,cmdline

Otherwise the phone won't boot.Only black screen with backlight on and then reboot after pressing the power button,even no Sony/CM logo.

(Another strange case:when I use sksplit to split the official kernel,the ramdisk does lay in 0x81400000.But if I import the hayabusa_defconfig,compile the kernel from Sony source without any change and mkelf with official ramdisk@0x81400000,the phone still refuses to boot.I have to change the 4 to 7 to make this kernel boot.Why?)
[Sony Cross-Device General] joebonrichie:
{MIRO/TIPO/J/E} Addresses

zImage --0x00208000

ramdisk --0x01400000

bootcmd --cmdline

i.e.

python mkelf.py -o boot.img zImage@0x00208000 1@0x01400000,ramdisk 2@cmdline
[Sony Cross-Device General] iamsuperuser:
I'm trying to build stock kernel from sony source for my Xperia ZL C6502 for the latest 10.4.B.0.569 firmware.

I followed the tutorial in the first post and also THIS one here.

I got to import the defconfig as .config

Now when I enter the command to build zImage i get the error quoted below

iamsuperuser@ubuntu:~/android/kernel$ ARCH=arm CROSS_COMPILE=~/android/arm-linux-androideabi-4.7/bin/arm-linux-androideabi- make -j8
CHK include/linux/version.h
CHK include/generated/utsrelease.h
CC scripts/mod/empty.o
make[1]: `include/generated/mach-types.h' is up to date.
CC kernel/bounds.s
/home/iamsuperuser/android/arm-linux-androideabi-4.7/bin/arm-linux-androideabi-gcc: No such file or directory
Is your PATH set correctly?
make[2]: *** [scripts/mod/empty.o] Error 2
make[1]: *** [scripts/mod] Error 2
make: *** [scripts] Error 2
make: *** Waiting for unfinished jobs....
/home/iamsuperuser/android/arm-linux-androideabi-4.7/bin/arm-linux-androideabi-gcc: No such file or directory
Is your PATH set correctly?
make[1]: *** [kernel/bounds.s] Error 2
make: *** [prepare0] Error 2

I'm so close to build my first kernel and yet I fail every time at this step.

It actually starts with gcc-version.sh error and ends up as quoted above.

So can someone help me here ?
[Sony Cross-Device General] DooMLoRD:
Check your paths to the toolchain
[Sony Cross-Device General] iamsuperuser:
I don't know how to set path to the toolchain but i found a post on THIS guide

Is this what you want me to correct ??
[Sony Cross-Device General] iamsuperuser:
OK compiled the zImage

It was not exactly named as 'zImage' but 'Image' of about 14.5MB size.

I renamed it to zImage.

git cloned DoomLoRD's build tools

Place the zImage in apq8064_fusion3 folder

Installed ia32-libs

Extracted ramdisk.cpio.gz from kernel.sin

Ran the cmommand ./mkbootimg............etc

AAAnd here it is

Big Thanks to DooMLoRD for his help and Amazing work :victory::good:
[Sony Cross-Device General] DooMLoRD:
You should not rename it... There will be a zImage in arch/arm/boot
[Sony Cross-Device General] iamsuperuser:
OK I tried again and i found that i had to install lzop

So now i have zImage in arch/arm/boot exactly as u said.

Now while making boot.img i'm getting the following error

error: could not load ramdisk 'ramdisk.cpio.gz'
[Sony Cross-Device General] iamsuperuser:
So should i

extract ramdisk from kernel.sin using flashtool

place it in the build tools folder along with zImage

And then mkbootimg

OR

should it not give any error at all in the first place ?

How should i proceed ?
[Sony Cross-Device General] DooMLoRD:
[MENTION=4218294]iamsuperuser[/MENTION]

Check the build scripts (open and read the shell script) for required filename of each component...
[Sony Cross-Device General] iamsuperuser:
I'm really sorry i did not understand what you wanted me to do here :eek:

Did you mean the makeit.sh file in ' build_tools-master/apq8064_fusion3 ' folder ?

I read that, its same command you posted in the tutorial

Thats when i extracted ramdisk from kernel.sin renamed it to 'ramdisk.cpio.gz' and made the boot.img
[Sony Cross-Device General] iamsuperuser:
Ok I'm stuck here with zImage

To make boot.img I need 'ramdisk.cpio.gz'

Where do I get it ??
[Sony Cross-Device General] Tommy-Geenexus:
[MENTION=2784807]DooMLoRD[/MENTION] has made an ramdisk extractor, look @op.

You need a stock kernel.sin to do that.

Sent from my gold iphone 5s runnning ios 7.04 and iossuperjailbreak
[Sony Cross-Device General] iamsuperuser:
So i got the ramdisk.cpio.gz with the help of kernel.sin-unpacker

I made the boot.img

When I flashed it onto my Xperia ZL C6502 the phone does not boot even the logo does not appear just keeps bootlooping :eek:

Where did I go Wrong ??
[Sony Cross-Device General] DooMLoRD:
Use the zImage from the kernel.unpacker and check if u still have boot issue... If device boots with unpacked/repacked kernel then something is wrong with your kernel configs...
[Sony Cross-Device General] iamsuperuser:
So I finally got it to work.

Turns out I had to repack the kernel.sin-ramdisk folder to ramdisk.cpio.gz using

find . | cpio -o -H newc | gzip > ../ramdisk.cpio.gz

and then mkbootimg

I have a working boot.img now. :victory:

Thanks you DooMLoRD for your patience

Can you please help me add a CWM recovery to this boot.img ?
[Sony Cross-Device General] DooMLoRD:
[MENTION=4218294]iamsuperuser[/MENTION]

I will write a tutorial on thar later ;)
[Sony Cross-Device General] iamsuperuser:
Hi there DooMLoRD !

One last help please :D

I've used your ramdisk from HERE to repack my stock kernel for XZL to get cwm.

The blue LED shows and vibrates but when i press volume button the phone boots into homescreen but not to recovery.

The keycodes do not seem to respond to the boot_rec event or something like that .....:confused:

So if i have to check whether the keys are responding to cwm or not, which files do i have to look in the ramdisk ?

In the stock ramdisk there is a file init.sony.rc, in there i found the keycodes for

Vol Up - 115

Vol Down - 114

And in Your Ramdisk the init.sh file checks for keycheck using

export VOLUKEYCHECK=`busybox cat /dev/keycheck1 | busybox grep '0001 0073'`
export VOLDKEYCHECK=`busybox cat /dev/keycheck1 | busybox grep '0001 0072'`

So if I change

0073 to 0115 &

0072 to 0114 will the kernel then boot into recovery ???

Z has so many kernels for rooting latest .569 fw but we ZL users are still struggling here to get a kernel working with cwm for .569 fw.

The CM 10.2 Kernel for ZL(Odin) boots into recovery but not into the OS. So we have to use workarounds to maintain root and cwm.

Its the same with every other ramdisk i tried on the stock kernel

-led appears

-phone vibrates

-i press both volume keys numerous times

-BUT the phone boots into homescreen, NOT the recovery and functions normally. :mad:

Here is the pure stock kernel I compiled from .569 source using your tutorial. I'm using it since 2 days, works fine on my XZL-C6502

C6502 Stock kernel IMG

I'm a little desperate and off topic :p But can you please help us ZL users getting a kernel working with cwm on .569 fw for now ?? :D
[Sony Cross-Device General] DooMLoRD:
start device

connect via ADB

execute following commands

adb shell getevent

(press CTRL+C immediatelly after u execute the above command)

look for the event corresponding to gpio_keys

that is the input event node to use :)

fix that in the bootrec file in /sbin (along with the correct event node)

and you should be good to go
[Sony Cross-Device General] iamsuperuser:
Still same problem :crying:

I did what you said and got this

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\iamsuperuser>cd C:\Program Files (x86)\Android\android-sdk\platform-tools

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
shell@C6502:/ $ getevent
getevent
add device 1: /dev/input/event10
name: "system_als"
add device 2: /dev/input/event0
name: "pmic8xxx_pwrkey"
add device 3: /dev/input/event8
name: "pm8921_chg_unplug_key"
add device 4: /dev/input/event6
name: "apq8064-tabla-snd-card Headset Jack"
add device 5: /dev/input/event5
name: "apq8064-tabla-snd-card Button Jack"
[COLOR="Red"]add device 6: /dev/input/event7
name: "gpio-keys"
could not get driver version for /dev/input/mouse0, Not a typewriter[/COLOR]
add device 7: /dev/input/event9
name: "mhl-rcp"
add device 8: /dev/input/event4
name: "apds9702"
add device 9: /dev/input/event3
name: "bma250"
add device 10: /dev/input/event2
name: "compass"
add device 11: /dev/input/event1
name: "clearpad"
could not get driver version for /dev/input/mice, Not a typewriter
/dev/input/event4: 0004 0003 000000ff
/dev/input/event4: 0000 0000 00000000
/dev/input/event3: 0003 0001 fffffff7
/dev/input/event3: 0003 0002 ffffff00
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0003 0000 0000000e
/dev/input/event3: 0003 0001 fffffff6
/dev/input/event3: 0003 0002 ffffff02
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0003 0000 00000011
/dev/input/event3: 0003 0002 ffffff01
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0003 0000 0000000f
/dev/input/event3: 0003 0002 ffffff02
/dev/input/event3: 0000 0000 00000000
^C
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
shell@C6502:/ $ adb reboot recovery
adb reboot recovery
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|shell@C6502:/ $ adb reboot recovery
adb reboot recovery
error: device not found
1|shell@C6502:/ $ exit
exit

C:\Program Files (x86)\Android\android-sdk\platform-tools>^A^A

So the event node for gpio-keys is event7

As I am using your ramdisk from xperia z doomkernelv20 ,

I changed the '8' in the below lines to '7' in bootrec-device file

export BOOTREC_EVENT_NODE="/dev/input/event8[COLOR="Red"](to 7)[/COLOR] c 13 72"
export BOOTREC_EVENT="/dev/input/event8[COLOR="Red"](to 7)[/COLOR]"

Then I repacked the ramdisk with my zImage and flashed it onto my XZL and the result , the phone does NOT boot into recovery.

When I flashed CM10.2 kernel for XZL the phone boots into recovery perfectly though the event node in its bootrec-device file was '8'

So may be the event node is not the problem

I also tried changing event node in the ramdisk of THIS kernel and repacked its ramdisk with my zImage, Still the phone does not boot into recovery.

Where should I look next ??
[Sony Cross-Device General] DooMLoRD:
Event8 was at c 13 72

Event7 should be c 13 71
[Sony Cross-Device General] iamsuperuser:
Finally IT WORKS !!!!!!!!!!!!!

Yaaaaaaaaaaaaaaaaaaaaaaaaaaaaaayyyyyyyyyyyyyyyyyyyy!!!!!! :victory::victory::victory:

Cannot thank you enough DooMLoRD:good::good::good::laugh::laugh:
[Sony Cross-Device General] Gustavo RD78:
I'm trying to compile a kernel

like applied the fix to the toolchain?