5,596,784 Members 48,061 Now Online
XDA Developers Android and Mobile Development Forum

[RECOVERY][crespo4g] 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 8579
Posts: 1,573
Join Date: Mar 2008
Location: KC MO

 
DONATE TO ME
Default [RECOVERY][crespo4g] 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 31 Users Say Thank You to Dees_Troy For This Useful Post: [ Click to Expand ]
 
Dees_Troy
Old
(Last edited by Dees_Troy; 7th October 2011 at 09:16 PM.)
#2  
Dees_Troy's Avatar
Senior Recognized Developer - OP
Thanks Meter 8579
Posts: 1,573
Join Date: Mar 2008
Location: KC MO

 
DONATE TO ME
Changelog - See our website!
 
Dees_Troy
Old
(Last edited by Dees_Troy; 17th August 2011 at 08:29 PM.)
#3  
Dees_Troy's Avatar
Senior Recognized Developer - OP
Thanks Meter 8579
Posts: 1,573
Join Date: Mar 2008
Location: KC MO

 
DONATE TO ME
FAQ:

How to install with Fastboot:

1. Download the fastboot binary for your computer from HTC
2. Connect your phone and boot it into fastboot
3. Run fastboot with the command
Code:

Code:
fastboot flash recovery path/to/recovery-twrp-crespo4g-1.0.3.img
Error when flashing some zip files:
twrp only supports the latest and greatest edify script for zip flashing. Please bug the zip developer to update the zip script to edify.

Does this back up the WiMAX partition?
That is an option if you chose, but you'll find it under "efs" and not wimax. Both the NS4G and the GSM Nexus S have an efs partition. The efs partition on the NS4G includes WiMAX along with some other fairly crucial data. It's a good idea to back up your efs separately (e.g. just pick efs and don't choose any other partitions) and keep this backup in a safe place.

Live support:
Click this link or join us in #twrp on Freenode IRC.
 
snandlal
Old
(Last edited by snandlal; 1st August 2011 at 02:33 PM.)
#4  
snandlal's Avatar
Senior Member
Thanks Meter 469
Posts: 1,949
Join Date: Apr 2010

 
DONATE TO ME
Yes. Thanks for this. Works great

So how will flashing our backed up images thru fastboot work since they are backed up as .win?

Uncle Jimmy says hello
The Following User Says Thank You to snandlal For This Useful Post: [ Click to Expand ]
 
ViViDboarder
Old
#5  
ViViDboarder's Avatar
Recognized Developer
Thanks Meter 616
Posts: 1,558
Join Date: Mar 2010
Location: San Francisco, CA

 
DONATE TO ME
Quote:
Originally Posted by snandlal View Post
Yes. Thanks for this. Works great

So how will flashing our backed up images thru fastboot work since they are backed up as .win?

Uncle Jimmy says hello
What partition?

Most are img files just with a different extension some are .tars. You can try it. :P If it doesn't work you can just restore.

Favorite Quotes: Emulators | Crysis

Nexus 7
Nexus 4 (CM10.2)
HTC One S (CM10) SOLD
Google Nexus One (CM7)
Touchpad (WebOS/CM9 with twrp 2) SOLD
ASUS Eee Pad Transformer (CM9) SOLD
EVO 3D (Mynz/CM9 + twrp 2) SOLD
EVO 4G (CM 7 + twrp 2) SOLD
iPhone 3G (whited00r) SOLD

Twitter | UbuntuForums Profile | MacRumors Forums | WinMatrix Profile

 
snandlal
Old
(Last edited by snandlal; 1st August 2011 at 02:57 PM.)
#6  
snandlal's Avatar
Senior Member
Thanks Meter 469
Posts: 1,949
Join Date: Apr 2010

 
DONATE TO ME
If i go in TWRP on my storage and look at the backed up images like system.win, data.win, boot.win. how would i use that image in fastboot if for some reason i couldnt get to recovery? Rename it to .img?

Uncle Jimmy says hello
 
Dees_Troy
Old
#7  
Dees_Troy's Avatar
Senior Recognized Developer - OP
Thanks Meter 8579
Posts: 1,573
Join Date: Mar 2008
Location: KC MO

 
DONATE TO ME
The .win files are either .tar or .tgz files (depending on whether you chose compression or not). The backups themselves are usually done with dd. So long as you're not messing with the recovery partition itself and leaving compression turned off, you should be good to go with fastboot flashing, though I don't have a NS4G myself to check.
 
AssassinsLament
Old
#8  
Recognized Developer
Thanks Meter 501
Posts: 735
Join Date: Jun 2007
Location: Twin Cities

 
DONATE TO ME
Quote:
Originally Posted by snandlal View Post
If i go in TWRP on my storage and look at the backed up images like system.win, data.win, boot.win. how would i use that image in fastboot if for some reason i couldnt get to recovery? Rename it to .img?

Uncle Jimmy says hello
No, you can not fastboot system/data/cache/sd-ext/.android_secure as those are essentially tgz. You can how ever fastboot or dd the others which are boot/recovery/efs by renaming it to .img
 
snandlal
Old
#9  
snandlal's Avatar
Senior Member
Thanks Meter 469
Posts: 1,949
Join Date: Apr 2010

 
DONATE TO ME
Quote:
Originally Posted by AssassinsLament View Post
No, you can not fastboot system/data/cache/sd-ext/.android_secure as those are essentially tgz. You can how ever fastboot or dd the others which are boot/recovery/efs by renaming it to .img
What? Ok so all im asking is.....the system.win in TWRP, can i rename that system.img and flash thru fastboot?

Uncle Jimmy says hello
 
Dees_Troy
Old
#10  
Dees_Troy's Avatar
Senior Recognized Developer - OP
Thanks Meter 8579
Posts: 1,573
Join Date: Mar 2008
Location: KC MO

 
DONATE TO ME
Quote:
Originally Posted by snandlal View Post
What? Ok so all im asking is.....the system.win in TWRP, can i rename that system.img and flash thru fastboot?

Uncle Jimmy says hello
You can fastboot these backups:
boot/recovery/efs

You cannot fastboot these:
system/data/cache/sd-ext/.android_secure

Hope that clears it up.

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

Advanced Search
Display Modes