yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] osm0sis:
Not TOO much by the looks of the CWM GitHub. Here's what I gather from the commits:

Jul 20, 2012 - 6.0.1.0 is still the most recent on ROM Manager, and fixed bugs related to the new 6.x line dedupe format.

Aug 04, 2012 - 6.0.1.1 allowed setting the backup format (dup/tar), update zip creation and cleaned up the menus.

Aug 17, 2012 - 6.0.1.2 fixes some issues with /sdcard/ (/data/media/), allowing recovery to support more than 1 sdcard.

Aug 30, 2012 - 6.0.1.3 appears to have properly fixed some threading issues with "key repeating" which koush felt was a big enough deal to merrit a version bump.

Edit: 6.0.1.3 is also the first build I notice that tapping on the edge/just below the bottom of the menus doesn't cause a reboot. :good:
[Samsung Galaxy Nexus] ChanceOfChange:
the bulder vers os not stable yet, i tried one of them before and i get nothing to works correctly.
[Samsung Galaxy Nexus] osm0sis:
Have you tried 6.0.1.3? I'm using it right now and I have zero problems. I've had zero problems since 6.0.1.0 in fact.
[Samsung Galaxy Nexus] ChanceOfChange:
i used 6.0.1.2 and found some bugs...now im at stable 6.0.1.0 and love it!
[Samsung Galaxy Nexus] osm0sis:
Please elaborate. I want to see if I can reproduce them.
[Samsung Galaxy Nexus] ChanceOfChange:
done it ans stills buging sometimes cant see the sdcard reflashed again the stable ver and all is ok..(im not mention i had to make the whole install again for this but help is help..and im pleased when i give it!
[Samsung Galaxy Nexus] osm0sis:
You shouldn't have to make a new install due to flashing a recovery..:confused: Oh well.

So you can't see the sdcard? Try 6.0.1.1 from the OP. Provided it was built before the sdcard patches that merrited 6.0.1.2 it should work fine and would help us narrow down the bug. Honestly though, works fine here on my GNex using the 6.0.1.3 Touch build I made and posted yesterday.

Edit: FYI (and this may be the confusion), the "mount /sdcard" option under Mounts and Storage is for external sdcard. the GNex internal sdcard is automatically mounted now along with /data/. If I go to "install zip from sdcard" -> "choose zip from sdcard" I'm seeing my sdcard contents no problem.
[Samsung Galaxy Nexus] ChanceOfChange:
its messing my backup like no recognize the data files...rare problem but excist! i do it for stability reason when i use something i use it for good and i wanna be stable and fast! in few words i know exactly want im doing! may i sak you something if you know? i use stock jb 4.1.1 rom and i try to find where are the nesecery files for dissable the hard key volume adjust beep...but i had no luck. can help me on this? if i do this i have the completely cool rom for me!
[Samsung Galaxy Nexus] osm0sis:
Probably a sound file somewhere you can delete/patch out to get the desired effect. I'm afraid I don't know though. Google?

It just occurred to me you might have run into that ROM Manager .nomedia in /sdcard/ bug too by your limited description. Removing the .nomedia file would show everything again.

If it's not that, then I still suggest you try 6.0.1.1 because it allows you to switch back to .tar backups. Less chance of those not being recognized I'd imagine. Suit yourself though.
[Samsung Galaxy Nexus] thegtfusion:
I just had some strange issue with 6.0.1.1 touch...all the zips i tried to flash were giving me status 7 errors.

so i downloaded the 6.0.1.3 touch version and everything seems well now. flashed it via fastboot :)

