FORUMS

CloudPlayer: DIY HiFi Music Streaming Solution

In our Helpful Guide to Music Streaming Services, we mentioned several different services … more

Optimize Battery Life with This Useful App

Battery life is an important aspect of your smartphone, especially if you use it for more … more

The OnePlus 2 & The Year of Smartphone Compromises

We are very close to entering the last third of 2015, and we have now seen many of … more

OnePlus 2 Teardown, Major Android Vulnerability – XDA TV

The OnePlus 2 has been officially released. That and much more news is … more

[RECOVERY][lt02ltetmo] TWRP 2.8.7.0 touch recovery [2015-06-23]

1,657 posts
Thanks Meter: 10,763
 
Post Reply Subscribe to Thread Email Thread
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.8.7.0:

-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)

Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.

System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.

resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.

This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.

CHANGELOG for 2.8.6.0:

-Fix daylight savings time rules for USA and Europe (_that)
-Allow mulitple overlays for popup boxes (Dees_Troy)
-Add pattern style password entry for decrypt (Tassadar)
-Keyboard improvements (_that)
-Update AOSP base to 5.1 (Dees_Troy)
-Reduce theme count to 5 and rely on scaling (Dees_Troy)
-Various scaling improvements (Dees_Troy)
-Improved handling of resources in the GUI (_that)
-Make scroll bar size proportional to list size (_that)
-Allow scoll lists to render without a header (_that)
-Make console scroll per pixel with kinetic scrolling (_that)
-Support styles in XML to reduce XML size and improve consistentcy (Dees_Troy)
-Various other fixes and improvements (mdmower, bigbiff, codelover, etc)

CHANGELOG for 2.8.5.0:

-Scale the GUI - TWRP can read the theme's resolution and scale it up or down to fit the theme to your screen's resolution
-Backups can now be cancelled while the backup is in progress (does not include restore because we don't want to leave your device in a bad state)
-Improve thread handling and move input handling into the main rendering thread to improve stability
-Make MTP work even if unplugged and plugged back in
-Unify scrollable list code and make kinetic scrolling feel more natural
-Fix handling of mapped zip files for OTA updates (CM12 updater)
-USB keyboards should now work on all devices that support USB host mode via a USB OTG cable
-Other small fixes and improvements

CHANGELOG for 2.8.4.0:

-Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
-Fix some MTP related crashes and bugs
-Eliminate TWRP toggling USB IDs during boot if MTP is enabled
-Fix various adb sideload issues
-Improve threading of actions
-Eliminate separate thread for screen timeout
-Update libblkid to 2.25.0
-Use power button as back button on watch themes for easier navigation
-Add mutex locking to data manager
-Improve custom theme handling on encrypted devices
-Allow the stock theme to be offset by build flags so we can center a lower res theme on a higher res screen especially for watches with round screens

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 NEW website! NOTE that the 2.8.6.0 version is ONLY available on our new site and is not available on our other, older mirrors!

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.
Last edited by Dees_Troy; 23rd June 2015 at 02:53 PM.
 
 
2nd May 2015, 04:21 AM |#2  
Dees_Troy's Avatar
OP Senior Recognized Developer
Flag KC MO
Thanks Meter: 10,763
 
Donate to Me
More
Note, this is for the LTE T-Mobile model only. It may work on other LTE models. I seriously doubt that it will work on the Wi-Fi only model as it uses a completely different chipset.

Device specific page with instructions for a manual install.

Direct download link for all current and past versions.
Last edited by Dees_Troy; 2nd May 2015 at 04:25 AM.
2nd May 2015, 05:51 AM |#3  
gr9nole's Avatar
Senior Member
Flag sakarya
Thanks Meter: 49
 
More
Support Sm-t210 ?
2nd May 2015, 02:56 PM |#4  
Dees_Troy's Avatar
OP Senior Recognized Developer
Flag KC MO
Thanks Meter: 10,763
 
Donate to Me
More
Quote:
Originally Posted by gr9nole

Support Sm-t210 ?

T210 is the Wi-Fi only model which uses a Marvell chipset instead of the Qualcomm chip found in the LTE models. This makes the 2 devices completely different internally and thus a completely different recovery would be needed for the T210.
The Following User Says Thank You to Dees_Troy For This Useful Post: [ View ]
3rd May 2015, 03:59 AM |#5  
rookie12's Avatar
Senior Member
Thanks Meter: 128
 
More
Quote:
Originally Posted by Dees_Troy

T210 is the Wi-Fi only model which uses a Marvell chipset instead of the Qualcomm chip found in the LTE models. This makes the 2 devices completely different internally and thus a completely different recovery would be needed for the T210.

Stupid question
Is it for the sm t210r?
3rd May 2015, 09:42 AM |#6  
jstath1972's Avatar
Senior Member
Thanks Meter: 551
 
More
Quote:
Originally Posted by gr9nole

Support Sm-t210 ?

Quote:
Originally Posted by rookie12

Stupid question
Is it for the sm t210r?

It's for SM-T217T.
3rd May 2015, 09:43 AM |#7  
gr9nole's Avatar
Senior Member
Flag sakarya
Thanks Meter: 49
 
More
Quote:
Originally Posted by jstath1972

It's for SM-T217T.

Understand
15th May 2015, 01:25 PM |#8  
mai77's Avatar
Senior Member
Thanks Meter: 561
 
More
Thumbs up T110 users are in the game now !
paziusss has now provided a TWRP 2.6.3.0,

which has got NO BOOT LOOP on T110.

great progress, since before last week T110 users had to reflash recov on a single use basis

maybe TWRP ver. 2.8.6.0 can be adapted for tab3 lite T110 too, at some point ...
18th May 2015, 01:45 AM |#9  
SwoRNLeaDejZ's Avatar
Senior Member
Flag Taunton
Thanks Meter: 259
 
More
Guys, can you please try to read the OP and the second post before flooding this thread with "haz support for t210 plz?".

This was made for the LTE models only, specifically the T217T and will NOT work on the WiFi only models.. None of them.
Post Reply Subscribe to Thread

Tags
recovery, team win, teamwin, twrp
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes