I second this. I attempted to reinstall the ota, without succeeding at first (lineage recovery).
Installing unifiednlp by pushing to /system-priv worked, so I am tempted to perform the same thing. (I don’t recall the exact procedure, could have been an OTA).
@oF2pks I do not have these files on my system after sideloading the ota.
I dug a bit more. Attached is a full log: recovery-log.zip (6.6 KB) .
The blame might be on lineage side this time: after mounting
/system/bin isn’t a folder anymore, and that’s the one used in the
$PATH As such, no command can be executed as soon as
/system is mounted. Moreover, I cannot use
/system/bin/ as it then complains of “too many symbolic links encountered”. I also tried copying
/tmp to have the executables (these didn’t seem to be symlinks), but I get the same issue (if anybody has an explanation, I’d be glad to hear it):
/system/bin/sh: /tmp/bin/ls: Too many symbolic links encountered.
I’m tired now, but it nows appear
ls is a symlink to
toybox, like busybox would be. Unsure why it didn’t show up previously.
I don’t know whether my device uses /system as root,
getprop ro.build.system_root_image returns nothing.
I will try to ask the lineage devs if I can. There seems to be something funky going on with the recovery, or something else. I previously tried with the 16.0 recovery, this was with the 17.1. The recovery mounts the system partition under
/mnt/system when asked. So I remounted it rw with
mount -o remount,rw /mnt/system, and changed the
SYSTEM variable in the f-droid install script to
SYSTEM="/mnt/system/system", as well as commenting the
mount /system line. That worked. But it is far from optimal, so it remains to be investigated. It might just be the lineage recovery putting its binaries in
/system/bin instead of
/system/system/bin, thereby causing all these issues.
It’s 2 am, I’m going to bed
edit: I tried to attach the updated zip, but it’s 2BM too big.
Takeaway: a lot more tests are needed in the install script, with better error messages. I might contribute them.