[OFFICIAL][RECOVERY] Cannibal Open Touch v3.0 Alpha Builds (latest: Alpha 9)

[Sblood86]

Cannibal Open Touch 3.0 Alpha 9

Disclaimer:
While we try to test our work as much as possible, it is always a possibility that something could go wrong and screw up your phone. We are not responsible for any damage that is done to your device, either directly or indirectly, as a result of using Cannibal Open Touch or any other Project Open Cannibal projects. Any damage done to your device is your responsibility and your responsibility only. We do this for fun, and we simply like to share our work.

What is Cannibal Open Touch?
Cannibal Open Touch is a custom recovery (like ClockworkMod or TWRP), created purely out of love for the platform and the desire to contribute something cool to the community. The name embodies everything that Cannibal Open Touch is. We take what we believe are the best features of popular recoveries like TWRP and ClockworkMod and, well, cannibalize them along with rolling out our own features.

Features:

• Full Touch UI
• Complete theme support, including app for management of themes (we'll get to that in a sec)
• On-device backup and restore
• Backup and restore via ADB
• Much much more planned!

Bugs:

• During installation, the standard Android installing icon gets displayed instead of the custom dialog box.

If you find a bug, please do not report it here! Instead, report it in the GitHub repository!

Screenshots
See the Screenshots tab above. (Or click me if you're using Tapatalk!)

Nandroid has been replaced!
Nandroid is in fact gone, and has been replaced with a much more robust backup solution. Backups can now be made either with ADB (the recommended way) or via the new Backup and Restore item in the main menu. Backups made via the built-in menu can be copied to a PC and restored via ADB, and backups made via ADB can likewise be copied to your device and restored using the Backup and Restore menu.

adb backup -f mybackupfilename.ab boot system data cache

You can also restore said backup by using adb, like so:

adb restore mybackupfilename.ab

Downloads:
Cannibal Open Touch hlte builds (latest: CannibalOpenTouch-2.99.9a_hlte.img)

How to install:

1. Download the latest Alpha image
2. Copy the image to your sdcard
3. Flash the image with dd using adb shell or a terminal emulator

   dd if=/sdcard/<path to image> of=dev/block/platform/msm_sdcc.1/by-name/recovery

   (may require entering su prior to running dd depending on rom and configuration)
4. Boot into recovery mode

Alternatively, you may flash using the zip option (available at the same download location) from pre-existing recovery.

Changelog:

3.0 Alpha 9 (2.99.9)

• Real menu scrolling! (but volume keys still work)
• All backup/restore operations now verify that you want to take action
• Resized UI to be more usable on all device resolutions
• Themes can now display a battery charge indicator (depends on individual theme settings)

3.0 Alpha 8 (2.99.8)

• Not released

3.0 Alpha 7 (2.99.7)

• On-device backup and restore

3.0 Alpha 6 (2.99.6)

• Complete theme support
• Recovery settings (Theme settings and Unsigned ZIP flashing)

The preceding list is not 100% complete. See the project source code page for the full commit list.

Cannibal Open Touch themes app:
We are currently seeking Alpha testers for an app that will let users download and choose themes without rebooting to recovery mode. Currently there are 20 slots open. If you wish to join please PM me. The only requirement is you must have a Google+ account and are willing to submit proper bug reports, should any arise.

Cannibal Open Touch Themes:
You can now make your own themes for Cannibal Open Touch! See the example themes (it's pretty self-explanatory). Themes must be installed in /sdcard/cot/themes/theme_name (or /data/media/cot/themes/theme_name) in order to work. Please feel free to submit pull requests to have your custom themes added to the theme repository. They will also be packaged and made available to download via the Cannibal Themes app (mentioned above)!

Contribute to Project Open Cannibal
If you like our work and want to see more, consider a donation to the project!

Project Open Cannibal gerrit: http://review.projectopencannibal.org

Credits:
tdm, for the superb touch code (and lots more)
drewwalton19216801, for helping to spearhead the project and forward porting most of our old functions
thenameisnigel, for picking up our webhosting while Drew was gone and assisting with device ports
anyone else who has ever contributed to any Android-related project

XDA:DevDB Information
Cannibal Open Touch, Tool/Utility for the T-Mobile Samsung Galaxy Note 3

Contributors
Sblood86, drewwalton19216801, thenameisnigel, tdm, CyanogenMod, Koush and many others

Version Information
Status: Alpha

Created 2014-10-28
Last Updated 2014-10-27

 

[Sblood86]

You will notice the image and zip are marked with an a after 2.99.9, this is because I had to re-enable overlays for qualcomm devices to display a screen (they were disabled for screenshots), the version is still 2.99.9

I'm not opposed to uploading an odin package but honestly do not know how to create one (not being an odin person) if someone would like to assist with this I'm available.

Heimdall could also be used to flash the image, if someone has the exact syntax I will add this to the OP.

I understand gsm builds for the Note3 are unified so I would expect this will work on other versions but am not posting it to the others until someone can confirm this. I only have a tmo tester at this time.

 

[allenjthomsen]

Looks interesting will test later

 

[Jonnyaces187]

Did anyone test?

 

[wormy987123]

So far it made a backup on my sprint note 3 but didn't restore the data correctly. I had to reboot recovery after wiping the phone for the backup to show up

Sent from my SM-G900P using Tapatalk

 

[Sblood86]

So far it made a backup on my sprint note 3 but didn't restore the data correctly. I had to reboot recovery after wiping the phone for the backup to show up

Sent from my SM-G900P using Tapatalk

Yeah I saw Drew and Ryan were discussing this in our dev hangout earlier. Not sure if they figured anything out yet or not; will catch up here in a bit. Sorry for the delay on my part, I was sleeping.

Edit:
Just spoke with Drew, we need a backup log to troubleshoot this (for some reason I thought they got one already).
After running a backup, before rebooting you can pull the log using adb.
Connected to your computer (with working adb drivers) please run the following

adb pull /tmp/bu.log

Since the logs are stored in tmp you have to pull it before rebooting or it will get erased.

 

[wormy987123]

Ok I'll do that when I get home

Sent from my SM-G900P using Tapatalk

 

[FeralFire]

I can confirm that it works on the international version (N9005).

Didn't play around much. But it successfully flashed a couple of zips I tried.

 

[nighthawk626]

I like this a lot. Really great job you guys did

Sent from my SM-N900T using XDA Free mobile app

 

[Morningstar]

Fantastic job guys! I'm intrigued... making some quick backups now (just to be safe), then I'll be trying this out. I wish I had the dedication to make something like this, but sadly, all my projects seem to end up half-finished and forgotten lol.

Just to be sure, since it is an Alpha, this is reversible, right? No permanent changes, can always go back to another Recovery? Not that I doubt you guys or the work you've put into this, just gotta ask....

edit: "Created 2014-10-28, Last Updated 2014-10-27".....
This Recovery can time travel??? [emoji15]
Now I'm really impressed! Lol

~★astra petas★~

 

[joluke]

Just to be sure, since it is an Alpha, this is reversible, right? No permanent changes, can always go back to another Recovery?

Flash Cwm recovery via ODIN and you are good to go

 

[Morningstar]

Flash Cwm recovery via ODIN and you are good to go

Figured as much, just had to make sure. Downloading now...

~★astra petas★~

 

[Morningstar]

Well, it looks like a decent Recovery, but unfortunately I ran into a serious problem, which I'm still trying to recover from (an hour and a half in). Here's what happened....

I flashed Cannibal, no problems there, booted into it and was just kind of poking around. Then I figured I'd go ahead and do a quick backup/restore, just to see how well it worked. In hindsight, I'm almost positive there wasn't enough open space on my internal storage to back up my Data partition (which is approaching 5gb), so I'm thinking that may have been the cause of things. That's just a guess though.

Anyway, it seemed to be backing up just fine. I watched it go all the way from 0% to 100% on System, and from 0% to 18% on Data, at which point I set the phone next to me and went to work on something on my computer. Around 30 seconds later I noticed the screen flash out of the corner of my eye, so I looked at it and it was back to the main Cannibal screen, even though it should've taken 8-10 more minutes, assuming the percentage rate shown is accurate. I didn't see any sort of errors or warnings or anything, so I figured what the hell, and started to restore the backup I had just made.

System seemed to restore just fine, but as soon as it started restoring Data, the phone reboot itself back into Recovery. Trying to restore the backup again had the same results, so next I tried just booting normally. It looked like it was booting alright for a minute, my boot animation played, and the LED was doing it's thing (gotta love Shinto kernel), but that's as far as it went. It just kept replaying the boot animation, never actually booting into Android (and the LED stopped doing it's thing). Let it sit like that for 15 minutes, then gave up.

Next thing I did, was Odin'ed TWRP back on, figuring I'd just restore one of my TWRP backups (I have 2 recent ones that I've restored more than once, so I know they're good). It flashed fine, booted up into Recovery, did a factory reset, since it was now saying I had 0mb free on my internal storage, and did a restore. Things looked alright, watched my boot animation play through then on to the 'Android is updating' screen, which went through all my apps, only to flash that SystemUI force closed for a fraction of a second, then went back into my boot animation, did the updating thing again (showing 13 fewer total apps this time), rinse and repeat. As I said, I'm positive the backup is good, as I've restored from it 4 or 5 times.

So...back to Recovery (TWRP now), and everything I try to do fails; install a clean ROM, fix permissions, wipe, you name it. Finally, after dicking around with various things in TWRP, trying to restore partial backups, manually copying system files, etcetera, I was able to get a ROM to install. Now I'm just in the long, arduous process of putting the ROM I was using back, and restoring things item by item to make sure nothing else funky is going on.

I'm not new to this, by any means, so I know it wasn't due to something stupid I might have done. The only thing I can figure that might've caused it is trying to do a backup without having enough free space on my internal storage, which, ok, is kind of stupid of me, but I would've expected an error or a failure or something, rather than the almost 2 hour debacle I've now been through. lol

Anyhoo, sorry for the novel. I figure'd it would be best just to describe everything thoroughly, in the hopes that someone might read it and figure out what caused it, so others don't have to go through the same thing.

 

[pyraxiate]

Well, it looks like a decent Recovery, but unfortunately I ran into a serious problem, which I'm still trying to recover from (an hour and a half in). Here's what happened....

I flashed Cannibal, no problems there, booted into it and was just kind of poking around. Then I figured I'd go ahead and do a quick backup/restore, just to see how well it worked. In hindsight, I'm almost positive there wasn't enough open space on my internal storage to back up my Data partition (which is approaching 5gb), so I'm thinking that may have been the cause of things. That's just a guess though.

Anyway, it seemed to be backing up just fine. I watched it go all the way from 0% to 100% on System, and from 0% to 18% on Data, at which point I set the phone next to me and went to work on something on my computer. Around 30 seconds later I noticed the screen flash out of the corner of my eye, so I looked at it and it was back to the main Cannibal screen, even though it should've taken 8-10 more minutes, assuming the percentage rate shown is accurate. I didn't see any sort of errors or warnings or anything, so I figured what the hell, and started to restore the backup I had just made.

System seemed to restore just fine, but as soon as it started restoring Data, the phone reboot itself back into Recovery. Trying to restore the backup again had the same results, so next I tried just booting normally. It looked like it was booting alright for a minute, my boot animation played, and the LED was doing it's thing (gotta love Shinto kernel), but that's as far as it went. It just kept replaying the boot animation, never actually booting into Android (and the LED stopped doing it's thing). Let it sit like that for 15 minutes, then gave up.

Next thing I did, was Odin'ed TWRP back on, figuring I'd just restore one of my TWRP backups (I have 2 recent ones that I've restored more than once, so I know they're good). It flashed fine, booted up into Recovery, did a factory reset, since it was now saying I had 0mb free on my internal storage, and did a restore. Things looked alright, watched my boot animation play through then on to the 'Android is updating' screen, which went through all my apps, only to flash that SystemUI force closed for a fraction of a second, then went back into my boot animation, did the updating thing again (showing 13 fewer total apps this time), rinse and repeat. As I said, I'm positive the backup is good, as I've restored from it 4 or 5 times.

So...back to Recovery (TWRP now), and everything I try to do fails; install a clean ROM, fix permissions, wipe, you name it. Finally, after dicking around with various things in TWRP, trying to restore partial backups, manually copying system files, etcetera, I was able to get a ROM to install. Now I'm just in the long, arduous process of putting the ROM I was using back, and restoring things item by item to make sure nothing else funky is going on.

I'm not new to this, by any means, so I know it wasn't due to something stupid I might have done. The only thing I can figure that might've caused it is trying to do a backup without having enough free space on my internal storage, which, ok, is kind of stupid of me, but I would've expected an error or a failure or something, rather than the almost 2 hour debacle I've now been through. lol

Anyhoo, sorry for the novel. I figure'd it would be best just to describe everything thoroughly, in the hopes that someone might read it and figure out what caused it, so others don't have to go through the same thing.

Easiest solution is to odin back to stock then flash twrp via odin. Then restore your backup. Would have been much faster.

 

[FeralFire]

Easiest solution is to odin back to stock then flash twrp via odin. Then restore your backup. Would have been much faster.

As I have quated from his post, he did do that.

Next thing I did, was Odin'ed TWRP back on, figuring I'd just restore one of my TWRP backups (I have 2 recent ones that I've restored more than once, so I know they're good).

That was quite an interesting read, man.
Glad you got out of it.
I would personally have just got fed up and flashed a stock rom through odin.

 

[Morningstar]

As I have quated from his post, he did do that.




That was quite an interesting read, man.
Glad you got out of it.
I would personally have just got fed up and flashed a stock rom through odin.

I would've too, but didn't feel like downloading a stock ROM, and thought it would be a fairly quick fix. I've messed things up plenty of times, but I've never had anything quite like that happen.

And just to be clear, I'm not saying it was due to any problem or bug in Cannibal, nor do I want to dissuade anyone else from using it. As far as I can tell though, the only "mistake" I made was trying to do a backup to the internal storage without having enough free space, so the devs may want to take a look at things just to be sure there isn't some nasty bug lurking there. :good:

 

[wormy987123]

I would've too, but didn't feel like downloading a stock ROM, and thought it would be a fairly quick fix. I've messed things up plenty of times, but I've never had anything quite like that happen.

And just to be clear, I'm not saying it was due to any problem or bug in Cannibal, nor do I want to dissuade anyone else from using it. As far as I can tell though, the only "mistake" I made was trying to do a backup to the internal storage without having enough free space, so the devs may want to take a look at things just to be sure there isn't some nasty bug lurking there. :good:

They are aware of the bug and I believe are working with a dev up stream to fix it. I to encountered the same error

Sent from my SM-N900P using Tapatalk

 

[ElRongMcBong]

no update?

 

[ryanrazer]

It is in T-mobile forum but download link says HLTE... Can i flash this to HLTE? i mean international hlte SM-N9005?
Also, i saw it an .iso file, whereas other recoveries i flashed like cwm and philz are .zip file (like all flashable android files i've flashed till now).
Can you enlighten me, plz?

 

[wormy987123]

It is in T-mobile forum but download link says HLTE... Can i flash this to HLTE? i mean international hlte SM-N9005?
Also, i saw it an .iso file, whereas other recoveries i flashed like cwm and philz are .zip file (like all flashable android files i've flashed till now).
Can you enlighten me, plz?

The .IMG file you would use while the phone is booted up. Using an app like Flashily

Sent from my SM-G900P using Tapatalk