Develop Bugs

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

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG for 3.0.2-0:
-Backups will now include adopted storage keys (Dees_Troy)
-Fixed an adb restore issue (bigbiff)
-Fixed rebooting when no OS is present (Dees_Troy)
-Fixed line wrapping in the GUI terminal (_that)
-Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)
CHANGELOG for 3.1.0-0:
-vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
-adb backup to stream a backup directly to or from your PC, see documentation here: https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9 (bigbiff)
-tweak MTP startup routines (mdmower)
-support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
-support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
-better indicate to users that internal storage is not backed up (Dees_Troy)
-improve automatic determination of TW_THEME (mdmower)
-minimal getcap and setcap support (_that)
-try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
-shut off backlight with power key (mdmower)
-timeout during FDE decrypt (Dees_Troy and nkk71)
-support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
-boot slot support (Dees_Troy)
-TWRP app install prompt during reboot (Dees_Troy)
-support for AB OTA zips (Dees_Troy)
-support new Android 7.x log command (Dees_Troy)
-update recovery sources to AOSP 7.1 (Dees_Troy)
-numerous bugfixes and improvements by too many people to mention
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
DOWNLOAD:
1) Install the TWRP app from the Play Store or grab the apk from our website
2) Open the app, agree to the terms, and enable root access
3) Select TWRP Flash
4) Search for your device and select the version you wish to download
5) Once the download is complete, select the file (it's usually in your downloads folder) and then Flash Recovery
OR:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our website.
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.

First!
Thank you!!

Nice!! Thanks guys!

Great work guys!

Thanks looks awesome!
Sent from my SPH-L710 using xda app-developers app

Great work
Sent from my SPH-D710 using Tapatalk 2

In know both do the same but is this better than cwm.
Sent from my SPH-L710 using Tapatalk 2

eduardmc said:
In know both do the same but is this better than cwm.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Yes it is. It has more features and the interface is better for accessibility. It also has themes. You can also rename your backups within the recovery.
Key Features:
Ability to save custom recovery settings
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)
What's new in 2.2.0:
On-screen keyboard in recovery! -- supports long press, backspace repeat, and swipe left deletes everything left of the cursor
Name new backups and rename existing backups
Rename files and folders in the file manager
Pseudo-terminal emulator
Support decrypting an encrypted data partition on Galaxy Nexus (enter password using keyboard)
Backup archive splitting -- allows backup and restore of data partitions larger than 2GB
Simplified XML layout support between resolutions
Added dual storage selection radio buttons to zip install, backup, and restore pages
Improved zip install compatibility
Updated update-binary source code
Numerous small bug fixes and improvements

Crazy question and the better part of me says no, but can you restore a backup made with cwm in twrp?

chrisbass said:
Crazy question and the better part of me says no, but can you restore a backup made with cwm in twrp?
Click to expand...
Click to collapse
No.
Sent from my SPH-L710 using xda premium

HELL YEAH....Thank You VERY MUCH for this. I used it always and loved it on my epic 4g and have been really missing it ever since I switch to my SGS3 and had to resort to using the old "caveman" style/method recovery again...LOL
Now I can use TWRP again. AWESOME!
Cheers!

Perfect! This recovery supports OpenRecoveryScript so i'm gonna have to make this an option in the Aroma installer.

Cannot mount scared or ext card while in recovery. Not really an issue since it didn't work on CWM or the older TWRP. miss that feature.
Sent from my SPH-L710 using xda app-developers app

glcK23 said:
Cannot mount scared or ext card while in recovery. Not really an issue since it didn't work on CWM or the older TWRP. miss that feature.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
What does mounting the sd card do? I'm able to backup/restore roms and backups from from the internal and external sd. Is that different?

cbond007 said:
What does mounting the sd card do? I'm able to backup/restore roms and backups from from the internal and external sd. Is that different?
Click to expand...
Click to collapse
It would mount it to be seen on your PC to transfer files.
But yes, long live TWRP. I couldn't get rid of CWM fast enough. Love this recovery.

glcK23 said:
Cannot mount scared or ext card while in recovery. Not really an issue since it didn't work on CWM or the older TWRP. miss that feature.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
If you have a 64GB card that's formatted as exFAT then recovery won't be able to mount it. You can reformat to FAT32 to fix. If not, then pull a log and paste it to a paste site and give me the link. I might be able to sort it out for you.

