Key facts
- Learn what ClockworkMod Recovery does, why CWM is now a legacy choice, and how to select, install, boot, back up, or replace recovery without guessing.
- ClockworkMod Recovery is a legacy custom recovery, not a universal download for every Android device.
- Use CWM only when a trustworthy device-specific guide identifies the exact model, codename, image, and installation method.
ClockworkMod Recovery, usually shortened to CWM, is a legacy custom recovery for Android phones and tablets. It gave older devices a menu for installing compatible update ZIP files, wiping selected partitions, and creating partition-level backups. CWM was important to early Android modding, but it is not a current universal recovery and it does not automatically root a device.
Do not install a recovery image selected only by processor, screen size, or a similar model name. A wrong image can leave the device unable to start recovery or Android. Use an exact device codename, board revision, boot layout, and trusted device-specific instructions.
Quick answer: should you install ClockworkMod Recovery?
- ClockworkMod Recovery is a legacy custom recovery, not a universal download for every Android device.
- Use CWM only when a trustworthy device-specific guide identifies the exact model, codename, image, and installation method.
- For a currently supported device, prefer the recovery named by its active ROM or device maintainer, such as a device-specific TWRP or Lineage Recovery build.
- Back up personal files separately because a recovery backup may exclude internal shared storage, photos, downloads, and encrypted data.
- Expect bootloader unlocking to erase user data when the manufacturer supports unlocking.
If you are repairing an old phone that already has CWM, the menu can still be useful. If you are installing a recovery today, first confirm whether the device even has a separate recovery partition. Modern A/B and Virtual A/B devices often store recovery resources in boot-related partitions, so an old fastboot flash recovery guide may target a partition that does not exist.
What ClockworkMod Recovery is
Android recovery is a small boot environment used for maintenance tasks outside the normal operating system. Stock recovery normally installs signed manufacturer updates, performs a factory reset, and exposes limited diagnostics. A custom recovery adds functions intended for developers and enthusiasts.
CWM became popular because it added:
- installation of compatible ZIP packages from storage;
- partition backup and restore, commonly called a Nandroid backup;
- partition mounting and selected wipe operations;
- ADB access and, in later builds, ADB sideload support;
- a text menu controlled with hardware buttons, with touch support on some builds.
CWM itself is not the same as root, SuperSU, a custom ROM, a bootloader, or SP Flash Tool. Root changes privileges inside Android. A custom ROM replaces operating-system components. A bootloader selects and verifies images during startup. SP Flash Tool is a MediaTek service utility. Combining all of them into one generic procedure, as old tutorials often did, hides important device-specific risks.
Is ClockworkMod Recovery still current?
Treat CWM as historical software for supported legacy hardware. The public CyanogenMod android_bootable_recovery source tree remains available, but its default branch is cm-14.1 and its last source push was in January 2017. That is useful for inspecting and building old recovery code, not evidence that a random CWM image supports a modern phone.
The current Android boot chain has also changed. AOSP documents separate recovery images on many non-A/B devices, recovery resources inside boot-related images on A/B devices, and additional structures such as vendor_boot, init_boot, dynamic partitions, and Android Verified Boot. An image made for an older dedicated recovery partition cannot be assumed to fit these layouts.
There is no safe “latest CWM APK” that discovers and installs the right recovery on every Android device. Old ROM Manager or CWM APK downloads may be incompatible, abandoned, or repackaged. Do not grant root access to an APK from an unknown mirror.
Recovery partition, recovery-as-boot, and A/B devices
| Device layout | Where recovery may live | Why an old guide can fail |
|---|---|---|
| Legacy non-A/B | A dedicated recovery partition | The image still needs the exact kernel, device tree, storage map, and hardware support |
| A/B seamless updates | Recovery resources can be in boot or another boot ramdisk | A separate recovery partition may not exist |
| Newer GKI or vendor-boot layout | boot, init_boot, vendor_boot, or a device-specific combination | Flashing one old-style image can break verified boot or omit vendor components |
| Samsung and other vendor protocols | Vendor-specific packages and download modes | Standard fastboot commands may be unsupported |
Do not infer the layout from the Android version alone. The finished device, launch version, update scheme, bootloader, and vendor implementation all matter.
CWM, TWRP, Lineage Recovery, or stock recovery?
| Recovery | Best fit | Main limitation |
|---|---|---|
| Stock recovery | Official updates, factory reset, warranty or service preparation | Usually cannot install unsigned community packages |
| ClockworkMod Recovery | An older device with a verified CWM build and established legacy instructions | Legacy project, weak fit for modern encryption and partition layouts |
| TWRP | A device listed on the official TWRP site with current device-specific instructions | Support and encryption behavior vary by device and firmware version |
| Lineage Recovery | A supported LineageOS installation whose official device guide requires it | Designed around the documented LineageOS workflow, not every modification |
The correct choice is the one maintained for the exact device and software branch. TWRP explicitly warns that an image for another device usually does not work. A LineageOS installation page likewise takes priority when you are installing LineageOS, because its recovery and sideload steps are tested as one device-specific process.
Before downloading a CWM recovery image
- Record the finished-device identity. Save the brand, full model number, regional variant, storage size, Android build, and current baseband.
- Find the device codename and board revision. A marketing name can cover several incompatible products. Confirm the codename from trusted device documentation, not from a download filename.
- Identify the boot layout. Determine whether the device is A-only, A/B, or Virtual A/B and whether it has a dedicated recovery partition.
- Check bootloader policy. Confirm that the manufacturer supports unlocking and read its consequences before enabling OEM unlocking.
- Back up files outside recovery. Copy photos, downloads, documents, messages, authenticator recovery codes, and app data using methods appropriate for the device.
- Keep stock recovery materials. Obtain the exact factory image or vendor recovery package and document how to return to stock.
- Verify the download. Use the maintainer's page, filename, version, checksum, and signature when supplied. Avoid link shorteners and anonymous reuploads.
AOSP states that bootloader unlocking should trigger a factory data reset. Finish and verify the backup before you send any unlock command. Do not relock a bootloader until the device has a complete compatible stock image and boots normally, because a locked bootloader may reject modified partitions.
Safe installation decision flow
- Start at the device manufacturer's support page or the active ROM project's official device page.
- Confirm that the guide names the exact model and codename you recorded.
- Use the recovery file linked by that guide. Do not substitute a similarly named CWM, TWRP, boot, or vendor-boot image.
- Install the current Android SDK Platform Tools from Google if the guide uses ADB or fastboot.
- Connect the phone and confirm that ADB sees the intended device before rebooting:
adb devices
adb reboot bootloader
fastboot devices
These commands only check the connection and request a bootloader restart. They do not choose a partition or write an image. Use a flash or temporary-boot command only when the exact device guide supplies it. Some devices can temporarily boot a recovery image for testing, while others require a permanent write or a vendor-specific tool. On A/B devices, a generic recovery-partition command can be wrong.
If the page gives only a processor name, tells every device to use the same image, or asks you to disable security controls for an unsigned driver, stop. That is not a reliable installation guide.
How to boot into CWM recovery
If CWM is already installed and Android still runs, the least ambiguous method is usually:
adb reboot recovery
This requires USB debugging, an authorized computer, and a working ADB connection. It does not install CWM. Other supported entry methods include selecting Recovery mode from the bootloader menu or using the manufacturer's documented hardware-key sequence while the device is powered off.
There is no universal Power plus Volume combination. Timing and keys differ, and some devices use separate bootloader, download, fastbootd, and recovery environments. If the screen shows “No command,” a stock recovery may be running rather than CWM.
Using the ClockworkMod menu
Classic non-touch CWM builds use the volume keys to move, Power or Home to select, and Back to return, but the controls vary. Read the labels before confirming an action. Common menu items include:
- reboot system now: leave recovery and start Android;
- install zip from sdcard: apply a compatible recovery ZIP;
- backup and restore: create or restore a partition backup;
- wipe data/factory reset: erase user data and settings;
- wipe cache partition: clear a legacy cache partition when present;
- mounts and storage: mount or format selected filesystems.
Never explore a recovery menu by confirming format, erase, wipe, or restore operations just to see what they do. A menu can complete the action immediately.
What a CWM or Nandroid backup includes
A Nandroid backup is a recovery-level copy of selected partitions. On an older CWM device it may include boot, system, data, cache, or device-specific partitions, depending on the build. It is not automatically a complete copy of every file on the phone.
- Check which partitions are selected and whether the backup completes without an error.
- Copy the backup folder to another storage device before wiping or repartitioning the phone.
- Keep a separate copy of internal shared storage because photos and downloads may be excluded.
- Do not restore EFS, modem, NV, calibration, or other identity-related partitions from another device.
- Do not assume an old backup can be restored after changing bootloaders, encryption, partition layouts, or Android generations.
Current TWRP documentation illustrates the same important boundary: a data-partition backup does not include /data/media, which is commonly exposed as internal storage. CWM layouts vary, so verify by inspecting the backup and by keeping ordinary file backups as well.
Installing a ZIP from CWM
Install only a ZIP built for the exact device, recovery environment, firmware base, and installation order. A package being visible in the file picker does not mean it is compatible.
- Read the ROM or package maintainer's current installation page from start to finish.
- Verify the exact device codename and any required firmware or bootloader version.
- Check the downloaded file's checksum when the publisher provides one.
- Complete both the partition backup and the separate personal-file backup.
- Use only the wipes named by the maintainer. Do not add “format system,” “erase all,” or repeated wipes from unrelated tutorials.
- Save the recovery log if installation fails instead of repeatedly applying the package.
A very old CWM build may not understand a current ZIP format, dynamic partitions, file-based encryption, or the package's required update engine. If the maintainer requires another recovery, use that recovery instead of forcing the ZIP through CWM.
Common ClockworkMod problems
| Symptom | Likely cause | Safe next step |
|---|---|---|
| CWM boots once, then stock recovery returns | The stock system restored recovery, or the device uses recovery-as-boot | Recheck the exact device guide and boot layout before writing again |
| Recovery stays on a black screen | Wrong kernel, display panel, device tree, or image format | Stop and restore the exact stock boot or recovery package |
| Hardware buttons do not navigate | The build uses a different key map or touch interface | Use a recovery build maintained for the exact device |
| Cannot mount data or internal storage | Unsupported encryption, filesystem, or partition layout | Do not format data until the maintainer documents that requirement and the backup is verified |
| Signature verification failed | Damaged, unsigned, wrong, or unsupported package | Verify the source and checksum; do not disable verification merely to continue |
| Status 7 or assert failure | The package rejected the device, firmware base, or installation state | Save the log and use the package maintainer's supported path |
| ADB sees no device in recovery | Driver, cable, authorization mode, or recovery ADB support | Use a data cable, direct USB port, current platform tools, and the correct vendor driver on Windows |
| Android no longer boots after restore | Backup mismatch, incomplete restore, verified-boot conflict, or changed partition layout | Return to the exact official recovery package or active device-maintainer instructions |
How to remove CWM and return to stock recovery
Custom recovery normally is not uninstalled like an Android app. It is replaced by the correct stock image or by a complete official factory package. The method depends on the boot layout and vendor tool.
- Download the factory image or recovery package for the exact model, region, carrier, storage variant, and build.
- Verify its source and checksum.
- Follow the manufacturer's documented restore procedure or the supported device guide.
- Boot the restored system and verify updates, cellular service, cameras, storage, and encryption.
- Relock the bootloader only if the device is fully stock and the official instructions explicitly call for it.
TWRP's official removal guidance makes the same general point: replacing a custom recovery with another recovery is normally the removal method, while stock images must come from the device vendor or another trusted device-specific source.
Frequently asked questions
Where can I download ClockworkMod Recovery?
There is no safe universal download. For a legacy device, use a preserved device-specific project page or source tree that names the exact model and codename and provides a checksum or reproducible build information. Do not use an anonymous “all devices” archive.
Is there a ClockworkMod Recovery APK?
Recovery is a boot image, not an ordinary Android app. Historical apps such as ROM Manager could automate tasks on some supported rooted devices, but an APK cannot make an incompatible recovery image safe. Avoid repackaged APK files from mirrors.
Does ClockworkMod Recovery root Android?
No. CWM can install a compatible ZIP, but root requires a separate device-specific method and package. Installing an old SuperSU ZIP from a generic tutorial can fail on current Android versions and boot layouts.
Can I install CWM on a modern Android phone?
Usually CWM is not the maintained choice. Modern devices may use A/B slots, dynamic partitions, vendor boot, init boot, file-based encryption, and Android Verified Boot. Use the recovery and instructions maintained for that exact device.
Can I boot CWM without a computer?
If CWM is already installed, use the documented hardware-key sequence or the recovery option in the device's bootloader menu. The key combination is not universal. An app-based reboot option may require root and still does not install recovery.
Does a CWM backup include photos and downloads?
Do not assume it does. Internal shared storage may be excluded even when the data partition is selected. Copy photos, downloads, and documents to separate trusted storage and verify both backups before wiping.
Sources and scope
This guide was reviewed on October 14, 2026 against the public CyanogenMod recovery source tree, AOSP documentation for recovery images, Android partitions, and bootloader locking and unlocking, plus the official TWRP guides covering what TWRP is, what to back up, backup exclusions, and replacing custom recovery. Recovery installation remains device-specific. The current manufacturer or active device maintainer's instructions take priority over this general guide.
