search

Stane1983 / aml-linux-usb-burn

Linux version of Amlogic USB Burn Tool
148 stars 42 forks source link

Create partitions [KO] #4

Open luckydevil13 opened 6 years ago

luckydevil13 commented 6 years ago

./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

Stane1983 commented 5 years ago

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.

hoshi411 commented 5 years ago

This problem happens when you don't run aml-flash as root. Run aml-flash as root and the problems is solved.

tech101us commented 4 years ago

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.

LITUATUI commented 2 years ago

Anyone found the solution yet?

bot45 commented 1 year ago

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]

LITUATUI commented 1 year ago

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.