TWRP Coral [Official]

[GROOVYJOSHCLARK]

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

 

[xdadottts]

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?

 

[bigbiff]

recovery.log

drive.google.com

2022-09-24-13-32-39-coral-logcat.txt

drive.google.com

I need logcat as well to see initialization of touch kernel modules. I am assuming you repacked TWRP into the recovery ramdisk?

 

[ax562]

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]

ok..latest TWRP is out!

twrp-installer-3.7.0_12-0-coral.zip	28.9M	2022-10-02 23:34:15 UTC
twrp-3.7.0_12-0-coral.img	64M	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..​

 

[son_91]

Has it worked on Android 13?

 

[GROOVYJOSHCLARK]

ok..latest TWRP is out!

twrp-installer-3.7.0_12-0-coral.zip	28.9M	2022-10-02 23:34:15 UTC
twrp-3.7.0_12-0-coral.img	64M	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]

ok..latest TWRP is out!

twrp-installer-3.7.0_12-0-coral.zip	28.9M	2022-10-02 23:34:15 UTC
twrp-3.7.0_12-0-coral.img	64M	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.

 

[ax562]

Has it worked on Android 13?

Not yet, still not working for 12, no touchscreen capabilities.

 

[ax562]

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]

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

 

[ax562]

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!!!.

 

[GROOVYJOSHCLARK]

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

 

[GROOVYJOSHCLARK]

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).

 

[xdadottts]

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.

 

[MJPollard]

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.

 

[bigbiff]

Not yet, still not working for 12, no touchscreen capabilities.

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.

 

[ax562]

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!

 

[GROOVYJOSHCLARK]

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.

Nice, thanks bigbiff! Let me know if you need testers..

 

[bigbiff]

Nice, thanks bigbiff! Let me know if you need testers..

I accidentally overrode the initial version instead of making a -1 release. However the fixed build for fastbooted twrp on lineage-19.1 will be up on twrp.me shortly.