Looks like the current-rockchip64 kernel that one receives with apt on PINE64 rockpro64 is 3.18.10 (6.18.10-current-rockchip64), vulnerable to copy-fail. This seems weird because if you go to https://armbian.com/boards/rockpro64 that page says that the "current" kernel for these systems is 6.18.26 and that is what you get when you download the image file. Is there an issue with updating the apt repos?

Looks like the current-rockchip64 kernel that one receives with apt on rk3318/28 is 3.18.10, vulnerable to copy-fail. This seems weird because if you go to https://armbian.com/boards/rk3318-box, that page says that the "current" kernel for these systems is 6.18.26 and that is what you get when you download the image file.

Things are still very sad with Ethernet. Is this could be related to some low-level timings in device configuration?

First of all, thanks for your reply. Even though you said there are no "vendor-lockin" i felt like so that's why i created a post on this forum as this issue came only after armbian os flash. As i said, after flashing armbian os, i was not able to use MASK button to bypass emmc boot and about a dozen of different os other than armbian failed to boot from SD card. Then i experimented on different methods including the PC connectivity but changing bootloader or os image didn't work as the mask communication is getting lost during flash command run. I deleted boot files from armbian boot partition to check if that fall back to SD card, but there was no luck. However armbian SD card boot still worked. So i confirmed that it is the change in bootloader that armbian made. Then i re installed armbian os inside emmc and used dd command to write the original bootloader images which is taken from the nanopi r6s official eflasher download link. It worked! Now i am able to install other os than armbian. Kindly fix this issue and acknowledge the same, otherwise people like me will think twice before testing latest armbian os next time. Best regards

Armbian does not have things like "vendor-lockin" or something and descriptions like "does not work" aren't much helpful as well. Either way, we cannot help with 3rd party OS since we neither know them nor deal with them, so I suggest to ask at the place where you got the image you are attempting to use get from, like http://friendlyarm.com/