Pita Bread

Some more details:
Ethernet is 100 Mbps (hardware). I have been struggling at first with armbian booting to a blank colored screen, with random color (pink, light blue, whatever). Turns out, my power supply cable was faulty and the ground connection was interrupted. This created an awkward situation where the power was circulating through the ground of the HDMI connection. Surprisingly this worked for the first stages of booting but soon would trigger the blank screen (I guess at the loading of the kernel framebuffer). as it should be known by reading the installation guides on the forum, the installation to eMMC must be done with the dedicated script, and not through armbian config; in the latter case, the device will be bricked. Of course I learned that the hard way. In my experience, re-flashing the original firmware via USB did not work, but it worked through the SD card. Hunting down the original Android image can be challenging as most links are dead/expired. I am attaching a `sbc-bench` run.  
The device is slow-ish but possibly usable for light tasks. Still, I think it's amazing I could salvage it, so thanks to the armbian community!
leelbox-s1.txt

TV Box Status Information Template Version 1.0
=======================================
TV Box Name: Leelbox S1 (PCB marking: "A95X_DDR4" "V1_1 2160906")
CPU: AMLogic S905X
RAM: 1 GB DDR4 (reported: 860 MiB) - 2 x SpecTek (Micron) "PPE05-075" "F1646"
Armbian build file name: Armbian_community 24.5.0-trunk.226
DTB file used: meson-gxl-s905x-p212.dtb
Kernel Version: Linux 6.6.22-current-meson64
Distribution Installed: Bookworm
Working Ethernet (Yes/No): Yes
Max Ethernet Speed that works (100/1000): to be verified
Does wifi work (Yes/No): Yes (RTL8189ETV)
Does bluetooth work (Yes/No): No
Does HDMI audio work (Yes/No): Not tested
 
Comments:
- also sold as ABOX-A1 according to online sources;
- installation to MMC worked without issue using the dedicated script.
 

Just for the record...
 
The image file I used to get my S905X3 box running was from this tutorial:
https://i12bretro.github.io/tutorials/0269.html
 
which references this site for the image file:
  https://drive.google.com/open?id=1n6CZa582uJECV3lzQDtFbmbyvmOSiUSg
 
The file is:
    Armbian_20.10_Arm-64_bullseye_current_5.9.0_desktop.img.xz
 
I used the dtb file  "meson-sm1-a95xf3-air.dtb"  from the Stable image referenced in SteeMans post.
 
This at least gets the board running and allows for an upgrade to the Debian Bullseye operating system using the apt-get command.
 
I can't get the current Stable images from the site referred to in SteeMans post here to work:
 
https://forum.armbian.com/topic/17106-installation-instructions-for-tv-boxes-with-amlogic-cpus/
 
Also the SHA checksums for these files don't seem to agree with the published value, so it may be there is some problem...
 
 
I hope this helps.
 

You are correct, none of the dtb's I tried from the release worked for me. Maybe I did not try them all!
 
That dtb had been downloaded and used by me about a year ago when I had made another attempt to install Armbian on my box. At the time installation process worked but the actual install was buggy.
 
Anyway I am happy to report that since yesterday's message, I made another attempt at installation and this time there were only minor issues whilst upgrading which were fairly easily resolved. I am sorry I cannot find the notes I took were I had recorded the actual error but I believe it was something about the system not able to register certain upgrades. These were then cleared and I had no further issues. I even went ahead and installed to EMMC with no issues whatsoever so now I don't need the SDcard anymore which I hope will improve the speed a bit as well as reliability. So far no more issues.
 
I have now only one question, given that I am now operating from EMMC, if in the future I would want to install a new upgrade how would I do it? Will installing from SDcard work or would it be sufficient to use the Upgrade Manager or sudo apt update; sudo apt upgrade?
 
Thanks.

Hi guys!
People on 4pda say that H96 Max x3, Vontar x3, HK1 Box and Transpeed X3 Air are the same hardware (last three even look the same ). I tried using @root-stas dtb file and it worked on Vontar x3. So I suggest to change topic name to include other boxes names - maybe that will gather more people in this thread. As of me expect known bugs my device can not detect all resolutions over HDMI. I have 1440p 75 Hz monitor and Armbian can detect only resolutions up to 1080p at 60 Hz. I'm experiencing color shifts as well. Most looks about right but grays are shifted towards yellowish red. If somebody is competent here enough to tell if these are device specific bugs or SoC/Armbian related please tell me so I can report it in right thread.

Here are modes detected on TV Box:

 
And here are modes detected on my laptop with Intel graphics running Ubuntu:

Here is color shift example:
grey

Thanks. But the newer version of the images  don't follow  same instructions and u-boot.ext was not working for me. So I started looking for the older image files

That worked perfectly for me. I have installed  it in eMMC and working great. Currently using  it as a headless server for my home network with Adguard and samba  server with External  HDD. USB 3.0 and  Gigabit Ethernet are working great.

The same story with Armbian on SD or USB. How to fix it?

Does anyone know what is the real specs of this board. I try to boot armbian in pendrive into it but it always boot to the android system or in recovery.  I try the different device tree but it always the same result. 
 
 

SOLVED !!
I have try using dtb for p281 and it's work right now, i search on google that p271 architecture is same with p281
Download armbian s9xx on here
I have use dtb file name is meson-gxl-s905w-p281.dtb on /dtb/amlogic
By following this step : 
Now it's work now
 
Thanks to armbian team and community !!

🏆 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
 
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
 
Force board Maskrom Mode
Maskrom Pins:
 

Thanks @SteeMan and @root-stas for your great support (without forgotten @balbes150 for his great job on Armbian)
 
Today's news:
1. I have burnt the version Armbian_20.05.4_Arm-64_bionic_current_5.7.0-rc6_20200518.img on the SD card with Etcher
2.  Copy u-boot.sd to u-boot.ext (impossible to boot on the SD card without this)
3. Modify uEnv.txt to choose meson-g12a-x96-max-no-cvbs DTB file in amlogic section:
4.  Boot on the SD card (with toothpick method because impossible with android update method due to error like this)
5.  Define root password and create user session
6. Force the Ethernet speed to 100Mb
sudo ethtool –s [device_name] speed 100 duplex full autoneg on 7. Now, I can use putty from another device to be connected on the TV Box !!!! 
 
 
Next step is to copy this configuration on the eMMC. So, I'm waiting your instructions to be sure that I can use this method:
cd /boot sudo cp u-boot.ext u-boot.sd cd sudo /root/install-aml.sh  

@Lotus09 I just made a video about gaming on RK3588.
Here my Mekotronics review video :
More video's on my channel about gaming on RK3588. It doesn't play every game, but enough to have a good time.

Hi all. 
Since I wanted a 3D intro for my Youtube Channel I started working with Blender again. Now the intro is finished I've got time to try to make a 3D Armbian Logo.
 

I'll show some of the progress here for those who are interested. And if anybody else wants to do the same, go  ahead. We can then compare the results.
I've only just begun. But I needed a break so I started writing this.
Here's how it begins... create a side view ... 


Then put those pictures in Blender, add a cube, position it right on both pictures, and start modeling....

All done with the NanoPi M4 on Armbian Bionic.

I'll slowly keep working on it. I can't promise it will look great, but nothing is lost if it doesn't... Someone once asked me to do this, I can't remember who it was. I think Chwe or jmcc or tido. Could also have been a ghost in my sleep.
Cheers, NicoD

ps: @Igor It would be nice if we could easily resize images in our posts. Maybe with a dropdown box and % would be easiest to do. I know this isn't a priority, just a suggestion. 
 

Hello !!
I ordered a box tv H96 MAX X3
 
With this configuration :
-CPU: Amlogic S905X3 quad core BRAS Cortex A55;
-GPU: ARM Mali-G31 MP2; - OS: Android 10.0;
-Memory: DDR3 4GB, eMMC 32/64GB/128GB
-Support: H.265, 8K @ 24fps, 4K @ 60fps, HD 2.1, USB3.0;
-Support 10/100M/1000M Ethernet, 2.4 and 5G dual Wifi,BT4.0;
I'd like to install Armbian on it to use it as a mini server.

Except that I'm a complete idiot when it comes to computers, and I've tried to follow tutorials I've already seen, but I can't get the hang of it.
I can't really find the right image and I don't really understand how to do it. 
When I try on my own and plug in my USB key, the box reboots in a loop and when I unplug it, it boots on Android.

Thank you, I'm also aware that I can "brick" it etc. .

Firstly, I would like to say I know next to nothing about what I am doing at all. I'm trying to learn though!
 
With the current shortage of decent SBCs at a reasonable price I thought being able to run Armbian on the above device would make it a very good deal.
 
I am only interested in using the device as a server so I currently have no information on running it as a desktop though I can burn an image and post the results if anyone is interested.
 
From reading the forums it seems many devices will try and boot from external storage of some sort before booting from emmc. This turned out not to be the case for this device.
 
I blundered about for a while just writing random stuff to sd cards and trying to boot, nothing worked.
 
I eventually connected a serial adapter to this board, there are holes on the board quite clearly marked, V,R,T and G. The baud rate is 1500000
 
