@procount
What I am running in to is,
I had originally installed "lineage23-rpi5-atv release 2025-10-14 (which is the current latest in PINN) using PINN and everything working fine.
On Nov 11 konstakang released lineage-23.0-20251111-UNOFFICIAL-KonstaKANG-rpi5-atv-ota.zip. Ideally we should be able to dirty flash over previous lineage-23.0 ATV build using TWRP recovery.
When I try to do that, I get error, Konstakang's response is,
"using any multi-boot solution is not supported. This is known to be broken on PINN as the recovery there doesn't use /dev/block/by-name/* to mount the partitions. And this is also why any multi-boot solutions are not supported here."
Issue is, if I want to get Konstakang latest build, I have to install again using PINN (ofcourse after you add it to PINN) and It will be clean install and I have to setup everything from start (install gapps, other apps I needed, setup sign in etc.)
Is this something possible to fix at PINN side?
What I am running in to is,
I had originally installed "lineage23-rpi5-atv release 2025-10-14 (which is the current latest in PINN) using PINN and everything working fine.
On Nov 11 konstakang released lineage-23.0-20251111-UNOFFICIAL-KonstaKANG-rpi5-atv-ota.zip. Ideally we should be able to dirty flash over previous lineage-23.0 ATV build using TWRP recovery.
When I try to do that, I get error, Konstakang's response is,
"using any multi-boot solution is not supported. This is known to be broken on PINN as the recovery there doesn't use /dev/block/by-name/* to mount the partitions. And this is also why any multi-boot solutions are not supported here."
Issue is, if I want to get Konstakang latest build, I have to install again using PINN (ofcourse after you add it to PINN) and It will be clean install and I have to setup everything from start (install gapps, other apps I needed, setup sign in etc.)
Is this something possible to fix at PINN side?
Statistics: Posted by sim_tcr — Sat Nov 22, 2025 5:29 am