[RECOVERY][ariel] TWRP 2.8.6.0 touch recovery [2015-06-07] - Fire HD 6 and 7 Original Android Development

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.
Phone look:
Tablet look:
CHANGELOG for 2.8.6.0:
Fix daylight savings time rules for USA and Europe (_that)
Allow mulitple overlays for popup boxes (Dees_Troy)
Add pattern style password entry for decrypt (Tassadar)
Keyboard improvements (_that)
Update AOSP base to 5.1 (Dees_Troy)
Reduce theme count to 5 and rely on scaling (Dees_Troy)
Various scaling improvements (Dees_Troy)
Improved handling of resources in the GUI (_that)
Make scroll bar size proportional to list size (_that)
Allow scoll lists to render without a header (_that)
Make console scroll per pixel with kinetic scrolling (_that)
Support styles in XML to reduce XML size and improve consistentcy (Dees_Troy)
Various other fixes and improvements (mdmower, bigbiff, codelover, etc)
CHANGELOG for 2.8.5.0:
Scale the GUI - TWRP can read the theme's resolution and scale it up or down to fit the theme to your screen's resolution
Backups can now be cancelled while the backup is in progress (does not include restore because we don't want to leave your device in a bad state)
Improve thread handling and move input handling into the main rendering thread to improve stability
Make MTP work even if unplugged and plugged back in
Unify scrollable list code and make kinetic scrolling feel more natural
Fix handling of mapped zip files for OTA updates (CM12 updater)
USB keyboards should now work on all devices that support USB host mode via a USB OTG cable
Other small fixes and improvements
CHANGELOG for 2.8.4.0:
Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
Fix some MTP related crashes and bugs
Eliminate TWRP toggling USB IDs during boot if MTP is enabled
Fix various adb sideload issues
Improve threading of actions
Eliminate separate thread for screen timeout
Update libblkid to 2.25.0
Use power button as back button on watch themes for easier navigation
Add mutex locking to data manager
Improve custom theme handling on encrypted devices
Allow the stock theme to be offset by build flags so we can center a lower res theme on a higher res screen especially for watches with round screens
CHANGELOG for 2.8.3.0:
MTP will now tell the host PC that storage is removed instead of disabling MTP completely
MTP will now report the correct max file size based on the file system in use to the host PC (may fix transfer of large files)
Update and improve fix permissions and make fixing contexts optional
Update SuperSU in TWRP to 2.40 and update install process
Make TWRP work properly on AArch64 (Nexus 9 is now built in true 64-bit binaries and libraries)
Attempt to set correct permissions and contexts on all files placed in storage so backups will show in Android
Fix kernel panic during MTP start on some devices
Support unicode fonts on devices with True Type Font support
Fix slider value not showing sometimes (vibration settings page)
Toggle MTP off during adb sideload to set correct USB IDs
Reduce library requirements for 5.0 L decrypt
Other minor fixes and improvements
Note: Starting with TWRP 2.8.2.0 and higher, adb sideload uses a new sideload method originally implemented in AOSP recovery. You will need the latest adb binaries to use sideload in these newer versions of TWRP. The version required is 1.0.32. You can find the version by running "adb version" on your computer. The new sideload feature no longer stores the zip on your device. Instead, a fuse file system is created in RAM and the zip is streamed from your computer. This puts less wear and tear on storage and ensures that large zips will not fill up all of your RAM. The sideload may spit an error on your PC side, but the zip should install just fine on your device.

---

Everything seems to be working. No known issues. USB-OTG works also
Downloadhttps://www.androidfilehost.com/?fid=24052804347756852
or use our TWRP Manager software to install it automatically for you
Install either by DD or maybe flashify will work for you.
Code:
dd if=recovery.img of=/dev/block/mmcblk0p7
Thanks goes to @Dees_Troy as this was my first MediaTek based device to build recovery for
This will also be taken official this week.

---

Pulled download temporarily

---

Thanks for your work dude but we do not have recovery image for our Fire 6 HD sadly ...

---

alucard_xs said:
Thanks for your work dude but we do not have recovery image for ou Fire 6 HD sadly ...
Click to expand...
Click to collapse
The HD 7 and HD 6 are EXACTLY the same device. The OTAs for both are EXACTLY the same. The only difference is the screen size. There essentially is no difference betweent the 2 devices

---

Sure but what about factory / recovery image, is there anyone floating around ?

---

alucard_xs said:
Sure but what about factory / recovery image, is there anyone floating around ?
Click to expand...
Click to collapse
just dump your current recovery.img.
dd if=/dev/block/mmcblk0p7 of=/sdcard/stockrecovery.img
Then as soon as you boot into recovery make a backup.

---

Root
Will flashing the SuperSU package in recovery root, or cause a bootloop?

---

ryanyz10 said:
Will flashing the SuperSU package in recovery root, or cause a bootloop?
Click to expand...
Click to collapse
Dont need to flash anything with TWRP. If you boot twrp then choose reboot to system option it will ask if you want to install SuperSU.

---

Reuploaded fixed version. Found a couple bugs that i didn't notice before. All good now

---

So for us the slow ones, can you explain this in detail?
You've replaced the stock recovery with TWRP, so we can flash images from USB drives ? But you need root to do the first flash to recovery, correct?
Will Amazon update re-write the recovery partition so you are back to stock ?

---

bibikalka said:
So for us the slow ones, can you explain this in detail?
You've replaced the stock recovery with TWRP, so we can flash images from USB drives ? But you need root to do the first flash to recovery, correct?
Will Amazon update re-write the recovery partition so you are back to stock ?
Click to expand...
Click to collapse
yes. and future custom roms if they come. You should be disabling OTAs anyways. OTAs im pretty sure will fail anyways with a custom recovery

---

jmz said:
yes. and future custom roms if they come. You should be disabling OTAs anyways. OTAs im pretty sure will fail anyways with a custom recovery
Click to expand...
Click to collapse
Man, that's pretty awesome! It sounds like one just needs one good TWRP flash, and then it's not that hard to recover after a screw up via OTG.
And it seems like with this TWRP we should be able to flash Amazon updates onto the device (such as 4.5.4), and install root on top after that ? Root 4ever ? How hard is it to make TWRP flash stock Amazon updates ? I want 4.5.4 , with root !!!
You could also change the size of /cache, and add it to /data, or move dalvik cache from /data to /cache, see these allocations (there is 1 Gb of space in /cache !!!):
http://forum.xda-developers.com/fire-hd/help/internal-memory-structure-hidden-t3122246
So even without a custom ROM there are tons of easy tweaks that one could do.
I actually got to like the Fire OS, it is super stable for me. With custom recoveries things are often quite rocky for a while. I'd like to get some sort of Android Setup app, in order to change things above and beyond what Amazon allows (such as that Cyrillic AOSP keyboard!).
Once you figure out how to put stock Amazon update files onto the device plus root, you can pretty much play with Xposed and get into risky stuff (not being afraid of bootloop.) Just make sure to keep the trusty TWRP handy!!!

---

bibikalka said:
Man, that's pretty awesome! It sounds like one just needs one good TWRP flash, and then it's not that hard to recover after a screw up via OTG.
And it seems like with this TWRP we should be able to flash Amazon updates onto the device (such as 4.5.4), and install root on top after that ? Root 4ever ? How hard is it to make TWRP flash stock Amazon updates ? I want 4.5.4 , with root !!!
You could also change the size of /cache, and add it to /data, or move dalvik cache from /data to /cache, see these allocations (there is 1 Gb of space in /cache !!!):
http://forum.xda-developers.com/fire-hd/help/internal-memory-structure-hidden-t3122246
So even without a custom ROM there are tons of easy tweaks that one could do.
I actually got to like the Fire OS, it is super stable for me. With custom recoveries things are often quite rocky for a while. I'd like to get some sort of Android Setup app, in order to change things above and beyond what Amazon allows (such as that Cyrillic AOSP keyboard!).
Once you figure out how to put stock Amazon update files onto the device plus root, you can pretty much play with Xposed and get into risky stuff (not being afraid of bootloop.) Just make sure to keep the trusty TWRP handy!!!
Click to expand...
Click to collapse
Yeah, I am going to be working on the update this week. Starting a new job tomorrow.
Also, I added a link to our software TWRP Manager so it is even easier to install TWRP.

---

jmz said:
Yeah, I am going to be working on the update this week. Starting a new job tomorrow.
Also, I added a link to our software TWRP Manager so it is even easier to install TWRP.
Click to expand...
Click to collapse
I just saw your boot unlocker thread, you should better manage your cross-references Congrats for getting us this far!
But I wonder if one could just flash 4.5.4 first, and then unlock the bootloader, and install TWRP, then root. Which bootloader versions can be unlocked? All so far? So people who were force updated to 4.5.4 are not SOL ?
Of course, it's easier to just have TWRP flash Amazon updates, then root is always available. That would be an enabling step, with the ability to flash Amazon stock ROMs, one can mess things up totally, and still recover back.
Exciting times, man !!!!

---

bibikalka said:
I just saw your boot unlocker thread, you should better manage your cross-references Congrats for getting us this far!
But I wonder if one could just flash 4.5.4 first, and then unlock the bootloader, and install TWRP, then root. Which bootloader versions can be unlocked? All so far? So people who were force updated to 4.5.4 are not SOL ?
Of course, it's easier to just have TWRP flash Amazon updates, then root is always available. That would be an enabling step, with the ability to flash Amazon stock ROMs, one can mess things up totally, and still recover back.
Exciting times, man !!!!
Click to expand...
Click to collapse
Messing with things more and more I don't think that is a fully working bootloader unlock. For example, I can't boot an unsigned boot.img after flashing. But I can boot it if I flash to recovery partition then issue adb reboot recovery.
Or that may just be a MTK/Amazon/LK thing. Not too sure at this point. But it seems right now, custom kernels are out of the question.

---

jmz said:
Messing with things more and more I don't think that is a fully working bootloader unlock. For example, I can't boot an unsigned boot.img after flashing. But I can boot it if I flash to recovery partition then issue adb reboot recovery.
Or that may just be a MTK/Amazon/LK thing. Not too sure at this point. But it seems right now, custom kernels are out of the question.
Click to expand...
Click to collapse
I see what you mean ... Even a partial unlock is huge step forward in terms of customization options, and the biggest deal is that now it's not too scary to screw up! Btw, in Amazon update files there is recovery-from-boot.p, is that the image we need for recovery? Or should we make a proper one via dd?
In Amazon update they seem to update recovery, but I wonder who checks for signed boot.img ? Is this part of the chipset ?
(from /recovery/etc ):
#!/system/bin/sh
if ! applypatch -c EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery:5888256:6d9d1bbc4172c107db3228ed8d9f97111219c617; then
log -t recovery "Installing new recovery image"
applypatch -b /system/etc/recovery-resource.dat EMMC:/dev/block/platform/mtk-msdc.0/by-name/boot:5370112:c2c686ada1b194050a3c8f05e2102345df48e9ce EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery 6d9d1bbc4172c107db3228ed8d9f97111219c617 5888256 c2c686ada1b194050a3c8f05e2102345df48e9ce:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi

---

bibikalka said:
I see what you mean ... Even a partial unlock is huge step forward in terms of customization options, and the biggest deal is that now it's not too scary to screw up! Btw, in Amazon update files there is recovery-from-boot.p, is that the image we need for recovery? Or should we make a proper one via dd?
In Amazon update they seem to update recovery, but I wonder who checks for signed boot.img ? Is this part of the chipset ?
(from /recovery/etc ):
#!/system/bin/sh
if ! applypatch -c EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery:5888256:6d9d1bbc4172c107db3228ed8d9f97111219c617; then
log -t recovery "Installing new recovery image"
applypatch -b /system/etc/recovery-resource.dat EMMC:/dev/block/platform/mtk-msdc.0/by-name/boot:5370112:c2c686ada1b194050a3c8f05e2102345df48e9ce EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery 6d9d1bbc4172c107db3228ed8d9f97111219c617 5888256 c2c686ada1b194050a3c8f05e2102345df48e9ce:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
Click to expand...
Click to collapse
all devices have that in some form or another.
I would make a dd backup of the stock one before flashing.

---

jmz said:
just dump your current recovery.img.
dd if=/dev/block/mmcblk0p7 of=/sdcard/stockrecovery.img
Then as soon as you boot into recovery make a backup.
Click to expand...
Click to collapse
Is there an option in TWRP Manager to save stock recovery without any reboots? This sounds like an easy feature to add. Or is this part of "live backup" ?

---

bibikalka said:
Is there an option in TWRP Manager to save stock recovery without any reboots? This sounds like an easy feature to add. Or is this part of "live backup" ?
Click to expand...
Click to collapse
No there isn't.
Well, I guess I am out of the game for awhile. Just bricked my Fire.