it came from my evo 3d so maybe it does need to be formatted. what about the internal sd card ? can that be formatted too ??
Sent from my SPH-L710 using xda app-developers app

Nice, i was waiting for this. TWRP blows away clockwork.

Great work! Made my life easier and this is definitely easier to use

steezc said:
Great work!
Click to expand...
Click to collapse
It absolutely will not install for me. Any way to get it as a tar file so I can use Mobile Odin.
_______________
Just Flash It !!!

[RECOVERY] TWRP 2.6.3.0 touch recovery [2013-09-16]

Team Win Recovery Project 2.x, 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.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
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 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.

Reserved!

Dees_Troy is one of the best and nicest developers here, he did it all in like 5 minutes
Kudos brother, this is a great addiction for the Wonder!

sorry , is the image size 7.984MB ?

hadidjapri said:
sorry , is the image size 7.984MB ?
Click to expand...
Click to collapse
4.37MB, MD5 is 4c689ba24c1657540d8094124bf1e155

Dees_Troy said:
Direct Download
Turn the device off. Press and hold volume down, volume up, and power until the device boots, then on your computer:
fastboot flash recovery openrecovery-twrp-2.3.2.3-mako.img
Click to expand...
Click to collapse
this link refers me to the file with 7.984MB

hadidjapri said:
this link refers me to the file with 7.984MB
Click to expand...
Click to collapse
Ahhh, that is what I get for copying and pasting >_<

Dees_Troy said:
Ahhh, that is what I get for copying and pasting >_<
Click to expand...
Click to collapse
you get me bricked my phone :crying:
i hope nobody do the same mistake as i am by flashing "extreme huge" recovery.img
i didn't notice that ancora's recovery partition only capped to 7.5MB :crying:
well, it's not a problem. ssc is near my house
thanks for porting TWRP to ancora :good:

post no weighted ANCORA WAE LAH ....!:good:

hadidjapri said:
you get me bricked my phone :crying:
i hope nobody do the same mistake as i am by flashing "extreme huge" recovery.img
i didn't notice that ancora's recovery partition only capped to 7.5MB :crying:
well, it's not a problem. ssc is near my house
thanks for porting TWRP to ancora :good:
Click to expand...
Click to collapse
Odin should be able to fix it.

Dees_Troy said:
Odin should be able to fix it.
Click to expand...
Click to collapse
well, ancora's download mode sucks. it wastes me almost 1,5hours only stucked in "press up to continue"
gonna try the twrp after ssc fix my phone :good:

Testing it..
Sent from my GT-P5100 using xda premium

Thanks for porting it!

Can I flash this with adb and this command? dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
-sent from my awesome phone-

hotheabilly said:
Can I flash this with adb and this command? dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
-sent from my awesome phone-
Click to expand...
Click to collapse
Tested it, yes it works. But I reverted to CWM for a reason.
Sent from my GT-I8150 using xda app-developers app

Kreaz said:
Tested it, yes it works. But I reverted to CWM for a reason.
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
Yes it works for me too, and yes I'm back to cwm for some reason too
-sent from my awesome phone-

comment removed.

hotheabilly said:
Yes it works for me too, and yes I'm back to cwm for some reason too
-sent from my awesome phone-
Click to expand...
Click to collapse
I screwed up ma phone. I flashed TWRP via ADB. When i reboot to recovery it goes to CWM. When i switch on normally it goes to TWRP!!! Now im havin 2 recoveries and i cant boot to SlimBean!!!!!! Any fix?!?!?
Edit: I did a full wipe and Restored my system. Thanks to CWM!!

jassim007 said:
I screwed up ma phone. I flashed TWRP via ADB. When i reboot to recovery it goes to CWM. When i switch on normally it goes to TWRP!!! Now im havin 2 recoveries and i cant boot to SlimBean!!!!!! Any fix?!?!?
Edit: I did a full wipe and Restored my system. Thanks to CWM!!
Click to expand...
Click to collapse
lololol you probably format your ROM partition by your command line and replacing the whole rom to TWRP, but this is the first case I've ever seen!

hotheabilly said:
lololol you probably format your ROM partition by your command line and replacing the whole rom to TWRP, but this is the first case I've ever seen!
Click to expand...
Click to collapse
Is there .tar format for flashing TWRP via Odin?

[Q&A] [REF] LVM Partition Remapping

Q&A for [REF] LVM Partition Remapping
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [REF] LVM Partition Remapping. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

When I try flashing the setuplvm, it fails with error message "unable to mount /data." I am using TWRP 2.8.0.1 and have tried wiping the data. Is there anything I can do to fix this issue?

alpha_5 said:
When I try flashing the setuplvm, it fails with error message "unable to mount /data." I am using TWRP 2.8.0.1 and have tried wiping the data. Is there anything I can do to fix this issue?
Click to expand...
Click to collapse
Did you flash setuplvm from the external SD per the instructions given elsewhere?
I plan on updating setuplvm sometime soon, but the issue you describe sounds like what happens if the ZIP resides on internal storage.

Entropy512 said:
Did you flash setuplvm from the external SD per the instructions given elsewhere?
I plan on updating setuplvm sometime soon, but the issue you describe sounds like what happens if the ZIP resides on internal storage.
Click to expand...
Click to collapse
I have the same problem. I had the ZIP on external SD with omni nightly and gapps.
Same error and no LVM.

Try the twrp from omni thread. Flash setuplvm and than update to twrp 2.8.0.1.

jebulol said:
I have the same problem. I had the ZIP on external SD with omni nightly and gapps.
Same error and no LVM.
Click to expand...
Click to collapse
Also, the other question is: Did you reboot recovery after flashing setuplvm???

Entropy512 said:
Also, the other question is: Did you reboot recovery after flashing setuplvm???
Click to expand...
Click to collapse
Yup.
I flashed TWRP 2.8.0.1, tried to install setuplvm and got "unable to mount /data." Rebooted and flashed latest Omni and realized it didnt work.

Entropy512 said:
Did you flash setuplvm from the external SD per the instructions given elsewhere?
I plan on updating setuplvm sometime soon, but the issue you describe sounds like what happens if the ZIP resides on internal storage.
Click to expand...
Click to collapse
Yes, I am flashing from the external SD card. Here is what I see when I try it.
E: Could not mount /data and unable to find crypto footer.
Updating partition details...
E: Unable to mount '/data'
Full SELinux support is present.
Installing '/external_sd/setuplvm_find7_FULL_WIPE_09012014.zip'...
Checking for MD5 file...
Skipping MD5 chck: no MD5 file found
Unmounting data partition
Extracting LVM tools
Unmounting sdcard partitions
Creating LVM physical volumes
Adding LVM physical volumes to volume group
Creating userdata logical volume
Rescanning and activationg LVM volumes
Formatting LVM volume
E: Error executing updater binary in zip '/external_sd/setuplvm_find7_FULL_WIPE_09012014.zip'
Error flashing zip '/external_sd/setuplvm_find7_FULL_WIPE_09012014.zip'
Updating partition details...
E: Unable to mount '/data'
I will also add that if I go to "Mount" in TWRP I am unable to select "data." The phone boots up fine and seems to be working properly otherwise.

Hi,
This happened to my X9076 too about a week back and that was due to my mistake of installing the rom right away without rebooting the recovery first.
If you also missed that very crucial part, I'm pretty sure all you have to do is clear the data, run the reversal LVM zip, boot to recovery again, run the partition mapping, then boot recovery one more time and after that just install the rom + gapps as usual.
I however accidentally booted up the system directly after the failed install which got me the Android is encrypting splash screen for 1 minute or 2 then telling me it failed and booted. After that TWRP couldn't access the /DATA at all.
I eventually got around it by flashing stock recovery and colorOS. The newer releases didn't work though, I took the oldest ones from OPPOforums and that worked.
After that I could flash back to TWRP, run the partitioning as supposed to and install Omni.

i've been wanting to try out omni with lvm for a while, but is lvm complete?
i also read that there's some issues with twrp, i'm a bit confused, which twrp version do i use?
i'm currently running a rom with an unified partition
i just have to return to split layout then flash the setup lvm in latest twrp recovery?
thanks in advance

binaryfalcon said:
i've been wanting to try out omni with lvm for a while, but is lvm complete?
i also read that there's some issues with twrp, i'm a bit confused, which twrp version do i use?
i'm currently running a rom with an unified partition
i just have to return to split layout then flash the setup lvm in latest twrp recovery?
thanks in advance
Click to expand...
Click to collapse
There have been some odd issues with the following:
1) setuplvm does not play nice with newer TWRP. I have some guesses why... In a few places in the Omni thread I gave manual instructions for doing the conversion in an ADB shell, those will work
2) For some reason, the app "TWRP Manager" flashes a bogus version of TWRP that has issues
Other than those two issues, LVM is complete, I've been running it for two months now. I just need to figure out why TWRP 2.8.0.1 (especially when flashed via TWRP Manager) behaves oddly.

Entropy512 said:
There have been some odd issues with the following:
1) setuplvm does not play nice with newer TWRP. I have some guesses why... In a few places in the Omni thread I gave manual instructions for doing the conversion in an ADB shell, those will work
2) For some reason, the app "TWRP Manager" flashes a bogus version of TWRP that has issues
Other than those two issues, LVM is complete, I've been running it for two months now. I just need to figure out why TWRP 2.8.0.1 (especially when flashed via TWRP Manager) behaves oddly.
Click to expand...
Click to collapse
appreciate the response
what do I need flash?
which twrp version do I use?
It's just a compatible twrp then setuplvm then flash omni?
any help appreciated, can't wait to try it out

Entropy512 said:
I just need to figure out why TWRP 2.8.0.1 (especially when flashed via TWRP Manager) behaves oddly.
Click to expand...
Click to collapse
I downloaded TWRP from http://techerrata.com/browse/twrp2/find7 and flashed using fastboot. Still had issues.

jebulol said:
I downloaded TWRP from http://techerrata.com/browse/twrp2/find7 and flashed using fastboot. Still had issues.
Click to expand...
Click to collapse
That should work fine on a device that is already in the LVM configuration. It does have issues with setuplvm currently though.
Someone who had issues with setuplvm and TWRP 2.8.0.1 finally posted a recovery.log - For some reason, TWRP 2.8.0.1 is not unmounting the sdcard partition, which causes issues when setuplvm tries to convert that partition into an LVM PV.
From now on, anyone with issues with setuplvm (or other issues within recovery) needs to post /tmp/recovery.log - This can be obtained via ADB with:
Code:
adb pull /tmp/recovery.log
when you are in TWRP after you've tried (and failed) to do whatever you're trying to do
Why? This provides MUCH more information about what went wrong than just the basic screen results/console output such as what alpha_5 posted a few posts back.

I'm not sure how this lvm implementation works ...
If I wipe /data in a twrp lvm compliant recovery, what will happen? It will wipe only /data stuff in lvm pool or the whole "partition" (including internal sdcard)?
Enjoy!
EDIT : I want to make a "factory reset" but without erasing my personnal datas (photos etc.).
---------- Post added at 03:47 PM ---------- Previous post was at 03:17 PM ----------
Wendigogo said:
I'm not sure how this lvm implementation works ...
If I wipe /data in a twrp lvm compliant recovery, what will happen? It will wipe only /data stuff in lvm pool or the whole "partition" (including internal sdcard)?
Enjoy!
EDIT : I want to make a "factory reset" but without erasing my personnal datas (photos etc.).
Click to expand...
Click to collapse
I tried and it's written in TWRP recovery : factory reset doesn't wipe personal data (in /data/media).
AWESOME JOB !

Wendigogo said:
I'm not sure how this lvm implementation works ...
If I wipe /data in a twrp lvm compliant recovery, what will happen? It will wipe only /data stuff in lvm pool or the whole "partition" (including internal sdcard)?
Enjoy!
EDIT : I want to make a "factory reset" but without erasing my personnal datas (photos etc.).
---------- Post added at 03:47 PM ---------- Previous post was at 03:17 PM ----------
I tried and it's written in TWRP recovery : factory reset doesn't wipe personal data (in /data/media).
AWESOME JOB !
Click to expand...
Click to collapse
Correct. It's the same way all Nexus devices since the GNex (and most other devices) are - a factory reset does an rm -r of everything outside of /data/media instead of formatting the whole partition.
Of course, it's a good idea to periodically back things up in case the filesystem gets hosed to the point of needing a format. (Extremely rare on ext4 these days, common for f2fs in my experience)

