Search the Community

Hi, First of all thank you very much for all the support and efforts you have taken to provide with the extensive documentation and images to flash on the android tv boxes. I am here in hope of some help and guidance, since ive not been able to solve this particular issue since past 2 months and with bare minimum sleep and enough efforts. I have a SDMC Tech STB which is DV8549 - Processor: Amlogic S905X2 - RAM: 2GB - EMMC: 8 / 32Gb (not sure but will share part number) - WiFi chip? Unsure since the part is rubbed off, and its not even necessary to run the wifi. It does not have the SD card slot unlike the normal TV Boxes. it seems to be locked? or rather would not go into any mode. it has a debug port, but it would not show any data apart from some wifi related things. in which if we keep pressing CTRL + C it will stop displaying that. There is some button given, unlike the TB Boxes, but that button upon pressing only takes into the recovery mode which leads to nothing but only would ask to Wipe Data and factory Reset, that is all. Just behind the EMMC Chip, there seems to be a Placment for a small Pushbutton which is not populated, but when we do short it, while plugging in the Power Supply, it would take the device in the WorldCup Mode. **What have i tried?** 1. Did put the device in worldcup mode and followed with a alot of files from Ricky Divjakovski, to try and flash some android images which were provided by other people online, but it would not do anything or would not lead to any flashing to the board. 2. Tried the Amlogic USB Burning tool, but even that would not lead to any of the flashing, did follow a lot of videos online but all the steps were made for the generic TV Boxes and none for my specific, but considering my electronics and embedded knowledge i tried my level best to do all the combinations to check if the usb burning tool would help to flash any rom it did not. So, both the standard ways which are meant to be used for the Generic TV Boxes are not available for me. The last step which im planning to do is, pull out the EMMC from the board, install it on the external EMMC Reader like the allSocket bga153/163 and copy all the files from the EMMC and erase it. but i have no idea after erasing, re-soldering the EMMC, where do i start and how do i install the armbian or any OS onto the board again? what do i expect from you or other users over here from the community? what should i do next? is there any way i can get this up and running? are there any steps i might be missing? Back of the board. Highlighted in RED is the button i would short and it would take me into the worldcup mode Highlighted in Blue is the button i would press, and it would take me to recovery. Front Of the Board from over here i was not able to attach any more photos to the post, so a humble request to follow up over here https://github.com/ophub/amlogic-s9xxx-armbian/issues/3214 for all the pictures. any help in regards to this shall be very very much amazing. thanks in advance.

Hello everyone! First of all, thanks for the useful thread. I'd like to know if you got the files for the SD card, Guillaume lopéré. And if installing this armbian I'd be able to use the tv box as a home server, deploying a Node.js project and using Docker. Best Regards, Gilliard

There should be a big difference in speed and powerconsumption; As I indicated in earlier post, edge kernel has no video encoding working, so at least is is SW encode. Debian/standard ffmpeg for aarch64 only had/has v4l2m2m, no dedicated RKMPP also no old OpenMAX rpi methods (in the past). I think this works for Qualcomm SoCs, but no others I am aware of. If you use RK35xx RKMPP I see almost 5x real-time speed for 1080p50 and low CPU load. See example below: root@rock5b:~# ffmpeg -hide_banner -codecs | grep -e h264_v4l2m2m -e h264_rkmpp DEV.LS h264 H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 (decoders: h264 h264_v4l2m2m h264_cuvid) (encoders: libx264 libx264rgb h264_nvenc h264_v4l2m2m h264_vaapi h264_vulkan) root@rock5b:~# /usr/share/jellyfin-ffmpeg/ffmpeg -hide_banner -codecs | grep -e h264_v4l2m2m -e h264_rkmpp DEV.LS h264 H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 (decoders: h264 h264_v4l2m2m h264_rkmpp h264_cuvid) (encoders: libx264 libx264rgb h264_nvenc h264_v4l2m2m h264_rkmpp) root@rock5b:~# /usr/share/jellyfin-ffmpeg/ffmpeg -y -hide_banner -c:v hevc_rkmpp -i /lan/record/2025-11-04-NPO-1.ts -map v -c:v h264_rkmpp -f mpegts /dev/null Input #0, mpegts, from '/lan/record/2025-11-04-NPO-1.ts': Duration: 06:59:01.58, start: 14798.887378, bitrate: 4058 kb/s Program 1 Metadata: service_name : NPO 1 service_provider: KPN Stream #0:0[0x1b63]: Video: hevc (Main) ([36][0][0][0] / 0x0024), yuv420p(tv, bt709), 1920x1080 [SAR 1:1 DAR 16:9], 50 fps, 50 tbr, 90k tbn Stream #0:1[0x1b64](dut): Audio: aac_latm (HE-AAC) ([17][0][0][0] / 0x0011), 48000 Hz, stereo, fltp Stream #0:2[0x1b69](dut): Audio: aac_latm (HE-AAC) ([17][0][0][0] / 0x0011), 48000 Hz, stereo, fltp (visual impaired) (descriptions) Stream #0:3[0x1b65](dut): Subtitle: dvb_teletext (libzvbi_teletextdec) ([6][0][0][0] / 0x0006), 492x250 No Program Stream #0:4[0x12]: Data: epg Stream mapping: Stream #0:0 -> #0:0 (hevc (hevc_rkmpp) -> h264 (h264_rkmpp)) Press [q] to stop, [?] for help Output #0, mpegts, to '/dev/null': Metadata: encoder : Lavf61.7.100 Stream #0:0: Video: h264 (High), nv12(tv, bt709, progressive), 1920x1080 [SAR 1:1 DAR 16:9], q=2-31, 2000 kb/s, 50 fps, 90k tbn Metadata: encoder : Lavc61.19.101 h264_rkmpp ^C[out#0/mpegts @ 0xaaaaea74fce0] Error writing trailer: Immediate exit requesteds speed=4.86x [out#0/mpegts @ 0xaaaaea74fce0] Error closing file: Immediate exit requested [out#0/mpegts @ 0xaaaaea74fce0] video:61287KiB audio:0KiB subtitle:0KiB other streams:0KiB global headers:0KiB muxing overhead: 6.096897% frame=12559 fps=244 q=25.0 Lsize= 65024KiB time=00:04:11.16 bitrate=2120.9kbits/s speed=4.87x ^C^CReceived > 3 system signals, hard exiting

I have a RK3228A TV Box which is able to properly boot armbian when flashed to its eMMC (no rknand) . However I don't use Armbian much often, probably a maximum of two to three times a month. I want to keep stock Android on eMMC, for video playback on the YouTube app is much faster compared to in firefox and Android has proper remote support which Armbian lacks. I tried flashing the armbian community image on the sdcard but the device didn't boot from sdcard unless the eMMC was wiped. I found that multitool is able to always boot from sdcard irrespective of whatever is in the emmc. After doing some research on the multitool build process, I think I need a properly configured idbloader, uboot and tee binary and then place them at proper offsets in the image, however the Armbian image already contains different data at those offsets. So, how can I build an Armbian image that can be booted from sdcard without wiping the eMMC ?

@Ducdanh Nguyen, if you mean usb<->uart converter, virtually anything with cmos/ttl 3.3v. i/o levels (5v. probably is fine too) will work. Based on ch340 or pl2303 or cp2101 or some FTDI chips - all they should work. But don't use usb<->rs232 converters or COM port directly. If you talking about soldering some sort of connector to tv box board, then I can't suggest anything, except some straight separate pin. This test points are just separate pads and they don't suit any of connectors I familiar with. IMO better way is to solder thin flexible wires (preferably in PTFE or silicone insulation) to the board, and then solder any kind of connector to them. You need uart connected only if you wish to interact by it means with tv box. Through uart you can interact with u-boot bootloader, inspect kernel output and have access to shell console with 'su' enabled. But, just to simply boot tv box, you don't need uart.

Hello, I have an X96q 2/16 TV Box. I installed the build "Armbian-unofficial_25.05.0-trunk_X96q-lpddr3-v1-3_bookworm_edge_6.12.11_server" on a 64GB microSD card, and everything is working fine. However, when I run armbian-install -m yes and select "Boot from eMMC — system on eMMC", I get the error: Error: Partition(s) on /dev/mmcblk2 are being used. Too many primary partitions. mount: /mnt/armbian-install.kYpi5v/rootfs: WARNING: source write-protected, mounted read-only. mount: /mnt/armbian-install.kYpi5v/bootfs: WARNING: source write-protected, mounted read-only. rm: невозможно удалить (Can't be deleted) '/mnt/armbian-install.kYpi5v/bootfs/bat': Файловая система доступна только для чтения (File system is read-only) rm: невозможно удалить '/mnt/armbian-install.kYpi5v/bootfs/bootlogo.bmp': Файловая система доступна только для чтения rm: невозможно удалить '/mnt/armbian-install.kYpi5v/bootfs/fastbootlogo.bmp': Файловая система доступна только для чтения rm: невозможно удалить '/mnt/armbian-install.kYpi5v/bootfs/font24.sft': Файловая система доступна только для чтения rm: невозможно удалить '/mnt/armbian-install.kYpi5v/bootfs/font32.sft': Файловая система доступна только для чтения rm: невозможно удалить '/mnt/armbian-install.kYpi5v/bootfs/magic.bin': Файловая система доступна только для чтения rm: невозможно удалить '/mnt/armbian-install.kYpi5v/rootfs/bat': Файловая система доступна только для чтения rm: невозможно удалить '/mnt/armbian-install.kYpi5v/rootfs/bootlogo.bmp': Файловая система доступна только для чтения rm: невозможно удалить '/mnt/armbian-install.kYpi5v/rootfs/fastbootlogo.bmp': Файловая система доступна только для чтения rm: невозможно удалить '/mnt/armbian-install.kYpi5v/rootfs/font24.sft': Файловая система доступна только для чтения rm: невозможно удалить '/mnt/armbian-install.kYpi5v/rootfs/font32.sft': Файловая система доступна только для чтения rm: невозможно удалить '/mnt/armbian-install.kYpi5v/rootfs/magic.bin': Файловая система доступна только для чтения Partition too small. Needed: 1896 Mb Available: 128 Mb. How can I fix this? Output of sudo lsblk: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS mmcblk2 179:0 0 14.6G 0 disk ├─mmcblk2p1 179:1 0 32M 0 part /mnt/armbian-install.38Slfn/bootfs │ /mnt/armbian-install.38Slfn/rootfs │ /mnt/armbian-install.3JZfHI/rootfs │ /mnt/armbian-install.Mqemrx/rootfs ├─mmcblk2p2 179:2 0 16M 0 part ├─mmcblk2p3 179:3 0 32M 0 part ├─mmcblk2p4 179:4 0 2G 0 part ├─mmcblk2p5 179:5 0 16M 0 part ├─mmcblk2p6 179:6 0 32M 0 part ├─mmcblk2p7 179:7 0 640M 0 part ├─mmcblk2p8 179:8 0 16M 0 part ├─mmcblk2p9 179:9 0 16M 0 part ├─mmcblk2p10 179:10 0 16M 0 part ├─mmcblk2p11 179:11 0 16M 0 part ├─mmcblk2p12 179:12 0 16M 0 part ├─mmcblk2p13 179:13 0 512K 0 part ├─mmcblk2p14 179:14 0 15.5M 0 part ├─mmcblk2p15 179:15 0 16M 0 part ├─mmcblk2p16 179:16 0 16M 0 part └─mmcblk2p17 179:17 0 11.7G 0 part mmcblk2boot0 179:32 0 4M 1 disk mmcblk2boot1 179:64 0 4M 1 disk mmcblk0 179:96 0 58.2G 0 disk └─mmcblk0p1 179:97 0 57.7G 0 part /var/log.hdd / zram0 254:0 0 986.1M 0 disk [SWAP] zram1 254:1 0 50M 0 disk /var/log zram2 254:2 0 0B 0 disk Output of sudo fdisk -l: Disk /dev/mmcblk2: 14.56 GiB, 15634268160 bytes, 30535680 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: AB6F3888-569A-4926-9668-80941DCB40BC Device Start End Sectors Size Type /dev/mmcblk2p1 73728 139263 65536 32M Microsoft basic data /dev/mmcblk2p2 139264 172031 32768 16M Microsoft basic data /dev/mmcblk2p3 172032 237567 65536 32M Microsoft basic data /dev/mmcblk2p4 237568 4431871 4194304 2G Microsoft basic data /dev/mmcblk2p5 4431872 4464639 32768 16M Microsoft basic data /dev/mmcblk2p6 4464640 4530175 65536 32M Microsoft basic data /dev/mmcblk2p7 4530176 5840895 1310720 640M Microsoft basic data /dev/mmcblk2p8 5840896 5873663 32768 16M Microsoft basic data /dev/mmcblk2p9 5873664 5906431 32768 16M Microsoft basic data /dev/mmcblk2p10 5906432 5939199 32768 16M Microsoft basic data /dev/mmcblk2p11 5939200 5971967 32768 16M Microsoft basic data /dev/mmcblk2p12 5971968 6004735 32768 16M Microsoft basic data /dev/mmcblk2p13 6004736 6005759 1024 512K Microsoft basic data /dev/mmcblk2p14 6005760 6037503 31744 15.5M Microsoft basic data /dev/mmcblk2p15 6037504 6070271 32768 16M Microsoft basic data /dev/mmcblk2p16 6070272 6103039 32768 16M Microsoft basic data /dev/mmcblk2p17 6103040 30535646 24432607 11.7G Microsoft basic data Output of (parted) print: Model: MMC R821MB (sd/mmc) Disk /dev/mmcblk2: 15.6GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 1 37.7MB 71.3MB 33.6MB fat16 bootloader msftdata 2 71.3MB 88.1MB 16.8MB env msftdata 3 88.1MB 122MB 33.6MB boot msftdata 4 122MB 2269MB 2147MB super msftdata 5 2269MB 2286MB 16.8MB misc msftdata 6 2286MB 2319MB 33.6MB recovery msftdata 7 2319MB 2991MB 671MB ext4 cache msftdata 8 2991MB 3007MB 16.8MB vbmeta msftdata 9 3007MB 3024MB 16.8MB vbmeta_system msftdata 10 3024MB 3041MB 16.8MB vbmeta_vendor msftdata 11 3041MB 3058MB 16.8MB ext4 metadata msftdata 12 3058MB 3074MB 16.8MB private msftdata 13 3074MB 3075MB 524kB frp msftdata 14 3075MB 3091MB 16.3MB empty msftdata 15 3091MB 3108MB 16.8MB media_data msftdata 16 3108MB 3125MB 16.8MB fat16 Reserve0 msftdata 17 3125MB 15.6GB 12.5GB f2fs UDISK msftdata Has anyone encountered this and knows how to fix it? Do I need to repartition the eMMC? If so, what is the safest way to do it without bricking the device? Any guidance would be greatly appreciated.

@leXia "no matter which image I use, it always boots into Android". Maybe it's not booting into FEL mode or it's not reading your SDcard. To enter FEL mode, power off the TV box, insert your SDcard, press and hold a hidden button (often inside the AV port, reachable with a toothpick) while connecting the power cable, release the button after a few seconds. If that doesn't work try another SDcard. Usually, if you box detects uboot and stops you'll just get a black screen. Without UART communication I can't really help. If it boots the kernel then you can check your SDcard for log files.

@Ducdanh Nguyen, about uart: just find someone with soldering skills - it's deal of 3 minutes to solder 3 wires. Screenshots: all them taken from one tv box. I've found recovery menu only once - when accidentally flashed update.zip with system and vendor partitions taken from other tv box (also HiSilicon-based). After flashing, something went wrong while starting Android, and box automatically rebooted to recovery.

@Sergey Lepeshkin i also note that the picture of the tv boxhttps://drive.google.com/drive/folders/1etPmH8ZG4UtPHI3Vf1U9MUHl5_gK_s-E are from diffrent boxes, but the reflash_from_backup.jpg is probalby mine. But i can't access the recovery menu, is there any way?

@Ducdanh Nguyen, I don't understand how you could use electrical (insulation?) tape to connect to test points... Nevertheless, all you need is a good electrical contact between wires and test points. Means has no matter. Beware: signal levels is 3.3V. Do not connect directly to RS232 interface! What about flashing my modified update.zip - don't worry. It doesn't alter partition table, bootloader and backup partition. If something goes wrong, or you just want original firmware back - just connect power while holding button near "A/V" jack. This will start reflashing using your original update.zip, located in backup partition. If you want to extract your original update.zip from backup partition, simplest way to do this is using uart. Connect uart to pc, boot tv box normally, open serial port on pc (115200/8/n/1), issue 'su' command, mount /backup and copy /backup/update.zip anywhere you want. About laptop - I don't understand, how it's related to this discussion... If you want to compile armbian using it - go ahead. It doesn't matter what cpu architecture or type of memory it uses. All you need is correct toolchain, which suits our tv box SoC.

Armbian Version: 6.12.56-current-rockchip64 TV Box: I have same board that is mentioned at this post. Issue: using the .dts mentioned in the above link I am able to see the clock with blinking separator. However I am not seeing the disk activity or LAN connections icon. If I am using devicetree changed to rk1188-box-led-conf-5, I can see the disk blinking icon and LAN connection, however the clock is not visible. Is there anyway I can get the clock as well the icons? Can you share the steps or the post that has the solution to this?

TV Box Status Information Template Version 1.0 TV Box Name (example: TX3 mini): T9 CPU (example: amlogic s905w): RK3328 Armbian build file name: Armbian_community_25.11.0-trunk.367_Rk3318-box_trixie_current_6.12.54_minimal.img DTB file used: rockchip/rk3318-box.dtb Kernel Version: 6.12.56-current-rockchip64 Distribution Installed (focal, buster, etc): trixie Working Ethernet (Yes/No):Yes Max Ethernet Speed that works (100/1000): 100 Max Does wifi work (Yes/No): Yes 2/5 Does bluetooth work (Yes/No): Yes Does HDMI audio work (Yes/No): Yes - after last update , (also analog and spdif ports are available - not tested). Additional Comments (provide any additional information you feel is important): IR Receiver yes 5 Digit display working: yes MASKROM PINS for recovery flashing available on the back side. SOC RK3328 RAM 4Gx4 D9PQL VFD DRIVER FD6551 WLAN CHIP SP6330 32 GB EMMc KLMBG2JENB VT RT9045 vfd.conf rk3318-t9.dtso Log android gpio T9.txt

the two tv box are quite different.The rk3318-H50 of this post is quite cheap, so are the component inside. By the way for the rk3318-H50: the PMIC is a DF1517, not an usual one. The Board has three leds (one red is power on always on the other two are both blu but I have never seen them on) and a 4 digit display plus (colon) usb, lan and wlan icons. Wifi works with the base configuration 2 and 5 ghz (although some warnings in the log). Bluetooth is recognized as well. I do not see any message related to the IR receiver. By the way it seems to be quite stable. This is the gpio list: android_tv_box_32:/ $ cat /sys/kernel/debug/gpio gpiochip0: GPIOs 0-31, parent: platform/pinctrl, gpio0: gpio-2 ( |vcc_otg_vbus ) out hi gpio-30 ( |vcc_sd ) out hi gpiochip1: GPIOs 32-63, parent: platform/pinctrl, gpio1: gpio-42 ( |bt_default_rts ) out lo gpio-50 ( |reset ) out hi gpio-53 ( |bt_default_poweron ) out hi gpio-56 ( |fd650_scl ) out hi gpio-57 ( |fd650_sda ) out hi gpio-58 ( |bt_default_wake_host) in hi gpiochip2: GPIOs 64-95, parent: platform/pinctrl, gpio2: gpio-81 ( |vcc_host_vbus ) out hi gpio-82 ( |power-led-ir ) out lo gpio-90 ( |power-led-normal ) out lo gpiochip3: GPIOs 96-127, parent: platform/pinctrl, gpio3: The T9 is an old and quite different TVBOX (cames in two flavours rk3318 and rk3328 from Sunwell) and everything is working "out of the box" - wifi, bluetooh, lan, hdmi, ir receiver. It has no leds but a 5 digit display + 6 icons but if you think it would be useful I can open it and peraphs describe it in a different post to avoid confusion. It seems to me that is more widespread as there are configuration files all around. Let me know if it is of ant interest.

I am in the process of installing Armbian on the X88pro13 TV box, which has the RK3528 CPU. https://github.com/joilg/x88pro wifi and ethernet are working

@jock, sorry for the confusion actually there are two boards (two different TV-BOX) one (here in this post) is an rk3318-H50 as you say T98... using FD650, the other one is rk3318-T9 (only T9) using FD655. All the dtso files posted are correct: for the H50 (T98) in this post you have the versions for the old kernel and the new one. Same in the other post "HELP WANTED" for the other TV BOX. At the end the two latest dtso are valid for the latest kernel. One of the difference between FD650 and FD655 is that the first one has 4 digits but 8 segments (0-7) on the contrary FD655 drives 5 digits and 7 segments (0..6). DTSO files are configured accordingly and fully working. Hope it clarifies.

I also happened to get an X88pro13 TV box on my desk. Since it promises good performance, I've been experimenting with getting Armbian running.. My first attempts look promising. Armbian-update and armbian-config are working. It could be a good platform for Smart-Home, Console and desktop Armbian is running well. _ _ _ __ __ _ _ _ /_\ _ _ _ __ | |__(_)__ _ _ _ ___ _ _ _ _ ___ / _|/ _(_)__(_)__ _| | / _ \| '_| ' \| '_ \ / _` | ' \___| || | ' \/ _ \ _| _| / _| / _` | | /_/ \_\_| |_|_|_|_.__/_\__,_|_||_| \_,_|_||_\___/_| |_| |_\__|_\__,_|_| v25.11 rolling for Hugsun X88pro running Armbian Linux 6.1.115-vendor-rk35xx Packages: Ubuntu stable (noble) Support: DIY (custom image) IPv4: (LAN) 192.168.178.71 (WAN) 130.185.10.185 Performance: Load: 82% Uptime: 0 min Local users: 3 Memory usage: 7% of 3.82G CPU temp: 41°C Usage of /: 10% of 58G RX today: 262 KiB Commands: Configuration : armbian-config Monitoring : htop HDMI output, LAN, Wi-Fi, and USB 2.0 are supported. Audio not tested yet. Bluetooth and USB 3.0 aren't working yet and require further investigation. IR remote control is also not working. I've shared my results and instructions for creating the image at: https://github.com/joilg/x88pro A ready-made image for an Armbian server with a console interface is available at: https://github.com/joilg/x88pro/tags A desktop version can also be easily created. Please try this version and let me know if you encounter any problems. johlnx

Hi , I am trying to configure orangepi to turn on and turn off tv. I installed and used cec-ctl to register the boad as playbac device. And then was able to put the TV on standby mode via sudo cec-ctl --device /dev/cec0 --standby --to 0 but not able to find how to turn ON the TV. Can someone please help. Thanks Manish

By some miracle of faith, yesterday at the last second before I gave up, I simply put Armbian_24.2.5_Rk322x-box_bookworm_current_6.6.22_minimal.img directly onto the SD card, and incredibly it loaded and I can use everything smoothly on the RK3229 (R329Q_V3.1), including running it on 5.0ghz Wi-Fi... but now the question is, can I put it on the NAND card? If it's not worth it, I'm thinking of leaving it on my SD card, then I'll buy other SD cards for my Raspberry Pi 1 b+ and another TV box I have (I haven't seen the card yet). I'm building a minilab. actually minilab(not working again) A computer with an AMD A4-4000 + 8GB RAM with Proxmox. A Raspy with Dietipi, Pihole, and Adguard. A TVBox-1 for observability (Grafana stack). A TVBox-2 to act as a redundancy node for TVBox-1 and a test server. Speaking directly, I took the image and ran the commands I saw on some postmarketos forums about recording directly via rkdev: rkdeveloptool wl 0x0 rockchip-rk322x-exemple.img

