FORUMS
Remove All Ads from XDA

[RECOVERY][pme] TWRP touch recovery

19,647 posts
Thanks Meter: 22,190
 
By Captain_Throwback, Retired Moderator / Recognized Developer / Recognized Contributor on 13th April 2016, 08:50 PM
Post Reply Email Thread
Announcement from Captain_Throwback: Fully Working TWRP for Marshmallow & Nougat now available on twrp.me!
Code:
*** Disclaimer ***

All flashing is done at your own risk!
While nothing from this thread should break your device,
don't come back here blaming anyone if it does!

Introduction
Quote:

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.

Images


Installation instructions
Quote:

NOTE: Read the FAQ from Post #2 to ensure that you're installing the correct version of TWRP!!

TWRP Image Install method:
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 of TWRP appropriate for your device/firmware
  2. Reboot to TWRP
  3. Hit Install and tap the "Install Image" 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

Alternate Installation Method:
Fastboot Install Method:
You will need the platform-tools from the Android SDK on your computer. Find the Android command line tools section on the page linked and install the SDK tools package. From the SDK Manager, download only the platform-tools to get adb and fastboot binaries.

Windows users will need proper drivers installed on their computer. You can try the Naked ADB drivers or the Universal ADB drivers if you don't already have a working driver installed

On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging. From your computer, open a command prompt and type:
Code:
adb reboot download
You should now be in fastboot mode.

Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
Code:
fastboot flash recovery twrp.img
Code:
fastboot reboot

Device Changelog
Quote:

Current version: 3.1.1-0:

Code:
  • Initial official release
Older Device-specific versions:
Code:
  • N/A

TWRP Official Changelog
Quote:

Current version: 3.1.1:

Code:
  • 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)
