yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] osm0sis:
I'd uninstall the SDK. You don't need 98% of that stuff unless you're a developer. All you need are the files from this post unzipped to a folder.

Make sure all your Android related drivers are uninstalled from whereever, start in Add/Remove Programs then Device Manager. This part can be tricky since it won't show disconnected devices by default, but here's some poweruser **** I learned not all that long ago: In Windows 7 - Start Menu, Right-click Computer -> Properties. Advanced system settings from the sidebar -> Environment variables -> New... -> Name: devmgr_show_nonpresent_devices Value: 1

Reboot and then go to Device Manager, View menu -> Show hidden devices. Now shows EVERYTHING. :)

Once you've done that, you're ready for the Universal Naked Driver. Hunted it down for you: http://xdaforums.com/showthread.php?t=1379875

Unzip it to a folder, and when you connect your Android device skip the Windows Update search and install the drivers by browsing the Windows driver installer to the Naked Driver folder.
[Nexus 7 Android Development] C.Hatfield:
Appreciate it .... been rocking UND long while .... sounds like 86'ing the SDK will def help though - only kept it around, wasting HD space, just for those random occasions when I can open a cmd window in platform-tools & use ADB .... NO ONE bothers to learn ADB anymore - you think I wanna be posting for a CWM zip ?! - hah !

I wanna make my own. :victory:
[Nexus 7 Android Development] osm0sis:
Hmm.. what USB cable are you using? If it's not the one that came with it the connector might be too short and explain why you're getting flakey access via ADB/Fastboot. You can thank Google/Asus for making a non-standard length microUSB connecter to compensate for their bevel..
[Nexus 7 Android Development] C.Hatfield:
Ahhhh, you just may have found the issue ! This is what I was getting at .... the potential, often unknown or over-looked subtler things re: USB cable !

I -usually- use the ASUS USB cable for both my Nexus' ... however, I cannot say for certain that I used it attempting to ADB FASTBOOT the latest CWMR .img - also, fyi .... .zip attempt #8

FAIL

.... been cleaning house - that was a good WIN/Dev Manager tip .... I have used that before, but failed to carry it over to my latest laptop - good lookin out !

Gonna call it a night after next reboot .... if interested, I will lyk if that is a solution :good:
[Nexus 7 Android Development] kzakhar:
^^^

a pure stream of subconsciousness.
[Nexus 7 Android Development] zolaisugly:
I am new to nexus7, have used cwm on my arc and can enter recovery by holding the back key. I understand that I need to hold the Vol button while pressing the power button.

Have tried this several times but can not enter recovery. I have rooted and installed cwm using the toolkit.

What am I missing thanks.
[Nexus 7 Android Development] osm0sis:
Things like that differ from device to device. Hold power+vol up+vol down and then select Recovery.
[Nexus 7 Android Development] WinDroidGuy:
Please see the OP if you're looking for the files from my Dropbox account...
[Nexus 7 Android Development] osm0sis:
This will hopefully save us some troubleshooting in this thread..
[Nexus 7 Android Development] Barleyman:
Ugh, I spent an hour trying to flash CWM, thinking I did something wrong. Looks like, 6.0.1.0 just will not work, neither touch nor regular. At least not on my 4.1.2 stock nexus. I checked the latest nightly (6.0.1.5) and it works without any issues.

Perhaps it should be replaced with 6.0.0.6 for the time being?
[Nexus 7 Android Development] osm0sis:
What? How does it not work? Be specific as to the ways you've tried to troubleshoot. Is your bootloader unlocked? Did you try using fastboot? That's by far the easiest, most fool-proof way.

6.0.0.6 is buggy. You should not run anything lower than 6.0.1.0, and it's recommended you run 6.0.1.5 even though WinDroidGuy can't seem to update the OP.
[Nexus 7 Android Development] WinDroidGuy:
Latest from Koush on the ROM Manager link is stil 6.0.1.0, unless I am missing something...I only updated the OP when new official builds were/are released.
[Nexus 7 Android Development] osm0sis:
Okay cool, thought that might be the case, but you never said anything so I wasn't sure. :) Still, could you please add the info I linked to above (post #246)? It would really help with a lot of the questions the thread sees on a daily basis. :good:
[Nexus 7 Android Development] zolaisugly:
How big a file should the backup file be from cwm?

I took a back up after the update and before modding,adding apps etc the file size is only 20mg...this can't right can it.

