yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] BennyJr:
Can you adb boot into recovery from the bootloader?

Oh and you can't 'adb reboot' in fastboot just hit the power button.
[Nexus 7 Android Development] Archangel:
yes and can do this while in fastboot (bootloader mode)

fastboot boot r3-recovery-clockwork-touch-6.0.0.4-nexus7-modaco.img (or whatever the name of your recovery.img is)
[Nexus 7 Android Development] BCD90:
The thing is when im in bootloader mode i can not access adb. I have tried this but it will not let me.
[Nexus 7 Android Development] BennyJr:
Bootloader = fastboot. Any adb commands wont work
[Nexus 7 Android Development] mrich137:
Which is correct. You won't be able to do adb commands in the bootloader. The command he asked you to try was a fastboot command, which should work
[Nexus 7 Android Development] ericsch333:
Make sure the drivers are installed had this problem with windows 7 download the naked driver pack and follow the instructions
[Nexus 7 Android Development] jumpman1229:
Okay so I need a little help with cmw backups. I want to delete a nandroid backup of a rom but I've noticed all the data is actually contained in the blobs folder. How do I know which blob files correlate with a certain nandroid backup?
[Nexus 7 Android Development] osm0sis:
I explained this literally 2 posts ago. Come on, man!

Edit: WinDroidGuy, can you add the info re: blobs, etc. from this post to the OP? It might help with these questions for the people who *somehow* find the time to read it before posting their questions. :mad: ;)
[Nexus 7 Android Development] cyanogendroid:
HELP!! My n7 WILL NOT get out of recovery! It just reboots cwm no matter what!
[Nexus 7 Android Development] osm0sis:
Weird. What'd you do immediately before that began? Flash something in CWM? You possibly borked your ROM and need to revert whatever changes you made.

You could also try:

adb reboot bootloader

then either fastboot reboot, or select Start on your phone.
[Nexus 7 Android Development] cyanogendroid:
Alright, I fixed it. The tablet would not boot into anything but cwm no matter what. Im no newb but I just got spooked by this. I ended up having to use the Nexus 7 Toolkit (which is awesome) to download a stock image and write it to the the device. That was the only way I could get it out of cwm. Phew :eek:

EDIT: thanks a bunch for the help btw
[Nexus 7 Android Development] osm0sis:
Wow! Yeah, reflashing the stock image is a surefire way to revert whatever changes you made. ;) Glad you got it working again.
[Nexus 7 Android Development] jumpman1229:
I deleted the actual folder which was only like 15MB so I don't know how to delete the blob folders associated with it. I went through adao file manager to delete it originally. Obviously I can't try to manually delete it through cwm bc that folder no longer exists
[Nexus 7 Android Development] osm0sis:
Here let me read this for you.

You also clearly didn't follow the link to the blob info in my post or you'd know this twice now.
[Nexus 7 Android Development] jumpman1229:
Lol alright alright. Thanks man!
[Nexus 7 Android Development] HBSN11:
Hey how did you fix this? Exact same thing is happening to me.

