[S905X] Fresh installation on Jadoo 5S Android TV Box

    Hi all,

    I am new here and apologies in advance. I am not a tech. savvy but can understand bit about tech. things.

    I have a old tvbox (Jadoo 5s) running with android 6.0.1 and chipset i found is S905x emmc, 8 GB prebuild storage and 2 GB RAM. I am trying to install LibreELEC as a main OS for this tvbox so then after i dont have android 6.0.1 on this box.

    I am unsure from where I could download the correct LibreELEC for this version tvbox and same can download device-tree. I have followed couple of youtube and instruction and getting fails from tvbox root to install with error: signature not verified and installation aborted. After couple of trial/error now box not recognised original registration so unable to download from internet within this box but i am able to use SD / USB to install apk etc.

    1). Please redirect me correct links to download .img and device-tree.

    2). Please guide me steps to follow.


    Thanks in advance

    Bob

    Do not attermpt to use old vendor-kernel device-tree files found on the internet, they will not work.

    Do not rename files to dtb.img and kernel.img etc. - this also will not work.

    The supported device-tree files are in the amlogic folder on the SD card.

    This is all explained in the wiki instructions you didn't read.

    • New

    Hi Chewitt,

    I have tried all possible ways as per wiki # Box images. Steps I have done:

    1). Downloaded latest LibreELEC-AMLGX.aarch64-12.0.1-box.img.gz

    2). Extracted files as .img

    3). Flashed to SD card using Etcher

    4). updated uEnv.ini with device tree name updates: dtb_name=/amlogic/meson-gxl-s905x-p212.dtb
    bootargs=boot=UUID=1708-1803 disk=UUID=742745a0-653c-4420-9ef5-6b5faba036fb quiet systemd.debug_shell=ttyAML0 console=ttyAML0,115200n8 console=tty0

    5). SD card inserted in box and started box with reset open following pin into hole pressing button.

    6). Screen show up to Jadoo 5s logo and then options available from root. I have attached picture here.

    However, I am unable to work out how it will boot to libreelec. this should be automatic but has not happened so I tried to access some options as per attached pictures.


    7). Just incase, I did extra steps to copy and past device tree with ext. change to .img not as dtb.img. but device tree name with.img so i can run under the options of apply update from EXT -> update from sd card -> device tree.img but it fails with same error: signature not validate and process aborted.


    I am not sure what I have missed or missing as I don't have much knowledge of Tech. but I am trying with some youtube videos and following you like tech. savvy.

    Much appreciated if you could guide more from here..

    Thanks

    Bob

    • New

    You need to power the box on with the reset button already pressed, then a couple of seconds later you release the button. In the default vendor bootloader this will force searching for and reading s905_autoscript on the SD card, which modifies the boot flow to look for LE boot files on the SD card (with no renaming). It is not uncommon for some experimenting with button press duration to be needed.

    I suspect you are either pressing recovery after boot or holding the recovery button down for too long, which results in Android recovery boot, which requires Android recovery .img files. These use the same .img file extension but are something completely different to an LE .img file. Renaming LE boot files to Android boot file names will trick Android recovery into loading a file it doesn't understand, but (as you can see) that doesn't achieve anything.

    It would be unusual but not impossible for the box to have a modified vendor bootloader that does not look for s905_autoscript and thus cannot be tricked into running LE the normal way. There usually is a way, but the process requires a serial console on the box to interupt/access the early boot flow and run manual commands. That skillset and process is generally beyond most users; and those with the aptitude for the task generally get on with it rather than asking for help with it.

    • New

    Hi Chewitt,

    1). I do press holding reset button and then after turning on tvbox.

    Yes, you are correct.

    2). Soon I turn on box within a second Jadoo TVs 5 logo pop up on screen and the reason i though i need a long press to enter into recovery mode and the result show up as per previous photos been attached.

    3). I will process again without holding too long recovery button / reset button.

    Q).

    1). After the previous process I have notice in my SD card folders have another 2 folders 1).Android & 2). Lost.Dir. been added and I am unsure how has been added. I am not too much concern if that's nothing relates to or if its a common? I have attached photo.

    2). press, hold reset /recovery button then turn on box and release button within couple 4-5sec. after power on. : scree will still come up Jadoo logo and then LE logo or jadoo tv logo should not pop up?

    Thanks

    Bob

    • New

    On most Amlogic devices you hold the recovery button, apply power, release after 2-3 seconds, then you see the LE boot splash once KERNEL has been booted. Some devices need 1 second, some 6-7 seconds. I've no idea what you box needs /shrug

    Box vendors can add a custom boot splash to u-boot (although most do not because it requires effort) and to customise the Android boot splash (most do, because it's simple). I've no idea which one you see /shrug

    If you box does anything different or needs some different process .. it's impossible to triage what's required without connecting a serial UART device to the board so we can see what happens or fails in the early boot process. That requires a) having a USB serial UART tool, and b) opening the box up to install it, which often requires wires or pins to be soldered to the board. Otherwise we are blind, and blind guesswork is a recipe for frustration not success.

    The 'Android' and 'LOST.DIR' folders were created by Android during recovery boot, it's harmless.

    • New

    A typical indication that the vendor u-boot is too old. It lacks the ability to run aml_autoscript in the environment.

    A more complicated but safe method:

    You can install the Amlogic USB Burning Tool on your computer, connect the box to the computer via USB cable and manually add the commands from the source file in the Windows cmd window to the u-boot environment.

    Another option would be to upgrade the Android to a higher version, but there is a risk that you will get an unsuitable firmware that will brick the box.

    • New
    Quote from chewitt

    On most Amlogic devices you hold the recovery button, apply power, release after 2-3 seconds, then you see the LE boot splash once KERNEL has been booted. Some devices need 1 second, some 6-7 seconds. I've no idea what you box needs /shrug

    Box vendors can add a custom boot splash to u-boot (although most do not because it requires effort) and to customise the Android boot splash (most do, because it's simple). I've no idea which one you see /shrug

    If you box does anything different or needs some different process .. it's impossible to triage what's required without connecting a serial UART device to the board so we can see what happens or fails in the early boot process. That requires a) having a USB serial UART tool, and b) opening the box up to install it, which often requires wires or pins to be soldered to the board. Otherwise we are blind, and blind guesswork is a recipe for frustration not success.

    The 'Android' and 'LOST.DIR' folders were created by Android during recovery boot, it's harmless.

    Thanks Chewitt,

    I will keep try...

    • New
    Quote from bumerc

    A typical indication that the vendor u-boot is too old. It lacks the ability to run aml_autoscript in the environment.

    A more complicated but safe method:

    You can install the Amlogic USB Burning Tool on your computer, connect the box to the computer via USB cable and manually add the commands from the source file in the Windows cmd window to the u-boot environment.

    Another option would be to upgrade the Android to a higher version, but there is a risk that you will get an unsuitable firmware that will brick the box.

    Hi Bumerc,

    The first option sounds ok my end to process.

    1). What are the steps to add this source code file commands into which file / folder in the box? I only see the file/folder options from android recovery as per previous photos attached in posts.

    Thanks

    Bob

    • New
    Quote from bob276

    Hi Bumerc,

    The first option sounds ok my end to process.

    1). What are the steps to add this source code file commands into which file / folder in the box? I only see the file/folder options from android recovery as per previous photos attached in posts.

    Thanks

    Bob

    Hi.

    Please follow the instructions in this PDF file for manual installation. For installation you need these files. Then try to establish the connection to the box via cmd.exe. Hold the reset button and run update.exe identify

    I will explain the remaining steps once you have established the connection to the box.

    You don't need any files on the box. The update.exe interacts directly with the u-boot via worldcup protocol and the u-boot writes the commands directly into the env partition of the eMMC, as if you were writing directly in the u-boot prompt via uart.