yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] mrich137:
I still think this is a problem with the boot loader itself since people are having the same issues with twrp and even the stock recovery. I tried to take a look at the boot loader, but as far as I was able to tell from my research, the bootloader.img file is an unknown format that can't be extracted. My guess is that the boot loader is somehow pointing at the wrong partition when you try to navigate to recovery, but then again I could be very wrong.
[Nexus 7 Android Development] RayYung:
Hey Mrich,

You forget to change the version# inside the update script.. :)
[Nexus 7 Android Development] mrich137:
Sorry, fixed! :)
[Nexus 7 Android Development] Shano56:
Heh. Thats why rom manager still showed 6.0.0.6 :p I flashed 6.0.1.0 in rom manager then updated touch with your zip. Thanks!
[Nexus 7 Android Development] mrich137:
Actually I don't know why ROM manager doesn't update the correct version when you flash with the zip. Even if I had put the correct version in the zip, it would Stoll tell you there's an update
[Nexus 7 Android Development] Shano56:
Well thats odd o.o
[Nexus 7 Android Development] m4rk0358:
I just rooted using the rootkit and it installed CWM. After getting into the recovery screen using Quick Boot i'm struggling to figure out how to select an option. None of the buttons work. When I press the power button I just get a screen with the CWM logo and nothing happens.

EDIT: NEver mind. Just realized recovery is touch screen.
[Nexus 7 Android Development] ssick92:
Works perfectly, love the delete and free space features
[Nexus 7 Android Development] 1randomtask:
unlocked the Nexus 7, flashed 6.0.1.0 touch, formatted /Cache, but any time i hit Backup i get "Can't mount backup path."

Any ideas?
[Nexus 7 Android Development] theoneofgod:
I keep getting "Error while restoring data" in the latest CWM 6.0.1.0

The backup was made with 6.0.1.0
[Nexus 7 Android Development] ianPhillips1:
What happened when you made the backup? Did it generate an MD5?

Ian
[Nexus 7 Android Development] nicknowsky:
no CWM REGULAR update flashable zip, that touch recovery is sketchy, im old school going back to G1 and MyTouch days with original Amon-Ra Recovery images.
[Nexus 7 Android Development] neilrl79:
I went into CWM6.0.1.0 and made a backup then rebooted system and couldn't connect to wifi anymore... I'm a little confused.... Any ideas on what caused that?

update; after resetting my router wifi is up and running again. weird.
[Nexus 7 Android Development] theoneofgod:
Yep. Restoring works for all but data. I had to start from scratch now but hopefully there's a way to get it back.
[Nexus 7 Android Development] smirkis:
mine works fine. I've made backups and restored plenty of times. no issues here
[Nexus 7 Android Development] theoneofgod:
With the touch cwm?
[Nexus 7 Android Development] DroidHam:
wtf? I flashed the update.zip over TWP and now whenever i boot i goto recovery automatically?

i cant even get to the bootloader, it keeps constantly cycling. I can't turn the device off.

phew, i was able to plug it in and reboot to bootloader through ADB and flash twp
[Nexus 7 Android Development] asawoszc:
I've taken 3 different backups on 6.0.1.0 and all have only been 20MB in size. I was trying to bounce between two ROMs but couldn't restore either backup properly. Full wipe and dalvik cleared as per normal process but not having any luck. Installing either ROM from scratch works every time. Will try again in the morning but my question is what has everyone else's backup size been? On my gnex my backups were about a gig each....

EDIT: Re-read some posts and my blobs folder is empty even after taking 4 backups now. All 4 backups are only 20MB in size. Obviously something isn't right but I haven't been able to figure it out yet. Any suggestions appreciated. Thanks.
[Nexus 7 Android Development] bisto321:
Not sure if I like the new format. I really liked being able to grab a dated nandroid folder off my device, make a full set of par recovery files for it, and store it offline.

Probably alone in this, but the blob folder is a bit unwieldy to handle when triyng to move it from device to PC because of the enormous amount of folders (10700 files in 3760 folders so far for me).

I can see the advantages for frequent flashers, the speed is great, but I like to back up once in a while and then move the whole backup off the device and store as an individual image.

Has anyone found a good way of storing the image 'off device' securely? Anyone using pre v6 recovery?

