yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] phonic:
Install the Android SDK and use adb to get the tablet to reboot into recovery.
[Nexus 7 Original Development] cpom1:
Thanks man. works great
[Nexus 7 Original Development] theoneofgod:
Can you boot into CWM using the bootloader (holding down vol - and power)
[Nexus 7 Original Development] phonic:
Yes. I think you have to hold both Vol buttons though. Not sure offhand since I did it myself through adb.
[Nexus 7 Original Development] Kidromulous:
Yes. When Andy is on his back hit the down key twice and hit power. Recovery
[Nexus 7 Original Development] theoneofgod:
When I do this, all I get is the Google logo, nothing else happens.

If I reboot into recovery using adb it works fine.
[Nexus 7 Original Development] philmein:
same here m8 paul says hes creating a script to help us reboot into recovery is fine its when you try from a coldboot ie bootloader you just get the black android screen and no cwm
[Nexus 7 Original Development] theoneofgod:
When using r2, I can't delete the backup made with any file explorer. Any help?
[Nexus 7 Original Development] phonic:
This has already been discussed in length in the thread. It was an issue with that version of CWM.

The solution is to download this zip:

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

and install it via CWM.

Note: It will delete ALL of your CWM backups in the /sdcard/clockworkmod/backup directory.

Then you can upgrade to R3 or the official release which doesn't have that issue.
[Nexus 7 Original Development] theoneofgod:
Thanks, but the latest CWM creates a ton of those blob files that I can't backup to my flash stick via OTG...
[Nexus 7 Original Development] phonic:
I haven't tried this myself, but I'm not sure why it would fail. Are you trying to copy them or move them? If the latter, it's probably related to the issue in R2 because of the way it created the "backup" directory.

Try flashing the zip, erasing all the backups, perform a new (R3 or production) CWM backup, and then try copying/moving them to USB.
[Nexus 7 Original Development] theoneofgod:
I am using R3 now, deleted all previous backups.

I tried to copy using ES File Explorer. It copies all from the original folder, but fails on anything regarding the blobs folder.
[Nexus 7 Original Development] phonic:
Ok, so I have a theory on this.

First, I checked the directory/file permissions and everything looks kosher.

However, there are (in my case) 9322 files in the blobs folder. Trying to just open the directory in Astro (file manager) caused it to hang. And 'ls' via terminal shell took about 20 seconds to just list them all.

Within the terminal shell, I *was* able to copy a single file to /sdcard/ manually, so it's definitely not a bug or permissions issue.

So I would guess that the large number of files is causing a problem with the file explorer app itself. If you need to copy it off, I would suggest trying various file managers to see which one(s) work, or use an app like Terminal Emulator to do it manually. Ie:

cp /sdcard/clockworkmod/blobs/* /mnt/sda1/blobs/
[Nexus 7 Original Development] budde2:
Is anyone else but me getting horrible quadrant scores

My Galaxy Nexus Gets higher scores
[Nexus 7 Original Development] Shano56:
Sorry about your low benchmark scores, but how is this related to recovery
[Nexus 7 Original Development] theoneofgod:
I get 4300 on quadrant, I think that's pretty good.
[Nexus 7 Original Development] sgt. slaughter:
lets keep the talk on recovery guys.....and try to not attack one another as we all are on the same team in the end of things! :)
[Nexus 7 Original Development] thebobp:
Does Koush include the same feature that makes the recovery permanent?
[Nexus 7 Original Development] thracemerin:
Yes
[Nexus 7 Original Development] zborn:
Im having the same issue. Ive tried to change permissions and some other things and. Nothing works. And they are two backups.
[Nexus 7 Original Development] Land Master:
Read the entire thread and pay specific attention to post #74

And ... This was an interim recovery and although it works fine there is an official recovery (both CWM and TWRP) available.

You should have flashed an "official" recovery but now you have additional steps to perform.
[Nexus 7 Original Development] theoneofgod:
Hi. I simply ran

adb pull sdcard/clockworkmod/

and it is now pulling all blob files.

Thanks.
[Nexus 7 Original Development] phonic:
Yup, that would work too.
[Nexus 7 Original Development] theoneofgod:
Not good. After more than half way down the line, it started spamming "Permission denied" so, this doesn't work.
[Nexus 7 Original Development] Shano56:
Try

adb pull /data/media/clockworkmod
[Nexus 7 Original Development] erica_renee:
Am i missing something

On my acer a500 When i boot into recovery i can access removable storage such as usb drive . Is there something im missing here. or is this just not a feature built into cwm or twrp recovery. With the nexus not having a sd card slot this feature should be on top of priority list as far as something to add ..

Sorry if this has been asked before but its very important as in order to do a full format and flash you have to have tablet connected to adb and computer..to push the files onto the device after you format all..

thanks in advance

Erica Renee geeky chic
[Nexus 7 Original Development] theoneofgod:
remote object '/data/media/clockworkmod' does not exist
[Nexus 7 Original Development] Phoenix84118:
So that wipe script didn't work for me. I still can't remove those files.

What's odd though is I made that backup on a different device (for RMA) and copied it to my new one. However even copies of those files trigger the problem.

The old device flashed CWM using ROM Manager (which lists 6.0.1.0). The only reason I switched to 6 from 5 was because 5 uses signed ints for file offsets (I presume), so my backup was over 2GB and unreadable.

What I'm going to do is copy my internal memory contents over to the computer and try to format the internal sd. Is that possible?

EDIT: CWM 6.0.1.0 still has the size problem. When the size of a file reaches 2GB, it rolls over to 16 EB. See screenshot. The actual ROM doesn't have this problem, just CWM.
[Nexus 7 Original Development] phonic:
Where are you CWM backups stored? The wipe zip will erase the /sdcard/clockworkmod/backup directory. If you renamed/moved it to something else, it won't work. Assuming it is the same, then flashing that zip should work.
[Nexus 7 Original Development] Phoenix84118:
Oh you know what, I was thinking it was erasing the entire /sdcard/clockworkmod directory, not the backup subdir. The blobs directory was also a problem, and that's at the same level iirc. My bad. I didn't pay attention to see if the backup directory was empty.

Anyway, the SD card wipe worked. CWM's format /sdcard option still works as expected. The screenshot was me copying my sdcard data back over.
[Nexus 7 Original Development] droid_1989:
A little unrelated,

But can't get into CWM recovery using vol keys and power, someone told me it's a known issue, anyone know if anyone's working on it? And if it's bootloader or CWM that's at fault?
[Nexus 7 Original Development] ben805:
I like the 5.8.0.2 much better for back up, not a fan of the incremental style with thousands of mini folder on 6.0.1.0. The only thing missing from the version 5 is it can't mount SDcard but not sure it work on the 6 anyway. :)
[Nexus 7 Original Development] chris.wueste:
To boot into the bootloader without adb, make sure the power is off, then hold both volume buttons and press and hold the power button, thats essentially all three buttons at once. it will immediately launch the bootloader and you can then choose to go into recovery, or reboot and so on.
[Nexus 7 Original Development] sabesh:
What's the difference between this and the one from ROM Manager? I plan to purchase a Nexus 7 and flash the MCR ROM today. And the instructions for that ROM say to install it via ROM Manager. Thanks.
[Nexus 7 Original Development] paulobrien:
Those instructions are wrong, i'll fix them. :)

P
[Nexus 7 Original Development] philmein:
Any luck with the script Paul tried this command adb shell mount /system && adb shell rm /system/recovery*'

And I am getting message system cannot be found however the adb shell mount command works on its own but when I put the full command in I get system cannot be found ( I take it its all one long command and not seperate ).

Still getting the black Google screen whenever I try to enter recovery via boot loader. Running this cwm and modaco ROM.

BTW thanks for the vplayer tip it rocks on the nexus 50% off too.
[Nexus 7 Original Development] smirkis:
do them separately

adb shell mount /system

adb shell rm /system/recovery*
[Nexus 7 Original Development] philmein:
im getting this error when i try?

Microsoft Windows [Version 6.1.7600]

Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\phils gigabyte\Desktop\ADB Made Easy - Portable> adb shell mount /syste

m

C:\Users\phils gigabyte\Desktop\ADB Made Easy - Portable>adb shell rm /system/re

covery*

rm: can't remove '/system/recovery*': No such file or directory

C:\Users\phils gigabyte\Desktop\ADB Made Easy - Portable>adb shell rm /system/re

covery

rm: can't remove '/system/recovery': No such file or directory

C:\Users\phils gigabyte\Desktop\ADB Made Easy - Portable>

and if i use just adb shell mount i get this

Microsoft Windows [Version 6.1.7600]

Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\phils gigabyte\Desktop\ADB Made Easy - Portable>adb shell mount

rootfs on / type rootfs (rw)

tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)

devpts on /dev/pts type devpts (rw,relatime,mode=600)

proc on /proc type proc (rw,relatime)

sysfs on /sys type sysfs (rw,relatime)

/dev/block/platform/sdhci-tegra.3/by-name/CAC on /cache type ext4 (rw,nodev,noat

ime,nodiratime,user_xattr,acl,barrier=1,data=ordered)

/dev/block/platform/sdhci-tegra.3/by-name/APP on /system type ext4 (rw,relatime,

user_xattr,acl,barrier=1,data=ordered)

C:\Users\phils gigabyte\Desktop\ADB Made Easy - Portable>
[Nexus 7 Original Development] sabesh:
After flashing this, I get a picture of the Android with open hatch with a red triangle with an exclamation mark on it. What am I doing wrong? Thanks.

EDIT: That looks like stock recovery. So, this interim CMW didn't flash after all, despite it flashing correctly:

C:\root>fastboot flash recovery recovery-clockwork-touch-5.8.0.2-nexus7-modaco.img

sending 'recovery' (6182 KB)... OKAY

writing 'recovery'... OKAY
[Nexus 7 Original Development] :
Worked like a charm!

---------- Post added at 10:25 PM ---------- Previous post was at 10:24 PM ----------

use volume buttons to navigate to recovery then select with power button.
[Nexus 7 Original Development] spences10:
Could you not just use the recovery builder from koush?

http://builder.clockworkmod.com
[Nexus 7 Original Development] Land Master:
On other devices I have used there is a file that executes on boot (bat file for lack of better terms) that re-writes the stock recovery partition. Simply renaming this file .bak insures that any custom recovery remains persistent after a reboot. Is it the same for this device?

If so, can you point us in the right direction of that file as I would rather not delete the entire "recovery" directory. OR, can we simply rename that directory?

Thanks for your contribution!!
[Nexus 7 Original Development] paulobrien:
Yes you can, as long as you don't want it to work.

It's called '/system/recovery-from-boot.p' IIRC.

P
[Nexus 7 Original Development] iorecki:
We type this in the boot loader or recovery ? I flashed cwm but can only get into after initial flash. I understand the ROM reverts the the recovery but I can't access stock recovery now either...
[Nexus 7 Original Development] Bxsteez:
Hmm I can't seem to get into recovery. I keep getting a red triangle. I've read that stock recovery is overwritting CWM?? Anyway around this?
[Nexus 7 Original Development] smirkis:
Make CWM Permanent -

1. Boot into recovery​

2. Go to Mounts and Storage​

3. Mount /System​

4. Type in Terminal​

adb shell

cd /system

mv recovery-from-boot.p recovery-from-boot.bak​
[Nexus 7 Original Development] paulobrien:
I'm going to update my superboot to resolve this tomorrow. Stay tuned.

P
[Nexus 7 Original Development] Beamer9408:
Don't want to confuse anyone but we can run adb commands in the bootloader on this device?
[Nexus 7 Original Development] Bxsteez:
Worked great...

Might want to add the booting into bootloader and fastbooting recovery manually instead of using the toolkit.
[Nexus 7 Original Development] TahrirSquare:
I have the same problem you guys are experiencing with CWM, when I try entering recovery from the boot loader it just puts the Google image with the unlocked lockpad. However when I use adb (adb reboot recovery), it takes me to CWM with no problem, so it is at least working via adb right now. Also works if you use android terminal emulator, just type SU press enter and allow as super user, then type reboot recovery and press enter in the terminal emulator it will then boot you into recovery with no problem.
[Nexus 7 Original Development] philmein:
Looking forward to this spent hours trying to sort this today

Thanks paul:o
[Nexus 7 Original Development] iorecki:
tried this and said the file didnt exist...

so i went and loaded MoDaCo Rom since i was in recovery anyways.

i can reboot into recovery(cwm) through the power options in the rom....but still cant access recovery via the bootloader unless i flash it again.

when i try to access recovery from the bootloader it just hangs at the google padlock screen.

it lets me do adb commands from the bootloader and recovery
[Nexus 7 Original Development] Land Master:
The file doesn't exist for me either ..... when I ls (list) the system directory this file is not there. I am wondering if this file gets added as part of the update to 4.1.1?

This is my assumption because I have not updated and I am NOT losing access to Clockwork (it is NOT being overwritten with the stock recovery) upon a reboot which is the reason these steps were included.

And, for what it's worth, I am not seeing the 4.1.1 update now that I have installed Clockwork and I have seen this behavior on prior devices where it won't take an OTA unless the stock recovery is in place.

These are all assumptions on my part but they make sense to me. Those of you that have been unable to complete those steps (mv command) ... are you still on 4.1 or have you updated?
[Nexus 7 Original Development] thebobp:
What's the difference between this one and birdman's?
[Nexus 7 Original Development] phonic:
This one works.
[Nexus 7 Original Development] Dsmforlife92:
Never mind
[Nexus 7 Original Development] spences10:
I thought it was an automated process now, what doesn't work?
[Nexus 7 Original Development] paulobrien:
The updated r2 revision removes the 'recovery-from-boot.p' file on /system which overwrites the recovery when the system is launched. For this reason, it's recommended you launch the recovery at least once after installation.

The recommended install method is 'adb reboot bootloader && fastboot flash recovery r2-recovery-clockwork-touch-5.8.0.2-nexus7-modaco.img && fastboot boot r2-recovery-clockwork-touch-5.8.0.2-nexus7-modaco.img'.

P
[Nexus 7 Original Development] evonc:
Flashed r2 and it's working great. Amazing work! Thanks!

Sent from my Nexus 7
[Nexus 7 Original Development] Dsmforlife92:
Still new to this nexus thing how to I flash this to I use my computer
[Nexus 7 Original Development] TahrirSquare:
Can you boot into recovery from the bootloader?
[Nexus 7 Original Development] philmein:
i cannot boot into recovery after flashing this and new superboot going back to stock then trying again
[Nexus 7 Original Development] TahrirSquare:
Not even using ADB or Rom toolbox(rebooter option)?
[Nexus 7 Original Development] philmein:
yes it will work with that just gone back to stock relocked bootloader then unlocked now i will root with pauls superboot install superuser from the market then install new cwm and ill report back

edit still not working ill try it with a custom rom

---------- Post added at 05:58 PM ---------- Previous post was at 05:10 PM ----------

cwm still does not work from bootloader im afraid it least not for me
[Nexus 7 Original Development] Gam3r 4 Life:
Anyone have any idea why I cant delete any backups made with this. Ive tried root explorer, es file explorer, and it says that it gave root permissions, but then says unable to delete. When I delete them from my PC it shows them disappear, but then they are still there.
[Nexus 7 Original Development] Kidromulous:
I have the same problem though I haven't tried it on a pc yet. I haven't figured out how to delete them either.
[Nexus 7 Original Development] phonic:
I haven't tried myself, but I did a quick glance at the permissions, and nothing indicates a problem. In fact, both the backup directories and the individual backup files are all set 664, with the group as sdcard_rw, which the normal user is in. So you shouldn't even need root to rm them.
[Nexus 7 Original Development] philmein:
Dito can note delete nandroid backup I made
[Nexus 7 Original Development] Gam3r 4 Life:
Ive renamed them, moved them, still cant delete. It also wont let me change the permissions. So they are locked somehow.
[Nexus 7 Original Development] phonic:
I don't want to attempt to delete mine, since I only have one backup right now. But I assume you are talking about:

/sdcard/clockworkmod/backup/(date/time/etc. directory)/files

Correct?

Are you trying to delete the directory (and if so which one) or the files themselves?

Have you looked at the permissions?
[Nexus 7 Original Development] Gam3r 4 Life:
Just the files themselves because Im running out of room. I have them backed up on my PC. I tried a different file explorer and it said that the sd card was read only. So I tried to change the permissions of the sd card but that didnt work. Can anyone else confirm they are able to delete back ups?
[Nexus 7 Original Development] Nexcellent:
Weird, i can delete Nandroids no problem at all :confused:
[Nexus 7 Original Development] Gam3r 4 Life:
Well, I have no idea then. Heres a picture of my permissions.
[Nexus 7 Original Development] phonic:
Weird, your directory permissions are different then mine. Try changing it to 777 (or rwxrwxrwx). Also, try installing/running a terminal app and manually deleting the directory "ie: rm /blah/blah/blah". See if it works without root first, then (if not) try running su first then rm'ing them. I have to assume it will work in the latter scenario. Worst case, it should tell you why it fails.

The only possible thing I can think of off the top of my head, assuming Root Explorer is really running as root, is if the files/directories are chattr'd immutable. Not sure how that could have happened, but it would result in a similar problem.
[Nexus 7 Original Development] evonc:
Interestingly, I cannot boot into recovery from bootloader until i have my nexus 7 plugged into my pc using a usb cord. Attempting to go to recovery via bootloader w/o being connected on usb results in the standard Google text screen and thats it.

I noticed this while browsing the Q&A section and a thread that suggested that they couldn't boot into recovery without usb cord being plugged in so i tried it and voila, it seems to be the culprit.

Thread: http://xdaforums.com/showthread.php?t=1777058

Credits to go kaywoo and others for noticing this!
[Nexus 7 Original Development] Gam3r 4 Life:
Im still unable to delete the backups, and Ive tried everything I can think of. Is there a way to wipe the whole internal SD Card?
[Nexus 7 Original Development] neilrl79:
Curiosity got the better of me and I tried to delete my nandroid and sure enough it won't delete. Also these back ups are huge!
[Nexus 7 Original Development] Gam3r 4 Life:
Glad to see its not just me. Ive posted a thread in the Q and A section asking for some help on this.
[Nexus 7 Original Development] Nexcellent:
I take it back.. i am unable to delete them either :(

If i delete on my PC, they will disappear but will show up again if i exit and come back into the folder.

I am sure Paul will fix this :D
[Nexus 7 Original Development] Gam3r 4 Life:
I hope he can, but this isnt a rom issue. I went back to stock and still couldnt delete them.
[Nexus 7 Original Development] Nexcellent:
Back to stock as in overwriting CWM back to stock recovery? That's crazy weird.
[Nexus 7 Original Development] Gam3r 4 Life:
No, just went back to a CWM backup I had of stock rom, before flashing Modaco.
[Nexus 7 Original Development] phonic:
Argh, this is NOT good. I just tried deleting my backup. It wouldn't work. I'm trying to find a work around..... The backup is 2GB, which is taking up a huge portion of my sdcard. I hope someone finds a fix to this soon.... I wonder if it would work via a flashable zip?
[Nexus 7 Original Development] Gam3r 4 Life:
Your telling me, Ive been working on this for hours. There has to be a way.
[Nexus 7 Original Development] sabesh:
Flashed perfectly! All good.
[Nexus 7 Original Development] phonic:
I FIGURED OUT A WAY TO DELETE THE FILES!*@&!*(@&*!@! WOO HOO!!(@!(@

I was scared for a minute. I was able to do it via CWM directly, using a custom flashable zip.

I'm putting together one that will erase the entire backup directory, as I just tested out a single file so far. Once I confirm that works (ie: deleting /sdcard/clockworkmod/backup) I will post it for everyone else.

---------- Post added at 09:21 PM ---------- Previous post was at 09:00 PM ----------

Ok, so some good news and some bad news.

The good news is, I was able to put together a flashable zip that WILL DELETE the entire CWM backup directory from the sdcard. It is available here:

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

You simply need to flash it via CWM. Easy peasy. I confirmed that the directory/files were all removed, AND the storage space is now available for other files (I checked df before and after).

The bad news is, before attempting to delete the directory, I first tried changing the permissions (recursively) to see if that was a better "fix" for this problem. Unfortunately, even with the directory 777 and the files 666, I still could not manually delete them through the system. Which means, whatever bug is causing this problem is much more severe than a file/directory permission thing.

In any case, until the CWM developer can figure out a way to fix this bug, at least we have a way to manually remove the backups and get our storage space back.

The script in the zip is very simple. It just does a recursive delete on /sdcard/clockworkmod/backup.

Enjoy!
[Nexus 7 Original Development] smirkis:
Paul will fix this. just be patient.
[Nexus 7 Original Development] burpootus:
Flashing the r2 version now. I've probably flashed recovery on this thing 6 or 8 times since Saturday. It's been very frustrating. I can't seem to keep CWM working.First it was the "not removing the recovery-from-boot.p file" thing, the last time seems to be the C to D update (I was in CWM to flash it). Haven't figured out the exact sequence, but it seems to quit working when I power down and back up. Sometimes it will only boot into recovery from ROM Manager. Very few times have I been able to boot into recovery using the buttons. I've seen the android laying on his back with a red triangle or the screen with google and a padlock on it until I'm blue in the face. I've used recoveries from 3 different dev's trying to get one to stick. This is my first Nexus device, what is the deal?!?!

Successfully flashed r2 version, while still in CWM, did nandroid backup. Rebooted, opened ROM Manager, selected reboot recovery, successfully entered recovery. Rebooted, powered off. Attempted to enter recovery with buttons, hold down power and volume down to get bootloader screen. Toggle volume to recovery, push power to enter, stuck on google with padlock screen, no recovery. Powered down and back up, successfully entered recovery from ROM Manager. Still no recovery from bootloader with buttons.
[Nexus 7 Original Development] sabesh:
Red triangle with exclamation means stock recovery, not CWM. So, it didn't flash properly.

Sent from my Nexus 7