TWRP Coral [Official]

Search This thread

wrongway213

Recognized Developer / Recognized Contributor / Re
Jul 27, 2014
5,071
8,814
32
Canton, OH
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.
 
  • Like
Reactions: Bdavidb71

bradical711

Senior Member
Aug 26, 2017
386
240
Google Pixel 4 XL
@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

Member
Feb 14, 2020
24
4
Moto G7 Play
Google Pixel 4 XL
@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

Senior Member
Aug 26, 2017
386
240
Google Pixel 4 XL
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

Member
Feb 14, 2020
24
4
Moto G7 Play
Google Pixel 4 XL
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

Senior Member
Aug 26, 2017
386
240
Google Pixel 4 XL
- 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!
 
Last edited:

hellomrwhite

Member
Feb 14, 2020
24
4
Moto G7 Play
Google Pixel 4 XL
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
 

bigbiff

Senior Recognized Developer
Jun 8, 2010
6,812
6,887
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.
 
  • Like
Reactions: bradical711

bradical711

Senior Member
Aug 26, 2017
386
240
Google Pixel 4 XL
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.
 
Last edited:

bigbiff

Senior Recognized Developer
Jun 8, 2010
6,812
6,887
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

Senior Member
Aug 26, 2017
386
240
Google Pixel 4 XL
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

Senior Recognized Developer
Jun 8, 2010
6,812
6,887
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.
 
  • Like
Reactions: bradical711

Top Liked Posts

  • There are no posts matching your filters.
  • 68
    [RECOVERY] TWRP 3.5.0_10-0 - TeamWin Recovery Project [/B]




    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.

    coral Device Config: https://github.com/bigbiff/android_device_google_coral


    DOWNLOAD:
    Please go to https://twrp.me to download the recovery image.

    Old info:

    Hello, this is a test build for coral users (will work on crosshatch/blueline later).

    So far I have decryption working, touch, adb and backup and restore seems to work. Super partition volumes can be mounted, and the super partition can be backed up.

    TWRP seems to be pretty stable now as of test 5. Missing features include adb sideload and repacking recovery which I will be working on in the upcoming months. Android 11 will be supported when stable APIs have been release and we have time to update to that release.

    June FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test1-coral.img
    July FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test4-coral.img
    July FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test5-coral.img
    - fix restoring of persist partition
    - fix restoring of super partition
    July FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test6-coral.img
    - allow repacking of TWRP from boot.img
    - magisk not working currently on repacked image
    August FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test7-coral.img
    August FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test8-coral.img
    - fix repacking magisk with TWRP


    - Credit to @Freak07 https://github.com/freak07/FLORAL - using his kernel as a base for Coral/Flame TWRP

    http://twrp.me
    30
    well.if you have a zip file would be even better

    Repacking is still being worked on. Fastboot only is workable. I have mentioned this in the thread.
    For people who want to know, I am working on ramdisk issues I am having before repacking.

    Please don't leave passive aggressive comments in the future.
    29
    Hello, I released a new test image:

    July FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test5-coral.img
    - fix restoring of persist partition
    - fix restoring of super partition
    29
    So is there a way to restore said backed up super partition?
    Btw thanks for the work you've put in so far, it's much appreciated.

    There has been a fix posted to our gerrit and merged. I am working on a ramdisk issue and will put a new test build that allows restore of super.
    21
    Hello, I was able to get repacking working, however you need to use a kernel with LZMA ramdisk support. I am using Kirisakura-FLORAL_5.2.2.zip for testing.

    Also I am now using @Freak07 FLORAL kernel as a base for the fastboot image in order to support the newer DTBO image from R.

    Please see the download in the FP.

    You can repack TWRP into the boot ramdisk with this version, and reboot to recovery is working. I need to test magisk next.
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