Werner

Armbian default login and password is always root and 1234. If this does not work, the image is not genuine.

I don't know, perhaps the author knows. Try. If it doesn't work, then fe's wiki is misleading.

You can try the following: After writing to nvme and spi do NOT reboot but mount the nvme drive to a random directory and check in /boot/armbianEnv.txt if the UUID matches the one from the nvme. If not, correct it (check blkid).

Neither of these is good advice. dd does not verify written data and balena etcher has known issues, hence it is not recommended either. Either use Armbian Imager (https://docs.armbian.com/User-Guide_Getting-Started/) or USBimager (https://gitlab.com/bztsrc/usbimager). Both are known to work.

moved

Hi, welcome. Syncing forums and tags with supported boards is (still) a manual job and from time to time I either cannot keep up or miss things. Like in this case. I'll fix this later and then move appropriately. Until then feel free to state your question in "Beginners" using the "other" tag. Cheers

moved to tvboxes

BalenaEtcher has known issues and therefore not recommended. Use Armbian Imager or USBimager. Also verify that the downloaded image is good by utilizing the checksum. https://docs.armbian.com/User-Guide_Getting-Started/#download-and-verification https://github.com/armbian/imager https://bztsrc.gitlab.io/usbimager/

Which device? which armbian version? nobody here has a second sight. from the screenshot you aren't even using armbian or at least nothing official.

moved

I'd start by comparing the device tree on a working and non-working image.

Probably a new product. Images are not compatible unless specifically marked as such.

https://docs.armbian.com/User-Guide_Getting-Started/#vendor-current-edge-or-legacy

The related PR states this was tested. @Efe Çetin can you confirm this still works as expected?