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

[ZwoelVi]

I haven't had any luck with the backup personally; you'd have to backup not only /system and /data, but /boot as well. I keep things pretty simple; I'm using the stock firmware with the stock kernel, the only thing I've flashed is Magisk.

so does the restore not work?

 

[V0latyle]

so does the restore not work?

I honestly don't know. I didn't have any luck and had to reflash everything. YMMV, and someone else may have been successful.

 

[ZwoelVi]

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?

 

[elong7681]

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

 

[ZwoelVi]

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]

If you've already checked for an updated kernel and there is not one available then I would assume from what you are telling me there isn't a way to use twrp but I could be completely wrong because I haven't tried using twrp on my Pixel 5

 

[ZwoelVi]

If you've already checked for an updated kernel and there is not one available then I would assume from what you are telling me there isn't a way to use twrp but I could be completely wrong because I haven't tried using twrp on my Pixel 5

alright, thank you very much

 

[elong7681]

alright, thank you very much

You're welcome

 

[j-o]

Is it safe?

 

[vandyman]

Safe what?
Modifications of any type, there is always a risk.

 

[elong7681]

alright, thank you very much

@ZwoelVi when you flash magisk in TWRP do you flash the patched boot img that you created from the magisk app or did you flash the magisk.apk

 

[ZwoelVi]

@ZwoelVi when you flash magisk in TWRP do you flash the patched boot img that you created from the magisk app or did you flash the magisk.apk

i don't flash magisk with twrp. Only with the flash tool

 

[elong7681]

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.

 

[vandyman]

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.

 

[V0latyle]

So is this still 3.5.0 or 3.5.2? Test 9 shows up as 3.5.2_11.0 on my phone.

 

[ZwoelVi]

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?

 

[elong7681]

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?

I figured it out, I'm currently on Android 11

 

[andybones]

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]

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]

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.