• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[RECOVERY] [11] [UNOFFICIAL] TeamWin Recovery Project

Search This thread

blas4me

Senior Member
Jun 30, 2009
632
137
Brooklyn, NY
OnePlus 7 Pro
Root wouldn't stick, so I had to patch my boot.img. Then followed the instructions, and updated magisk once booted. Haven't tried a backup yet, phone was down long enough trying to get perma-root.
 

Attachments

  • Screenshot_2021-06-12-13-01-25.png
    Screenshot_2021-06-12-13-01-25.png
    116.7 KB · Views: 82

xtzy

Member
Oct 19, 2019
40
11

lollyjay

Senior Member
Jul 26, 2012
3,785
1,654
Fresno
Anyone else with this TWRP error on backup?

I:addFile '/data/app' including root: 1
==> set selinux context: u:eek:bject_r:apk_data_file:s0
failed to lookup fscrypt tar policy for '/data/app' - '1a6a3c6a000000000000000000000000'
I:Error adding file '/data/app' to '/data/media/0/TWRP/BACKUPS/6d11274b/2021-06-14--08-54-32/data.ext4.win000'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:InfoManager saving '/data/media/0/TWRP/BACKUPS/6d11274b/2021-06-14--08-54-32/data.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
 

immppa

Senior Member
Dec 5, 2012
306
157
Joensuu
Anyone else with this TWRP error on backup?

I:addFile '/data/app' including root: 1
==> set selinux context: u:eek:bject_r:apk_data_file:s0
failed to lookup fscrypt tar policy for '/data/app' - '1a6a3c6a000000000000000000000000'
I:Error adding file '/data/app' to '/data/media/0/TWRP/BACKUPS/6d11274b/2021-06-14--08-54-32/data.ext4.win000'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:InfoManager saving '/data/media/0/TWRP/BACKUPS/6d11274b/2021-06-14--08-54-32/data.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
Opening post says:
bugs:
backup/restore is unreliable
 

dianoandr

Senior Member
Mar 2, 2017
209
101
Italy
OnePlus 7 Pro
In the first post of thread, the only bug of this recovery is clearly described:

bugs:
backup / restore is unreliable


so I don't think that, at the moment, the questions regarding errors related to the backup function, can have a decisive answer. 😉
 
  • Like
Reactions: lollyjay

imaGine00

Senior Member
Dec 17, 2015
78
20
Hi there :)

As soon as I boot on a ROM, this twrp stays unencrypted and don't propose me to put my password to decrypt and use all functions. What did I miss ? I don't know where to look for ??
And where can I find recovery ramdisk ? I'm on dotOS unofficial and Magisk says : "ramdisk: no"

thank you in advance, you made a super work :)
 

khalisz

Senior Member
Hi there :)

As soon as I boot on a ROM, this twrp stays unencrypted and don't propose me to put my password to decrypt and use all functions. What did I miss ? I don't know where to look for ??
And where can I find recovery ramdisk ? I'm on dotOS unofficial and Magisk says : "ramdisk: no"

thank you in advance, you made a super work :)
I think you have to relock and then unlock the BL (full erase, backup) and flash twrp and flash rom normally you'll be encrypted.
What's dotos ?
 
  • Like
Reactions: imaGine00

imaGine00

Senior Member
Dec 17, 2015
78
20
I think you have to relock and then unlock the BL (full erase, backup) and flash twrp and flash rom normally you'll be encrypted.
What's dotos ?

like totally relock the phone and then unlock it again ???
'cause I tried format data, then flash official twrp and oos10, it works OK.

I only get the problem when I try to work with this twrp and oos11 or custom A11 rom (like DotOS 5.1.1 ;-) )
 

dewin_prins

Member
Nov 22, 2017
26
1
i installed pixel experience on my oneplus 7 pro with this version of twrp but problem is now it is stuck on the Google boot screen when i want to go back to twrp it goes into the pixel experience recovery and have to flash twrp over again. The rom will not boot at all
 

Nebrassy

Recognized Developer
Sep 17, 2015
971
1,794
Lattakia
Xiaomi Poco X3 Pro

jaggillararla

Senior Member
Mar 27, 2015
795
126

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    As I explained, when your phone is :
    - Bootloader unlocked
    - Root
    You have to proceed the update differently if you don't want to lose everything include your data.
    Once again, first of all do a backup.

    1 - Get full OTA update zip. Also, get the latest Magisk APK, and rename it to Magisk.zip
    2 - On your phone, create a folder that contains the full OTA + Magisk (The OTA will be in the .Ota hidden folder if it has been automatically downloaded from OP, you can copy Magisk.zip to there)
    3 - Reboot to recovery
    4 - Flash the full OTA zip twice: (Flash Slot A and then B, or B and then A. Then go back to the Slot you started at).
    4a. On the TWRP home screen, select "Install", and install the full OTA update.
    4b. Switch between Slot A and Slot B by going to the TWRP home screen, and select "Reboot"
    4c. In the Reboot screen, select the Slot that isn't the "Current Slot"
    4d. Go back to the home screen, and Install the full OTA update into the switched Slot
    4e. Go back to the "Reboot" screen, and switch back to the original active Slot.
    5 - Go to back to the home screen, and select "Advanced"
    5a. Select "Flash current TWRP".
    6 - Install Magisk.zip.
    7 - Update is complete. You can Reboot to System.

    Updated the instructions above for clarity.

    Thanks a ton for the clarification! This step-by-step description really helped!
    2
    Yes, but as parag0n1986 said, flash magisk after twrp otherwise you will lose root.

    I updated the instructions in my post, to clarify the steps and fix the Magisk/TWRP flashing order.

    Not sure if anybody will really see those instructions, though. They'll be buried amongst the torrent of other posts. :D

    ¿GJ?
    2
    if you install current twrp after magisk, TWRP will erase magisk. Flash magisk very last
    Right, I forgot to mention this important step.
    2
    Yes, but as parag0n1986 said, flash magisk after twrp otherwise you will lose root.

    1
    Incorrectly typed command: pm remove-user 999
    pm command as shown was typed correctly several times.
    It does not show in the photo due to curved glass screen protector.
    Not working for me for some reason.
    Any information appreciated...
  • 76



    Introduction:

    Team Win Recovery Project or TWRP 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

    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, 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/TeamWin/android_bootable_recovery

    Gerrit Instance - http://gerrit.twrp.me

    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.


    Hello, this is TWRP, for Oneplus 7/Pro/5G that supports Android 11
    can be flashed to boot with working decryption on android 11 roms


    bugs:
    backup/restore is unreliable

    Installation:
    1. fastboot boot twrp.img
    2. go to Advanced > Flash Current TWRP
    3. after that is done, if you were using a custom kernel, reflash it now
    4. if you were using magisk, reflash it now

    Updating to a newer build:
    1. download new build to internal storage
    2. go to Advanced > Install Recovery Ramdisk
    4. select the new image
    5. after that is done, if you were using a custom kernel, reflash it now
    6. if you were using magisk, reflash it now

    Send me a beer: Crypto(Preferred) | PayPal

    Trees:
    https://github.com/nebrassy/device_oneplus_guacamole-TWRP
    https://github.com/nebrassy/device_oneplus_sm8150-common-TWRP

    Telegram group: https://t.me/NSSFB

    Download: https://www.androidfilehost.com/?w=files&flid=325945


    Download for FBEv2 (only use this if you're on a custom rom and the build above doesn't decrypt for you): https://www.androidfilehost.com/?w=files&flid=326211
    18
    new build is up

    fixed decryption on newer roms
    added an option to auto flash TWRP after flashing a rom
    fixed the problem where you needed to refresh sizes before being able to flash TWRP
    12
    I am in the same position as the person above my comment. Can someone please give me instructions?

    I am on a GM1917 with OxygenOS 10 Open Beta 19, and I want to jump to OxygenOS 11 Open Beta 5.

    Is this instruction my best path? https://forum.xda-developers.com/t/...eamwin-recovery-project.4289455/post-85157715

    Any advice from someone that has already updated would be highly appreciated, especially if you have a GM1917.



    PLEASE HELP!!!!!!

    I installed the OOS 11 OB5 through OTA and then I did not reboot.
    Then I installed Magisk in the Magisk app for both the current slot and slot_b.
    Then I rebooted.
    I was in my phone and nothing was wrong, then I booted into fastboot and I connected my phone to my computer.
    Then I installed this version of TWRP just like the original post says.
    Then I rebooted.
    NOW IT BOOTS ONLY INTO THIS VERSION OF TWRP!!!!
    HOW DO I GET MY PHONE BACK??????!!!!
    This is what I did to install the latest version of OOS 11 and keep root and this version of TWRP.
    Maybe it will help you.

    1. Install OTA update as a local upgrade but DON'T REBOOT.
    2. Open Magisk and install to direct install DON'T REBOOT.
    3. Open Magisk again and install to inactive slot NOW REBOOT.
    4. After reboot you should still be rooted and have the latest OTA update with stock recovery.
    5. Use phone stock recovery to boot into bootloader mode.
    6. Use your PC with adb to flash nebrassy 2 TWRP image in the phone bootloader mode.
    7. When in TWRP go to Advanced > Flash Current TWRP.
    8. Flash latest Magisk (have this .zip file in download folder already) again to keep root.
    9. Reboot and enjoy latest OOS11 version with TWRP and rooted.
    12
    Uploaded new build for non FBEv2 fixing backup in most cases, you should still not depend on TWRP backup as the only backup you have as restoring while encrypted can be problematic
    9
    Uploaded new build with f2fs support