Search the Community

Inspired by the incredible work @jock and @ilmich have done to make the RK322x platform stable on mainline Linux, I decided to tackle the application side of things. My goal was to turn these "e-waste" TV boxes into fully functional, low-latency Android Auto head units for our cars. This fork of OpenAuto is built as one of my "Is it possible to turn this into that?" projects. It turned out to be one heck of a nightmare to pull off, but at the same time a lot of fun because I can see the potential of these TV Boxes as something you can actually put in your car and turn into a usable head unit! System Requirements Target Device: RK322x TV Box (e.g., MXQ Pro 4K). OS: Armbian Bookworm or Trixie (Kernel 6.1+ recommended). RAM: 1GB recommended. FFMPEG Installed: This build requires a specific build of ffmpeg that can be found here. Release: v2.0.0-alpha This release represents a major architectural overhaul. I have removed heavy dependencies (PulseAudio, QtAudio, GStreamer) in favor of a lean, direct-to-hardware pipeline using RtAudio (ALSA) and FFmpeg v4l2_request. Download: https://github.com/Harleythetech/openauto-rk3229-armbian/releases Technical Details Video Engine: Switched from GStreamer to a custom FFmpeg + V4L2-Request backend. Leverages the v4l2drmprime patch set for Zero-Copy rendering. Enables full hardware H.264 decoding on Rockchip stateless decoders. Result: Stable 1080p 60fps stream on a 1GB RAM device. Audio Overhaul: Replaced PulseAudio and QtAudio with RtAudio. This creates a direct, low-latency path to the ALSA hardware driver. Display: Targets linuxfb (Framebuffer) by default instead (eglfs and ffmpeg have issues when you run them together due to DRM master lock) Configuration This release requires a specific ALSA configuration to allow audio mixing (dmix) without PulseAudio. Create/Edit /etc/asound.conf: pcm.!default { type asym playback.pcm "dmix_hdmi" capture.pcm "plug_null" } ctl.!default { type hw card 0 } pcm.plug_null { type plug slave.pcm "null" } pcm.dmix_hdmi { type dmix ipc_key 1024 ipc_perm 0666 slave { pcm { type hw card 0 device 0 } format S16_LE rate 48000 channels 2 period_size 512 buffer_size 4096 } bindings { 0 0 1 1 } } Known Issues Invisible Cursor: The mouse cursor works but is currently invisible when the FFmpeg video backend is active (rendering layer order issue). Backend Fallback: In rare edge cases where DRM initialization fails, the app may incorrectly default to Qt software output. Probably more, i haven't tested it that much Development Status: Active & Seeking Contributors Currently, I am the sole maintainer focusing on the RK322x platform (specifically the RK3229). I am actively looking for developers interested in expanding support to other devices (such as RK3328, RK3399, or Allwinner H3/H6). If you have experience with C++, Qt, or V4L2/DRM and want to help turn these TV boxes into capable head units, contributions are highly welcome! Repository: https://github.com/Harleythetech/openauto-rk3229-armbian Credits: @jock and @ilmich for ffmpeg patches and the csc-armbian-for-rk322x-tv-box-boards opencardev for openauto and aasdk

This is required to use Armbian on the amlogic TV boxes. Enabling multiboot is one of the steps on the install instructions.

Have you used Armbian on other amlogic TV Boxes? I would never recommend using an amlogic TV Box as a mini pc. The graphical performance is poor. See the FAQ for TV boxes pined in this forum.

