TWRP Coral [Official]

Search This thread

legend876

Member
Sep 16, 2022
40
14
Maybe I just gotta wait till there's a more stable build cause the touch not working on a12l either
 
I'm on 12.1 pixel experience is....an I don't know I just boot to it using fastboot boot twrp.img
thats the proper method, I urge newbs all the time, DO NOT INSTALL TWRP, just fastboot it when needed and keep the stock recovery / boot.img, otherwise it doesnt work right! No one listens though, users like to break things trying to appear as they know what they are doing, then it breaks, and users come here and complain X,Y,Z doesnt work, meanwhile they just did it wrong!
 

bigbiff

Senior Recognized Developer
Jun 8, 2010
6,963
7,219
thats the proper method, I urge newbs all the time, DO NOT INSTALL TWRP, just fastboot it when needed and keep the stock recovery / boot.img, otherwise it doesnt work right! No one listens though, users like to break things trying to appear as they know what they are doing, then it breaks, and users come here and complain X,Y,Z doesnt work, meanwhile they just did it wrong!
This happens to work for you well, since fastboot image has it's own built in kernel and modules. Whatever the user installs after a repack, has to work with TWRPs touch interface. A lot of times I have to know exactly what a user has installed to replicate and figure out the issue. A minimum log upload is required for any reasonable help.
 
  • Like
Reactions: GROOVYJOSHCLARK

legend876

Member
Sep 16, 2022
40
14
This happens to work for you well, since fastboot image has it's own built in kernel and modules. Whatever the user installs after a repack, has to work with TWRPs touch interface. A lot of times I have to know exactly what a user has installed to replicate and figure out the issue. A minimum log upload is required for any reasonable help.
On pixel experience android 12 it isn't touching with are without fastboot method also tried it on criod ROM Android 12 an ain't touching either i don't know wats the case are why
 
  • Like
Reactions: ax562
This happens to work for you well, since fastboot image has it's own built in kernel and modules. Whatever the user installs after a repack, has to work with TWRPs touch interface. A lot of times I have to know exactly what a user has installed to replicate and figure out the issue. A minimum log upload is required for any reasonable help.
agreed, and as always BigBiff, let me know if I can help you, or if you need anything from me (or to test/do anything) to help!
 

ax562

Senior Member
Aug 8, 2012
181
106
On pixel experience android 12 it isn't touching with are without fastboot method also tried it on criod ROM Android 12 an ain't touching either i don't know wats the case are why
You are right, I am on LOS19.1/090422 and I used "fastboot flash boot twrp*a12.img " and the touch screen does not work. Also, ufnortunately, a reboot brought me back to twrp and not system. I had to manually flash LOSrecovery090422.img to get system reboot back. I will try to update to latest LOS19.1/0918/22 and go from there. I seen some folks got this to work @GROOVYJOSHCLARK ? What OS are the people on that got this to work and build date? Is there any logs I can provide for debuggin purposes? Any suggestions would be greatly appreciated. Ty for your works @bigbiff

Edit: Forgot to mention that TWRP was asking for passcode to decrypt in which I couldn't press since screen is not working. I will remove passcode. Also, I am rooted using Magisk and no Gapps. I will update Magisk and LOS and report shortly.
 
Last edited:

legend876

Member
Sep 16, 2022
40
14
You are right, I am on LOS19.1/090422 and I used "fastboot flash boot twrp*a12.img " and the touch screen does not work. Also, ufnortunately, a reboot brought me back to twrp and not system. I had to manually flash LOSrecovery090422.img to get system reboot back. I will try to update to latest LOS19.1/0918/22 and go from there. I seen some folks got this to work @GROOVYJOSHCLARK ? What OS are the people on that got this to work and build date? Is there any logs I can provide for debuggin purposes? Any suggestions would be greatly appreciated. Ty for your works @bigbiff
Edit: Forgot to mention that TWRP was asking for passcode to decrypt in which I couldn't press since screen is not working. I will remove passcode. Also, I am rooted using Magisk and no Gapps. I will update Magisk and LOS and report shortlyi

You are right, I am on LOS19.1/090422 and I used "fastboot flash boot twrp*a12.img " and the touch screen does not work. Also, ufnortunately, a reboot brought me back to twrp and not system. I had to manually flash LOSrecovery090422.img to get system reboot back. I will try to update to latest LOS19.1/0918/22 and go from there. I seen some folks got this to work @GROOVYJOSHCLARK ? What OS are the people on that got this to work and build date? Is there any logs I can provide for debuggin purposes? Any suggestions would be greatly appreciated. Ty for your works @bigbiff
Edit: Forgot to mention that TWRP was asking for passcode to decrypt in which I couldn't press since screen is not working. I will remove passcode. Also, I am rooted using Magisk and no Gapps. I will update Magisk and LOS and report shortly.
I didn't get any reboot only just ain't touching but @xorrgnlusrx said he's on the latest Los an it's working fine
 
  • Like
Reactions: ax562

bigbiff

Senior Recognized Developer
Jun 8, 2010
6,963
7,219
You are right, I am on LOS19.1/090422 and I used "fastboot flash boot twrp*a12.img " and the touch screen does not work. Also, ufnortunately, a reboot brought me back to twrp and not system. I had to manually flash LOSrecovery090422.img to get system reboot back. I will try to update to latest LOS19.1/0918/22 and go from there. I seen some folks got this to work @GROOVYJOSHCLARK ? What OS are the people on that got this to work and build date? Is there any logs I can provide for debuggin purposes? Any suggestions would be greatly appreciated. Ty for your works @bigbiff

Edit: Forgot to mention that TWRP was asking for passcode to decrypt in which I couldn't press since screen is not working. I will remove passcode. Also, I am rooted using Magisk and no Gapps. I will update Magisk and LOS and report shortly.
You overwrote the boot partition with TWRP, so android will never boot. You will need to reflash the boot.img with LOS. I would need recovery.log and logcat to debug any touch issues.
 

ax562

Senior Member
Aug 8, 2012
181
106
You overwrote the boot partition with TWRP, so android will never boot. You will need to reflash the boot.img with LOS. I would need recovery.log and logcat to debug any touch issues.
Yes that is what was done on LOS19.1_090422 to recovery_b and once I updated to LOS19.1_091822, twrp*12.img was written to recovery_a. All I did is "fastboot flash boot twrp*12.img" as instructed. From my understanding, this is only supposed to be a temporary flash but again, once flashed I coould not boot system normally. All reboot defaulted back to twrp with no touchscreen access. I also disabled passcode and the problem persisted. I will report recovery.log and logcat shortly @bigbiff
 

Lughnasadh

Senior Member
Mar 23, 2015
4,345
4,855
Google Nexus 5
Huawei Nexus 6P
Yes that is what was done on LOS19.1_090422 to recovery_b and once I updated to LOS19.1_091822, twrp*12.img was written to recovery_a. All I did is "fastboot flash boot twrp*12.img" as instructed. From my understanding, this is only supposed to be a temporary flash but again, once flashed I coould not boot system normally. All reboot defaulted back to twrp with no touchscreen access. I also disabled passcode and the problem persisted. I will report recovery.log and logcat shortly @bigbiff
I think you want to fastboot boot twrp.img, not fastboot flash boot twrp.img
 

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.