Older versions:
Code:
3.1.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 (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
3.0.3: 3.0.2:
  • 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.
3.0.1:
  • 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
3.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
Additional Notes
  • 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 updated 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!
2.8.7.0:
  • Initial ground work for software drawn keyboard (_that)
  • Fix handling of wiping internal storage on datamedia devices (xuefer)
  • Allow DataManager to set and read values from the system properties (xuefer)
  • Fix crash when taking screenshots on arm64 devices (xuefer)
  • Fix error message after an ORS script completes (Dees_Troy)
  • Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
  • Add system read only option – more details below (Dees_Troy)
  • Add resize2fs and GUI option to run resize2fs (Dees_Troy)
  • Fix crash loop caused by empty lines in AOSP recovery command file (_that)
  • Prevent duplicate page overlays such as multiple lock screens (mdmower)
Additional Notes
  • Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
  • System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
  • resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
  • This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.

Downloads
Quote:

NOTE: Read the FAQ from Post #2 to ensure that you're installing the correct version of TWRP!!

Download
Latest Official versions

Sources
Device tree
Kernel source


FAQ - Post #2

Known Issues
Quote:

  • None

Bug Reporting
Quote:

If you have an issue, the first step is to post a recovery log so we can determine the cause of the issue. This is done in recovery using Advanced -> Copy Log, or adb pull /tmp/recovery.log. Once a log is uploaded we can determine how best to proceed. NOTE: Posts that are reporting bugs or issues without an accompanying recovery log will be ignored! Additionally, providing details about your device setup, including variant, firmware version, and exact steps to reproduce your issue will also be helpful in diagnosing the problem.


If your issue is determined to be 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 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!

Additional Help/Support:
Quote:

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

XDA:DevDB Information
TeamWin Recovery Project (TWRP), Tool/Utility for the HTC 10

Contributors
Captain_Throwback, nkk71, Dees_Troy, _that, bigbiff
Source Code: https://github.com/omnirom/android_bootable_recovery


Version Information
Status: Stable
Current Stable Version: 3.1.1-0
Stable Release Date: 2017-05-18

Created 2016-04-13
Last Updated 2017-05-19
The Following 110 Users Say Thank You to Captain_Throwback For This Useful Post: [ View ]
 
 
13th April 2016, 08:50 PM |#2  
Captain_Throwback's Avatar
OP Retired Moderator / Recognized Developer / Recognized Contributor
Flag Bensalem, PA
Thanks Meter: 22,190
 
10
Donate to Me
More
Frequently Asked Questions (FAQ)
1. Why is this device different than my previous HTC device?
  • With the 10 (and the M9 and A9 prior to it), HTC has moved to a block-based OTA system. This means that even mounting system as read-write (as TWRP typically does during startup checks) will nullify the device's ability to take an OTA. Any other changes to the system partition will also cause an OTA to fail (even if that check is removed from the OTA zip) due to "unexpected contents." Additionally, see this thread.
2. I decrypted my device and now I don't have signal. Did a TWRP update cause this?
  • No, this is not a TWRP issue. It appears that on the HTC 10, having a decrypted device prevents the SIM card/telephony from initializing, resulting in no mobile signal or data connection. The device comes with forced encryption enabled and currently must remain that way in order for mobile signal/data to work. TWRP does not change or affect any of that.
3. Which version of TWRP am I supposed to use?
  • The best version to use is 3.1.1-0, the latest official TWRP from twrp.me.
4. Why is there a "System" backup option and a "System Image" backup option now?
  • The "System" option is the standard tar backup. "System Image" is a dd backup of the entire system block device (/dev/block/bootdevice/by-name/system). The "System Image" option is only relevant if your system is unmodified. This allows you to make a fully stock backup that can be restored later to take an OTA.
    • NOTE: You only need to choose ONE of these options when making a backup!!
    • NOTE 2: If you are using a FAT32-formatted card, a "System Image" backup may fail (depending on your variant), due to the 4GB file limit on that format. For a successful System Image backup, internal storage or NTFS/exFAT-formatted external storage must be used (either SD card or USB-OTG)
5. How am I supposed to root?
  • Since the 10 has dm-verity enabled and forces encryption by default, root can only be achieved using the new "systemless" root methods. There are three currently working methods:
6. How do I backup stock recovery prior to flashing TWRP?
  • You can't. The "fastboot boot" command appears to be disabled on the 10's ABOOT, so TWRP must be fastboot flashed over stock recovery. You can however, extract the stock recovery.img from the OTA firmware.zip when it's received and use that to install the OTA.
  • An alternate method to obtain a stock recovery is listed below, but it requires 2 devices (either owned by you, or help from someone else in the forum):
    • Someone fastboot flash twrp and immediately make a backup of boot and upload it to XDA.
    • Once the above is available, someone else download that boot.img to their device, and fastboot flash twrp to the BOOT partition of their device.
    • Once the above is done, reboot the device, which will bring up TWRP, and then backup stock RECOVERY in TWRP, and upload to XDA.
    • Then, from within TWRP, use the Image install feature in TWRP to flash the stock boot.img.
7. How do I restore stock system so that I can accept an OTA?
  • Check the "Mount system as read-only" box in the Mount menu.
  • Restore stock "System Image" backup (This will only work if you've made a System Image backup prior to making any modifications to /system).
  • Fastboot flash stock recovery (fastboot flash recovery recovery_signed.img)
    • NOTE: It is also possible to restore stock recovery via the TWRP GUI. Rename the stock recovery file to "recovery.emmc.win" and place in the backup folder with the stock system image. Recovery will then show as a restore option. MAKE SURE YOU REALLY WANT TO DO THIS, AS TWRP WILL BE GONE WHEN YOU REBOOT OUT OF RECOVERY!!
    • NOTE 2: It is possible to install an OTA without using stock recovery (i.e. installing it with TWRP). TWRP will not flash the firmware.zip included in an OTA file. Please see here for a detailed description of the process.
  • Reboot to system, install OTA.
8. What if I have an RUU? Do I need to worry about all this OTA nonsense?
  • Not if you don't care about losing all your data. If you're S-ON and have an RUU available for your exact variant (model ID and CID must match) and software number (main version must be the same or newer), then you can get back to a fully stock state by relocking (fastboot oem lock) and flashing an RUU. However, if you'd prefer to take an OTA to keep your data intact, the method stated above is how to do so. Or, you can just run a custom ROM and wait for your ROM chef to update their ROM to the latest software (though you'll still have to find a way to update your firmware if you're not S-OFF)
9. After I go through all this and successfully apply an OTA, how do I make sure I have a clean starting point again?
  • After the OTA is applied and TWRP is flashed, it will once again detect an untouched system, which will mount system read-only and allow you to make a fully stock backup and start the process over again, this time with the new base.
10. After I restored my Data backup and boot back to Android, I'm entering the correct PIN/password, but it's telling me the password is wrong. What happened, and how do I fix it?
  • It appears that sometimes after restoring a backup of Data where security was enabled (such as a PIN or password lock), the device does not recognize the correct password. There are two ways to avoid this issue:
    • Disable security in Android before making a backup of data.
    • After restoring Data, while still in TWRP, use the TWRP File Manager to navigate to /data/system and delete all the locksettings.* files (such as locksettings.db, etc). When you reboot, the password will be gone.
The Following 54 Users Say Thank You to Captain_Throwback For This Useful Post: [ View ]
13th April 2016, 08:50 PM |#3  
Captain_Throwback's Avatar
OP Retired Moderator / Recognized Developer / Recognized Contributor
Flag Bensalem, PA
Thanks Meter: 22,190
 
10
Donate to Me
More
PSA for Devs regarding mounting system in updater-scripts
In order for ROM zips to function properly, ROM devs may need to change the way they're used to performing mount commands in their updater-scripts. Many ROM devs like to use busybox to mount system, like this:
Code:
run_program("/sbin/busybox", "mount", "/system");
However, on newer HTC devices, this will not always be effective, due to the variable state of system when booting into TWRP (more information in the above post). The most reliable way to mount system in TWRP is to use the below command:
Code:
run_program("/sbin/mount", "-t", "ext4", "/dev/block/bootdevice/by-name/system", "/system");
Since this calls the mount binary and specifies the proper filesystem of /system, it will work regardless of the mount state of /system within TWRP.

The reason people are having issues booting ROMs flashed without the above command is because custom ROMs typically include a command to format system within the updater-script, like this one:
Code:
run_program("/sbin/mke2fs", "-t", "ext4", "-m", "0", "/dev/block/bootdevice/by-name/system");
Notice that this calls the mke2fs binary directly and specifies the filesystem, so this command will run properly and format system. However, when the script attempts to mount system using the busybox mount command, it's unsuccessful, resulting in a failed ROM install (even though there likely isn't an error message) and an empty system partition. The same command format should be used both to format system and to mount it.

So, the solution is easy - replace your busybox mount commands with the direct version noted above. Running it that way should work regardless of the update-binary used, since it's not running mount directly but calling it (this makes a difference to some binaries for some reason). This will even work in situations where system has been mounted read-only by TWRP (more on that in the below post).

ROM Devs - please consider making this change going forward. The above method will ALWAYS WORK. Please use this and discontinue whatever other methods to mount system that you have previously used, as they will have inconsistent results, leading people to flash old versions of TWRP or blame TWRP for their errors.

I know HTC is changing how they do things, and it's different than we're all used to. Let's all adapt to the change together. :).
The Following 31 Users Say Thank You to Captain_Throwback For This Useful Post: [ View ]
13th April 2016, 08:59 PM |#4  
Captain_Throwback's Avatar
OP Retired Moderator / Recognized Developer / Recognized Contributor
Flag Bensalem, PA
Thanks Meter: 22,190
 
10
Donate to Me
More
You may notice that there's no device page for the HTC 10 on the twrp.me site. Well, obviously, that's because the device hasn't been released yet. However, if you happen to have the device already, you may be able to find a TWRP build for it somewhere, if you figure out where to look .

Once the device is released, please be assured that a device page will be created so everyone can easily get to it. Until that happens, I'll be keeping the thread closed. Thanks for your understanding!
The Following 25 Users Say Thank You to Captain_Throwback For This Useful Post: [ View ]
16th April 2016, 04:08 PM |#5  
Captain_Throwback's Avatar
OP Retired Moderator / Recognized Developer / Recognized Contributor
Flag Bensalem, PA
Thanks Meter: 22,190
 
10
Donate to Me
More
Alright, since @topjohnwu was kind enough to post a TWRP backup from his release version device, I'm opening the thread and offering an "unofficial" release on the Downloads tab until I can get the official build working.

Here's a link to the build:
twrp-3.0.2-1-pme - DEPRECATED BY OFFICIAL RELEASE

P.S. If you happen to have the currently elusive Sprint variant of the 10, this version WILL NOT WORK. I do have a working version for Sprint, but I will need to wait for the release software before I post it.
UPDATE: As of the official 3.0.2-2 release, the Sprint variant is supported!
The Following 18 Users Say Thank You to Captain_Throwback For This Useful Post: [ View ]
16th April 2016, 06:54 PM |#6  
Recognized Developer / Recognized Contributor
Flag Taipei
Thanks Meter: 25,985
 
Donate to Me
More
Quote:
Originally Posted by Captain_Throwback

Alright, since @topjohnwu was kind enough to post a TWRP backup from his release version device, I'm opening the thread and offering an "unofficial" release on the Downloads tab until I can get the official build working.

Here's a link to the build:
twrp-3.0.2-1-pme

P.S. If you happen to have the currently elusive Sprint variant of the 10, this version WILL NOT WORK. I do have a working version for Sprint, but I will need to wait for the release software before I post it.

Thanks a lot man. I've got a minor issue here, take a look at the picture, it has a mouse cursor in the center for all time.

Also, would you mind me contact you on hangouts? I am curious about some questions, and I cannot contact using PM.
The Following User Says Thank You to topjohnwu For This Useful Post: [ View ]
16th April 2016, 07:02 PM |#7  
Captain_Throwback's Avatar
OP Retired Moderator / Recognized Developer / Recognized Contributor
Flag Bensalem, PA
Thanks Meter: 22,190
 
10
Donate to Me
More
Quote:
Originally Posted by topjohnwu

Thanks a lot man. I've got a minor issue here, take a look at the picture, it has a mouse cursor in the center for all time.

Also, would you mind me contact you on hangouts? I am curious about some questions, and I cannot contact using PM.


You're just going to have to ignore the mouse cursor for now. I can't get get rid of that without kernel source.

Sure you can contact me on Hangouts. I do prefer PM, though.

P.S. Added mouse cursor issue to current bug list.
The Following User Says Thank You to Captain_Throwback For This Useful Post: [ View ]
16th April 2016, 09:16 PM |#8  
Captain_Throwback's Avatar
OP Retired Moderator / Recognized Developer / Recognized Contributor
Flag Bensalem, PA
Thanks Meter: 22,190
 
10
Donate to Me
More
I'm trying to do some preliminary setup for AOSP encryption support. Can someone with a device please try flashing the 3.0.2-2 version I just posted, and provide the recovery.log afterwards (provided it boots)? I'd really appreciate it. Thanks!
The Following 2 Users Say Thank You to Captain_Throwback For This Useful Post: [ View ]
16th April 2016, 10:09 PM |#9  
Captain_Throwback's Avatar
OP Retired Moderator / Recognized Developer / Recognized Contributor
Flag Bensalem, PA
Thanks Meter: 22,190
 
10
Donate to Me
More
Better yet, if someone can flash this 3.0.2-3 and pull a recovery log, and also post the output of lsmod either from adb shell or the TWRP Terminal, I'd appreciate it. I'm trying to a few things for decryption.
The Following User Says Thank You to Captain_Throwback For This Useful Post: [ View ]
17th April 2016, 04:17 AM |#10  
Recognized Developer / Recognized Contributor
Flag Taipei
Thanks Meter: 25,985
 
Donate to Me
More
@Captain_Throwback
Tried 3.0.2-2 and 3.0.2-3, both cannot boot. Is there a way to pull logs?
17th April 2016, 06:56 AM |#11  
Member
Flag Taipei
Thanks Meter: 52
 
More
Quote:
Originally Posted by Captain_Throwback

Better yet, if someone can flash this 3.0.2-3 and pull a recovery log, and also post the output of lsmod either from adb shell or the TWRP Terminal, I'd appreciate it. I'm trying to a few things for decryption.

Thanks Captain_Throwback .

twrp-3.0.2-2-pme.img & twrp-3.0.2-3-pme.img is work for me . devices TW 1.21.709.2 deodexed
Attached Files
File Type: log recovery_3.0.2-2.log - [Click for QR Code] (17.7 KB, 150 views)
File Type: log recovery_3.0.2-3.log - [Click for QR Code] (18.3 KB, 108 views)
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes