LluviaFria

It seems that it is not the same plate, my plate is that one

Can you try with another micro SD? I had no problem getting the image to work.

I don't know the system, is that Armbian?

and record the image with this program. (you must first unzip the image) https://win32diskimager.org/

format your micro SD with this program https://www.sdcard.org/downloads/formatter/

When there is a new version of your firmware, where will you publish it for download? since i couldn't get armbian to work from usb, i had given up and bought a raspberry pi 4 with 8gb ram, right now my odroidc4 is saved, this happened before you arrived with your firmware. When I get the cable, I'll let you know.

I have been trying to start armbian from usb for 1 month, and I was unsuccessful, I couldn't find any tutorial that would help me, the Armbian-config itself has an option to transfer the boot to the micro SD but that option does not work for me, the system never starts, It's a shame, I ended up buying a raspberry pi 4 just because I needed to boot from a usb, it's a shame because I like the temperatures of the odroidc4 compared to the temperatures of the raspberry pi4, where were you and your methods ? It would have been very useful to find tutorials for beginners with these methods.

Well I did the steps again, I have 2 micro SD cards, in one I did a clean and updated installation of Armbian_23.02.2_Odroidc4_jammy_current_6.1.11 image, the other one is an old and slow micro SD of 4gb I put it in a micro reader SD and plugged it into the odroidc4 in a usb port, then run the two commands making sure to get it right this time "/dev/sda". When finished, I take out the micro sd with the armbian system and connect the other micro SD with the u-boot in the odroidc4, and a usb 3.0 HDD disk with the armbian system, the system boots fine, I update the system with sudo apt update and sudo apt upgrade, i power cycle the system (for some reason when i use sudo reboot, the system doesn't boot, i have to force a shutdown to make it work again.) i can't do the last step, i don't have the 4pin UART cable. I also don't have an HDMI monitor to connect to. I hope you understand me because I'm using google translate. root@odroidc4:/home/odroid# fdisk -l Disk /dev/mmcblk0: 29.72 GiB, 31914983424 bytes, 62333952 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xc4d340a8 Device Boot Start End Sectors Size Id Type /dev/mmcblk0p1 8192 61702144 61693953 29.4G 83 Linux Disk /dev/zram0: 1.85 GiB, 1984663552 bytes, 484537 sectors Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/zram1: 50 MiB, 52428800 bytes, 12800 sectors Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/sda: 3.69 GiB, 3965190144 bytes, 7744512 sectors Disk model: R3PRO U-DISK Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes root@odroidc4:/home/odroid# dd if=/dev/zero of=/dev/sda dd: writing to '/dev/sda': No space left on device 7744513+0 records in 7744512+0 records out 3965190144 bytes (4.0 GB, 3.7 GiB) copied, 1212.41 s, 3.3 MB/s root@odroidc4:/home/odroid# dd bs=512 seek=1 conv=notrunc,fsync if=u-boot-meson.bin of=/dev/sda 2221+1 records in 2221+1 records out 1137520 bytes (1.1 MB, 1.1 MiB) copied, 0.454422 s, 2.5 MB/s root@odroidc4:/home/odroid# now the system booted from usb3.0 disk shows like this. root@odroidc4:~# df -h Filesystem Size Used Avail Use% Mounted on tmpfs 379M 15M 364M 4% /run /dev/sda1 146G 2.0G 142G 2% / tmpfs 1.9G 0 1.9G 0% /dev/shm tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 1.9G 0 1.9G 0% /tmp /dev/zram1 47M 1020K 43M 3% /var/log tmpfs 379M 0 379M 0% /run/user/0 root@odroidc4:~#

Hello, thanks for your answer, I did all the steps as you said and it seems to work, now the root is located on the usb 3.0 disk, but I didn't understand the last step " - boot the odroid c4 and post the serial console log" if you could explain how to do it, I would, sorry I don't have much knowledge in linux, I'm new to this. Now I am going to do a sudo apt update and sudo apt upgrade to update the system and see if it is solid or it breaks when updating. root@odroidc4:/# dd if=/dev/zero of=/dev/sda1 dd: writing to '/dev/sda1': No space left on device 5111809+0 records in 5111808+0 records out 2617245696 bytes (2.6 GB, 2.4 GiB) copied, 397.152 s, 6.6 MB/s root@odroidc4:/home/odroid# dd bs=512 seek=1 conv=notrunc,fsync if=u-boot-meson.bin of=/dev/sda1 2221+1 records in 2221+1 records out 1137520 bytes (1.1 MB, 1.1 MiB) copied, 0.222784 s, 5.1 MB/s root@odroidc4:/home/odroid# root@odroidc4:~# df -h Filesystem Size Used Avail Use% Mounted on tmpfs 379M 11M 369M 3% /run /dev/sda1 146G 2.0G 142G 2% / tmpfs 1.9G 0 1.9G 0% /dev/shm tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 1.9G 0 1.9G 0% /tmp /dev/zram1 47M 1020K 43M 3% /var/log tmpfs 379M 0 379M 0% /run/user/0 root@odroidc4:~# root@odroidc4:~# fdisk -l Disk /dev/mmcblk0: 57.95 GiB, 62226694144 bytes, 121536512 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xc4d340a8 Device Boot Start End Sectors Size Id Type /dev/mmcblk0p1 8192 5119999 5111808 2.4G 83 Linux Disk /dev/sda: 149.05 GiB, 160041885696 bytes, 312581808 sectors Disk model: Generic Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0xc4d340a8 Device Boot Start End Sectors Size Id Type /dev/sda1 8192 309428224 309420033 147.5G 83 Linux Disk /dev/zram0: 1.85 GiB, 1984663552 bytes, 484537 sectors Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/zram1: 50 MiB, 52428800 bytes, 12800 sectors Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes root@odroidc4:~# df -h Filesystem Size Used Avail Use% Mounted on tmpfs 379M 11M 369M 3% /run /dev/sda1 146G 2.0G 142G 2% / tmpfs 1.9G 0 1.9G 0% /dev/shm tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 1.9G 0 1.9G 0% /tmp /dev/zram1 47M 1020K 43M 3% /var/log tmpfs 379M 0 379M 0% /run/user/0 root@odroidc4:~#

Hello, thanks for your answer, I did all the steps as you said and it seems to work, now the root is located on the usb 3.0 disk, but I didn't understand the last step " - boot the odroid c4 and post the serial console log" if you could explain how to do it, I would, sorry I don't have much knowledge in linux, I'm new to this. Now I am going to do a sudo apt update and sudo apt upgrade to update the system and see if it is solid or it breaks when updating. root@odroidc4:/# dd if=/dev/zero of=/dev/sda1 dd: writing to '/dev/sda1': No space left on device 5111809+0 records in 5111808+0 records out 2617245696 bytes (2.6 GB, 2.4 GiB) copied, 397.152 s, 6.6 MB/s root@odroidc4:/home/odroid# dd bs=512 seek=1 conv=notrunc,fsync if=u-boot-meson.bin of=/dev/sda1 2221+1 records in 2221+1 records out 1137520 bytes (1.1 MB, 1.1 MiB) copied, 0.222784 s, 5.1 MB/s root@odroidc4:/home/odroid# root@odroidc4:~# df -h Filesystem Size Used Avail Use% Mounted on tmpfs 379M 11M 369M 3% /run /dev/sda1 146G 2.0G 142G 2% / tmpfs 1.9G 0 1.9G 0% /dev/shm tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 1.9G 0 1.9G 0% /tmp /dev/zram1 47M 1020K 43M 3% /var/log tmpfs 379M 0 379M 0% /run/user/0 root@odroidc4:~# root@odroidc4:~# fdisk -l Disk /dev/mmcblk0: 57.95 GiB, 62226694144 bytes, 121536512 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xc4d340a8 Device Boot Start End Sectors Size Id Type /dev/mmcblk0p1 8192 5119999 5111808 2.4G 83 Linux Disk /dev/sda: 149.05 GiB, 160041885696 bytes, 312581808 sectors Disk model: Generic Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0xc4d340a8 Device Boot Start End Sectors Size Id Type /dev/sda1 8192 309428224 309420033 147.5G 83 Linux Disk /dev/zram0: 1.85 GiB, 1984663552 bytes, 484537 sectors Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/zram1: 50 MiB, 52428800 bytes, 12800 sectors Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes root@odroidc4:~# df -h Filesystem Size Used Avail Use% Mounted on tmpfs 379M 11M 369M 3% /run /dev/sda1 146G 2.0G 142G 2% / tmpfs 1.9G 0 1.9G 0% /dev/shm tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 1.9G 0 1.9G 0% /tmp /dev/zram1 47M 1020K 43M 3% /var/log tmpfs 379M 0 379M 0% /run/user/0 root@odroidc4:~#

I'm running Armbian Cli 23.02.2 Jammy with Linux 6.1.11-meson64 on my OdroidC4, I'd like to be able to boot from a USB3.0 SSD, (I'm aware that this board doesn't have SPI flash memory, so you should sacrifice a micro SD to host the system boot) When I run armbian-config and go to the option to "boot from SD - systemd on SATA, USB or NVMe" the process seems to complete all the steps without difficulty, at the end the process asks to reboot, the problem starts here, at perform the reboot the system never boots, it stays in a loop, the SSD flashes led light as if it had activity, the same my odroid c4 flashes blue led light in a loop, but the system never appears by ssh. I hope someone can help me. Excuse my English, I'm using a translator.

Hello, I am trying to boot my odroid c4 from a USB 3.0 storage, the steps I am following are the ones that appear in armbian-config but, the steps seem to complete well but at the time of the first reboot my system does not boot, you seem to have found the solution, could you please make a small guide for beginners like me? my goal is to boot my odroid from USB3.0 storage with the image Armbian_23.02.2_Odroidc4_jammy_current_6.1.11, it is the version without a desktop, I connect via SSH, I do not use the latest image Armbian_23.5.1_Odroidc4_jammy_current_6.1.30 because the kernel does not seem to be stable.