• 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

elong7681

Senior Member
May 23, 2015
224
69
40
US
Moto X4
Google Pixel 2 XL
Since the third beta version, twrp no longer starts after I booted it via cmd. Do I absolutely need a different kernel? If so, how do you flash the elementalx kernel?
As long as you are rooted then you can download the app from the playstore and it will install it for you that's if the developer has put out a kernel for the Android 12 beta 3 version there may be other prerequisites but but you can check the entire thread and it will tell you if it is available what is needed to download that kernel for Android 12 beta 3
 
Last edited:

ZwoelVi

Member
Jun 21, 2016
18
4
20
Samsung Galaxy S7
Google Pixel 5
As long as you are rooted then you can download the app from the playstore and it will install it for you that's if the developer has put out a kernel for the Android 12 beta 3 version there may be other prerequisites but but you can check the entire thread and it will tell you if it is available what is needed to download that colonel for Android 12 beta 3
then there is currently no possibility to use twrp under the third beta version?
 

elong7681

Senior Member
May 23, 2015
224
69
40
US
Moto X4
Google Pixel 2 XL
How
i don't flash magisk with twrp. Only with the flash tool
So I figured it out I took a chance and flashed the APK with TWRP and it worked the only problem that I have is I cannot get the Play store to say that my device is certified I've done just about all the tricks in the book I can think of from deleting the storage and cache in the Play store app and rebooting the device I have the safety net fix installed through magisk I have magisk hide on and I cannot get it to say my phone is certified.
 
  • Like
Reactions: andybones

vandyman