If I backup again now will it include the apps that I installed?

Thanks for any help

From the darkest reaches of my mind...... Somebody turn on the light
[Nexus 7 Android Development] osm0sis:
@WinDroidGuy: Case in point!

@zolaisugly: Follow that link to CWM 6.x in the GNex forum, it has the info you need! :)
[Nexus 7 Android Development] Barleyman:
Bootloops, in the case of recovery boots normally after cwm fails to come up. Yes unlocked (I said 6.0.1.5 works fine). I used fastboot, both to flash and hotboot.

Flashing went without errors for both versions.
[Nexus 7 Android Development] osm0sis:
That's really weird that 6.0.1.0 would fail to boot for you... oh well, at least you've got 6.0.1.5 going.
[Nexus 7 Android Development] shane1diamond:
That's about right.I was worried about the size of the file as when I make backups for my g2x they are almost 1gb but I ran my back up for my N7 that was no bigger than 20+mb no problem. Of course I have very little apps.
[Nexus 7 Android Development] osm0sis:
You should also read the link in my reply to zolaisugly. It's not because you have "little apps" it's because of the new backup format. The bulk of the backup is now in the /blobs/ directory. The backup files are now just the differences from backup to backup.

If you're using 6.0.1.1+ you can go back to the old tar format of backups, which is easier if you plan on transferring them to your PC since 7 large files (tars) takes significantly less time to move than ~13,000 small files (dups).

@WinDroidGuy: Do you need any more proof the lack of information in the OP is confusing people? Please add the info I linked for you several times.
[Nexus 7 Android Development] shane1diamond:
I will definitely read that.thank you very much for that information.
[Nexus 7 Android Development] WinDroidGuy:
want me to add the whole post or which portion to make it "easier" less cluttered, I mean to add it a lot and get side tracked lol
[Nexus 7 Android Development] osm0sis:
Ah getting sidetracked happens to the best of us. :)

http://xdaforums.com/showpost.php?p=28407219&postcount=1

The two big quotes which are direct from koush about the new features and backup format are the parts I meant; so the "Here is what Koush said on his G+ Account" + quote, and "Here Koush explains how the new CWM method works that makes the backup files so small in size" + quote; those would be the parts that we really need over here for people. Unfortunately, I don't think there's any way around cluttering it up a bit so that people have the important 6.x info, though of course you could try rewording/summing it up if you like. ;)

Thanks so much for updating the post, it'll definitely decrease some of the troubleshooting/repetition. :good:
[Nexus 7 Android Development] kingofcomedy:
I made a backup before I have updated from 4.1.2 to 4.2 but now I can't restore the backup as CWM says "can't open directory, no files found" (or something similar). Anyone knows a solution to this problem?
[Nexus 7 Android Development] phonic:
Is the backup still on /sdcard? You might need to try mounting it manually first.
[Nexus 7 Android Development] kingofcomedy:
Yes, the backup is still on /sdcard. If I pretend I would like to install a zip-file from sd-card I can see the backup in /sdcard/0/clockworkmod/backup.
[Nexus 7 Android Development] phonic:
Well that's good, at least it's still there and sdcard is mounted. Did you try, after viewing the backup with the 'install zip' menu to go back and try to restore the backup? I assume so, which means something isn't working properly. I've used CWM to make backups, but never needed to restore one (knock on wood!) so I'm not sure if there are any tricks. Did you try the advanced restore menu to see if you can select it that way?
[Nexus 7 Android Development] osm0sis:
Yeah google just changed where everything's mounted again, but this time it's not symlinked the same way.

In ICS it was /sdcard/ -> /data/media/

In JB 4.1 it was /sdcard/ or /storage/sdcard0/ -> /data/media/

Now it's the same as 4.1 but they need to point to /data/media/0/

I'm guessing they're doing this to make room for more external sd's and OTGs in the filesystem. Pain in the ass though.
[Nexus 7 Android Development] rootbrain:
My understanding is it's because of the multi-user abilities. Each will have their own "storage" i. e. /data/media/0, /data/media/1....n and so on.

Rootbrain
[Nexus 7 Android Development] osm0sis:
Ah that makes a lot of sense. Thanks!
[Nexus 7 Android Development] rootbrain:
You can probably fix it with a symlink to /data/media if you don't want to ,make use of the multi-user functionality.

Rootbrain
[Nexus 7 Android Development] kingofcomedy:
Didn't work. Same error message: Couldn't open directory. No files found.

