Vim3Pro AOSP recovery image is too large for partition

[JWChoi1996]

Which Khadas SBC do you use?

Vim3Pro

Which system do you use? Android, Ubuntu, OOWOW or others?

Android Kernel 5.10

Which version of system do you use? Khadas official images, self built images, or others?

self built images
ref: Using Reference Boards  |  Android Open Source Project

Please describe your issue below:

I clone aosp kernel images follow below command.

git clone https://android.googlesource.com/kernel/hikey-linaro -b android-amlogic-bmeson-5.10

Then, I inserted some additional kernel functions and commands like ‘printk’ and rebuilt it.
The size of recovery.img file increased 32 MB → 32.X MB, and I modified BOARD_RECOVERYIMAGE_PARTITION_SIZE 32MB to 64MB in ‘device/amlogic/yukawa/BoardConfigCommon.mk’ file.

However, when using uboot and fastboot, I still get the below message.

FAILED (remote: too large for partition)

Which file should I modify other files or options?

Post a console log of your issue below:

target reported max download size of 117440512 bytes
sending 'recovery' (33412 KB)...
OKAY [  1.832s]
writing 'recovery'...
FAILED (remote: too large for partition)
finished. total time: 1.845s

[zonggestsu]

@zonggestsu

you would have to recompile the u-boot to and flash said u-boot to get what you’re looking for. the thing is that baylibre, i am guessing, was testing with the vim3 basic and so set hard sizes that accommodated that device. This is the file with the config for the partitions and ive already edited it to give more space on the userdata and super partitions, and you will only need to put it into the /include/configs folder of the source code that you can find by following these instructions , just scroll down, its below the files.

just a note, these havent been updated in a bit but id say it should be safe to use “u-boot/v2022.01/integ”, but if you run into issues with that version, you can use the version in the instruction instead. hope this helps

basically same process.
just a note, in the example config file, the “-” tells the compiler that the named partition of the device partition table takes up the remainder of the storage, as the device vim3 has 2 different models with differing storage sizes, and as such is more appropriate as a universal u-boot for the both of them. normally the recovery image is able to format and setup the userdata partition for first boot, but thats not working for some reason so theres a need to create a userdata image at rom compile to get the device to work as intended.