yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] osm0sis:
If you can adb shell, why don't you just use adb pull/push? Definitely the easiest. :good:
[Nexus 7 Android Development] jb0ne:
Good idea. Can I pull entire directories at once? I've never tried, only individual files.
[Nexus 7 Android Development] osm0sis:
Yup I usually back it all up at once.

adb pull /data/media/ C:\sd\
[Nexus 7 Android Development] jb0ne:
I noticed there are some other directories in there. If I just pull the clockworkmod one, then push it to a new Nexus 7, can I then restore with CWM? I've never tried a restore from one device onto another.
[Nexus 7 Android Development] osm0sis:
In theory yeah. I've never done it either. The new Nexus might think it's the old one because of the android ID though (and so might the Play Store). The legacy directory is just an empty placeholder for the symlink /sdcard/ when the device is booted, and obb is where large gamefiles go so that they can be shared across users, so it's technically part of your sdcard, what used to be in your /sdcard/Android/obb/ folder, and is symlinked to it when booted as well for compatibility. So the command above is what I use to grab everything so that if I restore my backup and the sdcard files it's literally a snapshot of what's on my device at that moment.
[Nexus 7 Android Development] osm0sis:
Just a quick note. The CWM links in my sig now go directly to my changelog post for that build, so that should make it easier for everyone to find the latest builds and info.
[Nexus 7 Android Development] jb0ne:
Thanks for your informative response. I'm starting to think it might be best to just do a TiBU of my N7 and restore the backup onto the new device. That'd probably be safer, if slower since I'll have to restore each app by hand (I've never found a way to do a a "batch restore" in TiBU but I'll poke around for one) and setup my widgets again by hand. Since TiBU does system apps and I have a few (Swype, Cerberus) I wonder if I should reinstall those properly on the new N7 just to be safe. In fact I'm going to see if TiBU can make a backup of just user-land apps and restore that...

Edit: I found the batch part, batch restore looks easy, and backup of use apps is possible too. My use apps are only 45 though and my system data is 96...would be nice to have my wifi points and cached passwords etc make it to my new N7... I can always do a restore of both user+system and if things go wonky factory reset and try again.

Edit 2: I just noticed TiBU can even make an update.zip of everything, I can just flash that onto my new N7 and see what happens :) I'll just make sure the OS ver is 4.2.1...or at least by the time I get my new N7 (out of stock now) that the OS's match.
[Nexus 7 Android Development] osm0sis:
Yeah I agree. That's the best way I can think of. It'll ask you to restore the android ID but you have the option not to, and that would be best on a different device. To do batch you tap the checkmark at the top. If you have the Pro key then there are no prompts at all and it just does it all in one shot. Worth the price, in my opinion. :)
[Nexus 7 Android Development] jb0ne:
Do have the pro, found batch options, at what point would it ask if I want to restore the Android ID? IfI do the update.zip flashing will I be given that choice somewhere? I just had to do a full restore on my phone as the sdcard died and it didn't ask for one (though that was just apps, the system was intact).
[Nexus 7 Android Development] osm0sis:
It only asks if the ID is different like after a factory reset. It does it when you batch restore, if I recall correctly.
[Nexus 7 Android Development] jb0ne:
Ok so maybe instead up making a CWM flashable update.zip I should dropbox sync the backup files onto my new N7 then run batch "restore missing apps+all system data", to make sure it asks me.
[Nexus 7 Android Development] osm0sis:
The CWM update zip only contains your user apps anyway, and no data as far as I know, so really all you need to use is TiBU for your purposes. Yeah DropBox or adb, however you want to move them over. Anyway, this is getting kind of off topic, but I think you know all you need to now though. :good:
[Nexus 7 Android Development] jb0ne:
Yes, I apologize, I realize it's getting off topic. I have the answers to my questions, thank you.

Now back to CWM official -- is there any reason to use the latest version over 6.0.1.9, considering 6.0.1.9 works with the 4.2 file structure ok? (trying to get back on topic).
[Nexus 7 Android Development] osm0sis:
Fixes. 6.0.2.3 is also official. ;)
[Nexus 7 Android Development] mobal:
Hello!

Sorry for my bad question. Regular CWM mean, is a touch free, use vol up and down + power button to do things?

Thanks!

mobal,
[Nexus 7 Android Development] sean.trinidade:
Correct
[Nexus 7 Android Development] mobal:
Thank You!

mobal,
[Nexus 7 Android Development] osm0sis:
Little update from before. I posted my working solution for relocking and unlocking the bootloader (with no data loss) in the form of a flashable zip how-to:

