[RECOVERY] TWRP 2.4.3 (downloads + DIY How-to) [for CM10/AOKP/PAC-man] - Sony Ericsson Xperia Neo, Pro

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.

Related

Custom Kernel Development: Devs only

---[ UPDATED: July 26, 2011 16:30 GMT ]---
\\--[ ANNOUNCEMENT ]--//
[Added] FreeKernel-mod350-Th#28 by ThJap
//--[ ANNOUNCEMENT ]--\\
I have started this thread based on zdzihu's suggestion...
This thread is intended for Developers ONLY...
A method of booting custom kernels (using kexec) has been developed. Thanks Bin4ry, zdzihu, jerpelea, MrHassell, blagus, and all other devs who are working hard to make this stable. (i am sorry if i missed any names)
hope the devs can use this thread to discuss on custom kernel dev....
please keep this thread clean for the devs to discuss the kernel development aspects...
for general discussions please use the following thread:
http://forum.xda-developers.com/showthread.php?t=1018391
i will also keep updating this regularly with the information like relevant posts; features, limitations & links to custom kernels currently available...
*** [IMP]: before flashing custom update.zips read this: how to find the version/type of recovery on ur current ROM ***
>>> How-To for testing custom kernel <<<
>>> How to build a Linux kernel and flash it to the phone {from SE Dev Blog} <<<
Custom kernel sources released:
Custom Kernel Sources for 2.0.A.0.504 by zdzihu
FreeXperia Project | Custom Kernel Sources for FreeXperia Kernel
FreeKernel-mod350-source by tkymgr
FreeKernel-mod352-source by tkymgr
zKernel-source by zdzihu
DooMKernel-source by DooMLoRD
Current list of custom kernels:
FreeKernel-alpha1 by zdzihu
FreeKernel-alpha1-in-call volume fix by zdzihu
FreeXperia Kernel-001 by jerpelea (from CM7.0 RC4 v014 k001 PREVIEW)
FreeXperia Kernel-002 by jerpelea (from CM7.0.0 J015 k002)
TripNKernel Modified FreeKernel-03 by TripNRaVeR
FreeXperia Kernel-003 / beta3 by Bin4ry (flashable update.zip via recovery)
FreeXperia Kernel beta4 by Bin4ry
FreeXperia Kernel-005 / beta5 by jerpelea (from CM7.0.0 J016 k005)
FreeXperia Kernel-006 / beta6 by jerpelea (from CM7.0.0 J016a k006)
FreeXperia Kernel-007 / beta7 by jerpelea (from CM7.0.3 J019 k007)
FreeXperia Kernel-008 / beta8 by jerpelea (from CM7.0.3 J020 k008)
FreeXperia Kernel-009 / beta9 by jerpelea (from CM7.0.3 J020a k009)
FreeXperia Kernel-010 / beta10 by jerpelea (from CM7.0.3 J020b k010)
FreeXperia Kernel-010 / beta10 [No UV] by jerpelea (from CM7.0.3 J020c K010)
FreeXperia Kernel-011 / beta11 by jerpelea (from CM7.0.3 FINAL J021 K011 & CM7.1.0 J001 K011)
FreeXperia Kernel-012 / beta12 by jerpelea
FreeKernel-docomo21.c-spec-v346 by tkymgr
FreeKernel-docomo2x.c-spec-v347 by tkymgr
FreeKernel-docomo2x.c-spec-v349 by tkymgr
FreeKernel-docomo2x.c-spec-v350 by tkymgr
FreeKernel-mod350-fix1 by tkymgr [ only boot.img & wifi module ]
FreeKernel-mod351 by tkymgr
FreeKernel-mod352 by tkymgr
zKernel-22062011 by zdzihu
zKernel-23062011-alt by zdzihu
FreeXperia Kernel-013 / beta13 by jerpelea (from CM7.1.0 RC1 J005 k013)
FreeKernel-mod352 #2 by tkymgr
FreeKernel-mod350-Th#11 by ThJap
zKernel-05072011 by zdzihu
FreeKernel-mod360 by tkymgr
zKernel-14072011 by zdzihu
zKernel-15072011 beta by zdzihu
DooMKernel v01 by DooMLoRD
DooMKernel v02 by DooMLoRD
zKernel-20072011 by zdzihu
zKernel-20072011_failsafe by zdzihu
FreeKernel-mod350-Th#25 by ThJap
FreeKernel-mod362 by tkymgr
DooMKernel v03 by DooMLoRD
FreeKernel-mod363 by tkymgr
FreeKernel-mod350-Th#28 by ThJap
Additional Info:
the following files are required in the /system/kernel/ folder:
splboot.ko (some devs move this file to /system/lib/modules/splboot.ko)
miniloader
boot.img (this is the actual custom kernel)
for booting the OS using custom kernel some modifications are required to the /system/bin/chargemon file
also some modified/updated modules (e.g. wifi.ko) are provided for compatibility with the custom kernel
Bootloader Bypass files:
There seems to be some issues face by some users, where in using a different version of miniloader helped them sort out the issues. So I will provide all those versions.
Flashable update.zip via recovery, contains miniloader & splboot.ko:
bootloader_bypass_files_v1.zip [slightly older miniloader] {came with older FreeXperiaKernels}
bootloader_bypass_files_v2.zip [older miniloader] (testing only) {came with FreeKernel by zdzihu}
bootloader_bypass_files_v3.zip [older miniloader] (testing only) {came with Flashtool v0.2.9.1}
bootloader_bypass_files_v4.zip [newest miniloader] {comes with newer FreeXperiaKernels (from CM7 J022 K011 onwards)} (recommended)
[IMP] for v4 miniloader: u need to be on the baseband from the baseband package provided in CM7 J022 for the v4 miniloader to work properly... even if u already have baseband 2.0.52 please reflash using the baseband package provided in CM7 J022... even if u are on a different ROM u will need to use the baseband from the above package to get custom kernel to work properly
FreeKernel-alpha1 by zdzihu
Linux Kernel Version:
2.6.29
Kernel features:
removed 32 fps cap
implemented netfilter (Droid wall, native USB/wifi tethering etc.)
undervolted to 0.950mV to save battery
don't remember what else I did, I bet something nasty
super ugly boot logo!
Requirements:
baseband .52 + the relevant kernel
clean 2.1 ROM, compatibile with .52 baseband (e.g. .504)
working xRecovery
Known Issues:
Tested On:
Stock SE Firmware 2.0.A.0.504
Link to download boot.img (flashable via recovery):
http://www.mediafire.com/?1gesziiz4pbvcr6
MD5 hash of boot.img:
Code:
d8e98b647641bc55270ccb73729f007f
Additional file(s) provided with kernel:
wifi.ko module
FreeKernel-alpha1 in-call volume fix by zdzihu
Linux Kernel Version:
2.6.29
Kernel features:
possible in-call volume fix
removed 32 fps cap
implemented netfilter (Droid wall, native USB/wifi tethering etc.)
undervolted to 0.950mV to save battery
don't remember what else I did, I bet something nasty
super ugly boot logo!
Requirements:
baseband .52 + the relevant kernel
clean 2.1 ROM, compatibile with .52 baseband (e.g. .504)
working xRecovery
Known Issues:
Tested On:
Stock SE Firmware 2.0.A.0.504
Link to download boot.img (flashable via recovery):
http://www.mediafire.com/?jx4lbhfioquw4sk
MD5 hash of boot.img:
Code:
5de24423ad2ccce80bbd5ac9aae3079a
Additional file(s) provided with kernel:
wifi.ko module
FreeXperia Kernel-001 by jerpelea (from CM7.0 RC4 v014 k001 PREVIEW)
Linux Kernel Version:
2.6.29
Kernel features:
tun/tap
dmmod
dmcrypt
1.1 ghz frequency
undervolt
ondemand cpu scaller (default)
camera debug messages
netfilter
Requirements:
baseband 2.0.52
Known Issues:
wifi doesnt work. enabling/activating wifi causes WLOD (white LED of Death) and then reboot
Tested On:
Cyanogen CM7.0 RC4 v014 k001 PREVIEW
Wolfbreaks CM6.1.3 v53 with Baseband Patch for 4x-52
TripNMiUI
FreeX10 beta4 hotfix1
Link to download boot.img (flashable via recovery):
http://www.mediafire.com/?8uzo3nudxh89x67
MD5 hash of boot.img:
Code:
fcacdb0189ca25b7c834a4a855f1776e
Additional file(s) provided with kernel:
kernel part of custom ROM
Bootloader bypass file(s) required to test custom kernel:
There seems to be some issues face by some users, where in using an older version of miniloader helped them sort out the issues. So I will provide here both versions.
Flashable update.zip via recovery, contains miniloader & splboot.ko:
bootloader_bypass_files_v1.zip [newest miniloader] (recommended)
bootloader_bypass_files_v2.zip [older miniloader] (testing only)
One question for bypass-method developers: is it necessary to have stock SE's ROM for better chances of succeeding in porting splboot/miniloader to X8?
2.1update1 - base anyone can restore with SEUS, demonstrated work from this point, with the FreeX10, FreeXperia, Wolfbreak, rendeiro2005 and others without many problems. It might be a case of, which has the least issues, what are they and how do we eliminate them.
The most common baseband with development is 52. FreeXperia - CM7 GingerBread - entirely developed for 52 - there are two groups.
Original Baseband series: 48-49-50-51-52 (52 = last of first generation)
Current Baseband series: 53-54-55-56-57-58 (59 - not released)
Baseband is a multiplexer. The core C files are - vendor/qcom-proprietary-qsd8k/data/qmi/qmuxd/../src/qmi_qmux.c and is compiled for ARM with* vendor/qcom-proprietary-qsd8k/data/qmi/qmuxd/../platform/qmi_platform_qmux_io.c and the core interface to the Linux kernel - vendor/qcom-proprietary-qsd8k/data/qmi/qmuxd/../platform/linux_qmi_qmux_if_server.c requires several SO - (ELF binaries) - be present, compiled and available to the kernel and the linker - /system/bin/linker
liblog.so
libdiag.so
libc.so
libstdc++.so
libm.so
Everything working - /data/radio/qmux_connect_socket - will bind to an address path and make possible, one radio with one input signal to many data-output-lines and many input lines. Herein the core networking is established, with WiFi and Bluetooth become linked, with the famous exploits for NULL pointer dereference vulnerability which exist in Linux kernels < .30 - Which is no coincidence, why many Kernels are below this release version.
sent from neptune
Achotjan_FreeX10 by achotjan
based on FreeKernel-alpha1 by zdzihu
---[ REMOVED ON DEVS REQUEST ]---
FreeXperia Kernel-002 by jerpelea (from CM7.0.0 J015 k002)
Linux Kernel Version:
2.6.29
Kernel features:
possible in-call volume fix
gps fix
lcd backlight resume fix
tun/tap
dmmod
dmcrypt
1.1 ghz frequency
undervolt
ondemand cpu scaller (default)
camera debug messages
netfilter
Requirements:
baseband 2.0.52
Known Issues:
wifi doesnt work
Tested On:
Cyanogen CM7.0.0 J015 k002
Wolfbreaks CM6.1.3 v53 with Baseband Patch for 4x-52
TripNMiUI FINAL 1.0.3
FreeX10 beta4 hotfix1
MiXeD MIUI 002 TMR mod
Link to download boot.img (flashable via recovery):
http://www.mediafire.com/?5egorvjv1lppno2
MD5 hash of boot.img:
Code:
25cb217886b88ba1085dfd164c8a3e8d
Additional file(s) provided with kernel:
kernel part of custom ROM
Bootloader bypass file(s) required to test custom kernel:
There seems to be some issues face by some users, where in using an older version of miniloader helped them sort out the issues. So I will provide here both versions.
Flashable update.zip via recovery, contains miniloader & splboot.ko:
bootloader_bypass_files_v1.zip [newest miniloader] (recommended)
bootloader_bypass_files_v2.zip [older miniloader] (testing only)
TripNKernel Modified FreeKernel-03
based on zdzihu's FreeKernel
Linux Kernel Version:
2.6.29
Kernel features:
removed 32 fps cap
Requirements:
baseband 2.0.49/2.0.52
Known Issues:
GPS (not confirmed)
apps2sd not working
Tested On:
TripNMiUI FINAL 1.0.3
Wolfbreaks CM6.1.3 with Baseband Patch for 4x-52
FreeX10 beta4 hotfix1
Achotjan_Froyo_2.2.1
scamble_v01.3 CM6.1.3
Link to download boot.img (flashable via recovery):
http://www.mediafire.com/?4mscmhfbr99hdt9
MD5 hash of boot.img:
Code:
aa40c889f482731eb4324e0c2a2b5336
Additional file(s) provided with kernel:
kernel part of custom ROM
Bootloader bypass file(s) required to test custom kernel:
There seems to be some issues face by some users, where in using an older version of miniloader helped them sort out the issues. So I will provide here both versions.
Flashable update.zip via recovery, contains miniloader & splboot.ko:
bootloader_bypass_files_v1.zip [newest miniloader] (recommended)
bootloader_bypass_files_v2.zip [older miniloader] (testing only)
how can we flash the .img file?
AN7 OverClocker said:
how can we flash the .img file?
Click to expand...
Click to collapse
A little more info please, wich kernel are you talking about? Tripnraver's, zdzihu's..?
If it's tripnraver's kernel you try to flash, you should just flash the zip-package you downloaded
i am talking about FreeXperia Kernel-002 by j.
This kernel is only available on .img file
You should place all your kernel files in /system/kernel/ and you must make some changes to chargemon (/system/bin/chargemon). I have no idea what changes you should exactly make..
hmmm...
i will re-upload the boot.img zips as update.zips flashable via recovery...
also for general discussions please use the following thread: http://forum.xda-developers.com/showthread.php?t=1018391
in the above thread i have already posted the changes which need to be made to the /system/bin/chargemon file to boot using custom kernels
system/bin/chargemon
system/bin/charger
system/lib/modules/wifi.ko
and Kernel folder needs to be copied out from ROMs to get custom Kernel.
Wolfbreak said:
system/bin/chargemon
system/bin/charger
system/lib/modules/wifi.ko
and Kernel folder needs to be copied out from ROMs to get custom Kernel.
Click to expand...
Click to collapse
i would not recommend copying the file /system/bin/chargemon as is (because of the different recoveries available & variations that each dev/each version of flashtool introduces) rather only search for the custom kernel booting part and add that to the chargemon file if it isnt there already...
also no need to copy the whole /system/kernel/ folder... u just need the boot.img for that specific custom kernel... (though here i assume that u already have miniloader & splboot.ko in /system/kernel/)
and yes individual rewritten modules (like wifi.ko) have to be copied too... it would be great if the devs can post update.zips which contain the hotfixes/addons (including custom kernel, modified modules, etc) so that the kernel and related files can be used on other roms too, instead of downloading the whole rom...
i would like to confirm that FreeXperia Kernel-002 by jerpelea (from CM7.0.0 J015 k002) is working well on Achotjan's V010
Has anyone tested one of the available kernels on FreeX10 Beta 4 ?
[Q] Is it also possible for x10?
Hi, I just found this:
http://forum.xda-developers.com/showthread.php?t=889503
So i wanted to ask wether it is possible to implement it in the custom Kernels of X10.
fknpwned said:
Has anyone tested one of the available kernels on FreeX10 Beta 4 ?
Click to expand...
Click to collapse
+1
sent from my Z orignal and modded 2.2 powered c64

[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.
screenshots?

[ROM] Huawei S7-10X Codeaurora 4.1.1

With the exception of a modified hardware/qcom/display for legacy support this is a straight compile of Codeaurora's 4.1.1 (M76XXUSNEKNLYA2515)
http://threader.zapto.org/experimental/s7/codeaurora-4.1/102113/boot.img
http://threader.zapto.org/experimental/s7/codeaurora-4.1/102113/system.img.bz2
Unpack system.img.bz2
Flash with fastboot.
fastboot erase cache
fastboot erase userdata
fastboot flash boot boot.img
fastboot flash system.img
Not working:
Phone.
Bluetooth.
Sensors.
Wifi.
Working:
display
Kernel source:
https://github.com/threader/Huawei_S7_kernel_2.6.35
Hardware/qcom/display & devices/huawei/s7
http://threader.zapto.org/experimental/s7/codeaurora-4.1/sources-buildprefs/
Android sources:
https://github.com/threader/
Credits
Asturel, dzo. Thanks!
Boot image will boot asturels CM10 http://goo.im/devs/asturel
A boot image to boot asturels cm10.1 on 10x http://threader.zapto.org/experimental/s7/cm10.1/boot.img
Hi,
Went trough my old disks and uploaded everything i could find to https://mega.co.nz/#F!3wAQxDDL!2MgX7NmPBUIOVYP3zLYElw
Upper Folders:
* Original Firmware (Norway - Sweden - Brazil)
Norway = 103 Sweden = ? Brazil = 101-2 || Brazil boot image can be used with Norway rom, a 101 will loose its camera when presented with the wrong version kernel
Seemingly ancient Huawei update app, for updating 2.1 to 2.2. ( In Firmware Folder )
* Original Froyo and Emotion Kernel sources
Seemingly lost from Huawei's site. Could not find the 2.6.32 kernel last i checked let alone 2.6.28
* Broadcom bcm4329 sources
Original upload by Huawei, suggest downloading all and comparing. Remember there being a problem with either of the files
Dev folder:
* Device-huawei-s7 / Hardware-qcom-display-s7 ( Codeurora 4.1.x / CM 10 (?) / JB)
To be compiled against a "M76XXUSNEKNLYA2515" Codeurora 4.1.x / CM 10 (?) / JB)
* Kernels
Latest 2.6.32.61 from me, suggest using the original config instead of the mine.
Earlier release of 2.6.35.14 - Should be stable but suggest github - https://github.com/threader/Huawei_S7_kernel_2.6.35 - again use your config!
What i think is the original Huawei S7 kernel just fixed to compile.
Codeaurora msm-2.6.32 - which i suggest grabbing this amongst others, if you want to start from scratch with kernel-2.6.32-FROYO.tar.bz2
* Broadcom - bcm4329
Unknown status, suggest a thorough look and compare against original Huawei - bcm4329 release.
* Codeaurora 4.1.x ( 4.1.1 ) M76XXUSNEKNLYA2515
Latest two experimental builds i could find
Codeurora-4.1.x-s7-nov-6-2013 was actually the last 4.1.1 date i found in my build directory, this may be wrong, but i uploaded what sees to be the last build i did really, but it might require 21-10-2013 boot.img to work.

[Kernel][XP][CM12] Miracle Kernel [V2]

The kernel is built from Xperia STE GitHub source.
For now, it only includes some changes in the kernel config.
Features:
- Ramdisk from latest CM12 build by percy_g2(with TWRP Recovery)
- Full features in xperiap_defconfig
- Some implements in standard Linux kernel options(mainly for development, will also be used in my later projects)
- Supports more types of ramdisk image
- More...
Download page: http://www.ifxor.com/Releases/Miracle_Kernel.php
Sources are here: https://github.com/XperiaSTE/android_kernel_sony_u8500
XDA:DevDB Information
Miracle Kernel for Xperia P, Kernel for the Sony Xperia P
Contributors
zhy0919, hubdroid.com, Xperia STE, percy_g2
Source Code: https://github.com/XperiaSTE/android_kernel_sony_u8500
Kernel Special Features:
Version Information
Status: Nightly
Created 2015-01-30
Last Updated 2015-01-30
were you able to resolve wifi sleep bug
Pleasant to see more people are working on SXP!) Thank you!
Which one to download?
@zhy0919
There are 4 links on http://www.ifxor.com/Releases/Miracle_Kernel.php
Which one is the latest?

Project Treble for Xperia XZs [G8321/2] [Pie 9.0] [no repartitioning]

