installed last night, works great..frankly i prefer the non-touch, dunnow why but its much better...i tried to rename the files, but there werent any files in the /system , flashed the CWM package, took a nandroid..all works great

Somehow this still does not seem to work for me:
After I reflashed the tilapia recovery (CWM 6.0.1.9), I executed the nakasig file and get:

Finding update package...
Opening update package...
Installing update...
Verifying current system...assert failed: apply_patch_check("/system/framework/framework-res.apk". "212e537985a59a7d40ff8b450a3de597ade4251c". "521503fb2a63dc6d80c4a1ecf72770c3745c4178")
E:Error in /sdcard/0/65880f45b1c0.signed-nakasig-JOP40D-from-JOP40C.65880f56.zip
(Status 7)
Installation aborted.

Originally Posted by gwisch

Somehow this still does not seem to work for me:
After I reflashed the tilapia recovery (CWM 6.0.1.9), I executed the nakasig file and get:

Finding update package...
Opening update package...
Installing update...
Verifying current system...assert failed: apply_patch_check("/system/framework/framework-res.apk". "212e537985a59a7d40ff8b450a3de597ade4251c". "521503fb2a63dc6d80c4a1ecf72770c3745c4178")
E:Error in /sdcard/0/65880f45b1c0.signed-nakasig-JOP40D-from-JOP40C.65880f56.zip
(Status 7)
Installation aborted.

That error message has absolutely nothing to do with the recovery image.

This special talapia version of CWM isn't some magic pill that will make every other problem go away. It's simply designed to accurately reflect the hardware for the tablet you own (talapia vs grouper) so you don't run into as many problems down the road installing OTA updates and custom ROMs that check.

However, you still need to meet ALL the other requirements of the updates. So if you made changes to your /system files, kernel (not in this case, but in general), build.prop, etc., the OTA update will still abort and explain why.

Did you even read the error message?
Verifying current system...assert failed: apply_patch_check("/system/framework/framework-res.apk".
It's pretty clear that you modified the framework file. You will need to revert that back to stock and flash the OTA again afterwards. Any other tweaks/modifications/freezes/removals/etc. of system apps will most likely result in the same thing.

TWRP is up...

---

I compiled a TWRP image for tilapia as well.

This actually took a little doing...my intention here was to simply compile some images, but since tilapia is only Android 4.2, and we don't have CM10.1 (officially), I actually endied up having to port TWRP whole cloth. This is compiled from TWRP source code, with a few tweaks.

There are a couple things about the port I would like to eventually tweak, I had to copy the sbin folder over by hand, and due to the intertwined nature of grouper/tilapia, settings derived from common files in the source code are named grouper still, (i.e. ueventd.grouper.rc instead of ueventd.tilapia.rc) but that is quibble stuff and may end up staying that way regardless, since many of the tilapia make files are merely pointers to the grouper files. It certainly doesn't hurt anything.

The TWRP image has been confirmed working with the OTAs.

I thought long and hard about possibly modifying these recovery images to allow users to flash grouper roms as well. I know it is unlikely that everything will be made available in two versions, even though it should be.

Any thoughts on this? It is a demonstrably better idea than having people use the grouper images, but I still think the developers/modders should be the ones handling this problem. People are going to NEED this recovery image once the nightlies of AOKP/CM10.1 and whatever start coming down, but I know that grouper zips will still be tempting to many.

Under the instructions in the first post, it says:

OR: 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

fastboot boot recovery recovery-CWM-tilapia-regular.img

So without flashing anything, I should be able to just point fastboot towards the clockworkmod file on my computer and it should reboot into clockworkmod right?

When I try to do this, it doesn't work, and I just get this:

C:\Program Files\Droid Explorer\SDK\tools>fastboot boot recovery D:\Downloads\recovery-CWM-tilapia-regular.img
cannot load 'recovery'

I also tried to follow the main instructions and it fails on step 2 with:

C:\Program Files\Droid Explorer\SDK\tools>fastboot flash recovery D:\Downloads\recovery-CWM-tilapia-regular.img
sending 'recovery' (6568 KB)... FAILED (remote: Bootloader is locked.) finished. total time: 0.021s

I looked at other threads and found out that normally flashing a custom recovery requires issuing a fastboot oem unlock command that wipes all data. Am I missing anything or is this actually required before either of these?

Originally Posted by manekineko

Under the instructions in the first post, it says:



So without flashing anything, I should be able to just point fastboot towards the clockworkmod file on my computer and it should reboot into clockworkmod right?

When I try to do this, it doesn't work, and I just get this:

C:\Program Files\Droid Explorer\SDK\tools>fastboot boot recovery D:\Downloads\recovery-CWM-tilapia-regular.img
cannot load 'recovery'

I also tried to follow the main instructions and it fails on step 2 with:

C:\Program Files\Droid Explorer\SDK\tools>fastboot flash recovery D:\Downloads\recovery-CWM-tilapia-regular.img
sending 'recovery' (6568 KB)... FAILED (remote: Bootloader is locked.) finished. total time: 0.021s

I looked at other threads and found out that normally flashing a custom recovery requires issuing a fastboot oem unlock command that wipes all data. Am I missing anything or is this actually required before either of these?

Yep. My bad.

I originally just posted the images as an alternative to the recoveries for the regular Nexus 7 (non-3g) images people were using. I later realized that some new people would come by so I threw rooting instructions as well. I didn't go back far enough, sorry. I will fix it now.

What you need to do is easy though, just like you mentioned you need to unlock your bootloader. So once you boot into the bootloader,

fastboot oem unlock

This will wipe all of your data, and there is no way around this, sorry. It is a security measure of some sort. There will be a screen where you acknowledge this and then the bootloader will unlock. You can then follow the rest of the instructions. Sorry for the confusion.

Update: Fixed and streamlined OP. Glad you got me to do this, I think it is better now.

In the rooting instructions, this line wasn't working for me, as /sdcard/ was for some reason a directory containing 3 folders (0, odb, legacy), where 0 had the normal contents of /sdcard/:

adb push CWM-SuperSU-v0.98.zip /sdcard/

Instead, I had to do:

adb push CWM-SuperSU-v0.98.zip /sdcard/0/

After that change, I was able to flash the zip and root successfully.

Hi OP,

I followed your instructions and managed to root my nexus 7 3G running stock Android 4.2.1. Thanks.
However there are some extra "incidents" which is not captured in your instructions and somehow it happen on my side, so I just detailed down what happen in case it can be of help to others:

Below is the full OP's original instruction and some extra "incidents" during rooting

Instructions

1. Boot into the bootloader (2 choices)

• Turn the device on while pressing volume down; or

• Code:

adb reboot bootloader

2. Unlock your bootloader

• THIS WILL WIPE ALL OF YOUR DATA! No way around it...

• Code:

fastboot oem unlock

My Nexus rebooted after this step and all the ADB drivers on my Windows 7 pc is gone. With my Nexus 7 still connected and booted up, when I do "adb device", I cannot see my device. I open the Device Manager and notice that the "ADB Composite Interface" driver is gone!
I got to re-install all my drivers for my Nexus 7 manually. I downloaded WugFresh Toolkit and follow the first step to re-install all the drivers. (I just wana try manual rooting, that's why I didn't use WugFresh Toolkit)
After making sure my device can be listed after "adb device", I proceed to

2a. Reboot into bootloader

adb reboot bootloader

3. 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

4. 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

5. To Root (With /system still mounted):
There is no error when pushing the zip file to /sdcard/ but the file just didn't appear. The windows command prompt also indicate that the push was successful. I notice that the my /sdcard/ directory is softlink to /data/media/, so I push to /data/media/ instead and it works! The zip file now appear in /sdcard/. I am not sure why is this so.

• Code:

adb push CWM-SuperSU-v0.98.zip /data/media/

• Flash the SuperSU zip in recovery ('Install' menu with TWRP or 'choose zip from sdcard' in CWM)

Reboot System

5a. CWM will give a warning message stating overwriting of flash recovery. I cannot recall what is that exact message. But you will be presented with a llist of options with one "Yes" and all "No". I choose "Yes" to retain CWM as my recovery.

COLOR="Red"]My Nexus rebooted after this step and all the ADB drivers on my Windows 7 pc is gone. With my Nexus 7 still connected and booted up, when I do "adb device", I cannot see my device. I open the Device Manager and notice that the "ADB Composite Interface" driver is gone!
I got to re-install all my drivers for my Nexus 7 manually. I downloaded WugFresh Toolkit and follow the first step to re-install all the drivers. (I just wana try manual rooting, that's why I didn't use WugFresh Toolkit)
After making sure my device can be listed after "adb device", I proceed to

I can't speak as to how Windows works exactly, but I can tell you that fastboot code does nothing to the 'host' PC. Not saying it didn't happen, but it wasn't fast boot.

[COLOR="Red"]There is no error when pushing the zip file to /sdcard/ but the file just didn't appear. The windows command prompt also indicate that the push was successful. I notice that the my /sdcard/ directory is softlink to /data/media/, so I push to /data/media/ instead and it works! The zip file now appear in /sdcard/. I am not sure why is this so.

The person above you reported that they had to push to /sdcard/0. I checked my original instructions and they work for me. I haven't decided what to put yet. They have been playing around with the standard nomenclature for emulated storage, but I have yet to see anything that explains the varied experiences. I haven't looked yet really, either

5a. CWM will give a warning message stating overwriting of flash recovery. I cannot recall what is that exact message. But you will be presented with a llist of options with one "Yes" and all "No". I choose "Yes" to retain CWM as my recovery.

I originally told people to follow the CWM directions on having permanent recovery. But some user experience taught me that some people are going to skip this step due to confusion over the warnings. So I decided to put in the manual method.

Thanks for your feedback.

I originally told people to follow the CWM directions on having permanent recovery. But some user experience taught me that some people are going to skip this step due to confusion over the warnings. So I decided to put in the manual method.

Hi,
In fact I am also confused about the warning. Not sure does choosing "Yes" means retain CWM or not. So I just choose "Yes" and saw that CWM is still the recovery after reboot.

So do you mean after this step:

adb shell
mv system/recovery-from-boot.p system/recovery-from-boot.bak
exit

It does not matter whether I choose "Yes" or "No" in the final phase, and I will still have CWM as my recovery?