[TOOL][HOW-TO] [N7] [grouper+tilapia] BootUnlocker Script [Flashable Zip]

http://xdaforums.com/showthread.php?t=2068207

Perfect for those who want the added security of the locked bootloader, but want the ability to unlock it to use fastboot flash when they wish without losing data in the process.
[Nexus 7 Android Development] osm0sis:
[moved to new CWM thread]
[Nexus 7 Android Development] osm0sis:
[removed]
[Nexus 7 Android Development] tylercarter:
awesome! thanks for this! Im very greatful someone updates this for us. :)

voted. nice job :)
[Nexus 7 Android Development] wojtek_pl:
Hi,

odd question:

when I make a backup with this Recovery, where it keeps all it's data on SDcard? I know there is a folder clockworkmod, but is there any other place? I'm trying to recover after full factory reset, restored this folder to my Nexus but when in Recovery Mode it cannot find data to restore from...
[Nexus 7 Android Development] osm0sis:
It keeps them in /data/media/clockworkmod; you likely restored the directory under your user account sd at /data/media/0/clockworkmod

If you (or anyone) haven't already, try out AROMA Filemanager. It really bridges the gap between CWM and TWRP in terms of functionality. The latest version even has a Terminal Console built in. I've got it all set up nice with Roboto and Holo Light theme.

You can easily boot into recovery and move the backups from your user account sd to the /data/media/clockworkmod directory with it. Do that and everything should work. :)
[Nexus 7 Android Development] osm0sis:
Since this thread never gets updated I thought I might reboot this thread, but it seems someone else had this idea too. ;)

[RECOVERY] ClockworkMod Recovery 6.0.2.3 [Fastboot&Flashable Zip] by htchoi5609

I've decided to move my nightlies posts over there (now at 6.0.3.0), and that's where to direct your questions if you'd like my help with troubleshooting as I won't be following this thread anymore. I hope all the regulars and anyone else will join me over there as well. :) :good:
[Nexus 7 Android Development] fredcorp6:
Hi,

Am running the latest CWM touch recovery on my nexus 4, with the rooted stock rom and stock kernel.

I read there will be an android 4.2.2 update in the next few weeks, and was wondering if I could just go ahead and install it like normal when it pops up?? Will I break my phone or loose root or anything if i do it?

Thanks.
[Nexus 7 Android Development] donshaffer:
Is there a way to change the names of the backup files in CWM? :confused:
[Nexus 7 Android Development] sean.trinidade:
I tend to use Rom manager to do that kind of stuff.
[Nexus 7 Android Development] donshaffer:
cool! That is exactly what I was looking for. :)
[Nexus 7 Android Development] hassam_tariq2003:
Osmosis Recovery Links are not WORKING in the 1st POST...!!!
[Nexus 7 Android Development] donshaffer:
Use mirror

http://xdaforums.com/showthread.php?p=43185417

[highlight]Phone: HTC EVO 3D

HTC Sense: 4.1

Software Number: FroZenROM-The Last Episode

Kernel Version: 3.0.1611684

Baseband Version: 1.09.00.0108

Build Number: 2.31.401.5

HBOOT: JuopunutBear 1.57.5757 s-off

Recovery: 4ext v1.0.0.5 RC8[/highlight]
[Nexus 7 Android Development] cyaclone:
Question I paid for the S4 Touch version through Rom Mgr, do I have to pay again for the Flo version for the N7?
[Nexus 7 Android Development] methslushee:
thank you thank you thank you
[Nexus 7 Android Development] Evo_Shift:
Why is it no matter which version of CWM I install I cannot get it to mount /sdcard? I just get the message E:Can't mount /sdcard/

This means I cannot flash SU to complete my root...
[Nexus 7 Android Development] evonc:
You don't need to mount sdcard to root. You should be able to find the zip file in the install from zip file option.

Sent from my Nexus 7
[Nexus 7 Android Development] mrich137:
I would use wugfresh's root toolkit. Easiest way IMHO.
[Nexus 7 Android Development] Evo_Shift:
How do you access the sd card in cwm to flash the zip if you cant mount it?

When I try to flash the su zip from cwm I get that message
[Nexus 7 Android Development] WinDroidGuy:
It auto mounts, you only need to mount external "sdcard" when one is present...the device doesn't have one, so don't need to mount it
[Nexus 7 Android Development] Evo_Shift:
I reflashd my recovery and all is well.

It was not allowing me to choose the command "choose a zip from sdcard" for whatever reason so I couldn't get into my internal storage. reflashing recovery seems to have fixed it for whatever reason.

