Posts by mickey

  • add kernel conf

    i have some question can somebody point me to add kernel config this step i must do to make wifi driver to work only i don,t know where to start :D :D

    Add path kernel config fw_path=/lib/firmware/brcm/fw_bcm4339a0_ag.bin
    nv_path=/lib/firmware/brcm/ap6335e_nvram.txt

    modifiy kernel config to

    CONFIG_BCMDHD_FW_PATH="/lib/firmware/brcm/fw_bcm4339a0_ag.bin"
    CONFIG_BCMDHD_NVRAM_PATH="/lib/firmware/brcm/ap6335e_nvram.txt"
    CONFIG_BCMDHD_CONFIG_PATH="/etc/wifi/config.txt"

    after kernel find broadcom driver

  • compile libreelec

    Quote from vpeter


    You are using unsupported distro (linuxmint) and some packages are missing. Because those packages (gperf makeinfo lzop ...) can't be installed automatically from a build scripts you need to install it by hand on your system. And then build process will work.

    oke thanks i give it a try :D :D

  • compile libreelec

    Quote from pajretX


    Have you read the wiki? Compile - LibreELEC
    You really should start there if you want to compile by yourself.

    yes only get Your system lacks the following tools needed to build LibreELEC ****
    gperf makeinfo lzop g++ xsltproc /usr/include/ncurses.h
    **** You seem to use a linuxmint system ****
    **** unsupported distro linuxmint ****
    Makefile:12: recipe for target 'image' failed
    make: *** [image] Error 1

  • compile libreelec

    i have some question because i am stuck i have download libreelec from git i have a zip package and have add files for my box know i wanna compile the package how to make a zip update package from this folder?

  • xbmc_env.properties ?

    How to setup xbmc_env.properties under linux libreelec i have been switch from android to libreelec only i want setup
    xbmc_env.properties to load from sdcard because know running from nand where to put the file under libreelec because i can not get it to work

  • [S812] OTT M8S 2G RAM 8G ROM BCM4335 WIFI


    testing no wifi no lan strange numbers ? using minix neo 8h plus 812 android

  • [S812] MIII Plus 2Gb\16Gb eMMC

    Quote from balbes150



    [hr]

    Judging by the output, the script is not executed. Describe in detail how You tried to activate the multi-boot. Have you tried to replace the files on the test ? Have you tried to change the name of the script with the "aml_autoscript" to "boot.scr" ?

    i have try all
    i do someting wrong i burn image LibreELEC-S812.LAN1000 to sdcard after that i replace the aml autoscript and aml autoscript zip with your 2 minix files i do revovery and relace i get recovery menu and can choose only the aml autoscrip zip if i choose aml auto script i get message - E: footer is wrong
    - E: signature verification failed


    if i use your LibreELEC-S812.LAN1000 zip package and install on sdcard package open and install on internal memory from the box if i restart with or without sdcard libreelec running only from internal with no wifi signal only lan

    so i don,t understand can you upload me one update zip package for sdcard with all in so i must only go to recovery and install

  • [S812] MIII Plus 2Gb\16Gb eMMC

    Quote from balbes150


    fw_printenv

    LibreELEC (community) Version: 8.0.0
    LibreELEC:~ # fw_printenv
    bootargs=console=ttyAMA0,115200n8 root=/dev/mmcblk0p9 rw
    bootcmd=run distro_bootcmd
    bootdelay=2
    baudrate=115200
    arch=arm
    cpu=armv8
    board=hikey
    board_name=hikey
    vendor=hisilicon
    soc=hi6220
    kernel_name=Image
    kernel_addr_r=0x00080000
    fdt_name=hi6220-hikey.dtb
    fdt_addr_r=0x02000000
    fdt_high=0xffffffffffffffff
    initrd_high=0xffffffffffffffff
    mmc_boot=if mmc dev ${devnum}; then setenv devtype mmc; run scan_dev_for_boot_part; fi
    boot_net_usb_start=usb start
    usb_boot=usb start; if usb dev ${devnum}; then setenv devtype usb; run scan_dev_for_boot_part; fi
    boot_prefixes=/ /boot/
    boot_scripts=boot.scr.uimg boot.scr
    boot_script_dhcp=boot.scr.uimg
    boot_targets=usb0 mmc1 dhcp
    boot_extlinux=sysboot ${devtype} ${devnum}:${distro_bootpart} any ${scriptaddr} ${prefix}extlinux/extlinux.conf
    scan_dev_for_extlinux=if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}extlinux/extlinux.conf; then echo Found ${prefix}extlinux/extlinux.conf; run boot_extlinux; echo SCRIPT FAILED: continuing...; fi
    boot_a_script=load ${devtype} ${devnum}:${distro_bootpart} ${scriptaddr} ${prefix}${script}; source ${scriptaddr}
    scan_dev_for_scripts=for script in ${boot_scripts}; do if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${script}; then echo Found U-Boot script ${prefix}${script}; run boot_a_script; echo SCRIPT FAILED: continuing...; fi; done
    scan_dev_for_boot=echo Scanning ${devtype} ${devnum}:${distro_bootpart}...; for prefix in ${boot_prefixes}; do run scan_dev_for_extlinux; run scan_dev_for_scripts; done
    scan_dev_for_boot_part=part list ${devtype} ${devnum} -bootable devplist; env exists devplist || setenv devplist 1; for distro_bootpart in ${devplist}; do if fstype ${devtype} ${devnum}:${distro_bootpart} bootfstype; then run scan_dev_for_boot; fi; done
    bootcmd_usb0=setenv devnum 0; run usb_boot
    bootcmd_mmc1=setenv devnum 1; run mmc_boot
    bootcmd_dhcp=run boot_net_usb_start; if dhcp ${scriptaddr} ${boot_script_dhcp}; then source ${scriptaddr}; fi
    distro_bootcmd=for target in ${boot_targets}; do run bootcmd_${target}; done
    bootfromrecovery=1
    bootfromnand=1

    LibreELEC:~ # udevadm info /sys/bus/sdio/devices/sdio\:0001\:1/
    P: /devices/platform/aml_sdio.0/mmc_host/sdio/sdio:0001/sdio:0001:1
    E: DEVPATH=/devices/platform/aml_sdio.0/mmc_host/sdio/sdio:0001/sdio:0001:1
    E: DRIVER=bcmsdh_sdmmc
    E: MODALIAS=sdio:c00v02D0d4335
    E: SDIO_CLASS=00
    E: SDIO_ID=02D0:4335
    E: SUBSYSTEM=sdio

  • [S812] MIII Plus 2Gb\16Gb eMMC

    Quote from balbes150


    Krypton and the image from the catalog LAN1000

    for some reason this box don,t see the image write on sdcard think protected from minix and don,t boot up from sdcard if i go to recovery mode i see sdcard with empty folder and nothing to install if i install from zip package this update running and start libreelec from internal memory only no android anymore i don,t need android so i have install your latest kodi 17 1000 version on the box all running oke only wired i have connection no option for wifi wifi enabled only there are no poppup wifi conection to choose from so wifi not working for me it will be great if you can fix this for me

  • [S812] MIII Plus 2Gb\16Gb eMMC

    i think i miss something so only this 2 files on sd card and recovery mode aml autoscript bin and autoscript zip and the libreelec file? or only this 2 files

  • [S812] MIII Plus 2Gb\16Gb eMMC

    Test script activate the multi-boot ready. Before using I need to ask You a number of nuances. Describe or give a link to the description of the steps You perform to install the updates of Your firmware from Sd card or from USB ? What files are in the update ? I need to specify the file name of the script that performs the You update. Here are the test files (script files and zip) for MINIX. You may have to rename the script from aml_autoscript to boot.src.uimg or boot.src

    Yandex.Disk

    i have 2 options to send firmware the one they i use i have format a sdcard to fat32 obx1 one that i put your LibreELEC-S812.MXIII_Plus.arm zip package know i have on the sd card factory update param aml and the libreelec zip know i put the sdcard in the box and with the tootpick recovery hole and power i start up if i release the button the update package start if i not release i come in revovery menu and can choose from there
    update from sd or udh here some video to this will see video youtube   orginal fw package from box android i have uploaded so maybe you can see wich file where i need

    so i must know use step 1 with the new aml autoscript you have make to dualboot


    options 2 with usb burning tool with Toothpick Method this i have only use for stock rom USB-OTG cable to my pc can only write there img file

    1.) Download the firmware package (.rar)

    2.) Extract it, you will get the firmware image (.img) & the burning tool

    3.) Install the new USB burning tool which is already included in the package (choose English at the beginning)
    Choose "Install anyway" when system prompts for driver installation
    3a.) Start the USB burning tool

    4.) Connect the Micro USB cable supplied with the box between the OTG port of the box and your computer
    (Windows based);

    5., press and hold the power button and recovery hole with Toothpick
    to get into flashing (recovery) mode.

    6.) Upon successful connection the "Connect success" message will be displayed inside the application

    7.) Load the firmware image by selecting "File -> Import image"

    8.) After loading, the 1st and 2nd box of "Configuration", "Erase flash" (Normal erase) and "Erase bootloader", should be checked by default.
    If you want the machine to restart immediately after flashing, check the "Reset after success" option as well.
    Then, click "Start" to start flashing

    9.) The upgrade process will take approximately 2-3 minutes, the last 5-10% takes longer time to complete,
    and you MUST make sure the power can't be disconnected during the upgrade (of course also the OTG) or your box could become a brick

    10.) Upon successful upgrade, the application will display the message "Burning successfully"
    then it's safe to unplug the power (and also the OTG! otherwise it will start to burn again after repower on if the USB burning tool is still running )
    and connect your hub back to the TV for 1st start (which is also very important and takes some minutes);


    So about 1st start:
    It's very important that you DO NOT cut the power off from the hub during the 1st start,
    since preloaded apps. will be installed in the background, if you power it off in the middle of the installation, some preloaded apps. might become be missing.

    NOTE: Always use the "Normal erase" option