1.What is Clockworkmod recovery (CWM)?
ClockworkMod recovery (CWM) is a modified unofficial recovery that is released for most devices running Android. It has much more capabilities than native recovery. On some devices it is installed instead of native recovery, on other devices it is installed in parallel. Allows you to:
If you can not turn on the phone and download android, you can always restore through CWM a previously created backup with all the applications and settings.
2.The menu structure of CWM Recovery
Reboot system - reboot the device
apply update.zip from sdcard - install the file update.zip, located in the root of the memory card sdcard \
wipe data / factory reset - full reset of settings and data, while the / data and / cache partitions are cleared in the internal memory of the device and the ".android_secure" system folder on the memory card is cleared
wipe cache partition - cleaning the partition / cache in the internal memory of the device
install zip from sdcard - install zip file from memory card
backup and restore - creating and restoring a backup
mounts and storage - mount and drive
advanced - additional
3.Navigate the menu
On all devices, CWM control is performed in different ways. But most devices use the following scheme:
On some devices, additional buttons are also used, for example, to return to the previous menu. The latest versions of CWM support screen clicks.
In CWM touch, the control is performed by pressing the desired functions.
If you make 5 swipes menu up and down, then turn on the "Rainbow mode" (multicolored menu items).
4.Clockworkmod recovery firmware
Installing CWM via RomManager is not suitable for all devices.
1) Install recovery via fastboot.
The native way of installing any recovery for Android devices is firmware recovery via fastboot in the recovery section of the phone. This method is preferable. How to enter fastboot mode and where to get the files for its work, read in the subject of firmware of your device, the methods and files are different everywhere. This method is suitable only for devices on which the boot loader is unlocked and on which there is a recovery partition. Recovery is stitched with the command:
fastboot flash recovery.img
fastboot - the name of the fastboot executable
recovery.img - the name of the image from the recovery
2) Installation of recovery in other ways.
On some devices, with a locked bootloader, or write protection for certain partitions, or to save a warranty, or if there is no recovery partition, or for other reasons, the recovery can be stitched either to the boot partition or to the system partition. It happens accordingly, either with the kernel firmware, or with the installation application.
3) Install recovery through the flash driver from the computer.
In this case, the firmware is used on the computer and its files go to it. For example, for Samsung it's Odin. For Motorola RSD Lite and so on.
5.Firmware CWM Recovery for complex devices.
7.Installing zip files
8.Structure of zip files
ZIP files are ordinary archives, which differ in that they contain firmware files and installation instructions (the META-INF folder). This is the instruction for CWM, which describes which files to copy and where, what to remove, what permissions they have to expose, and other actions that need to be performed when installing this ZIP, for example wipe, img image installation and etc. The firmware data in the archive lies in the same sections as they will be located in the device's memory. Sections in the archive can be represented as folders with files (the folder name exactly coincides with the name of the corresponding section in the internal memory), and in the form of images img. The boot partition can only be stitched in an image. Regardless of the purpose of this or that zip, zip'y for CWM can be distinguished by opening the archive as an ordinary archiver, inside there should be a folder "META-INF".
META-INF \ com \ google \ android \ update-script - this file contains the installation instructions, you can open it with a text editor, for example "notepad ++", and rewrite it if necessary. The new ZIP in the folder META-INF \ com \ google \ android contains two files "updater-script" and "update-binary" - by the presence of the second one you can define the file for the old CWM or for the new one. The old CWM is 2. *, new - 3. * and higher.
List of some commands that you can use in the zip statement
9.Creating and restoring a backup copy of the firmware (nandroid)
CWM recovery allows you to create a backup copy of the firmware of the device (not all partitions), such a backup is called nandroid. CWM reserves the boot, system, data, cache partitions in the device's internal memory and the ".androidsecure" folder on the device's memory card, if there are other partitions, for example, an ext partition on the memory card, or a webtop partition (only on some motorola devices) their backup. The sections with the firmware of the radio module, the camera (for some samsung devices) and the loader are not reserved. If there are other partitions on your device, it's best to clarify them in the appropriate firmware topic. Not only the operating system is backed up, but all settings and installed applications. Starting with the fifth version, CWM creates a backup copy in the tar archive, which is very convenient, because it can be opened by an ordinary archiver, for example WinRar. In older versions of CWM, the backup copy is a copy of all the partitions in the img images. The resulting backup can only be restored from the phone and only through the CWM. The device must have ClockWorkMod recovery installed.
- Run CWM recovery
- Select "Backup & restore"
- Select "backup"
- Select "YES"
- Select Reboot system now (reboot)
After that, a full backup will be added to the memory card in the clockworkmod / backup folder. The name of the backup includes the time and date of its creation, but the name can be given arbitrary, of course Latin alphabet without spaces
10.How to get root with recovery?
To get root on any version of the android and on any device it's enough to install superSU via non-native recovery: