yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy Note II] bsweetness:
Then why post another thread here instead of asking in that one (or in the other thread about blocking mode just a few threads down)? :)

It's working for me and for others. What problem are you having with it?

Edit: While the shortcut allows you to open up the settings for Blocking Mode, it's actual functionality is definitely hit or miss, with far more misses than hits. Perhaps that's the issue you're having.
[Android Apps and Games] lokiy2:
Let me introduce to you my friend Toppler Frog.

A little frog jumps over tussocks that disappear.

Help her to get a coveted coin collecting bonuses and avoiding enemies.

For the frog's movement tap on the tussock where you want to go.

To get to the next level need to get to the coin.

Toppler frog cries without coins

Little frog needs your help.

his home:

https://play.google.com/store/apps/details?id=draziw.karavan.perestroika

Screenshots:

If you have any suggestions, feel free to post them! We will certainly take your opinion into account.
[Samsung Galaxy 5 I5500] Deleted member 4372376:
Hi ICS 4.0.5 is installed, everything is working. The sd card fat32 filesystem can not see! What could be the problem? THX
[Samsung Galaxy 5 I5500] XdaNoob98:
Where did u get 4.0.5? And could u please tell us more about the problem?:D
[Samsung Galaxy 5 I5500] brewy:
What size is your SD? And you need int2ext script to use partition for internal memory if your SD is 4gb or below you need just a primary fat partition anything above is fat32 hope this helps
[Nexus 7 Q&A, Help & Troubleshooting] msr4:
Err. So I'm toying around with my Nexus 7, and when I took off the back cover, I noticed something. There's actually four buttons on the board, and its right below the volume down button. Why is it there? The back cover only has three accessible buttons. Pressing it doesn't seem to do anything, either.

EDIT: Pic if you're curious:
[Nexus 7 Q&A, Help & Troubleshooting] veeman:
I'm guessing it was supposed to be a camera button for a rear camera but they ditched the rear camera idea.

Sent from my Nexus 7
[Nexus 7 Q&A, Help & Troubleshooting] player911:
+1
[Nexus 7 Q&A, Help & Troubleshooting] Tyyr:
I took a look at the ifixit tear down and you can see them in there. It looks like the buttons aren't individual buttons but part of a larger assembly. More than likely they either got a deal on using that and just had functions for three of them, or its a standardized part. Do any ASUS tablets have four buttons in a close grouping like that?
[Galaxy S I9000 Q&A, Help & Troubleshooting] matthias1203:
Is there any mod to got stock 'glass lockscreen' on ics or jb rom. ?
[Kindle Fire Android Development] Sblood86:
Project Open Cannibal presents...

Cannibal Open Touch v2.1 for Amazon Kindle Fire (first generation)​

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.

Warning: Does NOT currently support KitKit

Main Features:

1. Theme support

2. Touch screen button controls!

3. GooManager support!

4. Advanced Backup

5. Delete old backups!

6. Persistent settings

7. User-defined backup locations!

8. ADB Sideload

9. Touchscreen calibration

10. Backported “retouch binaries” patch for ICS/JB compatibility

11. Backported extfs tools for better ICS/JB management

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!

Flashing instructions:

Flashing instructions can be found at the download link below.

Main Recovery Screenshots:

Main Gallery (external link) (Nexus 7 screen shots; will update soon)

Available Themes:

Themes Gallery (external link) (Again, Nexus 7 images shown here)

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 (external link)

For those of you who are either uncomfortable or incapable of using fastboot for some reason webdroidmt has done an updated Smirkit 2.1 for y'all, please see the original Smirkit release page for usage instructions.

XDA:DevDB Information

Cannibal Open Touch v2.1, a Tool/Utility for the Amazon Kindle Fire

Contributors

Sblood86, drewwalton19216801, thenameisnigel

Version Information

Status: Stable

Current Stable Version: 2.1

Stable Release Date: 2012-12-01

Created 2013-09-04

Last Updated 2013-11-28
[Kindle Fire Android Development] webdroidmt:
Good to see you posting COTR here! Thanks.

