Root [RECOVERY] Cannibal Open Touch v2.1 (latest update: 12/1/2012)

[drewwalton1921]

Project Open Cannibal presents...
Cannibal Open Touch v2.1 for LG Optimus V​

About Cannibal Open Touch:
Cannibal Open Touch is the next generation of custom recoveries. Jam-packed with cool and useful features, it can handle just about anything you can throw at it.

Main Features:
1. Support for both Edify and Amend scripting (flash all ROMS!)
2. Theme support
3. Get out of recovery boot loops
4. Touch screen button controls!
5. Compatibility with Xionia nandroid backups (if on LG Optimus device)
6. GooManager support!
7. Internal e2fsprogs for size
8. Backported “retouch binaries” patch for ICS/JB compatibility
9. Advanced Backup
10. Delete old backups!
11. Persistent settings
12. User-defined backup locations!
13. ADB Sideload
14. Touchscreen calibration

Why the name Cannibal Open Touch?
Because we can. The name also embodies everything that Cannibal Open Touch is. It is no longer just a variant of ClockworkMod Recovery, it is it's own recovery by itself. Combining features from ClockworkMod 5, Team UtterChaos' Sony Xperia recovery, AmonRa 3.0.6, Xionia CWMA and a heaping helping of our own special enhancements it is truly revolutionary.

What to do when an error occurs:
DO NOT simply say "xxxx doesn't work" as that is highly unhelpful and will probably be ignored. Instead, post the recovery log! To grab a log when an error occurs, simply open a terminal (or command prompt if on Windows), "cd" to an easily accessible directory and execute:

adb pull /tmp/recovery.log

Paste the log as an attachment (don't paste the text inside, as it can be quite lengthy), or paste it on pastebin.com.

WARNING!
If you are upgrading from a previous version of Cannibal Open Touch you must delete the settings.ini file located in the cotrecovery folder on your sdcard!

Already have a custom recovery?
You may use our handy Universal Installer!

Flashing instructions:
1. Follow these instructions (external link) for installing flash_image if you haven't already done so.
2. Make sure USB Debugging is ON and that you have ADB access
3. Download the Cannibal Open Touch image from the download link below.
4. Place the recovery image on your SD Card.
5. Fire up an ADB shell
6. Make sure you are in a root shell. If you are not, execute the "su" command now.
7. Execute "flash_image recovery /path/to/recovery.img" (replace /path/to/recovery.img with the ACTUAL path to the recovery image)
8. Reboot to recovery mode
9. PROFIT!

Main Recovery Screenshots
Main Gallery (external link)

Available Themes:
Themes Gallery (external link)

Download Cannibal Open Touch v2.1:
Note: The below link is an external link to the Project Open Cannibal forums. We do not require registration to download any public release, but we'd sure appreciate it if you stopped by to say hello

Cannibal Open Touch Download

 

[AndyOpie150]

The hardest thing for most will be having to change all there backups from Clockwork Mod recovery's which are so prevalent for the phone. It's kind of a pain, but is doable.
The last time I tried Cannibal I had to flash my backup using a ClockworkMod recovery first, then back that up with the Cannibal. Had to do that for every backup so I would be able to restore whatever ROM I felt like using that month with the Cannibal.

 

[drewwalton1921]

The hardest thing for most will be having to change all there backups from Clockwork Mod recovery's which are so prevalent for the phone. It's kind of a pain, but is doable.
The last time I tried Cannibal I had to flash my backup using a ClockworkMod recovery first, then back that up with the Cannibal. Had to do that for every backup so I would be able to restore whatever ROM I felt like using that month with the Cannibal.

ClockworkMod backups are 100% compatible. Just move them into /sdcard/cotrecovery/backup/<backup name>

It's the same folder structure, just replace /sdcard/clockworkmod with /sdcard/cotrecovery.

The reverse is also true, any backup made with Cannibal Open Touch is compatible with ClockworkMod 5.

Edit: This actually gave me an idea for a new feature to implement in the next version of Cannibal Open Touch that will make it stupid easy to import ClockworkMod backups. Congrats, you just unintentionally contributed to Cannibal Open Touch development

 

[AndyOpie150]

Great info: Hopefully those interested in trying it out will see this post.

Question: Does this new version not backup at every flashing of a zip (but instead make it an option), or is like the older versions that backed up by default?

Has it been tested on different zips, ie: ROM's, kernels, themes, patches (had a problem with the older version not being able to flash a MiRaGe and a BobZohme kernel, same kernels flashed no problem with the Touchscreen recovery).

Did you put the update from sd card option back into it (The ZV9 update is a great way to return to bone stock with stock recovery when needed)?

I'm starting to get re-interested in it. It had a lot of great options rolled into one recovery.

 

[drewwalton1921]

Great info: Hopefully those interested in trying it out will see this post.

Question: Does this new version not backup at every flashing of a zip (but instead make it an option), or is like the older versions that backed up by default?

Has it been tested on different zips, ie: ROM's, kernels, themes, patches (had a problem with the older version not being able to flash a MiRaGe and a BobZohme kernel, same kernels flashed no problem with the Touchscreen recovery).

Did you put the update from sd card option back into it (The ZV9 update is a great way to return to bone stock with stock recovery when needed)?

I'm starting to get re-interested in it. It had a lot of great options rolled into one recovery.

Sorry, I don't remember a single version that backed up on every flashing of a zip. It has always prompted, at which point you can elect to skip the backup (hint: you can also disable the prompt entirely in COT Settings).

As far as it being tested on different ZIPs, it has. I haven't had a single one not flash (except for improper ZIPs, but that's another story). Obviously I do not own an Optimus V so I don't know exactly what ZIPs have had issues in the past, likely they were due to us using an outdated CM7 repo that screwed with the device name.

The "update from sdcard" you're mentioning has never once been removed, just put in a ZIP Flashing menu (figured it made sense there, you know with it being a ZIP flashing tool and all).

 

[drew_t]

Question about doing a nandroid restore with COT: are any preliminary steps required (wiping, formatting, whatever), or can you just reboot into COT, use the menu to pick the backup you want to restore, and let it do its thing?

 

[AndyOpie150]

You have to wipe everything necessary for a new ROM install.

 

[unknownsoldi]

I thought restoring a nandroid was like restoring a HDD image on a computer, in that it overwrites everything on the partitions. This isn't so?

 

[AndyOpie150]

Yes and No. It doesn't do a good enough job and the problem is the residual data that's left in the partitions will corrupt the new data.
This is why you have to wipe, very thoroughly.

 

[unknownsoldi]

So it's recommended to wipe everything (cache, dalvik, data, system, boot)? Should wipes still be done three times?

Man, I wish recoveries would include more options to wipe all that stuff in one click. Some are close, but I haven't found one yet the does a one-click wipe of all the partitions.

Also, on a similar note, why isn't there a problem flashing recoveries if the recovery partition is never wiped?

 

[drewwalton1921]

Server issues have been resolved and data has been restored, read the latest post on our Google+ page for the juicy details.

 

[AndyOpie150]

Don't have an answer other than that end just seems to work as it's supposed to, and the rest.....doesn't.

 

[Thewraith420]

I normally wipe all out of habit from flashing zips but I know I've restored backups without wiping before you could always try... You have a backup.... lol

 

[sammyz]

So it's recommended to wipe everything (cache, dalvik, data, system, boot)? Should wipes still be done three times?

Man, I wish recoveries would include more options to wipe all that stuff in one click. Some are close, but I haven't found one yet the does a one-click wipe of all the partitions.

Also, on a similar note, why isn't there a problem flashing recoveries if the recovery partition is never wiped?

Because if you wipe recovery and forget to flash a new one, you'll be in fastboot....and that's a problem if you don't have a PC nearby.

 

[unknownsoldi]

Because if you wipe recovery and forget to flash a new one, you'll be in fastboot....and that's a problem if you don't have a PC nearby.

That's true, but I wasn't asking why it isn't wiped. Question is, if not wiping before restoring a nandroid can cause problems, wouldn't not wiping before flashing a recovery cause similar problems with the recovery partition? Couldn't residual data from an old recovery cause problems with the new recovery?

 

[sammyz]

That's true, but I wasn't asking why it isn't wiped. Question is, if not wiping before restoring a nandroid can cause problems, wouldn't not wiping before flashing a recovery cause similar problems with the recovery partition? Couldn't residual data from an old recovery cause problems with the new recovery?

Nah, recovery takes up very little space on the phone's partition. And it's just one file...it's not like multiple files the way a rom is....

 

[drewwalton1921]

Nah, recovery takes up very little space on the phone's partition. And it's just one file...it's not like multiple files the way a rom is....

You ever peeked inside a recovery image? It's actually multiple files

Also, there is no need to wipe partitions before restoring a Nandroid backup. That's only applicable when installing ROMs.

 

[sammyz]

You ever peeked inside a recovery image? It's actually multiple files

Also, there is no need to wipe partitions before restoring a Nandroid backup. That's only applicable when installing ROMs.

Yeah, but there something about .img files that's different than a rom...

 

[drewwalton1921]

Yeah, but there something about .img files that's different than a rom...

No, not really. I can make .img images out of any filesystem/partition on the device. The boot and recovery images are just compressed filesystems. They still have files, directories and permissions just like about every other filesystem in the world.

 

[sammyz]

No, not really. I can make .img images out of any filesystem/partition on the device. The boot and recovery images are just compressed filesystems. They still have files, directories and permissions just like about every other filesystem in the world.

Ik

 

[AndyOpie150]

Also, there is no need to wipe partitions before restoring a Nandroid backup. That's only applicable when installing ROMs.

Hmmm! Interesting. That's the first time I've seen that. I've never installed a backup without wiping everything necessary for a ROM install. I might wait on doing it that way until other members have verified that it doesn't corrupt the restored ROM.
It would speed up the proccess, but think I'll wait on the final verdict (other members who have done it in that manner with no ill effect or corruption) before I go about doing it the way you suggest.

 

[drewwalton1921]

Update:
We're back up. DDoS attack has been mitigated and no data has been lost. We will be migrating to a REAL webhost later this evening (one of us actually personally KNOWS the owner this time).

We're down. Again. Official word is that our webhost is currently under a DDoS attack. We're currently running a fundraising campaign to raise funds in order to purchase some real webhosting and keep Project Open Cannibal online. If you'd like to join the cause, the WePay page is here: https://www.wepay.com/donations/project-open-cannibal-hosting

 

[drewwalton1921]

Update on the situation:
Our host (and the datacenter they reside in) has informed us that we have been the target of a massive DDoS attack that has been going on for two days. Our account has been suspended due to the attack bringing down their entire server. We will be offline for a small bit while we deal with the attack and get everything back online. No data has been lost.

 

[Thewraith420]

Man... Just can't win

 

[drewwalton1921]

Man... Just can't win

Yes we can!

Thanks to our friends at bestlittlehosthouse.com we are now back online and running faster than ever!