Your Zidoo was factory-reset (or you just bought a second one). It re-scanned your
files, re-matched them its own way, and re-issued every entry id. Z-Keeper's mirror now describes
a device that no longer exists — but only the mirror. Everything you decided is still here.
The Zidoo
re-scanned by itself. New ids everywhere, a pile of fresh guesses, some of them wrong.
✗ starts over
Blueprint
keyed to this device's entry ids — every one of which the rebuild just discarded. What it
describes is real, but there is nothing left for it to point at.
✗ goes with the reset
Master Catalog
every identity you ever cemented, keyed to the FILE. A device reset can't reach it —
and it is what the player gets rebuilt from.
✓ untouched
The whole repair is teaching the device what your Master Catalog already knows — in roughly
five steps, most of them automatic.
A brand-new Zidoo takes this exact same path — it just has nothing to forget.
Z-Keeper · Rebuilding a device — 2 of 6
Step one: clear what the reset broke
Two tables are keyed to the ids the rebuild discarded — the mirror, and this device's
Blueprint. In Settings → Clear local database, tick both, and leave the
Master Catalog alone.
Clear local database
Choose what to remove. Each box explains what it is and what happens next.
Filesystem inventory your scan of the files on disk
Zidoo snapshot Z-Keeper's mirror of the Zidoo's library
Blueprint (this device's approved catalog) keyed to the ids the device just discarded
Master Catalog matches your cemented identities
Cleared with it: the mirror's movies, collections, series,
seasons and files — plus every file→Zidoo pairing and its approval, because those reference the
entries being deleted.
The recovery data is your Master Catalog, keyed on the
file path — the one thing a reset cannot touch. Tick that box and a repair becomes starting over.
The Blueprint goes because its every row points at an id the device threw away, and it
cannot be repaired before the player is. That costs you only what this device held differently:
its watched and favorite history.
A full sync is required afterwards — but understand what it does:
it re-reads what the device believes now (its own re-scan — some right, some wrong) so
Z-Keeper has an honest picture to compare against. Making the player correct is a later
step, and it's Push fixes that does it.
Both boxes say it out loud: clear these two together — leave the Master Catalog off.
Z-Keeper · Rebuilding a device — 3 of 6
Run a full Sync — and watch the Master Catalog vouch
The Matched phase compares every pairing the device just invented against your cement.
Wherever the Zidoo's TMDB id equals the id you cemented, the pairing is provably correct — so
Z-Keeper approves it for you and shows you the list for transparency.
ScanChangesMatchedUnmatchedBlueprint
Verified matches
0
approved automatically against your cement
Needs your review
0
the device disagrees, or matched nothing
Files on this device
647
re-registered from scratch after the reset
1917 (2019).mkvZidoo says TMDB 530915 · your cement says 530915✓
Alien (1979).mkvZidoo says TMDB 348 · your cement says 348✓
…631 moreevery one of them settled without you clicking a thing✓
631 settled without you. Your review list is 3 files long.
Z-Keeper · Rebuilding a device — 4 of 6
Needs your review: a short list, not a library
What's left is what the device genuinely got wrong on its own: a mis-match, a film it
parked as Unmatched, a file it never registered. The Matching tools are right there in the review —
fixing one here cements it, exactly like fixing it in Identify.
BladeRnr-disc2.mkvthe Zidoo parked it in UnmatchedChange match…
The Cell (2000).mkvmatched to the wrong filmChange match…
Anora (2024).mkvnever registered by the deviceCreate NFO / rename
Your Master Catalog carried 631
of the 647 files. These 3 are the whole afternoon's work — and each fix you
make now becomes the cemented answer, so the next rebuild won't ask again.
Fix them here, or leave them for Push fixes to do in one batch.
Z-Keeper · Rebuilding a device — 5 of 6
Push fixes: tell the device what the Master Catalog knows
Every step so far taught Z-Keeper about the device. This is the one that writes
the other way — and it is what actually rebuilds the Zidoo: your cemented answers pushed onto the
player, replacing the guesses it made on its own.
3
Matches
0
Collections
0
Categories
0
Artwork
0
Metadata
1 · Tell the Zidoo the right match — corrects the entry on the device, no file changes2 · Rename the files — always works; takes effect on the next library scan3 · Create NFO files — a sidecar beside each video, read on an NFO-priority scan
Matches were pushed, so Z-Keeper's picture of the device is now behind the device itself.
Run a full Sync to bring them back in step — the other Push sections stay locked until you do.
Run full Sync
Push writes. Everything else in the repair only reads and asks.
Z-Keeper · Rebuilding a device — 6 of 6
All three agree again
One more full Sync and the repair is done: the device, its Blueprint and the Master
Catalog tell the same story.
The Zidoo
every file matched the way you decided — including the three it got wrong alone.
✓ in step
Blueprint
rebuilt as you approve this device's new catalog — now keyed to ids that exist, and
describing a player that matches your Master Catalog.
✓ rebuilt clean
Master Catalog
unchanged throughout — it's what made the other two recoverable.
✓ the source
Mirroring a new device? Same path, minus the clearing: add the Zidoo,
point it at your files, run a full Sync. Your Master Catalog vouches for every file it already knows, so the new
player arrives on day one with a library it took you months to settle.