and with more prebuiltapks too (included only the first two errors). What I did previously was to replace the prebuiltapks with the downloaded zips of the prebuiltapks…is there something else I can do?
My first thought is that it is to do with failure of
repo forall -c ‘git lfs pull’
… maybe because I had that experience.
Did you check if the folders where you renamed got repopulated ?
You might try again
repo status > status.txt
your answer about your earlier status.txt
Is every other project fully ok and shows no modifications at all ?
did not deal with the other 800 odd projects which should appear in your output (my having other branches and devices is not relevant). The reason for asking is to find if repo is clean.
If you search that output ( ^ F ) how many times does “no AndroidManifest.xml found” occur ?
You might share the error.log and / or other logs (out directory) may may reflect the actual error better.
You could check the out put of
cat /proc/sys/kernel/unprivileged_userns_clone
= 1. Is a “permissions” thing; if 0 you may lack necessary permissions default is 1 in Ubuntu.
The apostrophe issue is not helped by the forum code box. The correct code in plain text:
repo forall -c ‘git lfs pull’
Copy and paste into a code box
repo forall -c ‘git lfs pull’
… as you say, it is a different and incorrect Unicode form, perhaps U+0027 ’ vs U+2019 ’ Tentatively it is a font effect.
Can you get a logcat as your first boot fails ? Perhaps try 2 terminals open, one to adb sideload the ROM, the other to create the logcat at the “right” moment. My guess would be not to start the logcat too early, perhaps as you see the bouncing e ?
I know that it may not work, but worth a try ?
I don’t recognise anything too odd in the build log.
Just Form the very little I remembert hearing about Samsung not booting…
Does Lineage include any vendor stuff? Some blobs?
If, are they in your build? Did you extract from the tablet?
58% 21714/37022] Target boot image: out/target/product/gts210wifi/boot.img
patch boot out/target/product/gts210wifi/boot.img out/target/product/gts210wifi/boot.img.lok
cp: bad ‘out/target/product/gts210wifi/boot.img.lok’: No such file or directory
Made boot image: out/target/product/gts210wifi/boot.img
…
99% 37021/37022] Package OTA: out/target/product/gts210wifi/lineage_gts210wifi-ota-eng.ronnz.zip
2023-08-29 11:15:37 - common.py - WARNING : Failed to read SYSTEM/etc/build.prop
2023-08-29 11:15:37 - common.py - WARNING : Failed to read VENDOR/etc/build.prop
2023-08-29 11:15:37 - common.py - WARNING : Failed to read VENDOR/build.prop
2023-08-29 11:15:37 - common.py - WARNING : Failed to read build.prop for partition vendor
2023-08-29 11:15:37 - common.py - WARNING : Failed to read PRODUCT/etc/build.prop
2023-08-29 11:15:37 - common.py - WARNING : Failed to read PRODUCT/build.prop
2023-08-29 11:15:37 - common.py - WARNING : Failed to read build.prop for partition product
2023-08-29 11:15:37 - common.py - WARNING : Failed to read SYSTEM_EXT/etc/build.prop
2023-08-29 11:15:37 - common.py - WARNING : Failed to read SYSTEM_EXT/build.prop
2023-08-29 11:15:37 - common.py - WARNING : Failed to read build.prop for partition system_ext
2023-08-29 11:15:37 - common.py - WARNING : Failed to read ODM/etc/build.prop
2023-08-29 11:15:37 - common.py - WARNING : Failed to read ODM/build.prop
2023-08-29 11:15:37 - common.py - WARNING : Failed to read build.prop for partition odm
2023-08-29 11:15:37 - common.py - WARNING : Failed to read VENDOR_DLKM/etc/build.prop
2023-08-29 11:15:37 - common.py - WARNING : Failed to read VENDOR_DLKM/build.prop
2023-08-29 11:15:37 - common.py - WARNING : Failed to read build.prop for partition vendor_dlkm
2023-08-29 11:15:37 - common.py - WARNING : Failed to read ODM_DLKM/etc/build.prop
2023-08-29 11:15:37 - common.py - WARNING : Failed to read ODM_DLKM/build.prop
2023-08-29 11:15:37 - common.py - WARNING : Failed to read build.prop for partition odm_dlkm
2023-08-29 11:15:37 - common.py - WARNING : Failed to read SYSTEM_DLKM/etc/build.prop
2023-08-29 11:15:37 - common.py - WARNING : Failed to read SYSTEM_DLKM/build.prop
2023-08-29 11:15:37 - common.py - WARNING : Failed to read build.prop for partition system_dlkm
2023-08-29 11:15:37 - common.py - INFO : Running: “/mnt/media/e/eOS/out/host/linux-x86/bin/unpack_bootimg --boot_img out/target/product/gts210wifi/obj/PACKAGING/target_files_intermediates/lineage_gts210wifi-target_files-eng.ronnz/IMAGES/boot.img --out /mnt/media/e/eOS/out/soong/.temp/boot__ktkl9xz.img”
2023-08-29 11:15:37 - common.py - WARNING : Unable to get boot image build props: Failed to run command ‘[‘unpack_bootimg’, ‘–boot_img’, ‘out/target/product/gts210wifi/obj/PACKAGING/target_files_intermediates/lineage_gts210wifi-target_files-eng.ronnz/IMAGES/boot.img’, ‘–out’, ‘/mnt/media/e/eOS/out/soong/.temp/boot__ktkl9xz.img’]’ (exit code 1):
Traceback (most recent call last):
I’m not sure, if I remember this right… I think there is a extract shell script which extracts from a build*xyz.zip maybe extract boot + vendor from your build and the LOS image you base on and compare them!???
Maybe there is another/better/simpler way, it’s more a reverse engeneering approach…
All the guides I see recommend docker – is something magic in the docker scripts which is required ? So I would try vendor_e (or docker) and build Lineage4microG – this way you might also filter out whether some /e/ contents are the problem.
