Mismatch firmware issue

linhmieu2

I am trying to port to samsung tab a7 lite using the standalone kernel method detailed in the guide. I have followed every step correctly to my knowledge, however I'm getting the problem is overlay and vendor use android 14 base but my kernel use android 12 (im trying to downgrade but theare are no method to downgrade on my tablet)

and i see mount log in dmesg in host:
[96434.125324] EXT4-fs (loop0): mounted filesystem 00017acc-df4f-433e-ae41-da447717a3f6 r/w with ordered data mode. Quota mode: none.
[96444.601967] EXT4-fs (loop0): unmounting filesystem 00017acc-df4f-433e-ae41-da447717a3f6.
after that , it switch to Usb Mass Storage

and my deviceinfo:
ydeviceinfo_name="Samsung Galaxy Tab A7 Lite"
deviceinfo_manufacturer="Samsung"
deviceinfo_codename="gta7litewifi"
deviceinfo_arch="aarch64"
deviceinfo_halium_version="12"
deviceinfo_kernel_source="https://github.com/gta7lite/android_kernel_samsung_ot8.git"
deviceinfo_kernel_source_branch="halium-12"
deviceinfo_kernel_defconfig="gta7litewifi_defconfig halium.config"
deviceinfo_kernel_clang_compile="true"
deviceinfo_kernel_llvm_compile="true"
deviceinfo_kernel_image_name="Image.gz"
deviceinfo_kernel_cmdline="bootopt=64S3,32N2,64N2 systempart=/dev/mapper/system console=tty0 androidboot.selinux=permissive"
deviceinfo_bootimg_header_version="2"
deviceinfo_bootimg_partition_size="33554432"
deviceinfo_bootimg_os_version="12"
deviceinfo_bootimg_os_patch_level="2021-09"
deviceinfo_ramdisk_compression="lz4"
deviceinfo_flash_pagesize="2048"
deviceinfo_flash_offset_base="0x00000000"
deviceinfo_flash_offset_kernel="0x40080000"
deviceinfo_flash_offset_ramdisk="0x51b00000"
deviceinfo_flash_offset_second="0x00f00000"
deviceinfo_flash_offset_tags="0x47880000"
deviceinfo_flash_offset_dtb="0x47c80000"
deviceinfo_dtb="gta7litewifi_dtb"
deviceinfo_rootfs_image_sector_size="4096"

thank you to any suggest
(Sorry for bad english)

k.nacke

@linhmieu2 You need to determine the VNDK level of your Android firmware, e.g. with adb shell getprop | grep vndk or using the Treble info app. Use that number to look up the corresponding Android version, e.g. at API levels. For example, if the VNDK version is 34, then you need to put deviceinfo_halium_version="14" in your deviceinfo file.
The VNDK level is the API version level, and this it what counts for halium. Note that the version derived in this way may not correspond the Android version your device displays. E.g. I have a OnePlus 11 running Android 15, but the VNDK version is still 33, which corresponds to Android 13. For this device, I need to use 13 as the halium version.
You may also want to put the number as ApiLevel into the /etc/gbinder.conf file in your system overlay.

There is no "Android 12 kernel". I think it would be better if you post the concrete problems you encounter. The telegram group for porters is also a good place to ask or search for answers.

Kai