Mike T
[Kindle Fire Android Development] webdroidmt:
Just made a nandroid & it seemed faster than 2.02, maybe placebo. :laugh: Didn't flash any roms , as I don't have anything new to flash...yet! I like the overall simplicity and the functions in plain language terms.

Couple of questions, where can I read up on how to install a theme? Is that something that the COTR android app does or will do? Also, as stated in the OP, I deleted my current .ini file but can I still restore older COTR nandroids, say from 2.02 with this version? I'm figuring yes but want to be sure.

Thanks again for an alternative to TWRP. Btw, when the skull logo first came up, I thought I got a virus or something. LOL Looks cool.

Mike T
[Kindle Fire Android Development] Sblood86:
I can't imagine what would effect speed but cool

Previous backups should work just fine yes as for themes we don't have a lot yet but there is an outline for creating them on both github and the POC forums. The apps capabilities are limited to Drew's java capabilities as I find java to be; well, it's unsavory, we'll leave it at that ;)

To that end I'm not sure but maybe.

Love it! :D
[Kindle Fire Android Development] Thepooch:
Thank you Sblood86 this is a great Christmas gift awesome work:). Updated index.
[Kindle Fire Android Development] Ixthusdan:
I assume this replaces twrp. Would I install this along side twrp? Will firefirefire offer a choice of recovery?
[Kindle Fire Android Development] webdroidmt:
Sblood, is there a way in settings to change the time? Thanks.

Mike T
[Kindle Fire Android Development] Sblood86:
Not at this time (no pun intended); requires an offset which varies a bit by location so it's a bit of a hack. Haven't done it yet but we may add a function for it in the future.
[Kindle Fire Android Development] webdroidmt:
Thanks for your reply, obviously it would be nice for proper timestamping of the nandroids, as now it reads 5 hours ahead for me.. But even without that, I've previously been enjoying using COTR and this new version with themes gives me a little something extra to play with. :D

Started messing around with the themes I d/l from the git, took the devildroid one and substituted the devildroid background out with the droid jellybean machine that's been floating around the web. Simple but looks pretty nice, I like green :laugh: and gives me a better idea how to work with the themes going forward. Gonna' work with the HTML color picker to see what other combos I can come up with.

Btw, just for the heck of it, I updated my smirkit with COTR 2.1 and flashed it instead of fast booting it.

Anyway, thanks again for this update.

Mike T
[Kindle Fire Android Development] Thepooch:
There can be only one.
[Kindle Fire Android Development] portezbie:
flashable zip?
[Kindle Fire Android Development] webdroidmt:
smirkit with COTR 2.1

For those not comfortable using fastboot, I've updated smirkit with COTR 2.1. You can find the download link on the smirkit thread here:

http://xdaforums.com/showpost.php?p=34974869&postcount=325

Mike T
[Kindle Fire Android Development] Sblood86:
Hmm; suppose it wouldn't be a bad idea I just didn't really consider it lol...

I almost messaged him in regards to that but I knew he didn't have a KF so I figured we'd leave it be lol

Edit: linked to the OP as well.
[Kindle Fire Android Development] dadeo1111:
great work, but..

I love new stuff and really want to try this -- it sounds great -- but with the past mis-flash issues with all versions of CWM and similar problems with many of the later TWRP versions on the KF device, I'm, to say the least, a little gun-shy. (the name also adds to my unease - but so would a pink unicorn heh)

Perhaps when I see folks posting multiple (2-3) successful flashes of different roms with this, I will jump on board with both feet. As clunky or ugly as it is, TWRP 2.1.1.1 works flawless for me and has for months so, as much as I like the latest/greatest, I'm holding off for now.

