[RECOVERY][bullhead] TWRP 3.1.1-0 touch recovery [2017-05-19]

[Dees_Troy]

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.

 

[Dees_Troy]

PSA: DO NOT restore EFS backups made with TWRP 3.0.2-1 as there is a bug in that version that affects how the backup is made. Backups of EFS made with TWRP 3.0.2-1 are invalid and should be discarded. Also, seriously people, do not restore EFS unless you absolutely know that you need to.

Device specific page including instructions for a manual install

Download links for current and past versions of TWRP

 

[randman2011]

NOTE: Decrypting data is not supported yet. The Nexus 5X will normally attempt to encrypt the device automatically on first boot. To use TWRP as you normally would, you will have to format data and install a slightly modified boot image with forceencrypt disabled.

Coming from an N5 I'm completely new to device encryption. Could someone explain what the implications of this are? Does installing TWRP require an unencrypted device? Will flashing it require a data format? When you say "use TWRP as you normally would," what would be different with this as it is?

Sorry for these probably really basic questions. I just have no idea what the implications of this are.

 

[mymusicathome]

From what I put together TWRP requires unencrypted kernel/boot. Not to fear though. Looks like chainfire had released an unencrypted kernel/boot - http://xdaforums.com/showthread.php?t=3219344

The N6 came with a forced encrypted kernel/boot. If you want to use a custom kernel you will be flashing an unencrypted kernel. When flashing a unencrypted kernel it will wipe your sdcard. You can encrypt your device later but this will wipe the sdcard.

It's best to flash an unencrypted kernel/boot first if you plan on using custom kernels/ROMs down the road.

 

[0.0]

Can a kernel with encryption be flashed even though the device is encrypted? The reason I ask is for compiling stock kernel with a lower vibration intensity value and not touching anything else

 

[mskip]

Can a kernel with encryption be flashed even though the device is encrypted? The reason I ask is for compiling stock kernel with a lower vibration intensity value and not touching anything else

If your device is encrypted you can still flash any image to your system (as long as the bootloader has been unlocked). Flashing a no-encrypt kernel will not change anything in the system until the device is wiped.

Mark.

 

[TheDj408]

Awesome ! Was waiting for this ! Will flash in an hour And report back !

EDIT: Works Great !

 

[briant1234]

So would I be good to go to install twrp after unlocking bootloader on the 5x?

 

[aes512]

So would I be good to go to install twrp after unlocking bootloader on the 5x?

No, this will screw up your device. http://www.xda-developers.com/a-look-at-marshmallow-root-verity-complications/

 

[Haul]

No, this will screw up your device. http://www.xda-developers.com/a-look-at-marshmallow-root-verity-complications/

How would that screw up his device? At worst, he would have a half broken recovery that can't read or write to his /data partition since he isn't also flashing a modified boot image or kernel, no?

 

[Hayth]

I tried flashing Chainfire's modified boot.img for this phone yesterday and it didn't seem to work. I initially had problems mounting my data partition, and when that failed I had issues with flashing the system.img to restore it - I fixed this by using a program called mfastboot to flash the system.img in 512mb chunks. I eventually managed to get the phone to boot after flashing it and formatting userdata but then I incurred more problems. I had multiple force closes of gapps when trying to go through Google setup. Once I got past these I couldn't check whether the phone had successfully been decrypted as Settings force closed if you tried to enter security. I'm not sure if anyone could shed any light on what I might have done wrong or whether they face the same issues and there's a problem with Chainfire's modified boot.img for the 5x.

EDIT: I think it might've been due to the fact there's 3 different builds - I'm on MDA89E so I'll wait for a modified boot.img for that before trying again.

 

[hachamacha]

