5,595,760 Members 38,625 Now Online
XDA Developers Android and Mobile Development Forum

[RECOVERY][otter] 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:08 PM.)
#1  
Dees_Troy's Avatar
Senior Recognized Developer - OP
Thanks Meter 8576
Posts: 1,573
Join Date: Mar 2008
Location: KC MO

 
DONATE TO ME
Default [RECOVERY][otter] 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 68 Users Say Thank You to Dees_Troy For This Useful Post: [ Click to Expand ]
 
That Baker Guy
Old
#2  
That Baker Guy's Avatar
Senior Member
Thanks Meter 32
Posts: 261
Join Date: Dec 2011
Location: Tobie Town
id love to try this out, but from the comments on the site, it appears that the commands listed do not work... also i have a mac so its probably different.
d2vzw PA
tf300t cm-10.2
nook color cm-10.2
 
AustinFire
Old
#3  
Senior Member
Thanks Meter 12
Posts: 102
Join Date: Feb 2012
Location: Pensacola
Sweet! I'll have to try this out!
 
kinfauns
Old
#4  
kinfauns's Avatar
Developer Committee / Senior Moderator
Thanks Meter 2876
Posts: 1,643
Join Date: Jan 2012
I just gave the new version a quick run around the block...

PROS: The distribution is no longer a boot image that forces a flash of the old FFF 1.0 along with TWRP. It's now an actual recovery image that can be flashed through fastboot like... "fastboot flash recovery twrp-fire-2.1.0.img"

CONS: Even though there are some more reboot options in this new version, they are all still broken. Just as in 2.0.0, none of the reboot options (system, recovery, bootloader... I'm assuming the last one is supposed to boot into fastboot mode) will reset the bootmode accordingly before the device is restarted. That makes these options pretty useless as the device will still continue to boot in the previous bootmode. So, the TWRP bootloops will continue to plague new users who have no idea how to get it to boot to the system.... bummer.
The Following 7 Users Say Thank You to kinfauns For This Useful Post: [ Click to Expand ]
 
AFAinHD
Old
#5  
AFAinHD's Avatar
Senior Member
Thanks Meter 524
Posts: 781
Join Date: Mar 2011
Location: Fenton, Missouri

 
DONATE TO ME
I love that we got this! Buuuuttttt I like 2.0 just fine. Its stable. It works. :) love to see progress though.:)

Sent from my Kindle Fire using XDA
Graphics Designer for the SickleSoftware dev team.


I made beautiful boot animations for the Nexus 7 before it was cool.
Want to know how to make your own bootanimation? Check out my noob-friendly guide! Here.
My goo.im repo - here.
 
smirkis
Old
#6  
smirkis's Avatar
Senior Member
Thanks Meter 610
Posts: 1,805
Join Date: Oct 2010
Location: San Diego, CA
its great to see progress, but as kinfaun said reboot is still broken.

Sent from my HTC Glacier using xda premium
T-Mobile G2>HTC Glacier>Samsung Galaxy Nexus>Google Nexus 4

Asus Transformer>Amazon Kindle Fire>Google Nexus 7>2013 Nexus 7
 
DJLamontagneIII
Old
#7  
DJLamontagneIII's Avatar
Recognized Contributor
Thanks Meter 3092
Posts: 2,539
Join Date: Sep 2008
Location: Providence, Rhode Island

 
DONATE TO ME
Quote:
Originally Posted by smirkis View Post
its great to see progress, but as kinfaun said reboot is still broken.

Sent from my HTC Glacier using xda premium
thats a deal breaker for me... thanks for the update tho
The Following User Says Thank You to DJLamontagneIII For This Useful Post: [ Click to Expand ]
 
smirkis
Old
#8  
smirkis's Avatar
Senior Member
Thanks Meter 610
Posts: 1,805
Join Date: Oct 2010
Location: San Diego, CA
I spoke with deestroy n were gonna try to get it resolved. yay lol

they don't have our device so its hard to know what doesn't work. looking forward to testing the update

Sent from my HTC Glacier using xda premium
T-Mobile G2>HTC Glacier>Samsung Galaxy Nexus>Google Nexus 4

Asus Transformer>Amazon Kindle Fire>Google Nexus 7>2013 Nexus 7
The Following 2 Users Say Thank You to smirkis For This Useful Post: [ Click to Expand ]
 
DJLamontagneIII
Old
#9  
DJLamontagneIII's Avatar
Recognized Contributor
Thanks Meter 3092
Posts: 2,539
Join Date: Sep 2008
Location: Providence, Rhode Island

 
DONATE TO ME
Quote:
Originally Posted by smirkis View Post
I spoke with deestroy n were gonna try to get it resolved. yay lol

they don't have our device so its hard to know what doesn't work. looking forward to testing the update

Sent from my HTC Glacier using xda premium
Sweet id switch back if it was fixed i like how its skinable
 
nckfrs
Old
#10  
Member
Thanks Meter 4
Posts: 65
Join Date: Aug 2009
i cant install any zip files i get unknown md5 error just rooted tonight

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes