Thanks, I'm going with option 1. However build fails while generating the main ninja file:

bootable/recovery/updater/ error: updater (EXECUTABLES android-x86_64) missing libgpt_static (STATIC_LIBRARIES android-x86_64) 
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.
build/core/ error: exiting from previous errors.

At the moment, I haven't switched to P yet. AFAICS, libgpt_static is provided by repo userfastboot, but it's not included in the O-MR1 manifest. However, it's not included either in master.


On Tue, Sep 25, 2018 at 9:51 PM Tan, Ming <> wrote:


  There are two type of live boot:

  1. GRUB live boot:

       a. Modify: Need to modify the mixin.spec, disable the AVB, slot-ab.

       b. Compile: make SPARSE_IMG=true project_celadon-efi -j 70

            You need to change the 70 to the CPU cores of your build server.

       c. The live boot mode will disable the avb, slot-ab and selinux.

       d. The data of live boot will not be saved.

  2. USB storage live boot:

      a. Need not modify any code.

      b. Compile:

            make SPARSE_IMG=true KERNELFLINGER_SUPPORT_USB_STORAGE=true gptimage -j 70

            You need to change the 70 to the CPU cores of your build server.

      c. The above command will generate a 14G file in out/target/product/cel_apl/ or out/target/product/celadon/

      d. Use dd in linux to flash this file to a USB disk.

      e. Use this USB disk to do live boot directly. BIOS will load kernelflinger in USB disk, and kernelflinger will load Android in USB disk directly.

      f. The Android will support full feature include avb and slot-ab and selinux, like install in the device internal storage.

      g. The data of live boot will be saved.



  For your patch, can you share the detail compile error log? You can add the ‘showcommands’ in your make command line for more detail make commands.


  BR/Tan Ming.


From: Michael Goffioul []
Sent: Wednesday, September 26, 2018 9:02 AM
To: Tan, Ming <>
Subject: Re: [ Celadon] Boot failure


Ok, I'll try that (although my target is really O-MR1, not P). In the meantime, can you answer these 2 questions:

1) I went through the mailing list archive and found instructions from May explaining that mixin.spec needs to be modified to use live boot. Is this till required?

2) Without making any code change, I needed to apply this patch in bootable/liveinstaller for the build to succeed (the same problem already existed in Android-IA):


diff --git a/ b/

index 4c204c4..0a9995b 100644

--- a/

+++ b/

@@ -86,6 +86,7 @@ $(PROJECT_CELADON-EFI): $(GRUB_FILES) | $(install_mbr)

                blksize=$$(($$blksize + $$size)); \

        done; \

        blksize=$$(($$(($$blksize + 64)) * 1024));      \

+       blksize=$$((blksize + (63 - (blksize % 63))));  \

        rm -f $@.fat; mkdosfs -n PROJECTCELADON -C $@.fat $$blksize

        mcopy -Qsi $@.fat $(BOOT_DIR)/* $^ ::






On Tue, Sep 25, 2018 at 8:52 PM Tan, Ming <> wrote:


  The live mode is supported.

  Can you try to use the Celadon P, not O-MR1? Some patchs will only exist in P, not in O-MR1?


  BR/Tan Ming.


From: Celadon [] On Behalf Of Michael Goffioul
Sent: Wednesday, September 26, 2018 8:01 AM
Subject: [ Celadon] Boot failure


I've compiled the celadon image using the omr1 manifest. I trying to boot a device using N2930 CPU, in live mode, but the screen turns black right after selecting the boot entry and the device freeze. I understand this is not part of the officially tested platforms, but I'm willing to debug it (I used to compile Android-IA 7 and 8 and they were running fine on the same platform).


Is the live mode still supported and what can I try to at least get the device to start booting?