Search the Community

I have an OTT TV Box, model ABOX-A1 ( 1G + 8G, S905X ). Inside it looks very similar to NEXBOX A95X discussed at https://www.savagemessiahzine.com/forum/index.php?showtopic=770346 . It has an analog AV port, with a 3PEAK TPF632A audio line driver on the output. So, all the digital audio stuff is inside the S905X SOC, and maybe some GPIO switches mute of that analog output chip. I first booted Devmfc_Debian-Bookworm_6.1.57-meson64_Minimal-23.10.12.img.xz from https://github.com/devmfc/debian-on-amlogic and had sound on the analog output. (The later Devmfc_Debian-Bookworm_6.6.1-meson64_Minimal-23.11.09.img.xz did not work.) I used its aml-multiboot-setup.sh script to set up automatic boot from USB or SD if they're present, without needing to hold the button in the bottom of the AV port. Then I decided I'd rather run Armbian, and I got Armbian_23.11.1_Aml-s9xx-box_bookworm_current_6.1.63_minimal.img.xz running from a USB drive. (I couldn't run Armbian_23.11.1_Aml-s9xx-box_bookworm_current_6.1.63.img.xz and some others, but I'm not 100% sure that I didn't do something wrong that prevented them from running.) This works fine, except there are absolutely no audio devices, either for HDMI or analog audio. I saw that the kernel modules that seem needed were present, but they weren't loaded and loading them didn't help. I guess they only work if the device tree informs Linux about that hardware being present. Using grep gx-sound-card /boot/dtb/amlogic/*s905x* I see only meson-gxl-s905x-khadas-vim.dtb, meson-gxl-s905x-libretech-cc.dtb, and meson-gxl-s905x-libretech-cc-v2.dtb contain that. I had had tried meson-gxl-s905x-p212.dtb and meson-gxl-s905x-nexbox-a95x.dtb so far, and neither have sound. Then I found https://github.com/torvalds/linux/commit/7e01e14e9f75385910d1e42f97a5e98f36244967 "arm64: dts: meson: add audio playback to S905X-P212 dts". After applying that patch, rebuilding the .dtb, and rebooting, I got a sound device. I could play audio files, and that took the appropriate amount of time, as if audio was going somewhere, but there was no analog audio output. Then, changing some things via amixer got it to work. These changes must have persisted, because I shut down, removed power, and booted again, and analog audio worked without having to do anything. I am attaching the altered .dtb file, the .dts file with the patch applied, and amixer output showing the current configuration with working analog audio. If you don't get audio, you can diff your amixer output against that output and see what might need to be changed. If you want to build the .dtb file yourself, note that the dtc program cannot handle the C preprocessor include directives found in these files. So, you first need to run them through the C preprocessor, and then you need to run dtc on the preprocessed output. Use something like cpp -nostdinc -I include -I arch -undef -x assembler-with-cpp arch/arm64/boot/dts/amlogic/meson-gxl-s905x-p212.dts ~/p212.dtsp To obtain the source code, I simply used https://github.com/armbian/build to start a build of a minimal Armbian system, telling it I want to custom configure the kernel. Then when the kernel configuration menu came up, I killed that, knowing all the files I needed were present. s905x-p212_audio_fix.tar.xz

Hello Everyone, I'm an armbian user since 2020 and i'm having issues trying to run armbian on a custom TV box made from a company that sell iptv solutions for business. I've got this from one of the company manager as the device was failing HDMI and didn't want to bother themself with RMA, i've got few but really they trew out like 50 pcs. The device has a Amlogic s905x3 soc with 2gb Ram and 16gb memory. 1 usb 2.0 and 1 usb 3.0 otg, micro sd slot and many other component. wifi and bluetooth board and it's PoE. I know that S905X3 isn't supported very much but i've seen some posts from users succeding, so why don't try to let armbian run? Tested with this img: Armbian_24.2.0_amlogic_s905x3_jammy_5.15.141_server_2023.12.07.img.gz tried different dtb but nothing starts, i do believe the bootloader is locked and i can't find the old aml_autoscript.zip file to flash. it has the recovery button behind the AV and it works to boot on recovery only, and with TWRP i did a full backup of the system. Tried with terminal to "reboot update" but it stuck on boot logo. here some few details, if somebody is interested on giving me an hand i can disclose more details about the device. [ 4.808428] ro.boot.oem.key1=ATV00104319 [ 4.808436] ro.boot.build.expect.baseband=N/A [ 4.808442] ro.boot.selinux=permissive [ 4.808448] ro.boot.dtbo_idx=0 [ 4.808454] ro.boot.firstboot=0 [ 4.808463] ro.hdmi.set_menu_language=true [ 4.808470] ro.wifi.channels= [ 4.808477] ro.allow.mock.location=0 [ 4.808483] ro.build.expect.bootloader=01.01.180822.145544 [ 4.808895] ro.boot.hardware=amlogic [ 4.808905] ro.boot.bootloader=U-Boot [ 4.809083] ro.product.cpu.abi=armeabi-v7a [ 4.809089] ro.product.cpu.abilist=armeabi-v7a,armeabi [ 4.809139] ro.hardware=amlogic [ 4.809168] ro.bootloader=U-Boot [ 4.809730] ro.board.platform=franklin [ 4.810076] pm.dexopt.boot=verify [ 4.810085] pm.dexopt.ab-ota=speed-profile [ 4.810095] pm.dexopt.install=speed-profile [ 4.810101] pm.dexopt.bg-dexopt=speed-profile [ 4.810108] pm.dexopt.first-boot=quicken [ 4.810218] ro.adb.secure=0 [ 4.810231] ro.secure=1 [ 4.810300] sys.usb.config=mtp,adb [ 4.810309] sys.usb.configfs=1 [ 4.810495] sys.usb.ffs.ready=1 [ 4.811106] log.tag.stats_log=I ro.vendor.app.optimization=true [ 4.813516] ro.vendor.vndk.version=26.1.0 [ 4.813527] ro.vendor.product.cpu.abilist=armeabi-v7a,armeabi [ 4.813535] ro.vendor.product.cpu.abilist32=armeabi-v7a,armeabi [ 4.813542] ro.vendor.product.cpu.abilist64= Thanks

The guide was created in response to the outdated or non-functional nature of much of the software provided by armbian-config->Software->Softy, particularly for TV boxes. It is tailored for advanced users who are adept at using commands, prefer manual installation, and favor the convenience of copying and pasting commands rather than searching for them on the armbian forum. While detailed explanations of each command's function won't be provided, I will include source links for each section, enabling you to conduct your own research. In this guide, I am using the latest ubuntu-based Armbian build: Armbian_23.11.1_Aml-s9xx-box_jammy_current_6.1.63_xfce_desktop.img.xz. Table of Contents check dtb burn Armbian to SD card configure boot partition install Armbian on SD card flashing install-aml.sh script Amlogic USB Burning Tool Amlogic Burn Card Maker Tool SHORT PIN method Team Win Recovery Project software install docker install openWRT install pi-hole install portainer install RPi monitor install xfce install midori browser install full armbian firmware install USB LTE dongle backup SD card armbian commands android stock firmware check dtb Install Device Info HW and open the app In the "SYSTEM" tab, you can find the "dtb" information for your box. This information is crucial for configuring the boot partition correctly. Please keep a note of your "dtb" (device tree blob) information for future boot partition configuration. burn Armbian to SD card Mare sure to use good, reliable and fast SD card from SandDisk, class 10, A1 Choose between ubuntu (jammy) and debian (bookworm) and download .xz file compressed image from the official Armbian archive. For advanced linux users who want a clean server (not even includes armbian-config), the "minimal" variant is recommended. Download burning tool balenaEtcher or USBImager and burn the compressed image to your SD card. https://docs.armbian.com/User-Guide_Getting-Started/ configure boot partition Open extlinux/extlinux.conf and uncomment the correct dtb for your box. If you make a mistake here, you will fail to boot. Make sure only one line is uncommented (check your dtb, for s912 SoC its q200 or q201). Go back to armbi_boot partition, copy the correct u-boot file according to your SoC and rename it to u-boot.ext. If you dont know your SoC, boot into Android, install/open Device Info HW app and go to SOC tab. The app may need root access to read device specs. install Armbian on SD card To boot the system for the first time you have to use one from the following - sometimes only one way of doing this works! If your box is installed with libreElec/coreElec, then you can't boot into Armbian, because you have to flash stock Android firmware first. Toothpick method: disconnect the power supply, insert card/drive, push reset button and connect the power while holding the button. Wait until Armbian logo appears and release the button. Terminal method: boot to Android, insert SD card with Armbian, install Terminal Emulator app (either from Google Play or APKMirror), run it and type reboot update. Your box should reboot to Armbian. Update&Backup: somewhere in the Android interface, perhaps the applications folder, you will find a program called Update OR Update&Backup, open it if you have "Update" app pre-installed, insert SD card with Armbian, select "Local" and choose ZIP file (aml_autoscript.zip) from the SD card; select "Update" and your box should reboot to Armbian. Recovery method: boot into Android, insert card/thumb drive and choose Reboot to recovery. Your box should boot into Armbian. ADB method: enable ADB (Google it) and run the following command in a terminal window: adb reboot update Menu button method (works with very few devices): disconnect the power supply, insert card/drive, push menu button on your remote control and connect the power while holding the button. Wait until Armbian boot script appears and release the button. install-aml.sh script NOTE: This will overwrite the Android ROM on the eMMC flash and attempt to install Armbian on the internal eMMC storage. Before beginning, make sure you have a backup of the stock Android ROM in the event the installation fails or you want to revert back to Android in the future. Proceed at your own risk. You can copy the working Armbian environment from SD card to eMMC using the install-aml.sh script. This file does a physical copy of whole system to eMMC. You can install Armbian to eMMC by running the shell script in the /root directory. Run the following commands in a terminal window: sudo su cd /root/ sudo ./install-aml.sh Once the Armbian finishes copying to the eMMC, shutdown Armbian, unplug power from the box, remove the SD card from the box, power the box back on to boot from the eMMC storage, if everything worked as expected, Armbian should boot from the internal eMMC storage and no longer require the SD/microSD card. Amlogic USB Burning Tool If you have a box with an Amlogic processor and need to update its firmware, install a custom ROM, or unbrick the box, the Amlogic USB Burning Tool is the recommended solution. It provides an easy-to-use interface for flashing firmware onto Amlogic-based devices. To use the Amlogic USB Burning Tool, follow these steps: Download the Amlogic USB tool zip file and extract it to the PC. In the folder, you have the InstallDriver.exe. This will install the required drivers for Amlogic TV boxes. Download the firmware file compatible with your box. Launch the Amlogic USB Burning Tool, change language and click “File” > “Import Image” to load the firmware file. Connect your box to your PC using a USB cable, ensuring the box is in recovery mode (toothpick method) or bootloader mode. The tool should detect your box, and you can click the “Start” button to begin the flashing process. Wait for the process to complete, and your box will reboot with the new firmware installed. Amlogic Burn Card Maker Tool With this method you can recover the device from a brick if you have no way to connect it to a PC. In this tutorial, we will guide you on using the burn card maker tool to create a bootable SD card for reinstalling Android Stock Firmware (ROM) on your box. You just need the correct firmware (ROM) for your specific box. Download Burn_Card_Maker v2.0.2 (3.96 MB). Extract the archive and run Burn_Card_Maker.exe file to run the tool. Click on upper left chinese menu and choose second option, check ‘English Version’ and restart the application. Choose disk then ‘Choose your image files’ to open image and select your specific .img firmware for your box. Press ‘Make’ button and wait to finish. Now insert the micro SD card in your box and power on while holding the reset AV button. You will be able to enter into recovery and the firmware will be flashed automatically. When the TV BOX reboots, remove the micro SD Card, this step is very important, wait 4-5 minutes and the update will completed. If your device fails to boot, your last option is to use the SHORT PIN method. SHORT PIN method Follow the steps outlined in the guide Amlogic Burn Card Maker Tool. If pressing the AV reset button doesn't work, it is likely that your device is unresponsive or "dead". In this case, you can try shorting out the PINS. Please note that at this point, you have little to lose in terms of further damage to the device. The SHORT PIN method can be used when other recovery methods and the Amlogic USB Burning Tool are not responsive. Please note that this method should only be attempted by those who fully understand the risks involved in handling electronics and take full responsibility for any potential issues that may arise. Dismantle: to proceed with the SHORT PIN method, you will need to dismantle your device. Remove the rubber placeholders on the back of the device to reveal screws. Unscrew these screws and carefully separate the device. Be cautious when removing the top part of the device, as the WIFI antenna is usually attached to it. Removing it too quickly may cause damage to the WIFI cable. NAND flash: locate the NAND flash chip, which is where the operating system is stored. Look closely at the PINS on the chip, as they are quite small. Identify two pins that are next to each other, and using a screwdriver, short them out by making them touch each other. Recovery menu: ensure that your SD card is inserted with the firmware image using the Burn Card Maker tool. Have your power supply and HDMI cable ready to be inserted. Now, slowly try different combinations of the PINS while applying power to the device. Eventually, you will find a combination that initiates the hardware and communicates with the SD card. This will initiate the boot sequence, and you should see a recovery menu on the screen. From there, the installation of Android will begin. Essentially, shorting out these two PINS is similar to holding the AV reset button. Again: Before applying power, hold down the two PINS and then apply power. Repeat this process until you see results or something on the screen. Sometimes, the screen may flash green or red, indicating that you have found the correct PINS but have the wrong firmware. In this case, return to your PC and find a different firmware image specific to your SoC. If you are unable to find the original stock ROM for your box, it is possible that your box is a clone of another well-known box. In this case, find the firmware for the box that is most closely related to yours. You need to make your box boot once into recovery/update mode to reinstall firmware from SD card. The SHORT PIN method modifies normal boot procedure to make your box look for kernel and dtb on SD card before booting from internal memory. https://inv.vern.cc/watch?v=CUfKNNgxb9E Team Win Recovery Project TWRP, short for Team Win Recovery Project, is a community-driven project that provides a custom recovery solution for Android devices. It supports backups, restoration, and custom ROM installation. https://twrp.me/Devices/ install docker ubuntu Add the GPG key: curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add - Add repository to APT sources: sudo add-apt-repository "deb [arch=$(dpkg --print-architecture)] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable" apt-get update Install Docker: apt-get install docker-ce docker-ce-cli containerd.io Test the installation: docker --version Install Docker Compose: sudo curl -L "https://github.com/ubiquiti/docker-compose-aarch64/releases/download/1.22.0/docker-compose-Linux-aarch64" -o /usr/local/bin/docker-compose<br> sudo chmod +x /usr/local/bin/docker-compose Test Docker Compose installation: docker-compose --version debian apt-get remove docker docker-engine docker.io containerd runc apt-get install ca-certificates curl gnupg lsb-release mkdir -p /etc/apt/keyrings curl -fsSL https://download.docker.com/linux/debian/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg echo "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/debian $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null apt update apt-get install docker-ce docker-ce-cli containerd.io docker-compose-plugin If you would like to use Docker as a non-root user, you should now consider adding your user to the docker group with something like: sudo usermod -aG docker $USER https://docs.armbian.com/User-Guide_Advanced-Features/#how-to-run-docker install openWRT On the host system, the full armbian firmware should be installed so you can use it on AP mode: wget https://imola.armbian.com/apt/pool/main/a/armbian-firmware-full/armbian-firmware-full_21.08.6_all.deb sudo dpkg -i armbian-firmware-full_21.08.6_all.deb Make sure your USB WIFI adapter supports AP mode: iw list Set country regulations, for example, to Spain set: iw reg set ES Make sure you are not runing wpa_supplicant on your host machine or docker container will tell messages like wlan0: Could not connect to kernel driver. sudo systemctl stop wpa_supplicant sudo systemctl disable wpa_supplicant Install dependencies: sudo apt install iw iproute2 gettext dhcpcd5 Initial configuration is performed using a config file, openwrt.conf. You can use the included openwrt.conf.example as a baseline, which explains the values. At the very least you’ll need to change the values of LAN_PARENT and WIFI_IFACE. Commands to download the repo and configure openwrt.conf git clone https://github.com/oofnikj/docker-openwrt.git cd docker-openwrt cp openwrt.conf.example openwrt.conf nano openwrt.conf Build the image: make build Create the openwrt container: make run If you arrive at * Ready, point your browser to LAN_DOMAIN and you should be presented with the login page. The default login is root with the password set as ROOT_PW. Any settings you configured or additional packages you installed will persist until you run: make clean This will delete the container and all associated Docker networks so you can start fresh if you screw something up. Installing will create and enable a service pointing to wherever you cloned this directory and execute run.sh on boot. make install https://forum.openwrt.org/t/running-openwrt-in-a-docker-container/56049 https://badgateway.qc.to/contain-your-router/ https://github.com/oofnikj/docker-openwrt install pi-hole Start by creating a directory where you will store the configuration file for the Pi-Hole docker container: mkdir pihole cd pihole nano docker-compose.yml Enter the following lines: services: pihole: container_name: pihole image: pihole/pihole:latest ports: - "53:53/tcp" - "53:53/udp" - "67:67/udp" - "80:80/tcp" environment: TZ: 'Europe/Berlin' WEBPASSWORD: '1234' networks: internal: ipv4_address: 192.168.16.10 # Assign a static IP within your router's subnet volumes: - './etc-pihole:/etc/pihole' - './etc-dnsmasq.d:/etc/dnsmasq.d' cap_add: - NET_ADMIN restart: unless-stopped networks: openwrt-lan: ipv4_address: 192.168.16.10 # Assign a static IP within your LAN subnet networks: openwrt-lan: If you are using ubuntu to run the pi-hole docker container, you may need to disable the systemd-resolve service: systemctl disable systemd-resolved.service systemctl stop systemd-resolved Then, you can bring your pi-hole up: docker-compose up -d As we managed our own router firmware using OpenWrt, you need to tell your router to send pi-hole IP as DNS server to client. Go to Interfaces -> Lan -> DHCP Server -> Advanced Settings, inside DHCP-Options enter value: 6,192.168.16.10. Apply changes and restart the LAN interface. https://pimylifeup.com/pi-hole-docker/ https://firebog.net/ https://arstech.net/pi-hole-blocking-lists-2023/ https://avoidthehack.com/best-pihole-blocklists install portainer docker volume create portainer_data docker run -d -p 8000:8000 -p 9000:9000 --name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data --network=openwrt-lan portainer/portainer-ce install xfce sudo apt-get -y install xorg lightdm xfce4 tango-icon-theme gnome-icon-theme dbus-x11 sudo startxfce4 To disable the desktop environment and return to tty1 after installing xfce on Armbian, you can follow these steps: Press Ctrl + Alt + F1 to switch to tty1. Log in with your username and password. Stop the display manager service by running the following command: sudo service lightdm stop This will stop the graphical interface and return you to the command line interface. To prevent the display manager from starting automatically on boot, run the following command: sudo systemctl disable lightdm install midori browser sudo apt install midori install RPi monitor The RPi monitor on port 8888 can also be installed for AMLOGIC boxes with the following command: sudo armbianmonitor -r install full armbian firmware By default, the Armbian builds only include a limited set of firmwares out of the box. To address certain driver issues, you may need to install the complete Armbian firmware. There are two ways to do this: either through armbian-config -> software -> Full, or by manually installing the firmware via a USB device if you don't have internet connectivity on your box. To manually install the firmware, download it from the following link: https://imola.armbian.com/apt/pool/main/a/armbian-firmware-full/. Once downloaded, copy the firmware to your USB device. Then, insert the USB device into the Armbian box and navigate to your home folder. cd ~ Check device identifier of your USB device: lsblk Mount USB device at ./usbstick and install the package: mkdir usbstick sudo mount /dev/sdX1 ./usbstick cd usbstick dpkg --install armbian-firmware-full_*.deb Replace sdX1 with your device identifier. install USB LTE dongle Armbian has a default setting that treats USB LTE Dongles as mass storage devices. However, in order for the dongle to be recognized as an Ethernet device, it needs to be switched from mass storage mode to network mode. To achieve this, we will need to install and configure usb-modeswitch. sudo nano /etc/usb_modeswitch.conf Paste the following: # Huawei E353 (3.se) and others TargetVendor=0x12d1 TargetProductList="14db,14dc" HuaweiNewMode=1 NoDriverLoading=1 Install usb-modeswitch: sudo apt-get update sudo apt-get install usb-modeswitch Switch dongle to network mode: sudo usb_modeswitch -v 12d1 -p 1f01 -c /etc/usb_modeswitch.conf You can now check if mass storage is removed: lsusb https://askubuntu.com/questions/757638/can-not-connect-huawei-e3372-modem-on-ubuntu-15-10-please-help https://installati.one/install-usb-modeswitch-ubuntu-20-04/ armbian commands Configure system, network, timezone, language, hostname, keyboard, etc: armbian-config Check temperature of SoC: armbianmonitor -m Get boot logs for inspection and automatically upload it to an online pasteboard service: armbianmonitor -u backup SD card Identify the SD Card: First, you need to identify the device name of your SD card. You can use the lsblk or fdisk -l command to list all storage devices and identify the SD card. Backup with dd: Use the dd command to create a raw image of the SD card. Here's an example command: sudo dd if=/dev/sdX of=/path/to/backup.img bs=4M status=progress Replace /dev/sdX with the actual device name of your SD card and /path/to/backup.img with the desired backup location and filename. Restoring from Backup: To restore the backup to a new SD card, you can use either balenaEtcher or a similar command in reverse: sudo dd if=/path/to/backup.img of=/dev/sdX bs=4M status=progress android stock firmware x96 Tanix Ugoos Vontar Mecool

