TWRP Coral [Official]

[2WildFirE]

So does this twrp test img work with Android 11?

ATM all images only work 100% for Android 10.

 

[wrongway213]

So does this twrp test img work with Android 11?

Lineage 17.1 = Android 10. Lineage 18.x is Android 11.

Simpler answer: unless it specifically says it's for Android 11 or a test for Android 11, assume it's not. I can't imagine something as major as "Android 11 support added" would be left out of changelogs/release notes.

 

[bradical711]

@bigbiff I recently updated to the new updated to the new TWRP recovery 3.5.0 from 3.4.0 test img 10. Now that I updated however, I have a problem. Before, I was able to decrypt data and now that I have updated, I am no longer able to do so. Everytime I try to decrypt with my correct password, it fails to do so now when before it worked.

 

[hellomrwhite]

@bigbiff I recently updated to the new updated to the new TWRP recovery 3.5.0 from 3.4.0 test img 10. Now that I updated however, I have a problem. Before, I was able to decrypt data and now that I have updated, I am no longer able to do so. Everytime I try to decrypt with my correct password, it fails to do so now when before it worked.

You should read the changelog for the new update that'll give you the answer

 

[bradical711]

You should read the changelog for the new update that'll give you the answer

That was the first thing I read before flashing the new image but thank you. It's possible I could have missed something but I went ahead and read the changelog again for my own sanity's sake rn. I saw something related to MTP still not working in the downloads section which I saw earlier already. I also did the update correctly to the new image following the instructions provided in the DL section. I also went ahead and reinstalled the new 3.5.0 image and same issue persists. So maybe you can elaborate on what I missed in the changelog that was related to decryption. Please and thank you if you don't mind. This is what I saw related to encryption. It was as follows "FBE Fixes - CaptainThrowback" "FDE encryption fixes - CaptainThrowback" .... Like I said, before I was able to decrypt my data and now I cannot with the new image. I didn't change passwords and even reset my password etc etc. Any further suggestions/help would be appreciated. Thank you!! I can of course post logs if need be, I am just curious if anyone has this issue/how to fix it.

 

[hellomrwhite]

That was the first thing I read before flashing the new image but thank you. It's possible I could have missed something but I went ahead and read the changelog again for my own sanity's sake rn. I saw something related to MTP still not working in the downloads section which I saw earlier already. I also did the update correctly to the new image following the instructions provided in the DL section. I also went ahead and reinstalled the new 3.5.0 image and same issue persists. So maybe you can elaborate on what I missed in the changelog that was related to decryption. Please and thank you if you don't mind. This is what I saw related to encryption. It was as follows "FBE Fixes - CaptainThrowback" "FDE encryption fixes - CaptainThrowback" .... Like I said, before I was able to decrypt my data and now I cannot with the new image. I didn't change passwords and even reset my password etc etc. Any further suggestions/help would be appreciated. Thank you!! I can of course post logs if need be, I am just curious if anyone has this issue/how to fix it.

New TWRP 3.5.0_9-0

Changelog:

- All TWRP 3.5.0_9 changes and improvements

- Persist and firmware (modem) partitions aren't backup-able anymore. Firmware partition backup/restore/wipe with vfat partition makes network issues; and with emmc backups are useless since can't be restored successfully, and this "filesystem" isn't wipeable.

- Persist partition doesn't need any backups/wipes/restores, and if someone has some particular issues, it's always better to go to latest stock firmware, better with pit file too.

I honestly made that comment because I had just seen this in another post, I'm definitely not someone claiming to know how to solve these issues, just trying to help a little my bad. Hopefully this helps

 

[bradical711]

- Persist and firmware (modem) partitions aren't backup-able anymore. Firmware partition backup/restore/wipe with vfat partition makes network issues; and with emmc backups are useless since can't be restored successfully, and this "filesystem" isn't wipeable.

- Persist partition doesn't need any backups/wipes/restores, and if someone has some particular issues, it's always better to go to latest stock firmware, better with pit file too.

Unfortunately this doesn't help me much but I appreciate your help for the reference. This doesn't help me because I'm not trying to back up either of those partitions or restore them. For reference, I was able to decrypt my /data before using my password on the previous twrp3.4.0.0-test10.img. I also made a full backup up of everything on the previous twrp3.4.0.0-test10.img including /data but am now unable to do so because /data can't be decrypted anymore with my password. I never restored my backup on the previous image but I wanted to have one on the fly just in case. I also already know what to backup/restore and what works etc etc. Would you mind linking to the other post that you saw btw? Please and thank you, that'll be the last I ask of you!

 

[hellomrwhite]

