Search the Community

@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.

Hello. I have easily managed to get armbian up and running of a usb stick, in fact everything worked perfect (hdmi, wifi, gbit ethernet, etc.). The tv box is h96-air-gbit (as the dtb is named), amlogic s905x3 soc, 32gb mmc, 4gb RAM, gigabit ethernet, 2xusb 2.0, 1xusb 3.0, sd card, hdmi, av port (reset button inside), spdif. The thing is, I wanted to benefit from the 32gb internal mmc storage, since I was running armbian from a 8gb usb stick (had a lot of those hanging around, and didn't want to buy a bigger one). I did notice the image I used had not armbian-install script, nor nand-sata-install. I did a manual install (snapshot copy) of my current system with the help of Claude.ai 1. step - create an setup another partition on the emmc (currently there were 2x 4M partitions - the bootloader I presume) sudo fdisk /dev/mmcblk1 sudo mkfs.ext4 -L ARMBIAN_ROOT /dev/mmcblk1p1 Note: Doing this seems enough reasonable to me (well, to my limited knowledge), no overwriting should have happened 2. step - snapshot copy the OS sudo mkdir -p /mnt/emmc sudo mount /dev/mmcblk1p1 /mnt/emmc sudo rsync -aAXv --exclude={"/dev/*","/proc/*","/sys/*","/tmp/*","/run/*","/mnt/*","/media/*","/lost+found"} / /mnt/emmc/ Note: This also seems alright, and the commands exited with no errors 3. step - update the extlinux.conf, the cmdline to point to the right UUID - the one from the emmc sudo blkid /dev/mmcblk1p1 sudo nano /mnt/emmc/boot/extlinux/extlinux.conf 4. step - just confirm everything is set, and shutdown, disconnect power and reconnect cat /mnt/emmc/boot/extlinux/extlinux.conf sync sudo umount /mnt/emmc Note: Everything seemed fine and correct. So after the whole process, I shut it down, removed the usb and booted. It didn't come online after a while, so I rebooted with hdmi connected (I did face some issues before, like unusally slow boot times in headless mode). It just never turned on. The logo was gone, so I figured something went quite wrong. Currently, the situation is the following: I reopened the board to connect uart for diagnostics. So The board without external storage (usb, sd card) doesn't boot, it does a certain sequence, but fails and just hangs (no reboot loop). If I have an external usb, the one which worked before (correct setup), it reboots in loop - it does try to boot from the usb, but fails. Chatgpt suggests that I probably overwrote some portions of the bootloader or firmware files on which armbian relied (some or most of the env vars are probably gone). Claude has a similar suggestion (FDT_BAD_MAGIC, get partition table from dts faild - the bootloader is messed up). I did try booting from usb and from sd - forcing multi boot (reset button), but that's definitely not the issue. The bootloader seems to be working up to a certain point - but booting from usb or sd produce the same error - last few lines of the log, right before the reboot (and it reboots indefinitely in loop): Device: SDIO Port B Manufacturer ID: fe OEM: 3456 Name: ASTCTran Speed: 50000000 Rd Block Len: 512 SD version 3.0 High Capacity: Yes Capacity: 7.3 GiB mmc clock: 40000000 Bus Width: 4-bit Device: SDIO Port B Manufacturer ID: fe OEM: 3456 Name: ASTCTran Speed: 50000000 Rd Block Len: 512 SD version 3.0 High Capacity: Yes Capacity: 7.3 GiB mmc clock: 40000000 Bus Width: 4-bit reading aml_autoscript 800 bytes read in 11 ms (70.3 KiB/s) ## Executing script at 01080000 ## Error: "bootfromsd" not defined get partition info failed !! reboot use default mode: normal bl31 reboot reason: 0xd bl31 reboot reason: 0x1 system cmd 1. Since, the aml_autoscript should definitely be working, the bootloader is the most probable issue. So, what Claude suggests is to flash s905x3 compatible u-boot. I managed to get the board in usb burn mode by mask rom (toothpick reset method didn't work). Currently I have the board plugged to pc (usb male to male) and uart connected (improvised RP2040 zero uart bridge). Please provide me with instructions and what to do. I soft bricked the board by following plausible instructions from ai, I don't want to hard brick it (I really liked it:) Also, I keep the board connected, since I don't know if I could reintroduce mask rom mode if turned off. Here is the complete log of one of the infinite reboots from the loop: SM1:BL:511f6b:81ca2f;FEAT:A0F83180:20282000;POC:F;RCY:0; EMMC:0; READ:0;0.0;CHK:0; bl2_stage_init 0x01 bl2_stage_init 0x81 hw id: 0x0001 - pwm id 0x00 bl2_stage_init 0xc0 bl2_stage_init 0x02 L0:00000000 L1:00000703 L2:00008067 L3:15000020 S1:00000000 B2:20282000 B1:a0f83180 TE: 146487 BL2 Built : 15:21:48, Aug 28 2019. g12a g1bf2b53 - luan.yuan@droid15-sz Board ID = 1 Set cpu clk to 24M Set clk81 to 24M Use GP1_pll as DSU clk. DSU clk: 1200 Mhz CPU clk: 1200 MHz Set clk81 to 166.6M fw parse done Load ddrfw from eMMC, src: 0x00060200, des: 0xf ffd0000, size: 0x0000c000, part: 0 Load ddrfw from eMMC, src: 0x00038200, des: 0xfffd0000, size: 0x00004000, part: 0 PIE I prepare done fastboot data load 00000000 emmc switch 1 ok ddr saved addr:00016000 Load ddr parameter from eMMC, src: 0x02c00000, des: 0xfffd0000, size: 0x00001000, part: 0 00000000 emmc switch 0 ok fastboot data verify verify result: 265 Cfg max: 5, cur: 1. Board id: 255. Force loop cfg DDR4 probe ddr clk to 912MHz Load ddrfw from eMMC, src: 0x00 014200, des: 0xfffd0000, size: 0x0000c000, part: 0 dmc_version 0001 Check phy result INFO : End of initialization INFO : End of read enable training INFO : End of fi ne write leveling INFO : ERROR : Training has failed! 1D training failed Cfg max: 5, cur: 2. Board id: 255. Force loop cfg DDR3 probe ddr clk to 792MHz Load ddrfw from eMMC, src: 0x0002c2 00, des: 0xfffd0000, size: 0x0000c000, part: 0 dmc_version 0001 Check phy result INFO : End of initialization INFO : End of read enable training INFO : End of fine wr ite leveling INFO : End of read dq deskew training INFO : End of MPR read delay center optimization INFO : End of Write leveling coarse delay INFO : End of write delay center optimization INFO : End of read delay center optimization INFO : End of max read latency training INFO : Td BL3X from eMMC, src: 0x00078200, des: 0x01768000, size: 0x000c8000, part: 0 BL33 CHK: 0xfffffff1 ADDR 01 7a1970 Load FIP HDR from eMMC, src: 0x00010200, des: 0x01700000, size: 0x00004000, part: 1 00000000 emmc switch 1 ok Load BL3X from eMMC, src: 0x00078200, des: 0x01768000, size: 0x000c8000, part: 1 bl2z: ptr: 05129330, size: 00001e40 0.0;M3 C HK:0;cm4_sp_mode 0 MVN_1=0x00000000 MVN_2=0x00000000 [Image: g12a_v1.1.3390-6ac5299 2019-09-26 14:09:46 luan.yuan@droid15-sz] OPS=0x10 ring efuse init 2b 0c 10 00 01 07 0e 00 00 0f 32 34 50 4d 50 50 [0.933 001 Inits done] secure task start! high task start! low task start! run into bl31 NOTICE: BL31: v1.3(release):4fc40b1 NOTICE: B L31: Built : 15:57:33, May 22 2019 NOTICE: BL31: G12A normal boot! NOTICE: BL31: BL33 decompress pass ERROR: Error initializing runtime service opteed_fast U-Boot 2015.01 (Jun 1 9 2020 - 20:04:27) DRAM: 3.8 GiBspi_post_bind(spifc): req_seq = 0 register usb cfg[0][1] = 00000000d7f3ec90 NAND: get_sys_clk_rate_mtd() 290, clock setting 200! NAND device id: 0 ff ff ff ff ff No NAND device found!!! nand init failed: -6 get_sys_clk_rate_mtd() 290, clock setting 200! NAND device id: 0 ff ff ff ff ff No NAND device found! !! nand init failed: -6 MMC: aml_privemmc/sd response timeout, cmd8, status=0x1ff2800 emmc/sd response timeout, cmd55, status=0x1ff2800 co-phase 0x3, tx-dly 0, clock 400000 co-phase 0x3, tx-dly 0, clock 40000000 aml_sd_retry_refix[983]:delay = 0x0,gadjust =0x162000 [mmc_startup] mmc refix success init_part() 282: PART_TYPE_DOS [mmc_init] mmc init success Amlogic multi-dtb tool Cannot find legal dtb! start dts,buffer=00000000d3e53620,dt_addr=00000000d3e53620 check_valid_dts: FDT_ERR_BADMAGIC get_partition_from_dts() 91: ret -9 get_partition_from_dts() 94: ret -9 get_ptbl_from_dtb()-272: get partition table from dts faild mmc_device_init()-1254: get partition table from dtb failed get_ptbl_rsv()-494: magic faild MPT, mmc_device_init()-1281: dtb&rsv are not exisIn: serial Out: s_verify_dtb_checksum()-3477: calc 0, store 0 update_dtb_info()-3585: cpy 1 is not val id _verify_dtb_checksum()-3477: calc 0, store 0 update_dtb_info()-3585: cpy 0 is not valid dtb_read()-3694: total valid _verify_dtb_checksum()-3477: calc 0, store 0 update_dtb _info()-3585: cpy 1 is not valid _verify_dtb_checksum()-3477: calc 0, store 0 update_dtb_info()-3585: cpy 0 is not valid dtb_read()-3694: total valid 0 emmc - EMMC sub system Usa ge: emmc dtb_read addr size emmc dtb_write addr size emmc erase dtb emmc erase key emmc fastboot_read addr size emmc fastboot_write addr size vpu: vpu_power_on vpu:[K M]Error:f[keymanage_dts_get_key_device]L100:/unify not parsed yet! [KM]Error:f[_get_km_ops_by_name]L248:key eth_exphy_para not know device 4 [KM]Error:f[key_unify_read]L312:key[eth_ exphy_para] no cfg in dts dwmac.f f3f0000 Waiting for PHY auto negotiation to complete. . . . done The Bes t Window is index 44 [KM]Error:f[keymanage_dts_get_key_device]L100:/unify not parsed yet! [KM]Error:f[_get_km_ops_by_name]L248:key eth_exphy_para not know device 4 [KM]E rror:f[key_unify_write]L279:key[eth_exphy_para] no cfg in dts libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <a ddress>" command. Aborting! dwmac.ff3f0000[KM]Error:f[keymanage_ta: erase the area which is uboot or data store erase partition <partition_name>: erase the area whi ch partition in u-boot store erase dtb store erase key store disprotect key store rom_protect on/off store scrub off|partition size scrub the area from offset and size store dtb i read/read/write addr <size> read/write dtb, size is optional store key read/write ad= 0 info->crc32 = 0 Magic is incorrect. boot-info is invalid. Resetting. save boo t-info info->magic = info->version_major = 1 info->version_minor = 0 info->slots[0].priority = 15 info->slots[0].tries_remaining = 7 info->slots[0].successful_boot = 0 info->slots[1].priority = 14 info->slots[1].tries_remaining = 7 info->slots[1].successful_boot = 0 info->crcion in u-boot store erase dtb store erase key store disprotect key st ore rom_protect on/off store scrub off|partition size scrub the area from offset and size store dtb iread/read/write addr <size> read /write dtb, size is optional store key read/write addr <size> read/write key, size is optional store ddr_parameter read/write addr <size> read/write ddr parameter[KM]Error:f[keymanage_dedid preferred_mode is <NULL>[0] hdr mode is 0 dv mode is ver:0 len: 0 hdr10+ mode is 0 [OSD]check dts: FDT_ERR_BADMAGIC, load default fb_addr parameters [OSD]set initrd_high: 0x3d800000 [OSD]fb_addr for logo: 0x3d800000 [OSD]check dts: FDT_ERR_BADMAGIC, load default fb_addr parameters [OSD]fb_addr for logo: 0x3d800000 [OSD]VPP_OFIFO_SIZE:0xfff01fff [CANVAS]canvas init [CANVAS]addr=0x3d800000 width=3840, height=2160 Cannot find dev. amot store erase dtb store erase key store disprotect key store rom_protect on/off store scrub off|partition size scrub the area from offset and size store dtb iread/read/write addr <size> read/write dtb, size is optional store key read/write addr <size> read/write key, size is optional store ddr_parameter read/write addr <size> read/write ddr parameter, size is o[KM]Error:f[keymanage_dnel error SARADC channel(2) is 0x3ff. saradc - saradc sub-system Usage: saradc saradc open <channel> - open a SARADC channel saradc close - close the SARADC saradc getval - get the value in current channel saradc test - test the SARADC by channel-7 saradc get_in_range <min> <max> - return 0 if current value in the range of current channel Command: bcb uboot-command Start ron_name>: erase the area which partition in u-boot store erase dtb store erase key store disprotect key store rom_protect on/off store scrub off|partition size scrub the area from offset and size store dtb iread/read/write addr <size> read/write dtb, size is optional store key read/write addr <size> read/write key, size is optional store ddr_parameter read/writeuboot-command Hit Enter or space or Ctrl+C key to stop autoboot -- : 0 Unknown command 'ddr_auto_fast_boot_check' - try 'help' pll tsensor avg: 0x1e95, u_efuse: 0x807a temp1: 25 ddr tsensor avg: 0x1eaf, u_efuse: 0x8076 temp2: 26 device cool done CONFIG_SYSTEM_AS_ROOT: systemroot system_mode: 1 Start read misc partition datas! Cannot find dev. amlmmc cmd <NULL> failed store - STORE sub-system Usage: store init flag store read name addr off|partition size read 'size' bytes starting at offset 'off' to/from memory address 'addr', skipping bad blocks. store write name addr off|partitiote addr <size> read/write key, size is optional store ddr_parameter read/write addr <size> read/write ddr parameter, size is optional store mbr addr update mbr/partition table by dtb [burnup]Err:store_read_ops,L84:cmd failed, ret=1, [store read misc 0xd3e4d090 0x0 0x820] failed to store read misc. info->magic = info->version_majosful_boot = 0 info->crc32 = -1075449479 Cannot find dev. amlmmc cmd <NULL> failed store - STORE sub-system Usage: store init flag store read name addr off|partition size read 'size' bytes starting at offset 'off' to/from memory address 'addr', skipping bad blocks. store write name addr off|partition size write 'size' bytes starting at offset 'off' to/frarameter read/write addr <size> read/write ddr parameter, size is optional store mbr addr update mbr/partition table by dtb [burnup]Err:store_write_ops,L148:cmd [store write misc 0xd3e4d090 0x0 0x820] failed active slot = 0 CONFIG_AVB2: null active_slot: normal Cannot find dev. amlmmc cmd <NULL> failed store - STORE sub-system Usage: store init flag store r on/off store scrub off|partition size scrub the area from offset and size store dtb iread/read/write addr <size> read/write dtb, size is optional store key read/write addr <size> read/write key, size is optional store ddr_parameter read/write addr <size> read/write ddr parameter, size is optional store mbr addr update mbr/partition table by dtb [burnup]Err:stornoSof sof timeout, reset usb phy tuning card in co-phase 0x2, tx-dly 0, clock 400000 co-phase 0x2, tx-dly 0, clock 400000 co-phase 0x2, tx-dly 0, clock 400000 co-phase 0x2, tx-dly 0, clock 400000 co-phase 0x2, tx-dly 0, clock 40000000 aml_sd_retry_refix[983]:delay = 0x0,gadjust =0x162000 [mmc_startup] mmc refix success init_part() 282: PART_TYPE_DOS [mmc_init] mmc init success Device: SDIO Port B Manufacturer ID: fe OEM: 3456 Name: ASTCTran Speed: 50000000 Rd Block Len: 512 SD version 3.0 High Capacity: Yes Capacity: 7.3 GiB mmc clock: 40000000 Bus Width: 4-bit Device: SDIO Port B Manufacturer ID: fe OEM: 3456 Name: ASTCTran Speed: 50000000 Rd Block Len: 512 SD version 3.0 High Capacity: Yes Capacity: 7.3 GiB mmc clock: 40000000 Bus Width: 4-bit reading aml_autoscript 800 bytes read in 11 ms (70.3 KiB/s) ## Executing script at 01080000 ## Error: "bootfromsd" not defined get partition info failed !! reboot use default mode: normal bl31 reboot reason: 0xd bl31 reboot reason: 0x1 system cmd 1.

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.

you might try to write (after gunzip) this u-boot boot-amlogic_gxl_a95x-r2-atf-aarch64.dd.gz from https://github.com/hexdump0815/u-boot-misc/releases/tag/250629-01 which i built some time ago via "dd if=boot-amlogic_gxl_a95x-r2-atf-aarch64.dd of=/dev/your-sd-card bs=512 seek=1 skip=1" to the sd-card to which you wrote the armbian image before and see if it boots (never tested it with armbian) - build instructions for that u-boot are here: https://github.com/hexdump0815/u-boot-misc/blob/wip-v2025-04/readme.gxl ... alternatively you might try to boot this (non armbian) image to see if that u-boot works at all on your device: https://github.com/velvet-os/imagebuilder-testimages/releases/download/autumn-release-2025-testimages/aarch64_mbr_uefi-aarch64-trixie-251016.img.gz (please keep in mind that anything around that image is not related to armbian and thus should not be discussed here as i do not want to hijack this armbian thread) @SteeMan - in case you are interested in getting some of this into armbian, maybe have a look at it and i can try to answer potential questions around it - this was just some experiment to boot amlogic via the u-boot uefi implementation and grub which worked out quite well - as a result an amlogic tv box feels a bit like a pc with a normal grub boot on the screen ... should be possible to make that work for many of the supported amlogic socs - i simply do not have the time to look further into this right now ...

So.... I am the winner of a Inovato Quadra4K from a drawing at my amateur radio club meeting. Yeah! Cool! It runs a software called HamClock automagically.... BUT WAIT! There is MORE! You can exit that app and run other applications... Providing you have a mouse & keyboard (because I am a native WinWeenie) or keyboard if you are a Linux forever personage. It also has a wireless interface that I would like to configure so it doesn't have to have an Ethernet tail tied to a port on our ISP router. I would rather it was mounted to a HDMI TV or monitor. So, I need the keyboard (and because I am a longtime WinWeenie and rodent dependent) mouse to reconfigure it. I would like to have it use a USB Logitech Unifier Nano dongle with wireless keyboard/mouse. By the way, the brilliant man that came up with this computer is trudging the same path I am, fighting cancer. His fight has gotten so tough he has shut down his company. I hope he gets better. Is there already a compiled binary for this with directions,,. or do I have to master the dark arts of programming routines, subroutines, interrupts, memory fetches, writes, threads and all that then compile it into something the machine understands? Please understand I didn't even take typing in high school, so college was a real bear.... When I was in high school Jobs and Wozniak were still dumpster diving behind Xerox-Park Corporation and Radio Shack. Any takers on this one? Thanks in advance, Dave, The-Other-One

Hey there forum! I've got this MXQ PRO 5G TV Box (Yes, I know It's been said the brand isn't important, but I figured I might as well say it anyways) thing a few days ago and, as you do, my first instinct was 'Let's linux it', which Is, as It turns out far more trouble than I had initially imagined. And frankly I am a little tired of slamming my head into a brick wall, repeating the same steps again and again so as a sort of last resort, I'm here to ask for your help (thanks in advance). To check which image to download and what steps to follow I've opened the box to take a peek at It's board. As the main CPU, RK3228A, for the storage 128GB of eMMC, and for the memory 8GB of RAM (which exactly type, I can't discover). Following the instructions on the first page of this topic, I downloaded an image, downloaded multitool, got my SD card. At first everything went according to the guide. Multitool flashed, the thing booted It and the partition expanded, then I shut it down and put the extracted .img into the 'images' folder, plug the card back in boot, flash, shut down once more and upon trying to boot, the LED stays off and doesn't turn on. After waiting for a solid 10 minutes I decide I'll just try booting it directly off the card. I flash It, plug it in and some images booted partially and some didn't. Some boot only to a certain point like starting a specific service (usually it got stuck after or during starting armbian-ramlog.service) and some just don't boot at all. I've tried disabling the services by manipulating the files on the card yet they just reappear again. After that I noticed that upon each boot there's a quick 'error' that happens, returning different numbers seemingly depending on the image on the card, either Internal error: Oops: 805 [#1] SMP ARM, or Oops: 80000005 SMP ARM or just Oops 5 which as far as I could find meant something related to illegal instructions (specifically interrupts). I haven't really made any progress past that. Also, If It's of any help, I can provide images of the board (from both sides) and all of It's components. Thanks in advance for all your help, friends!

Hi, how are you? Well, I don't know English very well, so this text will be translated using Google Translate since I'm Brazilian. Anyway. I found a way to boot the SD card with Linux on the Allwinner H3 chip, using a Chinese MXQ 4K 5G TV box. I booted Android normally and, using the remote control, pressed the power button and then confirmed. After shutting down, I booted with the remote control and Linux started normally. After that, every time I booted with the SD card, it booted perfectly. Another thing I did before, but I believe it doesn't affect this, was to enable USB0 device mode in developer mode. I hope this information helps with your Linux projects!

@jockNow, I've finally solved this problem. Successfully flashed the latest version of armbian, https://github.com/armbian/community/releases/download/26.2.0-trunk.151/Armbian_community_26.2.0-trunk.151_Rk3318-box_noble_current_6.12.63_gnome_ desktop.img.xz Next, I will share my problem-solving journey. I found that I couldn't enter maskrom/loader mode anyway, and when I accidentally inserted the USB flash drive into the multitool.img into the TV box and powered it directly on, I found that it actually started the system directly in the USB flash drive. So I guess that it may have changed the boot order after flashing the loader.bin before, and the armbian system I flashed in before it continued to toss before it could be configured, probably because the system files of the root partition were corrupted, causing it to not boot normally. Therefore, I simply tried to flash the firmware of the rk3188-box in the official community directly into the USB flash drive, because after these images are flashed into the USB flash drive, there is only the root partition, that is, the system. And there is no boot partition. I guess the boot partition may have been written somewhere else, and I don't need to worry about it anymore. So, I plugged the USB flash drive into the latest rk3318 firmware into the box and waited for a few minutes after powering on it directly and starting it, it obtained the IP address assigned by my router DHCP, I was so excited, I quickly connected to the rk3318-box through SSH, and made the preliminary configuration. Quickly enter the command armbian-install and select item 2, and immediately write the system on the USB flash drive to emmc. After the writing is completed, turn it off, unplug the USB flash drive, power on, wait for a few minutes, and the startup is successful. It means that I have successfully flashed the phone this time. Thank you very much for your help. @jockand @fabiobassa, You're passionate and highly skilled.

Hello everyone, I hope I'm in the right place. So I got an H50 tv box (T98) that I found lying around, and installed via the multitool everything including armbian itself, which works properly. The issue that I have is that I had to do all via ssh and haven't been able to get any HDMI output, tried updating lightdm, switching it to sleek, and at this point idk what else to do. Thank you in advance!

I've never used any other method. I'd suggest using a search engine to search for other methods to "enable multi boot on amlogic TV box"

https://forum.armbian.com/topic/26978-csc-armbian-for-rk3318rk3328-tv-box-boards/page/66/#findComment-231768 Thanks your help,jock. I hava a try to use the rkdevtool to install armbian. I just choose the iamge in url https://github.com/armbian/community/releases/download/26.2.0-trunk.151/Armbian_community_26.2.0-trunk.151_Rk3318-box_trixie_current_6.12.63_minimal.img.xz. But,there catch a error message in the tool. I don't known is this image is error or other reason?

Excuse me,jock. My TV-Box is the H96Max rk3318 4+64G.The box was installed Ubuntu 24.04,kenel 4.4，desktop vension by the seller。But now, i want to install the armbian system in the box.There are some problem for me that i have no HDMI-wire and no usb-keyboard,just only an usb-A to usb-A data-wire and a notepad computer。i think that i can't use the multitool.img to help me install the armbian. So, can you give me some help to install the armbian by USB-A to USB-A data-wire?I through some search some article to know maybe the RKdevtool can help me，but the tool need the loader.bin to flash the image. I don't know where is the loader.bin for rk3318.can you help me?

Hi guys, I try to install Armbian on my Amlogix G11pro (S509X2 based) TV Gamebox. It keeps booting only into my Emuelec SD card, if I plug it or with anyhting else it only boots into Android that is on eMMC. I understood that I have to use the toothpic method to press the reset button to get into the recovery mode. I tried this but failed as my toothpic didnt reach anything I could click, it just went through. so I opened the box and found that behind the audio jack there is nothing (see attached pic). there is empty space with three connectors on the board, maybe that is the place where usually the micro switch for the reset button sits, but I am not sure. Before I try to short these (why three connectors?), I would be like to have a bit more info, in order not to brick my board. The FAQ says to use the toothpic method is only one method of several, what are the other ones ? BR retro123

I am trying to install armbian on my Xiaomi mi tv box 3 I got the image on a flash drive it's a 16 gig USB 3 stick I got the files ready also but I don't know why it freezes when i enter the recovery screen and click on reboot to boatloader so If any on can help me fix this problem or start again that would be really useful thx

Hi, First of all, sorry for lengthy post and that I ask a lot of things at once, I am very new to linux and this would be my first real experience. I am trying to set up home automation and home assistant server. As I am just getting started to learn all the ropes, I thought about what could be used for sečrver and I remembered that I have an old T9 android TV box see the attachement, I read through this thread and tried to follow the instructions throughout the posts. I burned the armbian image to sd card, which insterted into the sd slot on the T9 board, however I am unable to get the board to boot from the sd card. The box boots normally into android, when no SD card is insterted. When the card is inserted, nothing happens and the box does not turn on at all. It may be a big ask, but would someone be able and willing to help me find out the next possible steps? I feel a bit overwhemed as I am not very knowledgable in this field and unsure how to follow the instructions, or better said, I am not sure if I am following the instructions right. Thank you!

Have you followed the information available on the download page? https://www.armbian.com/amlogic-s9xx-tv-box

Hello everyone, I have three Amlogic S905x TV boxes with a dead EMMC, and one with a desoldered EMMC (since I thought without it, they would boot from the microSD card). Is there a way to force them to boot into Armbian? Holding the power button doesn't work, and desoldering the EMMC didn't help either. I was able to boot Armbian using UART. A workaround is to use Ardruino, which sends commands to boot Armbian after a while, but that's a workaround, and I'd like a more elegant solution. 1) Download the *.img.gz image for the amlogic_s905x 2) Write the image to the microSD card using Rufus. 3) Connect the UART. Steps 2-6 in the brick instructions. 4) Insert the microSD card with Armbian into the console. 5) Turn on the console, close the testpoint, and at a certain point, the UART boot log will stop at gxl_p212_v1#. 6) Execute the following commands: mmc dev 1 env default -a -f;save setenv preboot 'if fatload mmc 0 1020000 aml_autoscript; then autoscr 1020000; fi; if fatload usb 0 1020000 aml_autoscript; then autoscr 1020000; fi; if fatload mmc 1 1020000 emmc_autoscript; then autoscr 1020000; fi;' save reboot Is there a simpler way to boot from a microSD card to default settings? Maybe I need to cleverly write a bootloader to it?

