TWRP Coral [Official]

Search This thread

japanicana83

Member
Dec 7, 2013
12
3
Columbus
[solved] Flashing the stock rom on my own failed, (flash_all.bat). However using the generic setting on the "tool all in one" application seems to have successfully flashed the rom. I don't understand how, but it did. Leaving the post in hopes that if someone else has this issue, it helps.

I successfully used fastboot to boot to twrp and then successfully copied the twrp image over to the phone and then flashed the twrp to boot.

Now my XL says "error boot prepare" in fastboot and attempting to flash either the original aosip boot or the last stock 10 boot results in FAILED (remote: failed to write to partition Not Found)

Attempting to fastboot install stock 10 failed "upon getting to "image-coral...zip" Not enough space.

Can anyone point me on the path of recovery or has my pixel flashed it's last firmware? Thanks in advance.
 
Last edited:

bigbiff

Senior Recognized Developer
Jun 8, 2010
6,856
7,051
I successfully used fastboot to boot to twrp and then successfully copied the twrp image over to the phone and then flashed the twrp to boot.

Now my XL says "error boot prepare" in fastboot and attempting to flash either the original aosip boot or the last stock 10 boot results in FAILED (remote: failed to write to partition Not Found)

Attempting to fastboot install stock 10 failed "upon getting to "image-coral...zip" Not enough space.

Can anyone point me on the path of recovery or has my pixel flashed it's last firmware? Thanks in advance.

You need to flash a LZMA ramdisk enabled kernel like Kirisakura.
 
  • Like
Reactions: japanicana83

GROOVYJOSHCLARK

Senior Member
  • [solved] Flashing the stock rom on my own failed, (flash_all.bat). However using the generic setting on the "tool all in one" application seems to have successfully flashed the rom. I don't understand how, but it did. Leaving the post in hopes that if someone else has this issue, it helps.

    I successfully used fastboot to boot to twrp and then successfully copied the twrp image over to the phone and then flashed the twrp to boot.

    Now my XL says "error boot prepare" in fastboot and attempting to flash either the original aosip boot or the last stock 10 boot results in FAILED (remote: failed to write to partition Not Found)

    Attempting to fastboot install stock 10 failed "upon getting to "image-coral...zip" Not enough space.

    Can anyone point me on the path of recovery or has my pixel flashed it's last firmware? Thanks in advance.

    I would not install TWRP, just ADB it, when needed. I would reset to the last 10 firmware with -w (backup everything first). What happens when you try to reset the firmware? Post the error logs, but that's your first step to undo the damage done by whatever happened.

    I am not sure exactly what you did, but to me, it sounds like you messed up the partitions hence you cant write to them. Resetting the firmware must be done in my opinion. Can you post step by step what you did to land you there and what status it is now?

    I personally havent used the all in one tool, but if not done carefully, can land you in a mess. I wouldnt use that right now, instead focus on getting the last 10 firmware working (or 11 if you dont care for TWRP).

    On the ADB side, I would make sure my framework is up to date, and make sure my USB/cable is healthy. Its possible you have an outdated ADB, but I think its more likely a partition issue but I could be wrong. These are all "guesses" as I have no way of knowing what was actually done, but thats where I would start and I have gotten my 4XL out of some dirty dark areas of no boot myself. The firmware always rescues me no matter how bad I break it.
     
    Last edited:
    • Like
    Reactions: flash713

    sasory

    Senior Member
    Feb 25, 2010
    610
    461
    Kaliningrad
    It was tough, but I did it. I installed the stock boot, patched the boot again, and only after that the sensor started working. Thanks to everyone who helped !!!
     

    mattwheat

    Senior Member
    Oct 25, 2012
    1,145
    581
    BIRMINGHAM
    Has anybody been able to flash ROMs, kernels, or mods from recovery? Or are we just using it for a way to create a backup? And for that matter has anyone restored a backup that they created through TWRP?
    Thanks in advance for any answers...
     

    Top Liked Posts

    • There are no posts matching your filters.
    • 3
      Any test for Android 12 please?
      TWRP 11 is only in beta very recently so it will take some time before 12 rolls out so please be patient. No ETA's so don't bother asking when 12 will roll out.

      On the 11 note, I tried the latest beta build and it wont go past the TWRP splash screen. Using stock OS with LZMA ramdisk kernel (EX). Does anyone else have luck with the 11 TWRP, and if so, what kernel did they use and what ROM are they on (or stock)?
      2
      How to decrypt data on Android 11, pin doesn't work and won't mount data to format.
      Unfortunately the build has been confirmed that it does work so it's an issue with your specific device. In most of these cases something is corrupted and you may need to do a clean flash to solve it. I've seen very rare cases where the issue was able to be isolated.
      2
      Here is the recovery log from ProtonAOSP with krishna floral on 11 using the latest 11 beta (stuck on splash):

      adb pull /tmp/recovery.log
      2
      You could try pulling the boot.img using ADB after twrp is installed then you'd have your boot and twrp recovery in your boot.img for future installs just fastboot your boot.img to boot partition and you'd have twrp and boot. Stock recovery installing again happened because the boot.img and recovery are together in the boot.img. Recovery is flashed to boot on AB partition devices. There is no seperate partition for recovery on AB devices like there was before AB partition devices. You can also try flashing magisk.zip once twrp is installed and see if it patches your boot.img, just make sure if your flashing both magisk zip and twrp that you fastboot boot twrp then install twrp.img to ramdisk in twrp first then reboot recovery and flash magisk and reboot system. Should work that way, I would think .. I have not done this last twrp and magisk install on my Pixel 4xl yet. I haven't even installed twrp because I'm waiting for more news and didn't want to jump the gun. Not saying that any of what I say here will work and is safe but if I had to have twrp now that's some things I would try.
      TWRP installed , just had to flash a kernel before reboot recovery or the touchscreen wouldn't work. I rooted by installing the magisk apk in recovery. Doesn't seem like it should have worked because it's not a zip or image but it worked no problem
      1
      Tell me how to make a log? I can't install TWRP permanently. Only temporarily.
      Others have already replied, but the easiest way I have found to pull a catlog is through ADB. I am sharing this for others so they can get the right type of logs needed for the devs.

      Make sure you have "USB debugging" enabled in dev options, then from your PC:

      adb shell
      su
      logcat -d > /storage/self/primary/CATLOGNAME.txt

      Most of the time, this is all you need "logcat -d", or the dev will tell you otherwise. If you need (or would like to see more) then you can run: "logcat -v raw" (but it generates a LOT of logs). If an option is not specified with -v on command line, the format defaults to ANDROID_PRINTF_LOG / "threadtime" so you only need to use -v option if you want different log results.

      This will save the current logs to your internal SD called CATLOGNAME.txt (so change it to something useful). This is assuming you have ROOT. The path I used is the storage path for my current ROM (full path so it doesn't hiccup on permissions), but it should work across the board:

      /storage/self/primary/CATLOGNAME.txt

      Using the lower case -d, will write the LOGCAT to the TXT file then close (otherwise the logcat keeps running until stopped). Using the > will "pipe" the results (write to the TXT and not on screen):

      adb logcat -d Dumps the log to the screen and exits

      Android apps work fine as well (CatLog) but it requires you to use/open the app, reproduce the issue, then capture it in the app, whereas ADB does it live from the shell without the back and forth of the app use.
    • 72
      [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.
      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.