Project Treble for Xperia XZs
With this project, you can run (almost) any Generic System Image(GSI) on your Xperia XZs. This means you can test LineageOS, Havoc, Pixel Experience...
No repartitioning necessary! This method is re-using the oem partition.
What is Project Treble?
Understanding Project Treble and Android updates
Talkin’ Treble: How Android engineers are winning the war on fragmentation
What are GSIs?
Android Source: Generic System Image (GSI)
Downloads:
ROM: Download the latest aosp_f8331_*-TREBLE-NIGHTLY.zip from sx.ix5.org/files/builds/keyaki/aosp/
TWRP: Download twrp-kagura-oem-to-vendor.img Wait until a treble-compatible recovery is made
How to install:
Back up your stuff
Wipe data and caches
Install the zip via TWRP (or unzip and install just the /boot and /vendor images via fastboot)
Install any GSI via "fastboot flash system your-gsi-image.img"
To use Magisk: Flash twrp-kagura-oem-to-vendor.img as recovery. Reboot into recovery and install Magisk like you usually would. If you want to go back to another ROM, you need to re-flash your old TWRP recovery as well.
Bugs: See post #2
DO NOT POST HERE FOR FLASHING HELP OR YOU WILL BE REPORTED. Read everything before posting.​
If you have questions, ask them in this thread: AOSP 9.0 Pie builds for F8331/F8332​
List of GSIs: phhusson's treble Generic System Image
Important: You need an A-Only, ARM64 GSI!
GSIs based on phhusson's work offer the best compatibility.
Magisk: For Magisk to work, you need to tweak your TWRP installation, since it doesn't know that we have shuffled /vendor to the oem partition. You need to change /oem to /vendor in TWRP's fstab file.
See above for a tweaked TWRP.
If you want to go back to any other AOSP-based ROM that is not a GSI, simply re-flash the regular oem image and install like you usually would.
For developers:
This method is repurposing the oem partition to hold /vendor and odm(blobs). There's 400mb of space on that partition and we are only using ~260mb for blobs, while vendor is only about 20-30mb.
Re-partitioning can be quite dangerous if you do not know what you are doing. This method should be safe for everyone.
Sources are up now.
local_manifests
kernel (with patches)
sony's repo_update
ix5_repo_update: run ix5_repo_update.sh and then treble_repo_update.sh
You need to tweak the following:
Kernel dtsi to disable "odm" and load /vendor from "bootdevice/by-name/oem"
PlatformConfig on tone
device-sony-common:
adreno-symlinks branch
symlink from /vendor/odm/lib to /vendor/lib instead of from /odm/lib: Extra symlinks for build.prop and radio (aosp already symlinks /odm to /vendor/odm, but it omits build.prop and our radio folder)
Misc fixes
PRODUCT_FULL_TREBLE_OVERRIDE needs to be "true"
device-sony-tone: treble fixes:
Mount oem as /vendor in fstab
"TARGET_COPY_OUT_VENDOR := vendor" needs to be set
Set VNDK versions, and override properties that get set because the build system is made to believe our XZ shipped with Oreo
device/sony/odm with odm files
Unpack the oem blobs under device/sony/odm/odm and follow the README in device/sony/odm/README.
We need to put the odm files("blobs") somewhere. They get symlinked from /vendor/odm to /odm; both locations need to be accessible.
sepolicy: Use the broad-updates branch (it's kinda hack-ish now because /odm/pm-service is using /dev/binder, which messes with sepolicy). Sepolicy is on permissive for these builds because of that issue.
Tested:
AOSP Extended (calling works, bluetooth may crash)
Havoc (no calling, bluetooth may crash)
Camera should work everywhere
Bugs are the same as the regular AOSP builds, plus some more if the GSI is not built well or doesn't have tweaks for Sony devices.
Happy holidays, I hope you have fun with this!​
XDA:DevDB Information
Project Treble for Xperia XZ F8331/2, ROM for the Sony Xperia XZ
Contributors
local__hero
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: .184 or later stock firmware
Based On: AOSP
Version Information
Status: Nightly
Created 2018-12-30
Last Updated 2018-12-30
XDA:DevDB Information
Project Treble for Xperia XZs [Pie 9.0], ROM for the Sony Xperia XZs
Contributors
local__hero
Source Code: https://git.ix5.org/felix/local-manifests-ix5
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Stock Oreo firmware, best .184
Based On: AOSP
Version Information
Status: Nightly
Created 2019-01-28
Last Updated 2019-06-10
Reserved
Reserved
Gb321 single card installation error
Man, can you explain the installation better? I don't understand how it installs on the vendor, boot and twrp (I'm Brazilian, I'm sorry for my bad English)
There's three vendors and none of them is image how can I flash them
Thread closed at op's request.
Thank you for your contributions :highfive:
strongst
Forum Moderator

Categories

Resources