[RECOVERY][otter] TWRP 3.1.0-0 touch recovery [2017-03-10]

Search This thread

leswgnr

Senior Member
Feb 3, 2012
181
45
New York
If you used the power button to get into recovery while FFF was loading, reboot to system will work fine. That's not what's being discussed here.

If you got to recovery that way, the bootmode was never changed and stayed (presumably) on 4000. So, hitting the reboot from within TWRP will continue to boot in normal mode and it "seems" to work fine.

Try setting the bootmode to recovery (5001) and restart the device to get to TWRP. Then if you try rebooting into the system, it will go back into TWRP because TWRP does not change the bootmode back to normal (4000) before attempting to reboot into the system.

The same problem exists for all the reboot options in 2.1.0... whether normal, recovery, or bootloader, it will not change the bootmode to the appropriate value before restarting the device. As a result, the device will just reboot using whatever bootmode is already set.

EDIT: What Sblood86 said above... I'm just longer winded.
That's a really clear explanation kingfauns-thanks. It does bring up something I've wondered tho. How is fff loading twrp if not by changing boot modes?
 

Sblood86

Inactive Recognized Developer
Apr 18, 2011
415
407
Middle of nowhere, Texas
That's a really clear explanation kingfauns-thanks. It does bring up something I've wondered tho. How is fff loading twrp if not by changing boot modes?

I'm about to go to work so I can't dig much deeper but here's a general idea, if you check where Pokey merged the recovery option inially you will see that the bootmode is actually checked but not changed. Instead it's setting the boot environment to recovery with the following:

Code:
s = getenv("recoverycmd");

As for how the environment commands work I would have a dig a little deeper but I don't have that time right now, Kinfauns may have a better answer but this should give you an idea.
 
  • Like
Reactions: smirkis

kinfauns

Retired Senior Moderator and Retired DC Lead
Jan 5, 2012
1,864
3,543
That's a really clear explanation kingfauns-thanks. It does bring up something I've wondered tho. How is fff loading twrp if not by changing boot modes?

I'm about to go to work so I can't dig much deeper but here's a general idea, if you check where Pokey merged the recovery option inially you will see that the bootmode is actually checked but not changed. Instead it's setting the boot environment to recovery with the following:

Code:
s = getenv("recoverycmd");

As for how the environment commands work I would have a dig a little deeper but I don't have that time right now, Kinfauns may have a better answer but this should give you an idea.


The important thing to note here is that the bootmode does not dictate to the bootloader how the bootup should proceed. Rather, the bootloader uses the bootmode as just one variable in its decision making process. Utlimately, the bootloader checks to see if either the bootmode has been set to recovery or the power button has been pressed during the temporary fastboot countdown. If either of those conditions happens to be true, the bootloader program will boot the device into recovery.

SBlood86 is right on about the line of code he pasted. Just to satisfy my own curiosity, I skimmed through the code to see what role that line plays in how the device boots up. I didn't study it too close, so I don't know all the ins/outs of what it's doing, but I have a general idea. That line fetches an environment variable defined with some options to be used when calling the run_command function. In this case, "recoverycmd" has some LED light settings (which I think is broken according to some posts pokey9000 made) and more important to this discussion, it indicates what storage device and partition should be used to boot.

Hopefully that's enough of a satisfactory explanation or else there's always the source code up on github!
 
  • Like
Reactions: Sblood86

N23

Senior Member
Mar 29, 2007
180
22
How can i install TWRP 2.1?

Every time i use the fastboot command (fastboot -i 0x1949 boot twrp-fire-2.1.0.img) it boots the 2.1 version - fine!
but then after a reboot and choosing to boot to the recovery through firefirefire it shows the previous installed twrp 2.0?
any ideas how to fix that eg. install twrp 2.1 permanent?
 

Dasanko

Senior Member
Dec 18, 2010
255
80
How can i install TWRP 2.1?

Every time i use the fastboot command (fastboot -i 0x1949 boot twrp-fire-2.1.0.img) it boots the 2.1 version - fine!
but then after a reboot and choosing to boot to the recovery through firefirefire it shows the previous installed twrp 2.0?
any ideas how to fix that eg. install twrp 2.1 permanent?

Change

fastboot -i 0x1949 boot twrp-fire-2.1.0.img

