All articles

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

11/10/2026· 4 min read

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

A phone that keeps restarting or gets stuck in a bootloop is one of the most common walk-in complaints — and one of the easiest to misdiagnose. This workflow helps your techs separate a software crash from a hardware fault, quote honestly, and avoid a comeback repair.

Process overview
Process overview

What the customer usually reports

Listen for the exact pattern before you touch the device. The symptom narrows the diagnosis fast:

  • Restarts at random, sometimes mid-call or mid-app
  • Restarts only under load (camera, games, navigation)
  • Restarts only while charging
  • Stuck on the manufacturer logo, never reaching the home screen
  • Boots fine, then dies after a few minutes of use

Write the pattern on the ticket. It is the single most useful clue your tech will have.

Step 1: Intake and data-risk conversation

Before any repair, confirm whether the customer needs data recovered. A bootlooping phone may still be readable, and repeated forced reboots can make recovery harder. Set expectations in writing: a repair that fixes the boot loop does not guarantee the data survives. If data matters, treat it as a separate job with its own quote.

Step 2: Rule out the cheap causes first

Do the quick checks before opening anything:

  • Force restart with the correct button combination for that model
  • Boot into safe mode to see whether a third-party app is the trigger
  • Check free storage — a completely full device can crash and reboot
  • Inspect the charging port for lint, corrosion, or bent pins
  • Try a known-good cable and charger, then a known-good battery if the model allows
  • Ask about recent drops, water exposure, or OS updates

If the phone behaves in safe mode, you are likely looking at a software or app issue, not a hardware failure.

Step 3: Software diagnosis

For suspected software faults:

  1. Back up whatever is accessible.
  2. Check for a pending OS update or a failed update that left the device unstable.
  3. Clear the cache partition where the platform supports it.
  4. Remove recently installed apps, especially ones with background services or accessibility permissions.
  5. As a last resort, reinstall the firmware — and tell the customer this wipes the device.

Document each step. If the phone still reboots after a clean firmware install with no apps restored, the fault is almost certainly hardware.

Step 4: Hardware diagnosis

When software is ruled out, work through the likely hardware causes in order of cost and risk:

  • Battery: a worn or swelling battery can cause random shutdowns and reboot loops, especially under load. Check health data where available and inspect for swelling.
  • Charging port and flex: a damaged port or liquid-corroded flex can cause power instability and reboots while charging.
  • Power button: a stuck or shorted power button reads as a constant press and forces restarts. Test the button feel and check for debris.
  • Liquid damage: corrosion on the logic board is a classic bootloop cause. Look for residue and treat it as a board-level job.
  • Logic board faults: a failing power management IC, damaged solder joints from a drop, or a bad storage chip. These need micro-soldering skills and a separate, clearly priced quote.

Step 5: Quote with options, not guesses

Give the customer a tiered quote: software-only fix, battery or port replacement, and board-level repair. Explain that the board-level option is the one that saves the device when cheaper fixes fail. Get approval in writing before proceeding, and note the no-fix, no-fee policy if you offer one.

Step 6: Test before pickup

After repair, run the device hard before you call the customer:

  • Reboot it several times manually
  • Charge it and use it while charging
  • Run the camera, GPS, and a video call
  • Confirm the storage, battery health, and network are stable
  • Leave it on the bench for a while to catch intermittent faults

Step 7: Close the ticket cleanly

Record what you found, what you replaced, and what you ruled out. If the customer declined the board-level repair, note that too — it protects you if the phone fails again and the customer returns. A clear ticket history turns a frustrating symptom into a trustworthy repair relationship.


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