Search the Community

I've this old tv box from a brazilian brand, called Intelbras IZY Play, the OEM appears to be SDMC, with the codename DV8038, it uses the s805x SoC. From what I've looked, it should be compatible using the files meson-gxl-s805x-p241.dtb u-boot-s905x-s912 The device does not have an SD card slot, so i'm trying to do it with a flash drive, however, after flashing it with balenaEtcher and doing the necessary changes to the files in my Windows PC, I cannot get it to boot, it justs enters a loop of showing the splash screen, turning off, showing the splash screen, and so on. I'm trying to turn it on pressing the hidden button that it has between the usb ports with a paper clip while I connect the power cable, if I do that without the USB stick on, it boots into a sort of recovery/fastboot screen similar to what android phones have. I've tried all variants of Armbian Bookworm, and I'm flashing Jammy as I write this post to test it as well, if it does work I will update the post.

Hello. I'm trying to run Armbian on an Acemak KII TV box (Amlogic S812 processor). From the page https://armbian.com/boards/aml-s805-mxq I downloaded the Armbian image Armbian_community_26.2.0-trunk.792_Aml-s805-mxq_trixie_current_6.12.28_minimal.img Using Win32DiskImager, I burned the Armbian image to a MicroSD card. In the armbianEnv.txt file, in the dtb_file line, I specified the path: dtb_file=/dtb/meson8m2-mxiii-plus.dtb I inserted the MicroSD card into the TV box. The TV box boots, Ethernet works, but there is no HDMI signal on the monitor. I tried specifying different dtb file variants in armbianEnv.txt. I found that if I specify the path dtb_file=/dtb/ meson8b-mxq.dtb , HDMI works (the console is displayed), but Ethernet doesn't. I decompiled the meson8b-mxq.dtb and meson8m2-mxiii-plus.dtb files, but I can't combine the files so that both Ethernet and HDMI work. I've attached the decompiled files. Please help me prepare a combined .dtb file meson8m2-mxiii-plus.dts meson8b-mxq.dts

Hello, I found this guide: https://github.com/robertojguerra/orangepi-zero-full-setup/blob/main/README2.md I followed the steps and built an Armbian image with current 6.12 kernel and now TV OUT (CVBS, Composite Video), after soldering a cable to the video pin on the board, is working on my Orange Pi One with an Allwinner H3 CPU (the patches might work for other H3/H2+ boards). I would like to get that functionality incorporated into Armbian.

Hello there, I followed from afar the advancement of the support on TV boxes for a while already, and I happened to stumble uppon a very cheap one on my local market. The specs are the following : -Amlogic S905W -2GB of ram -16GB of EMMC Following are some pictures I took, that shows the bare PCB. I hope that it will help answering questions I have. After looking into many written tutorials on getting armbian to boot on such machine, I have tested all .dtb files that are available, as long as quadruple-checked the u-boot file that needed to be used with that specific chip. I made sure to also press that buttom behind the jack-port before plugging in the board to hopefully boot onto the armbian install. Here are a few things I have observed. On all 3 available DTB files for the s905w, when using the u-boot-s905x-s912 file, none of them got me a picture after the first "splash screen". I have watched the power consumption during the "boot" and have seen the power fluctuating between 1.6 and 2.4W, until it setteled to 1.4W and stopped fluctuating. My very premature conclusion is that it somehow booted armbian but did not give me picture. The display that I am using was also showing that something was powered on, trying to send a picture but was not giving correct signal. Here's where my abilities end off. I do not know where to go next and what to try. I have not seen obvious pads to try connecting to UART, and I need assistance with going forward with that specific board. If anyone with experience can guide me, I'd appreciate it grately! Thank you in advance and hope this message finds the right person PS: The board boots fine to Android 7.1 otherwise, when not trying to boot to the SD card, so the machine is confirmed to be working!

Hi @SteeMan I have the same device as @Levy Barbosa and was able to acquire the logs. I took two. The first one booting normally, the second one I kept the reset button pressed while taking the log. Here is what I am planning: 1 - Have armbian running via an USB 2 - Dump its current firmware (not sure yet how to do it, will search more on it) 3 - Write armbian directly to the eMMC to boot it directly from there (not sure if its possible, but aiming it.) I am going to paste them here, let me know if you rather have me uploading a TXT file, just so I would not if any other log is needed in the future. Normal booting: Terminal log file ----------------------------------------------- OEMCrypto_GetOEMPublicCertificate: Provisioning method = 2. <0>GXL:BL1:9ac50e:bb16dc;FEAT:BFFC39BE:100;POC:3;RCY:0;EMMC:0;READ:0;1.0;1.0;CHK:0; TE: 313337 BL2 Built : 10:47:34, Jan 14 2019. gxl g152d217 - guotai.shen@droid11-sz set vcck to 1120 mv set vddee to 1000 mv Board ID = 7 CPU clk: 984MHz DDR enable rdbi DQS-corr enabled DDR scramble enabled DDR3 chl: Rank0 16bit @ 912MHz bist_test rank: 0 1c 00 39 2e 13 49 1f 01 3e 2e 12 4b 28 28 28 28 28 28 27 27 27 28 28 28 693 - PASS Rank0: 1024MB-2T-13 AddrBus test pass! Set ddr ssc: ppm1000- eMMC boot @ 0 sw8 s emmc switch 3 ok BL2: rpmb counter: 0x00000024 emmc switch 0 ok OTP_ARB=00000001 Load FIP HDR from eMMC, src: 0x0000c200, des: 0x01700000, size: 0x00004000, part: 0 Load BL3x from eMMC, src: 0x00010200, des: 0x01704000, size: 0x000f4000, part: 0 NOTICE: BL3-1: v1.0(release):3bc3888 NOTICE: BL3-1: Built : 11:28:51, May 10 2019 [BL31]: GXL CPU setup! NOTICE: BL3-1: GXL secure boot! NOTICE: BL3-1: BL33 decompress pass mpu_config_enable:system pre init ok dmc sec lock MVN_1=0x01010100 MVN_2=0x01010000 [Image: gxl_v1.1.3376-325f6f4 2019-05-27 16:25:06 shen.liu@droid11-sz] OPS=0x34 21 0d 34 00 37 2a 00 89 62 00 ac b5 67 13 99 02 [0.927393 Inits done] secure task start! high task start! low task start! INFO: BL3-2: ATOS-V2.4-239-g48b8c37d #1 Wed Feb 5 09:34:09 UTC 2020 arm INFO: BL3-2: Chip: GXL Rev: D (21:D - 30:2) INFO: BL3-2: crypto engine DMA INFO: BL3-2: secure time TEE INFO: BL3-2: CONFIG_DEVICE_SECURE 0xb200000e U-Boot 2015.01-gb7c1687 (Apr 08 2021 - 22:17:19) DRAM: 1 GiB Relocation Offset is: 36e85000 register usb cfg[0][1] = 0000000037f51148 [CANVAS]canvas init boot_device_flag : 1 Nand PHY Ver:1.01.001.0006 (c) 2013 Amlogic Inc. init bus_cycle=6, bus_timing=7, system=5.0ns reset failed get_chip_type and ret:fffffffe get_chip_type and ret:fffffffe chip detect failed and ret:fffffffe nandphy_init failed and ret=0xfffffff1 MMC: aml_priv->desc_buf = 0x0000000033e856b0 aml_priv->desc_buf = 0x0000000033e879f0 SDIO Port B: 0, SDIO Port C: 1 co-phase 0x2, tx-dly 0, clock 400000 co-phase 0x2, tx-dly 0, clock 400000 co-phase 0x2, tx-dly 0, clock 400000 emmc/sd response timeout, cmd8, status=0x1ff2800 emmc/sd response timeout, cmd55, status=0x1ff2800 co-phase 0x2, tx-dly 0, clock 400000 co-phase 0x2, tx-dly 0, clock 40000000 [mmc_startup] mmc refix success init_part() 297: PART_TYPE_AML [mmc_init] mmc init success Amlogic multi-dtb tool Multi dtb detected checkhw: hwid = 11 Multi dtb tool version: v2 . Support 2 dtbs. aml_dt soc: gxl platform: p241 variant: v2-1g dtb 0 soc: gxl plat: p241 vari: 1g dtb 1 soc: gxl plat: p241 vari: v2-1g Find match dtb: 1 start dts,buffer=0000000033e8a240,dt_addr=0000000033e99240 get_partition_from_dts() 71: ret 0 Amlogic multi-dtb tool Multi dtb detected checkhw: hwid = 11 Multi dtb tool version: v2 . Support 2 dtbs. aml_dt soc: gxl platform: p241 variant: v2-1g dtb 0 soc: gxl plat: p241 vari: 1g dtb 1 soc: gxl plat: p241 vari: v2-1g Find match dtb: 1 parts: 17 00: logo 0000000000800000 1 01: recovery 0000000001800000 1 02: misc 0000000000800000 1 03: dtbo 0000000000800000 1 04: cri_data 0000000000800000 2 05: param 0000000001000000 2 06: boot 0000000001000000 1 set has_boot_slot = 0 07: rsv 0000000001000000 1 08: metadata 0000000001000000 1 09: vbmeta 0000000000200000 1 10: tee 0000000002000000 1 11: vendor 0000000010000000 1 12: odm 0000000008000000 1 13: system 0000000050000000 1 14: product 0000000008000000 1 15: cache 0000000025000000 2 16: data ffffffffffffffff 4 init_part() 297: PART_TYPE_AML eMMC/TSD partition table have been checked OK! crc32_s:0x1577dad == storage crc_pattern:0x1577dad!!! crc32_s:0xee152b83 == storage crc_pattern:0xee152b83!!! crc32_s:0x7fd3b243 == storage crc_pattern:0x7fd3b243!!! mmc env offset: 0x2c400000 In: serial Out: serial Err: serial reboot_mode=cold_boot itest - return true/false on integer compare Usage: itest [.b, .w, .l, .s] [*]value1 <op> [*]value2 [store]To run cmd[emmc dtb_read 0x1000000 0x40000] _verify_dtb_checksum()-2755: calc f2d3afb4, store f2d3afb4 _verify_dtb_checksum()-2755: calc f2d3afb4, store f2d3afb4 dtb_read()-2972: total valid 2 update_old_dtb()-2953: do nothing Amlogic multi-dtb tool Multi dtb detected checkhw: hwid = 11 Multi dtb tool version: v2 . Support 2 dtbs. aml_dt soc: gxl platform: p241 variant: v2-1g dtb 0 soc: gxl plat: p241 vari: 1g dtb 1 soc: gxl plat: p241 vari: v2-1g Find match dtb: 1 vpu: clk_level in dts: 2 vpu: set clk: 200000000Hz, readback: 200000000Hz(0x501) vpu: vpu_clk_gate_init_off finish vpp: vpp_init cvbs: cpuid:0x21 cvbs: find performance_pal config hpd_state=0 vpp: vpp_matrix_update: 2 cvbs_performance_enhancement cvbs_config_hdmipll_gxl cvbs_set_vid2_clk vdac_enable: 1, module_sel:0x8 Net: dwmac.c9410000amlkey_init() enter! [EFUSE_MSG]keynum is 4 [BL31]: tee size: 0 CONFIG_AVB2: avb2 Start read misc partition datas! 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->crc32 = -1075449479 active slot = 0 wipe_data=successful wipe_cache=successful upgrade_step=2 reboot_mode:::: cold_boot amlkey_init() enter! amlkey_init() 71: already init! [EFUSE_MSG]keynum is 4 [BL31]: tee size: 0 [KM]Error:f[key_manage_query_size]L507:key[deviceid] not programed yet [KM]Error:f[key_manage_query_size]L507:key[oemkey] not programed yet [OSD]load fb addr from dts:/meson-fb [OSD]fb_addr for logo: 0x3fc00000 [OSD]load fb addr from dts:/meson-fb [OSD]fb_addr for logo: 0x3fc00000 [OSD]VPP_OFIFO_SIZE:0xfff00fff [CANVAS]addr=0x3fc00000 width=3840, height=2160 [OSD]osd_hw.free_dst_data: 0,719,0,575 amlkey_init() enter! amlkey_init() 71: already init! [EFUSE_MSG]keynum is 4 [BL31]: tee size: 0 [KM]Error:f[key_manage_query_size]L507:key[deviceid] not programed yet [KM]Error:f[key_manage_query_size]L507:key[oemkey] not programed yet gpio: pin GPIOAO_2 (gpio 102) value is 1 Command: bcb uboot-command Start read misc partition datas! BCB hasn't any datas,exit! amlkey_init() enter! amlkey_init() 71: already init! [EFUSE_MSG]keynum is 4 [BL31]: tee size: 0 [KM]Error:f[key_manage_query_size]L507:key[deviceid] not programed yet [KM]Error:f[key_manage_query_size]L507:key[oemkey] not programed yet (Re)start USB... USB0: USB3.0 XHCI init start Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.00 scanning bus 0 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found ** Invalid boot device ** Fail to detect device usb 0 get upgrade version failed Hit Enter or space or Ctrl+C key to stop autoboot -- : 0 CONFIG_SYSTEM_AS_ROOT: systemroot system_mode: 1 amlkey_init() enter! amlkey_init() 71: already init! [EFUSE_MSG]keynum is 4 [BL31]: tee size: 0 [KM]Error:f[key_manage_query_size]L507:key[deviceid] not programed yet [KM]Error:f[key_manage_query_size]L507:key[oemkey] not programed yet Start read misc partition datas! 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->crc32 = -1075449479 active slot = 0 CONFIG_AVB2: avb2 active_slot: normal [imgread]secureKernelImgSz=0x94a200 avb2: 1 Start read misc partition datas! 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->crc32 = -1075449479 active slot = 0 active_slot is normal ab_suffix is avb_slot_verify.c:524: DEBUG: Loading vbmeta struct from partition 'vbmeta'. Verified using testkey [store]To run cmd[emmc dtb_read 0x00000000357695c0 0x40000] dtb_read_shortcut()-2813: short cut in... Start read misc partition datas! 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->crc32 = -1075449479 active slot = 0 active_slot is normal Start read misc partition datas! 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->crc32 = -1075449479 active slot = 0 active_slot is normal Start read misc partition datas! 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->crc32 = -1075449479 active slot = 0 active_slot is normal avb verification: locked = 1, result = 0 ee_gate_off ... avb2: 1 ## Booting Android Image at 0x01080a00 ... reloc_addr =33f0a5a0 copy done Kernel command line: androidboot.dtbo_idx=0 buildvariant=user Start read misc partition datas! 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->crc32 = -1075449479 active slot = 0 active_slot is normal load dtb from 0x1000000 ...... Amlogic multi-dtb tool Single dtb detected find 1 dtbos dtbos to be applied: 0 Apply dtbo 0 Uncompressing Kernel Image ... OK kernel loaded at 0x01080000, end = 0x02958a00 libfdt fdt_getprop(): FDT_ERR_NOTFOUND Loading Device Tree to 000000001ffee000, end 000000001ffff4ba ... OK fdt_instaboot: no instaboot image Starting kernel ... uboot time: 6838532 us domain-0 init dvfs: 4 [ 0.000000@0] Reserved memory: unable to setup CMA region [ 0.232770@0] VMAP:handle_vmap_fault address ffffff802008c000 out of range [ 5.889934@2] init: Unable to set property 'ro.build.id' to 'PI' in property file '/system/build.prop': Read-only property was already set [ 5.897038@2] init: Unable to set property 'ro.build.version.incremental' to '20210409' in property file '/system/build.prop': Read-only property was already set [ 5.911478@2] init: Unable to set property 'ro.build.version.security_patch' to '2021-03-05' in property file '/system/build.prop': Read-only property was already set [ 5.926147@2] init: Unable to set property 'ro.build.date.utc' to '1619145388' in property file '/system/build.prop': Read-only property was already set [ 5.939635@2] init: Unable to set property 'ro.product.model' to 'IZY01' in property file '/system/build.prop': Read-only property was already set [ 5.952548@2] init: Unable to set property 'ro.product.brand' to 'Intelbras' in property file '/system/build.prop': Read-only property was already set [ 5.965901@2] init: Unable to set property 'ro.product.name' to 'IzyPlay' in property file '/system/build.prop': Read-only property was already set [ 5.978998@2] init: Unable to set property 'ro.product.device' to 'DV8038' in property file '/system/build.prop': Read-only property was already set [ 5.992358@2] init: Unable to set property 'ro.product.manufacturer' to 'SDMC' in property file '/system/build.prop': Read-only property was already set [ 6.005841@2] init: Unable to set property 'ro.wifi.channels' to '13' in property file '/system/build.prop': Read-only property was already set [ 6.018589@2] init: Unable to set property 'ro.build.fingerprint' to 'Intelbras/IzyPlay/DV8038:9/PI/20210409:user/release-keys' in property file '/system/build.prop': Read-only property was already set [ 6.038481@2] init: Unable to set property 'ro.product.first_api_level' to '28' in property file '/vendor/build.prop': Read-only property was already set [ 6.051357@2] selinux: avc: denied { set } for property=ro.net.pppoe pid=1 uid=0 gid=0 scontext=u:r:vendor_init:s0 tcontext=u:object_r:default_prop:s0 tclass=property_service permissive=0 [ 6.051357@2] [ 6.068258@2] init: Unable to set property 'ro.net.pppoe' to 'true' in property file '/vendor/build.prop': SELinux permission check failed [ 6.081330@2] selinux: avc: denied { set } for property=persist.sys.dts.edid pid=1 uid=0 gid=0 scontext=u:r:vendor_init:s0 tcontext=u:object_r:system_prop:s0 tclass=property_service permissive=0 [ 6.081330@2] [ 6.099550@2] init: Unable to set property 'persist.sys.dts.edid' to 'false' in property file '/vendor/build.prop': SELinux permission check failed [ 6.112706@2] selinux: avc: denied { set } for property=service.bootvideo pid=1 uid=0 gid=0 scontext=u:r:vendor_init:s0 tcontext=u:object_r:system_prop:s0 tclass=property_service permissive=0 [ 6.112706@2] [ 6.131353@2] init: Unable to set property 'service.bootvideo' to '0' in property file '/vendor/build.prop': SELinux permission check failed set property 'persist.sys.PQ.enable' to 'true' in property file '/vendor/build.prop': SELinux permission check failed [ 6.602149@2] init: Unable to set property 'ro.nrdp.validation' to 'ninja_6' in property file '/vendor/build.prop': Read-only property was already set [ 6.614889@2] init: Unable to set property 'ro.nrdp.modelgroup' to 'SDMCs805' in property file '/vendor/build.prop': Read-only property was already set [ 6.628353@2] selinux: avc: denied { set } for property=sys.fb.bits pid=1 uid=0 gid=0 scontext=u:r:vendor_init:s0 tcontext=u:object_r:system_prop:s0 tclass=property_service permissive=0 [ 6.628353@2] [ 6.646453@2] init: Unable to set property 'sys.fb.bits' to '32' in property file '/vendor/build.prop': SELinux permission check failed [ 6.659515@2] selinux: avc: denied { set } for property=ro.adb.secure pid=1 uid=0 gid=0 scontext=u:r:vendor_init:s0 tcontext=u:object_r:exported_secure_prop:s0 tclass=property_service permissive=0 [ 6.659515@2] [ 6.677689@2] init: Unable to set property 'ro.adb.secure' to '1' in property file '/vendor/build.prop': SELinux permission check failed [ 6.689845@2] selinux: avc: denied { set } for property=persist.sys.app.rotation pid=1 uid=0 gid=0 scontext=u:r:vendor_init:s0 tcontext=u:object_r:system_prop:s0 tclass=property_service permissive=0 [ 6.689845@2] [ 6.709158@2] init: Unable to set property 'persist.sys.app.rotation' to 'original' in property file '/vendor/build.prop': SELinux permission check failed [ 6.725543@2] init: /recovery not specified in fstab [ 6.977780@2] init: Could not find service hosting interface android.hardware.keymaster@3.0::IKeymasterDevice/default [ 6.983791@2] init: Could not find service hosting interface android.hardware.keymaster@3.0::IKeymasterDevice/default MESSAGE: USER-TA:log_msg:70: KeymasterTA (info): app/ipc/keymaster_ipc.cpp, Line 752: Amlogic KEYMASTER 2.0! Build Time: Jun 19 2018 14:46:55 [ 7.498202@3] init: couldn't write 2976 to /dev/cpuset/camera-daemon/tasks: No such file or directory [ 7.767829@1] init: setpgid failed for console: Operation not permitted [ 7.879853@2] init: Failed to bind socket 'pdx/system/vr/display/client': No such file or directory [ 7.910205@2] init: Failed to bind socket 'pdx/system/vr/display/manager': No such file or directory [ 7.947258@2] init: Failed to bind socket 'pdx/system/vr/display/vsync': No such file or directory [ 6.144032@2] selinux: avc: denied { set } for property=libplayer.livets.softdemux pid=1 uid=0 gid=0 scontext=u:r:vendor_init:s0 tcontext=u:object_r:default_prop:s0 tclass=property_service permissive=0 [ 6.144032@2] [ 6.163476@2] init: Unable to set property 'libplayer.livets.softdemux' to '1' in property file '/vendor/build.prop': SELinux permission check failed [ 6.176762@2] selinux: avc: denied { set } for property=libplayer.netts.recalcpts pid=1 uid=0 gid=0 scontext=u:r:vendor_init:s0 tcontext=u:object_r:default_prop:s0 tclass=property_service permissive=0 [ 6.176762@2] [ 6.196278@2] init: Unable to set property 'libplayer.netts.recalcpts' to '1' in property file '/vendor/build.prop': SELinux permission check failed [ 6.209516@2] selinux: avc: denied { set } for property=persist.fw.force_adoptable pid=1 uid=0 gid=0 scontext=u:r:vendor_init:s0 tcontext=u:object_r:default_prop:s0 tclass=property_service permissive=0 [ 6.209516@2] [ 6.229021@2] init: Unable to set property 'persist.fw.force_adoptable' to 'true' in property file '/vendor/build.prop': SELinux permission check failed [ 6.242651@2] selinux: avc: denied { set } for property=sys.ignore.inativecec pid=1 uid=0 gid=0 scontext=u:r:vendor_init:s0 tcontext=u:object_r:system_prop:s0 tclass=property_service permissive=0 [ 6.242651@2] [ 6.261600@2] init: Unable to set property 'sys.ignore.inativecec' to 'true' in property file '/vendor/build.prop': SELinux permission check failed [ 6.274701@2] selinux: avc: denied { set } for property=ro.sys.hdmiin.enable pid=1 uid=0 gid=0 scontext=u:r:vendor_init:s0 tcontext=u:object_r:default_prop:s0 tclass=property_service permissive=0 [ 6.274701@2] [ 6.293739@2] init: Unable to set property 'ro.sys.hdmiin.enable' to 'true' in property file '/vendor/build.prop': SELinux permission check failed [ 6.306792@2] selinux: avc: denied { set } for property=mbx.hdmiin.switchfull pid=1 uid=0 gid=0 scontext=u:r:vendor_init:s0 tcontext=u:object_r:default_prop:s0 tclass=property_service permissive=0 [ 6.306792@2] [ 6.325964@2] init: Unable to set property 'mbx.hdmiin.switchfull' to 'false' in property file '/vendor/build.prop': SELinux permission check failed [ 6.339174@2] selinux: avc: denied { set } for property=mbx.hdmiin.videolayer pid=1 uid=0 gid=0 scontext=u:r:vendor_init:s0 tcontext=u:object_r:default_prop:s0 tclass=property_service permissive=0 [ 6.339174@2] [ 6.358384@2] init: Unable to set property 'mbx.hdmiin.videolayer' to 'false' in property file '/vendor/build.prop': SELinux permission check failed [ 6.371936@2] selinux: avc: denied { set } for property=ro.com.android.dateformat pid=1 uid=0 gid=0 scontext=u:r:vendor_init:s0 tcontext=u:object_r:default_prop:s0 tclass=property_service permissive=0 [ 6.371936@2] [ 6.391048@2] init: Unable to set property 'ro.com.android.dateformat' to 'MM-dd-yyyy' in property file '/vendor/build.prop': SELinux permission check failed [ 6.405572@2] selinux: avc: denied { set } for property=net.tethering.noprovisioning pid=1 uid=0 gid=0 scontext=u:r:vendor_init:s0 tcontext=u:object_r:system_prop:s0 tclass=property_service permissive=0 [ 6.405572@2] [ 6.424689@2] init: Unable to set property 'net.tethering.noprovisioning' to 'true' in property file '/vendor/build.prop': SELinux permission check failed [ 6.439214@2] selinux: avc: denied { set } for property=ro.product.firmware pid=1 uid=0 gid=0 scontext=u:r:vendor_init:s0 tcontext=u:object_r:default_prop:s0 tclass=property_service permissive=0 [ 6.439214@2] [ 6.457345@2] init: Unable to set property 'ro.product.firmware' to '00502001' in property file '/vendor/build.prop': SELinux permission check failed [ 6.470652@2] selinux: avc: denied { set } for property=ro.product.otaupdateurl pid=1 uid=0 gid=0 scontext=u:r:vendor_init:s0 tcontext=u:object_r:default_prop:s0 tclass=property_service permissive=0 [ 6.470652@2] [ 6.489927@2] init: Unable to set property 'ro.product.otaupdateurl' to 'http://10.28.11.53:8080/otaupdate/update' in property file '/vendor/build.prop': SELinux permission check failed [ 6.506456@2] selinux: avc: denied { set } for property=ro.treble.enabled pid=1 uid=0 gid=0 scontext=u:r:vendor_init:s0 tcontext=u:object_r:default_prop:s0 tclass=property_service permissive=0 [ 6.506456@2] [ 6.525099@2] init: Unable to set property 'ro.treble.enabled' to 'true' in property file '/vendor/build.prop': SELinux permission check failed [ 6.537847@2] selinux: avc: denied { set } for property=fw.disable_quota pid=1 uid=0 gid=0 scontext=u:r:vendor_init:s0 tcontext=u:object_r:default_prop:s0 tclass=property_service permissive=0 [ 6.537847@2] [ 6.556546@2] init: Unable to set property 'fw.disable_quota' to 'true' in property file '/vendor/build.prop': SELinux permission check failed [ 6.569363@2] selinux: avc: denied { set } for property=persist.sys.PQ.enable pid=1 uid=0 gid=0 scontext=u:r:vendor_init:s0 tcontext=u:object_r:system_prop:s0 tclass=property_service permissive=0 [ 6.569363@2] t: Unable to set property 'ro.nrdp.validation' to 'ninja_6' in property file '/vendor/build.prop': Read-only property was already set [ 6.614889@2] init: Unable to set property 'ro.nrdp.modelgroup' to 'SDMCs805' in property file '/vendor/build.prop': Read-only property was already set [ 6.628353@2] selinux: avc: denied { set } for property=sys.fb.bits pid=1 uid=0 gid=0 scontext=u:r:vendor_init:s0 tcontext=u:object_r:system_prop:s0 tclass=property_service permissive=0 [ 6.628353@2] [ 6.646453@2] init: Unable to set property 'sys.fb.bits' to '32' in property file '/vendor/build.prop': SELinux permission check failed [ 6.659515@2] selinux: avc: denied { set } for property=ro.adb.secure pid=1 uid=0 gid=0 scontext=u:r:vendor_init:s0 tcontext=u:object_r:exported_secure_prop:s0 tclass=property_service permissive=0 [ 6.659515@2] [ 6.677689@2] init: Unable to set property 'ro.adb.secure' to '1' in property file '/vendor/build.prop': SELinux permission check failed [ 8.123657@0] android.hardware.health@2.0-impl: wakealarm_init: timerfd_create failed [ 8.335528@1] init: Could not find service hosting interface vendor.amlogic.hardware.hdmicec@1.0::IDroidHdmiCEC/default [ 8.355812@0] init: Could not find service hosting interface vendor.amlogic.hardware.systemcontrol@1.0::ISystemControl/default [ 8.429141@2] init: Could not find service hosting interface vendor.amlogic.hardware.systemcontrol@1.0::ISystemControl/default [ 8.519461@2] vfm_map_store:rm default [ 8.521327@0] vfm_map_store:add default decoder ppmgr deinterlace amvideo [ 8.545386@0] init: Could not find service hosting interface vendor.amlogic.hardware.hdmicec@1.0::IDroidHdmiCEC/default [ 8.575919@0] init: Could not find service hosting interface vendor.amlogic.hardware.systemcontrol@1.0::ISystemControl/default the package has 87 fws totally. The TA ver is v0.2 The fw ver is v0.2 the fw with 480 KB will be loaded. [ 8.614739@1] init: Subcontext init could not set 'ro.radio.noril' to 'true': Read-only property was already set dmicec@1.0::IDroidHdmiCEC/default [ 8.641382@0] meson-mmc: sdio: resp_timeout,vstat:0xa3ff2800,virqc:3fff [ 8.642358@0] meson-mmc: sdio: err: wait for irq service, bus_fsm:0x8 [ 8.649963@0] meson-mmc: sdio: resp_timeout,vstat:0xa3ff2800,virqc:3fff [ 8.655295@0] meson-mmc: sdio: err: wait for irq service, bus_fsm:0x8 [ 8.666466@0] meson-mmc: sdio: resp_timeout,vstat:0xa3ff2800,virqc:3fff [ 8.668230@0] meson-mmc: sdio: err: wait for irq service, bus_fsm:0x8 [ 8.681930@1] init: Subcontext init could not set 'ro.oem.key1' to 'ATV00104319': Read-only property was already set [ 8.708463@0] init: Could not start service 'factoryreset' as part of class 'main': Cannot find '/vendor/bin/factoryreset.sh': No such file or directory [ 8.905477@2] init: Failed to open file '/d/mmc0/mmc0:0001/ext_csd': No such file or directory [ 8.956764@1] init: Could not start service 'wifi_detect' as part of class 'main': Cannot find '/vendor/bin/sdmc_wifi_detect': No such file or directory [HDCP-TA] read hdcp key(hdcp_tx22.bin) ret = 0xFFFF0008 [HDCP-TA] read hdcp key(hdcp_tx14.bin) ret = 0xFFFF0008 ERROR SECURITY_KEY_READ 1 [HDCP-TA] read hdcp key(hdcp_rx14.bin) ret = 0xFFFF0006 [ 8.721681@1] init: Could not start service 'ir_leds_blink' as part of class 'main': Cannot find '/vendor/bin/ir_blink': No such file or directory [ 8.751238@3] init: couldn't write 3059 to /dev/cpuset/camera-daemon/tasks: No such file or directory [ 6.689845@2] selinux: avc: denied { set } for property=persist.sys.app.rotation pid=1 uid=0 gid=0 scontext=u:r:vendor_init:s0 tcontext=u:object_r:system_prop:s0 tclass=property_service permissive=0 [ 6.689845@2] [ 6.709158@2] init: Unable to set property 'persist.sys.app.rotation' to 'original' in property file '/vendor/build.prop': SELinux permission check failed [ 6.725543@2] init: /recovery not specified in fstab [ 6.977780@2] init: Could not find service hosting interface android.hardware.keymaster@3.0::IKeymasterDevice/default [ 6.983791@2] init: Could not find service hosting interface android.hardware.keymaster@3.0::IKeymasterDevice/default MESSAGE: USER-TA:log_msg:70: KeymasterTA (info): app/ipc/keymaster_ipc.cpp, Line 752: Amlogic KEYMASTER 2.0! Build Time: Jun 19 2018 14:46:55 [ 7.498202@3] init: couldn't write 2976 to /dev/cpuset/camera-daemon/tasks: No such file or directory [ 7.767829@1] init: setpgid failed for console: Operation not permitted [ 7.879853@2] init: Failed to bind socket 'pdx/system/vr/display/client': No such file or directory [ 7.910205@2] init: Failed to bind socket 'pdx/system/vr/display/manager': No such file or directory [ 7.947258@2] init: Failed to bind socket 'pdx/system/vr/display/vsync': No such file or directory console:/ # 6.081330@2] [ 6.099550@2] init: Unable to set property 'persist.sys.dts.edid' to 'false' in property file '/vendor/build.prop': SELinux permission check failed [ 6.112706@2] selinux: avc: denied { set } for property=service.bootvideo pid=1 uid=0 gid=0 scontext=u:r:vendor_init:s0 tcontext=u:object_r:system_prop:s0 tclass=property_service permissive=0 [ 6.112706@2] [ 6.131353@2] init: Unable to set property 'service.bootvideo' to '0' in property file '/vendor/build.prop': SELinux permission check failed [ 6.144032@2] selinux: avc: denied { set } for property=libplayer.livets.softdemux pid=1 uid=0 gid=0 scontext=u:r:vendor_init:s0 tcontext=u:object_r:default_prop:s0 tclass=property_service permissive=0 [ 6.144032@2] [ 6.163476@2] init: Unable to set property 'libplayer.livets.softdemux' to '1' in property file '/vendor/build.prop': SELinux permission check failed [ 6.176762@2] selinux: avc: denied { set } for property=libplayer.netts.recalcpts pid=1 uid=0 gid=0 scontext=u:r:vendor_init:s0 tcontext=u:object_r:default_prop:s0 tclass=property_service permissive=0 [ 6.176762@2] [ 6.196278@2] init: Unable to set property 'libplayer.netts.recalcpts' to '1' in property file '/vendor/build.prop': SELinux permission check failed [ 6.209516@2] selinux: avc: denied { set } for property=persist.fw.force_adoptable pid=1 uid=0 gid=0 scontext=u:r:vendor_init:s0 tcontext=u:object_r:default_prop:s0 tclass=property_service permissive=0 [ 6.209516@2] [ 6.229021@2] init: Unable to set property 'persist.fw.force_adoptable' to 'true' in property file '/vendor/build.prop': SELinux permission check failed [ 6.242651@2] selinux: avc: denied { set } for property=sys.ignore.inativecec pid=1 uid=0 gid=0 scontext=u:r:vendor_init:s0 tcontext=u:object_r:system_prop:s0 tclass=property_service permissive=0 [ 6.242651@2] [ 6.261600@2] init: Unable to set property 'sys.ignore.inativecec' to 'true' in property file '/vendor/build.prop': SELinux permission check failed [ 6.274701@2] selinux: avc: denied { set } for property=ro.sys.hdmiin.enable pid=1 uid=0 gid=0 scontext=u:r:vendor_init:s0 tcontext=u:object_r:default_prop:s0 tclass=property_service permissive=0 [ 6.274701@2] [ 6.293739@2] init: Unable to set property 'ro.sys.hdmiin.enable' to 'true' in property file '/vendor/build.prop': SELinux permission check failed [ 6.306792@2] selinux: avc: denied { set } for property=mbx.hdmiin.switchfull pid=1 uid=0 gid=0 scontext=u:r:vendor_init:s0 tcontext=u:object_r:default_prop:s0 tclass=property_service permissive=0 [ 6.306792@2] [ 6.325964@2] init: Unable to set property 'mbx.hdmiin.switchfull' to 'false' in property file '/vendor/build.prop': SELinux permission check failed [ 6.339174@2] selinux: avc: denied { set } for property=mbx.hdmiin.videolayer pid=1 uid=0 gid=0 scontext=u:r:vendor_init:s0 tcontext=u:object_r:default_prop:s0 tclass=property_service permissive=0 [ 6.339174@2] [ 6.358384@2] init: Unable to set property 'mbx.hdmiin.videolayer' to 'false' in property file '/vendor/build.prop': SELinux permission check failed [ 6.371936@2] selinux: avc: denied { set } for property=ro.com.android.dateformat pid=1 uid=0 gid=0 scontext=u:r:vendor_init:s0 tcontext=u:object_r:default_prop:s0 tclass=property_service permissive=0 [ 6.371936@2] [ 6.391048@2] init: Unable to set property 'ro.com.android.dateformat' to 'MM-dd-yyyy' in property file '/vendor/build.prop': SELinux permission check failed [ 6.405572@2] selinux: avc: denied { set } for property=net.tethering.noprovisioning pid=1 uid=0 gid=0 scontext=u:r:vendor_init:s0 tcontext=u:object_r:system_prop:s0 tclass=property_service permissive=0 [ 6.405572@2] [ 6.424689@2] init: Unable to set property 'net.tethering.noprovisioning' to 'true' in property file '/vendor/build.prop': SELinux permission check failed [ 6.439214@2] selinux: avc: denied { set } for property=ro.product.firmware pid=1 uid=0 gid=0 scontext=u:r:vendor_init:s0 tcontext=u:object_r:default_prop:s0 tclass=property_service permissive=0 [ 6.439214@2] [ 6.457345@2] init: Unable to set property 'ro.product.firmware' to '00502001' in property file '/vendor/build.prop': SELinux permission check failed [ 6.470652@2] selinux: avc: denied { set } for property=ro.product.otaupdateurl pid=1 uid=0 gid=0 scontext=u:r:vendor_init:s0 tcontext=u:object_r:default_prop:s0 tclass=property_service permissive=0 [ 6.470652@2] [ 6.489927@2] init: Unable to set property 'ro.product.otaupdateurl' to 'http://10.28.11.53:8080/otaupdate/update' in property file '/vendor/build.prop': SELinux permission check failed [ 6.506456@2] selinux: avc: denied { set } for property=ro.treble.enabled pid=1 uid=0 gid=0 scontext=u:r:vendor_init:s0 tcontext=u:object_r:default_prop:s0 tclass=property_service permissive=0 [ 6.506456@2] [ 6.525099@2] init: Unable to set property[ 8.905477@2] ini[ 10.906965@0] cectx c810023c.aocec: init_cec_port_info phy_addr:0, port num:1 [ 10.908545@0] cectx c810023c.aocec: port_seq=0x0 [ 10.913546@0] cectx c810023c.aocec: portinfo id:0 arc:0 phy:1000,type:0 [ 21.907015@3] cectx c810023c.aocec: init_cec_port_info phy_addr:0, port num:1 [ 21.908525@3] cectx c810023c.aocec: port_seq=0x0 [ 21.913196@3] cectx c810023c.aocec: portinfo id:0 arc:0 phy:1000,type:0 Playready TA Start Playready TA Exit! Playready TA_DestroyEntryPoint! OEMCrypto_GetOEMPublicCertificate: Provisioning method = 2. OEMCrypto_GetOEMPublicCertificate: Provisioning method = 2. set ta time 1777644040 OEMCrypto_GetOEMPublicCertificate: Provisioning method = 2. OEMCrypto_GetOEMPublicCertificate: Provisioning method = 2. OEMCrypto_GetOEMPublicCertificate: Provisioning method = 2. OEMCrypto_GetOEMPublicCertificate: Provisioning method = 2. OEMCrypto_GetOEMPublicCertificate: Provisioning method = 2. OEMCrypto_GetOEMPublicCertificate: Provisioning method = 2. OEMCrypto_GetOEMPublicCertificate: Provisioning method = 2. [ 94.217875@0] binder_alloc: 4709: binder_alloc_buf size 1056768 failed, no address space [ 94.221143@0] binder_alloc: allocated: 184 (num: 3 largest: 168), free: 1040200 (num: 1 largest: 1040200) [ 107.113192@0] unifykey: key_unify_init() already inited! [ 107.113771@0] unifykey: name: usid, size 37 [ 107.117434@0] unifykey: key_unify_init() already inited! OEMCrypto_GetOEMPublicCertificate: Provisioning method = 2. ----------------------------------------------- End log file This one with the reset button pressed: Terminal log file ----------------------------------------------- OEMCrypto_GetOEMPublicCertificate: Provisioning method = 2. [ 428.570277@1] unifykey: key_unify_init() already inited! [ 428.571318@1] unifykey: name: usid, size 37 [ 428.575539@1] unifykey: key_unify_init() already inited! OEMCrypto_GetOEMPublicCertificate: Provisioning method = 2. [ 441.929160@0] unifykey: key_unify_init() already inited! [ 441.929656@0] unifykey: name: usid, size 37 [ 441.933533@0] unifykey: key_unify_init() already inited! GXL:BL1:9ac50e:bb16dc;FEAT:BFFC39BE:100;POC:3;RCY:0;EMMC:0;READ:0;1.0;1.0;CHK:0; TE: 315899 BL2 Built : 10:47:34, Jan 14 2019. gxl g152d217 - guotai.shen@droid11-sz set vcck to 1120 mv set vddee to 1000 mv Board ID = 7 CPU clk: 984MHz DDR enable rdbi DQS-corr enabled DDR scramble enabled DDR3 chl: Rank0 16bit @ 912MHz bist_test rank: 0 1b 00 37 2f 14 4a 1e 00 3d 2f 13 4b 28 28 28 28 28 28 28 28 28 29 29 29 693 - PASS Rank0: 1024MB-2T-13 AddrBus test pass! Set ddr ssc: ppm1000- eMMC boot @ 0 sw8 s emmc switch 3 ok BL2: rpmb counter: 0x00000024 emmc switch 0 ok OTP_ARB=00000001 Load FIP HDR from eMMC, src: 0x0000c200, des: 0x01700000, size: 0x00004000, part: 0 Load BL3x from eMMC, src: 0x00010200, des: 0x01704000, size: 0x000f4000, part: 0 NOTICE: BL3-1: v1.0(release):3bc3888 NOTICE: BL3-1: Built : 11:28:51, May 10 2019 [BL31]: GXL CPU setup! NOTICE: BL3-1: GXL secure boot! NOTICE: BL3-1: BL33 decompress pass mpu_config_enable:system pre init ok dmc sec lock MVN_1=0x01010100 MVN_2=0x01010000 [Image: gxl_v1.1.3376-325f6f4 2019-05-27 16:25:06 shen.liu@droid11-sz] OPS=0x34 21 0d 34 00 37 2a 00 89 62 00 ac b5 67 13 99 02 [0.932030 Inits done] secure task start! high task start! low task start! INFO: BL3-2: ATOS-V2.4-239-g48b8c37d #1 Wed Feb 5 09:34:09 UTC 2020 arm INFO: BL3-2: Chip: GXL Rev: D (21:D - 30:2) INFO: BL3-2: crypto engine DMA INFO: BL3-2: secure time TEE INFO: BL3-2: CONFIG_DEVICE_SECURE 0xb200000e U-Boot 2015.01-gb7c1687 (Apr 08 2021 - 22:17:19) DRAM: 1 GiB Relocation Offset is: 36e85000 register usb cfg[0][1] = 0000000037f51148 [CANVAS]canvas init boot_device_flag : 1 Nand PHY Ver:1.01.001.0006 (c) 2013 Amlogic Inc. init bus_cycle=6, bus_timing=7, system=5.0ns reset failed get_chip_type and ret:fffffffe get_chip_type and ret:fffffffe chip detect failed and ret:fffffffe nandphy_init failed and ret=0xfffffff1 MMC: aml_priv->desc_buf = 0x0000000033e856b0 aml_priv->desc_buf = 0x0000000033e879f0 SDIO Port B: 0, SDIO Port C: 1 co-phase 0x2, tx-dly 0, clock 400000 co-phase 0x2, tx-dly 0, clock 400000 co-phase 0x2, tx-dly 0, clock 400000 emmc/sd response timeout, cmd8, status=0x1ff2800 emmc/sd response timeout, cmd55, status=0x1ff2800 co-phase 0x2, tx-dly 0, clock 400000 co-phase 0x2, tx-dly 0, clock 40000000 [mmc_startup] mmc refix success init_part() 297: PART_TYPE_AML [mmc_init] mmc init success Amlogic multi-dtb tool Multi dtb detected checkhw: hwid = 11 Multi dtb tool version: v2 . Support 2 dtbs. aml_dt soc: gxl platform: p241 variant: v2-1g dtb 0 soc: gxl plat: p241 vari: 1g dtb 1 soc: gxl plat: p241 vari: v2-1g Find match dtb: 1 start dts,buffer=0000000033e8a240,dt_addr=0000000033e99240 get_partition_from_dts() 71: ret 0 Amlogic multi-dtb tool Multi dtb detected checkhw: hwid = 11 Multi dtb tool version: v2 . Support 2 dtbs. aml_dt soc: gxl platform: p241 variant: v2-1g dtb 0 soc: gxl plat: p241 vari: 1g dtb 1 soc: gxl plat: p241 vari: v2-1g Find match dtb: 1 parts: 17 00: logo 0000000000800000 1 01: recovery 0000000001800000 1 02: misc 0000000000800000 1 03: dtbo 0000000000800000 1 04: cri_data 0000000000800000 2 05: param 0000000001000000 2 06: boot 0000000001000000 1 set has_boot_slot = 0 07: rsv 0000000001000000 1 08: metadata 0000000001000000 1 09: vbmeta 0000000000200000 1 10: tee 0000000002000000 1 11: vendor 0000000010000000 1 12: odm 0000000008000000 1 13: system 0000000050000000 1 14: product 0000000008000000 1 15: cache 0000000025000000 2 16: data ffffffffffffffff 4 init_part() 297: PART_TYPE_AML eMMC/TSD partition table have been checked OK! crc32_s:0x1577dad == storage crc_pattern:0x1577dad!!! crc32_s:0xee152b83 == storage crc_pattern:0xee152b83!!! crc32_s:0x7fd3b243 == storage crc_pattern:0x7fd3b243!!! mmc env offset: 0x2c400000 In: serial Out: serial Err: serial reboot_mode=cold_boot itest - return true/false on integer compare Usage: itest [.b, .w, .l, .s] [*]value1 <op> [*]value2 [store]To run cmd[emmc dtb_read 0x1000000 0x40000] _verify_dtb_checksum()-2755: calc f2d3afb4, store f2d3afb4 _verify_dtb_checksum()-2755: calc f2d3afb4, store f2d3afb4 dtb_read()-2972: total valid 2 update_old_dtb()-2953: do nothing Amlogic multi-dtb tool Multi dtb detected checkhw: hwid = 11 Multi dtb tool version: v2 . Support 2 dtbs. aml_dt soc: gxl platform: p241 variant: v2-1g dtb 0 soc: gxl plat: p241 vari: 1g dtb 1 soc: gxl plat: p241 vari: v2-1g Find match dtb: 1 vpu: clk_level in dts: 2 vpu: set clk: 200000000Hz, readback: 200000000Hz(0x501) vpu: vpu_clk_gate_init_off finish vpp: vpp_init cvbs: cpuid:0x21 cvbs: find performance_pal config hpd_state=0 vpp: vpp_matrix_update: 2 cvbs_performance_enhancement cvbs_config_hdmipll_gxl cvbs_set_vid2_clk vdac_enable: 1, module_sel:0x8 Net: dwmac.c9410000amlkey_init() enter! [EFUSE_MSG]keynum is 4 [BL31]: tee size: 0 CONFIG_AVB2: avb2 Start read misc partition datas! 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->crc32 = -1075449479 active slot = 0 wipe_data=successful wipe_cache=successful upgrade_step=2 reboot_mode:::: cold_boot amlkey_init() enter! amlkey_init() 71: already init! [EFUSE_MSG]keynum is 4 [BL31]: tee size: 0 [KM]Error:f[key_manage_query_size]L507:key[deviceid] not programed yet [KM]Error:f[key_manage_query_size]L507:key[oemkey] not programed yet [OSD]load fb addr from dts:/meson-fb [OSD]fb_addr for logo: 0x3fc00000 [OSD]load fb addr from dts:/meson-fb [OSD]fb_addr for logo: 0x3fc00000 [OSD]VPP_OFIFO_SIZE:0xfff00fff [CANVAS]addr=0x3fc00000 width=3840, height=2160 [OSD]osd_hw.free_dst_data: 0,719,0,575 amlkey_init() enter! amlkey_init() 71: already init! [EFUSE_MSG]keynum is 4 [BL31]: tee size: 0 [KM]Error:f[key_manage_query_size]L507:key[deviceid] not programed yet [KM]Error:f[key_manage_query_size]L507:key[oemkey] not programed yet gpio: pin GPIOAO_2 (gpio 102) value is 0 detect upgrade key gpio: pin GPIOAO_2 (gpio 102) value is 0 InUsbBurn noSof card out co-phase 0x2, tx-dly 0, clock 400000 co-phase 0x2, tx-dly 0, clock 400000 co-phase 0x2, tx-dly 0, clock 400000 emmc/sd response timeout, cmd8, status=0x1ff2800 emmc/sd response timeout, cmd55, status=0x1ff2800 emmc/sd response timeout, cmd1, status=0x1ff2800 [MSG]mmcinfo failed! co-phase 0x2, tx-dly 0, clock 400000 co-phase 0x2, tx-dly 0, clock 400000 co-phase 0x2, tx-dly 0, clock 400000 emmc/sd response timeout, cmd8, status=0x1ff2800 emmc/sd response timeout, cmd55, status=0x1ff2800 emmc/sd response timeout, cmd1, status=0x1ff2800 (Re)start USB... USB0: USB3.0 XHCI init start Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.00 scanning bus 0 for devices... 1 USB Device(s) found [imgread]secureKernelImgSz=0xf14a00 avb2: 1 Start read misc partition datas! 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->crc32 = -1075449479 active slot = 0 active_slot is normal ab_suffix is avb_slot_verify.c:524: DEBUG: Loading vbmeta struct from partition 'vbmeta'. Verified using testkey [store]To run cmd[emmc dtb_read 0x00000000357695c0 0x40000] dtb_read_shortcut()-2813: short cut in... Start read misc partition datas! 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->crc32 = -1075449479 active slot = 0 active_slot is normal Start read misc partition datas! 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->crc32 = -1075449479 active slot = 0 active_slot is normal Start read misc partition datas! 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->crc32 = -1075449479 active slot = 0 active_slot is normal avb verification: locked = 1, result = 0 ee_gate_off ... avb2: 1 ## Booting Android Image at 0x01080a00 ... reloc_addr =33f0a5a0 copy done Kernel command line: androidboot.dtbo_idx=0 buildvariant=user Start read misc partition datas! 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->crc32 = -1075449479 active slot = 0 active_slot is normal load dtb from 0x1000000 ...... Amlogic multi-dtb tool Single dtb detected find 1 dtbos dtbos to be applied: 0 Apply dtbo 0 Uncompressing Kernel Image ... OK kernel loaded at 0x01080000, end = 0x02958a00 libfdt fdt_getprop(): FDT_ERR_NOTFOUND Loading Ramdisk to 338a9000, end 33e729db ... OK Loading Device Tree to 000000001ffee000, end 000000001ffff4ba ... OK fdt_instaboot: no instaboot image Starting kernel ... uboot time: 10673245 us domain-0 init dvfs: 4 efuse_pw_en: 0x17 mgSz=0xf14a00 avb2: 1 Start read misc partition datas! 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->crc32 = -1075449479 active slot = 0 active_slot is normal ab_suffix is avb_slot_verify.c:524: DEBUG: Loading vbmeta struct from partition 'vbmeta'. [ 0.000000@0] Reserved memory: unable to setup CMA region [ 0.232780@0] VMAP:handle_vmap_fault address ffffff802008c000 out of range [ 0.232811@0] VMAP:handle_vmap_fault PC is:ffffff800923ffac, copy_mount_options, LR is:ffffff800923ff18 copy_mount_options [ 0.232823@0] VMAP:handle_vmap_fault task:32 kdevtmpfs, stack:ffffff8020088000, ffffffc039b4c920 [ 0.292767@0] codec_mm_module_init [ 0.308808@0] clkmsr c110875c.meson_clk_msr: failed to get msr ring reg0 [ 0.318963@0] cvbs_out: chrdev devno 263192576 for disp [ 0.605302@0] dmi: Firmware registration failed. [ 0.609965@0] vout: error: invalid vinfo1. current vmode is not supported [ 1.113429@0] mtdoops: mtd device (mtddev=name/number) must be supplied [ 1.136727@0] c81004c0.serial: clock gate not found [ 1.201690@0] c1108700.serial: clock gate not found [ 1.208084@0] amlogic-new-usb3 d0078080.usb3phy: This phy has no usb port [ 1.221872@0] meson-remote c8100580.rc: don't find the node <led_blink> [ 1.222855@0] meson-remote c8100580.rc: don't find the node <led_blink_frq> [ 1.242998@0] get fclk_div5 err [ 1.243029@0] vdin_drv_probe: vdin cannot get msr clk !!! [ 1.246410@0] get fclk_div5 err [ 1.249154@0] vdin_drv_probe: vdin cannot get msr clk !!! [ 1.258102@0] amlvideo2 probe called [ 1.258499@0] amlvideo2 probe called [ 1.262238@0] PPMGRDRV: err: ppmgr_driver_probe called [ 1.275314@0] meson-mmc: >>>>>>>>hostbase ffffff800852e000, dmode [ 1.322938@0] meson-mmc: >>>>>>>>hostbase ffffff8008538000, dmode [ 1.364658@0] meson-mmc: >>>>>>>>hostbase ffffff8008584000, dmode [ 1.405674@0] cectx c810023c.aocec: cec driver date:Ver 2019/1/7 [ 1.405674@0] [ 1.408712@0] cectx c810023c.aocec: not find 'port_num' [ 1.413325@0] cectx c810023c.aocec: using cec:0 [ 1.417582@0] cectx c810023c.aocec: get sleep state error! [ 1.423053@0] cectx c810023c.aocec: no hdmirx regs [ 1.427606@0] cectx c810023c.aocec: no hhi regs [ 1.432116@0] cectx c810023c.aocec: no periphs regs [ 1.436874@0] cectx c810023c.aocec: not find 'output' [ 1.446186@0] cectx c810023c.aocec: irq cnt:1 [ 1.447448@0] cectx c810023c.aocec: wakeup_reason:0x0 [ 1.451342@3] cectx c810023c.aocec: cev val1: 0x0;val2: 0x0 [ 1.456741@3] cectx c810023c.aocec: aml_cec_probe success end [ 1.500395@3] defendkey c8834500.defendkey: Reserved memory is not enough! [ 1.508953@3] snd_pcm_dai: aml audio pcm dai pinmux set error! [ 1.510988@3] meson-gxl-pinctrl pinctrl@4b0: pin GPIODV_24 already requested by c1108500.i2c; cannot claim for d0042000.snd_dmic [ 1.520660@3] meson-gxl-pinctrl pinctrl@4b0: pin-73 (d0042000.snd_dmic) status -22 [ 1.528150@3] meson-gxl-pinctrl pinctrl@4b0: could not request pin 73 (GPIODV_24) from group dmic_in_dv24 on device pinctrl-meson [ 1.539787@3] snd_dmic d0042000.snd_dmic: Error applying setting, reverse things back [ 1.547558@3] snd_dmic d0042000.snd_dmic: pinctrls error! [ 1.553602@3] spdif-dit spdif_codec: audio_spdif_out_mute can't get pinctrl [ 1.559899@3] spdif-dit spdif_codec: audio_spdif_in_mute can't get pinctrl [ 1.566611@3] spdif-dit spdif_codec: audio_spdif_in can't get pinctrl [ 1.786402@3] aml_meson_snd_card aml_sound_meson: ASoC: no source widget found for LOUTL [ 1.788912@3] aml_meson_snd_card aml_sound_meson: ASoC: Failed to add route LOUTL -> direct -> Ext Spk [ 1.798095@3] aml_meson_snd_card aml_sound_meson: ASoC: no source widget found for LOUTR [ 1.806104@3] aml_meson_snd_card aml_sound_meson: ASoC: Failed to add route LOUTR -> direct -> Ext Spk [ 2.356007@3] hub 2-0:1.0: config failed, hub doesn't have any ports! (err -19) [ 2.357781@3] usb usb2: Unsupported device [ 2.479442@2] thermal: read num_of_pp failed [ 2.774292@2] init: Init cannot set 'ro.boot.selinux' to 'permissive': Read-only property was already set [ 2.778390@2] init: Init cannot set 'ro.boot.selinux' to 'permissive': Read-only property was already set [ 2.807119@2] init: waitid failed: No child processes [ 2.811722@2] init: Unable to set property 'ro.product.first_api_level' to '28' in property file '/prop.default': Read-only property was already set [ 2.822498@2] init: Unable to set property 'ro.treble.enabled' to 'true' in property file '/prop.default': Read-only property was already set [ 2.833683@2] init: Unable to set property 'ro.adb.secure' to '1' in property file '/prop.default': Read-only property was already set [ 2.852316@2] init: Unable to read config file '/system/etc/init': open() failed: No such file or directory [ 2.856701@2] init: Unable to read config file '/product/etc/init': open() failed: No such file or directory [ 2.866440@2] init: Unable to read config file '/odm/etc/init': open() failed: No such file or directory [ 2.875842@2] init: Unable to read config file '/vendor/etc/init': open() failed: No such file or directory [ 2.898792@1] ueventd: Unable to read config file '/vendor/ueventd.rc': open() failed: No such file or directory [ 2.903600@1] ueventd: Unable to read config file '/odm/ueventd.rc': open() failed: No such file or directory [ 2.913543@1] ueventd: Unable to read config file '/ueventd.amlogic.rc': open() failed: No such file or directory [ 3.544760@2] init: setpgid failed for console: Operation not permitted [ 0.000267] Starting recovery (pid 2730) on Sun Jan 1 00:00:14 2017 [ 0.000574] led_ctrl_init in [ 0.000593] recovery filesystem table [ 0.000609] ========================= [ 0.000624] 0 /odm ext4 /dev/block/odm 0 [ 0.000648] 1 /product ext4 /dev/block/product 0 [ 0.000663] 2 /vendor ext4 /dev/block/vendor 0 [ 0.000678] 3 /bootloader emmc /dev/block/bootloader 0 [ 0.000693] 4 /logo emmc /dev/block/logo 0 [ 0.000708] 5 /vbmeta emmc /dev/block/vbmeta 0 [ 0.000723] 6 /recovery emmc /dev/block/recovery 0 [ 0.000738] 7 /boot emmc /dev/block/boot 0 [ 0.000752] 8 /misc emmc /dev/block/misc 0 [ 0.000767] 9 / ext4 /dev/block/system 0 [ 0.000784] 10 /vendor ext4 /dev/block/vendor 0 [ 0.000799] 11 /odm ext4 /dev/block/odm 0 [ 0.000815] 12 /param ext4 /dev/block/param 0 [ 0.000829] 13 /product ext4 /dev/block/product 0 [ 0.000845] 14 /metadata ext4 /dev/block/metadata 0 [ 0.000859] 15 /tee ext4 /dev/block/tee 0 [ 0.000874] 16 /cache ext4 /dev/block/cache 0 [ 0.000889] 17 /data ext4 /dev/block/data 0 [ 0.000904] 18 /sdcard vfat /dev/block/mmcblk1p1 0 [ 0.000919] 19 /sdcard vfat /dev/block/mmcblk1p2 0 [ 0.000933] 20 /sdcard vfat /dev/block/mmcblk1p3 0 [ 0.000948] 21 /sdcard vfat /dev/block/mmcblk1p4 0 [ 0.000962] 22 /sdcard vfat /dev/block/mmcblk1p5 0 [ 0.000977] 23 /sdcard vfat /dev/block/mmcblk1p6 0 [ 0.000992] 24 /sdcard vfat /dev/block/mmcblk2p1 0 [ 0.001007] 25 /sdcard vfat /dev/block/mmcblk2p2 0 [ 0.001021] 26 /sdcard vfat /dev/block/mmcblk2p3 0 [ 0.001035] 27 /sdcard vfat /dev/block/mmcblk2p4 0 [ 0.001054] 28 /sdcard vfat /dev/block/mmcblk2p5 0 [ 0.001070] 29 /sdcard vfat /dev/block/mmcblk2p6 0 [ 0.001085] 30 /sdcard vfat /dev/block/mmcblk 0 [ 0.001099] 31 /udisk auto /dev/block/sd## 0 [ 0.001113] 32 /tmp ramdisk ramdisk 0 [ 0.001127] # [ 3.827385@3] meson-gxl-pinctrl pinctrl@4b0: request() failed for pin 22 [ 3.828453@3] meson-gxl-pinctrl pinctrl@4b0: pin-22 (aml_sound_meson) status -22 [ 3.835813@3] meson-gxl-pinctrl pinctrl@4b0: could not request pin 22 (GPIOH_6) from group i2s_am_clk on device pinctrl-meson [ 3.847090@3] aml_meson_snd_card aml_sound_meson: Error applying setting, reverse things back [ 2.022123] E:failed to mount /udisk (No such file or directory) [ 2.022735] W:try mount /dev/block/mmcblk1p1 ... [ 2.122967] W:try mount /dev/block/mmcblk1p1 ... [ 2.223206] W:try mount /dev/block/mmcblk1p1 ... [ 2.323437] W:try mount /dev/block/mmcblk1p1 ... [ 2.423658] W:try mount /dev/block/mmcblk1p1 ... [ 2.523885] W:try mount /dev/block/mmcblk1p1 ... [ 2.624114] W:try mount /dev/block/mmcblk1p1 ... [ 2.724369] W:try mount /dev/block/mmcblk1p1 ... [ 2.824599] W:try mount /dev/block/mmcblk1p1 ... [ 2.924827] W:try mount /dev/block/mmcblk1p1 ... [ 3.025058] W:try mount /dev/block/mmcblk1p1 ... [ 3.125296] W:try mount /dev/block/mmcblk1p1 ... [ 3.225524] W:try mount /dev/block/mmcblk1p1 ... [ 3.325753] W:try mount /dev/block/mmcblk1p1 ... [ 3.425980] W:try mount /dev/block/mmcblk1p1 ... [ 3.526203] W:try mount /dev/block/mmcblk1p1 ... [ 3.626419] W:try mount /dev/block/mmcblk1p1 ... [ 3.726720] W:try mount /dev/block/mmcblk1p1 ... [ 3.826870] W:try mount /dev/block/mmcblk1p1 ... [ 3.927019] W:try mount /dev/block/mmcblk1p1 ... [ 4.029552] E:failed to mount /sdcard (No such file or directory) [ 4.034195] E:Can't read /cache/recovery/last_locale: No such file or directory[ 7.592926@0] systemcontrol: [ubootenv] upgrade_step is not a ubootenv variable. [ 7.600347@3] selinux: avc: denied { set } for property=const.filesystem.mode pid=2730 uid=0 gid=0 scontext=u:r:recovery:s0 tcontext=u:object_r:aml_display_prop:s0 tclass=property_service permissive=1 [ 7.600347@3] [ 7.619424@3] systemcontrol: /etc/mesondisplay.cfg:12: Expected keyword, got '/etc/mesondisplay.cfg:12'.systemcontrol: getBootEnv key:ubootenv.var.reboot_mode_android value:normalsystemcontrol: reboot_mode :normal [ 4.034322] locale is [en-US] [ 4.034363] stage is [] [ 4.034400] reason is [(null)] [ 7.660021@3] init: No such service 'hdcp_tx22' for ctl.stop [ 7.684027@0] selinux: avc: denied { set } for property=vendor.display-size pid=2730 uid=0 gid=0 scontext=u:r:recovery:s0 tcontext=u:object_r:netflix_prop:s0 tclass=property_service permissive=1 [ 7.684027@0] [ 7.699611@1] selinux: avc: denied { set } for property=persist.vendor.sys.hdr.state pid=2730 uid=0 gid=0 scontext=u:r:recovery:s0 tcontext=u:object_r:vendor_persist_prop:s0 tclass=property_service permissive=1 [ 7.699611@1] [ 5.038907] loaded /etc/recovery.kl [ 5.038964] skipping malformed recovery.lk line: back_door [ 5.038986] recovery key map table: [ 5.039000] 0 type:select value:28 key:97 28 15 158 -1 -1 [ 5.039016] 1 type:down value:108 key:108 114 109 -1 -1 -1 [ 5.039030] 2 type:up value:103 key:103 104 115 -1 -1 -1 [ 5.039045] [ 5.039058] loaded /etc/recovery.kl [ 5.039072] skipping malformed recovery.lk line: back_door [ 5.039087] recovery key map table: [ 5.039101] 0 type:select value:28 key:97 28 15 158 -1 -1 [ 5.039115] 1 type:down value:108 key:108 114 109 -1 -1 -1 [ 5.039130] 2 type:up value:103 key:103 104 115 -1 -1 -1 [ 5.039144] [ 5.039157] W:Failed to read max brightness: No such file or directory [ 5.039172] I:Screensaver disabled [ 5.039186] cannot find/open a drm device: No such file or directory [ 5.039201] fb0 reports (possibly inaccurate): [ 5.039216] vi.bits_per_pixel = 32 [ 5.039230] vi.red.offset = 16 .length = 8 [ 5.039244] vi.green.offset = 8 .length = 8 [ 5.039258] vi.blue.offset = 0 .length = 8 [ 5.074880] framebuffer: 0 (1280 x 720) [ 5.165868] erasing_text: en (47 x 19 @ 700) [ 5.168412] no_command_text: en (83 x 19 @ 700) [ 5.170989] error_text: en (33 x 19 @ 700) [ 5.784010] installing_text: en (156 x 19 @ 700) peed-profile [ 6.509285] pm.dexopt.first-boot=quicken [ 6.509301] ro.adb.secure=1 [ 6.509315] ro.secure=1 [ 6.509329] sys.usb.config=mtp [ 6.509342] sys.usb.configfs=1 [ 6.509357] log.tag.stats_log=I [ 6.509371] ro.logd.size.stats=64K [ 6.509384] ro.af.client_heap_size_kbyte=1536 [ 6.509399] ro.audio.mapvalue=0,0,0,0 [ 6.509413] ro.media.maxmem=419430400 [ 6.509426] ro.media.camera_usb.faceback=false [ 6.509441] ro.media.camera_preview.maxsize=1920x1080 [ 6.509455] ro.media.camera_preview.usemjpeg=1 [ 6.509470] ro.media.camera_preview.limitedrate=1920x1080x30,1280x720x30,640x480x30,320x240x28 [ 6.509485] drm.service.enable=true [ 6.509500] media.arm.audio.decoder=ape,flac,dts,ac3,eac3,wma,wmapro,mp3,aac,vorbis,raac,cook,amr,pcm,adpcm,aac_latm,rm [ 6.509516] media.wfd.use-pcm-audio=false [ 6.509530] media.wfd.video-bitrate=2000000 [ 6.509544] media.wfd.videoframerate=24 [ 6.509558] media.wfd.videoresolution-type=1 [ 6.509572] media.wfd.videoresolution-group=0 [ 6.509586] media.secmem.version=1 [ 6.509600] media.decoder.vfm.defmap=decoder [ 6.509614] media.decoder.vfm.drmmap=decoder [ 6.509628] media.amplayer.enable=true [ 6.509641] media.amplayer.thumbnail=true [ 6.509655] media.amplayer.dropwaitxms=100 [ 6.509669] media.amplayer.seekkeyframe=true [ 6.509683] media.amplayer.dsource4local=1 [ 6.509697] media.amplayer.enable-acodecs=ac3,eac3,rm,dts [ 6.509711] media.amplayer.widevineenable=true [ 6.509725] media.libplayer.seek.fwdsearch=1 [ 6.509740] media.libplayer.modules=vhls_mod,dash_mod,curl_mod,prhls_mod,vm_mod,bluray_mod [ 6.509755] media.libplayer.curlenable=true [ 6.509769] media.amsuperplayer.enable=true [ 6.509783] media.amsuperplayer.defplayer=PV_PLAYER [ 6.509797] media.amsuperplayer.m4aplayer=STAGEFRIGHT_PLAYER [ 6.509811] media.html5videowin.enable=1 [ 6.509825] persist.vendor.media.bootvideo=0050 [ 6.509839] ro.nrdp.modelgroup=SDMCs805 [ 6.509853] ro.nrdp.validation=ninja_6 [ 6.509867] ro.vendor.nrdp.audio.mixer.buffersize=1024 [ 6.509881] ro.vendor.nrdp.modelgroup=SDMCs805 [ 6.509895] ro.vendor.nrdp.validation=ninja_6 [ 6.509935] vendor.display-size=720x576 [ 6.509951] ro.boot.oem.key1=ATV00104319 [ 6.509965] pm.dexopt.shared=speed [ 6.509979] pm.dexopt.inactive=verify [ 6.509992] ro.boot.serialno=[REDACTED] [ 6.510006] ro.serialno=[REDACTED] [ 6.510020] service.adb.tcp.port=5555 [ 6.510034] security.perf_harden=1 [ 6.510047] net.bt.name=Android [ 6.510061] net.tethering.noprovisioning=true [ 6.510075] sys.fb.bits=32 [ 6.510089] sys.ignore.inativecec=true [ 6.510102] persist.sys.PQ.enable=true [ 6.510116] persist.sys.app.rotation=original [ 6.510130] persist.sys.dts.edid=false [ 6.510144] persist.sys.usb.config=mtp [ 6.510158] service.bootvideo=0 [ 6.510172] ro.vendor.app.optimization=true [ 6.510185] ro.vendor.vndk.version=26.1.0 [ 6.510199] ro.vendor.build.version.nts_patch=2019-10-17 [ 6.510214] ro.vendor.product.cpu.abilist=armeabi-v7a,armeabi [ 6.510228] ro.vendor.product.cpu.abilist32=armeabi-v7a,armeabi [ 6.510243] ro.vendor.product.cpu.abilist64= [ 6.510257] ro.vendor.autoconnectbt.isneed=false [ 6.510271] ro.vendor.autoconnectbt.btclass=50c [ 6.510285] ro.vendor.autoconnectbt.macprefix=00:CD:FF [ 6.510299] ro.vendor.autoconnectbt.rssilimit=70 [ 6.510314] ro.vendor.autoconnectbt.nameprefix=Amlogic_RC [ 6.510328] vendor.omx.osd_maxwidth=1280 [ 6.510342] vendor.omx.osd_maxheight=720 [ 6.510356] vendor.bluetooth.enable_timeout_ms=11000 [ 6.510370] persist.vendor.rtkbt.bdaddr_path=none [ 6.510384] persist.vendor.bluetooth.rtkcoex=true [ 6.841642] persist.vendor.bluetooth.prefferedrole=master [ 6.841670] persist.vendor.rtkbtadvdisable=false [ 6.841686] persist.vendor.sys.hdr.state=2 [ 6.841701] persist.vendor.sys.sdr.state=0 [ 6.841715] ro.vendor.platform.is.tv=0 [ 6.841729] ro.vendor.platform.is.supportHDR=false [ 6.841743] ro.vendor.platform.has.mbxuimode=true [ 6.841757] ro.vendor.platform.has.realoutputmode=true [ 6.841772] ro.vendor.platform.hdmi.device_type=4 [ 6.841786] ro.vendor.platform.need.display.hdmicec=true [ 6.841800] ro.vendor.platform.disable.audiorawout=false [ 6.841814] ro.vendor.platform.support.4k=false [ 6.841829] ro.vendor.platform.support.dts=true [ 6.841843] ro.vendor.platform.support.dolby=true [ 6.841857] ro.vendor.build.security_patch= [ 6.841871] ro.crypto.volume.filenames_mode=aes-256-cts [ 6.841885] [ 6.841898] Supported API: 3 [ 6.841912] #####bootable/recovery/recovery.cpp main 1791 [ 6.841970] #####bootable/recovery/recovery.cpp recopy_update_package 1538 fopen /cache/recovery/backup failed! (No such file or directory) [ 6.841989] #####bootable/recovery/recovery.cpp main 1795 update_package:(null) [ 6.842005] I:Saving locale "en-US" [ 6.509301] ro.adb.secure=1 [ 6.509315] ro.secure=1 [ 6.509329] sys.usb.config=mtp [ 6.509342] sys.usb.configfs=1 [ 6.509357] log.tag.stats_log=I [ 6.509371] ro.logd.size.stats=64K [ 6.509384] ro.af.client_heap_size_kbyte=1536 [ 6.509399] ro.audio.mapvalue=0,0,0,0 [ 6.509413] ro.media.maxmem=419430400 [ 6.509426] ro.media.camera_usb.faceback=false [ 6.509441] ro.media.camera_preview.maxsize=1920x1080 [ 6.509455] ro.media.camera_preview.usemjpeg=1 [ 6.509470] ro.media.camera_preview.limitedrate=1920x1080x30,1280x720x30,640x480x30,320x240x28 [ 6.509485] drm.service.enable=true [ 6.509500] media.arm.audio.decoder=ape,flac,dts,ac3,eac3,wma,wmapro,mp3,aac,vorbis,raac,cook,amr,pcm,adpcm,aac_latm,rm [ 6.509516] media.wfd.use-pcm-audio=false [ 6.509530] media.wfd.video-bitrate=2000000 [ 6.509544] media.wfd.videoframerate=24 [ 6.509558] media.wfd.videoresolution-type=1 [ 6.509572] media.wfd.videoresolution-group=0 [ 6.509586] media.secmem.version=1 [ 6.509600] media.decoder.vfm.defmap=decoder [ 6.509614] media.decoder.vfm.drmmap=decoder [ 6.509628] media.amplayer.enable=true [ 6.509641] media.amplayer.thumbnail=true [ 6.509655] media.amplayer.dropwaitxms=100 [ 6.509669] media.amplayer.seekkeyframe=true [ 6.509683] media.amplayer.dsource4local=1 [ 6.509697] media.amplayer.enable-acodecs=ac3,eac3,rm,dts [ 6.509711] media.amplayer.widevineenable=true [ 6.509725] media.libplayer.seek.fwdsearch=1 [ 6.509740] media.libplayer.modules=vhls_mod,dash_mod,curl_mod,prhls_mod,vm_mod,bluray_mod [ 6.509755] media.libplayer.curlenable=true [ 6.509769] media.amsuperplayer.enable=true [ 6.509783] media.amsuperplayer.defplayer=PV_PLAYER [ 6.509797] media.amsuperplayer.m4aplayer=STAGEFRIGHT_PLAYER [ 6.509811] media.html5videowin.enable=1 [ 6.509825] persist.vendor.media.bootvideo=0050 [ 6.509839] ro.nrdp.modelgroup=SDMCs805 [ 6.509853] ro.nrdp.validation=ninja_6 [ 6.509867] ro.vendor.nrdp.audio.mixer.buffersize=1024 [ 6.509881] ro.vendor.nrdp.modelgroup=SDMCs805 [ 6.509895] ro.vendor.nrdp.validation=ninja_6 [ 6.509935] vendor.display-size=720x576 [ 6.509951] ro.boot.oem.key1=ATV00104319 [ 6.509965] pm.dexopt.shared=speed [ 6.509979] pm.dexopt.inactive=verify [ 6.509992] ro.boot.serialno=[REDACTED] [ 6.510006] ro.serialno=[REDACTED] [ 6.510020] service.adb.tcp.port=5555 [ 6.510034] security.perf_harden=1 [ 6.510047] net.bt.name=Android [ 6.510061] net.tethering.noprovisioning=true [ 6.510075] sys.fb.bits=32 [ 6.510089] sys.ignore.inativecec=true [ 6.510102] persist.sys.PQ.enable=true [ 6.510116] persist.sys.app.rotation=original [ 6.510130] persist.sys.dts.edid=false [ 6.510144] persist.sys.usb.config=mtp [ 6.510158] service.bootvideo=0 [ 6.510172] ro.vendor.app.optimization=true [ 6.510185] ro.vendor.vndk.version=26.1.0 [ 6.510199] ro.vendor.build.version.nts_patch=2019-10-17 [ 6.510214] ro.vendor.product.cpu.abilist=armeabi-v7a,armeabi [ 6.510228] ro.vendor.product.cpu.abilist32=armeabi-v7a,armeabi [ 6.510243] ro.vendor.product.cpu.abilist64= [ 6.510257] ro.vendor.autoconnectbt.isneed=false [ 6.510271] ro.vendor.autoconnectbt.btclass=50c [ 6.510285] ro.vendor.autoconnectbt.macprefix=00:CD:FF [ 6.510299] ro.vendor.autoconnectbt.rssilimit=70 [ 6.510314] ro.vendor.autoconnectbt.nameprefix=Amlogic_RC [ 6.510328] vendor.omx.osd_maxwidth=1280 [ 6.510342] vendor.omx.osd_maxheight=720 [ 6.510356] vendor.bluetooth.enable_timeout_ms=11000 [ 6.510370] persist.vendor.rtkbt.bdaddr_path=none [ 6.510384] persist.vendor.bluetooth.rtkcoex=true [ 6.841642] persist.vendor.bluetooth.prefferedrole=master [ 6.841670] persist.vendor.rtkbtadvdisable=false [ 6.841686] persist.vendor.sys.hdr.state=2 [ 6.841701] persist.vendor.sys.sdr.state=0 [ 6.841715] ro.vendor.platform.is.tv=0 [ 6.841729] ro.vendor.platform.is.supportHDR=false [ 6.841743] ro.vendor.platform.has.mbxuimode=true [ 6.841757] ro.vendor.platform.has.realoutputmode=true [ 6.841772] ro.vendor.platform.hdmi.device_type=4 [ 6.841786] ro.vendor.platform.need.display.hdmicec=true [ 6.841800] ro.vendor.platform.disable.audiorawout=false [ 6.841814] ro.vendor.platform.support.4k=false [ 6.841829] ro.vendor.platform.support.dts=true [ 6.841843] ro.vendor.platform.support.dolby=true [ 6.841857] ro.vendor.build.security_patch= [ 6.841871] ro.crypto.volume.filenames_mode=aes-256-cts [ 6.841885] [ 6.841898] Supported API: 3 [ 6.841912] #####bootable/recovery/recovery.cpp main 1791 [ 6.841970] #####bootable/recovery/recovery.cpp recopy_update_package 1538 fopen /cache/recovery/backup failed! (No such file or directory) [ 6.841989] #####bootable/recovery/recovery.cpp main 1795 update_package:(null) [ 6.842005] I:Saving locale "en-US" 6.177150] ro.product.manufacturer=Amlogic [ 6.177164] ro.baseband=unknown [ 6.177178] ro.bootmode=unknown [ 6.177191] ro.hardware=amlogic [ 6.177205] ro.revision=0 [ 6.177219] ro.bootimage.build.date=Wed Mar 31 21:18:16 CST 2021 [ 6.177233] ro.bootimage.build.date.utc=1617196696 [ 6.177248] ro.bootimage.build.fingerprint=Amlogic/curie/curie:9/PI/20210331:user/release-keys [ 6.177263] ro.bootloader=unknown [ 6.177277] ro.debuggable=0 [ 6.177291] ro.property_service.version=2 [ 6.177305] sys.usb.state=mtp [ 6.177318] sys.usb.controller=c9100000.dwc2_a [ 6.177332] persist.sys.hdmi.keep_awake=false [ 6.177346] persist.sys.media.avsync=true [ 6.177360] persist.sys.dalvik.vm.lib.2=libart.so [ 6.177375] ro.sf.lcd_density=213 [ 6.177389] ro.sf.disable_triple_buffer=1 [ 6.177402] ro.boot.wificountrycode=XZ [ 6.177416] ro.hdmi.device_type=4 [ 6.177430] ro.radio.noril=false [ 6.177444] ro.zygote=zygote32 [ 6.177457] ro.opengles.version=131072 [ 6.177471] drm.service.enabled=1 [ 6.177485] camera.disable_zsl_mode=1 [ 6.177499] ro.config.low_ram=false [ 6.177513] ro.dalvik.vm.native.bridge=0 [ 6.177526] dalvik.vm.isa.arm.variant=cortex-a9 [ 6.177540] dalvik.vm.isa.arm.features=default [ 6.177555] dalvik.vm.dexopt.secondary=true [ 6.177569] dalvik.vm.usejit=true [ 6.177582] dalvik.vm.heapsize=384m [ 6.177596] dalvik.vm.dex2oat-Xms=64m [ 6.177610] dalvik.vm.dex2oat-Xmx=512m [ 6.177624] dalvik.vm.heapmaxfree=8m [ 6.177637] dalvik.vm.heapminfree=512k [ 6.177651] dalvik.vm.heapstartsize=8m [ 6.177665] dalvik.vm.appimageformat=lz4 [ 6.177679] dalvik.vm.usejitprofiles=true [ 6.177693] dalvik.vm.heapgrowthlimit=256m [ 6.177707] dalvik.vm.stack-trace-dir=/data/anr [ 6.177721] dalvik.vm.image-dex2oat-Xms=64m [ 6.177735] dalvik.vm.image-dex2oat-Xmx=64m [ 6.177749] dalvik.vm.heaptargetutilization=0.75 [ 6.177763] ro.boot.fake_battery=42 [ 6.177777] ro.vndk.version=28 [ 6.177790] ro.board.platform=gxl [ 6.177804] ro.vendor.build.date=Wed Mar 31 21:18:16 CST 2021 [ 6.177819] ro.vendor.build.date.utc=1617196696 [ 6.177833] ro.vendor.build.fingerprint=Amlogic/curie/curie:9/PI/20210331:user/release-keys [ 6.177848] ro.carrier=unknown [ 6.177862] ro.product.cpu.abilist32=armeabi-v7a,armeabi [ 6.177876] ro.product.cpu.abilist64= [ 6.177890] ro.product.board=curie [ 6.177904] ro.product.vendor.name=curie [ 6.177918] ro.product.vendor.brand=Amlogic [ 6.177932] ro.product.vendor.model=curie [ 6.177946] ro.product.vendor.device=curie [ 6.177960] ro.product.vendor.manufacturer=Amlogic [ 6.177974] ro.product.first_api_level=28 [ 6.177988] wifi.direct.interface=p2p0 [ 6.178002] wifi.interface=wlan0 [ 6.178016] ro.build.fingerprint=Amlogic/curie/curie:9/PI/20210331:user/release-keys [ 6.178030] pm.dexopt.boot=verify [ 6.178044] pm.dexopt.ab-ota=speed-profile [ 6.178058] pm.dexopt.install=speed-profile ----------------------------------------------- End log file

The TV box is equipped with an AP 6330 WiFi module. The Ethernet RTL module is 8911F.

In case someone finds this useful, I found a way to change the display mode from NTSC (default) to PAL NTSC to PAL: xrandr --output Composite-1 --set "TV mode" PAL xrandr --output Composite-1 --mode 720x576i PAL to NTSC: xrandr --output Composite-1 --set "TV mode" NTSC xrandr --output Composite-1 --mode 720x480i I thought I would have to recompile the whole kernel because the patch isn't working properly but these two commands did the trick. I don't know how to make this permanent but it works in the terminal.

Hi all, i've been going this forum long enough to try and root a tv box that i buyed recently, but this one is HEAVILY locked up, like nothing i have seen before. My objective here is to access 'su' so i can have access to rooting/overclocking this thing for emulators, and after that adding a heatsink, active cooling, etc. I tried ADB over all USBs (4 in total) but nothing. then i tried to see if root was available through some leftover app or vulnerability, but nothing. Then i tried following the specs from this thread (pretty similar in design to my PCB) but my UART displays nothing. (I leave the images from my setup below), i tried switching the wires, i tested the voltages and they return 3.3v, so they are ok. I tried the toothpick method to access recovery, but it has 2 buttons. 1 does nothing (AFAIK) and the other one goes directly to updating, so no menu. Any help is appreciated, as i'm out of any ideas. I leave my pictures below, and my specs: CPU: Alwinner H313 RAM: 1GB ROM: 8GB PCB: Z01S-v13.3, 2025.05.20 OS: Android 7-8 ish

Newbie on Armbian. I have an Allwinner H313 (confirmed) box that I want to to use as a basic Samba server. CPU:Allwinner H313Quad Core ARM Cortex A53 GPU:Mali-G31 OPenGL ES3.2 Memory:2GB Flash:16GB OS:Android 10.0 The actual firmware is a secure image and, no matter what procedure I do, I can't load any other image but the secure one. Debugging shows that 'fastbootd' has the "secure" flag set. My intention is to create a basic secure arm64 Debian image but I am having a hard time in doing so. Any ideas (specific Wiki, procedures) on how to create the secure image or "reset" the "secure" flag will be very appreciated. Thanks in advance.

DISCLAIMERS (PLEASE READ): - Everything in this post is provided AS-IS. This is not an official Armbian-supported target, and neither the Armbian project nor I am responsible for any damage, data loss, or broken devices caused by flashing or testing these images. - As with other TV boxes, please assume there may be board variants, undocumented hardware changes, weak power supplies, and marginal NAND/eMMC chips. Test carefully before writing anything to internal storage. - Please keep discussion and support in the forum thread, not in the official Armbian issue tracker. Hi all, I would like to share my work on bringing Armbian to Rockchip RK3128 TV boxes. These boxes are quite old now, and I do not think they are especially common anymore. Still, I suspect a lot of people may have one lying around somewhere in a drawer, unused after Android updates stopped or the original firmware became too slow to care about. I also had several of them lying around at home, which is what pushed me to start this project in the first place. Since I could not find an RK3128 Armbian effort comparable to the RK322x one, I decided to try doing the port myself. Another important motivation was simply to reduce e-waste: if even some of these old boxes can be turned into usable Linux machines again instead of being thrown away, that already feels worthwhile to me. First and foremost, I want to send special thanks to @jock and @fabiobassa for their RK322x TV box work on this forum. Their work was the foundation that made this RK3128 effort much easier to start from. 1. Main references and source code: Blog post with the full write-up: https://chieunhatnang.de/p/building-armbian-for-rockchip-rk3128/ Follow-up post for kernel 6.6.89 work: https://chieunhatnang.de/p/building-armbian-for-rockchip-rk3128-part-2/ Build scripts and releases: https://github.com/chieunhatnang-personal/RK3128-Linux-SupportingScripts RK3128 kernel 4.4 tree: https://github.com/chieunhatnang-personal/linux-kernel-4.4-rk3128-tvbox RK3128 kernel 6.6 tree: https://github.com/chieunhatnang-personal/linux-kernel-6.6-rk3128-tvbox 2. Current status At the moment I have two kernel lines: `4.4.194`, the older vendor-based line, which is already usable in practice `6.6.89`, the newer line, which allows these boxes to run a more up-to-date Armbian userspace What works in the current build: Custom U-Boot based on Rockchip U-Boot 2017.09 All four CPU cores, up to 1.2 GHz CPU frequency scaling and governors DRAM frequency control, both dynamic and fixed NAND, eMMC, SD card, and USB booting. The booting order is: USB >> SD Card >> NAND/eMMC (NAND and eMMC cannot be enabled at the same time because they share pins) OTG and EHCI/OHCI USB support Ethernet Wi-Fi support for SSV6051P, ESP8089, and several Realtek chips GPU acceleration UART1 and UART2, configurable Kernel `6.6.89` status in a bit more detail: CPU DVFS is stable after replacing the inherited/leakage-based OPP assumptions with a board-specific RK3128-safe table. The stable points I ended up using are `216 / 408 / 600 / 816 / 1008 / 1200 MHz` DMC / RAM devfreq works. In practice, simply enabling `dmc` works much better than I first expected, and boards can settle at different normal rates such as `396 MHz` or `456 MHz` GPU on `6.6.89` uses `Lima`, not the old Mali blob stack. That gives a maintainable Mesa/DRM path and hardware-accelerated OpenGL ES instead of depending on a legacy userspace blob VPU/video decode is still the weak point. I tried both `RKMPP` and `Hantro/V4L2` directions, but video processing is still limited, so I do not consider this a polished media-playback setup yet What does not work yet / known limitations: Bluetooth: not implemented or at least not validated, because I do not have a board with Bluetooth to test VPU / hardware video decoding is not in good shape yet SD card and SDIO Wi-Fi are currently using PIO mode on both kernel lines. This is slower than DMA, but stable enough for normal use 3. Image implementation I also made two RK3128 Armbian images based on existing RK322x Armbian images rather than building everything from scratch: Armbian 22.02: Based on the build provided by @jock, running kernel 4.4.189 Armbian 26.02: Based on the official Armbian build for rk322x, running kernel 6.6.89 In both cases, the idea was the same: keep the working RK322x Armbian userspace as a base, then replace the RK322x-specific parts with RK3128 ones, while the kernels themselves are based on Rockchip kernel sources. Compared with the original RK322x images, the RK3128 work mainly replaces or adds: boot.cmd / boot.scr changes so the boot flow can handle NAND and USB properly RK3128-specific Wi-Fi drivers and boot-time module loading logic rk3128-config a delayed Wi-Fi loader service RK3128-specific motd information the RK3128 kernel, DTB, and overlays For the `6.6.89` image specifically, there is some extra image-level cleanup and repackaging: remove the RK322x kernel / dtb / u-boot / BSP packages from the donor image pin those RK322x packages so they do not come back on upgrade install the RK3128 `6.6.89` Debian kernel packages rebuild the BSP package under the RK3128 name 4. Quick installation notes All required files are available from the releases page: The releaes page: https://github.com/chieunhatnang-personal/RK3128-Linux-SupportingScripts/releases Armbian 26.02 image: https://github.com/chieunhatnang-personal/RK3128-Linux-SupportingScripts/releases/download/kernel-6.6-armbian-26-v1.0/A26-release-20260415.zip Armbian 22.02 image: https://github.com/chieunhatnang-personal/RK3128-Linux-SupportingScripts/releases/download/kernel-4.4-armbian-22-v1.1/release-20260412.zip There are three installation layouts that are currently supported: 1. SD card only Pros: safest option, does not touch internal storage, easy to test and easy to remove, and if a board has an SD slot it can still be useful even when NAND/eMMC is completely dead Cons: slower than internal storage, and not every board has an SD slot Best for: first boot, testing, and boards where you want to keep the original Android install untouched 2. Full install to NAND / eMMC Pros: fastest and cleanest setup, uses the internal storage already present on the board Cons: overwrites the original Android install, and old NAND/eMMC may already be unreliable Best for: boards with healthy internal storage when you want a fully self-contained install 3. Hybrid install: bootloader on NAND / eMMC, rootfs on USB or SD card Pros: usually the most practical option for old TV boxes, works well when internal storage is only reliable enough for bootloader pieces, and can also help on boxes with problematic Android boot behavior Cons: more manual than the other methods, still depends on internal storage for the bootloader, and performance depends on the USB drive or SD card used Best for: boxes with weak or aging internal NAND/eMMC, or boxes where you want to avoid a full install to internal storage I describe each method in more detail below. 4.1. Install and boot from SD card Prepare: idbloader.img uboot.img trust.img rootfs.img Create an MBR partition table on the SD card, leave the first 16 MB empty, create one Linux partition, then write: idbloader.img to the raw device at seek=64 uboot.img to the raw device at seek=16384 trust.img to the raw device at seek=24576 rootfs.img to the first partition, not to the whole disk Example: DEV=/dev/sdX sudo parted -s "$DEV" mklabel msdos sudo parted -s "$DEV" mkpart primary ext4 16MB 100% sudo partprobe "$DEV" sudo dd if=idbloader.img of="$DEV" seek=64 conv=fsync sudo dd if=uboot.img of="$DEV" seek=16384 conv=fsync sudo dd if=trust.img of="$DEV" seek=24576 conv=fsync sudo dd if=rootfs.img of="${DEV}1" bs=4M status=progress conv=fsync sync I also provide a bootcardmaker.sh helper script in the same release directory to simplify this process. 4. 2. Full install to NAND / eMMC Prepare: rkxx_loader_vx.xx.xxx.bin parameter.txt uboot.img trust.img rootfs.img Then: Boot the board normally Connect a USB cable to the OTG port Open RKDevTool v2.69 In Advanced Function, erase the first 0x10000 sectors with Start LBA = 0x0 and Count = 0x10000 Press ResetDevice Wait for the board to return in MaskROM mode Go to Download Image Flash Loader, parameter, U-Boot, Trust, and rootfs 4. 3. Hybrid install: bootloader on NAND / eMMC, rootfs on USB or SD card This is the layout I use most often, and in practice it is probably the most useful one for old TV boxes. It is especially useful when internal NAND/eMMC is still good enough for Loader / parameter / U-Boot / Trust, but not reliable enough for a full root filesystem. A common symptom on these old boxes is that Android starts to boot and then hangs, or that the internal storage is simply too unreliable to trust with a full install. In this hybrid layout: Internal NAND/eMMC stores Loader, parameter, U-Boot, and Trust The root filesystem lives on USB or SD card Important: rootfs.img is a filesystem image, not a full disk image Write rootfs.img to a partition such as /dev/sdX1, not to the whole device Tools like BalenaEtcher are the wrong fit for this particular image layout Example: sudo dd if=rootfs.img of=/dev/sdX1 bs=4M status=progress conv=fsync sync 4.4. Post-install configuration After the board boots successfully, you can configure it either from the local console over HDMI or remotely over SSH if Ethernet is connected. Default login: user: root password: 1234 The first login will ask you to change the password. After that, run: rk3128-config This is the board-specific configuration tool for enabling and adjusting hardware features that may differ between RK3128 boxes. The most important options are: Wi-Fi chip selection RAM dynamic frequency: disabled by default. Enabling it can improve performance, but on some boards it may cause kernel hangs. If that happens, switch it back to disabled SD card storage enablement when booting from another device Display resolution OTG mode selection 5. Testing feedback is welcome If anyone here has RK3128 boards and wants to test, feedback would be very useful, especially for: Board photos and PCB markings Whether the board uses NAND or eMMC Boot method that works: SD, USB, NAND, eMMC Which Wi-Fi chip is present Serial logs, dmesg, and failure reports If there is enough interest and enough board coverage, I would be happy to keep improving this, cleaning it up further, and making it easier for other people to test. 6. Credits - @jock and @fabiobassa for the RK322x TV box work on the Armbian forum, which provided the main starting point, the images and practical reference for this RK3128 effort - Rockchip for the original kernel code base used as the foundation for both kernel lines

DISCLAIMERS (PLEASE READ): Everything you can find in this thread (binaries, texts, code snippets, etc...) are provided AS-IS and are not part of official Armbian project. For this reason not people from Armbian project nor myself are responsible for misuse or loss of functionality of hardware. THIS POST explains very well the troubles with TV Boxes and why they are not suitable for everyone Please don't ask about support or assistance in other non-community forums nor in the official Armbian github repository, instead post your questions in this thread, in the TV Boxes forum section (hardware related) or in the Peer-to-peer support section (general linux/software related). Following the recent thread on LibreElec forum about an unofficial image for rk3229 devices, I would like to make public the work made by me and @fabiobassa about bringing rk322x support to armbian. The project is now in -> mainline Armbian <- development fork -> here <- This first page and the last 3 or 4 pages of the thread are enough to get up to date with recent developments. Many useful experiences are scattered through the thread, but the most important things are collected here in the first page, so please read it carefully! Mainline kernel is fully supported and will receive most support in the future. Legacy kernel 4.4 is deprecated, but is kept around only for special purposes. What works: Should boot and work flawlessy on all boards with RK3228a, RK3228b and RK3229, with either DDR2 and DDR3 memories. Mainline u-boot Proprietary OPTEE provided as Trusted Execution Environment (needed for DRAM frequency scaling) All 4 cores are working Ethernet Serial UART (configured at 115200 bps, not 1.5Mbps!) Thermals, CPU and DRAM frequency scaling OTG USB 2.0 port (also as boot device!) EHCI/OHCI USB 2.0 ports MMC subsystem (including eMMC, SD and sdio devices) Hardware video acceleration NAND is available only on legacy kernel. To fully boot from NAND, use the Multitool and its steP-nand installation (instructions are below) Various WIFI over SDIO are supported (SSV6051P, SSV6256P, ESP8089, Realtek chips, etc...), ssv6256p driver is available only on legacy kernel Full GPU acceleration U-boot boot order priority: first the sdcard, then the USB OTG port and eventually the internal eMMC; you can install u-boot (and the whole system) in the internal eMMC and u-boot will always check for images on external sdcard/USB first. Unbrick: Technically, rockchip devices cannot be bricked. If the internal flash does not contain a bootable system, they will always boot from the sdcard. If, for a reason, the bootable system on the internal flash is corrupted or is unable to boot correctly, you can always force the maskrom mode shorting the eMMC clock pin on the PCB. Here there is the procedure, but you can also google around if you get stuck on a faulty bootloader, the technique is pretty simple and requires a simple screwdriver. There are however some unfortunate cases (expecially newer boards) where shorting the eMMC clock pin is difficult or impossibile, like eMMC or eMCP BGA chips with no exposed pins. In those cases pay double attention when burning something on the internal eMMC/eMCP and always test first the image from the sdcard to be sure it works before burning anything on eMMC/eMCP. Some useful links with pins, pads or procedures for some boards: Generic procedure for boards with non-BGA eMMC MXQPRO_V71 - eMCP H20 - eMCP ZQ01 - eMCP NAND vs eMMC vs eMCP difference: RK3228 and RK3229 tv boxes comes with three different flash memory chips: eMMC, NAND and eMCP. It does not depend upon the market name of the tv box and neither the internal board; manufacturers put whatever they find cheaper when they buy the components. NAND chip is just the non-volatile memory eMMC chip contains both the non-volatile memory plus a controller. eMCP chip contains the non-volatile memory, a controller for the non-volatile memory (like eMMC), but also contains a bank of DDR SDRAM memory on the same physical chip. The difference is very important, because eMMC and eMCP are far easier to support at various levels: the controller deals with the physical characteristics of the non-volatile memory, so the software has no to deal with. NAND chips instead are harder to support, because the software is required to deal with the physical characteristics and non-standard things that depends upon the NAND manufacturer. If you have a NAND chips you're unlucky because mainline kernel currently cannot access it, but also because you need special care and instructions explained later. You can discover if you have a NAND, eMMC or eMCP chip looking on the board are reading the signature on the flash memory chip. The Multitool (see later) also can detect which chip you have onboard: the program will warn you at startup if you have a NAND chip. NAND bootloader upgrade: IMPORTANT: don't do this is you have an eMMC or eMCP; skip this paragraph if you are unsure too! For very expert people who are having issues when (re)booting images, there is the chance to upgrade the bootloader on NAND. The NAND bootloader is nothing else than a regular idbloader (see official rockchip documentation) but contains some bits to correctly access the data on your flash memory. Upgrading requires to erase the existing flash content, in the worst case will require you to follow the Unbrick procedure above or restore an older but more compatible bootloader. If you are not mentally ready to overcome possible further issues, don't do this! The detailed instructions and the binaries are available at this post Multimedia: Mainline kernel: 3D acceleration is provided by Lima driver and is already enabled. Hardware video decoding: https://forum.armbian.com/topic/19258-testing-hardware-video-decoding-rockchip-allwinner/ Deprecated legacy kernel: multimedia features, like OpenGL/OpenGL ES acceleration, hardware accelerated Kodi, ffmpeg and mpv you can take a look to this post An effective tutorial from @Hai Nguyen on how to configure a box as a hi-quality music player using an USB audio card, and controlling it via remote control is available in this post Brief explanation about kernel naming: current kernel is the mainline LTS kernel version, most maintained and tested. This is the suggested version for production devices. If you don't know what to pick, pick this. legacy kernel (version 4.4) is provided by manufacturer; it is deprecated, unmaintained and not suggested. edge kernel is the development mainline kernel version, with experimental features and drivers; usually stable but perhaps suitable for production devices. You can switch from one kernel flavour to another using armbian-config or manually via apt. Installation (via SD card): Building: You can build your own image follow the common steps to build armbian for other tv boxes devices: when you are in the moment to choose the target board, switch to CSC/TVB/EOL boards and select "rk322x-box" from the list. Download prebuilt images from the following links: Archive builds (GPG-signed) - https://imola.armbian.com/dl/rk322x-box/archive/ SUGGESTED - Nightly built from trunk each week by Armbian servers (GPG-signed) - https://github.com/armbian/community Old images provided by me (unsigned and outdated) - https://users.armbian.com/jock/rk322x/armbian/stable Archived/older images: https://armbian.hosthatch.com/archive/rk322x-box/archive/ Multitool: The Multitool is a small but powerful tool to do quick backup/restore of internal flash, but also burn images and general system rescue and maintenance via terminal or SSH. Compressed images will be uncompressed on fly. Multitool - A small but powerful image for RK322x TV Box maintenance (instructions to access via network here) Quick installation instructions on eMMC: Build or download your preferred Armbian image and a copy of the Multitool; Burn the Multitool on an SD card; once done, place the Armbian image in images folder of the SD card NTFS partition; Plug the SD card in the TV box and plug in the power cord. After some seconds the blue led starts blinking and the Multitool appears; OPTIONAL: you can do a backup of the existing firmware with "Backup flash" menu option; Choose "Burn image to flash" from the menu, then select the destination device (usually mmcblk2) and the image to burn; Wait for the process to complete, then choose "Shutdown" from main menu; Unplug the power cord and the SD card, then replug the power cord; Wait for 10 seconds, then the led should start blinking and HDMI will turn on. The first time the boot process will take a couple of minutes or more because the filesystem is going to be resized, so be patient and wait for the login prompt. On first boot you will be asked for entering a password for root user of your choice and the name and password for a regular user Run sudo rk322x-config and select your board characteristics to enable leds, wifi chips, high-speed eMMC, etc... Run sudo armbian-config to configure timezone, locales and other personal options Congratulations, Armbian is now installed and configured! Despite the procedure above is simple and reliable, I always recommend to first test that your device boots Armbian images from SD Card. Due to the really large hardware variety, there is the rare chance that the images proposed here may not boot. If a bad image is burned in eMMC, the box may not boot anymore forcing you to follow the unbrick section at the top of this post. Quick installation instructions on NAND: Build or download your preferred Armbian image and a copy of the Multitool; Burn the Multitool on an SD card; once done, place the Armbian legacy kernel image in images folder of the SD card NTFS partition; Plug the SD card in the TV box and plug in the power cord. After some seconds the blue led starts blinking and the Multitool appears; OPTIONAL: you can do a backup of the existing firmware with "Backup flash" menu option; Choose "Burn Armbian image via steP-nand" from the menu, then select the destination device (usually rknand0) and the image to burn; Wait for the process to complete, then choose "Shutdown" from main menu; Unplug the power cord and the SD card, then replug the power cord; Wait for 10 seconds, then the led should start blinking and HDMI will turn on. The first time the boot process will take a couple of minutes or more because the filesystem is going to be resized, so be patient and wait for the login prompt. On first boot you will be asked for entering a password for root user of your choice and the name and password for a regular user Run sudo rk322x-config and select your board characteristics to enable leds, wifi chips, etc... Run armbian-config to configure timezone, locales and other personal options Congratulations, Armbian is now installed! Alternative: you can install the bootloader in NAND and let it boot from SD Card or USB: Download a copy of the Multitool and burn it on an SD card; Plug the SD card in the TV box and plug in the power cord. After some seconds the blue led starts blinking and the Multitool appears; RECOMMENDED: make a backup of the existing firmware with "Backup flash" menu option; Choose "Install Jump Start for Armbian" menu option: the Jump Start uses the internal NAND to boot from external SD Card or external USB Stick; Follow the general instructions to boot from SD Card below, skip the first erase eMMC step. Quick installation instructions to boot from SD Card: If you are already running Armbian from eMMC, skip to the next step. Instead if you are running the original firmware you need to first erase the internal eMMC; to do so download the Multitool, burn it on an SD Card, plug the SD Card and power the TV Box. Use "Backup flash" if you want to do a backup of the existing firmware, then choose "Erase flash" menu option. Build or download your preferred Armbian image; Uncompress and burn the Armbian image on the SD Card; Plug the SD Card in the TV Box and power it on; Wait for 10 seconds, then the led should start blinking and HDMI will turn on. The first time the boot process will take a couple of minutes or more because the filesystem is going to be resized, so be patient and wait for the login prompt; On first boot you will be asked for entering a password for root user of your choice and the name and password for a regular user Run sudo rk322x-config and select your board characteristics to enable leds, wifi chips, high-speed eMMC or NAND, etc... Run armbian-config to configure timezone, locales and other personal options, or also to transfer the SD Card installation to internal eMMC; Congratulations, Armbian is running from SD Card! A note about boot device order: With Armbian also comes mainline U-boot. If you install Armbian or just the bootloader in the eMMC or the Jump Start on internal NAND, the bootloader will look for valid bootable images in this order: External SD Card External USB Stick in OTG Port Internal eMMC Installation (without SD card, board with eMMC) If you have no sd card slot and your board has an eMMC, you can burn the armbian image directly on the internal eMMC using rkdeveloptool and a male-to-male USB cable: Download your preferred Armbian image from Armbian download page and decompress it. Download the rk322x bootloader: rk322x_loader_v1.10.238_256.bin Download a copy of rkdeveloptool: a compiled binary is available in the official rockchip-linux rkbin github repository. Unplug the power cord from the tv box Plug an end of an USB Male-to-male cable into the OTG port (normally it is the lone USB port on the same side of the Ethernet, HDMI, analog AV connectors) while pressing the reset microbutton with a toothpick. You can find the reset microbutton in a hole in the back of the box, but sometimes it is hidden into the AV analog jack Plug the other end of the USB Male-to-male cable into an USB port of your computer If everything went well, run lsusb: you should see a device with ID 2207:320b Run sudo rkdeveloptool rd 3 (if this fails don't worry and proceed to next step) Run sudo rkdeveloptool db rk322x_loader_v1.10.238_256.bin Run sudo rkdeveloptool wl 0x0 image.img (change image.img this with the real Armbian image filename) Unplug the power cord Done! Installation (without SD card, board with NAND) If you are in the unfortunate case you can't use an SD card for installation and your board has a NAND chip, you still have an option to use the quick Multitool installation steps via USB. Obtain a copy of rkdeveloptool: a compiled binary is available in the official rockchip-linux rkbin github repository. Unplug the power cord from the tv box Plug an end of an USB Male-to-male cable into the OTG port (normally it is the lone USB port on the same side of the Ethernet, HDMI, analog AV connectors) while pressing the reset microbutton with a toothpick. You can find the reset microbutton in a hole in the back of the box, but sometimes it is hidden into the AV analog jack Plug the other end of the USB Male-to-male cable into an USB port of your computer If everyting went well, using lsusb you should see a device with ID 2207:320b Run sudo rkdeveloptool wl 0x4000 u-boot-main.img (download u-boot-main.img.xz , don't forget to decompress it!) Unplug the power cord Now you can follow the instructions on how to install on eMMC/NAND via SD card, just use instead an USB stick to do all the operations and plug it into the USB OTG port. Once you reboot, USB OTG port will be used as a boot device. NOTE: NAND users without SD slot may be unhappy to know that it will be difficult to do extra maintenance with Multitool in case something breaks in the installed Armbian system: installing u-boot-main.img makes the installed system unbootable because it is missing the NAND driver. Alternative backup, restore and erase flash for EXPERTS: These backup, restore and erase flash procedures are for experts only. They are kept here mostly for reference, since the Multitool is perfectly able to do same from a very comfy interface and is the suggested way to do maintenance. Backup: Obtain a copy of rkdeveloptool: a compiled binary is available in the official rockchip-linux rkbin github repository. If you prefer, you can compile it yourself from the sources available at official rockchip repository Unplug the power cord from the tv box Plug an end of an USB Male-to-male cable into the OTG port (normally it is the lone USB port on the same side of the Ethernet, HDMI, analog AV connectors) while pressing the reset microbutton with a toothpick. You can find the reset microbutton in a hole in the back of the box, but sometimes it is hidden into the AV analog jack Plug the other end of the USB Male-to-male cable into an USB port of your computer If everyting went well, using lsusb you should see a device with ID 2207:320b change directory and move into rkbin/tools directory, run ./rkdeveloptool rfi then take note of the FLASH SIZE megabytes (my eMMC is 8Gb, rkdeveloptool reports 7393 megabytes) run ./rkdeveloptool rl 0x0 $((FLASH_SIZE * 2048)) backup.data (change FLASH_SIZE with the value you obtained the step before) once done, the internal eMMC is backed up to backup.data file Restore: first we have to restore the original bootloader, then restore the original firmware. Running rkdeveloptool with these switches will accomplish both the jobs: ./rkdeveloptool db rk322x_loader_v1.10.238_256.bin Downloading bootloader succeeded. ./rkdeveloptool ul rk322x_loader_v1.10.238_256.bin Upgrading loader succeeded. ./rkdeveloptool wl 0x0 backup.data Write LBA from file (100%) Download here: Erase the flash memory: clearing the internal eMMC/NAND memory makes the SoC look for external SD Card as first boot option. If there isn't any suitable SD Card, the SoC enters maskrom mode, which can then be used for full eMMC/NAND access using rkdeveloptool. This is perfectly fine if your box has an eMMC flash memory. NOTE: In case you have a NAND flash memory this option is however discouraged. The original bootloader contains some special parameters to correctly access the data. Clearing the flash memory will probably garbage the NAND data and restoring the bootloader may require some special instructions. Obtain a copy of rkdeveloptool: a compiled binary is available in the official rockchip-linux rkbin github repository. If you prefer, you can compile it yourself from the sources available at official rockchip repository Unplug the power cord from the board Plug an end of an USB Male-to-male cable into the OTG port (normally it is the lone USB port on the same side of the Ethernet, HDMI, analog AV connectors) while pressing the reset microbutton with a toothpick. You can find the reset microbutton in a hole in the back of the box, but sometimes it is hidden into the AV analog jack Plug the other end of the USB Male-to-male cable into an USB port of your computer If everyting went well, using lsusb you should see a device with ID 2207:320b run ./rkdeveloptool ef and wait a few seconds once done, the internal eMMC is erased and the device will boot from the sdcard from now on Partecipation and debugging: If you want to partecipate or need help debugging issues, do not hesitate to share your experience with the installation procedure of the boxes. In case of issues and missed support, provide as many as possible of these things is very useful to try and bring support for an unsupported board: some photos of both sides of the board. Details of the eMMC, DDR and Wifi chips are very useful! upload the device tree binary (dtb) of your device. We can understand a lot of things of the hardware from that small piece of data; and alternative is a link to the original firmware (you can do a full backup with the Multitool); dmesg and other logs (use armbianmonitor -u that automatically collects and uploads the logs online) attach a serial converter to the device and provide the output of the serial port; Critics, suggestions and contributions are welcome! Credits: @fabiobassa for his ideas, inspiration, great generosity in giving the boards for development and testing. The project of bringing rk322x into armbian would not have begun without his support! Justin Swartz, for his work and research to bring mainline linux on rk3229 (repository here) @knaerzche for his great contribution to libreelec support and mainline patches @Alex83 for his patience in testing the NAND bootloader upgrade procedure on his board @Jason Duhamell for his generous donation that allowed researching eMCP boards and esp8089 wifi chip

🏆 Become a sponsor, help to add other boards in armbian standart, you don't need to be a programmer to help the community, just need a copy of the ARM BOARD and a x86 computer to compile new versions. If you like what you see here and want to help: Donate Armbian the like button only costs a few dollars. Armbian Needs you help! Product Specification: Chipset: Rockchip RK3576 Octa Core ARM Mali G52 MC3 WIFI: WiFi6 11ax 1x1 80 MHz wifi controller: AP6275P RAM: DDR4 4GB/8GB ROM: eMMC 32GB/64GB/128GB OS: Android 14.0 || Armbian Vendor 6.1 Ethernet: 1000M Standard RJ-45 Bluetooth: BT 5.0 The RK3576 is indeed a lower-cost SoC but features four Cortex-A72 and four Cortex-A53 cores instead Android Base Files: H96-RK3576-ANDROID.dts H96-RK3576-ANDROID.dts H96-RK3576-BOX.dtb H96-RK3576-BOX.dtb RK3576_MiniLoaderAll.bin Vendor Kernel DTS: @RealAn H96-RK3576-VENDOR.dts Mainline status: Verify wifi controller: AP6275P Wifi Driver: https://drive.google.com/file/d/1n6x4tg5Xh24nWllOTJTq1ldVyDkK8W2Q/view?usp=sharing Flashing Tools: https://drive.google.com/file/d/1nLgPCBN0qmbzufWDFmISYc92JUpvwMPc/view?usp=sharing build_armbian.csc: https://drive.google.com/file/d/1VNR5QJlPylPsce9PI9O2TB3wOpshK2Bh/view?usp=sharing @hzdm Stock Firmware: method https://drive.google.com/file/d/1zLGvIxLE6vf8iSTjsyEr-Ly4MZ6ZahBB/view?usp=sharing Flashing Firmware Tutorial Factory Firmware for H96 Max M9 https://disk.yandex.ru/d/pWGEtRel0P9ejg https://drive.google.com/drive/folders/1g63F8fGSLEA9iK2_Mqzd6F0xfaTRnGlm?usp=sharing Factory Firmware for H96 Max M9S https://disk.yandex.ru/d/H17eGTYCjgmCsg https://drive.google.com/drive/folders/1Q360l5XbTVsWIvWkqy2xJ0sLpqHRSApM?usp=sharing TTL debug: RX TX GND pins: Enable SDCARD Reader: @rustamt method from 4pda Force board Maskrom Mode Maskrom Pins:

­DISCLAIMER (PLEASE READ): everything you can find in this thread (binaries, texts, code snippets, etc...) are provided AS-IS and are not part of official Armbian project. For this reason not people from Armbian project nor myself are responsible for misuse or loss of functionality of hardware. Please don't ask about support or assistance in other non-community forums nor in the official Armbian github repository, instead post your questions in this thread, in the TV Boxes forum section (hardware related) or in the Peer-to-peer support section (general linux/software related). Thank you! This thread is to give stable and mature long-term range support to rk3318/rk3328 found in many tv boxes in Armbian project as Community Supported Configuration (CSC). The current work is mainlined into Armbian project, but your mileage may vary; most recent developments live on my personal fork on github -> here <- Important notes: is just a personal opinion, but apparently widely supported, that rk3318 chip is not an official rockchip part. They probably are scrap rk3328 parts which have not passed conformance tests but are sold anyway to tv boxes manufacturers. They don’t reach the same operating frequency of the rk3328, have much higher leakage currents (and thus higher temperatures) and often the boards they are installed on are low quality with low quality components, in fact a very very common issue is the eMMC failure due to bad parts and bad soldering. So said, I personally suggest not to buy any rk3318 tv box, but instead find a properly supported SBC (Single Board Computer) if you need a reliable product. In the unfortunate case you already have such product, this thread may help you have some fun with them. What works: • Works on RK3318 and RK3328 TV boxes with DDR3 memories • Mainline u-boot • Mainline ATF provided as Trusted Execution Environment • All 4 cores are working • Ethernet • Serial UART (configured at stock 1.5Mbps) • Thermals and frequency scaling • OTG USB 2.0 port (also as boot device!) • EHCI/OHCI USB 2.0 ports and XHCI USB 3.0 ports • MMC subsystem (including , SD and sdio devices) • Hardware video acceleration (fully supported via RKMPP on legacy kernel, support via hantro and rkvdec kernel driver on mainline) • Various WIFI over SDIO are supported • Full acceleration on legacy kernel and mainline kernel • U-boot boot order priority: first the sdcard, then the USB OTG port and eventually the internal ; you can install u-boot (and the whole system) in the internal and u-boot will always check for images on external sdcard/USB first. Unbrick: Technically, rockchip devices cannot be bricked. If the internal flash does not contain a bootable system, they will always boot from the sdcard. If, for a reason, the bootable system on the internal flash is corrupted or is unable to boot correctly, you can always force the maskrom mode shorting the clock pin on the PCB. The procedure is explained here for rk322x, but for rk3318/28 is the same. In most of the rk3318/28 boards, shorting the clock pin is difficult or impossible because eMMC are BGA chips with no exposed pins. Pay double attention when burning something on the internal flash memory and always test first the image booting from the sdcard to be sure it works before burning anything in internal flash. This is a list of posts where forum users have been able to spot the eMMC clock pin to trigger the maskrom mode: H96 Max+ (board signature: RK3318_V1.4) by @Gausus X88 PRO 10 (board signature: X88_PRO_B) by @mathgaming HK1 Max (board signature YX_RK3318) by @Constantin Gatej Ninkbox N1 Max RK3318 by @enigmasphinx Hongtop H50 (board signature t98-3318-221-v11) by @GmP Partecipation and debugging: If you want to partecipate or need help debugging issues, do not hesitate to share your experience with the installation procedure of the boxes. In case of issues and missed support, provide as many as possible of these things is very useful to try and bring support for an unsupported board: some photos of both sides of the board. Details of the eMMC, DDR and Wifi chips are very useful! upload the device tree binary (dtb) of your device. We can understand a lot of things of the hardware from that small piece of data; and alternative is a link to the original firmware (you can do a full backup with the Multitool); dmesg and other logs (use armbianmonitor -u that automatically collects and uploads the logs online) attach a serial converter to the device and provide the output of the serial port; Multimedia: Mainline kernel: 3D acceleration is provided by Lima driver and is already enabled. Hardware video decoding: https://forum.armbian.com/topic/19258-testing-hardware-video-decoding-rockchip-allwinner/ Legacy kernel: If you need multimedia features, like OpenGL/OpenGL ES acceleration, hardware accelerated Kodi, ffmpeg and mpv you can take a look to this post Installation (via SD card): Building: You can build your own image follow the common steps to build armbian for other tv boxes devices: when you are in the moment to choose the target board, switch to /TVB/ boards and select "rk3318-box" from the list. Prebuilt images: Nightly stables - built from trunk by Armbian servers and GPG-signed: https://github.com/armbian/community Multitool: Multitool - A small but powerful image for RK3318/RK3328 TV Box maintenance. Download it from here Quick installation instructions on eMMC: Build or download your preferred Armbian image and a copy of the Multitool; Burn the Multitool on an SD card; once done, place the Armbian image in images folder of the SD card NTFS partition; Plug the SD card in the TV box and plug in the power cord. After some seconds the blue led starts blinking and the Multitool appears; OPTIONAL: you can do a backup of the existing firmware with "Backup flash" menu option; Choose "Burn image to flash" from the menu, then select the destination device (usually mmcblk2) and the image to burn; Wait for the process to complete, then choose "Shutdown" from main menu; Unplug the power cord and the SD card, then replug the power cord; Wait for 10 seconds, then the led should start blinking and HDMI will turn on. The first time the boot process will take a couple of minutes or more because the filesystem is going to be resized, so be patient and wait for the login prompt. On first boot you will be asked for entering a password for root user of your choice and the name and password for a regular user Run rk3318-config to configure the board specific options Run armbian-config to configure timezone, locales and other personal options Congratulations, Armbian is now installed! Despite the procedure above is simple and reliable, I always recommend to first test that your device boots Armbian images from SD Card. Due to the really large hardware variety, there is the rare chance that the images proposed here may not boot. If a bad image is burned in , the box may not boot anymore forcing you to follow the unbrick section at the top of this post. Quick installation instructions to boot from SD Card: If you are already running Armbian from eMMC, skip to the next step. Instead if you are running the original firmware you need to first erase the internal flash; to do so download the Multitool, burn it on an SD Card, plug the SD Card and power the TV Box. Use "Backup flash" if you want to do a backup of the existing firmware, then choose "Erase flash" menu option. Build or download your preferred Armbian image; Uncompress and burn the Armbian image on the SD Card; Plug the SD Card in the TV Box and power it on; Wait for 10 seconds, then the led should start blinking and HDMI will turn on. The first time the boot process will take a couple of minutes or more because the filesystem is going to be resized, so be patient and wait for the login prompt; On first boot you will be asked for entering a password for root user of your choice and the name and password for a regular user Run rk3318-config to configure the board specific options Run armbian-config to configure timezone, locales and other personal options, or also to transfer the SD Card installation to internal ; Congratulations, Armbian is running from SD Card! Tutorial - How to install Armbian on your TV Box (by @awawa) : https://www.hyperhdr.eu/2022/01/tv-box-mania-i-part-x88-pro-10.html A note about boot device order: With Armbian also comes mainline U-boot. If you install Armbian, the bootloader will look for valid bootable images in this order: External SD Card External USB Stick in OTG Port Internal The Multitool does not boot / How to burn image directly on eMMC: Some boards have the sdcard attached to an auxiliary (called also sdmmc_ext or external) controller which is not the common one. Forum findings declare that those boards are not able to boot from sdcard with stock firmware and they neither do in maskrom mode: the stock firmware always boots even if you put the multitool on sdcard. In such case, burning images directly on eMMC is the only way to have a working Armbian installation. You can follow these instructions by @fabiobassa to burn images directly on eMMC: https://forum.armbian.com/topic/17597-csc-armbian-for-rk3318rk3328-tv-box-boards/?do=findComment&comment=130453 Notes and special hardware: Script to change DDR memory frequency here Wireless chip AP2734, SP2734, HY2734C and similars: they are clones of AmPAK AP6334 which is combo wifi + bluetooth of broadcom BCM4334/B0 chips. You may need a special nvram file, instructions by @paradigman are here Critics, suggestions and contributions are welcome! Credits: @fabiobassa for his ideas, inspiration, great generosity in giving the boards for development and testing. The project of bringing rk3318 into armbian would not have begun without his support! @hexdump for his precious support in early testing, ideas and suggestions @MX10.AC2Nfor his patience in testing mxq-rk3328-d4 board support All the rockhip64 maintainers at Armbian project who have done and do most of the work to support the platform

I’m using the DEVMFC version [https://github.com/devmfc/debian-on-amlogic]. Additionally, I took the `/boot` partition and copied all the files from the Devmfc_Ubuntu-Oracular_6.12.11-meson64_Minimal-25.01.24.img.xz image. Then, I downloaded the same version available from the Armbian community, but with a graphical interface: Armbian_community_25.5.0-trunk.4_Aml-s9xx-box_noble_current_6.12.12_xfce_desktop.img.xz. I first flashed the Armbian image onto a USB drive. Then, in the `/boot` partition, I moved all existing root files into a `/backup` folder. After that, I copied the files from the DEVMFC version into the root of the `/boot` partition on the USB drive. Surprisingly, when I tried to boot this setup on a TV Box similar to the Vontar X4, which has an S905X4 processor, it actually booted! It prompted me to create a root password, a regular user, set the language, and select a time zone. Then, it successfully launched into X for the graphical interface. However, it seems that USB ports were either disabled, or the system froze—the login screen was visible, and the keyboard cursor was blinking, but no input was possible. I believe this is a solid starting point for getting Armbian images with a graphical interface running on S905X4 (Meson SC2), S905W2 (Meson S4), and S905Y4 (Meson S4) processors. Even without hardware-accelerated graphics, it should still be usable for basic applications like Notepad, text editors, spreadsheets, calculators, terminal access, and other simple tasks. Has anyone else made progress running Armbian on the S905X4?

I’m really happy to share that I finally managed to port the SV6256P (SSV6X5X) SDIO Wi-Fi driver from the legacy Linux 4.4 kernel to modern kernels. This repository contains my working port for Linux kernel 6.12 and newer, with updated mac80211/cfg80211 integration so the driver can build and run on recent Armbian systems. The chipset is commonly used in many low-cost TV boxes and embedded devices, but the original driver only supported legacy kernels (4.4). Now it’s functional again on modern systems, at least on my tested hardware (Allwinner H616 / X96 Q via SDIO). Repository link: https://github.com/cdhigh/armbian_sv6256p I’m quite excited to finally see this old Wi-Fi chip working on a 6.x kernel 🙂 [ 4.774151] ssv6x5x: importing configuration from /lib/firmware/ssv6x5x-wifi.cfg [ 4.778281] tu_ssv6xxx_sdio_init, probe @(____ptrval____) [ 4.779483] TU_SSV6XXX_SDIO mmc3:0001:1: Probing SDIO bus [ 4.779513] ssv6xxx_set_sdio_clk: set sdio clk 25000000Hz [ 4.799668] TU_SSV6XXX_SDIO mmc3:0001:1: vendor = 0x3030 device = 0x3030 [ 4.825421] TU_SSV6XXX_SDIO mmc3:0001:1: dataIOPort 0x10000 regIOPort 0x10020 [ 4.849181] TU_SSV6XXX_SDIO mmc3:0001:1: dataIOPort 0x10000 regIOPort 0x10020 [ 4.849530] TU_SSV6XXX_SDIO mmc3:0001:1: CHIP ID: SSV6006C0 [ 4.850373] ssv6x5x ops chk: tx=1 start=1 stop=1 config=1 add_if=1 rm_if=1 conf_filter=1 wake_txq=1 [ 4.850402] ssv6x5x chanctx chk: any=1 all=0 emulate=1 add=1 rm=1 chg=1 assign=0 unassign=0 [ 4.850409] ssv6x5x chanctx ops set but not complete [ 4.850424] Attach SSV6006 family HAL function [ 4.858285] MAC address from e-fuse [ 4.858311] EFUSE configuration [ 4.858315] Read efuse chip identity[79000000] ip link show: 6: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DORMANT group default qlen 1000 link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff

Currently working on a build for this device. It boots and is about 90% functional on 6.6 and 6.7 Kernel https://github.com/sicXnull/armbian-build/tree/X96Q-TVBOX-LPDDR3 Working - Desktop - Ethernet - Wifi Not working - DTS could use some work. Right now it does not detect internal EMMC so installing to EMMC is not an option. - Likely other things i've missed. I've uploaded two images to my git. Full w/Mate Desktop Minimal/Server Feel free to compile this yourself if you don't trust my images, it's encouraged. Changes are on the X96Q-TVBOX-LPDDR3 Branch Full W/Desktop ./compile.sh build BOARD=x96q-tvbox BRANCH=current BUILD_DESKTOP=yes BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no KERNEL_GIT=shallow RELEASE=bookworm Minimal/Server ./compile.sh build BOARD=x96q-tvbox BRANCH=current BUILD_DESKTOP=no BUILD_MINIMAL=yes EXPERT=yes KERNEL_CONFIGURE=no KERNEL_GIT=shallow RELEASE=bookworm

Recently has appeared some 3566 tv boxes in the wild, would be doable to run armbian on them? Since Rockchip seems kinda dedicated to openness the same goes for the RK3566?

@davem, I have similar X88 Pro TV box clone which got "X88PRO-RK3566-4D32-V2.1" written on the PCB. I was struggling to boot the system using SD card since the Android image that came with the box was not allowing. Thanks for sharing about the upgrade tool and modified x96x6.dtb. Without your posts I could not made it to work. I got "Armbian_community_26.2.0-trunk.792_Rk3566-box-demo_trixie_current_6.18.24_minimal.img.xz" successfully writte and booted. Later I have installed KDE based Desktop as well on 64GB Micro SD card. My USB 3.0 (the blue one) is somehow not working, Since I have a USB hub its not a deal breaker. Following are working properly as of now. Summary: Bluetooth - Working On Board LAN - 1000Mbps - Working. WiFI - connected to 2.4 Ghz network - Working. HDMI Display - Working. I have not test HDMI audio though. Sound - No 3.5mm Analog jack in this model. However the sound is working via Bluetooth head phone and Speaker with USB input/power. USB 2.0 - Connected Keyboard, mouse and speaker via USB 2.0 Hub - Working. USB 3.0 - This works fine when we boot in Android - Not working. Toss Link - Though the box got a port in the back, I don't have any device that can be connected - Not Tested. Note: I have windows 11 system as my desktop PC. I could not edit the Micro SD card created using BalenaEtcher. I had to use Ubuntu system in order to prepare the SD card and to edit the boot/armbianEnv.txt with fdtfile=rockchip/rk3566-box-X88PRO20.dtb

i have an android tv box. model name: tx 10 pro. i want to install ARMbian on it. there is a reset button under the av port. it has 2 gb of ram and 4 gb of rom (though the internet says 8G ram and 128G rom, also the android ui too). i have enabled both usb debugging and oem unlocking from the android developer option menu. the tv box can go to recovery mode using adb command. until going to the recovery mode, the adb connects perfectly but whenever it goes into recovery mode, the adb cant connect to the tv box. it consists option for fastboot inside the recovery mode but whenever i try to apply any command (e.g. fastboot/adb) the tv box doesnt show up among the devices when the device is in recovery mode. As there is no zip file for direct linux installation that i can use with flash from usb option. and the reset button beneath the av port does nothing, ive tried to flash multiple ARMbian Img files using both rufus and etcher but the screen just goes black whenever i press and hold the reset button beneath the av port. there is no option to install twrp as neither adb nor fastboot can connect whenever the device is in recovery mode. what to do?

Hello, sorry for my very bad english. I recently I bought a TV box with an h618 processor And I want to install Linux to make it a server but I only find images for the h616 processor, can I install one of these images on my TV box? It seems that the h616 processor and the h618 procesador are almost the same Thanks :D

Basically it has 1 gb ROM 8gb ram h3 chip and I HAVE put many img files on SD card NONE of them boot and as soon as I take the SD card out it boots into android perfectly fine... I'm lost on words and what to do I have also tried FEL mode on linux but the request times out with error -7 power supply is 5v 2a which is fine for this so not that and I'm using a 256gb a1 rated SD card. This is from a generic Chinese tv box called meecom and it has ADX-H-V1.0 written on it. I also changed the dtb files a lot but it still gave no display or sign that it was booted into armbian idk what to do help ( btw I repasted it that's why it has no thermal putty on it)

Good evening. Armbian for H313 X96-Q LPDDR3 TV-Box sicXnull/armbian-build) git clone --depth=1 --branch=main https://github.com/armbian/build "+CONFIG_SPL_IMAGE_TYPE_SUNXI_TOC0=y" in ~/build/patch/u-boot/u-boot-sunxi/board_x96q/arm64-sun1-h313-addr-x96q-lpddr3-defconfig.patch , adding secure-boot.patch and ~/build/patch/u-boot/u-boot-sunxi/board_x96q/sunsi-add-h616-internal-eth-phy-support.patch left untouched Android-boot.txt (normal boot sequence / eth & wlan=OK) Armbian_image_reboot_dmesg.txt Image reboot (sudo shutdown -r now) + dmesg log (wlan=OK, eth=not OK) Thanks in advance. Android-boot.txt Armbian_image_reboot_dmesg.txt

Hello, I have H96 Max TV box with RK3528 chip (4GB RAM, 64GB eMMC, Android 13, build RZX.V01.20240924). Board: RK3528_DDR3_8X4_V12. Problem: Box does not boot from TF card at all. No HDMI output, no DHCP lease, nothing. What I have: TF card slot on the box 1x USB 2.0 port, 1x USB 3.0 port No serial/UART adapter (DEBUG header visible on PCB but not connected) Android 13 still working on EMMC ADB access with root What I tried: Built Armbian with BOARD=rk3528-tvbox BRANCH=legacy BUILD_MINIMAL=yes RELEASE=trixie Extracted DTB from Android boot partition, added to image Wrote image to TF card with dd Verified RKNS header at sector 64 - correct Tried replacing idbloader with one from our custom U-Boot build Original U-Boot on EMMC appears to ignore TF card completely Question: How to make original U-Boot boot from TF card? Or is there a way to install Armbian to EMMC safely while keeping ability to recover? Device AIDA64 info: Model: H96_Max_RK3528 Device: rk3528_box Hardware: rk30board Thank you!

Hello everyone, I bought an H96 Max M9 TV box. I mainly use it for YouTube and watching movies, but later I wanted to use it for gaming, including emulators and modern community-made ports. This TV box, with its 8GB of RAM, has a lot of potential, but it is being wasted due to a common issue: the file manager. The problem is not the file explorer apps you install—I’ve tried them all—but the system’s storage manager (Android’s SAF), which seems to be poorly implemented or limited by the firmware. This causes issues such as: Selecting folders in PPSSPP (memory stick) Access for emulators like Dolphin Emulator Installing game ports that should run perfectly on this TV box, but cannot be installed due to bugs in the system file manager To be honest, I’m not very knowledgeable about these topics, but if anyone has experienced this or knows a possible solution and can share the information, I would really appreciate it in advance.

@jock Please help. Worst TV-box PCB I've ever seen in my life. Hardware: H96 Max "8K Ultra HD" (round case) PCB: RK3528_DDR3_8X4_V12 SoC: Rockchip RK3528 4GB DDR3 (8x Samsung K4B4G0446B) 64GB eMMC Samsung KLMCG2KETM WiFi: SKYWB8800 / SG-WB800E (AIC8800) Android 13, kernel 5.10.157, build RZX.V01.20240924.1740 I have TWO boards (same PCB revision, same markings). Both have DEBUG pads clearly labeled TX / GND / RX. UART completely silent in all combinations. Tried two different adapters: FTDI FT232 (ID 0403:6001) Silicon Labs CP2102 (ID 10c4:ea60) Both show up in dmesg fine, /dev/ttyUSB0 created, picocom opens. When powering device on — silence or garbage at all baud rates (115200, 230400, 460800, 921600, 1000000, 1152000, 1500000, 2000000, 3000000). Soldering done by a professional, crossover connection: adapter TX → board RX adapter RX → board TX GND ↔ GND VCC NOT connected (device powered separately) Loopback test on adapters works — adapters are OK. Devices are alive — Android boots normally, AIDA64 shows everything fine. Tested on both boards with both adapters — silence everywhere. Only garbage appears when physically jiggling wires (clearly body static, not device signal). My hypotheses: Vendor disabled UART output in stock loader/TPL for boot speed TX/RX pads repurposed as GPIO (LED / IR / etc.) DEBUG pads are actually NOT UART but JTAG/something else UART works but on some non-standard baud rate In fensoft U-Boot defconfig (https://github.com/fensoft/rk3528-tvbox) I see: CONFIG_BAUDRATE=1500000 CONFIG_DEBUG_UART_BASE=0xff9f0000 CONFIG_DEBUG_UART_CLOCK=24000000 Meaning fensoft uses this UART on similar boards. Why doesn't mine work? Background: spent 3 days trying to PXE boot Armbian. U-Boot (Ilya's + fensoft) works, TFTP/NFS works, kernel loads, initrd loads, DTB loads. But after booti the kernel dies instantly, so I need UART to see panic message. Tried many DTBs: evb1-ddr4, evb2-ddr3, android-native, nanopi-zero2, armsom-sige1, vontar-dq08, even stock Android DTB extracted from boot.img — all silent. Anyone experienced this on H96 Max RK3528 DDR3? Any way to force UART enable via some fastboot/adb command on Android before reboot? Attaching photos: PCB with RK3528_DDR3_8X4_V12 marking Close-up of DEBUG pads with soldered wires SG-WB800E WiFi module Thanks in advance for anyone who reads this!