Edit: as I got root back there is currently no need to restore the backup, but it's interesting anyway.
[Nexus 7 Android Development] rootbrain:
Copy the clockworkmod directory to /data/media . Do NOT put it under "0" or "legacy". looks like plenty of updates to apps will be needed.

Try it again.

Rootbrain
[Nexus 7 Android Development] rootbrain:
Who/where do we go to ask about cwm getting updated for 4.2? Techie types can figure this out but normal users not. Android and titanium backups are affected.

Rootbrain
[Nexus 7 Android Development] osm0sis:
Basically you can fire a tweet or a G+ message to koush directly. You can also comment on commits at the github repo.

https://github.com/CyanogenMod/android_bootable_recovery/commits/jellybean
[Nexus 7 Android Development] sandnap:
I outlined the (perhaps temporary) solution that I came up with here: http://xdaforums.com/showthread.php?t=1991657

Using a symbolic link will make it easy to reverse if CWM is modified to resolve the issue.
[Nexus 7 Android Development] kingofcomedy:
Took ages to copy the files (my N7 is almost full now) but it worked and I was able to restore 4.1.2 successfully. Thanks. :)

After I updated manually to 4.2 yesterday the official update is now offered to me. :) Will think about it some days. ;)
[Nexus 7 Android Development] osm0sis:
The one good thing I can think of that's coming from all of this is it will probably put a fire under koush's ass to finally update the build on ROM Manager from 6.0.1.0. :laugh::p
[Nexus 7 Android Development] iamelton:
+1..

wait too long for the "good old" nandroid backup format to be re-added to official releases (available since 6.0.1.1?)..
[Nexus 7 Android Development] osm0sis:
Looks like koush forgot that the N7 also had JB 4.2 on it so he didn't make official 6.0.1.5 builds for it like he did for the GN. N4 and N10 got 6.0.1.6 and the github changes just went live with that revision bump, so I'm building that for us now. Touch only since only like 20 people downloaded non-touch last time with nearly 200 for the touch. ;) If anyone really has an objection to this for some reason, let me know and I'll add a non-touch later.

Should fix the nesting /sdcard/0/0/0/0/ issue for those who like to switch ROMs a lot, and if it works like the official GN builds, it should fix the MD5 issue some were reporting for dup/blob format backups.
[Nexus 7 Android Development] tylercarter:
awesome! thankyou very much. I always prefer CWM but maybe thats cause im a little old school but hey im catchin on. Im goin with the touch version! lol :laugh:
[Nexus 7 Android Development] 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.

Nov 16, 2012 - 6.0.1.6 fixes nesting /sdcard/0/0/0 issue with ROM flashing on JB 4.2+, fixes dup/blob MD5 issue in 6.0.1.5.

Nov 17, 2012 - 6.0.1.7 more backup completion logging, support for fallback to single buffering video if dual fails as out of memory, potential fix for mako.

Nov 17, 2012 - 6.0.1.8 just another revision bump, no changes.

Nov 18, 2012 - 6.0.1.9 reverts mako hack fix.

Known Bugs:

- 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.

[ No attachments since a newer official has been released. ]
[Nexus 7 Android Development] rootbrain:
This is great. Question I have is should I stick with 6.0.1.5 since I'm staying with JB4.1.2 for awhile?

Rootbrain
[Nexus 7 Android Development] osm0sis:
Should be backwards compatible, and apparently fixes some bugs. I'd go for it. ;)
[Nexus 7 Android Development] tylercarter:
dang that was fast! he got 6.0.1.8 out for the nex 10 and 4
[Nexus 7 Android Development] rootbrain:
Yep working great on 4.1.2 still the cosmetic menu issue with choosing backup type. Also the delete backup should allow choosing which backup, if you have blobs from previous backup and choose tar, the delete won't remove the old blobs dir.

Rootbrain
[Nexus 7 Android Development] osm0sis:
Good catch. you should tweet it to him @koush or send him a note on g+. :)

I just sent him one about the backup format menu and needing a confirmation for sideload.
[Nexus 7 Android Development] kingofcomedy:
Thanks for the update. If I have a backup from JB 4.1.2 and another from JB 4.2 this version won't show me both if I want to restore, right (because of the different directories they are stored in)?

And nice to see the tar-format readded as I didn't like the blobs. ;)
[Nexus 7 Android Development] osm0sis:
Yup. tar has been there since 6.0.1.1. :)

