[Kindle Fire 2 Android Development] Hashcode:
[ THIS POST IS TEAMWIN'S STOCK TWRP POSTING. USE OF THE WORDS "US" AND "OURS" MEANS "DEES_TROY AND TEAMWIN" NOT HASHCODE ]

*** ALL CREDIT FOR TWRP BELONGS TO DEES_TROY AND TEAMWIN. ***

They do a BANG UP job on making a fantastic customizable touch-based recovery.

Donate to TeamWin:

http://www.teamw.in/project/twrp2

BEFORE YOU FLASH THIS, PLEASE MAKE SURE THAT YOU HAVE A 2ND-BOOTLOADER INSTALLED FROM HERE:

http://xdaforums.com/showthread.php?t=2100963

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.

Tablet look:

CHANGELOG for 2.6.3.0:

-Proper backup and restore of SELinux contexts (thanks to Tassadar)

-Pull in some ROM information for backup name generation

-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3

-Add 1200x1920 theme (thanks to Tassadar)

-A few other fixes and tweaks

CHANGELOG for 2.6.1.0:

-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)

-Initial support for f2fs file system formatting (Moto X)

-Update SuperSU install for 4.3 ROMs

-Fixed a permissions bug on files created during backup

-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match

-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible

-Ignore lost+found folder during backup and size calculations

-Various other minor bug fixes and tweaks

CHANGELOG for 2.6.0.0:

Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!

-Can encrypt a backup to prevent theft of private data from your backup files

-Updated graphics / icon courtesy of shift

-Updated exFAT to latest commits

-Fixed a problem with Samsung TouchWiz decryption

-Update SuperSU binary

-Fixed saving of backup partitions list

-Fixed saving of last used zip install folder

-Fixed backup of datadata on devices that use a separate partition for datadata

-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)

-Fixed some problems with partitioning a SD card

-Various other bug fixes and tweaks

Notes about encrypted backups:

Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.

Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.

CHANGELOG for 2.5.0.0:

Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.5.0.0 as your custom theme will likely not be compatible with the new changes!

-Added scrollable partition lists for mount, backup, restore, wipe, and storage selection

-Add new SliderValue GUI element for selecting brightness and screen timeout (thanks to Tassadar)

-Re-work AOSP and TWRP code to improve license compatibility between GPL and Apache

-Added official theme for 1080x1920 portrait devices (HTC One m7, HTC DNA, HTC Butterfly, Oppo Find 5, Sony Xperia Z, etc)

-Fixed a problem with directory permissions on split archive backups (backups usually restored with no app data)

-Fixed a problem with md5 verification of backups

-Added a search function to libtar (thanks to kokotas)

-Improve handling of XML errors (fix permissions)

-Fixed handling of subpartitions

-Improvements to recovery.fstab flags

-Fixed a problem with decryption not being able to locate the decryption key in some situations

CHANGELOG for 2.4.4.0:

-Added another libtar hardlink workaround to fix restore of some backups (usually related to Ubuntu Touch)

-More fixes for the file selector

-Switched from using busybox md5sum to a direct C function call

-Fixed capturing the exit status of tar based backups/restore - TWRP will display that there was an error if there was one again

-Update exFAT to latest commits

-Added a build flag to disable using the ioctl for screen blanking

CHANGELOG for 2.4.3.0:

-Fixed 2 bugs related to restore, one dealing with mknod failures (by bigbiff) and one dealing with restoring hardlinks (by Dees_Troy)

NOTE: If your backups weren't restoring correctly in earlier 2.4.x versions they should restore correctly now. Hopefully you didn't delete those backups. If you're still having problems, run the restore, go to advanced and copy log, then give us the log. Complaints without logs will be rightfully ignored.

-Added a scroll bar to file selectors and listboxes courtesy of Tassadar

-Added libblkid for more accurate detection of file systems and can now detect exFAT properly thanks to bigbiff

-Added a screen dim effect 2 seconds before screen off on some devices

-Finally fixed file selector crash (one of the joys of working with multi-threaded software)

-Fixed loading of screen timeout setting during startup

-Improvements and bugfixes to screen timeout code

-Fixed persistence of the 24 hour / military time setting

CHANGELOG for 2.4.2.0:

-Add screen timeout - screen will turn off automatically after 60 seconds, saves battery and prevents screen burn-in especially on AMOLED devices

-Add a brightness setting (requires device specific setup and only some devices have been added)

-Add a root checker and offer to install SuperSU if the device isn't already rooted

-Add a write buffer to libtar backups, significant improvements to speeds when backing up to exFAT target, minor improvements for other file systems

-Check and offer to fix root permissions if broken

-Add an option for a 24 hour clock display instead of AM/PM (aka military time)

-Move stock recovery reflash check to occur during the reboot cycle

-Add support for some MTK6xxx devices

-Change libtar to vfork to help prevent memory problems

-Add a "clicked" effect to most buttons, file selector, and listbox

-Improve timezone listbox to be more like file selector (per pixel kinetic scrolling, etc)

-Remove some no longer used settings (Forced MD5 sum on zips, size checking on image backups)

-Other minor bugfixes and improvements

CHANGELOG for 2.4.1.0:

-Fixed a problem with mkdosfs that formatted sdcards to 2GB

-Fixed handoff between vfat and exFAT on devices where blkid didn't detect vfat (fixes some issues with mounting sdcards)

-Fixed problems with changing working directory on MD5 creation/checking that may have prevented unmounting

-Backups will now store a copy of the backup log after the backup is completed (only if backup is successful)

CHANGELOG for 2.4.0.0:

-Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes (thanks to bigbiff)

-Support for exFAT formatted sdcards (also thanks to bigbiff)

-Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)

-Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running

-Added wipe cache and dalvik after ADB Sideload

-Replaced many system calls with their native C counterparts

-Fixed bugs in file manager where it would display an empty list after moving or deleting a folder

-Fixed AOSP recovery commands to run after decryption on encrypted devices

-Improvements for building TWRP in CM10.1

-Other minor bugfixes and improvements

NOTE: 2.4.0.0 is, as always, still compatible with your older backups!

** THIS IS A FLASHABLE .ZIP FILE FOR INSTALLING IN YOUR CURRENT VERSION OF TWRP **

DOWNLOAD:

[ DO NOT DOWNLOAD ANY FILES FROM TEAMWIN'S WEBSITE. IN GENERAL, THEY ARE MEANT TO BE FLASHED TO UNLOCKED DEVICES AND WON'T WORK FOR THE KINDLE FIRE 2 ]

You can download from goo.im here and place on your SDCARD:

http://goo.im/devs/Hashcode/otter2/recovery-zip/zip-otter2-twrp-2.6.3.1-recovery.zip

md5sum: b9eb941b1673396c91f73ccda010daf1

INSTALL INSTRUCTIONS:

During the BLUE logo screen press the power button to cycle through options and select "Recovery" to enter TWRP.

Select "Install"

Navigate to where you placed the file on your device

Select the .zip filename

Swipe to confirm flash

Reboot

KNOWN ISSUES:

None at the moment.

BUGS:

First: I'd read through this thread and see if your issue isn't answered.

Second: Try googling for it

Third: If it seems like a Kindle Fire 2 issue, then post in the thread.

Lastly: If you have found a bug, please consider posting it to TeamWin's github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!

SUPPORT:

Live support is available via #kindlefire-dev or #twrp on Freenode with your IRC client or just click this link.