[RECOVERY][find7] TWRP 3.1.1-0 touch recovery [2017-05-19]
- Thread starter Dees_Troy
- Start date
-
- Tags
- development
Thank you maxwen, I know it.
I was asking for the zip file, since usually there were released too, and they are more easy to install. No need of fastboot, but they are installable directly from recovery.
Anyway it was just a info question.
Thank you maxwen, I know it.
I was asking for the zip file, since usually there were released too, and they are more easy to install. No need of fastboot, but they are installable directly from recovery.
Anyway it was just a info question.
flash with flashify..download at google playstore
I remember one of those apps was causing issues with TWRP on Find7 some time ago.
I you use fastboot and flash twrp .img file from official site, you are sure you have the right recovery.
I have a Find 7a but can't boot into this recovery. While holding volume down the phone just shuts down again. No twrp to be seen. The first time I tried the install via TWRP 2.8.4 that was on there and after that I flashed it via ADB. Both times no response from the twrp. Anyone else had this?
Have the same issue. Last TWRP to work on Oppo Find 7a x9006 was 2.8.5 everything after that fails.
Tried to contact Team Win, but even though they are good on what they are doing, trying to tell them that there are bugs usually gives you childish and grammatically incorrect replies like "your gay", "n00b", "No one is telling you to use twrp".. -.-
Tried to contact Team Win, but even though they are good on what they are doing, trying to tell them that there are bugs usually gives you childish and grammatically incorrect replies like "your gay", "n00b", "No one is telling you to use twrp".. -.-
@bigbiff as the maintaineer maybe you could check this out:
I'm on a Find7a with twrp 3.0.2.0
Flashing setup LVM zip with latest recovery fails. It only works with twrp_find7_lvm_09012014.img provided by Entropy - he has a 7a and maybe did some workarouds for it.
Everything is here:
http://xdaforums.com/showpost.php?p=55187001&postcount=558
Setting up LVM with adb shell in 3.0.2.0 returns:
After reboot recovery I get:
Could not mount /data and unable to find crypto footer.
Failed to mount '/data' invalid argument
I can't work it around by changing /data to FAT and ext4 again. Then I can flash system and use it normally.
I'm on a Find7a with twrp 3.0.2.0
Flashing setup LVM zip with latest recovery fails. It only works with twrp_find7_lvm_09012014.img provided by Entropy - he has a 7a and maybe did some workarouds for it.
Everything is here:
http://xdaforums.com/showpost.php?p=55187001&postcount=558
Setting up LVM with adb shell in 3.0.2.0 returns:
Code:
~ # lvm pvcreate /dev/block/platform/msm_sdcc.1/by-name/userdata
File descriptor 8 (/dev/__properties__) leaked on lvm invocation. Parent PID 520: /sbin/sh
File descriptor 9 (socket:[7660]) leaked on lvm invocation. Parent PID 520: /sbin/sh
Physical volume "/dev/block/platform/msm_sdcc.1/by-name/userdata" successfully created
~ # lvm pvcreate /dev/block/platform/msm_sdcc.1/by-name/sdcard
File descriptor 8 (/dev/__properties__) leaked on lvm invocation. Parent PID 520: /sbin/sh
File descriptor 9 (socket:[7660]) leaked on lvm invocation. Parent PID 520: /sbin/sh
Physical volume "/dev/block/platform/msm_sdcc.1/by-name/sdcard" successfully created
~ # lvm vgcreate lvpool /dev/block/platform/msm_sdcc.1/by-name/userdata /dev/blo
ck/platform/msm_sdcc.1/by-name/sdcard
File descriptor 8 (/dev/__properties__) leaked on lvm invocation. Parent PID 520: /sbin/sh
File descriptor 9 (socket:[7660]) leaked on lvm invocation. Parent PID 520: /sbin/sh
Volume group "lvpool" successfully created
~ # lvm lvcreate -l 100%FREE -n userdata lvpool
File descriptor 8 (/dev/__properties__) leaked on lvm invocation. Parent PID 520: /sbin/sh
File descriptor 9 (socket:[7660]) leaked on lvm invocation. Parent PID 520: /sbin/sh
ffff0000-ffff1000 r-xp 00000000 00:00 0 [vectors]: mlock failed: Cannot allocate memory
ffff0000-ffff1000 r-xp 00000000 00:00 0 [vectors]: munlock failed: Cannot allocate memory
Logical volume "userdata" createdAfter reboot recovery I get:
Could not mount /data and unable to find crypto footer.
Failed to mount '/data' invalid argument
I can't work it around by changing /data to FAT and ext4 again. Then I can flash system and use it normally.
Just curious as to why this thread was updated to say there is a TWRP 3.1.0-0 when there is no .img image to install?
In any case, does it matter if 3.1.x is available? I am running on 3.0.2.0 and find it stable and good. Is there a need to upgrade (needlessly)? My Find 7 QHD has grown long in the tooth and already has problems reading the external micro SD card, and I am relegated to using just the 32 Gb of internal SD card for data storage.......
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
30Team 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.7Reserved
Starting with version 2.7.1.1, we're now doing a unified build for both the 1080p 7a and the 1440p devices. This means the same recovery image works on both devices and will provide you with the proper stock theme for your display. Of course, you can still install a custom theme if you like.
Link to device specific page on our website
Direct link to downloads folder for current / past versions5I know this might be a bad question, but can someone explain to me or send me a link on how i can install this recovery? I'd rather as stupid questions that brick my phone
Download the recovery file: http://techerrata.com/browse/twrp2/find7a
Install the Google ADB / Fastboot drivers (Windows http://goo.gl/ZWGG)
Hold in Power and Vol Up to put your Find 7 into Fastboot mode.
Plug your USB cable into your phone and computer.
Type fastboot devices.
You should see your phone listed. If you're do proceed.
To just boot the recovery: fastboot boot openrecovery-twrp-2.7.0.0-find7a.img
To install / flash the recovery: fastboot flash recovery openrecovery-twrp-2.7.0.0-find7a.img4
None until Oppo makes a final decision on the approach they're taking. I know that for a variety of reasons, including all of the issues encountered with the 2.0.2 beta, they are looking into making significant changes to their approach.
Either way, supporting any of these approaches with a single build that autodetects requires reworking many of the things related to the RECOVERY_SDCARD_ON_DATA build flag - it needs to be reworked so that everything that flag affects is done at run time instead of build time. I'll be working on this when I return from vacation, as it's something that needs to be done whether Oppo goes with the current disaster or goes with LVM.4