Hello community, I bought this TV box which happens to have fake specs, it seems it's really only 1GB RAM and 8GB of storage and comes with Android 7 instead of 12, however it has 2 USB ports and SD card reader, so I guess it could be flashed and repurposed for retro gaming or something like that. I think the SoC is Allwinner H3 (sun8iw7p1). It would be very much appreciated if someone could help me with these questions: 1) Where can I download or backup the stock firmware, yes the one with the fake specs? 2) Could it be flashed with some light version of Android TV or Google TV? 3) Can the memory be upgraded to 2 GB by replacing the RAM chips? Best regards

Hello, I would be grateful for some assistance on a sound issue. I installed Armbian_20.10_Arm-64_bullseye_current_5.9.0_desktop.img.xz on a YUNDOO Y6 TV Box with S905X. It worked fine, but I believe that there is no support for Armbian 20 anymore. Useful info, the sound was OK and the audio card was identified as GXL-S905X-P212. Then, I tried various versions of Armbian_23.11.1_Aml-s9xx-box_bookworm_current_6.1.63 and Armbian_23.11.1_Aml-s9xx-box_jammy_current_6.1.63. Most of them do work, but none detects the sound card. Now I am playing with Armbian_23.11.1_Aml-s9xx-box_bookworm_current_6.1.63_xfce_desktop.img, which actually has meson-gxl-s905x-p212.dtb in boot/dtb/amlogic. Yet, it cannot see the soundcard. No matter how I try, GXL-S905X-P212 is never shown as a connected device. I would appreciate any suggestion. However, please keep in mind that I am hardly an expert in Linux and have never tried Debian (only some variations of Ubuntu, and even that at beginner’s level).