Many thanks to the OP and all the other fine Android developer volunteers here as well. :highfive: Your efforts are immensely appreciated - especially when you innovate a new solution like this one. Unfortunately I'm a relative android n00b and have scant confidence in unbricking my device should that occur, and even, as low as prices are, less ability to replace it as I'm on fixed income that almost covers living expenses. Sorry.. :(
[Kindle Fire Android Development] isaiahhhhh:
I'm on board with you, I've become complacent with the ease of use the developers have granted us with flashing roms for the Kindle Fire. Much of what I learned when I first started messing with the Kindle Fire has been left in a dusty part of my brain because I haven't needed to use it. If I was still able to confidently unbrick the KF (or at least know i'd have a good shot at it) i'd give this recovery a try, but my confidence isn't there and neither is my funding for a new KF should I void the warrenty.
[Kindle Fire Android Development] Sblood86:
I understand the reluctance but also can state fairly plainly that IF you had been following CWM issues closely you would know that the only issues that CWM ever had with the kindle was Flashing 3.y kernels (resolved a long time ago with the first iteration of my recovery {before we renamed it}) and the super bricks with the ICS+ based recovery (solved by removing the EMMC wipe calls); this is a gingerbread hybrid so the last of those 2 isn't even remotely possible...

A fairly moderate amount of research would prove both of those statements; I would NOT release something that I wasn't confident worked. The only risk to bricking your devices while using this recovery is improper usage and/or flashing or doing something you shouldn't be doing...

Just to reinforce that statement I haven't used TWRP since last December when I rooted my Kindle Fire; it has always ran a variation of CWM or similar and guess what; it still works :P

I also have a jellybean based recovery for us; works flawlessly (I've been running it on my kindle for months without any emmc crashes {yes I do have the faulty samsung emmc so if there were still erase issues I would have a brick sitting on my desk; again, I don't :D}) apart from USB mass storage (which is the only reason we released the hybrid instead of the jellybean based recovery).

Now I know you guys are going to make up your own minds and so forth and I wouldn't ask for anything less; part of the reason I love Android devices is the Open Source nature and the fact that you aren't required to use one specific program so if you don't like the recovery that is entirely your right. Having said that I'd hate for fear to be the only thing that kept y'all from trying something new; read the recovery discussion in Hashcode and DooMLoRDs old recovery threads if you would like to know more on the subjects, also my CM7 thread discusses the my original iteration of CWM based 'hybrid' (gingerbread-ics) recovery (the release of which overshadowed as Hashcode released his ICS based recovery at the same time and people did have issues with it do to kernel wipe errors: these never occurred for those using the hybrid recovery and I'm sure you guys could find a few people to confirm that).

One final thought; instead of looking for posts saying it works, try finding one saying it doesn't :p (I personally never post when something works as it's implied in the fact that noone has screamed out saying it doesn't)

Edit: I forgot to mention we released 3 dev previews and a release candidate of this to our beta testers at the POC forums long before a public release ;) (the rc was actually only out for a week but that was mainly to make sure we hadn't broken anything {layout related} since dev3).
[Kindle Fire Android Development] webdroidmt:
COTR

A vote of confidence here for COTR. Don't get me wrong, I like TWRP with all its features, "pretty" UI and I especially like renaming my backups from within the recovery. But I had posted back in the summer that TWRP was becoming consistently unreliable for me in flashing ICS & JB roms, usually resulting in a flash failed error. At first I thought it was just bad downloads but this was with the MD5 matching and it would eventually flash after rebooting and reflashing on the second or third try. In a nutshell, every time I flashed a rom, I wondered if it was going to flash or bomb out on me.

With CWM not being a viable option, I was very happy to see Sblood release COTR and I've been using this as my recovery since August. I like supporting Sblood's work but more importantly I have confidence that my zips are going to flash every time as long as they are not corrupt.

Let me just say, I'm a flashaholic. :D I generally test just about every rom in this forum and I'm running nandroids just about every other day. Matter of fact, I maintain 3 different roms on this forum with 3 different Google accounts...they're cheap :laugh: Since I've been using COTR, I've not had one bad flash and I've backed up and restored more times than I can count without issue.

Now, if only the next version of COTR allows for renaming the nandroids. LOL Actually, I see from the COTR forum that it's on the to-do list. Well, that's my two cents and I guess we should all use what we're comfortable with in the long run.

Mike T
[Kindle Fire Android Development] mdaa83:
Looks promising. I flashed it using my favorite tool dd and it worked so far with my own unsigned zip file that resets all my custom tweaks via goo manager. I haven't tried any other features yet.
[Kindle Fire Android Development] firered365:
How do we make it portrait?
[Kindle Fire Android Development] Sblood86:
It's controlled in the screen firmware and driver controller in the kernel; simply put, you don't/can't. Sorry.
[Kindle Fire Android Development] :
SBlood,

I am interested in flashing this via smirkit (I believe Mike updated it to include the newest version of COTR)

Will this incidentally affect my dual booting?

Also, will I lose access to my TWRP nandroid backups?

Thanks for the time!

-Justin
[Kindle Fire Android Development] Sblood86:
I have no idea how this will effect your dualbooting (probably won't make a difference) as I haven't ran it; sometime in the not too distant future I'm going to have to cause I have a toy branch I've been working on to try to add altboot recovery options...

TWRP backups definitely will not work; there is a huge difference in how the backups are done on twrp vs CWM. We're using the CWM backup method at least for the time being (though to be fair I rewrote nandroid like crazy cause I hated the path generation redundancy). If you have backups you need to convert to COTR from TWRP I've heard of people using TWRP to restore their backups than fastbooting COTR and recreate said backups individually but frankly it's more effort than I would ever put in.
[Kindle Fire Android Development] :
WOW. Flashed it with smirkit. What a VAST improvement over twrp. Nandroid works great. Flashed a ROM wiped restored...so smooth and great interface.
[Kindle Fire Android Development] Vlasp:
Okay.

So I installed this via smirkit, and it worked yesterday. But today, when I booted recovery through fffe1.4a, it leads me to a blank screen. Help!

Devices:

Kindle Fire with AlienDroid primary and Modaco secondary
[Kindle Fire Android Development] :
OK...boot back into your system and flash it again with smirkit. If it doesn't work then flash twrp with smirkit.

Sent from my GT-N7000000000 using Tapastalker 2
[Kindle Fire Android Development] Vlasp:
I Installed a new ROM without smirkit:(

Devices:

Kindle Fire with AlienDroid primary and Modaco secondary
[Kindle Fire Android Development] :
wait for sblood to chime in
[Kindle Fire Android Development] Vlasp:
I just installed twrp from kfu and installed smirkit from there!:good::good:
[Kindle Fire Android Development] Sblood86:
Little interesting, not sure what would have caused the blank screen; I really should get y'all a flashable zip or something other than just the binary image.

It's working now though I take it Vlasp?
[Kindle Fire Android Development] Vlasp:
No, I had to install twrp 2.3.3.1 as it would lead me to the blank screen again using smirkit.
[Kindle Fire Android Development] :
Maybe you had a bad download
[Kindle Fire Android Development] Sblood86:
Very strange; I've never seen a black screen loading recovery on the kindle accept in the event that I flashed a fubard test image (I've done that a lot but this is no test image lol) or when screwing with the theme engine (as mentioned below).

Also haven't had anyone else report an error like this. I would definitely like to help resolve it though cause that's obviously not good...

This is very possible, definitely make sure you are checking the md5sums (though to be fair Smirkit has the md5sums included and checks them during flashing). I've never personally used Smirkit so my best recommendation/test option is going to be to fastboot the image and see what happens.

There is another possibility; were you running an older version of COTR? If so make sure to delete the settings file from cotrecovery/ on your sdcard (the wrong settings could in some cases cause the screen to boot blank; this is something I'm hoping to sort out in future releases with better error handling) (the same error can also occur if you apply a broken custom theme (as in missing any images), another thing that needs slightly better error handling (initial write up of the current theme engine was pushed to git by Drew and honestly I didn't notice the lack of error handling til sometime after release when I locked up my phone with a bad theme lol). Easiest solution for trying to use a bad theme is to delete the settings file again so that it launches the default theme.
[Kindle Fire Android Development] webdroidmt:
Hi Vlasp,

Just re-downloaded the smirkit 2.2 from here: http://xdaforums.com/showpost.php?p=35711679&postcount=329 and went from COTR to TWRP, then back to COTR again with no issues. Are you using smirkit 2.2 from the link above?

Also, as Sblood mentioned, smirkit won't flash the recovery if the MD5 doesn't match. Btw, what rom are you using? If it's Hashcode's AOSP 4.2 rom, you have to install busybox, or smirkit can't work. Although, you said it initially worked, so I'm confused. :confused:

Hopefully, you get it sorted out.

Mike T
[Kindle Fire Android Development] Vlasp:
Yes. And it passed the MD5 check. Weird. Will flash again.
[Kindle Fire Android Development] vbdss:
If i want to install a new rom but dont want to go through the process of installing apps and configuration os settings, should i restore only data and sd-ext if i have some apps moved to sdcard?
[Kindle Fire Android Development] :
Not the right place to ask this. Go to Q&A.
[Kindle Fire Android Development] Vlasp:
Will there ever be themes from sdcard. I tried to get a theme and it didn't work.
[Kindle Fire Android Development] Sblood86:
The themes do work but they are a little picky; these three definitely load (https://github.com/ProjectOpenCannibal/sdcard_themes) make sure you are using the default branch (gb-1024x600)

You would want to create a folder inside of sdcard/cotrecovery of theme with a subfolder of custom, so that the path is the following

/sdcard/cotrecovery/theme/custom/

And in the last folder place all the images and ini file from one of the listed themes.

We need to add some better error handling for themes but otherwise the engine works if anyone wants to do a custom theme they'll just want to make sure to follow the guidelines exactly.
[Kindle Fire Android Development] votinh:
Got the answers
[Kindle Fire Android Development] lindsay56:
Finding my backups

Can someone tell how I can see my backup list without opening file explorer or going into recovery btw is COTR ver2.1. I really like COTR recovery because it is very simple to use and does a much better job of wiping my Kindle Fire. I am running Hashcode's latest rom and FireFireFire 1.4.1.
[Kindle Fire Android Development] :
Wouldn't work changed my mind
[Kindle Fire Android Development] Sblood86:
Umm... Apart from recovery or a file manager there aren't a lot of ways to view your old backups, maybe part of the control app in the future but not as of yet.
[Kindle Fire Android Development] 404-Not Found:
will KitKat work with this recovery? I am having trouble with TWRP
[Kindle Fire Android Development] KindleUser:
Same here, won't mount data. Let's see if we get a reply.
[Kindle Fire Android Development] :
I'm a newbie, so I don't know what everyone is talking about. But I do thank COTR team for this recovery, TWRP was a fail for me :thumbup::thumbup::thumbup::thumbup::thumbup:

Sent from my air powered ceiling fan
[Kindle Fire Android Development] Sblood86:
It should work with kitkat in theory but I've yet to personally test it (been working on a rebase of sorts has had me distracted along with work and other projects)
[Kindle Fire Android Development] KindleUser:
I'll be your test monkey if you need one. It won't brick my device so it's worth risking.
[Kindle Fire Android Development] :
Edit : updated op

Sent from my air powered ceiling fan
[Kindle Fire Android Development] Sblood86:
For some reason I thought I updated the OP with the new link (I pasted it on the KFU page at one point), at anyrate I updated the OP.

Our domain expired while our system administrator was AWOL and got snagged up by domain trolls trying to sell it back for $200+

Next time you could just ask instead of assuming.
[Kindle Fire Android Development] :
After flashing 4.4, can I put back COTR?

Sent from my Amazon Kindle Fire
[Kindle Fire Android Development] callmechewy:
Download link is broken again.

Tried it manually and through the KFU.
[Kindle Fire Android Development] :
Same here

Sent from my air powered ceiling fan
[Kindle Fire Android Development] Sblood86:
Matt and Drew have been fiddling around with the server I don't know what's going on right now. The current version of recovery does not support flashing 4.4, while we have been working on an updated version there are still a number of issues.
[Kindle Fire Android Development] :
Sblood86 if u send me a dropbox link I can put it up on my goo.im for you

Sent from Omni Nexus 5
[Kindle Fire Android Development] :
And me to androidfilehost
[Kindle Fire Android Development] VTCruzer:
[MENTION=3973140]Sblood86[/MENTION] How's the progress on KitKat support?
[Kindle Fire Android Development] Sblood86:
Works on some devices, I need to sort out some issues w/ my build environment; nothing I compile boots atm (woo lol) and than test and fiddle the mako and otter.