5,601,223 Members 52,750 Now Online
XDA Developers Android and Mobile Development Forum

[RECOVERY][nozomi] TWRP 2.7.0.1 touch recovery [2014-03-11]

Tip us?
 
Dees_Troy
Old
(Last edited by Dees_Troy; 11th March 2014 at 08:09 PM.)
#1  
Dees_Troy's Avatar
Senior Recognized Developer - OP
Thanks Meter 8589
Posts: 1,575
Join Date: Mar 2008
Location: KC MO

 
DONATE TO ME
Default [RECOVERY][nozomi] TWRP 2.7.0.1 touch recovery [2014-03-11]

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.

Phone look:


Tablet look:


CHANGELOG for 2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes

Note: 2.7 marks the first time that we are dropping support for older devices. We are doing this because of the SELinux support needed to install 4.4 Kit Kat ROMs. The non-TWRP parts of the recovery image have to be built in at least a 4.1 tree and the kernel that is included in the recovery image has to support writing SELinux contexts. We don't own most of the devices that we support so we depend on outside testers and developers to help us update devices. In many cases we can't find someone readily. Come to #twrp on Freenode if you want to help bring your device up to date. You can tell right away if your device will support 4.4 ROMs in 2.7. Boot TWRP and press the console button (the square-ish button either in the bottom middle or upper right) to view the console output. If it doesn't say "Full SELinux support" in the console, then your device still needs some work. Help us help you.

CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks

CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks

DOWNLOAD:
Most devices can be updated quickly and easily with the TWRP Manager app:
Play Store Link
1) Install TWRP Manager from the Play Store
2) Open TWRP Manager and provide root permissions
3) Hit Advanced->Install Recovery
4) Verify the correct device name on your screen then press Install Recovery if the correct device is showing
OR:
You can find more information and download links on our website!

BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!

SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
The Following 37 Users Say Thank You to Dees_Troy For This Useful Post: [ Click to Expand ]
 
Dees_Troy
Old
(Last edited by Dees_Troy; 1st March 2013 at 08:24 PM.)
#2  
Dees_Troy's Avatar
Senior Recognized Developer - OP
Thanks Meter 8589
Posts: 1,575
Join Date: Mar 2008
Location: KC MO

 
DONATE TO ME
More information:

Most Xperia S kernels are probably including CWM by default in the boot image. About a month ago I submitted some changes to the CyanogenMod repos that were accepted. Newer builds of CM include a special extract_elf_ramdisk utility that I wrote to read and extract a recovery ramdisk from the FOTAKernel partition instead of using the ramdisk that is included in the boot image. If the ramdisk in the FOTAKernel partition is a stock Sony ramdisk or not present, then the existing ramdisk in the boot image is used instead. This setup allows users to choose which recovery they want to keep installed. This same setup is possible in other kernels including stock Sony kernels. On our website's download link you will find a copy of a recent stock ICS kernel for the Xperia S that includes TWRP as well as the extract_elf_ramdisk utility.

If the kernel you have installed doesn't support this extract_elf_ramdisk setup, then you won't be able to use the GooManager installed copy of TWRP. Bug your kernel or ROM developer and ask them to update their images so that you can choose what recovery you want.

What is the FOTAKernel partition?

The FOTAKernel partition is used by Sony to do FOTA updates when updating the boot image. Unlocked devices can't take Sony FOTA updates so using this partition for storing the recovery ramdisk seems like a good idea. Unlocked users aren't able to use this partition anyway and the FOTAKernel partition is effectively the "recovery" partition on Sony devices.
The Following 16 Users Say Thank You to Dees_Troy For This Useful Post: [ Click to Expand ]
 
eScapeeXc
Old
(Last edited by eScapeeXc; 2nd March 2013 at 12:16 AM.)
#3  
Senior Member
Thanks Meter 20
Posts: 115
Join Date: Dec 2009
Location: Vienna
Thanks a lot but from your site can we get only 2.4.0.0. And it's for the oldest rom kernel (.452). Can you please update the ramdisk and modem for the our Xperia S?
Device: Apple iPhone5 White

2. Device: Sony Xperia S
Android Version: 4.0.4 ICS
Bootloaderstatus: UNLOCKED
Kernel: Stock+ v5.3 w/ TWRP - by tosa.th
Rom: Stock .55 - by Sony
Mod: -
 
mrkidvn
Old
#4  
mrkidvn's Avatar
Member
Thanks Meter 3
Posts: 92
Join Date: Jan 2013
Location: Ho Chi Minh
anychange for locked BL?
 