EDIT: NVM figured it out. Thanks for posting your fix before!
[Nexus 7 Android Development] hungragezone:
can someone tell me how can i enter recovery mode after installing cwm in nexus 7 :(

nvm i found it :D
[Nexus 7 Android Development] neilrl79:
When I built 6.0.1.3 it would create a .zip but it was corrupt.
[Nexus 7 Android Development] osm0sis:
Did you know it was corrupt just from trying to open it or from trying to flash it? I didn't try to flash mine. I did notice the zip didn't include an updater-script under META-INF like most flashable zips but had an edify file in the root of the zip instead..
[Nexus 7 Android Development] neilrl79:
Well when i tried I got an empty .zip file and a few files other than the zip that could not be moved due to some error which I can't remember now.
[Nexus 7 Android Development] osm0sis:
Ah well it definitely built the zip correctly on my maguro (GN) build from the same time, but it left the zip contents in the /clockworkmod/image/ folder as well. Not sure if that's intended or not.

Either way, try it again with the grouper CWM nightly I linked. I'll try it myself on Friday once I have my N7. :)
[Nexus 7 Android Development] osm0sis:
Figured I might as well post this over here as well... This is a rough changelog I made based on the commits at the CWM GitHub:

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

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

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

Aug 30, 2012 - 6.0.1.3 appears to have properly fixed some threading issues with "key repeating" which koush felt was a big enough deal to merrit a version bump.
[Nexus 7 Android Development] adxgrave:
Sorry if this has been answered before, I can't find it. The thing is I've locked my bootloader after root, can I still updated cwm without unlocking?

Sent from my Nexus 7
[Nexus 7 Android Development] osm0sis:
Relocking was a bad idea since unlocking means a data wipe.

The only way you can update CWM is through CWM now using a flashable zip.
[Nexus 7 Android Development] hungragezone:
i flash cwm using Nexus 7 ToolKit

but i can only go to recovery mode when my nexus connect to PC, without connecting to PC, I can't go to recovery, I pressed vol +, -, power button but when i choose recovery from boot menu, my phone stuck at Google logo. How can i fix this bug :(
[Nexus 7 Android Development] neilrl79:
Yeah, the files were all in /clockworkmod/image/ but the zip itself was empty. I just built a new recovery last night but I went to bed before i had a chance to flash it and do some testing. I'll give it a shot later. Are you building at http://builder.clockworkmod.com and if so, are you using 6.0.1.0 as the input recovery? That is how I'm building it, tho I'm not 100% sure that is right.
[Nexus 7 Android Development] sean.trinidade:
Try the following in this order:

1) fastboot erase cache. If that doesn't help, then do

2) reflash recovery
[Nexus 7 Android Development] neilrl79:
You can't cold boot into recovery unless your connected to a pc, it's a known issue with the bootloader. You can reboot recovery from the os with a widget/ terminal.
[Nexus 7 Android Development] osm0sis:
No need for an input recovery for an Existing Device, just choose grouper from the pull-down on that tab. :)

Edit: I just built fresh 6.0.1.3 touch and non-touch builds just to make sure someone tried to "Publish to ROM Manager" for whatever that's worth.

No changes since Aug. 30 of course.
[Nexus 7 Android Development] neilrl79:
Every time I tried the "existing device" option the build failed, using an input recovery was the only way it built successfully for me.
[Nexus 7 Android Development] osm0sis:
Odd. No troubles here..
[Nexus 7 Android Development] hungragezone:
thank you!

I see what u said when google search but my friend told he can boot into recovery mode without connecting to PC

Now everything is done :D
[Nexus 7 Android Development] osm0sis:
This bootloader seems terrible. Can't boot into recovery from the bootloader, doesn't always switch properly into charging mode when powered off. I wish someone would patch it.
[Nexus 7 Android Development] smirkis:
can't patch it its closed source.

we need a custom bootloader like cyanoboot (ahem fattire lol).

that is the only way. I tried to explain this to fattire but he didn't see it as an issue.
[Nexus 7 Android Development] osm0sis:
Does he own an N7? He'd probably get the idea pretty quick if he did.
[Nexus 7 Android Development] smirkis:
he does. its only a matter of time I'm sure. but hopefully more people notice sooner rather than later.
[Nexus 7 Android Development] kingofcomedy:
Same for me. Any solutions yet? I already reflashed CWM.
[Nexus 7 Android Development] primetechv2:
So, I'm looking for a way to actually delete my backup (without making a new one)... I'd really like to free up some space on my Nexus. Any thoughts, or have I just sacrificed 1GB of my storage?
[Nexus 7 Android Development] osm0sis:
The option is right here:

Backup and Restore

delete > (remove your backups)

free unused backup data
[Nexus 7 Android Development] primetechv2:
thank you. This worked, even with a backup from an older edition that apparently didn't support deletion.
[Nexus 7 Android Development] osm0sis:
Reposting this from the GNex thread to keep everyone informed.

CWM Unofficial "Nightlies" Changelog:

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

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

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

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

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

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

Somewhere in there was a fix so tapping the the border/edge of the main menu doesn't trigger a reboot anymore. I also just noticed my first issue using these newer versions, the backup format (tar/dup) option menu seems broken. I'm guessing this is since the "key repeating" fix in 6.0.1.3. It's only an asthetic issue though, as the default format selection still appears to work fine; just the menu displays options below it from the Backup/Restore menu as well, where it didn't before.
[Nexus 7 Android Development] Vektor67:
I flashed the cwm 6.0.1.0 zip through twrp but now I'm stuck, in that only CWM will boot regardless of what rom I flash. I'm not sure how to get to an adb mode so that I can even flash back to stock and start over. To recap Reboot System brings me right back to recovery. In fact it doesn't appear to be able to turn off. Help Please.
[Nexus 7 Android Development] osm0sis:
Not sure what you did... when flashing a recovery it's definitely always recommended you do it via fastboot/bootloader.. maybe somehow you flashed over your ROM with your recovery?

When CWM is booted you have adb access. Have you used adb before? You need android drivers on your computer to do so, I recommend the Universal Naked Driver project since you only need one set of drivers for all the most common android devices that way..

Anyway, once you're set up open a command prompt in the directory with adb.exe and type "adb reboot bootloader" that should get you so you can flash through fastboot hopefully.
[Nexus 7 Android Development] hanschke:
6.0.1.4 touch for cwm anyone :confused:
[Nexus 7 Android Development] Vektor67:
Here here, I was just web searching for "unofficial" versions to try. I assume that there is a solid reason why cwm is being upgraded for this device, something more than a lack of interest. I was fully TWRP'd but I had one too many soft bricks using that recovery. I sure wish I were knowledgeable enough to build and/or port the latest cwm-touch for the N7. :crying:
[Nexus 7 Android Development] osm0sis:
They're easily enough found and/or created:

1) Head to http://builder.clockworkmod.com/

2) Click the Existing Devices tab.

3) Select "grouper" from the pulldown (if the pulldown only contains "None", refresh/hard-refresh the page until the list loads, there should be ~190 in there)

4) Choose whether you want CWM Touch or not with the checkbox.

5) Click Build.

If there has been a recent build, it will direct you to the recent builds page, with download links for the build server, otherwise it will queue it to be built and give you the build id and link to find it on the build server once it has been built.

Note that once you have it there is no point in building a new one unless there has been a new commit on GitHub:

https://github.com/CyanogenMod/android_bootable_recovery/commits/jellybean ..so don't get neurotic about higher "build" numbers. They're meaningless without a code change. ;)

I just built 2 in writing this:

Touch - http://jenkins.cyanogenmod.com/job/recovery/6832/, and non-Touch - http://jenkins.cyanogenmod.com/job/recovery/6833/

If you want it in a recovery flashable zip, download the update.zip from the OP and replace the recovery.img inside with your choice of the above.

Enjoy. :good:
[Nexus 7 Android Development] Rycon33:
Thanks mate:), just flashed the one you posted(touch version) and everything seems fine. Already tried flashing latest CM10 nightly just now.
[Nexus 7 Android Development] adxgrave:
I read on Koshik's G+ page that he added an option to create flashable zip directly from cwm. Where is it?
[Nexus 7 Android Development] osm0sis:
In 6.0.1.1 and higher.

Please read back at least a couple pages next time, I posted a changelog only 1 page ago..
[Nexus 7 Android Development] Vektor67:
Thank you very much:)

Thanks a bunch, I have 6.0.1.2 on my sgs3 and noticed some differences(I thought)

Mainly I wish to learn to compile from source, I have a couple of fairly powerful machines

which I'd like to use constructively and the more I use Linux the sooner I can give Windows the

'Ol heave ho. I'll flash what you built and work on compiling one of my own.

*off topic*

I'm so close, I'm stuck at extracting the proprietary files, but I've got AOSP & CM d/l & initialized

Before I hit the wall...maybe today :)

*back to topic*

Thanks again, I appreciate your taking the time to help.

I'm so close my Repo's are initialized I'm stuck trying
[Nexus 7 Android Development] WinDroidGuy:
The bootloader bug has been fixed with the 4.1.2 update :D

[DL][OTA][ROOT] 4.1.2 update

You can now boot directly into recovery instead of it just hanging and having to do it via adb
[Nexus 7 Android Development] osm0sis:
Also rotation in the stock launcher :D

WinDroidGuy:
[Nexus 7 Android Development] Rycon33:
Nice:cool:

Tapatalked from my Ace 2
[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, version bump for new device support.

Known bugs:

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

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

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

[Attachments removed since koush is about to release an official 6.0.1.5 with new fixes.]
[Nexus 7 Android Development] TheGoD:
Sorry if this has been ask already, but is there any way to get the old backup behavior back (without the incremental files)?
[Nexus 7 Android Development] osm0sis:
You really should search the thread next time. Seems like you didn't even read the post above yours.. "Aug 04, 2012 - 6.0.1.1 allowed setting the backup format (dup/

tar

)" also "Known bugs: - Backup format (

tar

/dup) option menu displays options below it from the Backup/Restore, cosmetic only."

It's under Backup/Restore -> Set default backup format. Select .tar, there is no indication in the menu that you've done anything but it'll be the old tar nandroids we know and love. To keep that setting active you must not remove the file /sdcard/clockworkmod/.default_backup_format . :good:
[Nexus 7 Android Development] TheGoD:
Yep sorry, just wanted to edit my post. In the meantime I figured out that tar is the old format and installed the .1.5 version posted above. Doing an backup right now^^

Sorry again and thanks for your help.
[Nexus 7 Android Development] C.Hatfield:
Quote:

Originally Posted by fmcfad01

Can you post the img file you built? I went to the builder site earlier today and the only thing you could select from the drop down for devices was 'None'. The site wasn't working for me.

^^This is what I am dealing with - STILL NONE - .... trying to get CWM 6.0.1.4 or .1.5 for my NEXUS 7 ..... have tried via ADB & via making my own zip with previously provided .img files .... I'm getting a little effing frustrated bc I

KNOW

its very possibly some small error I am unable to pinpoint ..... to any questions, most-likely YES, YES annnnd YES (I ALWAAAYS READ/SEARCH FIRST ;))

Can anyone offer me a little help by pointing out the simplest solution to the error I am (likely) making (CWM zip preferably) - pleeaase & many thanks !
[Nexus 7 Android Development] osm0sis:
The img files are 1 page back, as well as the solutions to the other problems you're having. Please read.
[Nexus 7 Android Development] C.Hatfield:
I DID bro .... and

ALWAYS

DO !!!

I am fairly Android saavy (thanks in no small part to XDA & the fact I read/research extensively & rarely even post, unless TO HELP) ... Maybe you'd think I surely would not have bothered to post, eh ?! Been here a few days n all, ya know ?! Now there is another post to lengthen the thread .... ya could've just hooked up a bro/"XDA Member" up (yeah, yeah whatever that means - the point is my stats should say enough - I know how XDA works, I KNOW the 'rules' & the ettiquite) with a quick PM with a CWM.zip in the same time it took you to post your reply that sounds as if you didn't read ALL of mine ? XDA used to be a respectful place .... hmmmmm :confused:

btw, your sig even has a link to the latest recovery but its just this OP .... also, no post in ANY thread explains why the recovery builder is only giving me the 'NONE' options regardless of refresh/hard reset, etc .... that was my main ? to begin with ....:confused: anyone else ???

>>> BTW, I have tried using ADB bc I love THE FACT THAT I LEARNED HOW TO DO IT (always update SDK) & have used that method to fastboot every recovery for a LONG time now, but Win7 x64 isn't recognizing my NEX-7 - only my GNEX .... possible issue with both devices trying to use my Android/Google DEVICE ID ??? Hell, I even tried using the NEXUS 7 toolkit but it doesn't even have the latest CWM recovery - I even PUT the latest .img files in the Toolkit folder to 'Flash' in FASTBOOT > again, point being > much effort invested for naught. Head>Wall.

Also -BEFORE- I posted, d/l'ed the update.zip in OP ... put those .img files from a page back that you're mentioning (yes, replacing the older recovery.img) .... left MET folder untouched .... created new .zip .... annnd nada. Tried 4 different times, using what Android knowledge I have gained That's why I am SIMPLY asking for a hook .... done plenty for others in my years here, obviously not to the extent as you but im sure you cant (honestly) say you've never hit a spot, AFTER ACTIVELY READING & SEARCHING, that you didn't ask for a simple hook AFTER having run into sooo many headaches ?!

Maaaybe not .... that must be awesome. :cool:
[Nexus 7 Android Development] osm0sis:
My post pointed you in the right direction. Of both our posts, yours was the more disrespectful and rude.

But either way, SURE, allow me to answer all of your questions by reposting things from 1 page ago :rolleyes::

"3) Select "grouper" from the pulldown (if the pulldown only contains "None", refresh/hard-refresh the page until the list loads, there should be ~190 in there)"

- And sometimes that takes A WHILE, I've had to do it off and on over 15min to get it to finally pull up the list.

"Note that once you have it there is no point in building a new one unless there has been a new commit on GitHub, so don't get neurotic about higher "build" numbers. They're meaningless without a code change."

- I JUST posted the images as of the latest revision and they are still the newest, so there is no reason to even be wasting the processor time of the build server.

"If you want it in a recovery flashable zip, download the update.zip from the OP and replace the recovery.img inside"

- And if you're spending all this time trying to install it via ADB, why don't you just flash it from the bootloader? No messing with zips. Instant and simple. Since you're so well read I'm sure you know to rename /system/etc/install-recovery.sh after an OTA, and also the flash command, but I'll post it anyway: fastboot flash recovery filename.img ;)

Nope. I believe in teaching a man to fish so he can feed himself. Besides, I don't even have a zip on hand since I just fastboot flash it via bootloader. Or, if I'm feeling lazy, I follow the method I already stated above for making a recovery flashable zip with the new version and then delete the zip afterwards.

Clearly the page has bugs. It can take awhile but the list will eventually populate if you refresh long enough. Possibly clear your browser cache too. And it's hard-refresh by the way; Ctrl+F5 should force your browser to get a new copy of the page regardless of caching.

Yep and now here's another pointless one, answering all of your questions. You're welcome. :good:

Edit: Addendum for your edited post. You should be using the Android Naked Driver, I don't have the link at my fingertips but there's a thread for it on the Galaxy Nexus forums I believe. One driver, all devices. Very nice. Toolkits are bad. Never used one since I wanted to know how to both do and undo everything important for my devices.

As for your attempts with update.zip - did you remember to rename the file from my post to recovery.img so that the one inside the update.zip was properly replaced?

Also, I got you man, here's your hook. :)
[Nexus 7 Android Development] C.Hatfield:
As for your attempts with update.zip - did you remember to rename the file from my post to recovery.img so that the one inside the update.zip was properly replaced?

WERD, yet nada . Been trying NEXUS 7 FASTBOOT FIX .... various methods, dead ends ..... :confused:

All I was trying to say (in NO disrepectful tone at all, I have seen too many DEV's and/or Forum Threads disappear bc of that pointless BS + you ain't getting jacksh*t for help that way - that is the problem with text) .... is that I have NEVER stopped trying, even though I posted for help, I -STILL- haven't stopped reading & re-rereading searching, researching ....

~ Also, it ain't that I don't know HOW to fish ... sometimes it takes someone with a little more experience to see a subtle flaw in anothers fishing "technique" & HELP A BRO GET THAT FISH. Who knows maybe this next .zip I am making (the 8th) with the SAME .img files is the one that works ....