Buyer access is for device lookup and self-check. Inspector access is limited to authorized staff; it does not by itself issue a certification report.

Illustrative scene created with AI, not a photograph of the actual device or inspection. Refer to the issued device report for inspection evidence.

What this page means

A proposed phone protocol, not an automatic certificate.

The 68 slots describe the phone checklist structure. Reports must show the applicable total, tested count, pass/fail, not-tested count and reasoned N/A. A badge can appear only after real inspection, evidence review and a released device report. Tablets and earphones require device-specific appendices before they can use a released standard.

Nimall Certified is Nimall’s documented inspection framework. It is not a government, manufacturer, authorized-service or third-party certification.

PHONE OPERATING STANDARD · V0.2 PROPOSED

68 checklist slots across 9 modules.

Open a module to see every checkpoint, method, pass condition and evidence requirement.

68checklist slots9 modules

01 Identity & provenance8 checks Confirms the device identity, lawful source and absence of undisclosed ownership or management locks. Examples: ID01 · Model and regional variant; ID02 · Serial and internal IMEI consistency; ID03 · Storage capacity View all checksHide checks

ID01

Model and regional variant

Method: Compare Settings/About, chassis label and intake record.
Pass condition: Model and regional variant agree; target-market relevance is recorded.
Evidence required: Settings capture and exterior label photo.

ID02

Serial and internal IMEI consistency

Method: Compare system identifiers with available chassis, tray and intake references.
Pass condition: Identifiers are internally consistent; any mismatch is HOLD.
Evidence required: Masked identifier captures from each available source.

ID03

Storage capacity

Method: Read system-reported total capacity and compare it with the intake listing.
Pass condition: Recorded and system-reported capacity agree.
Evidence required: Storage settings capture and intake reference.

ID04

Supplier invoice and chain of custody

Method: Review the supplier invoice, intake party, dates and internal hand-offs.
Pass condition: A traceable source and custody record exists with no unresolved gap.
Evidence required: Restricted internal invoice and custody references; not public.

ID05

Available blacklist or loss check

Method: Query an approved available source and record source, date and coverage.
Pass condition: No adverse result within the documented scope; scope limits are disclosed.
Evidence required: Dated internal lookup reference and source name.

ID06

Activation Lock or FRP cleared

Method: Connect to a network and complete normal activation without bypass; remove test accounts before release.
Pass condition: No former-owner credential is required and the final reset is rechecked.
Evidence required: Activation steps, reviewer record and final setup-screen evidence.

ID07

Carrier or SIM lock and market compatibility

Method: Read lock status and use a target-market SIM where available.
Pass condition: Lock status is disclosed and target-market compatibility is confirmed or HOLD.
Evidence required: Settings capture plus SIM registration or call record.

ID08

MDM, finance or remote-management restrictions

Method: Inspect management profiles, enrollment prompts and activation restrictions.
Pass condition: No active MDM, finance or remote-management restriction may limit ownership or normal use; any active restriction is HOLD/FAIL even if disclosed.
Evidence required: Profile/settings captures and activation notes.

02 Cosmetic condition7 checks Records measured visible wear separately from functional eligibility and safety decisions. Examples: CO01 · Screen glass scratches or cracks; CO02 · Rear cover condition; CO03 · Frame and corners View all checksHide checks

CO01

Screen glass scratches or cracks

Method: Clean the screen; inspect under fixed lighting and distance; count and measure defects.
Pass condition: No crack; scratches are measured, photographed and assigned to the actual grade.
Evidence required: Front photos under consistent light with scale reference.

CO02

Rear cover condition

Method: Inspect the cleaned rear surface under fixed lighting; count and measure wear.
Pass condition: No unsafe breakage or lifting; visible wear is graded and disclosed.
Evidence required: Rear photos with close-ups and scale where needed.

CO03

Frame and corners

Method: Inspect all edges and corners; record dents, chips and lengths.
Pass condition: No structural deformation; measured wear matches the stated grade.
Evidence required: Four-edge and four-corner photo set.

CO04

Camera cover condition

Method: Inspect every lens cover under angled light and verify image impact.
Pass condition: No crack or obstruction affecting capture; marks are disclosed.
Evidence required: Lens-cover close-ups and matching test images.

