[Recovery] ClockWorkMod (CWM) 6 by koush

[djxspeedy]

CWM Unofficial "Nightlies" Changelog - maguro:

https://github.com/CyanogenMod/android_bootable_recovery/commits/cm-11.0

Oct 6, 2013 - 6.0.4.3 is the most recent on ROM Manager, another version bump for new builds. No other changes.

Oct 7, 2013 - 6.0.4.4 fix touch events on some devices, updates to loki support.

Nov 11, 2013 - 6.0.4.5 remove all extra "no" options (create .many_confirm to restore), optional swipe-based touch controls on some devices, reboot more cleanly, vold fixes, new "last path" option under install zip and menu fixes, make/clean build fixes.

Jan 1, 2014 - 6.0.4.6 memory usage improvements, fix vold formatting, menu fixes, move all recovery settings to one file in /data/media/0/clockworkmod/, code cleanups, update loki support to v2.1, revert to old Andy with earwiggle (I worked around this change in the ramdisk because it was hideous).

Jan 22, 2014 - 6.0.4.7 build branch change to cm-11.0: add set_metadata and set_metadata_recursive to updater, don't change perms on symlinks, add reboot standalone command for 4.4 compatibility, support SHA-256 certificates in verifier, start healthd in recovery, logging improvements, fix secure adb, fix vold mounting, fix reboot timing, support xattr, improve dup backups by allowing for moved files, support multiple cores and inceased performance during backup/restore and package installation, revert to old Andy not merged; fix default backup format menu, update su daemon compatbility, code cleanups, include KK4.4 update-binary to fall back on if one in zip is too outdated or broken, switch to cat for backup and restore.

(For an unofficial list of other changes between recent versions, see my previous changelog.)


Known Bugs / Notes:
- Key test does not have a confirmation, so if triggered by mistake a hard reset is required if no USB connection is available to make it exit.
- SELinux in JB4.3+ changes the permissions of su on every boot, so after any boot back to Android you will get a su warning in CWM; it can be ignored.


Attached are recovery flashable zips of both the touch and non-touch versions.

 

[qu4nd]

CWM Official 6.0.4.7 Changelog - maguro:

https://github.com/CyanogenMod/andro...ommits/cm-11.0

Jan 29, 2014 - 6.0.4.7 adds fixes to "mounts and storage" menu hiding certain mounts like /efs and /radio by default and adds ro.cwm.forbid_format and ro.cwm.forbid_mount properties to adjust these per device, enable performance mode in tgz extract/compress only, disable performance mode for package installs.

(For an unofficial list of other changes between recent versions, see my previous changelog.)


Known Bugs / Notes:
- Key test does not have a confirmation, so if triggered by mistake a hard reset is required if no USB connection is available to make it exit.
- SELinux in JB4.3+ changes the permissions of su on every boot, so after any boot back to Android you will get a su warning in CWM; it can be ignored.
- efs (/factory) partition and many other important device partitions may now be accessible in the "mounts and storage" menu, so be careful not to format them.


Attached are recovery flashable zips of both the touch and non-touch versions.

cwm-recovery-clockwork-touch-6.0.4.7-maguro.zip
cwm-recovery-clockwork-6.0.4.7-maguro.zip

 

[djxspeedy]

CWM Unofficial "Nightlies" Changelog - maguro:
https://github.com/CyanogenMod/android_bootable_recovery/commits/cm-11.0

Jan 29, 2014 - 6.0.4.7 is the most recent on ROM Manager, adds fixes to "mounts and storage" menu hiding certain mounts like /efs and /radio by default and adds ro.cwm.forbid_format and ro.cwm.forbid_mount properties to adjust these per device, enable performance mode in tgz extract/compress only, disable performance mode for package installs.

Apr 10, 2014 - 6.0.4.8 display improvements for overlay devices and high res, f2fs support fixes, reboot command fixes, yaffs2 backup support, general cleanups and compile fixes, USB adb+ums fixes, support upstream minui changes, revert fallback update-binary and instead create a legacy property environment, loki updates, add native dualboot if supported, (ramdisk mod by myself to hide /factory,/boot,/sbl,/xloader from the format list).

(For an unofficial list of other changes between recent versions, see my previous changelog.)


Known Bugs / Notes:
- Key test does not have a confirmation, so if triggered by mistake a hard reset is required if no USB connection is available to make it exit.
- SELinux in JB4.3+ changes the permissions of su on every boot, so after any boot back to Android you will get a su warning in CWM; it can be ignored.


Attached are recovery flashable zips of both the touch and non-touch versions.

 

[djxspeedy]

CWM Unofficial "Nightlies" Changelog - maguro:
https://github.com/CyanogenMod/android_bootable_recovery/commits/cm-11.0

Jan 29, 2014 - 6.0.4.7 is the most recent on ROM Manager, adds fixes to "mounts and storage" menu hiding certain mounts like /efs and /radio by default and adds ro.cwm.forbid_format and ro.cwm.forbid_mount properties to adjust these per device, enable performance mode in tgz extract/compress only, disable performance mode for package installs.

Apr 10, 2014 - 6.0.4.8 display improvements for overlay devices and high res, f2fs support fixes, reboot command fixes, yaffs2 backup support, general cleanups and compile fixes, USB adb+ums fixes, support upstream minui changes, revert fallback update-binary and instead create a legacy property environment, loki updates, add native dualboot if supported.

Jun 4, 2014 - 6.0.4.9 swipe controls fixes, prevent changes to swap partitions, menu fixes, code cleanups, keep show log option on screen until dismissed, add SELinux context support to dup format backups, format non-vold extra storage to ext4 (if not otherwise specified), fix backup of directories named "media" that aren't /data/media, add SELinux context support to tar format backups, fix f2fs restore, (ramdisk mod by myself to hide /factory,/boot,/sbl,/xloader from the format list).

