yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] osm0sis:
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.

[ Attachments removed due to a new official. ]
[Samsung Galaxy Nexus] TheMan0790:
Quick question that I cannot figure out the answer to. I am on the latest nightly and can flash ROMs no problem, but flashing any type of kernel gives me a Status 7 error message and fails to flash the kernel. Thoughts?

Break me off a piece of that Kit-Kat ROM!
[Samsung Galaxy Nexus] scarcry:
have the exact same behavior. every kernel (anykernel format) gives me the status 7 error. downgrading to cwm 6.0.4.6 and same kernels install without a problem.

Tapatalked from my maguro running vanirAOSP nightlies
[Samsung Galaxy Nexus] TheMan0790:
Can you post a download link for 6.0.4.6?

Break me off a piece of that Kit-Kat ROM!
[Samsung Galaxy Nexus] osm0sis:
Status 7 means nothing, what did it actually fail on?

Regular kernel zips, even those with device asserts like franco.Kernel flash fine. Is it only with AnyKernel format? Please provide a link to a zip and I'll see if I can tell you why.
[Samsung Galaxy Nexus] TheMan0790:
Well, I have tried both Mpokang's Superram kernel and DirtyV's Linaro4.8 toolchain Sabermod kernels. Both fail. I have been able to flash both kernels on earlier recoveries before.

Break me off a piece of that Kit-Kat ROM!
[Samsung Galaxy Nexus] scarcry:
tried flashing dirtyV-SR5 from cwm 6.0.4.7.touch recovery but got following error:

set_perm: some changes failed

E:Error in /data/media/0/dirtyV-SR5.zip (Status 7)

Installation aborted.

I downgraded to cwm 6.0.4.6 and that same kernel zip flashed without a hitch.

HTH

Tapatalked from my maguro running vanirAOSP nightlies
[Samsung Galaxy Nexus] TheMan0790:
This is the exact error I am getting.

Break me off a piece of that Kit-Kat ROM!
[Samsung Galaxy Nexus] osm0sis:
Weird. My best guess is it must be due to this somehow: "include KK4.4 update-binary to fall back on if one in zip is too outdated or broken"

https://github.com/CyanogenMod/andr...mmit/a0f0fc021049fe3906336b558059f48fb36507fb
[Samsung Galaxy Nexus] osm0sis:
My AnyKernel zip for franco.Kernel works fine.. And it has set_perm_recursive in there and chmods in the .sh.
[Samsung Galaxy Nexus] osm0sis:
Also my sdcard Fix Permissions zip has set_perm and works fine. So basically it's just AnyKernel zips using the ancient-ass update-binary Koush originally included. If they update to something even reasonably newer (my zips all use the binary from a 4.2 OTA, if I recall correctly) then they'd work fine.
[Samsung Galaxy Nexus] TheMan0790:
Do you think you could re-upload 6.0.4.6? Thanks for your help.

Break me off a piece of that Kit-Kat ROM!
[Samsung Galaxy Nexus] osm0sis:
Lost and gone forever, I'm afraid. Unless someone else still has it laying around.

I tested my theory by replacing the update-binary from dirtyV with a couple newer ones and it still triggers the issue, looking into it further now.
[Samsung Galaxy Nexus] TheMan0790:
Oh, I see. Thanks for looking into the issue. I appreciate it.

Break me off a piece of that Kit-Kat ROM!
[Samsung Galaxy Nexus] osm0sis:
Okay, I figured it out. It's a mistake in the updater-script, not CWM at fault. ;)

The script contains the line:

set_perm(0, 0, 0777, "/tmp/dump_image");

But that file doesn't exist because the dev switched to the better method of using the "dd" command to dump the current kernel's boot.img.

I remove that line and the zip works fine. Tell your devs to fix their zips. CWM catches the bad syntax now, that's not a bug. :good:

Actually, maybe recommend they base it off of my "AnyKernel 2.0" zip if they like:

http://d-h.st/rXC :D

They can add ramdisk tweaks required for things like timer_slack that way too.
[Samsung Galaxy Nexus] scarcry:
https://www.dropbox.com/s/lbsgywf5hdmdj6m/cwm-recovery-clockwork-touch-6.0.4.6.b50157-maguro.zip

Tapatalked from my maguro running vanirAOSP nightlies
[Samsung Galaxy Nexus] osm0sis:
Thanks, but it's still the devs' jobs to fix their sloppy updater-scripts. Downgrading isn't the solution. :(
[Samsung Galaxy Nexus] scarcry:
I completely agree mate, just wanting to help.

Tapatalked from my maguro running vanirAOSP nightlies
[Samsung Galaxy Nexus] TheMan0790:
I appreciate all the help. For the moment, I have downgraded.