I think I have seen a post requesting a selection of either blob or the old data.img & system.img format - not sure how viable that is.
[Nexus 7 Android Development] spiff72:
I have been thinking of doing this as well. I might go back to the earlier non-blob backups for the same reason. It sounded good in theory, but in practice I think I like the self contained versions of the backups better.
[Nexus 7 Android Development] smirkis:
its hit or miss with features these days. people complained forever about how large backups were, and how it needed to be toned down some how. koush comes up with this blob method, stores only changes after initial backup, unless its a totally different rom. u can keep multiple backups with marginal increases in space used. its genius really. almost like, why even delete em. name em and backup the whole cwm backups folder. I honestly don't ever see a reason to store backups elsewhere. the only things backed up is /data which is easy to setup. everything else is included in fresh installs.

some people hate the new feature. some people understand it better because we've been around long enough to really feel the difference.
[Nexus 7 Android Development] phonic:
Good points.

How about a happy compromise? Why not provide a new version of CWM which supports either method? Allow people to either make comprehensive single-shot backups or incremental blobs. Then both groups would be happy.
[Nexus 7 Android Development] DataHawg:
Yes, good points smirkis. This is starting to make more sense to me now. I made a backup with CWM 6.1 right after I unlocked that I will keep on my N7. It's 642mb. I made another one since then and it was only about 25mb. I didn't really need that one so I deleted the whole blobs folder and the second backup. I still have the original backup of 642mb. I haven't tried it yet but I assume it should restore OK.

Sent from my Nexus 7
[Nexus 7 Android Development] smirkis:
Never delete the blob folder! Lol

Delete the backup and run free space from within recovery.
[Nexus 7 Android Development] DataHawg:
I can't delete the backups with root explorer. I can rename or move but it says delete failed when I try it. I've seen this asked as others are having the same issue but haven't seen an answer. Obviously I don't want to fill up my storage with Nandroids that I can't delete. I'm not familiar with running free space in recovery but I'll check it out. I'm also thinking of switching to TWRP and backing up from there. I don't have much on my tablet I care about losing so not a big deal to me anyway but I'd like to get this sorted out

Sent from my Nexus 7
[Nexus 7 Android Development] smirkis:
Mine delete fine. What cwm are you using? I'm using the latest touch version manually flashed via fastboot
[Nexus 7 Android Development] phonic:
This was a bug in a prior version of CWM. I assume you made these backups with the problematic version. As far as I know, there is no way to delete these through Android itself (ie: any file manager or via CLI). However, I did make a flashable zip that you can use via CWM (any version) that WILL erase your backups:

http://core.routed.com/CWM_Backup_Wipe.zip

Be advised, while this will fix your problem, it will delete your entire clockworkmod backup directory. Every backup in there. If you are comfortable editing updater-script files, you can tweak the included one to only remove what you need, but if not, just flash the above file. You could also transfer any needed ones to outside storage first to save them (if necessary).

All it does is remove the "backup" directory, so you don't need to wipe/etc. Just flash, reboot, and you should be good to go. Make sure you make future backups using the newer version of CWM.
[Nexus 7 Android Development] DataHawg:
Excellent. Thanks phonic. Yes, the first backup I made was with version 5 that came in the Root Toolkit. I made it right after I unlocked and rooted. I copied that one to my pc and after that installed CWM 6.0.1. I was able to delete the backup made with 6.0.1. I think I'll make another backup now that I have my apps installed and see if I can restore the first one. If it restores I'll probably just leave it there and make a new one from time to time. I have the 168gb model so having 2g of backups isn't a problem. Thanks again.
[Nexus 7 Android Development] phonic:
Np. Congrats on getting a 168GB model. I wish I could have gotten that one. I'm stuck with this lousy 16GB tab. :D
[Nexus 7 Android Development] DataHawg:
Made a fresh backup with CWM 6, restored the original I made with CWM 5, restored back to my fresh backup without a hitch. My blobs folder is back in the CM folder where it belongs and I won't delete it again! I'll share your zip with others who have backups they can't delete.
[Nexus 7 Android Development] thephased:
Would anyone know why the heck is my dated cwm backup folder only 20.2mb? My blobs folder is around 500mb. CWM said it used around 1300mb after it completed the backup and generated an MD5 sum.

I feel pretty screwed now if I need to go back to stock. I guess I can always flash the factory image.

I have CWM 6.0.1.0 non-touch recovery.

