Hey friends, I'm back. Well, good news. I got the box to boot from an SD card, specifically the 'Armbian_23.08.0-trunk_Rk322x-box_buster_edge_6.5.5_minimal.img' image, bad news I am not sure how to get it onto the eMCP and this is probably not the way you're supposed to boot armbian. I got the rk322x-box.dtb from the 'LibreELEC-RK322X.arm-11.0-nightly-20240218-d7324fb-rk322x.img' image (used by KanexMarcus in the comment here) and I had to add 'irqpoll' to extraargs in armbianEnv.txt, only after that did it boot. Ethernet works, wireless doesn't, using lsblk doesn't display the internal storage. Not sure what to do now, just figured I'd check in just to tell everyone what's going on and how I got it working.

Hello, I had a similar problem - unbootable Rock64 after kernel upgrade from 6.6.x to 6.12.x (error: Wrong Ramdisk Image Format). You can look in this thread djurny found a solution, that works for me. Maybe it will help.

I did establish a wifi connection and ssh sovol@IPaddress. Have the following: sovol@sovol:/$ ls -a -C . data lib opt run srv userdata .. dev lost+found packages sbin sys usr .resized etc media proc sdcard system var bin home mnt rockchip-test sha256sum.README tmp vendor boot info oem root sha256sum.txt udisk sovol@sovol:/$ uname -a Linux sovol 5.10.160 #54 SMP PREEMPT Mon Aug 5 22:22:56 CST 2024 aarch64 GNU/Linux Could not cd to root/ and tried to su using mks, makerbase, sovol and 1234 as root passwds. Edit: I can run root commands with sudo The boot/ directory only contained grub/, no hidden files and no *dtb. Edit: Regained wifi after changing channel ?congestion. I looked at the FCCid site and the photos submitted to the FCC show a Realtek rtk8189FTV chip. It looks like the Fn-Link chip was substituted perhaps due to Mainland/Taiwan tensions. Not sure the FCC knows about the chip substitution or if new wifi test data was generated. The wifi on this board is crippling in many ways, Crowsnest cam access saves me many trips up/down the stairs to check for print failures. Still, it does not look like Sovol will be providing any more firmware updates. The two that are available can only be installed by a wifi connection using OTA (Over The Air). Paranoia is high for wireless connections that you know nothing about. I'm wondering about replacing the mainboard with the mks-skipr and adding a wifi module with mainstream kernel support. May be a better path to MainStream klipper and reliable mainstream wifi. Edit: Was able to scp/pull the following files: config-5.10 gpio.txt ip_address.txt rockchip_config. Building my own image still may be an option but will need to deal with the wifi driver, a python script for crowsnest camera and the LED light. Edit: Armbian-mkspi has patches for rtl8189fs. Image building is doable - not sure if wifi will be improved but Mainline Klipper, a more recent kernel, packages with updates can be had on stock boards.

I just downloaded both images available on the download page (minimal and xfce desktop) and both images had the install-aml.sh script in the /root directory. As far as your current state, I only know of the windows amlogic tool as being the only available way to restore an android image. I know nothing about the Khadas tools you are trying to use, whether they will work on non-khadas boards, or if they can be used for what you are trying to do.

Ok. I don't mean to disrespect, but I did read the install instructions. It's just I couldn't find the /root/install-aml.sh script, I checked multiple times, reflashed it etc (even checked /boot ). Don't know if it makes any difference, I flashed my usb using dd, not balena. I did notice it makes two partitions (armbi_boot and armbi_root), but it worked anyway. If it does make a big difference, apologies for my ignorance. About ophub, I didn't really know - glad you pointed it out - that it's a fork that doesn't contribute and that uses the name without permission. Currently, I'm struggling trying to get the board in usb burn mode. I just don't know which pins to short, and don't want to short the wrong ones (even though I did play around). The mmc is ball-grid-array, so really hard to figure it out. I looked up the datasheet for the chip but I can't really figure it out. So I shorted something that looked shortable (I'm sorry, but I really didn't know what to short). It did allow me to enter usb burn mode once, but it stayed in usb burn for hours (I didn't want to unplug, since I knew I probably won't be able to get it there again). So I tried flashing the stock rom (official h96 website), but it timed out, then the board became unresponsive. I tried a couple of times, but nothing. Now I unplugged it, and can't get it back in usb-burn. It does have some reactions to shorting the same pins, looking at uart logs, but I just can't get it to enter that state anymore. Any help is greatly appreciated. Tools I have used: I'm running linux, so I can't use the standard usb burn amlogic tool. I clone the repo https://github.com/khadas/utils