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

[RECOVERY] [11] [OFFICIAL] TeamWin Recovery Project

Search This thread

Jerrvdll

Member
Dec 8, 2018
48
32
I have done it with my OnePlus 7p and two OnePlus 6, and it went flawless. I only lost TWRP and that is what you want.
 
Last edited:
  • Like
Reactions: iamMG

lvints

Senior Member
Jan 6, 2012
1,035
196
Timon
Has anyone tested version 3.6.0?
Is the backup/restore bug fixed?
Despite appearing on the OP7 Pro page it is flash safe on OP7 (non-pro), right?
 
  • Like
Reactions: jmbolivar

crazymika

Senior Member
Oct 18, 2012
58
36
hi i been trying to change my /data to f2fs without success

every time i change it via twrp it erases all my data but stays in ext4

any recomendations or succes experience someone has?

im on crdroid a11 op7 pro
The same to me, but when checking file system with adb command mount it said DATA is in F2FS
So maybe just wrong display in recovery, but this might break the backup function cause it is backup in ext4 format.
 

dobi3

Senior Member
Apr 18, 2013
93
32
Seaford
OnePlus One
OnePlus 2
Has anyone tested version 3.6.0?
Is the backup/restore bug fixed?
Despite appearing on the OP7 Pro page it is flash safe on OP7 (non-pro), right?
Just go here for OnePlus 7

 
  • Like
Reactions: lvints

Dan3ll1

Senior Member
Nov 10, 2016
107
32
OnePlus 7 Pro
I would be so free and link this thread if thats ok :)
Maybe someone can help me with that.


One question i do have. Why there are no .IMG files anymore? Only the .zip and the .zip.asc?
What does the .asc file do? Is it needed?
Or is the .zip file the normal file for flashing in ADB now?
 

christantoan

Senior Member
Oct 9, 2015
219
94
OnePlus 3T
OnePlus 7 Pro
One question i do have. Why there are no .IMG files anymore? Only the .zip and the .zip.asc?
What does the .asc file do? Is it needed?
Or is the .zip file the normal file for flashing in ADB now?
.IMG files are there, scroll down a bit.
I believe the .asc file is used for verification to make sure the file is not tampered/corrupted.
.zip file AFAIK is for flashing through Magisk (like the old official version) though I haven't tested yet.
 

Dan3ll1

Senior Member
Nov 10, 2016
107
32
OnePlus 7 Pro
.IMG files are there, scroll down a bit.
I believe the .asc file is used for verification to make sure the file is not tampered/corrupted.
.zip file AFAIK is for flashing through Magisk (like the old official version) though I haven't tested yet.
Oh man....I am special :)

Dont know but i thought that when the last time i downloaded straight from twrp.me both files where next to each other.
 
  • Like
Reactions: christantoan

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Hi guys,

    Is backup/restore working now on Android 11?

    Compatible with decryption?
    I haven't had to restore but I have a few nandroid backups I made in TWRP that I transferred to thumb drive in case I need them some day. I'm not encrypted.. I'll restore in about one hour from now and edit my post here as to the results. It's currently 7:42am my time..

    Edit added:
    Got tied up doing things or would have done this already. When I boot FBEv1 or v2 I get what's in attached screenshot. Screenshot_2021-12-26-12-20-14.png
    1
    Follow-up: I tried the following:

    fastboot erase userdata

    ... and then ...

    fastboot format:ext4 userdata

    Both stated that they succeeded.

    But when I went into TWRP, the data partition was still inaccessible.
    Could you just pick a rom , go into fastboot , do a fastboot flash boot boot.img, go into to recovery and then do a format erase, then flash the rom vis adb sideload do another format erase , reboot
    1
    PS: Perhaps I have to "decrypt data". However, I have no idea what password to give when asked inside of TWRP.
    Whenever I came to a password screen in twrp I just hit ok without inputting a password and it always worked.

    I was once stuck on the just the boot screen and the only thing that saved me was the msm tool,, but you said that was not an option, sorry I am not of more help.. Good luck
    1
    Whenever I came to a password screen in twrp I just hit ok without inputting a password and it always worked.

    I was once stuck on the just the boot screen and the only thing that saved me was the msm tool,, but you said that was not an option, sorry I am not of more help.. Good luck
    Thank you anyway. I appreciate the help you gave me.

    TWRP doesn't do the decryption on my device without my giving a password.

    Happy New Year!
    1
    Regarding the issue I reported above: now I luckily managed to get access to a PC that I used before for MSM unbrick flashes. It always worked fine with those unbrick flashes in the past, and this PC is still configured exactly as it was configured before, and I have confirmed that it has the same device drivers as before, and the driver is indeed the correct one.

    However, now the MSM flash consistently fails a few seconds after the EDL connection is established. It gives the "Sahara Connection Failed" message. This repeatedly occurs.

    With all that I have reported, I'm now thinking that my device might have some sort of basic problem with storage, firmware, or something else, and that it may very well be beyond repair.
    I can say my msm did not work untill the port drive section in my device manager said Qualcomm qds 9008, and it only says this when the phone goes into the edl mode, after edl it switches back to regular adb android device
  • 90



    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/TeamWin/android_device_oneplus_guacamole
    https://github.com/TeamWin/android_device_oneplus_sm8150-common

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

    Download: https://twrp.me/oneplus/oneplus7pro.html
    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
    14
    this is now official

    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
    11
    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.