Is it so hard to understand?
Everyone just write and ask without even try something by themselves.
This is exactly the case you need USB burning tool. It only require BL1 in the SoC itself, doesn’t matter if eMMC is empty or not. When it’s damaged the burning will fail.
Hopefully you did not burn BL1 as well… 
\[21:43:06 402\]\[Global\]\[Inf\]–OpenImg Z:\\KI_PLUS_S905D_v4_OTA-REPACK-20180815.img
\[21:43:06 412\]\[Global\]\[Err\]–\[21:43:06 412\]\[HUB1-4\]\[Inf\]–Connect path=USB xHCI Compliant Host Controller/P0/P3
\[21:43:06 724\]\[HUB1-4\]\[Inf\]–Start burning…
\[21:43:06 787\]\[HUB1-4\]\[Inf\]--------------ERASE BOOTLOADER------------
\[21:43:06 894\]\[HUB1-4\]\[Inf\]–2-2-0-0
\[21:43:07 450\]\[HUB1-4\]\[Inf\]-------------Download DDR.USB-----------
\[21:43:07 457\]\[HUB1-4\]\[Inf\]–2-2-0-0-0-1-0-0
\[21:43:07 458\]\[HUB1-4\]\[Inf\]–Control write pll reg1 0xd9000000:0x000000b1
\[21:43:07 973\]\[HUB1-4\]\[Inf\]–Control write pll reg1 0xd9000000:0x00005183
\[21:43:08 482\]\[HUB1-4\]\[Inf\]–Write initial succeed
\[21:43:08 482\]\[HUB1-4\]\[Inf\]–Upload encrypt at 0xc8100228
\[21:43:08 482\]\[HUB1-4\]\[Inf\]–chipid= 0x01dd856fd3c3ce3478520f53, ulValue = 0xbdfc31bc
\[21:43:08 482\]\[HUB1-4\]\[Inf\]–File change to DDR_ENC.USB
\[21:43:08 482\]\[HUB1-4\]\[Inf\]–Read encrypt value succeed
\[21:43:08 482\]\[HUB1-4\]\[Inf\]–Download DDR_ENC.USB,size: 0!
\[21:43:08 482\]\[Global\]\[Err\]–DDR_ENC.USB
\[21:43:08 482\]\[Global\]\[Err\]–DDR_ENC.USB
\[21:43:08 482\]\[HUB1-4\]\[Err\]–Read item data error, code -1
\[21:43:08 482\]\[Global\]\[Err\]–DDR_ENC.USB
\[21:43:08 526\]\[HUB1-4\]\[Err\]–\[0x10103005\]Romcode/初始化DDR/下载数据/读取镜像失败
\[21:43:08 526\]\[HUB1-4\]\[Inf\]–Close device handle 0x000016e8
| |
|:---|
| |
|----|
### **Support (Dune HD)**
### Hello,
Thank you for your detailed request — unfortunately, we are unable to provide low-level recovery firmware or service tools.
This is ancient box with Android 6 original factory firmware.
The old method we would have to tickle the Nand// short pins/force maskrom mode
Or you would need amlogic bootcard maker/not burn card maker.
Sure there is tutorials on y tube somewhere.
Use the Amlogic Bootcard Maker tool on your computer.
Drag the u-boot.bin file from the working device (or extract it from the .img file you extracted using dd if you are experienced in partition extraction).
Use the tool to flash the bootloader onto the card.
Place the original firmware file (even if it’s a .dff file) or the dd version onto the card.
Insert the card into the faulty device and press the Reset button
then connect the power. If the device boots successfully, it will be ready for flashing.
I don’t actually know the exact name of the boot disk, but if there’s a way to extract it from my computer using the dd command, that would be great.
Hi Zuma,
Thank you for your suggestion. I understand the process with the Amlogic Bootcard Maker tool, but since my device’s eMMC is completely wiped and I am unable to boot or access recovery, I need to take a different approach.
As you mentioned, if it’s possible to extract the bootloader and firmware using dd, I would like to kindly ask for your help in doing so via SSH.
Could you please follow these steps to clone the disk and send me the image?
Log in via SSH on the working device.
Use the following dd command to create a raw image of the device’s eMMC (or system partition):
dd if=/dev/mmcblk0 of=/storage/usb/backup.img bs=1M
(Replace /dev/mmcblk0 with the correct device path if needed.)
Once the image is created, you can transfer the image file to the USB drive and send it to me. You can also compress the file to make it easier to share.
If this is possible, it would be greatly appreciated as it would give me the image I need to restore the system.
Thank you again for your help, and I look forward to your reply.
i try
dd if=/dev/mmcblk0 of=/storage/backup_internal.img bs=1M iflag=direct oflag=direct conv=fsync
I sent you a message with the link…
About | FAQ | Terms of Service | Privacy Policy | Legal Notice