Found with google: https://forum.armbian.com/topic/34923-csc-armbian-for-rk322x-tv-box-boards/page/96/#findComment-218361

Okay, one step further: HDMI output is WORKING! initially I had the M1S connected to the Aux input of my AV receiver. There seems to be a problem with display detection (EDID, available modes) and so the M1S does not know which display mode to set. I then connected the M1S directly to an HDMI input of the TV and nothing changed. Rebooted and ... Surprise! Video output works, EDID information and available modes are available (wasn't when connected to AV receiver). So how can I tell Armbian to force a specific display mode even when no screen information is available?

my tv box: MXQ pro 4K 5G, Q44_V5.1_20210118, PROCESSOR: ALLWINNER TECH H3 LC267BA 91F2. I recorded the image on a 32gb sd card, but it doesn't boot. Has anyone solved it?

Seeking SKW (SWT6621 / EA6521) SDIO Wi-Fi driver source or Linux 6.x port Hi all, I’m running Nick's Armbian-unofficial_25.05.0-trunk_Tanix-tx6s-axp313_bookworm_edge_6.12.11_server.img.xz on a TV box that originally shipped with Android using kernel 5.15 AIDA64 run on Android gives: System Device Type: TV Manufacturer: Oranth Model: TX68 Brand: ADT-3 Board: exdroid Device: adt3 Hardware: sun50iw9p1 Platform: apollo Product: adt3 Installed RAM: 4 GB Total Memory: 3891 MB Available Memory: 2512 MB Internal Storage Total Space: 54.22 GB Internal Storage Free Space: 52.57 GB Bluetooth Version: 4+ Wi-Fi works perfectly under Android, but not under Armbian — the onboard Wi-Fi chip (connected over SDIO) is a SeekWave SWT6621, also known as SKW or EA6521. From the Android side, I can see the driver is provided in binary form via: /vendor/bin/hw/android.hardware.wifi-service-lazy /vendor/etc/init/init.wlan.common.rc /vendor/etc/firmware/SWT6621*_SDIO.bin and the kernel logs show active skw_scan and skw_dump_survey messages when Android is running. However, when booting Armbian, wlan0 never appears — only eth0 and virtual interfaces. This strongly suggests that the SKW SDIO driver needs to be rebuilt or ported for kernel 6.x. What I’m looking for: Has anyone already ported or rebuilt the SKW (SWT6621 / EA6521) SDIO driver for Linux 6.x / Armbian? If so, could you please share your source, patches, or build instructions? If the work is in progress, I’d be very happy to help or test — I have the Android image and full /vendor contents available for reference. Any leads on SeekWave source releases, OEM SDKs, or community ports would be greatly appreciated. Thanks in advance for any guidance — I’d rather reuse or help finish existing work than start from scratch if someone has already begun tackling this. Best Regards John

take note that these functions are done by other repos with specificity using the name Armbian, as an example ophub is (ab)using the name Armbian without permission and they do not contribute to the core development process. Rather they trick users into thinking they get support here and therefore (ab)using our resources. everyone in the community has this as the main feature of a TV box

@going Yes, git is a pain in ass. I think it's better to teach everyone the git commands. Maybe someone will learn from my instructions and contribute to the mainline Linux kernel and Armbian. Transpeed 8k618-t Tv box will always be supported because I learned how to use git commands and submit patches. I hope others will do the same. A lot of the patches are mainlined for h618. I don't think it will be too long before Armbian only needs a Transpeed 8k618 board config to build an image. But of course there's different variations of the same box. I hope this thread helps them because I won't be here forever.

@Hqnicolas Thanks for your response and apologies being so slow to reply busy IRL and then I forgot I used Google to sign up to this site.... yeah... Okay thanks - I thought it would just be a changing of timing so to speak on x86. In this case if I plan to develop for something I also go for the lowest variant of it, ofc, at this time both were Android. Rather code closer to the "metal" than bringing a whole web browser in to say "hello world" The images came from a link on this thread; either yourself or another member. Yeah I noticed a certain lag on the ethernet with 1GBit connection -- it has all the resources available yet it pings hard and downloads fluctuate. My plans for this Armbian is WiFi Repeater (router is broadcom and no Open- or DD-WRT alternative) to relay the signal. I don't want mesh, I don't need a TPLink account. The box will provide some services to Orange/Raspberry Pi systems. Right. I'm against AI So last thing I'd do. A link was provided but as I said expired. I'm sure there's differences in SDCard holders so didn't want to order two of the wrong type! Ah obrigado! I think your link may have solved it. I'll look in to it a bit in the future. Amazing how an Firestick turned me to Chinese TV boxes which are quite capable once you get rid of the Spyware. What I will say is, I think these boxes may have poor solder joints on the WiFi sub board, was hoping it was a misconfiguration my 8G model no longer recognizes the Wifi board, when I get the SD card holders I'll reflow it ad see. dmesg, lsusb, lspci know nothing of it. my 2G box the WiFi is fine. Regards