to

fastboot -i 0x1949 flash recovery twrp-fire-2.1.0.img
 
  • Like
Reactions: Mr. Ruz and N23

smirkis

Senior Member
Oct 8, 2010
1,820
611
San Diego, CA
wait for the update

dees_troy has fixed flashing and reboot issues, just waiting on his updated release =]

Sent from my HTC Glacier using xda premium
 

llavalle

Senior Member
Jan 28, 2012
51
4
Montréal
For some reasons, the 2.1.0 version does not seem to work on my fire...

2.0.0 works fine but as soon as I flash the 2.1.0, the recovery never works : FFF just hangs after the led turns orange (running FFF 1.2).

I flashed 2.0.0 back and it works fine... weird...

Edit : looks like flashing TWRP 2.1.0 reverted FFF to a previous version.. I lost my "dim green" option... is this normal?

Edit : was caused by a bad download. Cleared my browser cache, re-downloaded and flashed. All working fine now. BTW, don't use "Right-click | Save As" on the link, it will save a webpage (8kb)... Open the link to goo.im and wait for the download to start.
 
Last edited:

mjybarr

Senior Member
Jul 18, 2010
1,261
582
www.mexdroidmod.com
For some reasons, the 2.1.0 version does not seem to work on my fire...

2.0.0 works fine but as soon as I flash the 2.1.0, the recovery never works : FFF just hangs after the led turns orange (running FFF 1.2).

I flashed 2.0.0 back and it works fine... weird...

Edit : looks like flashing TWRP 2.1.0 reverted FFF to a previous version.. I lost my "dim green" option... is this normal?

Could you upload TWRP 2.0.0. I see that I can't find it anywhere.. thanks in advanced!

Sent from my HTC Vision using Tapatalk 2
 

uoY_redruM

Senior Member
May 1, 2010
3,469
1,941
Longwood, FL
My computer is down right now.. is there a easy to flash recoveries via terminal like you can on a phone?

Also, having a weird issue. Every time I try to flash a rom, twrp just reboots. Just started, I use to work fine...

Sent from my Kindle Fire using XDA
 

kinfauns

Retired Senior Moderator and Retired DC Lead
Jan 5, 2012
1,864
3,543
TeamWin has quietly updated TWRP for Kindle Fire to version 2.1.1

http://www.teamw.in/project/twrp2/79
http://goo.im/devs/OpenRecovery/blaze/openrecovery-twrp-blaze-2.1.1.img

  • All reboot options (System, Recovery, Bootloader) work as expected. No more "I'm stuck in TWRP" posts!!!
  • Installation problems found in version 2.1.0 have been fixed. All ROMs I've tested flash correctly. Batch install option is working.
  • Updated GUI (looks nice with a little splash of color)

Upgrade to version 2.1.1 is highly recommended for all users of previous TWRP versions.

Install using fastboot:

Code:
fastboot flash recovery openrecovery-twrp-blaze-2.1.1.img
 

webdroidmt

Senior Member
Dec 20, 2011
1,674
1,156
NJ
Updated from 2.0 to 2.1.1 and like the new look, also appreciate squashing the reboot bugs. Had no issues flashing Hashcode's latest rom and kernel, also made a couple of backups one compressed and one not, they restore fine.

Don't want to sound ungrateful here, because that's not the case. But...I'm not a fan of the swipe button to execute functions. Would've rather had just a plain old button to tap, maybe my fingers just can't stand the exercise. LOL

Dees_Troy, thanks for this update as well as your excellent work with the TP screen drivers.

Mike T
 

acax456

Senior Member
Feb 4, 2011
1,390
261
Hồ Chí Minh
TeamWin has quietly updated TWRP for Kindle Fire to version 2.1.1

http://www.teamw.in/project/twrp2/79
http://goo.im/devs/OpenRecovery/blaze/openrecovery-twrp-blaze-2.1.1.img

  • All reboot options (System, Recovery, Bootloader) work as expected. No more "I'm stuck in TWRP" posts!!!
  • Installation problems found in version 2.1.0 have been fixed. All ROMs I've tested flash correctly. Batch install option is working.
  • Updated GUI (looks nice with a little splash of color)

Upgrade to version 2.1.1 is highly recommended for all users of previous TWRP versions.

