Most of you are surely aware of TeamWin and their impressive work touch-based recovery interface concept. TWRP is such a known recovery with easy-to-use touch UI. Since the first day of the public release of Jelly-Bean source code, the team enrolled itself into the development of a new version of this amazing recovery and so, they have managed to introduce the users to TWRP 2.3
TWRP 2.3 may not offer you that many new features but it assures stability. The main aim of this version is the full re-write of the TWRP code into AOSP Jellybean source code, completely written in C++. Some of the zips may not work due to out-of-date update-binary, since TWRP now uses API 3 instead of 2.
Now, let’s proceed ourselves to the changes that have been made in 2.3 and its updated versions.
Changes In 188.8.131.52:
- Rebased onto AOSP Jelly Bean source code
- Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
- ADB sideload functionality from AOSP is included in 2.3.
- Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
- Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
- Faster boot times
- Added charging indicator while in recovery (only updates once every 60 seconds)
Changes In 184.108.40.206:
- Unmount system after boot to prevent some status 7 symlink failed errors on zip install
- USB Mass Storage code improvements
- Better handling of mounting storage during boot for some devices
- Fixed a problem with sizes of images (boot & recovery) after resetting defaults
- Fixed size errors during backup for some devices on recovery, etc.
- Fixed a problem with restoring backups when multiple archives were present
NOTE: backups from prior versions of TWRP are still compatible with 2.3
TWRP offers complete open-sourceness, so if you are interested in contributing then please head towards TWRP Github.
The link takes you to the TWRP 2.3 Page, downloads can be made by selecting your device on the top of the page. Good luck!