How to identify the exact phone model

Start in Settings

Record the model name, model number, and software build from the About screen. A retail name can cover several radio, regional, or carrier variants.

Check the physical device

If it will not start, inspect the box, SIM tray, regulatory label, or receipt. Never publish a serial number or IMEI when asking for help.

Match all identifiers

Use a record only when its model scope fits your phone. If a source covers a family rather than an exact model, the page should say so.

Marketing names are only the first key

A retail name such as Pixel 8, Galaxy S21 or iPhone 16 can represent several radio configurations and regional identifiers. Begin with the marketed name to find the family, then match the model code from Settings, the box or the regulatory label. Record the sales country and carrier if applicable. Storage colour and cosmetic edition rarely control lifecycle policy, but chipset, modem, carrier firmware or national compliance suffixes can. Never assume that a search result for the family automatically covers the phone in hand. The public record should state whether each variant is covered or needs a separate lifecycle review.

Find identifiers without exposing private data

On a working phone, use the About screen to locate model name, model number, software build and Android security patch or iOS version. If the phone will not boot, use the original box, purchase receipt, SIM-tray engraving or manufacturer identification guide. Hide serial numbers, IMEI, EID, phone number and account information before sharing a screenshot. IMEI can identify an individual unit and is not needed for a public lifecycle correction. A safe research record uses a product model, regional SKU, alias or public GTIN, not a subscriber or device-unique identifier.

Resolve family and child records deliberately

A canonical family page can group records for discovery, but a child record must remain separate when its evidence, support date or hardware is materially different. Pixel 6 and Pixel 6 Pro may share a policy source yet keep distinct model identifiers. Galaxy S21 and Galaxy S21 FE launched at different times and must not inherit one calendar result. iPhone regional A-numbers can share a lifecycle statement only when the source scope genuinely covers them. Merging duplicates should preserve old URLs with permanent redirects and an audit trail; splitting a record should start unpublished until evidence is attached.

Match the source at the same level

An exact-model source is strongest when it names the same code printed on the device. A family announcement may still be useful, but the record must label family scope and disclose excluded variants. Regional policy pages should not be described as global. Firmware evidence needs the same care: a build for SM-G991B does not prove delivery to every Galaxy S21 carrier model, and a Japanese Pixel code should not silently become the homepage’s US example. When evidence levels differ by claim, show them separately instead of assigning one blanket grade to the whole product name.

A repeatable identity checklist

Write down brand, marketed name, model code, region, carrier and hardware revision. Compare aliases and public GTINs only as supporting identifiers. Open the manufacturer’s identification page and confirm the physical characteristics or regulatory code. Then open the lifecycle source and verify that it covers the same product scope. If two records compete, prefer the exact code over the prettier name. If neither matches, do not force a result: submit a correction with the non-private identifiers and official source. Accurate unknown is safer than a confident support date attached to the wrong hardware.

When to submit a correction

Submit a correction when a public record selects the wrong canonical code, merges a materially different variant, labels a national source as worldwide, or omits an official identifier that changes the evidence match. Include the canonical page URL, non-private model details and the manufacturer source. Do not include an IMEI, serial number, account screenshot or address. The editor should reproduce the identity, capture the source, document the rationale and publish a readable revision only when the public meaning changes. Minor typography can be fixed without pretending that the evidence was newly reviewed. This keeps identity work auditable without creating fake freshness.

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