Broken symlinks in default.prop, bin, charger, etc
sounddrill31 opened this issue · comments
- [NA] I am running an official build of TWRP, downloaded from https://twrp.me/Devices/
- [Yes*] I am running the latest version of TWRP
- [Yes] I have read the FAQ (https://twrp.me/FAQ/)
- [Yes*] I have searched for my issue and it does not already exist
Device codename: A109
TWRP version: NA, 3.7.0-9.0
Device tree: https://github.com/sounddrill31/android_device_micromax_a109/
WHAT STEPS WILL REPRODUCE THE PROBLEM?
Build TWRP with minimal manifests omni and android 9 branch(also happens in 7.1 branch)
WHAT IS THE EXPECTED RESULT?
Recovery should atleast boot.
WHAT HAPPENS INSTEAD?
Recovery does not boot.
ADDITIONAL INFORMATION
Upon unpacking the image with carliv, we can see !<symlink>ÿþp r o p . d e f a u l t with NULL symbols. This happens with multiple files like default.prop, charger, bin, etc.
Vscode web shows that the files are symlinked, and half of them don't lead anywhere.
I will post logs in a bit./tmp/recovery.log:
dmesg:
Disclaimer: I used venv for python2. The command I used:
sudo apt install -y python2
virtualenv --python=python2 ~/.lineage_venv
source ~/.lineage_venv/bin/activate
sudo ln -sf /home/gitpod/.lineage_venv/bin/python /usr/bin/python
product_copy_files_ignored.txt
soong.log
I also tried compiling for a110(for testing) using fix-1 branch of https://github.com/sounddrill31/android_device_a110/tree/fix-1, and found the same error.
This issue seems to no longer persist, but my recovery is still not booting. Any help is appreciated.
TWRP 7.1 minimal branch doesn't have this issue but 9 does, yet 7.1 still doesn't boot...
crosspost from twrpdtgen comment