darkerm
Old
#5  
darkerm's Avatar
Senior Member
Thanks Meter 51
Posts: 515
Join Date: Feb 2012
Location: Dhaka
Advance Stock Kernel 17 comes with CWM.
How Can I install this over CMW?
Xperia S (Black)
eXistenZ Ultra 1.3.5
Unlocked Bootloader, Rooted
I am a Hardcore Mobile Gamer
 
Redstarr1
Old
#6  
Redstarr1's Avatar
Senior Member
Thanks Meter 357
Posts: 675
Join Date: May 2012
Location: Leuven
Quote:
Originally Posted by eScapeeXc View Post
Thanks a lot but from your site can we get only 2.4.0.0. And it's for the oldest rom kernel (.452). Can you please update the ramdisk and modem for the our Xperia S?
You should take a look at the "Download - FOTAKernel Image" header. There's no need to install that stock kernel, you can also just push the recovery. The way described on the website requires you use Terminal Emulator but there's an easier way. (I also don't really understand which is the right version because there is 2.4.3.0 for nozomi and 2.4.3.0 for LT26i and afaik that's the same device).

Just install GooManager on your phone, select "Flash ROMs" and there should be a message asking if you have a custom recovery. Select to install one and the latest version of TWRP will be installed.

I'm using Stock+ kernel, that already had TWRP 2.4.1 recovery, after doing this with GooManager I have TWRP 2.4.3.0. If you're using any of the other .55 kernels it should be work as well.

Quote:
Originally Posted by mrkidvn View Post
anychange for locked BL?
No idea.

Quote:
Originally Posted by darkerm View Post
Advance Stock Kernel 17 comes with CWM.
How Can I install this over CMW?
That's basically the same question eScapeeXc asked so the answer is the same .
My current devices:
Sony Xperia S: Paranoid Android by deedwar
Google Nexus 7 (2013): Paranoid Android
 
algates
Old
#7  
algates's Avatar
Senior Member
Thanks Meter 34
Posts: 227
Join Date: Sep 2012
Location: kumbakonam, TamilNadu
Default Re: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]

Is it works on locked bootloader?

Sent from my LT26i using xda app-developers app
 
Apology11
Old
(Last edited by Apology11; 7th May 2013 at 12:31 PM.)
#8  
Apology11's Avatar
Senior Member
Thanks Meter 177
Posts: 561
Join Date: Apr 2012
Location: Wertheim
Will:

dd if=/dev/zero of=/dev/block/mmcblk0p11

remove the recovery?

Is there a way to choose between the recovery from the kernel and this one on fota while booting?

How many space has the fota partition on our device?
 
mericon
Old
#9  
Senior Member
Thanks Meter 309
Posts: 293
Join Date: Aug 2011
Location: Aachen

 
DONATE TO ME
Quote:
Originally Posted by algates View Post
Is it works on locked bootloader?

Sent from my LT26i using xda app-developers app
It needs a modified ramdisk. So it will not work.
Device: HTC ONE SV (K2U)
The Following User Says Thank You to mericon For This Useful Post: [ Click to Expand ]
 
twk99
Old
#10  
Member
Thanks Meter 5
Posts: 38
Join Date: Sep 2012
Location: Sweden
Default Sv: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]

Quote:
Originally Posted by Dees_Troy View Post
More information:

Most Xperia S kernels are probably including CWM by default in the boot image. About a month ago I submitted some changes to the CyanogenMod repos that were accepted. Newer builds of CM include a special extract_elf_ramdisk utility that I wrote to read and extract a recovery ramdisk from the FOTAKernel partition instead of using the ramdisk that is included in the boot image. If the ramdisk in the FOTAKernel partition is a stock Sony ramdisk or not present, then the existing ramdisk in the boot image is used instead. This setup allows users to choose which recovery they want to keep installed. This same setup is possible in other kernels including stock Sony kernels. On our website's download link you will find a copy of a recent stock ICS kernel for the Xperia S that includes TWRP as well as the extract_elf_ramdisk utility.

If the kernel you have installed doesn't support this extract_elf_ramdisk setup, then you won't be able to use the GooManager installed copy of TWRP. Bug your kernel or ROM developer and ask them to update their images so that you can choose what recovery you want.

What is the FOTAKernel partition?

The FOTAKernel partition is used by Sony to do FOTA updates when updating the boot image. Unlocked devices can't take Sony FOTA updates so using this partition for storing the recovery ramdisk seems like a good idea. Unlocked users aren't able to use this partition anyway and the FOTAKernel partition is effectively the "recovery" partition on Sony devices.
Does this mean that flashing TWRP on Xperia S, this way, will prevent it from being overwritten every time a new kernel is flashed?

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes