You can swap the stock recovery environment for a custom one so you can start installing custom software and get root access if you like.

If the last time you installed a custom recovery image was back in 2011, then you probably only know the name Clockworkmod Recovery in the world of custom recoveries. Since then ClockworkMod has met its demise, which was primarily due to the arrival of TWRP Recovery, although if you were to read around the Web, you might see otherwise.

Both custom recovery images offered similar features, but TWRP has a touch-based interface whereas ClockworkMod only allowed for navigation to be done by using the Volume keys. Before ClockworkMod gave up development entirely, it created a Philz Touch Recovery which was supposed to rival TWRP since it too came with a touch-based interface. But the idea didn’t really kick off, people didn’t understand what Philz Touch was all about, and the writing was on the wall for all recoveries not named TWRP.

Since then four developers have been working many a day creating TWRP custom recovery images for hundreds of different devices. They also get help from people around the web who answer questions on forums such as the likes of XDA-Developers. There’s even an official TWRP app out now from the Google Play Store that, when available for a device, can make it possible to install the custom recovery without using ADB commands; all you need is root access instead, and then you just install it like any other root application.

Details of Note

  • The custom recovery images available in this guide are only to be installed on the OnePlus One smartphone. Most devices have a custom recovery image developed specifically for it, and you shouldn’t install one that is intended for another device unless advised it is okay by a professional.
  • The codename for the OnePlus One TWRP recovery image is “bacon.” You will see that codename in the TWRP image file path and also from your About Device menu so you know you are flashing the right file on the right device.
  • You can follow this guide on any of the major three computer operating systems: Windows, Mac, and Linux. You just need to download the right platform-tools file from the Android SDK package when you’re on the Android website, which is walked through during the guide below.
  • You can install the official TWRP Recovery application from the Google Play Store or from the TWRP website as an apk, if you have root access on the device already, and get the TWRP installed that way, no adb required. Once the app is installed, it will be in your Downloads folder. Navigate to the Downloads folder and select the TWRP application. When the application opens tap on the option for flashing the TWRP.

Files Required

How to Install TWRP Recovery on OnePlus One

If you already have TWRP installed on the OnePlus One smartphone, then you can just install the latest version of TWRP directly from the custom recovery itself by uploading it there. Achieving that would go as follows: download the TWRP to your computer, connect your device to the computer using the USB cable, transfer the TWRP file to the internal storage folder, disconnect the device from the computer and then boot it up into the Recovery mode where you would then flash the file.

For everyone else who hasn’t yet installed TWRP on the OnePlus One smartphone before now, you’ll need to do as follows:

1. Install the universal ADB drivers on the computer from the download link. That will make it possible for you to use adb commands as well as the OnePlus One smartphone. If you can’t get the OnePlus One smartphone connected to the computer, then you can also download the OnePlus USB drivers instead so the computer has both the ADB drivers and OnePlus drivers installed.

2. You need to have the platform-tools part of the Android SDK on your computer. From the download link, scroll down until you get to the command line tools section and then download the package that is made for your operating system.

3. Once you have the SDK Manager on your computer, check the box only for the platform-tools, so you end up with the adb and fastboot binaries installed on the computer.

You could also install the drivers from there as well if you wanted.

4. Pick up the OnePlus One smartphone and navigate to the Settings > About and tap your finger over the build number at least seven times so that the Developer Optionsmenu becomes unlocked. Then go back to the Settings, enter the Developer Optionsmenu and then enable the USB debugging mode.

5. Connect the OnePlus One smartphone to the computer by using the USB cable that it comes with.

6. Now on the computer open the Command Prompt and type the following command and hit Enter on your keyboard to get the OnePlus One smartphone into the bootloader mode and ready for the flashing:

adb reboot bootloader

7. Make sure you have copied the TWRP image file to the same folder as the adb and fastboot binaries. Also when you’re there, change the name of the TWRP to “twrp.img” by right-clicking the mouse pointer on it and selecting the Rename option from the menu.

8. From the command line type the following command and hit Enter on your keyboard to flash the custom recovery:

fastboot flash recovery twrp.img

9. Lastly type the following command and as soon as the OnePlus One smartphone reboots, hold down the key combination to boot directly into the recovery mode.

If you don’t sometimes the stock recovery will wipe over the custom recovery you just installed.

fastboot reboot

The custom recovery image for the OnePlus One smartphone is now installed, and you are ready to boot into recovery mode and start flashing the custom ROM or rooting zip files.

TWRP App Installation Method (Root Required)

If you decided to download the TWRP application from the Google Play Store or the APK file from the official TWRP website, then after you open the application you will be given a few different options to choose from. But before even going that far, it’s important to note that you should only install the TWRP APK file from the official TWRP website. If you’re installing it from Git, or any other file hosting website, it might not be the official version, and thus, it won’t have been built or tested by the official TWRP developers and maintainers.

Once the application is open, you’ll need to agree to not hold anyone from TWRP responsible for any issues that your device may face while using the application. This is a standard disclaimer that Team Win puts on top of each of the recovery image files from the official website as well, so it’s nothing new. It just explains that it is your decision to put the custom recovery on your device, and while they work hard to provide a quality product, there are no guarantees that your device isn’t susceptible to damages relating to TWRP while the custom recovery is installed. You can grant the application root permissions now as well. Root access can be obtained by flashing SuperSU, or other appropriate rooting files, from the custom recovery itself. Without root, you won’t have access to some of the app’s features, such as image flashing. It’s here also where you can enable InsightCore (a feature to monitor and record the network performance of your device).

Once you’ve accepted the agreements, you’ll see the TWRP application’s home screen, where you can choose to flash TWRP or view the network statistics. When choosing to flash the custom recovery, you’ll need to scroll and select your device from the list to make sure you are flashing the correct file. When the device is chosen, the TWRP application automatically then searches for the latest version of the TWRP for that device and will continue doing so every day for as long as the app is installed. This interval can also be altered from the Settings in the top right-hand corner of the device’s display when the apps open.

If root access has been enabled, you’ll see the chance to select the custom recovery image and the buttons for flashing the images to boot or from recovery. You should choose to flash the images to recovery. Only use the boot image flashing when you are flashing full boot images, not just kernel zimages.

That’s all.

Related Tutorials