If you want them you can just move them in adb shell from /data/media/0/clockworkmod/ to /data/media/clockworkmod/. Only thing is it won't detect blob backups and tars at the same time, as rootbrain just mentioned.
[Nexus 7 Android Development] iamelton:
6.0.1.9 is up at cwm site..

since i dont know where to look for the change log, i just ask here and hope someone can tell me..

can this version work with android 4.1.2 (not the latest 4.2) then (as i dont wanna upgrade yet at the moment)?
[Nexus 7 Android Development] keyra74:
changelog was posted some posts ago

http://xdaforums.com/showpost.php?p=34283182&postcount=278

flashed 6.0.1.9 on my nexus 7, no problem so far
[Nexus 7 Android Development] osm0sis:
CWM Official 6.0.1.9 Changelog:

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

Nov 18, 2012 - 6.0.1.9 is the most recent on ROM Manager, fixes bugs related to multi-user sd in JB 4.2+ and dup format MD5 issue, display improvements, reverts a mako hack fix.

(For a more detailed, but unofficial list of other changes between 6.0.1.0 and 6.0.1.9 see my previous changelog.)

Release Info:

https://plus.google.com/u/0/103583939320326217147/posts/CzstapsDpYf & https://plus.google.com/u/0/103583939320326217147/posts/b6cSma5GiSQ

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 reset is required if no USB connection is available to make it exit.

Fastboot Images Download: http://clockworkmod.com/rommanager

[Attachments removed due to newer posted build.]
[Nexus 7 Android Development] radx:
I just rooted my Nexus7 4.2 here and I installed recovery-clockwork-6.0.1.9-grouper.img.

When I do backups they are always placed at /data/media/clockworkmod/backup/ and not /sdcard/clockworkmod/backup/.

Also, when I choose to install zip from sdcard it always browse /data/media/ instead of /sdcard/.

When I just flashed the recovery the first time I kept getting the error:

E: Can't mount /sdcard/

But After rebooting the device going through the setup process and then rebooting back into recovery I was able to mount /sdcard/ or so I thought.

I've tried doing a full wipe data+cache and I've also tried formating /data /sdcard seperately. Not sure whatelse I can try. Any ideas would be most appreciated.﻿

Any idea what could be wrong? I think I did everything by the book.
[Nexus 7 Android Development] WinDroidGuy:
updated op with the latest build from Koush
[Nexus 7 Android Development] rootbrain:
Probably symlinks because of the new 4.2 filesystem structure.

i'm sticking on 4.1.2 until i see some better resons for upgrading.

Rootbrain
[Nexus 7 Android Development] derekny:
flash zip

i am currently running twrp, can i just flash the cwm-recovery-clockwork-touch-6.0.1.9-grouper.zip? will that just overwrite the twrp? thanks
[Nexus 7 Android Development] osm0sis:
Best way to find out is give it a try. :)
[Nexus 7 Android Development] derekny:
not sure if thats answer i was looking for, just give it a try and possibly f something up? not sure kinda noob to this. thanks tho i guess.....
[Nexus 7 Android Development] osm0sis:
No way it can mess anything up. The recovery partition is separate from everything else.
[Nexus 7 Android Development] truth77:
Has anyone tried koush version on 4.2.1?
[Nexus 7 Android Development] kwbr:
Just flash the cmw image from fastboot.

adb reboot bootloader
fastboot flash recovery recovery-clockwork-touch-6.0.1.9-grouper.img
[Nexus 7 Android Development] rootbrain:
Should work fine. I flashed the zip for my rezound with amon ra to change to cwm and had no trouble. Should be the same, no need for a dB.

Rootbrain
[Nexus 7 Android Development] osm0sis:
Just a heads up, I'm pulling my attachments for the CWM 6.0.1.9 flashable zips since WinDroidGuy linked directly to them in the OP instead of linking to my post, and refuses to answer my PMs on the matter:

http://xdaforums.com/showpost.php?p=34339967&postcount=288

Currently sitting at 1199 downloads for the touch, and 368 for non-touch, yet only 7 thanks, so maybe that's part of the reason. ;)

I'll be reuploading them shortly in the same post, just needed to break those direct links.
[Nexus 7 Android Development] l33ch0r:
I wonder where those backups are located.

Normally, as I know it from previous smartphones, there's a folder "clockworkmod" on /sdcard which contains the backups.