XOOM XOOM!
[Samsung Galaxy Nexus] GamaX320:
I also facing flashing Mpokang kernel and fancy kernel error problem.... downgrade
[Samsung Galaxy Nexus] osm0sis:
No. Tell the devs to fix their **** or it won't get done.
[Samsung Galaxy Nexus] akash3656:
Yea but some devs just totally stopped developing especially on the kernel side. I mean even Franco himself hasn't updated the kernel in a while (not that I'm complaining). And kernels like Trinity still work fine on 4.4 and I'm sure there are other kernels out there too with the same scenario. Stable, works with 4.4 but no longer updating.
[Samsung Galaxy Nexus] Vekhez:
[MENTION=4544860]osm0sis[/MENTION] can't flash kernel's with 6.0.4.7
[Samsung Galaxy Nexus] osm0sis:
[MENTION=5427457]Vekhez[/MENTION] you need to read the last 2 pages before posting. ;)
[Samsung Galaxy Nexus] Vekhez:
Yeah, I was more meaning that it doesn't work on the official version, but works fine on this version.. I have different results. :)
[Samsung Galaxy Nexus] osm0sis:
Ah wow! We went official for maguro. That is news! Thanks. :)

What's the error when it doesn't work in the official?
[Samsung Galaxy Nexus] Vekhez:
Nope, now having the same problem, maybe it's my phone, Status7 on yours and official, and sideload on 2.6.3.2 is broken, ehh.
[Samsung Galaxy Nexus] ruben46_:
issues with last version
[Samsung Galaxy Nexus] osm0sis:
Did you try fixing the broken AnyKernel zips how I suggested?

Be specific or don't post.
[Samsung Galaxy Nexus] mauro2390:
thanks for solving the weird issue read here if you are interested in http://xdaforums.com/showpost.php?p=50039823&postcount=1255
[Samsung Galaxy Nexus] rage913:
Alright, I'm probably asking the dumbest question in the world but I figured you guys would be able to help me in my endeavors of flashing. I was able to install adb and that's all great and dandy. When I open a command prompt I'm able to see my devices when I enter "adb devices" but this is with my d2tmo on and NOT in cwm, my devices' serial number shows up and I'm all good. Now from here is where things get into the gray area and I'm slightly confused. In order for me to flash a .img I need to be in fastboot. Now fastboot for my specific device (or so I've read) is download mode. Now when I enter download mode from cwm, adb decides to say I have no idea what device this is. I'll run "fastboot devices" to see If i can get my device to show up but it doesn't and I don't know if I'm inputting a command wrong. My drivers are up to date and I just checked through my devices in the properties of "my pc" and its reading my d2tmo as adb interface so I'm assuming that that's clear as well.

I've searched through the forum and I did see rather simple instructions of go into fastboot-->fastboot flash recovery [name of recovery].img but I don't know or understand how to get to that part. I have used youtube as well but all its showing is how to install the adb/sdk not so much on actually flashing something as specific as a .img let alone for my actual device...Can you guys help out?:confused::fingers-crossed:
[Samsung Galaxy Nexus] osm0sis:
First of all, this is the Galaxy Nexus thread. A little bit more open than your S3, and you should be asking your questions in the S3 forums since this isn't really generalizable to a Nexus device, "Samsung Galaxy" or not. ;)

That said, I do know your answers.. Download mode is ODIN and requires the tool of the same name; totally different from fastboot. If you've got CWM installed you're probably better off sticking with it and zips whenever you can.
[Samsung Galaxy Nexus] rage913:
I have no idea why this is saved for one of my threads. Told you I would be derpy. On top of that I had to have known th at download mode was for Odin. God I'm dumb. I chalk it up to late night texting. Either way thank you kind sir and I bid you good day :thumbup::cool:
[Samsung Galaxy Nexus] osm0sis:
CWM Official 6.0.4.7 Changelog - maguro:

https://github.com/CyanogenMod/android_bootable_recovery/commits/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.

[ Attachments removed since there is a newer nightly. ]
[Samsung Galaxy Nexus] GamaX320:
the official 6.0.4.7 fix the kernel problem??? Last time using unofficial cant flash kernel...
[Samsung Galaxy Nexus] osm0sis:
Come on, bro! The only "kernel problem" is that you don't read the thread. It's been explained several times by myself and others. The zips you're using are broken and I've explained how you or the devs need to fix them. :rolleyes:

As for the new /factory and other mounts problem, if our device maintainers don't officially fix it by the next nightly I'll start working around it myself using those new properties in the ramdisk.

Edit: Add to /default.prop:

# Hide inappropriate partitions from Mounts and Storage
ro.cwm.forbid_format=/factory,/boot,/sbl,/xloader
[Samsung Galaxy Nexus] rahimali:
At the very least, EFS mount/ factory format should have half a dozen warning screens and about a dozen more confirmation screens so that a person would get fed up before doing anything destructive... :rolleyes:
[Samsung Galaxy Nexus] aosp:
[MENTION=4544860]osm0sis[/MENTION] You build TWRP recently?

http://xdaforums.com/showthread.php?p=50931381
[Samsung Galaxy Nexus] osm0sis:
Nope. 2.7.0.0 is out though? That's cool.
[Samsung Galaxy Nexus] aosp:
Yup but still no backlight control being it was built from CM10.2 source but maybe the ramdisk could be modified to add it in make it dirty with [MENTION=4608636]bsmitty83[/MENTION] kernel?
[Samsung Galaxy Nexus] osm0sis:
Not a ramdisk fix by the looks of it. CWM is CM11.0 based. ;)
[Samsung Galaxy Nexus] akash3656:
I still think you'll still see at least some odd people still screwing up their EFS. Some people just love wiping everything.

A big warning may help though. TWRP has a big warning for wiping the entire internal storage, yet quite a number still mess up and wipe all their stuff somehow.
[Samsung Galaxy Nexus] hanschke:
.8 :confused:
[Samsung Galaxy Nexus] osm0sis:
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 is a recovery flashable zip of the touch version. A newer non-touch (swipe) version is available.
[Samsung Galaxy Nexus] drive2droad:
thanks for the 6.0.4.8 zip [MENTION=4544860]osm0sis[/MENTION] !!
[Samsung Galaxy Nexus] skyleth:
Is it still saving the backups outside the sdcard?

Enviado desde mi Galaxy Nexus mediante Tapatalk
[Samsung Galaxy Nexus] mrgnex:
Do you drive a delorean?
[Samsung Galaxy Nexus] drive2droad:
i wish I could drive one but with a V8 !!
[Samsung Galaxy Nexus] osm0sis:
6.0.4.8 is the posted build in your pic. You're confusing the Jenkins build number. :p
[Samsung Galaxy Nexus] mrgnex:
No xda was confused and displayed his post as from 1-1-1970. Lol thanks for the recoverys btw!
[Samsung Galaxy Nexus] osm0sis:
6.0.4.9 is out in the source. CM has disabled the Jenkins-based builder.clockworkmod.com though, so I can't make remote builds anymore. :mad:

[MENTION=2918596]Nburnes[/MENTION] any chance you'd be willing to lend a hand? :)
[Samsung Galaxy Nexus] Nburnes:
Just synced at 9:15 CST. (6m build with a little testing!)
[Samsung Galaxy Nexus] revanmj:
Which one is that? Normal or touch?
[Samsung Galaxy Nexus] osm0sis:
Swipe. Which is kinda like a hybrid between the two. Without Jenkins we can't build Touch since koush made it with closed-source touch code we don't have access to.

[MENTION=2918596]Nburnes[/MENTION] was looking at a couple 3rd-party replacements for the touch code the other day though. :fingers-crossed:

Edit: I think they deprecated the standalone recovery job because they're building the recoveries nightly with the CM ROMs now: http://jenkins.cyanogenmod.com/job/android/; still no good for us since they only keep the last 4 builds up, so you'd need to catch maguro as is flies by since they only put diffs in the nightlies. :mad: :(
[Samsung Galaxy Nexus] osm0sis:
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.

[ Attachment removed as a newer nightly is available. ]
[Samsung Galaxy Nexus] DJxSpeedy:
i dont like the new design (swipe).. is it ok to keep on cwm-recovery-clockwork-touch-6.0.4.8.b60876-maguro ?

or is the new recovery (swipe) needed for newer CM11 builds ?
[Samsung Galaxy Nexus] osm0sis:
Yeah it's totally fine to stay on 6.0.4.8 as far as I know, especially if you prefer touch. I left the zips posted a few pages back for that very reason. Here's the short link: http://v.ht/6048m. You can see the fixes you'll be missing in the changelog above. :)

I'm going to try and catch maguro during tomorrow's nightly builds on Jenkins so I can grab the recovery.img; we'll hope it's the touch version from the latest source. I looked into the source a bit and [MENTION=2918596]Nburnes[/MENTION] can also build with the defconfig I_AM_KOUSH to make it say "ClockworkMod Recovery" instead of "CWM-based Recovery" in case that was bothering anyone. :p
[Samsung Galaxy Nexus] DJxSpeedy:
thx for your fast answer ;)

