Now the lxc of my machine can run normally, but the image can no longer be displayed on the mobile phone. Can you help my friends in the community

I have the same problem as you, only the system image under the data partition can be mounted normally, other can not be mounted normally, only the command window is barely available

@TheVancedGamer I found that the machine can access the smallest command line through the serial port, but the UI cannot be displayed. I suspect that it is related to the failure of the vendor partition to mount properly, and the vendor partition is empty

As an ODM developer, I ported halium related code based on the code of my project. Now the machine can complete normal kernel loading, but the Android container seems to fail to start. Do you have any suggestions ? log as follows

root@ubuntu-phablet:/home/phablet# lxc-start -n android -F
lxc-start: android: start.c: lxc_spawn: 1673 Invalid argument - Failed to clone a new set of namespaces
lxc-start: android: start.c: __lxc_start: 1999 Failed to spawn container "android"
lxc-start: android: tools/lxc_start.c: main: 308 The container failed to start
lxc-start: android: tools/lxc_start.c: main: 313 Additional information can be obtained by setting the --logfile and --logpriority options

@Lakotaubp Hi,I changed my account, Now I want to transplant a new mobile phone. May I ask how can I succeed as soon as possible if I have the source code and image package of this mobile phone? I read the documentation that Standalone kernel method can be used to implement the simplest solution. However, the introduction of the scheme is not detailed enough, my mobile phone is android12 (system) +android 10(vendor) combination, this is because Qualcomm proposed to understand the coupling. My idea is that at present, we can re-unpack our boot.img, and then package halium's ramdisk+halium GSI system img and UT's rootfs to complete this solution. Is my idea correct ?