[RECOVERY] - TeamWin Recovery Project [REDFIN] [OFFICIAL]

Search This thread

andybones

Forum Moderator
Staff member
May 18, 2010
15,012
15,359
Google Pixel 5
Are you removing the pin before restoring? Can you post logcat from the lineage boot?
What about if I'm stuck in a bootloop and cant remove pin?
Or actually I could probably remove it in TWRPs file manager by going to /data/system and remove the files that end in the .key extension and any files that have “locksettings” such as Gatekeeper.password.key, gatekeeper.pattern.key, settings.db, locksettings.db-shm and locksettings.db-wal.

I'm not sure this is, or should be necessary but the only times I'm able to actually restore correctly is by first backing up my internal storage as to not lose anything. Then do factory reset and format data, "yes" and reboot the device. Let it boot up to the ROM, and add back my internal storage which contains my TWRP backup, reboot to the TWRP recovery and restore. And then it succeeds with the needing to do a reboot after the first initial boot.
 
Last edited:
  • Like
Reactions: elong7681

andybones

Forum Moderator
Staff member
May 18, 2010
15,012
15,359
Google Pixel 5
would twrp 3.6.2 work on android 12.1?
Good question. You can always try, but at your own risk.
I think I read one ROM it worked with, and curious myself.
I think it would boot, but maybe screen touch doesn't work, or all/most functions.
but absolutely NO clue. Really miss TWRP. I hope if it comes, it comes to A13 instead of A12, as I didn't get to use it much on A11, and I just only recently upgraded to A12 like 2 months ago. (i like it much better than excepted, and think A13 will really shine).
 

ziand

Senior Member
Apr 24, 2008
501
1,270
HTC U12+
Google Pixel 5
would twrp 3.6.2 work on android 12.1?
I think it would boot, but maybe screen touch doesn't work, or all/most functions.
Works perfect on A12.1. Touchscreen is working as like in temp TWRP as and in perm TWRP too. Good work !

One thing I could not run perm TWRP with 25200 Magisk, only with 24300 not higher.
If someone would like, here is a Boot Patch helper for flashing perm 3.6.2 TWRP and 24300 Magisk together:
it can be flashed from magisk module installer or from TWRP.
 
  • Like
Reactions: andybones

Snsnfsh

Member
Dec 21, 2017
10
1
Google Pixel 5
Works perfect on A12.1. Touchscreen is working as like in temp TWRP as and in perm TWRP too. Good work !

One thing I could not run perm TWRP with 25200 Magisk, only with 24300 not higher.
If someone would like, here is a Boot Patch helper for flashing perm 3.6.2 TWRP and 24300 Magisk together:
it can be flashed from magisk module installer or from TWRP.
Thankyou so much, Installed perfectly on Android 12.1/12L security Patch July 5, 2022
 
Last edited:

risk_06

Member
Apr 12, 2016
24
1
Hi!! Please i don't have clear the procedure for install TWRP , could you explain the process. i have a pixel 5 root, android 12 , magisk 25. i 'll loose my data?
 
Last edited:

andybones

Forum Moderator
Staff member
May 18, 2010
15,012
15,359
Google Pixel 5
Works perfect on A12.1. Touchscreen is working as like in temp TWRP as and in perm TWRP too. Good work !

One thing I could not run perm TWRP with 25200 Magisk, only with 24300 not higher.
If someone would like, here is a Boot Patch helper for flashing perm 3.6.2 TWRP and 24300 Magisk together:
it can be flashed from magisk module installer or from TWRP.
awesome!
thank you for trying and posting results.

have you/can you test backup/restore please and thank you
 

ziand

Senior Member
Apr 24, 2008
501
1,270
HTC U12+
Google Pixel 5
awesome!
thank you for trying and posting results.

have you/can you test backup/restore please and thank you
Yes, of course I tried. All works properly for backuping and restoring data. I have tested few months ago on stock A12.1 too.

Now I use my own script for backuping and script for restoring my data with some more options and including my some data on internal SD.
 

DroidRommer

Senior Member
Aug 12, 2016
103
49
Anyone tried flashing this-

Flash_twrp-3.6.2_11-0__Magisk-24.3-MAGISK-TWRP.zip on latest lineage 19.1? If not it's okay. later today when I know I'll have time to fix it if it soft bricks or anything I'll give it a try and report back. 👍


DroidRommer
 

gecowa6967

Member
Nov 11, 2020
17
11
I am on Android 13 I try to boot TWRP using `adb boot twrp-3.6.2_11-0-redfin.img` but I get stuck at the twrp logo. I waited for 10 minutes but still TWRP does not start. Is there a fix for this?

Thank you
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    I am on Android 13 I try to boot TWRP using `adb boot twrp-3.6.2_11-0-redfin.img` but I get stuck at the twrp logo. I waited for 10 minutes but still TWRP does not start. Is there a fix for this?

    Thank you
    No this is made for Android 11 and somewhat worked on Android 12.
  • 62
    [RECOVERY] TWRP 3.6.0_11-0 - TeamWin Recovery Project




    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.

    Device Config: https://github.com/bigbiff/android_device_google_redbull

    If others thing don't work, please report the issue and let me know.

    Download here:
    Test9: https://build.twrp.me/test/redfin/twrp-3.5.0-0-test9-redfin.img
    - fix cpu temperature display
    - turn off openaes
    - MTP: fix 100% CPU
    - fix perms for last_log.gz
    - one click flash option to keep twrp when updating boot in recovery - thanks @Nebrassy


    You need to install a kernel with built-in touch drivers such as ElementX-P5.
    First, install ElementX-P5, the use the install ramdisk recovery option in the Install menu to install the TWRP image.


    https://build.twrp.me/test/redfin/twrp-3.5.0-0-test1-redfin.img

    Please ignore the -10 in the version string when fastbooted into TWRP. I am hoping to get the a11 TWRP branch working in a10 trees.

    Test 2: https://build.twrp.me/test/redfin/twrp-3.5.0-0-test2-redfin.img
    Test 3: https://build.twrp.me/test/redfin/twrp-3.5.0-0-test3-redfin.img
    Decryption and backup restore working. Tested with April Firmware.
    Test 4: https://build.twrp.me/test/redfin/twrp-3.5.0-0-test4-redfin.img
    Enable MTP. Fix /sdcard bind mount to /data/media/0
    Test 5: https://build.twrp.me/test/redfin/twrp-3.5.0-0-test5-redfin.img
    Add partitions: misc, boot and persist. Enable repacking into ramdisk. Tested with ElementX-P5.
    Test 6: https://build.twrp.me/test/redfin/twrp-3.5.0-0-test6-redfin.img
    Fix repacking twrp into recovery. You need to install a kernel with built-in touch drivers such as ElementX-P5.
    First, install ElementX-P5, the use the install ramdisk recovery option in the Install menu to install the TWRP image.
    Test 7: https://build.twrp.me/test/redfin/twrp-3.5.0-0-test7-redfin.img
    Fix wiping Titan M chip. Fix decryption hanging on lineage-18.1 when booting TWRP.
    Test 8: https://build.twrp.me/test/redfin/twrp-3.5.0-0-test8-redfin.img
    Fix reboot to recovery from fastbootd.


    http://twrp.me
    23
    Hello all. I was able to get an initial decryption and backup/restore working.

    Here is test2 image: https://build.twrp.me/test/redfin/twrp-3.5.0-0-test2-redfin.img

    Remember this is still fastbootable only. I have to test repacking in the future.

    Currently only decrypts the 12/25/2020 patchlevel. I will try to upload today a version that will continue to work on future and current versions.
    22
    Here is test3, tested with the latest firmware: https://build.twrp.me/test/redfin/twrp-3.5.0-0-test3-redfin.img

    Please let me know what issues you have. I will be working on integrating fscrypt v1 policies so I can port over crosshatch to the aosp11 tree. I will work on repacking afterwards.
    20
    Should I keep crypto disabled or should I try to resolve the fscrypt includes somehow? With crypto disabled to avoid that error, I've got the Google boot splash with the above ADB fix for proper shell access including dmesg and logcat, but it fails to start actual TWRP and the logcat is complaining about missing vintf manifest entries for android.hardware.boot and android.hardware.health

    Edit: I also had to inject the Proton kernel for it to boot, I'm currently using the latest AOSP11 bramble/redbull with your commits cherry-picked like I did earlier with the lineage-18.1 attempt

    I just barely got Fscrypt working with decryption. I am working on fscrypt policy storage now. You can track my progress at the android_bootable_recovery project at https://gerrit.twrp.me
    18
    I posted a link to a test4 image in OP. I enabled MTP and fixed bind mount to /sdcard from /data/media/0.