[Android General] yesimxev:
Yup, not much results on google either. The significant diff to your guide is that the original recovery has only fstab.enableswap

recovery.fstab has the following - is it good format or messed up as mediatek tends to do (not sure which one is the messed up one)

/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system / ext4 ro wait,verify=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/metadata,slotselect
,recoveryonly

/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/vendor /vendor ext4 ro wait,verify=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/metadata,slot
select,recoveryonly

/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc wait,check,formattable,quota,resize,forcefdeo
rfbe=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/metadata
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/protect1 /mnt/vendor/protect_f ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,chec
k,formattable
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/protect2 /mnt/vendor/protect_s ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,chec
k,formattable
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/nvdata /mnt/vendor/nvdata ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check,formattable

/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/persist /mnt/vendor/persist ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,f
ormattable

/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/frp /persistent emmc defaults defaults

/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/box /vendor/BBSYS ext4 noatime,nosuid,nodev,barrier=1 wait,formattable,nofail

/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/cda /vendor/hidden/data ext4 noatime,nosuid,nodev,barrier=1 wait,slotselect,formattable,nofail

/devices/mtk-msdc.0/11240000.msdc1* auto auto defaults voldmanaged=sdcard1:auto,encryptable=userdata
/devices/soc/11270000.usb3_xhci* auto auto defaults voldmanaged=usbotg:auto

/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/nvram /nvram emmc defaults defaults
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/proinfo /proinfo emmc defaults defaults
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/para /misc emmc defaults defaults
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/recovery /recovery emmc defaults defaults
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo /logo emmc defaults defaults
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/expdb /expdb emmc defaults defaults
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/secro /secro emmc defaults defaults
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/seccfg /seccfg emmc defaults defaults

/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/lk /bootloader emmc defaults defaults,slotselect
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/boot /boot emmc defaults defaults,slotselect
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/md1img /md1img emmc defaults defaults,slotselect
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/md1dsp /md1dsp emmc defaults defaults,slotselect
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/md1arm7 /md1arm7 emmc defaults defaults,slotselect
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/md3img /md3img emmc defaults defaults,slotselect

/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/tee /tee emmc defaults defaults,slotselect

/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/odmdtbo /odmdtbo emmc defaults defaults,slotselect
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/dtbo /dtbo emmc defaults defaults,slotselect

A bit unusual. I don't want to take much of your time [MENTION=8355838]Augustoandro[/MENTION] , hence I'm not requesting a full port from you, but any help would be appreciated. I've found another MT6750 base with 720x1280 screen, and that one doesn't have twrp.fstab as yours. Both fails so I'm sure there's something I'm missing in addition to the guide

UPDATE: for my device, the mkbootimg needed --base and --ramdisk-offset, which solves the issue of "invalid kernel address - not lie in memory". However, still not enough - doesn't work either with fastboot boot nor flash