Guest PaulOBrien Posted July 13, 2012 Report Share Posted July 13, 2012 Hey folks! I've created a working ClockworkMod recovery for Nexus 7 for use until such time as Koush releases his. This is basically the Galaxy Nexus recovery fixed up for the Nexus 7. Needs must and all that. :) The r2 version is based on 5.8.0.2 (in case you don't like the new features in the 6 series) The r3 version is based on ClockworkMod Touch 6.0.0.4. Note: An official series 6 ClockworkMod recovery is now available from Koush / ROM Manager! The recommended install method is 'adb reboot bootloader && fastboot flash recovery r3-recovery-clockwork-touch-6.0.0.4-nexus7-modaco.img && fastboot boot r3-recovery-clockwork-touch-6.0.0.4-nexus7-modaco.img'. r2 - DOWNLOAD (ROMraid) - MD5: 42ebef60c54ca4709e7fafb80933a80dr3 - DOWNLOAD (ROMraid) - MD5: a3e2326843a18447bd03b73318bee5c0 Enjoy! P Link to comment Share on other sites More sharing options...
Guest Jele09 Posted July 13, 2012 Report Share Posted July 13, 2012 HI Paul, thanks for all the awesome work :) Appologies for the newbie question, how to apply the new CWM recovery on my N7? Cheers. Link to comment Share on other sites More sharing options...
Guest PaulOBrien Posted July 13, 2012 Report Share Posted July 13, 2012 'fastboot flash recovery filename.img' after doing 'fastboot oem unlock'. :) P Link to comment Share on other sites More sharing options...
Guest Jele09 Posted July 13, 2012 Report Share Posted July 13, 2012 'fastboot flash recovery filename.img' after doing 'fastboot oem unlock'. :) P Paul, Thank you so much, you are truely a legend among men! Worked perfectly and now have a MCR N7 :) Link to comment Share on other sites More sharing options...
Guest PaulOBrien Posted July 13, 2012 Report Share Posted July 13, 2012 Hurrah! :) P Link to comment Share on other sites More sharing options...
Guest munkimatt Posted July 13, 2012 Report Share Posted July 13, 2012 (edited) Hi Paul I'm having problems with this recovery image and, to be honest, all others I've tried. It seems I can boot in once but then any subsequent boots are met with a black screen, the Google logo and the open padlock symbol. I've tried a command I've seen on two other sites, adb shell > mount system > mv recovery-from-boot.p recovery-from-boot.bak but this fires back an error ofmv: can't rename 'recovery-from-boot.p' : No such file or directory. Any ideas? Edited July 13, 2012 by munkimatt Link to comment Share on other sites More sharing options...
Guest PaulOBrien Posted July 13, 2012 Report Share Posted July 13, 2012 Ah, boot into recovery and then do 'adb shell mount /system && adb shell rm /system/recovery*' and you'll be set from then on. P Link to comment Share on other sites More sharing options...
Guest Mtman1 Posted July 14, 2012 Report Share Posted July 14, 2012 Sorry for annoying you, but how do you access cwm with the button combo? It varys from each dev+cwm build.... Link to comment Share on other sites More sharing options...
Guest sabesh Posted July 14, 2012 Report Share Posted July 14, 2012 (edited) what are the button combos to boot into recovery? Thanks. EDIT: Nevermind. I figured it out. Edited July 14, 2012 by sabesh Link to comment Share on other sites More sharing options...
Guest cjb110 Posted July 16, 2012 Report Share Posted July 16, 2012 Sorry for annoying you, but how do you access cwm with the button combo? It varys from each dev+cwm build.... what are the button combos to boot into recovery? Thanks. EDIT: Nevermind. I figured it out. And it is??? Link to comment Share on other sites More sharing options...
Guest tehSmoogs Posted July 16, 2012 Report Share Posted July 16, 2012 Hola ppls, I'm unable to delete any of the backups I've taken with this, from within rom manager and file explorers and adb shell. Getting "operation not permitted" from adb shell, and that's after a "su". What have I screwed up? Any ideas? Link to comment Share on other sites More sharing options...
Guest tehSmoogs Posted July 16, 2012 Report Share Posted July 16, 2012 adb info regarding my delete issues:- shell@android:/sdcard/clockworkmod/backup # ls -la drwsrwsr-t root sdcard_rw 2012-07-13 14:12 2012-07-13.13.07.25 drwsrwsr-t root sdcard_rw 2012-07-13 19:00 2012-07-13.17.53.08 drwsrwsr-t root sdcard_rw 2012-07-14 20:06 2012-07-14-19.55.19 drwsrwsr-t root sdcard_rw 2012-07-16 08:50 2012-07-16.07.38.28 shell@android:/sdcard/clockworkmod/backup # ls -la 2012-07-13.13.07.25/ -rw-rw-r-- root sdcard_rw 8388608 2012-07-13 14:07 boot.img -rw-rw-r-- root sdcard_rw 15360 2012-07-13 14:12 cache.ext4.tar -rw-rw-r-- root sdcard_rw 128481280 2012-07-13 14:10 data.ext4.tar -rw-rw-r-- root sdcard_rw 237 2012-07-13 14:12 nandroid.md5 -rw-rw-r-- root sdcard_rw 12582912 2012-07-13 14:07 recovery.img -rw-rw-r-- root sdcard_rw 435058176 2012-07-13 14:07 system.ext4.tar shell@android:/sdcard/clockworkmod/backup # id uid=0(root) gid=0(root) 255|shell@android:/sdcard/clockworkmod/backup # rm 2012-07-13.13.07.25/boot.img rm failed for 2012-07-13.13.07.25/boot.img, Operation not permitted 255|shell@android:/sdcard/clockworkmod/backup # touch temp shell@android:/sdcard/clockworkmod/backup # ls -la drwsrwsr-t root sdcard_rw 2012-07-13 14:12 2012-07-13.13.07.25 drwsrwsr-t root sdcard_rw 2012-07-13 19:00 2012-07-13.17.53.08 drwsrwsr-t root sdcard_rw 2012-07-14 20:06 2012-07-14-19.55.19 drwsrwsr-t root sdcard_rw 2012-07-16 08:50 2012-07-16.07.38.28 -rw-rw-r-- root sdcard_rw 0 2012-07-16 11:12 temp shell@android:/sdcard/clockworkmod/backup # rm temp shell@android:/sdcard/clockworkmod/backup # cd 2012-07-14-19.55.19 shell@android:/sdcard/clockworkmod/backup/2012-07-14-19.55.19 # ls -la -rw-rw-r-- root sdcard_rw 8388608 2012-07-14 19:55 boot.img -rw-rw-r-- root sdcard_rw 8192 2012-07-14 20:05 cache.ext4.tar -rw-rw-r-- root sdcard_rw 753596416 2012-07-14 20:03 data.ext4.tar -rw-rw-r-- root sdcard_rw 237 2012-07-14 20:06 nandroid.md5 -rw-rw-r-- root sdcard_rw 12582912 2012-07-14 19:55 recovery.img -rw-rw-r-- root sdcard_rw 435725824 2012-07-14 19:56 system.ext4.tar shell@android:/sdcard/clockworkmod/backup/2012-07-14-19.55.19 # touch temp shell@android:/sdcard/clockworkmod/backup/2012-07-14-19.55.19 # ls -la -rw-rw-r-- root sdcard_rw 8388608 2012-07-14 19:55 boot.img -rw-rw-r-- root sdcard_rw 8192 2012-07-14 20:05 cache.ext4.tar -rw-rw-r-- root sdcard_rw 753596416 2012-07-14 20:03 data.ext4.tar -rw-rw-r-- root sdcard_rw 237 2012-07-14 20:06 nandroid.md5 -rw-rw-r-- root sdcard_rw 12582912 2012-07-14 19:55 recovery.img -rw-rw-r-- root sdcard_rw 435725824 2012-07-14 19:56 system.ext4.tar -rw-rw-r-- root sdcard_rw 0 2012-07-16 11:14 temp shell@android:/sdcard/clockworkmod/backup/2012-07-14-19.55.19 # rm temp shell@android:/sdcard/clockworkmod/backup/2012-07-14-19.55.19 # rm boot.img rm failed for boot.img, Operation not permitted 255|shell@android:/sdcard/clockworkmod/backup/2012-07-14-19.55.19 # huh? same perms & ownership as the temp file i created but I can't delete anything created by cwmr Help!! Link to comment Share on other sites More sharing options...
Guest PaulOBrien Posted July 16, 2012 Report Share Posted July 16, 2012 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 Link to comment Share on other sites More sharing options...
Guest tehSmoogs Posted July 16, 2012 Report Share Posted July 16, 2012 reproduced the "can't delete backup files" issue after downloading/flashing stock and rooting. used the r2 revision And I see theres another user with the same problem on xda http://forum.xda-developers.com/showpost.php?p=28861176&postcount=53. Link to comment Share on other sites More sharing options...
Guest PaulOBrien Posted July 17, 2012 Report Share Posted July 17, 2012 Updated to r3, which is based on the latest 6.0.0.4 Galaxy Nexus release. This also resolves the 'undeletable folders' issue. P Link to comment Share on other sites More sharing options...
Guest Custnam Posted July 19, 2012 Report Share Posted July 19, 2012 After failed restores with the new TWRP, and not liking the new incremental backups of the new CWM Ive decided to use this as my main recovery. Link to comment Share on other sites More sharing options...
Guest PaulOBrien Posted July 19, 2012 Report Share Posted July 19, 2012 This is based on the new recovery too (or at least r3 is!) With that in mind, I put the link to r2 (series 5 based) back in the first post... P Link to comment Share on other sites More sharing options...
Guest Custnam Posted July 19, 2012 Report Share Posted July 19, 2012 This is based on the new recovery too (or at least r3 is!) With that in mind, I put the link to r2 (series 5 based) back in the first post... P Yea, I didnt realize that your R3 was the same format until I saw the blob folder. Ill gladly use r2 as long as file deletion works? Link to comment Share on other sites More sharing options...
Guest PaulOBrien Posted July 19, 2012 Report Share Posted July 19, 2012 Yea, I didnt realize that your R3 was the same format until I saw the blob folder. Ill gladly use r2 as long as file deletion works? I need to fix that then. :) P Link to comment Share on other sites More sharing options...
Guest Custnam Posted July 20, 2012 Report Share Posted July 20, 2012 I need to fix that then. :) P Any luck on figuring out file deletion for R2? Link to comment Share on other sites More sharing options...
Guest PaulOBrien Posted July 20, 2012 Report Share Posted July 20, 2012 Not had a chance to look yet. P Link to comment Share on other sites More sharing options...
Guest Zeus1022 Posted July 20, 2012 Report Share Posted July 20, 2012 Can we not log into recovery mode from the bootloader screen??? switching to recovery mode and clicking the power button, makes it hang on Google screen. Using volume up+down and power Any ideas? Link to comment Share on other sites More sharing options...
Guest PaulOBrien Posted July 20, 2012 Report Share Posted July 20, 2012 Bootloader bug, it requires a USB connection. P Link to comment Share on other sites More sharing options...
Guest Zeus1022 Posted July 20, 2012 Report Share Posted July 20, 2012 Bootloader bug, it requires a USB connection. P Thanks :) I thought i was going nuts :) Link to comment Share on other sites More sharing options...
Guest Highland3r Posted July 21, 2012 Report Share Posted July 21, 2012 Anyone able to confirm their backup sizes please? They seem tiny compared to older versions of CWM (i.e previous backups would be >1gb) and now, after 3 or 4 backups (so a number of blobs etc) the total CWM folder size is only just over 1gb. (System/Data files are <1mb each etc) Just a little worried I've missed something and these backups are actually trash! Cheers Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now