TWRP Coral [Official]

Search This thread

stuzor

Member
Dec 31, 2008
37
5
Was smaller than the three I made as well. Strange isn't it?

Didn't help me. Did it fix your issue?

If someone can tell me what I am doing wrong great but I have had my phones rooted for damn near a decade and thus is the most recent set of steps I use.

Installed the latest canary magisk manager. From there wen tto install magisk by patching the boot.img from the version of android I am running by downloading the zip from the google pixel image site for android 11. At this point there is only one file offered for android 11 so it's hard to miss. I extract the image file and take out the boot.img file. I adb push it to my phone. From there I go to install magisk and select the option to patch the boot file or whatever it is called. I select the boot.img file and then patch it. It creates the magisk_patched.img file. I send that to my computer go into fastboot and either have tried installing or just running the file by either doing fastboot boot magisk_patched.img or fastboot flash boot --slot all magisk_patched.img. When I just boot (which worked in version 10) it fails the first boot, goes into recovery and then after clicking try again it rolls back. When i do the flashall I have to reflash the stock boot.img. Anyone have any ideas?
 

mattwheat

Senior Member
Oct 25, 2012
1,143
581
BIRMINGHAM
Once we've got TWRP installed to ramdisk and everything works fine i.e. able to boot back into TWRP by selecting recovery in fastboot without using the computer to boot the boot.img, can we flash other roms just as you would normally from twrp?
 

nikamura

Member
May 18, 2010
23
9
We just got minimal omni10 working yesterday. You can download that now and use my device tree for building.

I haven't pushed out any new builds since it was more of an environment compilation update then feature work.

Thanks for your information.
I'll try build TWRP for pixel4a using minimal omni10 manifest and refering your device tree.

I downloded minimal omni10 and refer yout device tree.
But failed to build.

I create omni_sunfish.mk like aosp_sunfish.mk.

I put this command
. build/envsetup.sh
lunch omni_sunfish-eng
make recoveryimage

ninja: no work to do.

The build ended.

So, I change make command
make bootimage

FAILED: ninja: '/home/takahiro/twrp/out/soong/.intermediates/frameworks/base/hiddenapi-lists-docs/android_common/removed-dex.txt', needed by '/home/takahiro/twrp/out/soong/hiddenapi/hiddenapi-flags.csv', missing and no known rule to make it

Could you give me some advice?
 

bigbiff

Senior Recognized Developer
Jun 8, 2010
6,813
6,890
I downloded minimal omni10 and refer yout device tree.
But failed to build.

I create omni_sunfish.mk like aosp_sunfish.mk.

I put this command
. build/envsetup.sh
lunch omni_sunfish-eng
make recoveryimage

ninja: no work to do.

The build ended.

So, I change make command
make bootimage

FAILED: ninja: '/home/takahiro/twrp/out/soong/.intermediates/frameworks/base/hiddenapi-lists-docs/android_common/removed-dex.txt', needed by '/home/takahiro/twrp/out/soong/hiddenapi/hiddenapi-flags.csv', missing and no known rule to make it

Could you give me some advice?

A/B devices have used the bootimage target for years. Recoveryimage target won't build the boot image you need.
 

nikamura

Member
May 18, 2010
23
9
A/B devices have used the bootimage target for years. Recoveryimage target won't build the boot image you need.

I built TWRP not A/B devices.
I'll try build bootimage. Thanks a lot:)

I use minimal omni10 manifest and omni_sunfish.mk like aosp_sunfish.mk.
lunch omni_sunfish-eng
make bootimage

Build failed.
This is error message
"bootable/recovery/gui/../twrpApex.hpp:18:10: fatal error: 'zip_archive/zip_archive.h' file not found
#include <zip_archive/zip_archive.h>"

include "-I system/core/libziparchive/include/", but fail?:confused:


https://gist.github.com/tnakamur/3858e17c101bbd59cb85f0bec90b111c
 
Last edited:

Madjax2020

Senior Member
Dec 7, 2019
408
57
call me a noob, whatever BUT when we installed TWRP ... if we boot recovery off the slot it was installed to ... TWRP boots up? because i was having some serious issues flashing a ROM and i switched to slot b and rebooted to recovery and BAM .... TWRP popped up

and whatyaknow i flashed another ROM through TWRP .. and it booted up WOW. didnt know this
 

bigbiff

Senior Recognized Developer
Jun 8, 2010
6,813
6,890
call me a noob, whatever BUT when we installed TWRP ... if we boot recovery off the slot it was installed to ... TWRP boots up? because i was having some serious issues flashing a ROM and i switched to slot b and rebooted to recovery and BAM .... TWRP popped up

and whatyaknow i flashed another ROM through TWRP .. and it booted up WOW. didnt know this

When you repack TWRP using the built in boot.img ramdisk repacker, it will flash the repacked boot image to both slots.
 

Madjax2020

Senior Member
Dec 7, 2019
408
57
When you repack TWRP using the built in boot.img ramdisk repacker, it will flash the repacked boot image to both slots.

Thank you @bigbiff for the reply. I think my twrp is on slot b. I can try and switch slots and reboot to recovery. When I flash a ROM then reboot to recovery sometimes I'm in that Roms recovery and not twrp, if that makes sense.
 

mattwheat

Senior Member
Oct 25, 2012
1,143
581
BIRMINGHAM
Ok I got TWRP installed correctly. I know this because I can reboot to bootloader then select recovery and it boots up to TWRP. When I flash any rom it goes thru the process and then says "successful"
I then reboot and it gets stuck in bootloop of the newly flashed rom. If after a while Ill power off then boot to the bootloader. Then select recovery and it'll then go to the temp recovery built into the rom I'm trying to flash. But once I boot to bootloader again it comes back up to my stock rom like nothing had ever happened. I'm lost. Lmao.
 

grape12

Member
Jul 29, 2017
12
0
Quote:
Originally Posted by bradical711

Which ROM?
DU.

Same issue with AOSIP. When TWRP loads, there is an * in the pin area. I removed it and entered the pin. Also tried leaving * and entering pin. No luck.
 

Daisymae

Senior Member
Mar 4, 2014
380
53
Quote:
Originally Posted by bradical711

Which ROM?
DU.

Same issue with AOSIP. When TWRP loads, there is an * in the pin area. I removed it and entered the pin. Also tried leaving * and entering pin. No luck.
Yeah, it's the Sept update that's doing it. The Aug ROM did it till Bigbiff came out with an update.
 

marbertshere

Senior Member
Feb 21, 2014
1,037
206
San Jose
Please forgive me as it's been so long since I've strayed from stock Android. From what I've read so far, I would be able to flash ROMs, make and restore backups, and keep magisk/twrp with the latest build, correct?
 

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