I tried flashing Chainfire's modified boot.img for this phone yesterday and it didn't seem to work. I initially had problems mounting my data partition, and when that failed I had issues with flashing the system.img to restore it - I fixed this by using a program called mfastboot to flash the system.img in 512mb chunks. I eventually managed to get the phone to boot after flashing it and formatting userdata but then I incurred more problems. I had multiple force closes of gapps when trying to go through Google setup. Once I got past these I couldn't check whether the phone had successfully been decrypted as Settings force closed if you tried to enter security. I'm not sure if anyone could shed any light on what I might have done wrong or whether they face the same issues and there's a problem with Chainfire's modified boot.img for the 5x.

EDIT: I think it might've been due to the fact there's 3 different builds - I'm on MDA89E so I'll wait for a modified boot.img for that before trying again.

I noticed that @mskip has this mda89e modified image mentioned in this post: http://xdaforums.com/showpost.php?p=63422766&postcount=17

PS: I've not ordered any new phone (yet) but am following things here anyway.

 

[mskip]

I tried flashing Chainfire's modified boot.img for this phone yesterday and it didn't seem to work. I initially had problems mounting my data partition, and when that failed I had issues with flashing the system.img to restore it - I fixed this by using a program called mfastboot to flash the system.img in 512mb chunks. I eventually managed to get the phone to boot after flashing it and formatting userdata but then I incurred more problems. I had multiple force closes of gapps when trying to go through Google setup. Once I got past these I couldn't check whether the phone had successfully been decrypted as Settings force closed if you tried to enter security. I'm not sure if anyone could shed any light on what I might have done wrong or whether they face the same issues and there's a problem with Chainfire's modified boot.img for the 5x.

EDIT: I think it might've been due to the fact there's 3 different builds - I'm on MDA89E so I'll wait for a modified boot.img for that before trying again.

SOMEONE TRIED FLASHING THE IMAGE AND IT DIDN'T BOOT SO I GUESS THE 5X IS A BIT DIFFERENT WITH REPACKING KERNELS. I WOULDN'T ADVISE TRYING TO FLASH IT BUT I WILL FIND OUT WHATS DIFFERENT AND REPACK THE IMAGE PROPERLY.

Mark.

 

[aes512]

How would that screw up his device? At worst, he would have a half broken recovery that can't read or write to his /data partition since he isn't also flashing a modified boot image or kernel, no?

It will put the phone in boot loop is why.

In other news: http://xdaforums.com/showpost.php?p=63426368&postcount=11

 

[suhail_kapoor]

seems like .. I have I am first person who didn't read the complete thread before taking the plunge.

So I fastboot unlocked my bootloader and flashed TWRP straight after. I am now stuck in a bootloop between "your device software cant be checked for corruption" organge screen and TWRPfirst install Failing.

can someone help me please ? I cant even turn off the phone .. kept holding the power switch for a minute no go.

update: I managed to get into fastboot mode again. then installed chainfire's bullhead boot.img and re-flashed recovery.img still no go

 

[hachamacha]

seems like .. I have I am first person who didn't read the complete thread before taking the plunge.

So I fastboot unlocked my bootloader and flashed TWRP straight after. I am now stuck in a bootloop between "your device software cant be checked for corruption" organge screen and TWRPfirst install Failing.

can someone help me please ? I cant even turn off the phone .. kept holding the power switch for a minute no go.

update: I managed to get into fastboot mode again. then installed chainfire's bullhead boot.img and re-flashed recovery.img still no go

