[CWM Touch][TWRP] Root + Recovery for Tilapia

Status
Not open for further replies.

philos64

Senior Member
May 27, 2010
3,471
3,215
113
Somewhere in Brittany
Last edited:

cmstlist

Senior Member
Jan 11, 2010
3,349
513
243
Toronto
how much time does it supposed to last the unlock? i typed fastboot oem unlock and it is waiting for device, and waiting and waiting. latest tilapia i saw is 2.3.2.1. where can i find 2.3.3.0?
Waiting for device should only take a few seconds. You need to get the correct fastboot drivers and be booted into fastboot. Use the command "fastboot devices" to verify if it can see the device.

Sent from my Galaxy Nexus using Tapatalk 2
 

faust.deaconu

Senior Member
Jun 20, 2011
359
37
28
Bucharest
faust.swissgoldglobal.com
Try with sudo.
Works on 12.10

Sent from my Nexus 7 using XDA Premium HD app
worked with sudo. but now can t make twrp permanent recovery. can t boot to recovery mode by presing volume up. i got into twrp recovery from bootloader menu but i can t "adb shell" or even "sudo adb shell". it says "insufficient permissions for device". i also tried to install cm10.1 from temporary twrp but instalation aborted.
 
Last edited:

andy034

Member
Feb 4, 2011
33
6
0
Hyderabad
How do i update my recovery?

I used a nexus 7 toolkit by Mark skippen and installed cwm 6.0.1.9. i think this is a grouper cwm as I am unable to install 4.2.2 for tilapia using this. it is giving me an assert failure. Now that my bootloader is unlocked, should i still have to follow all the steps in OP? Or can I flash any file to get a tilapia recovery?
thanks
 

mateorod

Inactive Recognized Developer
Nov 16, 2011
1,981
3,503
0
New Orleans
www.gigmasters.com
I used a nexus 7 toolkit by Mark skippen and installed cwm 6.0.1.9. i think this is a grouper cwm as I am unable to install 4.2.2 for tilapia using this. it is giving me an assert failure. Now that my bootloader is unlocked, should i still have to follow all the steps in OP? Or can I flash any file to get a tilapia recovery?
thanks
Wait...he still is installing grouper recovery? That should never have been happening in the first place. No wonder people are so down on tool kits. I hope he likes getting bug reports.

Flash recovery that is made for your device (the one is this thread will work fine.)

Edit: Did you uninstall any system apps?(Currents, Books, etc?) That will give you an assert failure even with tilapia recovery.
 
Last edited:

cmstlist

Senior Member
Jan 11, 2010
3,349
513
243
Toronto
I took a TWRP backup of my existing Nexus 7 3G (latest available official TWRP from Goo Manager on both devices) and restored it to the new one Google sent as a warranty replacement. It booted up and had all the apps, but was in a weird state where the home button didn't work and the quick settings didn't work from the upper right corner - which usually is the state that results from improperly skipping setup.

More confoundingly, all my apps were there but the app data had failed to restore properly. It remembered basics such as wi-fi settings, but all app data seemed to have been lost in translation.

Any idea why this would have happened?

I flashed both tabs to the latest CWM from ROM Manager and tried again. After hours of slow data transfer from one tab to the other, I finally restored the backup and it runs perfectly. Is there something wrong with TWRP?

I used compression and the data backup was split over 3 files due to its size.
 

sgw99

Senior Member
Oct 13, 2010
207
34
0
Greets, I am a rookie N7-3G user (yes, tilapia) and immediately flashed CM10.1 last week ;)

I flashed recovery-CWM-tilapia-regular.img at first ... but the step "mv system/recovery-from-boot.p system/recovery-from-boot.bak" did not work for me as the file system/recovery-from-boot.p does not exist (checked again right now).

CM10.1 installed, works fine, I am on the nightly from 0525 now.

But when I use the CyanogenMod-Updater it does not flash the updates correctly ... it says "untrusted Package".

"E:failed to verify whole-file signature" etc.

The recovery is "CWM-based Recovery v6.0.2.1". I retried this several times already to avoid corrupt downloads and make sure that it pulls the latest nightly. Does anyone have a hint for me? Do I miss something?

Thanks, Stefan

UPDATE: solved by flashing/using openrecovery-twrp-2.5.0.0-tilapia.img ... sorry for the noise, but maybe this posting helps someone else ;)
 
Last edited:

mateorod

Inactive Recognized Developer
Nov 16, 2011
1,981
3,503
0
New Orleans
www.gigmasters.com
Jeez, good catch. The whole reason this thread was created was because I saw the various toolkits and "indexes" (why need an index I will never know, the list of threads is enough for me) were recommending and installing grouper recovery. Since there was no CM10.1 yet, and no TWRP for 4.2 yet, I patched and built CWM and TWRP myself. I knew that anyone who installed grouped recovery would have a pretty hard time uodatingnto a proper tilapia ROM, whenever they came out.

So this was them only place to get tilapia recovery, for nearly a month in TWRPs case. But now it is everywhere, I only leave it up because you never know who might need clear root instructions.

Google "tilapia recovery", rooters of the future, and get the most recent recovery.img. Then follow the OP. I will be closing this thread shortly
 

mateorod

Inactive Recognized Developer
Nov 16, 2011
1,981
3,503
0
New Orleans
www.gigmasters.com
This was only in development because at the time it was the only working recovery for tilapia at all, and I believe it was the only TWRP for Android 4.2 anywhere, for the first month or so (until TWRP merged versions of my patches). Now Google search can get you any recovery for this device you want so thread is closed.

The only other reason to post here would be porting advice for later Android versions, which I would probably not see in time anyway.

If you need help rooting, read the OP and then if you have more problems/questions, post in Q&A. Thanks for the fish!!
 
Status
Not open for further replies.