Hi, sorry for raising a duplicated topic, but all similar ones didn’t not provide a solution to my problem.
I’m trying to build and flash Android version 11.0.0_r26 on VIM3 board. (In fact i will be happy if I’m able to flash any release of Android 11)
Instructions available on source.android.com and Khadas website work perfectly fine for master branch, but it is Android S Beta version, and is not suitable for my needs.
Main issue seems to be different partitions structure between VIM3 board and what is built out of AOSP.
Images that are being built for yukawa-userdebug target in my AOSP version are: boot.img, system.img, vendor.img, cache.img, userdata.img, ramdisk.img
However, images that are needed in order to flash the VIM3 board are: boot.img, super.img, cache.img, userdata.img, recovery.img, dtbo-unsigned.img.
So missing images are:
And it seems that they should be somehow built instead of
Or maybe a subset of those.
I’ve looked into the diff between master and 11.0.0_r26 for device/amlogic/yukawa and it seems like a substantial amount of changes to understand for an AOSP noob like me
My ideal solution as i see it would be one of the two:
- a post-build script that I will run on output directory that will recombine the generated images into the ones i need
- a minimal patch to device/amlogic/yukawa which will make necessary images come out of the build system
Can someone help with either approach please? Would also be grateful for any useful links to read in order to come up with a solution myself