Thanks for clearing the E: message up though. I realize now that was looking for an external card.
[Nexus 7 Android Development] BCD90:
Thank you all very much!!
[Nexus 7 Android Development] Shano56:
I had the same problem. Seems like a reflash fixed for me too. Also I tried pushing to /sdcard, but i could only push to /data/media instead
[Nexus 7 Android Development] evonc:
The mount options are generally used if you want to run an adb shell while in recovery to push/pull data and run other operations. Otherwise for a standard install, there is no reason to mount anything as sdcard gets mounted automatically and the updater script in the zip file handles the mounting/dismounting during a zip install.

Sent from my Nexus 7
[Nexus 7 Android Development] dynamicpda:
mrich, I'm doing research before doing anything to my N7. Is it possible that flashing the touch CWM is related to the soft bricking?
[Nexus 7 Android Development] brizey:
I tried using the zip and I could not reboot out of recovery. Reboot system would only reboot to recovery, even using adb. Had to use fastboot to reflash twrp.
[Nexus 7 Android Development] Fusion777:
For the record, all worked smoothly for me. Upgraded via ROM Manager, rebooted into recovery to try it. Then restarted, pulled down flashable touch Recovery from this thread. Rebooted back into recovery, flashed it, restarted and golden.

As recommended on another thread, running "reboot recovery" from terminal emulator allows you to enter recovery w/o a USB connection.

i777 w/ Siyah 3.4.3 dual booting AOKP and Shostock... yet sent from my iPad using Forum Runner
[Nexus 7 Android Development] brizey:
Thanks, i will try via ROM manager later today. Has anyone else had the issue of reboot system sending them back into recovery? Maybe i just had a bad download.
[Nexus 7 Android Development] tinpusher:
I had the same issue. Still trying to work it out.

I've not go the touch recovery 6.0.0.6 to install. However, I'm having the same sdcard issue from earlier in this thread.

Install zip from sdcard>choose zip from sdcard results in E:Can't mount /sdcard/

Thoughts?
[Nexus 7 Android Development] ctbear:
Did you just oem unlock right before this? That happened to me and a reboot fixed it.
[Nexus 7 Android Development] DJLamontagneIII:
Same thing happend to me after fashing the zip and now i cant even get it into fastboot to fix it.. any ideas guys???
[Nexus 7 Android Development] brizey:
Use adb:

adb reboot bootloader

Then flash a new recovery with fastboot.

That is what I did.
[Nexus 7 Android Development] DJLamontagneIII:
all good now.. for some reason i couldnt get into bootloader but managed to thanks
[Nexus 7 Android Development] Shano56:
Yeah I had to boot into android first, after OEM unlock
[Nexus 7 Android Development] tinpusher:
I did. I ended up restoring to stock with this thread:

http://xdaforums.com/showthread.php?t=1781250

Except I didn't lock the bootloader.

Then I tried again and it worked like a charm.

Thanks for the help.
[Nexus 7 Android Development] WinDroidGuy:
For those having issues booting in CWM after turning the device off and trying to use bootloader to do it, it won't work there is a bug. Just use the Widgetsoid widget to boot into recovery and works every time or use the ClockworkMod app.
[Nexus 7 Android Development] mrich137:
I don't think so. I flashed my zip in the stock rooted ROM and then flashed to this no problem. Only difference between me and my friend eho did soft brick as far as I can tell was that he didn't wipe before flashing the cm10 ROM.

In another thread someone had posted that there is a back up of the recovery that the boot loader may be checking when trying to get into recovery from the boot loader. My guess was that the boot loader is pointing to a different partition for recovery, which is why people get stuck at the boot screen, but his assumption is probably more likely. In any case the issue is most likely with the boot loader. Someone will need to take it apart and see what exactly its doing to cause the issue.
[Nexus 7 Android Development] brizey:
That should be common knowledge now...mods need to make sticky for it.

There are two boot issues. One as you described...bootloader will not boot to recovery on key presses without a PC.

The other is that the zip version of this CWM causes it to only boot to recovery...no way to boot back to system. Kind of the opposite problem in a way
[Nexus 7 Android Development] mrich137:
Ididnt knwoabout the second issue. I just reflashed the zip and it still works fine for me. Anyone else having problems with my zip? If so what recovery did you flash it in?
[Nexus 7 Android Development] brizey:
I flashed it in TWRP 2.2.1
[Nexus 7 Android Development] DJLamontagneIII:
That must be the issue i also flashed in twrp and got the recovery loop
[Nexus 7 Android Development] spiff72:
Just curious about the ability use ROM Manager as an interface to this recovery...

