Shinj1EVA reported that koush's web builder is now producing boo table CWM Touch images. I have built one and added it to the download page. I have not updated the regular CWM to 6.0.2.3 since there are no commits that affect how it works since I last built 6.0.2.1
12/20- All recoveries are functionally up to date as of this day.
I have seen most of the guides recommend flashing the 'grouper' recovery image. Don't do this. This is why your OTAs and update.zips are failing with 'Status 7'. Those zips have an assert check that ensures you are flashing your zips to the correct device. This is failing if you have a recovery image that was made for a different device.
Those assert checks are there for your protection and you should not get in the practice of working around them. Using grouper recovery.imgs is ill-advised and conceivably dangerous. The two devices differ in more respects than a simple assert check, including having different recovery.fstab files, which are used to make and configure recovery.
I have ported TWRP and compiled a CWM-based (Touch and non-touch) recovery image, made from CM10.1 tilapia source. You will need fastboot, at minimum, to write this recovery. To root, you will need the CWM-flashable zip of SuperSU by chainfire..
Instructions
Congratulations, you now have the proper tilapia custom recovery and can flash roms and OTAs. Anytime you get a 'status 7' from now on, you know that rom was not made for your device. CWM will have instructions that gives you the option of preserving custom recovery and maintaining root.
Downloads
Recovery (just pick one)
CWM Recovery (Touch/Non-Touch) (6.0.2.1)
TWRP 2.3.2.1
Root (Get the CWM flashable zip)
SuperSU
ClockworkMod is the work of the estimable koush and TWRP is from the good men of Team Win.
12/20- All recoveries are functionally up to date as of this day.
I have seen most of the guides recommend flashing the 'grouper' recovery image. Don't do this. This is why your OTAs and update.zips are failing with 'Status 7'. Those zips have an assert check that ensures you are flashing your zips to the correct device. This is failing if you have a recovery image that was made for a different device.
Those assert checks are there for your protection and you should not get in the practice of working around them. Using grouper recovery.imgs is ill-advised and conceivably dangerous. The two devices differ in more respects than a simple assert check, including having different recovery.fstab files, which are used to make and configure recovery.
I have ported TWRP and compiled a CWM-based (Touch and non-touch) recovery image, made from CM10.1 tilapia source. You will need fastboot, at minimum, to write this recovery. To root, you will need the CWM-flashable zip of SuperSU by chainfire..
Instructions
- Boot into the bootloader (2 choices)
- Turn the device on while pressing volume down; or
-
Code:
adb reboot bootloader
- Unlock your bootloader
- THIS WILL WIPE ALL OF YOUR DATA! No way around it...
-
Code:
fastboot oem unlock
- With your Nexus 7 3G in the bootloader and connected to your computer through the usb cable:
- replace recovery-CWM-tilapia-regular with the name of the recovery image you chose to download.
-
Code:
fastboot flash recovery recovery-CWM-tilapia-regular.img
- To make CWM your permanent recovery: (this can, despite the warnings, be undone. Do it.)
- Boot into recovery mode by pressing 'vol up' and when the menu says 'recovery mode' press the power button.
- Mount system in the 'mounts' menu
-
Code:
adb shell mv system/recovery-from-boot.p system/recovery-from-boot.bak exit
- To Root (With /system still mounted):
Code:adb push CWM-SuperSU-v0.98.zip /sdcard/
- Flash the SuperSU zip in recovery ('Install' menu with TWRP or 'choose zip from sdcard' in CWM)
- Reboot System
Congratulations, you now have the proper tilapia custom recovery and can flash roms and OTAs. Anytime you get a 'status 7' from now on, you know that rom was not made for your device. CWM will have instructions that gives you the option of preserving custom recovery and maintaining root.
- If you just want to boot into custom recovery instead of overwriting the stock or grouper recovery(playing fast and loose- keeping grouper recovery on-device for grouper roms, at least until devs add tilapia asserts to their updater-scripts), use
Code:
fastboot boot recovery recovery-CWM-tilapia-regular.img
- If you want to keep tilapia recovery but have a grouper rom you want to try, you will have to change the updater-script of that rom. It takes two seconds. Look at the third post for instructions.
Downloads
Recovery (just pick one)
CWM Recovery (Touch/Non-Touch) (6.0.2.1)
TWRP 2.3.2.1
Root (Get the CWM flashable zip)
SuperSU
ClockworkMod is the work of the estimable koush and TWRP is from the good men of Team Win.
Last edited: