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

Search This thread

bigbiff

Senior Recognized Developer
Jun 8, 2010
6,813
6,891
[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 not working yet. Touch, adb and flashing magisk works. I have not tested repacking yet since decryption doesn't work yet.

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

Download here: 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.

http://twrp.me
 

mistermojorizin

Senior Member
Dec 21, 2011
815
174
This boots on a pixel 4a5g, but touch controls and adb do not seem to work. Do you think it would take a lot of code changes to enable it on the 4a 5g? The two phones share kernels for what it's worth.
 

mistermojorizin

Senior Member
Dec 21, 2011
815
174
Can you provide me a copy of dmesg?

To get a dmesg, I need to use ADB (which doesn't work while booted into TWRP). So would this capture the info you'd need - boot into TWRP, reboot by holding power button, get a dmesg when it boots?

EDIT: so I'm trying to get it this way but the dmesg.txt comes out blank for some reason
 
Last edited:

bigbiff

Senior Recognized Developer
Jun 8, 2010
6,813
6,891
To get a dmesg, I need to use ADB (which doesn't work while booted into TWRP). So would this capture the info you'd need - boot into TWRP, reboot by holding power button, get a dmesg when it boots?

EDIT: so I'm trying to get it this way but the dmesg.txt comes out blank for some reason

Unfortunately that would be from the android kernel. I didn't realize adb wasn't working for you. Are you using windows?
 

mistermojorizin

Senior Member
Dec 21, 2011
815
174
Unfortunately that would be from the android kernel. I didn't realize adb wasn't working for you. Are you using windows?
yes, windows 10, latest adb drivers. when it boots to TWRP it doesn't recognize that any adb devices are connected.

when booting to android though, I can access ADB without problems
 

mistermojorizin

Senior Member
Dec 21, 2011
815
174
I was able to get touch working on the 4a5g using these commands:

fastboot flash boot twrp-3.5.0-0-test1-redfin.img
fastboot boot ProtonKernel-pixel5-v1.1.img

ADB Still didn't work. The log said couldn't mount storage. Under "mount" I could check every box except the last two (storage and external storage or sdcard I think).

the backup menu is very different looking than i'm used to. instead of being able to select which partitions to backup, there's only one option - "super (vendor, system, system ext...etc)" The only partition that's not listed there is the boot partition. Also, storage says 0mb . Not sure if it would have backed up anything.

Is it able to make backups on the Pixel 5? Can I get you any info (using the TWRP terminal or file manager mayber) to help development?
 

bigbiff

Senior Recognized Developer
Jun 8, 2010
6,813
6,891
I was able to get touch working on the 4a5g using these commands:

fastboot flash boot twrp-3.5.0-0-test1-redfin.img
fastboot boot ProtonKernel-pixel5-v1.1.img

ADB Still didn't work. The log said couldn't mount storage. Under "mount" I could check every box except the last two (storage and external storage or sdcard I think).

the backup menu is very different looking than i'm used to. instead of being able to select which partitions to backup, there's only one option - "super (vendor, system, system ext...etc)" The only partition that's not listed there is the boot partition. Also, storage says 0mb . Not sure if it would have backed up anything.

Is it able to make backups on the Pixel 5? Can I get you any info (using the TWRP terminal or file manager mayber) to help development?

The super partition and other partitions you can backup as byte images. However most of these can be restored from the stock firmware. I am working on decryption right now. I am not sure what to do about adb unless you can pull logcat and dmesg for clues for the 4a5g.
 

Top Liked Posts

  • 3
    I have flashed TWRP ,,, now problem No OS installed on A/B slot??
    You'll have to re flash the factory boot image.

    The Pixel phones do not have a recovery partition; if you flash TWRP, you overwrite /boot. The only way to use TWRP is to live boot via ADB.

    In the case of the Pixel 5, since decryption and MTP aren't working, TWRP is more or less useless for the time being.
  • 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
    5
    On the note of bramble, thought I could get away with cherry-picking your redbull patches into the new Lineage trees for bramble and replacing recovery with TWRP, but my final stopping point for the night is an ambiguous keystore include error that I'm too tired to figure out. If I shouldn't be trying to build TWRP in a lineage-18.1 tree right now, should I be in an OmniROM tree or some other hacky setup? I'm determined to make in-tree bramble builds of TWRP either once a repo is available or making the repo myself, because I wanna help fix any remaining issues :p
    Right now I am using aosp11 with modified repos only for twrp.
    3
    Thank you for your time and attention.
    3
    I have flashed TWRP ,,, now problem No OS installed on A/B slot??
    You'll have to re flash the factory boot image.

    The Pixel phones do not have a recovery partition; if you flash TWRP, you overwrite /boot. The only way to use TWRP is to live boot via ADB.

    In the case of the Pixel 5, since decryption and MTP aren't working, TWRP is more or less useless for the time being.
    2
    On the note of bramble, thought I could get away with cherry-picking your redbull patches into the new Lineage trees for bramble and replacing recovery with TWRP, but my final stopping point for the night is an ambiguous keystore include error that I'm too tired to figure out. If I shouldn't be trying to build TWRP in a lineage-18.1 tree right now, should I be in an OmniROM tree or some other hacky setup? I'm determined to make in-tree bramble builds of TWRP either once a repo is available or making the repo myself, because I wanna help fix any remaining issues :p
  • 41
    [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 not working yet. Touch, adb and flashing magisk works. I have not tested repacking yet since decryption doesn't work yet.

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

    Download here: 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.

    http://twrp.me
    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
    8
    I was able to get touch working on the 4a5g using these commands:

    fastboot flash boot twrp-3.5.0-0-test1-redfin.img
    fastboot boot ProtonKernel-pixel5-v1.1.img

    ADB Still didn't work. The log said couldn't mount storage. Under "mount" I could check every box except the last two (storage and external storage or sdcard I think).

    the backup menu is very different looking than i'm used to. instead of being able to select which partitions to backup, there's only one option - "super (vendor, system, system ext...etc)" The only partition that's not listed there is the boot partition. Also, storage says 0mb . Not sure if it would have backed up anything.

    Is it able to make backups on the Pixel 5? Can I get you any info (using the TWRP terminal or file manager mayber) to help development?

    The super partition and other partitions you can backup as byte images. However most of these can be restored from the stock firmware. I am working on decryption right now. I am not sure what to do about adb unless you can pull logcat and dmesg for clues for the 4a5g.
    5
    On the note of bramble, thought I could get away with cherry-picking your redbull patches into the new Lineage trees for bramble and replacing recovery with TWRP, but my final stopping point for the night is an ambiguous keystore include error that I'm too tired to figure out. If I shouldn't be trying to build TWRP in a lineage-18.1 tree right now, should I be in an OmniROM tree or some other hacky setup? I'm determined to make in-tree bramble builds of TWRP either once a repo is available or making the repo myself, because I wanna help fix any remaining issues :p
    Right now I am using aosp11 with modified repos only for twrp.
    5
    Setting sys.usb.configfs to 1 on init enabled adb on the 4a 5G.

    Updated logs:
    dmesg: https://pastebin.com/dJwVQjyb
    recovery: https://pastebin.com/EEZAkAei
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone