MovePhone

A working command-line build of the transfer engine: content sniffing by magic bytes, a plan that separates genuinely new files from ones already there and from name collisions, and a verified copy that writes to a .part file, hashes while streaming and only renames into place on a match. An interrupted move resumes from its ledger without redoing finished work. The source is opened read-only and nothing moves without --apply. It works on a mounted phone folder; speaking USB protocols directly is on the roadmap.

Naming status

Working name only — brand verdict **RENAME** (High). Collision: MovePhone / Moviefone confusion. Use a more distinctive name.

What it draws on

Existing paid software whose best ideas shaped this program: iMazing, Wondershare MobileTrans, TouchCopy, Droid Transfer.

Command line

There is nothing extra to install. The program you download is the command-line tool as well: give it arguments instead of double-clicking it and it runs as one, with its output on your terminal. The standalone builds below are the same engine on its own, for machines where you would rather not ship a window at all.

movephone: no command given

movephone - verified content migration between two mounted phone trees (Techlosoft Device Migration Kit)

USAGE
  movephone inventory --src <dir> [--json]
  movephone plan      --src <old-phone> --dst <new-phone> [--ledger <file.jsonl>] [--json]
  movephone transfer  --src <old-phone> --dst <new-phone> --ledger <file.jsonl> [--apply] [--json]
  movephone verify    --ledger <file.jsonl> [--json]
  movephone help | -h | --help

COMMANDS
  inventory  Walk the source tree, identify every file by MAGIC BYTES (falling
             back to the filename extension only when sniffing is inconclusive,
             and saying which was used), hash it with SHA-256, and report totals
             per content class plus the dedup-adjusted size.
  plan       Inventory both trees and classify every source item as
             new / already-present-identical / name-collision-different-content /
             duplicate-within-source. Prints bytes to move and a time estimate
             derived from a MEASURED throughput sample. Changes nothing.
  transfer   Execute the plan. DRY RUN BY DEFAULT: without --apply it prints
             exactly what it would do and writes nothing. Each file is streamed
             to NAME.part while being hashed, fsynced, compared against the
             source hash, and only then renamed into place. Every completed item
             is appended to the ledger, so an interrupted run resumes.
  verify     Re-hash everything the ledger claims was transferred and report
             drift (missing, resized or altered destination files).

FLAGS
  --src <dir>      The old phone: a mounted directory tree. Opened READ-ONLY.
  --dst <dir>      The new phone: a mounted directory tree. Written only under
                   --apply.
  --ledger <file>  Append-only JSON-lines record of completed items. Required by
                   transfer and verify, optional on plan (where it shows what a
                   resume would skip). Created on first use.
  --apply          Actually perform the transfer. Without it, transfer is a dry
                   run and the destination is not touched.
  --json           Machine-readable JSON output (all four reporting commands).

Short forms -s, -d and -l are accepted for --src, --dst and --ledger.
...

Recorded from the shipped binary, not written by hand.

Source

Every file the program is built from:

console.go · console_test.go · guided.go · inventory.go · main.go · main_test.go · plan.go · sniff.go · transfer.go · verify.go

SHA-256 checksums · build instructions & scope notes · full build plan