I had flashed this recovery before installing ROM manager on my N7. When I go into ROM manager it won't do anything without having the "latest" recovery. So I let it flash the recovery on the first menu item in ROM Manager. This gave me a non-touch version of 6.0.0.6. This one looks a little bit wonky on my tablet. The text is spaced very close together and actually appears to be SLIGHTLY cut off at the top.

So is there a way to flash the Touch version via fastboot and still have the functionality of ROM Manager?

Also, if I stick with the non-touch version, should the a nandroid made with the touch version still be useable with the non-touch? So if I backup again it will be an "incremental" backup?

Thanks!
[Nexus 7 Android Development] tarnar:
This worked great for me today, got it done and used it to install root / SuperSU.
[Nexus 7 Android Development] babygetoboy:
If we had this installed, then flashed the twrp recovery, how do we get back to this?
[Nexus 7 Android Development] neilrl79:
I also flashed with twrp and got stuck in recovery loop.
[Nexus 7 Android Development] mrich137:
I didn't test twrp, I've actually never used it, I thought it would work, but I guess its putting people into a boot loop. I would follow OPs original instructions and flash manually to get to this from twrp.
[Nexus 7 Android Development] mrich137:
Yes, but you may need to use a computer with the android SDK installed. Follow the OPs original instructions to flash manually via fast boot. Or download the rom manager app, flash the 6.0.0.6 non touch recovery and then boot into cwm non touch and use my zip to flash the touch version.

As far as I know non touch backups should work with the touch version.
[Nexus 7 Android Development] neilrl79:
Having some issues getting out of this loop. Any help would be appreciated.
[Nexus 7 Android Development] mrich137:
Do you have access to a computer with the android SDK installed? I would follow OPs original instructions to flash this recovery manually in fast boot.

I'm in class right now, but I should be able to help in about an hour when I get out.
[Nexus 7 Android Development] neilrl79:
I get waiting on device and nothing more.
[Nexus 7 Android Development] brizey:
while in cwm do:

adb reboot bootloader

on your pc. That got me into fastboot mode. Then flash the recovery per the instructions with fastboot.
[Nexus 7 Android Development] neilrl79:
No adb devices found....
[Nexus 7 Android Development] Kennnny1:
Updating the android-SDK resolved this for me.
[Nexus 7 Android Development] neilrl79:
OK, I'll give that a try.
[Nexus 7 Android Development] brizey:
I used the drivers, executables and dlls from the the one click root.
[Nexus 7 Android Development] neilrl79:
OK, I updated SDK now I am able to adb in recovery and fast boot at boot loader but I fast boot flashed the recovery and still end up in then recovery loop. I even flashed the r2 interim recovery with the same result.

Update, finally was able to get it by flashing the stock recovery.
[Nexus 7 Android Development] brizey:
Did you reboot via fastboot?

Edit: yeah, I flashed twrp, not cwm.
[Nexus 7 Android Development] neilrl79:
Yeah, fastboot reboot just put me right back to recovery, flashed stock recovery then fastboot reboot got me out of it, I ended up flashing CWM in rom manager and everything is golden now.
[Nexus 7 Android Development] phonic:
I've been using this. Works great. Wish it had the "touch" version like the interim CWM 6.0.0.6.
[Nexus 7 Android Development] Atamagaokashii:
Just flash the touch version from cwm.com using the toolkit or a dB/fast boot. Or flash the .zip that was posted.
[Nexus 7 Android Development] Caliyork:
I just restored a nandroid... IN 2 MINUTES! I'm not sure if you guys are used to that kind of speed, but it takes my g2x running clockwork 5.2.0.8 (or something like that) about 13 minutes. Plus, this thing seems to be almost unbrickable. :good:
[Nexus 7 Android Development] mattykellyuk:
Hi loving the recovery. The only problem I'm having is getting into recovery when the tablet is off. I do the volume down and power choose recovery see the Google logo with padlocks but recovery never loads. Any ideas would be appreciated. Btw had the same problem with the recovery flashed from rom manager too.

Thanks
[Nexus 7 Android Development] DJLamontagneIII:
Known issue with all recoverys.. For now we have to just use an app,termknal command or if you plug it into the computer you should be able to use the button method
[Nexus 7 Android Development] mattykellyuk:
Thanks
[Nexus 7 Android Development] WinDroidGuy:
Simple fix to boot into recovery and works every time. Just use the Widgetsoid widget to boot into recovery and works every time or use the ClockworkMod app

