rafman

@MMorales With my Compiled version of @Nick A github trunk with 6.7.12 kernel. I don't have problems except (Bluetooth). WiFi works and connects to my router. CPU Temp Sensor Works. OpenVfd is working. (with downloaded headers for 6.7.12) Sound is working LAN is Working. HDMI is working. Video (MPV with hardware Acceleration) seems to work Remote IR is working (with above .toml file and ir-keytables) Finally Only the BlueTooth is not Working.

For the Bluetooth : (my tv box is Transpeed 8k) I compile @Nick A gihub trunk with 6.7.12 kernel. I am still looking for a solution for Bluetooth. My dmesg shows : [ 17.147966] Bluetooth: RFCOMM TTY layer initialized [ 17.148004] Bluetooth: RFCOMM socket layer initialized [ 17.148113] Bluetooth: RFCOMM ver 1.11 [ 19.176140] Bluetooth: hci0: command 0x0c24 tx timeout [ 19.176239] Bluetooth: hci0: Opcode 0x0c24 failed: -110 [ 21.188126] Bluetooth: hci0: Opcode 0x0c24 failed: -110 [ 21.188163] Bluetooth: hci0: command 0x0c24 tx timeout [ 23.202926] Bluetooth: hci0: Opcode 0x0c24 failed: -110 [ 23.203000] Bluetooth: hci0: command 0x0c24 tx timeout [ 25.218922] Bluetooth: hci0: command 0x0c24 tx timeout [ 25.218925] Bluetooth: hci0: Opcode 0x0c24 failed: -110 [ 37.187145] Bluetooth: hci0: command 0x0c24 tx timeout [ 37.187148] Bluetooth: hci0: Opcode 0x0c24 failed: -110 [ 39.203189] Bluetooth: hci0: command 0x0c24 tx timeout [ 39.203190] Bluetooth: hci0: Opcode 0x0c24 failed: -110 Also kernel asks for an additional firmware blob file: (but i can't find it) [ 6.169613] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac4334-sdio.clm_blob failed with error -2 I already have place theese 2 files from (https://github.com/LibreELEC/brcmfmac_sdio-firmware) on my /lib/firmware and wifi seems to work (wlan0 is active) . brcmfmac4334-sdio.bin brcmfmac4334-sdio.txt as -rw-r--r-- 1 rafman rafman 398010 Oct 9 19:09 brcmfmac4334-sdio.transpeed,8k618-t.bin -rw-r--r-- 1 rafman rafman 2404 Oct 9 19:10 brcmfmac4334-sdio.txt My chip is this PS: @MMorales An other problem that i had, is when i switched to other kernel (like 6.10.9) from armbian-config or from command line, the system breaks and does not boot at all on next reboot. After that i found kernel headers for 6.7.12 here: https://mirrors.dotsrc.org/armbian-apt/pool/main/l/linux-headers-edge-sunxi64/linux-headers-edge-sunxi64_24.5.1_arm64__6.7.12-Sdacf-D440d-Pfa2b-Cdb7aH5c21-HK01ba-Vc222-Bf15a-R448a.deb and i was able to compile openvfd (with a small modification of openvfd_drv.c --> :629:35 by place a cast to (void *) NOW i can see the time on my Transpped LCD screen and i am testing further the driver.

For Transpeed 8k in order to make your IR remote to work with Armbian (it may works and with other H618 boxes, but i test it only on Transpeed 8k) do the following steps: 1> sudo apt-get install ir-keytable 2> copy the attached file transpeed-8k.toml to /etc/rc_keymaps/protocols/ 3> add the following line to your /etc/rc.local ir-keytable -p NEC -w /etc/rc_keymaps/protocols/transpeed-8k.toml It works with mpv / vlc /celluloid. Note: you can add any remote you have to your box by playing with ir-keytable is a very useful tool. transpeed-8k.toml

You can try but no guarantees (most likely you will break your installation) If you attempt to make it take care of your eMMC contents (you may destroy your Android) do it with your own risk.

This is not an easy job. if you try to attach an image that is build for a different board you will have incompatibilities and or hangs. Your current image is based on u-boot + kernel + patches.

@flikz I am glad to read that it works for your v5.1 board (your board is secure boot board). when you have time please post a photo of your board (if possible) it may help others. You can follow the bellow instructions to add hardware acceleration for your h264 videos on your Tv-Box. Is working for me (on bookworm). NOTE: Unfortunately hardware video acceleration is not completed yet but the above instructions seems to work with mpv. however when test it on (firefox / youtube) it does not makes any difference.

FYI: git clone https://github.com/sicXnull/armbian-build.git --branch X96Q-TVBOX-LPDDR3 --single-branch cd armbian-build ./compile.sh build BOARD=x96q-v1-3 BRANCH=current BUILD_DESKTOP=no BUILD_MINIMAL=no KERNEL_CONFIGURE=no RELEASE=bookworm build.log

@sicxnull Yesterday i make a fresh clone of : git clone https://github.com/sicXnull/armbian-build.git --branch X96Q-TVBOX-LPDDR3 --single-branch But when compile it I get an error [Error context msg [ Check MD5 sum of installed packages failed ..] I also tried to use FORCE_CHECK_MD5_PACKAGES=no but I receive the same error. after i clone the : git clone https://github.com/sicXnull/armbian-build.git and is compiled without errors, And finally i make a bookworm image (with secure boot) After i test the image on my tv-box (Z1): The Tv-box boots from SD card, however when i try to copy my image from SD card to eMMC then the Tv-box does not boot al all. I solve this problem with my old noble (secure boot) image (when i copy the bootloader to eMMC via armbian-config) Something is changed on u-boot ?

@eibrog I recompile it again because I deleted my old builds on my computer. You can download it Here: https://easyupload.io/58pgrm

@eibrog You can use the command: sudo armbian-config has similar functionality and capabilities if you want to customize your installation. NOTE: The errors you receive is from the dietpi script.

@eibrog I am glad to read that you succeed. This Tv-Box (Q1) works fine with Armbian. @svsruof You can also give a try with the above image to your box to see if Armbian is booting with secure boot.

Your Q1 box requires Secure boot image to boot. The first option is to compile Armbian yourself for secure boot using ( git clone https://github.com/sicXnull/armbian-build.git --branch X96Q-TVBOX-LPDDR3 --single-branch ) and by adding my patch or Nick A patch (attached above) if you are not familiar with compilation procedures I have uploaded my compiled image for you. Dowload it here : https://easyupload.io/86311i (it will remain for 30 days) ( I suggest you after download to uncompress the image is about 2.1 GB but if you use balena etcher is not necessary) Use balena etcher to burn it to your SD card and try to Boot you Q1 Box Normally your box will boot to Armbian. (Note that bluetooth and Wifi does not work at the moment because the driver for SV6256P is not availble yet) tell us about your results.

What you mean "flash" ? Tell us what you are doing. Did you try to boot Armbian on it ? Your box boots Android or is Bricked ?

No problem, everything is a lesson even if it succeeds or not. The good point of this research is that now i have two dead boxes alive and running (well). I made a free account on github and I order another one tv box (Transpeed 8k Android 12 TV BOX Allwinner H618 4GB Ram and 64 GB Rom) for further research (is on the way now).

Yes Keep going, your post was very useful for me. FYI: After problem is solved with the secure boot i tied to reproduce @Nick A patch myself using Nick A instructions I wanted to increase my git knowledge as many times i need to modify sources. so I deleted my old build and i make a fresh clone again and i applied the bellow instructions again. ---- git clone https://github.com/sicXnull/armbian-build.git --branch X96Q-TVBOX-LPDDR3 --single-branch cd ~/armbian-build ./compile.sh Ι Choose not to Change Kernel Configuration. I choose board menu click on "Show CSC/WIP/EOS/TVB" option then choose "x96q" I choose current/bookworm/server/Standard I stop the compilation process with Ctrl-C (after u-boot Receiving objects) cd cache/sources/u-boot-worktree/u-boot/v2024.01 sudo git add . sudo git commit --signoff sudo pico configs/x96q_lpddr3_defconfig I add CONFIG_SPL_IMAGE_TYPE_SUNXI_TOC0=y to the end of file and Save it. sudo openssl genrsa -out root_key.pem sudo git status sudo git add configs/x96q_lpddr3_defconfig sudo git add root_key.pem sudo git commit --signoff sudo git format-patch v2024.01 ---- here i had 2 files 0001-test.patch and 0002-configs-x96q-lpddr3.patch second file 0002-configs-x96q-lpddr3.patch was almost identical to Nick A file exept the (root_key.pem) contents however The prefix number was i a problem because if i used sudo mv 0002-configs-x96q-lpddr3.patch ~/armbian-build/patch/u-boot/u-boot-sunxi/ (without change prefix) compilation of armbian fails with reason (can't find file to patch at line..) and the patch execution order is 1st. if i remove the prefix execution order changes and the the patch is ok and armbian compiles. (after i realize that also Nick A patch does not have any prefix) I suppose that patch execution order is important, but how we control this order efficiently on a build system? Bellow are the final patches, both are working. configs-x96q-lpddr3-rafman.patch configs-x96q-lpddr3-Add-SECURE-BOOT.patch

@K R In the meantime you can try a Hack in order to boot Armbian to your box from miniarch image that boots with your box (MiniArch-20240715-6.10.10-board-h313.x96_q-SD-Image.img) i can't give any guarantee that it will succeeds but you can try it. (Warning if you are not familiar with below tools don't attempt to continue because if you make a mistake you may damage your hard drive) You will need : A PC with linux (Debian or ubuntu ) Gparted Disks utility (gnome-disks) An SD card 32GB (minimum) and an SD to USB card reader/adapter Balena Etcher (appimage) Armbian Image: https://github.com/sicXnull/armbian-build/releases/download/v24.8.0-trunk.425/Armbian-unofficial_24.11.0-trunk_X96q_bookworm_current_6.6.44_mate_desktop.img.xz Miniarch Image: MiniArch-20240715-6.10.10-board-h313.x96_q-SD-Image.img (you already have it) Steps: (Warning if you are not familiar with above tools don't attempt to continue because if you make a mistake you may damage your hard drive) 1:> Burn MiniArch-20240715-6.10.10-board-h313.x96_q-SD-Image.img using Balena Etcher to your SD card. 2:> After you Burn the image your SD Card will contain 2 partitions (BOOT, ROOT). 3:> Open gparted select your SD Card and remove/delete the ROOT partition on SD card. (apply all operations) 4:> create a new Ext4 partition on SD card (size at least 6 GB) and label it as ROOT. and (apply all operations) and after close gparted 5> unpack Armbian-unofficial_24.11.0-trunk_X96q_bookworm_current_6.6.44_mate_desktop.img.xz and now you will have --> Armbian-unofficial_24.11.0-trunk_X96q_bookworm_current_6.6.44_mate_desktop.img 5:> open Disks Utility, select your SD card on disks (left panel), and select ROOT partition (make it green on right panel) 6:> click on gear icon and select Restore Partition Image..., choose --> Armbian-unofficial_24.11.0-trunk_X96q_bookworm_current_6.6.44_mate_desktop.img When the process finish you will have BOOT, armbi_root partitions on your SD Card. Unmount/Remove and reinsert you SD Card to your PC. Open BOOT partition on SD card and remove/delete the bellow files: Image Image.gz open armbi_root/boot and copy the bellow files to BOOT/ armbianEnv.txt boot.bmp boot.cmd boot.scr config-6.6.44-current-sunxi64 initrd.img-6.6.44-current-sunxi64 --> rename to Image.gz System.map-6.6.44-current-sunxi64 uInitrd-6.6.44-current-sunxi64 vmlinuz-6.6.44-current-sunxi64 --> rename to Image Unmount the disks --> Insert SD card to your TV-Box and try to boot. With this method you don't need to modify the extlinux.conf, I have used his method to boot armbian when the it was not mature for my devices . Try it with you own risk, No guarantees. (if you encounter problems with Hdmi just wait for an upcoming release for your box) but if the system is booting you may have a working system from SD.

@Nick A @sicxnull According to device test results with secure boot image bellow. And because Bluetooth and WiFi does not work on both boxes Q1 and Z1 (same hardware except eMMC) I found and extract the Q1 stock android firmware dtb file (same hardware on both devices) and I need to modify or patch my local copy of (https://github.com/sicXnull/armbian-build.git --branch X96Q-TVBOX-LPDDR3 --single-branch) I want to ask if Android DTBs are Compatible with Armbian or they need additional maintenance ? Hardware is the bellow: wifi : SV6256P (Same on Z1 and Q1) Bluetooth: BR8052A01 (Same on Z1 and Q1) The android DTB for Q1 contains the below section information about BT and WiFi/Wlan: wlan { compatible = "allwinner,sunxi-wlan"; clocks = <0x1b>; pinctrl-0 = <0xd3>; pinctrl-names = "default"; wlan_busnum = <0x01>; wlan_power; wlan_io_regulator; wlan_regon = <0x53 0x06 0x12 0x01 0xffffffff 0xffffffff 0x00>; wlan_hostwake = <0x53 0x06 0x0f 0x06 0xffffffff 0xffffffff 0x00>; chip_en; power_en; status = "okay"; linux,phandle = <0x17d>; phandle = <0x17d>; }; bt { compatible = "allwinner,sunxi-bt"; clocks = <0x1b>; bt_power; bt_io_regulator; bt_rst_n = <0x53 0x06 0x13 0x01 0xffffffff 0xffffffff 0x00>; status = "okay"; linux,phandle = <0x17e>; phandle = <0x17e>; }; Were i have to place this information to recompile Armbian ? FYI: I attach bellow the full DTB and decompiled DTS file of Q1 tv-Box from Android stock firmware. Q1_device_tree.dtb.tar.gz Q1_device_tree.dts

Hello everyone. Here are the Test Results of my Z1 box. in the meantime i found that a another tv-box with almost identical hardware to Z1 (except the eMMC) is the Q1 box (photos included) Q1 Box also booting with the secure boot image of Armbian and runs well. Boards Specifications are: Processor: H313 (Same on Z1 and Q1) Emmc: (Kingston 16EMCP16 on Z1 - Micron JZ008 on Q1) pmic: AXP313a (Same on Z1 and Q1) wifi : SV6256P (Same on Z1 and Q1) Bluetooth: BR8052A01 (Same on Z1 and Q1) What Works (on both boxes) Boot from SD --OK Install to EMMC -- OK HDMI on Console -- OK Cpu Temp --Ok Ethernet --OK Sound --OK Video Playpack -- OK Onboard Led work only on Q1 on Z1 stays always blue. What does not Work (on both boxes) WiFi Adapter -- does not work Bluetooth -- does not work Bellow are the photos of Q1 Box (Manufacturer firmware is available for this box)

I solved the issue with Secure Boot today with your github branch (https://github.com/sicXnull/armbian-build.git --branch X96Q-TVBOX-LPDDR3 --single-branch) with an additional patch from @Nick A for SECURE BOOT. Right now i check further the box. NOTE: Take care with X96Q boxes from Alliexpress because you may receive Rockchip BOX (rk322x) that works, but is less powerfull than H313 and they stencil the chip as h313 there are lot of scammers. ( i Already have one ) Thanks again.

@Nick A Thanks for for the patch. With your patch I was able to compile Armbian and finally my dead box become Alive (up and running). it boots without problems. (i will check it further tonight) From your patch suppose that my mistake with git was that i did not edit the lines after sudo git commit --signoff on editor i just closed the editor, and for this reason sudo git format-patch v2024.01 not produce any patch file. I need more experience with git. Thanks again.

@sicxnull I confirm that I test: https://github.com/sicXnull/armbian-build/releases/download/v24.8.0-trunk.425/Armbian-unofficial_24.11.0-trunk_X96q_bookworm_current_6.6.44_mate_desktop.img.xz boots from eMMC and runs well on my old Z1 (x9q v1.3 lpddr3) variant. Ethernet, Hdmi, CPU Temp is working correctly now. Great job. PS: Unfortunately Z1 manufacturer changed the Hardware configuration on new tv-box version with different eMMC and the firmware requires secure boot TOC0 to boot. the above image is not working with the second newer Z1 device.

@Nick A With your command: sudo git format-patch -1 v2024.01 produced the file 0001-Prepare-v2024.01.patch (attached) i copy it to ~/armbian-build/patch/u-boot/u-boot-sunxi/ however patch is rejected with reason (reversed or previously applied patch detected) i think that something is going wrong with the patch file (it mainly contains names) FYI: i attach the patch file and the output output.txt 0001-Prepare-v2024.01.patch Untouched Armbian [ current/noble/server/Standard ] compiles successfully without issues.

@Lancoly Great news your board is booting. so you have a x96q v5.1 board. You will need to have a usb to ethernet adapter in order to complete installation on both ( miniarch and armbian) as on both the onboard ethernet is not working at this moment. The other way is to use USB tethering if you have a mobile phone (to share your data or wifi with your tv box) to complete your installation. instructions you can find here : https://www.geeksforgeeks.org/what-is-usb-tethering-and-how-to-enable-it/ just connect your box mobile phone enable usb tethering and you will have internet to complete installation. Please read this article about my experience with Armbian on x96q boxes : An other way is to try to compile armbian yourself and try to boot it. do the folloing steps: git clone https://github.com/sicXnull/armbian-build.git --branch X96Q-TVBOX-LPDDR3 --single-branch cd ~/armbian-build ./compile.sh Choose not to Change Kernel Configuration. choose board menu click on "Show CSC/WIP/EOS/TVB" option then choose "x96q" choose current/bookworm/server/Standard or Desktop if you prefer After a succesfull compilation Your image files should be in output/images directory. Burn image to sd card using balena etcher and try to boot your tv box. If compiled image does not boot at all then i will give you a hack with extlinux.conf to boot it. Note that i experienced problems with Hdmi on console, cpu temp , onboard Ethernet and eMMC/NAND boot fails. I need to make lot of tests this time. Please keep us informed about your progress.

@Nick A I am following your instructions step by step and i stucked on last step : I do the following steps : git clone https://github.com/sicXnull/armbian-build.git --branch X96Q-TVBOX-LPDDR3 --single-branch --OK (Resolving deltas: 100% (85645/85645), done.) cd ~/armbian-build --OK ./compile.sh --OK Ι Choose not to Change Kernel Configuration. --OK I choose board menu click on "Show CSC/WIP/EOS/TVB" option then choose "x96q" --OK I choose current/bookworm/server/Standard --OK I stop the compilation process with Ctrl-C (after u-boot Receiving objects) --Ok Then : cd cache/sources/u-boot-worktree/u-boot/v2024.01 --OK sudo git add . --OK (but here nothing asked about test) sudo git commit --signoff -- OK sudo pico configs/x96q_lpddr3_defconfig --OK I add CONFIG_SPL_IMAGE_TYPE_SUNXI_TOC0=y to the end of file and Save it. --OK sudo openssl genrsa -out root_key.pem --OK (file root_key.pem exists ok) sudo git status --OK (output bellow) ------------------------------------- (use "git add <file>..." to update what will be committed) (use "git restore <file>..." to discard changes in working directory) modified: configs/x96q_lpddr3_defconfig Untracked files: (use "git add <file>..." to include in what will be committed) root_key.pem ---------------------------------------- sudo git add configs/x96q_lpddr3_defconfig --OK sudo git add root_key.pem --OK sudo git commit --signoff --OK sudo git format-patch v2024.01 --OK At this point i don't see any .patch file to copy to ~/armbian-build/patch/u-boot/u-boot-sunxi/ with sudo git status I can see a list of files that are modified and root_key.pem is included as new file. if i do : sudo git diff --staged --patch > ~/armbian-build/patch/u-boot/u-boot-sunxi/test.patch or sudo git diff --cached > ~/armbian-build/patch/u-boot/u-boot-sunxi/mypatch.patch compilation fails with (Problem with ->mypatch(:1) (+804/-18)[52M, 5A] {sun50i-a64-recore.dts,cannot apply patch.....) something is wrong with the patch ! what do i make wrong ? FYI: (my git version is 2.34.1)

@Nick A I have trouble with this bricked board is a x96q variant (new) (older version with differen emmc boot miniarch), manufacturer firmware is not available but i am able to boot it with (iATV Q5 Stock Firmware) The board is booting from SD card (i used PhoenixCard.v4.2.4 to burn it as startup) and i am able to see the bootlogo but android does not start because on serial log i see that (rotpk is not written yet). I also decompiled the iATV Q5 Stock Firmware to fex files. firmware contains toc0.fex and toc1.fex The problem is that the board requires secure boot in order to boot. I am able to produce Open SSL certificate via (openssl genrsa -out root_key.pem) . How can I boot or compile Ambian for this secure boot device ? PS: if anyone has a working firmware for this device please provide link. Board Specifications are: Processor: H313 Emmc: Kingston 16EMCP16 (2GB Ram - 16GB Rom) pmic: AXP313a wifi : SV6256P BlueTooth: BR8052A01