Active threads

Hi folks, Very new to this community, very new to flashing Android boxes.. But I wanted to give this a shot and make use of an old TX5 Pro that I had in a drawer. Pleased to say, boots from the SD card fine, managed to get logged in and set up... all is working, WiFi, Bluetooth etc... However, I am just not able to get this to boot from the eMMC. I got to the point where I bricked it and had to re-flash Android onto it.. just to find myself in the same loop. I'll provide as much info as I can here, but let me know if you need something more specific. I'm no expert here, so here goes. Booting from the SD starts like this: When booted, all is working totally fine. However, removing the SD results in the following, where it will stay for eternity util rebooting and inserting SD: ChatGPT led me to screw this up entirely, despite getting this far based on it's instructions, so I'm turning to you for help. I really need to have this booting from the internal storage and not from an SD card. Here's the copy attempt: root@aml-s9xx-box:~# ./install-aml.sh Start script create MBR and filesystem /dev/mmcblk1 Start backup u-boot default 4+0 records in 4+0 records out 4194304 bytes (4.2 MB, 4.0 MiB) copied, 0.149809 s, 28.0 MB/s Start create MBR and partittion Start restore u-boot 442+0 records in 442+0 records out 442 bytes copied, 0.0044687 s, 98.9 kB/s 8191+0 records in 8191+0 records out 4193792 bytes (4.2 MB, 4.0 MiB) copied, 0.524224 s, 8.0 MB/s Done Start copy system for eMMC. Formatting BOOT partition...mkfs.fat 4.2 (2021-01-31) done. mount: (hint) your fstab has been modified, but systemd still uses the old version; use 'systemctl daemon-reload' to reload. Copying BOOT...done. Edit init config...done. sed: can't read /ddbr/install/boot.ini: No such file or directory done. Formatting ROOT partition... /dev/mmcblk1p2 contains a ext4 file system labelled 'ROOT_EMMC' last mounted on /ddbr/install on Fri May 23 19:51:02 2025 e2fsck 1.47.0 (5-Feb-2023) ROOT_EMMC: clean, 11/855120 files, 80315/3419392 blocks done. Copying ROOTFS. mount: (hint) your fstab has been modified, but systemd still uses the old version; use 'systemctl daemon-reload' to reload. Copy BIN Create DEV Copy ETC Copy HOME Copy LIB Copy LIB64 tar: lib64: Cannot stat: No such file or directory tar: Exiting with failure status due to previous errors Create MEDIA Create MNT Copy OPT Create PROC Copy ROOT Create RUN Copy SBIN Copy SELINUX Copy SRV Create SYS Create TMP Copy USR Copy VAR Copy fstab rm: cannot remove '/ddbr/install/usr/bin/ddbr': No such file or directory ******************************************* Complete copy OS to eMMC ******************************************* Here's some info about the setup, again, let me know if you need something extra: _ _ _ _ _ /_\ _ _ _ __ | |__(_)__ _ _ _ __ ___ _ __ _ __ _ _ _ _ (_) |_ _ _ / _ \| '_| ' \| '_ \ / _` | ' \ / _/ _ \ ' \| ' \ || | ' \| | _| || | /_/ \_\_| |_|_|_|_.__/_\__,_|_||_|_\__\___/_|_|_|_|_|_\_,_|_||_|_|\__|\_, | |___| |__/ v25.5 rolling for aml-s9xx-box running Armbian Linux 6.12.28-current-meson64 Packages: Debian stable (bookworm) Updates: Kernel upgrade enabled and 76 packages available for upgrade Support: for advanced users (rolling release) IPv4: (LAN) 10.0.1.102 (WAN) 5.13.247.183 Performance: Load: 32% Up time: 1 min Memory usage: 21% of 1.87G CPU temp: 54°C Usage of /: 20% of 29G RX today: 64 MiB Commands: Configuration : armbian-config Upgrade : armbian-upgrade Monitoring : htop System and Boot Logs: https://paste.armbian.com/fiqikiliju PRETTY_NAME="Armbian_community 25.5.0-trunk.538 bookworm" NAME="Debian GNU/Linux" VERSION_ID="12" VERSION="12 (bookworm)" VERSION_CODENAME=bookworm ID=debian HOME_URL="https://www.armbian.com" SUPPORT_URL="https://forum.armbian.com" BUG_REPORT_URL="https://www.armbian.com/bugs" ARMBIAN_PRETTY_NAME="Armbian_community 25.5.0-trunk.538 bookworm" root=UUID=e969167d-e6a9-4203-896f-ced402105523 rootflags=data=writeback console=ttyAML0,115200n8 console=tty0 rw no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 splash plymouth.ignore-serial-consoles NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS mmcblk0 ├─mmcblk0p1 vfat FAT32 armbi_boot 479F-151E 414M 19% /boot └─mmcblk0p2 ext4 1.0 armbi_root e969167d-e6a9-4203-896f-ced402105523 22.5G 19% /var/log.hdd / mmcblk1 ├─mmcblk1p1 vfat FAT16 BOOT_EMMC 75EA-4970 └─mmcblk1p2 ext4 1.0 ROOT_EMMC d0456959-1f46-4aad-b7f0-d784208d67a8 mmcblk1boot0 mmcblk1boot1 zram0 [SWAP] zram1 40.2M 7% /var/log zram2 label Armbian_community kernel /Image initrd /uInitrd fdt /dtb/amlogic/meson-gxl-s905x-p212.dtb append root=UUID=e969167d-e6a9-4203-896f-ced402105523 rootflags=data=writeback console=ttyAML0,115200n8 console=tty0 rw no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 splash plymouth.ignore-serial-consoles Any assistance would be greatly appreciate.

Have you tried with current or edge kernels?

Apologies. Didn't realise that. I have no means of connecting to uart - I'll want until a bootable version shows up.

I updated my system and it broke again. Had some trouble getting it to work again. For some reason the DTS editor doesn't come up in armbian-config anymore(?). Anyway, it can be done from the console. I decompiled the sun501-h6-orangepi-3-lts.dtb, edited it and compiled it again. It worked as a charm. I noticed that the spi pins had changed to 0x31 and 0x32 and the spi@5011000 phandle was 0x78 instead of 0x7a. I only changed status to "okay" and added the spidev@0 {...} section. Then I removed the dtbo overlay. spi@5011000 { compatible = "allwinner,sun50i-h6-spi\0allwinner,sun8i-h3-spi"; reg = <0x5011000 0x1000>; interrupts = <0x00 0x0b 0x04>; clocks = <0x06 0x53 0x06 0x51>; clock-names = "ahb\0mod"; dmas = <0x2e 0x17 0x2e 0x17>; dma-names = "rx\0tx"; pinctrl-names = "default"; pinctrl-0 = <0x31 0x32>; resets = <0x06 0x20>; status = "okay"; #address-cells = <0x01>; #size-cells = <0x00>; phandle = <0x78>; spidev@0 { compatible = "armbian,spi-dev"; reg = <0x00>; spi-max-frequency = <0xf4240>; }; };

I only tested the main configuration to ensure that the kernel and file system rootfs are normal, and other configurations have not been tested yet The attachments are patch files and several modified source files. The testing was conducted in my own buildroot project. It has not been tested in armbian yet (there are currently some issues with the armbian compilation environment). My buildroot project was launched based on the DTS of this post. I believe it should be available in armbian. add-rk3576h96-m9s-dts.patch rk3576-linux.dtsirk3576-h96-m9s.dtsrk3576.dtsi

It's a bit embarrassing, but in my case the fault was entirely mine. I seemed to have messed around a bit too much with the system. However, maybe this helps someone else with their problem as well. One of the changes I did to my system caused the /lib directory to be replaced by an actual directory instead of a symlink to /usr/lib. As the init.d script is stored in /usr/lib/init, the boot process couldn't find it anymore under the path it expects it to, the kernel panicked. I then removed the directory including all its contents and replaced it with the correct symlink again. Since then, my Cubietruck has been working fine.

I have resolved it, modified in the driver.

It would be nice to know what is the actual problem here, so we can at least add instructions. If XZ format is not supported, then probably it needs to be decompressed manually, perhaps renamed to ISO and then flash. Or there is some other trick here? P.S. Mirror fixed the problem on their side.

Released so far: 2025-05-22 18:26:26 lepotato/ 2025-05-22 06:07:29 tritium-h3/ (untested) 2025-05-21 22:12:58 tritium-h5/ (untested) 2025-05-21 13:54:39 nanopi-r2s/ 2025-05-21 13:19:56 nanopi-r4s/ 2025-05-21 13:10:48 bigtreetech-cb2/ 2025-05-21 12:37:56 nanopi-r1/ 2025-05-21 08:24:34 odroidxu4/ 2025-05-20 21:02:21 bananapim2plus/ 2025-05-19 16:34:51 tinkerboard/ 2025-05-19 16:08:37 odroidc1/ 2025-05-19 13:41:51 cubox-i/ 2025-05-19 13:33:57 udoo/ 2025-05-18 18:14:19 rock-5c/ 2025-05-15 20:00:20 odroidm1/ 2025-05-15 19:45:23 odroidn2/ 2025-05-15 19:22:52 uefi-x86/ 2025-05-15 19:07:47 uefi-arm64/ 2025-05-15 17:31:47 odroidc4/ 2025-05-15 17:26:55 bigtreetech-cb1/ 2025-05-15 14:28:07 bananapicm4io/ 2025-05-15 14:10:36 rockpi-e/ 2025-05-15 13:15:45 helios4/ 2025-05-15 13:09:35 bananapim2pro/ 2025-05-15 12:47:30 clearfogpro/ 2025-05-15 12:14:00 nanopik2-s905/ 2025-05-15 11:21:35 mksklipad50/ 2025-05-15 10:05:49 odroidc2/ 2025-05-14 18:48:20 bananapif3/ I do this manually, every day few boards, those which I have around - basically I am manually updating my test farm. Many thanks to all that already helped in making this list longer. Release text is also WIP - even AI helps, its still quite a lot of work to convince (drunk / stupid) AI what do we want If you have time, please help - make image https://docs.armbian.com/Process_CI/#prepare-application-images-for-release-release-manager test it and provide feedback. In case you find something, hit red button here and make a short note. Thank you! code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } Would you like to take on the role of maintainer for a specific board? https://docs.armbian.com/User-Guide_Board-Support-Rules/

Meanwhile, I have enabled ADB and debugging over wifi, and have connected to cli: 127|rk3528_box:/ $ uname -a Linux localhost 5.10.157-ab10 #319 SMP PREEMPT Sat Nov 11 21:49:28 CST 2023 aarch64 Toybox I think it is possible to copy firmware image from ADB session. If someone did/have instructions please point here.

Monado's first stable of release of 2025 is here. From enhanced Android support and driver updates to improved runtime stability and tooling, Collabora's XR team delivered a wide array of improvements for the cross-platform, open source OpenXR runtime. View the full article

I found this I hope it helps you @Luiz-SP

Hello there, I recently gained remote access to a Banana Pi F3 to test it, and everything went smoothly. The board was running Bianbu Linux, and I was able to install and use Docker without issues. Now, I'm considering purchasing the board and was wondering if the Armbian image would also support running Docker. Do you have any insights on this? Thanks!

thanks

Have you tried installing qemu-user-static package manually and retry?

Tried a few hours later? Alternativly you can choose a fixed mirror from here: https://docs.armbian.com/Mirrors/

@Nick A oh your build for the Tanix TX6S worked perfectly for me already (thanks!) though I did notice some weird behaviour on my other box that's supposed to be identical to this one. stuff like armbian-config freezing when trying to format the eMMC mainly. I noticed a hang in the kernel in the dmesg when that happened so I suspect there might be some minor difference in the hardware that I'll look into later. for right now I've moved to a box with an amlogic s905y4, which is a whole other can of worms. I got debian-on-amlogic to boot so I'm hoping I can copy over the u-boot and dtb in other to get armbian working on it, since it has more features for SBCs. thanks for your help nick!

Hi everyone, I'm having trouble recovering my Android TV box T95 Max with the following specs: CPU: Allwinner H616 RAM: 4GB ROM: 32GB Board: AXP313A V3.0 The box was freezing after boot, so I tried to reflash the firmware using PhoenixCard / suit. What I’ve Tried So Far: Downloaded and flashed T95-H616-A27.img & T95-H616-A29.img through FEL mode and Flashing completed successfully but the box only shows a black screen on both HDMI and the small front panel screen. Tried other firmware images labeled for T95 Max H616 AXP313A Tried re-burning the SD using different cards and readers I found a working Armbian img that worked from SD card: https://github.com/NickAlilovic/build/releases/download/v20240716/Armbian-20240716-unofficial_24.5.0-trunk_Transpeed-8k618-t_bookworm_edge_6.7.12_xfce_desktop_Secure_Boot.img.tar.xz I want to restore the TV box to a working firmware (Android 10 or 12) if possible. And is there any method to revive bootloader if it's corrupted Any working image file would be a huge help. Board Image attached:

Hi, sorry to bother you again. I recently tried to use latest Armbian 25.2.2 Bookworm and unfortunately 10mbps mode is not working. I suppose there is a regression. @brentr May I kindly ask you to have a look again at this topic? Cheers

In this second article of a three-part series, I look at how Matt Godbolt uses modern C++ features to try to protect against misusing an API that deals with destructive state transition based on a talk he gave on making code easy to use and hard to misuse. View the full article

I don't know particular about this board so I can only give generic clues and hints how to help us helping you. What kind of dependencies you mean? There is uboot only. For variables and boot script check the contents of /boot Power loss is not an issue. Most that can happen is corrupted rootfs.

ok how i fix it? go next: sudo find /boot -type f -name '*cs0*dtbo' i see on next: rk356x-spi<BUS>-m<MUX>-cs<CS>-spidev.dtbo │ │ │ │ │ │ │ └─ номер Chip-Select (0 или 1) │ │ └─ «mux» — какие именно ноги вывели наружу (m0, m1…) │ └─ номер аппаратного SPI-контроллера (spi0…spi5) └─ серия SoC (rk3566 / rk3568 = rk356x, rk3588 …) next setup instruction: | Шаг | Команды (копируйте строка-в-строку) | Что должно получиться | | | ------------------------------------------------------- | -------------------------------------------------------------------------------------- | ------------------------------------------------ | ---------------------------------------- | | 1. Перейти в домашний каталог | `cd ~` | | | | 2. Создать исходник DTS | `nano rk356x-spi3-m0-cs1-spidev.dts` | вставьте текст снизу → **Ctrl-O, Enter, Ctrl-X** | | | 3. Скомпилировать в DTBO | `dtc -@ -I dts -O dtb -o rk356x-spi3-m0-cs1-spidev.dtbo rk356x-spi3-m0-cs1-spidev.dts` | файл *.dtbo* рядом | | | 4. Узнать каталог оверлеев | `export OVR=/boot/dtb/rockchip/overlay` | (у вас именно такой путь) | | | 5. Скопировать файл | `sudo cp rk356x-spi3-m0-cs1-spidev.dtbo $OVR/` | | | | 6. Проверить | \`ls \$OVR | grep cs1\` | увидите *rk356x-spi3-m0-cs1-spidev.dtbo* | | 7. Убедиться, что в `/boot/orangepiEnv.txt` есть строка | `overlays=spi3-m0-cs0-spidev spi3-m0-cs1-spidev` | если всё ок — дальше | | | 8. Перезагрузить | `sudo reboot` | | | | 9. После ребута | `ls /dev/spidev3.*` | **/dev/spidev3.0 /dev/spidev3.1** | | #6 can be ignored. at #2 next: rk356x-spi3-m0-cs1-spidev.dts <=== name code: /dts-v1/; /plugin/; / { compatible = "rockchip,rk3566"; fragment@0 { target = <&spi3>; __overlay__ { #address-cells = <1>; #size-cells = <0>; status = "okay"; spidev@1 { /* CS1 = регистр 1 */ compatible = "spidev"; reg = <1>; spi-max-frequency = <10000000>; }; }; }; }; sudo reboot after this: ls /dev/spidev3.* orangepi@orangepi3b:~$ ls /dev/spidev3.* /dev/spidev3.0 /dev/spidev3.1 make like

@deskwizard I don't know why I refer to OPi5Max, maybe I had other tab/topic open or so, but it is clear that it is about the OPi5. Now I have the ROCK5B, just cloned the Armbian Bookworm from ROCK3A but did not write SPI yet. Power up with fixed 12V in USB-C and from SD-card with Armbian rock5b vendor U-Boot. rootfs from NVMe, SATA overlay enabled for 3.5inch HDD. 5 audio cards: root@rock5b:~# aplay -l **** List of PLAYBACK Hardware Devices **** card 0: rockchiphdmi0 [rockchip-hdmi0], device 0: rockchip-hdmi0 i2s-hifi-0 [rockchip-hdmi0 i2s-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: rockchiphdmi1 [rockchip-hdmi1], device 0: rockchip-hdmi1 i2s-hifi-0 [rockchip-hdmi1 i2s-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: rockchipdp0 [rockchip-dp0], device 0: rockchip-dp0 spdif-hifi-0 [rockchip-dp0 spdif-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 4: rockchipes8316 [rockchip-es8316], device 0: dailink-multicodecs ES8316 HiFi-0 [dailink-multicodecs ES8316 HiFi-0] Subdevices: 0/1 Subdevice #0: subdevice #0 card3 (unlisted) is HDMI-input I think, but disabled all in KDE settings tray except the 3.5mm plug ('headphones'). No further settings or volume change, mpv playing an mp3 instantly. I will likely do/test with 6.15 edge, also maybe 6.12 current (and other U-Boots as well). But first several mechanical/cooling things to tweak, need to drill/cut a hole for the SATA connector in the cooling metal I think.