Just about three months ago, we brought you news that the Team Win Recovery Project had received a massive update to version 2.1. April’s release largely heralded the start of a new age in recoveries—where one would no longer have to deal with cumbersome menus, instead interacting with a very user-friendly GUI.
It wasn’t simply about the GUI either. In addition to bringing an unrivaled level of UI polish, TWRP 2.1 offered users many advanced features such as update.zip queuing, a basic file manager, and dual storage support for Nandroid backups. Additionally, TWRP added support for the open source scripting engine OpenRecoveryScript, which works in conjunction with the previously covered GooManager.
How do you follow up something as revolutionary as TWRP 2.1? With TWRP 2.2, of course. That’s how! The new release builds on the previous offering by delivering many recovery “firsts.” For starters, this is the first recovery to feature on on-screen keyboard. Why would you want such a thing? How about naming and renaming Nandroid backups! TWRP 2.2 is also the only recovery to split extremely large backups, allowing users to backup and restore /data partitions larger than the 2 GB FAT32 file size limit.
In the words of XDA Recognized Developer Dees_Troy:
- On-screen keyboard in recovery! — supports long press, backspace repeat, and swipe left deletes everything left of the cursor
- Name new backups and rename existing backups
- Rename files and folders in the file manager
- Pseudo-terminal emulator
- Support decrypting an encrypted data partition on Galaxy Nexus (enter password using keyboard)
- Backup archive splitting — allows backup and restore of data partitions larger than 2GB
- Simplified XML layout support between resolutions
- Added dual storage selection radio buttons to zip install, backup, and restore pages
- Improved zip install compatibility
- Updated update-binary source code
- Numerous small bug fixes and improvements
Eager to get started? I know I am. Head to the links below to obtain the appropriate version for your device: