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

Search This thread

mindyabiznis

Senior Member
Oct 16, 2011
363
51
Quick question... Asking for a friend.

What would happen if someone was to

fastboot flash recovery twrp-3.5.0.0.img

Is that fixable? As it seems his phone will only boot to TWRP no matter what he does, when in TWRP there is ability to see root folders but no files, no access to sdcard storage, nothing.

Managed to reboot into OS with fastboot boot protonkernel5-v1.3.img from bootloader as installing a fresh kernel like clean slate or elementalx just causes the same problem.

But as soon as the phones restarted it boots TWRP

Is the phone bricked?

Edit: tried fastboot boot stock kernel, still have same problem.

When he did the initial fastboot flash recovery it said failed yet it's done something
 
Last edited:

GTDarthYoda

Senior Member
Jul 1, 2012
665
189
Quick question... Asking for a friend.

What would happen if someone was to

fastboot flash recovery twrp-3.5.0.0.img

Is that fixable? As it seems his phone will only boot to TWRP no matter what he does, when in TWRP there is ability to see root folders but no files, no access to sdcard storage, nothing.

Managed to reboot into OS with fastboot boot protonkernel5-v1.3.img from bootloader as installing a fresh kernel like clean slate or elementalx just causes the same problem.

But as soon as the phones restarted it boots TWRP

Is the phone bricked?

Edit: tried fastboot boot stock kernel, still have same problem.

When he did the initial fastboot flash recovery it said failed yet it's done something
Just remembered, kernel/recovery/boot I believe are all the same.
I attached the latest boot.img from the link I posted, try this.
fastboot flash recovery boot.img

Also link came from here. May update for the Pixel 5.
 
  • Like
Reactions: mindyabiznis

mindyabiznis

Senior Member
Oct 16, 2011
363
51
Just remembered, kernel/recovery/boot I believe are all the same.
I attached the latest boot.img from the link I posted, try this.
fastboot flash recovery boot.img

Also link came from here. May update for the Pixel 5.
See this is what I thought would work, but it didn't fix the problem.

What I got him to do was fastboot erase boot which stopped the TWRP from causing the bootloop, but it caused "no valid boot slot"

So then got him to extract the radio and bootloader file from latest stock image from Google, then fastboot flash --slot=all flash bootloader - drag and drop file into cmd

Fastboot reboot bootloader

Fastboot --slot=all flash radio - drag and drop file into cmd

Fastboot reboot bootloader

Boot into system - failed, so back into bootloader

Fastboot boot protonkernel

Booted into OS

Test reboot, bootloop into bootloader

Fastboot boot magisk patched protonkernel.img

Get into OS but lose root regular reboot so fastboot boot magisk patched proton kernel

Once in OS flash directly from magisk as it seems he had some sort of temp/half root

What a ballache, but thanks ever so much for your quick response and help though @GTDarthYoda you're an absolute star
 
Last edited:

mindyabiznis

Senior Member
Oct 16, 2011
363
51
Could someone please tell me where abouts the Magisk.apk file should go so when in TWRP it can be found and flashed? To finalise everything

never mind, found it

/media

Dragged and dropped from pc and flashed from there.
 
Last edited:

V0latyle

Senior Member
Feb 20, 2011
696
127
Google Pixel 5
See this is what I thought would work, but it didn't fix the problem.

What I got him to do was fastboot erase boot which stopped the TWRP from causing the bootloop, but it caused "no valid boot slot"

So then got him to extract the radio and bootloader file from latest stock image from Google, then fastboot flash --slot=all flash bootloader - drag and drop file into cmd

Fastboot reboot bootloader

Fastboot --slot=all flash radio - drag and drop file into cmd

Fastboot reboot bootloader

Boot into system - failed, so back into bootloader

Fastboot boot protonkernel

Booted into OS

Test reboot, bootloop into bootloader

Fastboot boot magisk patched protonkernel.img

Get into OS but lose root regular reboot so fastboot boot magisk patched proton kernel

