Related
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.
Thanks, though in keeping with GPL you need to post your buildable source. In addition so that others can continue and support what you have done, since you obviously have no desire to do so, that is essential. Not very helpful to the community to do a "one-off" venture.
Would you mind publishing your device configuration files for this build so that others can pick it up & maintain it?
jerdog said:
Thanks, though in keeping with GPL you need to post your buildable source. In addition so that others can continue and support what you have done, since you obviously have no desire to do so, that is essential. Not very helpful to the community to do a "one-off" venture.
Click to expand...
Click to collapse
the source is present on http://github.com/KangXperiaProject
also check the latest merged commits on http://smartdev.com.pl:8080
building with KXP_INCLUDE_TWRP := true will give you same product as I have provided here.
the kernel is built off already present sources on KXP github, so there is no GPL violation
and yes I will update the flags on BoardConfigs on all the devices after I make KXP Milestone1-R2 releases, I will sync all local changes.
but again to reiterate, to duplicate the kernel I have posted, stuff is already present on github to do so.
Dees_Troy said:
Would you mind publishing your device configuration files for this build so that others can pick it up & maintain it?
Click to expand...
Click to collapse
just give me a day or two please
and I'll PM you when it's done. (I will update all 15 Xperia devices with the flags needed )
Could anyone post a flashable zip please? don't have a PC right now
Sent from my Xperia T using xda premium
championswimmer said:
the source is present on http://github.com/KangXperiaProject
also check the latest merged commits on http://smartdev.com.pl:8080
building with KXP_INCLUDE_TWRP := true will give you same product as I have provided here.
the kernel is built off already present sources on KXP github, so there is no GPL violation
and yes I will update the flags on BoardConfigs on all the devices after I make KXP Milestone1-R2 releases, I will sync all local changes.
but again to reiterate, to duplicate the kernel I have posted, stuff is already present on github to do so.
Click to expand...
Click to collapse
Update your first post with links to the sources, along with any specific flags. And, to be GPL compliant, you do need to provide all aspects of the build in order that anyone could come in and build from your sources. The best way to do that is to link to the exact source for the specific project (not just the overall github) and to provide the instructions and flags, etc. used in building that specific project in like the README like linux and other GPL-compliant projects do
Although getting GPL compliant is important and totally supportable, I'd still like to leave a big, fat, spelled out THANK YOU for tinkering with TWRP on the xperias. Big thing, big win :thumbup:
Nice thread, well done champ.
If any users are interested in my TWRP build/changes you can see my fork here: https://github.com/cosmicdan/Team-Win-Recovery-Project/commits/jb-wip
Here are the flags I use for Xperia Play BTW:
Code:
# TWRP
DEVICE_RESOLUTION := 480x854
TARGET_RECOVERY_PIXEL_FORMAT := "RGB_565"
TW_FLASH_FROM_STORAGE := true
pictures please? i think this is the recovery have looking for
xdarkmario said:
pictures please? i think this is the recovery have looking for
Click to expand...
Click to collapse
FFS click
Sent from my R800i using xda premium
lol, totally was my plan as well.
olokos said:
FFS click
Sent from my R800i using xda premium
Click to expand...
Click to collapse
lol thanks, that was the recovery i was looking for, but it is now compatible with ICS so i had to go back. looks goo though and easy
xdarkmario said:
lol thanks, that was the recovery i was looking for, but it is now compatible with ICS so i had to go back. looks goo though and easy
Click to expand...
Click to collapse
Not stock ICS no, maybe wedgess will one day. But Turbo Kernel works on CM9/AOKP.
Sent from Xperia Play (R800a) with Tapatalk
I have done on my xperia tx Thank you all the same
Lets hope that will see it inserted in stock kernels too alongside with the cwm recovery . It would be awesome to have 2 recoveries in one kernel.
how to enter this recovery? xperia mini-smultron
shadik555 said:
how to enter this recovery? xperia mini-smultron
Click to expand...
Click to collapse
vol down when led is pink
championswimmer said:
vol down when led is pink
Click to expand...
Click to collapse
it dont work
i tried
AOKP r2 and this kernel,before i installed AOKP,it opened TWRP,but after i installed AOKP,wont open twrp
EDIT:solved-recovery manager,boot in recovery
Thanks! I will test it soon as i get home!
Dose it supports usb otg?
Sent from my Xperia S using xda premium
THIS IS A THREAD FOR TENDERLOIN ROM DEVELOPERS TO DISCUSS ISSUES REGARDING BUILDING, CODING, CREATING, DEBUGGING AND STABILIZING A CM10.1/JELLYBEAN 4.2.x ROM FOR THE HP TOUCHPAD. IF YOU AREN'T WORKING ON THIS, MOVE ALONG... NOTHING TO SEE HERE
Seriously, folks. This is an information exchange thread for developers. You're welcome to watch and listen, but PLEASE, please, don't ask user questions here, don't ask for ETA's, don't give huzzahs, and "I want this" stuff. Post that in the relevant ROM threads, the General or the Q&A. Thanks.
Thanks for starting this thread, shumash. Here's what I have so far:
I have built a 10.1 rom for the hp tenderloin. I am not posting the actual rom because it has a way to go. It is far from a daily driver. Instead, I am posting a link so other developers can build their own roms and maybe we can get a fully working cm10.1 rom.
My device tree is on github:
https://github.com/drmarble/android_device_hp_tenderloin/tree/10.1-ugly
On the 10.1-ugly branch is a semi working device tree for hp tenderloin cm10.1.
Many more details for building are included in the README file.
If you aren't set up to build cyanogenmod roms for the tenderloin, this won't be any use to you. It truely is developer only.
It is a work in progress. Very, very much a WIP.
Camera doesn't work.
Bluetooth doesn't work.
Thanks to the efforts of James Sullins the SDCARD mounts and sound works from the speakers.
This is heavily reliant on the work of Arne Coucheron.
His invaluable patches include:
http://review.cyanogenmod.org/#/c/34375
http://review.cyanogenmod.org/#/c/34377/
http://review.cyanogenmod.org/#/c/34374/
and his highly useful google doc:
https://docs.google.com/document/d/1cGKMXx112gGls9a6ziDTpPgObnU6ZExPy5tByqqIyI4/edit?pli=1
Without his work, we would still have no display.
Of course, everything depends upon the work of the cyanogenmod hp developers Dalingren, FatTire, jcsullins, eyeballer, dorregaray and all the rest.
All my patches are in one big, ugly patch. I included various gerrit patches that my patch is dependent on. I'll work on neatening it up so the commits are separate and readable. I just wanted to get this out there so others could work on it and we can get cm10.1 working.
I think that this is everything.
Please, lets have lots of folks working on this. We can't use gerrit because this isn't cyanogenmod. Steve Kondik feels that since we are dependent upon the legacy qcom repositories it isn't really cm. This is just a kang. We can post patches here, or link to our githubs. Or use pull requests. I also started a thread on Rootzwiki. IRC on #cyanogenmod-touchpad on Freenode is a good place to chat. Jcsullins has already contributed two essential patches that got us SDCARD mounting and sound via irc.
We can get this done together.
drmarble said:
Thanks for starting this thread, shumash. Here's what I have so far:
I have built a 10.1 rom for the hp tenderloin. I am not posting the actual rom because it has a way to go. It is far from a daily driver. Instead, I am posting a link so other developers can build their own roms and maybe we can get a fully working cm10.1 rom.
--SNIP--
We can get this done together.
Click to expand...
Click to collapse
Thanks for that informative post. What are you using for a default manifest and kernel source?
most of the information needed to build is in the README file at my github. I use the regular cm manifest and build tools. The local manifest I use is:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="drmarble/android_device_hp_tenderloin" path="device/hp/tenderloin" remote="github" revision="10.1-ugly" />
<project name="CyanogenMod/hp-kernel-tenderloin" path="kernel/hp/tenderloin" remote="github" revision="ics" />
<project name="CyanogenMod/android_hardware_atheros_wlan" path="hardware/atheros/wlan" remote="github" revision="jellybean" />
<project name="arco/android_hardware_qcom_display-legacy" path="hardware/qcom/display-legacy" remote="github" revision="cm-10.1" />
<project name="arco/android_hardware_qcom_media-legacy" path="hardware/qcom/media-legacy" remote="github" revision="cm-10.1" />
</manifest>
I just use the regular cm kernel. The addional repos work together with a couple of flags in Boardconfig.mk. Those are set in my "big_ugly_patch" which should have been broken up into several different ones. Really, you just have to set up a cm build environment, put in my local_manifest.xml, repo sync, apply the various commits listed in the README file and "brunch tenderloin".
To those who want a downloadable ROM. There isn't one yet. I don't think this is ready for anybody but home brewers. jcsullins' and others cm10 builds are much more stable and useable. This is just more fun for build-it-yourself-ers because it is newer and shinier. It's not a better android experience yet.
It may be worth mentioning, for clarity, to make sure you have included vendor/hp/tenderloin.
<project name="TheMuppets/proprietary_vendor_hp" path="vendor/hp/tenderloin" remote="github" revision="jellybean" />
I've been working on including the latest Adreno drivers but have found they are dependent on the CAF varriant, and we are stuck using legacy. Which is exactly why Steve Kondik said "I do not want to create official builds for any device that needs to use this. If your device can't support the latest driver for whatever reason, it's going to be janky and slow and probably worse than stock on 10.1."
I am trying to take some inspiration from the HTC Sensation, aka Pyramid, because that device is also msm8660 and they are utilizing the legacy display variant in 4.2.2 as well - without any complaints about video playback.
You can also use unzip-files.sh or extract-files.sh from device/hp/tenderloin to get the proprietary files. You just have to use jcsullins' latest cm10 zip file or installed rom (20130304etc.zip). These may be even more current than TheMuppets. They haven't been updated for 6 months. I know that the proprietary-files.txt file has been modified since then. I think that he updated some of the proprietary files so that sound would work. He also added some adreno libs, though we should look into the latest 4.2.2 adreno libs.
I'm trying out the Evervolv manifest, which is mostly AOSP. If it works, we may be able to get a mashup of the CM and AOSP source trees that gives us some options. So far, however, I've had to comment out the audio.primary.tenderloin package and the Settings package overlay in the tenderloin device source to get it to continue the compilation. I'll report back tomorrow.
drmarble said:
You can also use unzip-files.sh or extract-files.sh from device/hp/tenderloin to get the proprietary files. You just have to use jcsullins' latest cm10 zip file or installed rom (20130304etc.zip). These may be even more current than TheMuppets. They haven't been updated for 6 months. I know that the proprietary-files.txt file has been modified since then. I think that he updated some of the proprietary files so that sound would work. He also added some adreno libs, though we should look into the latest 4.2.2 adreno libs.
Click to expand...
Click to collapse
Are you getting any video playback with your builds using extract-flies.sh? All I ever seem to get is an infinite "loading" screen. I once used CM9 Adreno drivers in building CM10, with the same "loading" effect.
shumash said:
I'm trying out the Evervolv manifest, which is mostly AOSP. If it works, we may be able to get a mashup of the CM and AOSP source trees that gives us some options. So far, however, I've had to comment out the audio.primary.tenderloin package and the Settings package overlay in the tenderloin device source to get it to continue the compilation. I'll report back tomorrow.
Click to expand...
Click to collapse
Ok, after much thrashing, I"ve got everything compiled and waiting in the OUT folder, it stops with this:
Code:
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
out/target/product/tenderloin/obj/PACKAGING/systemimage_intermediates/unsparse_system.img: 1376/51296 files (0.0% non-contiguous), 60991/204800 blocks
Install system fs image: out/target/product/tenderloin/system.img
out/target/product/tenderloin/system.img+ maxsize=856424448 blocksize=135168 total=237901004 reserve=8650752
[email protected]:~/android/skz$
I'm guessing it has something to do with the releasetools, but I get no error. Any ideas?
If you look at my release patch I modify the release tools which changed for 10.1. I really need to separate that patch into it's separate parts. That would make it clear what you need to change. I did that months ago and really don't recall the reasons for each step, I just know that it works. The zip file format changed, as I recall. Wish I could help more. I'll get to work on cleaning up that patch and will make a cleaner branch soon.
drmarble said:
If you look at my release patch I modify the release tools which changed for 10.1. I really need to separate that patch into it's separate parts. That would make it clear what you need to change. I did that months ago and really don't recall the reasons for each step, I just know that it works. The zip file format changed, as I recall. Wish I could help more. I'll get to work on cleaning up that patch and will make a cleaner branch soon.
Click to expand...
Click to collapse
I think I've got that covered. I modified the releasetools, too, and tried both the modified Evervolv and CM versions, but what I get is that stop. I'll check and make sure, though, and I'll compile with the "-v" switch to see if there's something I missed.
I'm not sure if you are familiar with it, but you could try an application called Meld; its a diff viewer. It always comes in handy when I'm comparing code.
If you want to see what's different from the release tools in Evervolv and drmarble's repositories, you can just side by side compare them from your source locally :thumbup:
Also:
To go with the sound patch I removed one commit from the build process: # 34375 # MemoryHeapBase: ifdef for gingerbread/froyo compatibility We aren't using froyo libs apparently, thanks to jcsullins' new sound patch. This means we can remove -DBINDER_COMPAT from Boardconfig.mk.
For anyone who is not watching both threads
Sent from my SAMSUNG-SGH-T989 using xda premium
-SGA- said:
I'm not sure if you are familiar with it, but you could try an application called Meld; its a diff viewer. It always comes in handy when I'm comparing code.
If you want to see what's different from the release tools in Evervolv and drmarble's repositories, you can just side by side compare them from your source locally :thumbup:
Also:
To go with the sound patch I removed one commit from the build process: # 34375 # MemoryHeapBase: ifdef for gingerbread/froyo compatibility We aren't using froyo libs apparently, thanks to jcsullins' new sound patch. This means we can remove -DBINDER_COMPAT from Boardconfig.mk.
For anyone who is not watching both threads
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Chortle, I do need to watch everything, don't I? And I do use meld. It's a great tool. What I'd like to do is to run the "tenderloin_ota_from_target_files" python script from the command line. I can just see all those compiled files sitting there waiting to be zipped up!
I've tried utilizing drivers from the HTC sensation and jcsullins CM10 03/04 build with no further success in getting video playback to function.
Shumash, any luck with getting that to compile yet? Are you trying straight Evervolv source?
Sent from my SAMSUNG-SGH-T989 using xda premium
-SGA- said:
I've tried utilizing drivers from the HTC sensation and jcsullins CM10 03/04 build with no further success in getting video playback to function.
Shumash, any luck with getting that to compile yet? Are you trying straight Evervolv source?
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
I got a CM10.1 to compile, but it boots to the flashy screen. I'm in process of running a clean make to ensure I didn't leave something nasty around. The Evervolv source built to the point that it needs to be zipped into the OTA and release files, but I think there's something missing in the make files that connects with the releasetools. I ran a compile with the verbose switch set, and it acted like it just reached the end of the make files. I have also successfully built a ROM from PAC-man sources, but it also boots to the flashy screen.
Try flashing this after you flash your ROM. It's just a collection of Adreno drivers which I have been experimenting with, it might help get you booting!
-SGA- said:
Try flashing this after you flash your ROM. It's just a collection of Adreno drivers which I have been experimenting with, it might help get you booting!
Click to expand...
Click to collapse
Would you check out that zip file, _SGA_? It fails to flash; says error in zip file (I don"t have any md5 or zip file checking going on).
shumash said:
Would you check out that zip file, _SGA_? It fails to flash; says error in zip file (I don"t have any md5 or zip file checking going on).
Click to expand...
Click to collapse
Just downloaded and flashed now, did not run into any errors. Hmm... I've uploaded it again under a different name :good:
-SGA- said:
Try flashing this after you flash your ROM. It's just a collection of Adreno drivers which I have been experimenting with, it might help get you booting!
Click to expand...
Click to collapse
Would you check out that zip file, _SGA_? It fails to flash; says error in zip file (I don"t have any md5 or zip file checking going on).
EDIT: I found that all but two of the Adreno egl files are missing in the ROM zip. Copied the egl files and your other files manually, and it now boots . I guess is we're going to have to copy them as prebuilt until we have good source.
shumash said:
Would you check out that zip file, _SGA_? It fails to flash; says error in zip file (I don"t have any md5 or zip file checking going on).
EDIT: I found that all but two of the Adreno egl files are missing in the ROM zip. Copied the egl files and your other files manually, and it now boots . I guess is we're going to have to copy them as prebuilt until we have good source.
Click to expand...
Click to collapse
Don't know if the attached are the same as those posted by SGA, but these are official ones from QualComm that I have been using with some sucess. They are advertised as...
"This release contains the user-mode driver binaries for Qualcomm's Adreno 3xx and 2xx GPU on Google Android 4.2 Jelly Bean MR1. It has been tested with the CAF release A8064AAAAANLGD133402.1 and M8960AAAAANLGD230306.1. Supports any Adreno 2xx and 3xx GPU on Android 4.2 Jelly Bean MR1."
Is their any special rom/hardware/asus files needed for this device? If so can you post the github for it?
repo sync AOSP code
https://developers.google.com/android/nexus/drivers
Pirateghost said:
repo sync AOSP code
https://developers.google.com/android/nexus/drivers
Click to expand...
Click to collapse
Would those go in hardware/asus? I got an device tree, vendor and kernel files already.
TeckDude said:
Would those go in hardware/asus? I got an device tree, vendor and kernel files already.
Click to expand...
Click to collapse
untar them, and run the .sh from the root of your build directory....
Pirateghost said:
untar them, and run the .sh from the root of your build directory....
Click to expand...
Click to collapse
before knew this i built a version without those files you told me too add, Someone tested the rom i made for n7 and it worked fine accept a bootloop when changing lockscreen settings. Could that be because I didn't add those files in that build?
Hey im porting this rom to the Jewel or HTC EVO 4G LTE and I see no HTC related files for kernel, build, and Vendor folders.
Should I use the same folders from a different port like Evervolv and just copy and paste the folders or should I do all the stuff manually?
EDIT: Should I just edit the local manifest so it can pick up the appropriate files?
I was hoping it would be as easy as that but something tells me no (still hoping)
lreyes said:
EDIT: Should I just edit the local manifest so it can pick up the appropriate files?
Click to expand...
Click to collapse
yes - that would be the start if you already have an
existing device kernel and vendor folder for your device
It may require some minor changes in the device tree to
work with the pure AOSP build we are using.
So the closer the original device is to AOSP the better
maxwen said:
yes - that would be the start if you already have an
existing device kernel and vendor folder for your device
It may require some minor changes in the device tree to
work with the pure AOSP build we are using.
So the closer the original device is to AOSP the better
Click to expand...
Click to collapse
I'm using Evervolv source and its pure AOSP with some changes. Also it supports my device. So ill just move the folders to the OMNI source and then I'd do lunch or do I do brunch?
Sent from my EVO using XDA Premium 4 mobile app
I was thinking the same thing I now see that they added android_device_htc_msm8960-common to the omnirom repository so we may just be able to edit the localmanifest to pull some of the device specific stuff from another AOSP based rom repository (like CM) and preform an extractfiles for the device specific blobs and it should work . I am going to try when I have some time for the One S.
I have downloaded android keyboard source code. I but it contains some ndk code. I don't have ndk on my PC to compile it. I need someone to compile it and give lib please. I will attach ndk code here.
You can download the NDK from android developers website. https://developer.android.com/tools/sdk/ndk/index.html
There should be a guide for installation, also for compiling with eclipse.
Noted to self thrice via tapatalk
Can't download. my Internet connection is too slow to download huge files.
Sent from my Xperia Neo V using Tapatalk