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

Search This thread

theg00dguy

Member
Apr 7, 2022
12
1
Hi,

I have just got myself a Pixel 5 with Android 11 on it. I used to have a Pixel 2 on which I boot TWRP using ADB to make Nandroid backups. I'd like to do the same with the Pixel 5.

I have dowloaded twrp-installer-3.7.0_11-0-redfin.zip from the TWRP Pixel5 site. I was expecting to find a twrp.img file in the archive, but there isn't. There's "magiskboot" and "ramdisk-twrp.cpio". I have hunted high and low, but I cannot find any guidance on what to do with these files.

I read that a cpio file is an archive file of some sort, but I could find any way to unarchive it to see if the twrp.img file is within. The installation instructions on the TWRP Pixel5 site says to "run the following command: fastboot boot path/to/twrp.img", but where is this img file?

Any help would be gratefully recieved.

Thanks.

I am so sorry. I am blind as a bat and as thick as two short planks. The img file is right in front of me to download and did not see it.
 

HippoMan

Senior Member
May 5, 2009
2,160
938
Hippoland
You can download the *.img file from here:
Hi,

I have just got myself a Pixel 5 with Android 11 on it. I used to have a Pixel 2 on which I boot TWRP using ADB to make Nandroid backups. I'd like to do the same with the Pixel 5.

I have dowloaded twrp-installer-3.7.0_11-0-redfin.zip from the TWRP Pixel5 site. I was expecting to find a twrp.img file in the archive, but there isn't. There's "magiskboot" and "ramdisk-twrp.cpio". I have hunted high and low, but I cannot find any guidance on what to do with these files.

I read that a cpio file is an archive file of some sort, but I could find any way to unarchive it to see if the twrp.img file is within. The installation instructions on the TWRP Pixel5 site says to "run the following command: fastboot boot path/to/twrp.img", but where is this img file?

Any help would be gratefully recieved.

Thanks.
You can download the *.img file from here:
https://dl.twrp.me/redfin/
 

Durchmesser

Member
Oct 14, 2015
44
2
I running a LineageOS with Lineageos Recovery. I got the hint that I should be able to boot twrp without installing it with
Code:
fastboot boot twrp.img
My goal is to make a full Image of the Phone so I could play with other systems and switch back If I do not like them.

If I reboot to bootloader ant than run that command TWRP seems boot ing but never skip from bootscreen to the main menu. I tested this with twrp 3.6 and 3.7.

Any Idea how to temporary boot twrp?
 

manjaroid

Senior Member
Jun 25, 2019
346
161
I running a LineageOS with Lineageos Recovery. I got the hint that I should be able to boot twrp without installing it with
Code:
fastboot boot twrp.img
My goal is to make a full Image of the Phone so I could play with other systems and switch back If I do not like them.

If I reboot to bootloader ant than run that command TWRP seems boot ing but never skip from bootscreen to the main menu. I tested this with twrp 3.6 and 3.7.

Any Idea how to temporary boot twrp?
Which LOS release? If 20 the result you got is expected. You'll need 19 to boot TWRP.
 

Durchmesser

Member
Oct 14, 2015
44
2
Sorry I do not understand. I thought that It is not important which system is installed, If I only plan to boot the twrp temporary. I mentioned lineageos only to made it clear that TWRP is not installed.

My goal is to test several Rom like Graphene OS and other but be able to revert to my current system without loosing anything.
My plan was:
  1. boot twrp
  2. Backup all Partition to USB disk
  3. Flash another ROM
  4. Test it
  5. boot twrp again and restore the Backup
 

manjaroid

Senior Member
Jun 25, 2019
346
161
...I thought that It is not important which system is installed...
I wish that were the case but only Android 11 is fully supported meaning all TWRP releases for redfin can be installed to replace stock recovery and not just booted. TWRP 3.7.0 can be booted with Android 12 but not installed. TWRP isn't ready at all for 13.

I understand your goals and some are workable while others may not be. For example, if you're interested in Graphene you should follow the official installation instructions. ROMs made to be TWRP flashable are another story.
 

manjaroid

Senior Member
Jun 25, 2019
346
161
I was not planing to install Graphene with TWRP only the Backup and restore of my Lineageos.
I gotcha. Before yesterday I would have bet money that a Pixel 5 running LOS 19 would boot from TWRP 3.7.0. If it's supposed to but won't, one thing to consider is the fastboot version. Late releases have problems once the phone is in fastboot mode but 33.03 doesn't have the problem.
 

Durchmesser

Member
Oct 14, 2015
44
2
My Fastboot is the native version:

Code:
fastboot version 29.0.6-debian
Installed as /usr/lib/android-sdk/platform-tools/fastboot

Because the command worked and uploaded the Image, I never had the Idea that the fastboot version may could be the culprit.

I check if I may could update it.
 

Homeboy76

Recognized Contributor
Aug 24, 2012
3,868
2,310
Google Pixel XL
Google Pixel 7 Pro
My Fastboot is the native version:

Code:
fastboot version 29.0.6-debian
Installed as /usr/lib/android-sdk/platform-tools/fastboot

Because the command worked and uploaded the Image, I never had the Idea that the fastboot version may could be the culprit.

I check if I may could update it.
@Durchmesser, remove this version fastboot version 29.0.6-debian, Installed as /usr/lib/android-sdk/platform-tools/fastboot before installing the Linux version r. 33.0.3.

This may help you install SDK Platform-tools r. 33.0.3: How to install ADB on Windows, macOS, and Linux - Scroll down to, How to set up ADB on Linux.

Windows - SDK Platform-tools r. 33.0.3

Linux - SDK Platform-tools r. 33.0.3 is attached.
 

Attachments

  • platform-tools_r33.0.3-linux.zip
    7.2 MB · Views: 8
Last edited:
  • Like
Reactions: Durchmesser

Yeedatoy

Senior Member
Jul 18, 2018
363
151
38
Charlotte
AT&T HTC One X
Moto G6
Sorry I do not understand. I thought that It is not important which system is installed, If I only plan to boot the twrp temporary. I mentioned lineageos only to made it clear that TWRP is not installed.

My goal is to test several Rom like Graphene OS and other but be able to revert to my current system without loosing anything.
My plan was:
  1. boot twrp
  2. Backup all Partition to USB disk
  3. Flash another ROM
  4. Test it
  5. boot twrp again and restore the Backup
Why go through that trouble? Just install the Dsu side loader app, boot GSIs of the roms you want to test? You still have your current ROM and data, and you can enable sticky mode to stay in the other rom as long as you'd like. You keep root, and you can even leave the GSI installed permanently and have an almost fully functional dual boot with the exception of some technicalities
 

NetSpeedZ

Senior Member
Dec 9, 2012
120
8
Southwest USA
I wish that were the case but only Android 11 is fully supported meaning all TWRP releases for redfin can be installed to replace stock recovery and not just booted. TWRP 3.7.0 can be booted with Android 12 but not installed. TWRP isn't ready at all for 13.

I understand your goals and some are workable while others may not be. For example, if you're interested in Graphene you should follow the official installation instructions. ROMs made to be TWRP flashable are another story.
Hello - Just wanted to confirm comment regarding TWRP not currently compatible with Android 13. Confirmation on this would be appreciated.

I recently updated from 11 to 13 (on Pixel 5 - stock, rooted) and realized that I was unable to either boot temporarily to TWRP image or install it. I really only used TWRP to make nandroid backups and then copy those out to my computer for additional backup - if TWRP is currently not compatible with Android 13, the only backup I have is apps/data (to a Google Drive) - not the entire phone.

I knew there was a reason I didn't want to upgrade to 13 - just got tired of the weekly 'nag' screen to update. Should have relied on the old addage 'if it's not broke, don't fix it' :)
 
  • Like
Reactions: HippoMan

HippoMan

Senior Member
May 5, 2009
2,160
938
Hippoland
Hello - Just wanted to confirm comment regarding TWRP not currently compatible with Android 13. Confirmation on this would be appreciated.

I recently updated from 11 to 13 (on Pixel 5 - stock, rooted) and realized that I was unable to either boot temporarily to TWRP image or install it. I really only used TWRP to make nandroid backups and then copy those out to my computer for additional backup - if TWRP is currently not compatible with Android 13, the only backup I have is apps/data (to a Google Drive) - not the entire phone.

I knew there was a reason I didn't want to upgrade to 13 - just got tired of the weekly 'nag' screen to update. Should have relied on the old addage 'if it's not broke, don't fix it' :)
Yes. In my experience, every upgrade of Android lately makes the OS less user-friendly.

I stayed on Android 10 for a long time, even after Android 13 came out. Then, using a custom ROM, I was able to get up to Android 11 with a usable version of TWRP, but I don't plan to upgrade again any time in the foreseeable future.
 
Last edited:
  • Like
Reactions: Hiero and NetSpeedZ

manjaroid

Senior Member
Jun 25, 2019
346
161
Just wanted to confirm comment regarding TWRP not currently compatible with Android 13. Confirmation on this would be appreciated.
I see why my comment wasn't clear because I left out the word "not". At the time I thought I was saying "...only Android 11 is fully supported meaning not all TWRP releases for redfin can be installed..." Sorry about that.

The rest I believe is correct if not written clearly. Read this thread backward to confirm that TWRP isn't ready for Android 13 on Pixel 5 and won't even boot; TWRP 3.7.0 is partially ready for Android 12 in that it boots but can't be installed; for Android 11 TWRP works fully since its first release.
 

NetSpeedZ

Senior Member
Dec 9, 2012
120
8
Southwest USA
I see why my comment wasn't clear because I left out the word "not". At the time I thought I was saying "...only Android 11 is fully supported meaning not all TWRP releases for redfin can be installed..." Sorry about that.

The rest I believe is correct if not written clearly. Read this thread backward to confirm that TWRP isn't ready for Android 13 on Pixel 5 and won't even boot; TWRP 3.7.0 is partially ready for Android 12 in that it boots but can't be installed; for Android 11 TWRP works fully since its first release.
Appreciate the clarification.
 

Top Liked Posts

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