Synthetic Samsung reset-pair set, version 1.0
===============================================

Every file here was written by generate.py from a fixed seed (20261106). No file comes from a device. Run
codes, times, region codes, firmware names, identifiers and operator names are invented. All times are UTC.

What a "pair" is
  One invented Samsung handset captured two ways at about the same moment: a "full file system" folder view
  (ffs/) and an unpacked "bug report" view (bugreport/). Each handset was reset at known times and had SIM
  region changes before, between and after. The set lets you compare what each evidence source keeps.

What is in it
  pairs/<pair id>/ffs/efs/recovery/history            recovery runs, oldest first
  pairs/<pair id>/ffs/efs/recovery/extra_history      format lines, linked to history by the two-letter run code
  pairs/<pair id>/ffs/efs/imei/mps_code.dat           the current region (sales) code
  pairs/<pair id>/ffs/cache/recovery/                 last_log, last_log.1 ..., last_history, last_extra_history
                                                      (absent in 2 pairs: an empty cache folder)
  pairs/<pair id>/ffs/data/misc/bootstat/factory_reset   empty file; its modification time is the value
  pairs/<pair id>/ffs/data/property/persistent_properties.txt   text rendering of the boot-reason history
  pairs/<pair id>/ffs/data/system/users/0.xml         text rendering of the primary user record
  pairs/<pair id>/bugreport/bugreport-<...>.txt       the main bug report text (excerpt: sections the set models)
  pairs/<pair id>/bugreport/dumpstate_log.txt, main_entry.txt, version.txt
  pairs/<pair id>/bugreport/FS/cache/recovery/        a copy of the latest recovery run (4 pairs only)
  reference_answers.json                              the reference answers, one record per pair
  reference_answers.csv                               one row per recovery run, same content
  WORKSHEET.txt                                       questions to answer from the files
  generator/generate.py                               the script that wrote all of this (MIT)
  LICENCE.txt                                         licences

12 pairs in 5 categories: two_resets_plain, clock_1970, clock_gap_disagrees, one_reset, three_resets.

What the layouts are based on
  The recovery files follow SectraTEK Lab article LAB-0001 (Samsung recovery and reset trail). The recovery
  log text follows the log lines of AOSP recovery (https://android.googlesource.com/platform/bootable/recovery/+/refs/tags/android-14.0.0_r1/recovery.cpp).
  The bug report text follows the section headers described at
  https://source.android.com/docs/core/tests/debug/read-bug-reports . The bootstat record follows AOSP
  bootstat (the event value is the file modification time). Details those sources do not give are invented
  (how requested_time is written, the wording of dumpsys lines, the boot-reason cap of 3 entries, the
  FS/ folder in the bug report, text renderings of two binary or XML files). A tool that works on this set
  has been tested against the model, not against devices. It says nothing about accuracy on real phones.

The reference answers are not inside the pair folders, so you can work blind and compare after.

Check files with SHA256SUMS.txt or manifest.json (next to this archive).
Licence: data CC BY 4.0, generator MIT.