(For an unofficial list of other changes between recent versions, see my previous changelog.)


Known Bugs / Notes:
- Key test does not have a confirmation, so if triggered by mistake a hard reset is required if no USB connection is available to make it exit.
- SELinux in JB4.3+ changes the permissions of su on every boot, so after any boot back to Android you will get a su warning in CWM; it can be ignored.


Attached is a recovery flashable zip of the swipe version.
Swipe. Which is kinda like a hybrid between the two (ouch & non touch). Without Jenkins we can't build Touch since koush made it with closed-source touch code we don't have access to.

 

[djxspeedy]

also mir gefällt das "SWIPE" nicht bleibe erstmal bei cwm-recovery-clockwork-touch-6.0.4.8.b60876-maguro.zip

 

[qu4nd]

CWM Unofficial "Nightlies" Changelog - maguro:
https://github.com/CyanogenMod/andro...ommits/cm-11.0

Jan 29, 2014 - 6.0.4.7 is the most recent on ROM Manager, adds fixes to "mounts and storage" menu hiding certain mounts like /efs and /radio by default and adds ro.cwm.forbid_format and ro.cwm.forbid_mount properties to adjust these per device, enable performance mode in tgz extract/compress only, disable performance mode for package installs.

Apr 10, 2014 - 6.0.4.8 display improvements for overlay devices and high res, f2fs support fixes, reboot command fixes, yaffs2 backup support, general cleanups and compile fixes, USB adb+ums fixes, support upstream minui changes, revert fallback update-binary and instead create a legacy property environment, loki updates, add native dualboot if supported.

Jun 4, 2014 - 6.0.4.9 swipe controls fixes, prevent changes to swap partitions, menu fixes, code cleanups, keep show log option on screen until dismissed, add SELinux context support to dup format backups, format non-vold extra storage to ext4 (if not otherwise specified), fix backup of directories named "media" that aren't /data/media, add SELinux context support to tar format backups, fix f2fs restore.

Jun 30, 2014 - 6.0.5.0 fix adb shell command backup/restore, improve progress reporting, speed up backups by removing current filename output in the progress, major code clean-ups, allow selective restore of multiple partitions, logo display fixes, md5 calculator fixes, swipe/touch improvements, support capacitive touch keys, only show "Mount USB Storage" when available, (ramdisk mod by myself to hide /factory,/boot,/sbl,/xloader from the format list).

(For an unofficial list of other changes between recent versions, see my previous changelog.)


Known Bugs / Notes:
- Key test does not have a confirmation, so if triggered by mistake a hard reset is required if no USB connection is available to make it exit.
- SELinux in JB4.3+ changes the permissions of su on every boot, so after any boot back to Android you will get a su warning in CWM; it can be ignored.


Attached is a recovery flashable zip of the swipe version. Touch versions cannot be built unofficially anymore; the last unofficial touch build available is CWM 6.0.4.8.

cwm-recovery-clockwork-swipe-6.0.5.0.b75222-maguro.zip

 

[spoin]

Ich hab CM11 via Cyanogenmod-Installer aufgespielt. Wenn ich im Fastboot "Recovery" wähle kommt ein "CyanogenMod Simple Recovery". Kann ich da den Clockworkmod-Recovery einfach drüberbügeln?

Werden bei Aktualisierung des Recovery's die Nutzer-Daten aufm dem Gerät gelöscht? Oder kann ich mir das eher als "Bios-Update" vorstellen ohne Auswirkungen aufs OS? Weil ich mein Gerät ungern neu aufsetzen möchte, es läuft gerade einwandfrei.

Ich wähle also einfach das z.B. "recovery-clockwork-6.0.4.7-maguro.img" auf meiner SD-Karte und flashe es mit Hilfe des aktuell installiert CM-Recovery drauf?

Sorry für die Anfängerfragen..

 

[qu4nd]

Ein Recovery Wechsel hat keinen Einfluss auf den Rest des OS oder die Daten etc.
Ich kenne die "Simple Recovery" Variante zwar nicht, aber der Wechsel zwischen Recoveries geht normalerweise problemlos per Flash im aktuellen Recovery! Sollte also kein Problem darstellen...

 

[spoin]

Gerade versucht.. er sagt was von Signatur falsch oder so. Vermute der CM-Recovery wird nur signierte CM-Files flashen.. shit. Bekomm ich da noch auf anderem Wege ein CWM-Recovery drauf?

 

[qu4nd]

Fastboot oder Rom Manager

 

[spoin]

Rommanager war die Lösung! Wusste nicht dass es so einfach ist und man das direkt aus dem laufendem Android installieren/flashen kann.
Hab jetzt die neueste "offizielle" 6.0.4.7 Version drauf, auch wenn es schon 6.0.5.1. gibt.. die steht aber zumindest nicht auf der CWM Seite mit drauf.. also vermutlich noch Bastelstatus oder so.

Danke für die Hilfe!

 

[qu4nd]

Ich bin kein großer Fan von Rom Manager. Aber bzgl Recovery tut er ja was er soll...

 

[spoin]

Den kann ich ja jetzt wieder runter werfen oder? Und zukünftige CWM Versionen händisch via CWM-Recovery-Modus installieren oder? Also installieren wählen, .zip oder .img file übergeben und go? Oder geht das nur für OS-Installationen aber nicht für Recovery-Updates?

 

[qu4nd]

Die App kann runter...
Und aktuelle Recoveries kannst du als .zip im CWM selber flashen. Kein Problem!