A phone stuck on the boot logo does not need an immediate flash. The safe order is: charge the device and rule out the simple causes, document the customer's approval that data may be lost, take a backup if the phone allows it, and only then flash official firmware that matches the model, build and region. If the phone still hangs on the logo after a clean, matching flash, the problem is most likely the board, the memory or the power rail — not the software.

Most guides published online start with "factory reset" — exactly the step that wipes the customer's photos and apps before you know what went wrong. Start with diagnosis and give yourself a clear decision before the first click.

Separate two states first: a device that is stuck on the logo and going nowhere, and a device that reboots in a loop (bootloop). A loop is usually the system or corrupted data; a hard freeze can be hardware from day one.

  • An interrupted update or a full storage: system files stay incomplete, so boot stops at the logo every time.
  • Corrupted cache or app data after a system update or an untrusted app install.
  • Previously installed mismatched firmware or unstable root/custom recovery: the phone runs for days and then hangs without warning.
  • Mechanical causes: a stuck power button, a faulty cable or accessory, or a weak battery that makes every boot attempt fail.
  • Memory or power: a weak power rail or failing storage shows up first as a logo hang and later as a device that will not start at all.

Shop rule: do not touch "Factory reset" or "Format All" until you have a clear answer to one question — is the customer's data wanted?

This step is the real difference between a professional workshop and a random online guide. Four minutes of documentation protects you from a dispute that can cost more than the device itself.

  1. A clear photo of the logo screen, with the model, IMEI/serial and the customer's complaint recorded in the device file.
  2. An explicit clause in the repair intake receipt: is the data needed, and does the customer accept the flash and the possible loss of it?
  3. A short WhatsApp message before flashing that records the approval in writing; there is a ready template in WhatsApp messages for a repair shop.
  4. Do not start the flash without a written reply or a signature, even if the customer said verbally that the phone is "dead and the data does not matter".

Record all of it in the device file inside a shop system such as Warshati Plus, because the first question you will get two weeks later is: "What exactly did you do to the phone?"

Check the simple causes: button, accessories, charger and cache

Before opening any flashing tool, rule out what does not need a flash at all:

  • Charge for 20–30 minutes with a known-good charger and cable. A nearly empty battery produces a freeze that looks exactly like a system fault.
  • Disconnect everything: SIM, memory card, case and any connected accessory, then try a clean boot.
  • Test the power button mechanically or unplug its flex as a test. A stuck button creates a reboot loop that has nothing to do with software.
  • From recovery: wipe cache partition, then reboot system. This attempt can be the "last chance" to break the loop without losing data; if the loop continues, the next step is flashing official firmware that matches the model (Android Enthusiasts Stack Exchange).
  • If the phone boots: use safe mode to isolate the offending app, then take an immediate backup before anything else.

Recovery and download-mode key combinations differ between brands (usually Power + Volume Up or Power + Volume Down), so confirm the exact combination for the model in front of you instead of trying every option on a customer's device.

Customer backup before flashing: what is possible and what is not

A backup is not a magic step; it depends on what the device itself allows. There are only three cases:

  • The device boots to the system: copy what you can over USB, with the manufacturer's software or through the cloud, and note what did not transfer. Banking app data and encrypted messages usually do not move — say so to the customer in advance.
  • The device only boots to recovery: ADB or a custom recovery, if one is already installed; otherwise there is nothing to wait for, and your time is better spent on the flash.
  • The device does not boot at all: there is no backup. Explain it in writing and document that the customer accepted the flash with the possibility of data loss.

Professional warning: HOME_CSC in Odin preserves data in theory, but it is not a guarantee, and a format can be followed by an FRP lock asking for the previous Google or Mi account, which brings the device straight back to your bench (Android MT). Admitting that a backup is impossible is better than a false promise that loses you the customer.

Official flashing with known tools: Odin and SP Flash Tool

Golden rule: firmware that matches the model, build and region comes first. The wrong firmware is the number one reason a flash completes successfully and the phone still cannot boot (positioniseverything).

Samsung: flashing with Odin

  1. Put the device into download mode and connect it with an original or known-good cable directly to a rear-panel port.
  2. In Odin: BL file in its slot, AP in AP, CP in CP, and the fourth file in CSC.
  3. Leave only Auto Reboot and F. Reset Time ticked.
  4. The important decision: the CSC file wipes the storage completely, while HOME_CSC installs the system and keeps the data (mohamedovic). Choose based on documented consent, not on guesswork.
  5. Wait for PASS; the first boot after flashing can take 15–20 minutes, and a long wait there does not mean the job failed. Do not unplug the cable.
  6. A FAIL message is usually a bad cable or firmware for another region — not always a hardware fault.

MediaTek: SP Flash Tool

  1. Install the MediaTek VCOM drivers before connecting; without them the tool will never see the device.
  2. Load the scatter file from the same firmware package you downloaded, never one from a different package.
  3. Start with Download Only, and keep Format All + Download for difficult cases only (positioniseverything).
  4. Do not keep pressing Download when detection fails, and do not touch the preloader partition without trusted instructions.
  5. The first boot after writing all partitions can take 5–10 minutes, and unplugging the cable mid-write corrupts partitions.

Shop tools and verifying ownership

Boxes and server credits are a normal part of a technician's kit, like a soldering station or a programmer. Before any network unlock, IMEI repair or account-lock job, verify ownership with an invoice or ID, record the job in the device file, refuse suspicious devices, and follow your local law and the manufacturer's rules. Tools, licences and credits are available in the GSM tools store.

Which action for which symptom? A decision table — and when to blame the board

Use the table as a fast decision path before you open any tool:

SymptomFirst actionData impactNext decision
Hangs sometimes, then bootsSafe mode + immediate backupNo lossMonitor after delivery
Reboot loop after an updatewipe cache partition from recoveryNo lossIf it persists: official flash
Stuck after mismatched firmwareFlash firmware matching build and regionLikely lossFormat if still stuck
Stuck after a successful matching flashFormat from recovery + a patient 15–20 minute bootLossIf it stays: hardware check
Not recognised in download modeCable, port, USB driversNo lossCheck power rail and board
No current draw when pressing powerMeasure on a bench power supplyNo lossPower section or board

Signs it is the board: no current draw, no recognition in download mode after trying another cable and fresh drivers, repeated read/write failures, or a loop that survives a clean and matching flash. At that point stop flashing and move to the power rail and memory. More flash attempts will not change the result; they only delay the quote.

Delivery and documentation: test before the device leaves the bench

No device leaves the workshop without a short test list: network and SIM, front and rear camera, fingerprint, charging, sound and microphone, screen and touch, and a Google account that works without a surprise FRP lock.

  • A photo or note of the system build after flashing (build number and firmware version) proving exactly what was done.
  • A delivery receipt with a limited warranty stating that flashing may erase data, and describing the device's outgoing condition.
  • A WhatsApp notification and a tracking message for the customer, with every step logged in the device file.

This is where Warshati Plus saves real time: a device file with the full history, thermal-printed intake and delivery receipts, and a WhatsApp notification when the phone is ready. Try the free trial from the product page and run the workflow above on the next device that lands on your bench today.