aml-linux-usb-burn
aml-linux-usb-burn copied to clipboard
Stane1983
Create partitions [KO]
./aml-flash --img=./KM8PRO-NMF26Q-20170818.170921.V0321.img --soc=gxl --wipe --reset=n --parts=all
Waiting for Amlogic device to be connected... Rebooting the board ........[OK] Unpacking image [OK] Initializing ddr ........[OK] Running u-boot ........[OK] Create partitions [KO]
how to debug K0 error
Sorry for late reply. Your error means that bootloader can't find matching device tree in dtb.img. You have mismatch somewhere in IMG file.
This problem happens when you don't run aml-flash as root. Run aml-flash as root and the problems is solved.
I'm running into this problem as well. Even when running as root, face the KO error when reaching create partitions. I'm attempting to recover a Tanix TX3 Mini-A. I've tried the Windows AMLOGIC burning tool as well as this tool. Both seem to have issues with partition creation. I'm thinking the internal eMMC is in bad shape.
This problem happens when you don't run aml-flash as root. Run aml-flash as root and the problems is solved.
Apparently this solution does not help everyone, only in certain cases. It did not help me, I think that all the same problems with the memory itself. I think you need to try to pull the logs through the engineering ports on the board[RX,TX,3,3V,GND]
Just a heads up.
In my case the problem was that when I shorted the pins to be able to flash the box, they became "soldered". Therefore the box was always in reset mode. With a pin I "unsoldered" the pins and then I could reflash the box.
I got this tip from the CoreELEC forum.