Ok,them it is proved the image is not the problem. You can try up booting with the other card multiple times (warm start,cold start) if you have this error every time may it can be used for debugging the issue…so enabling debug in uboot flash to this card and send it as issue to mtk people
Do you have a linux-host or are you able to flash a binary at a specific position on card?
It is most my lack of linux experience there will be an issue here
Believe when you say host, then yes i have an old laptob with linux on - ubunto…
I think one of the failed SD card had issue with the quality on the card… but 2 different cards flashed with the image on the linux did not boot… 2 different cards did boot when written from windows (also the broken) but after a litle run time it came with errors on the card…
i dont’t know if windows have a application for checking sdcards independ of the filesystem…in linux there is badblocks which needs to be called in non-destructive mode for checking the sdcard has no bad sectors…
i only had problems in uboot reading the card, not after linux was booted…so this should be caused by card itself
I have added the skipkerneldownload=true to the config file
and changed the kernel file name in the same config file…
Is that enough to build with custom compiled kernel?
Package maintainer version is the version you’ve downloaded via apt
The img will work,but it cannot be pavked,so the img.gz is the old one
Which file have you renamed? I see that your own kernel file is used…
The cp copies the img file from uboot repo (img.gz with full bootchain till uboot) to a new file to always start from a clean base…else your previos image is changed