EDIT: im still getting status 7 :(. also signature check is disabled. WTF is going on???? has something corrupted ???
[Samsung Galaxy Nexus] bartolinio:
Do I well I can see that you can not mount sdcard from CWM so that it can access it via PC?
[Samsung Galaxy Nexus] osm0sis:
...

that counts for adb push/pull/shell as well. works fine.
[Samsung Galaxy Nexus] eternitys:
My Gnex is not detected by pc after upgrading to this CWM .. :(
[Samsung Galaxy Nexus] osm0sis:
Are you using the Universal Naked Driver? You should be: http://xdaforums.com/showthread.php?t=1426502

Everything works fine here.
[Samsung Galaxy Nexus] odm3xda:
I am still on 6.0.1.0 and flashing nightly builds of CM10 backing up and restoring nothing is wrong. I was thinking maybe I should upgrade my cwm but after reading feedback here I think I should stick to mine. Correct me if I am wrong
[Samsung Galaxy Nexus] osm0sis:
If you like blobs then yeah, no real reason. If you like tars then 6.0.1.1 at least. I still have zero problems with 6.0.1.3 though, not sure what other people are doing to somehow mess it up, but yeah, backed up and restored the other night, maguro and grouper.
[Samsung Galaxy Nexus] LNJ:
Can someone create a cwm flashable of the latest non touch version?
[Samsung Galaxy Nexus] osm0sis:
@Elisha: http://xdaforums.com/showthread.php?p=31045760#post31045760

Should be the same as any 6.0.1.3 you see around; no new commits to the cwm github since Aug. 30.
[Samsung Galaxy Nexus] quacklength:
idea for a small improvement of the CWM-recovery, which should speed up our devices a lot:

is it possible to exclude the blobs-folder from the UNIX file-listing: It would be just ".blobs" instead of "blobs". This simple change should speed up nearly any android-device running CWM-recovery, because the system won't index this huge folder with 10k-20k or even more small files. I tried to do this manually, but it isn't working because the recovery cloudn't find my blobs-directory anymore.
[Samsung Galaxy Nexus] osm0sis:
You'll have to submit your idea to koush via twitter or G+ as he rarely, if ever, checks these threads.
[Samsung Galaxy Nexus] LOulOo:
Hi all,

Is this version working with rom manager ?
[Samsung Galaxy Nexus] osm0sis:
Should work even though it's not specifically recognized, just go to the menu/settings and select Manual install.
[Samsung Galaxy Nexus] Mayday_XL:
Where can i download the CWMR Touch v6.0.1.3 ?
[Samsung Galaxy Nexus] bartolinio:
v6.0.1.3 flashable
[Samsung Galaxy Nexus] Nburnes:
Flashable CWM Touch 6.0.1.4 attached. Built today 9/17

Flashable CWM Non-Touch 6.0.1.4 attached. Also built today 9/17
[Samsung Galaxy Nexus] djmcnz:
But why post without a changelog?
[Samsung Galaxy Nexus] gianton:
Because there's no changelog, check the links with the dates.
[Samsung Galaxy Nexus] Nburnes:
https://github.com/CyanogenMod/android_bootable_recovery/commits/jellybean
[Samsung Galaxy Nexus] djmcnz:
And you expect the average user to understand that?

Man, discipline is dropping around here.

If people want to build/post the work of others (and seek the credit therein) why not take the time to post a human readable changelog? I really don't know understand. Especially 'recovery' of all things.

It takes no skill to build someone else's code so why not add value to the chain?
[Samsung Galaxy Nexus] Nburnes:
Then maybe the "average user" should just stick to the one in ROM Manager? These are obviously for people who want to run the latest and take that risk themselves. The changelog is very "human readable". Also, what credit have I taken at all?

If you have that much of an issue, then don't flash it?
[Samsung Galaxy Nexus] djmcnz:
That doesn't really answer my question. To "take that risk" has nothing to do with a changelog, similar risks exist with and without.

By my reckoning there's only three reasons one would make/post a build without a changelog:

They want to be "1st" and therefore don't have the time

They can't be bothered putting in the effort

They don't understand what has changed

And I don't see anything really redeeming about any of those options. Are there more?

What was your reason?
[Samsung Galaxy Nexus] osm0sis:
He's posting it for anyone who wants to run the latest version, and he's not taking credit for anything.

Quit trolling. As a "Recognized Developer" you should know better.
[Samsung Galaxy Nexus] Hatshipuh:
So after reading the commits I conclude there are no changes at all to 6.0.1.3, just a rev bump necessary for a ROM Manager release?
[Samsung Galaxy Nexus] KL4V1CL3:
Koush: "Changes can happen in repositories outside of recovery, like device repositories. I need to rev the recovery version to allow it to be published on ROM Manager."

Yes.
[Samsung Galaxy Nexus] djmcnz:
No, you've misunderstood. It was a legitimate question asked politely and doesn't at all fit the definition of trolling. Why would I **** in my own backyard?

You're correct on one observation - I do know better - it's "better" to always post a changelog. There's no valid reason for not doing so to the best of my knowledge and I was exploring this further. Perhaps there is a reason I'm not aware of?

As it turns out 6.0.1.4 is apparently a redundant build for the Galaxy Nexus so it's a waste of time and bandwidth posting it. If a changelog had been provided surely that would help people make an informed decision?

I appreciate that people may want to run the latest version but yet even you have avoided answering my quite simple question: if you're going to post something why wouldn't you include a changelog?

I'm not sure how you perceive this question to be either unreasonable or inflammatory.
[Samsung Galaxy Nexus] osm0sis:
I apologize if I misinterpretted a newcomer to the thread repeatedly taking a confrontational tone with someone over a small issue nobody else cares about as trolling..

The fact is we've been posting these CWM "nightlies" for months now, citing the official github for changes.

Look in other developer threads, often nightly changelogs will be incomplete, or there won't be one at all, and instead the developer refers people to the commits on github. This is status quo, my friend, so please drop whatever issue you have with it.
[Samsung Galaxy Nexus] djmcnz:
I'm the "newcomer" am I Mr. March 2012? ;)

It seems as if you are resigned to the status quo which is a pity. It never used to be like this on XDA (you probably don't realise that) but if you want to participate in a race to the bottom that's your prerogative I suppose. Current common practice conceivably seems acceptable to the community because when people ask where the changelog is they're either pointed to a repo or flamed - that's not how it used to be at all. And perhaps this masks the frustration experienced when no changelog is posted? That's a perspective worth considering. Because 'everybody else does it' is no excuse and you know this. Have a look in the General Android Apps & Themes section for a demonstration of how it should be done and is still being done, it's a better reference. And this wasn't a 'nightly' - it was a redundant build. No changelogs when posting somebody else's work is a regressive step for this forum which I would have thought we'd all try and prevent.

Imagine if somebody had done the same then when the backup method became exclusively blobs for a while. No changelog then would have caused an awful lot of grief. I think posting a changelog is a good way of demonstrating that you actually understand what you're unleashing on the unsuspecting masses - surely something to aspire to?

Asking a question politely isn't confrontational, that's a matter of interpretation and I can assure you I did not intend to antagonise. The defensive and obtuse responses received were the confrontational part. I think I've remained pretty objective don't you?

TL;DR - In the end it seems nobody can answer my question - "didn't do it because I don't understand what was merged" would have been fine... and far simpler! :) And I get that you all don't care. :confused:

/soapbox
[Samsung Galaxy Nexus] osm0sis:
I get that you have a chip on your shoulder about the current state of affairs on XDA, but your attitude that the lack of a changelog instantly makes the poster someone who doesn't understand what was changed is no more than an assumption, and rather unfair.

I myself was annoyed with the progressing lack of knowledge in the thread with respect to what had changed (eg. people not realizing that the option to switch back to tars was introduced in 6.0.1.1), and posted an unofficial changelog up to 6.0.1.3 a few pages back. Did I get on my soapbox? No, I sat down and worked out a simple readable changelog for the passing user. If you have such an issue then you could have been more productive, raising the level of discourse and doing the same. I see you quote my XDA join date as an attempt to belittle my opinions, well perhaps you should take a page from this "noob's" book next time and contribute rather than complain.
[Samsung Galaxy Nexus] sglscovill:
Well that was quite the discussion. BTW, you both write incredibly well! It was all worth the read. Valid opinions in both directions. Any who, tried update 6.0.1.4 and it seems to be running fine. Thank you
[Samsung Galaxy Nexus] osm0sis:
@sglscovill: Cheers. :) And now that we're back on topic, I might as well keep this going.

CWM Unofficial "Nightlies" Changelog:

https://github.com/CyanogenMod/android_bootable_recovery/commits/jellybean

Jul 20, 2012 - 6.0.1.0 is still the most recent on ROM Manager, and fixed bugs related to the new 6.x line dedupe format.

Aug 04, 2012 - 6.0.1.1 allowed setting the backup format (dup/tar), update zip creation and cleaned up the menus.

Aug 17, 2012 - 6.0.1.2 fixes some issues with /sdcard/ (/data/media/), allowing recovery to support more than 1 sdcard.

Aug 30, 2012 - 6.0.1.3 appears to have properly fixed some threading issues with "key repeating", version bump for new device support.

Sep 16, 2012 - 6.0.1.4 version bump for new device support. No other changes.

Somewhere in there was a fix so tapping the the border/edge of the main menu doesn't trigger a reboot anymore. I also just noticed my first issue using these newer versions, the backup format (tar/dup) option menu seems broken. I'm guessing this is since the "key repeating" fix in 6.0.1.3. It's only an asthetic issue though, as the default format selection still appears to work fine; just the menu displays options below it from the Backup/Restore menu as well, where it didn't before.
[Samsung Galaxy Nexus] TheDecipher:
Trouble copying Blob folder

Hi,

Is anyone else having problems copying the BLOBS folder from the phone to a computer. I am trying but the first time it stopped at around 80% and then said handle error or something like that. After that it just stops at around 0% every time i try to copy it. I'm using 6.0.1.1. Anyone else having the same problem?
[Samsung Galaxy Nexus] andQlimax:
use 5.x recovery...i dont see any reason to use a 6.x
[Samsung Galaxy Nexus] osm0sis:
6.0.1.1+ is faster than 5.x, even when making .tar backups. The tar format is better if you copy to your desktop, blobs are better if you plan on keeping multiple backups on your phone at a time.
[Samsung Galaxy Nexus] colocynth:
switch to tar format before backup if u want to copy the backup to pc

--- sent from Colocynth's Galaxy Nexus Tapatalk---
[Samsung Galaxy Nexus] andQlimax:
can you prove it? :D I think the code to make tar classic backups is the same in 5.x and 6.x
[Samsung Galaxy Nexus] slukk:
Hy everyone :D

Here the latest cwm (if you want):

recovery-clockwork-touch-6.0.1.4-maguro.img
[Samsung Galaxy Nexus] gavin-phelan:
Changes?
[Samsung Galaxy Nexus] colocynth:
thx. can anyone pls make a flashable zip?

--- sent from Colocynth's Galaxy Nexus Tapatalk---
[Samsung Galaxy Nexus] osm0sis:
You guys... Nburnes posted these like 2-3 pages back. There is a changelog 1 page ago.

Please learn to start reading back at least a couple pages in a topic before you post.

---------- Post added at 09:20 PM ---------- Previous post was at 08:40 PM ----------

I haven't dug into the code beyond recent commits, but from my testing/experience they seem faster. I remember 5.x taking a while and with 6.x I've repeatedly been like "Oh, hey, it's done already - that was fast." You can go ahead and try it yourself with a stop watch if you want to empirically prove or refute my claims ;). I also seem to recall reading Koush optimized the backup process in general to make it faster, and this would still apply whether you're using dup or tar.
[Samsung Galaxy Nexus] foyrtcw:
Well this recovery has proved useless. Installed the latest Market update for Apex which has resulted in a force close every time I try to go to the home screen. No worry though as I backup regularly and the last one was done on Saturday. Restore my latest backup and it has put it back as though it has been turned on for the first time, minus the setup procedure. All apps and data missing as it comes up with an error when restoring data. Try an older backup and that is even worse with an error while restoring the system!
[Samsung Galaxy Nexus] D3VI0US:
Download links for the 6.0.1.4 version added to the original post
[Samsung Galaxy Nexus] niamul:
The zip is only making backup of system
[Samsung Galaxy Nexus] osm0sis:
Yes, that's correct.
[Samsung Galaxy Nexus] joao7458:
Flash file cwm 6.0.1.4 anyone?
[Samsung Galaxy Nexus] kyokeun1234:
Could anyone explain the difference between dup backup and tar backup? Is dup backup where it backs up into the blob file?
[Samsung Galaxy Nexus] 3rdstring:
Look back a page or two