CO05

Seams, bending or lifting

Method: Check panel seams and flatness visually and with a straight reference.
Pass condition: No bending, separation or lifting; any such finding is HOLD or FAIL.
Evidence required: Edge-profile photos and measured gap notes.

CO06

Screws and repair-entry evidence

Method: Inspect screw heads, seams and tool marks for prior opening evidence.
Pass condition: Evidence is recorded; unresolved repair source or safety concern is HOLD.
Evidence required: Macro photos and repair-disclosure reference.

CO07

Ports, grilles and tray exterior

Method: Inspect ports, grilles and SIM tray for damage, debris and deformation.
Pass condition: No hazardous damage or obstruction; cosmetic wear is disclosed.
Evidence required: Close-up photos before and after safe cleaning.

03 Display & touch8 checks Checks pixels, burn-in, brightness, touch coverage and display-related parts disclosures. Examples: DT01 · Dead or stuck pixels; DT02 · Burn-in or persistent image; DT03 · Brightness and uniformity View all checksHide checks

DT01

Dead or stuck pixels

Method: Show black, white, red, green and blue full-screen patterns in a dim controlled area.
Pass condition: No visible dead or stuck pixel under the documented method; findings are measured.
Evidence required: Five screen photos and test pattern/version reference.

DT02

Burn-in or persistent image

Method: Display neutral grey and solid fields after normal use and observe persistence.
Pass condition: No persistent ghost image visible under the recorded setup.
Evidence required: Grey-field photo and observation time.

DT03

Brightness and uniformity

Method: Check low, mid and maximum brightness on a neutral field.
Pass condition: Brightness changes smoothly with no abnormal flicker or severe non-uniformity.
Evidence required: Photos at three levels and reviewer note.

DT04

Full-screen touch grid

Method: Trace every cell and edge of a controlled touch-grid test.
Pass condition: Every required cell records the trace with no gap or dead zone.
Evidence required: Completed grid capture and tool/version reference.

DT05

Multi-touch

Method: Use a controlled multi-touch tool and record simultaneous contacts.
Pass condition: The device records the expected contacts for its supported design.
Evidence required: Tool capture showing contact count.

DT06

Ghost touch

Method: Observe idle screens, typing and repeated drags for uncommanded input.
Pass condition: No uncommanded touch or repeated unexpected movement is observed.
Evidence required: Timed observation notes and video if a fault appears.

DT07

Brightness adjustment and auto mode

Method: Move the brightness control and test auto response where the model supports it.
Pass condition: Manual control works; supported auto mode responds to controlled light change.
Evidence required: Control captures and supported-feature note.

DT08

Display parts warnings and features

Method: Review parts/service history and verify advertised display features.
Pass condition: Warnings and replaced-display limits are disclosed; unresolved source or safety is HOLD.
Evidence required: System-history capture and feature-test notes.

04 Battery & charging8 checks Uses supported readings and controlled raw tests; missing validated baselines never become an automatic pass. Examples: BC01 · Battery health percentage; BC02 · Cycle count where available; BC03 · Swelling and thermal safety stop View all checksHide checks

BC01

Battery health percentage

Method: Read a supported numerical health value and record tool or system path and date.
Pass condition: At least 85% for an eligible phone with a validated reading; otherwise UNVERIFIED/HOLD.
Evidence required: Dated system/tool capture with method version.

BC02

Cycle count where available

Method: Read the manufacturer-supported cycle count field when the model exposes it.
Pass condition: Value is recorded exactly; never estimated. A natively unsupported field may be N/A with evidence.
Evidence required: System capture or documented unsupported-state evidence.

BC03

Swelling and thermal safety stop

Method: Inspect for swelling and monitor abnormal heat during controlled charging and workload.
Pass condition: No swelling or unsafe thermal behaviour; any concern stops testing and blocks release.
Evidence required: Exterior profile photos and temperature method/raw notes.

BC04

Wired charging stability

Method: Charge with a known-good compatible cable and adapter while observing connection stability.
Pass condition: Charging remains stable without repeated disconnects or unsafe heat.
Evidence required: Accessory IDs, start/end percentage and observation notes.

BC05

Wireless charging where supported

Method: Use a known-good compatible pad and verify a stable charging session.
Pass condition: Supported wireless charging starts and remains stable; unsupported design is N/A with evidence.
Evidence required: Pad ID, model support reference and charge capture.

BC06

Fixed 20-minute workload raw record

Method: Run the approved non-destructive workload; record raw start/end percentage and temperature.
Pass condition: Only passes against an approved model baseline and temperature method; missing baseline is HOLD.
Evidence required: Shared raw workload log with PS04, timestamps and model baseline version.

BC07

Fixed 30-minute idle raw record

Method: Leave the device in the approved idle state; record raw start/end percentage and temperature.
Pass condition: Only passes against an approved model baseline; missing baseline is HOLD.
Evidence required: Timed idle log, environment note and baseline version.

BC08

Battery parts or service warnings

Method: Review manufacturer parts/service messages and battery warnings.
Pass condition: Verified replacement is disclosed; unresolved source or safety is HOLD, not labelled counterfeit.
Evidence required: System-warning capture and repair evidence reference.

05 Cameras, audio & sensors12 checks Exercises each available camera, audio path, core sensor and haptic function. Examples: CA01 · Each rear camera still capture; CA02 · Front camera still capture; CA03 · Near and far autofocus View all checksHide checks

CA01

Each rear camera still capture

Method: Select every available rear camera and capture the same controlled near and wide scene.
Pass condition: Every advertised rear camera captures a clear file without error.
Evidence required: Original test images labelled by camera.

CA02

Front camera still capture

Method: Capture a controlled well-lit image with the front camera.
Pass condition: Front camera opens, focuses and saves a clear image.
Evidence required: Original front-camera test image.

CA03

Near and far autofocus

Method: Tap-focus on near and far reference targets with each focusing camera.
Pass condition: Focus moves and settles clearly at both distances without repeated hunting.
Evidence required: Near/far images and short focus video if needed.

CA04

Video record and replay

Method: Record a timed clip with movement and sound, then replay it on the device.
Pass condition: Recording saves and replays with synchronized visible image and audio.
Evidence required: Original clip and duration reference.

CA05

Flash

Method: Capture with flash in a controlled low-light scene.
Pass condition: Flash fires consistently and the resulting image is usable.
Evidence required: Low-light before/after images.

CA06

Microphones

Method: Record voice memo and video samples from the available microphone paths.
Pass condition: Speech is intelligible without severe dropout or distortion.
Evidence required: Original audio/video samples and path notes.

CA07

Loudspeaker

Method: Play a controlled reference tone and spoken sample at moderate levels.
Pass condition: Output is clear across the tested range without severe rattle or dropout.
Evidence required: Reference-file ID and observation note.

CA08

Earpiece through a test call

Method: Place a controlled test call and listen through the earpiece.
Pass condition: Speech is intelligible and stable during the call.
Evidence required: Masked call log and operator note.

CA09

Proximity sensor

Method: During a test call, cover and uncover the sensor area.
Pass condition: Display turns off near the face and returns when uncovered.
Evidence required: Short test note or video.

CA10

Ambient light sensor

Method: Expose the sensor to controlled darker and brighter conditions with auto brightness enabled.
Pass condition: Supported auto brightness responds in the expected direction.
Evidence required: Light-condition and screen-response notes.

CA11

Accelerometer and gyroscope rotation

Method: Rotate the device through portrait and landscape in a supported app.
Pass condition: Orientation changes consistently without freezing or uncontrolled movement.
Evidence required: Rotation sequence note or video.

CA12

Haptics

Method: Trigger supported keyboard, notification and system haptic events.
Pass condition: Expected haptic events are present and consistent without abnormal noise.
Evidence required: Event list and operator observation.

06 Connectivity8 checks Tests target-region network use with controlled setups, without promising laboratory throughput. Examples: CN01 · SIM registration and two-minute test call; CN02 · Mobile data; CN03 · Available Wi-Fi bands View all checksHide checks

CN01

SIM registration and two-minute test call

Method: Insert a compatible target-market SIM, register to network and complete a two-minute call.
Pass condition: Registration and the timed call remain stable. Missing setup is NOT TESTED/HOLD.
Evidence required: Masked network and call record.

