iPhone Won't Turn On? Boot-Loop & Board-Level Diagnosis

Before assuming the worst, rule out the easy causes. The overwhelming majority of won't-turn-on cases are a frozen device or a deeply drained battery, not a hardware fault. Work through these in order and give each one real time rather than rushing.

A force restart does not erase anything. It simply cuts power to a stuck system and forces it to start fresh. A hard charge matters because a deeply discharged lithium-ion battery can sit below the voltage the phone needs to even show the charging screen, sometimes for 15 to 30 minutes, before it wakes up. DFU mode is the deepest software recovery state and can revive a phone that a bad update has effectively bricked. Each step targets a different cause, so do not skip ahead.

• Force restart (iPhone 8 and later): press and release Volume Up, press and release Volume Down, then press and hold the Side button until the Apple logo appears. Keep holding for a full 15 to 20 seconds, not just a quick tap.
• Hard charge: use a known-good Apple or certified cable with a wall adapter (not a laptop USB port or a flaky power bank). Leave it plugged in, untouched, for at least 30 minutes before deciding nothing is happening. Then try a second cable and a second charger to rule out the accessory itself.
• Check for any sign of life: a faint vibration on a button press, the phone getting warm near the camera, a flash of the Apple logo that then disappears, or the screen glowing grey but staying black. Note exactly what you see, because that detail is your diagnostic clue.
• DFU restore: connect to a computer running Finder, or Apple Devices/iTunes, and enter DFU mode. A DFU re-flash can recover firmware, though a full restore does erase the phone, so back up first if it still powers on at all. If the computer never detects the phone in DFU, that itself points to a hardware-side fault.

If the home fixes fail, the single most useful thing you can do is correctly classify which of three states your phone is in. These three behave very differently and point to completely different parts of the hardware. Getting this right saves time, money and a lot of wrong assumptions before anyone opens the phone.

Describe your symptom to a technician using these terms and you have already done half the triage yourself.

When you press the button, your iPhone runs a precise sequence. Each stage depends on the one before it. A failure anywhere along this chain stops everything downstream, which is exactly why one tiny part can leave the whole phone dark. Understanding this chain is what separates a real diagnosis from swapping parts and hoping.

Think of it as a relay race. If the baton drops at stage two, stages three through seven never happen, no matter how healthy they are.

• Battery: supplies the raw cell voltage. A dead, swollen or deeply discharged battery, or a bad battery connector, stops everything at the very start.
• Charging IC (Apple's USB/charging controller): negotiates USB power and tells the system a valid source is connected. A failed charging IC can mean no charge, no DFU detection, and a phone that will not power even with a good battery.
• PMIC (power management IC): the heart of the board. It takes the battery rail and generates the many regulated voltage rails the rest of the phone needs. A failed PMIC is a classic no-power cause.
• Power rails: the individual regulated voltages (for example +1V8, +3V3, and the main SoC core rails). A shorted rail, often from liquid damage or a failed capacitor, pulls voltage down and blocks boot.
• CPU/SoC: once its rails are stable, the processor wakes and begins boot. If the rails are unstable under load, you get a boot loop rather than a cleanly dead board.
• NAND (storage): the CPU reads the operating system from NAND flash. A failing or cracked NAND solder joint is a leading cause of boot loops and the Apple-logo-then-restart pattern.
• Display and backlight: last in line. The backlight boost circuit lights the panel. A fault here gives you the black-but-alive phone: everything works, you just cannot see it.

A genuinely dead iPhone, with no vibration, no warmth and no DFU detection, almost always has a fault in the first half of the power chain. The board is not getting past the point where it can even start booting. After ruling out the battery and its connector, a board-level technician puts the board on a bench power supply and watches the current draw the instant power is applied.

That current reading is diagnostic gold. A board drawing zero milliamps is failing to even begin its power-up, pointing at the charging IC or the line feeding the PMIC. A board that draws a small, steady amount and then stalls suggests the PMIC starts but a rail will not come up. A board that pulls a high, locked current, sometimes called a dead short, means a rail is shorted straight to ground, frequently a failed capacitor or a liquid-corroded line. Each of those is a different repair, and you cannot tell them apart from the outside, which is exactly why guessing at part swaps wastes money.

A boot loop is the opposite of a dead board: it proves power is reaching the CPU and the phone is trying to start. The fault is that something fails partway through boot, so the system gives up and restarts, over and over. Because the CPU is alive, the cause is usually one step further along the chain.

The most common hardware cause of a hardware boot loop is the NAND, the storage chip. A cracked solder joint under the NAND, common after a drop or with age, intermittently breaks the data path so the CPU cannot reliably read the OS. Another cause is a rail that is fine at idle but sags the moment the CPU draws full current, which often traces back to a marginal PMIC or a weak capacitor. Software boot loops also exist, from a bad update, a failed jailbreak or corrupted system files, and those are fixable with a DFU restore. The practical rule: if a clean DFU restore on a computer fixes it, it was software. If the phone loops even in DFU or fails the restore at a specific point, suspect NAND or a power rail, and that is a motherboard repair.

This is the most misdiagnosed state and, happily, often the least serious for the core board. The phone vibrates on a force restart, gets detected by a computer, maybe rings or makes the connect sound, but the screen stays black. That means the entire power chain and the CPU are working. The problem lies in the display path.

The two usual suspects are the display connector or display itself (a loose, damaged or failed panel after a drop) and the backlight circuit on the board. The backlight boost converter steps battery voltage up to drive the panel's LEDs; if its driver, coil, filter or a backlight fuse fails (again, drops and liquid are common triggers), the image is actually being generated but there is no light to see it by. You can sometimes confirm a backlight fault by shining a torch at an angle across the screen and faintly seeing the interface. A display swap fixes the panel cases; a backlight repair is a focused board-level job restoring that one circuit.

Liquid damage deserves its own section because it is the great disguiser. It rarely fails one neat thing. Instead, water (especially anything with minerals, salt, sugar or soap) leaves a conductive, corrosive residue that creeps across the board, bridging lines that should never touch and slowly eating away at others. A phone can work for days or weeks after a spill, then die when corrosion finally bridges a critical rail.

Because liquid creates shorts and corrosion across many points, it can mimic any of the three states above, dead, boot loop or display failure, depending on which line corrodes first. The right response is not to keep charging it, which drives current through corroded paths and worsens the damage, and not to bury it in rice, which does nothing for residue already inside. Proper treatment is to open the phone promptly, inspect it under a microscope, and clean the board with isopropyl alcohol and an ultrasonic bath to physically remove residue before it corrodes further. Only after a clean can a technician honestly diagnose what is actually damaged underneath. Time genuinely matters here: the sooner the board is cleaned, the more is recoverable.

Here is the honest line between a simple fix and a microsoldering job. If the phone responds to a force restart, a hard charge, a cable or battery swap, or a DFU restore, it is not a board-level repair and you should not pay for one. The board-level reality begins only when those steps are exhausted and the fault sits in the power chain or storage itself.

Board-level work means diagnosing on a bench power supply, reading current draw, tracing rails, and then microsoldering: removing and reballing or replacing a BGA chip such as the PMIC, charging IC or NAND, repairing a shorted line, or rebuilding a backlight circuit. This is skilled work done under a microscope at controlled temperatures; it is not a part you simply slot in. iTweak has been doing board-level micro-soldering since 2012 and runs an 80-point diagnostic on every device, with a see-the-fault-before-you-pay approach, so you are paying to fix a confirmed fault rather than to find out what is wrong.

Costs vary hugely by the exact fault, the iPhone model and parts availability, so treat the figures below as approximate market-survey ranges, not quotes. The point is relative scale: a cable swap or restore costs nothing, a battery is modest, and board-level microsoldering sits higher because of the skill and equipment involved. A precise quote should come only after a proper diagnostic.

At iTweak, the 80-point diagnostic establishes the real fault first, and the price is set against the actual repair rather than a guess. Always insist on seeing the diagnosed fault before approving any board-level work.

Board-level diagnosis has always depended on the technician's experience, a schematic, a boardview and a steady probe. Recently that work has started to get AI assistance. One notable public example is Wrench Board, a source-available diagnostic workbench built by microsoldering technician Alexis Chapellier of Repair Valley. It ingests a board's schematic and boardview, models the power-up chain, and can run a deterministic engine that reasons forward (kill this part and the board blocks at this boot phase) and backward (these symptoms point to these suspect parts, probe here next), while a technician keeps the iron in hand. Per its makers, Wrench Board placed 2nd in Anthropic's Build with Opus 4.7 Claude Code hackathon in April 2026.

For transparency: iTweak did not build Wrench Board, did not enter that hackathon, and is not affiliated with Anthropic or Repair Valley. We mention it because it reflects where careful, board-aware diagnostics is heading. In our own workshop we use AI-assisted diagnostics alongside the bench supply, microscope and a technician's judgement. When such a tool sees the board, that means a technician deliberately captures an image with a microscope for it to read; it is not an autonomous camera roaming the board. And any learning is the recall of confirmed past repairs on the same device, not training Claude on customer data. The diagnosis still belongs to the human at the bench.

Quick answers to the questions we hear most when an iPhone won't turn on.

• My iPhone won't turn on at all, is it definitely dead? No. Try a force restart, a hard charge for 30+ minutes on a known-good cable and charger, and DFU detection on a computer first. Many no-power cases are a frozen system or a deeply drained battery, not a hardware fault.
• What is the difference between a boot loop and a dead phone? A dead phone shows no life at all; a boot loop shows the Apple logo and restarts repeatedly, which proves the CPU is getting power and is trying to start. They point to different parts and different repairs.
• Can a boot loop be fixed without opening the phone? Sometimes. If it is caused by software, a DFU restore from a computer can fix it. If it loops even in DFU, or the restore fails at a set point, the cause is usually NAND or a power rail, which is a motherboard repair.
• My screen is black but the phone vibrates and rings, what is wrong? That is black-but-alive: the board and CPU work, and the fault is in the display path or backlight circuit. Shine a torch across the screen; if you faintly see the interface, it is likely a backlight fault.
• I dropped my iPhone in water and it still worked, then died. Why? Liquid leaves corrosive residue that bridges and eats board lines over time, so it can fail days later. Stop charging it, do not use rice, and get the board cleaned with isopropyl alcohol and ultrasonic promptly to limit corrosion.
• Is board-level repair worth it versus replacing the phone? Often yes, especially for newer or higher-end iPhones where a targeted PMIC, charging IC or NAND repair costs far less than a new device. A proper diagnostic tells you the real fault and cost before you decide.
• Will I lose my data? A force restart and entering DFU mode do not erase data; a full DFU restore does. Board-level repairs that recover the original NAND aim to preserve your data; always ask first, and back up whenever the phone still powers on.