Yes, dup is with teh blobs
[Samsung Galaxy Nexus] kyokeun1234:
Thanks :)

I thought so, but needed to make sure. Guess I'm using tar method :D

Swyped on my Galaxy Nexus running AOKP with Franco Kernel
[Samsung Galaxy Nexus] 3rdstring:
or 3 or 4

http://xdaforums.com/showpost.php?p=31676010&postcount=490

:Edit: Nija edited :p
[Samsung Galaxy Nexus] adamslast:
Many thanks. :good:
[Samsung Galaxy Nexus] Zehlek:
Anyway to flash thru Terminal app?
[Samsung Galaxy Nexus] builtboosted:
How do I upgrade clockwork if I'm coming from 6.0

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] kyokeun1234:
fastboot flash recovery NAMEOFRECOVERY.img

Swyped on my Galaxy Nexus running AOKP with Franco Kernel
[Samsung Galaxy Nexus] c_86:
Thx!!
[Samsung Galaxy Nexus] osm0sis:
CWM Unofficial "Nightlies" Changelog:

https://github.com/CyanogenMod/android_bootable_recovery/commits/jellybean

Jul 20, 2012 - 6.0.1.0 is still the most recent on ROM Manager, and fixed bugs related to the new 6.x line dedupe format.

Aug 04, 2012 - 6.0.1.1 allowed setting the backup format (dup/tar), update zip creation and cleaned up the menus.

Aug 17, 2012 - 6.0.1.2 fixes some issues with /sdcard/ (/data/media/), allowing recovery to support more than 1 sdcard.

Aug 30, 2012 - 6.0.1.3 appears to have properly fixed some threading issues with "key repeating", version bump for new device support.

Sep 16, 2012 - 6.0.1.4 version bump for new device support. No other changes.

Oct 14, 2012 - 6.0.1.5 add minadbd, enable "adb sideload <zip>" command, image touch-ups, minor fixes, version bump for new device support.

Known bugs:

- Backup format (tar/dup) option menu displays options below it from the Backup/Restore, cosmetic only.

- Sideload does not have a confirmation, so if triggered by mistake a battery pull is required if no USB connection is available to make it exit.

- Some are reporting MD5 issues with the dup format starting with 6.0.1.5; tar format still works.

[Attachments removed since koush released an official 6.0.1.5 with new fixes.]
[Samsung Galaxy Nexus] reynierpm:
Any flashable zip for latest 6.0.1.5?
[Samsung Galaxy Nexus] osm0sis:
Just grab Nburnes' one from a few pages back and replace the recovery.img inside with your choice of touch or non-touch.
[Samsung Galaxy Nexus] kyokeun1234:
If I use tar as my backup and I set that up, does that set as the default? Or do I have to set it every time I want to backup?

Swyped on my Galaxy Nexus running AOKP with Franco Kernel
[Samsung Galaxy Nexus] osm0sis:
You set it once in the submenu and it makes a .default_backup_format file under /sdcard/clockworkmod/, so as long as you don't delete that file it'll be tar backups. There is no visual indicator in the menu as to which you've chosen though.
[Samsung Galaxy Nexus] kyokeun1234:
Nice to know! Thanks!
[Samsung Galaxy Nexus] reynierpm:
Excellent, do it as you suggested and works fine. Many thanks :good:
[Samsung Galaxy Nexus] Nburnes:
Flashable zips attached.
[Samsung Galaxy Nexus] D3VI0US:
I guess there is a problem in the 6.0.1.5 version : when you try to do a backup the recovery reboot after backing up the system

anybody having the same issue ? .. i rolled back to 6.0.1.4 now
[Samsung Galaxy Nexus] keanurives:
Recovery don't work

I have a problem with my nexus, when I press volume up + power at boot no longer appears in the recovery. Why?
[Samsung Galaxy Nexus] schnuffdroid:
it's ugly?! :D
[Samsung Galaxy Nexus] Rimher:
You should also update the name of the topic with the new version :)
[Samsung Galaxy Nexus] bartolinio:
search for the proper instructions going into the recovery
[Samsung Galaxy Nexus] keanurives:
I restored my nexus, I locked the bootloader and everything worked smoothly. I decided to flash a custom ROM (AOKP) using the tool Galaxy Nexus ToolKit. I flashed ClockworkMod Recovery 6.0.1.5 in this post, but the phone is off, turn it on and as I hold down volume up + power does not go into recovery, it only works on the bootloader. How should I do? thanks
[Samsung Galaxy Nexus] Nburnes:
Through the bootloader is how you get into recovery, unless you reboot directly using adb or fastboot or through a custom ROM.
[Samsung Galaxy Nexus] keanurives:
the key combination for ClockworkMod I do not work anymore. If she hits something the bootloader version I primelc03