CN02

Mobile data

Method: Load a controlled page or file over the registered mobile network.
Pass condition: Data session completes without repeated disconnect; no speed promise is made.
Evidence required: Network type, time and test reference.

CN03

Available Wi-Fi bands

Method: Connect to each available controlled band supported by the device.
Pass condition: Supported available bands connect and exchange data; capability limits are recorded.
Evidence required: Access-point IDs, band and connection result.

CN04

Bluetooth pairing and audio

Method: Pair with a known-good audio device and play a reference sample.
Pass condition: Pairing, connection and audio remain stable.
Evidence required: Accessory ID and pairing/audio notes.

CN05

Outdoor GNSS fix

Method: In an open outdoor area, request a location fix and record time and conditions.
Pass condition: A stable fix is obtained within the approved model method; no laboratory accuracy claim.
Evidence required: Timestamp, environment and diagnostic capture.

CN06

NFC with a known test tag

Method: Read a known non-payment NFC test tag where supported.
Pass condition: Supported NFC reads the tag consistently; no payment transaction is attempted.
Evidence required: Tag ID and read-result capture.

CN07

Hotspot

Method: Enable hotspot and connect one controlled client for a short data exchange.
Pass condition: Client connects and completes the controlled exchange.
Evidence required: Client ID, time and test reference.

CN08

Dual-SIM or eSIM when advertised

Method: Activate and switch between advertised SIM paths using approved test service where available.
Pass condition: Advertised and testable SIM paths register correctly; missing setup is NOT TESTED/HOLD.
Evidence required: SIM-path captures and service/setup reference.

07 Buttons, ports & biometrics6 checks Checks repeated physical controls, data transfer and controlled biometric unlocks. Examples: BP01 · Power and volume buttons; BP02 · Mute, action or home control; BP03 · USB port and data transfer View all checksHide checks

BP01

Power and volume buttons

Method: Press power, volume up and volume down ten times each.
Pass condition: Every press produces the expected response with no sticking or missed input.
Evidence required: Count sheet and operator note.

BP02

Mute, action or home control

Method: Operate each native supported control repeatedly and observe the system response.
Pass condition: Each supported control responds consistently; unsupported native feature may be N/A with evidence.
Evidence required: Control list and response capture.

BP03

USB port and data transfer

Method: Connect to a controlled host and copy a nonpersonal test file in both directions.
Pass condition: Connection remains stable and the file hash matches after transfer.
Evidence required: Cable/host IDs and before/after file hash.

BP04

Physical audio connector where supported

Method: Connect known-good wired audio equipment and play/record a reference sample.
Pass condition: Supported connector outputs and, where designed, inputs audio correctly.
Evidence required: Accessory ID and audio observation.

BP05

Fingerprint unlock 5 of 5

Method: Enroll a test finger and perform five controlled unlock attempts.
Pass condition: Five of five valid attempts unlock; enrollment is deleted before final reset.
Evidence required: Attempt log and deletion confirmation.

BP06

Face unlock 5 of 5

Method: Enroll a test face and perform five controlled valid unlock attempts.
Pass condition: Five of five valid attempts unlock; enrollment is deleted before final reset.
Evidence required: Attempt log and deletion confirmation.

08 Performance & software5 checks Records repeatable boot, software, storage and workload observations without overstating their scope. Examples: PS01 · Boot and restart three cycles; PS02 · OS version, update and support status; PS03 · Storage write and read test View all checksHide checks

PS01

Boot and restart three cycles

Method: Complete three full boot or restart cycles and record each duration and outcome.
Pass condition: All three cycles reach the normal usable state without crash or loop.
Evidence required: Three-cycle timing log.

PS02

OS version, update and support status

Method: Record installed OS, available update result and manufacturer support information at the test date.
Pass condition: Version and support status are accurately disclosed; no future support promise.
Evidence required: Dated settings captures and source reference.

PS03

Storage write and read test

Method: Write and read a controlled nonpersonal test file and compare its hash.
Pass condition: The limited test completes with matching hash; it is not a full-chip guarantee.
Evidence required: File size, timing and before/after hash.

PS04

Controlled 20-minute workload

Method: Run the approved app/camera workload while recording crashes, restarts and raw battery/temperature data.
Pass condition: No crash or reboot; battery/thermal pass still requires an approved model baseline.
Evidence required: Shared raw workload record with BC06.

PS05

Data wipe and former-account check

Method: Perform normal erase, verify setup state, then connect and activate to check prior-owner locks; erase test accounts again.
Pass condition: No former account or file remains and no lock appears during normal activation; not forensic-certified erasure.
Evidence required: Erase steps, activation result and final re-erase record.

09 Safety & report release6 checks Applies safety stops, independent review and the final device-to-report match before dispatch. Examples: SR01 · Visible liquid or corrosion indicators; SR02 · Supplied accessory safety; SR03 · Repair history and parts disclosures View all checksHide checks

SR01

Visible liquid or corrosion indicators

Method: Inspect accessible indicators and visible corrosion without immersion or destructive opening.
Pass condition: No unresolved liquid/corrosion safety concern; no water-resistance recertification claim.
Evidence required: Indicator/corrosion photos and access limitation note.

SR02

Supplied accessory safety

Method: A competent operator identifies supplied accessories and checks condition, compatibility and visible electrical safety.
Pass condition: No unsafe or unidentified supplied electrical accessory is released.
Evidence required: Accessory IDs, ratings and condition photos.

SR03

Repair history and parts disclosures

Method: Review manufacturer history, system warnings and available repair evidence with stated limitations.
Pass condition: Verified repairs are disclosed; unknown warning is not called counterfeit and unresolved risk is HOLD.
Evidence required: System captures and restricted evidence reference.

SR04

Device-specific photos and report match

Method: Compare masked identifiers, distinguishing marks and required photo set with the draft report.
Pass condition: The report and evidence belong to the same device with no unexplained mismatch.
Evidence required: Reviewer comparison checklist and photo index.

SR05

Independent reviewer sign-off

Method: A reviewer separate from the initial inspection checks critical gates, evidence completeness, version and time.
Pass condition: Reviewer resolves every HOLD and signs the internal release record; score cannot override a critical fail.
Evidence required: Internal reviewer ID, timestamp and protocol version.

SR06

Final pre-dispatch recheck and seal

Method: Recheck identity, activation state, physical condition, included items and report match immediately before dispatch.
Pass condition: Device still matches the released report and is sealed without test accounts or biometrics.
Evidence required: Dispatch checklist, seal reference and timestamp.

Recorded outcomes

Pending is not N/A.

Every applicable check ends with a visible consequence. A score never compensates for a critical safety, security or source failure.

Pass

The recorded evidence meets the stated condition.

Disclosed

A cosmetic condition or verified repair fact is shown separately; disclosure does not erase a functional gate.

Fail

The condition is not met. A critical fail blocks release.

N/A

Only for a feature the device was not designed to have, with device evidence.

Not tested / evidence missing

HOLD. No badge or released report until the gap is resolved.

Critical safety, security or source fail = ineligible. Score cannot override it.

AI-generated concept of an inspection handover; not Nimall staff, facilities or inspected stock — Illustrative scene created with AI, not a photograph of the actual device or inspection. Refer to the issued device report for inspection evidence.

Two decisions

Function tested. Condition explained.

Functional gates and cosmetic findings are recorded separately. Any future A/B/C grade must still pass all applicable functional and safety gates.

Every visible defect is counted or measured and photographed under a controlled lighting, distance and scale setup. A/B/C calibration thresholds are pending pilot validation, so no production grade is issued from this Preview.

Proposed A band

The lowest-wear band. The report must still list each measured mark; cracks, bending and lifting are never permitted.

Proposed B band

A middle measured-wear band to be calibrated in the pilot. Exact counts, lengths and photos remain visible to the customer.

Proposed C band

The highest eligible measured-wear band to be calibrated in the pilot; it never permits a structural or safety failure.

Cracks, bending or panel lifting are HOLD/FAIL—not merely a lower cosmetic grade.

85%Battery health

Nimall proposed phone threshold

A number only counts when the method is validated.

For an eligible phone, 85% is Nimall’s proposed minimum battery-health threshold—not an Apple or Samsung standard. If a reliable numerical method is unavailable, the device stays HOLD.

