TWRP Coral [Official]

[bigbiff]

[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

A11 Testing:

https://build.twrp.me/test/coral/twrp-3.5.0-0-test1-coral.img

Please test and let me know if anything isn't working.

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

 

[bigbiff]

What to backup
* super
* data
* persist
* boot
* any other partition desired

What to restore
* super
* data
* boot - depending on ROM support

Please just restore persist if you have a failed partition. I do not recommend restoring backups from phone to phone unless you know what you are doing.

These devices do not have a recovery partition. You will not be able to flash the img file directly to the phone. Make sure you use fastboot boot to temporarily boot TWRP and use adb to push it to the /sdcard folder for repacking.
Repacking TWRP into Boot partition
To repack TWRP into the boot partition to override stock recovery when rebooting to recovery, perform the following steps
1. adb push <latest_twrp_boot.img> /sdcard/
2. reboot to bootloader and fastboot latest boot.img of TWRP
3. Go to Install
4. Select your TWRP boot.img from /sdcard
5. Touch Install Image Recovery Ramdisk
6. Swipe to confirm flash
7. Reboot to recovery and android to verify installation

 

[Jkell69]

Glad to see this!

 

[wrongway213]

Finally TWRPified! Thanks for bringing this to us!

 

[Daisymae]

[RECOVERY] TWRP 3.4.0-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.

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


DOWNLOAD:
Hello, this is a test build for coral users (will work on crosshatch/blueline later). I was hoping adventurous people would try this fastbootable image out for testing.
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. Will check back later to see feedback. Don't try if you are unable to reset back to stock. Only try if you are curious to kick the tires.

June FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test1-coral.img
http://twrp.me

When trying to boot the image it gets stuck on the TWRP flash screen. I'm on a rooted custom rom. Sorry to sound stupid if I'm missing something obvious.

 

[Santarosa 503]

When trying to boot the image it gets stuck on the TWRP flash screen. I'm on a rooted custom rom. Sorry to sound stupid if I'm missing something obvious.

Same here ?

 

[wrongway213]

I'm stuck on splash screen as well, but I'm gonna try to push this thread in a more helpful direction with a detailed description and a logcat:

I'm on June radio/bootloader, running AOSiP, rooted with Magisk, build # QQ3A.200605.001

Here's the logcat of stuck @ splash
https://pastebin.com/sAMURQKw

If anything else you need tested or logged please don't be shy to tag me - I'm excited to see TWRP making its way here and I know it's been hard work. Hope the log helps and will gladly take more if it doesn't show the pertinent info you need.:good:

 

[Surge1223]

I'll follow in Wrong Ways example.

Build: du_coral-userdebug 10 QQ3A.200605.002.A1 eng.surge.20200605.155815 release-keys

Probs wont do much more than this for now. But figured id upload to help the cause

Few things I thought I might add.

-manually adding libion.so to /system/lib64 allows you to get further but then it requests libandroidicu.so which is an apex/android runtime lib which isn't available since system isn't mounted

-toybox missing pigz always shows up

 

[bigbiff]

I'll follow in Wrong Ways example.

Build: du_coral-userdebug 10 QQ3A.200605.002.A1 eng.surge.20200605.155815 release-keys

Probs wont do much more than this for now. But figured id upload to help the cause

Few things I thought I might add.

-manually adding libion.so to /system/lib64 allows you to get further but then it requests libandroidicu.so which is an apex/android runtime lib which isn't available since system isn't mounted

-toybox missing pigz always shows up

Thanks for the logs, I am working on getting our relink process working better so I hope to get that done soon to get all the built objects into the right space.

Apex files should be mounted and available before the decryption process happens. init is then configured to use these apex libraries for loading. It works locally but not on your pixels for some reason.

Can you post the results of mount -v?

Here is a new test image as well, I verified it on my own coral and it decrypted with pin: https://build.twrp.me/test/coral/twrp-3.4.0-0-test2-coral.img

Also this image is fastboot only. I need to work on installing into the ramdisk.

 

[Surge1223]

Thanks for the logs, I am working on getting our relink process working better so I hope to get that done soon to get all the built objects into the right space.

Apex files should be mounted and available before the decryption process happens. init is then configured to use these apex libraries for loading. It works locally but not on your pixels for some reason.

Can you post the results of mount -v?

Here is a new test image as well, I verified it on my own coral and it decrypted with pin: https://build.twrp.me/test/coral/twrp-3.4.0-0-test2-coral.img

Also this image is fastboot only. I need to work on installing into the ramdisk.

Sure, no problem. logs attached

 

[bigbiff]

Sure, no problem. logs attached

Thanks, did you try test2?

 

[Surge1223]

Thanks, did you try test2?

yep

fastboot boot /Users/surge/Downloads/twrp-3.4.0-0-test2-coral.img

---------- Post added at 02:02 AM ---------- Previous post was at 01:58 AM ----------

Thanks, did you try test2?

BTW, im stuck on splash whenever I try to do this, I thought decryption only took place when attempting to enter pin/pattern?

 

[bigbiff]

yep

fastboot boot /Users/surge/Downloads/twrp-3.4.0-0-test2-coral.img

---------- Post added at 02:02 AM ---------- Previous post was at 01:58 AM ----------



BTW, im stuck on splash whenever I try to do this, I thought decryption only took place when attempting to enter pin/pattern?

Boggling my mind that it works on my coral with out linking issues.

Can you post the results of getprop please?

 

[bigbiff]

yep

fastboot boot /Users/surge/Downloads/twrp-3.4.0-0-test2-coral.img

---------- Post added at 02:02 AM ---------- Previous post was at 01:58 AM ----------



BTW, im stuck on splash whenever I try to do this, I thought decryption only took place when attempting to enter pin/pattern?

It might be something funky happening with qsecomd starting up. There is a whole orchestration of steps that might cause an issue unfortunately. Until we get things ironed out you might have to wipe via stock recovery a few times. I assume by splash you mean the white G screen?

 

[Surge1223]

It might be something funky happening with qsecomd starting up. There is a whole orchestration of steps that might cause an issue unfortunately. Until we get things ironed out you might have to wipe via stock recovery a few times. I assume by splash you mean the white G screen?

I meant the twrp splash screen.

https://hastebin.com/ovamadoken.md

Could it have to do with the interface_start in relation to keymaster4?

---------- Post added at 02:23 AM ---------- Previous post was at 02:20 AM ----------

I meant the twrp splash screen.

https://hastebin.com/ovamadoken.md

Could it have to do with the interface_start in relation to keymaster4?

Wait did you want getprop while in recovery or booted?

 

[bigbiff]

I meant the twrp splash screen.

https://hastebin.com/ovamadoken.md

Could it have to do with the interface_start in relation to keymaster4?

---------- Post added at 02:23 AM ---------- Previous post was at 02:20 AM ----------



Wait did you want getprop while in recovery or booted?

Sorry, I would like it executed in recovery. I want to try and find out why it seems as when apex libraries are mounted, they do not seem to be added to the library search path in init.

Since some of the decryption programs don't find libion.so, they cannot start up.

 

[Surge1223]

Sorry, I would like it executed in recovery. I want to try and find out why it seems as when apex libraries are mounted, they do not seem to be added to the library search path in init.

Since some of the decryption programs don't find libion.so, they cannot start up.

heres getprop
https://hastebin.com/eluqagolub.md

heres list of files in /system/lib64
https://hastebin.com/uqoxuheqef.pl

 

[iamreinvented]

Got some $$ coming your way Monday OP.

Thank you for this. It could not have been easy

 

[dhacke]

@bigbiff,

i tested the test2 img, too and i have the same result as wrongway213 and Surge1223. It hangs on the twrp Splash Screen.
I'm on AOSiP Official (no Gapps) from june (=> latest build) so my factory image is on june, too (i don't know which slot is active atm).

Just a theory: Can it have to do with the fact that on the other slot is still the old AOSiP build with may factory image installed? Mayby this makes a crash on the decryption. I'm not a dev so it's just a assumption.
If you need logs i'm glad to give them to you but i know only the logcat from adb. So for more i would need guides/help.

 

[bigbiff]

@bigbiff,

i tested the test2 img, too and i have the same result as wrongway213 and Surge1223. It hangs on the twrp Splash Screen.
I'm on AOSiP Official (no Gapps) from june (=> latest build) so my factory image is on june, too (i don't know which slot is active atm).

Just a theory: Can it have to do with the fact that on the other slot is still the old AOSiP build with may factory image installed? Mayby this makes a crash on the decryption. I'm not a dev so it's just a assumption.
If you need logs i'm glad to give them to you but i know only the logcat from adb. So for more i would need guides/help.

No, it seems to be related to trying to load libion.so from apex images. Can you post a URL to the exact build you are using? I can test it on flame locally.