Before you try anything, attach your cable from the phone to the PC and open up a command window in any folder that has "fastboot" in the path. Periodically try this command "fastboot devices" and if you get any output that shows a device number, you can do fastboot commands. It isn't so important what's on the screen as whether you can communicate with the device. (I don't have a 5x, but this usually works on just about everything with a similar button config). Be patient. It might take a few tries. So that ^ is something you try periodically but you need to do this next paragraph or two depending upon how far you get:

You can try holding down (all at once for ~10-30 seconds) up & down & power and when you let go (or perhaps before) you should see the fastboot screen. If you do, good because you can repair it one way or another from there. If you see it or even if you don't, try the "fastboot devices" cmd from the cmd window. Repeat until you see a device number come back.

If you ever get fastboot talking to the phone, then download, unpack, (I mean unpack everything down to a directory with a windows batch file and some .img files in it) this file:

Here are the specific links for each variant:
don't need this: MDA89E - 6.0.0: https://dl.google.com/dl/android/aosp/bullhead-mda89e-factory-29247942.tgz
don't need this: MDA89F - 6.0.0: https://dl.google.com/dl/android/aosp/bullhead-mda89f-factory-08c99420.tgz
Get this one: MDB08I - 6.0.0: https://dl.google.com/dl/android/aosp/bullhead-mdb08i-factory-64536fcf.tgz

The one you probably need is the last one MDB081 since I think that is the modified boot image-version that Chainfire has made for bullhead.

Your phone and you probably need a break before trying this again, so just burn that entire file (the link after mdb08I) and if you use the batch file that basically resets everything, then you should be back to "stock" again but with this version (I think it's the latest OTA version).

Good luck.

 

[suhail_kapoor]

Before you try anything, attach your cable from the phone to the PC and open up a command window in any folder that has "fastboot" in the path. Periodically try this command "fastboot devices" and if you get any output that shows a device number, you can do fastboot commands. It isn't so important what's on the screen as whether you can communicate with the device. (I don't have a 5x, but this usually works on just about everything with a similar button config). Be patient. It might take a few tries. So that ^ is something you try periodically but you need to do this next paragraph or two depending upon how far you get:

You can try holding down (all at once for ~10-30 seconds) up & down & power and when you let go (or perhaps before) you should see the fastboot screen. If you do, good because you can repair it one way or another from there. If you see it or even if you don't, try the "fastboot devices" cmd from the cmd window. Repeat until you see a device number come back.

If you ever get fastboot talking to the phone, then download, unpack, (I mean unpack everything down to a directory with a windows batch file and some .img files in it) this file:

Here are the specific links for each variant:
don't need this: MDA89E - 6.0.0: https://dl.google.com/dl/android/aosp/bullhead-mda89e-factory-29247942.tgz
don't need this: MDA89F - 6.0.0: https://dl.google.com/dl/android/aosp/bullhead-mda89f-factory-08c99420.tgz
Get this one: MDB08I - 6.0.0: https://dl.google.com/dl/android/aosp/bullhead-mdb08i-factory-64536fcf.tgz

The one you probably need is the last one MDB081 since I think that is the modified boot image-version that Chainfire has made for bullhead.

Your phone and you probably need a break before trying this again, so just burn that entire file (the link after mdb08I) and if you use the batch file that basically resets everything, then you should be back to "stock" again but with this version (I think it's the latest OTA version).

Good luck.

many thanks mate that worked flawlessly, managed to recover device and so far installed chainfire's boot.img and twrp. on to rooting now.

 

[mskip]

QUESTION: Can someone who STILL has their device encrypted, flashed TWRP Recovery, pushed the root zip and then entered twrp to flash it explain exactly what happens on the screen in TWRP. Does it block the install process completely, ask for a password to decrypt the device before continuing, or not allow you to unlock it?

I just need to know that part to give better instructions for the toolkit rooting operation. Once the device has been decrypted there should be no problems at all but im just not sure whether to encourage the user to run a decrypt procedure first, before the root prodecure starts.

Any feedback would be appreciated.

Mark.

EDIT: I added the option anyway.

 

[m4r0v3r]

anybody know where the sources are for the kernel?

 

[shimp208]

anybody know where the sources are for the kernel?

They will be here https://android.googlesource.com/kernel/msm/ once Google updates a few things other repos for bulkhead such as device tree and more kernel files will be at https://android.googlesource.com under device/lge/bullhead and under device/lge/bullhead-kernel if that's needed. Let me know if you have more questions!