I put extra dtb files that I download on /boot/amlogic . For example I find that devmfc uses meson-sm1-ac2xx-generic.dtb on /boot/dtb/amlogic. So I copy it to Armbian boot partition on dtb/amlogic/meson-sm1-ac2xx-generic.dtb Then I edit extlinux/extlinux.conf label Armbian_community kernel /Image initrd /uInitrd fdt /dtb/amlogic/meson-sm1-ac2xx-generic.dtb append root=UUID=7dc5c0a3-acfc-4d51-a066-6c14d983a9de 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 I also test with other dtb files ad of course with the stock (default) image of Armbian just when donwload it, I use balenaetcher to write image on sd-card put it on a usb with sd-card reader and boot the tvbox, but doesn't work at all. The u-boot that I use is the u-boot-s905x3 that I copy to a directory and rename as u-boot.ext and then copy It to /boot. I oly try to run Armbian Systems from here → https://www.armbian.com/amlogic-s9xx-tv-box/ And I find devmfc when I search on google for " Debain s905x tv boxes" → thiss ystem works perfect, I only need to put on sd-card and put the sd-card on the usb with the sd-card reader and Tv Box shows HKSERIES and then go enter on the system devmfc. But I want some graphical friendly image to test the performance of tvbox as mini pc and because this I try to install xfce version of armbian. Thanks.

Hello - if someone get this type of TV Box from ebay (10€ ) - and dont have an GoogleAccount or do not want use the ADB way. The switch is located in one corner but not soldered. Use a small cable to put GND from end of arrow where the pointing of arrow in picture - to do the reset - (during restart just hold some seconds and device did start from SD-Card -) This device also features a RX/TX -Console and Jtag Interface - you find it if you take closer look.

The tv box has a fake specification (8 gb ram) ... But originally it should have less than 2 gigabytes of memory.