On my Nexus 7 there is a folder "clockworkmod". But inside of that folder is only another folder named "download" and this one contains pretty small sized files - definetely not the backups.

I first wondered, if CWM backed up at all, since it was very fast but then I thought, the Nexus 7 definetely has more performance than this old Desire HD :D

anyways, I restored the backup just to check, if it worked. It did - but I'm always cautious so I'd like to double-check, if the backup is existing.

Where can I find the backups?
[Nexus 7 Android Development] kwbr:
I say THANKS :laugh:
[Nexus 7 Android Development] osm0sis:
So I finally got around to migrating things on my shared N7 to multiuser today. Works pretty great so far. Did it over a fresh wipe using fastboot oem lock/unlock and interestingly enough the second user account sd is in /data/media/10/. I'd assumed all along it'd be in 1 or something since the owner is 0. Weird.

The other thing is .layout_version stays with only the number 2 inside.. So I wonder if the easiest solution to moving back to /sdcard/ would be to just change it to 1 or 0?
[Nexus 7 Android Development] osm0sis:
I'm not going to make a habit of this but, since koush has updated a separate branch that the public can't build from using builder.clockworkmod.com to 6.0.2.1 (for mako) already, I'll release an interim "6.0.1.9+" unofficial build (to distinguish it from the existing 6.0.1.9 builds) with the few fixes he has merged into the main branch from his mr1-staging testing branch so far.

Things that have changed: tar is now the default format again, the format selection submenu is fixed, wipe battery stats is gone because it's pointless, some other stuff.

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

[Attachment removed since new version posted.]
[Nexus 7 Android Development] osm0sis:
I hate triple posting but this is in the name of development and science...;)

segv11 could use the help of a few N7 grouper owners with bootloader 4.13 to see if there is any way to add the N7 grouper to his BootUnlocker app.

I've figured out how to unlock the bootloader without using fastboot and with no data loss on an individual device basis, but he's still trying to work out a general method so we need some more individual devices' partition dumps.

Read my post in the BootUnlocker thread here: http://xdaforums.com/showthread.php?p=35187203#post35187203

I'm willing to make personal unlock/lock zips for the next few people that volunteer to help in that thread. :) :good:

All you need is a custom recovery flashed and an unlocked bootloader. Using the zip I'll make for you, you won't suffer any data loss or have anything to lose by helping out.
[Nexus 7 Android Development] hanschke:
cannot wait for 6.0.2.2 :laugh:
[Nexus 7 Android Development] osm0sis:
CWM Official 6.0.2.3 Changelog:

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

Nov 18, 2012 - 6.0.1.9 is the previous official, fixes bugs related to multi-user sd in JB 4.2+ and dup format MD5 issue, display improvements, reverts a mako hack fix.

Dec 16, 2012 - 6.0.2.3 is the most recent on ROM Manager, larger font for 1080p+, backup format is now tar again by default, format choice menu now displays correctly and shows currently chosen format, wipe battery stats option removed, sdcard partition menu fixes, fixes for dedupe and a crash during backup.

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

Known Bugs:

- 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.

- Factory reset option may still wipe the /data/.layout_version file, resulting in the /0/0/0 issue; use format data instead. (Need confirmation on this bug).

Fastboot Images Download: http://clockworkmod.com/rommanager

[Attachment removed due to newer posted nightly.]
[Nexus 7 Android Development] tangcla:
So just to recap - your file is the same as the img file, just that it's packaged in a flashable zip?
[Nexus 7 Android Development] osm0sis:
Yeah, that's what the people like. I use fastboot, personally.
[Nexus 7 Android Development] xavier86:
You can also use Flash Image GUI.

https://play.google.com/store/apps/details?id=com.joeykrim.flashimagegui
[Nexus 7 Android Development] ghost+:
Backups are now located in data/media/clockworkmod
[Nexus 7 Android Development] hanschke:
i have done the flash but rom manager told me that i have the old build installed and have to update it. any reason why rom manager is wrong?
[Nexus 7 Android Development] jb0ne:
This makes them inaccessible to Windows since it mounts /sdcard; what would be the best way to move a backup made with 6.0.1.9 to a new Nexus 7 and restore it? (cracked screen, going to buy a new one with same size mem). I can adb shell, go to /data/media/clockworkmod and ls and see the backup and blobs dir, would it be best to copy those to /sdcard/clockworkmod so I can get to them and move them to a new device and restore?