arturito

Why such difficulties ? Just use normal images in which the NVMe + MTD installation works correctly via armbian-install.

Couldn't booti from NVME with armbian-config or armbian-install, finally I could do it, a dirty easy and convoluted following way. No details about burning stuff
 
This is what I did
 
1) boot system from fresh downloaded SD (Armbian Jammy Desktop)
 
2) NVME setup (sudo gparted)
   - if empty create a partition table (GPT)
     if not delete all partitions
   - create 256MB FAT16 partition (nvme0n1p1)
   - create EXT4 partition (nvme0n1p2)
   - optionally create more partitions (system recovery, backups ...)
   - format partitions nvme0n1p1 -> FAT16
   - format partitions nvme0n1p2 -> EXT4
   - check partitions (if old NVME)
   - label nvme0n1p1 as armbi_boot
   - label nvme0n1p2 as armbi_root
 
3) run sudo armbian-install
   - option 7 to flash mtdblock0 (bootloader install)
   - option 4 (to install system and boot from mtdblock0)
     choose nvme0n1p2 partition to install system
     don't POWEROFF, just EXIT
 
4) copy SD boot partition to nvme0n1p1
   - sudo dd if=/dev/mmcblk1p1 of=/dev/nvme0n1p1 bs=1M status=progress
   - sudo sync
 
5) armbianExt.txt setup on NMVE
   - sudo mount /dev/nvme0n1p1 /mnt
   - check boot files/directories are already copied (ls -l /mnt)
   - blkid
   - copy (CTL_INS -> new UUID) of nvme0n1p2 UUID (without "")
  with your favourite editor:
   - sudo vi armbianExt.txt
   - replace rootdev=UUID=with new UUID (SHIFT-INS)
   - save (ESC :x)
6) - sudo poweroff
   - remove SD
   - press power button to restart
 
Maybe this cam help someone
 

The info that I gathered from that thread is that the MTD/SPI bootloader that comes with the image I was trying doesn't handle ext4 file system on the NVMe.
 
So I downloaded one of your images:  Armbian_23.02.3_Orangepi5_lunar_legacy_5.10.110.img.xz
 
Verified the SHA-256 hash and then flashed to an SD card.  Flashed the MTD/SPI from that image and then rebooted with the Armbian Debian Bullseye Legacy CLI that did not previously boot up.
 
And...it booted up properly.  I use this version of OS as the software I'm using requires Bullseye.
 
In any case, thanks.

The standard armbia-install boot from MTD with system on NVME did not work for me! What did work:
 
- Boot from standard Armbian image from SD, then use armbian-install to flash the bootloader to MTD.
- dd the standard Armbian image to nvme0n1, power down, remove the SD card, power up.

Couldn't booti from NVME with armbian-config or armbian-install, finally I could do it, a dirty easy and convoluted following way. No details about burning stuff
 
This is what I did
 
1) boot system from fresh downloaded SD (Armbian Jammy Desktop)
 
2) NVME setup (sudo gparted)
   - if empty create a partition table (GPT)
     if not delete all partitions
   - create 256MB FAT16 partition (nvme0n1p1)
   - create EXT4 partition (nvme0n1p2)
   - optionally create more partitions (system recovery, backups ...)
   - format partitions nvme0n1p1 -> FAT16
   - format partitions nvme0n1p2 -> EXT4
   - check partitions (if old NVME)
   - label nvme0n1p1 as armbi_boot
   - label nvme0n1p2 as armbi_root
 
3) run sudo armbian-install
   - option 7 to flash mtdblock0 (bootloader install)
   - option 4 (to install system and boot from mtdblock0)
     choose nvme0n1p2 partition to install system
     don't POWEROFF, just EXIT
 
4) copy SD boot partition to nvme0n1p1
   - sudo dd if=/dev/mmcblk1p1 of=/dev/nvme0n1p1 bs=1M status=progress
   - sudo sync
 
5) armbianExt.txt setup on NMVE
   - sudo mount /dev/nvme0n1p1 /mnt
   - check boot files/directories are already copied (ls -l /mnt)
   - blkid
   - copy (CTL_INS -> new UUID) of nvme0n1p2 UUID (without "")
  with your favourite editor:
   - sudo vi armbianExt.txt
   - replace rootdev=UUID=with new UUID (SHIFT-INS)
   - save (ESC :x)
6) - sudo poweroff
   - remove SD
   - press power button to restart
 
Maybe this cam help someone