I found a .dts file for my TV set-top box on an amlogic processor, and I want to compile this file for Armbian, please tell me how to do this, my TV box is K1 plus. https://github.com/CoreELEC/device-trees-amlogic/tree/master

Hello everyone, I recently acquired a Tigre 2 TV Box with the following hardware specifications: Amlogic S905X processor, 2GB of RAM, and 16GB NAND storage (SkHynix). I attempted to install the Armbian operating system, and the installation process started from a USB drive. Unfortunately, after the installation, the device seems to be bricked as it doesn't boot up (led red). I've read that it might be possible to recover a bricked device by putting it into MaskROM mode through a process involving a short circuit. However, I'm not entirely sure how to do this, and I'm hoping someone here can provide guidance or steps on how to put my Tigre 2 TV Box into MaskROM mode. Any help or advice would be greatly appreciated. Thank you in advance!

Hello everyone, I have a Tigre 2 TV BOX with Amlogic S905X, 1GB DDR3, and 16GB NAND storage. I'm interested in installing Armbian on this device, but there doesn't seem to be native support for the latest Armbian versions for NAND storage. I'm wondering if there is any way to install Armbian on this box, and if so, where I can find an Armbian version with a graphical interface and a Legacy Kernel 3.4.x that is compatible with Amlogic processors. I appreciate any help in this regard. Thank you in advance.

