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

[Q] CM 10.1 on OpenPdroid not recognized by PDroid Manager

I have the same problem as this Christoph21x in post# 3347 in this thread
[Utility][2.9.9][07/19] Auto-Patcher (4.2.2) but they won't let me post there yet, so I'm asking my question here.
I'm running the stable CM 10.1.2, and when I try to flash the openpdroided CM 10.1.2 file, the recovery flashes it in an instant, and reboots. I don't think its flashing at all. Pdroid manager says that pdroid core wasn't found.
Oh, and where can I find the .exe file for the autopatcher that does this work? ApG Autopatcher. All the links I can find seem to go here: Kobik's Files The autopatcher fails to update from 2.6.0.1 which is given at the link to the latest 2.9.935 and I can't find anywhere to download the .exe. The latest files are on Github, but I don't know how to make an exe file out of it. The autopatcher says it can't fine Git on my computer but I installed it.

I've obtained the original Autopatcher off Github and these are the instructions:
Auto-Patcher
authored by pastime1971 and mateor(od)
A smali patcher that ports mods and themes across roms and devices. Extracts, decompiles/unpacks, patches, recompiles/repack, and outputs a flashable zip.
Requirements for execution
-jdk, cpio, patch
Designed to run on Linux, OSX and Windows (using Cygwin)
The main script expects the patches and patch_tools folders to be compressed. pastime has whipped up a script that gets you ready to use the program:
$./batch.sh
For usage and patch availability, place a rom.zip into this directory and try
$./auto_patcher <ROMNAME>.zip -h
I don't know what this means? Am I to type the bolded parts into Windows command line? I don't have much experience with command line, can someone run me through this?

[DEV ONLY] Sony JB4.3 Insecure ramdisk for locked bootloaders!

XZDualRecovery BETA
Version 2.7.60 feature highlight:
Added custom ramdisk support. It will now be able to run a customized ramdisk to boot a ROM! By default this will be disabled. To enable, set dr.insecure.ramdisk in the XZDR.prop file to true.
Property dr.ramdisk.location will contain the path/to/filename.ext to make it easier to use any space you like for testing.
Supports cpio.lzma, plain cpio and tar archives.
XZDR.prop will be inside the XZDualRecovery folder on your external SDcard if you have one, otherwise it will be placed inside /cache.
Click to expand...
Click to collapse
The XZ and Z1 versions of XZDualRecovery install a base version (almost stock kernel ramdisk) if you run a JB 4.3 ROM, which at this point does boot, without bootanimation and unfortunately with bootloops after showing a little bit of life.
As I have no Z1, there is no way for me to really create a working solution... So I will be needing your help! I did create a base package to work with, which does the above on the Xperia Z.
The idea is to have XZDR boot the Sony ROM using the custom ramdisk which will obviously have the security settings disabled, making sure system and rootfs will be remountable!
Help me help you guys get a solution for the remount issues!
XDA:DevDB Information
Sony JB4.3 Insecure ramdisk, a ROM for the Sony Xperia Z1
Contributors
[NUT]
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 14.2.A.0.290
Based On: STOCK
Version Information
Status: Alpha
Created 2013-12-22
Last Updated 2013-12-21

Project Downloads
The Z1 14.2.A.0.290 Stock kernel Ramdisk: View attachment ramdisk.tar.gz
Changed init.sony-platform.rc a bit, commented the mount of the securityfs, the echo to sony_ric/enable, disabled the ric service and changed the execution of chargemon to start chargemon.stock (otherwise it would only repeat itself!).

Testing FAQ
If you want to help out, make sure you have an external SDCard, this will save your bacon more then once for sure!
Remember you can always boot in to TWRP and use it's filemanager to create a file called 'donotrun' inside the XZDualRecovery folder, this will make XZDR skip all operations on the next boot, this will allow you to come out of a bootloop situation. :victory:
An alternative is to take out your SDcard and change the dr.insecure.ramdisk in XZDR.prop from true to false
The XZDR.prop file should look something like this:
Code:
dr.default.recovery=cwm
dr.vanilla.cwm=false
dr.enable.initd=false
dr.insecure.ramdisk=false
dr.ramdisk.location=/path/to/ramdiskname.ext
The location is unimportant, the extension is: It needs to be either a tar, cpio or a cpio.lzma.

[NUT] said:
Project Downloads
The Z1 14.2.A.0.290 Stock kernel Ramdisk: View attachment 2467634
Changed init.sony-platform.rc a bit, commented the mount of the securityfs, the echo to sony_ric/enable, disabled the ric service and changed the execution of chargemon to start chargemon.stock (otherwise it would only repeat itself!).
Click to expand...
Click to collapse
Ok NUT, How can i help you, I'm on locked bootloader C6906, i have downloaded the ramdisk but i don't know how to enable it, thanks in advance.....
I have your rom, and i enable init.d support, but in the XZDR.prop file the location of the ramdisk is dr.ramdisk.location=/system/bin/ramdisk.stock.cpio.lzma
How can transform the ramdisk.tar.gz into ramdisk.stock.cpio. lzma and put in there.....

cgomezparra said:
Ok NUT, How can i help you, I'm on locked bootloader C6906, i have downloaded the ramdisk but i don't know how to enable it, thanks in advance.....
I have your rom, and i enable init.d support, but in the XZDR.prop file the location of the ramdisk is dr.ramdisk.location=/system/bin/ramdisk.stock.cpio.lzma
How can transform the ramdisk.tar.gz into ramdisk.stock.cpio. lzma and put in there.....
Click to expand...
Click to collapse
I've put a small guide on post #2 on how the XZDR.prop file can look.
dr.enable.initd has nothing to do with the ramdisk feature though...

In a little while I look this good and made ​​you a hand.

[NUT] said:
I've put a small guide on post #2 on how the XZDR.prop file can look.
dr.enable.initd has nothing to do with the ramdisk feature though...
Click to expand...
Click to collapse
First try, my XZDR.prop file
dr.default.recovery=cwm
dr.vanilla.cwm=false
dr.enable.initd=true
dr.insecure.ramdisk=true
dr.ramdisk.location=/storage/sdcard1/ramdisk.tar.gz
Nothing happens, i have to rename ramdisk.tar.gz into ramdisk.tar only and edit the XZDR accordingly?
Thanks.
Second try with renamed ramdisk.tar, nothing happens
dr.ramdisk.location=/storage/sdcard1/ramdisk.tar

You have to un-gzip it first before it will work...

I just tried it on my c6902 w/ locked bootloader
and it stuck at SONY logo

Will re-open as soon as the RELEASE version of XZDualRecovery has been released for the Z1... As the OP info is already out of date:
Please do NOT try to do this right now, it will most certainly fail.
Thread Closed.

cm 11 kernel 0% patched

hello everyone
can anyone please patch any cm 11/11.1 xperia arc kernel for 0% battery error..
if you know how to build a kernel please make one patched kernel for me..
i have searched the thread but there is no cm 11 kernel patch.
i know about this thread but can't compile a kernel
http://forum.xda-developers.com/showthread.php?t=1312398
Compile your own version
This are simplified steps. If you dont know how to do, search in the forum.
- First, download the stock kernel source for Xperia (watch out for the correct version), or the sources for your custom ROM you want to use if its not compatible with stock kernel. The developer thread of dev Kalled from Sony (search on developer thread) has some instructions on how to compile the kernel.
This is the direct link to download Sony stock kernel sources:
http://developer.sonymobile.com/downloads/opensource/
- For the ARM compiler, download the CodeSourcery arm eabi compiler version 2010q1.
https://sourcery.mentor.com/sgpp/lit...al/release1294
- Install the compiler on Linux (You can use a virtual machine if you have Windows - use Virtual Box or VMWave Player, both are free for home use).
- Overwrite the bq27520 driver source code with the patched driver from this thread.
- Next, follow the guide on Kalled thread to select phone version and compile the Kernel.
- In the end of compilation, you get a zImage file, that is YOUR Kernel. Congratulations.
- You need a ramdisk. If you are targeting a custom ROM, get a ramdisk compatible with your custom ROM. Also, you can go to DoomLord thread about ramdisk and get a ramdisk suitable for your building. Or generate/use your own ramdisk if you know how. If you use other's ramdisk, give theirs credit.
- With kernel image and ramdisk, generate the file boot.img using mkbootimg tool from Android SDK, or abootimg tool from kubuntu repositories.
- If you choose to use mkbootimg, download a compiled version of mkbootimg, or compile your own version from Android SDK.
- Now you have a boot.img file. Flash it on your phone using fastboot and you are done.
KERNEL I WANT IT TO BE PATCHED
http://www.mediafire.com/download/3o9w31gni49fz4t/11DarkAnzu20140320.img
I HAVE ATTACHED WHAT'S NEEDED(PATCH TO BE REPLACED)..
PLZZ ANYONE HELP..

[SCRIPT][KK][STOCK] AutoROM Flasher v2.1

AUTOROM FLASHER v2.1 (Final update)
Hello everyone!
This is the first script i made for our Moto G 2014, and now i'm actually sharing with y'all to using and testing!
The reason i made it was to avoid the boring command-by-command thing we all deal with while flashing stock kitkat rom.
If you guys like it, please, comment and share your opinion! I'll be glad to read every post!
How to use it on Linux:
1. Open terminal by using Ctrl + Alt + T
2. Cd the directory where is located both system and script file (The script NEEDS TO BE on the moto g system files folder)
3. Do a chmod +x autoromflasher.sh to grant all permissions
4. Execute it using sh ./autoromflasher.sh
5. Wait for it and then it's done!
Download link (LINUX VERSION): MEGA
Download link (WINDOWS VERSION):
MEGA
Download link (WINDOWS ALTERNATE VERSION):
MEGA
Github for devs: LINK
Enjoy
Op

Changelog
10/02/2015
1. Added linux version
2. Support for all distros
12/02/2015
1. Added windows version
2. Added windows alternate version for MFASTBOOT.EXE users
21/02/2015 (this will be the last update)
1. Added github "mirror" for dev
2. Updated Linux version
3. Added TWRP flashing support (linux)
4. Added Philz flashing support (linux)

@mrnickel - we really need some nice script for Linux, you should also check @luca020400 work
http://forum.xda-developers.com/moto-g-2014/development/ultimate-moto-g-2014-toolkit-t2979862

cociuba said:
@mrnickel - we really need some nice script for Linux, you should also check @luca020400 work
http://forum.xda-developers.com/moto-g-2014/development/ultimate-moto-g-2014-toolkit-t2979862
Click to expand...
Click to collapse
Thanks, i will check it out! [emoji1]

last update
this will be my last update on this script
hope anyone manage to use it for flashing and stuff XD
in this last change, i've added some TWRP and Philz support, just like Luca on his Toolkit (Thanks m8!)
So that's it, appreciate everyone that used it, i think i'm going to do some scripts in a future, but for this week i'm done haha
op