Used phone support checklist

Verify identity

Match model code, storage, region, and carrier status with the listing. Do not rely on a family name alone.

Check remaining support

Look for both major OS promises and security end dates. Prefer primary evidence and account for policy-derived uncertainty.

Check condition and ownership

Confirm activation lock is removed, test core functions, inspect for damage, review recalls, and obtain a receipt.

Verify the listing before discussing price

Ask the seller for the exact model code, sales region, carrier lock status, storage and a photo of the About screen with IMEI, serial and account details hidden. Match those facts to an official identification guide and the DevLifeCheck variant list. A listing titled only ‘Galaxy S21’ can conceal S21 FE, carrier and regional differences. Confirm that the phone activates, that activation lock is removed and that the seller can provide a receipt. If identity remains ambiguous, price cannot compensate for the risk of receiving a different lifecycle record or unsupported radio variant.

Calculate supported life remaining

Read security end, OS commitment, current firmware and cadence as separate fields. A seven-year launch promise does not mean seven years remain today. Recompute the remaining window from the reviewed end month and treat a policy-derived Grade B date as a calculation, not a guaranteed final patch. For an iPhone with no defensible future end, use Apple’s current affected-products and security-release pages instead of inventing a resale horizon. Decide how long you intend to keep or hand down the phone, then require a buffer for migration before the documented support boundary.

Inspect battery and repair evidence

Check for swelling, a lifting display, unexpected heat, liquid damage and low battery health. Do not press or charge a swollen device. Ask who performed any screen or battery repair, which parts were used and whether biometric functions or seals changed. Numeric repairability and battery claims need a named scheme, version, jurisdiction and exact product match. An iFixit score is not an EPREL rating, and an Apple playback estimate is not measured battery endurance. Obtain a repair quote and compare it with supported life remaining, not only with the asking price.

Search recalls in the relevant markets

Use the brand, model code, battery and bundled charger names across CPSC, EU Safety Gate, UK OPSS and Health Canada where relevant. A dated no-match screen means only that those queries found no matching notice; it is not a worldwide safety clearance. If a notice matches, follow the official remedy before buying, charging or shipping the product. Marketplace sellers may reuse photos or omit accessory identifiers, so inspect the actual unit. Keep the URL and date of every regulator search with the purchase notes.

Finish with ownership and recovery checks

Test cameras, microphones, speakers, charging, Wi-Fi, mobile service and buttons during the return period. Verify that the device can install currently offered updates. Before adding important accounts, create recovery codes and ensure another trusted device can complete authentication. After purchase, update first, set a strong screen lock, enable encryption and install only needed apps. Keep the receipt and matched model record. If the seller cannot remove activation lock, the patch is stale beyond the documented cadence, or the identity does not match, walk away rather than treating a lower price as evidence.

Know what this checklist cannot verify

A remote listing cannot prove battery authenticity, water resistance, hidden damage, stolen status in every jurisdiction or future manufacturer support. A clean activation does not certify a repair, and a recent screenshot can be reused by a dishonest seller. Use a protected payment method, written return terms and an in-person or reputable inspection when the risk justifies it. DevLifeCheck provides lifecycle evidence, not a unit-level condition report. If the exact model remains uncertain or an important official source is unavailable, record the result as unknown and do not let urgency or a discount turn missing evidence into a positive conclusion.

Worked examples from the catalog

Use the model identifier and jurisdiction together; a marketed name alone is not enough. These records show how the method is applied to real evidence.

How this guide was produced

DevLifeCheck separates manufacturer commitments, regulator notices and editorial interpretation. The editor checks the linked primary sources, records the applicable model and region, and avoids turning a missing date into an estimate.

Related guidance