Xiaomi Releases Kernel Source Code For Mi4i

If you’ve been following the XDA News Portal lately, you might have noticed an … more

How to Listen to Beats 1 on Android Right Now

If you felt a bit left out by Apple launching their own online radio station Beats 1 … more

NVidia SHIELD TV – XDA TV Device Review

The SHIELD TV is a not an Android smartphone device. However, that doesn’t mean it … more

PSA: Having cellular connectivity or texting issues tonight?

You’re not alone…Tonight, many users are experiencing a myriad … more

[RECOVERY][grouper] TWRP touch recovery [2015-06-23]

1,656 posts
Thanks Meter: 10,684
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:


-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 and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at to help us keep devices up to date and working.


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


-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


-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

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
You can find more information and download links on our NEW website! NOTE that the version is ONLY available on our new site and is not available on our other, older mirrors!

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!

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:52 PM.
The Following 261 Users Say Thank You to Dees_Troy For This Useful Post: [ View ]
17th July 2012, 07:30 PM |#2  
Dees_Troy's Avatar
OP Senior Recognized Developer
Flag KC MO
Thanks Meter: 10,684
Donate to Me
The Following User Says Thank You to Dees_Troy For This Useful Post: [ View ]
17th July 2012, 07:39 PM |#3  
Rafase282's Avatar
Senior Member
Flag Bronx
Thanks Meter: 326
Donate to Me
I'm going to try this as soon as the UPS guy drops by with my N7.
Meanwhile, would it be possible to add support for the G2X?

I'm using a port and it has a few bugs besides being outdated.

Edit: Updating to 2.3 thanks a lot!
Last edited by Rafase282; 12th October 2012 at 06:58 PM.
17th July 2012, 07:42 PM |#4  
clockcycle's Avatar
Senior Member
Flag Miami, FL
Thanks Meter: 410
Nice, looks impressive. Thanks for sharing.
17th July 2012, 07:44 PM |#5  
DJLamontagneIII's Avatar
Recognized Contributor
Flag Mom's Basement
Thanks Meter: 3,984
Donate to Me
No issues so far and looks really sweet...thanks allot man

Sent from my Nexus 7 using Tapatalk 2
Last edited by DJLamontagneIII; 17th July 2012 at 07:53 PM.
17th July 2012, 07:52 PM |#6  
Senior Member
Thanks Meter: 118
Big fan of TWRP thanks alot, the only issue which also exists with CWM is that you can't enter recovery from the bootloader. Thanks A lot.
17th July 2012, 08:11 PM |#7  
Senior Member
Thanks Meter: 1,152
Is this compatible with say a future Rom with aroma installer?

Sent from my HTC Sensation 4G using xda premium
17th July 2012, 08:25 PM |#8  
LostInNorth805's Avatar
Senior Member
Flag Oxnard,CA
Thanks Meter: 40
Originally Posted by Rafase282

I'm going to try this as soon as the UPS guy drops by with my N7.
Meanwhile, would it be possible to add support for the G2X?

I'm using a port and it has a few bugs besides being outdated.

Its already in the development section for the G2X

Sent from my Nexus 7 using xda premium
17th July 2012, 08:49 PM |#9  
Rafase282's Avatar
Senior Member
Flag Bronx
Thanks Meter: 326
Donate to Me
Originally Posted by LostInNorth805

Its already in the development section for the G2X

Sent from my Nexus 7 using xda premium

It is a port not from the creator as far as I know I could be wrong and again, it is outdated and with bugs.

On a topic related notice, I just got my N7. Charging it to update it.

I'm reading the guides but any particular one that any of you used and proved suspenseful?
The Following User Says Thank You to Rafase282 For This Useful Post: [ View ]
17th July 2012, 08:50 PM |#10  
Senior Member
Thanks Meter: 545
So will this have the same reboot/sticking issues that CWM does?
Post Reply Subscribe to Thread

nexus 7, recovery
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes