As many of you already know, and as Dingux troubleshooting guide
says, it's important to put zImage
and then rootfs
files as the very first files on the card.
But what to do if you want to replace the kernel or rootfs image ?
You may just override these files with the new ones, but if you do so - there are chances you won't be able to boot Dingux again,
and you will have to backup files, reformat the card, and only then do the things in a clean way - copy zImage, rootfs and only then copy back all your files you backed up.
What a mess and what a waste of time !
Copying all these gigabytes from and back to card may take a whole hour !
Not to mention a frustration if you have to do that again and again.
Here comes the solution. Instead of all this "I like to move it move it", we will just move zImage
to the beginning of the disk:
1) download http://www.kessels.com/JkDefrag/JkDefrag-3.36.zip
and extract jkdefrag.exe from it
2) find out the drive letter your Dingux card uses - let's say, H:
3) from the directory where you extracted jkdefrag.exe run the following command line (using the appropriate disk drive letter):JkDefrag.exe -a 5 H:\zImage H:\rootfs
Now put your card back into Dingoo and/or reset it - it should pass the Dingux logo screen and boot successfully. Some technical info:
- There are people that don't experience this "stuck at Dingux logo" behavior, and I believe it's connected with the size of the card they are using.
With my 8G card I cannot boot every time I replace zImage.
- I used WinHex to see what happens when you replace or add new files.
I erase a number of files sitting at the beginning of the disk, then copy new file into it and - voila - it doesn't reuse the just freed clusters - but puts the new file somewhere else.