Senior Member
Jul 30, 2012
400
120
S.Jersey
Google Pixel 5
Mann you gots me searching for a file that don't exist, lol. Kidding (sorta), but if you read my above post, release of v2.0.0 we clearly knew about, and if you follow in the Proton Telegram or are a Patreon, you also can see the announcement for v2.1.0..
You said v2.4 -- with all that's going on with A12 on the horizon and nature of safetynet, and all the SN test .zips floating around, this was obviously a confusing egg-hunt. Thank you for clarifying it was a typo, and I kindly ask you edit your above post to say the correct v2.1.0 if you wouldn't mind.
I actually found safetynet-fix-v1.2.0-MOD.zip to be enough for myself for things to work. However I am still on August update, no idea how much of a factor this is playing. (I wasn't using a specific module) as I was using the SysUI MOD found in themes section with the SN fix baked in. So I had to remove it from the MOD.zip, which I finally got around to so I could test.
---------------------

And now back to our regularly scheduled programming ...
Sorry for all the confusion.
There are two versions on github.
Reading the Magisk thread about all of the safety net mods put in a dizzy state. Lol
Please read the Magisk thread and you will see that there is a 2.4 version.
Also if you can, please clean this ot.
 

ZwoelVi

Member
Jun 21, 2016
18
4
20
Samsung Galaxy S7
Google Pixel 5
How

So I figured it out I took a chance and flashed the APK with TWRP and it worked the only problem that I have is I cannot get the Play store to say that my device is certified I've done just about all the tricks in the book I can think of from deleting the storage and cache in the Play store app and rebooting the device I have the safety net fix installed through magisk I have magisk hide on and I cannot get it to say my phone is certified.
Do you mean that your device is currently being drm l3 certified. So that you can't watch streaming content in full resolution? Works twrp with Android 12 Beta 4?
 

andybones

Forum Moderator
Staff member
May 18, 2010
14,636
14,924
Google Pixel 5
Sorry for all the confusion.
There are two versions on github.
Reading the Magisk thread about all of the safety net mods put in a dizzy state. Lol
Please read the Magisk thread and you will see that there is a 2.4 version.
Also if you can, please clean this ot.
Cleaned. And I'll clean again if necessary but there's nothing wrong with a clarification post.

Anyway: "Please read the Magisk thread (for what? I'm passing SN on September OTA) and you will see that there is a 2.4 (for SN or for Magisk? If for SN why not say the Magisk SN thread, or the Magisk HideProps thread, which has the most up-to-date information/fixes. and If for Magisk, v2.4 could be confused for another typo of v24, as we are on v23 correctly of Magisk last I checked) version." So do you see how a vague post like this can cause one confusion, and leads to more questions than answers.

I find it best to try and get in a habit of more information, and say the Name+FullVersionNumber-vx.x.x ie. Safetynet-v2.1.0 is kdrag0ns latest, while not released yet to public, Safetynet-v2.0.0 is available. Nothing needs any guessing here.
 

ominouswanderer

New member
Aug 19, 2012
3
0
First off, thanks for the awesome release! Love TWRP and happy to see it on the Pixel 5.

Unfortunately... I kind of messed up when installing and hoping to get some help. I booted into TWRP and accidently installed the newest version (which doesnt have the touch controls). Along the way I think I accidently flashed my Boot and am having some partition issues.

Now that I'm trying to fix many of the previous proposed solutions do not seem to work.

If I try fastboot boot twrp.img it reboots into Fastboot Mode but does not load into TWRP - it also gives the error (bootloader) boot.img missing cmdline or OS version . If I try booting into system it boots the newer TWRP version that does not have touch controls.

If I try flashing boot I get the error FAILED (remote: Failed to write to partition Not Found).

I downloaded the stock files image-redfin-rd1a.200810.022.a4 and extracted the boot.img. When I try to do fastboot flash boot boot.img I get an error of FAILED (remote: Failed to write to partition Not Found).

Anyone have any ideas on how I can get this sorted out? Been working on this for a couple hours now and seem to keep going in circles. I genuinely appreciate any support or ideas, thanks in advance!!
 

hunfatal

Senior Member
Nov 10, 2011
717
414
Budapest
OnePlus X
Google Pixel 5
First off, thanks for the awesome release! Love TWRP and happy to see it on the Pixel 5.

Unfortunately... I kind of messed up when installing and hoping to get some help. I booted into TWRP and accidently installed the newest version (which doesnt have the touch controls). Along the way I think I accidently flashed my Boot and am having some partition issues.

Now that I'm trying to fix many of the previous proposed solutions do not seem to work.

If I try fastboot boot twrp.img it reboots into Fastboot Mode but does not load into TWRP - it also gives the error (bootloader) boot.img missing cmdline or OS version . If I try booting into system it boots the newer TWRP version that does not have touch controls.

If I try flashing boot I get the error FAILED (remote: Failed to write to partition Not Found).

I downloaded the stock files image-redfin-rd1a.200810.022.a4 and extracted the boot.img. When I try to do fastboot flash boot boot.img I get an error of FAILED (remote: Failed to write to partition Not Found).

Anyone have any ideas on how I can get this sorted out? Been working on this for a couple hours now and seem to keep going in circles. I genuinely appreciate any support or ideas, thanks in advance!!

I think you should reflash the whole factory image (you will lose data) and it will work.
 
  • Like
Reactions: elong7681

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Sorry for all the confusion.
    There are two versions on github.
    Reading the Magisk thread about all of the safety net mods put in a dizzy state. Lol
    Please read the Magisk thread and you will see that there is a 2.4 version.
    Also if you can, please clean this ot.
    Cleaned. And I'll clean again if necessary but there's nothing wrong with a clarification post.

    Anyway: "Please read the Magisk thread (for what? I'm passing SN on September OTA) and you will see that there is a 2.4 (for SN or for Magisk? If for SN why not say the Magisk SN thread, or the Magisk HideProps thread, which has the most up-to-date information/fixes. and If for Magisk, v2.4 could be confused for another typo of v24, as we are on v23 correctly of Magisk last I checked) version." So do you see how a vague post like this can cause one confusion, and leads to more questions than answers.

    I find it best to try and get in a habit of more information, and say the Name+FullVersionNumber-vx.x.x ie. Safetynet-v2.1.0 is kdrag0ns latest, while not released yet to public, Safetynet-v2.0.0 is available. Nothing needs any guessing here.
    2
    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.
    2
    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.
    1
    How
    i don't flash magisk with twrp. Only with the flash tool
    So I figured it out I took a chance and flashed the APK with TWRP and it worked the only problem that I have is I cannot get the Play store to say that my device is certified I've done just about all the tricks in the book I can think of from deleting the storage and cache in the Play store app and rebooting the device I have the safety net fix installed through magisk I have magisk hide on and I cannot get it to say my phone is certified.
    1
    First off, thanks for the awesome release! Love TWRP and happy to see it on the Pixel 5.

    Unfortunately... I kind of messed up when installing and hoping to get some help. I booted into TWRP and accidently installed the newest version (which doesnt have the touch controls). Along the way I think I accidently flashed my Boot and am having some partition issues.

    Now that I'm trying to fix many of the previous proposed solutions do not seem to work.

    If I try fastboot boot twrp.img it reboots into Fastboot Mode but does not load into TWRP - it also gives the error (bootloader) boot.img missing cmdline or OS version . If I try booting into system it boots the newer TWRP version that does not have touch controls.

    If I try flashing boot I get the error FAILED (remote: Failed to write to partition Not Found).

    I downloaded the stock files image-redfin-rd1a.200810.022.a4 and extracted the boot.img. When I try to do fastboot flash boot boot.img I get an error of FAILED (remote: Failed to write to partition Not Found).

    Anyone have any ideas on how I can get this sorted out? Been working on this for a couple hours now and seem to keep going in circles. I genuinely appreciate any support or ideas, thanks in advance!!

    I think you should reflash the whole factory image (you will lose data) and it will work.
  • 54
    [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.