Install using fastboot:

Code:
fastboot flash recovery openrecovery-twrp-blaze-2.1.1.img

Can i flash it on my kindle fire use terminal??

Sent from my LG-P500 using Tapatalk 2
 

Top Liked Posts

  • There are no posts matching your filters.
  • 75
    [RECOVERY][otter] TWRP 3.1.1-0 touch recovery [2017-05-19]

    Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its 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.




    CHANGELOG for 3.0.2-0:

    -Backups will now include adopted storage keys (Dees_Troy)
    -Fixed an adb restore issue (bigbiff)
    -Fixed rebooting when no OS is present (Dees_Troy)
    -Fixed line wrapping in the GUI terminal (_that)
    -Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)


    CHANGELOG for 3.1.0-0:

    -vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
    -adb backup to stream a backup directly to or from your PC, see documentation here: https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9 (bigbiff)
    -tweak MTP startup routines (mdmower)
    -support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
    -support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
    -better indicate to users that internal storage is not backed up (Dees_Troy)
    -improve automatic determination of TW_THEME (mdmower)
    -minimal getcap and setcap support (_that)
    -try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
    -shut off backlight with power key (mdmower)
    -timeout during FDE decrypt (Dees_Troy and nkk71)
    -support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
    -boot slot support (Dees_Troy)
    -TWRP app install prompt during reboot (Dees_Troy)
    -support for AB OTA zips (Dees_Troy)
    -support new Android 7.x log command (Dees_Troy)
    -update recovery sources to AOSP 7.1 (Dees_Troy)
    -numerous bugfixes and improvements by too many people to mention

    CHANGELOG for 3.0.2-0:

    -Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
    -Add Greek translation to some builds.

    CHANGELOG for 3.0.1-0:

    -support new CM 13.0 pattern encryption (sultanqasim)
    -fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
    -libtar updated to latest upstream and fixes (jcadduono)
    -fixes for loading custom themes (_that)
    -TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
    -translation updates - added Italian, Czech and Polish and significant updates to Dutch
    -progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
    -fix input box text display (Dees_Troy)
    -reboot option after zip install complete (bigbiff)
    -other mostly invisible bug fixes and improvements

    CHANGELOG for 3.0.0-0:

    -Completely new theme - Much more modern and much nicer looking (by z31s1g)
    -True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
    -Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
    -Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
    -Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
    -Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
    -SuperSU prompt will no longer display if a Marshmallow ROM is installed
    -Update exfat, exfat fuse, dosfstools (by mdmower)
    -Update AOSP base to 6.0
    -A huge laundry list of other minor fixes and tweaks

    WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.

    Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.

    Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.

    We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!

    DOWNLOAD:
    1) Install the TWRP app from the Play Store or grab the apk from our website
    2) Open the app, agree to the terms, and enable root access
    3) Select TWRP Flash
    4) Search for your device and select the version you wish to download
    5) Once the download is complete, select the file (it's usually in your downloads folder) and then Flash Recovery
    OR:
    Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
    1) Download the latest version from our website on your device
    2) Reboot to TWRP
    3) Hit Install and tap the "Images..." button in the lower right
    4) Browse to the location of the TWRP image on your device and select it
    5) Select recovery from the partition list and swipe to flash
    OR:
    You can find more information and download links on our website.

    BUGS:
    If you have found a bug, please consider posting it to our 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 #twrp on Freenode with your IRC client or just click this link.
    20
    flash upload the flashable zip of 2.2.2.1

    Sent from my LG-P500 using xda premium

    Here is a flashable zip...Enjoy! :)

    MD5: edf2b1a6ac2bf05d049d1ca7ff675c07
    17
    Where is the best place to find a zip of 2.5?

    Sent from my Amazon Kindle Fire using XDA Premium HD app

    Here you go Otter TWRP zips from 2.5.0.0 up to 2.6.3.1 this is for all that need to update one TWRP version at a time so they can run KitKat rom enjoy.
    16
    here is an update zip for TWRP 2.3.3.1 :) not sure why it's 2.3.3.1 and not 2.3.3.0 like OP says but got the recovery.img from OPs link and just updated the zip file for flashing to make it easier to install .
    13
    here is a zip to flash the new TWRP 2.4.0.0 put on sd flash reboot recovery and your good to go :)