I wait 30 mins not change. 
Good morning ,when you plug in power cord do you get any lights on when holding reset button using burn card method.Also rename MINI_MXIII_107L1_0425.img to aml_upgrade_package.img. Also if no lights are showing you might have to use original remote and press power button to start process. Also you can try without hdmi connected and wait for lights to come on
For an old box, there is a lot of effort going into this.
Try putting any random zip file in with the three files
Guys!
CE is boot from SD card, I now repair the partitions.
Hmmā¦ error writing
CoreELEC:~ # dd if=/dev/zero of=/dev/bootloader
dd: error writing '/dev/bootloader': No space left on device
1644465+0 records in
1644464+0 records out
841965568 bytes (803.0MB) copied, 4.716681 seconds, 170.2MB/s
CoreELEC:~ #Yes, as you could boot the burncard, you can also run CE. The only thing missing to normal release: your box has no bootloader, therefore you need to additionally apply the uboot to the SDcard.
Regarding your repair:
I would not call it an error. Zero device is infinite, so it will write to the partition until itās full. The strange thing is that the partition seems to have size of 803MB, should be 4MB.
Your partition table seems to be still broken. you should focus on fixing this first (if possible). To fillup the partitions with the right content is quite easy then.
Whatās the result of mmc partconf?
Have you tried bumercs tip with modified .ini settings?
Try store init 4 may also work
/dev not the eMMC.
CoreELEC:~ # df -h
Filesystem Size Used Available Use% Mounted on
devtmpfs 803.0M 803.0M 0 100% /dev
/dev/mmcblk0p1 511.7M 170.0M 341.7M 33% /flash
/dev/loop0 155.5M 155.5M 0 100% /
/dev/mmcblk0p2 13.5G 19.0M 13.5G 0% /storage
tmpfs 906.1M 0 906.1M 0% /dev/shm
tmpfs 906.1M 9.4M 896.7M 1% /run
tmpfs 906.1M 0 906.1M 0% /sys/fs/cgroup
tmpfs 906.1M 2.6M 903.5M 0% /var
tmpfs 906.1M 0 906.1M 0% /tmp
CoreELEC:~ #Can you show ls /dev/mmc* and ls /dev/ result?
CoreELEC:~ # ls /dev/mmc*
/dev/mmcblk0 /dev/mmcblk0p1 /dev/mmcblk0p2
CoreELEC:~ # ls /dev/
amaudio ion tty13 tty53
amaudio_ctl kmem tty14 tty54
amaudio_utils kmsg tty15 tty55
amhdmitx0 lirc0 tty16 tty56
amstream_abuf log tty17 tty57
amstream_hevc loop-control tty18 tty58
amstream_mpps loop0 tty19 tty59
amstream_mpts loop1 tty2 tty6
amstream_rm loop2 tty20 tty60
amstream_sub loop3 tty21 tty61
amstream_sub_read loop4 tty22 tty62
amstream_userdata loop5 tty23 tty63
amstream_vbuf loop6 tty24 tty7
amsubtitle loop7 tty25 tty8
amvideo mali tty26 tty9
amvideo_poll mem tty27 ttyS0
amvideocap0 mmcblk0 tty28 ttyS1
aocec mmcblk0p1 tty29 ttyprintk
ashmem mmcblk0p2 tty3 tv
audiodsp0 mqueue tty30 ubi_ctrl
autofs net tty31 uhid
block network_latency tty32 uinput
btrfs-control network_throughput tty33 uio0
bus null tty34 unifykeys
char ppmgr tty35 urandom
console ppp tty36 vcs
cpu_dma_latency ptmx tty37 vcs1
di0 pts tty38 vcs2
disk random tty39 vcs3
display rfkill tty4 vcs4
efuse rtc tty40 vcs5
esm_rx rtc0 tty41 vcs6
fb0 shm tty42 vcsa
fb1 snd tty43 vcsa1
fd stderr tty44 vcsa2
fsck.log stdin tty45 vcsa3
full stdout tty46 vcsa4
fuse sw_sync tty47 vcsa5
ge2d tty tty48 vcsa6
gpio_keyboard tty0 tty49 video10
hwrng tty1 tty5 wifi_power
i2c-0 tty10 tty50 zero
initctl tty11 tty51
input tty12 tty52
CoreELEC:~ #Assuming /dev/mmcblk0 is your eMMC, there should also be /dev/mmcblk0boot0, /dev/mmcblk0boot1 and /dev/mmcblk0rpmb. As they donāt show up, maybe thatās the reason you cannot revover via bootcard.
As there is also no /dev/bootloader/ device showing up, i guess the following will also fail:
dd if=/dev/zero of=/dev/bootloader bs=4M count=1
dd if=/storage/bootloader.PARTITION of=/dev/bootloader bs=512 seek=1
Maybe this will work:
dd if=/storage/bootloader.PARTITION of=/dev/mmcblk0 bs=1M
This is the bootloader.PARTITION (848 KB)
But at this point, Iām out of ideas if/how to fix. Maybe some more skilled persons like @anon88919003 can give you further tips.
result:
CoreELEC:~ # dd if=/storage/downloads/bootloader.PARTITION of=/dev/mmcblk0 bs=1M
0+1 records in
0+1 records out
868352 bytes (848.0KB) copied, 0.013280 seconds, 62.4MB/s
CoreELEC:~ #After reboot, please show ls /dev/mmc* and ls /dev/ result again.
Now cant boot the Coreelec, maybe burn the SD again, I continue tomorrow.
Best option is to get the original firmware for your device and use Burn Card Maker and short the eMMC.
By shorting the eMMC the bootloader then you will force the device to boot from the SD, the restore process is automatic from there.
Before shorting pins try this https://mega.nz/file/TtEy3CbA#tTpSM1BG1ltPhe8dnbarnv-SV-LiHkDiZX3KJwN1e94 older boot card maker with this https://mega.nz/file/v8ViBA6K#_c216zH3UZqUkOlabyu-umh7E7KOaWFbM-X-YNJOPk8 u-boot.bin file. Change language to English by clicking 2nd drop down button. Method burn u-boot bin file to sdcard ā¦ Insert sdcard in box power on with reset pressedā¦ After this you can connect with usb burning tool and .img fileā¦I do not have s905 soc box to test but this method worked on older socs
U-boot.bin will not be read from the SD if you do not short the pins.
Using Burn Card Maker is the same as using USB Burning Tool, it just doesnāt require a USB A to A lead and a computer to be plugged into the device.
I used eMMC short pins method, results:
SD: Android robot stop X
UBT: 9% stop, message: [0x30405004]UBOOT/Partition boot/Verify patition/Error result
Maybe damaged the eMMC only 7.2 GB show, but this is 16 GB chip.
gxb_p200_v1#mmc dev 1
[mmc_init] mmc init success
mmc read lba=0x14000, blocks=0x400
Amlogic multi-dtb tool
Cannot find legal dtb!
start dts,buffer=0000000073ed29a0,dt_addr=0000000073ed29a0
get_partition_from_dts: FDT_ERR_BADMAGIC
!!!!get dts FAILED
mmc get partition error!
switch to partitions #0, OK
mmc1(part 0) is current device
gxb_p200_v1#mmcinfo
Device: SDIO Port C
Manufacturer ID: 65
OEM: 646f
Name: M MOR
Tran Speed: 25000000
Rd Block Len: 512
MMC version 4.41
High Capacity: Yes
Capacity: 7.2 GiB
Bus Width: 8-bit
gxb_p200_v1#Maybe you are using incorrect firmware for your device then.
Coreelec boot from SD UART log: