Amlogic S805 Firmware

1 view

Skip to first unread message

Beatrix Gerke

unread,

Aug 3, 2024, 5:02:58 PM8/3/24

to gannmarringpsych

Here is the newest stock firmware for the MXQ Amlogic s805 tv box.There are two versions for the MXQ, one is coming with broadcom ap6181 wifi module(without bluetooth function) , the other is coming with broadcom ap6210 ( built in bluetooth version)

How to upgrade By Micro SD card:
1.Unzip the zip/rar file,and copy 2 files to TF card Root directory;
2.Insert the micro sd card to MXQ, go to find a toothpick and press the reset button which hide in the AV port; after you press the reset button, power on the MXQ.
3.OK,it will be into update process.

1.Update the skype and XBMC to lastest version.
2.Update DLNA/Aliplay version.
3.Fix video problem when use Hulu and Viet Nam TV
4.Fix SONY TVModel:KLV-40V530Asound stutter in 480i screen resolution 480i
5. Improve Netflix playback
6.Optimize mkv video playback
7.Optimize TrueHD video playback
8. Add the support for DVI device;
9. Fix reboot problem when do the screenshot in video playback;
10. Other tweaks

Could your consider removing the passwords from the compressed files?
It is difficult enough to download and install the files with this strange methods as you do not provide OTA updates to add even more difficulties with the passwords.

Is there a way to add the MXQ box to the armbian supported OS's with nand support? This is a similiar device as the S805 ODROID device and the difference is only that this device has also a nand storage on it.

I have already successfully tried to use zoneminder on NAS with ARMv5. I think s805 is possible to use zoneminder. Soon I should receive a sample TV box with S805 chip, then I'll be able to check it out. Armbian install it in internal memory. In manual mode it works. Need some time to test automatic procedures for installing to the internal memory.

With a multi-boot system from Alex without making significant changes to the way that Linux will not work. You can try to use a universal multiboot. If you collect the correct script (not difficult), which is responsible for system start, you can try to achieve system operation.

@@balbes150
i also have a few s805 boxes lying around, i wouldn't mind testing your images on hem too (i think i have at least one black mxq and one beelink s85, the two have different boards).

here's the current uboot env of my s85, it was most certainly modified by an openelec boot image, through a recovery update process.

On platforms S805 uses an older version of u-boot and organization of memory is different from s905. Therefore, the algorithms and commands to the external load will be different. I now analyze and test different options. I would be useful to see the output of "help" from Your consoles. What would determine which commands are available in all devices (something you can use).

Gathered a working version of the image armbian (console) for the s805. Checked on my existing Board with S805 (spot i5). The image starts and runs. Due to the lack of work on my Board USB connector, I was unable to test the USB flash drive. To use, you can write the image to the media, copy it to the root of the first (FAT) partition and rename "dtb.img" is needed for the Board file (from the directory dtb of the first partition of the written medium). Order of use

