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.
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
Dees_Troy said:
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.
Click to expand...
Click to collapse
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.
From what I put together TWRP requires unencrypted kernel/boot. Not to fear though. Looks like chainfire had released an unencrypted kernel/boot - http://forum.xda-developers.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.
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
0.0 said:
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
Click to expand...
Click to collapse
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.
Awesome ! Was waiting for this ! Will flash in an hour And report back !
EDIT: Works Great !
So would I be good to go to install twrp after unlocking bootloader on the 5x?
briant1234 said:
So would I be good to go to install twrp after unlocking bootloader on the 5x?
Click to expand...
Click to collapse
No, this will screw up your device. http://www.xda-developers.com/a-look-at-marshmallow-root-verity-complications/
aes512 said:
No, this will screw up your device. http://www.xda-developers.com/a-look-at-marshmallow-root-verity-complications/
Click to expand...
Click to collapse
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?
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.
Hayth said:
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.
Click to expand...
Click to collapse
I noticed that @mskip has this mda89e modified image mentioned in this post: http://forum.xda-developers.com/showpost.php?p=63422766&postcount=17
PS: I've not ordered any new phone (yet) but am following things here anyway.
Hayth said:
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.
Click to expand...
Click to collapse
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.
Pbrah said:
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?
Click to expand...
Click to collapse
It will put the phone in boot loop is why.
In other news: http://forum.xda-developers.com/showpost.php?p=63426368&postcount=11
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
suhail_kapoor said:
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
Click to expand...
Click to collapse
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.
hachamacha said:
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.
Click to expand...
Click to collapse
many thanks mate that worked flawlessly, managed to recover device and so far installed chainfire's boot.img and twrp. on to rooting now.
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.
anybody know where the sources are for the kernel?
m4r0v3r said:
anybody know where the sources are for the kernel?
Click to expand...
Click to collapse
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!
Related
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.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!
CHANGELOG for 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)
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.
DOWNLOAD:
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 NEW website! NOTE that the 2.8.6.0 version is ONLY available on our new site and is not available on our other, older mirrors!
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 said:
Thanks to Dr_Drache for testing for me!
Team Win Recovery Project 2.3, 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.3.2.0:
-Fixes / enhancements to handle the multiple user setup introduced by Android 4.2 (see notes)
-Fixed a bug with deleting a backup with a space in the name
-Added highlights on keyboard key presses
CHANGELOG for 2.3.1.0:
-Unmount system after boot to prevent some status 7 symlink failed errors on zip install
-USB Mass Storage code improvements
-Better handling of mounting storage during boot for some devices
-Fixed a problem with sizes of images (boot & recovery) after resetting defaults
-Fixed size errors during backup for some devices on recovery, etc.
-Fixed a problem with restoring backups when multiple archives were present
CHANGELOG for 2.3.0.0:
-Rebased onto AOSP Jelly Bean source code
-Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
-ADB sideload functionality from AOSP is included in 2.3, see this link for more info
-Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
-Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
-Faster boot times
-Added charging indicator while in recovery (only updates once every 60 seconds)
While this update may not bring a host of new must-have features, this update is a significant re-write of much of the core TWRP code. AOSP Jelly Bean recovery source moved to mostly C++ code and now all of the "TWRP" code is fully rewritten into C++ as well. Now that we've laid this groundwork, we're in a much better position to pull in future AOSP recovery updates as well as implementing more great new features.
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
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 30 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.
Click to expand...
Click to collapse
Sweet thanks.
Sent from my CM9 HTC Thunderbolt from Tapatalk 2.4
Note, I forgot to have Dr_Drache test off-mode charging. Can someone install this, turn the device completely off, then plug it into a charger. The charge light should come on, maybe blink once or twice, but after about 2 minutes, the charge light should stay on without blinking anymore. Please let me know!
jonah1234 said:
Sweet thanks.
Sent from my CM9 HTC Thunderbolt from Tapatalk 2.4
Click to expand...
Click to collapse
THANK YOU
Dees_Troy said:
Note, I forgot to have Dr_Drache test off-mode charging. Can someone install this, turn the device completely off, then plug it into a charger. The charge light should come on, maybe blink once or twice, but after about 2 minutes, the charge light should stay on without blinking anymore. Please let me know!
Click to expand...
Click to collapse
Off mode charging is fine
Sent from my ADR6425LVW using Tapatalk 2
vinylfreak89 said:
Off mode charging is fine
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Good deal, thanks for checking it and confirming.
I've ran into some trouble with mine. I have created three backups, each with slight differences to system, trying some things out on the ROM. The lase edit was the build.prop. It wouldn't boot so I went to Recovery to restore one of my backups. When it is a good 10 seconds into restoring system, the progress bar stops turning and it reboots. Each time I try this it seems to stop at a slightly different point into the system restore. Most of the time it wont go far enough to allow boot, just the splash screen and then it automatically boots into TWRP.
All of that is ok, and I could get around it, but now my phone is dead! Any suggestions?
*Edit* Got it guys. I was able to use the USB charger from my TPrime and it charged in TWRP. After it charged a bit I was able to fastboot flash TWRP again and restore one of the backups. I'm not sure how it became corrupted, but its all good now!
When will the size be fixed?
Sent from my HTC Droid DNA
jonah1234 said:
When will the size be fixed?
Sent from my HTC Droid DNA
Click to expand...
Click to collapse
I don't have a DNA or any other 1080 * 1920 device that uses a portrait layout (no rotation in recovery). I am unable to do the upscale myself. There's a theme guide on our website if someone wants to to do it.
Dees_Troy said:
I don't have a DNA or any other 1080 * 1920 device that uses a portrait layout (no rotation in recovery). I am unable to do the upscale myself. There's a theme guide on our website if someone wants to to do it.
Click to expand...
Click to collapse
Alright I will give that a try later today.
Sent from my HTC Droid DNA
For some reason I can't make backups anymore. It gets about a quarter way, then reboots. I tried cwm..and same issue. Anyone have any ideas?
it has rebooted on me during a backup as well. i tried again and was successful, but there definitely seems to be a bug somewhere
Hello,
Definitely a bug, seems that after the first successful backup unit will no longer get past the system file.
UPDATE, your backups will complete if you do not change the name. Leave it as the date or default name If this does not work for you the only other thing I have done since it was rebooting was to install/update busybox. This may also work for those who are restoring backups and getting the reboot...did you change the file name? Whatever I am sure it is just a temp bug that will be fixed soon as well as the layout.
Cheers
Has anyone got a fix for the screen size yet?
starscream86 said:
Has anyone got a fix for the screen size yet?
Click to expand...
Click to collapse
I was looking into it ealier today. I haven't gotten it just yet tho.
Sent from my HTC Droid DNA
jschill31 said:
Hello,
Definitely a bug, seems that after the first successful backup unit will no longer get past the system file.
UPDATE, your backups will complete if you do not change the name. Leave it as the date or default name If this does not work for you the only other thing I have done since it was rebooting was to install/update busybox. This may also work for those who are restoring backups and getting the reboot...did you change the file name? Whatever I am sure it is just a temp bug that will be fixed soon as well as the layout.
Cheers
Click to expand...
Click to collapse
I have backups failing when not changing the name as well. Bug happens either way.
After several attempts I am eventually able to get a good backup, but it fails more often than it completes.
Deuces said:
I have backups failing when not changing the name as well. Bug happens either way.
After several attempts I am eventually able to get a good backup, but it fails more often than it completes.
Click to expand...
Click to collapse
Interesting, obviously this needs a bit of work. I have not tried to make another one, I have been spending time modding the factory shipped rom. There are so many features hidden by Verizon. Also there is something running in the background that eats our batteries. Hard to start cranking on a rom without a reliable recovery. I sent a note over on the TWRP website, hopefully someone will have some ideas. On the size issue has anyone tried using a TWRP skin from one of the 1080p tablets?
Cheers
Have you looked into using one of the 1080p tablet themes? I plan on doing that tonight.
Sent from my HTC6435LVW using Tapatalk 2
jschill31 said:
Have you looked into using one of the 1080p tablet themes? I plan on doing that tonight.
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
Any luck with that?
starscream86 said:
Any luck with that?
Click to expand...
Click to collapse
Hello,
Actually a big NO on that...this recovery isn't even recognizing the THEME folder? It seems this has a few bugs to iron out. I looked at pulling the resource the other day and building a new one but I can't seem to find a reliable git for the DNA? If anyone knows of one please let me know and I will pull the files late tonight. I am not a DEV by all means but have been building for multiple devices for over two years and have a smoking build machine. I am not comfortable working on any roms until we have a solid recovery. Don't get me wrong, this does backup after a few tries but what I am worried about is a fail when trying to restore. I have read where Clockwork it the same way, seems to have something to do with the partitions?
Cheers
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.
Kernel source for Bricked kernel being used in TWRP is here:
https://github.com/showp1984/bricked-mako/tree/twrp_recovery
Has built-in thermal management to help prevent CPU overheat.
Hell yes. I'll flash this and report back. Love some TWRP.
DARKSIDE
Wicked! Been waiting for this!
Just flashed and it won't boot to it. Just reboots the device :s
Tried flashing with goo manager and bit wouldn't stick.
Transmitted from my GALAXYSIII running Jelly Bean. XDA premium
benjamin.j.goodwin said:
Wicked! Been waiting for this!
Just flashed and it won't boot to it. Just reboots the device :s
Click to expand...
Click to collapse
Same here, tried both goomanager and fastboot method
Tried to install it from goomanager and now I can't boot into recovery. also, when I used rom toolbox to boot into recovery, i got force closes from gapps and a few others. Weird behavior. Any idea where I should start looking?
I've been using TWRP since the beginning of time and absolutely love it! I guess my last excuse for not rooting has finally been put to rest
Sent from my Nexus 4
enserio said:
Tried to install it from goomanager and now I can't boot into recovery. also, when I used rom toolbox to boot into recovery, i got force closes from gapps and a few others. Weird behavior. Any idea where I should start looking?
Click to expand...
Click to collapse
Download the image and flash it through fastboot. It's the safest way to do it.
Sent from my Nexus 4 using XDA Premium HD app
dots in IRC tested and confirmed that the latest build flashes and boots fine. Sorry for any inconvenience.
Dees_Troy said:
Can someone try this when they get a chance?
http://techerrata.com/dees_troy/mako.img
See if it will flash and stick with fastboot flash recovery mako.img
Let me know. Can also get on IRC and try to catch me there.
#twrp on Freenode with your IRC client or just click this link.
Click to expand...
Click to collapse
Confirmed the TWRP you posted mako.img boots up
cwm sticks but this will not. makes me very sad. i love twrp and not so much cwm recovery. also getting gapps (calendar storage etc. force closes when attempting to boot to recovery via goomanager. If anyone can get it to stick please post here how you accomplished please.
Dees_Troy said:
Can someone try this when they get a chance?
http://techerrata.com/dees_troy/mako.img
See if it will flash and stick with fastboot flash recovery mako.img
Let me know. Can also get on IRC and try to catch me there.
#twrp on Freenode with your IRC client or just click this link.
Click to expand...
Click to collapse
I can confirm that this worked for me. I wiped caches, rebooted, then manually went back into recovery just to make sure it stuck. Thank you mucho.
n82k said:
cwm sticks but this will not. makes me very sad. i love twrp and not so much cwm recovery. also getting gapps (calendar storage etc. force closes when attempting to boot to recovery via goomanager. If anyone can get it to stick please post here how you accomplished please.
Click to expand...
Click to collapse
I did as the man said and flashed through fastboot. Like you, I get the gapps fc when I try to boot in recovery via goomanager or rom toolbox. Kinda weird, and I'd like to get rid of it. Pretty sure it's not a part of flashing this recovery, though. Gotta be in how we rooted and flashed recovery the first time.
n82k said:
cwm sticks but this will not. makes me very sad. i love twrp and not so much cwm recovery. also getting gapps (calendar storage etc. force closes when attempting to boot to recovery via goomanager. If anyone can get it to stick please post here how you accomplished please.
Click to expand...
Click to collapse
Try the one he just posted 2 posts back. It boots up fine
The version in GooManager should now flash and boot just fine too.
Dees_Troy said:
The version in GooManager should now flash and boot just fine too.
Click to expand...
Click to collapse
confirmed!!
Sent from my Nexus 4 through Tapatalk
Dees_Troy said:
The version in GooManager should now flash and boot just fine too.
Click to expand...
Click to collapse
Worked fine for me too. I had cwm installed first through the toolkit for what its worth...
Sent from my Nexus 4
Flashed through goo manager app and it booted fine.
Sent from my Nexus 4 using Tapatalk 2
<3
Great job ! Installed smoothly via Goomanager and also sticks and works properly, haven't had this recovery before but looks promising !
For sure gonna give it a good try after CWM and 4EXT and feel the differences !
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.
The theme is a bit undersized. We're using the 1200x1920 theme that's also used on the Nexus 7 2013. At this point we do not feel that it's worth the effort to maintain a stock TWRP theme for 1536x2048 unless more devices pop up using this resolution.
At least running the stock ROM from Google, the Nexus 9 is *ALWAYS* encrypted even if you did not set up encryption. It uses "default_password" as the default password. TWRP can decrypt this and will do so automatically if the default_password is in use.
If you have not unlocked your bootloader, you will need to do so. Hold volume up and down while turning the device on. You will be in the bootloader. Do a "fastboot oem unlock" followed by a "fastboot reboot" from your computer to unlock. This will wipe all of your data including internal storage so back up anything you might want first. If you do not fastboot reboot before installing TWRP, you will probably have to perform a "Format Data" from within TWRP. It is highly recommended that you let the device boot normally immediately after doing the fastboot oem unlock and wait to install TWRP after the first successful boot after the unlock.
Device specific page on our website.
Download link for current and past versions.
Yeeeessss!
Getting this going right now.
Nice work !!
Yay!!!! Thank you so much!!
The app crashes when i select the divice i want to use.
Got it up and running fine. Looks good. Didn't do much, just flashed a different system font but that worked.
The TWRP application from the Play Store didn't work at all, just crash after crash. So just installed the recovery.img with fastboot and everything is fine.
Great to see this!
Question, I read on g+ that decryption is causing issues with making backups other than a raw data image (much lager than a .tar or .win as you use) so this does work now? Also you noted that adb sideload and USB OTG were the only ways to flash a new ROM, is this still the case or will we be able to flash from internal data?
Maybe the best thing for me to do is just flash and find all this out....
Thanks for the great work once again!
Wohooooo . Awesome.
demkantor said:
Great to see this!
Question, I read on g+ that decryption is causing issues with making backups other than a raw data image (much lager than a .tar or .win as you use) so this does work now? Also you noted that adb sideload and USB OTG were the only ways to flash a new ROM, is this still the case or will we be able to flash from internal data?
Maybe the best thing for me to do is just flash and find all this out....
Thanks for the great work once again!
Click to expand...
Click to collapse
As noted in the second post, decrypt of the data partition is working properly on the Nexus 9. I waited to do this release until I got the data decrypt working so none of those issues apply anymore.
Excellent. Making a backup now.
Anyone else having the twrp manager app crashing on you when installing recovery?
jd1639 said:
Anyone else having the twrp manager app crashing on you when installing recovery?
Click to expand...
Click to collapse
I flashed the .img file via fastboot with no issues. Generally it is the safest way to go. Some one reported earlier the TWRP app was not working properly.
Well, let the easy flashing and backuping begin Thanks!
nrage23 said:
I flashed the .img file via fastboot with no issues. Generally it is the safest way to go. Some one reported earlier the TWRP app was not working properly.
Click to expand...
Click to collapse
I'd the image up on team win?
Sent from my Nexus 5 using XDA Free mobile app
nrage23 said:
I flashed the .img file via fastboot with no issues. Generally it is the safest way to go. Some one reported earlier the TWRP app was not working properly.
Click to expand...
Click to collapse
What about flashify ?
---------- Post added at 06:44 PM ---------- Previous post was at 06:44 PM ----------
pantmunu said:
What about flashify ?
Click to expand...
Click to collapse
I will actually give it a shot myself when i get home .
jd1639 said:
I'd the image up on team win?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Yes you can download the img file from their website.
nrage23 said:
Yes you can download the img file from their website.
Click to expand...
Click to collapse
Thanks, I found it
Sent from my Nexus 5 using XDA Free mobile app
Cheers!!
pantmunu said:
What about flashify ?
---------- Post added at 06:44 PM ---------- Previous post was at 06:44 PM ----------
I will actually give it a shot myself when i get home .
Click to expand...
Click to collapse
Flashing isn't working, it can't find the boot partition. I think it's probably because of the encryption
Sent from my Nexus 9 using XDA Free mobile app
[RECOVERY] [4/5/16] TWRP 3.2.1-0 - TeamWin Recovery Project
TeamWin is proud to present TWRP 3.2.1-0 for the Samsung Galaxy Note 5 (GSM)!
Youtube video: http://www.youtube.com/watch?v=RIvWVS_Rkxo
Full TeamWin credits are on the TWRP page on the TeamWin website: http://teamw.in/project/twrp2
Introduction:
Team Win Recovery Project or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. 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.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
See changelog below for new features
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe cache & dalvik, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/omnirom/android_bootable_recovery
Gerrit for TWRP Official Device Configs - http://gerrit.twrp.me
Gerrit Instance - http://gerrit.omnirom.org
If you have made your own twrp build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
noblelte Device Config: https://github.com/TeamWin/android_device_samsung_noblelte
Kernel: https://github.com/TeamWin/android_kernel_samsung_noblelte
DOWNLOAD:
All official devices are listed at the top of the page on the Team Win website. Search for the device in the textbox.
http://twrp.me
Support:
Click http://webchat.freenode.net/?channels=twrp for live support or join us in #twrp on Freenode IRC servers
Changelog
Please see https://twrp.me for release notes.
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.
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
TWRP 3.0.0-0 is out now for all currently supported devices.
What’s new in 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!
You can track the progress of builds here
Head over to the devices page to find install instructions and download links.
TWRP 3.0.0-0 is out now for all currently supported devices.
What’s new in 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!
You can track the progress of builds here
Head over to the devices page to find install instructions and download links.
2.8.7.1
- fix OTG
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)
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.
Known working:
SM-N920T - note 5 tmobile
SM-G928G - s6 edge +
bigbiff said:
Known working on Tmobile Note 5 so far.
Click to expand...
Click to collapse
AWESOME - will be flashing soon - thanks - as always for your work - it is greatly appreciated!
Flashed and booted successfully into recovery -but saw somethnig I have never seen before -
System partitian unmodivied twrp can leave your system partitian unmodified to make it easier for you to take official updates. Twrp will be unable to prevent stock rom from replacing twrp and will not offer to root your device.
Swipe to allow modification...
I assume this means if I select allow modification - it will flash as normal but then would not allow official updates - is that correct?
ALso - OTG is not currently working - hoping this will be taken care of sometime in the future?
I have never seen this before and wondered what the ramifications of this are?
I had problem installing this through ODIN using img.tar.md5, it would failed to download to device and the device would not boot system/receovery , I had to download the img file and flash it using flashify since CWM doesn't do img flashing. Will there be zip file available in near future? Other than that, so far so good everything is working as usual!
Crushader said:
I had problem installing this through ODIN using img.tar.md5, it would failed to download to device and the device would not boot system/receovery , I had to download the img file and flash it using flashify since CWM doesn't do img flashing. Will there be zip file available in near future? Other than that, so far so good everything is working as usual!
Click to expand...
Click to collapse
When I flashed the TWRP Tar in Odin - it flashed and then seemed to hangup at the end when it was clearly finished flashing - it just sat there for a while - maybe 20 seconds - but then it completed the flash and booted immediately into TWRP when I saw the initial warning/tip I mentioned in my previous post - but it did complete the flash from ODIN it just took longer than usual.
mocsab said:
When I flashed the TWRP Tar in Odin - it flashed and then seemed to hangup at the end when it was clearly finished flashing - it just sat there for a while - maybe 20 seconds - but then it completed the flash and booted immediately into TWRP when I saw the initial warning/tip I mentioned in my previous post - but it did complete the flash from ODIN it just took longer than usual.
Click to expand...
Click to collapse
Mine just flashed and then it failed right away and download mode stays on, tried to reboot to recovery to test but it have me an error something about update system failed, try to restore from smart switch on PC. Sop I had to go back to arter's custom CWM from ODIN and then the phone boots up again. Lucky that Flashify managed to flash TWRP img file and everything is working. My model is N920I.
GSM means international lte version ? like n920C ?
mocsab said:
AWESOME - will be flashing soon - thanks - as always for your work - it is greatly appreciated!
Flashed and booted successfully into recovery -but saw somethnig I have never seen before -
System partitian unmodivied twrp can leave your system partitian unmodified to make it easier for you to take official updates. Twrp will be unable to prevent stock rom from replacing twrp and will not offer to root your device.
Swipe to allow modification...
I assume this means if I select allow modification - it will flash as normal but then would not allow official updates - is that correct?
ALso - OTG is not currently working - hoping this will be taken care of sometime in the future?
I have never seen this before and wondered what the ramifications of this are?
Click to expand...
Click to collapse
I will look at enabling OTG soon. 5.1.1 on all phones introduced dm-verity on the system partition. If it gets modified, OEM updates are disabled, and the OEM kernel will fail to boot. If you want to keep completely stock, you need to keep the system r/o
Flashing custom roms/kernels with this turned off will make it so you can have it r/w. R/O will backup the entire system as an image using dd.
bigbiff said:
I will look at enabling OTG soon.
Click to expand...
Click to collapse
awesome - if you need help testing it (I helped you with that on the S6) just let me know
AlMaghraby said:
GSM means international lte version ? like n920C ?
Click to expand...
Click to collapse
All GSM versions should potentially work.
re: TWRP 2.8.7.3
bigbiff said:
Known working on Tmobile Note 5 so far.
Click to expand...
Click to collapse
Just thought to let you know that the "twrp-2.8.7.3-noblelte.img" also works
100% (except for OTG) on my G928T S6 Edge+ phone.
On twrp itself you forgot to change the version number from 2.8.7.0 to 2.8.7.3
When I go into twrp recovery the version still says 2.8.7.0 but it's only cosmetic.
Thanks for all your work!
Can someone test http://build.twrp.me/twrp/twrp-2.8.7.1-noblelte.img.tar for OTG please?
I left my darn OTG at home and cant test until after work - if no one else does, I will try i tthen and will report back. Thanks BigBiff - really appreciate your work!
works on n920c thanks however the odin flashable tar didn't work I made my own tar file without the cach ims don't know why
bigbiff said:
Can someone test http://build.twrp.me/twrp/twrp-2.8.7.1-noblelte.img.tar for OTG please?
Click to expand...
Click to collapse
Installed - but won't recognized OTG when I try to mount in TWRP - I seem to recall you needed the DSMEG after attempting to put the OTG in - but I don't remember how to get the DMSEG - any help is appreciated and I will post the log after I return - assuming I get instructions on where to get it
thanks
mocsab said:
Installed - but won't recognized OTG when I try to mount in TWRP - I seem to recall you needed the DSMEG after attempting to put the OTG in - but I don't remember how to get the DMSEG - any help is appreciated and I will post the log after I return - assuming I get instructions on where to get it
thanks
Click to expand...
Click to collapse
adb shell dmesg > /sdcard/dmesg.txt
AlMaghraby said:
works on n920c thanks however the odin flashable tar didn't work I made my own tar file without the cach ims don't know why
Click to expand...
Click to collapse
Hm, how did you make the tar, just removed the cache.img?
I flashed this using flashfire beta app... installed the .tar file using the firmware flash function in flashfire.
This worked well... only thing I noticed was it shows as v2.8.7.0 but the download link shows as v2.8.7.3
Not sure which it is supposed to be, but either way, it did install.
Thanks. I don't yet have an otg, or else I would be willing to test that feature for you.
bigbiff said:
adb shell dmesg > /sdcard/dmesg.txt
Click to expand...
Click to collapse
I had to install SDK Tools - and Java - once installed I confirmed device is connected - went to recovery and tried to connect OTG - immediately after I attempted the commands you gave in Terminal on my computer and I got a message saying could not find the path specfied - I know I am doing something wrong but can't figure out what?
I did try using the Terminal in TWRP - and did a command for dmesg and when I checked in my sd card after booting - I found there was a file there - it is called dmsesg but I don't know if it is what you are looking for - (Even a broken clock is corect twice day) hope this is what you needed...
OFFICAL TWRP RELEASED, this thread is no longer active. 3-30-2018
https://twrp.me/motorola/motorolamotox4.html
---
UNOFFICIAL BUILDS -- USE AT YOUR OWN RISK AND KNOW HOW TO GET YOURSELF OUT OF TROUBLE IF IT ARISES. I ASSUME NO RESPONSIBILITY FOR YOUR BROKEN THINGS.
UPDATED 01-11-2018
There are now 7.1 based and 8.0 based builds. Obviously, be careful to select the proper download. While I don't think flashing/booting the wrong one would permanently brick the device, let's not find out
For now I will not be attempting to make data decryption work. It is REQUIRED that you unencrypt your device by formatting userdata, so back up your stuff first.
IMPORTANT NOTES: TWRP for OREO is a bit of a pain as it currently requires manually editing your fstab. I have tried to automate this process, but it breaks stuff. So just be aware before you begin that it is a rather time consuming process.
If you make any change to your boot partition after flashing SuperSU, you will need to reflash it or you will get a bootloop.
8.0 OREO TWRP INSTALLATION:
OREO SEEMS VERY FINICKY AND DOES NOT LIKE CHANGES TO ITS FILESYSTEM -- BE PREPARED TO REFLASH STOCK.
0. FLASH OREO FACTORY IMAGE (may work otherwise, but we should be starting from fresh stock here)
1. Download FASTBOOT BOOTABLE TWRP for 8.0/OREO below
2. Download SuperSU 2.82 SR5 below
3. Move SuperSU to external SD or USB OTG
4. From bootloader, fasboot BOOT TWRP
5. Flash SuperSU (note: do not format /data now... not necessary and will cause errors on boot)
6. Reboot system
7. With any root file editor/text editor (Amaze, Total Commander, etc) open /system/vendor/etc/fstab.qcom as a text file for editing.
8. At the end of the /data partition entry, delete "fileencryption=ice" and replace it with "encryptable=footer".
9. Save fstab.qcom (and make sure it is actually saved properly!)
10. Reboot to bootloader and fasboot BOOT TWRP
11. Go to Wipe, hit the FORMAT DATA button, and type "yes" to format /data. This will erase your data, obviously:silly:
12. Reboot system (should now be unencrypted, verify in Settings>Security or by booting TWRP and checking /data with File Manager.
If you later choose to flash TWRP (not the bootable we used here!), you may need to flash SuperSU again to avoid bootloops.
7.1.1 NOUGAT TWRP INSTALLATION:
1. Download current TWRP for 7.1.1 build below
2. Download SuperSU 2.85 SR5 (https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
3. Move SuperSU to your external Micro SD card.
4. Fastboot flash the TWRP image.
5. Reboot to TWRP.
6. FORMAT data (not wipe...use the "FORMAT DATA" button and type "yes". OBVIOUSLY THIS WILL ERASE YOUR DATA)
7. Install SuperSU 2.85 SR5
8. Reboot to system (it WILL bootloop a couple times...don't panic!) and confirm that device is unencrypted by checking that SETTINGS>SECURITY>ENCRYPTION now prompts "encrypt" (don't do it).
DOWNLOADS:
TWRP FOR 7.1.1 (Nougat) DOWNLOAD: https://drive.google.com/open?id=1Et-AQgCNx7WDAwzihlI51euUa2ixKHEP
TWRP FOR 8.0 (Oreo) DOWNLOAD: https://drive.google.com/open?id=1WcVS_3rloF7jxPulj_jKxfsp3zy5pB5N
FASTBOOT BOOTABLE TWRP IMAGE (OREO BASED): https://drive.google.com/open?id=12ClviqtEjtflB63UQ1CZQNKEqkprBO0u **For temporary TWRP boot using "fastboot boot". Do not flash or you will be stuck in recovery!**
DEVICE TREE: https://github.com/mightysween/android_device_motorola_payton (NEEDS TO BE UPDATED WITH OREO BRANCH)
changelog:
BETA4
-reverted to 3.2.0 for current build (release candidate rebased to 3.2.1).
-fixed "format data" button
-finalized fstab for OTG/SD/INTERNAL mounting
-target is now UNENCRYPTED devices only (/data decrypt will not be fixed)
BETA3
-Rebased to TWRP 3.2.1
-USB OTG working
-all partitions mounting correctly
-considered working except for decrypt and MTP/ADB
BETA2
-fixed internal storage mount
BETA1
- updated source to TWRP 3.2.0
ALPHA3
- Fixed USB mounting (adb/mtp still nonfunctional) BROKEN IN BETA1
ALPHA2
- SD Card fixed
ALPHA1
- /system is now properly mounted.
- now plays nice with our working root method.
- ramdisk is patched to prevent first boot encryption once /data is decrypted (now requires flashable ZIP)
NOT WORKING:
adb/mtp/sideload
/data decryption (abandoned -- /data access requires unencryption)
CREDITS: @kraatus90 for kernel fix, @Chainfire for SuperSU, @jcadduono for no-verity-opt-encrypt scripts.
---
Thanks so much for all your work!
hi,
you said this is really unstable and could brick the device easily. however, you seem to be testing and experimenting with your device a lot, so i'd like to ask if you have any particual unbrick method that you use when something goes wrong.. like, a via fastboot flashable image or something simmilar...?
thanks for your work!
Thanks for you work. If you have any unbrick methods pls tell.appreciated your work ?
I am not going to provide step by step "unbrick" methods, because until the partitioning is properly set up, TWRP has potential access to things that can not be fixed.
Again, this is still highly experimental.
All that said, my entire process to protect any device remains the same: Have a backup for every partition you will be testing, make as few changes as possible at a time, test boot images before flashing (fastboot boot), and test restore methods frequently (flashing back to stock or backups), and don't do anything unless you are highly certain of the outcome.
By those standards, there is nothing to gain by installing TWRP right now, as its basic function (install/backup/restore) is not set up yet.
Found the BoardConfig flag to enable FBE (TW_INCLUDE_CRYPTO_FBE := true) but do not have the lib it is dependent on (libe4crypt) and I don't see it anywhere yet...
For reference (not sure this is most current, but it demonstrates the process)
https://github.com/nijel8/TWRP/commit/bd7492de28963b7e74e8e5d3f17ec9a5a287d9c3
I have confirmed that FBE support is present in the source, dependent on this missing module... so need to figure out where/how to enable it.
It is possible that this entire process is specific to only certain devices (i.e. Pixel, Nexus). If this is the case, we may be stuck at this point for awhile.
Obvious workaround is to not be encrypted to begin with -- but that isn't a "solution".
mightysween said:
It is possible that this entire process is specific to only certain devices (i.e. Pixel, Nexus). If this is the case, we may be stuck at this point for awhile.
Click to expand...
Click to collapse
This appears to be the case, unfortunately. Seems that the TWRP FBE support was built specifically for the Google implementation of FBE which was merged into kernel sources for Nexus and Pixel. Not even using the qseecomd I assumed it was... will remove on next build.
Info on FBE:
https://source.android.com/security/encryption/file-based
Will be testing options to disable forced encryption, and if necessary dm-verity...
Anyone who wants to dig through kernel for related flags and props, it would be greatly appreciated!
Hey, where did the big "format data" button go in TWRP? Is that optional on compile... can't find a flag for it...
Making good progress this morning.
Seem to have a build with properly decrypted /system, and working SD Card. I also have patched the boot.img to disable forced encryption on the first boot. But now, I can not find a safe way to fully format (not "wipe") the /data partition. As mentioned in the previous post, the "FORMAT DATA" button is missing. The fastboot command "fastboot format userdata" returns an error that it does not support RAW format.
Need to figure out why this is happening... and once I do, I believe I can reformat /data without encryption and then will have an almost fully working TWRP build. Obviously, the ideal solution would be to have TWRP work out of the gate with an encrypted /data, but until then this is going to be our best option.
Will post an updated test build in the OP soon.... needs further testing before I would recommend non-expert users to try it.
Getting very close now!
UPDATE: ADDED NEW BUILD TO OP
---
Also, just occurred to me that the ramdisk will need to be patched every time, so now that I have SD card support will be testing some of the existing flashable ZIPs out there that are designed specificially to prevent first-boot encryption and/or disable dm-verity.
---
mightysween said:
Hey, where did the big "format data" button go in TWRP? Is that optional on compile... can't find a flag for it...
Click to expand...
Click to collapse
This is really the only hold up... I changed the partition from 'Advanced Wipe", but as expected, it was still encrypted on boot as it doesn't actually format the footer where encryption is stored. I can't figure out where that darn "FORMAT DATA" button ran off to, and that is exactly what we need here.
mightysween said:
This is really the only hold up... I changed the partition from 'Advanced Wipe", but as expected, it was still encrypted on boot as it doesn't actually format the footer where encryption is stored. I can't figure out where that darn "FORMAT DATA" button ran off to, and that is exactly what we need here.
Click to expand...
Click to collapse
I don't know how to help except to say that using TWRP 3.1.0-MOD_1 with my XT1254 (DROID Turbo), when you go to wipe it has two buttons --- one on the left for Advanced Wipe and Format Data on the right.
johnjingle said:
I don't know how to help except to say that using TWRP 3.1.0-MOD_1 with my XT1254 (DROID Turbo), when you go to wipe it has two buttons --- one on the left for Advanced Wipe and Format Data on the right.
Click to expand...
Click to collapse
I have 3.1.1-0 (same version I am building here) on several other devices, and the button is there. It has to be triggered by something during compile, but I can't figure it out. Driving me nuts
Looking through TWRP source, and can find actions for every other button (wipe, backup, restore, install, etc) but not for format. Hmm.
I posted over on an old but semi-active TWRP flags thread, maybe someone will have some insight.
Wondering if I make a stock boot image without the encryption tag in fstab, and then wipe data and reboot... then flash my image. That may make it so the data partition is never encrypted in the first place and allow TWRP to work.
But that is an ugly, non-user friendly fix. Why can't we just format /data?
---
Final update for today... this seems to be a compile issue, which is a good thing. I tried to manually decrypt /data from the TWRP command line, and got this:
No crypto support was compiled into this build.
Click to expand...
Click to collapse
So, I must be missing something in boardconfig still... and maybe need to set up a small proprietary vendor folder with the necessary libs
mightysween said:
Final update for today... this seems to be a compile issue, which is a good thing. I tried to manually decrypt /data from the TWRP command line, and got this:
So, I must be missing something in boardconfig still... and maybe need to set up a small proprietary vendor folder with the necessary libs
Click to expand...
Click to collapse
Thanks for doing all of this! I wish I had the time and knowledge to help.
Had a few PM's checking on TWRP status, so an update.
The good news is that the X4 is using Qualcomm based decryption for /data... the bad news is that most if it seems to be closed source. This will take some time for me to figure out, but I have already made some progress by sifting through logs.
Right now, I am trying to find a device with similar decrypt scheme to have some more guidance on the process.
mightysween said:
Had a few PM's checking on TWRP status, so an update.
The good news is that the X4 is using Qualcomm based decryption for /data... the bad news is that most if it seems to be closed source. This will take some time for me to figure out, but I have already made some progress by sifting through logs.
Right now, I am trying to find a device with similar decrypt scheme to have some more guidance on the process.
Click to expand...
Click to collapse
dont know all about these things but maybe xiaomi mi a1 twrp can help as it is also using same a/b partition. and twrp is already there for it
vivek638 said:
dont know all about these things but maybe xiaomi mi a1 twrp can help as it is also using same a/b partition. and twrp is already there for it
Click to expand...
Click to collapse
Thanks, the Mi A1 is one of the devices I have been comparing to, and has been quite helpful.
mightysween said:
Thanks, the Mi A1 is one of the devices I have been comparing to, and has been quite helpful.
Click to expand...
Click to collapse
Keep searching. wish i could have helped but dont know anything about compiling n all..
I'm not much of a programmer, but I can look through the files. Is there anything in particular we're searching for?