Help with Mecool K1 Plus

  • How to get these files?

    u-boot.bin.usb.bl2

    u-boot.bin.usb.tpl

    u-boot.bin.usb.bl2 = DDR.USB

    u-boot.bin.usb.tpl = UBOOT.USB

    Unpack the aml_upgrade_package.img that I sent you and search for these files in the output directory

  • ~$ '/media/jaroslaw/30BAD20DBAD1CF88/utils/aml-flash-tool/tools/linux-x86/update' write '/media/jaroslaw/30BAD20DBAD1CF88/utils/UBOOT.USB' 0x200c000

    ERR: write data to device failed

    I don't know what to do with it. The same error all the time.

  • ERR: write data to device failed

    What happens when you run the “update identify” command? You then have to initialize the RAM memory before you can write TPL to it.

    What happens when you run the “update run d9000000” command to initialize the RAM memory?

  • ~$ '/home/jaroslaw/Pobrane/utils-master/aml-flash-tool/tools/linux-x86/update' identify

    AmlUsbIdentifyHost

    This firmware version is 2-4-0-0

    ~$ '/home/jaroslaw/Pobrane/utils-master/aml-flash-tool/tools/linux-x86/update' run 0xd9000000

    [update]Run at Addr d9000000

    AmlUsbRunBinCode:ram_addr=d9000000

    ~$ '/home/jaroslaw/Pobrane/utils-master/aml-flash-tool/tools/linux-x86/update' write '/media/jaroslaw/30BAD20DBAD1CF88/utils/UBOOT.USB' 0x200c000

    ERR: write data to device failed

    Edited once, last by hudyj (September 6, 2021 at 5:18 PM).

  • 1. run ddr init:

    update cwr DDR.USB 0xd9000000

    update write ..yourpath../gxl/usbbl2runpara_ddrinit.bin 0xd900c000

    update run 0xd9000000

    2. run uboot (usb tpl)

    update write DDR.USB 0xd9000000

    update write UBOOT.USB 0x200c000

    update write ..yourpath../gxl/usbbl2runpara_runfipimg.bin 0xd900c000

    update run 0xd9000000

  • jaroslaw@jaroslaw-RC410-RC510-RC710:~$ '/media/jaroslaw/30BAD20DBAD1CF88/utils/aml-flash-tool/tools/linux-x86/update' cwr '/media/jaroslaw/30BAD20DBAD1CF88/utils/aml-flash-tool/tools/linux-x86/DDR.USB' 0xd9000000

    ................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................

    Transfer Complete! total size is 49152 Bytes

    jaroslaw@jaroslaw-RC410-RC510-RC710:~$ '/media/jaroslaw/30BAD20DBAD1CF88/utils/aml-flash-tool/tools/linux-x86/update' write '/media/jaroslaw/30BAD20DBAD1CF88/utils/aml-flash-tool/tools/linux-x86/usbbl2runpara_ddrinit.bin' 0xd900c000

    ..

    Transfer Complete! total size is 32 Bytes

    jaroslaw@jaroslaw-RC410-RC510-RC710:~$ '/media/jaroslaw/30BAD20DBAD1CF88/utils/aml-flash-tool/tools/linux-x86/update' run 0xd9000000

    [update]Run at Addr d9000000

    AmlUsbRunBinCode:ram_addr=d9000000

    jaroslaw@jaroslaw-RC410-RC510-RC710:~$ '/media/jaroslaw/30BAD20DBAD1CF88/utils/aml-flash-tool/tools/linux-x86/update' write '/media/jaroslaw/30BAD20DBAD1CF88/utils/aml-flash-tool/tools/linux-x86/DDR.USB' 0xd9000000

    ERR: write data to device failed

  • jaroslaw@jaroslaw-RC410-RC510-RC710:~$ '/media/jaroslaw/30BAD20DBAD1CF88/utils/aml-flash-tool/tools/linux-x86/update' run 0xd9000000

    [update]Run at Addr d9000000

    AmlUsbRunBinCode:ram_addr=d9000000

    jaroslaw@jaroslaw-RC410-RC510-RC710:~$ '/media/jaroslaw/30BAD20DBAD1CF88/utils/aml-flash-tool/tools/linux-x86/update' write '/media/jaroslaw/30BAD20DBAD1CF88/utils/aml-flash-tool/tools/linux-x86/DDR.USB' 0xd9000000

    ERR: write data to device failed

    Here you have already initialized RAM. In this step, instead of DDR.USB, load the TPL UBOOT.USB to the address described above

    Code
    media/jaroslaw/30BAD20DBAD1CF88/utils/aml-flash-tool/tools/linux-x86/update write media/jaroslaw/30BAD20DBAD1CF88/utils/aml-flash-tool/tools/linux-x86/UBOOT.USB 0x200c000

    then

    Code
    update write ..yourpath../gxl/usbbl2runpara_runfipimg.bin 0xd900c000
    update run 0xd9000000
  • jaroslaw@jaroslaw-RC410-RC510-RC710:~$ '/media/jaroslaw/30BAD20DBAD1CF88/utils/aml-flash-tool/tools/linux-x86/update' cwr '/media/jaroslaw/30BAD20DBAD1CF88/utils/aml-flash-tool/tools/linux-x86/DDR.USB' 0xd9000000

    ................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................

    Transfer Complete! total size is 49152 Bytes

    jaroslaw@jaroslaw-RC410-RC510-RC710:~$ '/media/jaroslaw/30BAD20DBAD1CF88/utils/aml-flash-tool/tools/linux-x86/update' write '/media/jaroslaw/30BAD20DBAD1CF88/utils/aml-flash-tool/tools/linux-x86/usbbl2runpara_ddrinit.bin' 0xd900c000

    ..

    Transfer Complete! total size is 32 Bytes

    jaroslaw@jaroslaw-RC410-RC510-RC710:~$ '/media/jaroslaw/30BAD20DBAD1CF88/utils/aml-flash-tool/tools/linux-x86/update' run 0xd9000000

    [update]Run at Addr d9000000

    AmlUsbRunBinCode:ram_addr=d9000000

    jaroslaw@jaroslaw-RC410-RC510-RC710:~$ '/media/jaroslaw/30BAD20DBAD1CF88/utils/aml-flash-tool/tools/linux-x86/update' write '/media/jaroslaw/30BAD20DBAD1CF88/utils/aml-flash-tool/tools/linux-x86/UBOOT.USB' 0x200c000

    ERR: write data to device failed

  • hudyj

    My guess is that you have a clone device and it is a gxbb (s905) platform, that would explain the PLL error. I'll send you gxbb blobs, well worth a try…

    I don’t want to have a say, but you could try it with the image I made in the same way. (Extract the content with the customization tool.)

    dtech
    July 13, 2021 at 10:00 AM

    I only dare to suggest this because the same model of device has already been revived with it.

  • Hi,

    I have a K1 (or KI ?) plus Amlogic S905 box.

    I think iit is this box.

    Libreelec can be installed witth the GXBB dtb. I searched a very long time for an Android firmware. I tried many.

    A few days ago I found an appropriate one which works (flashed it with Amlogic burning tool).

    mega_link

    Ist's from the website:

    http://androidopinions.com/vensmile-k1-pl…mware-download/. (not my website)

    Edited 3 times, last by runnershigh (May 1, 2023 at 1:11 PM).

  • Hi,

    Please take some box and board photo.

  • In the meantime, we managed to unbrick the KI Plus S905D (1G/8G) in the background with creited.

    The vendor never released a factory image (only an OTA update was released), so it was impossible to repair the bricked devices so far.

    I was able to create an image, close to the factory ROM state, that could be used with the USB burning tool:

    KI_PLUS_S905D_v4_OTA-REPACK-20180815 — Yandex.Disk

    Hi,

    I have some dvb-t2 android box, see post (unknown s905d dvb-t box), and tried your ROM, but did not work. It wrote DDR init failed... Reset.... Can you help me to get the device again alive?

    Thanks

    standal

  • I have some dvb-t2 android box, see post (unknown s905d dvb-t box), and tried your ROM, but did not work. It wrote DDR init failed...

    Any kind of ROMs should not be installed on a box that is not properly identified. Moreover, this is particularly true for boxes with tuners. If you have several pieces of this box, it would be best to make a flashdump from one of the working pieces.