Once in OS flash directly from magisk as it seems he had some sort of temp/half root

What a ballache, but thanks ever so much for your quick response and help though @GTDarthYoda you're an absolute star
If booting the kernel boots into system, you should be able to use
Code:
fastboot flash boot boot.img

Where "boot.img" is either the stock boot image, or the kernel
 

V0latyle

Senior Member
Feb 20, 2011
696
127
Google Pixel 5
See this is what I thought would work, but it didn't fix the problem.

What I got him to do was fastboot erase boot which stopped the TWRP from causing the bootloop, but it caused "no valid boot slot"

So then got him to extract the radio and bootloader file from latest stock image from Google, then fastboot flash --slot=all flash bootloader - drag and drop file into cmd

Fastboot reboot bootloader

Fastboot --slot=all flash radio - drag and drop file into cmd

Fastboot reboot bootloader

Boot into system - failed, so back into bootloader

Fastboot boot protonkernel

Booted into OS

Test reboot, bootloop into bootloader

Fastboot boot magisk patched protonkernel.img

Get into OS but lose root regular reboot so fastboot boot magisk patched proton kernel

Once in OS flash directly from magisk as it seems he had some sort of temp/half root

What a ballache, but thanks ever so much for your quick response and help though @GTDarthYoda you're an absolute star
If booting the kernel boots into system, you should be able to use
Code:
fastboot flash boot boot.img

where "boot.img" is the stock boot image or the custom kernel
 
  • Like
Reactions: mindyabiznis

mindyabiznis

Senior Member
Oct 16, 2011
363
51
I don't know if this has already been addressed but I cannot see any phone files when booted into TWRP.

The only files I can see and use/flash are in data/media.

Is this because of the encryption not fully working or?

I don't have any encryption setup on my phone.
 

bigbiff

Senior Recognized Developer
Jun 8, 2010
6,856
7,050
twrp.me is offline

Edit.: For the official builds, only the american servers are offline, European servers working. However this won't help us, I guess the build server is in the US (build.twrp.me).
Our host did an IP subnet change on us and I just found out yesterday. Hope to be up tonight, but might take a while longer.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    twrp.me is offline

    Edit.: For the official builds, only the american servers are offline, European servers working. However this won't help us, I guess the build server is in the US (build.twrp.me).
    Our host did an IP subnet change on us and I just found out yesterday. Hope to be up tonight, but might take a while longer.
    3
    could someone upload the test8 version?
    Is attached.
    1
    See this is what I thought would work, but it didn't fix the problem.

    What I got him to do was fastboot erase boot which stopped the TWRP from causing the bootloop, but it caused "no valid boot slot"

    So then got him to extract the radio and bootloader file from latest stock image from Google, then fastboot flash --slot=all flash bootloader - drag and drop file into cmd

    Fastboot reboot bootloader

    Fastboot --slot=all flash radio - drag and drop file into cmd

    Fastboot reboot bootloader

    Boot into system - failed, so back into bootloader

    Fastboot boot protonkernel

    Booted into OS

    Test reboot, bootloop into bootloader

    Fastboot boot magisk patched protonkernel.img

    Get into OS but lose root regular reboot so fastboot boot magisk patched proton kernel

    Once in OS flash directly from magisk as it seems he had some sort of temp/half root

    What a ballache, but thanks ever so much for your quick response and help though @GTDarthYoda you're an absolute star
    If booting the kernel boots into system, you should be able to use
    Code:
    fastboot flash boot boot.img

    where "boot.img" is the stock boot image or the custom kernel
    1
    all download links are dead right now for me
    twrp.me is offline

    Edit.: For the official builds, only the american servers are offline, European servers working. However this won't help us, I guess the build server is in the US (build.twrp.me).
    1
    could someone upload the test8 version?
  • 47
    [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:
    Test 8: https://build.twrp.me/test/redfin/twrp-3.5.0-0-test8-redfin.img
    Fix reboot to recovery from fastbootd.

    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.


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