and thx for the link..its nice from you but i have always an older backup of CWM on my pc ;)
[Samsung Galaxy Nexus] osm0sis:
Bad news. The ones being built with CM are swipe, not touch. Touch fans are out of luck unless [MENTION=2918596]Nburnes[/MENTION] can figure out an alternative to koush's closed-source touch code. Otherwise you're stuck waiting for official releases to get new touch versions; but for now 6.0.4.8 is still newer than the latest official, of course. ;)

I found this out by downloading the flo recovery that was just built in the last 30 minutes and flashing it on my N7, and it says "CWM-based Recovery" even. Weird. You'd think CM would set the flag I_AM_KOUSH to make it official CWM branding.
[Samsung Galaxy Nexus] a3361035:
Jenkins gets mirrored, no need to snipe.

http://mirrors.reflected.net/pub/get.cm/jenkins/

You just need to know the job number, so for 20140617:

http://mirrors.reflected.net/pub/get.cm/jenkins/72765/

That way you can always get the latest cwmr-swipe.

Can someone build CM's new simple recovery?

https://github.com/CyanogenMod/android_bootable_recovery-cm
[Samsung Galaxy Nexus] IonAphis:
Osmosis,

A few questions, as it has been a while since I used the Galaxy Nexus (doing this for a friend).

First, he is coming from CWM 6.0.3.6, there is no problem flashing CWM 6.0.4.7 or 6.0.4.8 directly?

Second: which is the touch version of these 2 nightlies:

cwm-recovery-clockwork-touch-6.0.4.8.b60876-maguro.zip - [Click for QR Code] (6.92 MB, 1626 views)

cwm-recovery-clockwork-6.0.4.8.b60877-maguro.zip - [Click for QR Code] (6.92 MB, 619 views)

Third: Would you still have the CWM 6.0.4.7 flashable zip?

Thanks so much!
[Samsung Galaxy Nexus] Reptilez_DK:
No problems going from 6.0.3.6 to any newer version.

The first one is the touch, as it says in the filename.

6.0.4.7 is available from this thread, IIRC. And from ROM-manager. :)

These typos came from my maguro.
[Samsung Galaxy Nexus] IonAphis:
Thanks for your answer, but I cant find 6.0.4.7 flashable zip official, not nightly, anywhere. There are the 6.0.4.8 but those are nightly. In the front page I see the 6.0.4.7 img, but I need the flashable version.

Thanks for all the help!
[Samsung Galaxy Nexus] osm0sis:
Use 6.0.4.8, all the revisions have been released officially for other devices, I just call them nightlies because they're newer than our latest official. There is no extra polish or anything that goes into the code for an official, believe me.
[Samsung Galaxy Nexus] a3361035:
Version 6.0.5.0

http://review.cyanogenmod.org/#/c/67163/

Notable changes since 6.0.4.9:

* Segfault fixes for command line nandroid backup/restore

* Optimizations to progress thread so it doesn't get overloaded with

screen updates (this significantly improves backup/restore speed)

* Fixes for command line nandroid backups of vold volumes

* Correctly update background image for errors and finished processes

* Allow selective restore of more than one partition at a time

* New MD5 calculator only verifies checksums of partition(s) selected

for restore and warns you when files or checksums are not found

* New touch code supports a wider variety of devices for swipe control

and virtual (capacative touch) keys are now supported

* Only show Mount USB storage option if possible

Download:

http://mirrors.reflected.net/pub/get.cm/jenkins/75222/
[Samsung Galaxy Nexus] osm0sis:
Nice! They're doing my job for me. :)

Now if only they'd bring back Touch builds..

Anyone wanting to flash the above recovery.img via recovery should check out my new Flashify Script zip. It takes an image in the same directory and flashes it to the correct partition. ;)

http://v.ht/osm0
[Samsung Galaxy Nexus] Nburnes:
Someone want to test something for me? It's quite ugly as the images don't work correctly (but oddly does on my N5). It is both touch and swipe enabled. Not promising anything really works.

[IMG="CM Recovery"]https://i.imgur.com/1WitDcu.png[/IMG]

;)
[Samsung Galaxy Nexus] osm0sis:
Haha wow, it's hideous! :p

Probably a color space thing and assets meant for a different dpi. Touch works well though!

[MENTION=2918596]Nburnes[/MENTION] I see Tom also pushed the updated touch code to CWM proper; any chance you could enable touch like he suggests in the commit and build CWM Touch with the I_AM_KOUSH defconfig enabled so we can see if it builds a working legit branded build? :D

Edit

: I guess I should get around to doing up a proper post for 6.0.5.0 now that I've got some time. ;)

The build linked above was removed, but I'll try to find another one from before they started adding new changes again on July 10th. :good:

Edit 2

: Ah the CM M8 snapshot build has it. Perfect!