[RECOVERY][angler] TWRP 3.0.2-3 UNOFFICIAL touch recovery [2016-??-??] - Nexus 6P General

Hello folks!
Apparently the official TWRP recovery 3.0.2 has some sort of problems with android 7.1.1 Nougat, so this unofficial recovery was created to work around those issues in the meantime.
The official hosting of this unofficial recovery is in this thread: http://forum.xda-developers.com/nex...recovery-twrp-2-8-7-0-touch-recovery-t3234976
It is buried almost all the way at the end.
For sake of convenience, I am making it available here for those that wish to get going with it quickly. Note that I am not the developer of this nor am I the maintainer. This is here for easy reference only. You should speak with TWRP Grand Poobah Dees_Troy in the above thread for further details.
twrp-3.0.2-3-angler.zip 14.2 MB
https://mega.nz/#!tdcUAa4a!G-bGMWznEUAkE3Ih3ioaHq2Fx0NdzGnIlhY-nuPg__s
Installation instructions are straightforward:
1. Decompress the zip file so you have the .img file. Do not flash the zip file!
2. Place the recovery image in the same folder as your ADB / fastboot apps.
3. Put your phone in boot loader mode: Power button + volume down button.
4. Pull open a console in this directory and type fastboot devices. Proceed when you a serial number and "fastboot" next to it.
5. Type fastboot flash recovery twrp-3.0.2-3-angler.img. If all goes well you should see a success message of some sort.
6. Reboot and enjoy!
I've been using this for a few ROM installs already and haven't seen any problems.
Best of luck to you!

---

Guess I'll give this a go and report back later on heh. Will this recovery actually stay after a restart?
Sent from my Nexus 6P using XDA-Developers mobile app

---

Hmm, seems to be working ok for me on the 7.1.1 DP2 release.
Sent from my Pixel XL using Tapatalk

---

PearsonDKA said:
Guess I'll give this a go and report back later on heh. Will this recovery actually stay after a restart?
Click to expand...
Click to collapse
Like some others have mentioned, I keep seeing it disappear after restarting the phone once, twice or a few times, so I have to re-flash it almost every time I need it.
Not sure what the hangup is. Size-related?

---

CaptShaft said:
Like some others have mentioned, I keep seeing it disappear after restarting the phone once, twice or a few times, so I have to re-flash it almost every time I need it.
Not sure what the hangup is. Size-related?
Click to expand...
Click to collapse
You need to flash either Root or a modified boot image for it to stay

---

jaytv said:
You need to flash either Root or a modified boot image for it to stay
Click to expand...
Click to collapse
Good to know. 2 questions:
1) What modifications to a regular boot image do we need to make to keep it?
2) Are all boot images the same? Can we all use the same modified boot image or does it differ depending on the ROM?

---

CaptShaft said:
Good to know. 2 questions:
1) What modifications to a regular boot image do we need to make to keep it?
2) Are all boot images the same? Can we all use the same modified boot image or does it differ depending on the ROM?
Click to expand...
Click to collapse
Sounds like time for you to do some reading as to what root and boot images are. Search works great. I suggest the threads on SuperSU (a form of root) and also looking at the many wonderful custom boot images and Roms that are floating around in this forum.
The simple answer is flash Super Su or find a modified boot image for the current release and flash that.
Also, Heisenberg's excellent beginner's thread in Nexus 6p general is a great place to start.
Enjoy!

---

Just what I was looking for.
I was in TWRP loop forever and couldn't figure it out till this thread. No issues now

---

I've installed the one from the main thread and it's working for me.
I just wanted to mention what the bugs are:
shadowstep said:
TWRP versions 3.0.2-1 and above work with Android Nougat 7.0's encryption, TWRP 3.0.2-0 and below don't. Also, both versions 3.0.2-1 and 3.0.2-2 are buggy at the moment, but none of those bugs are along the lines of encryption. Read the end of this post for more information.
(Replies snipped)
EFS partition is never needed to be restored under any general circumstance. It is the partition where the phone stores its IMEI information, MAC address, product code, etc. and will never be needed to be modified or changed in any way. Even if you're flashing a stock factory image (be it of 6.0.1 or 7.0, whenever it is out), it would never touch this partition. You should just backup it once, store it away for emergency purposes and never backup or restore it again.
Okay now moving onto important notes and the bugs:
1. TWRP 3.0.2-0: Is stable and has no known bugs. However, it has not been updated to handle Android Nougat 7.0's encryption. Hence, if you're on 7.0 and you're encrypted, it will keep asking for an encryption password even if you don't have one or if you have one and are inputting it correctly, it will refuse to accept it. If you're on 7.0 and you're unencrypted, then this version should be fine.
2. TWRP 3.0.2-1: Is not stable and has a known bug. The bug would affect those who are restoring their EFS partition using this version of TWRP. The EFS partition has two subparts to it, i.e. /efs1 and /efs2. So, when you check EFS at the backup option menu in TWRP, it backups /efs1 to efs1.emmc.win and /efs2 to efs2.emmc.win, which is fine. However, while restoring (and here is when the bug comes in), it restores efs1.emmc.win to /efs1 but restores the same backup of efs1.emmc.win to /efs2 as well (which it shouldn't be doing and instead it should be restoring the corresponding efs2emmc.win to /efs2). This can brick your phone. Hence, the fatal bug.
This version, however, supports Android Nougat 7.0's encryption. Therefore, as long as you don't backup/restore EFS with this version, you should be good using it with either Android Marshmallow 6.0.1 or Android Nougat 7.0, encrypted or unencrypted.
3. TWRP 3.0.2-2: Is not stable and has a known bug (with the EFS bug most likely fixed in this version, but this is unconfirmed since there is no changelog available yet). The bug would affect those who are backing up their data using this version. TWRP creates the backups of your selected partitions as tar files. The bug that is present in this version would give you an error (most likely the one that @stankyou got) as it is unable to write the second tar file after processing approximately 1 GB of data and would cancel the backup. Hence, the bug.
This version, however, also supports Android Nougat 7.0's encryption. Therefore, as long as you don't create backups with this version, you should be good using it with either Android Marshmallow 6.0.1 or Android Nougat 7.0, encrypted or unencrypted.
4. @jcadduono has created unofficial builds (versions 3.0.2-3) for the Nexus 6P (Angler) and Nexus 5X (Bullhead) without the broken patches. They are up-to-date, but have the adb backup patches rebased out until the bugs are solved. These builds are untested, and he recommends sticking with 3.0.2-0 instead for the time being.
Click to expand...
Click to collapse
TL;DR 3.0.2-0 doesn't support Nougat encryption. 3.0.2-1 has bug restoring EFS. 3.0.2-2 has bug creating backups over 1GB.

---

ADB sideload is not working in TWRP 3.0.2-3 (twrp-3.0.2-3-angler.img - MD5 2fcc19da388ab727aac69b6165ac7888), not sure if this is @jcadduono or not. It's working in previous build IIRC. Is this expected? Thank you.

---

vibranze said:
ADB sideload is not working in TWRP 3.0.2-3 (twrp-3.0.2-3-angler.img - MD5 2fcc19da388ab727aac69b6165ac7888), not sure if this is @jcadduono or not. It's working in previous build IIRC. Is this expected? Thank you.
Click to expand...
Click to collapse
I had a few failures with it in TWRP, yes.
Until fixed, you'll have to do ADB push instead and then load from TWRP install.
Alternately, you can do fastboot flash commands while in the bootloader.

---

Grospolina said:
I've installed the one from the main thread and it's working for me.
I just wanted to mention what the bugs are:
TL;DR 3.0.2-0 doesn't support Nougat encryption. 3.0.2-1 has bug restoring EFS. 3.0.2-2 has bug creating backups over 1GB.
Click to expand...
Click to collapse
I noticed that bug yesterday restoring a backup. TWRP appeared to hang whilst restoring, I left it a further five minutes, then hard reset the power button. When the phone loaded up, I found it had restored correctly.

---

3.0.2-4 twrp ?
Anybody have the capabilities to roll the 3.0.2-3 version in with The Flash's 3.0.2-0_F2FS version lol; and make a version compatible with Nougat encryption as well as F2FS (and without EMS restore problem, nor backup error issue) ?
I know I sure don't, and now that I'm on christmas break I am just sitting around - in fact if anybody could point me to a resource, I have the time and I'm sure I could pick it up quick, I could try and compile it! I've been wanting to give back to this great community since I joined; maybe now that I've done a couple years of engineering school and been searching thru the forums, I can help throw this together.
I'm going to assume that I look up those two builds sources on GitHub, then use Parallels Windows to use a Linux distro (because I'm on a Macbook Pro) to combine the sources and make a build? Honestly, if I could get any advice, I'd love to jump on it.

---

3.0.3.0 is out. Anyone know the changelog ?

---

Here's the link: https://dl.twrp.me/angler/twrp-3.0.3-0-angler.img.html
Would be nice to know a changelog

---

ariefabuzaky said:
3.0.3.0 is out. Anyone know the changelog ?
Click to expand...
Click to collapse
Unfortunately, the answer is here. I did not expect to see a nag screen after making a backup!

---

