Legacy v9.2 (LTS) builds for Amlogic S805/S8X2, S905/S912 and all WeTek boxes

    Quote from jim_p

    How can I prove to someone that the builds are on kodi 18 or that kodi 18 runs python2? For some reason, I can not run this, or any other kodi parameter like kodi --help, on le.

    Code
    LibreELEC:~ # /usr/lib/kodi/kodi.bin --version
18.9 (18.9.0) Git:18.9-Leia Media Center Kodi
Copyright (C) 2005-2020 Team Kodi - http://kodi.tv

    Thanks dtech and libreelec team, for your efforts.

    Reporting to say that the LibreELEC-Generic_S905.arm-9.2.8.13 is working on my Nexbox MXQ PRO with Amlogic S905 SoC. Installed to internal emmc storarage. Wifi was fine from the first boot (box has Realtek 8189etv) but Ethernet was not working until I used gxbb_p201.dtb as dtb.img. Cheers.

    this is my first post i have seen the MODERATOR dtech being so kind with everyone and solved many problems so i want to take my chance

    my problem is i have Pandora 3D game box which is Amlogic CPU: S812 and MICRON NAND (29F16G09CBA) CHIP i was playing with its partitions to enable some tweak and bricked it..now i am in a situation where i have ADB backup of all partitions but lost all partitions (image1) (sda&sda1 is the usb pendrive attached in a machine)and i dont have the factory firmware for it to restore it to a original position


    please suggest me something


    i can access recovery(image2) when i burn card with my uboot.bin just recovery with root access but partitions are gone

    Quote from dtech

    Would the goal be to restore the original environment or to install LibreELEC?

    I have an idea for the second, but the first needs to be investigated.

    Just bring it back to life either LibreElec or original no problem at all

    Because I am tired trying roms after roms

    Quote from y0ush4

    Because I am tired trying roms after roms

    If it's not the factory one and there's no backup, it's not exactly a good base.

    Quote from y0ush4

    m8m2_n200_1g

    Then there is a problem, because I don't have a 1GB image for S812, only for S802 (MXIII-1G).

    There was a test kernel for the 1GB box, it might work with that (but it was not made for the latest image):

    Quote from dtech

    If it's not the factory one and there's no backup, it's not exactly a good base.

    Then there is a problem, because I don't have a 1GB image for S812, only for S802 (MXIII-1G).

    There was a test kernel for the 1GB box, it might work with that (but it was not made for the latest image):

    how to test it? i mean how to make a single file for usb_burning_tool? or something which can fix the partitions of the NAND and i am not after latest version i am satisfied with the 4.4 kitkat which was working smooth before it was bricked

    Quote from y0ush4

    how to test it? i mean how to make a single file for usb_burning_tool? or something which can fix the partitions of the NAND and i am not after latest version i am satisfied with the 4.4 kitkat which was working smooth before it was bricked

    Unfortunately, I'm not an expert in ADB operations or Android-based tricks, I think bumerc can help you more with that.

    Amlogic USB Burning Tool also requires a specific ROM format, but my images are not firmware/ROM images, only OS images (kernel + rootfs), so these do not contain any manufacturer-specific partitions. (Except M8S+ and WeTek images!)

    Hi dtech, I'd like to thank you for the work you have done here, and to report that your S805 HD18Q build works really well on my HTV3 Android box. It's almost perfect, and I have figured out how to fix some of the issues I encountered. I will list the issues I ran into, what I was able to fix, and some other notes in case anyone else with this box ends up reading this post.

    1. This is the remote.conf that works for my box, maybe you can add it to the list of supported remotes:

    htv3-remote.conf

    2. I had to enable "force suspend instead of poweroff" in the system settings, otherwise the remote control would not turn the box on. I know it's explained on your opening post, but I figured I'd mention it here in case someone with the same box reads it.

    3. This box has a led on the front. On Android, the LED turns blue when powered on, and red when powered off. On LibreElec it was just always blue. I noticed it worked on Lakka 2.x, so I looked for differences between LibreElec and Lakka S805 config, and I noticed Lakka had this led on /sys/class/leds/m201_costdown::front/.

    I set CONFIG_LEDS_M201_COSTDOWN=y and built the HD18Q image using your source code and it is now working as intended. https://github.com/dtechsrv/Libre….arm.conf#L3201

    Would you consider enabling this for S805 on the master branch?

    4. This box has a breathing light on top of the box. On Android, it's red when the internet is disconnected, and blue when it is connected, and it's turned off when the box is powered off. There's also an option on the settings page to turn on the "breathing light" mode, which puts it to fade in and out while cycling through the colors.

    On LibreElec, it's purple on boot, and cyan once it's booted. When M201_COSTDOWN led is enabled (see point 3 above), then it's green when the power is on and cyan when the power is off. This is the only issue I have not yet been able to solve on my own. I'd like to have the same behavior as on Android, but I can't figure out how to control it. On Android there's nothing listed under /sys/class/leds/, and I have not found any clues inspecting the motherboard. I am a newbie when it comes to this, so it's very possible I may have missed it. Any pointers on how to dig deeper into this breathing light issue would be greatly appreciated.

    5. I installed the zach-morris addon repository from the LibreElec Alpha repository, and then tried to install the IAGL program addon, but it failed saying it requires python 3. As it turns out, plugin.program.iagl-2.1.8.zip is the last version that works with python 2, but it's not available on the repository. I had to install it from zip, but then it worked fine.

    6. The addon libretro MESEN for NES crashes when opened. QuickNES is sluggish and has the wrong colors. Nestopia works very well on the games I tested.

    7. PCSX ReARMed was a bit sluggish on the default settings, but it runs pretty smoothly with PSX cpu clock set to 63 instead of the default of 57.

    8. The box has a reset button on the bottom of the board instead of the AV port, but it does not always work to bring up the boot loader. However, pressing the MENU button on the remote repeatedly during boot works pretty consistently.

    I am attaching some images of the box here:

    Pictures of the box, board, and remote

    Quote from dtech

    If it's not the factory one and there's no backup, it's not exactly a good base.

    Then there is a problem, because I don't have a 1GB image for S812, only for S802 (MXIII-1G).

    There was a test kernel for the 1GB box, it might work with that (but it was not made for the latest image):

    is there any Amlogic_burning_tool *.IMG tested on any box (s812)which exactly match with m8m2_n200_1g ?Available somewhere what my idea is just to restore the partitions... no matter what the result is

    Aglan

    Sorry for not replying until now, I've been away from my build environment for quite a few days now, but I'll review your suggestions on what can be implemented in the next version. I would definitely like to ask for your patience for a few days.

    y0ush4

    This does not make much sense, because the dtb id will not be enough, the size of the partitions can be different per manufacturer and/or model, so it makes no sense to flash a "similar" ROM.

    You should get the factory one, either from the manufacturer, or find someone who has the same device on a dedicated Android forum and ask them to make a raw flashdump of the box and upload it somewhere.

    We here on this forum, but especially on this topic, probably won't be able to help you.

    I came across the post

    linux-meson/arch/arm/boot/dts/amlogic/meson8m2_n200_1G.dtd at master · endlessm/linux-meson
    Contribute to endlessm/linux-meson development by creating an account on GitHub.
    github.com


    Which is exactly matching my configuration if somehow I could get

    meson8m2_n200_1G.dtb

    I request anyone arrange me the file atleast I can try to get back my machine I can repack the backup with these files


    Please I request anyone if can be arranged DTB atleast I can try


    Another user seems to have this file also

    Armbian for Amlogic S805 and S802/S812
    forum.armbian.com


    I hope someone still have that

    Quote from dtech

    Aglan

    Sorry for not replying until now, I've been away from my build environment for quite a few days now, but I'll review your suggestions on what can be implemented in the next version. I would definitely like to ask for your patience for a few days.

    No rush, I am glad I got this far, and like I said in my post, I was able to build the image myself with the M201_COSTDOWN led enabled, so the box is working here. I can watch HDHomeRun and play retro games, which is more than I expected from a 8 years old Chinese box that has been gathering dust in the garage for years at my parents place.

    I have unplugged the breathing light cable from the board for now so it's not always on, but I'd appreciate any pointers on that when you have time. It's a silly feature, but it's there, so I'd like to make it work if I can.

    y0ush4

    I still don't understand what you want to achieve with a single dtb file, but a few things are good to know:

    • The 3.10 kernel cannot load external dtbs from a file, only the version integrated into the kernel, so the dtb itself is not enough.
    • Android (factory) and LE/Armbian (universal) dtbs are not the same, the latter almost always lack the static partition table.
    • The dtb you are looking for only says that it is for a device equipped with an S812 SoC and 1GB of RAM. There are quite a few such boxes.
    Quote from dtech

    You should get the factory one, either from the manufacturer, or find someone who has the same device on a dedicated Android forum and ask them to make a raw flashdump of the box and upload it somewhere.

    We here on this forum, but especially on this topic, probably won't be able to help you.

    I would like to ask you that since you want to restore the factory environment, you can either open a new topic here on the forum, or inquire on an Android-specific forum. I would be very happy to help, but unfortunately I indicated before that I can't, so all your requests/questions about restoring the original state are offtopic from now on.