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. The boot/ directory only contained grub/, no hidden files and no *dtb. 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 Realtek being based in Taiwan. 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, which 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. This would be an easier path to MainStream klipper.

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

I don't believe you did. As the install instructions linked to from the download page don't mention any of the things you tried (like armbian-config, armbian-install, nand-sata-install, etc). These are the instructions for the amlogic s9xx tv box builds (again these are linked from the download page): https://forum.armbian.com/topic/33676-installation-instructions-for-tv-boxes-with-amlogic-cpus These instructions tell you to run /root/install-aml.sh which is not what you said you did. Now a further note is that ophub is a fork of Armbian. They do not contribute to Armbian development, do not participate in these forums and use the Armbian name without permission. So if you choose to use their software, you will need to discuss their software on their forums as we can't help you at all with ophub software.

Hi, thank you for the quick reply. I did read the install instructions, but the thing is there was no install script. I downloaded the minimal iot image I think. I did try updating armbian-config but there was no options for install. And since I didn't find many tutorials on how-to-install, I used claude - sonnet 4.5 (I kinda trust it more than gpt 5, but it still hallucinates sometimes). I admit I don't really like relying on ai tools, but I really find them quite useful (and sometimes quite wrong). Anyway, I don't know if the image didn't include install script or maybe I accidentally removed it with apt autoremove (shouldn't be the case, since I only removed xfce and related components with apt autoremove). And I couldn't find it with apt search. I have now downloaded an image from https://github.com/ophub/amlogic-s9xxx-armbian/releases. It has quite a bigger footprint: ~750MB compressed, compared to ~300MB compressed I downloaded from this site (labeled minimal iot). I also have acquired a h96 air p2 firmware from the official h96 site. Will report how it works. I still would like to try to flash armbian to mmc after I hopefully get it booting from the usb. Do you know why I didn't have an install script in my image? I mean how does it work, can I maybe just download it from somewhere (for my exact box) or why isn't it added in apt? I will try to flash this other image downloaded from github to the usb and see if there is the install script.