I also can't get into recovery by holding volume up/down + power. After the bootloader comes up and i select recovery, the screen just hangs at the Google logo.

I can get into recovery from adb ok it seems though.
[Nexus 7 Android Development] smirkis:
the blobs is your info

backup communicates with the blobs

new backups only store the differences, unless its a different rom

the issue of not being able to enter recovery is a bootloader issue, and is known. were all hoping this issue gets resolved some day with maybe a custom bootloader. connect your device to a PC and try again. or, use an app such as goomanager or rommanager

were all in the same boat. without a working os, or near a PC, were kinda ****ed. if u flash a bad rom and it wont boot, the only way to fix it is connect to a PC and enter recovery manually with the button combo
[Nexus 7 Android Development] thephased:
Thanks for clearing all that up. I understand how the blobs folder works now.

Much appreciated. I can rest a lot easier now.
[Nexus 7 Android Development] StuMcBill:
I made a backup of my MoDaCo ROM, flashed ParanoidAndroid and decided to go back to my MoDaCo ROM, however, I got an error while restoring /data backup. Any ideas why this would be? I am on 6.0.1.0.

Also, how does blobs work when you are backing up 2 different ROMS? For example, I have my MoDaCo rom backed up now, what will happen to the blobs when I backup ParanoidAndroid? Would I still be able to restore to MoDaCo?

Sorry if these are silly questions?
[Nexus 7 Android Development] StuMcBill:
Just deleted all my backups, backed up my current rom and tried to restore it - works no problem. I guess my backup was corrupted somehow.

My question still stands though, will backups work while going across different roms? (MoDaCo -> AOKP for example)

Cheers

Stewart
[Nexus 7 Android Development] mrich137:
I think the backups just check the hash to see if the files are identical, skip if they are and backup if they aren't. If you're backing up different roms I would assume it would still work the same way, backing up different versions and skipping identical ones, but I don't know how different the files are from one rom to another and how much would be skipped.

In theory I think it should work but I can't say for sure.
[Nexus 7 Android Development] nawoa:
This "blobs" thing is retarded. Try backing it up to a PC. MTP is so damn slow it takes forever and a day to start actually copying anything because there's so much crap to sort through. So I should just keep it on my device? Right, I'll keep 2 GB of backup data on a device that only has 13 GB usable and no expandable storage. Heaven forbid I also have Titanium backups, that's like 4 GB.
[Nexus 7 Android Development] cHarOn99:
sorry wrong thread
[Nexus 7 Android Development] holyzombiejesus:
Grrr my mac keeps downloading all the recovery files as ".ndif" files, which don't work.
[Nexus 7 Android Development] DataHawg:
Why are your TB backups 4gb? How many copies are you keeping anyway? I have mine setup to only keep one copy and when I run a batch backup again it deletes the old ones. You can also get an OTG cable for a buck fifty and put stuff on a thumb drive for storage. I have 2 nandroid backups on mine (one from right after I rooted and one recent one) and a TB backup and still have plenty of free space left. If you want a bunch of movies and videos put them on a thumb drive or a Kingston WiFi drive. Amazon has the 16gb unit on sale for 40 bucks and you can stream movies direct from the drive without copying them over. I haven't tried one but great reviews on Amazon's sight.
[Nexus 7 Android Development] smirkis:
I never store backups. Nor do I ever use TB. A nice fresh install is always nice to start with, and one good backup from just before flashing is always nice to have. Delete all others, and watch over time how much you never really worry about this stuff.
[Nexus 7 Android Development] wing_addict_usa:
I have the same problem, are you encrypted by chance? I am :(
[Nexus 7 Android Development] landstander:
You can likely work around this, provided that you're able to boot into recovery and have a working adb installation.

Full disclaimer: This is not something I came up with... I originally saw it described on RootzWiki. I have not verified that it works on a N7, but will try it later tonight and report back... my N7 is encrypted, but I made a point of rooting it beforehand. I've used it successfully on my Galaxy Nexus phone, however​

Once you're booted into recovery and verify that adb is functional (via "adb devices" or similar), what you want to do is create a tmpfs (ramdisk) filesystem mounted at /sdcard. This example makes it 300 MB in size.

adb shell mount -t tmpfs -o size=300M,mode=0777 tmpfs /sdcard

Next use adb to push the relevant file(s) across.

adb push whatever.zip /sdcard/

If all went as expected, the file will be visible to CWM at this point and you can flash it normally. There's a reasonable possibility that we'll need to tweak the commands a bit, however, as I seem to recall that the N7 uses /data/media in recovery rather than /sdcard... should be easy enough to sort out.

Now there are a few caveats. The first, of course, is that tmpfs is a transient filesystem... it only exists until the device is rebooted, so you'll have to do this anytime you decide to flash something new. The second is that any attempt by the zipfile's installation script to mount or access /data will obviously fail, so this might not be useable in all cases. None of the files I've looked at do this (Superuser and SuperSU certainly don't), so it probably isn't an issue in most cases.
[Nexus 7 Android Development] landstander:
The example I provided above actually worked to flash Superuser 3.2-RC2, except for one significant detail... you have to use TWRP instead of CWM. It seems that CWM insists on mounting /sdcard immediately prior to flashing the zip, which isn't necessary (although it would't know that) since we manually populated it, and then aborts when the attempted mount fails. TWRM, on the other hand, saw the zipfile immediately, and allowed me to flash it without incident. It did show some error messages related to mounting /data at the very end (after the flash had completed), but I chose to ignore them since I already knew that Superuser doesn't place anything there.

I suspect that following the full steps from the original RootzWiki post (extracting update-binary and updater-script from the zip, and running them manually) would have been successful in either case, but I'm not going to worry about testing that scenario
[Nexus 7 Android Development] jt.one:
im a bit confused with the original post, because not sure how updated it is-

can somebody enlighten me ? :)

if i flash cwm recovery through pc adb fastboot, will it be permanent?

or will i have to get inside root explorer and delete the "stock recovery"

and THEN, flash cwm recovery via pc adb fastboot?
[Nexus 7 Android Development] smirkis:
just flash with rom manager. if you want the touch version use fastboot

the newest versions delete that file for you.
[Nexus 7 Android Development] catalinu:
bricked? - SOLVED

Hy guys,

I had the 5.0.5 CWM installed with the 4.1 JB on an unlocked loader. An OTA update seems to locked it (the lock on google boot), but I didn't paid attention. I installed CWM 6 and downloaded the zip found on the 2nd post on that thread for the touch cwm. I rebooted in recovery (in 6.0), installed the zip (without any error) and asked cwm to reboot into recovery to test the touch cwm. It started to boot loop with a black screen :eek:

I can't boot in recovery (with 3 buttons, even after I took the batery out). If I connect it to PC (with correct USB drivers, I used them a lot before), in windows 7, it makes a da-da-da sound (a fault device sound?) and not the da-ti sound for a correct one. But it detected the device (the OMAP4440 apperas for one second in device manager) but it disapears after one second (the ti-da sound that the USB is disconnected) and it loops on da-da-da / ti-da sounds (connected / disconnected), so I am unable to run adb commands....

Any suggestion?

thanks

Edit: Solved, thanks to http://forum.gsmhosting.com/vbb/f634/unbrick-dead-samsung-gt-i9250-galaxy-nexus-gt-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/
[Nexus 7 Android Development] Niksko:
Having a bit of an issue. I flashed CWM a while ago (2 weeks). I've just gone to try and do a backup and my N7 just sits at the Google logo after I've booted into the bootloader and selected the recovery option.

Any ideas?
[Nexus 7 Android Development] smirkis:
connect a USB to our n7 and PC and try again. or use an app to reboot to recovery within the os. like goomanager or rommanager.

its a bootloader issue, not recovery
[Nexus 7 Android Development] htchoi5609:
Nice :)
[Nexus 7 Android Development] rion_j:
any way to get to the recovery when in a bootloop? i've bootlooped a few times and have had to re-install the factory image twice now. :( when in the bootloader, and choosing recovery your never actually taken to cwm recovery.
[Nexus 7 Android Development] mrich137:
When on the bootloader screen type "fastboot reboot" which should force it into rebooting correctly. Then either use rom manager, adb or any other method to get into recovery. The adb command should be "adb reboot recovery"
[Nexus 7 Android Development] smirkis:
or, do this..

this needs to be sticked somewhere, but if you connect your nexus to a PC via USB, do your button combo to enter fastboot/bootloader and select recovery, it boots fine. without the USB connected. it hangs at the Google logo

the bootloader needs to be fixed lol.
[Nexus 7 Android Development] rion_j:
thanks for the suggestion. fastboot reboot works great, but i tried the adb command to adb reboot recovery but i get an error "device not found" i assume this is related to drivers, but i'm on a mac so shouldnt matter.
[Nexus 7 Android Development] gokart2:
Does the newest touch version compress backups?
[Nexus 7 Android Development] MacZzang:
I followed exactly what it says here and now my tab wont boot into recovery and when I just try to boot it up normally I get boot loops.. what to do now? :(
[Nexus 7 Android Development] navodwickra:
download the recovery image from

http://www.clockworkmod.com/rommanager/

then hold power and volume down until the device goes to bootloader then connect to pc and flash that image via fastboot
[Nexus 7 Android Development] redmonke255:
I used the update.zip from 6.0.0.6 to update to 6.0.1 touch but the version is still listed as 6.0.0.6. Anyone else's like this?
[Nexus 7 Android Development] racer321:
What do i flash?

I installed ROM manager on my Nexus 7 and it installed CWM 6.0.1.0, But now I would like the touch version...which file should I flash? :)
[Nexus 7 Android Development] smirkis:
download the touch version from that link, and use fastboot
[Nexus 7 Android Development] neilrl79:
Any word on 6.0.1.1? The ability to create a .zip of your current set up is something I've been looking forward to for a while.
[Nexus 7 Android Development] WinDroidGuy:
It's not available for the Nexus 7 or Galaxy Nexus yet unfortunately :( just some LG devices and Galaxy Tabs and other random devices

Sent from my SCH-I535
[Nexus 7 Android Development] spaceman860:
6.0.1.1 is available for the galaxy nexus

Sent from my BAKED Nexus
[Nexus 7 Android Development] WinDroidGuy:
Hmm, I didn't see it listed on the ROM Manager site. Maybe I overlooked it.

Sent from my SCH-I535
[Nexus 7 Android Development] 350d:
weird, can't get in cwm recovery at all!

I tried fastboot flash, fastboot boot, rommanager(install and restart recovery), even tried from codename 3.1.1 power menu ( flashed from nexus toolkit). Not work. More I also go back to latest factory image and do flash cwm recovery again, but is still ****.
[Nexus 7 Android Development] kptnk:
Recovery Bootloop

guys i have a huge problem here : i flashed the 6.0.1.0 zip, made a backup, wiped and flashed another rom ; then reboot system..and i'm in bootloop in recovery ; i always go back to cwm, i can't even power off the N7, nor go to fastboot mode.

as i don't have another recovery to flash, i'm stuck :(

anyone could help please ?
[Nexus 7 Android Development] smirkis:
do u have adb? try adb reboot bootloader.

or, press n hold the power button til it reboots
[Nexus 7 Android Development] kptnk:
holding power button doesn't work : i always come back to cwm

I'm trying to use adb right now...i don't manage to use cmd to use it for now...:(

EDIT : OK, i managed to reboot in fastboot using adb ; and then flash twrp...but i don't what happened with cwm, that's why i changed of recovery ; thanks anyway.
[Nexus 7 Android Development] neilrl79:
How did you install CWM? I ask because there was a .zip that if you flashed it with twrp it would go into a recovery loop. Wugfresh's nexus tool got me out of it. Had to flash the stock .img and re-do everything but it didn't take long.
[Nexus 7 Android Development] kptnk:
That's exactly what i did : i was on twrp and wanted to try cwm (had my N7 today, so i'm trying quite different things ;) ), so i flashed the flashable zip released on official cwm's thread OP....and welcome to Recovery Bootloop land !!!!

I haven't had to flash a stock image, because once in Fastboot mod, i used Mskip Toolkit to flash twrp back. My problem was to go back to fastboot, and with adb this was done in 3 clicks....

So i've learn 1 thing : never again i'll flash a cwm zip ! i'll use exclusively adb now.
[Nexus 7 Android Development] neilrl79:
good call... I'm pretty sure I suggested that a disclaimer be put on the link for that zip because it was a known issue but I guess that never happened.... or I thought about suggesting it and forgot.....
[Nexus 7 Android Development] neilrl79:
I made this on the recovery builder, it's cwm 6.0.1.2, back-ups seem to work but the new feature of making a .zip of your currently installed rom seems to be broken. Figured i'd post it in case someone wanted to mess around with it.