Posts by hudyj

Quote from runnershigh

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)

Display More

Hi,

Please take some box and board photo.

Quote from dtech

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

I had extracted the necessary files from this image and tried to upload as well

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

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

~$ '/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

~$ '/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.

How to get these files?

u-boot.bin.usb.bl2

u-boot.bin.usb.tpl

Quote from bumerc

Ah ok. But I still don't understand how flashing the gxbb fw could affect the boot ROM (BL1). Additional start devices SPI and NAND appeared in the BL1 boot sequence. Ok, let's assume - the card reader in your box is no longer working or the SD card is defective. This could lead to incorrect loading of BL2. I will create an aml_upgrade_package.img file and integrate the new u-boot. You will try to do the USB-burn via UBT.

see the logs from UBT and aml flash tool from linux. UBT shows 0x10105004 error

My box has an s905d SoC. It was bricked by mistake, because I uploaded FW from an older version of s905.

Board name on photo

These are my logs (with a booted SD card),

and board photo

If necessary, I will take a more detailed photo

Anyone have any idea?

Every time the logs start at BL1: 9ac50e ..... with and without an mSD card inserted.

bbb.bmp

I don't know anything about it, but I think this is the info you are looking for:

GXL:Fixed PLL lock failed

I have exactly the same box as the user creited "KI PLUS S905D 1G 8G DDR3 LR"

I used Ubuntu Desktop OS, logs unchanged.

BL1:9ac50e:bb16dc;FEAT:ADFC318C:0;POC:0;RCY:0;USB:0;SPI:0;CHK:A7;EMMC:400;NAND:81;SD:0;READ:0;0.0;CHK:0;

no sdio debug board detected

TE: 2129999

BL2 Built : 15:21:58, Mar 26 2020. gxl g486bc38 - gongwei.chen@droid11-sz

set vdd cpu_a to 1120 mv

set vdd cpu_b to 1050 mv

set vddee to 1000 mv

Board ID = 6

SYS PLL lock check 1

SYS PLL lock check 2

SYS PLL lock check 3

SYS PLL lock check 4

SYS PLL lock check 5

SYS PLL lock check 6

SYS PLL lock check 7

SYS PLL lock check 8

SYS PLL lock check 9

SYS PLL lock check 10

SYS PLL lock failed! reset...

GXL:Fixed PLL lock failed

Quote from bumerc

eMMC, 29-30

Can you show it in the picture? Does this method work on other Samsung eMMC chips?

I ask because I have k1 plus, I don't know what to do next. I uploaded the u-boot.bin.sd.bin file from your post to the mSD card.
my logs:

Quote from bumerc

Short the pins and and press the space bar on the keyboard. This aborts the autoboot

which pins?

Quote

Hi hudyj. I used the port closest to the TFCARD. It is the only one that triggers something in my Windows (new device attached sound).

Regarding the cable, I used one cable from a cooling pad for laptops (no branded).

I would really suggest you to try to use a UART cable, to check exactly what is happening with your device.

Which version of usb burning tool are you using?

I connect the 12V plug. This time I used factory USB A-A cable.

Quote from dtech

Now you just plugged in the UART and got this output, or did you even manage to flash the image I linked earlier?

Amlogic burning tool still showing error with all images, also yours.

[0x10105002]Romcode/Initialize DDR/Read initialize status/USB Control setup error.

in UART unchanged : BL1:9ac50e:a1974b;FEAT:ADFC318C;POC:3;RCY:0;EMMC:0;READ:0;CHK:AA;SD:0;READ:0;CHK:AA;USB:8;