I have two VMedia VBox Quad+ (Amlogic s805, 1gb ddr3 ram, Android 4.4) android tv boxes that have been collecting dust and I am trying to make them useful. I haven't had any luck trying to get LibreELEC up and running though.
I've tried using Etcher to burn the img onto my micro sd card, tried updating from the zip and I've downloaded and tired anything I could get my hands on. My most recent attempts have been with LibreELEC 7.0.3.3.
I've also tried putting the img itself on the microSD card and renaming it to "recovery.img" and adding a factory_update_param file. In recovery mode when I select the sd card, it doesn't show anything. But if I load the box normally then go to settings, system updater, local updates, I can go to the sd card and select the .img. It'll then try to update using it but it fails to prepare.
I am on Windows 10 and do not have any linux environment set up so any advice would need to be Windows 10 based. I know I'm probably missing something super simple or extremely obvious but I'm new to this whole "custom firmware on crappy android boxes" world.
I also dug up a box that has been collecting dust for three years and I'm trying to give it life. Mine is an MX Pro with Amlogic S805. It also can't boot from mSD card but I use newer images. Why don't you try them?
I tried the newer versions and it's the same thing. I hold the reset button with a toothpick and plug in the power and it doesn't boot up anything, only takes me to the Android System Recovery screen where you can reboot system, apply update, or factory reset the box.
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.
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.
I work for company that product iptv, hbbtv and digital tv software both of server side and client side, so I am in android hybrid set-top box development team, how can I implement an app that do scan, play channel, channel up, channel down and show subtitle ... in this case media receive form coax antenna cable... the tuner of set-top box is amlogic...there is an app installed in set-top box, but i need develop my own app for do some custom work and task...please help me...how can i do that?help with document, library, and open source example project about that...thank you
After android 5.0, they have implemented TV apis also inluding lower level tv_input related HAL sources. Compile your tuner firmware with android standalone toolchain and port it to HAL. Take a look at
3) Start building your DVB software stack, including databases for channel lists, EPG and the like. Maybe you need to record TV events to HDD or SD Card and play them back again? It pays off to use OMX decoders for hardware assisted A/V playback - particularly H.264 and H.265 can make any CPU choke. Look out for mux and codec formats not supported by Android (MPEG2 video is only sometimes supported, LATM/LOAS AAC audio is not, etc.)