Hi all, I know this is a bit of a long shot given the age of the hardware, but I’m wondering if anyone here has ever experimented with running Armbian on an EVPad 2S (the old Android TV box). I’ve been tinkering with some older devices and thought it might be interesting to see if this one can be repurposed. I’ve attached a screenshot of the system info - unfortunately, it’s pretty sparse. The box is running Android 4.4.2 with kernel version 3.4.39, but the processor type is listed as “UNKNOWN,” and I haven’t found much documentation on the chipset or board layout. so before I dive deeper I wanted to ask: Has anyone managed to get Armbian (or any Linux distro) running on it? Are there known limitations with the chipset or bootloader that make it a dead end? Any tips, resources, or even “don’t bother” experiences would be appreciated. Thanks in advance for any insights - sometimes these older boxes surprise us, but I realize support may be very limited.

A long time ago, I made an armbian guide, which included adding a kernel patch. Can you try this method? "Move them* to ~/armbian-2023.05/build/userpatches/kernel/archives/sunxi-6.1 (using the scp command or sshfs)" * would mean the cpio file (use diff3 to convert to patch file**) and any linux configuration patches needed to make your initramfs. ** diff3 linux_orig_source_folder linux_source_folder_with_cpio_file https://github.com/robertojguerra/orangepi-zero-full-setup/blob/main/README2.md#73-add-the-tv-encoder-driver-to-the-linux-kernel-source

I have a Magicsee N5 Max X4 TV box (Amlogic S905X4). Has anyone tried this with this model? I tried removing the # S905X4_Generic symbol, but it still gives an error when booting. Could you please help me? Thank you!

Hello!! I am looking for help to boot Armbian on a generic TV Box sold as "MXQ Pro 4K 5G". I have tried multiple images (including official and community builds from sicXnull), but I only get a black screen or signal loss immediately after the boot attempt. Device Specifications: Model on case: MXQ Pro 4K 5G Board ID: IK316Q-EMCP_V4.1 SoC: Allwinner H313 (identified as sun50iw9p1 in Android) RAM: 1GB (Single chip configuration) Storage: 8GB eMMC Current Status: I am able to boot into the stock Android. To attempt the Armbian boot, I've tryed the Power up method, the power up pressing the hidden AV switch, using the reboot update command from a terminal emulator within Android. The issue: Upon executing the reboot command, the Android system shuts down, the display signal cuts off (or stays black), and the device never initializes Armbian (no HDMI output, no LEDs blinking differently). What I have tried: