Informative but Individually Unreliable: An Empirical Study of Android Reset Indicators and Their Clocks

Evidence of whether and when an Android device was reset lies in recovery logs, boot-reason properties and setup flags, each dated by its own clock, and descriptions of one or a few devices do not say how often these sources exist or how far their dates can be trusted. We read every reset-related source on 14 full file system extractions (12 Samsung; Android 10 to 16) and seven bug reports from four vendor families, classified the clock of each date, and tested a candidate rule that dates an undated recovery entry from a wipe's requested time. The Samsung recovery history was absent on all three units of one flagship generation, and on three older devices its header clock printed a constant, impossible year that passes a plausibility test. The boot-reason history never held a factory-reset entry, and the setup flags cycled around updates. The rule held on one phone, within 57 s of independent file times; on the only other phone able to test it, its central assumption failed by 526 days, a failure exposed by comparing two anchors. On these devices, reset indicators were informative but individually unreliable: each needs its own clock checked before a date is reported.

Authors

Institutions

Publication Details

Journal
Zenodo (CERN European Organization for Nuclear Research)
Published
2026-10-27
DOI
https://doi.org/10.5281/zenodo.23717926
Primary Topic
Digital and Cyber Forensics
Type
preprint
Controls
|||
ALL TIME
JAN
FEB
MAR
APR
MAY
JUN
JUL
AUG
SEP
OCT
preprint

Informative but Individually Unreliable: An Empirical Study of Android Reset Indicators and Their Clocks

Daniel Kwaku Ntiamoah Addai
Zenodo (CERN European Organization for Nuclear Research)
Digital and Cyber Forensics
preprint

Informative but Individually Unreliable: An Empirical Study of Android Reset Indicators and Their Clocks

Daniel Kwaku Ntiamoah Addai
preprint en

Abstract

Evidence of whether and when an Android device was reset lies in recovery logs, boot-reason properties and setup flags, each dated by its own clock, and descriptions of one or a few devices do not say how often these sources exist or how far their dates can be trusted. We read every reset-related source on 14 full file system extractions (12 Samsung; Android 10 to 16) and seven bug reports from four vendor families, classified the clock of each date, and tested a candidate rule that dates an undated recovery entry from a wipe's requested time. The Samsung recovery history was absent on all three units of one flagship generation, and on three older devices its header clock printed a constant, impossible year that passes a plausibility test. The boot-reason history never held a factory-reset entry, and the setup flags cycled around updates. The rule held on one phone, within 57 s of independent file times; on the only other phone able to test it, its central assumption failed by 526 days, a failure exposed by comparing two anchors. On these devices, reset indicators were informative but individually unreliable: each needs its own clock checked before a date is reported.

Zenodo (CERN European Organization for Nuclear Research)
Prudential Financial (United States) (US)
Digital and Cyber Forensics
AI Navigator

Ask Laika to Summarize, Analyze, and Connect papers live on the map.

Summarize Papers & Methodologies

Extract key findings, datasets, and comparative methods across publications.

Benchmark Rankings & Visual Analytics

Rank top research institutions, authors, funders, topics, and journals by Field-Weighted Citation Impact (FWCI) and paper volume with instant charts.

Connect Distant Disciplines

Bridge topological clusters on the map to find hidden collaborative intersections.

Laika access coming soon