volume giù + power = odin mode = funziona

volume su + volume giù + power = fastboot mode = funziona

volume su + power = clockworkmod recovery = non funziona
[Samsung Galaxy Nexus] Nburnes:
I've never known volume up + power to boot recovery mate
[Samsung Galaxy Nexus] albsat:
Please can someone share info on tar/dup format?

What are the differences? Thanks
[Samsung Galaxy Nexus] Nburnes:
https://plus.google.com/103583939320326217147/posts/L5aVZe7C9vg

Blobs store a ton of tiny files that take up a ton of space on device - easily 3GBs+ depending on how often you backup

Tar is the old format that stores everything in simple .tars - they are much faster backing up and tend to be much smaller

(I personally make sure to switch backup method to .tar as do many other users)
[Samsung Galaxy Nexus] builtboosted:
So I can just flash this in clockwork. Or do I need to Odin.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] cwhitney24:
Just flash in recovery

sent from my Galaxy Nexus while eating bacon
[Samsung Galaxy Nexus] albsat:
Very helpful. Thnx again.
[Samsung Galaxy Nexus] osm0sis:
No problem with that here... must be something else going on with your setup. :(

I'm with Nburnes on this one. Can't say I've ever heard of that key combo, and I'm sure I've tried them all in the past.

Power+Volume Down for ODIN. Hold all 3 for bootloader.
[Samsung Galaxy Nexus] gianton:
No such problem here, just did a backup.
[Samsung Galaxy Nexus] builtboosted:
Which recovery

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] CMNein:
CWM or TWRP.
[Samsung Galaxy Nexus] builtboosted:
So I boot into recovery and flash the zip. Thanks!

Edit: worked perfectly

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] kramnod:
Does anyone know how to adjust the brightness of clockworkmod, it burns the superamoled, specially if you fall asleep while flashing, it does not automatically turn off the screen.......

The screen not automatically turning off is ok as long as we can set the brightness level on it to prevent the Superamoled getting burned by the static image of Clockworkmod...
[Samsung Galaxy Nexus] kyokeun1234:
Sadly no. I wish though.

Swyped on my Galaxy Nexus running AOKP with Franco Kernel
[Samsung Galaxy Nexus] osm0sis:
****ing ****! Tell me about it! :p It seriously needs a screen timeout or option to turn off the screen. I was trying to figure out why I have a discolored band - burn in :mad: - going across near the top of my screen, too low to be the notification area or the Google search bar. It was the ****ing blue bar at the top selection in CWM. Now I make sure to move it down one or two so it doesn't get worse. :eek::(