Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,733,098 Members 46,612 Now Online
XDA Developers Android and Mobile Development Forum

[RECOVERY][deb/flo] TWRP 2.7.1.0 touch recovery [2014-06-05]

Tip us?
 
Dees_Troy
Old
(Last edited by Dees_Troy; 5th June 2014 at 09:12 PM.)
#1  
Dees_Troy's Avatar
Senior Recognized Developer - OP
Thanks Meter 9025
Posts: 1,582
Join Date: Mar 2008
Location: KC MO

 
DONATE TO ME
Default [RECOVERY][deb/flo] TWRP 2.7.1.0 touch recovery [2014-06-05]

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.1.0:
-Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
-Various bugfixes to backup and restore
-Improvements to USB storage handling
-Added a class to search for files to make finding the correct brightness file automatic in most cases
-Various other bugfixes and tweaks

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

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 95 Users Say Thank You to Dees_Troy For This Useful Post: [ Click to Expand ]
 
Dees_Troy
Old
#2  
Dees_Troy's Avatar
Senior Recognized Developer - OP
Thanks Meter 9025
Posts: 1,582
Join Date: Mar 2008
Location: KC MO

 
DONATE TO ME
Default Reserved

The Following 5 Users Say Thank You to Dees_Troy For This Useful Post: [ Click to Expand ]
 
Dees_Troy
Old
#3  
Dees_Troy's Avatar
Senior Recognized Developer - OP
Thanks Meter 9025
Posts: 1,582
Join Date: Mar 2008
Location: KC MO

 
DONATE TO ME
You may need the new SuperSU beta for 4.3 to get root working, not sure.

Thanks to viperboy for testing.
The Following 8 Users Say Thank You to Dees_Troy For This Useful Post: [ Click to Expand ]
 
aooga
Old
#4  
aooga's Avatar
Senior Member
Thanks Meter 824
Posts: 2,839
Join Date: Feb 2011
Location: California
Already??? Wow, thanks!

---------- Post added at 05:02 PM ---------- Previous post was at 05:01 PM ----------

Quote:
Originally Posted by Dees_Troy View Post
You may need the new SuperSU beta for 4.3 to get root working, not sure.

Thanks to viperboy for testing.
Thats right. The old one doesn't work on my Nexus 4, so I dont think it will work here either.
The Following User Says Thank You to aooga For This Useful Post: [ Click to Expand ]
 
Mr. Steve
Old
#5  
Mr. Steve's Avatar
Senior Member
Thanks Meter 56
Posts: 196
Join Date: Nov 2010
Location: Newark, Delaware
Quote:
Originally Posted by aooga View Post
Already??? Wow, thanks!

---------- Post added at 05:02 PM ---------- Previous post was at 05:01 PM ----------



Thats right. The old one doesn't work on my Nexus 4, so I dont think it will work here either.
I believe SuperSU got an update yesterday so that you don't need to use the beta app on 4.3
Current devices:
Nexus 5 (32gb) running L Developer Preview;
Nexus 7 (32gb)(2013) running stock 4.4.3 rooted; Latest Franco kernel
Previous devices:
Nexus 4 (16gb),Nexus 7 (32gb)(2012),Galaxy Nexus (CDMA), Motorola Droid 2, Motorola Droid
 
tw1tch175
Old
(Last edited by tw1tch175; 27th July 2013 at 01:19 AM.)
#6  
tw1tch175's Avatar
Senior Member
Thanks Meter 60
Posts: 278
Join Date: Dec 2010
Flashing now, will update when Im rooted with custom recovery

Running perfectly, flashed chainfires root and installer supersu and now my nexus 7 is rooted and I am happy!
 
Mr. Steve
Old
#7  
Mr. Steve's Avatar
Senior Member
Thanks Meter 56
Posts: 196
Join Date: Nov 2010
Location: Newark, Delaware
Quote:
Originally Posted by tw1tch175 View Post
Flashing now, will update when Im rooted with custom recovery
The suspense is killing me.
Current devices:
Nexus 5 (32gb) running L Developer Preview;
Nexus 7 (32gb)(2013) running stock 4.4.3 rooted; Latest Franco kernel
Previous devices:
Nexus 4 (16gb),Nexus 7 (32gb)(2012),Galaxy Nexus (CDMA), Motorola Droid 2, Motorola Droid
 
ATGAdmin
Old
#8  
ATGAdmin's Avatar
Senior Member
Thanks Meter 1035
Posts: 1,366
Join Date: Feb 2012
Location: Western NY State
Why is the recovery for our device called "TWRP for Nexus 7 2013 [flo]" and not "[razor]"?

HTC One Running Onelicious
LG GPad 8.3
Running LGelicious
Licious ROMs 2013-2014
 
Mr. Steve
Old
#9  
Mr. Steve's Avatar
Senior Member
Thanks Meter 56
Posts: 196
Join Date: Nov 2010
Location: Newark, Delaware
Quote:
Originally Posted by ATGAdmin View Post
Why is the recovery for our device called "TWRP for Nexus 7 2013 [flo]" and not "[razor]"?
The device codename is razor while the board id is flo. On the old Nexus 7 for example, the device codename was nakasi while the board id was grouper.
Current devices:
Nexus 5 (32gb) running L Developer Preview;
Nexus 7 (32gb)(2013) running stock 4.4.3 rooted; Latest Franco kernel
Previous devices:
Nexus 4 (16gb),Nexus 7 (32gb)(2012),Galaxy Nexus (CDMA), Motorola Droid 2, Motorola Droid
The Following User Says Thank You to Mr. Steve For This Useful Post: [ Click to Expand ]
 
phuduong
Old
#10  
Senior Member
Thanks Meter 60
Posts: 231
Join Date: Aug 2005
YAYYYYYYYYYY, finally I got ROOT on new Nexus 7
HTC One M8 Silver (32GB)
ROM: Insert Coin M8

HTC One M7 White (16GB)
ROM: Insert Coin 6th Sense


Apple iPhone 5 White (32GB)
iOS: iOS 7.1.1

Google Nexus 7 2013 (32GB)

If I have helped you, please hit the the THANKS button!

The Following User Says Thank You to phuduong For This Useful Post: [ Click to Expand ]
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes