April 9Apr 9 Hi, First of all i'd like to thanks thanks all of you for your job or questions that help me to rescue from trash rk3318 based devices. I recover from a friend a X88 pro 10 (4G/128G), witch is a really chip old android-box. I looking for making a media center running kodi and and minimal web browser for unsupported kodi streaming services. I successfully install armbian_community trunk (Rk3318-box_noble_current_6.xx.xx_xfce_desktop.img.xz) using multitool. Spoiler recover with original X88pro_B_rk3318_d4_11.0_SP6330_20210125_r1(X88pro10 1.0.1).img with Linux_Upgrade_Tool (RK-wiki | github) _ _ _ _ _ /_\ _ _ _ __ | |__(_)__ _ _ _ __ ___ _ __ _ __ _ _ _ _ (_) |_ _ _ / _ \| '_| ' \| '_ \ / _` | ' \ / _/ _ \ ' \| ' \ || | ' \| | _| || | /_/ \_\_| |_|_|_|_.__/_\__,_|_||_|_\__\___/_|_|_|_|_|_\_,_|_||_|_|\__|\_, | |___| |__/ v26.2 rolling for RK3318 Box running Armbian Linux 6.18.21-current-rockchip64 Packages: Ubuntu stable (noble) Support: for advanced users (rolling release) IPv4: (LAN) 192.168.xxx.xxx (WAN) xxx.xxx.xxx.xxx Performance: Load: 2% Uptime: 1d 22h 21m Memory usage: 14% of 3.87G CPU temp: 45°C Usage of /: 6% of 114G RX today: 1 MiB Tips: Becoming a sponsor? https://github.com/sponsors/armbian I run rk3318-config and choose this config: RK3318 (max 1.1Ghz...) no selection on eMMC additional speed options rk3318-box-led-conf2 X88_PR_B_boards Reboot and Install kodi and codec with : sudo apt install ffmpeg mpv kodi kodi-repository-kodi --install-recommends I have some issues : xfce menu is quite slow when I navigate for choosing app. chromium is very very slow and video on youtube are too lagy when decoding Kodi works on xfce but can't decode video, i try on standalone (choose on connection window), still can't decode. I looking on this post without success and this one, same issue. If anyone have a idea to help me to save this device and make me able to use it as a media center. Thanks
April 17Apr 17 @usual user can we achieve in browser video hardware acceleration now, and how? I tried many combinations with no success. Any suggestions are highly appreciated!
April 18Apr 18 22 hours ago, Sharkam said: can we achieve in browser video hardware acceleration now, and how? I haven't looked at this use case for a very long time. I can no longer remember since when it has worked out-of-the-box for me. Since decoder support has been part of the GStreamer framework for a very long time, hardware-supported video decoding works for all browsers that use this framework with the standard packages of the distribution of my choice. When v4lrequest support was still implemented with the out-of-tree patches using the stateful method, it also worked with Firefox out-of-the-box. Just an accordingly patched FFmpeg framework was required. This is likely no longer going to work with the current patches for the FFmpeg framework and requires an additional implementation in Firefox. I suspect, however, that this will only happen after the official inclusion of v4lrequest support in the FFmpeg framework, as is also the case with MPV. To what extent patches for Firefox are already available is unknown to me. For the distribution of my choice, I have in any case rebuilt the FFmpeg and MPV packages with the corresponding patches. I have to confess that I usually use Firefox and the video decoding works flawlessly for my use cases. However, I cannot say whether this is actually hardware-accelerated, because the SBCs I use with a graphical Desktop are powerful enough to function sufficiently even with only software decoding. I'm just taking the lazy way here and waiting for it to end up in Manline. For SBCs that need hardware acceleration, I simply use a browser that uses the GStreamer framework.
April 19Apr 19 Thank you very much for your reply! Which gstreamer based browser, as I tried epiphany in noble and it didn't seem to work.
April 19Apr 19 3 hours ago, Sharkam said: Which gstreamer based browser I usually use Falkon in a Plasma environment with Wayland backend.
April 22Apr 22 Hello I am trying to install armbian on this box (Bqeel U1 Max 4/128G but unable to boot multitool from SD. tried multiple cards and sw (rufus/etcher) does anyone know what could be the reason and how to solve it? I took pics and serial logs also of a successful factory boot. Spoiler sdfail.txt boot DC.txt
April 23Apr 23 ok found the issue, I got the wrong multitool image. the link on 1st post was broken returning 404 so I had to search elsewhere ended up choosing 322x folder instead of 3318. correct link to update 1st post https://users.armbian.com/users.armbian.com/jock/web/rk3318/
April 23Apr 23 Author @lsdlsd88 hello! Thanks for sharing the photos and the serial logs; it looks like the stock firmware did not pick up the sdcard at all. The sdcard seems to be detected, but for some reason the rockchip miniloader of the stock firmware does not it as first source. Are you able to retrieve the first 100-200 megabytes of the original firmware via serial? You should be able to use dd even within Android. edit: ah-ha ok, I understand! there is misconfiguration in the webserver and the link changes; thanks, I updated it!
May 14May 14 Hi everyone. I have this RK3318 chip box running Ubuntu, but I can't enable SSH to reinstall it. It doesn't have a display output port. Is there any way to reinstall the OS without desoldering the eMMC to reflash it? (I don't know how to put it back if I take it off). I've already tried flashing via USB and the RX/TX/GND lines, but neither worked. Model: AROP-01 CPU: Quad-core ARM processor Memory: 2GB System Storage: 64GB eMMC Network Interface: 1 × Ethernet USB Interface: 1 × USB Type-C Power: 5V/2A Dimensions: 103 × 103 × 20 mm Package Contents: 1 × Manual, 1 × Ethernet Cable, 1 × Power Cable Thank you.
May 17May 17 Hello everyone, I am reaching out to see if anyone in the community has successfully managed to get the internal Wi-Fi working on a box with the Realtek RTL8703bs chip. I have a MXQ Pro max (t9-RK3328) and I am using the latest Armbian build (Armbian_community_26.2.0-trunk.904_Rk3318-box_trixie_current_6.18.30_minimal.img.xz) provided by @jock for RK3318/RK3328 TV boxes. Here is the situation: 1. Using `rk3318-config` with `rk3318-box-led-conf1`, the chip is correctly powered and detected on the SDIO bus. 2. `dmesg` shows: `mmc1: new high speed SDIO card at address 0001`. 3. The hardware ID is confirmed as `024c:b703`. My questions : - Has anyone ever managed to make this specific chip (RTL8703bs) work on Armbian? - Does anyone have a patched driver (`.ko`), a specific `.dtbo` overlay, or a workaround that doesn't require recompiling the entire kernel from scratch? Here is my system log for reference: https://paste.armbian.com/ecadekazaz Thank you very much for your time and any advice you can share!
May 18May 18 Author @Suly rtl8703bs works with 8723cs driver, but the proprietary driver has been disabled so far in newer kernels because maintenance was becoming more and more complex. Actually I don't remember if it works with the mainline kernel driver. Probably it works, but I don't know if it is enable in rockchip64 kernel; it is surely enabled in rockchip armhf family.
May 19May 19 Hello @jock, thank you for the quick reply! Indeed, the drivers for the 8723cs have been disabled in the rockchip64 version, as confirmed by my config file: grep -i "8723" /boot/config-$(uname -r) # CONFIG_RTL8723CS is not set # CONFIG_RTW88_8723CS is not set I found 2 GitHub repos with the uncompiled drivers for the 8723cs chipset: - https://github.com/VictorIstratii151/rtl8703bs_rtl8723cs_linux_driver - https://github.com/TinkerBoard-Android/rockchip-android-external-wifi_driver/tree/android14-rockchip I tried to compile them natively on my machine but without success. They relies on Android-specific headers that are missing in Armbian. Regarding the rockchip armhf family you mentioned, do I need to completely reinstall Armbian on my board using a different image (the 32-bit armhf one)? Do I have to use the Armbian build framework to achieve this? Or is there a way/tool to cross-compile this specific module for my current 64-bit setup? Thanks again for your help!
June 23Jun 23 Hi, All. I've make brick X88 PRO B while update firmware. So, I'm trying recoverying from MASK ROM mode, PC recognized Rockchip USB VID/PID, but rockchip tool makes error like below, (in Admin mode with PowerShell or CMD prompt are same, even windows 10/11 ) using tool: GitHub - cpebit/rkdeveloptool-bin --------------------------------------------------------- PS C:\prog\rkdeveloptool-bin-master\bin> .\rkdeveloptool.exe ld DevNo=1 Vid=0x2207,Pid=0x320c,LocationID=201 Maskrom PS C:\prog\rkdeveloptool-bin-master\bin> .\rkdeveloptool.exe rd 3 Reset Device quit, creating comm object failed! --------------------------------------------------------- I'm tryed install a rockchip device driver but it not effects totally. GUI tools (like RKDevTool.exe ) also make error result. Please someone give me a hint that makes progress.... Thank you advance.
September 11Sep 11 Hi Jock, Thanks for the tutorials. Managed to installed on T9 RK3328_box. Currently updating armbian with few errors, managed them later. Box screen is shut tho, I've read somewhere earlier on how to fix it. Will do it later. Image from RK3328-Heltec Edited September 11Sep 11 by Hasrie Add image
September 12Sep 12 I fixed Wi-Fi association on my H96 Max V12 RK3318 (BCM4334/HS2734C SP). Armbian detected wlan0 and scanned 2.4/5 GHz networks, but every AP returned CTRL-EVENT-ASSOC-REJECT ... status_code=16 before WPA authentication. The issue was not the BCM4334 firmware binary: stock Android fw_bcm4334b1_ag.bin and Armbian /lib/firmware/brcm/brcmfmac4334-sdio.bin have the identical SHA-256 eb0d5c42a693651b3a5400b8b1c70807adeaf179cc7cc53ef611af09b76adf00. The fix was replacing only /lib/firmware/brcm/brcmfmac4334-sdio.rockchip,rk3318-box.txt with vendor/etc/firmware/nvram_4334.txt extracted from the matching stock Android 12 H96 Max V12 image, while preserving the box's real macaddr=. The generic Armbian AP6334 NVRAM differs in regulatory, PA/RSSI, RF switch-map, and 2.4/5 GHz power-calibration values. After reboot, the box connected to 5 GHz WPA2, received DHCP, and passed internet pings. I suggest offering this HS2734C/SP NVRAM as an optional AP6334 variant rather than replacing the generic default. Edited September 12Sep 12 by Opcode_0xFF
September 12Sep 12 Was getting U-Boot problem after crashing my network (DHCP was sending out wrong gateway IP). Have 1 old box with good working USB3 and eMMC and 2 newer with broken eMMC and not good working USB. It was the good one that running production HA and backup was well made but only on the eMMC . . . The U-boot was started from mmcblk2boot0 and trying loading the system from /dev/mmcblk0p1 and halting then can not load the root file system. Some repower was not working all time the same. So taking one of the not so good one down and moving the SD-card to the "good" one an its was booting the U-boot from the card and the system is loading OK from the eMMC !! Was looking in /boot/armbianEnv.txt but only rootdev=UUID was in it. Looking in /boot/boot.cmd and one nice setenv rootdev "/dev/mmcblk0p1" in it but shall not being changed. Putting in setenv rootdev "/dev/mmcblk2p1" power off and removing the SD-card and power on and booting OK but the network is one large mess and all automation is not done . . . After getting all in sync i rebooting the box and all is OK. So i hope its working then the system is being updated in the future. Is Arbian having some strange problems after last U-boot updates ? I have never seen the system using the eMMC mmcblk2boot0 or mmcblk2boot1 for loading the U-boot but now is using them but messing up the root partition from U-boot. All 3 Boxes is running v26.5.1 for RK3318 Box running Armbian Linux 6.18.44-current-rockchip64 sys upgrade to Ubuntu stable (resolute) TSL. Thanks in advance for great work done and hope all our boxes is going strong until some better mini SPC is coming for our system!!
September 17Sep 17 Author On 9/12/2026 at 7:03 PM, Opcode_0xFF said: The fix was replacing only /lib/firmware/brcm/brcmfmac4334-sdio.rockchip,rk3318-box.txt with vendor/etc/firmware/nvram_4334.txt extracted from the matching stock Android 12 H96 Max V12 image ... It is already mentioned in the first page under the "Special Hardware" paragraph.
September 20Sep 20 On 4/16/2021 at 10:30 AM, jock said: Multitool: Multitool - A small but powerful image for RK3318/RK3328 TV Box maintenance. Download it from here The link from the original post is dead
September 25Sep 25 Hey guys! I need some help getting Armbian booting on my Zidoo X7. Right now the box doesn't boot with the Armbian SD card. I will attach my UART logs,my DTS file i extracted using termux(i dont have root acess in termux but i dont know how i managed to extract it,oh well). Armbian image file : https://armbian.lv.auroradev.org/archive/rk3318-box/archive/Armbian_23.11.1_Rk3318-box_bookworm_current_6.1.63_minimal.img.xz Any help would be appreciated! (I am sorry if I hijacked this thread)armbianuartlogszidoox7.dts https://www.cnx-software.com/wp-content/uploads/2017/08/Z3328_V1.0-Board-Large.jpg (not my photo but i figured i should use this because its a very clear photo) Edited September 25Sep 25 by dougdimmadome
October 3Oct 3 Hey guys.Follow up: on zidoo x7.I got armbian working by burning the image to emmc via rkdeveloptool.I will post a walkthrough on how i got it working after a professional guides me on how to fix these issues.Issues i got:With the rk3318-box.dtb ethernet works just fine but my usb ports are dead,no voltage also,with rk3328-z28pro.dtb i got no ethernet but got usb.Is there any way in making my stock kernel 3.10.103 dts file i extracted from android work on here with modifications?zidoox7.dts Imagine i used: Armbian_23.11.1_Rk3318-box_bookworm_current_6.1.63.img EDIT: I will post a breif walkthrough(its NOT a tutorial) on how i got armbian on zidoo x7. DONT FORGET I AM NOT LIABLE FOR ANY DAMAGE OR WORSE BECAUSE OF THIS DTB OR OTHER STUFF.rk3328-zidoox7-custom.dtb I managed to write my own dtb,i integrated usb and ethernet support I took rk3328-z28pro.dts as a base (which had working USB) and modified the Ethernet node to use the internal PHY (ethernet@ff550000 set to okay with RMII mode) instead of the external RGMII controller (ff540000 set to disabled). rk3318-box.dtb rk3328-z28pro.dtb Edited October 3Oct 3 by dougdimmadome
October 3Oct 3 Hey guys! Follow up on the Zidoo X7. THIS IS ONLY FOR ZIDOO X7 (personal log,not a tutorial).Only try this if you are experienced with hardware tinkering.I am not tech support, and i am not responsible for bricked devices or damage. CRITICAL SAFETY WARNING (POWER SUPPLY LEAKAGE): A cheap or counterfeit adapter can leak hazardous mains voltage onto the DC ground line. Why this matters: Connecting via USB-A to USB-A can instantly DESTROY your host PC's motherboard or USB ports. It can fry your TV's HDMI ports or deliver a severe electric shock. Rule: If you feel even a mild tingling,DISCARD THAT POWER ADAPTER IMMEDIATELY and use a quality,isolated 5V DC supply. NOTE: Thermal throttling and other safety features are UNTESTED.Assume untested parts of the system are non-functional. Near the spdif audio port there is the rockusb flashing mode button hole,use a sim ejecter or something thin and low profile and hold it down while inserting the male to male usb cable. DOWNLOAD THE DTB FILE(WARNING: I ONLY TESTED USB AND ETHERNET SUPPORT,it was not thoroughly tested so use it ar ur own risk,if u need wifi and bluetooth u need to buy external wireless adapters that are linux supported,i will never add wifi and bluetooth support because its complicated and i am not smart enough) rk3328-zidoox7-custom.dtb The MicroSD card boot was causing me way too many issues, so I figured I should just erase my eMMC completely and flash Armbian directly onto it. I used rkdeveloptool on Linux for this. I know its probably not ideal to flash the raw armbian img file directly on the emmc but thats what I had success with, ur success may vary. PREREQUISITES: USB-A to USB-A cable: Premade Commercial Cable: If you use an off-the-shelf USB-A to USB-A cable (where +5V/VCC is connected), DO NOT plug in the DC barrel jack power supply at the same time. Let the TV box draw power directly through the host computer's USB port.Before proceeding,wait a little bit(maximum 2 minutes) so the capacitors discharge.Plug it into the box usb port labeled as "OTG". Why? Plugging in both the DC power supply and a standard USB cable causes a voltage conflict / backfeeding between the host PC and the box's power rail, which can destroy your computer's USB controller or the board! Image: Armbian_23.11.1_Rk3318-box_bookworm_current_6.1.63.img.xz (Don't forget to extract the .img file!) (image link is https://armbian.lv.auroradev.org/archive/rk3318-box/archive/Armbian_23.11.1_Rk3318-box_bookworm_current_6.1.63.img.xz) Loader: Download a loader such as rk3328_loader_ddr333_v1.14.249.bin STEP 1: CHECK DEVICE MODE First, run: sudo rkdeveloptool ld If it returns something along the lines of: DevNo=1 Vid=0x2207,Pid=0x320c,LocationID=202 Maskrom You are good to go But if it returns LOADER instead: DevNo=1 Vid=0x2207,Pid=0x320c,LocationID=202 Loader Run this to restart it in maskrom if it were in loader mode: sudo rkdeveloptool rd 3 After getting it out of loader proceed further. STEP 2: LOAD BOOTLOADER AND ERASE FLASH WARNING! THIS WILL COMPLETELY ERASE THE FLASH MEMORY. Always have a backup before proceeding (I don't know the command for backing up eMMC via rkdeveloptool, so do your research!). 1. Load the loader into RAM: sudo rkdeveloptool db rk3328_loader_ddr333_v1.14.249.bin (It should say "Downloading bootloader succeeded.") 2. Erase the flash memory: sudo rkdeveloptool ef STEP 3: WRITE ARMBIAN TO EMMC Write the image to sector 0: sudo rkdeveloptool wl 0 /path/to/Armbian_23.11.1_Rk3318-box_bookworm_current_6.1.63.img It should start saying "Write LBA from file" and slowly progress to 100%. This may take a few minutes, so be patient! Once finished, reboot the device: sudo rkdeveloptool rd It should (key word is SHOULD) now boot directly into Armbian. STEP 4: POST-INSTALLATION & FIXING USB PORTS If Armbian booted successfully: 1. Complete the initial setup process on screen or via serial console. 2. Plug in an Ethernet cable, find the IP address of the Zidoo X7 on your network, and SSH into it. 3. On ur linux host computer,do "scp /path/to/rk3328-zidoox7-custom.dtb userwithROOTacess@boxip:/tmp/" 4. SSH into it,run sudo cp /tmp/rk3328-zidoox7-custom.dtb /boot/dtb/rockchip/ 5. Edit your boot config file: sudo nano /boot/armbianEnv.txt You will see something like this: verbosity=1 bootlogo=false overlay_prefix=rockchip fdtfile=rockchip/rk3318-box.dtb rootdev=UUID=b82a1580-8fe4-456f-abe4-a32ca973b55e rootfstype=ext4 4. Replace: fdtfile=rockchip/rk3318-box.dtb With: fdtfile=rockchip/rk3328-zidoox7-custom.dtb 5. Save the file,run the command sync wait around 15s then reboot it. 6.Boot back into box,ssh into it back again,type sync just to make sure everything got saved. NOTE: If u used a wrong dtb file or did something and the box no longer boots,restart it,hook it up to UART and spam press CTRL + C very fast(it may take a lot of tries),u will be dropped on a prompt that looks like a smiley face "=>",remove every storage medium inserted in the tv box,identify how ur emmc identifies(i dont know the command so do ur research),in my case it was mmc erase 0 0x800000(it basically wipes the first 4gb of the EMMC),type reset,box will restart and redo all the steps. NOTE: Disabling kernel updates is recommended for increased stability on a tv box because a new update can introduce a bug or the dtb may not be read correctly,but it will leave the system a bit more vulnerable. UART PINS FOR ZIDOO X7(KEEP IN MIND WARNINGS) PLEASE NOTE IT USES 3.3V LOGIC NEVER USE A 5V ADAPTER LOGIC NOTE:1,500,000 bps for uart(1.5mbps) credits to this link for the original non edited image: https://www.cnx-software.com/wp-content/uploads/2017/08/Z3328_V1.0-Board-Large.jpg Doug Dimmadome, owner of the Dimmsdale Dimmadome Edited October 5Oct 5 by dougdimmadome
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.