Quick update: Upon reaching out to the Telegram UBPorts Porting forum, Pavlov, a member of the group suggested me to intentionally cause a panic in the init script and stated that after that, hopefully the crash handler can initialize a shell connection for me. I've tried his approach and I also ran the mer_kernel_check utility on the .config file produced during the build process inside workdir/downloads/KERNEL_OBJ and all the flags that came out to be "NOT SET" and were required for halium to work were set in a separate devspecific.config file which has been pushed to the kernel repository but even after all this I face the same issue at the end. Please let me know where I have gone wrong with my approach to implementing the panic in the init script
Quick update: Upon reaching out to the Telegram UBPorts Porting forum, Pavlov, a member of the group suggested me to intentionally cause a panic in the init script and stated that after that, hopefully the crash handler can initialize a shell connection for me. I've tried his approach and I also ran the mer_kernel_check utility on the .config file produced during the build process inside workdir/downloads/KERNEL_OBJ and all the flags that came out to be "NOT SET" and were required for halium to work were set in a separate devspecific.config file which has been pushed to the kernel repository but even after all this I face the same issue at the end. Please let me know where I have gone wrong with my approach to implementing the panic in the init scriptscript
Kernel Repository:https://gitlab.com/systemmaniac2010/kernel_motorola_sm6225
Device Repository:https://gitlab.com/systemmaniac2010/motorola-rhode