OK, first, some boiler plate:
- An absolute path starts with a / and is always valid.
- A relative path starts with any other character. It’s only valid from a specific directory.
So let’s break down the command:
edl qfil bin/rawprogram.xml bin/patch0.xml flash/ --loader=bin/prog_emmc_firehose_8953_ddr.mbn
edl is the name of the binary we wish to run
qfil is an argument that specifies edl’s mode, it expects several options, in order:
- the PATH to rawprogram.xml
- the PATH to patch0.xml
- the PATH to the .bin files
—loader= specifies that edl should use a specific binary to communicate with the device. It expects one option:
- the PATH to prog_emmc_firehose_8953_ddr.mbn
Let’s imagine an example:
You open a terminal, then clone and build edl.
The path to your edl binary is now most likely:
/home/you/edl/build/
Next, you download and extract the rom from this thread. It’s likely path is:
/home/you/Download/kingston-ha-rom
Now you go to flash the rom, and copy/paste my example command. But it doesn’t work, why?
You supplied edl with the wrong paths!
My example, for brevity, only shows the relative path that coordinates with the files in the rom archive.
For the command to work in your environment, you must update the paths in your command to reflect where the files actually are.
So, given our example, a correct command would be:
edl qfil /home/you/Download/kingston-ha-rom /bin/rawprogram.xml /home/you/Download/kingston-ha-rom/bin/patch0.xml /home/you/Download/kingston-ha-rom/flash/ --loader= /home/you/Download/kingston-ha-rom/bin/prog_emmc_firehose_8953_ddr.mbn
Though you could also do it with a relative path:
edl qfil ../../Download/kingston-ha-rom/ bin/rawprogram.xml ../../Download/kingston-ha-rom/ bin/patch0.xml ../../Download/kingston-ha-rom/flash/ --loader= ../../Download/kingston-ha-rom/ bin/prog_emmc_firehose_8953_ddr.mbn
To the shell, both of these commands evaluate exactly the same.
So when I say “check your paths” this is what I mean.