Once I had done this, I realised how much earlier I should have done it, I now had a little light on what was going on.
 
It appeared from using printenv that the boot targets are set on this device to go for emmc first. There is no saveenv so this left me wondering how I was going to ever get it to boot without needing the serial adapter.
 
There appeared to be no option to boot from SD. What I did notice was that one of the boot targets was usb0 and so I wrote the Armbian_22.02.0-trunk_Station-m2_bullseye_legacy_4.19.219.img to a USB stick.
 
I replaced the rk3566-firefly-roc-pc.dtb with the one attached which I extracted from the Android firmware.
 
I then tried to boot from this by breaking into the boot sequence using ctrl-c and then used "run bootcmd_usb0".
 
I saw that it was trying to boot but then was unable to find the root filesystem. I now thought that USB wasn't compiled in/loaded at this stage and this led me to believe that I may be able to get this working by now adding an SD card with the same image on it.
 
This worked! I ended up with a login prompt and networking was working and I could SSH in.
 
So how now do I get it to boot from my combo?
 
I started by using fdisk and deleted all partitions on the emmc, this trashed everything and after restoring the android image back to the emmc using the rockchip recovery tool and a bit more reading, I could see that u-boot was on the second emmc partition.
 
There were actually 15 partitions on the emmc.
 
I now deleted all but the first two and issued the reboot command.
 
I still have no explanation for what happened next.
 
For some reason, the usb storage seemed no longer to be recognised but yet the first stage of the boot seemed to be happening but then it was crashing. I knew what the problem was from my earlier experimentation. When I wrote the SD card, I hadn't replaced the DTB as I believed I only needed the SD for the root filesystem. I quickly added the DTB so the SD and rebooted.
 
This was now successful. I was now booting from the SD card, something I hadn't seemed to be able to do from the u-boot command line, that will just be some error of mine.
 
I quickly added a partition to the emmc and copied the root filesystem there. I then updated the sd card extlinux to point to that emmc partition for the root filesystem and thats just about currently where I am at.
 
|_   _/ _ \| ___|  |  _ \| |_   _ ___
  | || (_) |___ \  | |_) | | | | / __|
  | | \__, |___) | |  __/| | |_| \__ \
  |_|   /_/|____/  |_|   |_|\__,_|___/
Welcome to Armbian 22.05.3 Bullseye with Linux 4.19.219-station-p2
System load:   2%               Up time:       7:36
Memory usage:  13% of 7.50G     IP:            192.168.50.29
CPU temp:      43°C             Usage of /:    6% of 58G
Last login: Sun Aug  7 23:34:24 2022 from 192.168.50.121
 
cat /proc/cpuinfo
processor       : 0
BogoMIPS        : 48.00
Features        : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
CPU implementer : 0x41
CPU architecture: 8
CPU variant     : 0x2
CPU part        : 0xd05
CPU revision    : 0
processor       : 1
BogoMIPS        : 48.00
Features        : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
CPU implementer : 0x41
CPU architecture: 8
CPU variant     : 0x2
CPU part        : 0xd05
CPU revision    : 0
processor       : 2
BogoMIPS        : 48.00
Features        : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
CPU implementer : 0x41
CPU architecture: 8
CPU variant     : 0x2
CPU part        : 0xd05
CPU revision    : 0
processor       : 3
BogoMIPS        : 48.00
Features        : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
CPU implementer : 0x41
CPU architecture: 8
CPU variant     : 0x2
CPU part        : 0xd05
CPU revision    : 0
Hardware        : Rockchip RK3566 BOX DEMO V10 ANDROID Board
Serial          : 399eb13dd69295ae
 
free
               total        used        free      shared  buff/cache   available
Mem:         7862464     1014552     6063900       61308      784012     6705776
Swap:              0           0           0
 
I really wish I could get the saveenv to work but I guess this means rebuilding u-boot and flashing that, then I could boot from emmc, I can already do that from the u-boot cli but I'm quite some reading and experimentation away from that.
 
I conclude from this though that there will never be a way to get to this stage without hooking up to a serial adapter first as I can see no way to delete those emmc partitions without that and so it will always try and boot the android first.
 
Maybe a custom firmware that only contains the u-boot? That too is much reading away.
 
I hope this all helps someone in some way, I wouldn't be where I am with this now without the help of this forum.
 
The box, by the way is this one: https://www.amazon.co.uk/gp/product/B098DY737L
 
The replacement dtb is attached.
 
I also managed to get Proxmox running on it
 
 
 
 
 
t95plus.dtb

@Pita Bread Instead of using nearly two year old images, it probably would be best to start with the most recent images: https://www.armbian.com/amlogic-s9xx-tv-box

2023-10-18
Today I will start with the second attemp to use ARMBIAN on a TV Box for a fully Linux desktop experience.

I gaved the old TV Box (T95 Max+) to one of my nephews as a retro game console with Emuelec (he was very pleased). I could make ARMBIAN work with the Ubuntu version from this link. I used the 6.1.11 jammy version. The user interface and the ethernet port worked well with the meson-sm1-a95xf3-air-gbit.dtb file. Sadly I could not make the sound or the wifi to work, but I could easily reach wifi connection through a USB Wifi Device.
 
I also changed the original device firmware for Aidan's ROM, which let me install a pure Android TV system on the TV Box, instead of the uglier original one.
 
Today I will start trying a new TV Box: the A95X F3 AIR, with 4 GB of RAM, 32 Gb of internal memory and 100 Mbits ethernet. I will let you know how the ARMBIAN experiment went.
 
 
 

Well, after trying all the DTB files, these are the results:
 
meson-sm1-a95xf3-air.dtb
Boots with a graphical user interface. Max Res 4K There is no WIFI connection There is no Ethernet connection There is no sound
meson-sm1-a95xf3-air-gbit.dtb
Boots with a graphical user interface. Max Res 1080p There is no WIFI connection It appears there is Ethernet connection There is no sound  
meson-sm1-bananapi-m2-pro.dtb
Boots with a graphical user interface. Max Res 1080p There is no WIFI connection It appears there is Ethernet connection There is no sound  
meson-sm1-bananapi-m5.dtb
Boots with a graphical user interface. Max Res 1080p There is no WIFI connection It appears there is Ethernet connection There is no sound  
meson-sm1-h96-max.dtb
Boots with a graphical user interface. Max Res 1080p It appears there is Bluetooth (at least an item is showed) There is no WIFI connection It appears there is Ethernet connection There is no sound  
meson-sm1-khadas-vim3l.dtb
The system does not start  
meson-sm1-odroid-c4.dtb
The system does not start  
meson-sm1-odroid-hc4.dtb
The system does not start  
meson-sm1-sei610.dtb
The system does not start  
meson-sm1-x96-air.dtb
Boots with a graphical user interface. Max Res 1080p There is no Bluetooth There is no WIFI connection There is no Ethernet connection There is no sound  
meson-sm1-x96-air-gbit.dtb
Boots with a graphical user interface. Max Res 1080p There is no Bluetooth There is no WIFI connection It appears there is Ethernet connection There is no sound  
I think I will try to continue with meson-sm1-h96-max.dtb file.
 
Using a USB Wifi Stick I'm perfectly capable to connect to a Wifi Network.
 
---------------------------------------------
I updated the system using (on terminal):
 
sudo apt update  
Then
 
sudo apt upgrade ---------------------------------------------
 
 
 
Now I will try to install the TV Box Wifi and Sound Drivers
 
 
 
---------------------------------------------
 

After adding the meson-sm1-a95xf3-air.dtb file on extlinux.config I was able to start on a graphical user interface.
 
Then I used these credentials:
 
User:
root
 
Password:
1234
 
By the way, for this test I'm using a Rii X8+ USB Mini Keyboard, which works as a keyboard and a touchpad
 
 
-------------------------------------
After this achievement, I have some questions:
How do I Active the wifi connection? Could I try another DTB file? Or Should I try using a USB Wifi Stick and then try to update the drivers from the terminal using some commands? The same question goes for sound driver.  
 
-------------------------------------
 

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

 

---------------------------------------------------------------------------
This post was constructed from the
answers of another one, so I will try
to clarify what's going on.
---------------------------------------------------------------------------
 
 
I'm trying to install ARMBIAN 23.02.2 on a T95 MAX+ TV Box, with an AMLOGIC S905X3 proccessor (4 GB of RAM; 100 mbit/s ethernet; 32 Gb of internal memory).
 
The 23.8.1 ARMBIAN version for AMLOGIC (link) proccessors, does not work well. It was suggested to me (Thanks to @well83) to use the 23.02.2 version (link). In this post I will be trying the Armbian_23.02.2_Aml-s9xx-box_bullseye_current_6.1.11_xfce_desktop.img.xz file.
 
After trying some differents DTB files I was able to boot to a graphical user interface (see the subsequent answers below for more details). Now I'm trying to determine how to install and/or congifure the propper wifi and sound drivers.
 

Note that this thread is archived.  Current information can be found at:
https://forum.armbian.com/topic/33676-installation-instructions-for-tv-boxes-with-amlogic-cpus