Hi, after reading the very entertaining thread regarding the BPI-W2 and the following opening of the bsp-kernel on github, I became curious and when prices dropped for the Lake-1-TV-Box, I decided to play around with it. Without very much documentation there was a bunch of trial and error and still many things are not absolutely clear to me, but finally I could boot an armbian build today: _ _ _ | | __ _| | _____ / | | | / _` | |/ / _ \ | | | |__| (_| | < __/ | | |_____\__,_|_|\_\___| |_| Welcome to ARMBIAN 5.68 user-built Ubuntu 18.04.1 LTS 4.9.119-rtd1295 System load: 1.49 0.74 0.31 Up time: 3 min Memory usage: 4 % of 1631MB IP: CPU temp: 46°C Usage of /: 11% of 7.2G [ General system configuration (beta): armbian-config ] New to Armbian? Check the documentation first: https://docs.armbian.com Thank you for choosing Armbian! Support: www.armbian.com This is still connected over the serial port and completely untested. I had to use the strange chained double-u-boot and load kernel and dtb manually (from raw sd card sectors), so it is not even close to alpha. But it seems, that this can be improved. I plan to make a repeatable build config, but do not expect some really usable stuff anytime soon. The situation with the lack of mainline support was already discussed in the other thread and the future does not look very bright here. This is more or less a personal playground at the moment. But if anyone is interested, you can leave comments or questions here. Sticky part (updated 03-03-2019): RTD1295-Devices: Tested: Lake 1 Home Cloud TV Box Untested: Beelink SEA 1, Zidoo X9s, Zidoo X8, Zidoo X10, Probox2 AVA, WD My Cloud Home, ... All development and tests thus far have been done on the Lake-1-TV-Box. It can not be ruled out, that the other boxes have other u-boot-versions/-configurations. Prerequisites: Mandatory: Serial connection soldered to the PCB (to reach the u-boot-shell) and a suitable terminal software. Further information here: https://en.opensuse.org/HCL:Lake1 (I can not confirm that „SD rescan“ does not work. Only „fatls“ and „fatload“ never worked for me, that’s why raw sector reads are used.) Recommended: Access to a Windows-PC, a USB-male-to-male-cable and the knowledge to re-flash the device by yourself. If you are not comfortable in doing this, DON’T DO IT!!! YOU CAN BRICK YOUR DEVICE FOREVER !! Current installation process (booting from SD-Card): Build a full-OS-image with armbian selecting „lake1“ from this fork: https://github.com/Staars/build. This will create an image with kernel image and dtb written to sectors before the root partition. The u-boot-build of armbian is not used. Write the image (using etcher) to an SD-card. For the moment we will not touch the eMMC of the target device and therefore will work as non-destructive as possible. This might change in the future and it should be no problem to implement a eMMC-only solution, but at the moment there is no solution in sight, that would let you dual-boot Android and Linux. Create a terminal connection to the serial pins of your target device and intercept the boot process immediately after power up to reach the first u-boot-shell. Now we have to edit the BOOTCMD the following way: env edit bootcmd sd read $kernel_loadaddr 800 954a; sd read $fdt_loadaddr a440 5d; env set bootargs earlycon=uart8250,mmio32,0x98007800 console=ttyS0,115200 noinitrd root=/dev/mmcblk0p1 rootfs=ext4 init=/sbin/init; b2ndbc; bootr env save This is a relatively harmless operation and can be reversed with the insertion of 'bootr' in step 2. The Android-installation on the eMMC stays untouched. 4. Now at every boot the device will initialize the SD (which can fail!!), load the image and dtb, change the bootargs and call the second u-boot, which then will (hopefully) boot the kernel. U-boot: At the moment u-boot will be build, but not used. Because of bootloader encryption this will likely stay that way. We can build the fsbl-parts, but without the proper encryption the boot stops, when the first part (hw_setting) is loaded. A separated u-boot-fork at https://github.com/Staars/u-boot-rtd is used for the armbian build, but that does not really matter. We must use the vendor-u-boot and we can not do real scripting (no RUN-command) but only chaining of commands. Kernel: The starting point from Sinovoip was labeled 4.9.119, but this is very likely not the whole story. Some parts are even newer and some are probably older, given the fact that git-cherry-picking showed possible updates when used with the stable linux-4.9-branch below tag:4.9.119. The additional phoenix drivers were partly integrated in the kernel-fork on https://github.com/Staars/linux-kernel-rtd/tree/latest_patched as an extra folder to keep them in one place. If there should be really an adoption of this platform in the future, it might be a good idea to go the other way around and merge the soc-specific parts into a generic linux-4.9.-fork. This is a bit of work, but it should be possible. The fork is currently patched to 4.9.174 New kernel fork started at https://github.com/Staars/linux-stable/tree/linux-4.19.y (not 4.20 because of LTS) and armbian build config updated. DTS/DTB: This is a minimal changed version for the banana-pi w2. Bluecore.audio: I do not really know if this (audio firmware?) is useful outside of Android. It is written to the SD-Image (directly behind the DTB), but not loaded. What works: -SATA-port (incl. booting with /root on SSD with bootarg 'root=/dev/sataa1') -WLAN (onboard 8821AU), but there are very short freezes every few seconds -simple software install (i.e. OMV) -reboot/restart works, but can take some time -bluetooth What does NOT work: -bluetooth -halt/restart Things to do: -waiting for someone, who confirms, that this is repeatable on other setups -working on the DTS/DTB -test Ethernet, USB -HDMI-in/-out or graphics in general (very low priority for me) -eMMC-only-install (must check first, where it is safe to write data) -test 4.19 (functional regression expected) Board_Pics:

There's no armbian community image available to this device, don't flash images from other users, you will need to build your images, for tv-box it's all at your own risk, build your armbian image by applying this custom files use this DTS

Issue booting Multitool on RK322x Box (Kingston eMCP) - Red IR Light Only Hi everyone, First of all, thank you for this incredible project. Bringing new life to these generic boxes is vital work. I am struggling to boot the Multitool on an "RPC Plus" TV Box. Here are my hardware specs and the steps I’ve taken so far: Hardware Specs: SoC: Rockchip RK3228A. Storage/RAM: 8GB Kingston eMCP (Chip ID: O8EMCP08-ELSCV100). SD Card: 16GB Lexar microSD (Class 10). Board LEDs: POWER, NET, and IR. Since the official download links for the Multitool are currently down (I get a 404 error idk why), I had to compile it myself on a Debian machine using the https://github.com/paolosabatino/armbian-build?tab=readme-ov-file repo and the ./create_image.sh rk322x script. I flashed the 500MB image to a 16GB Lexar card using BalenaEtcher and placed the Armbian minimal forky (6.18.7) image inside the /images folder (file name Armbian_community_26.2.0-trunk.357_Rk322x-box_forky_current_6.18.7_minimal.img.xz). The problem is that the box just won't boot from the SD card. When I hold the reset button and plug the power, the only thing I get is a static red light on the IR LED—no HDMI signal, no activity on the Power or Net LEDs, nothing. Android still boots fine if I pull the card out, so the hardware is okay, but it seems the boot process is hanging. I've tried both the reset and update buttons with different timings but no luck so far. I’m attaching pictures of the board and the chip. Any help to get this thing past the red light would be great. I'm putting the pictures of the board here in case it helps. Thanks! IMG_6826.HEIC IMG_6827.HEIC

Installed to the EMMC with armbian-install and no issues it all. Took about 10 minutes and now boots from the EMMC with no SD card inserted. I think I paid $35AU for this thing and it came with the remote, a bluetooth keyboard, HDMI cable and power supply. Absolute bargain when you compare it to the current price of Rasperry PI's especially when it comes with it's own case and internal storage. Thanks to everyone who contributed to getting these images out there, it's fantastic. I've also got the IR remote working. I followed rafman's post but this didn't fully work for me. It allowed the remote to work and I could see it was working with ir-keytable -t but the desktop and any open apps wouldn't respond to it. The solution was to copy the toml file to /etc/rc_keymaps/magcubic.toml then edit /etc/rc_maps.cfg and add the following to the bottom of the file * rc-empty <whatever_name>.toml * rc-empty magcubic.toml Adding the line to the rc.local file was not required. I've attached a picture of the remote and the toml file I created. I didn't map the buttons in the top right section as this remote has a learning function and you're supposed to learn the codes from your TV remote. But here are the codes my remote was using for these buttons by default. Power 0x1f1 Set 0x1f2 TVIN 0x1f3 VOL- 0x1f4 VOL+ 0x1f5 Edit: If you are going to use on media player apps you will probably want to edit the toml file and change "KEY_OK" to "KEY_SPACE". OK doesn't let you select things with the OK button but SPACE does. magcubic.toml

Version 3 Has been released! Complete UI Overhaul The entire user interface has been rebuilt from the ground up using Qt QML, delivering a modern automotive HMI experience optimized for touchscreen displays. New Home Screen - Large centered clock with configurable 12-hour/24-hour format - Gradient background (#00021A → #001D3F) - Swipe navigation to media player - Clean, minimal design with Readex Pro typography New Bottom Navigation Dock - 5-button dock: Home | Music | Android Auto | Volume | Settings - Always visible for quick access (except when running AA) - Icon-based navigation with visual feedback New Music Player - Album art display with track metadata - Playback controls (Previous, Play/Pause, Next) - Integrated with system media Redesigned Settings - Modern two-column layout with left sidebar navigation - 8 categories: General, Video, Audio, Input, Bluetooth, WiFi, System, About - Toggle switches, sliders, and radio buttons - Real-time system info (CPU temp, memory, frequency) - Live date/time display in header New Features - 12/24-Hour Time Toggle: Switch between time formats in Settings → General - Readex Pro Font: Variable weight font for consistent automotive typography - Modernized UI: The Original Crankshaft-NG was just not suitable for car use so i had to refresh it Technical Changes - Qt Widgets → QML Migration — Complete rewrite of UI layer - UIBackend Bridge — New C++ backend class exposing 50+ properties to QML - EGLFS Optimized — Designed for direct framebuffer rendering - No Animations — Instant transitions for 1GB RAM constraint - Centralized Theming — Theme.qml singleton for consistent styling Removed - GPIO settings (not applicable to TV Boxes) - DAC settings (using ALSA directly) - RTC settings (no CMOS battery, NTP only) - TSL2561 light sensor support (Pi-specific) - Camera module settings (Pi-specific) Bug Fixes - Fixed Cursor issue by utilizing Cursor plane (41, z-pos 2) - Fixed std::mutex missing include in RtAudioOutput - Fixed ColorOverlay import for Qt GraphicalEffects - Fixed time display showing 24hr with AM/PM suffix - Fixed buffer overflow warning in FFmpegDrmVideoOutput - Fixed QCursor conversion error in autoapp.cpp Known Issues: - Music player metadata not populated (requires media service integration, will be done in the next patch) - Volume popup not implemented (this require modifying the asound.conf before implementing) Issues? Open a ticket in https://github.com/Harleythetech/openauto-rk3229-armbian/issues Download https://github.com/Harleythetech/openauto-rk3229-armbian/releases/tag/oark322x-V3.0.0-alpha

I had X96 Mate from long time, which is 4GB/32GB with H616 CPU, (It is almost same as Tanix TS6s) Tried many images from orange pi for same chip, none worked perfectly. Found out Sunix Linux community got support for H616, but they don't build full OS images, After hell of searching found a repo from https://github.com/warpme/miniarch He hosts MiniArch SD card image which works on many devices, from same link got SD card image for Tanix tx6s which also worked on x96_Mate (both got H616) Here is the file I used - https://github.com/warpme/miniarch/releases/download/20230106-6.1.5-g78293cd3/MiniArch-20230106-6.1.5-board-h616.tanix_tx6s-SD-Image.img.xz 1- Wrote img to SD card using Etcher 2- Inserted SD card in Device 3- Powered ON the device and it Booted from SD card 4- followed update instructions on GitHub Repo. 5- Rebooted after all updates, 6- Basic Arch was ready to be used Here USB keyboard , LAN, HDMI worked normally. After reboot, logged in as root, and ran "start" command, Now here selected option 5, which is install EndeavourOS Process just ask you Yes/No questions, then you can select your DE, location etc. Automated script downloaded bunch of files and started its installation. Got the message that installation is done successfully and came back to terminal. Rebooted from terminal After this point got only blank screen , dont know it is still booting without HDMI or not So need to revert back to step -1 writing basic image to SD card. And this time sticking to terminal only. all this process is done on SD card only, and android on eMMC is safe .

If this is AW869A chip then it uses the AIC 8800 Linux Driver. My X98H TV box has a AIC8800 chip in it. https://linux-sunxi.org/Wifi#AW869A AW869A The AW869A is a highly integrated module with Dual band WiFi6 combination solution to support 1 × 1 IEEE 802.11b/g/n/ac/ax WLAN standards It uses the aic8800 firmware. A driver can be found at AIC 8800 Linux Driver. You'll need to compare the GPIO settings. Your Android dts uses HEX the mainline kernel is using DEC. https://www.rapidtables.com/convert/number/hex-to-decimal.html?x=12 rfkill { compatible = "allwinner,sunxi-rfkill"; status = "okay"; chip_en; power_en; pinctrl-0 = <0x63>; pinctrl-names = "default"; phandle = <0xcc>; wlan { compatible = "allwinner,sunxi-wlan"; clocks = <0x0e 0x04>; clock-names = "osc32k-out"; wlan_busnum = <0x01>; wlan_power; wlan_regon = <0x23 0x06 0x12 0x00>; wlan_hostwake = <0x23 0x06 0x0f 0x00>; wakeup-source; phandle = <0xcd>; }; bt { compatible = "allwinner,sunxi-bt"; clocks = <0x0e 0x04>; clock-names = "osc32k-out"; bt_power; bt_rst_n = <0x23 0x06 0x13 0x01>; phandle = <0xce>; }; }; btlpm { compatible = "allwinner,sunxi-btlpm"; status = "okay"; uart_index = <0x01>; bt_wake = <0x23 0x06 0x11 0x00>; bt_hostwake = <0x23 0x06 0x10 0x01>; wakeup-source; phandle = <0xd0>; }; Mainline dts: https://github.com/NickAlilovic/build/blob/666dc0fabd8a284ccf50d784f6bd0bf948dd073d/patch/kernel/archive/warpme-6.12/2001-arm64-dts-allwinner-h618-add-x98h.patch#L87-L95 https://github.com/NickAlilovic/build/blob/666dc0fabd8a284ccf50d784f6bd0bf948dd073d/patch/kernel/archive/warpme-6.12/2001-arm64-dts-allwinner-h618-add-x98h.patch#L182-L200 https://github.com/NickAlilovic/build/blob/666dc0fabd8a284ccf50d784f6bd0bf948dd073d/patch/kernel/archive/warpme-6.12/2001-arm64-dts-allwinner-h618-add-x98h.patch#L278-L297 The specific values <0x23 0x06 0x12 0x00> generally map to: 0x23: The controller or bank ID: pinctrl@300b000 { phandle = <0x23>; 0x06: The specific GPIO pin number: In Allwinner's pinctrl driver, banks are 32 pins wide. The formula is: (Bank_Letter_Index * 32) + Pin_Number 1. The Bank Index Map Bank Index PA 0 PB 1 PC 2 PD 3 PE 4 PF 5 PG 6 PH 7 PI 8 0x12: The active-high/low flags or drive strength. In the 3-cell GPIO format used by Allwinner (sunxi), the third cell (e.g., 0x12) is a bitmask that defines the electrical properties of the pin. To decode 0x12 (which is binary 0001 0010), you break it down into bits: 1. Bitmask Breakdown for 0x12 Bit 0 (0x01): Active Polarity. 0 = Active High. 1 = Active Low (Our bit 0 is 0, so this is Active High). Bit 1 (0x02): Open Drain / Open Source. 0 = Push-Pull. 1 = Single-ended/Open-Drain (Our bit 1 is 1, so this is Open-Drain). Bit 4 (0x10): Internal Pull-up. 0 = No pull-up. 1 = Pull-up Enabled (Our bit 4 is 1, so this is Pull-up Enabled). Summary of 0x12: This pin is configured as Active High, with an Open-Drain output and an internal Pull-up resistor enabled. 0x00: Reserved or additional configuration. In Allwinner-based systems (like the H6 or H616), this value is defined in the GPIO controller's device tree binding documentation within the Linux kernel source code. The structure is documented in the kernel under Documentation/devicetree/bindings/pinctrl/allwinner,sun4i-a10-pinctrl.yaml

If you can get termux app to run in android, you may be able to dump the dtb, which may give you clues as to the compatability of the chip. I have issues with some tv boxes with termux versions, but there are older versions available if the current one in playstore won't load or just doesn't work. su -c 'dd if=/sys/firmware/fdt of=<USB_PATH>/device.dtb' or simply su -c 'cp /sys/firmware/fdt <USB_PATH>/device.dtb' [Change USB_PATH as required, of course] The path /sys/firmware/fdt is correct for accessing the in-memory DTB on most running Linux/Android systems. The link http://nskhuman.ru/allwinner/krugh618.php?np=3 refers to what looks like your box or similar: "The board contains a microcircuit with the designation HK5236F - this is a hybrid microcircuit, its possible analogue is AW869A manufactured by Allwinner. AW869A is a dual-band WiFi6, BT5.2 highly integrated module, supporting WLAN 1*1 IEEE 802.11a/b/g/n/ac/ax and BT 5.2 standard, can realize WLAN/BT, has low power consumption" The links after that text give more info....

This is a great thread. I've had a magcubic android 12 box I've been using for a while just to watch things off a USB when we stay at hotels. It looks like the one in this video but the chip ID's are different. Mine seems to be running with Samsung memory, the clock chip? is FD650 instead of FD6551 and the wifi chip is labelled as HK5236F. Most hotel TV's don't support modern video codecs so this has worked ok. But I want to look at accessing my NAS remotely and this box is a bit of a dud if you want to install your own apps. Play store doesn't work, aurora store doesn't work. Tried sideloading Tailscale and it just crashes. While doing some research I noticed it also seems to be sold under the Vontar brand so I flashed @Nick A "Armbian-unofficial_25.05.0-trunk_Vontar-h618_bookworm_edge_6.12.11_xfce_desktop.img" to an SD card and it booted up. Happy days. It appears to have ethernet but I have not plugged it in yet. No wifi though. I just have 2 questions. 1. Is there any way this can be made to boot from internal storage or do I need to keep the SD card in if I want to run Armbian on it? 2. Is there a driver available for this wifi chip and do I need to mess around updating the boot image or can I just run a command for it? I'm not a regular linux user but I've got a bit of experience messing around. I don't currently have an environment setup to build my own image but I've played around with WSL before so I could probably set something up. Thanks for everyone that has contributed to this. It's good to make use of these boxes considering how cheap they are.

That isn't what you use for amlogic tv boxes. Follow the instructions linked from the download page: https://www.armbian.com/amlogic-s9xx-tv-box

Hello everyone! I have TV box MX10 based on RK3328. It freezes on the manufacturer's label on boot. So I need to update the firmware. I followed the instructions from 1st post but didn't get success. When I run "Erase eMMC" it change modal windows with messages very fast and at the end shows "Successfully done". The same when I run "Write new image". It shows immediately that it is flashed. I have run the shell and checked `dmesg` and found there errors like "group start error -110, status 0x0". What does it mean? Then I installed "rkdeveloptool" and followed steps from this thread: - ld - I see TV box in Loader mode - rd 3 - switch to Maskrom mode - dd loader.bin - done - wl 0x0 armbian.img - done - rd - toexit when I run tv box I got the same freeze on logo and that's all Is eMMC died? or?

Hi there this is not an x96 but a 'Q10 android TV' the mb looks the same as x96 i have tried some miniarch and your armbians versions (thanks for sharing) but nothing works, anyone can identificate if this mb is compatible ? There is no information about this exact model since it looks very recent. thanks in advance

@shexplorer I did something similar to a tv box i had around, not this model. Generally, the cpu comes with some sort of uboot. Written in firmware not emmc. The catch is that that uboot usually writes its persistent environment on the eMMC. And most of the time its not even a file on a partition, like in (and this is an example) between bytes 2000 to 8000 of the mmc. This uboot is only visible via serial console. no hdmi output. (and its quite old) This uboot then attempts to chainload the mmc or usb uboot. And its at this phase you get image. So on my setup, i had CPU uboot but no environment (because i smashed it with my armbian image...), and that environment was needed to boot both mmc or usb. Using a serial port (and pressing control +c ) i was able to instruct uboot it to boot armbian on the usb drive. And i mean manually with command like fatload 0x1000000 usb0.1 linux.img. But every time i reloaded would go back to the endless loop. So the next step was to find a stock image of my device and dump it into the emmc, via usb booted linux. (i actually only copied like the 1st 10MB, only needed uboot env, not the chinese android) Please know that this is not the image you download from any manufacturer website, those are snap-in upgrades that only change part of the emmc, you need a image that someone extracted with dd command from the entire mmc. After that i swore to never touch that emmc again... Maybe this is your problem too Get a serial connected to your device and check if you can see the cpu level uboot. If it is the same issue, maybe someone here can give you the 1st 10MB of their device, if you create a new thread asking for it. Edited to place the "e" on emmc. tnx johlnx for the fix

@kingbecher This is now off topic for this thread, but you need to look at: https://www.armbian.com/amlogic-s9xx-tv-box

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.

You should have followed the install instructions on the download page: https://www.armbian.com/amlogic-s9xx-tv-box Given where you are now, you need to find an original android image, flash that to return the board to a clean state, and then follow those instructions. The amlogic s9xx TV box builds use the android bootloader to bootstrap the boot process which at this point you have overwritten part of.

I've spent the last couple of months playing around (low-end testing just to see what the software and I are capable of) with Debian and docker: RSS, Nextcloud, navidrome, immich, nothing earth-shattering. I was doing this in a VM so I could wipe and restart in case of failure/learning curve issues, which was great. Everybody's got to have a hobby, right? After much foibles, I had gotten the setup into something I liked and understood the pratfalls to expect in installation. Ready for primetime, I didn't want to leave this in the VM (I have constant paranoia about usage on my power-sucking desktop), but I have a T95 Max plus TV box sitting around doing nothing but Kodi and it's on all the time, so I started dreaming about how I could get a version of Linux on it and do all my docker homelab junk and kodi and maybe make a diy NAS out of the thing. Armbian to the rescue! I grabbed the wrong image (I got the barebones CLI only version instead of something with a graphic interface that I figured would be easier to manage) and I was able to boot off the sdcard and was able to install docker and portainer and had a working web interface, so...great...for a first try. I then installed it to the emmc and managed to get xfce4 for a desktop interface so I can see what I'm doing. The CLI version didn't really match any of the tutorials I was reading (there are suggestions that I could change the desktop with arnbian-config, but that's either false or was published for an early version and weeded out in later version, iDK). Anywho, after mixing and matching instruction from amlgoic s905x3 and s905 versions, I have a working armbian with an xfce4 interface with working sound, USB, wireless and Ethernet. I was warned that all of those peripherals may or may not work in this endeavour, but I am happy to say they all work after I did a bunch of updates and upgrades of the armbian. Docker is going and the containers are all going and after 2x installs, I have a working Kodi going, so I am delighted and amazed. Now I have a couple of smallish problems. Honestly they are minor, but I have succeeded so far and I'm full of false bravado so I an hoping I can Gert some insight or suggestions: First, when I write the armbian to the emmc, the sdcard stopped working, period. Armbian refuses to see it as a device and I can't boot off it using the toothpick reset method. I've also tried using the amlogic flash utility with a male-to-male usb cable and my PC won't see it either, which tells me the sdcard interface is bunged, either the kernel can't see it or does not have drivers. Either way, if I have future problems I have to trash the whole setup because I am incapable of reflashing the box. Plus, the box is only 32gb and I was hoping to use the sdcard as storage, but I guess not. I've also thought of adding a USB card reader and seeing if I can get the box to see an sdcard through that, but I don't have a lot of faith there if it's a driver issue. Second, the xfce interface asks for my username and password every boot but my mouse and keyboard take a minute to kick in. It's annoying to me to be waving a mouse around and thinking the system has locked up, when it's really just taking some time to activate the USB. What would be attractive to me is that I bypass the login screen,but I can't find the spot in arnbian-config that allows me to set an automatic login (again, the tutorial I'm reading may be old, but the options just aren't there in my version). Sigh. So my questions to the geniuses and gurus out there: Has anyone had the same problem with the sdcard and/or were able to fix it and how, and How can I set an automatic login through terminal? The interface I have really doesn't have any real system settings like peripherals to show and won't let me adjust anything anyways.

I bricked my original H96MAX TV box while tinkering with it, so I bought a new one. The new unit works fine with both wireless and wired networks on Android, but after flashing the firmware Armbian_26.2.0-trunk.302_H96-tvbox-3566_forky_current_6.18.6_minimal.img, the wired network stops working and only the wireless network is functional. Please help me fix this issue, thank you!

If you mean the built-in script as described in the instructions linked to from the download page (https://www.armbian.com/amlogic-s9xx-tv-box) Then yes that should do everything you need.