BC06 and PS04 may share one raw 20-minute workload record. BC06/BC07 raw percentages and temperature do not auto-pass without an approved model baseline and measurement method.

Operating workflow

No badge before inspection and independent review.

Real inspection and review must be completed by people. The page and template do not create a valid report or QR code.

1
Intake, identity & safety
Register the device, source evidence and immediate safety stops.
2
Inspection
Run applicable checks with controlled tools and raw records.
3
Repair & retest
Disclose verified work; resolve or retain HOLD items.
4
Independent review
A second reviewer checks critical gates and evidence.
5
Device report
Release only a device-specific, privacy-filtered report.
6
Dispatch
Recheck identity, reset state, included items and seal.
7
Return & reinspection
Reopen the record and inspect again before any new release.

Required setup

Controlled tools and per-unit records.

The exact equipment list must be approved for each model family and site before operations begin.

Known-good compatible cables, adapters, chargers and test accessories
Controlled SIM, Wi‑Fi, Bluetooth, NFC tag and nonpersonal test files
Five-colour display patterns, touch-grid and supported manufacturer diagnostics
Consistent lighting, distance, scale references and camera capture
Approved temperature measurement method and model baselines
Restricted custody/repair evidence store plus independent reviewer account

Device report design

A released report belongs to one inspected device.

Public output contains masked identifiers and an internal inspector code. Full IMEI, invoices, signatures and personal data stay restricted.

Masked identity

What is recorded: Recorded: model, region, storage and masked serial/IMEI.
How it is obtained: Obtained: system settings and matched intake references.
What the customer sees: Customer sees: masked values and match status only.
Why it matters: Why it matters: prevents a generic model report being reused.

Parts & repair

What is recorded: Recorded: verified repairs, warnings and evidence limits.
How it is obtained: Obtained: manufacturer history, system messages and available records.
What the customer sees: Customer sees: verified facts and unresolved limitations.
Why it matters: Why it matters: an “unknown” warning is not automatically counterfeit.

Photos & raw records

What is recorded: Recorded: required angles, measured defects and selected raw logs.
How it is obtained: Obtained: consistent capture setup and controlled tests.
What the customer sees: Customer sees: privacy-filtered device photos and relevant findings.
Why it matters: Why it matters: condition and results can be checked against evidence.

Inspection & review

What is recorded: Recorded: protocol version, timestamps and internal inspector/reviewer codes.
How it is obtained: Obtained: human inspection plus independent review.
What the customer sees: Customer sees: dates, version and masked staff codes.
Why it matters: Why it matters: shows which released procedure governed the result.

Report lookup status

What is recorded: Recorded: release status and report reference when a real backend exists.
How it is obtained: Obtained: not generated by this page or blank template.
What the customer sees: Customer sees: currently a SAMPLE process explanation only.
Why it matters: Why it matters: no QR or lookup capability is claimed before a real service exists.

SAMPLE · UNRELEASED

Example report structure — not a valid device report.

NO VALID REPORT

No real identifier, inspection, pass result or QR code is represented here. The fields below show how a future released record would separate counts and outcomes.

DeviceSample phone / masked ID ••••

Applicable slots: —
Tested: —
Passed: —
Failed: —
Not tested: —
N/A with reason: —

Public view never exposes full IMEI, supplier invoices, signatures or personal data.

Supporting operator templates

Blank records for human completion.

These files contain no passed results and do not issue a badge. A trained operator and independent reviewer must complete and approve the real record.

Download blank CSV · English Download blank CSV · العربية Download blank JSON template

Protocol v0.2 is proposed. Model-specific acceptance limits and equipment approval must be released before operational use.

Method references

Manufacturer guidance used as input.

These sources help shape the proposed methods. Apple and Samsung do not endorse, authorize or certify Nimall.

Release boundary

A badge requires a completed, reviewed and released report.

Until the pilot, model appendices, equipment and real per-device reporting workflow are operational, the framework remains proposed.

Not every Nimall device or item is Nimall Certified.
This page does not automatically create a certificate, report or QR code.
Inspection does not create an unconditional warranty or replace stated return and warranty terms.
A badge status must be traceable to one released, privacy-filtered device report.

Search Trending

New Arrival

All Categories