← Everything Tech HutDiagnose
🧠

Learn How Tech Works

Build a mental model that lets you diagnose unfamiliar technology instead of memorizing random fixes. Good troubleshooting is controlled evidence gathering.

Guide 1 of 6

The six layers behind most device problems

Power, hardware, firmware, operating system, application, and network/service form a useful troubleshooting stack.

Check these in order

  1. 1Power supplies usable energy. No indicators means start here before software.
  2. 2Hardware performs physical work: screen, storage, memory, radios, sensors, ports, and processors.
  3. 3Firmware starts hardware and exposes it to the operating system; BIOS/UEFI and device firmware live here.
  4. 4The operating system manages drivers, files, permissions, accounts, updates, and apps.
  5. 5Applications and cloud services sit above those layers; a working device can still fail because a vendor server, login, or subscription is unavailable.
What the result means: Ask which lowest layer is proven. A webpage problem does not justify replacing a router until power, link, internet, DNS, browser, and service evidence are separated.

Guide 2 of 6

Describe symptoms without guessing the cause

A precise observation is reusable evidence; a guessed diagnosis can send every later step in the wrong direction.

Check these in order

  1. 1Write what you did, what you expected, and exactly what happened—including lights, sounds, messages, timing, temperature, and repeatability.
  2. 2Replace ‘the battery is broken’ with ‘it shuts off at 40%, works on the charger, and the case is flat.’
  3. 3Ask what changed immediately before the failure: update, drop, liquid, new cable, power outage, account change, or nothing obvious.
  4. 4Compare scope: one app, one user, one device, one room, the whole network, or every user.
  5. 5Photograph errors and record model/version before restarting; transient evidence often disappears.
What the result means: Good symptom descriptions naturally identify the next comparison test and make manufacturer/provider/repair support far more efficient.

Guide 3 of 6

Change one variable and use comparison tests

Controlled A/B comparisons locate a fault without needing expensive diagnostic equipment.

Check these in order

  1. 1Use a known-good cable on the suspect device, then the suspect cable on a known-good device. This separates cable from device.
  2. 2Test the same computer on another network and another computer on the same network.
  3. 3Compare safe mode versus normal startup, external versus internal display, wired versus Wi‑Fi, and near-router versus distant-room results.
  4. 4Change only one thing, write the result, and restore it if it did not help. Multiple simultaneous changes destroy the evidence.
  5. 5Prefer reversible tests before firmware changes, disassembly, purchases, resets, formatting, or account removal.
What the result means: A result that follows the accessory identifies the accessory; a result that stays with the device identifies the device; a result that changes with environment identifies the environment or configuration.

Guide 4 of 6

Protect data before repair

The value of the files can exceed the value of the hardware. Repair strategy changes when no backup exists.

Check these in order

  1. 1Identify irreplaceable items: photos, documents, messages, authentication codes, encryption keys, app databases, and recordings.
  2. 2Use the 3-2-1 idea for important data: three copies, on two types of storage, with one copy away from the device/location.
  3. 3Verify backups by opening sample files and checking dates/counts. A sync icon or successful message is not enough.
  4. 4Record encryption, account, recovery, and two-factor details securely before resets or drive/phone replacement.
  5. 5If a drive clicks, vanishes, or contains the only copy, stop repair attempts that write to it and choose data recovery before system repair.
What the result means: Once data is independently verified, troubleshooting can safely include more invasive steps. Without a backup, preserving access and avoiding writes takes priority.

Guide 5 of 6

Repair safely and buy the right part

Exact model identification, service information, ESD control, battery safety, and part quality matter as much as tool skill.

Check these in order

  1. 1Record full model, revision, region, serial prefix, connector, dimensions, voltage, polarity, interface, and capacity requirements before shopping.
  2. 2Read the manufacturer service manual or a trustworthy model-specific guide from start to finish before opening the device.
  3. 3Disconnect power and battery where documented; use ESD precautions, organized screws, photos, correct drivers, and no force.
  4. 4Treat lithium batteries, mains power supplies, CRTs, lasers, capacitors, broken glass, and liquid contamination as special hazards.
  5. 5Compare the cost of part, tools, adhesive/seals, calibration, data risk, warranty, and comeback time against professional repair or replacement.
What the result means: A cheap part is not cheap if it cannot be calibrated, breaks biometric features, compromises sealing, or damages the board. The correct decision may be repair, professional service, data recovery, replacement, or no action.

Guide 6 of 6

Know when to stop and escalate

Good troubleshooting includes recognizing when the consequence of a mistake is greater than the learning value.

Check these in order

  1. 1Stop for smoke, sparks, burning/chemical smell, battery swelling, exposed mains voltage, serious liquid corrosion, or uncontrolled heat.
  2. 2Escalate when irreplaceable data has no backup, the device is under warranty, or required calibration/pairing tools are unavailable.
  3. 3Use the internet provider for line/signal/provisioning faults, the carrier for SIM/eSIM/account faults, and the vendor for cloud/ownership problems.
  4. 4Use qualified repair for board-level work, high-voltage equipment, structural battery damage, hazardous materials, or safety-critical devices.
  5. 5Bring evidence: exact model, symptom, timeline, photos, error codes, tests performed, results, and what must not be erased.
What the result means: Escalation is not failure. A clear diagnostic handoff prevents repeated basic steps, protects data, and reduces unnecessary part replacement.

Still not sure what is wrong?

Use the guided diagnosis to narrow the problem down safely.

Start guided diagnosis →