but in this software there is no dtv app. i am not able use tv tunner(satellite channels )
You are welcome 
DVB tuner support is only integrated on the kernel side. You can implement DTV in the Android later. Unfortunately, I no longer have a test device to do this. Use LibreElec for these purposes.
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?
no success aml script got from liberlec
I don't understand why you add aml_autoscript to the Android files. It is only used to boot LE. Read these instructions and write LE to the SD card.
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
LibreElec
Write LibreElec img to mSD card. Open the mSD card on the PC. Look for aml_autoscript.. in the first FAT partition.
This script has nothing to do with Android.
Android
*.img unpack
You should only unpack the aml_upgrade_package.img and not extract the individual partitions.
This does not look good. The only thing i can suggest is to use the RAM memory directly. To do this, read this document Amlogic_update_usb_tool_user_guide.
The individual steps are described in section 4.2.
because I uploaded FW from an older version of s905
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.
Second time... Your bootloader also contains this string:
Code "Built : 15:21:58, Mar 26 2020. gxl g486bc38 - gongwei.chen@droid11-sz"
Yes, I am aware of this. Here the gxl bl2 blob is loaded and executed because it used the bootloader I posted. However, this does not explain the difference described above. )
There are KI Plus boards with an S905 processor. A photo of someone else's board does not explain the difference between the two different boot ROM logs.
Please remove the heat sink and attach CPU photo
You are posting logs from 2 completely different devices..
This is from gxl Platform:
BL1:9ac50e:a1974b;FEAT:ADFC318C;POC:3;RCY:0;EMMC:0;READ:0;CHK:AA;SD:0;READ:0;CHK:AA;USB:8;
And this is probably gxbb platform:
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;
The full log would be helpful here. Take some board photos..
files available on sd card are already shown in attached image, in the previous post, (sd card is prepared from boot card maker, then files pasted on it.
ie
aml_upgrade_package.img
gxl_p230_2g_pie.dtb
u-boot.bin
I mean LibreElec files.
"copy unpacked partitions to the sd card"
means copy all unpacked files to sd card root and then
Yes.
Android you can also write to emmc by hand. To do this, you first have to unpack the aml_upgrade_package.img with a repack tool, copy unpacked partitions to the sd card and write to emmc with the following commands:
(First you have to burn the dtb that you already did in step 3), then
sdc_update dtbo dtbo.PARTITION normal
sdc_update boot boot.PARTITION normal
sdc_update recovery recovery.PARTITION normal
sdc_update logo logo.PARTITIO normal
sdc_update system system.PARTITION sparse
sdc_update vendor vendor.PARTITION sparse
sdc_update odm odm.PARTITION sparse
sdc_update product product.PARTITION sparse
reboot[mmc_init] mmc init success
switch to partitions #0, OK
mmc1(part 0) is current deviceNo, everything is fine. I suspect a weak power supply, or something like that..
reading aml_autoscript
** Unable to read file aml_autoscript **This bootloader needs aml_autoscript so that booting from the SD card works. This script is currently missing on the FAT partition of your SD card. I haven't used an LE for a long time - which files are on your LE SD card?
[store]amlmmc erase 1Cannot find dev.emmc was not found. Insert the sd card and manually switch to emmc:
mmc dev 1Now repeat steps 1-3, but without the "reset" command.
There is a little DDR timing problem, I'll try to fix it later.
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;
Log is incomplete.The information about the platform in front of the BL1 is missing. Post the full log. Is that GXBB: BL1… or GXL: BL1…?
How do you write the u-boot on the sd card? Do you have linux?
Try the following steps:
1. Determine the exact name of your block device sdX (sd card) with the lsblk command.
lsblk2. Unmount the FAT partition of the found block device
sudo umount /dev/sdX13. Clean the unpartitioned area on the SD card
sudo dd if=/dev/zero of=/dev/sdX bs=1 count=444
sudo dd if=/dev/zero of=/dev/sdX bs=512 skip=1 seek=1 count=20474. Write this u-boot.bin.sd.bin binary
sudo dd if=u-boot.bin.sd.bin of=/dev/sdX conv=fsync,notrunc bs=1 count=444
sudo dd if=u-boot.bin.sd.bin of=/dev/sdX conv=fsync,notrunc bs=512 skip=1 seek=1
sudo eject /dev/sdX