Sent from my Nexus 7
[Nexus 7 Android Development] Goobz:
Quick boot works too.
[Nexus 7 Android Development] brizey:
Yeah, i was pleasantly surprised. Takes about five minutes on my thunderbolt and kindle fire.
[Nexus 7 Android Development] phonic:
True, there are many ways to get into recovery from a working tablet, through apps or manually executing the "reboot recovery" command.

But that doesn't help someone who can't boot into Android in the first place. The only solution right now is to use a USB cable attached to a computer and do it manually.

And yes, it's a known issue with any non-stock recovery.

The only long term solution seems to be to create a custom bootloader that works properly, or find some other hack.

I personally believe the issue is due to the lack of the stock recovery image in the /system directory, since it tries to flash that all the time. The bootloader gets upset if it's not there.

Has anyone tried taking the CWM image (not the zip, the image) and placing it in the /system directory and naming it the same as the stock one? I wonder if that would not only fix the issue, but also get it to have a CWM failsafe recovery image too? It might be worth a shot to test out.
[Nexus 7 Android Development] evonc:
Actually stock recovery fails to boot w/o usb cable plugged in as well or atleast when i tried to boot it directly from bootloader. I have a feeling the issue is bootloader related itself. The bootloader will freeze if you try to go into it while connected to the wall adapter.
[Nexus 7 Android Development] phonic:
Interesting, did not know that. Thanks for the heads up.

So yeah, it definitely looks like a bootloader bug in general. That scraps my "workaround" idea.
[Nexus 7 Android Development] ssick92:
No issues for me with the touch .zip.

Thank you very much
[Nexus 7 Android Development] Character Zero:
Any issues restoring nandroids? I have 6.0.0.5 on my Galaxy Nexus and it bootloops on the X boot animation when restoring any of m Jelly Bean nandroids.
[Nexus 7 Android Development] BaconStep:
I havent had any issues with restoring nandroids
[Nexus 7 Android Development] mrich137:
Lol, anyone know how to take a look into the boot loader? If its any consolation I thought it was a good theory. Im guessing my first assumption is correct then and the boot loader is pointing to the wrong partition when you try to get to recovery.
[Nexus 7 Android Development] smirkis:
me neither. it was the first thing I tested. backup, restore, reboot. wee
[Nexus 7 Android Development] ssick92:
This may be a dumb question but here goes...

I did a nandroid using the touch .zip CWM. Well looking at my SD card storage, there was a folder in the CWM folder on the sdcard called "Blobs" and it was almost 1.5 GB. Also it wouldn't show up in the Storage section of settings so my numbers weren't adding up to 5.92 like they should.

What is this folder? Do I need it?
[Nexus 7 Android Development] nicksoph:
The blobs folder and the backup folder in clockworkmod folder contain the backups - the blobs folder actually contains copies of the files that have been backed up (renamed to the hash values) with the backup folder being used to adminiser the process. If you want to delete files do so from the backup folder and they will be removed from the blobs folder when you next run a backup.

nick
[Nexus 7 Android Development] ssick92:
Thanks, so basically 1 nandroid backup takes approximately 2 GB? 500 mb for the backup folder and 1.5 GB for the blobs folder? That seems like more than usual to me, however this is my first Asus device and/or Tablet.

If I use that other recovery, does it still take up as much space?
[Nexus 7 Android Development] mrich137:
No. Koush redid the way that CWM does the nandroids. Basically if a file is already backed up, it won't back it up again. This is how it will work for all devices going forward.

Link to The post
[Nexus 7 Android Development] ssick92:
Perfect, thanks so much that clears everything up.
[Nexus 7 Android Development] BaconStep:
Non touch 6.0.1.0 is on ROM manager
[Nexus 7 Android Development] smirkis:
koush added backup delete. awesome! this should clear up some confusion on properly deleting backups.
[Nexus 7 Android Development] mrich137:
Here's the zip file for the new touch recovery 6.0.1.0 http://db.tt/pLDeKXEf

Adding to my OP as well. Feel free to mirror!
[Nexus 7 Android Development] WinDroidGuy:
Thanks, I'm adding it now :) also updated the links to the .img flies
[Nexus 7 Android Development] BennyJr:
Whats new besides backup delete?
[Nexus 7 Android Development] ikn0wagh0st:
darn, I was really hoping this new update would be able to boot from the bootloader. Oh well. Maybe next update.
[Nexus 7 Android Development] mrich137:
Nothing as far as I can tell. Couldn't find a changelog for it either.
[Nexus 7 Android Development] fis324:
I thought so too.

I want you to fix this problem as soon as possible.
[Nexus 7 Android Development] Archangel:
Back-up delete is great but does it properly restore all parts of a nadroid? So far the new touch recoveries have not for me?