5,604,367 Members 48,664 Now Online
XDA Developers Android and Mobile Development Forum

[RECOVERY][toro] TWRP 2.7.0.0 touch recovery [2014-03-10]

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

 
DONATE TO ME
Default [RECOVERY][toro] TWRP 2.7.0.0 touch recovery [2014-03-10]

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 59 Users Say Thank You to Dees_Troy For This Useful Post: [ Click to Expand ]
 
zedorda
Old
#2  
zedorda's Avatar
Senior Member
Thanks Meter 21
Posts: 205
Join Date: Apr 2011
I really love this recovery.
 
tacosrdelicioso
Old
#3  
Senior Member
Thanks Meter 231
Posts: 1,239
Join Date: Mar 2011
This recovery kicks burt

Sent from my Galaxy Nexus using xda premium
 
PacerguyDon
Old
#4  
PacerguyDon's Avatar
Senior Member
Thanks Meter 219
Posts: 684
Join Date: Mar 2011
Location: Boise

 
DONATE TO ME
Thank you much. Love having touch again
~Don~
Galaxy Nexus
RasbeanJelly/Trinity
Moto Xoom
Team Eos 3

Give Minus or
Dropbox a try.
 
gi812
Old
#5  
Member
Thanks Meter 1
Posts: 32
Join Date: Oct 2010
did 2.1.2 add any thing that makes it worth flashing form 2.1.1?

i guess the major reason for it was the sprint phone?
 
jcmm11
Old
#6  
Senior Member
Thanks Meter 168
Posts: 392
Join Date: Feb 2012
Quote:
Originally Posted by gi812 View Post
did 2.1.2 add any thing that makes it worth flashing form 2.1.1?

i guess the major reason for it was the sprint phone?
Bug fix. Apparently 2.1.1 would only back-up and not restore

Sent from my Galaxy Nexus using XDA
 
cowsquad
Old
#7  
cowsquad's Avatar
Senior Member
Thanks Meter 265
Posts: 1,098
Join Date: Aug 2009
Location: Portland, Oregon

 
DONATE TO ME
This recovery is working flawlessly

Sent from my Galaxy Nexus using Tapatalk 2
 
tacosrdelicioso
Old
#8  
Senior Member
Thanks Meter 231
Posts: 1,239
Join Date: Mar 2011
Quote:
Originally Posted by cowsquad View Post
This recovery is working flawlessly

Sent from my Galaxy Nexus using Tapatalk 2
Except for it refuses to flash pure aosp build 5

Sent from my Galaxy Nexus using xda premium
 
zedorda
Old
#9  
zedorda's Avatar
Senior Member
Thanks Meter 21
Posts: 205
Join Date: Apr 2011
I had to switch back to CWM bc I ran into too many ROMs refusing to flash. Hope this issue can be remedied soon.
 
phoenixs4r
Old
#10  
phoenixs4r's Avatar
Senior Member
Thanks Meter 27
Posts: 410
Join Date: Aug 2010
Quote:
Originally Posted by zedorda View Post
I had to switch back to CWM bc I ran into too many ROMs refusing to flash. Hope this issue can be remedied soon.


Sent from my Galaxy Nexus

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes