[DEV][RECOVERY] TeamWin Recovery Project for X8 [11-11-2012] - XPERIA X8 Original Android Development

ATTENTION!
AT THIS MOMENT THIS IS ONLY A WORK IN PROGRESS PROJECT,
RECOMMENDED FOR DEVS AND TESTERS ONLY!
To the haters/spammers/etc:
The TeamWin Recovery Project is Open Source Project, available for
everyone and I talked with Dees_Troy, and he accept this project.
In the links you can found a modded kernel from alfsamsung, before you
start a permission war: I have permission from alfsamsung too, since 2012 march,
so do not start "do you have permission???" questions.
Some suggestion:
This is a development thread.
If you want to say: this project is wonderful or a big piece of sh*t, better if you leave it.
Earlier sgt. meow opened a discussion thread about TWRP, if you can't help in the development,
please go there if you want to write something.
I have really few time to work on this project.
If you want to help, write your ideas, and write what do you want to do.
For example:
If you want to work with themes, or any part of the code, please inform me.
XDA Developers site is a COMMUNITY
Better if we share the tasks, and work more developers on ONE project than everyone working alone.
I will try to manage this project, and if the project will be stable, I will send back the code/configuration/etc
changes to the original TeamWin team to help their work.​
What is it?
This is a modified TeamWin Recovery for the X8
For more information visit the official TeamWin Recovery Project page.
http://teamw.in/project/twrp2
Whats working:
Touch control
Install zip updates (some zip files need a newer update-binary)
Backup and Restore (except the android_secure folder)
Built in terminal and filemanager
Mounts
Wipes
USB Mount
Need to fix:
Some UI related changes (a few button/checkbox in wrong place)
Backup/restore of the android_secure folder
All non discovered bugs...
How to build from source:
With CM7:
First step: Prepare the build environment
Download the modded CM7_build from Dees_Troy:
https://github.com/Dees-Troy/TWRP2-CM7_build
and replace your own build/core/Makefile with the one from the downloaded file.
Second step: modify the prelinker map
Search the device specific BoardConfig.mk (or BoardConfigCommon.mk) and check where is your prelinker map. Defined with the TARGET_PRELINKER_MAP variable, for example in the MiniCM7 source the TARGET_PRELINKER_MAP point to /device/semc/msm7x27-common/prelink-linux-arm-x8.map
Merge these binaries:
#libraries for TWRP
libmmcutils.so 0x9C500000 # [<64K]
libbmlutils.so 0x9C400000 # [<64K]
libflashutils.so 0x9C300000 # [<64K]
libmincrypt.so 0x9C200000 # [<64K] #This need only is you use crypto​
WARNING!!! Check the last address in the original file, and recalculate the added binaries address!!!
With CM9/CM10/AOKP:
Waiting for other devs
TWRP related settings (merge into the BoardConfig.mk, and you can found these settings in the source too)
#TWRP
BOARD_HAS_NO_REAL_SDCARD := false
DEVICE_RESOLUTION := 320x480
RECOVERY_GRAPHICS_USE_LINELENGTH := true
TARGET_RECOVERY_GUI := true
TARGET_RECOVERY_PIXEL_FORMAT := "RGB_565"
TARGET_USE_CUSTOM_LUN_FILE_PATH :=/sys/devices/platform/usb_mass_storage/lun0/file
TW_CUSTOM_POWER_BUTTON := 107
TW_EXTERNAL_STORAGE_PATH := "/sdcard"
TW_EXTERNAL_STORAGE_MOUNT_POINT := "sdcard"
TW_FLASH_FROM_STORAGE := true
TW_HAS_DOWNLOAD_MODE := false
TW_HAS_NO_RECOVERY_PARTITION := true
TW_INCLUDE_CRYPTO := false
TW_INCLUDE_JB_CRYPTO := false
TW_NEVER_UNMOUNT_SYSTEM := false
TW_NO_BATT_PERCENT := false
TW_NO_REBOOT_BOOTLOADER := true
TW_NO_USB_STORAGE := false
TW_SDEXT_NO_EXT4 := false​
To build it, you need only:
Replace the files in bootable/recovery with the files from the source
Code:
. build/envsetup.sh
lunch
make recoveryimage
When the build finished, grab the needed files from:
out/target/product/shakira/recovery/root
While this project is only alpha stage, better if you use it in dual recovery mode (CWM+TWRP)
Here is a sample bootrec file (with this sample the normal methods (key press on kernel logo or use the Reboot to recovery option in the rom) start the CWM recovery, if you touch the screen on kernel logo, the TWRP start.
Code:
#!/sbin/sh
# With alfsamsung kernels and stock use these values:
cat /dev/input/event1 > /dev/keycheck&
cat /dev/input/event0 > /dev/tscheck&
[COLOR="Red"]# USE THESE VALUES ON ALL NAA BASED KERNELS :) [COLOR="Blue"]// thanks for feherneoh[/COLOR]
cat /dev/input/event2 > /dev/keycheck&
cat /dev/input/event1 > /dev/tscheck&[/COLOR]
sleep 2
kill -9 $!
if [ -s /dev/keycheck -o -e /cache/recovery/boot ]
then
rm /cache/recovery/boot
mount -o remount,rw rootfs /
umount -l /system
umount -l /data
umount -l /cache
umount -l /mnt/sdcard
rm -r /sdcard
rm -r /not/sdcard
mkdir /sdcard
mkdir /tmp
rm /etc
mkdir /etc
cp /recovery.fstab /etc/recovery.fstab
mount /dev/block/mmcblk0p1 /sdcard
/sbin/recovery &
/sbin/adbd recovery
fi
if [ -s /dev/tscheck ]
then
mount -o remount,rw rootfs /
umount -l /system
umount -l /data
umount -l /cache
umount -l /mnt/sdcard
chroot /recovery /init
fi
mkdir /system/lib/modules
ln -s /modules/sdio.ko /system/lib/modules/sdio.ko
ln -s /modules/tiwlan_drv.ko /system/lib/modules/tiwlan_drv.ko
ln -s /modules/tiap_drv.ko /system/lib/modules/tiap_drv.ko
chown u+s /sbin/charger
mount -o remount,noatime,noauto_da_alloc,nodiratime,barrier=0,nobh,ro /dev/block/mtdblock0 /system
/sbin/charger
With this sample you must place the recovery files into /recovery folder of the ramdisk or if you have /recovery partition place it there (don't forget to mount the recovery partition)
If you use the ramdisk own init.rc file to start the recovery (instead of the method with change root to the recovery own folder) you need to modify the init.rc file, add the path of the recovery files to the LD_LIBRARY_PATH variable:
Code:
# setup the global environment
export PATH /sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin
export LD_LIBRARY_PATH /vendor/lib:/system/lib[COLOR="Red"]:/path_of_the_recovery (usually the /sbin folder)[/COLOR]
Links:
Source: https://github.com/pilu1978/TeamWin_Recovery_X8
Link for the prebuilt binaries (you can try it without compiling):
http://www.mediafire.com/?wxkmwnh1afc7aa1
If you not want to play with this project, just want to try it
here is a modded alfs8a kernel with CWM+TWRP:
http://www.mediafire.com/?7qy1fq3yv4gjra8​

---

Work in progress:
Fix for the old update-binary (if the zip package contains normal installer then use the built-in version from the ramdisk, if the update contains aroma installer use the one from the zip package)
Fix for the android_secure backup/restore
Fix the UI bugs (correct some button/checkbox position and remove some useless thing)
Aroma Filemanager instead of the built-in filemanager
Fix the errors with the busybox what compiled with twrp (to make standalone twrp, no need external busybox or cwm recovery to use it)
SOURCES AND BINARIES WILL BE UPDATED ONLY WHEN THESE FIXES FULLY WORKING!!!
The cooperative work failed, working alone.

---

Reserved for other developers who working on this project

---

Reserved for future usage

---

Hi, I'd like to know what has this Recovery more than the others ? I didn't find in the Thread the specs of it.
Thanks.

---

WHTA?'''
What version is this cwm....... Can i port this to the stock kernel??

---

With Jelly Bean repos, your config not working. The recovery compiling without error. But the made recovcery doesn't work. The Blue background and teamwin text flashing constantly... Now I try to find why...

---

Neur0Nerd said:
Hi, I'd like to know what has this Recovery more than the others ? I didn't find in the Thread the specs of it.
Thanks.
Click to expand...
Click to collapse
Go there: http://teamw.in/project/twrp2 (link added to the first post)
xperiafan13 said:
What version is this cwm....... Can i port this to the stock kernel??
Click to expand...
Click to collapse
This is NOT ClockWorkMod This is TeamWin Recovery V2.3.1.1 And as I wrote: this project is open source. If you want to port for stock kernel, you can do it. Only one request: please inform me about your work.
Daveee10 said:
With Jelly Bean repos, your config not working. The recovery compiling without error. But the made recovcery doesn't work. The Blue background and teamwin text flashing constantly... Now I try to find why...
Click to expand...
Click to collapse
No idea why. Try to use the precompiled binaries. If these binaries work with JB kernel, maybe I forgot something, or need to add something. The source based on the official JB branch of TeamWin Recovery.

---

no, the prebuilt recovery doen't work too.. But I don't see the init.rc change in your first post.
I think that:
Adding .:/sbin after export LD_LIBRARY_PATH before any other path...

---

Yes, I forgot it, later I will correct it. (now on mobile). But the prebuilt binaries contains this mod. And when you compile the recovery, the listed folder in the 1st post contains the correct init.rc. And how to use the recovery? Try to use it with chroot.
Sent from my E15i using xda app-developers app

---

pilu1978 said:
Yes, I forgot it, later I will correct it. (now on mobile). But the prebuilt binaries contains this mod. And when you compile the recovery, the listed folder in the 1st post contains the correct init.rc. And how to use the recovery? Try to use it with chroot.
Sent from my E15i using xda app-developers app
Click to expand...
Click to collapse
no, that not the correct for me... in my kernel init.rc very different from that.. Trying to change all needed file to twrp recovery file... So I want use twrp only one recovery in kernel now.. If working I will make the dual recovery method or modular recovery... But now I go to bed because tomorrow I will working. So the next compiling is tomorrow evening...

---

The compiled init.rc is correct for the recovery. I think better if you use it in dual recovery mode, and make standalone twrp recovery after a longer test period. And I think better if you re-init the phone with the recovery own init.rc file instead of replacing existing files in ramdisk. This method clean and work, and compatible with the kernel what have recovery partition.
Sent from my E15i using xda app-developers app

---

I'm going to compile now using the jb-wip branch. Will let you know how it goes.

---

Umm...pilu1978, your modified kernel's init (the one in the recovery folder) is smaller in size than that of mine. Also would the same bootrec work on ICS kernels? I'm pretty sure it will. However when I tried it didn't boot (missed out some bits of code, I guess). So I'm going to use your one now and test. Will report what happens.

---

Good work bro
downloaded and testing now
cheers

---

For those who want to test it on other kernels here is the .zip edition:
https://docs.google.com/folder/d/0B_4r4JB1Is2QX3VSSDBZZF81ckU/edit
Download then install from CWM & enjoy
Sent from my E15i using xda app-developers app

---

sgt. meow said:
Umm...pilu1978, your modified kernel's init (the one in the recovery folder) is smaller in size than that of mine. Also would the same bootrec work on ICS kernels? I'm pretty sure it will. However when I tried it didn't boot (missed out some bits of code, I guess). So I'm going to use your one now and test. Will report what happens.
Click to expand...
Click to collapse
Yes, it can work with all kernel. The init binary compiled from CM7 sources, this is the reason of the smaller size. The init in ICS/JB kernels a little bit bigger, these binaries contains additional user groups, etc, but for the recovery this is not important. The init.rc is much smaller because it NOT contains the basic file structure/settings what needed for the ROM. The recovery can work with a totally empty phone without any ROM, because this is INDEPENDENT from the installed (or not installed) android version (you also use CWM what compiled with CM7 source tree in your ICS/JB kernels without any problem). The bootrec is only a simple script, what contains some conditions (what happen IF key pressed and what happen IF you touch the screen). You can use any script when the phone booting (call with exec command in init.rc/init.delta.rc

---

It still didn't work. When I tap the screen, it boots into CWM touch. Now I'll try and use your binaries and see what happens.
@feherneoh
Good work bro. Works like a charm.

---

You use the bootrec from 1st post? Try to use the one from the sample kernel, later I will check the posted bootrec, maybe forgot something...
EDIT: looks like the posted bootrec and the other in the sample kernel is near 100% same. Two differences:
1. In the kernel the bootrec check the screen type and select the correct version of touch cwm (this is absolute not do anything with twrp)
2. In the kernel bootrec file a secondary condition exist to start twrp, it will start IF touch the screen OR a file exists in /cache/recovery (I add options for boot to twrp in my own rom, but it can't be a reason of cwm starting instead of twrp)
Sent from my E15i using xda app-developers app

---

Nope, using your binaries didn't work either.