Posts by kostaman


    kostaman There were no changes in device trees since 7.0.2.009. If you perform an update without dropping a device tree in Update folder, /dev/dtb partition is untouched.

    I didn't think there was a change.
    So this is strange ?


    I have a similar issue on a Q-Box 2/16GB, posted about it here. Did you update a box on which you installed a couple of add-ons? Because I have this issue when I try to update or do a fresh install and restore a backup.

    I am completely stock. I cannot even get past boot animation after 19th November version.
    I am also coming from stock no add ons 19th November.

    kszaq i installed (LibreELEC-S905.aarch64-7.0-devel-20161119092613-r23439-gc23e2fb.img) to SD Card and then installed to internal memory.
    All went well and rebooted and power off and on no issues.
    After the internal memory flash i updated to the 2nd December build without a device tree.
    Gets stuck on Boot up logo.
    Is there a device tree i missed during the Dev Versions somewhere between 6th November Device Trees and the 2nd Dec version.
    To cut it short What Date Device Tree should i have on this box.
    Is it the 6th November ? device_trees
    I go back to the 19th November via SD Card install installtointernal command and it boots normal.
    Works normal again with 19th November version. Internal and Sd card install.
    T95N-2G Mini M8s Pro S905 (2GB /8GB Realtek wifi fix trees always used)
    Model : T95N-2G


    Just create a file fake.zip on your SD CARD which contains LE.


    My instructions state:
    Please be aware that you cannot just put the Fake ZIP on the SD Card that has LE on it and UPDATE via the Update App.
    You may want to correct your instructions as that method wont work.
    Correct me if i am wrong because the fake zip method only worked when it was on a USB stick for me.
    Otherwise i got the failed screen. See link below
    #483


    Recovery work with laptop for reflash firmware ? (i have see video in Youtube guy flash TX5 Pro with Toothpick)
    effectively recovery mod dont work in "Toothpick method" on TV


    Don't worry about USB Burning tool using a PC. Not necessary with our problem.
    Only problem we have is we don't know what will happen if we install LE to internal memory.
    Will we ever see recovery again ?
    Deki we have very new Android Firmware Marshmallow 6.0.1 Dated 26th October 2016. Android 6.0.1
    I can't even find this version anywhere for this box.
    anthontex gave some good advice #484  about the recovery issue is related to the Android version we have.
    Check your version of Android to see if it is the same date as mine.


    It happens that sometimes when starting the Android TV with LibreElec does not catch internet over RJ45? You have to start several times, until you pick it up, even unplug it from the current ... I know it has no wired internet connection, because Kodi sets the date and time does not update it.


    #1,014

    I don't know what box you have but go to link above and read from there.

    Picture of my non Branded MiniMx S905 2gb/16gb
    Had this problem.
    It is a Beelink but un branded.


    Question now (sorry i'm Newbie in android/libreelec) it's possible install Libreelec in the nand that ok, but android in the SD card ?

    Stick with LE on SD Card. Don't install to internal until we work out this recovery issue.
    The Android 6.0.1 on these boxes has given me crashing issues with Koying's SPMC but it is not this box only, it is happening on the WetekHub
    as well. So there may be some issues forthcoming with 6.0.1.
    Good news is the Dev build SPMC resolved crashes on my box.
    No running Android on SD Card.
    The box runs really well and has great WIFI using /ac 5GHZ.


    I have no idea for now, there might be some change that I need to introduce in the script - that said I have not encountered this yet with my boxes.

    Thanks kszaq
    I'm not sure this is an issue with Android 6.0.1 or just the Android Version for this box.
    I've noticed SD Cards are now showing up Named SD Card and USB's also showing up with whatever they are Named when formatting them. Not sure this causes anything with the script. Wild guess from my limited knowledge.
    Cannot load volume/misc! and failed to mount etc as in screenshot above post is confusing.
    I can add that the fake zip from USB stick using the UPDATE APP in Android works 100% of the time in installing LE to SD card.
    I know that because i booted into recovery whilst in Android and then chose reboot which loaded Android.
    After that LE on the SD Card was ignored (script lost). Reboot and Power off in Android did not boot to LE any more.
    Fake zip method above got LE back.
    I can also report that i pulled the SD Card out after powering off box with remote and restarted Android three times with reboot and power off.
    I then inserted the SD Card with LE on it and powered box up , which booted successfully into LE.


    Hi, still is here maybe solution by 150balbes. Don´t worry Russian language and go to bottom of web page, there is english language part.

    s905_multi_boot · 150balbes/Amlogic_s905 Wiki · GitHub

    This solution I have used on my MXV+ box, because I had similar problems like you.

    Thank You for reading and replying.
    I have a S905X Chip and the script is written in kszaq builds.
    My issue is the damn box does not go looking for a recovery even in Android using toothpick method. :s


    Hi kostaman, thanks for your precise description. For what I remember (I don't have that box), that box should boot to LE "in a normal way" like toothpick method only if Android version is <= 05082016. Recent firmwares locked the ability to boot with toothpick method:exclamation: so I've seen someone that suggested to downgrade to that firmware version. But actually you have found a workaround for this :rolleyes: thanks


    I just checked my firmware version : 26th October 2016. Android 6.0.1
    I will have a play with this box when i have some time.
    kszaq might shed some light on what they have done to block search for recovery when trying to use toothpick method.
    My concern is what will happen if i install LE to internal and then want to go to recovery ?
    It seems the only way i can get there at the moment is with Android UPDATE App and a Fake ZIP from USB Stick.
    No idea what i'd use after LE is installed internally, to get into recovery ?
    Unless i downgrade Android which is not something i want to do.
    Thank you for the feedback anthontex. I'm sure this issue will arise again with another member. :idea:

    My first S905X Chip box arrived today and here is the drama i had to get LE on SD Card to work.

    TX5 PRO Amlogic S905X 2GB+16GB


    1. Toothpick method: disconnect the power supply, insert card/drive, use a toothpick to push reset button and connect the power while holding the button. Wait until LibreELEC logo appears and release the button. Used With and Without Device tree.
    Failed with just the boot animation and no further.

    2. Recovery method: boot into Android, insert card/thumb drive and choose Reboot to recovery.(Had to use an APP)
    Your box should boot into LibreELEC.
    Failed same result as above.

    3. Factory recovery method : Tried to boot into recovery without any SD Card inserted.
    This box just displays the boot animation and stays there. Failed same result as above.
    It is a bit of a worry this box does not go into recovery using the toothpick method.
    I haven’t tried TWRP Recovery as this box has a working OTA (Shock Horror)

    4. Recovery method (take 2nd variant): if you have "Update" app pre-installed open it, insert SD card with LE/connect USB drive, and choose any ZIP file in the app for update. Your box should reboot to LE.
    This method "Worked"

    Please be aware that you cannot just put the Fake ZIP on the SD Card that has LE on it and UPDATE via the Update App.
    Something is not right regarding update using normal recovery methods i have used in the past with S905 Chip.


    EDIT: UPDATED TO LibreELEC-S905.aarch64-7.0-devel-20161202213923-r23473-g8a53869.img , No issue updating.


    OP updated with new build. A few improvements, including fixed PVR addons and smoother GUI.

    kszaq Official ANT 1 Addon (Lambda) from Kodi REPO choosing Live from the menu is giving me some strange behaviour in that it opens the stream 1 out of 8 attempts. When it doesn't open there seems to be an issue that the stream has opened but the screen stays on the menu. There are no GUI sounds when using remote until i stop the stream.
    I turned OFF accelerate H264 (never) and the streams open normally.
    See screenshot of settings which work. It is the same with other addons in Lambdas greek addons for live.
    I thought this may help identify what is going on using this addon.

    Test box MiniMX 1gb/8gb S905.
    Sharp Aquos Quatron 70 inch tv
    Box to HDMI simple set up.


    OP updated with 17 beta 6 build.

    Now That Is A Seriously Big Improvement In Memory Recovery !
    Now it's like my S805 as far as Memory recovery goes.
    :D

    What was that all about ? Are we moving forward with 32-bit userspace (32-bit builds provide lower memory consumption)
    or going backwards going forward. ?
    This is a little over my head due to my limited knowledge in what has happened here using a 64bit chip. :huh:
    I've just loaded this version on my test box so i will report back.

    Test box MiniMX 1gb/8gb S905.
    Sharp Aquos Quatron 70 inch tv
    Box to HDMI simple set up.


    Power off, on the other hand, works with libreelec. The linux system shuts down properly and the hardware is also deactivated (at least partially, I actually tried it and measured a drop in power usage with a plug-in power meter). At this point, there is no more linux kernel running, and control of the box has returned to the original bootloader.

    It is the job of this bootloader to wait for a power-on event (remote code, power button press, ...) and re-start the operating system. If your remote does not restart the power-down box, it is the boot loader's fault.

    Very well explained :idea:


    So. As I understand "on/off issue on a95x s905 1/8" is totally libreelec bug. Not box's firmware.

    There are about 20 DIFFERENT Chinese boxes or maybe more using kszaq builds and THE ONLY BOX with this power
    issue is the Nexbox A95X S905 1gb/8gb. So the fact U-Boot is not touched in these builds, it makes sense.
    So how do you come up with an opinion that this is an LE bug and kszaq is wrong.?
    My advice on the issue is totally based on kszaq's advice and i only made it so as to stop repetitive posts on this box.
    Read a bit about U-Boot Android and what it is and you will understand.


    Are you asking a question about Android Firmware on your Nexbox A95x S905 or are you talking about LibreELEC issues ?
    There is no mention about LibreELEC in your details.


    So I did try it thanks.
    Just one question.
    If I disable CEC will I still be able to turn my box on and off with the box remote?
    Thanks.

    CEC has nothing to do with your Standard Remote.
    Shouldn't cause anything to do with the workings of your remote.
    Only affects external remotes like your TV remote being able to control your box.
    Other options when CEC is activated like turn off box when TV is turned off will of course not work.
    I'm not sure of the issue you have with CEC being turned on.
    If you don't use it then turn it off. Cheers.