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

[RECOVERY] TWRP 3.5.0_10-0 - TeamWin Recovery Project [REDFIN] [TESTING]

Search This thread

ominouswanderer

New member
Aug 19, 2012
3
0
Appreciate the response!

I'm trying to reflash the factory image and not sure how to do so. I downloaded both the basic firmware image-redfin-rd1a.200810.022.a4 as well as the OTA redfin-ota-rq3a.210905.001-1843e067 and my issue is that I can't figure out how to get to ADB Sideload. I am having issues loading TWRP, and the default recovery mode isn't working since it had installed the newer version of TWRP which doesn't have the touch support.

Is there an alternative way to flash the whole factory image via fastboot or a way that I can get ADB sideload working again?
 

hunfatal

Senior Member
Nov 10, 2011
740
453
Budapest
OnePlus X
Google Pixel 5
Appreciate the response!

I'm trying to reflash the factory image and not sure how to do so. I downloaded both the basic firmware image-redfin-rd1a.200810.022.a4 as well as the OTA redfin-ota-rq3a.210905.001-1843e067 and my issue is that I can't figure out how to get to ADB Sideload. I am having issues loading TWRP, and the default recovery mode isn't working since it had installed the newer version of TWRP which doesn't have the touch support.

Is there an alternative way to flash the whole factory image via fastboot or a way that I can get ADB sideload working again?
You don't need the OTA image, and also you don't need sideload.

You download the full factory image from here (this is the latest, september security patch version), unpack it, put the phone into fastboot and run flash-all.bat (windows) or flash-all.sh (linux).

Note that this will erase the phone, so as I mentioned in the earlier post, all data will be lost.
 
  • Like
Reactions: andybones

ominouswanderer

New member
Aug 19, 2012
3
0
I really appreciate the continued help. I downloaded the zip and ran flash-all.bat and am getting an error message. Full log below, any ideas?

Code:
target reported max download size of 268435456 bytes
sending 'bootloader' (8754 KB)...
OKAY [  0.310s]
writing 'bootloader'...
(bootloader) Flashing Pack version r3-0.3-7241848
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition uefisecapp_a
(bootloader) Flashing partition featenabler_a
(bootloader) Flashing partition logfs
OKAY [  0.323s]
finished. total time: 0.636s
rebooting into bootloader...
OKAY [  0.050s]
finished. total time: 0.052s
< waiting for device >
target reported max download size of 268435456 bytes
sending 'radio' (149780 KB)...
OKAY [  3.577s]
writing 'radio'...
(bootloader) Flashing Pack version SSD:g7250-00132-210419-B-7294132
(bootloader) Flashing partition modem_a
OKAY [  0.553s]
finished. total time: 4.132s
rebooting into bootloader...
OKAY [  0.050s]
finished. total time: 0.052s
error: failed to load 'image-redfin-rq3a.210905.001.zip': Not enough space
Press any key to exit...
 

dragynbane222

Senior Member
Jul 2, 2012
190
66
Google Pixel 4 XL
Google Pixel 5
I really appreciate the continued help. I downloaded the zip and ran flash-all.bat and am getting an error message. Full log below, any ideas?

Code:
target reported max download size of 268435456 bytes
sending 'bootloader' (8754 KB)...
OKAY [  0.310s]
writing 'bootloader'...
(bootloader) Flashing Pack version r3-0.3-7241848
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition uefisecapp_a
(bootloader) Flashing partition featenabler_a
(bootloader) Flashing partition logfs
OKAY [  0.323s]
finished. total time: 0.636s
rebooting into bootloader...
OKAY [  0.050s]
finished. total time: 0.052s
< waiting for device >
target reported max download size of 268435456 bytes
sending 'radio' (149780 KB)...
OKAY [  3.577s]
writing 'radio'...
(bootloader) Flashing Pack version SSD:g7250-00132-210419-B-7294132
(bootloader) Flashing partition modem_a
OKAY [  0.553s]
finished. total time: 4.132s
rebooting into bootloader...
OKAY [  0.050s]
finished. total time: 0.052s
error: failed to load 'image-redfin-rq3a.210905.001.zip': Not enough space
Press any key to exit...
How much ram and free disk space do you have on that PC? that specific error is local to the PC and refers to not having enough space in either temporary storage or disk space. Depending on if you're on Linux or Windows, temporary storage with either be on the disk itself on Windows or in a Ramdisk in what's known as tmpfs in Linux.
 
  • Like
Reactions: andybones
I think you should reflash the whole factory image (you will lose data) and it will work.
There's some things to try first.

Download and extract the factory image > RQ3A.210905

Reflash the bootloader:
Code:
fastboot flash bootloader bootloader-redfin-r3-0.3-7241848.img
fastboot reboot-bootloader

Reflash radio just to be safe:
Code:
fastboot flash radio radio-redfin-g7250-00132-210419-b-7294132.img
fastboot reboot-bootloader

