Jump to content

zhuceluntan

Members
  • Posts

    6
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I'm also troubled by this boot issue. For older images balbes150 offers with uEnv.txt, such as Armbian_20.06.0_Arm-64_buster_current_5.7.2_20200619.img.xz, I can always boot from USB no matter what's been installed on the emmc. This is extremely useful because I can easily restore emmc to original Android using ddbr. However, when it comes to the newer images without uEnv.txt, such as Armbian_20.10_Arm-64_bullseye_current_5.9.0.img.xz, everything changed. I cannot boot from usb anymore unless the system on emmc is original Android. I've been seeking for solution since April 2021 but no answer could be found by now.
  2. Thank you for the knowledge. I will pay attention from now on.
  3. @balbes150 Please let me know if any information you need is missing.
  4. @balbes150The original topic. I just use Armbian_20.10_Arm-64_buster_current_5.9.0.img.xz and find out that I cannot boot from USB anymore after installing the Armbian into EMMC. My device is phicomm-n1, and my steps were: 1. Edit /extlinux/extlinux.conf 2. Rename u-boot-s905x-s912 to u-boot.ext 3. ./install-aml.sh Now the EMMC is at the highest priority. However, the USB was always the highest when using previously published images such as Armbian_20.06.0_Arm-64_buster_current_5.7.2_20200619.img.xz What could I do to make it boot from USB first? Thank you.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines