el es

Hi, I installed the wrong image on a Rockchip RK3288 (Hannspree) Android 5.1 TV box. Now it won't boot from internal memory or sd-card, power on, light up or anything. Like it was hit by lightning. Is this expected? What has happened? (This very comprehensive and helpful post says that "If the internal flash does not contain a bootable system, they will always boot from the sdcard.") Thank you good people (The tag on this post is wrong... I could not find a RK3288 tag)

Had been thinking of doing so, as it happens. I'm not sure, can I be useful? I am familiar with Github, but I only have beginner Python/C/SQL so far. Do you need testers? Don't get me wrong - I do appreciate the project, and it is a good one. Thanks for the links to the FAQs.

No replies... First error is apparently due to different types of RK3288 which may not be compatible with the image. Post below recommends using a Tinkerboard image. For second error I wonder if it is a problem with whether ISO9660 is supported. Perhaps it needs the .img.xz image rather than .iso.

Hi, I used multitool and installed Armbian_22.05.0-trunk_Xt-q8l-v10_jammy_current_5.15.35_xfce_desktop.img.xz onto a Hanspree AK01 miniPC. It does not boot and drops into a busybox shell: Starting version 249.11.0ubuntu3 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... BEgin: Running scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done. done. Gave up waiting for root file system device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Missing modules (cat /proc/modules: ls /dev) ALERT! UUID=90fc5c5eq-35fd-44dc-97d8-a8d0cbaba4ba does not exist. Dropping to a shell! Busybox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu3) Buid-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) What should I try now? I also tried pausing the boot in u-boot, and booting a xubuntu 22.04 live USB: U-Boot 2022.04-armbian *Apr 24 2022 16:31:34 +0000) Model: XT-Q8L-V10-RK3288 DRAM: 2GiB Core: 189 devices, 22 classes, devicetree: separate MMC: dvmc0ff0c0000: 1, dvmc0ff0c0000: 0 Loading environment from MMC: *** Warning - bad CRC, using default environment In: serial Out: vidconsole Err: vidconsole Model: XT-Q8L-V10-RK3288 Net: eth0: ethernet0ff290000 starting USB... Bus usb00ff5400000: USB DWC2 Bus usb00ff5500000: USB DWC2 Scanning bus usb00ff5400000 for devices... 5 USB device(s) found Scanning bus usb00ff5500000 for devices... 1 USB device(s) found Hit any key to skip autoboot: 0 =>usb storage Device 0: Vendor A1: Rev: Prod: Mass Storage Type: Removble Hard Disk Capacity: 15376.0 15GiB =>usbboot usb 0 Loading from usbdevice 0, partition 1: Name: ISO9660 Type: U-Boot Unknown Image Type How do I fix the ubuntu install fail? Is there something that can be done in busybox? How would I boot from the SD-card, or a USB? Thank you