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

Search This thread

sid4306

Member
Jan 14, 2019
17
4
OnePlus 6
Earlier this week I tried to update my current TWRP V 3.6.1-11 to the newer 3.6.2-11. ROM is LOS 19.1 build 20220621 (A12).
Tried two different ways:
a) from TWRP 3.6.1 flash the 3.6.2 installer zip
b) from bootloader run 'fastboot boot TWRP-3.6.2.img', then in TWRP 3.6.2 ran 'Advanced-flash current TWRP' (or whatever that is called in the english version)

in both case when I tried to reboot to system I would end up in TWRP again. Trying to run 'Advanced-Fix recovery bootloop' would invariably end up in an error reporting some problems with patching the kernel or something like that (sorry that I didn't record the exact message, it was a bit late by the time I gave up)

I could fix that by restoring the boot partition from my latest Nandroid which of course brought back TWRP 3.6.1. Of course I can easily live with the older version, I juast was hoping for some fixes esp. in the decryption range, but , well...

Question is: am I missing an important step or is this an issue that others are having as well?
also , the correct method I assume will be reboot to recovery after (a) method .
 
  • Like
Reactions: lm089

applyscience

Senior Member
Nov 25, 2016
173
49
OnePlus 9
i use my old 6 for testing out the progress of ubuntu touch, windows on arm, nethunter and various other projects. Lately, i have had to bounce around from Android 9, 10 and 11 and various ROMs based on each. on all 3, I have been using the same TWRP i found when the first official teamwin release gave me issues. I tried 3.6 when it came out, but they all had weird hang-ups.(OTA not working, adb debugging not triggering on sideload attempts and of course the inability to decrypt and requiring a password)

so i just went back to the version that has always just worked for me. just today it took me from 9 to 11 and now im back on 9 (ubuntu touch requires 9 for helium to work)

I only provided the img because I can only vouch for its stability and success rate when loaded in fastboot (fastboot boot TWRP.img) and, once in, allow the TWRP instance to flash itself via the advanced section . if functional, go ahead and flash any os you want. i usually find myself using adb sideload as many installs require user data and sometimes, the whole system, to be wiped beforehand.

if it works, beforehand, i just go back into twrp and flash a zip to copy the current slot into the other as a safety net. this can also be done with a handful of magisk modules and even fastboot enhance, but i mainly just use that as a simpler solution to payload.bin extractions.
 

Attachments

  • TWRP-3.5.2-enchilada-Nebrassy-2.img
    64 MB · Views: 25
  • Like
Reactions: lm089

lm089

Senior Member
i use my old 6 for testing out the progress of ubuntu touch, windows on arm, nethunter and various other projects. Lately, i have had to bounce around from Android 9, 10 and 11 and various ROMs based on each. on all 3, I have been using the same TWRP i found when the first official teamwin release gave me issues. I tried 3.6 when it came out, but they all had weird hang-ups.(OTA not working, adb debugging not triggering on sideload attempts and of course the inability to decrypt and requiring a password)

so i just went back to the version that has always just worked for me. just today it took me from 9 to 11 and now im back on 9 (ubuntu touch requires 9 for helium to work)

I only provided the img because I can only vouch for its stability and success rate when loaded in fastboot (fastboot boot TWRP.img) and, once in, allow the TWRP instance to flash itself via the advanced section . if functional, go ahead and flash any os you want. i usually find myself using adb sideload as many installs require user data and sometimes, the whole system, to be wiped beforehand.

if it works, beforehand, i just go back into twrp and flash a zip to copy the current slot into the other as a safety net. this can also be done with a handful of magisk modules and even fastboot enhance, but i mainly just use that as a simpler solution to payload.bin extractions.
Greast thanks, the other day I was looking for that and couldn't find ...
I used a while back with an A11 based ROM, now I'm running LOS 19.1 (A12). Any risk using this one with A12? I guess not, but experience counts ;)
 

applyscience

Senior Member
Nov 25, 2016
173
49
OnePlus 9
Greast thanks, the other day I was looking for that and couldn't find ...
I used a while back with an A11 based ROM, now I'm running LOS 19.1 (A12). Any risk using this one with A12? I guess not, but experience counts ;)
I've used it on lineage 19.1, which is what my 6 has right now.

However, since they already offer their recovery image as a separate download and in the flashable zip. I just use that with adb commands (push, pull, sideload,etc) fastboot enhancer paired with any native recovery is just better supported and suited for A11+ these days.
 

lm089

Senior Member
the one thing I'm really missing from LOS recovery is the ability to create Nandroid backups; I create an unencrypted one before each OTA; a bit of work but not really that much once it became a routine, and I don't OTA each build anyways. Having recent backups at hand more than once saved my phones' lifes. If there was a reasonable way to create full backups I'd turn my back on TWRP as well, at least on my OP6
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 33



    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 6 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_enchilada
    https://github.com/TeamWin/android_device_oneplus_sdm845-common

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

    Download: https://twrp.me/oneplus/oneplus6.html
    6
    Hello guys,
    I would really appreciate your support as I am stuck for 2 days with my phone with the stupid crashdump mode black screen. :(

    I am on Android 11, stock rom, rooted with Magisk and unlocked bootloader.
    I got stuck after I tried to update Magisk and also when I updated my 3.4 TWRP to the 3.6 version.
    Actually I can't even boot into the 3.6 TWRP. I just see the homescreen and stops there.
    Now my phone only reboots to the 3.4 TWRP, but inside everything is decrypted and I can't see my files.
    I also tried to fastboot flash the latest images of: boot. abl, dtbo, fw , but I still can't access my system.

    Any ideas?
    The latest TWRP have issues to boot properly, some decrypt situation.
    First, remove PIN/Password/Pattern in your system, then adb reboot bootloader, now boot attached TWRP through bootloader (fastboot boot TWRP-3.5.2-enchilada-Nebrassy-2.img) then flash Orange Recovery, reboot recovery and done.
    5
    uploaded new build supporting stock android 11
    4
    this is now official

    3
    Please elaborate which version do you use to fastboot. I tried all of them with no positive result
    https://androidfilehost.com/?w=files&flid=326976 , this is the earlier version of the official one, but the fastboot boot is working fine. So fastboot it using this and continue install the official installer zip