bkkzak said:
Here's the link: https://dl.twrp.me/angler/twrp-3.0.3-0-angler.img.html
Would be nice to know a changelog
Click to expand...
Click to collapse
You can always look at their repository
Since 2016-09-01:
- Change version to 3.0.3 to support the app release - 27 hours ago
- Update Ukraine language translation (via jemmini) - 27 hours ago
- Add TWRP app install via TWRP recovery - 29 hours ago
- TWRP Language Update - 7 days ago
- Change handling of /cache due to AB devices not having cache - 7 days ago
- Support backup/restore of FBE policies - 8 days ago
- Support File Based Encryption - 10 days ago
- Add boot slot support - 12 days ago
- Support new AB OTA zips - 12 days ago
- Copy Kernel Logs - 5 months ago
- Improve backup & wipe exclusion handling - 2 weeks ago
- Fix adb shell in 7.0 tree - 6 weeks ago
- Check if mount point is dir during startup - 6 weeks ago
- MD5 verification sanity - 8 weeks ago
- Fix image flashing: attempt 2 - 8 weeks ago
- Fix image flashing - 3 months ago
- Update to android-7.1 - 4 weeks ago
- Fix libcrypto dependency in 6.0 trees - 3 months ago
- Clean up PartitionSettings - 3 months ago
- Fix compressed backups with split archives - 3 months ago
- Fix restore of subpartitions - 4 months ago

---

Unfortunately for me, I still have issues decrypting an encrypted phone on TWRP 3.0.2-3 and 3.0.3-0. TWRP prompts for a password and won't take my PIN.
Running the latest ResurrectionRemix (CM-based), which enables device encryption. I'm still searching around to see what I need to do about this.
Edit: Update: Huh, weird, got it to mount.
I rebooted back into Android, went in to Security and set a device encryption password with "Change encryption password".
I hadn't set one before. It requests my screen lock PIN then to enter an alphanumeric encryption password.
Attempted to remove it again immediately (it doesn't show any feedback when I tap "Replace encryption password" then enter my screen lock PIN), and rebooted into recovery.
TWRP prompted again for an encryption password but now accepts my device lock PIN and it mounts!
Rebooted again, and now the phone requests a PIN unlock during boot >.<
Went back in to Security and went straight to "Replace encryption password", entered my PIN, and saw no feedback again. Rebooted back into Recovery.
TWRP prompts again but accepts my PIN. Rebooting to Android again, I am prompted again on boot to enter my screen PIN to finish the boot process. Sooo now I guess I have to figure out how to disable the device encryption PIN, or something. Oh well. I'll update if I make progress.
The end goal is to reach a point where TWRP will mount (even if it's manually with an entered PIN), and to not have a phone that requires a PIN unlock during boot. But I guess that's still safer and I can live with it. It's just different from how the ROM originally behaved, is all.
Edit: Update again!
Disabled my PIN/security altogether, rebooted into recovery. TWRP mounts without any prompts. Nice. Reboot int system, it boots fine. Also nice.
Set a new screen lock PIN, do not select to use it on bootup, and set my fingerprints again. Apps work immediately fine after, I did not have to reset them to use that auth method. Woot, nice.
Restart into TWRP, no prompt, good. Restart into System again, no prompt during boot.
So I guess in the end you have to disable and re-enable device screen locking security if you hit this issue in TWRP on a 6P? It could be my ROM as well.

---

CaptShaft said:
Hello folks!
Apparently the official TWRP recovery 3.0.2 has some sort of problems with android 7.1.1 Nougat, so this unofficial recovery was created to work around those issues in the meantime.
The official hosting of this unofficial recovery is in this thread: http://forum.xda-developers.com/nex...recovery-twrp-2-8-7-0-touch-recovery-t3234976
It is buried almost all the way at the end.
For sake of convenience, I am making it available here for those that wish to get going with it quickly. Note that I am not the developer of this nor am I the maintainer. This is here for easy reference only. You should speak with TWRP Grand Poobah Dees_Troy in the above thread for further details.
twrp-3.0.2-3-angler.zip 14.2 MB
https://mega.nz/#!tdcUAa4a!G-bGMWznEUAkE3Ih3ioaHq2Fx0NdzGnIlhY-nuPg__s
Installation instructions are straightforward:
1. Decompress the zip file so you have the .img file. Do not flash the zip file!
2. Place the recovery image in the same folder as your ADB / fastboot apps.
3. Put your phone in boot loader mode: Power button + volume down button.
4. Pull open a console in this directory and type fastboot devices. Proceed when you a serial number and "fastboot" next to it.
5. Type fastboot flash recovery twrp-3.0.2-3-angler.img. If all goes well you should see a success message of some sort.
6. Reboot and enjoy!
I've been using this for a few ROM installs already and haven't seen any problems.
Best of luck to you!
Click to expand...
Click to collapse
tu 2: is that recovery image the same as under point one? and where is the ADB /fastbootfolder? these not exist