NavKal .zenc rebuild online
Puts your edited read back into a NavKal container, using the original as the mould. Runs in your browser against our server — there is nothing to install and no licence to keep alive.
Sending costs nothing. We confirm we have your files, run the job on our server and tell you whether we can do it. You decide about paying after that — and you get a ready-to-use .zenc file.
| Price | 250 credits ($250.00) |
| You upload | .nav / .bin + .zenc |
| You get back | .zenc |
| Max size | 64 MB |
| Applies to | MaxxForce DT · MaxxForce N9 / N13 · Siemens SID803 · NavKal |
- A ready-to-use .zenc file, in seconds
- A yes-or-no answer on your file before you pay anything
- Works from any machine — nothing to install or license
- Charged per file, only when it succeeds
- No copy of your file is kept, ever
| NavKal .zenc decrypt | 250 cr |
| INSITE .eif opener | 120 cr |
| INSITE .eif rebuild | 120 cr |
How it works
Four steps, and you find out whether it can be done before you pay anything. What you get back is a ready-to-use .zenc file.
Upload it here. We confirm on screen that it arrived, with its name and size. This costs nothing.
We run the whole job on our server and answer one question: can we do this file, yes or no. If the answer is no you are told why, and nothing is charged — ever.
Only if the answer was yes. The price is shown before you decide, you tick to accept the payment terms, and the credits come off your balance.
Straight away, in the browser. Your file is processed in memory and never written to our disks.
How you pay
This tool costs 250 credits per file. Credits are prepaid and one credit is one US dollar — 250 credits is $250.00, with no subscription, no monthly fee and no minimum order.
You buy credits with a card or a PayPal account on the credits page, in packs — the larger packs carry a bonus, so a shop doing several files a week pays less per file. Credits do not expire and every movement, spent or returned, is listed in your account. Before any payment goes through — buying credits, or spending them here — you tick a box to accept the payment terms, and they are shown in full at that moment rather than hidden behind a link.
If a job fails after you have paid, the credits go back to your balance automatically and a refund line appears in your history. You are never charged for a file you did not receive.
How the NavKal .zenc rebuild works
Going the other way is harder than it looks, and this is the part most people get wrong. A NavKal container is not the read with a wrapper around it. When it holds a flash transcript, it also carries sequence numbers, module identifiers and a tail that NavKal checks — details that cannot be invented from a read alone.
So the original file does the work: your untouched .zenc is the mould, and only the bytes that came out of the module are replaced with yours. Everything else is preserved exactly. That is why the tool asks for two files and refuses to work with one.
Then the result is opened again and compared against the read you uploaded, byte for byte, before you are given it. If a single byte differs, you get an error and a refund instead of a file. That check is the whole point: a transcript only writes the regions the original flash session wrote, so an edit outside those regions cannot survive the round trip — and a file that flashes a module with your changes silently missing is far worse than being told no.
Checksums are your business, not ours: this tool rebuilds the container and does not touch the content of the read. If the read needs its checksum recalculated first, do that before you rebuild.
Questions
Because the container carries information that is not in the read — session details the file needs in order to be accepted. Rebuilding it from scratch would mean guessing them. Using your original as the mould means nothing has to be guessed.
It means your change sits outside the region the original file writes to the module, so it could not be carried over. Nothing is charged. Usually it means the read was edited somewhere the original flash session never touched — or that the .zenc you supplied as the mould is not the one this read came from.
No, and deliberately so — it hands back exactly the bytes you supplied, wrapped. Use the Siemens SID checksum tool on this site first if your read needs that, then rebuild the container.
No. The file is processed in memory and never written to disk. Nothing is stored, nothing is indexed, and the result only exists in your browser once it comes back. Close the tab and it is gone.
The credits go back to your balance automatically and a refund line appears in your credit history. You are only ever charged for a file you actually received.
No. It runs on our server, so it works from a workshop laptop, a machine in the yard, or a computer that has never had manufacturer software on it. There is no licence, no dongle and nothing to keep alive.