Entropy512 said:
Correct. It's the same way all Nexus devices since the GNex (and most other devices) are - a factory reset does an rm -r of everything outside of /data/media instead of formatting the whole partition.
Of course, it's a good idea to periodically back things up in case the filesystem gets hosed to the point of needing a format. (Extremely rare on ext4 these days, common for f2fs in my experience)
Click to expand...
Click to collapse
Yes, always following the 3 main rules when playing with my devices :
1- Make a backup
2- Make a backup
3- Make a backup
And as I do that oftenly my backups are never outdated.
Enjoy!

Setting up LVM on oppo find 7 from a custom rom?
Hello,
I am tired of my app space always out (I can't update apps now and have limited my apps to about 1/2 of what I normally would have).
From quite a ways back, I had installed Gummy, I think M4, right around when they stopped supporting the rom.
My question is how would I set up LVM from this point in time? I'm unsure how to revert back to any colorOS system (and I would prefer never to go back that way anyway, however I do see cos1.2 in a restore kernal section). I have TWRP 2.7.1.0 currently in use.
update: I see that twrp from the OS, can download the latest TWRP so I am currently DL and will try to install 2.8.7.1. If this successfully gets installed, can I flash the LVM program directly, then a 5.x or later D.U., Nameless, or OMNI rom afterwards?
Your help would be greatly appreciated as I have put this off for way too long however understand it's an amazing phone w/lots of hardware capability.
Update: downloading 2.8.7.1 from the app's interface didn't work well. I had to get back into flashify and install from local file version 2.8.5.0. When I get into bootup>TWRP, i have a split screen where the left side is scrolling slowly downwards. All functionality is normal just screen split flipping is annoying.

Hi.
Anyone give me working download link for "set up LVM" and "remove LVM" flashable zip please.
I can't download them from oppo forum.

Hi Entropy512, All,
I have installed succesfully LVM with the last OmniRoma Available but everytime I try to download something or take a picture with the camera, It says "For use camera, insert and SD Card". I checked the threat and I do not find any clue of how to solve this. Probably I miss something in the configuration process.
Any help?
Thanks in advance

[RECOVERY][blanc] TWRP 3.2.1-0 touch recovery [2018-02-19]

This is for the Mate 10 Pro (BLA). Touch does not work quite right on the non-Pro Mate 10. It may work on other models, but I have not tested it and most likely the device name will be wrong.
NOTE: Decrypting data is not currently supported. MTP also does not work, but you can use adb to push and pull files.
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.2.1-0:
-minui fixes (cryptomilk)
-Better android-8.0 compatibility in ROM trees (Dees_Troy)
-Fix missing library in android-8.0 (nkk71)
-Fix inconsistent SDCard naming (DevUt)
-Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
-Allow restoring adb backups in the TWRP GUI (bigbiff)
-Fix gzip backup error in adb backups (bigbiff)
-Fix a bug in TWRP's backup routines that occasionally corrupted backup files (nkk71)
-Better support for installing Android 8.0 based zips due to legacy props (nkk71)
-Support vold decrypt with keymaster 3.0 in 8.0 firmwares (nkk71)
-Decrypt of synthetic passwords for Pixel 2 (Dees_Troy)
-Support newer ext4 FBE policies for backup and restore in libtar (Dees_Troy)
-v2 fstab support (Dees_Troy)
-Bring TWRP forward to android 8.0 AOSP base (Dees_Troy)
-Various other minor bugfixes and tweaks
CHANGELOG for 3.1.1-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
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!
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.

NOTE: fastboot flash to recovery_ramdisk and not to recovery as this device does not have a regular recovery partition.
Device Page, Download Links, Mirrors:
https://twrp.me/huawei/huaweimate10pro.html
Download:
https://dl.twrp.me/blanc

Omg thank you so much for this its feels like a hope of life for a cancer patient ?

where is the download?

@Kane1706 https://twrp.me/huawei/huaweimate10pro.html and the direct link https://eu.dl.twrp.me/blanc/twrp-3.2.1-0-blanc.img.html

Booted into recovery but touch is not working
Mate 10 alp-l29.

Has anyone tested this on the Mate 10 (non-pro) yet?

aDarkBox said:
Has anyone tested this on the Mate 10 (non-pro) yet?
Click to expand...
Click to collapse
Tested on ALP-l09 Huawei mate 10 but does not work although installed and everything but pressing swipe does not work the touch
Enviado desde mi ALP-L09 mediante Tapatalk
---------- Post added at 10:31 AM ---------- Previous post was at 10:31 AM ----------
Dees_Troy said:
This is for the Mate 10 Pro. It may work on other models, but I have not tested it and most likely the device name will be wrong.
NOTE: Decrypting data is not currently supported. MTP also does not work, but you can use adb to push and pull files.
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.2.1-0:
-minui fixes (cryptomilk)
-Better android-8.0 compatibility in ROM trees (Dees_Troy)
-Fix missing library in android-8.0 (nkk71)
-Fix inconsistent SDCard naming (DevUt)
-Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
-Allow restoring adb backups in the TWRP GUI (bigbiff)
-Fix gzip backup error in adb backups (bigbiff)
-Fix a bug in TWRP's backup routines that occasionally corrupted backup files (nkk71)
-Better support for installing Android 8.0 based zips due to legacy props (nkk71)
-Support vold decrypt with keymaster 3.0 in 8.0 firmwares (nkk71)
-Decrypt of synthetic passwords for Pixel 2 (Dees_Troy)
-Support newer ext4 FBE policies for backup and restore in libtar (Dees_Troy)
-v2 fstab support (Dees_Troy)
-Bring TWRP forward to android 8.0 AOSP base (Dees_Troy)
-Various other minor bugfixes and tweaks
CHANGELOG for 3.1.1-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
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!
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.
Click to expand...
Click to collapse
Tested on ALP-l09 Huawei mate 10 but does not work although installed and everything but pressing swipe does not work the touch
Enviado desde mi ALP-L09 mediante Tapatalk

This is for BLA-L09 / BLA-L29
Not for ALP

Backup ans Restore Working?

touch is working fine for bla-l29 but storage is not the internal storage that i placed my files on its full of garbled folders

BLA-L29 Working?

Look at the post above yours, you may get the answer.

ngoralph said:
touch is working fine for bla-l29 but storage is not the internal storage that i placed my files on its full of garbled folders
Click to expand...
Click to collapse
This is because the internal storage is encrypted, and for now, this version of TWRP doesn't support decryption.
I guess that only solution for now would be to format (not Wipe) internal storage. Maybe dees_troy will soon find a solution, and decrypting will be fully supported.

Pretoriano80 said:
This is because the internal storage is encrypted, and for now, this version of TWRP doesn't support decryption.
I guess that only solution for now would be to format (not Wipe) internal storage. Maybe dees_troy will soon find a solution, and decrypting will be fully supported.
Click to expand...
Click to collapse
at least that's a partial fix, thank you

ngoralph said:
at least that's a partial fix, thank you
Click to expand...
Click to collapse
I didn't tested personally, so i can't guarantee if it works or if the /data is re-encrypted upon reboot.
Let us know if you succeed!

ngoralph said:
at least that's a partial fix, thank you
Click to expand...
Click to collapse
Pretoriano80 said:
I didn't tested personally, so i can't guarantee if it works or if the /data is re-encrypted upon reboot.
Let us know if you succeed!
Click to expand...
Click to collapse
You need to remove fileencryptioninline from /vendor/etc/fstab.kirin970, else it will re-encrypt
And formatting wipes /data (Like a factory reset, meaning files will be missing )

ante0 said:
You need to remove fileencryptioninline from /vendor/etc/fstab.kirin970, else it will re-encrypt
And formatting wipes /data (Like a factory reset, meaning files will be missing )
Click to expand...
Click to collapse
Thanks, i knew there's a way to remove encryption from fstab, but i wasn't sure how it works on Mate 10. [emoji6]
Obviously, the best way would be to have encryption support in TWRP, but at least we have a workaround.
Btw, this encryption issue also affects backup operations, i guess!?

Pretoriano80 said:
Thanks, i knew there's a way to remove encryption from fstab, but i wasn't sure how it works on Mate 10. [emoji6]
Obviously, the best way would be to have encryption support in TWRP, but at least we have a workaround.
Btw, this encryption issue also affects backup operations, i guess!?
Click to expand...
Click to collapse
For /data yes, all other partitions will backup fine.

ante0 said:
For /data yes, all other partitions will backup fine.
Click to expand...
Click to collapse
Yes, i mean for /data! [emoji6]The best part is that now, with TWRP available, we have more options to recover from possible soft-bricks, bootloops, etc.

How to decrypt your OP3(T) device with custom rom?

A question about decrypting your device, in this case Luisrom Android 10, but would most probably count for other roms too.
Did not try it already but would like to decrypt my device and would like a confirmation if the following is the right procedure without doing a new install:
Boot in recovery
Make a backup of /data to internal storage with TWRP
Make a backup of internal storage to my pc
Format data in TWRP
Copy internal storage back from pc to OP3(T)
Restore backup from /data with TWRP
Reboot with decrypted phone
I could do a dirty flash afterwards ofcourse, but because /system is not touched I think the steps above should be enough.
Could someone confirm if this is right?

Just tried what I described above but seems not to work.
After reboot, phone is starting again with encrypting and after next reboot everything is encrypted again.
It also seems as if Android 10 (read it somewhere) is using file based encryption, so not only on a higher level...
So for now, I only see a fresh install as the solution.
Would someone know another solution to keep your data without doing a fresh install it would be nice to know.
Any input is welcome!

Johan2020 said:
Just tried what I described above but seems not to work.
After reboot, phone is starting again with encrypting and after next reboot everything is encrypted again.
It also seems as if Android 10 (read it somewhere) is using file based encryption, so not only on a higher level...
So for now, I only see a fresh install as the solution.
Would someone know another solution to keep your data without doing a fresh install it would be nice to know.
Any input is welcome!
Click to expand...
Click to collapse
First of all: decrypting is what happens on each reboot if data is encrypted. Decrypting is making something encrypted readable again. Removing encryption is something completely different.
For your question: which rom are you booting? This sounds like you are using a rom with forced encryption enabled. Dosable forced encyption in fstab before first system boot.
You can't use fbe with op3/t. No blobs, no twrp... Either you havn't read closly enough or you belived some ignorant not reading closely enough: g requires new devices shipped the first time with q to use fbe. All devices shipped originaly with fde can still use fde with q.
Reference: https://source.android.com/security/encryption/file-based

nvertigo67 said:
First of all: decrypting is what happens on each reboot if data is encrypted. Decrypting is making something encrypted readable again. Removing encryption is something completely different.
For your question: which rom are you booting? This sounds like you are using a rom with forced encryption enabled. Dosable forced encyption in fstab before first system boot.
You can't use fbe with op3/t. No blobs, no twrp... Either you havn't read closly enough or you belived some ignorant not reading closely enough: g requires new devices shipped the first time with q to use fbe. All devices shipped originaly with fde can still use fde with q.
Reference: https://source.android.com/security/encryption/file-based
Click to expand...
Click to collapse
I am using CrDroid 6.4 Luisrom which is not enforcing encryption, just as most other custom roms.
I had enabled encryption though after installation to see if encryption was working already for installing CrD Luis on my work phone (where I want encryption).
After that I decided to go back to unencrypted, following the procedure above, which did not work.
Did not make the link between fbe and file based encryption, but ofcourse this is the same and not available on op3/t.
Must have been sleeping when I wrote that.
Based on what you wrote and my missing knowledge;
After encrypting, is fstab changed also and would the solution have been to change fstab back also before rebooting after restore?

Johan2020 said:
After encrypting, is fstab changed also and would the solution have been to change fstab back also before rebooting after restore?
Click to expand...
Click to collapse
No. fstab isn't changed during encryption, neither for forced encryption nor for "voluntary" ( ) encryption.
Maybe the problem is the restored data itself: the rom setting for encryption is restored as well if you restore the data unconditionaly... Perhaps this way the reencryption is triggered. Did you try to boot the rom without restoring data? If it's unencrypted on a clean boot, but is (re)encrypted after first boot after restoring the backup, you have the answer. If it's encrypzed on a clean boot, formating to remove the enctyption has failed.

nvertigo67 said:
No. fstab isn't changed during encryption, neither for forced encryption nor for "voluntary" ( ) encryption.
Maybe the problem is the restored data itself: the rom setting for encryption is restored as well if you restore the data unconditionaly... Perhaps this way the reencryption is triggered. Did you try to boot the rom without restoring data? If it's unencrypted on a clean boot, but is (re)encrypted after first boot after restoring the backup, you have the answer. If it's encrypzed on a clean boot, formating to remove the enctyption has failed.
Click to expand...
Click to collapse
Good point, did not try that unfortunately and just did a fresh install so.... not really eager to try it now
But I think indeed reencryption was triggered because of also restoring the encryption settings.
Will try it when I have some spare time and want to take the risc of a fresh install again