We need answer in Indonesian likely. Need parse issue truncated? User says error: FAILED: ninja: 'vendor/xiaomi/apollo/proprietary/vendor/lib64/ likely incomplete. Need advise. Need perhaps common LineageOS bring-up with vendor blobs missing from build due to proprietary-files extraction, path, symlinks, 32/64, vendor makefile missing. Need ask paste complete error but can provide likely causes/fixes. Need reason about AOSP/Lineage build. Error `ninja: 'vendor/xiaomi/apollo/proprietary/vendor/lib64/...' missing and no known rule to make it` typically due to vendor blobs not extracted or Android.bp/Android.mk referencing missing file. SM8250 apollo Xiaomi Mi 10T Pro? "apollo" is Xiaomi Mi 10T/Mi 10T Pro? Actually Apollo = Redmi K30S Ultra / Mi 10T, code apollo. LineageOS 21 unofficial maybe. Need explain. Potential command `mka bacon` fails because modules prebuilt firmware/lib file named in proprietary-files.txt but extraction didn't happen, or vendor tree points to path but file absent due to new partition structure and arch. Need check. Need discuss vendor/xiaomi/apollo/proprietary directory is usually generated by `extract-files.sh` using adb from stock ROM. Need run: ``` source build/envsetup.sh breakfast apollo ./extract-files.sh path/to/dump ``` or ``` ./vendor/xiaomi/apollo/extract-files.sh /path/to/dump ``` if using device tree vendor? Actually path: lineage has vendor/xiaomi/apollo from TheMuppets? For extraction, in device/xiaomi/apollo perhaps `extract-files.sh`. In many modern trees: `vendor/xiaomi/apollo` is blobs repository; extraction script puts into it. If manually cloned TheMuppets, should exist. Need identify exact missing filename. User's message cut after lib64/. Need ask to post full error. But can share commands to diagnose: ``` ls -l vendor/xiaomi/apollo/proprietary/vendor/lib64/ find vendor/xiaomi/apollo/proprietary -maxdepth 3 -type f | head grep -R "vendor/lib64/" -n . ``` `ninja: error: '...', needed by '...', missing and no known rule to make it` means file referenced from `.mk`, `.bp`, or proprietary-files? Need run `mka bacon -j1`? no. Use `m bacon`? Build output. Common fixes: - Ensure blob repo populated, symlinks? For `vendor/xiaomi/apollo` expected proprietary files. Check if directory has only Android.mk / BoardConfigVendor.mk / .git. Run extraction. - Ensure all `proprietary-files.txt` entries extracted: `vendor/xiaomi/apollo/proprietary/lib64/...` etc. Note `vendor/lib64` prefix. Some blobs might be optional: in proprietary-files.txt prefix with `-`. If file does not exist in stock ROM, extraction skips; if referenced from generated Android.bp? Usually generated by `extract_utils`. - Use correct dump matching exact firmware build. Run from device connected in recovery? `adb root`, mount system/vendor. Use `./extract-files.sh` with rom directory. - For LineageOS 21 Android 14, use proper extraction script from device tree and blob branches matching. `TheMuppets/proprietary_vendor_xiaomi_apollo` for lineage-21? If absent, extraction. Maybe apollo uses `device/xiaomi/apollo` from TheMuppets? Need mention vendors mismatch can cause missing files: device tree expects blob not in vendor. Need sync branches/commits. - `mka bacon` maybe from `m` alias; run `make bacon` or `mka bacon` not relevant. - `vendor/xiaomi/apollo/proprietary/vendor/lib64/` path trailing slash suggests missing item maybe library. Ensure no dangling path due to file list including empty directory? Ninja doesn't need directory. - SELinux file_contexts? Not cause missing build prerequisite. lib link? If prefixed path in product copy files? Need maybe specific to LineageOS builds: AOSP includes generated `Android.mk` in vendor tree that defines modules for `$(LOCAL_PATH)/proprietary/vendor/lib64/lib*.so`. If a blob is a symlink to another missing blob? For example vendor/lib64/libqdMetaData.so? If symlinks in proprietary blobs repo created as plain text? Git cannot preserve symlinks? It can. Some blobs symlink. Missing because `git lfs`? No. Could be `vendor/xiaomi/apollo/proprietary/vendor/lib64/libQnnHtp.so` etc. Need formulate response: start by saying error not complete; need full line. But likely. Need include step-by-step: 1. Clean and verify environment: ``` cd ~/android/lineage source build/envsetup.sh breakfast apollo ``` 2. Check that blobs extracted: ``` ls vendor/xiaomi/apollo/proprietary ls vendor/xiaomi/apollo/proprietary/vendor/lib64 | head ``` If missing/empty: - obtain stock ROM matching firmware (global/EU etc) - unpack super/firmware; for Android 14 system/vendor - run extraction: ``` cd device/xiaomi/apollo ./extract-files.sh /path/to/dump ``` or if script in `vendor/xiaomi/apollo`: ``` ./vendor/xiaomi/apollo/extract-files.sh /path/to/dump ``` But modern Lineage scripts are usually in `device/xiaomi/apollo` or `vendor/xiaomi/apollo`. Use `find`: ``` find . -path '*apollo*' -name extract-files.sh ``` Need note `extract-files.sh` may expect `adb` not directory; some accepts path. Use `--help`. - Alternative clone proper TheMuppets repo: ``` git clone https://github.com/TheMuppets/proprietary_vendor_xiaomi_apollo -b lineage-21 vendor/xiaomi/apollo ``` But branch could not exist. Need caution. For unofficial device? Use repo from device maintainer. Avoid blindly cloning mismatched. If using lineage-21 maybe TheMuppets branch. If repo is already there, reset/clean. 3. If file listed in `proprietary-files.txt` but not from ROM, update device tree for your blob version: ``` grep -R "" device/xiaomi/apollo vendor/xiaomi/apollo ``` If line in proprietary-files, verify exact file exists in stock dump. If it doesn't, maybe wrong stock firmware or file should be optional `-`. Do not just delete line unless understand. For optional: Edit proprietary-files.txt, prefix with `-` to allow missing (old convention? In Lineage extraction, `-` means optional? Need verify. In proprietary-files extraction, prefix `-` in list means remove? Let's recall `extract_utils` line syntax. Example: ``` # All blobs are extracted # Prefix with '-' to disable extraction -lib64/libfoo.so ``` Actually in Lineage extraction script, `proprietary-files.txt`: A line prefixed with `-` is treated as `DISABLE`? Let's check memory. In `extract_utils.sh`, entries can be prefixed: - `-` means optional? Let's remember from LineageOS wiki: "If a blob is available on multiple devices, use `-` to check?"; In `extract-files.py`, syntax: ``` # Ignore a line by prefixing with # # Add optional blobs with ` - ` prefix? # Lines starting with - are ignored (disabled)?? ``` I have seen proprietary-files.txt: ``` # RenderScript -system/vendor/lib/libRS.so ``` No, examples: `-vendor/lib/libwvhidl.so` maybe means "do not extract for some source"? Let me recall from LineageOS proprietary-files: often lines: ``` # Blobs necessary for Crypto vendor/lib64/libQSEEComAPI.so ``` At end optional lines: ``` # Not present in all versions -vendor/lib64/libqdMetaData.so ``` Maybe `-` means disabled, while no `-` required. Also `+`? Actually `extract_utils.sh` uses: ``` # Get file list if [ -f "$MY_DIR/proprietary-files.txt" ]; then SRC_LIST="$(grep -v '^#' ... | sed -e 's|^-||')" ... ``` Could be prefix `-` means "do not fail if missing" yes I think optional? Need be precise. Look up memory: In many proprietary-files.txt from Lineage: ``` # Sensors vendor/lib64/libdiag.so ``` A line with `-` means "do not extract; need from source"? Hmm. I recall `extract-files.sh` output: To skip removing existing file? The utility `extract_utils.sh` defines functions. It parses: ``` if [[ "$line" == -* ]]; then line="${line#-}" DISABLE_DEPS= fi ``` I used LineageOS. In `vendor/lineage/build/tools/extract_utils/extract_utils.sh`, in `parse_file_list`, for each line: ``` # If the line starts with a dash, it should be ignored when checking for dependencies. if [[ "$line" =~ ^- ]]; then line=${line:1} DO_NOT_CHECK_DEPS=1 fi ``` Not sure. Need avoid asserting optional syntax incorrectly. Say "tandai optional/sesuai konvensi tree Anda" or use `--section`? Better. 4. If file is referenced by local device vendor makefile but not in blob repo: path case and architecture. The error path includes `/vendor/lib64/` under proprietary, but Android.mk should copy from `proprietary/vendor/lib64` to target `vendor/lib64`. If symlink e.g. `libc++.so`? check. ``` ls -l vendor/xiaomi/apollo/proprietary/vendor/lib64/ ``` If symlink target missing: ``` find vendor/xiaomi/apollo/proprietary -type l -xtype l ``` Fix by re-extracting, restore symlink, or use `extract-files.sh`. 5. Search build graph for who needs it: ``` grep -R "nama-file" -n device/xiaomi/apollo vendor/xiaomi/apollo vendor/qcom/opensource ``` or use `ninja -t query`? AOSP has `ninja -C out/soong/build` etc. Easier: ``` grep -R "$(basename missingpath)" . ``` Focus in `out/soong/build.ninja`? It may be generated: ``` grep -R "" out/soong/build.ninja out/soong/Android-*.mk 2>/dev/null | head ``` Generated makefile in `out/soong/Android-*.mk` may reference. But simpler. 6. If path uses `TARGET_COPY_OUT_VENDOR`? Need note Android 10+ dynamic partitions / vendor. For Android 14 with vendor partition, blobs under `/vendor`; many trees move `/system/lib` etc. Path in proprietary files has `vendor/lib64`. If vendor blobs are in `vendor/xiaomi/apollo/proprietary/system_ext` etc, ensure `BOARD_VENDOR_SEPOLICY_DIRS` not. Missing prerequisite not sepolicy. 7. Clean build after changes: ``` make clean # or more targeted rm -rf out/target/common/obj/PACKAGING/target_files_intermediates m clobber # heavy source build/envsetup.sh lunch lineage_apollo-userdebug mka bacon ``` Actually `make clean` unnecessary but if generated files stale, use `m installclean` or remove `out/soong/.bootstrap`. Need recommend after re-extract: `make clean` maybe huge, but safe. Or `rm -rf out/target/product/apollo/vendor`? Better use `mka bacon` will regenerate. 8. Dependencies: `repo sync -j...`, `source build/envsetup.sh`, `lunch lineage_apollo-userdebug`, `mka bacon`. Maybe issue from absent proprietary blobs with `git lfs`? TheMuppets no LFS. Check `vendor/xiaomi/apollo` tracked in `.repo/local_manifests`? Missing because `repo sync` didn't include TheMuppets due local manifest only device/kernel. Add local manifest: ``` ``` But line. 9. Name `apollo` maybe codename? Xiaomi apollo has SM8250. Android 14 LineageOS 21; source branch. Need specific device tree likely by "xiaomi-sm8250-devs"? Could have vendor repo. Search GitHub. But we can't browse. Could mention "ambil vendor tree dari maintainer yang cocok dengan device tree; jangan campur lineage-20/21". Need perhaps explain mka bacon error when `vendor/xiaomi/apollo/proprietary/vendor/lib64/` missing directory entirely. Could be because `vendor/xiaomi/apollo` repo is not in `repo` manifest. Need confirm by `ls`. Potential full error common: ``` FAILED: ninja: 'vendor/xiaomi/apollo/proprietary/vendor/lib64/libcapability.so', needed by 'out/target/product/apollo/.../vendor/lib64/libcapability.so', missing and no known rule to make it ``` or `vendor/xiaomi/apollo/proprietary/vendor/lib64/libwvhidl.so`. The path with no filename in prompt maybe due truncation in chat; perhaps exact missing file after slash. We can ask. Need provide diagnostic commands. Need be careful: For Android 14, `libwvhidl.so` likely moved? But no. Let's craft robust Indonesian answer. Since user likely expects solution. Start: "Errormu terpotong; pesan lengkap mutlak. Tapi pola ini umum: Ninja tidak menemukan blob prebuilt yang dideklarasikan `Android.mk`/`Android.bp` di vendor tree. Artinya build graph tahu harus copy file itu, tetapi filenya tidak ada / symlink target hilang / ekstraksi belum lengkap / vendor tree mismatch." Then sections: A. Quick check: ``` cd ~/android/lineage ls -l vendor/xiaomi/apollo/proprietary/vendor/lib64/ find vendor/xiaomi/apollo/proprietary -type l -xtype l grep -R "$(basename MISSING_FILE)" -n device/xiaomi/apollo vendor/xiaomi/apollo | head find . -name extract-files.sh -path '*apollo*' ``` If missing file exactly. Also check `git status` in vendor repo: Git can't store empty dirs. If doesn't exist but declared, add repo. B. If blobs not present -> extract: ``` ./device/xiaomi/apollo/extract-files.sh /path/to/stock_dump # or script location found above ``` Need use ROM matching firmware: - Same region/model (apollo) and build fingerprint as device tree expects. - For Android 14 maybe stock HyperOS/Android 13 ROM? blobs from appropriate stock. - If using `adb`: ``` adb root adb remount ./extract-files.sh ``` Actually script usage varies. Better: ``` ./extract-files.sh -h ``` Then run with path. C. If using TheMuppets: ``` repo sync --force-sync vendor/xiaomi/apollo ``` or: ``` git -C vendor/xiaomi/apollo clean -xdf git -C vendor/xiaomi/apollo reset --hard ``` But if not in manifest: ``` # add to .repo/local_manifests/apollo.xml ``` Example but branch caveat: ``` ``` Then sync. Note if unofficial branch, use maintainer's repo. D. If file is symlink broken: ``` find vendor/xiaomi/apollo/proprietary -type l -xtype l -print ``` Fix by re-extract or create correct symlink from source stock (don't create empty dummy). Could use `ln -sf ...`; but do not copy random. For missing blob in vendor tree but exists in `proprietary/...` with 32/64 mismatch? Need ensure expected architecture and path. Example maybe `/vendor/lib64/libfoo.so` but extracted to `vendor/lib64/libfoo.so`? Actually under proprietary then. E. Mismatch device/vendor: - `device/xiaomi/apollo`, kernel, and `vendor/xiaomi/apollo` must be from same lineage-21 branch/commit. If one uses Android 13 vendor tree, it references old blobs and makefile names. Sync matching. - Maintainer's `vendor/xiaomi/apollo` may not be official. Check `lineage_apollo.mk` inherits `vendor/xiaomi/apollo`. - `repository` file? Check `vendor/xiaomi/apollo/Android.mk` for package name and files. F. If proprietary-files list references it but source ROM doesn't include: - It can be optional; use proper extraction script. Do not simply `touch` dummy .so (will bootloop/crash). - Update `proprietary-files.txt`, `device-vendor.mk`, or blob repo to match dump. If maintainer tree expects file from a particular MIUI version, use that version. - If it is not needed, remove from makefile *and* proprietary-files; if needed, get correct blob from matching firmware. Need vendor symlink? For VNDK? important. - For ELF missing, could be symlink to e.g. `libfoo.so` in system. Check `readelf`/`file`. G. Clean & rebuild: ``` source build/envsetup.sh breakfast apollo # or lunch lineage_apollo-userdebug make installclean mka bacon ``` If changed `vendor` makefiles and it still refers deleted path: ``` rm -rf out/soong/.bootstrap out/soong/build.ninja out/target/product/apollo source build/envsetup.sh lunch lineage_apollo-userdebug mka bacon ``` Maybe `mka` target? Use `m bacon`? `mka` from `m`? The user likely. We can just `mka bacon`. Need mention check full file: ``` FAILED: ninja: 'vendor/xiaomi/apollo/proprietary/vendor/lib64/', needed by ... ``` "kirim baris lengkap + file apa + output `ls -l` path + grep list, nanti bisa pinpoint." Could include "jika error persis berhenti di `.../lib64/` tanpa nama file, berarti output terpotong; Ninja tidak pernah komplain directory kosong." A directory alone cannot be missing? Ninja can have directory as output? It could be `vendor/xiaomi/apollo/proprietary/vendor/lib64/` as path trailing, likely truncated by UI. The actual target is a file. Need mention. Maybe we can infer from any known common file. Let's search memory of SM8250 apollo LineageOS failures. Could be specific missing library: `libwfdaac_vendor.so`, `libTrustZoneOptimizedProcess.so`, `libVendorMiuiCamera`? Xiaomi apollo. Maybe on Xiaomi apollo, common missing blob `vendor/lib64/libqcodec2_core.so`? Hmm. But without full error, not specific. Need maybe answer with exact repo name: `TheMuppets/proprietary_vendor_xiaomi_apollo`. Does TheMuppets have apollo? Search memory: TheMuppets has many `proprietary_vendor_xiaomi_apollo` possibly. Xiaomi SM8250: apollo, alioth, lmi, umi, cas, cmi? `apollo` is Redmi K30S Ultra/Mi 10T. TheMuppets likely. Branch? LineageOS official supports `apollo`? LineageOS 21 supported device list maybe apollo? It may be `apollo` (Mi 10T/10T Pro/Redmi K30S Ultra) currently? LineageOS 21 official supports `apollo`? Maybe not. If unofficial, branch `lineage-21` in maintainer repos. Use `lineage-21`. Potential cause: vendor blobs repo cloned but not recursive? TheMuppets no submodules maybe LFS? no. Need address dynamic partitions and `vendor/` symlinks: In vendor blob tree, for devices using `PRODUCT_COPY_FILES` to copy from vendor: `vendor/xiaomi/apollo/proprietary/vendor/lib64`. If build references path in generated `Android.mk` but file doesn't exist due to case? Linux case sensitive. Need include checking file list manually: ``` grep -n "" vendor/xiaomi/apollo/*.mk vendor/xiaomi/apollo/*.bp vendor/xiaomi/apollo/proprietary-files.txt device/xiaomi/apollo/*.mk device/xiaomi/apollo/*.bp ``` But vendor generated `Android.mk` often in root and has many. `grep -R`. Need include "jangan pakai file dummy/touch: build might lolos tetapi runtime crash karena ELF invalid." Strong caution. Maybe use `git rev-parse HEAD` of device and vendor and compare in maintainer manifest. Provide: ``` git -C device/xiaomi/apollo log -1 --oneline git -C vendor/xiaomi/apollo log -1 --oneline ``` Then repo sync force. Need perhaps answer about `mka bacon` failing due to missing `vendor/xiaomi/apollo/proprietary/vendor/lib64/` *directory* not file: AOSP's `PRODUCT_COPY_FILES` can copy directories? `PRODUCT_COPY_FILES` expects files, not dirs. If line lacks wildcard? `PRODUCT_COPY_FILES += vendor/xiaomi/apollo/proprietary/vendor/lib64:$(TARGET_COPY_OUT_VENDOR)/lib64`? AOSP cannot copy dirs. But error prints directory, maybe indeed a directory is an input. Could be `LOCAL_PREBUILT_LIBS += ...`? Need consider. If `PRODUCT_COPY_FILES` references a directory as source, Ninja error `'vendor/xiaomi/apollo/proprietary/vendor/lib64/' missing ...`? Actually `PRODUCT_COPY_FILES` line could be malformed: colon and path. But likely not. If full path ends in slash as directory, could be due to missing variable expansion in makefile, e.g. `PRODUCT_COPY_FILES += vendor/xiaomi/apollo/proprietary/vendor/lib64/:...`? Build systems don't like dirs. Need tell to check full error and makefile for directory copy; should be individual files via `PRODUCT_COPY_FILES` or use `$(call add-to-product-copy-files-if-exists)`. But Android build transitive requires input file. Another cause is generated file list stale from removed blob. `out/soong/build.ninja` still references removed file. Clean generated outputs. But if user changed vendor tree after build, could stale. This is plausible. Need include early: If file used to exist and removed, run clean. But if fresh sync or build repeatedly, not. Could be caused by `extract-files.sh` symlink: On Windows or filesystem, symlinks represented as text, causing missing? Build on Linux. If using NTFS? no. Need discuss "proprietary/vendor/lib64/" path no filename - "kemungkinan ada `LINE_FOR_MISSING` in `vendor/xiaomi/apollo/Android.mk`, cari semua module prebuilt in that directory. Use: ``` grep -R "proprietary/vendor/lib64" -n vendor/xiaomi/apollo | head -50 ``` Maybe many. But to find missing exactly, full Ninja line. Need maybe mention "build should not use vendor blob repo under `vendor/xiaomi/apollo` if extraction script writes elsewhere. Some device trees expect blobs under `vendor/xiaomi` only for 32-bit; generated by `.repo` etc." Let's structure response with enough detail (desired 5). Avoid too long? We have ample. Indonesian. Potential final: ``` Error itu bukan error compiler, tapi error dependency Ninja. Artinya file input prebuilt tidak ada. Contoh: FAILED: ninja: 'vendor/xiaomi/apollo/proprietary/vendor/lib64/libXYZ.so', needed by 'out/target/product/apollo/vendor/lib64/libXYZ.so', missing and no known rule to make it ``` Then steps. Let's include exact shell commands placeholders. Start with "Kirim baris lengkap, karena nama file penting." But deliver solution. Detailed workflow: 1. Determine missing file and module: ``` export M= ls -l vendor/xiaomi/apollo/proprietary/vendor/lib64/$M find vendor/xiaomi/apollo/proprietary -type l -xtype l grep -R --line-number "$M" device/xiaomi/apollo vendor/xiaomi/apollo | head -20 ``` If no `M`, because prompt truncated. 2. Check vendor repo presence: ``` ls -la vendor/xiaomi/apollo git -C vendor/xiaomi/apollo status git -C vendor/xiaomi/apollo rev-parse --abbrev-ref HEAD git -C vendor/xiaomi/apollo rev-parse HEAD ``` If no files / only `.git`, repository not synced. In `repo`, manifest. Add. Provide local manifest example: ``` mkdir -p .repo/local_manifests cat > .repo/local_manifests/apollo.xml <<'EOF' EOF repo sync --force-sync vendor/xiaomi/apollo device/xiaomi/apollo ``` Caveat: Use repository from device maintainer; if branch unavailable, use correct branch/commit. 3. Extract from stock firmware: ``` adb root adb remount find device/xiaomi/apollo -maxdepth 2 -name extract-files.sh cd device/xiaomi/apollo ./extract-files.sh /path/to/dump ``` or: ``` ./extract-files.sh ``` depending script. Ensure output goes to `vendor/xiaomi/apollo`. If generated files in device tree? The script may write to vendor. Need run from proper cwd: ``` ./extract-files.sh /path/to/stock_rom_directory ``` Modern `extract-files.sh` often expects `adb`, not path? Let's verify from LineageOS: device tree has `extract-files.sh`: ``` #!/bin/bash set -e DEVICE=... VENDOR=xiaomi ... if [ "$1" = "" ]; then SRC=adb else SRC=$1 fi ... ./../../../vendor/lineage/build/tools/extract_utils.sh ... ``` Can accept ADB or directory. Fine. Mention use ROM matching `ro.product.device=apollo`, `ro.build.fingerprint` from `vendor/xiaomi/apollo` / device tree commit. If blob doesn't exist in ROM, the tree expects different firmware. 4. If using prebuilt TheMuppets repo, don't extract over it? Can `repo sync`. If extracted and git repo status dirty, okay. 5. If missing symlink: ``` find vendor/xiaomi/apollo/proprietary -type l -xtype l -ls ``` Fix by reextract; preserve symlinks. Commands to create? avoid. 6. If file listed in `proprietary-files.txt` but absent: ``` grep -R --line-number "$M" vendor/xiaomi/apollo/proprietary-files.txt device/xiaomi/apollo/proprietary-files.txt ``` If line begins `-`? Actually maybe optional. Need phrase: "jika tree versi ini memang opsional, gunakan mekanisme optional pada extract_utils (biasanya prefix `-` atau `?`, tergantung versi `extract_utils.sh`; cek dokumentasi/header file) atau hapus referensi jika memang tidak dibutuhkan. Jangan `touch` dummy." Maybe avoid specifying. 7. Check mismatch: - Device/Kernel/Vendor from same Android version: LineageOS 21 vs 20. If mix, `Android.bp`/`Android.mk` reference a file not in one blob branch. - Use maintainer's commit. 8. Clean: ``` source build/envsetup.sh breakfast apollo mka installclean # or rm out... rm -f out/soong/build.ninja mka bacon ``` Need not delete entire out? `make clean` yes. If only stale: ``` rm -rf out/soong/.bootstrap out/soong/build.ninja ``` But Android build system may have more. `m clobber` impossible if build fails? `m clobber` can. Standard: `make clean` or `mka clean`. Actually AOSP has `m clean`? `m clean` works? `make clean`. Use `mka clean`? In AOSP, `m clean` runs clean? I think `m` can run targets, `m clean` maybe. Simpler: ``` rm -rf out source build/envsetup.sh lunch lineage_apollo-userdebug mka bacon ``` Heavy but reliable. Mention if sure. 9. If only one optional blob missing and you cannot get it, not recommended. Explain if missing library is required for hardware, it may cause no boot. 10. Request full log: ``` mka bacon 2>&1 | tee build.log grep -n -A3 -B3 "FAILED: ninja" build.log | tail -50 ``` Post: - full FAILED line through `missing and no known rule` - path `ls -l` of file - output of `grep -R` for file - branches/commits of device/vendor. Need perhaps include explaining "mka bacon includes `bacon` target (OTA zip); for debug use `mka systemimage` or `mka` to isolate." Maybe not. Need mention AOSP generated `proprietary/vendor/lib64` usually managed by `Soong` module generated by `extract_utils`: check `vendor/xiaomi/apollo/Android.mk` has `LOCAL_MODULE := lib...` and `LOCAL_SRC_FILES := proprietary/vendor/lib64/lib...`. If source file absent. For prebuilt modules, can use `LOCAL_CHECK_ELF_FILES := false`? No not relevant. Missing file still. Need include path with `apollo` and `SM8250`: Some blob names depend on Qualcomm. The `vendor/lib64` can be from `system/vendor/lib64`; with GKI etc. Need mention mount `super`: for Android dynamic partitions, stock firmware dump needs `system`, `system_ext`, `product`, `vendor`, `odm`, and `odm_dlkm/vendor_dlkm`? For `/vendor/lib64`, only vendor. But if kernel modules missing maybe other errors. Potential issue with proprietary vendor repo generated for different partition layout: In `proprietary-files.txt` entries: ``` vendor/lib64/lib... ``` extract to `vendor/xiaomi/apollo/proprietary/vendor/lib64/lib...`. If file is a symlink `vendor/lib64/libfoo.so -> /system/lib64/...`? Extraction script handles. If source has symlink and destination doesn't, maybe not. Could include command to list all broken symlinks before build; but a missing regular file cannot be found by type broken if absent. Need maybe include command to check Git LFS: ``` git -C vendor/xiaomi/apollo lfs ls-files ``` Not likely. TheMuppets does not use LFS. Skip. Need discuss `repo sync` with `--force-sync` because generated vendor tree may have been partially copied by extract script; subsequent `repo sync` errors. Use: ``` repo sync -c --force-sync --no-clone-bundle vendor/xiaomi/apollo ``` Commit mismatch. Need be precise with `breakfast` vs `lunch`: For LineageOS, `breakfast apollo` does lunch. Fine. Need ensure no hallucinated optional prefix. Let's either omit prefix or phrase "lihat header proprietary-files.txt; extract_utils mendukung penanda optional, tetapi sintaks dapat berbeda." Good. Let's consider if the user might expect a fix for specific missing file after slash. Could we ask first? But final should be useful. Need maybe mention "pastikan `ALLOW_MISSING_DEPENDENCIES=false`? Do not set `ALLOW_MISSING_DEPENDENCIES=true` or `BUILD_BROKEN...`; build may pass but package missing. Not recommended. If debug only, no." There are flags `BUILD_BROKEN_MISSING_REQUIRED_MODULES := true`? Not recommend. Could mention "jangan membuat folder kosong; Git tidak track, Ninja tidak butuh dir." If error literally directory missing: ``` mkdir -p vendor/xiaomi/apollo/proprietary/vendor/lib64 ``` won't solve because the actual file is what's required. Don't do. Need mention "for vendor blobs, file name in build is relative to source tree; ensure checkout includes vendor subdir. Some proprietary repos use `proprietary/vendor/lib64` and `proprietary/system/lib64`; don't move manually." Maybe include an example diagnostic with ``: ``` MISSING="libfoo.so" test -e vendor/xiaomi/apollo/proprietary/vendor/lib64/$MISSING && echo OK || echo MISSING ``` If the error path includes e.g. `libfoo.so`, set. Need answer in Indonesian with moderate length. The final should not include markdown too insane but can use headings. Let's outline final: ``` Pesan error LineageOS kamu terpotong; bagian setelah lib64/ penting. Tapi pola `FAILED: ninja: '...`, needed by ..., missing...` artinya file prebuilt blob tidak ada ketika Ninja menyusun image. Ini bukan compiler. Langkah cepat: 1. Ambil error lengkap... 2. Cek file... 3. Cari referensi... ``` Then "Kemungkinan dan solusi". Could be worth giving a "paling umum" conclusion: If `vendor/xiaomi/apollo/proprietary` absent/empty, vendor blobs belum diekstrak/sync. Solve with TheMuppets or extract-files. If exists but one file missing, mismatch blobs. If broken symlink, reextract. If stale out, clean out. Need include exact commands for extraction. Let's write. Start: ``` cd ~/android/lineage source build/envsetup.sh breakfast apollo find device/xiaomi/apollo -maxdepth 3 -name extract-files.sh -print ``` Then: ``` cd device/xiaomi/apollo ./extract-files.sh /path/to/stock_dump_apollo ``` Or if script lives in `vendor/xiaomi/apollo`: ``` ./vendor/xiaomi/apollo/extract-files.sh /path/to/stock_dump_apollo ``` Actually command relative to root if in vendor. Add note depending on script. Then: ``` cd ~/android/lineage git -C vendor/xiaomi/apollo status --short find vendor/xiaomi/apollo/proprietary -type f | wc -l find vendor/xiaomi/apollo/proprietary -type l -xtype l -print ``` For TheMuppets: ``` repo sync --force-sync device/xiaomi/apollo kernel/xiaomi/sm8250 vendor/xiaomi/apollo ``` or with exact kernel? Xiaomi apollo uses `kernel/xiaomi/sm8250` maybe. Device kernel path maybe `device/xiaomi/sm8250-common`? Actually apollo uses common tree `device/xiaomi/sm8250-common`? Need no need. Use placeholders: ``` repo sync --force-sync device/xiaomi/apollo device/xiaomi/sm8250-common vendor/xiaomi/apollo ``` But common repo names uncertain. Could avoid kernel names. Local manifest example with caution. Maybe mention if `repo sync` says no project. If already there, force reset. Need mention checking `lineage_apollo.mk`: ``` grep -R "vendor/xiaomi/apollo" -n device/xiaomi/apollo ``` Maybe device tree has `$(call inherit-product, vendor/xiaomi/apollo/apollo-vendor.mk)`. If vendor repo in source but missing file because branch: ``` git -C vendor/xiaomi/apollo branch -a ``` Pick `lineage-21`. If none, from maintainer. `TheMuppets` may have `lineage-21`. If branch not available, use commit from local manifest. Diagnose reference: ``` FILE="$(basename /path/di/error)" # copy exact grep -R --line-number "$FILE" device/xiaomi/apollo vendor/xiaomi/apollo | head -50 ``` Need full error. Alternatively, search all missing: ``` ``` If file declared by generated `vendor/xiaomi/apollo/Android.mk`, the `proprietary-files.txt` line may be in device tree. Broken symlink: ``` find vendor/xiaomi/apollo/proprietary -xtype l -ls ``` `-xtype l` works for broken? GNU find: `-xtype l` means symbolic link to non-symlink? Actually `-xtype l` checks if file is symlink for other types? Let's recall: `-xtype c` same as `-type` unless file is symlink, then checks target type. For broken symlink, `-xtype l` returns true? A broken symlink has target type unknown; `-xtype l` may true? Better use `find ... -type l ! -exec test -e {} \; -print`, but that has shell complexities. Common: ``` find vendor/xiaomi/apollo/proprietary -type l -xtype l ``` This finds dangling symlinks? I think yes: `-xtype l` for broken symlinks? Let's verify. GNU find: `-xtype l` true for broken symbolic links? Example common command: `find . -xtype l` lists broken symlinks. Yes. Good. If broken: ``` # jangan ln manual dulu; jalankan ulang extract-files / sync repo ``` If something not extracted due to firmware: ``` # example dump mount mkdir -p ~/apollo_dump # extract super? ``` Not needed. Clean: ``` cd ~/android/lineage rm -rf out/target/product/apollo out/soong/build.ninja source build/envsetup.sh breakfast apollo mka bacon ``` Maybe `rm -rf out/soong/build.ninja` not enough; recommend: ``` rm -rf out ``` or `make clean` before full. Say "untuk memastikan tidak stale, `make clean`; jika mau cepat, hapus minimal...". Actually `make clean` also huge. Use: ``` mka clean ``` I think `mka clean` works but use `make clean` known. Important: Running extract after or before lunch? Script may need env. Usually run source envsetup and breakfast first. Mention. Need discuss don't use `ALLOW_MISSING_DEPENDENCIES`: ``` # jangan: ALLOW_MISSING_DEPENDENCIES=true mka bacon ``` or `BUILD_BROKEN_ELF_PREBUILT_PACKAGE_COPY := true`? Not appropriate. It may hide. Need include "jika file itu memang tidak dibutuhkan, perbaiki makefile/source list. Contoh cari di `vendor/xiaomi/apollo/Android.mk` and remove module or in `proprietary-files.txt`. But removing required lib can make ROM fail boot." Advice. Let's consider exact Android build error flow. For prebuilt ELF, Soong's `cc_prebuilt_library_shared` source can be missing. Ninja error path refers to source. For vendor makefile generated by `extract_utils` using Make, modules may be `LOCAL_PREBUILT_LIBS`? Actually generated `Android.mk` includes: ``` include $(CLEAR_VARS) LOCAL_MODULE := lib... LOCAL_MODULE_CLASS := SHARED_LIBRARIES LOCAL_MODULE_SUFFIX := .so LOCAL_SRC_FILES := proprietary/vendor/lib64/lib... LOCAL_MODULE_PATH := $(TARGET_OUT_VENDOR)/lib64 ... ``` If file missing, ninja errors. Also symlinks in repo from TheMuppets maybe not preserved if using no git. Good. Could mention `vendor/xiaomi/apollo/proprietary/vendor/lib64` path itself can be absent if extraction script wrote `proprietary/vendor/lib64` under wrong output. Check `extract-files.sh` line `VENDOR_REPO` maybe environment. ``` bash -x ./extract-files.sh ... ``` may show. Maybe user wants "mka bacon error due to ..." Need response could be moderately concise but include enough. Let's draft final in Indonesian: ``` Errormu terpotong setelah lib64/. Kalau pola lengkapnya: FAILED: ninja: 'vendor/.../lib64/libXYZ.so', needed by ... ``` Then details. Need not mention "I can't solve without complete". But ask to send if still. Let's include a section "Kesimpulan singkat". Maybe start with: "Paling umum: vendor blobs belum lengkap. Jalankan extraction atau gunakan repo vendor yang cocok. Jangan bikin file dummy." Then commands. Let's write final with headings. Potential exact command: ``` cd ~/android/lineage source build/envsetup.sh breakfast apollo ``` Find extraction: ``` find device/xiaomi/apollo vendor/xiaomi/apollo -name extract-files.sh -print ``` Then: ``` cd device/xiaomi/apollo ./extract-files.sh /path/to/apollo-stock-dump ``` If fails due permission: ``` chmod +x extract-files.sh ``` No. After extraction, recheck file: ``` ls -l vendor/xiaomi/apollo/proprietary/vendor/lib64/ ``` Wait if currently in device dir, path relative root. In command, specify: ``` cd ~/android/lineage ls -l vendor/xiaomi/apollo/proprietary/vendor/lib64/ ``` If TheMuppets: ``` repo sync --force-sync vendor/xiaomi/apollo git -C vendor/xiaomi/apollo checkout lineage-21 git -C vendor/xiaomi/apollo reset --hard git -C vendor/xiaomi/apollo clean -xdf ``` Caveat: checkout before reset. But force sync enough. `git clean -xdf` wipes local extraction (if this is a git checkout). Do not use if you have local modifications? Mention. Local manifest example: ``` ``` Maybe remote omitted; repo may know github default? Actually project tag needs `remote`. TheMuppets name under GitHub known as `TheMuppets` remote. Without remote could default? In repo manifest, `remote` required? `default` remote if omitted. Simpler include `remote="github"` but that remote must exist. Lineage default manifest may define `remote="github"`. Could avoid full manifest and say add via `repo` from maintainer. But useful. Could mention if using official LineageOS, local manifests not needed because `roomservice` auto-add. For unsupported/unofficial, repo init manifest not include vendor; add manually or `breakfast` may use `lineage_apollo.mk` missing. Actually `breakfast` may auto-fetch from `lineage.dependencies`? `roomservice` uses `lineage.dependencies` from device tree to fetch dependencies? For Lineage, `breakfast` can run roomservice to add missing repos from `lineage.dependencies`? It adds dependencies in `.repo/local_manifests/roomservice.xml`. For `apollo` if not official, maybe dependencies. Need include `source build/envsetup.sh; breakfast apollo` before extraction? fine. Need mention check if `vendor/xiaomi/apollo` is gitignored? No. Potential issue: `mka bacon` target uses `bacon` only in Lineage. Error from `ninja` before packaging. No. Let's formulate final answer: ``` Jawaban singkat: file prebuilt yang dideklarasikan tidak ada. Perbaiki sumber blob; bukan dengan touch. ``` Then detailed. I think final deliverable: - explanation - commands to diagnose - extraction/sync solutions - check mismatch and symlinks - clean build - ask for complete error if still. Let's write in Indonesian with code blocks. Avoid overly long but enough. Pesan error kamu terpotong setelah `.../vendor/lib64/`, jadi nama file yang hilang belum terlihat. Akan tetapi pola `FAILED: ninja: 'vendor/xiaomi/apollo/proprietary/vendor/lib64/...' missing and no known rule to make it` hampir selalu berarti: > File blob/prebuilt yang dideklarasikan oleh device/vendor tree tidak ada di source tree saat Ninja membangun image. Ini **bukan error compiler**. Yang perlu diperbaiki adalah ketersediaan file blob atau referensinya. ## 1. Ambil error lengkap dulu Jalankan: ```bash cd ~/android/lineage source build/envsetup.sh breakfast apollo mka bacon 2>&1 | tee build.log ``` Cari baris lengkapnya: ```bash grep -n -A4 -B4 "FAILED: ninja" build.log | tail -80 ``` Yang penting adalah nama file setelah `lib64/`, misalnya: ```text vendor/xiaomi/apollo/proprietary/vendor/lib64/libtidakada.so ``` ## 2. Cek apakah blob benar-benar ada Misal nama file yang hilang adalah `libcontoh.so`: ```bash cd ~/android/lineage ls -l vendor/xiaomi/apollo/proprietary/vendor/lib64/libcontoh.so ``` Cek juga apakah ada symlink rusak: ```bash find vendor/xiaomi/apollo/proprietary -xtype l -ls ``` Cek siapa yang mereferensikan file tersebut: ```bash grep -R --line-number "libcontoh.so" \ device/xiaomi/apollo \ vendor/xiaomi/apollo 2>/dev/null | head -50 ``` Kalau file tidak ada, bukan folder yang perlu dibuat. **Jangan** melakukan `touch file.so` atau membuat file dummy karena build bisa lolos tetapi hasil ROM bisa gagal boot/crash. ## 3. Solusi paling umum ### A. Vendor blob belum diekstrak / belum lengkap Cari script ekstraksi: ```bash find device/xiaomi/apollo vendor/xiaomi/apollo \ -name extract-files.sh -print ``` Lalu jalankan dengan stock ROM/dump yang cocok dengan device tree: ```bash cd ~/android/lineage/device/xiaomi/apollo ./extract-files.sh /path/ke/stock_rom_apollo ``` Atau jika script berada di vendor tree: ```bash cd ~/android/lineage ./vendor/xiaomi/apollo/extract-files.sh /path/ke/stock_rom_apollo ``` Beberapa script bisa langsung memakai perangkat lewat ADB: ```bash adb root adb remount ./extract-files.sh ``` Pastikan stock dump cocok dengan tree Android 14/LineageOS 21. Jangan mencampur blob dari ROM versi lain sembarangan. Setelah ekstraksi, cek ulang: ```bash ls -l vendor/xiaomi/apollo/proprietary/vendor/lib64/ ``` ### B. Gunakan repo vendor blobs yang cocok Untuk Xiaomi Apollo biasanya tersedia repo vendor dari TheMuppets atau maintainer terkait: ```bash cd ~/android/lineage repo sync --force-sync vendor/xiaomi/apollo ``` Jika repo belum masuk manifest, tambahkan lewat `.repo/local_manifests/apollo.xml`, contoh: ```xml ``` Lalu: ```bash repo sync --force-sync vendor/xiaomi/apollo ``` Catatan: jika `apollo` yang kamu pakai adalah unofficial/porting, jangan asal memakai branch TheMuppets. Pakai repo vendor dari maintainer device tree yang sama. Device tree, kernel, dan vendor blobs harus berasal dari branch/commit yang cocok. ### C. Cek mismatch versi device tree vs vendor tree Ini sering terjadi bila: - device tree LineageOS 21, - tetapi vendor blob masih dari LineageOS 20/Android 13, - atau firmware asal berbeda region/version. Cek commit yang sedang dipakai: ```bash git -C device/xiaomi/apollo log -1 --oneline git -C vendor/xiaomi/apollo log -1 --oneline ``` Pastikan keduanya satu generasi. Kalau ragu, lakukan force sync/reset untuk kedua repo sesuai instruksi maintainer. ### D. Symlink blob rusak Kalau hasil `find ... -xtype l` menunjukkan symlink rusak, jalankan ulang ekstraksi atau sync ulang vendor repo. Jangan membuat isi file baru secara manual. ## 4. Kalau file memang tidak diperlukan Kadang device tree masih mereferensikan blob lama yang sudah tidak ada di firmware baru. Perbaikannya adalah: - update `proprietary-files.txt`, - update generated `Android.mk`/`Android.bp` atau file make device/vendor yang mereferensikannya, - atau ganti ke blob/firmware yang sesuai. Jangan hanya menghapus satu baris lalu berharap aman. Jika library itu dibutuhkan driver/hardware, ROM bisa tetap build tetapi gagal boot atau hardware mati. ## 5. Bersihkan output build setelah memperbaiki blob Setelah blob diperbaiki atau repo disinkronkan ulang: ```bash cd ~/android/lineage source build/envsetup.sh breakfast apollo make clean mka bacon ``` Kalau hanya perubahan kecil dan ingin cepat, minimal hapus generated output terkait: ```bash rm -rf out/soong/build.ninja out/target/product/apollo ``` Tetapi jika ragu, `make clean` lebih aman. ## Kesimpulan singkat Paling mungkin: 1. `vendor/xiaomi/apollo/proprietary/vendor/lib64/...` belum lengkap karena `extract-files.sh` belum dijalankan atau gagal, atau 2. repo `vendor/xiaomi/apollo` tidak cocok dengan device tree `device/xiaomi/apollo`, atau 3. ada blob symlink rusak / file dihapus tetapi masih direferensikan. Langkah pertama yang paling praktis: ```bash cd ~/android/lineage find device/xiaomi/apollo vendor/xiaomi/apollo -name extract-files.sh -print ls -l vendor/xiaomi/apollo/proprietary/vendor/lib64/ find vendor/xiaomi/apollo/proprietary -xtype l -ls ``` Kirimkan baris `FAILED: ninja` secara lengkap beserta nama file setelah `lib64/`, dan output `ls -l` untuk path file tersebut serta `grep -R` nama file itu. Dari situ bisa ditentukan apakah masalahnya ekstraksi blob, mismatch branch, symlink, atau referensi makefile yang harus diperbaiki.

dndm