From an article at: https://torrentfreak.com/brazil-regulator-claims-80-of-pirate-tv-boxes-were-blocked-last-week-231030/ "Brazil's telecoms regulator Anatel claims that during an operation last week, it successfully blocked around 80% of pirate 'TV boxes' in the country. Estimates from early 2023 suggest that seven million were active in Brazil." Maybe they could be re-purposed to run Armbian /s What's your take on this?

Recently I've installed armbian on my 905 TV box using this article as a guide: https://i12bretro.github.io/tutorials/0269.html After some experiments with dtb files and tuning everything seems to work fine except of one thing: the box can't be turned off, it boots immediately after shutting down. I've found a similar problem described in several articles, for example: https://gist.github.com/george-hawkins/a897a6fe116093a4c1f29ad19df088de It is suggested to enable XHCI HCD quirks in grub. But there is not such file in the system I've installed, the closest thing I found was config-5.9.0-arm-64 file. What is the right way to modify it to add XHCI HCD quirks? Or maybe the suggested method doesn't suite for my system? Sorry if my question is dumb, I'm a total noob with Linux.

H96 Pro Plus android TV box stuck at 2%, Tried to re install many, but stuck on 2%, any clue from fellows.,.,regards H96 Pro Plus CZ-S32-V3 (DDR4) 2016-12-15(A15)

