TWRP Coral [Official]

Search This thread
It takes a MAN to admit their mistakes. Kudos to you good sir. I make mistake and most times can admit to my mistakes (working on becoming the best me). Honestly, I made the same mistake because I was following the LOS install guide which states it's a "temporary" flash. It technically is because once the full LOS system package is installed it reflashes boot to whatever vesion is being installed. With that being said, this was all tested on LOS 19.1 v091822 (Android 12 not sure if LOS 20 is even out for Android 13) stock LOS kernel and stock recovery 091822. I used the LOS update feature from within LOS 19.1 to update (been updating using this method since LOS 19.1 v050822). I have been trying to test twrp version = twrp-3.6.2-0-a12-coral.img. I spoke with a LOS dude via irc and his thoughts on the matter were that most likely the kernel of the twrp-3.6.2-0-a12-coral.img is being compilled without touch screen support. I'm not sure if that's the case I haven't dug in too deep on this matter but I might. Curious what @bigbiff thinks? Recap, flashing or booting into active /boot slot gives no touch screen capabilities. For the folks stating that this is working, what ROM/kernel are you using? Thanks for all the feed back/help!
lol thanks :) I try not to ever do what I did do, but I am only human, and I make plenty of mistakes so chalk it up to user error
 
  • Like
Reactions: ax562

xdadottts

Member
Oct 2, 2022
14
1
Confirmed "touch" is not functional using twrp-3.6.2-0-a12-coral.img
Running: Build lineage_coral-userdebug 12SQ3aA-220705.004
LOS ver: 19-20221002-NIGHTLY-coral
PIXEL 4 XL

What is method to make backup of the running ROM as an image?
Is there a cmd-line option?
 

ax562

Senior Member
Aug 8, 2012
181
106
I need logcat as well to see initialization of touch kernel modules. I am assuming you repacked TWRP into the recovery ramdisk?
Logcat was provide with recovery log (2 seperate links). In regards to twrp, all I did is "fastboot boot twrp-3.6.2-0-a12-coral.img". Let me know if you need anything else. Ty
 

xdadottts

Member
Oct 2, 2022
14
1
ok..latest TWRP is out!

twrp-installer-3.7.0_12-0-coral.zip28.9M 2022-10-02 23:34:15 UTC
twrp-3.7.0_12-0-coral.img64M 2022-10-02 23:34:11 UTC
But when I fastboot boot twrp*.img , i get no touchscreen. Need "lzma"
I downloaded Kirisakura-FLORAL_9.0.2.zip

BTW, I'm using : Build lineage_coral-userdebug 12SQ3aA-220705.004 LOS ver: 19-20221002-NIGHTLY-coral ROOTED!

@[SIZE=3]GROOVYJOSHCLARK[/SIZE] or Can someone advise on next set of steps to install kernel and twrp? Can I use Fastboot or Recovery or..​

 
ok..latest TWRP is out!

twrp-installer-3.7.0_12-0-coral.zip28.9M 2022-10-02 23:34:15 UTC
twrp-3.7.0_12-0-coral.img64M 2022-10-02 23:34:11 UTC
But when I fastboot boot twrp*.img , i get no touchscreen. Need "lzma"
I downloaded Kirisakura-FLORAL_9.0.2.zip

BTW, I'm using : Build lineage_coral-userdebug 12SQ3aA-220705.004 LOS ver: 19-20221002-NIGHTLY-coral ROOTED!

@[SIZE=3]GROOVYJOSHCLARK[/SIZE] or Can someone advise on next set of steps to install kernel and twrp? Can I use Fastboot or Recovery or..​

I do not install TWRP, I only ever fastboot it when needed (so its temporary and not persistent) which is how you want to use TWRP. As to kernels, be careful or you will bootloop to bootloader if you choose one for stock (and most are). I also do not run any 3rd party kernels; just what LOS provides. When using EX Kernel or FKIM Kernel, it BL loops, so dont try it unless you are on the stock firmware. I used to use EX/FKM but not anymore, others can chime in, but I have not found a working kernel for LOS 19.1 that doesn't bootloop (nor do I really need a 3rd party kernel with LOS's kernel). I find LOS is well suited for my needs and I am dev/power user so I dont recommend 3rd party kernels right now.
 

ax562

Senior Member
Aug 8, 2012
181
106
ok..latest TWRP is out!

twrp-installer-3.7.0_12-0-coral.zip28.9M 2022-10-02 23:34:15 UTC
twrp-3.7.0_12-0-coral.img64M 2022-10-02 23:34:11 UTC
But when I fastboot boot twrp*.img , i get no touchscreen. Need "lzma"
I downloaded Kirisakura-FLORAL_9.0.2.zip

BTW, I'm using : Build lineage_coral-userdebug 12SQ3aA-220705.004 LOS ver: 19-20221002-NIGHTLY-coral ROOTED!

@[SIZE=3]GROOVYJOSHCLARK[/SIZE] or Can someone advise on next set of steps to install kernel and twrp? Can I use Fastboot or Recovery or..​

Also, if twrp touchscreen is not working it doesn't matter what kernel you are using, twrp boots own kernel and at this moment it's not supporting touchscreen. You can see this when you boot to LOS recovery, touch screen is functional.
 
Last edited:

ax562

Senior Member
Aug 8, 2012
181
106
All right folks, I found a work around for the time being using twrp for android 12.1. twrp does support usb mouse capabilities and I was able to use a usb wireless mouse (with usb c to a adapter) through the usb port. I successfully backed up and restored 2 different OS'. I can add details if anyone is interested. Ty @bigbiff for your continued works!
 

xdadottts

Member
Oct 2, 2022
14
1
T.Y to GROOVYJOSHCLARK & ax562
@ax562 I would like details howto "use a usb wireless mouse (with usb c to a adapter) through the usb port" I downloaded scrcpy . I also installed the TWRP.apk, but it states: "Unable to locate recovery"-see scrnshot
 

Attachments

  • Screenshot_20221013-203718_Official TWRP App.png
    Screenshot_20221013-203718_Official TWRP App.png
    104.5 KB · Views: 19

ax562

Senior Member
Aug 8, 2012
181
106
T.Y to GROOVYJOSHCLARK & ax562
@ax562 I would like details howto "use a usb wireless mouse (with usb c to a adapter) through the usb port" I downloaded scrcpy . I also installed the TWRP.apk, but it states: "Unable to locate recovery"-see scrnshot
You are going to have to temporary boot into twrp in fastboot mode with "fastboot boot TWRP.img". From there you will not have touchscreen capabilities but you can connect a usb mouse to the usb c port. I'm using an Anker usb c to a adapter to a logitech usb wireless adapter for my wireless mouse. From there you will see the mouse pointer and can use twrp. TWRP was asking me if I was sure I wanted to back up with pin code, so I'm pretty sure there might be a decryption issue so I backed up without any screen lock security(BACKUP EVERYTHING ALWAYS!!!). Once backed up I wiped dalvik/data and installed LOS 19.1 from twrp but had to reboot to LOS recovery to flash gapps (Magisk flashing in twrp and LOS recovery didn't work flashed magisk.apk once in LOS). Once that LOS system was good to go I booted back into twrp (fastboot boot TWRP.img) and backed that system up (I always wype dalvik art cache before backing up, BACKUP EVERYTHING ALWAYS!!!). Once that system was backed up I wiped dalvik art cache/data and restored my original system backup and boom...good to go. After first boot, another restart is required after restores. Hope that makes sense.

P.S. For whatever reason, I'm on a linux/gnu OS and fastboot stopped working for me. Not sure what happened (thinking OS kernel driver bug, will try differenent linux system soon. was haning on "sending boot img") but downloaded platformtools for windows and executed from dir in power shell terminal "./fastboot boot TWRP.img". Anyone seeing this bug in Linux based OS?

Edit: I added "BACKUP EVERYTHING ALWAYS!!!" per @GROOVYJOSHCLARK advice. For me, backing up everything is just a common thought but I get how someone new to this could make a mistake. Repeat BACKUP EVERYTHING ALWAYS!!!. :p
 
Last edited:
Also, if twrp touchscreen is not working it doesn't matter what kernel you are using, twrp boots own kernel and at this moment it's not supporting touchscreen. You can see this when you boot to LOS recovery, touch screen is functional.
NICE! I did not know that part (kernel in recovery embedded in the latest TWRP), but it makes sense
 
  • Like
Reactions: ax562
You are going to have to temporary boot into twrp in fastboot mode with "fastboot boot TWRP.img". From there you will not have touchscreen capabilities but you can connect a usb mouse to the usb c port. I'm using an Anker usb c to a adapter to a logitech usb wireless adapter for my wireless mouse. From there you will see the mouse pointer and can use twrp. TWRP was asking me if I was sure I wanted to back up with pin code, so I'm pretty sure there might be a decryption issue so I backed up without any screen lock security. Once backed up I wiped dalvik/data and installed LOS 19.1 from twrp but had to reboot to LOS recovery to flash gapps (Magisk flashing in twrp and LOS recovery didn't work flashed magisk.apk once in LOS). Once that LOS system was good to go I booted back into twrp (fastboot boot TWRP.img) and backed that system up (I always wype dalvik art cache before backing up). Once that system was backed up I wiped dalvik art cache/data and restored my original system backup and boom...good to go. After first boot, another restart is required after restores. Hope that makes sense.

P.S. For whatever reason, I'm on a linux/gnu OS and fastboot stopped working for me. Not sure what happened (thinking OS kernel driver bug, will try differenent linux system soon. was haning on "sending boot img") but downloaded platformtools for windows and executed from dir in power shell terminal "./fastboot boot TWRP.img". Anyone seeing this bug in Linux based OS?
Nice layout of steps and explanations! This is what XDA is intended for, so I applaud this post! I, however, will wait it out for TWRP to mature but in all reality, I don't use TWRP (like I used to years ago), I ALWAYS had an updated NANDROID, but that's going back 5/6 years ago. I no longer need them, and at this point, I only boot a recovery to install ROM and/or wipe for a new ROM install, so I don't really use recoveries anymore. I also don't bother NANDROID'ng anymore with how often I switch ROMs to test/help others, but it's nice to see this type of post showing others a workaround and how-to do it if you chose to use TWRP and NAROID. I just backup my internal SD to PC (for pics and such) and use Carbonite SMS Backup for TXT/MMS's, and TiB for any apps I want to retain data, but otherwise, I setup fresh when making a new Daily Driver ROM (I.E., by daily ROM is LOS 19.1) so unless I am testing another ROM to help someone, I am on LOS 19.1 (so no need for TWRP anymore).

I LOVE this type of thinking though, you are outside the box thinking and that's EXACTLY the type of users we need here on XDA!!! Well done!! I always urge and encourage users to try new things, or things out of the box, or trying to figure out/fix things by tinkering (smartly) so you don't lose data, and this post was most definitely done that way, so well done, seriously (I am being 100% authentic).

My only comment would be to URGE users to BACKUP everything (as if they were to wipe and start over), just in case of data-loss (so they can recover from any type of disaster). Thats only the thing I would add to it, but otherwise I love this post and thought process!!

For me personally, EVERY TIME I skip a backup, I have an issue. This is even if it's just changing kernels or something very minimal (like applying an update, who knows but it shouldn't break anything), and yet, it always will end in some type of disaster, and I need my backups (I didn't take)! However, WHEN I backup, nothing ever happens. I am the type of engineer to ALWAYS prepare for the worst but hope for the best, and it's saved my butt many times in my career (senior sys architect/engineer).
 
  • Like
Reactions: ax562

xdadottts

Member
Oct 2, 2022
14
1
Thanks ax562.. I shall try replicating your steps.

TWRP has its own kernel and boot.img file too

FWIW, sideloading the twrp-installer-3.7.0_12-0-coral.zip WORKS, touchscreen and all, but you loose root. It boots into LOS19.1 and then you do the patched Magisk all over again to ROOT.

Installing the TWRP app gets error : "Unable to locate recovery "
(post 711) and interestingly the app keeps continually crashing when selecting the option "TWRP FLASH". This was to try installing the twrp.img file from the phone so it would attach to the "recovery" menu..

Shall keep an eye out for updated versions of TWRP
.
Naturally, I shall keep an eye here on updated postings.

I shall update after trying
ax562. steps.
 
Thanks ax562.. I shall try replicating your steps.

TWRP has its own kernel and boot.img file too

FWIW, sideloading the twrp-installer-3.7.0_12-0-coral.zip WORKS, touchscreen and all, but you loose root. It boots into LOS19.1 and then you do the patched Magisk all over again to ROOT.

Installing the TWRP app gets error : "Unable to locate recovery "
(post 711) and interestingly the app keeps continually crashing when selecting the option "TWRP FLASH". This was to try installing the twrp.img file from the phone so it would attach to the "recovery" menu..

Shall keep an eye out for updated versions of TWRP
.
Naturally, I shall keep an eye here on updated postings.

I shall update after trying
ax562. steps.

I don't think I'm the only one here who really wishes you'd stop changing font colors and styles every other sentence. It makes reading your posts headache-inducing (and the post I quoted is a prime example, because changing the text color to white effectively made half your post invisible). People who are irritated and annoyed will be less likely to want to help you. Food for thought.
 
  • Like
Reactions: GROOVYJOSHCLARK

ax562

Senior Member
Aug 8, 2012
181
106
It looks like only lineage-19.1 isn't working because they compiled all the touchdrivers into the kernel. I am looking at doing that now for coral and flame. It still works fine on stock 12.1.
Yup, tried fastbooting the latest 3.7 just for fun (didn't see much difference in github repo) and still no touch screen capabilities using LOS 19.1. I also forked your's and LOS repo just to start poking around. Let me know if you need anything else @bigbiff and ty for all your works!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 77
    [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:
    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
    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.
    24
    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.