Unable to run am using unchroot on Elsa (LG V20 VS995)

[ShadowEO]

When attempting to run unchroot am from a terminal I receive Aborted

While running logcat at the same time (which does run under unchroot), I receive:

EDIT: Here's a better copy of the logcat I receive: https://gist.github.com/ShadowEO/d31ae46d8b21e59e3bcec86c93913bab

It appears that app_process is crashing. I DID attempt to set LD_LIBRARY_PATH to /system/lib64 but received the same behavior. BOOTCLASSPATH is correctly set.

It (the log) cuts off where I ended, but this is without any changes to the environment after installation. I noticed in the changelog something about fixing unchroot am, do I need to remove and reinstall my container before that takes effect? I also tried the Configure command in the menu.

[meefik]

Most likely some environment variables are not set. You can open the script file /sbin/unchroot and change it.
Unfortunately I do not have a 64-bit device to check. On my 32-bit ARM device works correctly.

[ShadowEO]

Ok, I'll look into what I can find and will send a pull request if I manage to find a fix!

Found the environment variable my phone's copy of app_process is expecting, ANDROID_DATA=/data was missing in the unchroot environment

Once this was set, am functioned properly. I'll fork the cli repo and make a pull request for it.

[charlala]

I experience the same or similar problem: when using unchroot, many env variables are missing but for me adding them back does not fix the 'Abort' problem when using the am or pm commands.
Strangely enough this only happens when I root the rom with magisk, Supersu works fine (but more and more roms can not be rooted with supersu anymore, e.g. the treble based ones).
@meefik do you have any idea about this? And if you want I can donate you a 64-bit device, regardless of this problem. Please PM me about it.

[meefik]

@charlala please put here your unchroot file:

cat /sbin/unchroot

[charlala]

@meefik ok I reinstalled the exact same device. Both installations (the magisk rooted one and the supersu one) were clean and from scratch, official lineageos 14.1 rom, no other apps (besides yours).
I can tell the PATH is different but I'm not sure what that means.

MAGISK 17.1 (problems):

#!/bin/sh
if [ "$(whoami)" != "root" ]; then
sudo $0 "$@"; exit $?
fi
chroot_exec=$(which chroot)
PATH=/data/user/0/ru.meefik.linuxdeploy/bin:/data/user/0/ru.meefik.linuxdeploy/bin:/sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin
if [ $# -eq 0 ]; then
$chroot_exec /proc/1/cwd su -
else
$chroot_exec /proc/1/cwd "$@"
fi

---

SUPERSU 2.82 (works as expected):

#!/bin/sh
if [ "$(whoami)" != "root" ]; then
sudo $0 "$@"; exit $?
fi
chroot_exec=$(which chroot)
PATH=/data/user/0/ru.meefik.linuxdeploy/bin:/data/user/0/ru.meefik.linuxdeploy/bin:/su/bin:/sbin:/vendor/bin:/system/sbin:/system/bin:/su/xbin:/system/xbin
if [ $# -eq 0 ]; then
$chroot_exec /proc/1/cwd su -
else
$chroot_exec /proc/1/cwd "$@"
fi

[meefik]

It's old version of unchroot. Here new version:

#!/bin/sh
if [ "$(whoami)" != "root" ]; then
sudo $0 "$@"; exit $?
fi
chroot_exec=$(which chroot)
export PATH=
export BOOTCLASSPATH=
if [ $# -eq 0 ]; then
$chroot_exec /proc/1/cwd su -
else
$chroot_exec /proc/1/cwd "$@"
fi

Run Menu-Configure for update this file.

[charlala]

@meefik thank you, I tried the new version. In the Magisk rom it still does not work. I wonder if I'm the only user experiencing problems with Magisk rooted devices? As soon as I use the menu-configure update, it deletes the BOOTCLASSPATH line from the unchroot script.
I also checked the ENV variables with the android terminal on the same system and the BOOTCLASS variable is there.

[meefik]

@charlala What your LD version?

[charlala]

@meefik I used 2.10 but also just tried 2.20, it gives the same result.

[meefik]

In latest version of LD the BOOTCLASSPATH variable always setted, see the source code: https://github.com/meefik/linuxdeploy-cli/blob/master/include/core/unchroot/deploy.sh

Please try Menu->Configure in latest version of LD or add BOOTCLASSPATH from Android environment to this file.

[charlala]

Ah - you are correct, BOOTCLASSPATH does get populated now. Still the pm command results in an 'Abort' :(
I included the output of the env command:

magiskdevice.txt

[meefik]

@charlala Thank you for your offering! I really don't have any 64 bit devices for tests. But how do it? Do you sending parcel by post?

[charlala]

@meefik I sent you an email ;) Pls also note my previous post - the am and pm commands still 'Abort' in the unchroot...