|TeamWin Recovery Project|
|Lizenz||GPL version 3|
|Entwickler||Team Win, Ethan Yonker, bigbiff|
The TeamWin Recovery Project (short TWRP) is an alternative, manufacturer-independant [[Recovery systems for several Android devices. It is based on the AOSP-Android-Recovery, extended with several features and it's own user interface. The Recovery is fully touchscreen-based and can not be controlled using the volume keys (up and down) as well as not with the power key to select menu entries.
In difference to the ClockWorkMod, TWRP provides a built-in file manager, different themes as well as other advanced options for backup, wipe and restore (e.g only backup or restore some partitions, bypass the MD5-checksum creation or choose an own name for a data set like backups). The installation of zip files provides a way of adding multiple zip files (up to 10) in a so called Batch-Job, which are processed one after one.
To use the TeamWin-Recovery, it has to be installed on the device. This is done with the fastboot command "flash". It's required, that the USB driver for the device is installed correctly and that the fastboot.exe is present, which is, e.g., shipped with the Android SDK, but can also be installed standalone. The recovery itself can be retrieved/downaloded as an image file (*.img). This file needs to be copied in the same directory where the fastboot.exe is saved in (for simplicity) and renamed to recovery.img.
Afterwards, a command line window is opened [WINDOWS] + [R] -> "cmd" -> [RETURN]) and, within this window, navigated to the directory, where the fastboot.exe is saved in (you can use the windows command to navigate through directories in the command line, followed by the directory path, e.g.: cd C:\android\fastboot).
To proceed, the android device needs to be connected to the computer using the USB cable, followed by executing the following command in the same command line window, which was used before:
fastboot flash recovery recovery.img
After the successful flash of the recovery (which is noted with a success message in the command line window), the device can be started into the recovery-system out of the bootloader. The TeamWin Recovery is now installed successfully.
ADB in recovery
If the android device is started in the TeamWin recovery, you can execute ADB commands against the device. If, during the use of the adb, the command is rejected with the message device not found, you should check, if the correct USB drivers for the device are installed, and, in case of using the Windows operating system, you should check, if the device is correctly recognized in the Windows device manager.
The OpenRecoveryScript is a, licensed under the GNU GPL Version 2.0 (and therefore open-source), Scripting-Engine, which allows the script-based execution of Recovery commands. Because the engine is open-source and licensed under a free license, it can be used by anyone for anything, which was an advantage over the extendedcommands implementation, which was used in the ClockWorkMod.
Using a simple text file, saved in the /cache/recovery/ directory with the name openrecoveryscript, the recovery can be instructed to execute the described set of commands during the startup, e.g. the installation of a zip archive such as a ROM, or the deletion of a partition.
Creating a screenshot inside of TWRP
- A screenshot can be created using the same shortcut as in the android system itself by pressing POWER+VOLDOWN at the same time.
- The screenshot image is saved on
- the internal sd card (/sdcard/Pictures/Screenshots) or
- the external sd card (/external_sd/Pictures/Screenshots) if you installed something from there or saved a backup on it.
- To change the location where the screenshot should be saved, simply navigate to the Install menu and select the Storage: ***** part at the top where you can change the storage, which is also used as the partition where screenshots are saved to.
- "Team-Win-Recovery-Project/openrecoveryscript.cpp at android-5.0 · TeamWin/Team-Win-Recovery-Project". Abgerufen am 2015-02-28.
- "OpenRecoveryScript - RootzWiki". Abgerufen am 2015-02-28.