All articles

How to Handle a Phone That Keeps Restarting or Bootlooping: Step-by-Step Diagnosis for Repair Shops

10/17/2026· 4 min read

How to Handle a Phone That Keeps Restarting or Bootlooping: Step-by-Step Diagnosis for Repair Shops

A phone that keeps restarting or bootloops is one of the most common walk-in complaints — and one of the easiest to misdiagnose. This guide walks through a repeatable intake-to-repair workflow so your techs stop guessing and start quoting with confidence.

Process overview
Process overview

What "keeps restarting" actually means

Customers use the same words for very different failures. Before you touch the device, classify the symptom:

  • Random restarts while in use — the phone boots normally, then reboots on its own.
  • Bootloop — the phone restarts repeatedly during startup and never reaches the home screen.
  • Stuck on logo — the device hangs at the Apple or manufacturer logo.
  • Restarts under load — only happens during calls, gaming, charging, or camera use.

Each pattern points to a different root cause, so write the exact behavior on the ticket. Ask the customer when it started, whether it followed a drop, a liquid exposure, an update, or a battery replacement.

Step 1: Intake and customer interview

  • Confirm the passcode and whether the customer needs data preserved.
  • Ask about recent drops, water contact, third-party repairs, and software updates.
  • Note whether the phone is under warranty or has a carrier/insurance plan.
  • Back up the data if the device boots long enough — this protects both the customer and your shop.

Step 2: Rule out software first

Software causes a surprising share of restart complaints, and it's the cheapest thing to test.

  • Boot into safe mode (Android) or recovery mode (iPhone) to see if the restarts stop.
  • Check for a pending OS update or a recently installed app that correlates with the start of the problem.
  • Look for storage that is completely full — it can cause instability and boot failures.
  • On iPhones, review the analytics logs for panic or kernel messages that hint at hardware faults.

If the device is stable in safe mode or recovery, you're likely looking at a software or third-party app issue rather than a board-level fault.

Step 3: Check the battery and power path

A failing or swollen battery is a leading cause of random restarts, especially under load.

  • Test battery health and cycle count where the OS reports it.
  • Inspect the battery connector and flex for corrosion or looseness.
  • Check charging behavior — a phone that restarts only while charging may have a port, cable, or charging IC issue.
  • Look for swelling, which is a safety issue and must be handled carefully.

Step 4: Inspect for liquid and drop damage

  • Open the device and look for corrosion, residue, or water indicators.
  • Check board-level connectors, the display flex, and the charging port flex for damage.
  • Look for loose or partially seated connectors — a common cause of bootloops after a previous repair.
  • On devices with a history of drops, inspect for cracked solder joints or a damaged logic board.

Step 5: Isolate the fault with known-good parts

Swap in known-good components one at a time:

  1. Battery
  2. Charging port flex
  3. Display assembly (if the phone restarts when the screen flex is stressed)
  4. Dock/board connectors

If the restarts stop with a swapped part, you've found the fault. If they continue, the issue is likely board-level and should be quoted as a micro-soldering or board repair job.

Step 6: Quote, document, and set expectations

  • Quote software troubleshooting, part replacement, and board repair as separate line items.
  • Warn the customer that data loss is possible on bootlooping devices and get written acknowledgment.
  • Record the exact symptom, tests performed, and parts swapped on the ticket so the next tech can pick up where you left off.
  • If the device is board-level, explain the timeline and the risk before taking a deposit.

Step 7: Test before pickup

  • Run the phone through a full restart cycle several times.
  • Test charging, calls, camera, and Wi-Fi to confirm stability under load.
  • Confirm the customer's data is intact if that was part of the job.
  • Have the customer sign off on the repair and note any remaining risk.

Common mistakes to avoid

  • Quoting a board repair before testing software and the battery.
  • Skipping the customer interview and missing a recent drop or liquid exposure.
  • Failing to back up data before troubleshooting a bootlooping device.
  • Not documenting which parts were swapped, which makes repeat visits harder to diagnose.

A consistent restart/bootloop workflow turns a frustrating, unpredictable repair into a predictable, quotable job — and keeps customers coming back when the next device fails.


Photo: Tima Miroshnichenko / Pexels

Get repair-shop growth tips in your inbox

Practical guides on pricing, workflow and getting paid. No spam — unsubscribe anytime.

Keep reading

Run your repair shop with RagoxCell

Intake, repairs, invoicing, payments and a customer portal — in one place.

Start free trial