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

Search This thread
By:
Advanced…
O

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?
 
H

hunfatal

Senior Member
Nov 10, 2011
830
628
Budapest
OnePlus X
Google Pixel 5
ominouswanderer said:
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?
Click to expand...
Click to collapse
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
O

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

dragynbane222

Senior Member
Jul 2, 2012
228
102
Google Pixel 4 XL
Google Pixel 5
ominouswanderer said:
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...
Click to expand...
Click to collapse
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
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
10,299
5
18,207
The Heartland of America
Google Pixel 5
Google Pixel 5a
hunfatal said:
I think you should reflash the whole factory image (you will lose data) and it will work.
Click to expand...
Click to collapse
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.
 
  • Like
Reactions: andybones and hunfatal
andybones

andybones

Retired Forum Moderator / Inactive RD
May 18, 2010
15,092
15,480
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
 
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
10,299
5
18,207
The Heartland of America
Google Pixel 5
Google Pixel 5a
andybones said:
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
Click to expand...
Click to collapse
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

andybones

Retired Forum Moderator / Inactive RD
May 18, 2010
15,092
15,480
Google Pixel 5
V0latyle said:
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.
Click to expand...
Click to collapse
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!
 
B

bigbiff

Senior Recognized Developer
Jun 8, 2010
6,964
7,245
V0latyle said:
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.
Click to expand...
Click to collapse
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

vandyman

Senior Member
Jul 30, 2012
870
478
S.Jersey
Moto G 5G
Google Pixel 6
V0latyle said:
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.
Click to expand...
Click to collapse
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.
 
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
10,299
5
18,207
The Heartland of America
Google Pixel 5
Google Pixel 5a
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
B

bigbiff

Senior Recognized Developer
Jun 8, 2010
6,964
7,245
V0latyle said:
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.
Click to expand...
Click to collapse
TWRP 12 isn't even WIP. TWRP 11 will be done soon. It's taken about a year to implement A11 requirements.
 
  • Like
Reactions: elong7681 and Homeboy76
You must log in or register to reply here.

Similar threads

aleasto
[ROM][OFFICIAL][redfin] LineageOS 20
Replies
1K
Views
165K
M
maddvector
kdrag0n
ROM ❯ PIXEL 5 ❯ OFFICIAL ❯ ProtonAOSP 11
Replies
840
Views
154K
aosp_cat
aosp_cat
dabug123
[ROM][OFFICIAL][Android 11]ScorpionROM v4.7[Google Pixel 5][Redfin]
Replies
164
Views
48K
G
ghost9640
Sukrut4778
[ROM][14.0.0_r25][redfin][OFFICIAL] Evolution X [02/11/24]
Replies
295
Views
44K
H
hk25
H
[ROM][13/12.1/11][UNOFFICIAL][redfin] crDroid v9.15/v8.20/v7.39
Replies
441
Views
52K
H
hunfatal

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 65
    B
    bigbiff
    [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

    GitHub - bigbiff/android_device_google_redfin

    Contribute to...
    github.com github.com

    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
    View
    23
    B
    bigbiff
    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.
    View
    22
    B
    bigbiff
    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.
    View
    20
    B
    bigbiff
    JoshuaDoes said:
    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
    Click to expand...
    Click to collapse

    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
    View
    18
    B
    bigbiff
    I posted a link to a test4 image in OP. I enabled MTP and fixed bind mount to /sdcard from /data/media/0.
    View

New posts