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

Search This thread

azeem40

Senior Member
Jun 13, 2013
936
235
Frisco
I'd say start fresh and work through it.

Do a fresh fastboot flash and provide that log/entry here.
Then after you boot TWRP again, wipe system/data/cache/davlik, flash your ROM and before you reboot provide the recovery.log (from Settings or Advanced I believe, will copy to your SD card).
If you still aren't able to boot into Android I'm guessing we can find the problem there there.
When you say provide the log for the fastboot, do you mean tell here what it said when I did that or a logcat?
 

Pure Drive GT

Senior Member
Jan 14, 2013
220
104
Find 7 X9076

I really don't like to ask ETA'esque questions, but I'm kind of cornered by certain circumstances XD Are you guys already working on a version for the X9076 (Find 7 QHD Global). If so, is it possible to give me a very rough time frame on when it could be available? Any kind of answer much appreciated :)
 

Mord0rr

Senior Member
May 24, 2013
1,095
158
Some thoughts here:

I have S3 + Phils recovery and i can say at this moment, a lot of experience with that device...

Now, i have a Oppo7A international just rooted.

I been reading problems with recoverys an loops, and even not working with some rooms or even official rom backups..

My questions:

1 - Can i install this normally, without affecting my original rom from oppo?
2 - Can i install any other rom with no problems?
3 - (continuation of point 1) In case i did install a personal rom, can i use this recovery to return to a official oppo rom?

Yes i do now TWRP from S3, since i did use it for a time.

Thank you!
 

Mord0rr

Senior Member
May 24, 2013
1,095
158
And i did try,,,but what a hell is adb?

Enter fastboot and.......???

Why can i enter recovery oppo and simply flash TWRP image?

Arghhh.....very confuse this!
 

beton87

Senior Member
Jan 7, 2013
482
116
Wrocław
Does this support flashing roms from Oppo? Because I couldnt flash ColorOS on the latest TWRP. It would be a nice feature, I had to fash stock recovery instead.
 

Mord0rr

Senior Member
May 24, 2013
1,095
158
Does this support flashing roms from Oppo? Because I couldnt flash ColorOS on the latest TWRP. It would be a nice feature, I had to fash stock recovery instead.

I have the same doubt.

Yesterday, finally i manage install TWRP.:good:

Also, can i continue receive updates OTA for official rom, with TWRP installed?:eek:
 

majikfox

Senior Member
Oct 25, 2010
240
55
Your title says "Find 7."

But you only support the Find 7a.

Please fix your title.
 

ZenithHammerhead

Senior Member
Nov 8, 2013
113
35
worldinhd.wordpress.com
Posted something similar in the CM11 ROM thread, but there may be a fix on the recovery side of things also...

Whenever I try to flash a ROM, I get an error with something along the lines of "This package was made for x9006...This is a FIND7". The I have an Oppo Find 7a, and I keep getting this error.

Obviously this issue was there in the past, as I remember seeing it on the forums back when the device first shipped, but I'm getting this again. I'm coming from stock ROM with the newest version of TWRP installed also...any ideas?

Can I change the device name..? Or can I change the compatible list of devices on the ROM package?
 

kishd

Senior Member
Oct 25, 2011
561
196
OnePlus 6T
Samsung Galaxy Note 10+
Posted something similar in the CM11 ROM thread, but there may be a fix on the recovery side of things also...

Whenever I try to flash a ROM, I get an error with something along the lines of "This package was made for x9006...This is a FIND7". The I have an Oppo Find 7a, and I keep getting this error.

Obviously this issue was there in the past, as I remember seeing it on the forums back when the device first shipped, but I'm getting this again. I'm coming from stock ROM with the newest version of TWRP installed also...any ideas?

Can I change the device name..? Or can I change the compatible list of devices on the ROM package?

I think it would be better to ask the ROM developer to add FIND7 to the asserts in the ROM so that all the find 7 ROMs are standardised

Sent from my X9007 using Tapatalk
 
  • Like
Reactions: Entropy512

Entropy512

Senior Recognized Developer
Aug 31, 2007
14,088
25,086
Owego, NY
Posted something similar in the CM11 ROM thread, but there may be a fix on the recovery side of things also...

Whenever I try to flash a ROM, I get an error with something along the lines of "This package was made for x9006...This is a FIND7". The I have an Oppo Find 7a, and I keep getting this error.

Obviously this issue was there in the past, as I remember seeing it on the forums back when the device first shipped, but I'm getting this again. I'm coming from stock ROM with the newest version of TWRP installed also...any ideas?

Can I change the device name..? Or can I change the compatible list of devices on the ROM package?
All ColorOS releases I've seen look for FIND7 - for this reason, we have chosen to make recovery report as FIND7 in order to permit flashing stock ColorOS packages and OTA updates (yes, you can take OTAs with TWRP, although many such OTAs will clobber TWRP in the process requiring you to reflash it.)

My guess is whatever you're flashing had its asserts configured back when there were severely broken recoveries reporting as x9006.

http://www.oppoforums.com/threads/ro-build-product-for-qhd-find7.16351/ - I admit I didn't properly capitalize some of my answers here, but based on Oppo's response (Find 7a and 7s, aka 7 builds would be unified, and all would use FIND7 for the asserts), we chose to have TWRP report as FIND7.

A package can choose to check for multiple values when doing assert checks, but a recovery can only report one value for ro.build.product, etc.
 

&roid

Senior Member
Mar 2, 2011
600
125
I can't get the new version to work. So I had to revert back to the old version. I'm using a find 7a.

Sent from my Find7
 

Top Liked Posts

  • There are no posts matching your filters.
  • 30
    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.
    7
    Reserved

    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 versions
    5
    I 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 :p

    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.img
    4
    Any change of an official TWRP that supports the unified partition that OPPO is working on in their forums?

    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
    @Entropy512 any news on twrp 2.8.1…?
    TWRP 2.8.3.0 is published