*** Disclaimer *** All flashing is done at your own risk! While nothing from this thread should break your device, don't come back here blaming anyone if it does!
Team Win Recovery Project 3.x, or twrp3 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!
Fastboot Install Method:
You will need the platform-tools from the Android SDK on your computer. Find the Android command line tools section on the page linked and install the SDK tools package. From the SDK Manager, download only the platform-tools to get adb and fastboot binaries.
Windows users will need proper drivers installed on their computer. You can try the Naked ADB drivers or the Universal ADB drivers if you don't already have a working driver installed
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging. From your computer, open a command prompt and type:
You should now be in fastboot mode.Code:
adb reboot bootloader
Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
fastboot flash recovery_a twrp.img fastboot flash recovery_b twrp.imgAlternate Installation Method (requires prior TWRP installation):Code:
TWRP Image Install method:
Most devices can be updated quickly and easily within TWRP if you already have version 22.214.171.124 or higher installed. NOTE: This will only flash TWRP to the active slot!
- Download the latest version of TWRP appropriate for your device/firmware
- Reboot to TWRP
- Hit Install and tap the "Install Image" button in the lower right
- Browse to the location of the TWRP image on your device and select it
- Select recovery from the partition list and swipe to flash
TWRP Official Change Log
Frequently Asked Questions (FAQ)
If you have an issue, the first step is to post a recovery log so we can determine the cause of the issue. This is done in recovery using Advanced -> Copy Log, or adb pull /tmp/recovery.log. Once a log is uploaded we can determine how best to proceed. NOTE: Posts that are reporting bugs or issues without an accompanying recovery log will be ignored! Additionally, providing details about your device setup, including variant, firmware version, and exact steps to reproduce your issue will also be helpful in diagnosing the problem.
If your issue is determined to be 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 contact us via our website. 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!