Unfortunately this doesn't help me much but I appreciate your help for the reference. This doesn't help me because I'm not trying to back up either of those partitions or restore them. And for reference, I was able to decrypt my /data before using my password on the previous twrp-test10.img. I also made a full backup up of everything on the previous image including /data but am now unable to do so because /data can't be decrypted anymore with my password. I never restored my backup on the previous image but I wanted to have one on the fly just in case. I also already know what to backup/restore and what works etc etc. Would you mind linking to the other post that you saw btw? Please and thank you, that'll be the last I ask of you!

For sure this is the link for the original comment on the related post hope you get some real help better than my noobish attempt lol

[RECOVERY][3.5.1_9][UNIFIED][matisse][millet] TWRP Recovery

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...

forum.xda-developers.com

 

[bigbiff]

Unfortunately this doesn't help me much but I appreciate your help for the reference. This doesn't help me because I'm not trying to back up either of those partitions or restore them. For reference, I was able to decrypt my /data before using my password on the previous twrp3.4.0.0-test10.img. I also made a full backup up of everything on the previous twrp3.4.0.0-test10.img including /data but am now unable to do so because /data can't be decrypted anymore with my password. I never restored my backup on the previous image but I wanted to have one on the fly just in case. I also already know what to backup/restore and what works etc etc. Would you mind linking to the other post that you saw btw? Please and thank you, that'll be the last I ask of you!

Did you do a format of data or just a wipe? The problem with FBE devices, is that once you format data, TWRP cannot restore data from your backup because those keys are needed for restore. You shouldn't format data unless there is a serious issue and just let TWRP run the logic to wipe data without wiping required metadata files.

Once a format has been done, gatekeeper will not allow usage of the old FBE keys.

 

[bigbiff]

Hello all, I have released an update on https://twrp.me that enables MTP for this device. Please let me know if there are any major issues,

 

[hellomrwhite]

Hello all, I have released an update on https://twrp.me that enables MTP for this device. Please let me know if there are any major issues,

Can't seem to find the updated post

 

[bradical711]

Did you do a format of data or just a wipe? The problem with FBE devices, is that once you format data, TWRP cannot restore data from your backup because those keys are needed for restore. You shouldn't format data unless there is a serious issue and just let TWRP run the logic to wipe data without wiping required metadata files.

Once a format has been done, gatekeeper will not allow usage of the old FBE keys.

I did neither of those options but that is super good info to note, so thank you. All I did was upgrade TWRP from the last test image to the official image and I can no longer decrypt my /data. It says "unable to mount /data (invalid argument)". I actually just updated to the new TWRP 3.5.0_10-1 and the same issue persists. I disabled my password and it still asked for a password inside of TWRP... TWRP also says it cannot access "data/recovery/.version" and when I open the file inside a file viewer it still says TWRP 3.4.0 inside of the file. TWRP also cannot access the ".twrps" settings file either. I don't know how much this info helps though.

 

[bigbiff]

I did neither of those options but that is super good info to note, so thank you. All I did was upgrade TWRP from the last test image to the official image and I can no longer decrypt my /data. It says "unable to mount /data (invalid argument)". I actually just updated to the new TWRP 3.5.0_10-1 and the same issue persists. I disabled my password and it still asked for a password inside of TWRP... TWRP also says it cannot access "data/recovery/.version" and when I open the file inside a file viewer it still says TWRP 3.4.0 inside of the file. TWRP also cannot access the ".twrps" settings file either. I don't know how much this info helps though.

Can you post logcat and recovery.log?

 

[bradical711]

Can you post logcat and recovery.log?

I tried to get recovery.log from within TWRP when booted by copying logs to data/media/recovery but there isn't a log posted inside the folder when I reboot. I also couldn't figure out how to pull a logcat from within TWRP... If you could please tell me how to get both a logcat & recovery.log for you, I will have them posted.

 

[bigbiff]

I tried to get recovery.log from within TWRP when booted by copying logs to data/media/recovery but there isn't a log posted inside the folder when I reboot. I also couldn't figure out how to pull a logcat from within TWRP... If you could please tell me how to get both a logcat & recovery.log for you, I will have them posted.

recovery.log is in a temporary file system and gone when you leave TWRP.

To get logcat, execute logcat > /tmp/logcat.log then use adb to pull it.

 

[GROOVYJOSHCLARK]

@bigbiff I just wanted to say thank you for your hard work and the awesome dedication you show us by bringing a working TWRP recovery for our pixel 4 XLs! I am going to send you a few beers when I get to work to show my appreciation!

 

[sharpz811]

So does this work for Android 11 or just Android 10? Much appreciate the hard work!

 

[WoZzYDoesitbest]

Following... Wondering same about Android 11?

 

[bigbiff]

Following... Wondering same about Android 11?

As noted before, it supports android 10 only.

 

[sharpz811]

As noted before, it supports android 10 only.

I'm sorry we must be blind because no where in the op does it specify compatible Android versions.