To build dtb files for other models, please provide to me either a dts file from need model, or provide a link to the firmware or to provide a working dtb file from the correct model. In the first stage, you can try to use the files in the dtb (don't forget to copy to the root of the FAT partition and rename to "dtb.img").

From that moment on the TV console activated universal multiboot and you can run it on a different system from external media. The internal system remains unchanged and no it does not suffer from this.

At the moment there are three files, you can try all three files. If the system fails to boot, you need to collect suitable for your TV box new dtb file. For this you need to send me the relevant information. On these links, you can read the details on how you can capture the image on the medium.

This is a common mistake. Usually it is associated with a media error. Sometimes this error is related to a bad download of the file (error when downloading). First check how to prepare the media. Must be FAT system. The media is better to have no more than 2 GB. For the S805 is better to use SD card, because in many models of u-boot S805 not working install updates from a USB. They can only use the SD card activate the multi-boot. Alternatively, download the special image at the link. Burn it to the media. To replace the files on those that are designed to S805. PLEASE NOTE the files in the original image state is designed to S905 they need to replace the files for the S805.

Share the link to Your dtb file. It is necessary to try to collect all variant dtb file based on the Assembly environment and the kernel sources , which in Armbian. Maybe it will help to start the system. It is advisable to try all the dtb files that are in the directory and on the website. Sometimes it helps initial boot (not all hardware will work, but the main thing is to find a basic piece of data).

In the last images added two scripts to perform a full backup and restore the entire internal memory (ddBR). It is convenient to use in front of various experiments with the contents of the internal memory.

I uploaded the new images. Try them. You need to try everything available in the catalog of dtb files (from all models). I have oddly enough, the i5 is better earned the console image file from hq18. When using native dtb files (from version) i5) was the problem. The system did not boot (had a kernel panic) with the native tether 1Gb, which runs Android. With dtb file 512MB the system was started and worked, but was determined only 350 MB of memory. And file from hq18, it works correctly, the memory was 790 MB and the system was stably run. By the way, I downloaded the desktop Ubuntu image. It works for me, there is a Desk XFCE , but the colors are not correct and can not see the cursor. Have to move the fly at random.

Someone have found how use Mali and UMP drivers for accelerate something in Armbian Linux? Its a possibility? Odroid C1 use same processor and have acceleration! I dont find any 2d or 3d acceleration information for this s805 tv boxes. Even the Video play acceleration not have development.

Any one uses Armbian with swap partition? I am having problem with swap , when ram its at 60% , swap activates but the kernel gives error and freeze the system. And I have to unplug the box. Its normal? This kernel don't work with swap?

Just wanted to comment and let you know you're not the only one with this problem. I recently started using Armbian on a S805 box I have laying around and get the same thing too. When I set a swap partition to either a USB stick formatted for swap or a swap file I made in the internal memory I get errors similar to yours.

Pay attention. Changed the algorithm for specifying dtb. Now it corresponds to the General method. Be sure to update the universal multi-boot using the latest images (5.67). To select the desired dtb, edit the first line in the file "uEnv.ini". Specify your version of the file name from the image or you can copy your version of the file to the media and enter its name. You no longer need to copy and rename anything.

1. I checked the latest images on the s805. Systems with kernel 3.10 start up and run normally, as in previous images, even without a universal multi-boot update. In the image with the kernel 3.10.33 there is a small error, there was no script to enable the screen (/boot/hdmi.sh) and there is no service to run it. It is easy to fix it-copy the necessary files from the previous version and enable the service.

2. The image with the kernel 4.20 works on s805, it is necessary to replace the name of the dtb file in the "uEnv.ini" to " meson8b_ec100.dtb". With this dtb file I have a wired network and can manage the system via SSH. HDMI does not work yet, but can have a full-fledged server with control over the network or UART.

Thank you so much for your effort and contribute. Thank to you, I now able to run armbian on my old, laggy S805 android box with just only 1G ram and 4G MMC. Unfortunately, whenever I try to transfer installation from USB to MMC( with Android preinstalled), it said "not enough of memory" - may be because of my only 4G MMC . Do you have any tips/ideas to flash armbian to MMC?( I dont need android at all). I've thought of resize android partitions( extend /data partition) or build my own image file then flash it by USB Flashing Tool but haven't done it yet. I just wanted to know that it's possible to install your image to a 4G memory space. Thank you.

I now able to run armbian on my old, laggy S805 android box with just only 1G ram and 4G MMC. Unfortunately, whenever I try to transfer installation from USB to MMC( with Android preinstalled), it said "not enough of memory" - may be because of my only 4G MMC . Do you have any tips/ideas to flash armbian to MMC?( I dont need android at all). I've thought of resize android partitions( extend /data partition) or build my own image file then flash it by USB Flashing Tool but haven't done it yet. I just wanted to know that it's possible to install your image to a 4G memory space.