I tried to write different images from the h6 family, for example: Arabian_23.11.0_allwinner_tanix-tx6_bullseye_5.136_server_2023.10.20.img to my SD and USB drive, however, this does not work. If you install the SD card and turn it on, then the red LED lights up on the device and that's it. The device simply ignores the USB flash drive and loads android. What could be the problem?

Google has launched the new Chromecast with Google TV (HD) powered by an Amlogic S805X2 quad-core Cortex-A35 CPU that offers a cheaper alternative to the Chromecast with Google TV (4K) that is limited to 1080p60 resolution, instead of the 4Kp60 video output supported by the Amlogic S905X3 model. While the processor is slower, the system comes with less memory (1.5GB vs 2GB), and only supports 1080p60, it supports the more efficient AV1 video decoding and as well as A/B partitions for seamless updates since the firmware does not need to be downloaded to the internal storage before the Chromecast with Google TV (HD) specifications: SoC – Amlogic S805X2 quad-core Cortex-A35 processor with Mali-G31 MP2 GPU, 1080p60 H.265, H.264, VP9, AV1 video decoder System Memory – 1.5GB RAM Storage – 8GB eMMC flash with support for “virtual A/B updates with compression“ Video output – HDMI up to 1080p60 with HDR support [...] The post Chromecast with Google TV (HD) features Amlogic S805X2 CPU with AV1 video support appeared first on CNX Software - Embedded Systems News. View the full article

Hi. I'm out of my depth here, but I noticed that one of the official Armbian builds with platinum support is for the Khadas VIM1S, which has a S905Y4 SOC with 2GB of RAM. This is a similar configuration to many cheap Android TV boxes. According to some sources I can find, the S905W2 is also in the same family as the S905Y4 (Amlogic NE S4). Both are also supported by Coreelec, although I understand that Coreelec DTB's can't be used with Armbian. What would be involved in porting Armbian from the VIM1S to S905Y4/S905W2 TV boxes? Is this likely to work, and where could I start? Thanks!

Hello, I have two of those TV box Android Q+ tv box, which apparently has H616 CPU in it, and I am trying for literally two days to install armbian or some other linux on it (I want to repurpose them to something usefull). I tried with all the images for orangepi zero 2, tanix t96s/96, basically all the images that I could imagine and could find, that apparently should boot from SD card. My procedure is that I press button inside of AV port, with SD card inserted, and pluging power in whilist holding reset button, and it newer boots into any armbian or other distro that I tried. I saw few people here managed to install linux on it, but I ran out of ideas, if somebody can just direct me to correct image/procedure how to install it. I also followed this https://indomus-it.translate.goog/guide/come-installare-e-configurare-armbian-su-q-plus-q-smart-tv-box/?_x_tr_sl=auto&_x_tr_tl=en&_x_tr_hl=en-US&_x_tr_pto=wapp#boot, to no avail. Thank you!

Hi With a web search and in Kodi wiki I found only outdated info. Which ARM board with much better performance than Raspberry (I want 4K streaming) and good Linux support? Which is the flagship of 2023 for TV box? Installation and setup should be easy, like a x86 PC. I am not yet sure if I run LibreElec or armbian Thanks