Lastly, try updating the image without wiping:
Code:
fastboot update image-redfin-rq3a.210905.001.zip
**DO NOT USE THE -W SWITCH, that triggers the factory reset**

If everything flashes successfully, the phone should boot into system.

I do not recommend installing TWRP; just boot it temporarily for flashing files, but don't flash it to /boot.
 

andybones

Forum Moderator
Staff member
May 18, 2010
14,706
14,974
Google Pixel 5
Does it work on A11? As far as say, making a nandroid of my stock (encrypted) ROM and being able to restore?
I can't recall if this was ever answered, from what I see.

thank you
 
Does it work on A11? As far as say, making a nandroid of my stock (encrypted) ROM and being able to restore?
I can't recall if this was ever answered, from what I see.

thank you
Depends on what you mean by "work". As of test 5, this has been working to decrypt and flash on Android 11; I've been using it to install the OTAs and reflash Magisk.

I did try to use the nandroid backup when I went to a custom ROM; it didn't work for me.
 
  • Like
Reactions: andybones

andybones

Forum Moderator
Staff member
May 18, 2010
14,706
14,974
Google Pixel 5
Depends on what you mean by "work". As of test 5, this has been working to decrypt and flash on Android 11; I've been using it to install the OTAs and reflash Magisk.

I did try to use the nandroid backup when I went to a custom ROM; it didn't work for me.
Sorry should had been more informative, but you answered it anyway!
I mean't, could I, on my rooted, encrypted A11 P5, take a nandroid, and If I was hit with the pixel is starting bug or any other reason, and had to factory reset, would I be able to restore that previous nandroid.
Appreciate the infos!
 

bigbiff

Senior Recognized Developer
Jun 8, 2010
6,879
7,093
Depends on what you mean by "work". As of test 5, this has been working to decrypt and flash on Android 11; I've been using it to install the OTAs and reflash Magisk.

I did try to use the nandroid backup when I went to a custom ROM; it didn't work for me.
Can you post the logs?

From my testing as long as you don't hose FBE, restore works great for me.
 
  • Like
Reactions: andybones

vandyman

Senior Member
Jul 30, 2012
430
133
S.Jersey
Google Pixel 5
Google Pixel 6
Attempted to boot TWRP test 9 on the Android 12 beta. No joy - stays stuck on the TWRP screen, does not reach decrypt. ADB communication works, able to reboot to bootloader.

Followed this guide to manually flash the patched boot.img...wouldn't boot, although I didn't use canary, so I'm about to go try that now.
I tried the same as you did with stable v23.
As I said above, I am thinking that magisk has to be uninstalled. But if magisk gets hosed in the process, magisk will not install again without a complete wipe. At least for me.

If anyone knows how to uninstall magisk using adb ,please let me know.
 
Update:

TWRP does not currently work with the 12 Beta, with the exception of ADB access.

The only way I've been able to boot with root is by temporarily booting the Magisk patched boot.img while leaving the stock boot image intact.

Update: After using the flash tool with verity and verification disabled, I was able to flash the patched boot.img, and am now on rooted 12 beta 5.

Attempting to boot TWRP just results in the TWRP loading screen with ADB connectivity.
 
Last edited:
  • Like
Reactions: vandyman

bigbiff

Senior Recognized Developer
Jun 8, 2010
6,879
7,093
Update:

TWRP does not currently work with the 12 Beta, with the exception of ADB access.

The only way I've been able to boot with root is by temporarily booting the Magisk patched boot.img while leaving the stock boot image intact.

Update: After using the flash tool with verity and verification disabled, I was able to flash the patched boot.img, and am now on rooted 12 beta 5.

Attempting to boot TWRP just results in the TWRP loading screen with ADB connectivity.
TWRP 12 isn't even WIP. TWRP 11 will be done soon. It's taken about a year to implement A11 requirements.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Except I'm not wrong. It's clear that my comments have been misunderstood. I'm not responsible for that.

    Because, despite my having explained multiple times that I was doing it correctly, he continued to insist that I was doing it wrong, or that I'm just wrong period. My point was that not everyone has the same experiences, and my experience has been such that I cannot boot with TWRP installed to ramdisk AND Magisk installed to /boot. This has been a known problem ever since the Pixel 2.

    Again, you misunderstood. Go read my post again. I specifically explained what each command does and what the outcome is. If you flash TWRP to /boot, that will be all you have in /boot - no kernel. Therefore, every time your phone tries to boot, it will only boot into TWRP.

    Therefore, the only correct way to get into TWRP (at least the first time) is to live boot it via ADB, at which time you can install it to ramdisk - but only if you're on Android 11, because on the 12 Beta, TWRP just boots to the TWRP logo.

    As far as bricking, as far as I know it's nearly impossible to brick these phones by erasing or flashing a bad image to /boot. You'll just be stuck in bootloader, and the only thing you'd have to do is flash a good boot image.

    If you screw up the bootloader on the other hand...yeah, you're probably screwed, unless you're handy with JTAG and willing to tear your phone apart.
    Again, let's ALL play nice.
    Ok, So you were not wrong (which I never said you were), but rather misunderstood..
    I don't need to go back and re-read your post. I understand the confusion.. It's when I get a PM about that confusion, and then I see another user making a post about it.

    Clearing up the confusion is good though, many times, needed.

    And feedback is also good.
    It works for him and not you.
    Talking it out like adults, though, just may, get us to the root of why it's working for one and not the other.
    Correct, the OG Droid actually had a /recovery partition, as did every other device I used up until I went Google and got the Pixel 2 almost 4 years ago.

    No. That's not what I'm doing, and I've explained in detail multiple times what happens if TWRP is flashed to /boot.
    And I think it's best for others who come into this thread to not have to be confused about the flashing to the boot partition.
    As we know, It should be booted, fastboot boot twrp.img and let's stick to that, otherwise we are approaching off-topic.
    1
    And all @ziand did was give information, after saying you were wrong. And he's within his right to say that you posted incorrect information (nicely), while backing it up, which he did..
    Except I'm not wrong. It's clear that my comments have been misunderstood. I'm not responsible for that.
    However, I'm confused why you're telling him he's being obnoxious and to give it a rest..
    Because, despite my having explained multiple times that I was doing it correctly, he continued to insist that I was doing it wrong, or that I'm just wrong period. My point was that not everyone has the same experiences, and my experience has been such that I cannot boot with TWRP installed to ramdisk AND Magisk installed to /boot. This has been a known problem ever since the Pixel 2.
    And I've been confused myself since this fastboot flash boot twrp.img command was posted.
    I'd really like not to see anyone bricking their devices.
    And I'm not saying flashing twrp.img to the boot partition would brick anything, I don't know for sure, but confusion when flashing the wrong .img to a partition is how it happens.
    Again, you misunderstood. Go read my post again. I specifically explained what each command does and what the outcome is. If you flash TWRP to /boot, that will be all you have in /boot - no kernel. Therefore, every time your phone tries to boot, it will only boot into TWRP.

    Therefore, the only correct way to get into TWRP (at least the first time) is to live boot it via ADB, at which time you can install it to ramdisk - but only if you're on Android 11, because on the 12 Beta, TWRP just boots to the TWRP logo.

    As far as bricking, as far as I know it's nearly impossible to brick these phones by erasing or flashing a bad image to /boot. You'll just be stuck in bootloader, and the only thing you'd have to do is flash a good boot image.

    If you screw up the bootloader on the other hand...yeah, you're probably screwed, unless you're handy with JTAG and willing to tear your phone apart.
    1
    Context matters, though. When I posted that, I was specifically pointing out that it's the wrong thing to do on our devices, as it overwrites /boot. Someone else had mentioned only being able to boot into TWRP, the likely cause of which being that they had done exactly what I described.
    Well it's usually best not to make assumptions, but I see your point here.
    Context absolutely does matter, couldn't agree with you more.
    But you being upset (understandably ofc, and you are always free to report ANY post you wish), I feel this deserved my time spent on doing my best to alleviate any issues.

    Just one of the great things of XDA is the XenForo update.
    And the first time you made the post with the fastboot flash boot twrp.img was post #158 and you can see I actually "Liked" that way back on Jul 21, 2021. (ie I didn't do it today, and trying to say I did it before this discussion).
    The post which I *think* was the root of confusion comes from your post #209 --however, I can't say for certain, but I don't think it really is a matter anymore as I feel it's cleared up, but if not feel free to let me know.

    I appreciate you responding level-headed, and filling me in with the information you did, and why you had responded the way you had.
    This will help someone down the line, and that's how these forums *should* work. Or at least it's how I like to see them go.
    Again, I'm sorry you felt irked. But being an adult about how you respond, makes more of a difference, because had you gotten more upset, responded rudely or worse, then maybe your post would be reported, and I don't want to see that.

    Context contributes to learning. (y)
    1
    Well, I'm 34, so I don't have time to waste getting in online pissing matches.

    Back to the topic at hand:

    As I stated previously, installing TWRP to ramdisk with Magisk installed on the stock kernel always resulted in a boot loop for me. I didn't try this on custom kernels. The reason for this, and I'm heavily paraphrasing here, is something about Magisk on Android 11 made it not play nice with TWRP in ramdisk. Was I the only one with this issue?

    Also, do we know what the issue is with TWRP and Android 12? Is it as simple as needing to be ported over?
  • 56
    [RECOVERY] TWRP 3.5.0_10-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

    Hello, this is a test build for redfin users

    Decryption is working. Touch, adb and flashing magisk works. Repacking works. I am currently working on fastbootd support.

    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.