Damage symptoms

Screen Damage Symptoms: Start With What You See

Start here when you can describe what the screen is doing but do not yet know why. Compare the closest symptom first, then move into the most likely cause.

  • Start with what you can see
  • Plain-English symptom checks
  • Clear next steps when the cause is still unclear

Start with what you see

Black spots, lines, ghost touch, or dead areas: start with the closest match.

You do not need to know yet whether the cause was pressure, water, or heat. If you can describe what the screen is doing, start with the visible pattern and narrow it down before guessing.

Start here if the screen is showing:

  • A black patch, dark area, or spreading spot

    Start here when the screen shows a visible change you can point to right away.

  • Lines that showed up after pressure or a flex event

    Start with the pattern before you decide whether pressure, moisture, or something else is behind it.

  • Touch acting on its own or becoming hard to control

    Erratic touch, ghost taps, or drifting input belong here before you jump into repair guesses.

  • One part of the touchscreen no longer responding

    Dead strips, corners, or keyboard areas are easier to identify by symptom before you worry about the exact cause.

If your bigger problem is backup, access, or documenting the damage before it changes, switch to the next-step guides instead of comparing more symptoms.

Common symptoms

Choose the symptom guide that matches what changed.

Pick the closest visible pattern first. You can always move to a cause guide after the symptom makes the likely explanation clearer.

Visible pattern

Dark spots on a screen

Start here when you see a black patch, bruise, or dark area but do not yet know whether pressure, water, or heat is the strongest cause.

Usually points toward internal pressure damage, liquid intrusion, or heat-stressed layers rather than a simple software issue.

Visible pattern

Lines after pressure

Start here when vertical or horizontal lines appeared after a squeeze, flex, lid-closure event, or transport pressure.

A good starting point when something physical happened but the exact internal failure is still unclear.

Visible pattern

Ghost touch after damage

Start here when the screen taps, swipes, or types on its own after damage, moisture exposure, or another physical event.

Useful when you need to separate digitizer instability from broader panel failure and decide whether backup comes first.

Visible pattern

Touch dead zones

Start here when one part of the touchscreen no longer responds and the usable area is shrinking.

Helps you decide whether you are dealing with localized hardware damage, a cover-layer problem, or damage that needs service.

Possible causes

Once the symptom is clear, compare the most likely cause.

Pressure, water, and heat can create similar-looking problems. Use the symptom first, then move into the cause guide that best fits what happened.

Likely cause

Pressure damage

Check this when a squeeze, flex event, bag pressure, or closed-lid accident is the strongest explanation once the symptom is clearer.

See cause guide

Likely cause

Water damage

Check this when spill history, condensation, or staged worsening makes moisture the stronger explanation.

See cause guide

Likely cause

Heat damage

Check this when the symptom appeared after direct sun, trapped heat, or another clear heat event.

See cause guide

Quick check

Screen tests

Run tests when the device is still usable enough to capture evidence before you commit to a likely cause.

Run screen tests

Before you keep testing

Stop comparing symptoms once the next safe move is obvious.

These guides should help you identify the problem, not trap you in endless checking once the device, your data, or your claim matters more.

Keep the next move clearer than the theory.

  • Move to action pages when the device still matters more than the diagnosis feels satisfying.
  • Do not keep stress-testing a screen that already shows bruising, unstable touch, or worsening lines.
  • Use cause guides to narrow the problem, but stop there once the next safe move is obvious.
  • Use tests only when the device is stable enough that evidence capture does not create extra risk.

Next move

Move on once the best next step is clear.

Use these symptom guides to get oriented, then switch to backup, documentation, or a cause guide as soon as that becomes the more useful next step.