Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create partitions [KO] #4

Open
luckydevil13 opened this issue Sep 14, 2018 · 6 comments
Open

Create partitions [KO] #4

luckydevil13 opened this issue Sep 14, 2018 · 6 comments

Comments

@luckydevil13
Copy link

./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
Copy link
Owner

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
Copy link

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

@tech101us
Copy link

tech101us commented Aug 1, 2020

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
Copy link

LITUATUI commented May 9, 2022

Anyone found the solution yet?

@bot45
Copy link

bot45 commented Nov 23, 2022

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
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants