25th August 2012, 02:41 PM
(Last edited by Shaaan; 30th October 2012 at 11:35 AM.)
Recognized Contributor / Recognized Developer
Thanks Meter 4,667
Join Date: May 2011
DONATE TO ME
[CWM-Recovery][DISCONTINUED] New CWM 188.8.131.52 [Update- 20/10/12]
This project has been discontinued. Any dev please feel free to take over the project.
Hey guys, i present to you a new updated version of CyanogenMod Recovery a.k.a CWM 184.108.40.206. The current version that we use is 220.127.116.11
The new permanent build is up. Its no-more a WIP.
But still please test and report back.
Edit : The bricked ace is causing a lot of problems. I cannot test the recoveries. If possible please consider donating so that i can get it repaired.
Donation link below my profile picture.
Permanent version : CWM 18.104.22.168
You are using this at your own risk. I am not responsible for any bricks or thermonuclear wars.
How to flash :
Download the zip and put it in the sdcard.
Reboot to recovery and flash the zip.
Reboot to system. (This system is very important as it links all recovery files to the system.)
Now reboot to recovery and enjoy.
PS : The backups created by this CWM are indeed very small in size. Its a new feature. Don't come running to me asking why it happens. Read below about how it works.
Changelog of CWM 6 :
As said by Koush himself -
New backup format that deduplicates data between backups.
Fixed restores > 2GB.
Minor UI tweaks (new background, animated Android)
Create Android Update Zips on device : Using this new feature, anyone can create an update.zip package of their currently installed ROM for others to use.
In the past, I have merged/rebased every CWM with AOSP. With Jellybean, I have decided this is no longer in the best interest of the project. There are only a few areas of AOSP recovery that are of interest (roots.c - file system, minui, and updater). Those will continue to be merged into CWM. Other than that, doing a full rebase with every code drop has been a giant headache, with the code churn from upstream that providing little to no value to CWM.
In any case, this unties my hands to deviate completely from AOSP, with the primary goal to make a much more polished touch UI.
ROM Manager is a little over 2 years old, and though it has grown in features quite a bit since its first incarnation, parts are starting to show its age. I've been contemplating a significant UI rewrite for some time now, and will pull the trigger on that shortly. I also want to add in some features that I am hoping will be of some interest:
* A paid ROM section for devs to publish their work and support their hobby.
* Upload your current ROM to ROM Manager for anyone to use, from the device.
* Connect ROM Manager to the Recovery Builder for automatic updates of recovery. No device left behind
Speaking of the Recovery Builder; it has been pleasantly successful. To date, around 1700 recoveries have been built. Many for devices ROM Manager currently does not even support.
Anyways, if you have any suggestions for the future of ClockworkMod products, please drop me a line!.
Here koush explains how the backup size is so small :
New ClockworkMod Backup Format
Don't delete /sdcard/clockworkmod/blobs
I've gotten a few questions about how this works, so I figured I'd make a post on it.
Basically, here's what happens:
The files being backed up are hashed (sha256, not that it matters). Then it checks for a file with the name of the hash in
So, if the hash of the file was c5273884b90d490134e7737b29a65405cea0f7bb786ca82c63 37ceb24de6f5ed, it looks for /sdcard/clockworkmod/blobs/c5273884b90d490134e7737b29a65405cea0f7bb786ca82c63 37ceb24de6f5ed
If the hash file is found, it continues on to the next file. Otherwise, it copies the file to the blobs directory with the file name being the hash.
ROMs and user data, for the most part, do not change too much between builds and backups. So, your APKs, system files, etc, are generally only stored once. This saves a ton of space. Especially between incremental backups.
Some of you may be thinking "well, how do I delete a backup?".
First, never delete the blobs directory. This would actually delete all your backups by rendering them unusable.
Simply delete the usual backup directory, and the next time you run a backup, all the unused hash files will be automatically delete (a process known as garbage collection). The recovery will show "Freeing space..." while this is happening.
nims11, dragonnn for testing
clockworkmod team especially utkanos