On firmware C.47 after changing any settings the system stops booting. Flashing a modified vbmeta which helped to solve the problem on C.44 firmware doesn't work anymore and also leads to problems with booting the system. Perhaps someone knows how to get Konabess to work on the latest C.47 firmware?
what about in oos 13 f72? tried several combinations with vbmeta and vendor partitions, no luck. always ends up dmverity crashdump or constant reboot cycle to fastboot.
what about in oos 13 f72? tried several combinations with vbmeta and vendor partitions, no luck. always ends up dmverity crashdump or constant reboot cycle to fastboot.
On firmware C.47 after changing any settings the system stops booting. Flashing a modified vbmeta which helped to solve the problem on C.44 firmware doesn't work anymore and also leads to problems with booting the system. Perhaps someone knows how to get Konabess to work on the latest C.47 firmware
Join the telegram group mentioned above or visited the Konabess GitHub. The info is there. There are also YouTube videos. Lots of info about it if you simply search for it.
Peeps kept asking me in Telegram and in xda so here is what you do to update OOS without crash dump.
From your CURRENT ROM payload.bin, extract dtbo, vendor_boot, vbmeta, vbmeta_system, vbmeta_vendor. Then use the commands i put below. After that just local flash the ota and use magisk to patch inactive slot.
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash boot magisk.img - the magisk patched boot.img
On firmware C.47 after changing any settings the system stops booting. Flashing a modified vbmeta which helped to solve the problem on C.44 firmware doesn't work anymore and also leads to problems with booting the system. Perhaps someone knows how to get Konabess to work on the latest C.47 firmware?