All Activity

Hello and thanks for your answer. Seems that no, I'm trying R-studio now and it's finding 7 superblocks, and for now it has found 5000+ files... Will try to get this back after the scanning.

For anyone looking for simple instructions to install the official Armbian image for "H96 Max V56" (as of August 30th, 2025) using a Linux PC (e.g. Ubuntu Desktop 24.04): 1. Install the "rkdeveloptool" tool first, as instructed in: https://docs.radxa.com/en/zero/zero3/low-level-dev/rkdeveloptool?host-os=debian sudo apt-get update sudo apt-get install -y libudev-dev libusb-1.0-0-dev dh-autoreconf pkg-config libusb-1.0 build-essential git wget git clone https://github.com/rockchip-linux/rkdeveloptool cd rkdeveloptool autoreconf -i ./configure make -j $(nproc) sudo cp rkdeveloptool /usr/local/sbin/ At the time of writing, this installed version 1.32. If you installed "rkdeveloptool" from Ubuntu's repos, it would install version 1.0 which may work, but let's be on the safe side here... 2. Connect and boot the device to loader/maskrom mode 2.1 While pressing the reset button (back/right) with a pin, connect the USB 2.0 port (back/left) and the power cable. Gotta be careful here not to miss the reset button pressing while connecting the cables. 2.2 Use the rkdeveloptool tool to identify the device and the mode it is on ("loader" or "maskrom"). $ rkdeveloptool ld ...should show the connected device if point 2.1 was successful - e.g. on my 8GB RAM device it printed this: DevNo=1 Vid=0x2207,Pid=0x350a,LocationID=304 Loader Or after I had already flashed Armbian, it would show: DevNo=1 Vid=0x2207,Pid=0x350a,LocationID=304 Maskrom (If you installed "rkdeveloptool" from Ubuntu's repo, the command is "rkdeveloptool list" if I recall correctly - every other "rkdeveloptool" command following though is the same) Now grab the latest release of Armbian for this device. At the time of writing it was: https://github.com/armbian/community/releases/download/25.11.0-trunk.106/Armbian_community_25.11.0-trunk.106_H96-tvbox-3566_bookworm_current_6.12.44_minimal.img.xz (the name of the device is on the filename) Extract the included .img file with (sudo apt install xz-tools): $ unxz Armbian_community_25.11.0-trunk.106_H96-tvbox-3566_bookworm_current_6.12.44_minimal.img.xz 2.2.1 If in "loader" mode (see the last part of the command's output above), simply flash Armbian directly. E.g. $ sudo rkdeveloptool wl 0x0 Armbian_community_25.11.0-trunk.106_H96-tvbox-3566_bookworm_current_6.12.44_minimal.img (if you attempt to flash the attached bootloaders, you'll get a "device not supported" error - Armbian already contains a bootloader) 2.2.2 If in "maskrom" mode (e.g. if you are re-flashing Armbian), flash the bootloader first: # For the 8GB RAM device use the attached (in this post) H96-MAX-8gb-MiniLoaderAll.bin file $ sudo rkdeveloptool db H96-MAX-8gb-MiniLoaderAll.bin # For the 4GB RAM device use the attached (in this post) H96-MAX-4gb-MiniLoaderAll.bin file $ sudo rkdeveloptool db H96-MAX-4gb-MiniLoaderAll.bin ...and then re-flash Armbian as you did the first time: $ sudo rkdeveloptool wl 0x0 Armbian_community_25.11.0-trunk.106_H96-tvbox-3566_bookworm_current_6.12.44_minimal.img 2.3 Reboot the device with: $ sudo rkdeveloptool rd Done! If all goes well, once you reboot the device you will be asked to set a root password and optionally a sudo user. Rebooting afterwards you should now be greeted with: _ _ _ _ _ /_\ _ _ _ __ | |__(_)__ _ _ _ __ ___ _ __ _ __ _ _ _ _ (_) |_ _ _ / _ \| '_| ' \| '_ \ / _` | ' \ / _/ _ \ ' \| ' \ || | ' \| | _| || | /_/ \_\_| |_|_|_|_.__/_\__,_|_||_|_\__\___/_|_|_|_|_|_\_,_|_||_|_|\__|\_, | |___| |__/ v25.11 rolling for h96-tvbox-3566 running Armbian Linux 6.12.44-current-rockchip64 Packages: Debian stable (bookworm), possible distro upgrade (trixie) Updates: Kernel upgrade enabled and 2 packages available for upgrade Support: for advanced users (rolling release) IPv4: (LAN) 192.168.1.10 (WAN) 1.2.3.4 Performance: Load: 3% Uptime: 2 min Memory usage: 2% of 7.50G CPU temp: 40°C Usage of /: 3% of 57G Commands: Configuration : armbian-config Upgrade : armbian-upgrade Monitoring : htop Last login: Sat Aug 30 12:47:54 2025 Key points: - If you do this the first time, it's obviously a matter of just flashing the latest Armbian image directly. - You don't need to open the device or compile Armbian. - It's simpler than 2 years ago when I bought the device thanks to people like @Hqnicolas (muito obrigado Nicolas!) H96-MAX-4gb-MiniLoaderAll.bin H96-MAX-8gb-MiniLoaderAll.bin

please be more specific, what happened exactly? where did you get that statement that netplan or networkmanager are not supposed to touch firewall settings? when you bring a network interface up or down that can obviously affect firewall rules.

you just overwrote all your data. sorry for the bad news.

I fixed in the past some problems with sata drive by setting to "rolling" the sources in armbian-config. A few day ago I wanted to upgrade to trixie (debian 13) sources. I forgot to set up again the armbian-config sources to "stable" and I went in a bad situation with my raid1 : it completely disappeared from /etc/mdadm/mdadm.conf, and was unable to mount. After several struggling with the command line tools, I managed to get it recreated by the following command : mdadm --create --force /dev/md0 \ --level=1 \ --raid-devices=2 \ /dev/sdc1 /dev/sdd1 \ --metadata=1.2 --data-offset=$(( 264192/2 ))K Now it seems to be syncing, but I think the filesystem was damaged... (though I don't now, perhaps all be ok again after sync) Is there a way other than photorec to get my data back ? Thanks a lot.

@Ducdanh Nguyen can you see your axp chip? never heard of bigfish. Is that a heat sink on your SOC? Not sure why it has no writing on it. Install this android app it should give you more information https://play.google.com/store/apps/details?id=com.finalwire.aida64&hl=en_CA&pli=1 Did you apply the secure boot patch?

Hello everyone - I started having problems with installing to eMMC and I assume it is related to uboot. It used to work in the past on my devices but it doesn't anymore. The script runs successfully without any errors (besides not finding the ini file, which is irrelevant supposedly). But when trying to boot from eMMC (sd removed), I get a couple of errors (Card did not respond to voltage select), which indicates, that the eMMC can't be found. It tries booting from USB and ETH and ultimately fails. Is anybody else seeing this issue? I'm running a Vontar X3 (identical with HK1 and X96 max). By the way - the eMMC is fine. When I boot from the SD card, I can mount the eMMC ROOT and BOOT partition and they seem all correct.

This does not seem to work anymore. The flashing works but when trying to boot from eMMC, the device can't initialize the eMMC anymore ("Card did not react to voltage select"). Anybody else seeing this problem?

Hello crew, I have similar issues with installing to eMMC. In the past I was able to flash to eMMC and boot from there. I bought a second device (I'm running 2 Vontar X3, which are identical with HK1 and H96 Max, running 905x3) and flashing the newer versions of Armbian does not work anymore. I can run it from the SD card, I can even run the install script, but it will only boot, when the SD card is still in. When I try booting from the eMMC, it does not work. In the past it worked but something seems to have changed over time. I'm going the clean route and flash the original android firmware before trying to flash Armbian, to have a clean environment. I assume it's a change in U-Boot and the eMMC not being initialized correctly. When trying to boot, I get a bunch of "Card did not respond to voltage select! : -110" error messages. Then it tries booting over USB or ETH, which all fails. Does anybody know, how I could make it boot from eMMC again? Who is responsible for uboot? Thanks in advance!

Specifically, your board is "Community Maintained" That means it is not supported by Armbian resources (beyond the automated infrastructure to make builds and host them for the community) https://docs.armbian.com/User-Guide_Board-Support-Rules/#community-maintained

@Nick A su binary installed, but not working correctly, i don't know why, the chip is def h313 because i used cat /proc/cpuinfo(and others) and with grok commands i can confirm it uses cortex-a53 (which includes in h313) and bigfish manufactor/ or codename idk but it's part of allwinner, i mean enought to prove that mine is h313

@dale you need a display overlay that is compatible with tm16xx. OpenVFD overlays are NOT supported. You can read README.md and dt-bindings documentation at https://github.com/jefflessard/tm16xx-display But note that there has been many changes recently to the code base since the driver is currently in review process to be upstreamed into mainline kernel (targeting v6.18). So double check which bindings version format has been integrated into Armbian rockchip64. The GitHub repo also contains a vfd-convert utility to automatically convert OpenVFD configuration files to expected tm16xx DTSO. But : 1. It requires OpenVFD conf file, not dtso. 2. You may need to go through file history to get the version matching of what has been integrated into Armbian rockchip64.

@Ducdanh Nguyen do you know which axp chip you have on your board? It’s a very small chip with axp written on it. I don’t see the H313 markings on your SOC chip. Are you sure you have a H313? If you don’t see an axp chip you might not even have a allwinner SOC. If your android is rooted then it probably has one installed.

If you can solve the problem, please share it with the community.

@Jean-Francois Lessard I'm sorry for the typo. Yes the controller is tm1628. ls /sys/class/leds --> shows empty. Dmesg doesn't show any message for tm16xx. I've attached the working overlay source for openvfd which I have the clock digits working at least with. (The full icons would be card, usb, Low wifi, hi wifi, apps and eth) openvfd_x98h.dts

To replace an image on the eMMC, the MASKROM mode is not necessary. It is only required when the firmware is so damaged that it no longer works, but the signature is still intact and the MASKROM code still executes it. To replace an image, it is sufficient to boot from a rootfs that is not on the eMMC and replace it from there. And the good thing about it is that no device-specific hacks are necessary, just a properly configured bootflow. Furthermore, it is also self-contained, as no external devices with special software or other dependencies are necessary. It can also be automated in such a way that it runs unattended and the user only has to start the process initially.

Wait @Nick A when a device is rooted, do i need a root manager???

@Nick A i flashed it to my card and it's not booting to armbian...

Customizing image and customizing kernel are different tasks. For latter use the code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } kernel-config command and then copy over the created config file from output to userpatches. The framework will look for custom kernel configuration files and uses them if they're detected. More details here: https://zuckerbude.org/armbian-using-kernel-config/

@Nick A success build log : https://paste.armbian.eu/simirepihe

Thanks. I'll have to look into that. I expect that's for customizing the packages installed?

Armbian uses Netplan by default to manage network settings. But when it uses NetworkManager as renderer, it silently changes iptables rules—without asking, without telling. *Neither Netplan nor NetworkManager are supposed to manage firewall settings.* But they do it anyway, behind the scenes. That kind of behavior—making security changes without user consent—feels a lot like what malware does.

@Nick A full log (failed): [💲|🌱] Starting main configuration [💲|🌱] Using REVISION from [ main VERSION file: '25.05.0-trunk' ] [💲|🌿] Enabling extension [ armbian-config ] [💲|🌱] Sourcing family configuration [ /home/nguye/build/config/sources/families/sun50iw9.conf ] [💲|🌿] Enabling extension [ sunxi-tools ] [💲|✅] change-tracking: after sourcing family config [ KERNEL_MAJOR_MINOR='6.12' ] [💲|✅] change-tracking: after sourcing family config [ KERNELBRANCH='tag:v6.12.11' ] [💲|✅] change-tracking: after sourcing family config [ LINUXFAMILY='sunxi64' # (was: 'sun50iw9') ] [💲|✅] change-tracking: after sourcing family config [ KERNELPATCHDIR='archive/warpme-6.12' ] [💲|✅] change-tracking: after sourcing family config [ BOOTBRANCH='tag:v2025.01' ] [💲|✅] change-tracking: after sourcing family config [ BOOTPATCHDIR='u-boot-h616' ] [💲|✅] change-tracking: after sourcing family config [ ATFBRANCH='tag:lts-v2.10.14' ] [💲|✅] change-tracking: after sourcing family config [ NETWORKING_STACK='network-manager' ] [💲|🌱] Sourcing arch configuration [ arm64.conf ] [💲|✅] change-tracking: after sourcing arm64 arch [ ATFDIR='arm-trusted-firmware' ] [💲|🌱] Using NETWORKING_STACK [ NETWORKING_STACK: network-manager ] [💲|🌱] Adding networking extensions [ net-network-manager, net-chrony ] [💲|🌿] Enabling extension [ net-network-manager ] [💲|🌿] Enabling extension [ net-chrony ] [💲|🌱] Extension manager [ processed 17 Extension Methods calls and 27 Extension Method implementations ] [💲|🌱] x96q-lpddr3 [ Using allwinner/sun50i-h313-x96-q-lpddr3.dtb for edge ] [💲|💥] Error 1 occurred in SUBSHELL [ SUBSHELL at /home/nguye/build/lib/functions/configuration/config-desktop.sh:48 ] [💲|💥] Cleaning up [ please wait for cleanups to finish ] [💲|🌿] ANSI log file built; inspect it by running: [ less -RS output/logs/log-build-5e1956f5-4bb3-4cdf-b026-7bcfa7d1794e.log.ans ] [💲|🌱] Share log manually: [ use one of the commands below (or add SHARE_LOG=yes next time!) ] [💲|🌿] Share log manually: [ curl --data-binary @output/logs/log-build-5e1956f5-4bb3-4cdf-b026-7bcfa7d1794e.log.ans https://paste.armbian.com/log ] [💲|🌿] Share log manually: [ curl --data-binary @output/logs/log-build-5e1956f5-4bb3-4cdf-b026-7bcfa7d1794e.log.ans https://paste.armbian.de/log ] [💲|🌿] Share log manually: [ curl --data-binary @output/logs/log-build-5e1956f5-4bb3-4cdf-b026-7bcfa7d1794e.log.ans https://paste.next.armbian.com/log ] [💲|🌿] Share log manually: [ curl --data-binary @output/logs/log-build-5e1956f5-4bb3-4cdf-b026-7bcfa7d1794e.log.ans https://paste.armbian.eu/log ] nguye@DESKTOP-IFEAUMD:~/build$ EDIT: it continued while i tried Debian 12 Next i choosed xfce config_base (onlyone) internet

@Nick A i choosed x96q-lpddr3 (csc) Allwinner H313 TVB with 2gigs of ram and emmc (my box uses emmc) debian 11 image with desktop enviroment

by the way i don't see any options with allwinner h313 and 1gb ram, can i just choose the 2gb x96q?