Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,804,709 Members 47,138 Now Online
XDA Developers Android and Mobile Development Forum

[TOOL/UTILITY][TWRP][ 2.7][RECOVERY] TWRP 2.7.2.1 TeamWin Recovery Project 6/21

Tip us?
 
bigbiff
Old
(Last edited by bigbiff; 21st June 2014 at 10:18 PM.)
#1  
Recognized Developer - OP
Thanks Meter 3,663
Posts: 4,140
Join Date: Jun 2010

 
DONATE TO ME
Default [TOOL/UTILITY][TWRP][ 2.7][RECOVERY] TWRP 2.7.2.1 TeamWin Recovery Project 6/21

Default [RECOVERY] [6/21/14] TWRP 2.7.2.1 - TeamWin Recovery Project

TeamWin is proud to present TWRP 2.7.2.1 for the Samsung Galaxy Note 2 (Verizon)!



Youtube video: http://www.youtube.com/watch?v=RIvWVS_Rkxo

Full TeamWin credits are on the TWRP page on the TeamWin website: http://teamw.in/project/twrp2

Introduction:

Team Win Recovery Project or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's 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.

Key Features:

Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Decryption of /data
Easy selection of internal/external storage
See changelog below for new features

In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe cache & dalvik, and run a backup.

We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.

Theming:

Information on TWRP 2 Theming - http://teamw.in/project/twrp2themers

Known Issues:

CWM backups are not compatible - please make a fresh backup in TWRP as soon as you have flashed it


Source Code:

GitHub - https://github.com/omnirom/android_bootable_recovery

Gerrit Instance - http://gerrit.omnirom.org

If you have made your own twrp build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.

t0ltevzw Device Config: https://github.com/TeamWin/android_d...msung_t0ltevzw

Kernel: https://github.com/bigbiff/android_k...msung_smdk4412

DOWNLOAD:

All official devices are listed at the top of the page on the Team Win website. Search for the device in the textbox.

http://teamw.in/project/twrp2


Support:

Click http://webchat.freenode.net/?channels=twrp for live support or join us in #twrp on Freenode IRC servers
Phone: OPPO Find 7 QHD
ROM: Cyanogenmod 11
64 GB Class 10 Sandisk



If you need help please, please, please, please post recovery.log.
1. adb pull /tmp/recovery.log or Advanced->Copy Log to SDCard
2. Upload /tmp/recovery.log or /sdcard/recovery.log to http://paste.tinyw.in

How to submit a bug report!

Support: Click http://webchat.freenode.net/?channels=twrp for support or join us in #twrp on Freenode IRC servers
The Following 45 Users Say Thank You to bigbiff For This Useful Post: [ Click to Expand ]
 
bigbiff
Old
(Last edited by bigbiff; 21st June 2014 at 10:18 PM.)
#2  
Recognized Developer - OP
Thanks Meter 3,663
Posts: 4,140
Join Date: Jun 2010

 
DONATE TO ME
Default Changelog

2.7.2.1
- fix formatting emmc partitions

2.7.2.1
- fix formatting emmc partitions

2.7.2.0
All thanks to @Dees_Troy
- fix crash in setting contexts on datamedia
- fix restoring data partition as f2fs after formatting f2fs
- mount data after being formatted

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. 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

2.7.0.1
Update with fix for splitting system

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.

 

2.6.3.2
Add F2FS Support

2.6.3.1
Add SELINUX support

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
Move exfat to GPL kernel module for bugs with exfat-fuse

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

2.6.0.1
Fix Data being listed twice in advanced wipe

2.6.0.0
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
Can encrypt a backup to prevent theft of private data from your backup files
Updated graphics / icon courtesy of shift
Updated exFAT to latest commits
Fixed a problem with Samsung TouchWiz decryption
Update SuperSU binary
Fixed saving of backup partitions list
Fixed saving of last used zip install folder
Fixed backup of datadata on devices that use a separate partition for datadata
Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
Fixed some problems with partitioning a SD card
Various other bug fixes and tweaks

Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.

Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.

2.5.0.1
Fix decryption of encrypted devices.

2.5.0.0
Added scrollable partition lists for mount, backup, restore, wipe, and storage selection
Add new SliderValue GUI element for selecting brightness and screen timeout (thanks to Tassadar)
Re-work AOSP and TWRP code to improve license compatibility between GPL and Apache
Fixed a problem with directory permissions on split archive backups
Fixed a problem with md5 verification of backups
Added a search function to libtar (thanks to kokotas)
Improve handling of XML errors (fix permissions)
Fixed handling of subpartitions
Improvements to recovery.fstab flags
Fixed a problem with decryption not being able to locate the decryption key in some situations

2.4.4.0
Added another libtar hardlink workaround to fix restore of some backups (usually related to Ubuntu Touch)
More fixes for the file selector
Switched from using busybox md5sum to a direct C function call
Fixed capturing the exit status of tar based backups/restore - TWRP will display that there was an error if there was one again
Update exFAT to latest commits
Added a build flag to disable using the ioctl for screen blanking

2.4.3.0
Fixed 2 bugs related to restore, one dealing with mknod failures (by bigbiff) and one dealing with restoring hardlinks (by Dees_Troy)
NOTE: If your backups weren't restoring correctly in earlier 2.4.x versions they should restore correctly now. Hopefully you didn't delete those backups. If you're still having problems, run the restore, go to advanced and copy log, then give us the log. Complaints without logs will be rightfully ignored.
Added a scroll bar to file selectors and listboxes courtesy of Tassadar
Added libblkid for more accurate detection of file systems and can now detect exFAT properly thanks to bigbiff
Added a screen dim effect 2 seconds before screen off on some devices
Finally fixed file selector crash (one of the joys of working with multi-threaded software)
Fixed loading of screen timeout setting during startup
Improvements and bugfixes to screen timeout code
Fix Military Time setting persisting

2.4.2.0
Add screen timeout - screen will turn off automatically after 60 seconds, saves battery and prevents screen burn-in especially on AMOLED devices
Add a brightness setting (requires device specific setup and only some devices have been added)
Add a root checker and offer to install SuperSU if the device isn't already rooted
Add a write buffer to libtar backups, significant improvements to speeds when backing up to exFAT target, minor improvements for other file systems
Check and offer to fix root permissions if broken
Add an option for a 24 hour clock display instead of AM/PM (aka military time)
Move stock recovery reflash check to occur during the reboot cycle
Add support for some MTK6xxx devices
Change libtar to vfork to help prevent memory problems
Add a "clicked" effect to most buttons, file selector, and listbox
Improve timezone listbox to be more like file selector (per pixel kinetic scrolling, etc)
Remove some no longer used settings (Forced MD5 sum on zips, size checking on image backups)
Other minor bugfixes and improvements

2.4.1.0
Fix exfat and vfat detection
Fix formatting vfat past 2 GB

2.4.0.1
Revert to using kernel modules for exFAT for performance


2.3.3.2

Uploaded with the following debrick fix courtesy of AndreiLux: https://github.com/AndreiLux/Perseus...45f37bcbae2951

2.3.3.1

Updated Kernel due to this recommendation from AndreiLux: http://forum.xda-developers.com/show....php?t=2057364

2.3.3.0
Increased Brightness
Added better handling of wiping on /data/media devices with Android 4.2 to help prevent multiple upgrades of the file system for multiple users
NOTE: It is not recommended to jump back and forth between 4.1 and 4.2 ROMs. If you do, this may trigger additional upgrades and you will have to manually move your files back to the "single user" layout when going back to 4.1.

Fixed renaming of backups when a space is present
Added decrypt button to mount page if you cancel decryption during boot
Added ignore blkid flag support
Fixed handling of MTD partitions during mount
Fixed some keyboard mapping issues on 800x1280 layout
Phone: OPPO Find 7 QHD
ROM: Cyanogenmod 11
64 GB Class 10 Sandisk



If you need help please, please, please, please post recovery.log.
1. adb pull /tmp/recovery.log or Advanced->Copy Log to SDCard
2. Upload /tmp/recovery.log or /sdcard/recovery.log to http://paste.tinyw.in

How to submit a bug report!

Support: Click http://webchat.freenode.net/?channels=twrp for support or join us in #twrp on Freenode IRC servers
The Following 9 Users Say Thank You to bigbiff For This Useful Post: [ Click to Expand ]
 
bigbiff
Old
(Last edited by bigbiff; 28th December 2012 at 11:45 PM.)
#3  
Recognized Developer - OP
Thanks Meter 3,663
Posts: 4,140
Join Date: Jun 2010

 
DONATE TO ME
FAQ

Q. What partitions should I backup?
A. For the first backup I recommend system, data, boot, efs and modem. Subsequent backups for rom testing are system, data and boot.
Phone: OPPO Find 7 QHD
ROM: Cyanogenmod 11
64 GB Class 10 Sandisk



If you need help please, please, please, please post recovery.log.
1. adb pull /tmp/recovery.log or Advanced->Copy Log to SDCard
2. Upload /tmp/recovery.log or /sdcard/recovery.log to http://paste.tinyw.in

How to submit a bug report!

Support: Click http://webchat.freenode.net/?channels=twrp for support or join us in #twrp on Freenode IRC servers
The Following 3 Users Say Thank You to bigbiff For This Useful Post: [ Click to Expand ]
 
mazz0310
Old
#4  
Senior Member
Thanks Meter 18
Posts: 143
Join Date: Dec 2007
Awesome, very glad to see this.

Do you know, is it worth flashing this over the one that came with the bootloader unlock or are they basically the same?
The Following User Says Thank You to mazz0310 For This Useful Post: [ Click to Expand ]
 
*Madmoose*
Old
#5  
Senior Member
Thanks Meter 165
Posts: 551
Join Date: Aug 2011
Version 2.3.2.3 is the version that is installed with the unlock procedure. Looking at the version number in the OP...they are the same.
 
bigbiff
Old
#6  
Recognized Developer - OP
Thanks Meter 3,663
Posts: 4,140
Join Date: Jun 2010

 
DONATE TO ME
Quote:
Originally Posted by *Madmoose* View Post
Version 2.3.2.3 is the version that is installed with the unlock procedure. Looking at the version number in the OP...they are the same.
Good to know since I don't have the vzw variant myself. This will be just a placeholder for new releases since I guess everyone will have TWRP by default.
Phone: OPPO Find 7 QHD
ROM: Cyanogenmod 11
64 GB Class 10 Sandisk



If you need help please, please, please, please post recovery.log.
1. adb pull /tmp/recovery.log or Advanced->Copy Log to SDCard
2. Upload /tmp/recovery.log or /sdcard/recovery.log to http://paste.tinyw.in

How to submit a bug report!

Support: Click http://webchat.freenode.net/?channels=twrp for support or join us in #twrp on Freenode IRC servers
 
imnuts
Old
#7  
imnuts's Avatar
Recognized Developer
Thanks Meter 2,977
Posts: 3,418
Join Date: Jul 2007
Location: West Chester

 
DONATE TO ME
Quote:
Originally Posted by *Madmoose* View Post
Version 2.3.2.3 is the version that is installed with the unlock procedure. Looking at the version number in the OP...they are the same.
Just re-read AdamOutlers post and it looks like he's using TWRP from the Sprint GNote2. This looks like it was setup specifically for the Verizon version, but the hardware is probably similar enough that it doesn't matter much.
Setup a Development Environment
Setup and Use the Android SDK
Stock Odin Restore files

You can find the answer to all of your questions right here. If that doesn't work, then try this or this
The Following User Says Thank You to imnuts For This Useful Post: [ Click to Expand ]
 
winco209
Old
#8  
winco209's Avatar
Senior Member
Thanks Meter 14
Posts: 179
Join Date: Dec 2012
Location: merced ca
Default problem twrp wont zip files getting error messages

I unlock my device then boot into twrp then try to flash jelly beans rom and I keep getting error cant find md5
 
bigbiff
Old
#9  
Recognized Developer - OP
Thanks Meter 3,663
Posts: 4,140
Join Date: Jun 2010

 
DONATE TO ME
Quote:
Originally Posted by winco209 View Post
I unlock my device then boot into twrp then try to flash jelly beans rom and I keep getting error cant find md5
Disable md5 checking...
Phone: OPPO Find 7 QHD
ROM: Cyanogenmod 11
64 GB Class 10 Sandisk



If you need help please, please, please, please post recovery.log.
1. adb pull /tmp/recovery.log or Advanced->Copy Log to SDCard
2. Upload /tmp/recovery.log or /sdcard/recovery.log to http://paste.tinyw.in

How to submit a bug report!

Support: Click http://webchat.freenode.net/?channels=twrp for support or join us in #twrp on Freenode IRC servers
 
bigbiff
Old
#10  
Recognized Developer - OP
Thanks Meter 3,663
Posts: 4,140
Join Date: Jun 2010

 
DONATE TO ME
Quote:
Originally Posted by imnuts View Post
Just re-read AdamOutlers post and it looks like he's using TWRP from the Sprint GNote2. This looks like it was setup specifically for the Verizon version, but the hardware is probably similar enough that it doesn't matter much.
Yeah I am using the vzw build.prop from a system dump a while back. Also if that's true, sprint has different partitions.

ASAP:

ls -l /dev/block/platform/dw_mmc/by-name
cat /proc/partitions
Phone: OPPO Find 7 QHD
ROM: Cyanogenmod 11
64 GB Class 10 Sandisk



If you need help please, please, please, please post recovery.log.
1. adb pull /tmp/recovery.log or Advanced->Copy Log to SDCard
2. Upload /tmp/recovery.log or /sdcard/recovery.log to http://paste.tinyw.in

How to submit a bug report!

Support: Click http://webchat.freenode.net/?channels=twrp for support or join us in #twrp on Freenode IRC servers

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes